A portion of the disclosure of this patent document contains material which 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 2015, WMS Gaming, Inc.
Embodiments of the inventive subject matter relate generally to wagering game systems, and more particularly to devices that integrate social contact identifiers into wagering games of wagering game systems.
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.
Embodiments of the invention are illustrated in the Figures of the accompanying drawings in which:
This description of the embodiments is divided into four sections. The first section provides an introduction to embodiments of the invention, while the second section describes example operating environments. The third section describes example operations performed by some embodiments. The fourth section presents some general comments.
This section provides an introduction to some embodiments of the invention.
Wagering games are expanding in popularity. Many gamers are demanding greater access to wagering games and content related to wagering games. As a result, some wagering game companies have created social network sites that provide a way for wagering game enthusiasts to congregate and share their passion for wagering games.
A social network site allows social network users to create online personas. The social network site allows users to create user accounts with one or more unique identifiers that represent the online persona. One example of a unique identifier is an “avatar”. Avatars are graphical, “cartoon-like” depictions of a social network persona. These online personas and associated avatars add to the fun of belonging to a social network. Hence, embodiments of the invention enable wagering game companies to combine the fun of social networks with the enjoyment and excitement derived from playing wagering games.
The mobile machine 106 presents a wagering game. In some embodiments, the wagering game has graphics (e.g., icons) on a display 114. The icons represent elements of the wagering game. In some embodiments, the icons are used to represent the outcome of the game, such as the icons on a slots reel, as shown in
By displaying the avatar identifier 108 in the wagering game, the integrator 102 has integrated a reference to one of the player's friends into the wagering game. Therefore, the integrator 102 combines a fun element of social networks into the fun and excitement of wagering games. In addition, the integrator 102 can further enhance the experience by providing rewards to the friends whose identifier appeared in the wagering game while rewarding the game player as well. For example, the integrator 102 can generate a reward and assign it to an account 116 belonging to the friend whose identifier was integrated into the wagering game. When the friend accesses the account 116 via a computer 138, or wagering game, the friend can see the reward 118 displayed on the account 116. The player can also be rewarded. For example, when the friend's identifier 108 appeared in the wagering game, the mobile machine 106 could treat the identifier 108 as a “wild card” type of icon. The wild card icon could represent any of the normal icons that appear, thus potentially affecting the outcome of the game. For instance, if a row of three apple icons were necessary for a “win” of the wagering game, a row with two apple icons and a “wild card” identifier 108 would be equivalent to three apples icons. Therefore, the player would win the game. Furthermore, the integrator 102 can also provide rewards to the player's social network account.
According to some embodiments of the invention, the social contact identifier integrator 102 can provide a host of different rewards. The following non-exhaustive list enumerates some possible rewards:
Although
This section describes example operating environments and networks and presents structural aspects of some embodiments. More specifically, this section includes discussion about wagering game networks, social contact identifier integrator architectures, wagering game machine architectures, wagering game machine communications networks, social network features, and mobile wagering game machines.
The wagering game machines 206, 211, 212 described herein can take any suitable form, such as floor standing models (e.g., 212), handheld mobile units (e.g., 206), bar-top models, workstation-type console models, surface computing machines (e.g., 211), etc. Further, the wagering game machines 206, 212 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 206, 211, 212 and wagering game servers 218 work together such that wagering game machines 206, 211, 212 can be operated as a thin, thick, or intermediate client. For example, one or more elements of game play may be controlled by the wagering game machines 206, 212 (client) or the wagering game servers 218 (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 218 can perform functions such as determining game outcome or managing assets, while the wagering game machines 206, 211, 212 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 206, 211, 212 can determine game outcomes and communicate the outcomes to the wagering game server 218 for recording or managing a player's account.
In some embodiments, either the wagering game machines 206, 211, 212 (client) or the wagering game server(s) 218 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) 218) or locally (e.g., by the wagering game machines 206, 211, 212). 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.
The wagering game network 200 also includes a reward server 232, a community server 234, and one or more client devices 236, 238. The wagering game network 200 also includes a social contact identifier integrator 202. The social contact identifier integrator 202 can integrate social contact identifiers into wagering games. The social contact identifier integrator 202 may be internal or external to a casino 220 and may interact with any suitable wagering game network component to integrate social contact identifiers into wagering games, to assign rewards to reward recipients' accounts, and to send notification messages to reward recipients' accounts and devices. In some embodiments, the social contact identifier integrators 202 can reside inside any of the network components (e.g., wagering game server 218, community server 234, etc.)
Any of the wagering game network components (e.g., the wagering game machines, servers, etc.) can include hardware and machine-readable media including instructions for performing the operations described herein. Machine-readable media includes any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine (e.g., a wagering game machine, computer, etc.). For example, tangible machine-readable media includes read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory machines, etc. Machine-readable media also includes any media suitable for transmitting software over a network.
In
The social contact identifier integrator architecture 300 also includes a rewards controller 314 configured to control the assignment of rewards to user accounts, to notify user accounts of rewards, and to allow user accounts redeem rewards.
The social contact identifier integrator architecture 300 also includes an integration rules store 316 configured to store rules regarding the integration of social network user account identifiers into wagering games.
The social contact identifier integrator architecture 300 also includes a user settings store 318 configured to notify user accounts of rewards according to user settings.
The social contact identifier integrator architecture 300 also includes an authorization information store 320 configured to store unique identification information (user account names, passwords, security keys, serial numbers, media access control addresses, etc.) that the social identifier integrator 302 can use to verify and control authorization of social networks, control commands, etc.
The CPU 426 is also connected to an input/output (“I/O”) bus 422, which can include any suitable bus technologies, such as an AGTL+ frontside bus and a PCI backside bus. The I/O bus 422 is connected to a payout mechanism 408, primary display 410, secondary display 412, value input device 414, player input device 416, information reader 418, and storage unit 430. The player input device 416 can include the value input device 414 to the extent the player input device 416 is used to place wagers. The I/O bus 422 is also connected to an external system interface 424, which is connected to external systems 404 (e.g., wagering game networks). The external system interface 424 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 422 is also connected to a location unit 438. The location unit 438 can create player information that indicates the wagering game machine's location/movements in a casino. In some embodiments, the location unit 438 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 438 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 one embodiment, the wagering game machine 406 can include additional peripheral devices and/or more than one of each component shown in
In one embodiment, the wagering game machine 406 includes a social contact identifier integrator 437. The social contact identifier integrator 437 can process communications, commands, or other information, where the processing can integrate social contact identifiers into wagering games, provide rewards, send notifications of the rewards, and control rewards redemption.
Furthermore, any component of the wagering game machine 406 can include hardware, firmware, and/or machine-readable media including instructions for performing the operations described herein.
The social network account 503 also includes a list of social contact “friends” 516, which can contain one or more social contact cards 518. These social contact cards 518 contain information about other social network account owners that have a social relationship to the owner of the social network account 503. The social contact cards could be card shaped, cubed shaped, etc. Information on the cards can be static or dynamic and can include links to information. The social contact cards can have information on the front, back, or any surface. Each of the social contact cards 518 can include identifiers 520, such as avatars, that help to uniquely identify the social contact. The social network account 503 also includes additional buttons 532, such as to remove a social contact card 518 from the list of friends or to check to see which friends have received rewards. In some embodiments, the list of friends 516 might be limited to those that have played wagering games within a set period of time.
The social network account 503 also includes an invitation screen for inviting or accepting an invitation from another social network account to be added to the list of friends 516. The social network account 503 also includes a notification settings box 526 for storing user settings about notifying the account owner of rewards. For example, the notification settings box 526 can include buttons 528, 530 indicating how the account owner should be notified of rewards (e.g., in real-time, upon login). A field 529 indicates a location for contact information (e.g., cell phone number, email address, etc.) for where to send the notification message.
The social network account 503 can be created and stored on a community server 534, also connected to the communications network 522. Any social network accounts associated with social contacts in the friends list 516 can also be stored on the community server 534. A social contact identifier integrator 502 can work in conjunction with the community server 534 to access and modify social network accounts. Other devices connected to the communications network 522, such as the computer 536, can access the social network account 503 via the communication network 522.
The social contact identifier integrator 602 can assign rewards to social network accounts on the community server 634. The social contact identifier integrator 602 can work in conjunction with a reward server 632 to generate, assign, store and redeem rewards.
The social network account 703 can be created and stored on a community server 734, also connected to the communications network 722. Any social network accounts associated with social contacts in the friends list 716 can also be stored on the community server 734. A social contact identifier integrator 702 can work in conjunction with the community server 734 to access and modify social network accounts. Other devices connected to the communications network 722, such as the computer 736, can access the social network account 703 via the communication network 722.
In addition, the social network account 703 includes a rewards redemption screen 726 to allow a reward recipient to redeem rewards, such as “spendable” points, or other forms of spendable value. The reward server 732 can work in conjunction with network devices, like the wagering game machine 706 or the social contact identifier integrator 702 to allow a reward recipient to redeem awards. In some embodiments, rewards can be spent in a casino on wagering game activities, like playing wagering games or ordering casino services. In some embodiments, the rewards can be spent, transferred, exchanged, etc., for products or services that are not wagering game related. For example, the computer 736 can connect to the community server 734 to access the spendable rewards in the social network account 703. Then, the computer 736 can spend the rewards on a third party web site, hosted by a third party web server 740.
According to some embodiments of the invention, the social contact identifier integrator 702, or other network devices, can allow reward recipients to use rewards in many ways. The following non-exhaustive list enumerates some possible ways rewards can be used.
Although
This section describes operations associated with some embodiments of the invention. In the discussion below, the flow diagrams will be described with reference to the block diagrams presented above. 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 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 less than all the operations shown in any flow diagram.
The flow 900 continues at processing block 904, where the social contact identifier integrator displays the social contact identifier as part of the wagering game. The social contact identifier integrator can randomly displays the social contact identifier as part of the game elements. For example, the social contact identifier integrator can display the social contact identifier on any part of the wagering game machine that presents the wagering game, such as on game reels, on game characters, on bonus sections, on point trackers, and on results displays. The social contact identifier integrator can also display the social contact identifier on machines that are connected to the wagering game machine, such as on peripheral devices, external monitors, etc.
The flow 900 continues at processing block 906, where the social contact identifier integrator determines one or more rewards to provide to one or more reward recipient accounts. In some embodiments, the reward recipients can be the player and the social contact whose identifier appeared in the wagering game. Rewards can be varied, as described further above. A rewards server can assist the social contact identifier integrator in determining rewards. The social contact identifier integrator can determine the values of rewards based on various factors. For example, the social contact identifier integrator can determine reward values based on the habits of a user. For example, the social contact identifier integrator can increase reward values to incentivize play on a single game type that a user plays frequently. The social contact identifier integrator could also increase reward values, such as with a bonus amount, for new games to incentivize players to try new games. On the other hand, the social contact identifier integrator can decrease reward values to discourage play on a single game. Furthermore, the social contact identifier integrator can determine more than one reward. The rewards can be separate and distinct from each other. For example, the social contact identifier integrator can determine one reward to provide two separate and distinct rewards to provide at once-one to the game player's account and one reward to provide to the account of the social contact whose identifier appeared in the wagering game.
The flow 900 continues at processing block 908, where the social contact identifier integrator determines whether additional activity is required to obtain the reward. For example, the social contact identifier integrator could require a performer (e.g., the player, the potential reward recipient, any other person or group of people associated with the reward, etc.), to perform additional steps to obtain the reward. The social contact identifier integrator could require the performer to perform the additional activity outside of the wagering game. For example, the social contact identifier integrator could require a performer to perform a scavenger hunt to obtain the reward. The scavenger hunt could include requiring that the performer play a certain series of games. Hence, the activity could be performed without having to leave a game terminal. In some embodiments, the social contact identifier integrator could require the activity performer, or group of performers, to perform activities beyond a casino, on the Internet, or anywhere else the outcome of the activity can be reported electronically to the social network identifier integrator. If the social contact identifier integrator requires the performer to perform additional activity before assigning the reward, the process continues at block 910. Otherwise, the process continues at block 914.
The flow 900 continues at processing block 910, where the social contact identifier integrator presents instructions for performing the additional activity. The social contact identifier integrator can provide instructions to the performer about how to obtain the determined reward.
The flow 900 continues at processing block 912, where the social contact identifier integrator determines that the additional activity is completed. The social contact identifier integrator can monitor the required additional activity to look for a predetermined outcome that indicates completion of the additional activity. Once the performer achieves the outcome, then the social contact identifier integrator will recognize the outcome and determine that the additional activity is complete.
The flow 900 continues at processing block 914, where the social contact identifier integrator assigns the one or more rewards to the one or more reward recipient accounts. The social contact identifier integrator can assign the rewards to reward recipients in different ways. If the reward recipient has a user accounts on a social network, the social contact identifier integrator can assign the reward to the user account. In some embodiments, however, the social contact identifier integrator can assign the rewards in other ways, such as via email messages, through printed vouchers or coupons, etc. Hence, a specific user account is not required.
The flow 1000 continues at processing block 1004, where the social contact identifier integrator selects a first social network user account associated with a wagering game player.
The flow 1000 continues at processing block 1006, where the social contact identifier integrator determines one or more social contact identifiers of one or more second social network user accounts associated with the first social network user account.
The flow 1000 continues at processing block 1008, where the social contact identifier integrator gathers the one or more social contact identifiers into a group. In some embodiments, the social contact identifier integrator can gather the identifiers on a client. For example, the social contact identifier integrator could download the social contact identifiers onto the client to create the group on the client. To ensure that resources on the client are not over burdened, the social contact identifier integrator could download social contact identifiers only during less client intense activity. On the other hand, in some embodiments, the social contact identifier integrator can gather the identifiers on a server. The social contact identifier integrator can gather the social contact identifiers one by one from a community server into a group that is left on a wagering game server. The wagering game server can be in constant communication with the community server to update the group of social contact identifiers if new social contacts are added or removed from a player's account.
The flow 1000 continues at processing block 1010, where the social contact identifier integrator selects at least one of the social contact identifiers from the group. The social contact identifier integrator can randomly select the social contact identifier from the group. The social contact identifier integrator can utilize a random selection algorithm that watches the progress of the wagering game. As game play progresses, when a graphical game play element is going to appear on the wagering game display screen, the social contact identifier integrator decide to use a graphical social contact identifier, like an avatar, in place of the graphical game play element. The social contact identifier integrator can select the social contact identifier based on “mystery events”, which are criteria unknown to the wagering game player. Mystery events can range from pure randomness to other criteria built into the wagering game programming.
The flow 1000 continues at processing block 1012, where the social contact identifier integrator randomly inserts the social contact identifier into the wagering game in connection with a wagering game play element. For example, some wagering games utilize reels, or depictions of reels, with icons on the reels that line up to determine a game outcome. For example, a wagering game may contain icons of cherries, bananas and apples on the reels. The social contact identifier integrator can randomly select and replace the depiction of the normal icon (e.g. cherry, apple, banana, etc.) with the social contact identifier (e.g. an avatar). As a result, for the game play, such as for one or more spins of the reel, the identifier appears in place of the normal icon. In some embodiments, the social contact identifier integrator might not entirely replace the normal icon, but could integrate the social contact identifier with the graphic (e.g., place an image of an avatar on the apple). In some embodiments, the social contact identifier may appear in a secondary display, such as part of a game bonus in connection with the wagering game. In some embodiments, the replacement may not be random.
The flow 1000 continues at processing block 1014, where the social contact identifier integrator alters the wagering game payout calculation depending on the placement of the social contact identifier. In some embodiments, the wagering game has play elements that determine the game outcome. For example, as described in the paragraph above, some wagering games utilize reels, or depictions of reels, with icons on the reels that line up to determine a game outcome. For example, as described previously, a wagering game may contain icons of cherries, bananas and apples. The object of the wagering game may be to line up three cherries in a row, which would mean a “win”, and therefore a payout. Suppose that a player spins the reels and the social contact identifier integrator randomly replaces an apple icon with a social contact identifier. The game rules could treat the social contact identifier as a “wild card” type of icon, meaning that it could be used as a cherry icon if desired. Therefore, if two cherries lined up in the win row, and if a social contact identifier filled in the third icon spot on that row, then the game play would result in a “win”, and the payout would be affected. The payout is affected because the apple icon would not have resulted in a win. However, because the “wild card” social contact identifier appeared, and was treated as a wild card type of icon, then the game did result in a win. If, however, a social contact identifier integrator randomly inserted the social contact identifier over the apple icon, but the social contact identifier did not line up in the “win” row, then the social contact identifier would not have affected the outcome of the game. Nevertheless, because the social contact identifier was inserted into the game play, it could still be used to generate some form of reward, as described in block 1014.
The flow 1000 continues at processing block 1016, where the social contact identifier integrator determines one or more rewards to provide to any one of the first and second user accounts. Specifically, the social contact identifier integrator can determine one or many types of rewards, as described further above. The reward recipient can be any one of the first and second social network user accounts, specifically the social network user account that is a related to the inserted social network identifier.
The flow 1000 continues at processing block 1018, where the social contact identifier integrator writes the reward to any one of the first and second user accounts.
The flow 1000 continues at processing block 1020, where the social contact identifier integrator sends a notification message of the reward to any one of the first and second user accounts. In some embodiments, the social contact identifier integrator notifies the recipients of the rewards according to user settings set within the recipients social network user account. For example, the reward recipient's account can have a user setting that indicates that the social network identifier integrator should notify the reward recipient immediately of any rewards. The user settings could also indicate contact instructions, such as phone number to which the social network identifier integrator can send a text message. As a result, the social network identifier integrator could read that setting and accordingly send a notification of the reward via text message to the reward recipient's cell phone. Hence, the reward recipient can earn and receive notifications of rewards even when the reward recipient is not connected to the wagering game network.
The flow 1000 continues at processing block 1022, where the social contact identifier integrator allows any one of the first and second user accounts to redeem the reward. The social contact identifier integrator can work in conjunction with a rewards server to allow reward recipients to redeem rewards through their user accounts. Rewards can be redeemed in many ways, some of which are described in
The flow 1100 continues at processing block 1104, where the community server associates a first social contact identifier with the first account. The first social contact identifier identifies a user associated with the first account. The first social contact identifier can be a unique identifier of the user. For example, the social contact identifier can be an avatar chosen by the user assigned to the first user account.
The flow 1100 continues at processing block 1106, where the community server determines a second user account to associate with the first account.
The flow 1100 continues at processing block 1108, where the community server determines whether mutual acceptance is required by the first and second accounts before associating the second user account to the first user account. In some embodiments, both user accounts need to be in agreement regarding any associations, and the process continues at block 1110. In other embodiments, however, where mutual agreement is not required, the process continues at block 1114.
The flow 1100 continues at processing block 1110, where the community server sends an invitation to the second user account to be associated with the first user account.
The flow 1100 continues at processing block 1112, where the community server receives from the second account an indication of acceptance to the invitation. If there is no mutual acceptance, then the social contact identifier integrator can send a message to the inviting user account that the invitee user account rejected the invitation. If, however, there is mutual acceptance, the process continues.
The flow 1100 continues at processing block 1114, where the community server associates a second social contact identifier from the second account to the first account. The second social contact identifier from the second account identifies a user associated with the second account. The second social contact identifier can be a unique identifier of the social contact. For example, the social contact identifier can be an avatar chosen by the user assigned to the second user account.
The mobile wagering game machine 1200 includes several input/output devices. In particular, the mobile wagering game machine 1200 includes buttons 1220, audio jack 1208, speaker 1214, display 1216, biometric device 1206, wireless transmission devices 1212 and 1224, microphone 1218, and card reader 1222. Additionally, the mobile wagering game machine can include tilt, orientation, ambient light, or other environmental sensors.
In one embodiment, the mobile wagering game machine 1200 uses the biometric device 1206 for authenticating players, whereas it uses the display 1216 and speakers 1214 for presenting wagering game results and other information (e.g., credits, progressive jackpots, etc.). The mobile wagering game machine 1200 can also present audio through the audio jack 1208 or through a wireless link such as Bluetooth.
In one embodiment, the wireless communication unit 1212 can include infrared wireless communications technology for receiving wagering game content while docked in a wager gaming station. The wireless communication unit 1224 can include an 802.11G transceiver for connecting to and exchanging information with wireless access points. The wireless communication unit 1224 can include a Bluetooth transceiver for exchanging information with other Bluetooth enabled devices.
In one embodiment, the mobile wagering game machine 1200 is constructed from damage resistant materials, such as polymer plastics. Portions of the mobile wagering game machine 1200 can be constructed from non-porous plastics which exhibit antimicrobial qualities. Also, the mobile wagering game machine 1200 can be liquid resistant for easy cleaning and sanitization.
In some embodiments, the mobile wagering game machine 1200 can also include an input/output (“I/O”) port 1230 for connecting directly to another device, such as to a peripheral device, a secondary mobile machine, etc. Furthermore, any component of the mobile wagering game machine 1200 can include hardware, firmware, and/or machine-readable media including instructions for performing the operations described herein.
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 of the invention, 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 is a continuation of, and claims priority benefit of, U.S. application Ser. No. 13/717,222, filed on Dec. 17, 2012. U.S. application Ser. No. 13/717,222 is a continuation of, and claims priority benefit to U.S. application Ser. No. 12/678,206, which is a National Stage of International Application No. PCT/US08/77310 filed Se. 23, 2008. The International Application No. PCT/US08/77310 claims priority benefit to U.S. Provisional Application No. 60/974,626 filed Sep. 24, 2007.
Number | Name | Date | Kind |
---|---|---|---|
5470079 | Lestrange et al. | Nov 1995 | A |
5823879 | Goldberg et al. | Oct 1998 | A |
6068552 | Walker et al. | May 2000 | A |
6110041 | Walker et al. | Aug 2000 | A |
6117009 | Yoseloff | Sep 2000 | A |
6142872 | Walker et al. | Nov 2000 | A |
6159096 | Yoseloff | Dec 2000 | A |
6254483 | Acres | Jul 2001 | B1 |
6342010 | Slifer | Jan 2002 | B1 |
6350199 | Williams et al. | Feb 2002 | B1 |
6358150 | Mir et al. | Mar 2002 | B1 |
6364765 | Walker et al. | Apr 2002 | B1 |
6394899 | Walker | May 2002 | B1 |
6520856 | Walker et al. | Feb 2003 | B1 |
6628939 | Paulsen | Sep 2003 | B2 |
6692353 | Walker et al. | Feb 2004 | B2 |
6699125 | Kirmse et al. | Mar 2004 | B2 |
6769986 | Vancura | Aug 2004 | B2 |
6843724 | Walker et al. | Jan 2005 | B2 |
7040987 | Walker et al. | May 2006 | B2 |
7169052 | Beaulieu et al. | Jan 2007 | B2 |
7240093 | Danieli et al. | Jul 2007 | B1 |
7311608 | Danieli et al. | Dec 2007 | B1 |
7458894 | Danieli et al. | Dec 2008 | B2 |
7559838 | Walker et al. | Jul 2009 | B2 |
7938727 | Konkle | May 2011 | B1 |
8167712 | Sarkar et al. | May 2012 | B2 |
8974289 | Allen et al. | Mar 2015 | B2 |
20020042296 | Walker et al. | Apr 2002 | A1 |
20020090985 | Tochner et al. | Jul 2002 | A1 |
20020111209 | Walker et al. | Aug 2002 | A1 |
20020142846 | Paulsen | Oct 2002 | A1 |
20020183105 | Cannon et al. | Dec 2002 | A1 |
20030003988 | Walker et al. | Jan 2003 | A1 |
20030224852 | Walker et al. | Dec 2003 | A1 |
20040180712 | Forman et al. | Sep 2004 | A1 |
20050043092 | Gauselmann | Feb 2005 | A1 |
20050054438 | Rothschild et al. | Mar 2005 | A1 |
20050071481 | Danieli | Mar 2005 | A1 |
20050170890 | Rowe et al. | Aug 2005 | A1 |
20050209001 | Moshal | Sep 2005 | A1 |
20050277469 | Pryzby et al. | Dec 2005 | A1 |
20050277474 | Barry | Dec 2005 | A1 |
20050289056 | Guinn | Dec 2005 | A1 |
20060160614 | Walker et al. | Jul 2006 | A1 |
20060247039 | Lerner et al. | Nov 2006 | A1 |
20060264257 | Jaffe et al. | Nov 2006 | A1 |
20060271959 | Jacoby et al. | Nov 2006 | A1 |
20070002057 | Danzig et al. | Jan 2007 | A1 |
20070015584 | Frenkel | Jan 2007 | A1 |
20070054728 | Hood | Mar 2007 | A1 |
20070060380 | McMonigle et al. | Mar 2007 | A1 |
20070072677 | Lavoie et al. | Mar 2007 | A1 |
20070077988 | Friedman | Apr 2007 | A1 |
20070155507 | Gatto et al. | Jul 2007 | A1 |
20080004097 | Maya et al. | Jan 2008 | A1 |
20080009344 | Graham et al. | Jan 2008 | A1 |
20080064492 | Oosthoek | Mar 2008 | A1 |
20080102916 | Kovacs et al. | May 2008 | A1 |
20080214308 | Lyons et al. | Sep 2008 | A1 |
20080234049 | Leblanc et al. | Sep 2008 | A1 |
20080272541 | Walker et al. | Nov 2008 | A1 |
20090036196 | Ansari et al. | Feb 2009 | A1 |
20090093290 | Lutnick et al. | Apr 2009 | A1 |
20090117989 | Arezina et al. | May 2009 | A1 |
20090131163 | Arbogast et al. | May 2009 | A1 |
20090163267 | Fine | Jun 2009 | A1 |
20090170608 | Herrmann et al. | Jul 2009 | A1 |
20100019453 | Oakes et al. | Jan 2010 | A1 |
20100203963 | Allen et al. | Aug 2010 | A1 |
20100210358 | Csurka et al. | Aug 2010 | A1 |
20100279764 | Allen et al. | Nov 2010 | A1 |
20110092275 | Gagner et al. | Apr 2011 | A1 |
20110105229 | Sitrick | May 2011 | A1 |
20110143830 | Fine | Jun 2011 | A1 |
20110237321 | Fine | Sep 2011 | A1 |
20110300925 | Adiraju et al. | Dec 2011 | A1 |
20120094737 | Barclay et al. | Apr 2012 | A1 |
20120282995 | Allen et al. | Nov 2012 | A1 |
20130150150 | Allen et al. | Jun 2013 | A1 |
20130316818 | Earley et al. | Nov 2013 | A1 |
20140148245 | Allen et al. | May 2014 | A1 |
Number | Date | Country |
---|---|---|
2490605 | Nov 2012 | GB |
2009042563 | Apr 2009 | WO |
2009086489 | Jul 2009 | WO |
Entry |
---|
“AU Application No. 2012202623 Examination Report”, Apr. 15, 2013, 8 pages. |
“PCT Application No. PCT/US08/77310 International Preliminary Report on Patentability”, Apr. 1, 2010, 6 pages. |
“PCT Application No. PCT/US08/77310 International Preliminary Report on Patentability”, Sep. 14, 2010, 4 pages. |
“PCT Application No. PCT/US08/77310 International Search Report”, Dec. 8, 2008, 7 pages. |
“PCT Application No. PCT/US08/88381 International Preliminary Report on Patentability”, Aug. 16, 2010, 12 pages. |
“PCT Application No. PCT/US08/88381 International Search Report”, Feb. 24, 2009, 10 pages. |
“UK Application No. 1208182.4 Examination Report”, Dec. 17, 2013, 5 pages. |
“UK Application No. 1208182.4 Examination Report”, Sep. 3, 2012, 9 Pages. |
“U.S. Appl. No. 12/678,206 Office Action”, Mar. 30, 2012, 21 pages. |
“U.S. Appl. No. 12/810,685 Final Office Action”, Dec. 26, 2012, 10 pages. |
“U.S. Appl. No. 12/810,685 Office Action”, Aug. 1, 2012, 12 pages. |
“U.S. Appl. No. 12/810,685 Office Action”, Dec. 23, 2011, 15 pages. |
“U.S. Appl. No. 13/464,964 Office Action”, May 30, 2013, 21 pages. |
“U.S. Appl. No. 13/717,222 Final Office Action”, Jul. 7, 2014, 6 Pages. |
“U.S. Appl. No. 13/717,222 Office Action”, Mar. 17, 2014, 8 Pages. |
“U.S. Appl. No. 13/826,335 Office Action”, Nov. 20, 2014, 15 Pages. |
Prizehearts, LLC, “Lotto Love and Pals Available Next Generation Keno/Lottery Software”, 24-7 Press Release, Apr. 5, 2006, 2 pages. |
Co-pending U.S. Appl. No. 14/171,596, filed Feb. 3, 2014, 42 pages. |
Co-pending U.S. Appl. No. 13,826,335, filed Mar. 14, 2013, 30 pages. |
Co-pending U.S. Appl. No. 13,707,222, filed Dec. 17, 2012, 44 pages. |
Co-pending U.S. Appl. No. 13/464,964, filed May 5, 2012, 44 pages. |
“U.S. Appl. No. 12/810,685 Office Action”, Mar. 17, 2015, 14 Pages. |
“U.S. Appl. No. 14/171,596 Office Action”, Feb. 20, 2015, 10 Pages. |
Number | Date | Country | |
---|---|---|---|
20150170464 A1 | Jun 2015 | US |
Number | Date | Country | |
---|---|---|---|
60974626 | Sep 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13717222 | Dec 2012 | US |
Child | 14610660 | US | |
Parent | 12678206 | US | |
Child | 13717222 | US |