US2007015573A1PendingUtilityA1

Method and system for automated responsible gaming controls

47
Assignee: ONEIDA INDIAN NATIONPriority: Jul 14, 2005Filed: Jul 11, 2006Published: Jan 18, 2007
Est. expiryJul 14, 2025(expired)· nominal 20-yr term from priority
G07F 17/3255G07F 17/3237G07F 17/3206G07F 17/32G07F 17/3232G07F 17/3239
47
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Player information is received and a player is authenticated based on government regulations. Player deposits are compared to limits associated with player accounts. Upon reaching a limit associated with the account, the player may be prevented from depositing additional funds or playing games. In this way, gaming facilities may monitor gaming and ensure responsible gaming for all players.

Claims

exact text as granted — not AI-modified
1 . A method for processing a gaming deposit, comprising: 
 receiving a deposit amount and an account identifier associated with a player account;    comparing the deposit amount to a limit associated with the player account; and    if the deposit amount is within the limit, adding the deposit amount to the player account.    
   
   
       2 . The method of  claim 1 , wherein the limit is a maximum amount withdrawn subtracted from an amount deposited.  
   
   
       3 . The method of  claim 1 , wherein the limit is an amount of game play.  
   
   
       4 . The method of  claim 1 , wherein the limit is predetermined.  
   
   
       5 . The method of  claim 1 , wherein the limit is based on government regulations.  
   
   
       6 . The method of  claim 1 , further comprising searching a database to locate the limit associated with the player.  
   
   
       7 . The method of  claim 1 , further comprising associating the limit with the player account.  
   
   
       8 . The method of  claim 1 , further comprising issuing the account identifier to the player after storing player information.  
   
   
       9 . A method for authenticating a player at a gaming facility, comprising: 
 receiving an account identifier from a player, wherein the account identifier is associated with a player account corresponding to the player;    authenticating the player based on stored information associated with the account identifier;    after the player has been authenticated, receiving a request for a gaming transaction from the player; and    determining if the requested gaming transaction is within a pre-established gaming limit associated with the player account.    
   
   
       10 . The method of  claim 9 , further comprising: 
 after reaching the limit, denying the transaction.    
   
   
       11 . The method of  claim 10 , further comprising: 
 prohibiting gaming transactions from the player for a period of time after denying the transaction.    
   
   
       12 . The method of  claim 9 , further comprising: 
 after reaching the limit, notifying the player that the limit was reached.    
   
   
       13 . The method of  claim 9 , further comprising: 
 warning the player that the limit is approaching.    
   
   
       14 . The method of  claim 9 , further comprising: 
 after reaching the limit, sending a notice to a contact associated with the player account that the limit was reached.    
   
   
       15 . The method of  claim 14 , wherein the notice is one of: an e-mail, a text message, a voice message, and a letter.  
   
   
       16 . The method of  claim 9 , wherein the transaction is a game play.  
   
   
       17 . The method of  claim 9 , wherein the transaction is a deposit to the player account.  
   
   
       18 . The method of  claim 9 , wherein authenticating the player comprises: 
 measuring biometric information of the player; and    determining if the measured biometric information matches the stored information.    
   
   
       19 . The method of  claim 9 , wherein authenticating the player comprises: 
 measuring personal identification information of the player; and    determining if the personal identification information matches the stored information.    
   
   
       20 . The method of  claim 9 , wherein the authenticating occurs during a game play.  
   
   
       21 . The method of  claim 9 , wherein the authenticating occurs before a game play.  
   
   
       22 . The method of  claim 9 , wherein the limit is a maximum amount withdrawn subtracted from an amount deposited.  
   
   
       23 . The method of  claim 9 , wherein the limit is an amount of game play.  
   
   
       24 . The method of  claim 9 , wherein the limit is predetermined.  
   
   
       25 . The method of  claim 9 , wherein the limit is based on government regulations.  
   
   
       26 . The method of  claim 9 , further comprising searching a database to locate the limit associated with the player.  
   
   
       27 . A method for automatically implementing gaming controls, comprising: 
 establishing a gaming constraint associated with a player;    receiving a request for a gaming transaction from the player;    determining whether the requested gaming transaction would violate the gaming constraint associated with the player;    approving the requested gaming transaction, when it is determined that the requested gaming transaction would not violate the gaming constraint associated with the player.    
   
   
       28 . The method of  claim 27 , wherein the gaming transaction request is a deposit to the player account.  
   
   
       29 . The method of  claim 27 , wherein the gaming transaction request is a wager.  
   
   
       30 . The method of  claim 27 , wherein the gaming transaction request is a game play request.  
   
   
       31 . The method of  claim 27 , wherein the gaming transaction request is a withdrawal request.  
   
   
       32 . The method of  claim 27 , wherein the gaming constraint is a maximum amount of time the player may game during a predetermined time period.  
   
   
       33 . The method of  claim 27 , wherein the gaming constraint is a maximum amount of money the player may deposit into a gaming account.  
   
   
       34 . The method of  claim 27 , wherein the gaming constraint is a maximum wager amount the player may make while gaming.  
   
   
       35 . The method of  claim 27 , further comprising: 
 processing the requested gaming transaction, when the requested gaming transaction has been approved.    
   
   
       36 . The method of  claim 27 , further comprising: 
 storing the gaming constraint in a player account corresponding to the player.    
   
   
       37 . The method of  claim 27 , further comprising: 
 storing, in a player account corresponding to the player, data related to gaming activities of the player; and    wherein the determining further comprises: 
 analyzing the stored data based on the requested gaming transaction.  
   
   
   
       38 . The method of  claim 27 , further comprising: 
 rejecting the requested gaming transaction, when it is determined that the requested gaming transaction would violate the gaming constraint associated with the player.    
   
   
       39 . The method of  claim 38 , further comprising: 
 displaying a message to the player regarding the rejected gaming transaction.    
   
   
       40 . The method of  claim 38 , further comprising: 
 sending a message to a contact person associated with the player regarding the rejected gaming transaction.    
   
   
       41 . A method for automatically implementing gaming controls, comprising: 
 establishing a gaming constraint associated with a player account;    receiving a player account identifier;    determining whether a transaction associated with the player account identifier would violate the gaming constraint associated with the player account; and    approving the transaction, when it is determined that the requested transaction would not violate the gaming constraint associated with the player account.    
   
   
       42 . The method of  claim 41 , wherein the transaction is one of: a login, a game play, a deposit, and a withdrawal.  
   
   
       43 . A system for automatically implementing gaming controls, comprising: 
 an establishing component configured to establish a gaming constraint associated with a player;    a receiving component configured to receive a request for a gaming transaction from the player; and    a determining component configured to: 
 determine whether the requested gaming transaction would violate the gaming constraint associated with the player; and  
 approve the requested gaming transaction, when it is determined that the requested gaming transaction would not violate the gaming constraint associated with the player.  
   
   
   
       44 . The system of  claim 43 , wherein the gaming transaction request is a deposit to the player account.  
   
   
       45 . The system of  claim 43 , wherein the gaming transaction request is a wager.  
   
   
       46 . The system of  claim 43 , wherein the gaming transaction request is a game play request.  
   
   
       47 . The system of  claim 43 , wherein the gaming transaction request is a withdrawal request.  
   
   
       48 . The system of  claim 43 , wherein the gaming constraint is a maximum amount of time the player may game during a predetermined time period.  
   
   
       49 . The system of  claim 43 , wherein the gaming constraint is a maximum amount of money the player may deposit into a gaming account.  
   
   
       50 . The system of  claim 43 , wherein the gaming constraint is a maximum wager amount the player may make while gaming.  
   
   
       51 . The system of  claim 43 , further comprising: 
 a processor configured to process the requested gaming transaction, when the requested gaming transaction has been approved.    
   
   
       52 . The system of  claim 43 , further comprising: 
 a database configured to store the gaming constraint in a player account corresponding to the player.    
   
   
       53 . The system of  claim 43 , wherein the database is further configured to store, in a player account corresponding to the player, data related to gaming activities of the player, and wherein the determining component is further configured to analyze the stored data based on the requested gaming transaction.  
   
   
       54 . The system of  claim 43 , wherein the determining component is configured to reject the requested gaming transaction, when it is determined that the requested gaming transaction would violate the gaming constraint associated with the player.  
   
   
       55 . The system of  claim 54 , further comprising: 
 a display component configured to display a message to the player regarding the rejected gaming transaction.    
   
   
       56 . The system of  claim 54 , further comprising: 
 a notifying component configured to sending a message to a contact person associated with the player regarding the rejected gaming transaction.    
   
   
       57 . A computer-readable medium including instructions for automatically implementing gaming controls, the method comprising: 
 establishing a gaming constraint associated with a player;    receiving a request for a gaming transaction from the player;    determining whether the requested gaming transaction would violate the gaming constraint associated with the player;    approving the requested gaming transaction, when it is determined that the requested gaming transaction would not violate the gaming constraint associated with the player.    
   
   
       58 . A system for automatically implementing gaming controls, the system comprising: 
 means for establishing a gaming constraint associated with a player;    means for receiving a request for a gaming transaction from the player;    means for determining whether the requested gaming transaction would violate the gaming constraint associated with the player;    means for approving the requested gaming transaction, when it is determined that the requested gaming transaction would not violate the gaming constraint associated with the player.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.