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 2012, WMS Gaming, Inc.
Embodiments of the inventive subject matter relate generally to wagering game systems and networks that, more particularly, responsible gaming systems and networks.
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.
However, for some people, playing wagering games in excess can lead to negative issues and problems with over spending and addictive gambling behaviors. Wagering game providers are concerned with these negative issues that face the gaming industry and are attempting to determine ways to assist wagering game players to gamble responsibly.
Embodiments are illustrated in the Figures of the accompanying drawings in which:
This description of the embodiments is divided into five sections. The first section provides an introduction to embodiments. The second section describes example operating environments while the third section describes example operations performed by some embodiments. The fourth section describes additional example operating environments while the fifth section presents some general comments.
This section provides an introduction to some embodiments.
As mentioned previously, wagering game providers face challenges determining ways to assist wagering game players to gamble responsibly. Embodiments of the inventive subject matter, however, present solutions to many of those challenges. Embodiments of the inventive subject matter present ways to encourage and enforce responsible gaming in an account based gaming system. Some embodiments can present a player account's actual account statistics during a wagering game session. Some embodiments can present wagering statistics and trends in reports. The player can select from report templates to present and organize the account statistics. In some embodiments, the system can enforce limits and encourage players to restrict gaming activity when those limits are exceeded or close to being exceeded. For example, some embodiments present incentives to reduce gaming activity when the limits are exceeded or close to being exceeded. These embodiments, and many others, are described in further detail below. For example,
In some embodiments herein a player may be referred to interchangeably as a player account, or vice versa. Account based gaming systems often utilize player accounts when transacting and performing activities, at the computer level, that are initiated by players. Therefore a “player account” is often referred to herein as a representative of the player at a computerized level. Therefore, for brevity, to avoid having to describe the interconnection between player and player account in every instance, a “player account” may be referred to herein in either context. Further, in some embodiments herein, the word “gaming” is used interchangeably with the word “gambling”.
The wagering game machine 160 can present the financial report 120 simultaneously while presenting a wagering game in the wagering game display 110, between wagers, upon request of the player account, or at any time during the wagering game session, to provide a perceptible indicator of the amounts of money that the player account has spent, won, lost, transacted, etc., on gambling. The system 100 can present the financial report 120 in any location on the wagering game machine 160, or on any other device, that is viewable during the wagering game session, for example, (1) as a part of the display 101 (e.g., in a separate window or frame from the wagering game), (2) on a peripheral device connected to the wagering game machine 160 (e.g., on a box-top monitor, on a side monitor, etc.), (3) on a personal device wirelessly connected to the wagering game machine 160 (e.g., via text messages on a cell phone, via spoken amounts on a personal digital assistant), (4) on a secured website, etc. The system 100, thus, imposes the financial report 120, or some other indication of the accounting data, in an intrusive manner on the gambling activity to ensure that the player account has notification that gambling activity may be exceeding, or has exceeded, responsible gambling boundaries.
The system 100 can present a report selection control 102 to select a report template that controls the information presented in the financial report 120. The report template can be a stored template, or other form of metadata, that can select and present account information tracked and stored by the account server 170, the wagering game machine 160, and the wagering game server 150. In some embodiments, the account server 170 can store the report template and other preferences related to the financial report 120. In other embodiments, other devices (e.g., the wagering game machine 160, the wagering game server 150, etc.), can store the report templates and other preferences related to the financial report 120. The report template can change the type of information presented on the financial report 120, including different transaction types (e.g., withdrawals, bets, deposits, etc.), different graphs (e.g., money transacted, trends, etc.), transaction limits, warnings, suggestions for conserving funds, incentives for performing responsible gambling activity, game play statistics related to financial transactions, and other such information. For instance, a specific report template may present changes in an account balance, including a textual representation of the change in the account balance via a beginning balance value 104, an ending balance value 105, and a balance difference value 106. The balance difference value 106 indicates how much the account balance has changed for the time period selected in a time period control 103. The time period control 103 may include a dropdown, or other selection menu, that a player account can use to select time period parameters for the financial statistics that are presented in the financial report 120. The report template can also present graphical representations of the change in the account balance via a balance change chart 108. The balance change chart 108 can illustrate numerical account balance values in an easily viewable format so that the player account can quickly view and comprehend gambling trends for the selected time period.
The system 100 can also present panels or controls for using the report (e.g., in a wagering game machine interface, on a website interface, on a kiosk interface, etc.). For example, the system 100 can present a report export panel 121 with a report destination dropdown 109 and a report submission control 111. The report destination dropdown 109 can include selection options of where to send the financial data in the financial report 120 (e.g., a printer, a bill, an email, an export file, a sponsor friend or family member account, an administrative account, a website, a personal storage device, etc.). The player account can select the report submission control 111 to transmit the financial data. In some embodiments, the system 100 can use export templates for presenting the financial report 120 on a final medium (e.g., a final destination document, file, disk, etc.). The export templates can also convert the data into formats that can be used in various data sources and file formats (e.g., comma separated value, dBase, etc.). In some embodiments, the system 100 can generate reports by themes or topics. The system 100 can also show positive information about game play (e.g., amounts won over a time period).
Although
In some embodiments, wagering game machines and wagering game servers work together such that wagering game machines 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 (client) or the wagering game servers (server). Game play elements can include executable game code, lookup tables, configuration files, game outcome, audio or visual representations of the game, game assets or the like. In a thin-client example, the wagering game server can perform functions such as determining game outcome or managing assets, while the wagering game machines can present a graphical representation of such outcome or asset modification to the user (e.g., player). In a thick-client example, the wagering game machines can determine game outcomes and communicate the outcomes to the wagering game server for recording or managing a player's account.
In some embodiments, either the wagering game machines (client) or the wagering game server(s) can provide functionality that is not directly related to game play. For example, account transactions and account rules may be managed centrally (e.g., by the wagering game server(s)) or locally (e.g., by the wagering game machines). Other functionality not directly related to game play may include power management, presentation of advertising, software or firmware updates, system quality or security checks, etc.
This section describes example operating environments and networks and presents structural aspects of some embodiments. More specifically, this section includes discussion about wagering game system architectures.
The wagering game system architecture 200 can also include a wagering game server 250 configured to control wagering game content, provide random numbers, and communicate wagering game information, account information, and other information to and from a wagering game machine 260. The wagering game server 250 can include a content controller 251 configured to manage and control content for the presentation of content on the wagering game machine 260. For example, the content controller 251 can generate game results (e.g., win/loss values), including win amounts, for games played on the wagering game machine 260. The content controller 251 can communicate the game results to the wagering game machine 260. The content controller 251 can also generate random numbers and provide them to the wagering game machine 260 so that the wagering game machine 260 can generate game results. The wagering game server 250 can also include a content store 252 configured to contain content to present on the wagering game machine 260. The wagering game server 250 can also include an account manager 253 configured to control information related to player accounts. For example, the account manager 253 can communicate wager amounts, game results amounts (e.g., win amounts), bonus game amounts, etc., to the account server 270. The wagering game server 250 can also include a communication unit 254 configured to communicate information to the wagering game machine 260 and to communicate with other systems, devices and networks.
The wagering game system architecture 200 can also include the wagering game machine 260 configured to present wagering games and receive and transmit information to encouraging and enforcing responsible gaming. The wagering game machine 260 can include a content controller 261 configured to manage and control content and presentation of content on the wagering game machine 260. The wagering game machine 260 can also include a content store 262 configured to contain content to present on the wagering game machine 260. The wagering game machine 260 can also include a report selection controller 263 configured to select report templates that present financial transactions during a wagering game session. The wagering game machine 260 can also include an account data controller 264 configured to generate data, graphs, and other presentations of account information, including financial spending on wagering game activities. The account data controller 264 can also be configured to send the data to one or more locations and/or devices external to a wagering game machine (e.g., to a customer's casino bill, to a printer, to a website, to a personal storage device, etc.). The account data controller 264 can also convert the data into different formats for use on other devices, on data sources, etc. The account data controller 264 can also be configured to present account data to other accounts associated with the player account (e.g., administrative accounts, friend accounts, family accounts, sponsor accounts, etc.). The account data controller 264 can also be configured to present financial account data from other accounts (e.g., friend and/or family accounts, other casino accounts linked to a player account, etc.).
Each component shown in the wagering game system architecture 200 is shown as a separate and distinct element connected via a communications network 222. However, some functions performed by one component could be performed by other components. For example, the wagering game server 250 can also be configured to perform functions of the report selection controller 263, the account data controller 264, and other network elements and/or system devices. Furthermore, the components shown may all be contained in one device, but some, or all, may be included in, or performed by multiple devices, as in the configurations shown in
This section describes operations associated with some embodiments. In the discussion below, some flow diagrams are described with reference to block diagrams presented herein. However, in some embodiments, the operations can be performed by logic not described in the block diagrams.
In certain embodiments, the operations can be performed by executing instructions residing on machine-readable media (e.g., software), while in other embodiments, the operations can be performed by hardware and/or other logic (e.g., firmware). In some embodiments, the operations can be performed in series, while in other embodiments, one or more of the operations can be performed in parallel. Moreover, some embodiments can perform more or less than all the operations shown in any flow diagram.
The flow 300 continues at processing block 304, where the system tracks accounting transaction data during the wagering game session. In some embodiments, the system can track monetary accounting transactions, such as cash and credit withdrawals, deposits, and wagers. The system can also track non-monetary transactions, such as accumulations of non-cash awards (e.g., status points, customer appreciation points, free spins, etc.). The accounting transaction data can include raw accounting data pertaining to any activity on a player account's wagering activities. In some embodiments, the system can track a change in a player account balance and present that information. In some embodiments, the system can track the accounting transaction data during the wagering game session and/or determine accounting data from other periods (e.g., a series of sessions, a period of days, etc.).
The flow 300 continues at processing block 306, where the system presents the accounting transaction data during the wagering game session. In some embodiments, the system can present the accounting transaction data (“accounting data”) per game, per session, per day, or for other time periods (e.g., duration of a hotel stay, each year, over a lifetime). The system can also present accounting data per activities or subject matters (e.g., per player request, by game classifications, by game types, by game themes, etc.). The system can utilize visual and audible notifications to present the accounting data. The system can utilize warning indicators, charts of wagering activity, and pop-ups reminders, etc. The system can present the accounting data in auxiliary windows, devices, on a website, etc. In some embodiments, the locations and positions of the accounting data can be pre-configured on a display. In other embodiments, a player account can configure when and how the accounting transaction data is presented on a display. In some embodiments, the system can convert the accounting transaction data to a transportable file format (e.g., so that player can import into personal financial software, so that player can store in a text file/spreadsheet, so that player can store in a database, etc.). In some embodiments, the system can present the accounting data to a third party monitoring account (e.g., a gambling buddy, a spouse, an administrative user, a casino staff member, etc.). In some embodiments, the system can present accounting information for other player accounts that are associated with the player account (e.g., linked accounts, multiple sub-accounts to the one account, etc.). In some embodiments, the system can present accounting data as is relates to game-play statistics (e.g., the accounting data per minutes played over time, accounting data for peak play hours, accounting data for winning periods versus losing periods, etc.). The accounting data that is related to game-play statistics can help the player to determine spending trends based on their play performance, their amount of time in a wagering game session, etc. The system can also provide controls so that a player can enter values of what the player believes their time to be worth. The system may provide controls to value some times more than others (i.e., different times may be more valuable or guarded than others). The system can then determine an equivalent money amount in lost time. The system can set limits on gambling based on times, time ranges, time values, etc. (e.g., the system prevents gambling during family meal times).
The flow 300 continues at processing block 308, where the system determines a transaction report template. The system can provide controls for a player account to select the transaction report template (“report template”). For example, in
The flow 300 continues at processing block 310, where the system presents the accounting data using the transaction report template.
The flow 300 continues at processing block 312, where the system presents financial transaction statistics data for other player accounts. In some embodiments, the system can show statistics for other players on average for how they are betting at the time. The system can present the statistics for the other players as anonymous information without revealing the other player's personal information. The system can provide a gauge of the current gambling feel of a casino environment over short time periods. The gauge indicates whether the player is gambling responsibly based on statistical information such as other players' gambling activities in the short term, typical responsible gamer activity, perceived responsible gaming, etc. The system can present data from other player accounts that are playing other wagering game sessions simultaneously with the player account's wagering game session. In some embodiments, the system can compare the player's statistics to other gamers that match specific criteria, such as gamers with similar financial backgrounds, gamers with similar amounts of play time, etc. The gauge can also indicate past player activity and/or compare current play to past player activity.
The flow 400 continues at processing block 404, where the system determines one or more player preferences, for the player account, regarding the presentation of the accounting data during the wagering game session. For example, in
The flow 400 continues at processing block 406, where the system determines a transaction limit set in the one or more player preferences. For example, in
The flow 400 continues at processing block 408, where the system indicates the transaction limit during the wagering game session. For example, in
The flow 400 continues at processing block 412, where the system presents an incentive and/or a suggestion to limit wagering activity when the use of funds is close to exceeding the transaction limit. For instance, in
The flow 400 continues at processing block 414, where the system restricts wagering activity when the limit is reached. In some embodiments, the system can restrict what a player account can do, based on the account data presented during the wagering game session. For example, the system can prevent wagers after the player account has exceeded limits. In some embodiments, the system can restrict wagering activity for limits on single bets (e.g., limit bets to be less than $1 as suggested in the suggestions box 511) as well as for the wagering game session (e.g., limit wagering games for ½ hour as also suggested in the suggestions box 511).
This section describes example operating environments, systems and networks, and presents structural aspects of some embodiments.
The CPU 626 is also connected to an input/output (“I/O”) bus 622, which can include any suitable bus technologies, such as an AGTL+ frontside bus and a PCI backside bus. The I/O bus 622 is connected to a payout mechanism 608, primary display 610, secondary display 612, value input device 614, player input device 616, information reader 618, and storage unit 630. The player input device 616 can include the value input device 614 to the extent the player input device 616 is used to place wagers. The I/O bus 622 is also connected to an external system interface 624, which is connected to external systems (e.g., wagering game networks). The external system interface 624 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 622 is also connected to a location unit 638. The location unit 638 can create player information that indicates the wagering game machine's location/movements in a casino. In some embodiments, the location unit 638 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 638 can include a radio frequency identification (RFID) tag that can determine the wagering game machine's location using RFID readers positioned throughout a casino. Some embodiments can use GPS receiver and RFID tags in combination, while other embodiments can use other suitable methods for determining the wagering game machine's location. Although not shown in
In some embodiments, the wagering game machine 606 can include additional peripheral devices and/or more than one of each component shown in
In some embodiments, the wagering game machine 606 includes a responsible gaming module 637. The responsible gaming module 637 can process communications, commands, or other information, where the processing can configure, control, encourage and/or enforce responsible gambling for wagering games.
Furthermore, any component of the wagering game machine 606 can include hardware, firmware, and/or machine-readable media including instructions for performing the operations described herein.
The wagering game machine 700 comprises a housing 712 and includes input devices, including value input devices 718 and a player input device 724. For output, the wagering game machine 700 includes a primary display 714 for displaying information about a basic wagering game. The primary display 714 can also display information about a bonus wagering game and a progressive wagering game. The wagering game machine 700 also includes a secondary display 716 for displaying wagering game events, wagering game outcomes, and/or signage information. While some components of the wagering game machine 700 are described herein, numerous other elements can exist and can be used in any number or combination to create varying forms of the wagering game machine 700.
The value input devices 718 can take any suitable form and can be located on the front of the housing 712. The value input devices 718 can receive currency and/or credits inserted by a player. The value input devices 718 can include coin acceptors for receiving coin currency and bill acceptors for receiving paper currency. Furthermore, the value input devices 718 can include ticket readers or barcode scanners for reading information stored on vouchers, cards, or other tangible portable storage devices. The vouchers or cards can authorize access to central accounts, which can transfer money to the wagering game machine 700.
The player input device 724 comprises a plurality of push buttons on a button panel 726 for operating the wagering game machine 700. In addition, or alternatively, the player input device 724 can comprise a touch screen 728 mounted over the primary display 714 and/or secondary display 716.
The various components of the wagering game machine 700 can be connected directly to, or contained within, the housing 712. Alternatively, some of the wagering game machine's components can be located outside of the housing 712, while being communicatively coupled with the wagering game machine 700 using any suitable wired or wireless communication technology.
The operation of the basic wagering game can be displayed to the player on the primary display 714. The primary display 714 can also display a bonus game associated with the basic wagering game. The primary display 714 can include a cathode ray tube (CRT), a high resolution liquid crystal display (LCD), a plasma display, light emitting diodes (LEDs), or any other type of display suitable for use in the wagering game machine 700. Alternatively, the primary display 714 can include a number of mechanical reels to display the outcome. In
A player begins playing a basic wagering game by making a wager via the value input device 718. The player can initiate play by using the player input device's buttons or touch screen 728. The basic game can include arranging a plurality of symbols along a pay line 732, which indicates one or more outcomes of the basic game. Such outcomes can be randomly selected in response to player input. At least one of the outcomes, which can include any variation or combination of symbols, can trigger a bonus game.
In some embodiments, the wagering game machine 700 can also include an information reader 752, which can include a card reader, ticket reader, bar code scanner, RFID transceiver, or computer readable storage medium interface. In some embodiments, the information reader 752 can be used to award complimentary services, restore game assets, track player habits, etc.
The described embodiments may be provided as a computer program product, or software, that may include a machine-readable medium having stored thereon instructions, which may be used to program a computer system (or other electronic device(s)) to perform a process according to embodiments(s), whether presently described or not, because every conceivable variation is not enumerated herein. A machine readable medium includes any mechanism for storing or transmitting information in a form (e.g., software, processing application) readable by a machine (e.g., a computer). The machine-readable medium may include, but is not limited to, magnetic storage medium (e.g., floppy diskette); optical storage medium (e.g., CD-ROM); magneto-optical storage medium; read only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; or other types of medium suitable for storing electronic instructions. In addition, embodiments may be embodied in an electrical, optical, acoustical or other form of propagated signal (e.g., carrier waves, infrared signals, digital signals, etc.), or wireline, wireless, or other communications medium.
This detailed description refers to specific examples in the drawings and illustrations. These examples are described in sufficient detail to enable those skilled in the art to practice the inventive subject matter. These examples also serve to illustrate how the inventive subject matter can be applied to various purposes or embodiments. Other embodiments are included within the inventive subject matter, as logical, mechanical, electrical, and other changes can be made to the example embodiments described herein. Features of various embodiments described herein, however essential to the example embodiments in which they are incorporated, do not limit the inventive subject matter as a whole, and any reference to the invention, its elements, operation, and application are not limiting as a whole, but serve only to define these example embodiments. This detailed description does not, therefore, limit embodiments, which are defined only by the appended claims. Each of the embodiments described herein are contemplated as falling within the inventive subject matter, which is set forth in the following claims.
This application is a continuation of U.S. patent application Ser. No. 13/127,496, filed May 4, 2011, which is a National Stage Entry of PCT Application No. US2009/63321 filed Nov. 4, 2009, which claims priority benefit to provisional U.S. Patent Application Ser. No. 61/111,496 filed Nov. 5, 2008.
Number | Name | Date | Kind |
---|---|---|---|
4240635 | Brown | Dec 1980 | A |
4283709 | Lucero et al. | Aug 1981 | A |
4335809 | Wain | Jun 1982 | A |
4339798 | Hedges et al. | Jul 1982 | A |
4359631 | Lockwood et al. | Nov 1982 | A |
4467424 | Hedges et al. | Aug 1984 | A |
4494197 | Troy et al. | Jan 1985 | A |
4575622 | Pellegrini | Mar 1986 | A |
4636951 | Harlick | Jan 1987 | A |
4648600 | Olliges | Mar 1987 | A |
4669730 | Small | Jun 1987 | A |
4760527 | Sidley | Jul 1988 | A |
4815741 | Small | Mar 1989 | A |
4842278 | Markowicz | Jun 1989 | A |
4856787 | Itkis | Aug 1989 | A |
4880237 | Kishishita | Nov 1989 | A |
4882473 | Bergeron et al. | Nov 1989 | A |
4926327 | Sidley | May 1990 | A |
4994908 | Kuban et al. | Feb 1991 | A |
5038022 | Lucero | Aug 1991 | A |
5069453 | Koza et al. | Dec 1991 | A |
5119295 | Kapur | Jun 1992 | A |
5159549 | Hallman, Jr. et al. | Oct 1992 | A |
5179517 | Sarbin et al. | Jan 1993 | A |
5197094 | Tillery et al. | Mar 1993 | A |
5223698 | Kapur | Jun 1993 | A |
5259613 | Marnell, II | Nov 1993 | A |
5265874 | Dickinson et al. | Nov 1993 | A |
5276312 | McCarthy | Jan 1994 | A |
5287269 | Dorrough et al. | Feb 1994 | A |
5297802 | Pocock et al. | Mar 1994 | A |
5324035 | Morris et al. | Jun 1994 | A |
5326104 | Pease et al. | Jul 1994 | A |
5332076 | Ziegert | Jul 1994 | A |
5371345 | LeStrange et al. | Dec 1994 | A |
5408417 | Wilder | Apr 1995 | A |
5429361 | Raven et al. | Jul 1995 | A |
5457306 | Lucero | Oct 1995 | A |
5470079 | LeStrange et al. | Nov 1995 | A |
5505449 | Eberhardt et al. | Apr 1996 | A |
5524888 | Heidel | Jun 1996 | A |
5559312 | Lucero | Sep 1996 | A |
5581461 | Coll et al. | Dec 1996 | A |
5586937 | Menashe | Dec 1996 | A |
5611730 | Weiss | Mar 1997 | A |
5613912 | Slater | Mar 1997 | A |
5655961 | Acres et al. | Aug 1997 | A |
5674128 | Holch et al. | Oct 1997 | A |
5722890 | Libby et al. | Mar 1998 | A |
5732398 | Tagawa | Mar 1998 | A |
5755621 | Marks et al. | May 1998 | A |
5761647 | Boushy | Jun 1998 | A |
5762552 | Vuong et al. | Jun 1998 | A |
5770533 | Franchi | Jun 1998 | A |
5797794 | Angell | Aug 1998 | A |
5800269 | Holch et al. | Sep 1998 | A |
5811772 | Lucero | Sep 1998 | A |
5823879 | Goldberg et al. | Oct 1998 | A |
5830067 | Graves et al. | Nov 1998 | A |
5830068 | Brenner et al. | Nov 1998 | A |
5830069 | Soltesz et al. | Nov 1998 | A |
5836817 | Acres et al. | Nov 1998 | A |
5857911 | Fioretti | Jan 1999 | A |
5871398 | Schneier et al. | Feb 1999 | A |
5917725 | Thacher et al. | Jun 1999 | A |
5919091 | Bell et al. | Jul 1999 | A |
5949411 | Doerr et al. | Sep 1999 | A |
5952640 | Lucero | Sep 1999 | A |
5959277 | Lucero | Sep 1999 | A |
5971271 | Wynn et al. | Oct 1999 | A |
5971849 | Falciglia | Oct 1999 | A |
5984779 | Bridgeman et al. | Nov 1999 | A |
6019283 | Lucero | Feb 2000 | A |
6024640 | Walker et al. | Feb 2000 | A |
6039648 | Guinn et al. | Mar 2000 | A |
6048269 | Burns et al. | Apr 2000 | A |
6049823 | Hwang | Apr 2000 | A |
6089982 | Holch et al. | Jul 2000 | A |
6093100 | Singer et al. | Jul 2000 | A |
6101477 | Hohle et al. | Aug 2000 | A |
6110041 | Walker et al. | Aug 2000 | A |
6113495 | Walker et al. | Sep 2000 | A |
6120024 | Lind | Sep 2000 | A |
6141006 | Knowlton et al. | Oct 2000 | A |
6183366 | Goldberg et al. | Feb 2001 | B1 |
6247643 | Lucero | Jun 2001 | B1 |
6264560 | Goldberg et al. | Jul 2001 | B1 |
6280326 | Saunders | Aug 2001 | B1 |
6280328 | Holch et al. | Aug 2001 | B1 |
6319125 | Acres | Nov 2001 | B1 |
6322446 | Yacenda | Nov 2001 | B1 |
6347086 | Strachan | Feb 2002 | B1 |
6358151 | Enzminger et al. | Mar 2002 | B1 |
6383078 | Yacenda | May 2002 | B1 |
6409602 | Wiltshire et al. | Jun 2002 | B1 |
6471590 | Saunders | Oct 2002 | B2 |
6508709 | Karmarkar | Jan 2003 | B1 |
6629890 | Johnson | Oct 2003 | B2 |
7022017 | Halbritter et al. | Apr 2006 | B1 |
7128652 | Lavoie et al. | Oct 2006 | B1 |
20010003100 | Yacenda | Jun 2001 | A1 |
20010031663 | Johnson | Oct 2001 | A1 |
20020002075 | Rowe | Jan 2002 | A1 |
20020028709 | Finer et al. | Mar 2002 | A1 |
20020077178 | Oberberger et al. | Jun 2002 | A1 |
20020111213 | McEntee et al. | Aug 2002 | A1 |
20020166126 | Pugh et al. | Nov 2002 | A1 |
20030027631 | Hedrick et al. | Feb 2003 | A1 |
20030054868 | Paulsen et al. | Mar 2003 | A1 |
20030100371 | Gatto et al. | May 2003 | A1 |
20030104863 | Park | Jun 2003 | A1 |
20030212636 | Resnick | Nov 2003 | A1 |
20030224854 | Joao | Dec 2003 | A1 |
20040084524 | Ramachandran | May 2004 | A1 |
20040102238 | Taylor | May 2004 | A1 |
20040121841 | Xidos et al. | Jun 2004 | A1 |
20040147313 | Stanley et al. | Jul 2004 | A1 |
20040231018 | Olson | Nov 2004 | A1 |
20050020354 | Nguyen et al. | Jan 2005 | A1 |
20050064938 | Xidos et al. | Mar 2005 | A1 |
20050101383 | Wells | May 2005 | A1 |
20050107156 | Potts et al. | May 2005 | A1 |
20050187012 | Walker et al. | Aug 2005 | A1 |
20060100009 | Walker et al. | May 2006 | A1 |
20060121972 | Walker et al. | Jun 2006 | A1 |
20060121979 | Kennard et al. | Jun 2006 | A1 |
20060211493 | Walker et al. | Sep 2006 | A1 |
20070015573 | Angell et al. | Jan 2007 | A1 |
20070167209 | Jaffe et al. | Jul 2007 | A1 |
20070259714 | Block et al. | Nov 2007 | A1 |
20110077073 | Gagner et al. | Mar 2011 | A1 |
20110201408 | Gagner et al. | Aug 2011 | A1 |
20110245943 | Agarwal et al. | Oct 2011 | A1 |
20130225273 | Gagner et al. | Aug 2013 | A1 |
Number | Date | Country |
---|---|---|
0769769 | Apr 1997 | EP |
10192537 | Jul 1998 | JP |
200245557 | Feb 2002 | JP |
2002210186 | Jul 2002 | JP |
2005118431 | May 2005 | JP |
200687714 | Apr 2006 | JP |
2006116244 | May 2006 | JP |
WO-9530944 | Nov 1995 | WO |
WO-8906998 | Aug 1998 | WO |
WO-0176710 | Oct 2001 | WO |
WO-03045517 | May 2003 | WO |
WO-2007107883 | Sep 2007 | WO |
WO-2008058279 | May 2008 | WO |
WO-2009137633 | Nov 2009 | WO |
WO-2010054027 | May 2010 | WO |
Entry |
---|
U.S. Appl. No. 12/991,391 Office Action, Mar. 12, 2012, 29 pages. |
U.S. Appl. No. 13/858,467, filed Apr. 8, 2013, Gagner, Mark B., et al. |
U.S. Appl. No. 13/858,467 Office Action, Dec. 30, 2013, 6 Pages. |
“Amendment in the Nature of a Substitute H.R. 3125, Offered by Mr. Goodlatte of Virginia”, Tech Law Journal www.techlawjournal.com Date obtained from the Internet Dec. 20, 2005 Apr. 5, 2000, 3 pages. |
“AT&T Corp. v. Coeur D'Alene Tribe, 45 F. Supp. 2d 995 (D. Idaho 1998)”, 1998 , 14 pages. |
“Bill HR 3125 IH The Internet Gambling Prohibition Art Oct. 21, 1999”, 17 pages. |
“Casino Systems Solutions”, IGT International Game Technolgoy Mar. 19, 1997, 20 pages. |
Examination Report, Sep. 17, 2009, 3 pages. |
“H.R. 3125, 106th Congress, 2d Session”, Internet Prohibition Act of 2000 http://thomas.loc.gov Date obtained from the Internet: Nov. 23, 2005 Oct. 21, 1999, 9 pages. |
“High-Tech Gambling Debuts at Turning Stone”, Syracuse Post Standard Feb. 27, 1995, 1 page. |
Pct Application No. PCT/US09/43055 International Preliminary Report on Patentability, Jun. 21, 2010, 14 pages. |
PCT Application No. PCT/US09/43055 International Search Report, Jun. 22, 2009, 10 pages. |
PCT Application No. PCT/US09/63321 International Search Report on Patentability, Oct. 5, 2010, 9 pages. |
PCT Application No. PCT/US09/63321 International Search Report, Dec. 22, 2009, 8 pages. |
PCT Application No. PCT/US2007/084316 International Preliminary Report on Patentability, Jan. 13, 2009, 8 pages. |
PCT Application No. PCT/US2007/084316 International Search Report and Written Opinion, May 23, 2008, 10 pages. |
“S. 692, 106th Congress, 1st Session”, Internet Gambling Prohibition Act of 1999, 8 pages. |
Singapore Application 0800336-0 IPO of Singapore Written Opinion, Feb. 25, 2009 , 7 pages. |
U.S. Appl. No. 11/483,558 Office Action, Jun. 24, 2009, 9 pages. |
U.S. Appl. No. 12/513,486 Office Action, Feb. 23, 2012, 36 pages. |
Banks, Michael A., “America Online: A Graphics-Based Success”, Link-Up Jan./Feb. 1992, pp. 12, 14 and 15. |
Conti, Carl, “Letter to Bruce T. Samboy”, Jun. 27, 1994, 2 pages. |
Corbisiero, Jr., Richard F., “Letter to Niels C. Holch”, Jul. 14, 1994, 1 page. |
Gatley, Susan, “Turning Stone Inter-Office Memorandum to Bong Woo”, re Instant Keno Issues Oct. 17, 1994 , 3 pages. |
Green, Marian, “Cashing in”, Indian Gaming Business Fall 2006, 21-23. |
Grochowski, John, “The Cashless Puzzle”, Slot Manager Jan./Feb. 2008, 5 pages. |
Holch, Niels C., “Letter to Hon. Richard F. Corbisiero, Jr.”, Jul. 12, 1994, 1 page. |
Minder, Jacqueline L., “Letter to Ron Mach”, Jun. 20, 1994, 1 page. |
Monteau, Harold , “Letter to Richard M. Milanovich”, National Indiam Gaming Commission Jun. 6, 1995, 2 pages. |
Monteau, Harold A., “Semiannual Regulatory Agenda”, National Gaming Indian Commission Obtained from the Internet: Feb. 26, 2007, 1 page. |
Quick Track Gaming, Inc., , “QuickTrack”, , 44 pages. |
Samboy, Bruce T., “Letter to Carl Conti”, Jun. 13, 1994, 2 pages. |
Samboy, Bruce T., “Letter to Carl Conti”, Jul. 1, 1994, 2 pages. |
Samboy, Bruce T., “Letter to Hon. Richard F. Corbisiero, Jr.”, Jun. 1, 1994 , 7 pages. |
Samboy, Bruce T., “Letter to Hon. Richard F. Corbisiero, Jr.”, Jun. 14, 1994, 8 pages. |
Smith, Katherine A., “Letter to Hon. James R. Hurley”, Jun. 15, 1994, 4 pages. |
Washburn, Kevin K., “Win Sports Betting”, Mar. 13, 2001, 3 pages. |
Yerak, Becky , “At Cashless Slots: You've got mail, and a jackpot No more coins to insert, but you can get messages”, USA Today Nov. 13, 2000, 4 pages. |
Number | Date | Country | |
---|---|---|---|
20120190437 A1 | Jul 2012 | US |
Number | Date | Country | |
---|---|---|---|
61111496 | Nov 2008 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13127496 | US | |
Child | 13437657 | US |