This application is a continuation of U.S. application Ser. No. 12/617,717, filed Nov. 12, 2009, and entitled “GAMING SYSTEMS INCLUDING VIRAL GAMING EVENTS,” which is hereby incorporated herein by reference.
The present invention relates to games and game features, and particularly to wagering game events.
Early gaming machines presented a single wagering game. For example, early slot machines presented a single game in which a set of reels were spun and the stopping positions of the reels define the outcome of the game. Later, video gaming machines were developed. These gaming machines were configured to present slot games in a video format, as well as other games such as video poker.
In order to increase the excitement associated with these games, various secondary game events have been developed. For example, gaming machines have been outfitted with rotating wheels. When a player receives a particular winning result of a base game, such as a particular slot reel outcome, the wheel may spin and stop on a segment which defines a bonus award. Similarly, video gaming machines have been configured to present various video secondary events. These events may comprise a variety of animated sequences which provide entertainment and the potential for awards.
Also, as gaming machines have been linked to gaming systems, awards have been developed which increase the number of participating players. For example, gaming machines may be linked to a jackpot system. If a player of one of the gaming machines of the system obtains a particular winning outcome, they may be awarded the jackpot. In order to increase the level of excitement of such a system, the players of other gaming machines at which the jackpot was not won may be awarded a consolation prize.
Still, these secondary events or awards have limitations, and new and exciting gaming events remain desirable.
The invention is associated with distribution of viral events, such as viral gaming events, amongst devices. The devices can present the viral events. The devices can, for example, be gaming machines and/or mobile devices.
In accordance with one aspect of the invention, a viral gaming event is triggered and is first presented at one or more first gaming machines at a time T1. The viral gaming event then spreads to one or more second gaming machines at a time T2 which is later than the time T1. The viral gaming event may comprise a gaming event such as a bonus event, or a non-gaming event such as a promotional message from the casino or an alert. The viral gaming event may be the same or different at each gaming machine. The viral gaming event may comprise a single player event (i.e. played by the player of the particular machine) or be a group event (wherein multiple players participate in the event).
The viral gaming event may be triggered in various fashions, such as a result of game play at a particular gaming machine, results or actions at multiple gaming machines, a result of a casino-operator action, or randomly. The viral gaming event might be initiated at a single gaming machine or multiple gaming machines. The viral gaming event may spread to multiple gaming machines, including not only one or more second gaming machines but one or more third, fourth, etc. gaming machines.
The viral gaming event preferably ceases to spread and has an end. The end may be defined by the award of a predetermined amount of bonus awards, the expiration of a time period, infection of a certain number of gaming machines or the like.
The viral gaming event may have various propagation patterns including direction of spread and rate of spread. The viral gaming event may spread in certain directions, may be spread to achieve desired game play goals, may spread randomly, and may spread based upon player qualification criteria or the like. The characteristics of the viral gaming event may be varied. For example, game play metrics obtained from a player tracking system or one or more cameras may be used to determine the particular gaming machines which are infected, the rate of spread or the like. Feedback may be provided during the viral gaming event to modify the characteristics of the event after it is triggered.
Information may be provided to players and potential players regarding infection of gaming machines with the viral gaming event and the spread thereof. Such alerts may comprise visual, audible or other alerts at infected gaming machines. Visual, audio or other information may also be provided regarding the direction of viral event propagation, such as digital signage or light pipes and ropes which illuminate to define paths of spread of the viral gaming event.
In one embodiment the viral gaming event may be implemented by gaming machines in a peer-to-peer networking environment. In another embodiment, a gaming system includes a plurality of gaming machines and at least one viral event server in communication with those gaming machines. The viral event server is preferably configured to spread the viral event to the gaming machines.
In another embodiment, a system for distributing a viral benefit to a mobile device can include at least: a first plurality of mobile devices, each of the first plurality of mobile devices having a display to display a first viral benefit; a second plurality of mobile devices, each of the second plurality of mobile devices having a display to display a second viral benefit; and a viral event server. The viral server can, for example be configured to: determine whether to initiate a viral event; determine a type of first viral benefit to distribute to one or more of the first plurality of mobile devices if it is determined that the viral event is initiated; distribute the first viral benefit to one or more of the first plurality of mobile devices; determine whether to distribute the second viral benefit to one or more of the second plurality of mobile devices; and transmit the second viral benefit to the one or more of the second plurality of mobile devices if it is determined that the second viral benefit to one or more of the second plurality of mobile devices is to be distributed.
In another embodiment, a method for distributing a viral benefit to a mobile device can include at least: determining, at a server, whether to initiate a viral event; determining, at the server, a first viral benefit to distribute to one or more of a first plurality of mobile devices if it is determined that the viral event is initiated; distributing the viral benefit to one or more of the first plurality of mobile devices; determining whether to distribute a second viral benefit to one or more of a second plurality of mobile devices; and transmitting the second viral benefit to the one or more of the second plurality of mobile devices if it is determined that the second viral benefit to one or more of the second plurality of mobile devices is to be distributed.
In still another embodiment, a program storage device readable by a machine tangibly embodying a program of instructions executable by the machine can perform a method for distributing a viral benefit to a mobile device. The method can, for example, include at least: determining, at a server, whether to initiate a viral event; determining, at the server, a first viral benefit to distribute to one or more of a first plurality of mobile devices if it is determined that the viral event is initiated; distributing the viral benefit to one or more of the first plurality of mobile devices; determining whether to distribute a second viral benefit to one or more of a second plurality of mobile devices; and transmitting the second viral benefit to the one or more of the second plurality of mobile devices if it is determined that the second viral benefit to one or more of the second plurality of mobile devices is to be distributed. The transmitting of the second viral benefit to the one or more second mobile devices can be triggered by an event at one or more of the first plurality of mobile devices.
Further objects, features, and advantages of the present invention over the prior art will become apparent from the detailed description which follows, when considered with the figures provided herein.
In the following description, numerous specific details are set forth in order to provide a more thorough description of the present invention. It will be apparent, however, to one skilled in the art, that the present invention may be practiced without these specific details. In other instances, well-known features have not been described in detail so as not to obscure the invention.
In general, the invention comprises viral game events, methods of game play (“games”) including such events, and gaming machines and systems configured to present such events or features. A viral gaming event of the invention comprises a gaming event, such as a bonus or secondary event, which spreads from one or more first gaming machines to one or more additional gaming machines.
Content associated with a viral game event could be a game feature such as a bonus, a game symbol, a message from the server, a promotional message from the casino, an informational alert, and the like. The viral game event could be implemented as a software module. The software module monitors game events, gathers data, views files, processes logic, displays animation, etc., at the gaming devices. In one implementation, the viral game software is a self-contained distributed software application that's constructed with popular programming and languages such as C, C++, Java, C#, Perl, Javascript, Python, etc. The software module is transferred to a gaming device for execution. In another implementation, the viral game event is built as a web service to be executed at a remote server.
In one embodiment, the gaming machine 100 defines a generally enclosed interior space for housing one or more components. As illustrated, the gaming machine 100 generally comprises a housing or cabinet 102 for supporting and/or enclosing various components required for operation of the gaming machine. In the embodiment illustrated, the housing 102 includes a door located at a front thereof, the door capable of being moved between an open position which allows access to the interior, and a closed position in which access to the interior is generally prevented. The configuration of the gaming machine 100 may vary. In the embodiment illustrated, the gaming machine 100 has an “upright” configuration. However, the gaming machine 100 could have other configurations, shapes or dimensions (such as being of a “slant”-type, “bar-top” or other configuration as is well known to those of skill in the art).
The gaming machine 100 preferably includes at least one display device 104 configured to display game information. The display device 104 may be a mechanical, electro-mechanical or electronic display, such as one or more rotating reels, a video display or the like. When the display device 104 is an electronic video display, it may comprise a cathode ray tube (CRT), high resolution flat panel liquid crystal display (LCD), projection LCD, plasma display, field emission display, digital micro-mirror display (DMD), digital light processing display (DLP), multilayer LCD display, an E-ink display, a light emitting display (LED, OLED) or other suitable displays now known or later developed, in a variety of resolutions, sizes and formats (e.g. 4:3, widescreen or the like). The display 104 may be capable of projecting or displaying a wide variety of information, including images, symbols and other indicia or information associated with game play, game promotion or other events. The gaming machine 100 may include two or more display devices. For example, a secondary display device might be associated with the housing or cabinet 102 along with the main display device 104, or might be associated with a top box or the like, as illustrated in
The gaming machine 100 may be configured to present a wide variety of games. Such games might be Class III type games such as slot games and video poker games, or Class II type games such as bingo, pull-tab games, lotto or instant lottery style games. In one embodiment, certain game outcomes may be designated as winning outcomes. Prizes or awards may be provided for winning outcomes, such as monetary payments (or representations thereof, such as prize of credits), or the like. As detailed below, one or more of the awards may have certain characteristics or features.
The gaming machine 100 also preferably includes one or more player input devices 108 (such as input buttons, plunger mechanisms, a touch-screen display, joystick, touch-pad or the like) that may be utilized by the player to facilitate game play. Also included in the player input devices 108 is a means for accepting monetary value. As illustrated in
In one preferred embodiment, the gaming machine 100 includes a microprocessor or controller (not shown) for controlling the gaming machine, including receiving player input and sending output signals for controlling the various components of the machine 100 (such as generating game information for display by the display 104). The controller may be arranged to receive input such as a purchase/bet signal when a purchase/bet button is depressed, and a currency insert signal when a player inserts bills or coins. The controller may be arranged to send signals for determining winning combinations, for causing the coin hopper/dispenser, or printer, or an electronic fund transfer (EFT), to pay winnings, and to cause the display to display winning amount information. In addition, the controller is preferably arranged to determine if a round of game play has resulted in a win, and if so, the prize to be awarded to the player for that win.
The controller may be configured to execute machine readable code or “software” or otherwise process information, such as obtained from a remote server. Software or other instructions may be stored on a memory or data storage device. The memory may also store other information, such as pay table information. The gaming machine 100 may also include one or more random number generators for generating random numbers for generating random game outcomes, or such might be located remotely. For example, if the gaming machine 100 is a stand-alone machine configured to present a slot game or a video poker game, the random number generator(s) might be located at the machine. However, if the gaming machine 100 is used to present server-based or networked games, such as bingo games, the random number generator(s) might be located at the server.
In operation, the player may initiate game play by providing value, such as a wager. The wager may be made by activating one of the player input devices 108 such as a one credit button 116 which places a single credit purchase or wager or a max credit button 118 which places a maximum purchase or wager for that round of game play. The maximum purchase or wager is commonly defined as playing or betting an amount comprising a multiple of the value of a single purchase or wager up to a predefined upper purchase or bet limit or threshold. When the player actuates either the one credit button 116 or the max credit button 118, a wager is placed or purchase is made in that amount and the player's credit base is decreased by the number of credits wagered. The player's remaining credit base is typically displayed to the player by way of the display device 104. Upon making a purchase or placing a wager, the game may begin automatically or the player may join a game already in progress, or the player may initiate the game by activating another player input device, upon which the gaming machine 100 presents one or more game elements which are used to determine if the player has received a winning combination.
The gaming machine 100 generally includes a means for awarding a player a prize or winnings accumulated during game play. When a player obtains a winning outcome, the player is preferably paid prizes or awards in the form of stored credits, the amount of which is indicated to the player on the display 104. A “cash out” button may be provided for permitting a player to be paid the winnings or redeeming any credits initially paid into the gaming machine 100. The term “cash out” is used herein to define an event initiated by the player wherein the player receives a number of coins or currency that is equivalent to the value of the player's accrued credit base.
Typically when a player cashes out, the gaming machine 100 is configured to dispense a media or voucher, such as via a printer 114, which represents the cash-out value. The player may utilize this voucher at other gaming machine or convert the voucher to currency, such as at a cashier's station. However, depending upon the configuration of the gaming machine 100, the player might receive a cash or coin disbursement. For example, the gaming machine 100 might be configured to activate a coin hopper or coin handling device (not shown) which physically counts and delivers the proper number of coins to the player. The coin handling device is commonly configured to transport coins from a supply source (hopper or bin filled with coins) to a coin tray 124 or payout receptacle where the player physically receives the coins.
As indicated above, the gaming machine 100 may be configured as a stand-alone device, such as when the machine is configured to present a slot game or a video poker game. As detailed below, however, the gaming machine 100 may be a server-based or networked machine. For example, the gaming machine 100 may be configured to obtain game code or game outcome information from a remote server 130. The gaming machine 100 may also communicate with a remote accounting server and/or player tracking server, as is well known in the art.
It will be appreciated that the gaming machine and system described and illustrated in
One aspect of the invention is a viral gaming event or feature. Such an event may be presented at a gaming machine or device 100 such as described above.
The viral gaming event of the invention has two primary components: a viral gaming event trigger and viral gaming event spread or transmission. The viral gaming event is initiated by a trigger. The trigger may be random and/or be a particular event. For example, the trigger may be generated randomly at a server or a gaming machine. Alternatively, the trigger might occur when a particular game result occurs. Such an outcome might be the appearance of a particular symbol or a group of symbols, one or more winning game outcomes, certain non-winning outcomes, or various other events at a gaming machine or groups of gaming machines. Other events might comprise a certain number of credits wagered or a certain number of games played at a gaming machine or across a gaming system, or a group of symbols or outcomes received at a bank, or a jackpot received at one or more gaming machines, or a predefined time, place, or machine designated by the casino manager, for example.
Upon the trigger, the viral gaming event is initiated at one or more first gaming machines. Initiation of the event at a gaming machine is akin to “infection” of the machine with the viral gaming event. In one embodiment in which the trigger is a particular event at a gaming machine, the viral gaming event is initiated at that gaming machine. However, the event might be initiated at more than one gaming machine, such as gaming machines spread across the floor of a casino, the gaming machines of a bank of gaming machines or the like. Another salient characteristic is that the viral gaming event can “hop” to other qualified games or machines even before the event is consummated at the “infected” game or machine. Like a biological flu, this viral propagation during the incubation period speeds up the propagation and create more excitement for the players because of the multiple potential payouts that overlap and sequentially occurring all around the players. Even when multiple games are being played simultaneously at one gaming machine, the concurrent games can be susceptible to “infection” if they meet the criteria.
The viral gaming event may be coupled with or comprise content related to any number of events. For example, the viral gaming event might comprise a game, a bonus event, a secondary game or the like. Other contents such as a notification of a 3rd-party sponsored prize, a bonus alert, a promotional message, an advertisement, a group message, music, video, and the like can also be coupled with a viral gaming event. The viral gaming event might be the same for each gaming machine regardless of the type or manufacturer of the gaming machine. For example, the viral gaming event might comprise a particular animated bonus event, regardless of whether the gaming machine is a spinning reel slot machine or video poker machine. In other embodiment, the viral gaming event might vary depending upon the gaming machine, the game being played, the player, time, and/or other parameters. For example, the viral gaming event might comprise a bonus opportunity for a 1000 credit payout. At a video poker machine the viral gaming event might be presented as a poker game having the opportunity for a 1000 credit payout if a particular win is achieved, while at a slot machine the viral gaming event might be presented as a spin of the reels with the opportunity for a 1000 credit payout if a particular symbol or combination of symbols is achieved. The configuration of a game on a gaming machine can also cause a variation of viral gaming event. For example, a viral gaming event may present an opportunity for a player of a gaming machine to win a $10,000 progressive jackpot (a traveling progressive) at a $5-denominated slot game, and may present a $1,000jackpot at a $0.25 denominated game. Such a traveling progressive jackpot offers a player of the infected gaming machine a limited time (the infection period) to win a portion of its funds, scaled up or down proportionately with the amount that a player bets.
The viral gaming event might comprise a single player/machine event or it might comprise a group play type event. In a group play implementation, a community bonus event could cause multiple viral bonus events to be subsequently generated at nearby slot machines associated with the group game. For example, when a community bonus wheel is spinning in a group game, it could generate a viral bonus event that “infects” nearby associated gaming machines and cause them to have bonus spins at a later time. The viral gaming event continues to hop or spread to other qualified games until a termination event occurs. Also, the viral gaming event might result in an award, such as a bonus award, or it might have one or more outcomes that do not result in any additional award. The value of the awards that may be won at a particular machine may be based upon the size of player's wager, a side wager, a random event, or the like.
The viral gaming event may be presented via the main display of a gaming machine, via a secondary display or by one or more displays or devices common to one or more gaming machines. The viral gaming event might require one or more player inputs. The viral gaming event might be presented without a requirement for a further wager or might require a player to place a wager or an additional wager. In one embodiment, a player may be required to place a side wager in order to be eligible for the viral gaming event to spread to their machine.
In accordance with the invention, the viral gaming event preferably spreads from one or more first gaming machines to one or more other gaming machines over time. In particular, after the viral gaming event is initiated at the one or more first gaming machines at a first time T1, it spreads to and is initiated at one or more additional gaming machines at a time T2. The time delay between when the viral gaming event is initiated at the one or more first gaming machines and the one or more additional gaming machines may vary. For example, the time delay could be very short (seconds) or long (minutes, hours, etc.).
In addition, the viral gaming event may spread beyond one or more second gaming machines to other gaming machines. As one example, the total number of gaming machines “infected” over time may be bell curved (i.e. one or more gaming machines at time T1, increasing to a higher number of gaming machines at a time T2 and then decreasing to a fewer number of machines at a time T3). The number of gaming machines which are infected may also be random or have various other patterns, such as increasing linearly, geometrically, or exponentially over time until an end time.
It will also be appreciated that the rate of spread of the viral gaming event may vary. For example, the viral gaming event may spread from one or more first gaming machines at a time T1 to one or more second gaming machines in a time T2, and from the one or more second gaming machines to one or third gaming machines in a time T3, where the time intervals between T2/T1 and T3/T2 differ.
In one embodiment, the viral gaming event preferably ends or stops spreading at some point in time. When the viral gaming event ends, it preferably no longer spreads to additional gaming machines. The spread of the viral gaming event may end after a certain number of gaming machines have been infected, after a period of time from when the one or more first gaming machines were infected, until a pool of award money has been exhausted, or based upon various other criteria. In a preferred embodiment, the viral gaming event ends before all gaming machines in a particular location or environment are infected, whereby the viral gaming event is perceived as a special or bonus event as to those machines which receive it (compared to those which do not).
The viral gaming event may end at a particular machine once the event has been played or presented at that machine (though the event may still be spreading to other machines and/or games before the consummation of the viral gaming event at the current gaming machine/game). If the viral gaming event has a long duration, such as a group-type event, then the viral gaming event might end at each machine at a termination time. For example, once a viral gaming event is initiated at a gaming machine it may continue until the entire viral gaming event is terminated at all machines, as detailed below.
Once each gaming machine is infected, the viral gaming event is presented at that gaming machine. As indicated, the viral gaming event which is presented at each machine may be unique (i.e., tailored to a player or a game), or may be similar the event presented at other gaming machines.
In a preferred embodiment, the viral gaming event is implemented in a gaming system including multiple gaming machines. Preferably, the event is controlled by one or more system controllers. The system controller might comprise a server which is in communication with the gaming machines.
The system 200 preferably comprises a controller or server 222. The server 222 may comprise a computing device configured to execute machine readable code. In a preferred embodiment, the server 222 is in communication with the gaming machines 220 via one or more communication links 224. Such links 224 might comprise wired or wireless links, or combinations thereof.
In one embodiment, the server 222 may initiate a viral gaming event trigger. For example, the server 222 might monitor coin-in/credit wager data at the gaming machines 220. If a certain threshold is met, the server 222 may initiate the viral gaming event. Following the decision to instantiate the viral gaming event, the server 222 may determine a propagation pattern, one or more seed gaming machines, and the direction and rate of propagation. The server 222 might select one or more gaming machines 220 at which the event is to be initiated. The server 222 might receive feedback that the triggers that took place, and then spread the viral gaming event to other gaming machines 220.
In another embodiment, a viral gaming event might be triggered at a gaming machine or machines 220. The server 222 is then notified of the triggering event. The server 222 might then determine the propagation pattern, and spread the viral gaming event to other gaming machines 220. This is a hybrid implementation in which the triggering event is initiated by a game or gaming machine and then propagates by a server.
In one embodiment, the server 222 might utilize an existing communication network which links the gaming machines 220, such as a player tracking or accounting system. However, in environments where gaming machines are associated with different systems (such as those of different manufacturers), the server 222 might communicate with each of those different gaming machines via other communication links. Such links might be direct to the gaming machines or might be via the servers of the other systems. If the game or gaming machine supports a standard communication protocol, no protocol translation is needed. However, if the game or gaming machine does not support a standard protocol, a protocol mediator server may be needed to translate the communication commands to the language that the gaming machine supports.
It is also possible for the viral gaming event to be presented by gaming machines in a peer-to-peer environment. In this configuration, each gaming machine may be configured with a viral gaming event application. Each application may determine if a viral gaming event trigger has occurred. If so, that gaming machine may initiate the viral gaming event and then send a message directly to one or more other selected gaming machines to spread the viral gaming event. In a peer-to-peer communication approach, the triggering event takes place at a game and then propagates directly to other qualified games or gaming machines without the need for a central server. A manual approach in which a casino manager initiates the triggering event can take place whether the viral gaming event is constructed via a client-server or a peer-to-peer architecture.
A variety of additional aspects of the invention will now be described.
In one embodiment, spread of the viral gaming event may be random. In other configurations, it may be controlled, such as based upon various criteria. For example, the viral gaming event may be spread from one or more first gaming machines to other gaming machines that have or are experiencing a lower rate of game play. A player tracking or other system may be used to monitor game play at gaming machines across a system. Certain machines, such as in certain areas of a casino, may experience lower rates of play. This information may be provided to the viral gaming event server and the viral gaming event server may cause the viral gaming event to be initiated at or spread to those machines. The viral gaming event may thus be used as a tool to entice players to play gaming machines which are otherwise not being played.
Patterns of infection or rates of infection may also be varied by other factors. For example, the spread of a viral gaming event may be a different rate during the day versus night, or during periods of high gaming activity versus low activity.
In another embodiment, other sensors or devices may be used to provide information to the viral gaming event system for use in controlling the spread of the viral gaming event. For example, instead of using game play information from a player tracking system, the viral gaming system might obtain information from one or more cameras. These cameras may provide visual information regarding the gaming floor, such as information regarding patterns of patron movement, gaming machine occupancy and the like. This information may be analyzed and used by the viral gaming event server in determining the propagation of the viral gaming event. Such camera or other gathered information may also be used during the spread of the gaming event to determine if desired goals are being met (i.e. a feedback control) and, as detailed below, used to change various viral gaming event metrics during the event to achieve those goals.
The viral gaming server may utilize various control strategies. For example, the viral gaming server may employ a pre-programmed strategy in determining the viral gaming event. This strategy might comprise, for example, locating gaming machines which are inactive and spreading the viral gaming event to those machines. The control strategy might include a learning component. For example, the viral gaming event server may employ strategies and feedback in order to modify control strategies. Such strategies might be used and modified, for example, to achieve certain goals such as even player distribution across a gaming floor, maximized gaming machine occupancy or the like.
As one aspect of viral gaming event spread, different viral gaming events may be presented at different times and to different machines. As indicated above, different viral gaming events may be presented at different gaming machines. For example, viral gaming events offering differing levels of awards may be offered at different gaming machines, such as to manipulate play patterns. As one example, viral gaming events with low awards may be initiated at gaming machines that are active and viral gaming events with high awards may be initiated at gaming machines that are inactive (so as to attempt to draw new players to those inactive machines).
As indicated, the spread of the viral gaming event from machine to machine may be based upon various criteria or controls. As other examples, the viral gaming event might spread based upon a geometric progression (a randomly selected or predetermined geometric pattern). Such a pattern might comprise a propagation direction and rate of propagation. The viral gaming event might also spread to proximate gaming machines or the like. In another embodiment, the viral gaming event may spread to players in certain groups or meeting certain qualifications. For example, the viral gaming event may spread to all players having certain common metrics associated with the player tracking/profile information.
In one embodiment, the viral gaming event may only spread to gaming machines which are in active play or may spread based upon other criteria. For example, the viral gaming event might only spread to games where players have met certain qualifying requirements (such as duration of play, minimum player loyalty points, Gold Club members, etc.).
However, in other embodiments, the viral gaming event may spread to inactive gaming machines or may spread based upon other/external criteria than player qualification. As indicated, for example, the viral gaming event may be spread to gaming machines with a low level of game play. In the event a gaming machine is inactive, it is possible that the viral gaming event permits a player to achieve winnings without a wager. For example, a player might travel to a gaming machine which has been infected and the player may be permitted to play a bonus viral gaming event with the opportunity for winnings without any wager.
In one embodiment, when a gaming machine is infected with the viral gaming event (or the event is initiated at that gaming machine), notification may be provided to the player thereof and/or potential players via various messaging technologies. For example, various types of visible, audible or other alerts such as email, text messages to a player's mobile device (such as a phone or PDA) may be provided. Such alerts might comprise notification via the main display of the gaming machine, a secondary display, various lights or speakers. In one embodiment, the alert might comprise an audible notification that the gaming machine has been “infected”. Preferably, such alerts can be used by players or potential players to track or monitor to the spread of the viral gaming event.
In one embodiment, path lighting or other elements might be used to display the spread of the viral gaming event. Path lighting in a floor, ceiling or the like may define multiple paths between gaming machines of a casino. The particular paths of spread may be illuminated, thus providing players with a visual indication of how the viral gaming event is spreading. Other types of alerts or indicators may be provided, such as laser light, sound propagation, synchronized vibration of the chairs, vibrating the player's mobile device, text messaging to the player's mobile device, and the like.
In one embodiment, it is possible for there to be a time delay between when a gaming machine is infected with the viral gaming event and when it is presented at the gaming machine. This might be referred to as an incubation period. For example, the viral gaming event might spread to one or more second gaming machines. An alert may be provided to the players thereof that the gaming machines have been infected. However, the viral gaming event itself might be presented immediately or after some period of time. In this manner, a player knows that the machine is infected and the viral gaming event will be presented, but does not know when. This entices the player to continue to play the gaming machine in anticipation of the viral gaming event being presented. During the incubation period, the viral gaming event may continue to propagate and infect other games. Thus, the viral gaming event may overlap at two or more games/gaming machines (as compared to an embodiment wherein the virus spreads sequentially and an event at one or more games/gaming machines must end before another event starts at other games/gaming machines).
As one aspect of the invention, viral gaming event data may be gathered and analyzed. Information may be gathered regarding the results of viral gaming events at each individual machine, the number of viral gaming events initiated vs. those which were played (i.e. were inactive machines played when the event was initiated at the machine), etc. This information may be used to determine how future viral gaming events are initiated or spread, the awards to be offered and the like.
It will be appreciated that the various features of the invention may be utilized in various combinations. For example, the viral gaming event may be configured to spread at differing rates over time, coupled with feedback control which causes the viral gaming event to spread to particular gaming machines based upon rate of game play. Further, multiple viral gaming events can occur on a casino floor, allowing such hybrid events as a game being infected with more than one viral gaming event at one time. This allows the player to be eligible for multiple bonuses, for instance.
In accordance with the invention, numerous advantages are realized. The present invention substantially increases the excitement of playing games, including wagering games. In particular, players know that a bonus or other gaming event which is additional to their base gaming event may be triggered and presented at any time. More importantly, even if such an event is not initiated at their gaming machine, if that event is initiated at another gaming machine it may still spread to their gaming machine. Once a gaming machine is infected, players can anticipate infection of other machines. Thus, substantial anticipation is created while the viral gaming event spreads through the various gaming machines.
An additional advantage of the viral gaming event is that it may be used to increase gaming play. Aside from the inherent excitement that the event presents, the viral gaming event may be particularly spread to gaming machines having low gaming activity. This spread may entice players to follow the spread of the viral gaming event to those machines. As players move to those machines, game play is increased on those gaming machines.
It will be understood that the above described arrangements of apparatus and the method there from are merely illustrative of applications of the principles of this invention and many other embodiments and modifications may be made without departing from the spirit and scope of the invention as defined in the claims.
Number | Name | Date | Kind |
---|---|---|---|
2033638 | Koppl | Mar 1936 | A |
2062923 | Nagy | Dec 1936 | A |
4741539 | Sutton et al. | May 1988 | A |
4948138 | Pease et al. | Aug 1990 | A |
5067712 | Georgilas | Nov 1991 | A |
5429361 | Raven et al. | Jul 1995 | A |
5655961 | Acres et al. | Aug 1997 | A |
5704835 | Dietz, II | Jan 1998 | A |
5727786 | Weingardt | Mar 1998 | A |
5833537 | Barrie | Nov 1998 | A |
5919091 | Bell et al. | Jul 1999 | A |
5947820 | Morro et al. | Nov 1999 | A |
5997401 | Crawford | Dec 1999 | A |
6001016 | Walker et al. | Dec 1999 | A |
6039648 | Guinn et al. | Mar 2000 | A |
6059289 | Vancura | May 2000 | A |
6089977 | Bennett | Jul 2000 | A |
6095920 | Sudahiro | Aug 2000 | A |
6110041 | Walker et al. | Aug 2000 | A |
6142872 | Walker et al. | Nov 2000 | A |
6146273 | Olsen | Nov 2000 | A |
6165071 | Weiss | Dec 2000 | A |
6231445 | Acres | May 2001 | B1 |
6270412 | Crawford et al. | Aug 2001 | B1 |
6293866 | Walker et al. | Aug 2001 | B1 |
6290600 | Glasson | Sep 2001 | B1 |
6353390 | Beri et al. | Mar 2002 | B1 |
6364768 | Acres et al. | Apr 2002 | B1 |
6416406 | Duhamel | Jul 2002 | B1 |
6416409 | Jordan | Jul 2002 | B1 |
6443452 | Brune | Sep 2002 | B1 |
6491584 | Graham et al. | Dec 2002 | B2 |
6505095 | Kolls | Jan 2003 | B1 |
6508710 | Paravia et al. | Jan 2003 | B1 |
6561900 | Baerlocker et al. | May 2003 | B1 |
6592457 | Frohm et al. | Jul 2003 | B1 |
6612574 | Cole et al. | Sep 2003 | B1 |
6620046 | Rowe | Sep 2003 | B2 |
6641477 | Dietz, II | Nov 2003 | B1 |
6645078 | Mattice | Nov 2003 | B1 |
6719630 | Seelig et al. | Apr 2004 | B1 |
6749510 | Giobbi | Jun 2004 | B2 |
6758757 | Luciano, Jr. et al. | Jul 2004 | B2 |
6773345 | Walker et al. | Aug 2004 | B2 |
6778820 | Tendler | Aug 2004 | B2 |
6780111 | Cannon et al. | Aug 2004 | B2 |
6799032 | McDonnell et al. | Sep 2004 | B2 |
6800027 | Giobbi et al. | Oct 2004 | B2 |
6804763 | Stockdate et al. | Oct 2004 | B1 |
6811486 | Luciano, Jr. | Nov 2004 | B1 |
6843725 | Nelson | Jan 2005 | B2 |
6846238 | Wells | Jan 2005 | B2 |
6848995 | Walker et al. | Feb 2005 | B1 |
6852029 | Baltz et al. | Feb 2005 | B2 |
6869361 | Sharpless et al. | Mar 2005 | B2 |
6875106 | Weiss et al. | Apr 2005 | B2 |
6884170 | Rowe | Apr 2005 | B2 |
6884172 | Lloyd et al. | Apr 2005 | B1 |
6902484 | Idaka | Jun 2005 | B2 |
6908390 | Nguyen et al. | Jun 2005 | B2 |
6913532 | Bearlocher et al. | Jul 2005 | B2 |
6923721 | Luciano et al. | Aug 2005 | B2 |
6935958 | Nelson | Aug 2005 | B2 |
6949022 | Showers | Sep 2005 | B1 |
6955600 | Glavich et al. | Oct 2005 | B2 |
6971956 | Rowe et al. | Dec 2005 | B2 |
6984174 | Cannon et al. | Jan 2006 | B2 |
6997803 | LeMay et al. | Feb 2006 | B2 |
7018292 | Tracy et al. | Mar 2006 | B2 |
7032115 | Kashani | Apr 2006 | B2 |
7033276 | Walker et al. | Apr 2006 | B2 |
7035626 | Luciano | Apr 2006 | B1 |
7037195 | Schneider et al. | May 2006 | B2 |
7048628 | Schneider | May 2006 | B2 |
7048630 | Berg et al. | May 2006 | B2 |
7063617 | Brosnan et al. | Jun 2006 | B2 |
7076329 | Kolls | Jun 2006 | B1 |
7089264 | Guido et al. | Aug 2006 | B1 |
7094148 | Bearlocher et al. | Aug 2006 | B2 |
7105736 | Laakso | Sep 2006 | B2 |
7111141 | Nelson | Sep 2006 | B2 |
7144321 | Mayeroff | Dec 2006 | B2 |
7152783 | Charrin | Dec 2006 | B2 |
7169041 | Tessmer et al. | Jan 2007 | B2 |
7169052 | Beaulieu et al. | Jan 2007 | B2 |
7175523 | Gilmore et al. | Feb 2007 | B2 |
7181228 | Boesch | Feb 2007 | B2 |
7182690 | Giobbi et al. | Feb 2007 | B2 |
RE39644 | Alcorn et al. | May 2007 | E |
7243104 | Bill | Jul 2007 | B2 |
7247098 | Bradford et al. | Jul 2007 | B1 |
7259718 | Patterson et al. | Aug 2007 | B2 |
7275989 | Moody | Oct 2007 | B2 |
7285047 | Gielb et al. | Oct 2007 | B2 |
7311608 | Danieli | Dec 2007 | B1 |
7314408 | Cannon et al. | Jan 2008 | B2 |
7316615 | Soltys et al. | Jan 2008 | B2 |
7316619 | Nelson | Jan 2008 | B2 |
7318775 | Brosnan et al. | Jan 2008 | B2 |
7326116 | O'Donovan et al. | Feb 2008 | B2 |
7330108 | Thomas | Feb 2008 | B2 |
7346358 | Wood et al. | Mar 2008 | B2 |
7355112 | Laakso | Apr 2008 | B2 |
7384338 | Rothschild et al. | Jun 2008 | B2 |
7387571 | Walker et al. | Jun 2008 | B2 |
7393278 | Gerson et al. | Jul 2008 | B2 |
7396990 | Lu et al. | Jul 2008 | B2 |
7415426 | Williams et al. | Aug 2008 | B2 |
7425177 | Rodgers et al. | Sep 2008 | B2 |
7427234 | Soltys et al. | Sep 2008 | B2 |
7427236 | Kaminkow et al. | Sep 2008 | B2 |
7427708 | Ohmura | Sep 2008 | B2 |
7431650 | Kessman | Oct 2008 | B2 |
7448949 | Kaminkow et al. | Nov 2008 | B2 |
7500913 | Baerlocher | Mar 2009 | B2 |
7510474 | Carter | Mar 2009 | B2 |
7513828 | Nguyen et al. | Apr 2009 | B2 |
7519838 | Suurballe | Apr 2009 | B1 |
7559838 | Walker et al. | Jul 2009 | B2 |
7563167 | Walker et al. | Jul 2009 | B2 |
7572183 | Olivas et al. | Aug 2009 | B2 |
7585222 | Muir | Sep 2009 | B2 |
7602298 | Thomas | Oct 2009 | B2 |
7607174 | Kashchenko et al. | Oct 2009 | B1 |
7611409 | Muir et al. | Nov 2009 | B2 |
7637810 | Amaitis et al. | Dec 2009 | B2 |
7644861 | Alderucci et al. | Jan 2010 | B2 |
7653757 | Fernald et al. | Jan 2010 | B1 |
7699703 | Muir | Apr 2010 | B2 |
7722453 | Lark et al. | May 2010 | B2 |
7758423 | Foster et al. | Jul 2010 | B2 |
7771271 | Walker et al. | Aug 2010 | B2 |
7780529 | Rowe et al. | Aug 2010 | B2 |
7780531 | Englman et al. | Aug 2010 | B2 |
7785192 | Canterbury et al. | Aug 2010 | B2 |
7811172 | Asher et al. | Oct 2010 | B2 |
7819749 | Fish | Oct 2010 | B1 |
7822688 | Labron | Oct 2010 | B2 |
7828652 | Nguyen et al. | Nov 2010 | B2 |
7828654 | Carter | Nov 2010 | B2 |
7828661 | Fish | Nov 2010 | B1 |
7850528 | Wells | Dec 2010 | B2 |
7874919 | Paulsen et al. | Jan 2011 | B2 |
7877798 | Saunders et al. | Jan 2011 | B2 |
7883413 | Paulsen | Feb 2011 | B2 |
7892097 | Muir et al. | Feb 2011 | B2 |
7909692 | Nguyen et al. | Mar 2011 | B2 |
7909699 | Parrott et al. | Mar 2011 | B2 |
7918728 | Nguyen et al. | Apr 2011 | B2 |
7927211 | Rowe et al. | Apr 2011 | B2 |
7927212 | Hedrick et al. | Apr 2011 | B2 |
7951008 | Wolf et al. | May 2011 | B2 |
8057298 | Nguyen et al. | Nov 2011 | B2 |
8057303 | Rasmsen | Nov 2011 | B2 |
8087988 | Nguyen et al. | Jan 2012 | B2 |
8117608 | Slettehaugh | Feb 2012 | B1 |
8133113 | Nguyen | Mar 2012 | B2 |
8182326 | Speers et al. | May 2012 | B2 |
8210927 | Hedrick | Jul 2012 | B2 |
8221245 | Walker | Jul 2012 | B2 |
8226459 | Barrett | Jul 2012 | B2 |
8226474 | Nguyen et al. | Jul 2012 | B2 |
8231456 | Zielinski | Jul 2012 | B2 |
8235803 | Loose et al. | Aug 2012 | B2 |
8282475 | Nguyen et al. | Oct 2012 | B2 |
8323099 | Durham et al. | Dec 2012 | B2 |
8337290 | Nguyen et al. | Dec 2012 | B2 |
8342946 | Amaitis | Jan 2013 | B2 |
8403758 | Homik | Mar 2013 | B2 |
8461958 | Saenz | Jun 2013 | B2 |
8469813 | Joshi | Jun 2013 | B2 |
8602875 | Nguyen | Dec 2013 | B2 |
8613655 | Kisenwether | Dec 2013 | B2 |
8696470 | Nguyen | Apr 2014 | B2 |
8745417 | Huang et al. | Jun 2014 | B2 |
8858323 | Nguyen et al. | Oct 2014 | B2 |
9235952 | Nguyen | Jan 2016 | B2 |
9292996 | Davis et al. | Mar 2016 | B2 |
9466171 | Hornik | Oct 2016 | B2 |
9483901 | Nguyen | Nov 2016 | B2 |
9576425 | Nguyen | Feb 2017 | B2 |
9626826 | Nguyen | Apr 2017 | B2 |
9666021 | Nguyen | May 2017 | B2 |
9672686 | Nguyen | Jun 2017 | B2 |
9741205 | Nguyen | Aug 2017 | B2 |
9811973 | Nguyen | Nov 2017 | B2 |
9814970 | Nguyen | Nov 2017 | B2 |
9842462 | Nguyen | Dec 2017 | B2 |
9875606 | Nguyen | Jan 2018 | B2 |
9875609 | Nguyen | Jan 2018 | B2 |
20010004607 | Olsen | Jun 2001 | A1 |
20010016516 | Takatsuka | Aug 2001 | A1 |
20010047291 | Garahi | Nov 2001 | A1 |
20020042295 | Walker et al. | Apr 2002 | A1 |
20020111210 | Luciano, Jr. et al. | Aug 2002 | A1 |
20020111213 | McEntee et al. | Aug 2002 | A1 |
20020113369 | Weingardt | Aug 2002 | A1 |
20020116615 | Nguyen et al. | Aug 2002 | A1 |
20020133418 | Hammond et al. | Sep 2002 | A1 |
20020137217 | Rowe et al. | Sep 2002 | A1 |
20020142825 | Lark et al. | Oct 2002 | A1 |
20020147047 | Letovsky et al. | Oct 2002 | A1 |
20020147049 | Carter, Sr. | Oct 2002 | A1 |
20020151366 | Walker et al. | Oct 2002 | A1 |
20020167536 | Valdes et al. | Nov 2002 | A1 |
20020183105 | Cannon et al. | Dec 2002 | A1 |
20030001338 | Bennett et al. | Jan 2003 | A1 |
20030008696 | Abecassis et al. | Jan 2003 | A1 |
20030027635 | Walker et al. | Feb 2003 | A1 |
20030064805 | Wells | Apr 2003 | A1 |
20030064807 | Walker et al. | Apr 2003 | A1 |
20030092480 | White et al. | May 2003 | A1 |
20030100361 | Sharpless et al. | May 2003 | A1 |
20030103965 | Jung et al. | Jun 2003 | A1 |
20030104860 | Cannon et al. | Jun 2003 | A1 |
20030104865 | Itkis et al. | Jun 2003 | A1 |
20030148809 | Nelson | Aug 2003 | A1 |
20030162588 | Brosnan et al. | Aug 2003 | A1 |
20030199295 | Vancura | Oct 2003 | A1 |
20030224852 | Walker et al. | Dec 2003 | A1 |
20030224854 | Joao | Dec 2003 | A1 |
20040002386 | Wolfe et al. | Jan 2004 | A1 |
20040005919 | Walker et al. | Jan 2004 | A1 |
20040023709 | Beaulieu et al. | Feb 2004 | A1 |
20040023716 | Gaelmann | Feb 2004 | A1 |
20040038736 | Bryant | Feb 2004 | A1 |
20040048650 | Mierau et al. | Mar 2004 | A1 |
20040068460 | Feeley | Apr 2004 | A1 |
20040082385 | Silva et al. | Apr 2004 | A1 |
20040106449 | Walker et al. | Jun 2004 | A1 |
20040137987 | Nguyen et al. | Jun 2004 | A1 |
20040127290 | Walker et al. | Jul 2004 | A1 |
20040147308 | Walker et al. | Jul 2004 | A1 |
20040224753 | Odonovan et al. | Nov 2004 | A1 |
20040256803 | Ko | Dec 2004 | A1 |
20040259633 | Gentles et al. | Dec 2004 | A1 |
20050003890 | Hedrick et al. | Jan 2005 | A1 |
20050004980 | Vadjinia | Jan 2005 | A1 |
20050026696 | Hashimoto et al. | Feb 2005 | A1 |
20050101376 | Walker et al. | May 2005 | A1 |
20050101383 | Wells | May 2005 | A1 |
20050130728 | Nguyen et al. | Jun 2005 | A1 |
20050181870 | Nguyen et al. | Aug 2005 | A1 |
20050181875 | Hoehne | Aug 2005 | A1 |
20050187020 | Amaitis et al. | Aug 2005 | A1 |
20050202875 | Murphy et al. | Sep 2005 | A1 |
20050209002 | Blythe et al. | Sep 2005 | A1 |
20050223219 | Gatto et al. | Oct 2005 | A1 |
20050239546 | Hedrick | Oct 2005 | A1 |
20050255919 | Nelson | Nov 2005 | A1 |
20050273635 | Wilcox et al. | Dec 2005 | A1 |
20050277471 | Rsell et al. | Dec 2005 | A1 |
20050282637 | Gatto et al. | Dec 2005 | A1 |
20060009283 | Englman et al. | Jan 2006 | A1 |
20060036874 | Cockerille | Feb 2006 | A1 |
20060046822 | Kaminkow et al. | Mar 2006 | A1 |
20060046830 | Webb | Mar 2006 | A1 |
20060046849 | Kovacs | Mar 2006 | A1 |
20060068893 | Jaffe et al. | Mar 2006 | A1 |
20060073869 | LeMay et al. | Apr 2006 | A1 |
20060073897 | Englman et al. | Apr 2006 | A1 |
20060148551 | Walker et al. | Jul 2006 | A1 |
20060189382 | Muir et al. | Aug 2006 | A1 |
20060217170 | Roireau | Sep 2006 | A1 |
20060217193 | Walker et al. | Sep 2006 | A1 |
20060247028 | Brosnan et al. | Nov 2006 | A1 |
20060247035 | Rowe et al. | Nov 2006 | A1 |
20060252530 | Oberberger et al. | Nov 2006 | A1 |
20060253481 | Guido et al. | Nov 2006 | A1 |
20060281525 | Borissov | Dec 2006 | A1 |
20060281541 | Nguyen et al. | Dec 2006 | A1 |
20060287106 | Jensen | Dec 2006 | A1 |
20070004510 | Underdahl et al. | Jan 2007 | A1 |
20070026935 | Wolf et al. | Feb 2007 | A1 |
20070054739 | Amaitis et al. | Mar 2007 | A1 |
20070060254 | Muir | Mar 2007 | A1 |
20070060306 | Amaitis et al. | Mar 2007 | A1 |
20070060319 | Block et al. | Mar 2007 | A1 |
20070060358 | Amaitis et al. | Mar 2007 | A1 |
20070077981 | Hungate et al. | Apr 2007 | A1 |
20070087833 | Feeney et al. | Apr 2007 | A1 |
20070087834 | Moser et al. | Apr 2007 | A1 |
20070093299 | Bergeron | Apr 2007 | A1 |
20070129123 | Eryou et al. | Jun 2007 | A1 |
20070149279 | Norden et al. | Jun 2007 | A1 |
20070149286 | Bemmel | Jun 2007 | A1 |
20070159301 | Hirt et al. | Jul 2007 | A1 |
20070161402 | Ng et al. | Jul 2007 | A1 |
20070184904 | Lee | Aug 2007 | A1 |
20070191109 | Crowder et al. | Aug 2007 | A1 |
20070207852 | Nelson et al. | Sep 2007 | A1 |
20070207854 | Wolf et al. | Sep 2007 | A1 |
20070241187 | Alderucci et al. | Oct 2007 | A1 |
20070248036 | Nevalainen | Oct 2007 | A1 |
20070257430 | Hardy et al. | Nov 2007 | A1 |
20070259713 | Fiden et al. | Nov 2007 | A1 |
20070259717 | Mattice et al. | Nov 2007 | A1 |
20070270213 | Nguyen et al. | Nov 2007 | A1 |
20070275777 | Walker et al. | Nov 2007 | A1 |
20070275779 | Amaitis et al. | Nov 2007 | A1 |
20070281782 | Amaitis et al. | Dec 2007 | A1 |
20070281785 | Amaitis et al. | Dec 2007 | A1 |
20070298873 | Nguyen et al. | Dec 2007 | A1 |
20080015032 | Bradford et al. | Jan 2008 | A1 |
20080020824 | Cuddy et al. | Jan 2008 | A1 |
20080032787 | Low et al. | Feb 2008 | A1 |
20080070652 | Nguyen et al. | Mar 2008 | A1 |
20080070681 | Marks et al. | Mar 2008 | A1 |
20080076505 | Nguyen | Mar 2008 | A1 |
20080076506 | Nguyen et al. | Mar 2008 | A1 |
20080076548 | Paulsen | Mar 2008 | A1 |
20080076572 | Nguyen et al. | Mar 2008 | A1 |
20080096650 | Baerlocher | Apr 2008 | A1 |
20080102956 | Burman et al. | May 2008 | A1 |
20080102957 | Burnman et al. | May 2008 | A1 |
20080113772 | Burrill et al. | May 2008 | A1 |
20080119267 | Denlay | May 2008 | A1 |
20080139306 | Lutnick | Jun 2008 | A1 |
20080146321 | Parente | Jun 2008 | A1 |
20080150902 | Edpalm et al. | Jun 2008 | A1 |
20080153583 | Huntley et al. | Jun 2008 | A1 |
20080161110 | Campbell | Jul 2008 | A1 |
20080167106 | Lutnick et al. | Jul 2008 | A1 |
20080182667 | Davis et al. | Jul 2008 | A1 |
20080200251 | Alderucci | Aug 2008 | A1 |
20080207307 | Cunningham, II et al. | Aug 2008 | A1 |
20080214258 | Brosnan et al. | Sep 2008 | A1 |
20080234047 | Nguyen | Sep 2008 | A1 |
20080238610 | Rosenbereg | Oct 2008 | A1 |
20080252419 | Batchelor | Oct 2008 | A1 |
20080254878 | Sauders et al. | Oct 2008 | A1 |
20080254881 | Lutnick et al. | Oct 2008 | A1 |
20080254883 | Patel et al. | Oct 2008 | A1 |
20080254891 | Sauders et al. | Oct 2008 | A1 |
20080254892 | Sauders et al. | Oct 2008 | A1 |
20080254897 | Sauders et al. | Oct 2008 | A1 |
20080263173 | Weber et al. | Oct 2008 | A1 |
20080300058 | Sum et al. | Dec 2008 | A1 |
20080305864 | Kelly et al. | Dec 2008 | A1 |
20080305865 | Kelly et al. | Dec 2008 | A1 |
20080305866 | Kelly et al. | Dec 2008 | A1 |
20080311994 | Amaitis et al. | Dec 2008 | A1 |
20080318669 | Buchholz | Dec 2008 | A1 |
20080318686 | Crowder et al. | Dec 2008 | A1 |
20090005165 | Arezina et al. | Jan 2009 | A1 |
20090011822 | Englman | Jan 2009 | A1 |
20090029766 | Lutnick et al. | Jan 2009 | A1 |
20090054149 | Brosnan et al. | Feb 2009 | A1 |
20090077396 | Tsai et al. | Mar 2009 | A1 |
20090088258 | Saunders et al. | Apr 2009 | A1 |
20090098925 | Gagner et al. | Apr 2009 | A1 |
20090104977 | Zielinski | Apr 2009 | A1 |
20090104983 | Okada | Apr 2009 | A1 |
20090118002 | Lyons | May 2009 | A1 |
20090118013 | Finnimore et al. | May 2009 | A1 |
20090118022 | Lyons et al. | May 2009 | A1 |
20090124366 | Aoki et al. | May 2009 | A1 |
20090131151 | Harris et al. | May 2009 | A1 |
20090132163 | Ashley, Jr. et al. | May 2009 | A1 |
20090137255 | Ashley et al. | May 2009 | A1 |
20090138133 | Buchholz et al. | May 2009 | A1 |
20090149245 | Fabbri | Jun 2009 | A1 |
20090149261 | Chen et al. | Jun 2009 | A1 |
20090153342 | Thorn | Jun 2009 | A1 |
20090156303 | Kiely et al. | Jun 2009 | A1 |
20090176578 | Herrmann et al. | Jul 2009 | A1 |
20090191962 | Hardy et al. | Jul 2009 | A1 |
20090197684 | Arezina et al. | Aug 2009 | A1 |
20090216547 | Canora et al. | Aug 2009 | A1 |
20090219901 | Bull et al. | Sep 2009 | A1 |
20090221342 | Katz et al. | Sep 2009 | A1 |
20090227302 | Abe | Sep 2009 | A1 |
20090239666 | Hall et al. | Sep 2009 | A1 |
20090264190 | Davis et al. | Oct 2009 | A1 |
20090275410 | Kisenwether et al. | Nov 2009 | A1 |
20090275411 | Kisenwether et al. | Nov 2009 | A1 |
20090298468 | Hsu | Dec 2009 | A1 |
20100002897 | Keady | Jan 2010 | A1 |
20100004058 | Acres | Jan 2010 | A1 |
20100056248 | Acres | Mar 2010 | A1 |
20100062833 | Mattice et al. | Mar 2010 | A1 |
20100079237 | Falk | Apr 2010 | A1 |
20100081501 | Carpenter et al. | Apr 2010 | A1 |
20100081509 | Burke | Apr 2010 | A1 |
20100099499 | Amaitis et al. | Apr 2010 | A1 |
20100124967 | Lutnick et al. | May 2010 | A1 |
20100130276 | Fiden | May 2010 | A1 |
20100160043 | Fujimoto et al. | Jun 2010 | A1 |
20100178977 | Kim et al. | Jul 2010 | A1 |
20100197383 | Rad et al. | Aug 2010 | A1 |
20100203955 | Sylla | Aug 2010 | A1 |
20100203963 | Allen | Aug 2010 | A1 |
20100227662 | Speers et al. | Sep 2010 | A1 |
20100227670 | Arezina et al. | Sep 2010 | A1 |
20100227671 | Laaroussi | Sep 2010 | A1 |
20100227687 | Speers et al. | Sep 2010 | A1 |
20100234091 | Baerlocher et al. | Sep 2010 | A1 |
20100279764 | Allen et al. | Nov 2010 | A1 |
20100323780 | Acres | Dec 2010 | A1 |
20100325703 | Etchegoyen | Dec 2010 | A1 |
20110009181 | Speers et al. | Jan 2011 | A1 |
20110039615 | Acres | Feb 2011 | A1 |
20110065492 | Acres | Mar 2011 | A1 |
20110105216 | Cohen | May 2011 | A1 |
20110111827 | Nicely et al. | May 2011 | A1 |
20110111843 | Nicely et al. | May 2011 | A1 |
20110111860 | Nguyen | May 2011 | A1 |
20110118010 | Brune | May 2011 | A1 |
20110159966 | Gura et al. | Jun 2011 | A1 |
20110183732 | Block | Jul 2011 | A1 |
20110183749 | Allen | Jul 2011 | A1 |
20110207525 | Allen | Aug 2011 | A1 |
20110212711 | Scott | Sep 2011 | A1 |
20110212767 | Barclay et al. | Sep 2011 | A1 |
20110223993 | Allen et al. | Sep 2011 | A1 |
20110263318 | Agarwal et al. | Oct 2011 | A1 |
20110306400 | Nguyen | Dec 2011 | A1 |
20110306426 | Novak et al. | Dec 2011 | A1 |
20120015709 | Bennett et al. | Jan 2012 | A1 |
20120028703 | Anderson et al. | Feb 2012 | A1 |
20120028718 | Barclay et al. | Feb 2012 | A1 |
20120034968 | Watkins et al. | Feb 2012 | A1 |
20120046110 | Amaitis | Feb 2012 | A1 |
20120094769 | Nguyen et al. | Apr 2012 | A1 |
20120100908 | Wells | Apr 2012 | A1 |
20120108319 | Caputo et al. | May 2012 | A1 |
20120122567 | Gangadharan et al. | May 2012 | A1 |
20120122584 | Nguyen | May 2012 | A1 |
20120122590 | Nguyen | May 2012 | A1 |
20120172130 | Acres | Jul 2012 | A1 |
20120184363 | Barclay et al. | Jul 2012 | A1 |
20120190426 | Acres | Jul 2012 | A1 |
20120194448 | Rothkopf | Aug 2012 | A1 |
20120208618 | Frerking | Aug 2012 | A1 |
20120231885 | Speer, II | Sep 2012 | A1 |
20120239566 | Everett | Sep 2012 | A1 |
20120322563 | Nguyen et al. | Dec 2012 | A1 |
20120330740 | Pennington et al. | Dec 2012 | A1 |
20130005433 | Holch | Jan 2013 | A1 |
20130005443 | Kosta | Jan 2013 | A1 |
20130005453 | Nguyen et al. | Jan 2013 | A1 |
20130065668 | LeMay | Mar 2013 | A1 |
20130281188 | Guinn | Mar 2013 | A1 |
20130104193 | Gatto et al. | Apr 2013 | A1 |
20130059650 | Sylia et al. | May 2013 | A1 |
20130132745 | Schoening et al. | May 2013 | A1 |
20130185559 | Morel | Jul 2013 | A1 |
20130196756 | Nguyen | Aug 2013 | A1 |
20130196776 | Nguyen | Aug 2013 | A1 |
20130210513 | Nguyen | Aug 2013 | A1 |
20130210514 | Nguyen | Aug 2013 | A1 |
20130210530 | Nguyen | Aug 2013 | A1 |
20130225279 | Patceg | Aug 2013 | A1 |
20130225282 | Williams et al. | Aug 2013 | A1 |
20130252730 | Joshi | Sep 2013 | A1 |
20130316808 | Nelson | Nov 2013 | A1 |
20140006129 | Heath | Jan 2014 | A1 |
20140057716 | Massing et al. | Feb 2014 | A1 |
20140087862 | Burke | Mar 2014 | A1 |
20140094295 | Nguyen | Apr 2014 | A1 |
20140179431 | Nguyen | Jun 2014 | A1 |
20140274309 | Nguyen | Sep 2014 | A1 |
20140274319 | Nguyen | Sep 2014 | A1 |
20140274320 | Nguyen | Sep 2014 | A1 |
20140274342 | Nguyen | Sep 2014 | A1 |
20140274357 | Nguyen | Sep 2014 | A1 |
20140274360 | Nguyen | Sep 2014 | A1 |
20140274367 | Nguyen | Sep 2014 | A1 |
20140274388 | Nguyen | Sep 2014 | A1 |
20150089595 | Telles | Mar 2015 | A1 |
20150133223 | Carter | May 2015 | A1 |
20150143543 | Phegade | Aug 2015 | A1 |
20170116819 | Nguyen | Apr 2017 | A1 |
20170116823 | Nguyen | Apr 2017 | A1 |
20170144071 | Nguyen | May 2017 | A1 |
20170148259 | Nguyen | May 2017 | A1 |
20170148261 | Nguyen | May 2017 | A1 |
20170148263 | Nguyen | May 2017 | A1 |
20170206734 | Nguyen | Jul 2017 | A1 |
20170228979 | Nguyen | Aug 2017 | A1 |
20170243440 | Nguyen | Aug 2017 | A1 |
20170337770 | Nguyen | Nov 2017 | A1 |
Number | Date | Country |
---|---|---|
2033638 | May 1980 | GB |
2062923 | May 1981 | GB |
2096376 | Oct 1982 | GB |
2097570 | Nov 1982 | GB |
2335524 | Sep 1999 | GB |
12005000454 | May 2007 | GB |
WO 05073933 | Aug 2005 | WO |
WO 2008027621 | Mar 2008 | WO |
WO 2009026309 | Feb 2009 | WO |
WO 2009062148 | May 2009 | WO |
WO 2010017252 | Aug 2009 | WO |
Entry |
---|
Benston, Liz, “Harrahs Launches iPhone App; Caesars Bypasses Check-in,” Las Vegas Sun, Las Vegas, NV. Jan. 8, 2010. |
Finnegan, Amanda, “Casinos Connecting with Customers via Iphone Apps”, May 27, 2010, Las Vegas Sun, Las Vegas, NV. |
Gaming Today Staff, “Slots showcased at 2009 National Indian Gaming Assoc.”, GamingToday.com, Apr. 14, 2009. |
Green, Marian,“Testing Texting Casino Journal”, Mar. 2, 2009. |
Hasan, Ragib, et al., “A Survey of Peer-to-Peer Storage Techniques for Distributed File Systems”, National Center for Supercomputing Applications, Department of Computer Science, University of Ilinois at Urbana Champain, Jun. 27, 2005. |
Jones, Trahern, “Telecon-equipped drones could revolutionize wireless market”, azcentral.com, http://www.azcentral.com/business/news/articles/20130424telecom-equipped-drones-could-revolutionize-wireless-market.html, downloaded Jul. 2, 2013, 2 pages. |
Yancey, Kitty Bean, “Navigate Around Vegas with New iPhone Apps”, USA Today, Jun. 3, 2010. |
iAPS, Daily Systems LLC, 2010. |
Notice of Allowance for U.S. Appl. No. 12/757,968, dated Dec. 18, 2013. |
Office Action for U.S. Appl. No. 12/945,889, dated Dec. 18, 2013. |
Office Action for U.S. Appl. No. 13/632,828, dated Jul. 30, 2013. |
Restriction Requirement for U.S. Appl. No. 13/801,256, dated Dec. 30, 2013. |
Office Action for U.S. Appl. No. 13/801,171, dated Dec. 26, 2013. |
Office Action for U.S. Appl. No. 13/801,234, dated Jan. 10, 2014. |
Final Office Action for U.S. Appl. No. 13/296,182, dated Feb. 12, 2014. |
Office Action for U.S. Appl. No. 12/617,717, dated Feb. 25, 2014. |
Office Action for U.S. Appl. No. 13/801,076, dated Mar. 28, 2014. |
Final Office Action for U.S. Appl. No. 13/633,118, dated Apr. 3, 2014. |
Office Action for U.S. Appl. No. 13/843,192, dated Apr. 3, 2014. |
Office Action for U.S. Appl. No. 13/632,743, dated Apr. 10, 2014. |
Office Action for U.S. Appl. No. 13/801,121, dated Apr. 11, 2014. |
Final Office Action for U.S. Appl. No. 12/945,889, dated Jun. 30, 2014. |
Notice of Allowance for U.S. Appl. No. 12/617,717, dated Jul. 14, 2014. |
Office Action for U.S. Appl. No. 13/801,121, dated Sep. 24, 2014. |
Office Action for U.S. Appl. No. 13/801,171, dated Sep. 22, 2014. |
Office Action for U.S. Appl. No. 13/801,234, dated Oct. 1, 2014. |
Final Office Action for U.S. Appl. No. 13/843,192, dated Oct. 21, 2014. |
Office Action for U.S. Appl. No. 13/632,743, dated Oct. 23, 2014. |
Office Action for U.S. Appl. No. 12/945,889, dated Oct. 23, 2014. |
Office Action for U.S. Appl. No. 13/632,828, dated Nov. 7, 2014. |
Office Action fpr U.S. Appl. No. 12/797,610, dated Dec. 15, 2014. |
Final Office Action for U.S. Appl. No. 12/945,889, dated Feb. 12, 2015. |
Final Office Action for U.S. Appl. No. 13/801,171, dated Mar. 16, 2015. |
Office Action for U.S. Appl. No. 13/833,116, dated Mar. 15, 2015. |
Office Action for U.S. Appl. No. 13/632,828, dated Apr. 10, 2015. |
Final Office Action for U.S. Appl. No. 13/801,121, dated Apr. 21, 2015. |
Final Office Action for U.S. Appl. No. 13/557,063, dated Apr. 28, 2015. |
Office Action for U.S. Appl. No. 13/296,182, dated Jun. 5, 2015. |
Office Action for U.S. Appl. No. 13/843,192, dated Mar. 15, 2013. |
Office Action for U.S. Appl. No. 12/797,610, dated Jul. 14, 2015. |
Final Office Action for U.S. Appl. No. 13/833,953, dated Jul. 17, 2015. |
Notice of Allowance for U.S. Appl. No. 12/945,889, dated Jul. 22, 2015. |
Office Action for U.S. Appl. No. 12/945,888 dated Apr. 10, 2012. |
Final Office Action for U.S. Appl. No. 12/945,888 dated Sep. 21, 2012. |
Advisory Action for U.S. Appl. No. 12/945,888 dated Jan. 30, 2013. |
Office Action for U.S. Appl. No. 12/581,115 dated Dec. 20, 2011. |
Final Office Action for U.S. Appl. No. 12/581,115 dated Sep. 13, 2012. |
Notice of Allowance for U.S. Appl. No. 12/581,115 dated May 24, 2013. |
Office Action for U.S. Appl. No. 12/619,672 dated Dec. 20, 2011. |
Final Office Action for U.S. Appl. No. 12/619,672 dated Nov. 6, 2012. |
Office Action for U.S. Appl. No. 12/619,672 dated Mar., 7, 2013. |
Office Action for U.S. Appl. No. 12/617,717 dated Oct. 4, 2011. |
Office Action for U.S. Appl. No. 12/617,717 dated Apr. 4, 2012. |
Advisory Action for U.S. Appl. No. 12/617,717 dated Jun. 12, 2011. |
Office Action for U.S. Appl. No. 12/617,717 dated Jun. 17, 2013. |
Office Action for U.S. Appl. No. 12/797,610 dated Dec. 8, 2011. |
Final Office Action for U.S. Appl. No. 12/797,610 dated Jun. 6, 2012. |
Office Action for U.S. Appl. No. 12/797,610 dated Feb. 26, 2013. |
Office Action for U.S. Appl. No. 12/757,968, dated May 9, 2012. |
Final Office Action for U.S. Appl. No. 12/757,968, dated Nov. 29, 2012. |
Office Action for U.S. Appl. No. 12/757,968, dated Apr. 25, 2013. |
Office Action for U.S. Appl. No. 12/797,616 dated Mar. 15, 2012. |
Final Office Action for U.S. Appl. No. 12/797,616 dated Oct. 13, 2012. |
Office Action for U.S. Appl. No. 12/797,616 dated Feb. 13, 2013. |
Final Office Action for U.S. Appl. No. 12/797,616 dated May 8, 2013. |
Office Action for U.S. Appl. No. 13/296,182 dated Dec. 5, 2012. |
Frontier Fortune game, email notification, MGM Resorts Intl., Aug. 9, 2013. |
“Getting Back in the Game: Geolocation Can Ensure Compliance with New iGaming Regulations”, White Paper, Quova, Inc., 2010. |
Notice of Allowance of U.S. Appl. No. 12/619,672, dated Aug. 23, 2013. |
Office Action for U.S. Appl. No. 13/801,256, dated Jul. 2, 2013. |
Notice of Allowance for U.S. Appl. No. 12/619,672, dated Oct. 3, 2013. |
Notice of Allowance for U.S. Appl. No. 12/757,968, dated Oct. 11, 2013. |
Final Office Action for U.S. Appl. No. 12/797,610, dated Jul. 10, 2013. |
Office Action for U.S. Appl. No. 12/797,616, dated Aug. 10, 2015. |
Final Office Action for U.S. Appl. No. 13/801,234, dated Aug. 14, 2015. |
Final Office Action for U.S. Appl. No. 13/833,116, dated Sep. 24, 2015. |
Office Action for U.S. Appl. No. 13/801,121, dated Oct. 2, 2015. |
Office Action for U.S. Appl. No. 14/017,150, dated Oct. 7, 2015. |
Office Action for U.S. Appl. No. 14/017,159, dated Oct. 7, 2015. |
Office Action for U.S. Appl. No. 13/801,271 dated Oct. 19, 2015. |
Office Action for U.S. Appl. No. 14/211,536 dated Oct. 19, 2015. |
Final Office Action for U.S. Appl. No. 13/632,828, dated Oct. 22, 2015. |
Office Action for U.S. Appl. No. 14/217,066, dated Dec. 17, 2015. |
Notice of Allowance for U.S. Appl. No. 13/557,063, dated Dec. 23, 2015. |
Office Action for U.S. Appl. No. 13/296,182, dated Dec. 23, 2015. |
Final Office Action for U.S. Appl. No. 13/843,192, dated Dec. 30, 2015. |
Office Action for U.S. Appl. No. 13/801,076, dated Jan. 11, 2016. |
Office Action for U.S. Appl. No. 12/945,888, dated Jan. 22, 2016. |
Notice of Allowance for U.S. Appl. No. 13/843,192, dated Aug. 10, 2016. |
Final Office Action for U.S. Appl. No. 14/211,536, dated Mar. 14, 2014. |
Notice of Allowance for U.S. Appl. No. 13/833,116, dated Oct. 11, 2016. |
Notice of Allowance for U.S. Appl. No. 13/801,271, dated Dec. 2, 2016. |
Notice of Allowance for U.S. Appl. No. 12/797,610, dated Dec. 7, 2016. |
Notice of Allowance for U.S. Appl. No. 13/632,828, dated Dec. 16, 2016. |
Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 19, 2016. |
Notice of Allowance for U.S. Appl. No. 14/211,536, dated Dec. 28, 2016. |
Notice of Allowance for U.S. Appl. No. 13/801,256, dated Jan. 20, 2017. |
Office Action for U.S. Appl. No. 13/800,917, dated Feb. 3, 2017. |
Final Office Action for U.S. Appl. No. 12/797,616, dated Feb. 10, 2017. |
Office Action for U.S. Appl. No. 12/945,888, dated Feb. 28, 2017. |
Final Office Action for U.S. Appl. No. 14/189,948, dated Mar. 17, 2017. |
Office Action for U.S. Appl. No. 15/400,840, dated Mar. 10, 2017. |
Notice of Allowance for U.S. Appl. No. 13/801,121, dated Mar. 29, 2017. |
Office Action for U.S. Appl. No. 15/270,333, dated Mar. 30, 2017. |
Office Action for U.S. Appl. No. 15/402,945, dated Apr. 5, 2017. |
Office Action for U.S. Appl. No. 15/271,488, dated Apr. 19, 2017. |
Final Office Action for U.S. Appl. No. 14/217,066, dated Apr. 21, 2017. |
Office Action for U.S. Appl. No. 14/216,986 dated Apr. 26, 2017. |
Office Action for U.S. Appl. No. 13/801,171, dated Jun. 14, 2017. |
Office Action for U.S. Appl. No. 14/017,159, dated Jun. 29, 2017. |
Notice of Allowance for U.S. Appl. No. 15/270,333, dated Jul. 5, 2017. |
Final Office Action for U.S. Appl. No. 13/800,917, dated Jul. 13, 2017. |
Notice of Allowance for U.S. Appl. No. 13/801,234, dated Jul. 5, 2017. |
Notice of Allowance for U.S. Appl. No. 14/217,066, dated Jul. 14, 2017. |
Final Office Action for U.S. Appl. No. 14/518,909, dated Jul. 19, 2017. |
Final Office Action for U.S. Appl. No. 13/801,121, dated Sep. 15, 2016. |
Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 17, 2015. |
Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 19, 2016. |
Notice of Allowance for U.S. Appl. No. 15/293,751, dated Aug. 4, 2017. |
Advisory Action for U.S. Appl. No. 14/189,948, dated Jul. 28, 2017. |
Final OA for U.S. Appl. No. 13/801,256, dated Aug. 15, 2014. |
Final OA for U.S. Appl. No. 13/801,256, dated Feb. 18, 2015. |
Advisory Action for U.S. Appl. No. 13/801,256, dated Dec. 5, 2014. |
Office Action for U.S. Appl. No. 13/801,256, dated Jan. 12, 2016. |
Final Office Action for U.S. Appl. No. 13/801,256, dated Aug. 16, 2016. |
Office Action for U.S. Appl. No. 13/801,256, dated Aug. 18, 2017. |
Office Action for U.S. Appl. No. 13/622,702, dated Aug. 31, 2017. |
Office Action for U.S. Appl. No. 12/945,888, dated Sep. 1, 2017. |
Office Action for U.S. Appl. No. 14/017,150, dated Sep. 7, 2017. |
Notice of Allowance for U.S. Appl. No. 14/189,948, dated Sep. 13, 2017. |
Office Action for U.S. Appl. No. 15/138,086, dated Oct. 19, 2017. |
Notice of Allowance for U.S. Appl. No. 15/402,945 dated Nov. 21, 2017. |
Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 13, 2017. |
Final Office Action for U.S. Appl. No. 15/271,488, dated Dec. 21, 2017. |
Office Action for U.S. Appl. No. 15/671,133, dated Dec. 22, 2017. |
Final Office Action for U.S. Appl. No. 14/216,986, dated Dec. 26, 2017. |
Restriction Requirement for U.S. Appl. No. 15/427,307, dated Jan. 17, 2018. |
Office Action for U.S. Appl. No. 15/798,363, dated Jan. 26, 2018. |
Office Action for U.S. Appl. No. 15/427,291, dated Jan. 29, 2018. |
Final Office Action for U.S. Appl. No. 14/017,159, dated Feb. 1, 2018. |
Final Office Action for U.S. Appl. No. 13/622,702, dated Feb. 22, 2018. |
Office Action for U.S. Appl. No. 15/811,654, dated Feb. 22, 2018. |
Final Office Action for U.S. Appl. No. 13/622,702, dated Feb. 27, 2018. |
Number | Date | Country | |
---|---|---|---|
20140094316 A1 | Apr 2014 | US |