Embodiments of the inventive subject matter relate generally to wagering game systems and networks that, more particularly, control wagering games via a wireless, portable device.
Wagering game machines, such as slot machines, video poker machines and the like, have been a cornerstone of the gaming industry for several years. Generally, the popularity of such machines depends on the likelihood (or perceived likelihood) of winning money at the machine and the intrinsic entertainment value of the machine relative to other available gaming options. Where the available gaming options include a number of competing wagering game machines and the expectation of winning at each machine is roughly the same (or believed to be the same), players are likely to be attracted to the most entertaining and exciting machines. Shrewd operators consequently strive to employ the most entertaining and exciting machines, features, and enhancements available because such machines attract frequent play and hence increase profitability to the operator. Therefore, there is a continuing need for wagering game machine manufacturers to continuously develop new games and gaming enhancements that will attract frequent play.
Furthermore, to facilitate the use of wagering games, some wagering game manufacturers generate wagering game machines and applications that utilize a player account. Using a player account for wagering games is referred to generally as account based wagering (ABW) and tracking player via the accounts is generally referred to as player tracking. A player signs up for the player account, stores information in the account and keeps funds in an account for wagering. A player can login to a wagering game machine, which presents wagering games during a wagering game session. The wagering game machine can read from a player-tracking card that identifies the player, such as when a player swipes a magnetic strip of the card against a magnetic card reader. The magnetic card reader reads unique information about the player account via the card swipe and initiates a wagering game session using the unique information to access the player account from an account server. The wagering game machine conducts the wagering game session using the player account, such as to use funds for wagering, for storing rewards earned from playing wagering games, etc. Wagering game manufacturers, therefore, are continuously looking for innovative ways of tracking players and enhancing use of account based wagering.
Embodiments are illustrated in the Figures of the accompanying drawings in which:
This description of the embodiments is divided into six sections. The first section provides an introduction to embodiments. The second section describes example embodiments while the third section describes example operations performed by some embodiments. The fourth section describes additional example embodiments while the fifth section describes example operating environments. The sixth section presents general comments.
This section provides an introduction to some embodiments.
As stated previously, wagering game manufacturers are continuously looking for innovative ways of tracking players and enhancing use of account based wagering.
The wagering game machine 160 detects wireless signals from the fob 101 generated via user input, such as when the user 190 presses a button on the fob 101. When the user presses the button on the fob 101, for example, the fob 101 sends a wireless signal 110. In some embodiments, the fob 101 can authenticate a fingerprint of the user 190 before sending the wireless signal 110. The wireless signal 110 includes information about the fob 101 and use of the fob 101, such as a unique device identifier (“DID”) 104 assigned to the fob 101 or a motion identifier (“MID”) 106 that identifies a motion 114 performed by the user 190 (e.g., a “Z” motion made by the user 190 while pressing the button on the fob 101). The wireless signal 110 can also specify a button identifier (“BID”) 108 that identifies a specific activity associated with the button on the fob 101 (e.g., holding down of a right-hand side button on the fob 101). The motion 114 and the specific activity associated with the button can be configured according to user preference prior to using the fob 101 (e.g., see
The wagering game machine 160 receives the wireless signal 110 and verifies the identity assigned to the fob 101 (e.g., queries the wagering game server 150, which identifies that the DID 104 is assigned to the player account 171). The wagering game machine 160 can communicate with the account server 170 to access the player account 171. The wagering game machine 160 can further verify the meaning of the motion 114 and the button action according to user preference settings. For example, the wagering game machine 160 uses the MID 106 and BID 108 to determine that, according to user-preference settings of the player account 171, a “Z” motion in combination with an action of holding the right button on the fob 101 indicates an intention to “login” to the wagering game machine 160. Based on the verification of the meaning of the MID 106 and the BID 108, the wagering game machine 160 can then initiate a wagering game session for the player account 171. The wagering game machine 160 can also perform other security measures, such as asking for a password. The user 190 can use the fob 101 to control movement on a display of the wagering game machine 160, such as to enter numbers and letters of a password. The wagering game machine 160 and/or wagering game server 150 can then fund the wagering game session using funds stored in the player account 171 which can be used to gamble on gaming content (e.g., a primary game application 103 that includes reels 107, a credit meter 113, a bet meter 115, and a spin button 117). The wagering game machine 160 presents additional information 120 that indicates various gaming activities that can be performed via use of the fob 101, such as selecting secondary wagering game applications, modifying bet amounts, and spinning the reels 107. Thus, the fob 101 can be used as a game controller for the duration of the wagering game session to perform wagering game activities.
Further, some embodiments of the inventive subject matter describe examples of account-based-wagering mobile controllers in various venues accessible via a communication network, such as the communications network 122 in
Further, in some embodiments herein a user may be referred to as a player (i.e., of wagering games), and a player may be referred to interchangeably as a player account. Account-based-wagering systems utilize player accounts when transacting and performing activities, at the computer level, that are initiated by players. Therefore, a “player account” represents the player at a computerized level. The player account can perform actions via computerized instructions. For example, in some embodiments, a player account may be referred to as performing an action, controlling an item, communicating information, etc. Although a player, or person, may be activating a game control or device to perform the action, control the item, communicate the information, etc., the player account, at the computer level, can be associated with the player, and therefore any actions associated with the player can also be associated with the player account. Therefore, for brevity, to avoid having to describe the interconnection between player and player account in every instance, a “player account” may be referred to herein in either context. Further, in some embodiments herein, the word “gaming” is used interchangeably with “gambling.”
Although
This section describes some example embodiments.
In
In
This section describes operations associated with some embodiments. In the discussion below, some flow diagrams are described with reference to block diagrams presented herein. However, in some embodiments, the operations can be performed by logic not described in the block diagrams.
In certain embodiments, the operations can be performed by executing instructions residing on machine-readable storage media (e.g., software), while in other embodiments, the operations can be performed by hardware and/or other logic (e.g., firmware). In some embodiments, the operations can be performed in series, while in other embodiments, one or more of the operations can be performed in parallel. Moreover, some embodiments can perform more or less than all the operations shown in any flow diagram.
In some embodiments, the system detects the first wireless signal when the fob is within a specific distance range, or proximity, to a casino device. The system can activate use of the fob for a wagering game session simply by being within proximity to the casino device. In other example, however, the system can require security measures that verify the authenticity of the user to whom the fob has been assigned. For example, the system can require that the first wireless signal include an indication of a unique movement of the fob in relation to the casino device (e.g., the “Z” movement described in
In some embodiments, the system can also require a biometric identification of the player via the fob before initiating a wagering game session (e.g., scan the player's fingerprint, detect a scent signature of the player, scan the player's retina, scan a player's facial map, etc.).
In some embodiments, the system detects, from the first wireless signal, information that identifies a specific casino device. For example, if a player is near multiple wagering game machines, and the player wants to use a specific wagering game machine for a wagering game session, the player can point the fob at the specific wagering game machine. The fob detects an orientation of the front of the fob and its directionality in relation to the specific wagering game machine. The fob can include the orientation data in the first wireless signal. The system, using the orientation data, can select the specific wagering game machine and establish the communication interface between the specific wagering game machine and the fob. In some embodiments, the system can require the fob to touch the casino device to select the wagering game session.
In some embodiments, the system tracks a location of the fob and presents a message (e.g., via a display, via speakers, etc.) along with an invitation to perform an activity in a wagering game or other wagering-game related application of the casino device (as similarly described in
The flow 800 continues at processing block 804, where the system initiates a wagering game session for the player account in response to detecting the identifier. For instance, when the fob interfaces with the casino device, the system initiates a wagering game session on the casino device for the player account using account login information. For example, the fob can transfer encrypted data, such as the identifier. The casino device, such as a wagering game machine, can decrypt and use the encrypted data to initiate a login process for a player account, for instance, as described in
The flow 800 continues at processing block 806, where the system detects, via a second wireless signal, a use of the fob in response to player input, and performs an activity for a wagering game, presented during the wagering game session, based on the use of the fob as indicated via the second wireless signal. For instance, the use can be a specific type of movement or motion (e.g., a tossing motion, a shaking motion, etc.) of the fob in relation to the casino device. The use can also be a specific action associated with a button, a mouse, a pointer, or other user-input mechanism on the fob. In some embodiments, the activity indicates a placement of a wager amount for a wagering game. The system transacts the wager using funds from the player account. In some embodiments, the fob movement indicates a wager based on a type of movement (e.g., a throwing motion made while holding the fob indicates a tossing of a coin). In some embodiments, the activity performed in the wagering game involves movement of a game object, such as movement of reels, game elements, game characters, game icons, avatars, initials, etc. The activity can include interacting with groups of players (e.g., performing group tasks, competing at group games, etc.). In some embodiments, the system further generates an outcome in response to the use of the fob, such as generating a random number and using the random number to create a wagering game outcome (e.g., to create a reel-stop position). The system can further incorporate uses of the fob for games of skill.
In some embodiments, the system initiates a selection of a type of game that utilizes a type of the motion performed using the fob. For instance, the system can detect input via the fob for selecting a game title, type, or theme based on specific motions made with the fob that emulate a primary activity of the title, type or theme. For example if the system detects an overhead, tossing motion made using the fob, the system could evaluate and determine that the overhead, tossing motion is related to fishing games (i.e., the overhead tossing motion emulates a casting of a fishing line). The system could also evaluate and determine that the overhead, tossing motion is related to coin toss games (i.e., the overhead, tossing motion emulates a throwing motion of a coin). The system could also evaluate and determine that the overhead, tossing motion is related to specific sports games, such as football or baseball (i.e., the overhead, tossing motion emulates a type of throw typically performed in football or baseball). In another example, types or amounts, of motion of the fob can indicate different types or themes, such as movie themes, episodic game types, etc.
In some embodiments, the system initiates a transfer of funds from the player account to a wagering game session based on use of the fob, such as via specific motions, button presses, etc. For instance, the system can deposit and/or withdraw funds from a player account. In other embodiments, the system can access account settings or other account data, such as accessing player preferences, contact information, etc. in response to use of the fob.
The system can further generate and transmit a third wireless signal, addressed to, and receivable exclusively by, the fob. The third wireless signal, for example, can instruct the fob to request a verification from the user before performing an activity during the wagering game session (e.g., the system sends a signal to the fob to generate a light, sound, or vibration when a bet is made and request that a user press an additional button before the system transacts the bet). The system then, in response, receives a fourth wireless signal, from the fob, which authorizes the system to perform the activity.
Further, as mentioned previously, the system can provide controls via a user interface for a user to configure player preference associated with the fob prior to using the fob (e.g., preferences to indicate specific motions that indicate bet amounts, preferences to indicate a button usage rate, etc.).
The flow 800 continues at processing block 808, where the system generates an outcome in the wagering game in response to the activity and associates the outcome with the player account. For instance, in response to the activity (e.g., in response to a wager), the system can generate an outcome for a wagering game (e.g., a win or a loss). If the system generates a winning outcome, the system can store a reward for the win directly in the player account, such as by transferring funds to the player account, storing in the player account a persistent object that represents a game achievement, adding loyalty points to the player account, increasing social status points for the player account, storing a virtual asset in the player account, adding free spins to the player account, storing discounts for products or services available in a casino to the player account, and so forth.
The flow 800 continues at processing block 810, where the system transmits data, via a third wireless signal, for receipt by the fob, where the data indicates a feedback response to one or more of the activity and the outcome. For example, the system generates data that instructs the fob to generate one or more of lights, sounds and vibrations. The lights can be LEDs, for example, and a color of the LEDs can specify an activated or deactivated state of the fob. The LEDs can further indicate performance of the activity. The data can further instruct one or more speakers on the fob to generate sounds or instruct vibration devices to become active.
In some embodiments, the system can further transmit data for storage on the fob. For example, the system can store game activity, game history, etc. The fob stores the data, in some instances, for access after the wagering game session. For example, the system can store information about the game, such as a recording of an exciting game activity or outcome that was performed in the wagering game. The user can then carry the fob out of the casino, and connect the fob to a personal computer at home to replay the recording.
Further, in some embodiments, the system can terminate a wagering game session in response to use of the fob. For example, the system can terminate a wagering game session automatically in response to when a fob leaves a proximity range or in response to a specific combination of movement and button actions (e.g., a reverse “Z” motion combined with hold of a left button).
According to some embodiments, a wagering game system (“system”) can provide various example devices, operations, etc., to controlling wagering games via a mobile controller. The following non-exhaustive list enumerates some possible embodiments.
Use of a Mobile Controller without a Player Account.
In some embodiments, the system can utilize a fob, or similar type of mobile controller, during a wagering game session without connecting to a player account. For example, a player can insert a ticket or card that includes an identifier that represents the player temporarily during a wagering game session. The fob can provide the identifier, but does not necessarily have to be assigned to a player account. Instead, the identifier can be used to track game activity, wagers, and rewards, during the wagering game session. The ticket, card, or fob can transmit the identifier to the wagering game machine, and the wagering game machine can store information about the wagering game session, such as money transactions, until the session ends, and then write data to the ticket, card, fob, etc. The fob can be used wirelessly during the wagering game session to control actions for wagering games. Afterwards, a player can take the ticket, card, fob, etc., to a casino bank, or kiosk, and cash out, or attain other rewards.
This section describes example operating environments, systems, networks, etc. and presents structural aspects of some embodiments.
The wagering game system architecture 900 can also include a wagering game server 950 configured to control wagering game content, provide random numbers, and communicate wagering game information, account information, and other information to and from a wagering game machine 960. The wagering game server 950 can include a content controller 951 configured to manage and control content for presentation on the wagering game machine 960. For example, the content controller 951 can generate game results (e.g., win/loss values), including win amounts, for games played on the wagering game machine 960. The content controller 951 can communicate the game results to the wagering game machine 960. The content controller 951 can also generate random numbers and provide them to the wagering game machine 960 so that the wagering game machine 960 can generate game results. The wagering game server 950 can also include a content store 952 configured to contain content to present on the wagering game machine 960. The wagering game server 950 can also include an account manager 953 configured to control information related to player accounts. For example, the account manager 953 can communicate wager amounts, game results amounts (e.g., win amounts), bonus game amounts, etc., to the account server 970. The wagering game server 950 can also include a communication unit 954 configured to communicate information to the wagering game machine 960 and to communicate with other systems, devices and networks.
The wagering game system architecture 900 can also include a mobile controller 935 configured to control mobile communications, transmit and receive wireless signals associated with a wagering game player account and that describe player input. In some embodiments, the mobile controller 935 is a pocket-sized computing device. In some examples, the mobile controller 935 is a fob. In other examples the mobile controller 935 may be incorporated into, or be, a smartphone, a personal digital assistant, a mobile computer, a mobile internet device, a portable media player, a mobile phone, a pager, a personal navigation device, etc. In some embodiments, the mobile controller 935 may include radio frequency identification (RFID) components, near-field communication mechanisms, and other wireless communication elements.
The wagering game system architecture 900 can also include the wagering game machine 960 configured to present wagering games and receive and transmit information to controlling wagering games via the mobile controller 935. The wagering game machine 960 can include a content controller 961 configured to manage and control content and presentation of content on the wagering game machine 960. The wagering game machine 960 can also include a content store 962 configured to contain content to present on the wagering game machine 960. The wagering game machine 960 can also include a communication unit 963 configured to communicate with the mobile controller 935. The wagering game machine 960 can also include a mobile controller unit 964 configured to interpret data received from the mobile controller 935 to login users, control wagering game sessions, control wagering game activity, and so forth. The mobile controller unit 964 is further configured to generate instructions, notifications, and other information to transmit to via wireless signals to the mobile controller 935.
The wagering game system architecture 900 can also include a secondary content server 980 configured to provide content and control information for secondary games and other secondary content available on a wagering game network (e.g., secondary wagering game content, promotions content, advertising content, player tracking content, web content, etc.). The secondary content server 980 can provide “secondary” content, or content for “secondary” games presented on the wagering game machine 960. “Secondary” in some embodiments can refer to an application's importance or priority of the data. In some embodiments, “secondary” can refer to a distinction, or separation, from a primary application (e.g., separate application files, separate content, separate states, separate functions, separate processes, separate programming sources, separate processor threads, separate data, separate control, separate domains, etc.). Nevertheless, in some embodiments, secondary content and control can be passed between applications (e.g., via application protocol interfaces), thus becoming, or falling under the control of, primary content or primary applications, and vice versa. In some embodiments, the secondary content can be in one or more different formats, such as Adobe® Flash®, Microsoft® Silverlight™, Adobe® Air™, hyper-text markup language, etc. In some embodiments, the secondary content server 980 can provide and control content for community games, including networked games, social games, competitive games, or any other game that multiple players can participate in at the same time. In some embodiments, the secondary content server 980 can control and present an online website that hosts wagering games. The secondary content server 980 can also be configured to present multiple wagering game applications on the wagering game machine 960 via a wagering game website, or other gaming-type venue accessible via the Internet. The secondary content server 980 can host an online wagering website and/or a social networking website. The secondary content server 980 can include other devices, servers, mechanisms, etc., that provide functionality (e.g., controls, web pages, applications, etc.) that web users can use to connect to a social networking application and/or website and utilize social networking and website features (e.g., communications mechanisms, applications, etc.). In some embodiments, the secondary content server 980 can also host social networking accounts, provide social networking content, control social networking communications, store associated social contacts, etc. The secondary content server 980 can also provide chat functionality for a social networking website, a chat application, or any other social networking communications mechanism. In some embodiments, the secondary content server 980 can utilize player data to determine marketing promotions that may be of interest to a player account. The secondary content server 980 can also analyze player data and generate analytics for players, group players into demographics, integrate with third party marketing services and devices, etc. The secondary content server 980 can also provide player data to third parties that can use the player data for marketing. In some embodiments, the secondary content server 980 can provide one or more social networking communication mechanisms that publish (e.g., post, broadcast, etc.) a message to a mass (e.g., to multiple people, users, social contacts, accounts, etc.). The social networking communication mechanism can publish the message to the mass simultaneously. Examples of the published message may include, but not be limited to, a blog post, a mass message post, a news feed post, a profile status update, a mass chat feed, a mass text message broadcast, a video blog, a forum post, etc. Multiple users and/or accounts can access the published message and/or receive automated notifications of the published message.
Each component shown in the wagering game system architecture 900 is shown as a separate and distinct element connected via a communications network 922. However, some functions performed by one component could be performed by other components. For example, the wagering game server 950 can also be configured to perform functions of the communication unit 963, the mobile controller unit 964, and other network elements and/or system devices. Furthermore, the components shown may all be contained in one device, but some, or all, may be included in, or performed by, multiple devices, as in the configurations shown in
The wagering game machines described herein (e.g., wagering game machine 960) can take any suitable form, such as floor standing models, handheld mobile units, bar-top models, workstation-type console models, surface computing machines, etc. Further, wagering game machines can be primarily dedicated for use in conducting wagering games, or can include non-dedicated devices, such as mobile phones, personal digital assistants, personal computers, etc.
In some embodiments, wagering game machines and wagering game servers work together such that wagering game machines can be operated as thin, thick, or intermediate clients. For example, one or more elements of game play may be controlled by the wagering game machines (client) or the wagering game servers (server). Game play elements can include executable game code, lookup tables, configuration files, game outcome, audio or visual representations of the game, game assets or the like. In a thin-client example, the wagering game server can perform functions such as determining game outcome or managing assets, while the wagering game machines can present a graphical representation of such outcome or asset modification to the user (e.g., player). In a thick-client example, the wagering game machines can determine game outcomes and communicate the outcomes to the wagering game server for recording or managing a player's account.
In some embodiments, either the wagering game machines (client) or the wagering game server(s) can provide functionality that is not directly related to game play. For example, account transactions and account rules may be managed centrally (e.g., by the wagering game server(s)) or locally (e.g., by the wagering game machines). Other functionality not directly related to game play may include power management, presentation of advertising, software or firmware updates, system quality or security checks, etc.
Furthermore, the wagering game system architecture 900 can be implemented as software, hardware, any combination thereof, or other forms of embodiments not listed. For example, any of the network components (e.g., the wagering game machines, servers, etc.) can include hardware and machine-readable storage media including instructions for performing the operations described herein.
The memory unit 1030 may also include an I/O scheduling policy unit and I/O schedulers. The memory unit 1030 can store data and/or instructions, and may comprise any suitable memory, such as a dynamic random access memory (DRAM), for example. The computer system 1000 may also include one or more suitable integrated drive electronics (IDE) drive(s) 1008 and/or other suitable storage devices. A graphics controller 1004 controls the display of information on a display device 1006, according to some embodiments.
The ICH 1024 provides an interface to I/O devices or peripheral components for the computer system 1000. The ICH 1024 may comprise any suitable interface controller to provide for any suitable communication link to the processor unit 1002, memory unit 1030 and/or to any suitable device or component in communication with the ICH 1024. The ICH 1024 can provide suitable arbitration and buffering for each interface.
For one embodiment, the ICH 1024 provides an interface to the one or more IDE drives 1008, such as a hard disk drive (HDD) or compact disc read only memory (CD ROM) drive, or to suitable universal serial bus (USB) devices through one or more USB ports 1010. For one embodiment, the ICH 1024 also provides an interface to a keyboard 1012, selection device 1014 (e.g., a mouse, trackball, touchpad, etc.), CD-ROM drive 1018, and one or more suitable devices through one or more firewire ports 1016. For one embodiment, the ICH 1024 also provides a network interface 1020 through which the computer system 1000 can communicate with other computers and/or devices.
The computer system 1000 may also include a machine-readable storage medium that stores a set of instructions (e.g., software) embodying any one, or all, of the methodologies to control wagering games via a mobile controller. Furthermore, software can reside, completely or at least partially, within the memory unit 1030 and/or within the processor unit 1002. The computer system 1000 can also include a mobile controller unit 1037. The mobile controller unit 1037 can process communications, commands, or other information, to control wagering games via a mobile controller. Any component of the computer system 1000 can be implemented as hardware, firmware, and/or machine-readable storage media including instructions for performing the operations described herein.
The CPU 1126 is also connected to an input/output (“I/O”) bus 1122, which can include any suitable bus technologies, such as an AGTL+frontside bus and a PCI backside bus. The I/O bus 1122 is connected to a payout mechanism 1108, primary display 1110, secondary display 1112, value input device 1114, player input device 1116, information reader 1118, and storage unit 1130. The player input device 1116 can include the value input device 1114 to the extent the player input device 1116 is used to place wagers. The I/O bus 1122 is also connected to an external system interface 1124, which is connected to external systems (e.g., wagering game networks). The external system interface 1124 can include logic for exchanging information over wired and wireless networks (e.g., 802.11g transceiver, Bluetooth transceiver, Ethernet transceiver, etc.)
The I/O bus 1122 is also connected to a location unit 1138. The location unit 1138 can create player information that indicates the wagering game machine's location/movements in a casino. In some embodiments, the location unit 1138 includes a global positioning system (GPS) receiver that can determine the wagering game machine's location using GPS satellites. In other embodiments, the location unit 1138 can include a radio frequency identification (RFID) tag that can determine the wagering game machine's location using RFID readers positioned throughout a casino. Some embodiments can use GPS receiver and RFID tags in combination, while other embodiments can use other suitable methods for determining the wagering game machine's location. Although not shown in
In some embodiments, the wagering game machine 1106 can include additional peripheral devices and/or more than one of each component shown in
In some embodiments, the wagering game machine 1106 includes a mobile controller unit 1137. The mobile controller unit 1137 can process communications, commands, or other information, where the processing can control wagering games via a mobile controller.
Furthermore, any component of the wagering game machine 1106 can include hardware, firmware, and/or machine-readable storage media including instructions for performing the operations described herein.
The wagering game machine 1200 comprises a housing 1212 and includes input devices, including value input devices 1218 and a player input device 1224. For output, the wagering game machine 1200 includes a primary display 1214 for displaying information about a basic wagering game. The primary display 1214 can also display information about a bonus wagering game and a progressive wagering game. The wagering game machine 1200 also includes a secondary display 1216 for displaying wagering game events, wagering game outcomes, and/or signage information. While some components of the wagering game machine 1200 are described herein, numerous other elements can exist and can be used in any number or combination to create varying forms of the wagering game machine 1200.
The value input devices 1218 can take any suitable form and can be located on the front of the housing 1212. The value input devices 1218 can receive currency and/or credits inserted by a player. The value input devices 1218 can include coin acceptors for receiving coin currency and bill acceptors for receiving paper currency. Furthermore, the value input devices 1218 can include ticket readers or barcode scanners for reading information stored on vouchers, cards, or other tangible portable storage devices. The vouchers or cards can authorize access to central accounts, which can transfer money to the wagering game machine 1200.
The player input device 1224 comprises a plurality of push buttons on a button panel 1226 for operating the wagering game machine 1200. In addition, or alternatively, the player input device 1224 can comprise a touch screen 1228 mounted over the primary display 1214 and/or secondary display 1216.
The various components of the wagering game machine 1200 can be connected directly to, or contained within, the housing 1212. Alternatively, some of the wagering game machine's components can be located outside of the housing 1212, while being communicatively coupled with the wagering game machine 1200 using any suitable wired or wireless communication technology.
The operation of the basic wagering game can be displayed to the player on the primary display 1214. The primary display 1214 can also display a bonus game associated with the basic wagering game. The primary display 1214 can include a cathode ray tube (CRT), a high resolution liquid crystal display (LCD), a plasma display, light emitting diodes (LEDs), a three-dimensional (3D) display, or any other type of display suitable for use in the wagering game machine 1200. Alternatively, the primary display 1214 can include a number of mechanical reels to display the outcome. In
A player begins playing a basic wagering game by making a wager via the value input device 1218. The player can initiate play by using the player input device's buttons or touch screen 1228. The basic game can include arranging a plurality of symbols 1232 along a pay line, which indicates one or more outcomes of the basic game. Such outcomes can be randomly selected in response to player input. At least one of the outcomes, which can include any variation or combination of symbols, can trigger a bonus game.
In some embodiments, the wagering game machine 1200 can also include an information reader 1252, which can include a card reader, ticket reader, bar code scanner, RFID transceiver, or computer readable storage medium interface. In some embodiments, the information reader 1252 can be used to award complimentary services, restore game assets, track player habits, etc.
Embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments of the inventive subject matter may take the form of a computer program product embodied in any tangible medium of expression having computer readable program code embodied in the medium. The described embodiments may be provided as a computer program product that may include a machine-readable storage medium having stored thereon instructions, which may be used to program a computer system to perform a process according to embodiments(s), whether presently described or not, because every conceivable variation is not enumerated herein. A machine-readable storage medium includes any mechanism that stores information in a form readable by a machine (e.g., a wagering game machine, computer, etc.). For example, machine-readable storage media includes read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media (e.g., CD-ROM), flash memory machines, erasable programmable memory (e.g., EPROM and EEPROM); etc. Some embodiments of the invention can also include machine-readable signal media, such as any media suitable for transmitting software over a network.
This detailed description refers to specific examples in the drawings and illustrations. These examples are described in sufficient detail to enable those skilled in the art to practice the inventive subject matter. These examples also serve to illustrate how the inventive subject matter can be applied to various purposes or embodiments. Other embodiments are included within the inventive subject matter, as logical, mechanical, electrical, and other changes can be made to the example embodiments described herein. Features of various embodiments described herein, however essential to the example embodiments in which they are incorporated, do not limit the inventive subject matter as a whole, and any reference to the invention, its elements, operation, and application are not limiting as a whole, but serve only to define these example embodiments. This detailed description does not, therefore, limit embodiments, which are defined only by the appended claims. Each of the embodiments described herein are contemplated as falling within the inventive subject matter, which is set forth in the following claims.
This application claims the priority benefit of U.S. Provisional Patent Application No. 61/531,477 filed on Sep. 6, 2011. A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. Copyright 2012, WMS Gaming, Inc.
Number | Name | Date | Kind |
---|---|---|---|
4926327 | Sidley | May 1990 | A |
4937853 | Brule et al. | Jun 1990 | A |
5007649 | Richardson | Apr 1991 | A |
5038022 | Lucero | Aug 1991 | A |
5042809 | Richardson | Aug 1991 | A |
5083271 | Thacher et al. | Jan 1992 | A |
5096195 | Gimmon | Mar 1992 | A |
5119295 | Kapur | Jun 1992 | A |
5135224 | Yamamoto et al. | Aug 1992 | A |
5159549 | Hallman, Jr. et al. | Oct 1992 | A |
5179517 | Sarbin et al. | Jan 1993 | A |
5192854 | Counts | Mar 1993 | A |
5197094 | Tillery et al. | Mar 1993 | A |
5223698 | Kapur | Jun 1993 | A |
5265874 | Dickinson et al. | Nov 1993 | A |
5277424 | Wilms | Jan 1994 | A |
5290033 | Bittner et al. | Mar 1994 | A |
5297802 | Pocock et al. | Mar 1994 | A |
5317135 | Finocchio | May 1994 | A |
5321241 | Craine | Jun 1994 | A |
5324035 | Morris et al. | Jun 1994 | A |
5326104 | Pease et al. | Jul 1994 | A |
5332076 | Ziegert | Jul 1994 | A |
5348299 | Clapper, Jr. | Sep 1994 | A |
5371345 | LeStrange et al. | Dec 1994 | A |
5373440 | Cohen et al. | Dec 1994 | A |
5408417 | Wilder | Apr 1995 | A |
5429361 | Raven et al. | Jul 1995 | A |
5440108 | Tran et al. | Aug 1995 | A |
5457306 | Lucero | Oct 1995 | A |
5470079 | LeStrange et al. | Nov 1995 | A |
5475205 | Behm et al. | Dec 1995 | A |
5491326 | Marceau et al. | Feb 1996 | A |
5507491 | Gatto et al. | Apr 1996 | A |
5536008 | Clapper, Jr. | Jul 1996 | A |
5551692 | Pettit et al. | Sep 1996 | A |
5559312 | Lucero | Sep 1996 | A |
5575374 | Orus et al. | Nov 1996 | A |
5580310 | Orus et al. | Dec 1996 | A |
5580311 | Haste, III | Dec 1996 | A |
5609337 | Clapper, Jr. | Mar 1997 | A |
5613680 | Groves et al. | Mar 1997 | A |
5613912 | Slater | Mar 1997 | A |
5627356 | Takemoto et al. | May 1997 | A |
5645485 | Clapper, Jr. | Jul 1997 | A |
5655961 | Acres et al. | Aug 1997 | A |
5655966 | Werdin, Jr. et al. | Aug 1997 | A |
5674128 | Holch et al. | Oct 1997 | A |
5697482 | Orus et al. | Dec 1997 | A |
5722890 | Libby et al. | Mar 1998 | A |
5735432 | Stoken et al. | Apr 1998 | A |
5737418 | Saffari et al. | Apr 1998 | A |
5749784 | Clapper, Jr. | May 1998 | A |
5755621 | Marks et al. | May 1998 | A |
5762552 | Vuong et al. | Jun 1998 | A |
5770533 | Franchi | Jun 1998 | A |
5797794 | Angell | Aug 1998 | A |
5800269 | Holch et al. | Sep 1998 | A |
5810664 | Clapper, Jr. | Sep 1998 | A |
5811772 | Lucero | Sep 1998 | A |
5816918 | Kelly et al. | Oct 1998 | A |
5830068 | Brenner et al. | Nov 1998 | A |
5839956 | Takemoto | Nov 1998 | A |
5869826 | Eleftheriou | Feb 1999 | A |
5902983 | Crevelt et al. | May 1999 | A |
5917725 | Thacher et al. | Jun 1999 | A |
5919091 | Bell et al. | Jul 1999 | A |
5928082 | Clapper, Jr. | Jul 1999 | A |
5949042 | Dietz, II et al. | Sep 1999 | A |
5952640 | Lucero | Sep 1999 | A |
5959277 | Lucero | Sep 1999 | A |
5984779 | Bridgeman et al. | Nov 1999 | A |
6012832 | Saunders et al. | Jan 2000 | A |
6048269 | Burns et al. | Apr 2000 | A |
6050487 | Bonifas et al. | Apr 2000 | A |
6089982 | Holch et al. | Jul 2000 | A |
6280326 | Saunders | Aug 2001 | B1 |
6280328 | Holch et al. | Aug 2001 | B1 |
6340331 | Saunders et al. | Jan 2002 | B1 |
6471590 | Saunders | Oct 2002 | B2 |
6511377 | Weiss | Jan 2003 | B1 |
6547664 | Saunders | Apr 2003 | B2 |
6577733 | Charrin | Jun 2003 | B1 |
6579182 | Orus et al. | Jun 2003 | B1 |
6585598 | Nguyen et al. | Jul 2003 | B2 |
6601771 | Charrin | Aug 2003 | B2 |
6607441 | Acres | Aug 2003 | B1 |
6623357 | Chowdhury | Sep 2003 | B2 |
6645075 | Gatto et al. | Nov 2003 | B1 |
6652380 | Luciano | Nov 2003 | B1 |
6729957 | Burns et al. | May 2004 | B2 |
6729958 | Burns et al. | May 2004 | B2 |
6735487 | Marshall et al. | May 2004 | B1 |
6736725 | Burns et al. | May 2004 | B2 |
6739975 | Nguyen et al. | May 2004 | B2 |
6746330 | Cannon | Jun 2004 | B2 |
6752312 | Chamberlain et al. | Jun 2004 | B1 |
6851607 | Orus et al. | Feb 2005 | B2 |
6890258 | Weiss | May 2005 | B2 |
6896616 | Weiss | May 2005 | B2 |
6896619 | Baltz et al. | May 2005 | B2 |
6905411 | Nguyen et al. | Jun 2005 | B2 |
6908391 | Gatto et al. | Jun 2005 | B2 |
6916244 | Gatto et al. | Jul 2005 | B2 |
6916247 | Gatto et al. | Jul 2005 | B2 |
6935953 | Marcu | Aug 2005 | B2 |
6945870 | Gatto et al. | Sep 2005 | B2 |
6969320 | Lind et al. | Nov 2005 | B2 |
6997807 | Weiss | Feb 2006 | B2 |
7004837 | Crowder, Jr. et al. | Feb 2006 | B1 |
7033274 | Orus et al. | Apr 2006 | B1 |
7036012 | Charrin | Apr 2006 | B2 |
7080782 | Charrin | Jul 2006 | B2 |
7147558 | Giobbi | Dec 2006 | B2 |
7152783 | Charrin | Dec 2006 | B2 |
7217190 | Weiss | May 2007 | B2 |
7467404 | McAllister et al. | Dec 2008 | B2 |
7783381 | Walker et al. | Aug 2010 | B2 |
7846020 | Walker et al. | Dec 2010 | B2 |
7850518 | Walker et al. | Dec 2010 | B2 |
8007361 | Walker et al. | Aug 2011 | B2 |
8021231 | Walker et al. | Sep 2011 | B2 |
8113935 | Walker et al. | Feb 2012 | B2 |
8142280 | Walker et al. | Mar 2012 | B2 |
8197324 | Walker et al. | Jun 2012 | B2 |
8231455 | Walker et al. | Jul 2012 | B2 |
20050109841 | Ryan et al. | May 2005 | A1 |
20080207307 | Cunningham, III et al. | Aug 2008 | A1 |
20080274798 | Walker et al. | Nov 2008 | A1 |
20080305862 | Walker et al. | Dec 2008 | A1 |
20090098936 | Lawrence et al. | Apr 2009 | A1 |
20090124376 | Kelly et al. | May 2009 | A1 |
20090176565 | Kelly | Jul 2009 | A1 |
20090176566 | Kelly | Jul 2009 | A1 |
20090239667 | Rowe et al. | Sep 2009 | A1 |
20100069138 | Acres | Mar 2010 | A1 |
20100148442 | Walker et al. | Jun 2010 | A1 |
20100252997 | Walker et al. | Oct 2010 | A1 |
20110014963 | Walker et al. | Jan 2011 | A1 |
20120115616 | Phillips et al. | May 2012 | A1 |
20120172114 | Walker et al. | Jul 2012 | A1 |
Number | Date | Country |
---|---|---|
1139310 | Oct 2001 | EP |
WO-0221377 | Mar 2002 | WO |
WO-2005033911 | Apr 2005 | WO |
WO-2006017268 | Feb 2006 | WO |
WO-2006036906 | Apr 2006 | WO |
WO-2007059418 | May 2007 | WO |
WO-2007067213 | Jun 2007 | WO |
WO-2007107883 | Sep 2007 | WO |
WO-2007134109 | Nov 2007 | WO |
WO-2008013541 | Jan 2008 | WO |
WO-2008018874 | Feb 2008 | WO |
WO-2008027801 | Mar 2008 | WO |
WO-2008039174 | Apr 2008 | WO |
WO-2008039175 | Apr 2008 | WO |
WO-2008101204 | Aug 2008 | WO |
WO-2008106270 | Sep 2008 | WO |
WO-2008154048 | Dec 2008 | WO |
WO-2008154588 | Dec 2008 | WO |
WO-2009025673 | Feb 2009 | WO |
WO-2009032007 | Mar 2009 | WO |
WO-2009064813 | May 2009 | WO |
WO-2011156401 | Dec 2011 | WO |
Number | Date | Country | |
---|---|---|---|
20130252714 A1 | Sep 2013 | US |
Number | Date | Country | |
---|---|---|---|
61531477 | Sep 2011 | US |