The present invention relates generally to methods and devices for providing games, such as wagering games.
Many casino patrons enjoy simultaneously playing more than one wager gaming machine. Typically, such patrons will need to move from one wager gaming machine to another, inserting credit, making wagers, hitting the “Play” button of each machine, etc. Each wager gaming machine is typically in a different phase of play at any particular time. In some cases, if one wager gaming machine requires a player's attention for more than a few seconds, another wager gaming machine may be idle. Another patron may believe that the idle machine is available. It would be desirable to provide more versatile methods and devices for simultaneously playing more than one wager gaming machine.
Methods and devices are provided for simultaneously playing more than one gaming machine, including but not limited to simultaneously playing more than one wager gaming machine. Some implementations coordinate the responses of multiple gaming machines that are involved in a concurrent gaming session. As used herein, the terms “concurrent gaming session,” “concurrent play” and the like mean a gaming session involving multiple gaming machines. The terms may refer to, but are not limited to, a single-player gaming session involving multiple gaming machines. For example, a patron may be able to provide credit and/or user input for all gaming machines that are involved in a concurrent gaming session by interacting with only one gaming machine. Similarly, a patron may be able to present a player loyalty device (e.g., a player tracking card) to only one gaming machine, but still may be able to obtain player loyalty points corresponding to gaming on all gaming machines that are involved in a concurrent gaming session. The terms “player tracking” and “player loyalty” may be used synonymously herein.
Some implementations provide a coordinated game presentation involving all gaming machines that are involved in a concurrent gaming session. For example, the game outcomes on all participating gaming machines may be presented in a sequential fashion, e.g., from left to right, right to left, etc. In some implementations, coordinating the wager gaming sessions of multiple wager gaming machines involves combining a game outcome of two or more gaming machines to produce a combined wager gaming outcome that could not be produced in its entirety by an individual gaming machine.
Some embodiments described herein provide a wager gaming machine that includes the following elements: apparatus for presenting wagering games; an interface system configured for communicating with at least one other device; a user input system configured for receiving a selection from a player to use multiple wager gaming machines during a wager gaming session; and a logic system comprising at least one logic device (such as a processor, a programmable logic device, etc.).
The logic system may be configured to control the apparatus for presenting wagering games and to send an indication responsive to the received selection, via the interface system, for functionality of a second wager gaming machine to be disabled, at least in part. It should be appreciated that what is described herein with reference to a “second wager gaming machine” or the like will be generally applicable to other wager gaming machines. Accordingly, even though such functionality may not be explicitly described with regard to a third wager gaming machine, a fourth wager gaming machine, etc., it should be understood that such remarks could apply to more than one additional wager gaming machine.
For example, the responsive indication may comprise an indication to disable at least a portion of a user input system, a player tracking system, a device for receiving indicia of credit and/or a device for dispensing indicia of credit on the second wager gaming machine. The indication may comprise an indication to disable at least a portion of gaming controller functionality of the second wager gaming machine.
The selection received from the player may include at least one identified wager gaming machine. The responsive indication may be for functionality of the identified wager gaming machine to be disabled, at least in part. The logic system may be further configured to evaluate a combined wager gaming outcome by reference to a combined wager gaming outcome paytable. The combined wager gaming outcome paytable may comprise at least one combined wager gaming outcome that could not be produced in its entirety by either the identified wager gaming machine or the other wager gaming machine.
The logic system may be further configured to provide the wager gaming session by coordinating responses of the wager gaming machine and the second wager gaming machine. For example, the coordinating process may involve enabling at least one component associated with the wager gaming machine to provide functionality relating to the second wager gaming machine. The component may be, for example, a component of a value input system that is configured for receiving indicia of credit. The value input system component may be a bill acceptor, a ticket or voucher reader, etc. In some such embodiments, indicia of credit received by a value input device of the wager gaming machine may be applied to game play on the second wager gaming machine.
In some embodiments, a payout system of the wager gaming machine may be configured for dispensing indicia of credit relating to wager gaming on the wager gaming machine and/or the second wager gaming machine. The coordinating process may involve enabling a ticket printer of the wager gaming machine to print a ticket corresponding to credits associated, at least in part, with the second wager gaming machine. The coordinating process may involve controlling a device of the wager gaming machine for dispensing indicia of credit to dispense currency, coins or tokens corresponding to credits associated, at least in part, with the second wager gaming machine.
The coordinating process may involve enabling at least a portion of a user input system of the wager gaming machine to receive input relating to functionality of the second wager gaming machine. For example, the coordinating process may involve enabling a touch screen, buttons, a joystick and/or an optical imaging device of the wager gaming machine to receive input relating to functionality of the second wager gaming machine.
The coordinating process may involve enabling a reader of the wager gaming machine to provide functionality relating to the second wager gaming machine. The reader may be a magnetic card reader, a radio frequency identification tag reader, etc. For example, player loyalty data obtained via a player loyalty card reader may be associated with wager gaming on the wager gaming machine or the second wager gaming machine. A player may provide a single player loyalty card to the wager gaming machine, but may be able to receive player loyalty points relating to wagering games played on the second wager gaming machine. Accordingly, some implementations involve enabling predetermined devices of the wager gaming machine to operate as a centralized device set for a plurality of wager gaming machines.
The coordinating process may involve controlling a time interval between first images of a first game outcome displayed on the wager gaming machine and second images of a second game outcome displayed on the second wager gaming machine. The coordinating process may involve combining a first wager gaming outcome on the wager gaming machine with a second wager gaming outcome on the second wager gaming machine to produce a combined wager gaming outcome. In some such embodiments, the combined wager gaming outcome could not be produced in its entirety by either the wager gaming machine or the second wager gaming machine.
The logic system may be configured to send an indication, via the interface system, for functionality of a third wager gaming machine to be disabled, at least in part. The logic system may be further configured to provide the wager gaming session by coordinating responses of the wager gaming machine and the third wager gaming machine.
The logic system may be configured to control, at least in part, the operations of the second wager gaming machine. For example, the user input system may be configured (at least temporarily) for receiving instructions relating to the second wager gaming machine. According to some such embodiments, the user input system may comprise a display configured to present, under the control of the logic system, a graphical user interface for receiving instructions regarding the second wager gaming machine.
The interface system may comprise a network interface. The interface system may be configured for communication with the second wager gaming machine via free space optical communication. The interface system may be configured for communication with the second wager gaming machine via an industrial automation protocol. The interface system may include at least one network interface that is configured for communication with other devices, either directly or indirectly. For example, the network interface may be configured for communication with other devices via an Ethernet standard, via Transmission Control Protocol (“TCP”) and/or Internet Protocol (“IP”), etc. Other examples of protocols are described herein with reference to specific embodiments.
Alternative implementations described herein involve a method that includes the following steps: receiving an indication that a player desires to use multiple wager gaming machines during a gaming session, the indication including an identified wager gaming machine; sending a command to disable at least a portion of the functionality of the identified wager gaming machine; and providing the gaming session by coordinating responses of the identified wager gaming machine and at least one other wager gaming machine.
For example, the command may comprise a command to disable at least a portion of a user input system and/or at least a portion of a player tracking system of the identified wager gaming machine. The command may comprise a command to disable a device for receiving indicia of credit for the identified wager gaming machine. The command may comprise a command to disable at least a portion of gaming controller functionality of the identified wager gaming machine.
The providing process may involve making the identified wager gaming machine operate, at least in part, under the control of another device. For example, the providing process may involve making the identified wager gaming machine operate, at least in part, under the control of a server and/or making the identified wager gaming machine operate, at least in part, under the control of a wager gaming machine.
The coordinating process may involve coordinating a display of images or sounds on the identified wager gaming machine and at least one other wager gaming machine. The coordinating process may involve controlling a time interval between first images displayed on the identified wager gaming machine and second images displayed on a second wager gaming machine. The coordinating process may involve combining player loyalty points for wager gaming on the identified wager gaming machine and player loyalty points for wager gaming on at least one other wager gaming machine.
Alternatively, or additionally, the coordinating process may involve combining a first wager gaming outcome on the identified wager gaming machine with a second wager gaming outcome on at least one other wager gaming machine to produce a combined wager gaming outcome. In some instances, the combined wager gaming outcome could not be produced in its entirety either by the identified wager gaming machine or the other wager gaming machine. The method may further involve evaluating the combined wager gaming outcome by reference to a combined wager gaming outcome paytable. The combined wager gaming outcome paytable may comprise at least one combined wager gaming outcome that could not be produced in its entirety by either the identified wager gaming machine or the other wager gaming machine.
Alternative embodiments described herein involve an apparatus that includes an interface system and a logic system. The interface system may include at least one interface (e.g., a network interface or a user interface) configured for receiving an indication that a player desires to use multiple wager gaming machines during a gaming session. In some embodiments, the interface system may be configured for communication via an industrial automation protocol.
The received indication may include an identified wager gaming machine. The logic system may be configured to provide the gaming session by coordinating responses of the identified wager gaming machine and at least one other wager gaming machine.
The logic system may be configured to send a command, via the interface system, to disable at least a portion of the functionality of the identified wager gaming machine. For example, the command may comprise an instruction to disable at least a portion of a user input system or a player tracking system of the identified wager gaming machine. The command may comprise an instruction to disable a device for receiving indicia of credit for the identified wager gaming machine. The command may comprise an instruction to disable at least a portion of gaming controller functionality of the identified wager gaming machine.
The providing process may involve controlling the identified wager gaming machine, at least in part. For example, the providing process may involve providing game outcome data to the identified wager gaming machine.
The coordinating process may involve coordinating a display of wager game outcome images on the identified wager gaming machine and at least one other wager gaming machine. The coordinating process may involve controlling a time interval between first images displayed on the identified wager gaming machine and second images displayed on a second wager gaming machine. The coordinating process may involve combining player loyalty points for wager gaming on the identified wager gaming machine and player loyalty points for wager gaming on at least one other wager gaming machine.
Alternatively, or additionally, the coordinating process may involve combining a first wager gaming outcome on the identified wager gaming machine with a second wager gaming outcome on at least one other wager gaming machine to produce a combined wager gaming outcome. In some such embodiments, the combined wager gaming outcome could not be produced in its entirety either by the identified wager gaming machine or the other wager gaming machine. The logic system may be further configured to evaluate the combined wager gaming outcome by reference to a combined wager gaming outcome paytable. The combined wager gaming outcome paytable may include at least one combined wager gaming outcome that could not be produced in its entirety either by the identified wager gaming machine or the other wager gaming machine.
In some embodiments, a server may comprise at least some elements of the apparatus. In some embodiments, a wager gaming machine may comprise at least some elements of the apparatus.
These and other methods of the invention may be implemented by various types of hardware, software, firmware, etc. For example, some features of the invention may be implemented, at least in part, by one or more stationary gaming machines, by one or more portable gaming devices and/or other type of mobile devices, by one or more host devices, servers, etc. Some embodiments of the invention are provided as computer programs embodied in machine-readable media. The computer programs may include instructions for controlling one or more devices to perform the methods described herein.
While the present invention will be described with reference to a few specific embodiments, the description is illustrative of the invention and is not to be construed as limiting the invention. Various modifications to the present invention can be made to the preferred embodiments by those skilled in the art without departing from the true spirit and scope of the invention as defined by the appended claims. For example, the steps of methods shown and described herein are not necessarily performed in the order indicated. It should also be understood that the methods of the invention may include more or fewer steps than are indicated.
Device functionality may be apportioned by grouping or dividing tasks in any convenient fashion. Therefore, when steps are described herein as being performed by a single device (e.g., a single server), the steps may alternatively be performed by multiple devices and vice versa.
Referring now to
In some such alternative implementations, wagering games may be presented on “thin” terminals. As used herein, the terms “thin terminal,” “thin client” or the like may refer broadly to client computers and/or client software that depend, at least to some extent, on one or more central devices for processing activities but which may potentially have a range of processing capabilities. As such, the term “thin client” may sometimes be used as the term is generally known in the art, but may also be used to refer to a more versatile device and/or related software, such as a diskless node or a hybrid client. In some implementations, a portion of a device (such as a line card of a network device, a blade of a blade server, etc.) may be configured to perform at least some of these steps, or other steps described herein. Examples of some such devices will be provided below.
In step 101, a player is prompted to indicate whether to have a wager gaming session on a single machine or on multiple machines. Step 101 may involve indicating that a particular wager gaming machine can be configured for simultaneous play involving other wager gaming machines. Step 101 may be performed actively (e.g., via an audio, video and/or other visual prompt) or passively (e.g., via a sign, a label, a static display, etc.). Step 101 may be omitted in some implementations.
In this example, step 101 involves presenting a visual prompt to a player on a display device of a wager gaming machine. One such visual prompt is shown in
Here, the patron is advised by area 201 of GUI 200a that this wager gaming machine can operate either in “single-machine” mode or can be used to control simultaneous play on multiple wager gaming machines. Area 201 also invites the player to select one of the two options. If the player wants to play in “single-machine” mode, the player can select the option indicated by area 203, e.g., by touching that portion of the display or by using another user interface device, such as a button of a button panel. If the player chooses the single-machine option, it will be determined in step 105 (see
However, if the player selects the option indicated by area 205 of
In this example, nearby wager gaming machines are polled to determine their availability for use in a concurrent gaming session (step 108) and then a player will be provided a user interface that allows the player to select one or more additional wager gaming machines, if any are available. (Step 110.) For example, in step 108 a logic device (e.g., of wager gaming machine 209a, of a server, of a bank switch, etc.) may query another logic device (e.g., of the selected wager gaming machine, of a bank switch, of a server or of another device of the casino's system) to determine the availability of nearby wager gaming machines for use in a concurrent gaming session. The player may, e.g., be presented with a GUI such as that depicted in
Whether or not the depicted wager gaming machines are in the same row, the depicted wager gaming machines are preferably close enough to the player that wagering games presented on them are potentially viewable by the player. For example, alternative implementations may depict wager gaming machines within a predetermined radius of the player, those within the predetermined radius that have a predetermined orientation relative to the player, etc. Whether the wagering games presented on the depicted wager gaming machines are actually viewable by the player may depend on various factors, such as the number of nearby players, the arrangement of the wager gaming machines, the height of the player, etc.
In some implementations, only wager gaming machines that are currently available are indicated in area 207. In other implementations, nearby wager gaming machines may be indicated in area 207 even if they are not available. If so, unavailable wager gaming machines may be depicted in a manner that indicates that they are unavailable. For example, wager gaming machines that are available may be portrayed using bright colors whereas those which are unavailable may be shown using faded colors. Alternatively, unavailable wager gaming machines may be crossed out, may be labeled “IN USE,” etc. Furthermore, the GUI may preclude wager gaming machines that are unavailable from being selectable by the player.
The message in area 213a also prompts the patron to select another wager gaming machine for concurrent play. (Step 115.) In this example, when a player's selection of another wager gaming machine is received (step 120), it will be determined whether the selected wager gaming machine is still available. (Step 125.) In alternative embodiments, step 125 may not be necessary. For example, after initially determining that an identified wager gaming machine is available for concurrent play, that wager gaming machine may remain available for a predetermined time to allow the player time to select one or more machines for concurrent play. For example, a credit input device and/or other features of the identified wager gaming machine may be temporarily disabled even before any selection is made by the player. If the identified wager gaming machine is not available, the patron will be so advised and will be prompted to select another wager gaming machine. (Step 115.)
In this example, the patron selects wager gaming machine 209b, which is adjacent to, and on the left side of, wager gaming machine 209a. Here, the patron selects wager gaming machine 209b by selecting the corresponding wager gaming machine icon in area 207, e.g., by touching that portion of area 207 or by using another user interface device to select that icon. Wager gaming machine 209a makes a query and receives a response indicating that wager gaming machine 209b is still available. In some implementations, there may be an authentication process to ensure that, e.g., an unauthorized device does not establish control over wager gaming machine 209b.
In some implementations, as here, after determining that a selected wager gaming machine is still available, at least part of the functionality of the selected wager gaming machine will be disabled. (Step 130.) In this example, wager gaming machine 209a has sent an indication to disable at least part of the functionality of wager gaming machine 209b. For example, wager gaming machine 209a may send a request to a device (e.g., a server, a bank switch, etc.) of a casino's computer system. If the request is approved, the device will send a command to disable at least part of the functionality of wager gaming machine 209b. Alternatively, wager gaming machine 209a may send a request, a command, etc., directly to wager gaming machine 209b. In other implementations, if it is determined that a selected wager gaming machine is available, that wager gaming machine will be instructed to partially disable itself without the need for a further request, command, etc., from wager gaming machine 209a.
Although not all implementations of the invention involve disabling the functionality of other wager gaming machines, it can be advantageous to disable at least some of such functionality. For example, disabling the functionality of other wager gaming machines involved in simultaneous multi-machine play can reduce the potential for contention with other players who may wish to play one of the machines selected for concurrent play. If, for example, user input devices (such as buttons on a button panel, GUIs on a display screen, etc.) and/or the device(s) for receiving indicia of credit (such as currency, tickets, etc.) on wager gaming machine 209b were disabled, it would be more obvious to another player that this machine is currently in use and is not available.
Similarly, if a player tracking card reader (or other mechanism for interacting with a player loyalty device, such as a radio frequency identification (“RFID”) reader) of wager gaming machine 209b were disabled, it should be evident to another player that wager gaming machine 209b is not available. For example, a bezel may normally light up after a player inserts a player loyalty card. If the bezel does not light up after the player inserts the player loyalty card, the player receives an indication that this feature has been temporarily disabled. In some implementations, at least some of the other functionality of a wager gaming machine's logic system, input/output system, peripheral devices, etc., may be disabled. For example, some of the functionality of a credit input device, a player tracking (or other) card reader, etc., may be disabled. A master gaming controller of wager gaming machine 209b may be configured to receive user input, credit data, etc. from wager gaming machine 209a, e.g., via a network interface, an infrared, radio frequency or other interface, etc.
In this example, the player decides to select another wager gaming machine. Here, the patron selects wager gaming machine 209c by selecting the corresponding wager gaming machine icon in area 207, e.g., by touching that portion of area 207 or by using another user interface device to select that icon. After receiving the player's indication identifying another wager gaming machine (step 120), wager gaming machine 209a makes a query and receives a response indicating that wager gaming machine 209c is available. (Step 125.) Accordingly, part of the functionality of wager gaming machine 209c is disabled. (Step 130.)
However, the player decides not to select any additional wager gaming machines at this time. Accordingly, the player interacts with area 215, e.g., by pressing the corresponding part of a touch screen. Therefore, it is determined in step 135 that the player is finished identifying wager gaming machines for the present time.
Although
After the player is finished identifying wager gaming machines (at least for the moment), the player will be preferably be provided with some type of user interface for controlling game play on more than one wager gaming machine. This feature is not necessary for implementing all aspects of the invention, but can significantly increase player convenience and satisfaction when implemented. In some implementations, as here, the player will be able to provide credit, initiate play and/or make game-related responses for all associated wager gaming machines from a single one of the wager gaming machines. The single wager gaming machine may sometimes be referred to herein as a “master” wager gaming machine or the like. In some such implementations, one or more user input devices (such as buttons, switches, etc. on a “master” wager gaming machine may be used to provide user input regarding play on all associated machines. In this example, a GUI is provided for controlling multiple wager gaming machines from a master wager gaming machine. (Step 140).
Examples of GUIs that may be used for controlling multiple wager gaming machines from a master wager gaming machine are provided in
Credit meters 320a, 320b and 320c indicate how much credit is available for wager gaming on wager gaming machines A, B and C, accordingly. In this example, the player has not yet provided credit for game play: credit meters 320a, 320b and 320c all indicate zero credits. Accordingly, area 325 prompts the player to provide one or more indicia of credit (such as currency, a ticket, a voucher, etc.) to wager gaming machine 209a. Wager gaming machine 209a may provide other prompts, e.g., an audio prompt, a light associated with a bill and/or ticket validator may flash, etc.
At the time that GUI 300b of
Accordingly, area 330 informs the player of the total credits accepted by wager gaming machine 209a and prompts the player to indicate how much of that total will be apportioned to wagering on machine A, the master wager gaming machine. A player may indicate how many credits to apportion by interacting with GUI 300b, e.g., by touching or otherwise selecting the corresponding portion of area 330.
As indicated in GUI 300c of
As shown in GUI 300d of
The present invention provides various embodiments by which a selected wager gaming machine may be configured, at least temporarily, as a master by providing user input regarding all wager gaming machines that will be involved in this wager gaming session. In some such embodiments, one or more GUIs on the master wager gaming machine will allow a player to provide input corresponding to each machine. For example, in a layout generally like that of GUI 300d, areas 305, 310 and 315 may each provide separate areas for providing user input for wager gaming machines A, B and C, respectively.
In other embodiments, dedicated and/or configurable buttons or other user input devices on the master wager gaming machine may be used to provide user input for each machine. For example, wager gaming machine 209a may have one or more configurable buttons for which a different appearance and/or functionality may be provided, e.g., according to data downloaded from a central system. The buttons may be configured, for example, according to the number of wager gaming machines involved, the type of wagering game presented and/or other factors. In other embodiments, a button panel and/or other user input devices may be pre-configured to support play on multiple wager gaming machines. A portion of the input devices may indicate “machine 1” (or the like), another may indicate “machine 2” (or the like) and so on.
In the example depicted in
During game play, money will typically be won and/or lost at different rates by the wager gaming activities on machines A, B and C. At the time that GUI 300e of
However, in this example, the player decides to provide more credit for machine C. As shown in area 330 of GUI 300f (see
It will be appreciated from the foregoing discussion that some implementations of the invention provide at least some level of coordination between participating wager gaming machines. Accordingly, in step 145 of
Some implementations may, for example, allow a player to send a “play” command (or the like) to all participating wager gaming machines at approximately the same time. One such implementation is depicted in
In some implementations, data regarding the wager gaming on all participating wager gaming machines will be reflected in the player's player loyalty account. Referring now to
In some such implementations, the card readers (or the like) of player tracking systems 401a and 401b of wager gaming machines 209b and 209c may have been temporarily disabled according to the indication sent in step 130 of
Credit input data, user input data and/or other such data may, for example, be sent from logic system 415a via network interface system 413a and received via network interface systems 413b and 413c. In some such implementations, one or more logic devices of a network device may provide related functionality. For example, processor 427a of line card 425a may be configured to forward credit input data and/or user input data from wager gaming machine 209a to logic system 415b, via line card 425b or to logic system 415c, via line card 425c. Forwarding data may be established after wager gaming machines are selected by a patron (e.g., during a process such as that described above) and stored in a memory of bank switch 420, e.g., memory 429a of line card 425a.
As mentioned elsewhere herein, in some implementations game services, including but not limited to the determination of game outcomes, the aggregation of wager gaming machines for a concurrent gaming session, the provision of player loyalty services, accounting services, etc., may be provided by one or more devices of a central system, such as host devices 441 and/or servers 443. Relevant data may be stored in one of storage devices 445, and/or in a network storage system. For the sake of simplicity, intermediate network devices (such as switches, routers, etc.) of a casino network are depicted as a cloud in
Alternatively, or additionally, data may be sent from logic system 415a via free space optical communication links 407a and received via free space optical communication links 407b and 407c. The free space optical communication links may, for example, comprise transmitters and receivers for infrared light according to an Infrared Data Association (“IrDA”) standard, radio frequency transceivers, or any other convenient devices suitable for short-range wireless communication.
Some implementations of the invention provide at least some level of coordination of the presentations of wagering games, including but not limited to coordinating the presentations of game outcomes, between participating wager gaming machines. For example, some implementations involve a degree of coordination between sounds provided by audio systems 405a, 405b and 405c and/or images presented by display systems 403a, 403b and 403c. In some such implementations, game outcomes may be displayed in a sequential fashion, e.g., from right to left, left to right, etc., in a sequential fashion. In some implementations, game outcomes may be displayed in a substantially simultaneous fashion. Different implementations may provide varying levels of coordination between the displays.
Some gaming machines may include an interface system having at least one network interface that is configured for communication with other devices via an Ethernet standard, via Transmission Control Protocol (“TCP”) and/or Internet Protocol (“IP”), etc. In some embodiments, the communication protocol used between participating wager gaming machines may be supplemented or replaced by protocols which ensure that communications are transmitted and received within a specified period of time. For example, an automotive control protocol such as CANbus™ (ISO 11898) or FlexRay™, or an industrial automation protocol such as Profibus™ (IEC 61158/IEC61784) may ensure messages are conveyed with minimal latency. In some embodiments, synchronization of networked devices may be improved by employing utilities such as the Network Time Protocol or Precision Time Protocol (IEEE 1588). Such implementations may allow game outcomes, etc., to be presented in a highly controlled manner. For example, if game outcomes are presented in a sequential fashion, e.g., from right to left, left to right, etc., the time interval between an event presented on a first wager gaming machine and a corresponding event presented on a second wager gaming machine (e.g., on an adjacent wager gaming machine) can be closely controlled.
In some implementations, coordinating the wager gaming sessions of multiple wager gaming machines will involve combining a game outcome of two or more gaming machines to produce a combined wager gaming outcome. In some such embodiments, at least one of the combined wager gaming outcomes could not be produced in its entirety by an individual gaming machine. Some examples are provided in
Referring first to
Because the probability of obtaining 9 of the same symbols along payline 505 is so small, the corresponding win amount may be larger than any win amount available when playing only one machine at a time. Even if a player obtained, e.g., 7 or 8 of the same symbols along payline 505, the corresponding win amount may still be larger than any win amount available when playing only one machine at a time. Because some symbols are generally more common than others, the probability of obtaining any particular symbol combination will depend on how the reels (or their representations) are formed.
The evaluation of game outcomes involving multi-machine paylines and the like may be made by reference to corresponding multi-machine paytables. Depending on the implementation, such paytables may be stored in a particular wager gaming machine (e.g., in a memory of master wager gaming machine 209a of
The multi-machine paylines provided herein are not limited to horizontal paylines, however. Other possible multi-machine paylines are depicted in
In some embodiments, casinos may establish criteria that players must meet in order to establish and/or maintain concurrent play on multiple wager gaming machines. For example, a concurrent play option may be offered only to preferred players. Such preferred players may be, for example, players of at least a predetermined level in a player loyalty program.
In some such embodiments, the criteria for maintaining concurrent play on multiple wager gaming machines may include wager information. For example, if the time interval between a player's wagers and/or other wagering criteria (e.g., a wager amount per unit of time) drops below a predetermined level, concurrent play may be disabled, at least in part. The wagering criteria may take into account how many wager gaming machines are involved in concurrent play. For example, a wagering criterion may comprise a wagering rate (wager amount per unit time) divided by the number of wager gaming machines are involved in concurrent play.
In some such embodiments, if the criterion or criteria for concurrent play are not met, concurrent play may be partially disabled by disabling control by the wager gaming machine assigned as the master gaming controller and the wager gaming machine associated with a low wagering play may be disconnected. Alternatively, or additionally, concurrent play may be completely disabled if predetermined criteria, including but not limited to wagering criteria, are not met. Preferably, the player receives a prompt indicating that such an action will take place unless the player takes remedial action, e.g., by placing a wager of a certain amount. Such embodiments are designed to prevent players from reserving wager gaming machines only to let them stand at idle or allow them to be under-utilized.
Limits may also be placed on the number of wager gaming machines that can be involved in concurrent play. For example, a casino may determine that no more than 3 wager gaming machines can be involved in concurrent play. In some implementations, the number of wager gaming machines that can be involved in concurrent play may depend on whether a player is a preferred player. For example, the number of wager gaming machines that can be involved in concurrent play may depend on a player's level in a player loyalty program. In some such embodiments, a player may be allowed to include 2, 3 or 4 wager gaming machines for concurrent play, depending on the player's level in the player loyalty program.
Some networks described herein provide methods and devices for managing one or more networked gaming establishments. Such networks may sometimes be referred to herein as server-based gaming networks, Sb™ networks, or the like. Some such gaming networks described herein allow for the convenient provisioning of networked gaming machines and other devices relevant to casino operations. Game themes may be easily and conveniently added or changed, if desired. Related software, including but not limited to player tracking software, peripheral software, etc., may be downloaded to networked gaming machines, mobile gaming devices, thin clients and/or other devices, such as kiosks, networked gaming tables, player stations, etc.
In some implementations, servers or other devices of a central system will determine game outcomes and/or provide other wager gaming functionality. In some such implementations, wagering games may be executed primarily on one or more devices of a central system, such as a server, a host computer, etc. For example, wager gaming determinations (such as interim and final game outcomes, bonuses, etc.) may be made by one or more servers or other networked devices. Player tracking functions, accounting functions and even some display-related functions associated with wagering games may be performed, at least in part, by one or more devices of casino network and/or of a central system.
One example of an Sb™ network is depicted in
Here, casino computer room 820 and networked devices of a gaming establishment 805 are illustrated. Gaming establishment 805 is configured for communication with central system 863 via gateway 850. Gaming establishments 893 and 895 are also configured for communication with central system 863.
In some implementations, gaming establishments may be configured for communication with one another. In this example, gaming establishments 893 and 895 are configured for communication with casino computer room 820. Such a configuration may allow devices and/or operators in casino 805 to communicate with and/or control devices in other casinos. In some such implementations, a server in computer room 820 may control devices in casino 805 and devices in other gaming establishments. Conversely, devices and/or operators in another gaming establishment may communicate with and/or control devices in casino 805.
For example, a server of casino 805 or central system 863 may be provisioned with relatively more advanced software (e.g., 3-D facial recognition software) for patron identification than servers of other networked locations. Such a server may process patron identification requests from devices in casino 805 as well as patron identification requests from devices in gaming establishments 893 and 895.
Here, gaming establishment 897 is configured for communication with central system 863, but is not configured for communication with other gaming establishments. Some gaming establishments (not shown) may not be in communication with other gaming establishments or with a central system. Gaming establishment 805 includes multiple gaming machines 821, each of which is part of a bank 810 of gaming machines 821. In this example, gaming establishment 805 also includes a bank of networked gaming tables 853. However, the present invention may be implemented in gaming establishments having any number of gaming machines, gaming tables, etc. It will be appreciated that many gaming establishments include hundreds or even thousands of gaming machines 821 and/or gaming tables 853, not all of which are necessarily included in a bank and some of which may not be connected to a network. At least some of gaming machines 821 and/or mobile devices 870 may be “thin clients” that are configured to perform client-side methods as described elsewhere herein.
Some gaming networks provide features for gaming tables that are similar to those provided for gaming machines, including but not limited to bonusing, player loyalty/player tracking and the use of cashless instruments. Relevant material is provided in U.S. patent application Ser. No. 11/154,833, entitled “CASHLESS INSTRUMENT BASED TABLE GAME PROMOTIONAL SYSTEM AND METHODOLOGY” and filed on Jun. 15, 2005, U.S. Provisional Patent Application No. 60/858,046, entitled “AUTOMATED PLAYER DATA COLLECTION SYSTEM FOR TABLE GAME ENVIRONMENTS” and filed on Nov. 10, 2006, U.S. patent application Ser. No. 11/129,702, entitled “WIDE AREA TABLE GAMING MONITOR AND CONTROL SYSTEM” and filed on May 15, 2005, U.S. patent application Ser. No. 11/425,998 entitled “PROGRESSIVE TABLE GAME BONUSING SYSTEMS AND METHODS”, filed Jun. 22, 2006 and U.S. patent application Ser. No. 11/225,299, entitled “UNIVERSAL CASINO BONUSING SYSTEMS AND METHODS” and filed on Sep. 12, 2005, all of which are incorporated herein by reference. Accordingly, software related to such features may be provided and/or controlled, and related data may be obtained and/or provided, according to the present invention.
Some configurations can provide automated, multi-player roulette, blackjack, baccarat, and other table games. The table games may be conducted by a dealer and/or by using some form of automation, which may include an automated roulette wheel, an electronic representation of a dealer, etc. In some such implementations, devices such as cameras, radio frequency identification devices, etc., may be used to identify and/or track playing cards, chips, etc. Some of gaming tables 853 may be configured for communication with individual player terminals (not shown), which may be configured to accept bets, present an electronic representation of a dealer, indicate game outcomes, etc.
Some gaming networks include electronically configurable tables for playing table games. U.S. patent application Ser. No. 11/517,861, entitled “CASINO DISPLAY METHODS AND DEVICES” and filed on Sep. 7, 2006, describes some such tables and is hereby incorporated by reference. An operator may select a desired game, such as a poker game or a blackjack game, and the table will be automatically configured with geometrical patterns, text, etc., which are appropriate for the desired table game. The desired type of table game may be selected by a control on the table itself or according to instructions received from, e.g., a server or a casino manager via a network interface.
Gaming establishment 805 also includes networked kiosks 877. Depending on the implementation, kiosks 877 may be used for various purposes, including but not limited to cashing out, prize redemption, redeeming points from a player loyalty program, redeeming “cashless” indicia such as bonus tickets, smart cards, etc. In some implementations, kiosks 877 may be used for obtaining information about the gaming establishment, e.g., regarding scheduled events (such as tournaments, entertainment, etc.), regarding a patron's location, etc. Software related to such features may be provided and/or controlled, and related data may be obtained and/or provided, according to the present invention. For example, in some implementations of the invention, kiosks 877 may be configured to receive information from a patron, e.g., by presenting graphical user interfaces.
In this example, each bank 810 has a corresponding switch 815, which may be a conventional bank switch in some implementations. Each switch 815 is configured for communication with one or more devices in computer room 820 via main network device 825, which combines switching and routing functionality in this example. Although various communication protocols may be used, some preferred implementations use the Gaming Standards Association's G2S Message Protocol. Other implementations may use IGT's open, Ethernet-based SuperSAS® protocol, which IGT makes available for downloading without charge. Still other protocols, including but not limited to Best of Breed (“BOB”), may be used to implement various aspects of the invention. IGT has also developed a gaming-industry-specific transport layer called CASH that rides on top of TCP/IP and offers additional functionality and security.
Here, gaming establishment 805 also includes an RFID network, implemented in part by RFID switches 819 and multiple RFID readers 817. An RFID network may be used, for example, to track objects (such as mobile gaming devices 870, which include RFID tags 827 in this example), patrons, etc., in the vicinity of gaming establishment 805. Some examples of how an RFID network may be used in a gaming establishment are set forth in U.S. patent application Ser. No. 11/655,496, entitled “DYNAMIC CASINO TRACKING AND OPTIMIZATION” and filed on Jan. 19, 2007 and in U.S. patent application Ser. No. 11/599,241, entitled “DOWNLOADING UPON THE OCCURRENCE OF PREDETERMINED EVENTS” and filed on Nov. 13, 2006, all of which are hereby incorporated by reference.
As noted elsewhere herein, some implementations of the invention may involve “smart” player loyalty instruments, such as player tracking cards, which include an RFID tag. Accordingly, the location of such RFID-enabled player loyalty instruments may be tracked via the RFID network. In this example, at least some of mobile devices 870 may include an RFID tag 827, which includes encoded identification information for the mobile device 870. Accordingly, the locations of such tagged mobile devices 870 may be tracked via the RFID network in gaming establishment 805. Other location-detection devices and systems, such as the global positioning system (“GPS”), may be used to monitor the location of people and/or devices in the vicinity of gaming establishment 805 or elsewhere.
Various alternative network topologies can be used to implement different aspects of the invention and/or to accommodate varying numbers of networked devices. For example, gaming establishments with large numbers of gaming machines 821 may require multiple instances of some network devices (e.g., of main network device 825, which combines switching and routing functionality in this example) and/or the inclusion of other network devices not shown in
Storage devices 811, Sb™ server 830, License Manager 831, Arbiter 833, servers 832, 834, 836 and 838, host device(s) 860 and main network device 825 are disposed within computer room 820 of gaming establishment 805. In practice, more or fewer devices may be used. Depending on the implementation, some such devices may reside in gaming establishment 805 or elsewhere.
One or more devices in central system 863 may also be configured to perform, at least in part, tasks specific to the present invention. For example, one or more servers 862, arbiter 833, storage devices 864 and/or host devices 860 of central system 863 may be configured to implement the functions described in detail elsewhere herein. These functions may include, but are not limited to, providing functionality for devices such as wager gaming machines 821, mobile devices 870, etc. Such functionality may include, but is not limited to, the implementation of concurrent wager gaming by a player on multiple wager gaming devices, e.g., as described above with reference to
One or more of the servers of computer room 820 may be configured with software for receiving a player's wager gaming notification parameters, determining when a wagering condition corresponds with the wager gaming notification parameters and/or providing a notification to the player when the wagering condition corresponds with the wager gaming notification parameters. Moreover, one or more of the servers may be configured to receive, process and/or provide image data from cameras 809, to provide navigation data to patrons (e.g., to indicate the location of and/or directions to a gaming table, a wager gaming machine, etc., associated with a wager gaming notification), etc.
For example, navigation data (which may include map data, casino layout data, camera image data, etc.) may be provided by one or more of the servers of computer room 820 to mobile devices 870. Some implementations of the present invention include a plurality of networked cameras 809, which may be video cameras, smart cameras, digital still cameras, etc. In some such implementations, such cameras may provide, at least in part, real-time navigation features such as those described in U.S. patent application Ser. No. 12/106,771, entitled “Real-Time Navigation Devices, Systems and Methods,” which is incorporated herein by reference.
Other devices that may be deployed in network 805 do not appear in
The servers and other devices indicated in
Some of these servers may be configured to perform tasks relating to accounting, player loyalty, bonusing/progressives, configuration of gaming machines, etc. One or more such devices may be used to implement a casino management system, such as the IGT Advantage™ Casino System suite of applications, which provides instantaneous information that may be used for decision-making by casino managers. A Radius server and/or a DHCP server may also be configured for communication with the gaming network. Some implementations of the invention provide one or more of these servers in the form of blade servers.
Some preferred embodiments of Sb™ server 830 and the other servers shown in
In some implementations of the invention, many of these devices (including but not limited to License Manager 831, servers 832, 834, 836 and 838, and main network device 825) are mounted in a single rack with Sb™ server 830. Accordingly, many or all such devices will sometimes be referenced in the aggregate as an “Sb™ server.” However, in alternative implementations, one or more of these devices is in communication with Sb™ server 830 and/or other devices of the network but located elsewhere. For example, some of the devices could be mounted in separate racks within computer room 820 or located elsewhere on the network. Moreover, it can be advantageous to store large volumes of data elsewhere via a storage area network (“SAN”).
Computer room 820 may include one or more operator consoles or other host devices that are configured for communication with other devices within and outside of computer room 820. Such host devices may be provided with software, hardware and/or firmware for implementing various aspects of the invention. However, such host devices need not be located within computer room 820. Wired host devices 860 (which are desktop and laptop computers in this example) and wireless devices 870 (which are PDAs in this example) may be located elsewhere in gaming establishment 805 or at a remote location.
Some embodiments of the invention include devices for implementing access control, security and/or other functions relating to the communication between different devices on the network. In this example, arbiter 833 serves as an intermediary between different devices on the network. Arbiter 833 may be implemented, for example, via software that is running on a server or another networked device. Some implementations of Arbiter 833 are described in U.S. patent application Ser. No. 10/948,387, entitled “METHODS AND APPARATUS FOR NEGOTIATING COMMUNICATIONS WITHIN A GAMING NETWORK” and filed Sep. 23, 2004 (the “Arbiter Application”), which is incorporated herein by reference and for all purposes. In some preferred implementations, Arbiter 833 is a repository for the configuration information required for communication between devices on the gaming network (and, in some implementations, devices outside the gaming network). Although Arbiter 833 can be implemented in various ways, one exemplary implementation is discussed in the following paragraphs.
Referring to
Although the program memories 922, 932 are shown in
As shown in
Communications between the gaming machine 821 and the network computer 923 may involve different information types of varying levels of sensitivity resulting in varying levels of encryption techniques depending on the sensitivity of the information. For example, communications such as drink orders and statistical information may be considered less sensitive. A drink order or statistical information may remain encrypted, although with moderately secure encryption techniques, such as RC4, resulting in less processing power and less time for encryption. On the other hand, financial information (e.g., account information, winnings, etc.), download information (e.g., game and/or peripheral software, licensing information, etc.) and personal information (e.g., social security number, personal preferences, etc.) may be encrypted with stronger encryption techniques such as DES or 3DES to provide increased security.
As disclosed in further detail in the Arbiter Application, the Arbiter 833 may verify the authenticity of devices in the gaming network, including but not limited to devices sending queries and/or remote procedure calls to gaming machines. The Arbiter 833 may receive a request for a communication session from a network device. For ease of explanation, the requesting network device may be referred to as the client, and the requested network device may be referred to as the host. The client may be any device on the network and the request may be for a communication session with any other network device. The client may specify the host, or the gaming security arbiter may select the host based on the request and based on information about the client and potential hosts. The Arbiter 833 may provide encryption keys (session keys) for the communication session to the client via the secure communication channel. Either the host and/or the session key may be provided in response to the request, or may have been previously provided. The client may contact the host to initiate the communication session. The host may then contact the Arbiter 833 to determine the authenticity of the client. The Arbiter 833 may provide affirmation (or lack thereof) of the authenticity of the client to the host and provide a corresponding session key, in response to which the network devices may initiate the communication session directly with each other using the session keys to encrypt and decrypt messages.
Alternatively, upon receiving a request for a communication session, the Arbiter 833 may contact the host regarding the request and provide corresponding session keys to both the client and the host. The Arbiter 833 may then initiate either the client or the host to begin their communication session. In turn, the client and host may begin the communication session directly with each other using the session keys to encrypt and decrypt messages. An additional explanation of the communication request, communication response and key distribution is provided in the Arbiter Application.
Referring again to
If a host device is located in a remote location, security methods and devices (such as firewalls, authentication and/or encryption) should be deployed in order to prevent the unauthorized access of the gaming network.
Similarly, any other connection between gaming network 805 and the outside world should only be made with trusted devices via a secure link, e.g., via a virtual private network (“VPN”) tunnel. For example, the illustrated connection between Sb™ server 830, gateway 850 and central system 863 (that may be used for communications involving peripheral device software downloads, etc.) is advantageously made via a VPN tunnel. Details of VPN methods that may be used with the present invention are described in the reference, “Virtual Private Networks-Technologies and Solutions,” by R. Yueh and T. Strayer, Addison-Wesley, 2001, ISBN#0-201-70209-6, which is incorporated herein by reference and for all purposes. Additionally VPNs may be implemented using a variety of protocols, such as, for example, IP Security (IPSec) Protocol, Layer 2 Tunneling Protocol, Multiprotocol Label Switching (MPLS) Protocol, etc. Details of these protocols, including RFC reports, may be obtained from the VPN Consortium, an industry trade group (http://www.vpnc.com, VPNC, Santa Cruz, Calif.).
Alternatively, a permanent virtual circuit (“PVC”) can be established to provide a dedicated and secure circuit link between two facilities, e.g., between a casino and central system 863. A PVC is a virtual circuit established for repeated use between the same data terminals. A PVC could be provided, for example, via AT&T's Asynchronous Transfer Mode (“ATM”) switching fabric. Some implementations provide a dedicated line from an endpoint (e.g., from casino 805) into the ATM backbone. Other implementations provide a connection over another network (e.g., the Internet) between an endpoint and the nearest device of the ATM backbone, e.g., to the nearest edge router. In some such implementations, the fixed-sized cells used in the ATM switching fabric may be encapsulated in variable sized packets (such as Internet Protocol or Ethernet packets) for transmission to and from the ATM backbone.
For security purposes, information transmitted to, on or from a gaming establishment may be encrypted. In one implementation, the information may be symmetrically encrypted using a symmetric encryption key, where the symmetric encryption key is asymmetrically encrypted using a private key. The public key may, for example, be obtained from a remote public key server. The encryption algorithm may reside in processor logic stored on the gaming machine. When a remote server receives a message containing the encrypted data, the symmetric encryption key is decrypted with a private key residing on the remote server and the symmetrically encrypted information sent from the gaming machine is decrypted using the symmetric encryption key. A different symmetric encryption key is used for each transaction where the key is randomly generated. Symmetric encryption and decryption is preferably applied to most information because symmetric encryption algorithms tend to be 100-10,000 faster than asymmetric encryption algorithms.
Some network implementations may use Trusted Network Connect (“TNC”), which is an open architecture provided by the Trusted Network Connect Sub Group (“TNC-SG”) of the Trusted Computing Group (TCG). TNC enables network operators to provide endpoint integrity at every network connection, thus enabling interoperability among multi-vendor network endpoints. Alternatively, or additionally, the Secure Internet File Transfer (“SIFT”) may be employed. SIFT allows devices to send and receive data over the Internet in a secure (128-bit encryption) method of transport.
Providing secure connections between devices in a gaming network, such as the connections between the local devices of the gaming network 805 and central system 863, allows for the deployment of many advantageous features. For example, a customer (e.g., an employee of a gaming establishment) may be able to log onto an account of central system 863 to obtain the account information such as the customer's current and prior account status. Automatic updates of a customer's software may also be enabled. For example, central system 863 may notify one or more devices in gaming establishment 805 regarding new products and/or product updates. For example, central system 863 may notify server (or other device) in computer room 820 regarding new software, software updates, the status of current software licenses, etc. Alternatively, such updates could be automatically provided to a server in computer room 820 and downloaded to networked gaming machines.
After the local server receives this information, relevant products of interest may be identified (by the server, by another device or by a human being). If an update or a new software product is desired, it can be downloaded from the central system. Similarly, a customer may choose to renew a software license via a secure connection with central system 863, e.g., in response to a notification that the software license is required.
In addition, providing secure connections between different gaming establishments can enable alternative implementations of the invention. For example, a number of gaming establishments may be owned and/or controlled by the same entity. In such situations, having secure communications between gaming establishments makes it possible for a gaming entity to use one or more servers in a gaming establishment as an interface between central system 863 and gaming machines in multiple gaming establishments. For example, new or updated software may be obtained by a server in one gaming establishment and distributed to gaming machines in that gaming establishment and/or other gaming establishments. A server in one gaming establishment may perform services, such as patron identification services, in response to a request from a device in another gaming establishment.
The interfaces 1068 are typically provided as interface cards (sometimes referred to as “linecards”). Generally, interfaces 1068 control the sending and receiving of data packets over the network and sometimes support other peripherals used with the network device 1060. Among the interfaces that may be provided are FC interfaces, Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, and the like. In addition, various very high-speed interfaces may be provided, such as fast Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POS interfaces, FDDI interfaces, ASI interfaces, DHEI interfaces and the like.
When acting under the control of appropriate software or firmware, in some implementations of the invention CPU 1062 may be responsible for implementing specific functions associated with the functions of a desired network device. According to some embodiments, CPU 1062 accomplishes all these functions under the control of software including an operating system and any appropriate applications software.
CPU 1062 may include one or more processors 1063 such as a processor from the Motorola family of microprocessors or the MIPS family of microprocessors. In an alternative embodiment, processor 1063 is specially designed hardware for controlling the operations of network device 1060. In a specific embodiment, a memory 1061 (such as non-volatile RAM and/or ROM) also forms part of CPU 1062. However, there are many different ways in which memory could be coupled to the system. Memory block 1061 may be used for a variety of purposes such as, for example, caching and/or storing data, programming instructions, etc.
Regardless of network device's configuration, it may employ one or more memories or memory modules (such as, for example, memory block 1065) configured to store data, program instructions for the general-purpose network operations and/or other information relating to the functionality of the techniques described herein. The program instructions may control the operation of an operating system and/or one or more applications, for example.
Because such information and program instructions may be employed to implement the systems/methods described herein, the present invention relates to machine-readable media that include program instructions, state information, etc. for performing various operations described herein. Examples of machine-readable media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM) and random access memory (RAM). The invention may also be embodied in a carrier wave traveling over an appropriate medium such as airwaves, optical lines, electric lines, etc. Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher-level code that may be executed by the computer using an interpreter.
Although the system shown in
The above-described devices and materials will be familiar to those of skill in the gaming industry and/or in the computer hardware and software arts. Although many of the components and processes are described above in the singular for convenience, it will be appreciated by one of skill in the art that multiple components and repeated processes can also be used to practice the techniques of the present invention.
Although illustrative embodiments and applications of this invention are shown and described herein, many variations and modifications are possible which remain within the concept, scope, and spirit of the invention, and these variations should become clear after perusal of this application. For example, while much of the discussion herein involves wager gaming involving stationary wager gaming machines, some aspects of the present invention may be applied to gaming that involves of other types of devices, e.g., one or more mobile gaming devices. Moreover, some aspects of the present invention are not limited to wager gaming, but may instead be applied generally to various other types of gaming. Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
4335809 | Wain | Jun 1982 | A |
4572509 | Sitrick | Feb 1986 | A |
4652998 | Koza et al. | Mar 1987 | A |
4842278 | Markowicz | Jun 1989 | A |
4856787 | Itkis | Aug 1989 | A |
4866515 | Tagawa et al. | Sep 1989 | A |
4924378 | Hershey et al. | May 1990 | A |
5138712 | Corbin | Aug 1992 | A |
5142622 | Owens | Aug 1992 | A |
5178395 | Lovell | Jan 1993 | A |
5179517 | Sarbin et al. | Jan 1993 | A |
5276312 | McCarthy | Jan 1994 | A |
5288978 | Iijima | Feb 1994 | A |
5305195 | Murphy | Apr 1994 | A |
5344144 | Canon | Sep 1994 | A |
5349642 | Kingdon | Sep 1994 | A |
5375206 | Hunter et al. | Dec 1994 | A |
5377993 | Josephs | Jan 1995 | A |
5393057 | Marnell, II | Feb 1995 | A |
5404567 | DePietro et al. | Apr 1995 | A |
5429361 | Raven et al. | Jul 1995 | A |
5430791 | Feit et al. | Jul 1995 | A |
5438508 | Wyman | Aug 1995 | A |
5465082 | Weingardt | Nov 1995 | A |
5499340 | Barritz | Mar 1996 | A |
5507491 | Gatto et al. | Apr 1996 | A |
5511781 | Wood et al. | Apr 1996 | A |
5530232 | Taylor | Jun 1996 | A |
5531448 | Moody | Jul 1996 | A |
5559313 | Claus et al. | Sep 1996 | A |
5560603 | Seelig et al. | Oct 1996 | A |
5564700 | Celona | Oct 1996 | A |
5566337 | Szymanski et al. | Oct 1996 | A |
5578808 | Taylor | Nov 1996 | A |
5586257 | Perlman | Dec 1996 | A |
5586937 | Menashe | Dec 1996 | A |
5617331 | Wakai et al. | Apr 1997 | A |
5626341 | Jones et al. | May 1997 | A |
5630757 | Gagin et al. | May 1997 | A |
5640192 | Garfinkle | Jun 1997 | A |
5643086 | Alcorn et al. | Jul 1997 | A |
5649118 | Carlisle et al. | Jul 1997 | A |
5655603 | Schulte et al. | Aug 1997 | A |
5655961 | Acres et al. | Aug 1997 | A |
5664998 | Seelig et al. | Sep 1997 | A |
5671412 | Christiano | Sep 1997 | A |
5702304 | Acres et al. | Dec 1997 | A |
5708709 | Rose | Jan 1998 | A |
5717604 | Wiggins | Feb 1998 | A |
5732950 | Moody | Mar 1998 | A |
5741183 | Acres et al. | Apr 1998 | A |
5745879 | Wyman | Apr 1998 | A |
5752882 | Acres et al. | May 1998 | A |
5755621 | Marks et al. | May 1998 | A |
5758069 | Olsen | May 1998 | A |
5759102 | Pease et al. | Jun 1998 | A |
5762552 | Vuong et al. | Jun 1998 | A |
5766076 | Pease et al. | Jun 1998 | A |
5768382 | Schneier et al. | Jun 1998 | A |
5779545 | Berg et al. | Jul 1998 | A |
5779549 | Walker et al. | Jul 1998 | A |
5788573 | Baerlocher et al. | Aug 1998 | A |
5800268 | Molnick | Sep 1998 | A |
5806855 | Cherry | Sep 1998 | A |
5820459 | Acres et al. | Oct 1998 | A |
5823873 | Moody | Oct 1998 | A |
5828840 | Cowan et al. | Oct 1998 | A |
5833540 | Miodunski et al. | Nov 1998 | A |
5836817 | Acres et al. | Nov 1998 | A |
5845283 | Williams et al. | Dec 1998 | A |
5851011 | Loff | Dec 1998 | A |
5851149 | Xidos et al. | Dec 1998 | A |
5855515 | Pease et al. | Jan 1999 | A |
5871398 | Schneier et al. | Feb 1999 | A |
5876284 | Acres et al. | Mar 1999 | A |
5885158 | Torango et al. | Mar 1999 | A |
5890962 | Takemoto | Apr 1999 | A |
5903732 | Reed et al. | May 1999 | A |
5905248 | Russell et al. | May 1999 | A |
5913164 | Pawa et al. | Jun 1999 | A |
5917725 | Thacher et al. | Jun 1999 | A |
5918039 | Buswell et al. | Jun 1999 | A |
5925127 | Ahmad | Jul 1999 | A |
5941773 | Harlick | Aug 1999 | A |
5947820 | Morro et al. | Sep 1999 | A |
5947822 | Weiss | Sep 1999 | A |
5951397 | Dickinson | Sep 1999 | A |
5951611 | La Pierre | Sep 1999 | A |
5971271 | Wynn et al. | Oct 1999 | A |
5971849 | Falciglia | Oct 1999 | A |
5974409 | Sanu et al. | Oct 1999 | A |
5980093 | Jones et al. | Nov 1999 | A |
5983190 | Trower, II et al. | Nov 1999 | A |
5991760 | Gauvin et al. | Nov 1999 | A |
5991790 | Shah et al. | Nov 1999 | A |
5996068 | Dwyer, III et al. | Nov 1999 | A |
5999808 | La Due | Dec 1999 | A |
6001016 | Walker et al. | Dec 1999 | A |
6003066 | Ryan et al. | Dec 1999 | A |
6003094 | Dean | Dec 1999 | A |
6003123 | Carter et al. | Dec 1999 | A |
6011850 | Bertrand et al. | Jan 2000 | A |
6024640 | Walker et al. | Feb 2000 | A |
6033307 | Vancura | Mar 2000 | A |
6068552 | Walker et al. | May 2000 | A |
6068982 | Rolfe et al. | May 2000 | A |
6071190 | Weiss et al. | Jun 2000 | A |
6079711 | Wei et al. | Jun 2000 | A |
6085247 | Parsons, Jr. et al. | Jul 2000 | A |
6089975 | Dunn | Jul 2000 | A |
6089982 | Holch et al. | Jul 2000 | A |
6099408 | Schneier et al. | Aug 2000 | A |
6106396 | Alcorn et al. | Aug 2000 | A |
6108420 | Larose et al. | Aug 2000 | A |
6110041 | Walker et al. | Aug 2000 | A |
6113098 | Adams | Sep 2000 | A |
6113495 | Walker et al. | Sep 2000 | A |
6117013 | Eiba | Sep 2000 | A |
6135884 | Hendrick et al. | Oct 2000 | A |
6135887 | Pease et al. | Oct 2000 | A |
6141737 | Krantz et al. | Oct 2000 | A |
6142872 | Walker et al. | Nov 2000 | A |
6149522 | Alcorn et al. | Nov 2000 | A |
6151707 | Hecksel et al. | Nov 2000 | A |
6159095 | Frohm et al. | Dec 2000 | A |
6162122 | Acres et al. | Dec 2000 | A |
6168520 | Baerlocher et al. | Jan 2001 | B1 |
6203428 | Giobbi et al. | Mar 2001 | B1 |
6206782 | Walker et al. | Mar 2001 | B1 |
6219836 | Wells et al. | Apr 2001 | B1 |
6224486 | Walker et al. | May 2001 | B1 |
6234896 | Walker et al. | May 2001 | B1 |
6241608 | Torango | Jun 2001 | B1 |
6251014 | Stockdale et al. | Jun 2001 | B1 |
6254483 | Acres | Jul 2001 | B1 |
6257981 | Acres et al. | Jul 2001 | B1 |
6264561 | Saffari et al. | Jul 2001 | B1 |
6287200 | Sharma | Sep 2001 | B1 |
6287202 | Pascal et al. | Sep 2001 | B1 |
6293866 | Walker et al. | Sep 2001 | B1 |
6304905 | Clark | Oct 2001 | B1 |
6308271 | Tanaka | Oct 2001 | B2 |
6312332 | Walker et al. | Nov 2001 | B1 |
6312333 | Acres | Nov 2001 | B1 |
6319122 | Packes, Jr. et al. | Nov 2001 | B1 |
6319125 | Acres | Nov 2001 | B1 |
6345386 | Delo et al. | Feb 2002 | B1 |
6353928 | Altberg et al. | Mar 2002 | B1 |
6354946 | Finn | Mar 2002 | B1 |
6358150 | Mir et al. | Mar 2002 | B1 |
6361437 | Walker et al. | Mar 2002 | B1 |
6361441 | Walker et al. | Mar 2002 | B1 |
6364314 | Canterbury | Apr 2002 | B1 |
6368216 | Hedrick et al. | Apr 2002 | B1 |
6383074 | Boggs | May 2002 | B1 |
6389538 | Gruse et al. | May 2002 | B1 |
6389589 | Mishra et al. | May 2002 | B1 |
6394902 | Glavich et al. | May 2002 | B1 |
6394907 | Rowe | May 2002 | B1 |
6397381 | Delo et al. | May 2002 | B1 |
6398645 | Yoseloff | Jun 2002 | B1 |
6402614 | Schneier et al. | Jun 2002 | B1 |
6409602 | Wiltshire et al. | Jun 2002 | B1 |
6418554 | Delo et al. | Jul 2002 | B1 |
6425828 | Walker et al. | Jul 2002 | B2 |
6427227 | Chamberlain | Jul 2002 | B1 |
6439996 | LeMay et al. | Aug 2002 | B2 |
6442529 | Krishan et al. | Aug 2002 | B1 |
6443839 | Stockdale et al. | Sep 2002 | B2 |
6450887 | Mir et al. | Sep 2002 | B1 |
6457175 | Lerche | Sep 2002 | B1 |
RE37885 | Acres et al. | Oct 2002 | E |
6488585 | Wells et al. | Dec 2002 | B1 |
6503146 | Walker et al. | Jan 2003 | B2 |
6503147 | Stockdale et al. | Jan 2003 | B1 |
6508710 | Paravia et al. | Jan 2003 | B1 |
6511068 | Sklansky et al. | Jan 2003 | B1 |
6523166 | Mishra et al. | Feb 2003 | B1 |
6527638 | Walker et al. | Mar 2003 | B1 |
6532543 | Smith et al. | Mar 2003 | B1 |
6533664 | Crumby | Mar 2003 | B1 |
6565434 | Acres | May 2003 | B1 |
6575832 | Manfredi et al. | Jun 2003 | B1 |
6578199 | Tsou et al. | Jun 2003 | B1 |
6592457 | Frohm et al. | Jul 2003 | B1 |
6595856 | Ginsburg et al. | Jul 2003 | B1 |
6607439 | Schneier et al. | Aug 2003 | B2 |
6609978 | Paulsen | Aug 2003 | B1 |
6620047 | Alcorn et al. | Sep 2003 | B1 |
6628939 | Paulsen | Sep 2003 | B2 |
6638170 | Crumby | Oct 2003 | B1 |
6645077 | Rowe | Nov 2003 | B2 |
6648758 | Bennett et al. | Nov 2003 | B2 |
6652378 | Cannon et al. | Nov 2003 | B2 |
6656040 | Brosnan et al. | Dec 2003 | B1 |
6656044 | Lewis | Dec 2003 | B1 |
6682423 | Brosnan et al. | Jan 2004 | B2 |
6685567 | Cockerille et al. | Feb 2004 | B2 |
6695696 | Kaminkow | Feb 2004 | B1 |
6712699 | Walker et al. | Mar 2004 | B2 |
6712702 | Goldberg et al. | Mar 2004 | B2 |
6722986 | Lyons et al. | Apr 2004 | B1 |
6733390 | Walker et al. | May 2004 | B2 |
6746327 | Frohm et al. | Jun 2004 | B2 |
6749510 | Giobbi | Jun 2004 | B2 |
6780111 | Cannon et al. | Aug 2004 | B2 |
6782477 | McCarroll | Aug 2004 | B2 |
6786819 | Baerlocher et al. | Sep 2004 | B2 |
6790142 | Okada et al. | Sep 2004 | B2 |
6790143 | Crumby | Sep 2004 | B2 |
6802778 | LeMay et al. | Oct 2004 | B1 |
6804763 | Stockdale et al. | Oct 2004 | B1 |
6805634 | Wells et al. | Oct 2004 | B1 |
6811488 | Paravia et al. | Nov 2004 | B2 |
6813765 | Flores | Nov 2004 | B1 |
6816882 | Conner et al. | Nov 2004 | B1 |
6823456 | Dan et al. | Nov 2004 | B1 |
6830515 | Rowe | Dec 2004 | B2 |
6832958 | Acres et al. | Dec 2004 | B2 |
6834245 | Ota et al. | Dec 2004 | B2 |
6836794 | Lucovsky et al. | Dec 2004 | B1 |
6837793 | McClintic | Jan 2005 | B2 |
6843723 | Joshi | Jan 2005 | B2 |
6843725 | Nelson | Jan 2005 | B2 |
6846238 | Wells | Jan 2005 | B2 |
6852031 | Rowe | Feb 2005 | B1 |
6855054 | White et al. | Feb 2005 | B2 |
6855057 | Namba et al. | Feb 2005 | B2 |
6857959 | Nguyen | Feb 2005 | B1 |
6860810 | Cannon et al. | Mar 2005 | B2 |
6863608 | LeMay et al. | Mar 2005 | B1 |
6866581 | Martinek et al. | Mar 2005 | B2 |
6866584 | Michaelson | Mar 2005 | B2 |
6866586 | Oberberger et al. | Mar 2005 | B2 |
6875109 | Stockdale | Apr 2005 | B2 |
6875110 | Crumby | Apr 2005 | B1 |
6878063 | Manfredi et al. | Apr 2005 | B2 |
6884162 | Raverdy et al. | Apr 2005 | B2 |
6884166 | Leen et al. | Apr 2005 | B2 |
6884170 | Rowe | Apr 2005 | B2 |
6884171 | Eck et al. | Apr 2005 | B2 |
6884173 | Gauselmann | Apr 2005 | B2 |
6884174 | Lundy et al. | Apr 2005 | B2 |
6887151 | Leen et al. | May 2005 | B2 |
6887156 | DeWeese et al. | May 2005 | B2 |
6889159 | Klotz et al. | May 2005 | B2 |
6890256 | Walker et al. | May 2005 | B2 |
6896616 | Weiss | May 2005 | B2 |
6896618 | Benoy et al. | May 2005 | B2 |
6899627 | Lam et al. | May 2005 | B2 |
6899628 | Leen et al. | May 2005 | B2 |
6901375 | Fernandez | May 2005 | B2 |
6902478 | McClintic | Jun 2005 | B2 |
6902481 | Breckner et al. | Jun 2005 | B2 |
6908390 | Nguyen et al. | Jun 2005 | B2 |
6908391 | Gatto et al. | Jun 2005 | B2 |
6910965 | Downes | Jun 2005 | B2 |
6923720 | Loose | Aug 2005 | B2 |
6939226 | Joshi | Sep 2005 | B1 |
6939234 | Beatty | Sep 2005 | B2 |
6942571 | McAllister et al. | Sep 2005 | B1 |
6945870 | Gatto et al. | Sep 2005 | B2 |
6960136 | Joshi et al. | Nov 2005 | B2 |
6991544 | Soltys et al. | Jan 2006 | B2 |
7051004 | Nuttall et al. | May 2006 | B2 |
7066815 | Walker et al. | Jun 2006 | B2 |
7105736 | Laakso | Sep 2006 | B2 |
7156741 | Hornik et al. | Jan 2007 | B2 |
7355112 | Laakso | Apr 2008 | B2 |
7360761 | Durham et al. | Apr 2008 | B2 |
8147322 | Walker et al. | Apr 2012 | B2 |
20010036857 | Mothwurf et al. | Nov 2001 | A1 |
20010044337 | Rowe et al. | Nov 2001 | A1 |
20010046893 | Giobbi et al. | Nov 2001 | A1 |
20010055990 | Acres | Dec 2001 | A1 |
20020032049 | Walker et al. | Mar 2002 | A1 |
20020045474 | Singer et al. | Apr 2002 | A1 |
20020045484 | Eck et al. | Apr 2002 | A1 |
20020057800 | Gordon et al. | May 2002 | A1 |
20020058546 | Acres | May 2002 | A2 |
20020068629 | Allen et al. | Jun 2002 | A1 |
20020068631 | Raverdy et al. | Jun 2002 | A1 |
20020071557 | Nguyen | Jun 2002 | A1 |
20020071560 | Kurn et al. | Jun 2002 | A1 |
20020080969 | Giobbi | Jun 2002 | A1 |
20020111209 | Walker et al. | Aug 2002 | A1 |
20020116615 | Nguyen et al. | Aug 2002 | A1 |
20020137217 | Rowe | Sep 2002 | A1 |
20020138594 | Rowe | Sep 2002 | A1 |
20020144116 | Giobbi | Oct 2002 | A1 |
20020151358 | Walker et al. | Oct 2002 | A1 |
20020151360 | Durham et al. | Oct 2002 | A1 |
20020151363 | Letovsky et al. | Oct 2002 | A1 |
20020160826 | Gomez et al. | Oct 2002 | A1 |
20020169022 | Canterbury | Nov 2002 | A1 |
20020173355 | Walker et al. | Nov 2002 | A1 |
20020174160 | Gatto et al. | Nov 2002 | A1 |
20020174444 | Gatto et al. | Nov 2002 | A1 |
20020177483 | Cannon | Nov 2002 | A1 |
20020183105 | Cannon et al. | Dec 2002 | A1 |
20020188940 | Breckner et al. | Dec 2002 | A1 |
20030027638 | Schneider et al. | Feb 2003 | A1 |
20030032474 | Kaminkow | Feb 2003 | A1 |
20030036430 | Cannon | Feb 2003 | A1 |
20030045351 | Gauselmann | Mar 2003 | A1 |
20030045354 | Giobbi | Mar 2003 | A1 |
20030054879 | Schneier et al. | Mar 2003 | A1 |
20030060268 | Falconer | Mar 2003 | A1 |
20030060286 | Walker et al. | Mar 2003 | A1 |
20030064771 | Morrow et al. | Apr 2003 | A1 |
20030064807 | Walker et al. | Apr 2003 | A1 |
20030069058 | Byrne et al. | Apr 2003 | A1 |
20030073497 | Nelson | Apr 2003 | A1 |
20030078093 | Simms et al. | Apr 2003 | A1 |
20030078094 | Gatto et al. | Apr 2003 | A1 |
20030078101 | Schneider et al. | Apr 2003 | A1 |
20030092489 | Veradej | May 2003 | A1 |
20030093669 | Morais et al. | May 2003 | A1 |
20030100359 | Loose et al. | May 2003 | A1 |
20030100369 | Gatto et al. | May 2003 | A1 |
20030100370 | Gatto et al. | May 2003 | A1 |
20030100371 | Gatto et al. | May 2003 | A1 |
20030100372 | Gatto et al. | May 2003 | A1 |
20030104865 | Itkis et al. | Jun 2003 | A1 |
20030114218 | McClintic | Jun 2003 | A1 |
20030114219 | McClintic | Jun 2003 | A1 |
20030115351 | Giobbi | Jun 2003 | A1 |
20030125107 | Cannon | Jul 2003 | A1 |
20030139214 | Wolf et al. | Jul 2003 | A1 |
20030140134 | Swanson et al. | Jul 2003 | A1 |
20030162583 | Baerlocher et al. | Aug 2003 | A1 |
20030162589 | Nguyen et al. | Aug 2003 | A1 |
20030171149 | Rothschild | Sep 2003 | A1 |
20030176219 | Manfredi et al. | Sep 2003 | A1 |
20030181231 | Vancura et al. | Sep 2003 | A1 |
20030186745 | Nguyen et al. | Oct 2003 | A1 |
20030188306 | Harris et al. | Oct 2003 | A1 |
20030190941 | Byrne | Oct 2003 | A1 |
20030195033 | Gazdic et al. | Oct 2003 | A1 |
20030216182 | Gauselmann | Nov 2003 | A1 |
20030224852 | Walker et al. | Dec 2003 | A1 |
20030228904 | Acres et al. | Dec 2003 | A1 |
20030228907 | Gatto et al. | Dec 2003 | A1 |
20030228912 | Wells et al. | Dec 2003 | A1 |
20030232650 | Beatty | Dec 2003 | A1 |
20040002381 | Alcorn et al. | Jan 2004 | A1 |
20040002385 | Nguyen | Jan 2004 | A1 |
20040003389 | Reynar et al. | Jan 2004 | A1 |
20040005919 | Walker et al. | Jan 2004 | A1 |
20040010700 | Mont | Jan 2004 | A1 |
20040015423 | Walker et al. | Jan 2004 | A1 |
20040023721 | Giobbi | Feb 2004 | A1 |
20040024666 | Walker et al. | Feb 2004 | A1 |
20040029635 | Giobbi | Feb 2004 | A1 |
20040038723 | Schneier et al. | Feb 2004 | A1 |
20040048660 | Gentles et al. | Mar 2004 | A1 |
20040048667 | Rowe | Mar 2004 | A1 |
20040053664 | Byrne | Mar 2004 | A1 |
20040054952 | Morrow et al. | Mar 2004 | A1 |
20040063489 | Crumby | Apr 2004 | A1 |
20040072604 | Toyoda | Apr 2004 | A1 |
20040072608 | Toyoda | Apr 2004 | A1 |
20040072619 | Brosnan et al. | Apr 2004 | A1 |
20040082385 | Silva et al. | Apr 2004 | A1 |
20040092310 | Brosnan et al. | May 2004 | A1 |
20040098597 | Giobbi | May 2004 | A1 |
20040106446 | Cannon et al. | Jun 2004 | A1 |
20040106452 | Nguyen et al. | Jun 2004 | A1 |
20040124243 | Gatto et al. | Jul 2004 | A1 |
20040127279 | Gatto et al. | Jul 2004 | A1 |
20040132532 | Brosnan et al. | Jul 2004 | A1 |
20040133485 | Schoonmaker et al. | Jul 2004 | A1 |
20040142739 | Loose et al. | Jul 2004 | A1 |
20040142742 | Schneider et al. | Jul 2004 | A1 |
20040152509 | Hornik et al. | Aug 2004 | A1 |
20040162144 | Loose et al. | Aug 2004 | A1 |
20040166923 | Michaelson et al. | Aug 2004 | A1 |
20040166940 | Rothschild | Aug 2004 | A1 |
20040166942 | Muir | Aug 2004 | A1 |
20040176162 | Rothschild | Sep 2004 | A1 |
20040176167 | Michaelson et al. | Sep 2004 | A1 |
20040179701 | Boyd | Sep 2004 | A1 |
20040180721 | Rowe | Sep 2004 | A1 |
20040180722 | Giobbi | Sep 2004 | A1 |
20040185936 | Block et al. | Sep 2004 | A1 |
20040193726 | Gatto et al. | Sep 2004 | A1 |
20040198494 | Nguyen et al. | Oct 2004 | A1 |
20040198496 | Gatto et al. | Oct 2004 | A1 |
20040204232 | Asher et al. | Oct 2004 | A1 |
20040204244 | Rathsack et al. | Oct 2004 | A1 |
20040214622 | Atkinson | Oct 2004 | A1 |
20040214627 | Jordan et al. | Oct 2004 | A1 |
20040214640 | Giobbi | Oct 2004 | A1 |
20040214641 | Giobbi | Oct 2004 | A1 |
20040215756 | VanAntwerp et al. | Oct 2004 | A1 |
20040219967 | Giobbi et al. | Nov 2004 | A1 |
20040219983 | Giobbi | Nov 2004 | A1 |
20040224770 | Wolf et al. | Nov 2004 | A1 |
20040229684 | Blackburn et al. | Nov 2004 | A1 |
20040229698 | Lind et al. | Nov 2004 | A1 |
20040229699 | Gentles et al. | Nov 2004 | A1 |
20040235559 | Brosnan et al. | Nov 2004 | A1 |
20040235563 | Blackburn et al. | Nov 2004 | A1 |
20040242298 | Inamura et al. | Dec 2004 | A1 |
20040242303 | Walker et al. | Dec 2004 | A1 |
20040242328 | Blackburn et al. | Dec 2004 | A1 |
20040242329 | Blackburn et al. | Dec 2004 | A1 |
20040242330 | Blackburn et al. | Dec 2004 | A1 |
20040242331 | Blackburn et al. | Dec 2004 | A1 |
20040243848 | Blackburn et al. | Dec 2004 | A1 |
20040243849 | Blackburn et al. | Dec 2004 | A1 |
20040248642 | Rothschild | Dec 2004 | A1 |
20040248645 | Blackburn et al. | Dec 2004 | A1 |
20040248646 | Canterbury | Dec 2004 | A1 |
20040248651 | Gagner | Dec 2004 | A1 |
20040254006 | Lam et al. | Dec 2004 | A1 |
20040254013 | Quraishi et al. | Dec 2004 | A1 |
20040254014 | Quraishi et al. | Dec 2004 | A1 |
20040254954 | Gatto et al. | Dec 2004 | A1 |
20040255139 | Giobbi | Dec 2004 | A1 |
20040259629 | Michaelson et al. | Dec 2004 | A1 |
20040259633 | Gentles et al. | Dec 2004 | A1 |
20040259640 | Gentles et al. | Dec 2004 | A1 |
20040259643 | Gentles | Dec 2004 | A1 |
20040266532 | Blackburn et al. | Dec 2004 | A1 |
20040266533 | Gentles et al. | Dec 2004 | A1 |
20050003886 | Englman et al. | Jan 2005 | A1 |
20050009599 | Ryan | Jan 2005 | A1 |
20050009601 | Manfredi et al. | Jan 2005 | A1 |
20050009607 | Russell et al. | Jan 2005 | A1 |
20050010738 | Stockdale et al. | Jan 2005 | A1 |
20050014559 | Mattice et al. | Jan 2005 | A1 |
20050032566 | Baerlocher et al. | Feb 2005 | A1 |
20050032573 | Acres et al. | Feb 2005 | A1 |
20050032577 | Blackburn et al. | Feb 2005 | A1 |
20050037708 | Torvinen | Feb 2005 | A1 |
20050043072 | Nelson | Feb 2005 | A1 |
20050043088 | Nguyen et al. | Feb 2005 | A1 |
20050043090 | Pryzby et al. | Feb 2005 | A1 |
20050043094 | Nguyen et al. | Feb 2005 | A1 |
20050044535 | Copper | Feb 2005 | A1 |
20050049037 | Anderson et al. | Mar 2005 | A1 |
20050054431 | Walker et al. | Mar 2005 | A1 |
20050054438 | Rothschild et al. | Mar 2005 | A1 |
20050054440 | Anderson et al. | Mar 2005 | A1 |
20050054445 | Gatto et al. | Mar 2005 | A1 |
20050054447 | Hiroyama et al. | Mar 2005 | A1 |
20050054448 | Frerking et al. | Mar 2005 | A1 |
20050059457 | Rothschild et al. | Mar 2005 | A1 |
20050059493 | Tyson et al. | Mar 2005 | A1 |
20050059494 | Kammler | Mar 2005 | A1 |
20050064939 | McSheffrey et al. | Mar 2005 | A1 |
20050075983 | St. Denis | Apr 2005 | A1 |
20050081623 | Frank | Apr 2005 | A1 |
20050086286 | Gatto et al. | Apr 2005 | A1 |
20050090313 | Rowe | Apr 2005 | A1 |
20050096114 | Cannon et al. | May 2005 | A1 |
20050096133 | Hoefelmeyer et al. | May 2005 | A1 |
20050097342 | Gatto et al. | May 2005 | A1 |
20050101370 | Lind et al. | May 2005 | A1 |
20050107164 | Muir et al. | May 2005 | A1 |
20050113172 | Gong | May 2005 | A1 |
20050114272 | Herrmann et al. | May 2005 | A1 |
20050119045 | Fujimoto | Jun 2005 | A1 |
20050119046 | Fujimoto | Jun 2005 | A1 |
20050137012 | Michaealson | Jun 2005 | A1 |
20050148385 | Michaealson | Jul 2005 | A1 |
20050181860 | Nguyen et al. | Aug 2005 | A1 |
20050193209 | Saunders et al. | Sep 2005 | A1 |
20050221882 | Nguyen et al. | Oct 2005 | A1 |
20050233794 | Cannon et al. | Oct 2005 | A1 |
20050261060 | Nguyen et al. | Nov 2005 | A1 |
20050261061 | Nguyen et al. | Nov 2005 | A1 |
20050282629 | Gagner | Dec 2005 | A1 |
20050282638 | Rowe | Dec 2005 | A1 |
20060009273 | Moshal | Jan 2006 | A2 |
20060019747 | Loose et al. | Jan 2006 | A1 |
20060019750 | Beatty | Jan 2006 | A1 |
20060025209 | Walker et al. | Feb 2006 | A1 |
20060030409 | Lechner et al. | Feb 2006 | A1 |
20060031829 | Harris et al. | Feb 2006 | A1 |
20060036573 | Watanabe et al. | Feb 2006 | A1 |
20060039132 | Chen | Feb 2006 | A1 |
20060040735 | Baerlocher | Feb 2006 | A1 |
20060068875 | Cregan et al. | Mar 2006 | A1 |
20060073887 | Nguyen et al. | Apr 2006 | A1 |
20060084486 | Belger et al. | Apr 2006 | A1 |
20060084502 | Downs, III et al. | Apr 2006 | A1 |
20060089194 | Joshi et al. | Apr 2006 | A1 |
20060094508 | D'Amico et al. | May 2006 | A1 |
20060111170 | Hornik et al. | May 2006 | A1 |
20060121972 | Walker et al. | Jun 2006 | A1 |
20060128460 | Muir et al. | Jun 2006 | A1 |
20060135255 | Roth | Jun 2006 | A1 |
20060160614 | Walker et al. | Jul 2006 | A1 |
20060172794 | Walker et al. | Aug 2006 | A1 |
20060194633 | Paulsen | Aug 2006 | A1 |
20060211479 | Walker et al. | Sep 2006 | A1 |
20060211480 | Walker et al. | Sep 2006 | A1 |
20060217170 | Roireau | Sep 2006 | A1 |
20060217171 | Roireau | Sep 2006 | A1 |
20060217172 | Roireau | Sep 2006 | A1 |
20060217176 | Walker et al. | Sep 2006 | A1 |
20060223613 | Walker et al. | Oct 2006 | A1 |
20060223636 | Walker et al. | Oct 2006 | A1 |
20060240887 | Walker et al. | Oct 2006 | A1 |
20060240889 | Walker et al. | Oct 2006 | A1 |
20060240892 | Walker et al. | Oct 2006 | A1 |
20060246983 | Huard et al. | Nov 2006 | A1 |
20060247012 | Walker et al. | Nov 2006 | A1 |
20060252523 | Walker et al. | Nov 2006 | A1 |
20060258446 | Nguyen et al. | Nov 2006 | A1 |
20060287107 | Okada | Dec 2006 | A1 |
20070004509 | Banton | Jan 2007 | A1 |
20070054741 | Morrow et al. | Mar 2007 | A1 |
20070060323 | Isaac et al. | Mar 2007 | A1 |
20070135215 | Walker et al. | Jun 2007 | A1 |
20070191090 | O'Halloran et al. | Aug 2007 | A1 |
20070232397 | Katz | Oct 2007 | A1 |
20080039175 | Tessmer et al. | Feb 2008 | A1 |
20080318656 | Walker et al. | Dec 2008 | A1 |
20090111574 | Rowe | Apr 2009 | A1 |
20090197659 | Christensen | Aug 2009 | A1 |
20090325670 | Kelly et al. | Dec 2009 | A1 |
20090325672 | Kelly | Dec 2009 | A1 |
Number | Date | Country |
---|---|---|
0 655 265 | May 1995 | EP |
0843272 | May 1998 | EP |
1004970 | May 2000 | EP |
1199690 | Feb 2004 | EP |
0813132 | Jan 2005 | EP |
1378873 | Mar 2005 | EP |
1238688 | May 2005 | EP |
1378874 | May 2005 | EP |
1471710 | May 2005 | EP |
1291048 | Jun 2005 | EP |
1 610 275 | Dec 2005 | EP |
WO 9727570 | Jul 1997 | WO |
WO 9835309 | Aug 1998 | WO |
WO 9856475 | Dec 1998 | WO |
WO 9910849 | Mar 1999 | WO |
WO 9941718 | Aug 1999 | WO |
WO 9965579 | Dec 1999 | WO |
WO 0025281 | May 2000 | WO |
WO 0032286 | Jun 2000 | WO |
WO 0161437 | Aug 2001 | WO |
WO 0222225 | Mar 2002 | WO |
WO 02099760 | Dec 2002 | WO |
WO 03028830 | Apr 2003 | WO |
WO 03041825 | May 2003 | WO |
WO 03045515 | Jun 2003 | WO |
WO 03045516 | Jun 2003 | WO |
WO 2004004855 | Jan 2004 | WO |
WO 2004103495 | Dec 2004 | WO |
WO 2005028056 | Mar 2005 | WO |
WO 2005029220 | Mar 2005 | WO |
WO 2005033825 | Apr 2005 | WO |
WO 2005033826 | Apr 2005 | WO |
WO 2005120672 | Dec 2005 | WO |
WO 2006027677 | Mar 2006 | WO |
WO 2006039067 | Apr 2006 | WO |
WO 2007103054 | Sep 2007 | WO |
Entry |
---|
Bally Live-Server Based Gaming brochure, written by Bally Gaming Systems, published in 2006. |
Bonusing Solutions without Limits brochure, written by Bally Gaming Systems, published in 2005. |
SB Products—The Next Big Innovation, printed from www.igt.com in Aug. 2006. |
Server Based: Other Possibilities Article; published by www.casinocenter.com in May 2006. |
Transferring Gaming brochure, written by Cyberview Technology, published in 2006. |
Number | Date | Country | |
---|---|---|---|
20110028205 A1 | Feb 2011 | US |