USB device protocol for a gaming machine

BACKGROUND OF THE INVENTION

[0002] This invention relates to gaming peripherals for gaming machines such as slot machines and video poker machines. More particularly, the present invention relates to standard peripheral communication connections between the gaming peripheral and the gaming machine.

[0003] There are a wide variety of associated devices that can be connected to a gaming machine such as a slot machine or video poker machine. Some examples of these devices are lights, ticket printers, card readers, speakers, bill validators, coin acceptors, display panels, key pads, and button pads. Many of these devices are built into the gaming machine. Often, a number of devices are grouped together in a separate box that is placed on top of the gaming machine. Devices of this type are commonly called a top box.

[0004] Typically, the gaming machine controls various combinations of devices. These devices provide gaming features that augment the features of the gaming machine. Further, many devices such as top boxes are designed to be removable from the gaming machine to provide flexibility in selecting the game features of a given gaming machine.

[0005] The features of any device are usually controlled by a “master gaming controller” within the gaming machine. For example, during a game the master gaming controller might instruct lights to go on and off in various patterns, instruct a printer to print a ticket or send information to be displayed on a display screen. For the master gaming controller to perform these operations, connections from the device are wired directly into some type of electronic board (e.g., a “back plane” or “mother board”) containing the master gaming controller.

[0006] To operate a device, the master gaming controller requires parameters, operation features and configuration information specific to each peripheral device. This information is incorporated into software and stored in some type of memory device on the master gaming controller. This device-specific software operates the features of the device during a game. As an example, to operate a set of lights, the software for the master gaming controller would require information such as the number and types of lights, features of the lights, signals that correspond to each feature, and the response time of the lights.

[0007] One disadvantage of the current operation method for devices controlled by a master gaming controller is that each time a device is replaced the gaming machine must be shutdown. Then, the wires from the device are disconnected from the master gaming controller and the master gaming controller is rewired for the new device. A device might be replaced to change the game features or to repair a malfunction within the device. Similarly, if the circuit board containing the master gaming controller or the master gaming controller itself needs repair, then the wiring from the all the devices connected to the gaming controller must be removed before the gaming controller can be removed. After repair or replacement, the master gaming controller must be rewired to all of the devices. This wiring process is time consuming and can lead to significant down-time for the gaming machine. Further, the person performing the installation requires detailed knowledge of the mechanisms within the gaming machine. Accordingly, it would be desirable to provide a standard communication protocol and/or connection system for installing or removing devices and master gaming controllers that simplifies this wiring process.

[0008] Another disadvantage of the current operation method of devices controlled by a master gaming controller involves the software for the devices. When a new device is installed on a gaming machine, software specific to the device must be installed on the master gaming controller. Again, the gaming machine must be shutdown and the person performing this installation process requires detailed knowledge of the gaming machine and the device. Accordingly, it would be desirable to simplify the software installation process.

SUMMARY OF THE INVENTION

[0009] This invention addresses the needs indicated above by providing a gaming machine having a plurality of “gaming peripherals,” each communicating with a master gaming controller via a standard peripheral interface such as the USB (Universal Serial Bus ). For some gaming peripherals, the communication between the master gaming controller and the gaming peripheral may include various security features such as encryption, secure ports, and secure hubs. For USB compatible communications, characteristics of a USB gaming peripheral class are defined. The USB gaming peripheral class allows features of a USB gaming peripheral in the USB gaming peripheral class to be controlled by a USB host in a manner compatible with USB.

[0010] One aspect of the present invention provides a gaming machine. The gaming machine may be generally characterized as comprising: a master gaming controller designed or configured to control one or more games played on the gaming machine and to communicate with a plurality of USB gaming peripherals using a USB compatible communications; and the plurality of USB gaming peripherals coupled to the gaming machine and in communication with the master gaming controller. Each of the plurality of USB gaming peripherals may comprising: 1) a USB compatible communication connection, 2) one or more peripheral devices specific to each USB gaming peripheral where each peripheral device supports one or more USB features, and 3) a USB peripheral controller designed or configured i) to control the one or more peripheral devices and ii) to communicate with the master gaming controller and peripheral devices using the USB compatible communications. The USB peripheral controller may comprise: one or more USB compatible interfaces wherein each USB compatible interface is mapped to one USB feature in the one of peripheral devices. The gaming machine may be a mechanical slot machine, a video slot machine, a keno game, a lottery game, or a video poker game. The one or more peripheral devices are selected from a group consisting of lights, printers, coin hoppers, bill validators, ticket readers, card readers, key pads, button panels, display screens, speakers, information panels, motors, mass storage devices and solenoids.

[0011] In particular embodiment, the gaming machine may comprise a USB compatible host controller. The gaming machine may also comprise a plurality of USB compatible feature drivers wherein each feature driver communicates with a USB feature on one of the peripheral devices associated with the feature driver. The master gaming controller may be further designed or configured to run feature client processes that communicate with one of the USB features using its associated USB compatible feature driver.

[0012] In yet another embodiment, the master gaming controller may be further designed or configured: 1) to interrogate the USB gaming peripheral to determine capabilities of the USB gaming and 2) to load at least one of a USB gaming peripheral class driver, USB compatible feature drivers and combinations thereof for operating the determined capabilities of the USB gaming peripheral. Thus, the master gaming controller may include a memory storing one or more USB compatible drivers for at least some of the USB gaming peripherals. The USB compatible gaming peripheral class driver may be used for driving each USB gaming peripheral. The USB compatible gaming peripheral class driver may be capable of interrogating the USB compatible interfaces to determine the USB features of the USB gaming peripheral. In addition, the USB compatible gaming peripheral class driver may be capable of loading USB compatible feature drivers for each determined USB feature.

[0013] In particular embodiments, the master gaming controller may include a memory storing software for encrypting, decrypting, or encrypting and decrypting the USB compatible communications between the master gaming controller and at least one of the USB gaming peripherals. The USB peripheral controller may include a non-volatile memory arranged to store at least one of a) configuration parameters specific to the individual USB gaming peripheral and b) state history information of the USB game peripheral. The configuration parameters may include a mapping of the USB compatible interfaces to their respective USB features. The USB gaming peripheral may also comprise one of a USB compatible device controller and USB compatible hub.

[0014] These and other features of the present invention will be presented in more detail in the following detailed description of the invention and the associated figures.

BRIEF DESCRIPTION OF THE DRAWINGS

[0015]
FIG. 1 is a perspective drawing of a gaming machine having a top box and other devices.

[0016]
FIG. 2 is a block diagram depicting a gaming peripheral and its connection to a master gaming controller

[0017]
FIG. 3 is a block diagram depicting a more detailed example of a gaming peripheral in accordance with this invention.

[0018]
FIG. 4 is a flow diagram depicting the gaming peripheral power-up and communication process with the master gaming controller.

[0019]
FIG. 5 is a flow diagram depicting the post power-up communication phase between the gaming peripheral and master gaming controller.

[0020]
FIG. 6 is a flow diagram depicting the details of a general communication process of a peripheral device via a standard peripheral interface as presented in FIG. 5.

[0021]
FIG. 7 is a flow diagram depicting the details of a general event transaction as presented in FIG. 5.

[0022]
FIG. 8 is a block diagram of a USB communication architecture that may be used to provide USB communications in the present invention.

[0023]
FIG. 9 is a block diagram of master gaming controller in communication with a USB gaming peripheral.

[0024]
FIG. 10 is an interaction diagram of communications between a host and a USB gaming peripheral of the present invention.

[0025]
FIG. 11 is a block diagram of a software architecture in a gaming machine for communicating with USB gaming peripheral.

[0026]
FIG. 12 is a method in a gaming machine of initializing communications between the gaming machine and a USB gaming peripheral.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] Turning first to FIG. 1, a video gaming machine 2 of the present invention is shown. Machine 2 includes a main cabinet 4, which generally surrounds the machine interior (not shown) and is viewable by users. The main cabinet includes a main door 8 on the front of the machine which opens to provide access to the interior of the machine. Typically, the main door 8 and/or any other portals which provide access to the interior of the machine utilize a locking mechanism of some sort as a security feature to limit access to the interior of the gaming machine. Attached to the main door are player input switches 32, a coin acceptor 28, and a bill validator 30, a coin tray 38, a belly glass 40, and a monitor mask 42. Viewable through the main door is a video display monitor 34 and an information panel 36. The display monitor 34 will typically be a cathode ray tube, high resolution flat-panel LCD, or other conventional electronically controlled video monitor. The information panel 36 is a back-lit, silk screened glass panel with lettering to indicate general game information including, for example, the number of coins played. The bill validator 30, player input switches 32, video display monitor 34, and information panel are devices used to play a game on the game machine 2. The devices are controlled by circuitry (not shown) housed inside the main cabinet 4 of the machine 2. Many possible games, including traditional slot games, video slot games, video poker, keno, and lottery, may be provided with gaming machines of this invention.

[0028] The gaming machine 2 includes a top box 6, which sits on top of the main cabinet 4. The top box 6 houses a number of devices including speakers 10, 12, 14, a glass panel with display lamps 16, a ticket printer 18 which prints bar-coded tickets 20, a key pad 22 for entering player tracking information, a florescent display 24 for displaying player tracking information, and a card reader 26 for entering a magnetic striped card containing player tracking information. The top box 6 may house different or additional devices than shown in the FIGS. 1 and 2. The devices housed in the top box 6 add features to a game played on the machine 2. During a game, these devices are controlled, in part, by circuitry (not shown) housed within the main cabinet 4 of the machine 2. Peripheral control circuitry in top box 6 also provides some control functions for the top box devices. The top box 6 is designed to be removable from the machine 2. Typically, the top box 6 is replaced to repair a device within the top box 6 or to install a new top box 6 with a different set of devices.

[0029] When a user wishes to play the gaming machine 2, he or she inserts cash through the coin acceptor 28 or bill validator 30. At the start of the game, the player may enter playing tracking information using the card reader 26, the key pad 22, and the florescent display 26. During the game, the player views game information using the video display 34. Usually, during the course of a game, a player is required to make a number of decisions which affect the outcome of the game. The player makes these choices using the player input switches 32. During certain game events, the gaming machine 2 may display visual and auditory effects that can be perceived by the player. These effects add to the excitement of a game, which makes a player more likely to continue playing. Auditory effects include various sounds that are projected by the speakers 10, 12, 14. Visual effects include flashing lights, strobing lights or other patterns displayed from lights on the gaming machine 2 including lights behind the front glass 16 on the top box 6 or from lights behind the belly glass 40. After the player has completed a game, the player may receive game tokens from the coin tray 38 or the ticket 20 from the printer 18, which may be used for further games. Further, the player may receive a ticket 20 for food, merchandise, or games from the printer 18.

[0030]
FIG. 2 is a block diagram depicting a gaming peripheral and its connection to a master gaming controller. The master gaming controller 200 shown in FIG. 2 is housed within the main cabinet 4 of the gaming machine 2 shown in FIG. 1. The master gaming controller 200 controls one or more games played on the gaming machine 2. Typically, the master gaming controller is connected to a mother board or “back plane” 202, which is attached to the back of the main cabinet 4 of the gaming machine 2. The back plane 202 may include an acceptor (not shown) for mechanically engaging or latching to the master gaming controller 200 and a root expansion hub 206 containing one or more standard communications ports 208. The standard communication ports 208 are used to connect to other devices containing standard communication ports.

[0031] The standard communication ports 208, root expansion hub 206, hub 210 and hub 230 and the connections to the devices comprise a communication system that allows the master gaming controller 200 to communicate with devices connected to this system. The devices and the connections shown in the figure are only one embodiment of the present invention. Typically, a device is not required to be plugged into a particular port. Examples of devices, which might be connected to a root expansion hub 206 with standard communication ports 208 on a mother board 202 with a master gaming controller 200, include fiber optic conversion 204, a remote hub 210, a coin acceptor 216, a bill validator and a gaming peripheral 228. These devices may be housed within the main cabinet 4 of the gaming machine 2 or may reside outside of the main cabinet 4. Other examples of devices which might incorporate a standard communication port 208 that communicate with the master gaming controller 200, include the coin hopper 212, the bill validator 214, the coin acceptor 216, the button panel 218, the light array 236, the printer 238, the card reader 240, the camera 242, in FIG. 2 and the speaker 10 which is part of an audio system, the display screen 34, the information panel 36, the key pad 22 in FIG. 1. These devices might be connected directly to the mother board 202 containing the root expansion hub 206 using one or more of the standard communication ports 208 or through one or more devices containing standard communication ports, which are connected to the root expansion hub 206 on the mother board 202. For example, the coin hopper 212 is connected to a standard communication port 222 on the bill validator 214. The bill validator 214 is connected to the root expansion hub 206 on the mother board 202 containing the master gaming controller 200. As another example, the camera 242 is connected to the hub 230 on the gaming peripheral 228, which is connected to the root expansion hub 206 on the mother board 202.

[0032] The root expansion hub 206, which is integrated into the back plane 202, provides breakout connections for devices within the gaming cabinet without requiring additional hardware or non-integrated communication port expansion including the remote hub 210 or the hub 230. Typically, the connections to the root expansion hub 206 are from a connection to a root port within the circuitry of the master gaming controller 200 (i.e., the root port provided by circuitry incorporated into the master gaming controller 200). When the root expansion hub is connected to a root port on the master gaming controller 200, the root expansion hub 206 may be provided with a higher level of security than the other remote hubs including the hubs 210 and 230. In general, any hub can be provided with more or less security than other hubs in the gaming machine. The security for the hub may be provided by limiting access to the interior of the gaming machine using one or more doors with mechanical and/or electrical locking mechanisms. These locks may be monitored by the master gaming controller 200 using sensor devices including electric switches. Further, the ports 208 and 224 within the root expansion hub may have additional security features. For example, access to the ports may be limited using an electronic key or covers with mechanical locks which prevent access. Further, devices connected to these ports may be locked down to prevent the disconnection of a device. Further, electronic or mechanical sensors including evidence tape may be used on a particular port to determine whether a port has been accessed or not. One or more of these security features as well as other security features may be used to secure specific ports on the root expansion hub 206 or any other ports used to connect devices.

[0033] Using the standard communication ports 208 and the root expansion hub 206, the master gaming controller 200 may be removed from the acceptor on the mother board which is attached to the back plane 202 without disconnecting or rewiring any of the devices connected to the standard communication ports 208. Also, additional devices may be connected to the root expansion hub 206 on the mother board 202 without rewiring the mother board 202 and master gaming controller 200. For example, when the remote hub 210 is disconnected from one of the communication ports 208 on the root expansion hub 206 and replaced with a connection to another device, including but not limited to a camera 242, the coin hopper 212, the bill validator 214, or the coin acceptor 216, then the mother board 202 and the master gaming controller 200 would not need to be rewired.

[0034] Also, the standard communication ports in the root expansion hub 206, the hub 210, and the 230 may not accept connections to all types of devices to provide additional security. For example, the level of security on the standard communication port 224 might be higher than the other standard communication ports 208 on the root expansion hub 206. Thus, the standard communication port 224 on the root expansion hub 206 might accept connections only from devices requiring a higher level of security including but not limited to the bill validator 214, the coin acceptor 216, and the gaming peripheral 228. In this example, the master gaming controller 200 would not recognize input from the bill validator 214, the coin acceptor 216 or the gaming peripheral unless these devices were connected through a standard communication port with a higher level of security including 224. This security may be provided by mechanical, electronic or software means or combinations thereof. For example, port 224 may be housed within a secure locking enclosure to ensure that no one can connect or disconnect through that port without having the necessary key. As another example, the master gaming controller includes a temporary port or hub 201. Usually, this port 201 is used for an electronic key and is used for diagnostics and other secure operations on the master gaming controller. During operation of the gaming machine, a device is not typically connected through this port. Secure ports and data encryption help to meet the necessary security requirements for a gaming machine.

[0035] During the operation of the gaming machine 2, the master gaming controller 200 communicates with devices connected through the system of standard communication ports and connections. The master gaming controller 200 includes a memory storing software for executing a standard communication protocol that allows communication with the various devices using the standard communication connections. This communication protocol may include encryption capability for communicating with one or more devices. The master gaming controller 200 communicates with devices to obtain information about a device including whether it is operating properly or whether it is still connected. In FIGS. 4, 5, 6, and 7, this communication process is described in detail.

[0036] During a game, the master gaming controller 200 controls devices. Using the standard communication connections and the standard communication protocol, the master gaming controller 200 may send instructions to a device to perform a specific operation. These instructions may be in the form of low-level or high-level instructions. The master gaming controller 200 sends low-level instructions to devices that it directly controls. Examples of low-level instructions might include turning on a specific light, turning off a specific light, starting a motor, or stopping a motor. The master gaming controller may send high-level instructions to the gaming peripheral 228. A gaming peripheral 228 is a device that contains, for example, a hub 230 with standard communication connections, a peripheral controller 234, and connections to one or more peripheral devices. Typically, the peripheral controller controls one or more peripheral devices. Also, when the communication connections and the standard communication protocol are used, the peripheral controller 234 enables communication between the master gaming controller 200 and one or more peripheral devices. Examples of some peripheral devices, which might be included as part of gaming peripheral 228, are the lights 236, printer 238, smart card reader 240, the bill validator 214, the coin acceptor 216, the button panel 218, in FIG. 2 and the speaker 10, the video display screen 34, the key pad 22, and the florescent display 24 in FIG. 1. The peripheral controller 234 controls the peripheral devices connected to the peripheral controller 234 including the lights 236, the printer 238, and the smart card reader 240. When the master gaming controller 200 sends the high-level instruction to the gaming peripheral 228 requesting an operation from a peripheral device controlled by the peripheral controller 234, the peripheral controller 234 receives a high-level instruction and converts it to the low-level instructions specific to the operation requested from the master gaming controller 200. For example, the master gaming controller 200 might send a high-level instruction to the gaming peripheral 228 to “strobe” its lights 236. The peripheral controller 234 would receive this high-level instruction and send out a series of low-level instructions to the lights 236 including instructions to turn on and off specific lights at specified intervals. As another example, the master gaming controller might send an instruction to the gaming peripheral 228 to “print a coupon”, the peripheral controller 234 would receive this high-level instruction and convert it to a series of low-level instructions for the printer 238 including start motor, print string, advance to new line, advance paper, stop motor. The high-level instruction set that allows the master gaming controller 200 to operate a peripheral device on a gaming peripheral 228 with a peripheral controller 234 is stored as device driver software on a memory device on the master gaming controller 200.

[0037]
FIG. 3 is a block diagram depicting a more detailed example of a gaming peripheral in accordance with this invention. The master gaming controller 200 is connected to the hub 230 which includes standard communication connections on the gaming peripheral. The peripheral controller 234 is connected to the hub 230 using a peripheral connection 300. The peripheral connection 300 is connected to a transient and surge protector 304. The transient and surge protector 304 protects the peripheral controller from signals arriving on the peripheral connections which might damage a control microprocessor 312.

[0038] Power from the master gaming controller 200 is transmitted to a power conversion unit 302. The power conversion unit 302 converts the voltage arriving from the master gaming controller 200 to voltages needed for the control microprocessor 312 of the peripheral controller 234 or any of the peripheral devices connected to the peripheral controller 234 including but not limited to the motor 320, the lights 322 or the printer 324. The peripheral devices may also receive power directly from the power supply unit (not shown) with or without using the power conversion unit 302. The power supply unit is usually contained within the main cabinet of the gaming machine.

[0039] Hardware needed to connect the peripheral controller 234 to a specific peripheral device is located in the peripheral interface 318. At least one or more peripheral devices are connected to the peripheral interface 318. These peripheral devices may include the motor 320, the lights 322, the printer 324, card readers, key pads, button panels, information panels, display screens, bill validators, and coin acceptors. The configuration of the peripheral controller 234, which includes information about the types of peripheral devices controlled by the peripheral controller 234, is stored in a non-volatile memory 316. When the peripheral devices on a gaming peripheral are changed, the non-volatile memory 316 can be replaced or reprogrammed to incorporate the new configuration.

[0040] The peripheral controller contains a control microprocessor 312 that controls communication with the master gaming controller 200. Further, the control microprocessor 312 converts high-level instructions from the master gaming controller 200 requesting specific operations from the peripheral devices controlled by the peripheral controller 234 to low-level instructions needed to perform the operation. In one embodiment, the control microprocessor 312 includes a fixed memory 310, a volatile memory 308, a timer 314, a fail safe 315, and a master controller communication 306. In other embodiments, either the fixed memory 310 or the volatile memory 308 or both may be located outside of the control microprocessor.

[0041] The volatile memory 308 and fixed memory 310 may be upgraded using the volatile memory expansion 309 and the fixed memory expansion 311. The fixed memory expansion 311 might be in the form of an EPROM or flash memory. When flash memory-is used, it may be possible to field upgrade the operating code of the peripheral controller. The volatile memory expansion 309 might be in the form of static RAM which uses a long-life battery to protect the memory contents when power is removed.

[0042] In a preferred embodiment, each gaming peripheral containing a peripheral controller 234 contains an essentially identical control microprocessor 312. In such modular designs, the power conversion circuitry 302 and surge/transient protector circuitry will also be essentially identical from peripheral to peripheral. The only distinctions between peripheral controllers in individual peripherals will reside in the peripheral interface 318 and the information stored in non-volatile memory 316. This allows for rapid design and reduced maintenance of gaming machine peripherals.

[0043] Within the control microprocessor 312, the master controller communication 306 controls the communication between the peripheral controller 234 and the master gaming controller 200. The control microprocessor may be an off-the-shelf device including an Infineon Technologies C541U family of microcontrollers. The master controller communication 306 performs the communication using a standard communication protocol. Essentially, it implements the protocol associated with a standard communications protocol such as USB, IEEE1394, or the like. The timer 314 sends signals to the control microprocessor 312 which controls execution of code. The fail-safe 315 contains code which is independent of the code in the control microprocessor 312. When code within the control microprocessor 312 is lost or malfunctions, the fail safe 315 will reset the entire gaming peripheral. As an example, the fail safe 315 might expect a message from the control microprocessor 312, which includes “do not reset.” When the fail safe 315 receives this message, the fail safe 315 will wait a specified interval for the next “do not reset” message. When the fail safe 315 does not receive a message including “do not reset” after a specified interval, the fail safe 315 resets the gaming peripheral.

[0044] The fixed memory 310 is a read only memory which is not lost when the control microprocessor 312 loses power. The fixed memory 310 stores general code that the control microprocessor 312 uses while operating. The code stored in the fixed memory 310 may be identical in every peripheral controller 234. To control a specific peripheral device, the control microprocessor 312 uses code stored in the fixed memory 310 in conjunction with peripheral device specific information stored in the non-volatile memory 316. The volatile memory 308 stores code, parameters, data from the peripheral devices and data from the master gaming controller 200 that the control microprocessor 312 needs to operate. The data in volatile memory 308 is lost when the control microprocessor 312 loses power. Critical information including the current state of peripheral devices is stored in the non-volatile memory 316. The nonvolatile memory might be an EEPROM, flash card memory or a battery powered RAM. In the event of a power failure or some other malfunction, the information in non-volatile memory 316 is used to restore the gaming peripheral to its state before the malfunction occurred. For example, when a player enters cash into the gaming machine 2, this information can be stored in non-volatile memory 316 on the peripheral controller 234. After this information is stored in non-volatile memory, it will be available to determine the state of the machine 2 when any subsequent malfunctions occur.

[0045]
FIG. 4 is a flow diagram depicting an example of the gaming peripheral power-up and communication process with the master gaming controller. This process is described for one gaming peripheral. For a plurality of gaming peripherals, this process is implemented for each gaming peripheral. When a gaming peripheral loses power which may include an accidental power loss or planned maintenance for the gaming peripheral, the process in FIG. 4 is usually followed. When a gaming peripheral first receives power, the standard control microprocessor, as an example see 312 in FIG. 3, executes self-diagnostics to confirm the peripheral is operating properly in block 400. The control microprocessor will load software stored in its fixed memory. With this software the control microprocessor will execute a series of self-diagnostics to determine that its various components are operating properly. These tests may include testing the processor, timer, fail safe and master communication controller functions of the control microprocessor.

[0046] After the control microprocessor completes its self-diagnostics in block 400, the gaming peripheral's configuration and state history is loaded into the control microprocessor's volatile memory from non-volatile memory outside of the control microprocessor in block 410. The non-volatile memory stores information about the peripheral devices that are connected to the control microprocessor through the peripheral interface. This information tells the standard control microprocessor what type of gaming peripheral it is controlling. The control microprocessor loads the information stored in the non-volatile memory and loads code stored in the control microprocessor's fixed memory into volatile memory on the control microprocessor to operate the peripheral devices. In FIG. 3, the control microprocessor 312, the volatile memory 308, the fixed memory 310, the non-volatile memory 316, and the peripheral interface 318 are one possible embodiment of the hardware needed to implement the process in block 410. One possible example of configuration information, which might be stored in non-volatile memory, is information describing a light panel connected to the gaming peripheral. The non-volatile memory might store information including the type of light panel, the number of lights, the response time of the lights, the signal needed to turn the light on, the signal needed to turn the light off, the communication rate and the communication buffer size for the light. As another example, the non-volatile memory might store configuration information for a motor connected to the gaming peripheral, this information might include the type of motor, the signal needed to turn the motor on, the signal needed to turn the motor off, the response time of the motor, the communication buffer size and the communication rate for the motor.

[0047] In block 410, the control microprocessor loads the state history of the gaming peripheral from the non-volatile memory. The state history includes game information that describes states of the peripheral devices of a gaming peripheral that occur while a game is being played on a gaming machine. For example, state information stored in the non-volatile memory might include the amount of cash a player has entered into the machine, each step of the game, the choices a player has made during the game, the position of reels or the status of lights. When a gaming machine loses power or malfunctions during a game, the information stored in the non-volatile memory is used to restore the gaming machine to the state in the game that occurred just before the power loss or malfunction. In general, when a gaming machine is being powered-up, the gaming peripheral will initialize itself to a pre-determined “safe” state until the master controller connects to it. When communication is established between the gaming peripheral and master gaming controller, the control microprocessor may attempt to transfer relevant state history information it has retrieved from its nonvolatile memory to the master gaming controller.

[0048] In block 420, after self-diagnostics and initializing itself to some state, the peripheral controller may test the peripheral devices that it controls. This step is optional. Examples of some tests the peripheral controller might execute include turning lights on and off on a light panel, printing a test ticket from a printer, displaying a test pattern on a video display screen, or projecting a sound pattern from a speaker.

[0049] In block 430, the peripheral controller establishes communication between the gaming peripheral and the master gaming controller. Using the standard communication connections and the standard communication protocol, the peripheral controller establishes communication with the master gaming controller. One embodiment of the hardware needed for this communication process between the peripheral controller and the master gaming controller is shown in FIG. 3. One example of the initial communication sequence and data exchange between the peripheral controller and master gaming controller can be represented as a series of high-level questions. A typical sequence to establish communication might proceed as a message from the master gaming controller including “is anyone there?” The peripheral controller might respond, “yes” and the master gaming controller might ask, “what type of device are you?” Then, the peripheral controller might respond, “I am a gaming peripheral of some type.” To this question, the master gaming controller might respond, “what is your communication rate and buffer size?” The peripheral controller would send this information to the master gaming controller and the devices would continue to communicate. The questions described above are representative of the type of information that is passed between devices using a standard communication protocol. The actual information passed by the devices corresponding to the questions will be specific to the particular protocol.

[0050] There are many different standard communication protocols including USB or IEEE1394, and the like. Each of these protocols utilizes a standard communication sequence. But, the standard communication sequence may vary depending on the type of protocol that is used. When the master gaming controller is using a USB protocol to communication over the standard communication, the following information or a portion of this information might be exchanged between the master gaming controller and peripheral controller: 1) release specification number, 2) device class, 3) subclass (e.g. version) 4) device communication protocol and revision, 5) Maximum receive and send packet sizes, 6) vendor identification, 7) product identification, 8) device release number, 9) manufacturer string, 10) product string, 11) device descriptor, 12) device protocol, 13) serial number, and 14) number of configuration interfaces. The USB standard is widely-known and described in various references such as USB Hardware and Software, John Garney, Ed Solari Shelagh Callahan, Kosar Jaff, Brad Hosler, published by Annabooks 11838 Bernado Plaza Court, San Diego, Calif., 92128, copyright 1998, ISBN 0-929392-37-X, which is incorporated herein by reference for all purposes.

[0051] After establishing communication with the gaming peripheral, the master gaming controller queries the gaming peripheral for peripheral devices. This process is called the device enumeration sequence in block 440. One or more peripheral devices attached to the gaming peripheral may communicate with the master gaming controller or may be controlled by the master gaming controller during the course of a game. In this step, the master gaming controller requests device information from the peripheral controller. Again, the information exchange between the master gaming controller and peripheral controller can be represented as a series of high-level questions. The format of the information exchange may vary depending on the communication protocol being used. As an example, the first question from the master gaming controller to the peripheral controller might be “do you have any devices?” When the gaming peripheral replies “yes”, the master gaming controller might ask “what is the device?” The peripheral controller will then send information to the master gaming controller, in some format or protocol established before the communication process began, as to the type of peripheral device. This device identification protocol is distinct from the communication protocol.

[0052] For certain devices requiring a higher level of security including but not limited to bill validators and coin acceptors, the master gaming controller might determine which port it is using. Using the device identification protocol and the port information, the master gaming controller may or may not communicate with the gaming peripheral. It may issue an error message and prevent further operation if the device is not using a required port. As a specific example, the master gaming controller may require that an electronic key (e.g., a software dongle) be inserted into to a port prior to operation of that port (as a security measure). When a peripheral device is subsequently connected into the port where an electronic key has been used, the master gaming controller may only communicate with certain types of devices that are allowed access into this port based on the information provided by the electronic key.

[0053] In block 450, the master gaming controller initializes one or more selected device drivers for the peripheral device identified in block 440. Using a device identification number or some other system for identifying the peripheral device, the master gaming controller selects a software device driver which will operate the features of the peripheral device enumerated in block 440. The master gaming controller first searches for a software driver which exactly corresponds to the peripheral device. When the master gaming controller can not locate a software driver which exactly corresponds to the peripheral device, the master gaming controller may search for a similar software driver that might operate all or some of the features of the peripheral device. Examples of peripheral devices which might be operated by a master gaming controller using a software driver include lights, printers, video display screens, coin counters, coin acceptors, bill validators, ticket readers, key pads, motors, and card readers. After choosing a software driver, the master gaming controller makes the software available for use. Usually, this is done by loading the software into memory. When a software driver can not be located for a particular peripheral device, the master gaming controller does not operate this device during the game. When the peripheral device without a software driver is critical for operation of the gaming machine, the master gaming controller may generate an error message.

[0054] In block 440, to select the software driver, the master gaming controller may use a device identification protocol. As an example, the device identification protocol might include a series of numbers which correspond to a specific peripheral device. As an example, combinations of the device class, manufacturer, device protocol and serial number information from a particular device might be used. From these numbers, the master gaming controller would be able identify the type of the peripheral device and its features. Related peripheral devices with similar features might have similar numbers. For example, two versions of a peripheral device, device A and device B might share in common one or more numbers including 11112 to denote device A and 11113 to denote device B. This is similar to the concept of an address mask in network technology. This selection process may vary depending on the peripheral's manufacturer and the driver implementation.

[0055] In block 460, the master gaming controller determines whether the device enumeration sequence is completed. When more devices need to be enumerated, the master gaming controller returns to block 440. In block 460, the master gaming controller might determine whether more devices need to be enumerated by querying the peripheral controller or the master gaming controller might know the number of peripheral devices connected to the gaming peripheral by its type. The type of the gaming peripheral was identified when communication was established in block 430. In block 470, when the enumeration process is completed for all the peripheral devices connected to a peripheral controller, the master gaming controller may look for additional peripheral devices connected to other peripheral controllers to enumerate and return to block 440. When all of the peripheral devices connected to all the peripheral controllers are enumerated, the process shown in FIG. 4 is complete.

[0056] One advantage of the enumeration and device driver initialization process in blocks 440, 450, 460 is that enumeration may occur at any time while the machine is running. For example, when lights connected to the gaming peripheral are not functioning, the lights could be removed from the gaming peripheral for repair and replaced with a new set of lights while the gaming machine is running and the master gaming controller might unenumerate the old lights and then enumerate the new lights. Potentially, the power-up and communication process in FIG. 4 might be carried out by the master gaming controller without intervention by an attendant or other maintenance person.

[0057]
FIG. 5 is a flow diagram depicting the post power-up communication phase between the gaming peripheral and master gaming controller. In this figure, some of the possible communication and operational processes that occur between the master gaming controller and the gaming peripheral during the post power-up operational phase of the gaming machine are described. Some events that might occur during this phase include operating the gaming peripheral during the course of a game, operating the gaming peripheral between games, and operating the gaming peripheral during maintenance.

[0058] In block 505, communication with a peripheral device via a standard peripheral interface occurs. In one possible embodiment, this step may be initiated when the master gaming controller requests an operation or information from one of the peripheral devices comprising the gaming peripheral. In a preferred embodiment, the peripheral controller receives this message as a high level instruction and converts the instruction to one of more low-level instructions needed to operate or communicate with the peripheral device. The details of this step are described in FIG. 6. The low-level instructions from the peripheral controller are sent to the peripheral device via the peripheral interface. The peripheral device receives the instructions and performs the requested operation. As an example, a light panel might turn on a specific light or turn its lights on in a specific pattern including strobing or flashing. After performing the operation, the peripheral device may signal to the peripheral controller that the operation has been completed. In another step, the peripheral controller may verify to the master gaming controller that the requested operation was performed. In another possible embodiment, this step may be initiated when a peripheral device on the gaming peripheral is utilized. For example, a player wishing to start a game might insert a player tracking card into a card reader connected to the gaming peripheral. In this example, the card reader might send a message to the peripheral controller that a card has been inserted. Then, in another step, this message might be relayed to the master gaming controller in some format and a series of communication events between the gaming peripheral and master gaming controller might commence. This type of process where the communication sequence starts in the peripheral device might be occur for a number of different peripheral devices connected to the gaming peripheral including card readers, ticket readers, coin acceptors, bill validators, key pads, and button panels.

[0059] During the communication process in 505, a number of possible steps were identified where the peripheral controller might send information to the master gaming controller regarding the operation of a specific peripheral device. This communication step is called process event in block 510. The details of this process are described later in FIG. 7. When processing an event, critical information from a peripheral device, including but not limited to a coin being accepted by a coin acceptor, a ticket being read by a ticket reader, or a bill validator accepting a bill, is transmitted between the gaming peripheral and master gaming controller so that the information is preserved in the event of a power failure or malfunction during operation of the gaming machine. The communication step in block 510 requires that the peripheral controller and master gaming controller are communicating properly. In block 508, the communication between the master gaming controller and peripheral controller is checked. When normal communication between the master gaming controller and peripheral controller is verified, the event is processed in block 510. When the transaction in block 510 has been processed successfully, the communication between the peripheral controller and master gaming controller continues starting in block 505.

[0060] When a communication problem has been identified between the master gaming controller and peripheral controller, the process branches to block 515. During operation of the gaming machine in block 515, the master gaming controller may send signals to one or more of the peripheral devices connected to the peripheral controller to determine whether the peripheral device is still connected. For communication purposes, the master gaming controller views the peripheral controller and the peripheral device as one entity. When the peripheral controller is disconnected from the master gaming controller, the peripheral devices connected to the peripheral controller through the peripheral interface are no longer able to communicate with the master gaming controller and the master gaming controller might assume all the peripheral devices were disconnected. When a peripheral device is disconnected or no longer communicating with the peripheral controller, the peripheral controller, which is still able to communicate with the master gaming controller, might detect the disconnect and could send a message to the master gaming controller that the peripheral device is no longer communicating or connected to the peripheral controller. For example, a peripheral device may be accidentally disconnected from the peripheral controller as a result of faulty wiring between the peripheral controller and the peripheral device might cause a disconnection. In another example, a peripheral device might be intentionally disconnected from the gaming peripheral and peripheral controller for maintenance of the peripheral device. Further, in another example, the peripheral device might be disconnected from the gaming peripheral and peripheral controller and reconnected with another peripheral device to tamper with the gaming machine. In each of the cases, the master gaming controller is designed to detect the disconnection of the peripheral device. As an example, the USB communication protocol addresses this issue with the design of the communication bus and wiring. The peripheral controllers may assist in detecting disconnects whenever possible.

[0061] The communication between the peripheral controller and the master gaming controller may use “keep alive” messages which are regularly sent to the master gaming controller at specified intervals. When the master gaming controller does not receive this message after a specified interval, it may put the gaming machine or gaming peripheral into an error checking mode. Also, when the peripheral controller believes that a peripheral device has been disconnected, the gaming peripheral may be placed into an error checking mode by the peripheral controller.

[0062] In block 520, the master gaming controller may send a message to the peripheral device at specified intervals asking whether it is operating properly or the peripheral device may send a message to the master gaming controller at specified intervals affirming it is operating properly. The message may be in response to a request by the master gaming controller to perform a specific operation. For example, when the master gaming controller sends a message to a light panel to strobe its lights which is interpreted by the peripheral controller and sent to the light panel, the light panel might send a message back to the peripheral controller verifying that it is strobing its lights. As another example, the light panel or any other peripheral device may send regular messages to peripheral controller including “ready”, “operational” or “performing operation”. In the event the peripheral controller stops receiving these messages or similar messages, the peripheral controller may decide that the peripheral device is not responding properly and place the gaming peripheral into an error checking mode. Further, the peripheral controller may relay this message to the master gaming controller, which may place the gaming peripheral or gaming machine into an error checking mode. When the peripheral is connected and responding properly, the peripheral controller loops back to block 505 for the next communication event

[0063] In block 525, when the peripheral controller or master gaming controller determines that a peripheral device may have been disconnected or that a peripheral device may be responding improperly, a decision is made as to the type of error and response. In block 530, when the peripheral controller or master gaming controller determines that a “critical error” has occurred, the peripheral controller or master gaming controller will log the error and request attendant. An attendant might be requested by lighting a light on the gaming machine or a message might be sent to a remote location requesting some response. A “critical error” is an event that requires external intervention for the machine to clear the error. For example, errors resulting from possible tampering with the gaming machine might result in a critical error. In block 535, when a non-critical error occurs, the peripheral controller or master gaming controller determines whether the error is the result of a planned disconnect.

[0064] In block 540, when a peripheral device is being removed as the result of a planned disconnect (e.g. planned maintenance), the master gaming controller will unenumerate the peripheral device and adjust its operation to reflect the device being removed. The unenumeration of the peripheral device might proceed in the reverse of the enumeration process described in FIG. 4. In the unenumeration process, the master gaming controller would unload the device driver for the disconnected peripheral device and stop communication attempts with the device. Depending on the peripheral device, the gaming machine might continue operating with the peripheral device disconnected. For example, when a light panel is disconnected from the gaming peripheral for repair, the gaming machine might continue operation without the light panel. The ability to unenumerate a device and keep operating is advantageous when the peripheral device can not be immediately repaired or replaced.

[0065] In block 545, in the event of a non-critical error that is not the result of a planned disconnect, the peripheral controller or master gaming controller may attempt to ignore, reset or reinitialize the peripheral, depending on the exact nature of the critical error. Further, the peripheral controller or master gaming controller may log this error in some type of event log. For example, in the process of printing a ticket, the printer may malfunction. When the printer malfunction is deemed a minor error, the peripheral controller or master gaming controller might reset the printer in block 545 and then start the communication process again in block 505 in attempt to print the ticket again. In another possible example, the master gaming controller might ignore the minor error and again request the operation from the device.

[0066]
FIG. 6 is a flow diagram depicting some details of the communication with a peripheral device via a standard peripheral interface in block 505 in FIG. 5. In the power-up phase described in FIG. 4, the master gaming controller establishes communication with the gaming peripheral and selects software drivers for the peripheral devices the master gaming controller can operate. In block 600, the master gaming controller may use the software driver to send the peripheral controller a high-level instruction that requests the operation of a specific feature of the peripheral device. This high-level instruction is sent using the standard communication connection hardware and the standard communication protocol. A possible hardware embodiment of this process was shown in FIG. 2. For a light panel, examples of a potential high-level instructions might include “strobe lights”, “flash lights”, “implement light pattern A”, or “implement light pattern B”. For a ticket printer, examples of potential high-level instructions might include “print a ticket for 10 game plays”, “print a coupon for restaurant A”, or “print a coupon for hotel A.” Further high-level instructions might be sent to other types of peripheral devices including button panels, video display screens, card readers, motors, key pads, bill validators, coin acceptors, and information panels. In block 610, the peripheral controller receives a high-level instruction for a peripheral device and converts the high-level instruction into to one or more low-level instructions that are needed to perform the specific operation on the peripheral device. For example, a high-level instruction from the master gaming controller to “strobe lights” on a light panel with 3 lights connected to the gaming peripheral might be converted to a sequence low-level instructions including “turn on light 1”, “wait 100 milliseconds,” “turn off light 1”, “turn on light 2,” “wait 100 milliseconds”, “turn off light 2”, “turn on light 3.” In block 620, the peripheral controller sends the device specific low-level instructions through the peripheral interface to the peripheral device. The sequence of low-level instructions sent from the peripheral controller allow the peripheral device to perform the operation requested by the master gaming controller.

[0067]
FIG. 7 is a flow diagram depicting the details of the EVENT TRANSACTION step in block 510 in FIG. 5. While the gaming machine is operating and particularly when a player is playing a game, the peripheral controller and master gaming controller may attempt to store information on some events that occur on one or more of the peripheral devices. Typically, the critical events are stored in non-volatile memory on both the peripheral controller and the master gaming controller to ensure that in the event of a power failure or some other malfunction within the gaming machine during a game, critical event information is not lost. In the event of a power failure or some other malfunction within the gaming machine which interrupts a game, this critical event information can be used to determine the state of the gaming machine and game before the interruption.

[0068] In block 700, the first step in an event transaction between the peripheral controller and the master gaming controller is shown. In block 700, the peripheral device sends some information to the peripheral controller through the peripheral interface. The peripheral controller receives the data from the peripheral device and decides whether the information constitutes a critical event. A few possible examples of critical events might be the coin acceptor acknowledging a coin drop, the bill validator acknowledging receiving cash or the ticket reader receiving a ticket for game play. In block 710, when the peripheral controller decides the information from the peripheral device is a critical event, the peripheral controller may send all or portion of the data for storage in non-volatile memory on the peripheral controller. A potential hardware embodiment of this process is shown in FIG. 3. In block 720, after recording the critical event information in non-volatile memory, a copy of the critical event information, which may be encrypted, is sent to the master gaming controller using the standard communication protocol and standard communication connections. The critical event information may include a sequence number to avoid duplicate transactions. In block 730, the master gaming controller receives the critical event information. When the information is encrypted, the master gaming controller decrypts the information. All or a portion of the information received from the peripheral controller is stored in non-volatile memory on the master gaming controller. In block 740, the master gaming controller sends a notification back to the peripheral controller that the critical event sent from the peripheral controller was received. In block 750, after receiving this notification message from the master gaming controller, the peripheral controller may clear information from a previous critical event from its non-volatile memory.

[0069] In FIGS. 8-12 methods and apparatus are described that allow USB communications between a master gaming controller and peripheral devices on the gaming machine. In FIG. 8, a USB communication architecture is briefly described. In FIG. 9, the USB communication architecture is described in the context of a gaming environment involving communications between a master gaming controller and USB gaming peripherals. In FIG. 10, dataflow between a gaming host computer, such as a master gaming controller, and USB gaming peripheral using USB communications is presented. In FIG. 11, a gaming machine software architecture that allows USB communications is described. In FIG. 12, a method of initializing communications between the gaming host computer and the USB gaming peripheral are described.

[0070]
FIG. 8 is a block diagram of a USB communication architecture 800 that may be used to provide USB communications in the present invention. A USB device 803 may be subdivided into a number of components, such as: device, configuration, interface and endpoint. Class specifications define how a device uses these components to deliver the functionality provided to the host system. In some cases a host system uses device-specific information in a device or interface descriptor to associate a device with a driver, such as the device identification protocol described with respect to FIG. 5. The standard device and interface descriptors contain fields that are related to classification: class, subclass and protocol. These fields may be used by a host system to associate a device or interface to a driver, depending on how they are specified by the class specification.

[0071] The relationships between a USB device 803 and a host system 801 may be described according to a number levels. At the lowest level, the host controller 814 physically communicates with the device controller 816 on the USB device 803 through USB 818. Typically, the host 801 requires a host controller 814 and each USB device 800 requires a device controller 816.

[0072] At the middle layer, USB system software 810 may use the device abstraction defined in the Universal Serial Bus Specification to interact with the USB device interface 812 on the USB device. The USB device interface is the hardware (such as firmware) or software, which responds to standard requests and returns standard descriptors. The standard descriptors allow the host system 801 to learn about the capabilities of the USB device 803. The Universal Serial Bus Specification provides the device framework 808, such as the definitions of standard descriptors and standard requests.

[0073] At the highest layer the device driver 804 uses an interface abstraction to interact with the function provided by the physical device. The device driver 804 may control devices with certain functional characteristics in common. The functional characteristics may be a single interface of a USB device or it may be a group of interfaces. In the case of a group of interfaces, a class specification may be implemented by the USB device. If the interface belongs to a particular class, the class specification may define this abstraction. Class specifications add another layer of requirements directly related to how the software interacts with the capability performed by a device or interface which is a member of the class. In the present invention, characteristics of a gaming peripheral class specification that is compatible with USB are described that may be used to provide USB communications in a gaming machine.

[0074] A USB class describes a group of devices or interfaces with similar attributes or services. The actual definition of what constitutes a class may vary from one class to another. A class specification, such as gaming peripheral class specification, defines the requirements for such a related group. A complete class specification may allow manufacturers to create implementations, which may be managed by an adaptive device driver. A class driver is an adaptive driver based on a class definition. Adaptive drivers may be developed by operating system and third party software vendors as well as manufacturers supporting multiple products.

[0075] Typically, two devices (or interfaces) may be placed in the same class if they provide or consume data streams having similar data formats or if both devices use a similar means of communicating with a host system. USB classes may be used to describe the manner in which an interface communicates with the host, including both the data and control mechanisms. Also, USB classes may have the secondary purpose of identifying in whole or in part the capability provided by that interface. Thus the class information can be used to identify a driver responsible for managing the interface's connectivity and the capability provided by the interface.

[0076] Grouping devices or interfaces together in classes and then specifying the characteristics in a class specification may allow the development of host software which can manage multiple implementations based on that class. Such host software may adapt its operation to a specific device or interface using descriptive information presented by the device. The host software may learn of a device's capabilities during the enumeration process for that device (see descriptions of FIGS. 4, 5 and 12). A class specification may serve as a framework for defining the minimum operation of all devices or interfaces which identify themselves as members of the class.

[0077] Returning to FIG. 8, in the context of USB architecture 800, the term “device” may have different meaning depending on the context in which it is used. A device in the USB architecture may be a logical or physical entity that performs one or more functions. The actual entity described depends on the context of the reference. At the lowest level, a device may be a single hardware component, such as a memory device. At a higher level, a device may be a collection of hardware components that perform a particular function, such as a USB interface device. At an even higher level, the term “device” may refer to the function 806 performed by an entity attached to the USB, such as a display device. Devices may be physical, electrical, addressable, or logical. Typically, when used as a non-specific reference, a device is either a hub or a function 806. A hub is USB device that provides attachment points to the USB.

[0078] A typical USB communication path may start with a process executed on a host system, which may wish to operate a function of a physical device. The device driver 804 may send a message to the USB software 810. The USB software may operate on the message and send it to the host controller 814. The host controller 814 may pass the message through the serial bus 818 to the hardware 816. The USB device interface may operate on the message received from the hardware 812 and route it to a target interface which may route information to the physical device, which performs the desired operation.

[0079] USB changes the traditional relationship between driver and device. Instead of allowing a driver direct hardware access to a device, USB limits communications between a driver and a device to four basic data transfer types (i.e. bulk, control, interrupt and isochronous) implemented as a software interface provided by the host environment. Thus, a device must respond as expected by the system software layers or a driver will be unable to communicate with its device. For this reason USB compatible classes, such as a gaming peripheral of the present invention, are based at least on how the device or interface connects to USB rather than just the attributes or services provided by the device.

[0080] As an example, a gaming peripheral class may describe how a USB gaming peripheral is attached to a host system, either as a single unidirectional output pipe or as two unidirectional pipes, one out and one in for returning detailed gaming peripheral status. The gaming peripheral class may also focus on the format of the data moved between host and device. While raw (or undefined) data streams may be used, the class may also identify data formats more specifically. For instance, the output (and optional input) pipe may choose to encapsulate gaming peripheral data as defined in another industry standard, such as a SAS protocol used by IGT (Reno, Nev.). The gaming peripheral class may provide a mechanism to return this information using a class specific command. In the present invention, the appearance of the interfaces which are members of the gaming peripheral class are specified.

[0081]
FIG. 9 is a block diagram of master gaming controller 200 in communication with a USB gaming peripheral 830. The master gaming controller 200 may be considered a host 801 with hardware and software functionality as was described with respect to FIG. 8. The USB gaming peripheral 830 may be considered with USB device hardware and software functionality as was described with respect to FIG. 8.

[0082] The master gaming controller 200 may use USB communication 850 to communicate with a number of peripheral devices, such as, lights, printers, coin counters, bill validators, ticket readers, card readers, key pads, button panels, display screens, speakers, information panels, motors, mass storage devices and solenoids, described with respect to FIG. 3. The USB communication 850 may include the hardware and software, such as but not limited to, the USB software 816, the host controller 814, the serial bus 818, USB device interface 812, interfaces 815 and USB peripheral controller 832. The USB peripheral controller 832 may provide device controller 816 (see FIG. 8) functionality for the USB gaming peripheral 830. The USB peripheral controller 832 may be another embodiment of the peripheral controllers described with respect to FIGS. 1-6, such as peripheral control 234 described with respect to FIG. 3.

[0083] The USB communication 850 may allow a gaming drivers 824, such as gaming feature drives and gaming class drivers, to be utilized by the gaming software 820, such as the gaming machine operating system 822, to operate features, such as 833, 834 and 836 on peripheral devices 838 and 840. The logic for each USB gaming peripheral 830 may be divided into a collection of USB features, such as 833, 834 and 836. A USB feature may be independent code that controls a single I/O device or several essentially identical I/O devices, such as reels or bonus wheels. For instance, device 838 may be a bonus wheels for a gaming machine and device 840 may be one more or reels for a mechanical slot machine. Feature 834 may control the lights for the bonus wheel 840 and feature 836 may control the movement of the bonus wheel, such as start, spin-up, spin-down and stop. Feature 833 may control similar functions for one or more reels 840, such as start, spin-up, spin-down and stop for each reel.

[0084] Within the USB gaming peripheral 830, each device, such as 838 and 840, may have one or more features. The present invention is not limited to devices with two, such as 838, and a device may have a plurality of features. Each USB feature may typically have a unified purpose, which may be defined in the gaming peripheral class of the present invention. For example, a USB gaming peripheral 830 with two devices, such as buttons for input and lights for output may have two features buttons feature and lights feature. The buttons feature and the lights features may be controlled by corresponding gaming feature drivers in the gaming drivers 824. For instance, a gaming button feature driver may control the buttons feature and a gaming lights feature driver may control the lights feature via the USB communication 850.

[0085] The designation of the number of features in a gaming peripheral may be left to the manufacturer of the USB gaming peripheral. A manufacturer may divide a task that is performed by the peripheral into multiple features, as long as it makes sense for the peripheral to be viewed in software in that manner. The maximum number of features that are allowed on a single peripheral may be limited by the USB solution that is selected for the peripheral.

[0086]
FIG. 10 is an interaction diagram of communications between a host 860, such as a master gaming controller and a USB gaming peripheral 830 of the present invention via USB communications 850. A USB device, such as USB gaming peripheral 830, may have many configurations and interfaces. Detailed information on configurations and interfaces found in the USB standard specifications at www.usb.org. Basically, a configuration is a collection of interfaces (e.g., interfaces 815, in FIG. 9).

[0087] In the present invention, each feature has its own interface. For instance, Feature A is mapped to interface 1 and feature B is mapped to interface 2. The present invention is not limited to two interfaces and two features, e.g., features (1-N) may be mapped in a one to one relationship to interfaces (1-N). A feature, such as Feature A or Feature B may support commands that are particular to its function (feature-specific commands).

[0088] For example, a wheel feature may have a “spin” command and a “stop spin” command. These messages may not be found in other features such as lights feature. Therefore, feature-specific messages may be directed to the interface allocated for that feature. For instance, Feature A may receive feature A-specific commands via Feature A messages 880 sent to interface 1 and Feature B may receive feature B-specific commands via Feature B messages 864 sent to interface 2. The gaming peripheral device class may be designed such that it allows for any feature to add new feature specific commands without impacting the base class protocol. Therefore, a new peripheral sharing a common base class protocol may add functionality without requiring changes to older peripherals already using the common base class protocol.

[0089] In the gaming device class of the present invention, all features will normally use interface zero for asynchronous messages 872. Thus, interface zero may be normally used for asynchronous communication between the peripheral 830 and the host 860. Every gaming peripheral 830 may share common messages 872 that give it the identity of a gaming peripheral. Such messages include CRC calculation request, hardware reset request, enter tilt mode request, clear tilt mode request, enter self-test mode request, get configuration request, and get status request among others. Common messages may be directed to the peripheral as a whole, such as 876, or to a specific feature, such as Feature A or Feature B. When the message is directed to the peripheral as a whole, interface zero is used as the destination of the message. When the message is directed at a feature, the interface for that feature is used as the destination of the message.

[0090] The gaming peripheral class driver 870 that manages the physical device (e.g., the USB gaming peripheral 830) on the host machine may run the appropriate feature drivers to control each feature (see FIG. 11). For example, the gaming peripheral class driver 870 may load feature driver 878 and 862 to control features A and B on the USB gaming peripheral 830. The gaming peripheral class driver 870 may be able to determine which features a USB gaming peripheral 830 supports and corresponding feature drivers to load by interrogating the USB gaming peripheral when communications are initiated. For example, when a printer feature is detected by the gaming peripheral class driver on the USB gaming peripheral, the printer feature driver may be loaded and run on the host machine. The gaming software on the machine will then have access to the printer and will be able to print tickets. Details of the interface between the gaming software and the gaming feature drivers are described with respect to FIG. 11. Details of methods used to determine the features of a gaming peripheral and corresponding drivers to load are described with respect to FIGS. 5 and 12.

[0091] As described above, in the present invention, each feature has its own interface. The advantage for having its own interface is that the USB host on the gaming machine may view a physical device (i.e., the gaming peripheral) as a collection of features. This may simplify the driver architecture on the host. Further, the use of a one to one mapping of features to interfaces may allow coding for interfaces and features to be re-used for different USB gaming peripherals sharing common features.

[0092]
FIG. 11 is a block diagram of a gaming software architecture 851 in a gaming machine for communicating with USB gaming peripheral of the present invention. Details of a gaming software architecture which may be used with the present invention are described in co-pending U.S. application Ser. No. 10/040,329, filed on Jan. 3, 2002 and titled “Game Development Architecture that Decouples the Game Logic from the Graphics Logic,” which is incorporated herein in its entirety and for all purposes.

[0093] The gaming operating system on the gaming machine may run feature client processes that use capabilities of peripheral devices connected to the gaming machines, such as peripheral devices located on USB gaming peripherals as described with respect to FIGS. 8-10. To utilize the functions of a peripheral device on the USB gaming peripheral, a feature client process, such as 852 or 854, may send feature-specific commands to a feature driver. The feature clients may send commands and queries to the feature drivers via an inter process communication (IPC) which is supported by the gaming operating system. The gaming drivers 824, the feature driver 862 and 878 and gaming peripheral class driver 870 are described with respect to FIGS. 9 and 10.

[0094] As an example, feature client process 852 may wish to operate lights on USB gaming peripheral 830 as part of a game outcome presentation on a gaming machine. The lights on the USB gaming peripheral may be controlled by feature driver 862. Therefore, the feature client process may send a command, such as “flash lights,” to feature driver 862. Then the driver 862 may use USB communication 850 as was described with respect to FIG. 10, to send the “flash light” command to the USB gaming peripheral 830 so that the lights may be flashed.

[0095] The feature client processes, 852 and 854, may send common commands to the gaming peripheral class driver 870. Examples of common commands include but are not limited to CRC calculation request, hardware reset request, enter tilt mode request, clear tilt mode request, enter self-test mode request, get configuration request, and get status request. These commands may be directed to the USB gaming peripheral as whole or to a specific feature on the USB gaming peripheral.

[0096] A feature client process may send commands to different feature drivers at different times. For instance, feature client processes 852 and 854 may be the same process. At a first time, feature client process 852 may send a feature-specific command to control a first feature on the USB gaming peripheral 830 via feature driver 862. At a second time, the same process, the feature client process 854, may send a feature-specific command to control a second feature on the USB gaming peripheral 830 via feature driver 878. In general, different process may attempt to operate the same feature driver at the same time or different times or the same process may attempt to operate different feature drivers while it is running.

[0097] The USB gaming peripheral 830 may make use of interrupt transfers (see USB specifications) to report changes in statuses, asynchronous events, and rejection of messages. Whenever the peripheral or feature has a message to for the host, the host will receive it within the polling interval set for the interrupt pipe. The use of interrupt transfers is beneficial because the software using the peripheral on the host machine will not be interrupted if the peripheral has nothing to report. A good use of this is in the retrieval of the result of a CRC calculation. Once the host machine has requested a CRC calculation on the peripheral, it does not need to check with the peripheral every so often to find out whether or not the CRC calculation is done. When the USB gaming peripheral is done with the operation, it will report the CRC back to the host. Other messages that make use of interrupt transfers include status updates from a feature and rejection reasons for any command.

[0098] In FIG. 11, interrupt transfers, using USB communication 850, to the drivers 862, 870 and 878 are indicated by the three arrows from the USB gaming peripheral 830 to each driver, respectively. After the information is received at the drivers via the interrupt transfers, the feature client processes 852 or feature client process 854 may receive information from one of the drivers. The manner in which the information is sent from the driver to the feature client process may vary depending on the operating system and software architecture that is used.

[0099]
FIG. 12 is a method 900 in a gaming machine of initializing communications between a host, such as master gaming controller on a gaming machine, and a USB gaming peripheral. After the device is connected to a USB port, in 905, the USB host may detect the USB gaming peripheral and begin communications. In 910, the USB host may enumerate the device as was described with respect to FIG. 5. In the enumeration sequence, in 915, the host may determine a number of interfaces defined for the device. Next, in 920, the USB host may notify the gaming peripheral class driver of the presence of a new gaming peripheral. In 925, the gaming peripheral class driver on the host may interrogate each interface to find out what feature is present. In 930, the class driver may load and run feature drivers to communicate with the features on the gaming peripheral. In one embodiment, the loading of feature drivers may be initiated by feature client processes (see FIG. 9). Then, clients on the host may operate the features on the USB gaming peripheral and its corresponding physical device via the feature driver. In 935, the host may begin communications with the USB gaming peripherals, such as sending feature-specific commands to feature drivers or common commands to the gaming peripheral class driver using USB communication. The feature-specific commands or the common commands may be used by the host to operate the USB gaming peripheral.

[0100] Although the foregoing invention has been described in some detail for purposes of clarity of understanding, it will be apparent that certain changes and modifications may be practiced within the scope of the appended claims. For instance, while the gaming machines of this invention have been depicted as having gaming peripherals physically attached to a main gaming machine cabinet, the use of gaming peripherals in accordance with this invention is not so limited. For example, the peripheral features commonly provided on a top box may be included in a stand along cabinet proximate to, but unconnected to, the main gaming machine chassis.

	Number	Date	Country
Parent	09414659	Oct 1999	US
Child	09635987	Aug 2000	US

	Number	Date	Country
Parent	09635987	Aug 2000	US
Child	10214255	Aug 2002	US

	Number	Date	Country
Parent	10214255	Aug 2002	US
Child	10246367	Sep 2002	US

USB device protocol for a gaming machine

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

US Classifications

International Classifications

Abstract

Description

Claims

RELATED APPLICATION DATA

Divisions (1)

Continuations (1)

Continuation in Parts (1)