Method and apparatus for monitoring game play
First Claim
1. A system for monitoring player betting during play of a table game comprising:
- one or more bet spots configured to receive a bet;
one or more antenna associated with one or more bet spots, the one or more antenna capable of detecting a bet within a detection zone;
a dealer interface configured to accept input from a dealer to create game data;
a reader configured to receive one or more signals from the one or more antenna;
a processor configured to receive the one or more signals from the reader and the game data, and further configured with memory having machine readable code comprising;
machine readable code configured to determine deck penetration based on the game data from the dealer and an average number of cards dealt dealt per hand, wherein the average number of cards dealt per hand is based on a historical average;
machine readable code configured to determine betting patterns for one or more players based on the one or more signals from the reader;
machine readable code configured to detect changes in betting patterns for one or more players in relation to the deck penetration; and
machine readable code configured to generate a flag in response to changes in betting patterns for one or more players in relation to the deck penetration.
9 Assignments
0 Petitions
Accused Products
Abstract
A bet detection system which may execute on a computer based processing device is disclosed for use with DID tokens to detect unwanted or unfair betting patterns by players. The system utilizes a table equipped with DID token detection antenna associated with the one or more bet spots for the player positions. DID token antenna may detect DID tokens at the dealer position, other bet spots, or chip trays. A dealer interface allows the dealer to provide the game data to the detection system. The detection system processes the game data and the bet data, such as bet amount for the players. Based on this processing, bet patterns may be generated for the players and in relation to deck penetration information, deviations in bet patterns may be detected and appropriate notification provided.
120 Citations
39 Claims
-
1. A system for monitoring player betting during play of a table game comprising:
-
one or more bet spots configured to receive a bet; one or more antenna associated with one or more bet spots, the one or more antenna capable of detecting a bet within a detection zone; a dealer interface configured to accept input from a dealer to create game data; a reader configured to receive one or more signals from the one or more antenna; a processor configured to receive the one or more signals from the reader and the game data, and further configured with memory having machine readable code comprising; machine readable code configured to determine deck penetration based on the game data from the dealer and an average number of cards dealt dealt per hand, wherein the average number of cards dealt per hand is based on a historical average; machine readable code configured to determine betting patterns for one or more players based on the one or more signals from the reader; machine readable code configured to detect changes in betting patterns for one or more players in relation to the deck penetration; and machine readable code configured to generate a flag in response to changes in betting patterns for one or more players in relation to the deck penetration. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A bet detection system for use with a table game comprising:
-
one or more antenna for receiving token data from two or more DID equipped tokens; a dealer interface for generating game data; a processor configured execute machine readable code to process the token data and the game data, the machine readable code comprising; machine readable code configured to deck penetration using the game data and an average number of cards dealt per hand, wherein the average number of cards dealt per hand is based on a historical average; machine readable code configured to track a player'"'"'s bet deviation; and machine readable code configured to compare a player'"'"'s bet deviation to a threshold value responsive to the deck penetration. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16)
-
-
17. A method for monitoring for unwanted betting patterns during one or more wagering events on a table game comprising:
-
detecting one or more bet amounts of one or more bets by one or more players; receiving game data from the dealer via a dealer interface; processing the bet amount and the game data via a processor to determine a bet amount pattern for at least one of the one or more players; processing at least the game data via the processor to determine deck penetration based on the game data and an average number of cards dealt per hand, wherein the average number of cards dealt per hand is based on a historical average; and processing the bet amount pattern for at least one player in relation to deck the penetration via the processor to detect unwanted betting patterns by at least one player. - View Dependent Claims (18, 19, 20, 21, 22, 23, 24, 25, 26)
-
-
27. A method for monitoring betting during play of wagering events on a table game comprising:
-
providing a wagering event using DID tokens and a DID token detecting gaming table interfaced to a detection system having machine readable code configured to process signals generated by DID token reading; tracking DID tokens bet during play via a processor and associating DID tokens bet with a particular player; calculating via a processor one or more types of player wagering data from the tracking of DID tokens comprising; total amount bet during game play; total amount lost during game play; total amount won during game play; determining deck penetration using an average number of cards dealt per hand, wherein the average number of cards dealt per hand is based on a historical average; comparing the player wagering data to one or more thresholds in relation to the determined deck penetration; responsive to the comparing, generating one or more notifications regarding the player wagering data; and automatically electronically sending one or more notifications regarding the comparing of player wagering data to the one or more thresholds when the player wagering data meets the one or more thresholds. - View Dependent Claims (28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39)
-
Specification