This application claims priority to U.S. Provisional Patent Application No. 60/881,407 filed on Jan. 19, 2007 titled TABLE MONITORING IDENTIFICATION SYSTEM, WAGER TAGGING AND FELT COORDINATE MAPPING.
1. Field of the Invention
The invention relates to wagering game monitoring and in particular to a method and apparatus for monitoring a table and game play at table to track game play.
2. Related Art
Gambling has become a popular form of entertainment in the United States and in numerous foreign countries. Although numerous wagering events are offered within the casino or other gaming environment, one of the most traditional and popular forms of wagering occurs at table games. As is widely understood, traditional table games utilize a playing surface, often called a felt, upon which a dealer or other game operator offers a wagering event to one or more players or upon which a player may make a bet or wager.
As compared to slot or video type games, traditional table games offer greater excitement for some players, group play, and often attract big money players, which can result in larger profit margins for the casino. Slots or video type games, however, often integrate a player tracking system that allows a computerized system to monitor a player's participation, such as how often a player plays and how much a particular player wagers. Furthermore, electronic gaming machines, such as slot or video type machines accurately detect wagers and payouts and thus are very efficient at preventing cheating. In a table game environment however, it is often difficult to track how much money a player wagers and thus it is likewise difficult to accurately provide complimentary gifts or reward good customers to encourage a return to a particular property. Prior art systems use gaming tokens embedded with Radio Frequency Identification (“RFID”) to track a player's betting for this purpose. An example of such a system is the Mikohn® Gaming Corporation's d/b/a Progressive Gaming International Corporation's Tablelink® product.
However, even with prior art bet tracking techniques, numerous wagering aspects may be missed or unmonitored. One drawback to prior art systems is that existing RFID type systems may not be able to accurately track every token, particularly when numerous tokens are stacked. In addition, prior art systems may suffer from inter-antenna interference if RFID antennas are spaced too closely together as such for games that have multiple and independent betting options per player seat, such as for example, the game of baccarat. As a result, table layouts require sufficient spacing between antenna, which in turn may prevent desired felt layout or prevent presentation of the desired game.
Another drawback of prior art table monitoring systems resulted when attempting to interface monitoring systems with a particular game. In prior art systems, the dealer or pit boss was forced to synchronize the monitoring system software with the particular game in play, and the particular version of the game in play. This step required additional training and time from busy casino personnel and failure to perform this step correctly will result in the tracking system providing faulty data that is not synchronized to game play.
Another drawback to the prior art is that while a RFID equipped token may be detected when placed on the table, once removed from the table, its status as a previous bet may be lost. In addition, payouts to a particular winning wager may not be associated with a winning wager, but simply detected as additional tokens being placed on the table. To adequately monitor game play, aspects of table monitoring beyond monitoring tokens placed on and removed from the table may be required.
The method and apparatus described below overcomes these drawbacks and provides additional benefits.
The table monitoring system generally comprises a camera configured to create a table image and image data, a RFID system configured to create RFID data, and a processing engine configured to process the image data and the RFID data to create one or more tags. In one or more embodiments, each tag represents at least one table event and has the image data and the RFID data associated therewith. The image data and RFID data may be associated to one or more tags in various ways. For example, the image data and RFID data may be associated based on a coordinate mapping (as discussed below), or based on the time of the table event which caused the image and/or RFID data to be created. As a table game is played, the processing engine may associate additional image data and RFID data created during play of the game to an already created tag. This allows a table event, over the course of a table game, to be monitored by its associated tag. A database may be included in the system to store the RFID data, the image data, or both if storage of such data is necessary.
In some embodiments, the table monitoring system may comprise one or more control parameters corresponding to each of the table games the monitoring system is designed to monitor. In these embodiments, the processing engine processes image data and RFID data according to the control parameters for the game presently being played. It is noted that in some embodiments, the system may include felt identification which allows the system to identify the felt currently being used on the table. In these embodiments, control parameters may be associated with the felt identification to allow the system to use control parameters suited for a particular felt.
The table monitoring system may also comprise a coordinate grid having one or more grid coordinates assigned to one or more relevant locations on the table. The image data and the RFID data may then by mapped to the coordinate grid to allow the system to determine where a table event has occurred. As stated, in one or more embodiments, the image data and RFID data may be assigned to one or more tags based on the coordinate mapping. In one or more embodiments, a biometric interface may be included to create player identification data and associate the identification data with one or more grid coordinates on the table. The processing engine, in one or more embodiments, may also be configured to cross-reference the RFID data and the image data based on the time and grid coordinates of the table events.
In one or more embodiments, the table monitoring system may include one or more peripherals such as but not limited to a card shoe, card shredder, chip tray, or the like. The peripherals may each have an identification code and one or more control parameters associated therewith. The processing engine may then be configured to identify and process table events related to these peripherals according to their individual identification codes and control parameters.
It is contemplated that some embodiments of the table monitoring system will not include a camera and may instead rely on the RFID system to tag and monitor table events. However, embodiments having a camera may utilize image data created by the camera to better monitor table events. For example, the system may comprise a plurality of bet locations within the detection zone of a single RFID antenna. RFID alone may not allow table events, such as wagers placed certain these bet locations, to be distinguished. Therefore, the system or an image controller in the system may be configured to identify the one or more table events such as but not limited to placing of bets in any of the bet locations. The processing engine may now be configured to distinguish the table events occurring in any of the bet locations by cross-referencing the image data created by the image controller with the RFID data from the RFID system.
The image controller in one or more embodiments creates image data by analyzing the table images created by the camera and identifying bet locations for and table events of each table game that is being monitored. Notably, a separate image controller is not required in every embodiment because other elements of the monitoring system, such as the camera, may perform the function of the image controller.
The method of monitoring one or more table games is an electronic method of monitoring. In one or more embodiments, the method comprises creating RFID data in response to one or more table events detected by one or more RFID antennas, each of the RFID antennas having a detection zone, and creating image data by analyzing a plurality of table images. Once this data is created the RFID data and the image data may be cross-referenced and mapped to a coordinate grid. One or more tags representing at least one of the table events and having RFID data, image data, or both associated therewith may then be created. As the table game is played any additional RFID data, image data, or both may be associated with at least one of the earlier created tags.
The method of table game monitoring may include identifying one or more players and associated at least one relevant location on the coordinate grid to the identified player. This is used to allow the wagers of a particular player to be monitored. In addition, the method may include identifying at least one felt identification associated with at least one of the table games to be monitored. Once a felt has been identified, the RFID data, image data, or both may be associated to one or more tags according to the felt identification's corresponding control parameters.
Some table games may have multiple bet locations within the detection zone of a single RFID antenna. Accordingly, some embodiments of the method of electronic table game monitoring may include distinguishing each table event occurring within the detection zone of a particular RFID antenna by cross-referencing the RFID data and the image data. Finally, some embodiments of the method may include the step of storing the RFID data, image data, or both in a database.
Other systems, methods, features and advantages of the invention will be or will become apparent to one with skill in the art upon examination of the following figures and detailed description. It is intended that all such additional systems, methods, features and advantages be included within this description, be within the scope of the invention, and be protected by the accompanying claims.
The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention. In the figures, like reference numerals designate corresponding parts throughout the different views.
In this example embodiment of a table, configured for use with the game of blackjack, there is an outer edge 104 of the table 100. One or more player stations 112 are provided and configured for use by a player to participate in a waging game or a game of chance offered at the table such as blackjack. In this embodiment the player stations 112 comprise a bet spot 116 wherein a player may place one or more wagers during the course of play. For example, the player may place the chips or tokens within area 116 when placing a bet during the course of play. Overlapping the bet spot 116 is a detection zone 120. The detection zone 120 comprises a zone within which a bet detection system, described below, may detect the token, such as an amount bet by a player at a player location 112 or player station at the table 100. Likewise, the simple presence of a bet may also be detected by the bet detection system or other data stored on the token.
In other various embodiments, one or more supplemental bet spots 130 may be located in one or more other locations on the table surface 108. By way of example, a supplemental bet spot 130 may be located as shown and shared by more than one player. A supplemental detection zone 134 may likewise be associated with the supplemental bet spot 130 to detect a bet therein. The supplement bet spots 130 may comprise coin buy spots with associated detection. A supplemental detection zone 134 could also be added to detect multiple bets that are required or optional by a player in proprietary table games such as Caribbean Stud Poker®, Three Card Poker®, Royal Match 21®, Texas Hold'em Bonus™, and Two Card Joker Poker™.
In this example embodiment a dealer position 138 is located generally opposite one or more of the player positions. As is generally understood, the dealer presents the game from the dealer station 138. Associated with the dealer station 138 are one or more dealer spots 142 which in turn may be associated with one or more dealer detection zones. The dealer spot 142 is a location on or in some way associated with the table and/or the dealer on which tokens may be placed for detection by the detection system. As used herein, the term token often references a detectable identification type token. The dealer detection zone 146 is the area in which the detection system can detect tokens placed in the dealer spot 142. This dealer detection zone 146 could be used in player banked traditional table games such as those played in the State of California or other jurisdictions. The dealer detection zone 146 may also be used to hold ante bets contributed by players in Class II gaming jurisdictions such as Native American gaming establishments in the State of Florida.
A dealer interface 150 may also be place near the dealer position 138. The dealer interface 150 comprises a user interface configured to allow the dealer to provide input to the detection system and optionally receive input from the detection system. In various embodiments, the dealer interface 150 comprises one or more buttons, dials, display screens, lights or other illumination devices, speakers or other audible indicators, or analog dials, potentiometers, or keypads. Through use of the dealer interface 150, the dealer is able to provide input to the detection system or receive data from the detection system.
The shuffle indicator button 208 comprises a dealer input device or indicator that the dealer may utilize to provide an input to the detection system that a shuffle has just occurred or is about to occur. Another shuffle indicator may come from an attached card shuffler mechanism. Either method provides data to the system to signal when dealing from a newly shuffled shoe is about to occur. The game start button 216 comprises an indicator that the dealer may utilize to provide an input to the detection system that a new game is about to begin. As used herein, a game start is defined as a dealing of a round of cards or other indicia to the players. In other games, other events may define the start of a new game. It is contemplated that multiple games may occur between shuffles of the deck.
Of course, in embodiments which utilize indicia other than cards, such as games that utilize dice or wheels, other buttons with different labels may be utilized to achieve the method and apparatus as described herein. It is also contemplated that the dealer interface 150 may include a key board and/or a display to thereby provide means for the dealer to input player information and player position. The dealer interface 150 may also be equipped with player tracking interface to accept and read player tracking cards and to be able to receive number or letter codes for a player. The player tracking interface will lock in a name or code to identify each player using a player location 112. The player tracking interface can be operated by the dealer or pit supervisory personnel to provide this Play Lock-In Data.
The bets complete button 220 may be utilized when all the bets for a particular round of play have been placed and hence, any additional bets or changes to the bet pattern may be in violation of the game rules. It is further contemplated that a button may also be included on the interface 150 to indicate that bets are being allowed or accepted. This may also be used during a payout or bet collection period.
The display 230 may comprise any type of display capable of providing information to the dealer or other casino personnel. Any type of information may be provided. In one embodiment alerts regarding detected events may be shown on the display, such as but not limited to, players changing their bets or bets being placed at the incorrect time.
As shown in
In one example embodiment the token 300 and DID technology 312 comprise a microchip having read and write memory, such as for example 256 bits, with one or more configurable sections to meet the particular application. Data may be entered into the DID device and sealed or encrypted to prevent fraud or tampering. In one embodiment, at least some of the data stored within the DID device may be changed or updated by a casino or when provided to a player.
The DID antenna 404 connects to a multiplexer or switch 420, which in this embodiment controls communication between a reader 424 and the antenna 404. It is contemplated that communication between the reader 424 and the one or more antenna 404 is bi-directional such that the reader may provide an electrical excitation signal to the antenna 404. The antenna 404 converts the electrical signal to an electro-magnetic field (EMF), which excites or powers the DID aspects of the token located within the detection zone. As a result and in response to the excitation EMF signal, the antenna may also detect data emitted from the DID device. The data is sent back, via the multiplexer 420, to the reader 424.
A token tray 280 may also be provided that reads and/or writes incoming and/or outgoing tokens. This provides the monitoring system with data regarding the tokens purchased by players and tokens collected by players. This allows the system to further track incoming and outgoing tokens. Tokens purchased by a player and not passing through the token tray 280, i.e. won or cashed in, may be assumed to have left with or been kept by the player. Tokens presented for play on the table that do not pass through the token tray 280 may be assumed to have been brought to the table by the player.
Operation of the other DID antenna associated with the other player stations occurs as described above. A dealer DID antenna 424 is also provided with the associated detection zone. One or more secondary bet or token spot antennas 428 with associated detection zones are also provided as shown. These elements 424, 428 also connect to the multiplexer/switch 420. Hence, the reader 424 may selectively read the DID information contained within the tokens placed at the bet spots as shown in
The reader 424 connects to any type processor which may be embodied in a computer 430 having memory 434. The computer is configured to execute machine readable code which may be stored on the memory 434. The machine readable code may comprise software code or code logic capable of interaction with other systems, such as the reader. Software code may be referred to herein as machine readable code. The computer 430 may include an input interface for receiving input from a user such as pit supervisory personnel or dealer, such as a keyboard, analog dial, potentiometer, mouse, touch screen, or any other device capable of providing information to the computer. The computer 430 may also be configured with one or more displays. The computer 430 will allow the input of information by pit supervisory personnel and/or a dealer.
In the embodiment shown in
The biometric interface 448 comprises any type system configured to monitor and identify players based on one or more player characteristics. In one such configuration a camera is capable of capturing a player's picture, such as of their face, and the biometric system compares the player's picture to a data base of known dishonest players or banned individuals. In another configuration the biometric system is capable of identifying a player through vein recognition such as by capturing a representation of a player's vascular system by an infrared camera. The biometric system 448 in connection with the bet detection system may be utilized to monitor for and identify certain players who may be attempting to gain an unfair advantage. One exemplary biometric system is available from Biometrica Systems, Inc in Las Vegas, Nev.
It is also contemplated that the computer 430 and the network 440 may be equipped to send and receive e-mail or other forms of electronic output. In one embodiment, the detection system, such as the computer 430, the network 440, or a mail server associated with the network, may be controlled to send e-mail, voice messages, or other notification to a party to alert or notify them of information generated by the detection system.
As used herein the term table monitoring system is defined to mean the entire system that monitors play on the table. At a high level, this may comprise one or more of the following, a RFID system, an overhead or table mounted camera, and/or a dealer interface. Also part of the table monitoring system are one or more peripheral devices such as those elements shown in
As can be appreciated, the engine must know how to interpret the incoming data from the various table monitoring components. One aspect that is used to interpret the data is for the engine to ‘know’ the game in play and the table layout. And for an engine to properly process the data, the engine preferably is able to properly interpret the data based on known information about the game in play, the table layout, and location of RFID antennas and which bet locations those antennas correspond to, the type of data provided from each peripheral, the required rules and procedures of the game, the required method of play for the players and the dealers, and any other aspect of the table monitoring system and game.
As shown in
The table identification provides a code or identification to the table monitoring system which may be used to retrieve a pre-stored set of control parameters which are used to interpret and/or process data received by the engine from the other components of the table monitoring system. Upon receiving this code, the proper control parameters may be retrieved from memory and used by the engine to properly interpret and process the incoming data.
As way of example, and not limitation,
The control parameters may also define the data received from the table's peripherals. As shown in the embodiment of
The control parameters may also be different for different versions of a particular peripheral. For example, different electronic card shoes may be in use and as such, different shoes, or different versions of the same shoe may have different data output characteristics, which should be known by the engine so that data from the peripherals may be properly interpreted and utilized.
As a result of providing a table identification on the table and associating control parameters with the table identification, the process of configuring the table monitoring system to properly function with the table and game played thereon is greatly reduced. If manually entered, the code is present on the table for easy reading and entry. If automatically read, the system may be fully automated, that is, upon use of the table, the table identification is read and processed by the system. Errors may be reduced, as the code is on the table, or in the case of an automated procedure, the process occurs automatically, thereby eliminating errors or failure to enter new table identification when a table or game is changed. An automated read process, as described below, is particularly helpful considering that tables or game rules may be switched multiple times per day.
With regard to
Also shown on
Felt layout codes are better understood based on
In the embodiment of
In reference to
In addition, a peripheral located at a particular grid coordinate may be identified as a particular peripheral based on its location at a grid location that is assigned to the peripheral. For example, a shuffler may be placed at 70, 5, 0 location. Thus, when the RFID or image system detects something at 70, 5, 0, the engine may conclude that whatever is at that location is the shuffler. Other means for identifying the shuffler are also possible in the event the shuffler is moved to accommodate a dealer.
Using overhead monitors and the grid arrays, the wagering areas 1608 may be monitored individually. Using image analysis, each betting area of the three bet locations 1608 can be distinguished based on the imaged area. The grid location of the wager is compared to the known grid locations for each wager area to determine at which known locations the wager was placed. The engine may thus determine where the wager was placed. The amount of the wager may also be determined by the image system or the RFID system.
Contained within the wager area 2108 are two wager locations 2116 and 2112. The single antenna RFID system is not capable of detecting upon which of the two wager areas 2112, 2116 the wager was placed. To account for this limitation, an overhead camera 1200 is configured to generate an image of the table and wager/cards thereon.
The predetermined and known table coordinates and the image data, and the mapping on to the grid to obtain grid coordinates for the wagers is shown in the figure associated with each wager and in the resulting table monitoring data shown in engine data 2120. The engine data comprises data collected from the wagering system. It comprises a combination of RFID data, chip ID numbers and location data. The time that the wager is places may be recorded by the system. In this manner, using a single RFID antenna for multiple wagering locations, and a camera/image monitoring system, the wagers may be accurately tracked. The RFID system provides information regarding the chip (token) serial number and denomination amount and in which antenna the wager is placed. Time information is also provided. The image information may be mapped into grid coordinates to determine upon which particular wagering area (within the detection zone of a single RFID antenna) the token was placed. Time information may also be provided with the image information. By cross-referencing this information, precise wager tracking may occur.
The engine data 2120 shows the types of data which may be collected from the single RFID antenna area with image tracking. In the embodiment of
The stack recognition event log shows the time and grid location for the separate stacks 2130 in the wager areas 2116, 2112. The RFID event log shows the RFID data collected when each stack 2130 is placed on the table. By cross-referencing these logs, and using the data as a reference, precise monitoring of the wagers placed in each wager area 2116, 2112 is possible even though both wager areas are within a single RFID antenna area.
In operation, it is farther contemplated that tagging may occur to facilitate and provide means for tracking. Tagging is defined herein as a system and method for the engine to associate a unique identifier with a wager or other table occurrence to thereby track the wager or occurrence during play. By assigning a tag to the event, such as for example, the wager tag may be used to track the wager. Other occurrences on the table, such as movement of the wager, may be tracked as being associated with the original tag. Payouts to the wager may also be assigned as sub-events associated with the tag, or create a new tag that is associated with or linked to the original wager.
In one embodiment the tag represents or contains all of the information associated with the event or game piece, such as wager. This may include but is not limited to player tracking card location, wager location, wager amount, wager time, wager token ID, game phase when wager was made, and player position of wager. In certain games, this wager may be moved to different locations on the table, or re-wagered by leaving the original wager on the table. Assigning a tag to the wager to represent the wager and the associated data, provides a simplified manner for the engine to track the tag.
If the wager or other element leaves the felt, the tag may expire, be closed, or continue to be tracked. The system may also discontinue tracking a tag if a wager or other element leaves the felt. Generally, an element leaves the felt when it is taken off the table such as when winnings are paid to a player and the player takes the tokens comprising the winnings off the gaming table. However, leaving the felt may also mean that the element is no longer relevant to the play of the game and thus in some embodiments an element may leave the felt without physically being taken off the table. It is contemplated that, tracking may be resumed if the wager or other element reenters the felt.
A data file may store the tag data and the tracking system may graphically or non-graphically utilize the tag to track table events. Use of a tag may minimize hardware by reducing the number of RFID antennas needed per player seat, for example, to monitor and track each betting option for a game such as baccarat, without using a tagging method as described, the RFID system will need to have a minimum of three separate antennas per betting option, which are typically Player, Banker and Tie bets per player seat. The tagging function will allow one antenna in combination of the imaging data to provide the needed information to distinguish each betting option per player seat made during each game. The tagging function will also allow an easier method to separately track and distinguish all bets made per betting option and per player seat as seen and practiced as backline, or simply, back betting. It is contemplated that the tagging function may be based solely on timing of the movement, adding, or subtracting wagers within one or more known periods of the game. Back betting is such that allows gamblers to wager behind or for the player which are seated at the gaming table.
In one embodiment, a wager may be tagged and payouts to that wager may also be tagged. Comparison between tag data and the pay out data may occur to verify that the payout is the proper match for the wager based on table or game parameters, such as payout rates, and to verify that the proper wager was paid. Linking a tag to a wager provides the benefit of distinguishing that each wager is credited and accumulated for each individual player. Linking a tag to a payout provides the advantage of monitoring and distinguishing the actual winnings of each player and thus provides a more accurate means of game and player tracking.
The following provides additional information and disclosure regarding the subject matter disclosed herein. As is understood, casinos around the world offer fast pace, high volume gambling activity on a wide variety of live action table games. This fast pace, high volume live gaming environment is vulnerable to various cheating methods that are performed by gamblers and employees that wish to gain an unfair advantage over the casino. In addition, casino management may desire to track game play to improve casino operation and casino management.
Currently, the technology disclosed herein can be used to create a table game monitoring apparatus that will expand upon the casino's toolset to accurately monitor and report all data regarding how a live table game has been played. In addition to reporting the historic data, the technology allows the monitoring apparatus to report real time events that may indicate that some sort of cheating or game play outside the rules of the game has occurred. The software may monitor, report, and store most if not all data associated with each live table game on a casino floor.
In general terms, within the field of view, the Overhead Optical Engine will provide real time data and events based on game piece placements and movements. In addition, the Optical Engine will provide environmental data that describes game attributes along with the available administrative items installed on the table.
For the purpose of this document, game pieces are defined as all the pieces and items that allow a live game to be played from its beginning to its full conclusion. In addition, there are administrative items that casino personnel use on a regular basis that helps to manage the operation of the gaming table between and during games and may or may not have any direct relationship to the game play. Generally, game pieces can be categorized as wagering pieces, playing pieces, and administration items.
Wagering pieces are the physical items that the player will use to place bets with. The player will usually place these pieces in a predefined area within the playing area of the game. These wagering items can simply be gaming chips, tokens, plagues, or real currency such as paper money or coin. Playing pieces are the devices that are used during the game play that will determine the final outcome of the actual game being played. These devices can be playing cards, dice, balls (in conjunction with a roulette wheel), or tiles. Administrative items can be categorized as either static or dynamic items. The static items will typically be items such as the felt layout, drop box slot, discard rack, or tip box slot. The dynamic pieces would be items such as the cut card, roulette marker, player rating cards, or in some cases, special devices used by the dealer to indicate the current state of the game being played or the actual outcome of the game.
Also disclosed herein is Optical Engine Logic. The Optical Engine logic will use image capturing hardware and electronics along with the proper recognition algorithms in order to distinguish all game piece items on a live table game in a real time manner. The Optical Engine may be configured to: a) provide data on command that describes the administrative components installed on the game, b) provide an event when it senses the presence of any new game pieces, c) provide an event when a previously detected game piece has moved from one zone to another, d) provide an event when any previously recognized and tagged item has been removed from the field of view of the image capturing hardware, and e) provide a game piece change of state event. Each event will provide the administrative data that will include time stamp data and the normal packet wrappers.
Also disclosed herein is Administrative Component Data. Administrative components can be defined as either being static or dynamic items. Static types are items that remain constant throughout any game cycle and may infrequently. Static items can be felt layouts, chip trays, the slot of the drop box and tip box, a discard rack, a card shoe, etc. Dynamic types are items that are intermittent and may not be used during each game cycle. One such item could be the shuffle card that indicates when a new shuffle is needed for the shoe.
The static items may be the components that will be more detailed as the concept is such that will allow automatic configuration and association of game engines to physical tables based on the optical engine decoding the static components. The main component to define is the felt layout as follows:
The next components are items such as the chip tray, drop box and tip box slots, and other devices that are permanent or semi-permanent static items. These items can be marked with an encoding that the optical engine can easily decode. The encoding may at a minimum include a unique serial number per item. The optical engine should also include the zone in which each item has been detected. In the case of the chip tray and chip tray cover, the optical engine should provide events when the chip tray cover has either been removed or replaced (both events are useful to detect openers and closers of the game along with providing a security alert each time the chip tray cover has been removed).
Also disclosed herein is a New Game Piece Event. A New Game Piece Event may be formatted to include; a) a unique tag ID of the new item placed in the field of view, b) the game piece class, c) the game piece data (if applicable), d) the game piece state, e) the geographic location of the game piece, and f) the administrative details of the event.
Unique Tag ID
The unique tag ID (UTID) number could be based off a random number or a sequential number. However, regardless the method of assigning an ID number, UTID and will be unique for that game cycle and, ideally throughout a definable minimum period of time.
Game Piece Class
The game piece class defines the category in which the new game piece falls into. The game pieces classes can be grouped as follows:
The game piece data defines the value (if applicable) of the new game piece. This data could be the value of the playing card or the value of each rolled dice.
Game Piece State
The game piece state is reserved for items such as playing cards to detail whether the card is face up face down. This will allow the image capturing hardware and software to keep track of this type of device until the card has been turned over.
Game Piece Location
The game piece location data details the physical location of where the new game piece has been placed.
While various embodiments of the invention have been described, it will be apparent to those of ordinary skill in the art that many more embodiments and implementations are possible that are within the scope of this invention. In addition, the various features, elements, and embodiments described herein may be claimed or combined in any combination or arrangement.
Number | Name | Date | Kind |
---|---|---|---|
2410845 | Snell et al. | Nov 1946 | A |
2983354 | Ember et al. | May 1961 | A |
3034643 | Keller et al. | May 1962 | A |
3350802 | Segal | Nov 1967 | A |
3766452 | Burpee et al. | Oct 1973 | A |
D232367 | Garaventa | Aug 1974 | S |
D237724 | Garaventa | Nov 1975 | S |
D240053 | Garaventa | May 1976 | S |
3953932 | Graves | May 1976 | A |
3968582 | Jones | Jul 1976 | A |
3983646 | Howard | Oct 1976 | A |
4026309 | Howard | May 1977 | A |
4435911 | Jones | Mar 1984 | A |
4510495 | Sigrimis et al. | Apr 1985 | A |
4531187 | Uhland | Jul 1985 | A |
4814589 | Storch et al. | Mar 1989 | A |
4939354 | Priddy et al. | Jul 1990 | A |
5088093 | Storch et al. | Feb 1992 | A |
5103081 | Fisher et al. | Apr 1992 | A |
5166502 | Rendleman et al. | Nov 1992 | A |
5216234 | Bell | Jun 1993 | A |
5283422 | Storch et al. | Feb 1994 | A |
5332219 | Marnell et al. | Jul 1994 | A |
5345231 | Koo et al. | Sep 1994 | A |
5361885 | Modler | Nov 1994 | A |
5367148 | Storch et al. | Nov 1994 | A |
5374061 | Albrecht | Dec 1994 | A |
5406264 | Plonsky et al. | Apr 1995 | A |
5423551 | Stavinsky | Jun 1995 | A |
D361350 | Nelson | Aug 1995 | S |
5451756 | Holzer et al. | Sep 1995 | A |
5548106 | Liang et al. | Aug 1996 | A |
5548110 | Storch et al. | Aug 1996 | A |
5549300 | Sardarian | Aug 1996 | A |
5586936 | Bennett et al. | Dec 1996 | A |
5651548 | French et al. | Jul 1997 | A |
5676376 | Valley | Oct 1997 | A |
5681039 | Miller | Oct 1997 | A |
5683084 | Dean et al. | Nov 1997 | A |
D387391 | Jones et al. | Dec 1997 | S |
5707287 | McCrea, Jr. | Jan 1998 | A |
5722893 | Hill et al. | Mar 1998 | A |
5735742 | French | Apr 1998 | A |
5772505 | Garczynski et al. | Jun 1998 | A |
5785321 | van Putten et al. | Jul 1998 | A |
5803808 | Strisower | Sep 1998 | A |
5809482 | Strisower | Sep 1998 | A |
5831527 | Jones et al. | Nov 1998 | A |
D402331 | Serowik et al. | Dec 1998 | S |
D408868 | Floge et al. | Apr 1999 | S |
5890717 | Rosewarne et al. | Apr 1999 | A |
5898321 | Ilkbahar et al. | Apr 1999 | A |
5911626 | McCrea | Jun 1999 | A |
5919090 | Mothwurf | Jul 1999 | A |
5941769 | Order | Aug 1999 | A |
5947821 | Stone | Sep 1999 | A |
5951011 | Potter et al. | Sep 1999 | A |
5957776 | Hoehne | Sep 1999 | A |
D420401 | Bayne | Feb 2000 | S |
6021949 | Boiron | Feb 2000 | A |
D421466 | McBride | Mar 2000 | S |
6039650 | Hill | Mar 2000 | A |
6059659 | Busch et al. | May 2000 | A |
6062564 | Terminel | May 2000 | A |
D427644 | Stern | Jul 2000 | S |
6093103 | McCrea, Jr. | Jul 2000 | A |
6126166 | Lorson et al. | Oct 2000 | A |
6165069 | Sines et al. | Dec 2000 | A |
6186505 | Perrie et al. | Feb 2001 | B1 |
6186895 | Oliver | Feb 2001 | B1 |
6210275 | Olsen | Apr 2001 | B1 |
D442643 | Florence | May 2001 | S |
6267671 | Hogan | Jul 2001 | B1 |
6299534 | Breeding et al. | Oct 2001 | B1 |
6299536 | Hill | Oct 2001 | B1 |
6319125 | Acres | Nov 2001 | B1 |
D452283 | Regan, II et al. | Dec 2001 | S |
D459760 | Tamura et al. | Jul 2002 | S |
6460848 | Soltys et al. | Oct 2002 | B1 |
6464584 | Oliver | Oct 2002 | B2 |
D468367 | Florence et al. | Jan 2003 | S |
6514140 | Storch | Feb 2003 | B1 |
6517072 | McInerney | Feb 2003 | B1 |
6517073 | Vancura | Feb 2003 | B1 |
6517435 | Soltys et al. | Feb 2003 | B2 |
6517436 | Soltys et al. | Feb 2003 | B2 |
6520857 | Soltys et al. | Feb 2003 | B2 |
6527271 | Soltys et al. | Mar 2003 | B2 |
6530837 | Soltys et al. | Mar 2003 | B2 |
6533658 | Walker et al. | Mar 2003 | B1 |
6533662 | Soltys et al. | Mar 2003 | B2 |
6561897 | Bourbour et al. | May 2003 | B1 |
6568682 | Hogan et al. | May 2003 | B1 |
6579180 | Soltys et al. | Jun 2003 | B2 |
6579181 | Soltys et al. | Jun 2003 | B2 |
6581747 | Charlier et al. | Jun 2003 | B1 |
6582301 | Hill | Jun 2003 | B2 |
6590889 | Preuss et al. | Jul 2003 | B1 |
6595857 | Soltys et al. | Jul 2003 | B2 |
6604998 | Singer et al. | Aug 2003 | B1 |
6609710 | Order | Aug 2003 | B1 |
6612928 | Bradford et al. | Sep 2003 | B1 |
6619662 | Miller | Sep 2003 | B2 |
6626757 | Oliveras | Sep 2003 | B2 |
6629019 | Legge et al. | Sep 2003 | B2 |
6629591 | Griswold et al. | Oct 2003 | B1 |
6629889 | Mothwurf | Oct 2003 | B2 |
6633545 | Milbrandt | Oct 2003 | B1 |
6637746 | Baranauskas | Oct 2003 | B1 |
6638161 | Soltys et al. | Oct 2003 | B2 |
6646451 | Lanan | Nov 2003 | B2 |
6647058 | Bremer et al. | Nov 2003 | B1 |
6652379 | Soltys et al. | Nov 2003 | B2 |
6659875 | Purton | Dec 2003 | B2 |
6663490 | Soltys et al. | Dec 2003 | B2 |
6671311 | Raphaeli et al. | Dec 2003 | B1 |
6671358 | Seidman et al. | Dec 2003 | B1 |
6679492 | Markowiak | Jan 2004 | B2 |
6685564 | Oliver | Feb 2004 | B2 |
6685568 | Soltys et al. | Feb 2004 | B2 |
6688979 | Soltys et al. | Feb 2004 | B2 |
6690673 | Jarvis | Feb 2004 | B1 |
6709333 | Bradford et al. | Mar 2004 | B1 |
6711207 | Amrany et al. | Mar 2004 | B1 |
6712696 | Soltys et al. | Mar 2004 | B2 |
6733388 | Mothwurf | May 2004 | B2 |
6747560 | Stevens, III | Jun 2004 | B2 |
6758751 | Soltys et al. | Jul 2004 | B2 |
6829252 | Lewin et al. | Dec 2004 | B1 |
6834251 | Fletcher | Dec 2004 | B1 |
6843725 | Nelson | Jan 2005 | B2 |
6848994 | Knust et al. | Feb 2005 | B1 |
6908385 | Green | Jun 2005 | B2 |
6964416 | McClintic et al. | Nov 2005 | B2 |
6964612 | Soltys et al. | Nov 2005 | B2 |
6965205 | Piepgras et al. | Nov 2005 | B2 |
6967563 | Bormaster | Nov 2005 | B2 |
7018291 | Lemke et al. | Mar 2006 | B1 |
7152045 | Hoffman | Dec 2006 | B2 |
7172507 | Fujimoto et al. | Feb 2007 | B2 |
7559839 | Bahar | Jul 2009 | B2 |
20020084587 | Bennett et al. | Jul 2002 | A1 |
20020123376 | Walker et al. | Sep 2002 | A1 |
20020147042 | Vuong et al. | Oct 2002 | A1 |
20030064775 | Fujimoto et al. | Apr 2003 | A1 |
20030064798 | Grauzer et al. | Apr 2003 | A1 |
20030195025 | Hill | Oct 2003 | A1 |
20040207156 | Soltys et al. | Oct 2004 | A1 |
20050012269 | Grauzer et al. | Jan 2005 | A1 |
20050026682 | Grauzer et al. | Feb 2005 | A1 |
20050082750 | Grauzer et al. | Apr 2005 | A1 |
20050219599 | White et al. | Oct 2005 | A1 |
20050225080 | Wicker | Oct 2005 | A1 |
20050242506 | Yoseloff | Nov 2005 | A1 |
20060177109 | Storch | Aug 2006 | A1 |
20060252521 | Gururajan et al. | Nov 2006 | A1 |
20060258427 | Rowe et al. | Nov 2006 | A1 |
20060281537 | Abbott et al. | Dec 2006 | A1 |
20070026204 | Caulley et al. | Feb 2007 | A1 |
20070029394 | Wicker et al. | Feb 2007 | A1 |
20070035399 | Hecht et al. | Feb 2007 | A1 |
20070057469 | Grauzer et al. | Mar 2007 | A1 |
20070060311 | Rowe et al. | Mar 2007 | A1 |
20090124379 | Wells | May 2009 | A1 |
Number | Date | Country |
---|---|---|
P 44 39 502.7 | Nov 1994 | DE |
44 39 502 C 1 | Sep 1995 | DE |
WO 9706865 | Feb 1997 | WO |
WO 9818531 | May 1998 | WO |
WO 0022585 | Apr 2000 | WO |
WO 06037220 | Apr 2006 | WO |
Number | Date | Country | |
---|---|---|---|
20080180250 A1 | Jul 2008 | US |