US 7,967,682 B2Grant
Wireless gaming environment
Issue Date:2011-06-28
•17 Claims
•41 Drawing Sheets
Abstract
A system employs a server computing system with an integrated database and wireless communications devices, for example, handheld personal digital assistants (PDAs). The server computing system may also communicate with fully automated data collection systems associated with some gaming tables and/or with the casino's legacy data collection systems and databases. The server computing system may communicate with various non-gaming related casino systems, such as point-of-sale terminals and/or accounting systems, related to the various guest facilities, for example, allowing player comps to be freely exchanged for services and merchandise. The wireless communications devices permit remote wagering.
Metadata
Assignee
- Bally Gaming, Inc.
Inventor
- Richard Huizinga
Application Information
Application Number:US 11/480,274
Filing Date:2006-06-30
Priority Date:2006-04-12
Art Unit:3717
Classifications
IPC:
G06F17/00G06F19/00
Patent Drawings (41 sheets)
Description
Cross-Reference to Related Application
[0001] This application claims the benefit under 35 U.S.C. §119(e) of U.S. Provisional Patent Application Ser. No. 60/791,397 filed Apr. 12, 2006.
Background of the Invention
[0002] 1. Field of the Invention
[0003] This description generally relates to the field of wagering or gaming, and more particularly to facilitating the monitoring of activities at various wagering games, and automating the gaming environment via communications devices, for example, handheld wireless communications devices.
[0004] 2. Description of the Related Art
[0005] Gaming has enjoyed phenomenal growth over the recent past, with the addition of numerous forms of wager based gaming, the legalization of wagering in a large number of jurisdictions domestically and internationally, and the construction of numerous casinos to service the increasing demand for gaming opportunities.
[0006] Casinos provide a large variety of games and other forms of entertainment of its customers. For example, casinos may provide gaming machines such as slot machines, video slot machines or video poker machines. Casinos also provide table games such as blackjack, various types of poker, craps, roulette, baccarat, big wheel or wheel of fortune, to name a few. Due to the large amounts of money, particularly cash involved in gaming, casinos must carefully monitor the activities of both players and casino employees. Careful and continuous monitoring of gaming activities not only enhances security, but also permits the management to better manage the casinos' business, for example, selecting the number of mix of tables, the hours of operation of various tables, staffing, etc.
[0007] Most casinos employee a large number of individuals to manually track the gaming activities. These individuals, often referred to as “pit bosses” observe the activity at various tables and/or gaming machines, and manually record the activity. In some casinos, the manually recorded information is later manually entered into one or more computing systems. This information may include information regarding the dealer's performance, for example, the number of hands dealt during all or a portion of a dealer's shift, average house take, etc. This information may also include information regarding a player's performance, for example, time spent wagering, average wager, etc. The manual system suffers numerous drawbacks, including the delay in entry and processing of the information by the computing systems, if any, the use of disparate databases to store information, and the added opportunity to introduce errors while transferring the information from manually record sheets to the computing systems.
[0008] A number of systems have been proposed for automating certain aspects of tracking a player's performance. Many casinos employ player identification or “comp” cards to identify players and automated systems for monitoring how long a player remains at a gaming table. In such systems, the time is typically determined as the time between a first reading of the comp card when the player arrives at a gaming table and a second reading when the player leaves the gaming table. These systems typically rely on manual observations to 1) guess the average amount of a player's wagering, and 2) guess the average number of hands per unit of time, in order to estimate the amount wagered and consequently the amount of complimentary benefit to be awarded to the player. Some players have learned to take advantage of these systems to enhance the value of complimentary benefits, commonly referred to as “comps,” received by increasing their bet amounts when the pit boss is watching, and reducing their bet amounts when the pit boss is not watching.
[0009] Some of the Applicants' prior patent applications have taught the full automation of data collection for both player information and casino personnel information, in the context of certain table games, for example blackjack. Such fully automated data collection may not be suitable to all wagering games. Economically, some casinos may only be able to automate a portion of its games in the short term, making fully automated data collection and integration across the entire casino floor a long-term investment.
[0010] Additionally, many of the proposed systems do not address the various non-gaming aspects of the casino's business, for example, providing guest facilities such as guest rooms, restaurants, coffee shops, souvenir or gift shops, gymnasiums, and/or childcare facilities, or providing other forms of entertainment such as shows and nightclubs.
[0011] Further, many casinos experience a wide fluctuation in the number of customers who wish to play or otherwise enjoy the various accommodations offered by the casino. These fluctuations may be periodic, for example daily, weekly, monthly or yearly, or may be non-periodic, for example during special events. The building and staffing of new casino facilities is daunting. Zoning, the cost of land, the cost of construction, and the costs associated with background checking, training and keeping casino staff available are substantial. Casino operators are thus typically presented with the unenviable decision of committing significant resources to building and staffing sufficiently to accommodate the maximum number of players during times of high demand, or risk losing business during times of high demand.
[0012] Like any business, casinos can greatly benefit by increasing the timeliness and accuracy of data capture, and by seamlessly integrating the data in its various database systems. Casinos can also greatly benefit if variations in demand can be accommodated without building and staffing new facilities.
Brief Summary of the Invention
[0013] The manual data entry system that casino pit personnel currently employ for player tracking is replaced, at least in part, with a system employing wireless communications devices, for example, handheld personal digital assistants (PDAs), and a server computing system with an integrated database. The server computing system may also communicate with fully automated data collection systems associated with some gaming tables and/or with the casino's legacy data collection systems and databases. Further, the server computing system may communicate with various non-gaming related casino systems, such as point-of-sale (POS) terminals and/or accounting systems, related to the various guest facilities. For example, the server computing system may allow player comps to be freely exchanged for services and merchandise, for example rooms, meals, drinks, tickets to shows, and/or daycare services.
[0014] Additionally, or alternatively, a system employing wireless communications devices, for example, handheld personal digital assistants (PDAs), and a server computing system with an integrated database, may allow players to wager and access other casino facilities. The system may, for example, allow players to play wagering games without physically occupying the limited number of positions available at the casino's gaming tables, thereby allowing a casino to accommodate additional patrons without having to build and/or staff additional facilities. The server computing system may also communicate with fully automated data collection systems associated with some gaming tables and/or with the casino's legacy data collection systems and databases. Further, the server computing system may communicate with various non-gaming related casino systems, such as point-of-sale (POS) terminals and/or accounting systems, related to the various guest facilities. For example, the server computing system may allow player comps to be freely exchanged for services and merchandise, for example, rooms, meals, drinks, tickets to shows, and/or daycare services. Communications may advantageously employ wager transaction packets which may transmit intact, all information used in placing a wager.
Brief Description of the Several Views of the Drawings
[0015] In the drawings, identical reference numbers identify similar elements or acts. The sizes and relative positions of elements in the drawings are not necessarily drawn to scale. For example, the shapes of various elements and angles are not drawn to scale, and some of these elements and angles are arbitrarily enlarged and positioned to improve drawing legibility. Further, the particular shapes of the elements as drawn, are not intended to convey any information regarding the actual shape of the particular elements, and have been solely selected for ease of recognition in the drawings.
[0016] FIG. 1 is a schematic diagram of a casino communications system employing a network comprising a number of wired access points such as pit podium personal computers, a number of wireless communications devices, a number of wireless access points for providing communications with the wireless communications devices, and a server computing system, according to one illustrated embodiment.
[0017] FIG. 2 is a front plan view of a wireless communications device suitable for use as part of the casino communications system of FIG. 1 , according to one illustrated embodiment.
[0018] FIG. 3 is a functional block diagram of a wireless communications device suitable for use as part of the casino communications system of FIG. 1 , according to one illustrated embodiment.
[0019] FIG. 4 is a schematic diagram of a casino communications system integrated with a legacy casino management system according to one illustrated embodiment.
[0020] FIG. 5 is a schematic diagram of a data exchange model for the casino communications system according to one illustrated embodiment.
[0021] FIG. 6 is a front plan view of the wireless communications device of FIG. 1 , showing a login screen of a graphical user interface, according to one illustrated embodiment.
[0022] FIG. 7A is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a tracking screen of a graphical user interface, according to one illustrated embodiment.
[0023] FIG. 7B is a front plan view of the tracking screen of FIG. 7A .
[0024] FIG. 8 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a position selection screen of a graphical user interface, according to one illustrated embodiment.
[0025] FIG. 9A is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a fill request screen of a graphical user interface, according to one illustrated embodiment.
[0026] FIG. 9B is a front plan view of the fill request screen of FIG. 9A .
[0027] FIG. 10A is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a credit request screen of a graphical user interface, according to one illustrated embodiment.
[0028] FIG. 10B is a front plan view of the credit request screen of FIG. 10A .
[0029] FIG. 11A is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a view position screen of a graphical user interface, according to one illustrated embodiment.
[0030] FIG. 11B is a front plan view of the view position screen of FIG. 11A .
[0031] FIG. 12 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of an assign new player screen of a graphical user interface, according to one illustrated embodiment.
[0032] FIG. 13 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a search results screen of a graphical user interface, according to one illustrated embodiment.
[0033] FIG. 14 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of an end session screen of a graphical user interface, according to one illustrated embodiment.
[0034] FIG. 15 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a move player screen of a graphical user interface, according to one illustrated embodiment.
[0035] FIG. 16 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a markers screen of a graphical user interface, according to one illustrated embodiment.
[0036] FIG. 17 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a player's photo screen of a graphical user interface, according to one illustrated embodiment.
[0037] FIGS. 18A-18B are a flow diagram of a method of operating a user interface of a wireless communications device, according to one illustrated embodiment.
[0038] FIG. 19 is a flow diagram of a method useful for controlling remote wagering directly on a game occurring at a gaming table, without intermediary decisions or actions by the player(s), according to one illustrated embodiment.
[0039] FIGS. 20A-20B are a flow diagram of a method useful for controlling remote wagering directly on a game occurring at a gaming table, with intermediary decisions or actions by the player(s), according to one illustrated embodiment.
[0040] FIG. 21 is a flow diagram of a method useful for controlling remote wagering indirectly on a game occurring at a table game or on a gaming machine by a secondary player, without intermediary actions or decisions by the secondary players, according to one illustrated embodiment.
[0041] FIGS. 22A-22B are a flow diagram of a method useful for controlling remote wagering indirectly on a game occurring at a table game or on a gaming machine with intermediary actions of decisions by the primary player(s), according to one illustrated embodiment.
[0042] FIG. 23 is a flow diagram of a method in which wagers are accepted if entered into the wireless communications device before initial and/or intermediary wagers are locked out, according to one illustrated embodiment.
[0043] FIG. 24 is a flow diagram of a method in which wagers are accepted if received by a casino server computing system before initial and/or intermediary wagers are locked out, according to one illustrated embodiment.
[0044] FIG. 25 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a game type selection screen of a graphical user interface, according to one illustrated embodiment.
[0045] FIG. 26 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a table limit screen of a graphical user interface, according to one illustrated embodiment.
[0046] FIG. 27 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a select game screen of a graphical user interface, according to one illustrated embodiment.
[0047] FIG. 28 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a backline wagering screen of a graphical user interface, according to one illustrated embodiment.
[0048] FIG. 29 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a place wager screen of a graphical user interface, according to one illustrated embodiment.
[0049] FIG. 30 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a wager accepted screen of a graphical user interface, according to one illustrated embodiment.
[0050] FIG. 31 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a wager declined screen of a graphical user interface, according to one illustrated embodiment.
[0051] FIG. 32 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a wager open screen of a graphical user interface, according to one illustrated embodiment.
[0052] FIG. 33 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a wager closing screen of a graphical user interface, according to one illustrated embodiment.
[0053] FIG. 34 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a wager closed screen of a graphical user interface, according to one illustrated embodiment.
[0054] FIG. 35 is a front plan view of the wireless communications device of FIG. 1 , showing a portion of a game view screen of a graphical user interface, according to one illustrated embodiment.
[0055] FIG. 36 is a schematic diagram of a data structure suitable to implement the wager transaction packet structure, according to one illustrated embodiment.
[0056] FIG. 37 is a schematic diagram of a data structure suitable to implement the wager transaction packet structure, according to another illustrated embodiment.
[0057] FIG. 38 is a flow diagram of a method of operating the casino server computing system, according to one illustrated embodiment.
Detailed Description of the Invention
[0058] In the following description, certain specific details are set forth in order to provide a thorough understanding of various embodiments of the invention. However, one skilled in the art will understand that the invention may be practiced without these details. In other instances, well-known structures associated with cameras, imagers, scanners, optics, computers, computer networks, data structures, databases, and networks such as the Internet or cellular networks, have not been described in detail to avoid unnecessarily obscuring the descriptions of the embodiments of the invention.
[0059] Unless the context requires otherwise, throughout the specification and claims which follow, the word “comprise” and variations thereof, such as “comprises” and “comprising” are to be construed in an open, inclusive sense, that is as “including but not limited to.”
[0060] Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0061] The headings provided herein are for convenience only and do not interpret the scope or meaning of the claimed invention.
Environment
[0062] FIG. 1 shows a gaming environment such as a casino 10, having a number of areas for performing, participating or otherwise engaging in various activities typically associated with casinos. For example, the casino 10 may include a number of gaming areas 12 devoted to gaming activities. Gaming areas 12 may include a number of games such as banks of gaming machines 14 and/or gaming tables such as blackjack 16, baccarat 18, poker 20, roulette 22, and/or big wheel 24 tables to name a few. Only one gaming area and only one of each type of table is enumerated in FIG. 1 for the sake of clarity of illustration. The games may be clustered in groups commonly referred to as pits. Also for example, the casino 10 may include one or more customer facility areas 26 devoted to customer facilities such as guest rooms, restaurants, coffee shops, souvenir or gift shops, gymnasiums, restrooms, and/or childcare facilities. Also for example, the casino 10 may include one or more entertainment areas 28 such as theaters or nightclubs or play areas. The casino may further include one or more backroom areas 30, such as counting rooms and/or cashiers' or tellers' cages. These areas 12, 26, 28 are typically connected by walkways 32.
[0063] The casino may employ a network 34. The network 34 may include a number of wired access points such as pit podium personal computers 36 linked to the network 34 by one or more network switches 38. Note only one pit podium personal computer 36 and only one network switch 38 is enumerated in FIG. 1 for the sake of clarity or presentation. In typical use, the pit podium personal computers 36 will provide information to casino personnel such as dealers or pit bosses, regarding a specific player's performance, previous history with the casino, and/or preferences. Additionally, the pit podium personal computers 36 may be manually operated by authorized casino personnel, for entering gaming information.
[0064] The network 34 may additionally or alternatively include a number of wireless access points 40 linked to the network 34 by one or more network switches 38. Note only one wireless access point 40 is enumerated in FIG. 1 for the sake of clarity of presentation. The wireless access points 40 include receivers and antennas, and may also include transmitters to allow wireless communications with one or more casino server computing systems 42 by one or more wireless communications devices 44 via the network 34. Note only one wireless communications device 44 is enumerated in FIG. 1 for the sake of clarity or presentation.
[0065] In one embodiment, the wireless communications devices 44 are distributed to authorized casino personnel, such as pit bosses, to allow the casino personnel to manually enter information regarding customers or players, and/or employees such as dealers, servers or wait staff. In another embodiment, the wireless communications devices 44 are distributed to customers or players, for example, to allow players to play, track their own comps and/or to order services and merchandise such as food, drinks, tickets, parking valet, cleaning, room service, etc.
[0066] The wireless access points 40 may be distributed about the casino 10, including one or more floors, to provide wireless coverage of all or selected portions of the casino 10. For example, the wireless access points 40 may be distributed in a grid pattern, and attached to the ceiling or walls of the casino 10. The wireless access points 40 may be attached to various equipment or structures such as the gaming tables 16-24 and/or gaming machine banks 14. The wireless access points 40 may further be distributed in guest rooms (not shown).
[0067] While illustrated as a single network 34, the network may be composed of one or more networks, interconnected via various bridges, routers and/or other network equipment, as will be readily apparent to one of skill in the art. While FIG. 1 illustrates a number of pit podium personal computers 36 and wireless access points 40 positioned within the casino 10, in some embodiments one or more wired or wireless access points may exist outside of the casino 10, as will be readily apparent to those of ordinary skill in the art.
[0068] FIGS. 2 and 3 shows a wireless communications device 44 according to one illustrated embodiment. The wireless communications devices 44 may take the form of personal digital assistants (PDAs), handheld personal computers (PCs), appropriately configured cellular telephones, or other handheld communications devices. Suitable wireless communications devices 44 may, for example, take the form of devices with wireless local area network (WLAN) capability per IEEE specification 802.11b.
[0069] The wireless communications devices 44 may include a user interface such as a keyboard or keypad 46 and/or display 48 such as a liquid crystal display (LCD) which may, or may not, be touch-sensitive to serve as a user input device. Where the display 48 is touch-sensitive, the wireless communications devices 44 may also include a stylus 49 to enter information via the touch-sensitive display 48. The wireless communications devices 44 may also include a magnetic strip reader 50 to read identifying information from media such as player complimentary (“comp”) cards, and/or credit, debit and gift cards moved through a slot 51.
[0070] The wireless communications devices 44 may include a processor 52, and memory such as random access memory (RAM) 54, Read Only Memory (ROM) 56, flash memory and/or electronically erasable programmable read only memory (EEPROM) coupled by one or more system buses 58 to store data and instructions for execution by the processor 52. The wireless communications devices 44 may also include a keypad driver to couple user entries at the keypad 46 to the processor 52, and/or a display driver 62 to couple display data from the processor 52 to the display 48.
[0071] The wireless communications devices 44 may also include a transmitter and receiver, or transceiver 64 under the control of the processor 52, and coupled to one or more antennas 66 to wirelessly transmit and/or receive information. Additionally, or alternatively, the wireless communications devices 44 may include an illuminator (not shown), for example, a laser or a light emitting diode (LED) such as an infrared LED to optically transmit information. Optical transmission requires line-of-sight between the transmitter and receiver, which is typically considered to be a disadvantage, but may be considered advantageous where security is a concern or where location determination is desirable.
[0072] The wireless communications devices 44 may optionally include a smartcard 67 or similar module. The smartcard 67 may encode a unique identifier which may be associated to a user, for example via a secure database operated by the casino. The smartcard 67 may be permanently secured in the wireless communications device 44. Alternatively, the smartcard 67 may be selectively removable therefrom and installable in another wireless communications device, allowing the user to easily upgrade wireless communications devices 44 or switch wireless communications devices 44, for example, based on the particular casino they are patronizing.
[0073] The unique identifier may advantageously be hardwired in the smartcard 67, and may not be read, copied or otherwise discernable without the destruction of the smartcard 67. For example, the unique identifier may be used to generate responses to identification queries produced by the casino system. The smartcard 67 may execute a cryptographic algorithm to generate the response using the unique identifier. In one embodiment, the cryptographic algorithm may take the form of a public/private key pair algorithm. The smart card 67 may also employ a seed or other value provided in the identification query in generating the response using the cryptographic algorithm. Consequently, the unique identifier and/or cryptographic algorithm is only known by the casino server computing system 42, and the unique identifier itself is never transmitted beyond the casino server computing system 42 or firewall associated therewith.
[0074] The identifying information may be related by the casino server computing system 42 to an equipment identifier physically associated with the wireless communication device (e.g., stored in memory 54, 56 or microprocessor 52). This may, for example, allow the casino server computing system 42 to determine whether a particular wireless communications device 44 is authorized for use, and also whether the particular user using the particular wireless communications device is the owner or authorized or registered user for the wireless communications device 44. Thus, the casino server computing system 42 may track stolen, lost or otherwise undesirable wireless communications devices 44, and deny access by such wireless communications devices 44 to the casino's automated facilities. Likewise, the casino server computing system 42 may track users who have bad debt, have been identified as cheaters or are otherwise undesirable, and deny access to the casino's automated facilities by smartcards 67 associated with such users. Further, the casino may rely on the smartcard 67 to verify the age of user attempting to place a wager. The user's age may be verified during a registration or authorization process. For example, casino personnel may verify age from a government issued identification document (e.g., drivers license, passport) as a prerequisite to receiving a smartcard 67 or to registering or otherwise authorizing the smartcard 67 for use in placing wagers. Allowing a minor to use a smartcard 67 may be considered a crime similar to lending a minor a driver's license. As a further example, a photograph of the authorized or registered smartcard user may be displayed by a wireless communications device 44 used by a casino employee, for example when suspicion exists that a minor is wagering. This approach may be enhanced with the use of biometric data captured by one or more biometric sensors, which may be a part of the wireless communications device 44 or a peripheral device. Biometric data may include iris scan, finger or thumbprints, voice samples, or other biometric measures.
[0075] The wireless communications devices 44 may optionally include a global positioning system (GPS) receiver 68 to receive GPS positioning information from one or more GPS satellites. The wireless communications device 44 may provide the global positioning data to the casino server computing system(s) 42 (FIG. 1 ). Additionally, or alternatively, the casino server computing system(s) 42 may optionally employ other means for determining the location of the wireless communications device 44, for example triangulation, delay between receipt of a signal by two or more wireless access points 40, determination of signal strength at two or more wireless access points 40, or other similar techniques.
[0076] FIG. 4 shows one embodiment of a casino communications system 70, employing the network 34, pit podium personal computers 36, network switches 38, wireless access points 40, the casino server computing system(s) 42, and wireless communications devices 44a, 44b, 44c. Additionally, the casino communications system 70 may include a variety of gaming table or gaming machine (e.g., slots, video slots, video poker) based automatic data collection systems 72a, 72b, 72c, such as the table game data collection system discussed in commonly assigned U.S. Pat. No. 6,460,848. These automatic data collection systems, collectively referenced as 72, may communicate over the network 34 with the casino server computing system(s) 42 via one or more of the network switches 38.
[0077] The casino communications system 70 may additionally or alternatively include an interface 74 to casino information services 76. For example, the interface 74 may include a digital subscriber line (DSL) or cable modem 78, a LAN or WAN connection 80 to a firewall or virtual private network (VPN) 82 between the modem 78 and a network switch 38.
[0078] The casino server computing system(s) 42 may serve as a proxy for the casino's legacy networked computing system(s) 84. The legacy networked computing system(s) 84 may, for example, comprise a local area network (LAN) 86 including a casino management system (CMS) 88, one or more casino personal computers 90, one or more network switches 92, and a router 94. The legacy networked computing system(s) 84 may, for example, include one or more of the following: existing player comp systems, security systems, reservation systems, room service systems, telephone billing systems, POS terminals and/or systems, accounting systems, employee tracking and monitoring systems.
[0079] FIG. 5 shows a data exchange model 100 illustrating bi-directional communications between the casino communications system 70 and the CMS 88 for facilitating the integration of information between pit podium personal computers 36, wireless communications devices 44, automatic data collection systems 72, and the legacy CMS 88. In particular, a real-time interface 102 provides time sensitive bi-directional communications between a database 104 via Java system 106 and a CMS database 108 via legacy system 110 (e.g., AS/400). For example, the real-time interface 102 may transfer player rating and/or player comp information. The database may communicate with one or more of the wireless communications devices 44 via suitable communications channels 112a, 112b. Additionally, a delayed queue interface 114 provides less time sensitive bi-directional communications between the casino communications system 70 and the CMS 88.
Monitoring/Tracking by Employees
[0080] FIG. 6 shows a login screen 150 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment.
[0081] The login screen 150 may include the name and/or advertisement 152 for the particular casino. The login screen 150 includes a user name field 154 for entry of a user name and a password field 156 for entry of a user password. Access is denied unless an authorized user name and corresponding password are entered into the appropriate fields 154, 156. A user-selectable login icon 158 allows the user to submit the user name and password for authentication/verification.
[0082] FIGS. 7A and 7B show a tracking screen 160 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The tracking screen 160 shows the active tables and/or players that are being tracked.
[0083] The tracking screen 160 includes a user-selectable scrollable bar 162 for viewing additional portions of the tracking screen 160. The tracking screen 160 also includes a user-selectable and scrollable menu 164 for identifying and selecting among a number of pits to display. The tracking screen 160 displays each gaming table and/or gaming machine in the selected pit as a separate row 166a-166f. Each player position at the gaming table or gaming machine is also identified by a suitable icon 168 (only one called out in the figures for sake of clarity of illustration). In the illustrated example, the tracking screen 160 shows a selected pit identified as PIT-02, which includes six (6) blackjack tables, each with seven (7) player positions. The tracking screen 160 may further include a user-selectable icon 170 for logging off.
[0084] FIG. 8 shows a position selection screen 180 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment.
[0085] The position selection screen 180 includes a pit identification field 182 and a table identification field 184. The table is represented as a row 186, with the various player positions 188 (only one called out in the figures for sake of clarity of illustration) represented across the row 186. A player position 188 may be identified and selected. The position selection screen 180 represents the selected player position 188 with a visual indicator, for example highlighting, different color, flashing, marqueeing, and/or enhanced size or line weight.
[0086] The position selection screen 180 also includes a user-selectable add row icon 190 to add a new gaming table or gaming machine to a pit. The position selection screen 180 further provides user-selectable request fill icon 192 and request credit icon 194 for requesting a fill or credit, and fill request field 196 and credit request field 198 to provide results or status of the requests.
[0087] FIGS. 9A and 9B show a fill request screen 200 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The fill request screen 200 is displayed in response to selection of the request fill icon 192 (FIG. 8 ). The fill request screen 200 may include a scroll bar 202 to allow a user to view all of the information on the fill request screen 200.
[0088] The fill request screen 200 has a number of fields 204 for entering a request fill amount for different denominations of chips, and a total field 206 for displaying a sum total of chips requested (e.g., sum of quantity times denomination for all requested denominations). The user can use the fill request screen 200 to request a chip tray loaded with specific quantities of chips of various denominations. The user then selects a fill request icon 208 to submit the request.
[0089] FIGS. 10A and 10B show a credit request screen 220 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The credit request screen 220 is displayed in response to selection of the request credit icon 194 (FIG. 8 ). The credit request screen 220 may include a scroll bar 222 to allow a user to view all of the information on the credit request screen 220.
[0090] The credit request screen 220 has a number of fields 224 for entering a credit request amount for different denominations of chips, and a total field 226 for displaying a sum total of chips requested (e.g., sum of quantity times denomination for all requested denominations). The user can use the credit request screen 220 to request a chip tray loaded with specific quantities of chips of various denominations. The user then selects a credit request icon 228 to submit the request.
[0091] FIGS. 11A and 11B show a view position screen 240 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The view position screen 240 allows a user to view and/or enter information (e.g., tracking, comps) about a specific player position using the wireless communications device 44.
[0092] The view position screen 240 includes a pit identification field 242, a table identification field 244 and a player identification field 246 which display pit identifier, table identifier and player identifier, respectively, of a selected pit, table and player. The view position screen 240 may also include player name field 248 and a player identifier field 250, to display a player name, if known, and a unique identifier assigned to the player for tracking purposes, respectively.
[0093] The view position screen 240 may also include a start date and time field 252 and a last update date and time field 254 that display a date and time that the player tracking starts and a date and time of a most recent update for the player, respectively.
[0094] The view position screen 240 may also include markers field 256, buy back field 258 and total field 260 to display any markers advanced by the player, player buy back of the makers, and a total outstanding amount, respectively.
[0095] The view position screen 240 may also include a chip buy in field 262 to display a player's existing chip buy in amount, and an add chip buy in field 264 where the user may enter an amount of chips the player is currently buying in with. The view position screen 240 may also include a cash buy in field 266 to display a player's existing cash buy in amount, and an add cash buy in field 268 where the user may enter an amount of cash the player is currently buying in with. The view position screen 240 may also include a cash bets lost field 270 to display a player's cash loss, and an add cash lost field 272 where the user may enter an amount of cash the player is currently losing. The view position screen 240 may also include an average bet field 274 to display the player's average bet, and an update average bet field 276 where the user may enter an updated amount of average bet for the player.
[0096] The view position screen 240 may also include a decision per hour field 278 where the user may enter a number representing the actual or estimated number of decisions the player is making per hour or some other periodic interval, and a skill level field 280 where the user may enter a value representing an estimated skill level of the player. A total wagered field 282 may display a total amount wagered to date by the player, and a theoretical win field 284 may display a total amount that of a theoretical win for the player.
[0097] The view position screen 240 may further include a user-selectable update icon 286 to submit newly entered information. A user-selectable end session icon 288 allows the user to indicate that a player has ended gaming, while a user-selectable move players icon 290 allows the user to indicate that a player has moved to a new gaming table or gaming machine. A user-selectable markers icon 292 allows the user to indicate the player has offered a maker, and in response to the selection of such may pass control to a suitable screen.
[0098] FIG. 12 shows an assign new player screen 300 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The assign new player screen 300 allows a user to enter a new player into the casino communications system 70 using the wireless communications device 44.
[0099] The assign new player screen 300 includes a pit identification field 302, a table identification field 304, and a player identification field 306 which display pit identifier, table identifier, and player identifier, respectively, of a selected pit, table, and player. The assign new player screen 300 may include a casino identifier field 308, where the user may enter a casino identifier. The assign new player screen 300 may also include a player identifier field 310 where the user may enter a player identifier, player first and second name fields 312, 314 where the user may enter player first and second name, respectively, and a city field 316 where the user may enter a city associated with the player such as a city of primary residence. Where known, this information helps to uniquely identify a player. The assign new player screen 300 may include a user-selectable search icon 316, which the user may use to lookup or otherwise search for a particular player based on the information entered into one or more of the fields of the assign new player screen 300.
[0100] FIG. 13 shows a search results screen 320 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The search results screen 300 provides a user with results in response to selection of the search icon 316 (FIG. 12 ) of the assign new player screen 300.
[0101] The search results screen 320 includes a pit identification field 322, a table identification field 324 and a player identification field 326 which display pit identifier, table identifier, and player identifier, respectively, of a selected pit, table, and player. The search results screen 320 lists names 328a, 328b of each player that matches the criteria identified or entered in the fields of the assign new player screen 300 when the search icon 316 was selected, with associated user-selectable icons 330a, 330b for selecting the associated name. The search results screen 320 may include a user-selectable search icon 332, selectable to perform further searching.
[0102] FIG. 14 shows an end session screen 340 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The end session screen 340 allows a user indicate when a player has stopped playing.
[0103] The end session screen 340 includes a pit identification field 342, a table identification field 344 and a player identification field 346 which display pit identifier, table identifier and player identifier, respectively, of a selected pit, table and player. The end session screen 340 also includes a player field 348 that identifies the player. The end session screen 340 further includes an end date and time field 350 that identifies the ending date and time and a walk amount field 352 where the user may enter an actual or estimated amount of money (cash, chips and/or vouchers) with which the player is walking away from the gaming table or piece of gaming equipment. A user-selectable end session icon 354 allows the user to provide the information into the remainder of the casino communications system 70.
[0104] FIG. 15 shows a move player screen 360 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The move player screen 360 allows a user to indicate when a player has moved to a new gaming table or gaming machine.
[0105] The move player screen 360 includes a pit identification field 362, a table identification field 364 and a player identification field 366 which display pit identifier, table identifier and player identifier, respectively, of a selected pit, table and player. The move player screen 360 also includes a player field 368 that identifies the player. The move player screen 360 further includes an end date and time field 370 that identifies the ending date and time and a walk amount field 372 where the user may enter an actual or estimated amount of money (cash, chips and/or vouchers) with which the player is walking away from the gaming table or piece of gaming equipment. A user-selectable end session icon 374 allows the user to provide the information into the remainder of the casino communications system 70.
[0106] FIG. 16 shows a markers screen 400 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The markers screen 400 allows a user track markers offered or made by players and buy back of the same by players. The markers screen 400 may be displayed in response to selection of the markers icon 292 (FIG. 11B ).
[0107] The markers screen 400 includes a pit identification field 402, a table identification field 404, and a player identification field 406 which display pit identifier, table identifier and player identifier, respectively, of a selected pit, table and player. The markers screen 400 also includes a player field 408 that identifies the player. The markers screen 400 further includes an available credit field 410 that displays an available credit amount for the identified player. A makers request field 412 and a buy back request field 414 allow the user to enter amounts indicative of a marker requested by the player or a buy back of a previous maker tendered by the player. The markers screen 400 includes a user-selectable submit icon 416 operable to submit the maker or buy back request to the remainder of the casino communications system 70. A marker log field 418 displays a list of outstanding markers for the player.
[0108] FIG. 17 shows a player's photo screen 430 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The player's photo screen 430 allows a user to see a photograph of a player, if any are on record and associable to the player based on entered player data (e.g., player first and/or last name, etc.).
[0109] The player's photo screen 430 include a photo field 432 in which the photograph is displayed in response to selection of the markers icon 292 (FIG. 11B ). The player's photo screen 430 may also include a player name field 434 where the player's name is displayed, if known. A user-selectable back icon 436 allows the user to move back to the previous screen.
[0110] FIG. 18 shows a method of operating a user interface of wireless communications device 44, according to one illustrated embodiment, where screens navigation is performed between four distinct levels.
[0111] The user may start at the login screen 150, entering a user name and password to gain access to the wireless communications device 44. Upon successfully logging on, the wireless communications device 44 displays home screen 160, allowing the user to select a pit and/or gaming table. In response to the selection of the pit and/or gaming table, the wireless communications device 44 displays the position selection screen 180, allowing the user to select various actions or functions.
[0112] For example, if the user selects request fill icon 192 (FIG. 8 ), the wireless communications device 44 displays the fill request screen 200. If the user selects the request credit icon 194 (FIG. 8 ), the wireless communications device 44 displays the credit request screen 220. If the user selects the add row icon 190 (FIG. 8 ), the wireless communications device 44 displays the view position screen 240, allowing the user to select various actions or functions.
[0113] For example, if the user wishes to assign a player, the wireless communications device 44 displays the assign player screen 304 where the user may enter identifying information for a player. If the user then selects the search icon 318 (FIG. 12 ), then the wireless communications device 44 displays the search results screen 320 (FIG. 13 ) with results of a search performed using the entered identifying information. This may allow the user to uniquely identify a player based on limited information.
[0114] If the user selects the end session icon 286 (FIG. 11B ), the wireless communications device 44 displays the end session screen 340 (FIG. 14 ), where the user can enter the actual or estimated walk amount.
[0115] If the user selects move player icon 290 (FIG. 11B ), the wireless communications device 44 displays the move player screen 360 (FIG. 15 ), where the user can enter the actual or estimated walk amount.
[0116] If the user selects the markers icon 292 (FIG. 11B ), the wireless communications device 44 displays the markers screen 402 (FIG. 16 ), where the user may enter a marker request amount or buy back amount. This may facilitate the issuing and buy back of markers.
[0117] If the user selects to view a photograph of the player, the wireless communications device 44 displays the player photo screen 430 (FIG. 17 ), with the photograph or picture, if any are available.
[0118] If the user selects the logout icon 170 (FIG. 7B ) from the home screen 160, the wireless communications device 44 displays a logout screen 151, which in some embodiments may be the same as, or similar to the login screen 150 (FIG. 6 ).
Wagering
[0119] Players may choose to locally wager by physically occupying a player position or physically placing a wager at a gaming table or at a piece of gaming equipment such as a slot machine, video slot machine or video poker machine. Alternatively, a player may chose to remotely wager without physically occupying a player position or physically placing a wager at a gaming table or at a piece of gaming equipment, using a wireless communications device 44. Wagering via a wireless communications device 44 may be particularly advantageous during times of high demand when the casino is busy or crowded, or when it is otherwise difficult to find an available player position at a gaming table or piece of gaming equipment. Alternatively, wagering via a wireless communications device 44 may advantageously allow players to wager in a more discreet fashion, and/or in a player preferred setting, for example a hotel room, lounge, restaurant, or theater.
[0120] When remotely wagering via the wireless communications device 44, the player may be physically present at or proximate the gaming table or piece of gaming equipment, and may even be able to observe the play on the gaming table or piece of gaming equipment. However, the player will not occupy a player position or have a wager physically placed at the gaming table (e.g., seat or bet circle) or piece of gaming equipment. Alternatively, the remotely wagering player may be physically distant from the gaming table or piece of gaming equipment, and unable to directly observe the play on the gaming table or piece of gaming equipment. As described in detail below, in such a situation the wireless communications device 44 may provide the player with a display and audio of the play at the gaming table, either as a video and audio feed of the actual play or as a simulation thereof. This allows the player to enjoy the experience of the sights and sounds of the game without the inconvenience of being physically present at the gaming table or piece of gaming equipment.
[0121] As used herein and in the claims, the terms “local wager,” “local wagering,” “locally wagering” or similar terms mean that the player is physically occupying a player position or has physically placed a wager at the gaming table or gaming machine. As used herein and in the claims, the terms “remote wager,” “remote wagering,” “remotely wagering” or similar terms mean that the player is not physically occupying a player position and has not physically placed a wager at the gaming table or gaming machine, even if the player is proximate the gaming table or gaming machine.
[0122] The player may choose to remotely wager directly, placing wagers directly on the outcome of the game using the wireless communications device 44. Alternatively, or additionally, the player may choose to remotely wager indirectly using the wireless communications device 44. For example, the player may place a “backline” wager on an outcome of play by another player who may occupy a position at the gaming table or piece of gaming equipment. A form of backline wagering is discussed in U.S. Pat. No. 6,991,544 issued Jan. 31, 2006. In such situations, the player directly playing the game may be denominated as the primary player and the player indirectly playing may be denominated as the secondary player. Such a situation may accommodate further orders of players, for example tertiary players.
[0123] Some games do not require or employ intermediary decisions after placing the wager (e.g., no decision on whether to take additional playing cards, increasing, decreasing, adding or removing wagers). Such games may, for example, include baccarat, roulette, wheel of fortune, craps, bingo, and/or keno. Other games typically include intermediary decisions by a player after placing the wager (e.g., whether to take additional playing cards, increasing, decreasing, adding or removing wagers). Such games may, for example, include blackjack, poker, and/or LET IT RIDE®.
[0124] Pieces of gaming equipment are typically configured to be played by individual players. Thus, the pieces of gaming equipment are typically “on demand” systems in that they are responsive to a single player, and the player may enter or exit play at any time, for example by placing a currency or a gaming chip in the gaming machine. In contrast, gaming tables are typically set up to handle multiple players at a time and typically have seven or more player positions and/or betting circles. Thus, anywhere from one to seven or more players may be playing a given gaming table. Players typically may enter or exit play at a gaming table only at completion of a game or round of a game.
[0125] In order to prevent players from obtaining an advantage over the casino and/or each other, it is important to exercise control over the timing of wager placement and/or removal of wagers. The dealer or other personnel typically perform this function, limiting the placement or removal of wagers to acceptable times or events. For example, in roulette a croupier may pass their hand over the table and announce no more bets while the wheel is spinning. Also for example, a stickman in craps may hold the dice until all wagers are placed, or a dealer in blackjack will wait until the wagers are placed before dealing the playing cards.
[0126] Controlling the timing of wager placement in remote wagering is a significant problem. The casino communications system should ensure that wagers are only placed at specified times or instances during the gaming. For example, the casino communications system may only allow wagers to be placed via the wireless communications devices 44 before playing cards are dealt, or 10 before a roulette wheel or wheel of fortune is spun. For some games, the casino communications system may allow wagers to be placed during the game, either at specific periods or in response to the occurrence of defined events. Thus, for example, the casino communications system may allow a split hand wager, an insurance wager or a double down wager to be placed after the initial playing cards have been dealt if the player is initially dealt a pair, if the dealer shows an Ace, or if the total for the player's initial two cards is ten or eleven, respectively. Alternatively, the casino communications system may allow wagers to be removed after each playing card is turned over, for example in the game known as LET IT RIDE®.
[0127] At set out herein, the particular approach used to control the timing of wagering will depend on a variety of factors, such as: 1) whether the remote wagering is in the gaming table environment or the gaming machine environment; 2) whether the game is intended for play by an individual player (e.g., on demand) or by multiple players; 3) whether the remote wagering is direct or indirect (i.e., backline); and/or 4) whether the game includes intermediary decisions (e.g., hitting, additional wagers, and/or removal of wagers during play) or not.
[0128] FIG. 19 shows a method 600, that is useful for controlling remote wagering directly on a game occurring, at a gaming table, without intermediary decisions or actions by the player(s).
[0129] Optionally at 602, the wireless communications device 44 and/or some other device provides the game odds, for example providing a visual and/or audio prompt to a player or potential player where the odds are fixed for certain types of games or for certain games and hence may be stored in the wireless communications device 44 or may be provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70. Alternatively, or additionally, the odds may be game or gaming table specific, and hence would typically be provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70.
[0130] At 604, the wireless communications device 44 and/or some other device announces the opening of initial wagering, for example providing a visual and/or audio prompt to a player or potential player. The announcement may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated when the particular gaming table is ready to accept initial wagers, typically between the end of one game or round and the start of a next game or round.
[0131] At 606, initial wagers, if any, are accepted. As discussed in more detail below, in one embodiment the wagers are accepted at the wireless communications device, while in another embodiment the wagers are accepted at the casino server computing system(s) 42 that is part of the casino communications system 70.
[0132] At 608, the wireless communications device 44 and/or some other device announces the time remaining for initial wagering, for example providing a visual and/or audio prompt to a player or potential player. The announcement may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated by or in response to events on or a timer associated with the particular gaming table, or may be provided in response to a timer or other clock signal generated by the wireless communications device. The announcement may be repeated from time to time, updating the amount of time remaining. Alternatively or additionally, a countdown of the remaining time may be visually and/or aurally provided for all or some portion of the period during which initial wagers are accepted.
[0133] At 610, initial wagers, if any, are accepted. As discussed in more detail below, in one embodiment the wagers are accepted at the wireless communications device, while in another embodiment the wagers are accepted at the casino server computing system(s) 42 that is part of the casino communications system 70.
[0134] At 612, the wireless communications device 44 and/or some other device announces the closure of initial wagering, for example providing a visual and/or audio prompt to a player or potential player, and locks out further wagers at 614. The announcement and/or lockout may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated by or in response to events on or a timer associated with the particular gaming table, or may be provided in response to a timer or other clock signal generated by the wireless communications device.
[0135] At 616, the game starts. For example, the game may start with the dealing of cards, rolling of dice, spinning of a wheel, or drawing of a number. At 618, the game stops. For example, the game may stop when hands of playing cards are resolved against each other or against a standard, when a dice comes to a stop, a wheel stops spinning or a set of numbers have been drawn. At 620, the initial wagers are reconciled based on the outcome of the game event(s), the wagers placed, and the odds. In some embodiments reconciliation may take place on the wireless communications device 44, advantageously reducing the computational burden on the casino server computing system(s) 42. In some embodiments reconciliation may take place on the casino server computing system(s) 42, advantageously providing enhanced security.
[0136] FIGS. 20A-20B show a method 630 that is useful for controlling remote wagering directly on a game occurring a gaming table, with intermediary decisions or actions by the player(s).
[0137] Optionally at 632, the wireless communications device 44 and/or some other device provides the game odds, for example providing a visual and/or audio prompt to a player or potential player where the odds are fixed for certain types of games or for certain games and hence may be stored in the wireless communications device 44 or may be provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70. Alternatively, or additionally, the odds may be game or gaming table specific, and hence would typically be provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70.
[0138] At 634, the wireless communications device 44 and/or some other device announces the opening of initial wagering, for example providing a visual and/or audio prompt to a player or potential player. The announcement may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated when the particular gaming table is ready to accept initial wagers, typically between the end of one game or round and the start of a next game or round.
[0139] At 636, initial wagers, if any, are accepted. As discussed in more detail below, in one embodiment the wagers are accepted at the wireless communications device, while in another embodiment the wagers are accepted at the casino server computing system(s) 42 that is part of the casino communications system 70.
[0140] At 638, the wireless communications device 44 and/or some other device announces the time remaining for initial wagering, for example providing a visual and/or audio prompt to a player or potential player. The announcement may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated by or in response to events on or a timer associated with the particular gaming table, or may be provided in response to a timer or other clock signal generated by the wireless communications device. The announcement may be repeated from time to time, updating the amount of time remaining. Alternatively or additionally, a countdown of the remaining time may be visually and/or aurally provided for all or some portion of the period during which initial wagers are accepted.
[0141] At 640, initial wagers, if any, are accepted. As discussed in more detail below, in one embodiment the wagers are accepted at the wireless communications device, while in another embodiment the wagers are accepted at the casino server computing system(s) 42 that is part of the casino communications system 70.
[0142] At 642, the wireless communications device 44 and/or some other device announces the closure of initial wagering, for example providing a visual and/or audio prompt to a player or potential player, and at 644 further wagers are locked out. The announcement and/or lockout may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated by or in response to events on or a timer associated with the particular gaming table, or may be provided in response to a timer or other clock signal generated by the wireless communications device.
[0143] At 646, the game starts. For example, the game may start with the dealing of cards, rolling of dice, spinning of a wheel, or drawing of a number.
[0144] At 647, the occurrence of a game event or a time is determined. For example, a game event may be the dealing of a first playing card, last playing card or other playing card, the spin of a wheel, a spinning wheel coming to a stop, roll of dice, an action by a player, dealer, other participant, or other casino personnel. The determination may be performed using sensors at the gaming table, or based on information from such sensors. Also for example, time may be a period based on a time of day, week or year or on a period after or before the occurrence of an action or event occurring at the gaming table or elsewhere.
[0145] At 648, the wireless communications device 44 and/or some other device announces the opening of intermediary wagering, for example providing a visual and/or audio prompt to a player or potential player. The announcement may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated when the particular gaming table is ready to accept intermediary wagers, typically between the end of one game or round and the start of a next game or round.
[0146] At 650, intermediary wagers, if any, are accepted. As discussed in more detail below, in one embodiment the wagers are accepted at the wireless communications device, while in another embodiment the wagers are accepted at the casino server computing system(s) 42 that is part of the casino communications system 70.
[0147] At 652, the wireless communications device 44 and/or some other device announces the time remaining for intermediary wagering, for example providing a visual and/or audio prompt to a player or potential player. The announcement may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated by or in response to events on or a timer associated with the particular gaming table, or may be provided in response to a timer or other clock signal generated by the wireless communications device. The announcement may be repeated from time to time, updating the amount of time remaining. Alternatively or additionally, a countdown of the remaining time may be visually and/or aurally provided for all or some portion of the period during which intermediary wagers are accepted.
[0148] At 654, intermediary wagers, if any, are accepted. As discussed in more detail below, in one embodiment the wagers are accepted at the wireless communications device, while in another embodiment the wagers are accepted at the casino server computing system(s) 42 that is part of the casino communications system 70.
[0149] At 656, the wireless communications device 44 and/or some other device announces the closure of intermediary wagering, for example providing a visual and/or audio prompt to a player or potential player, and locks out further wagers at 658. The announcement and/or lockout may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated by or in response to events on or a timer associated with the particular gaming table, or may be provided in response to a timer or other clock signal generated by the wireless communications device.
[0150] At 660, the game stops. For example, the game may stop when hands of playing cards are resolved against each other or against a standard, when a dice comes to a stop, a wheel stops spinning or a set of numbers have been drawn. At 662, the initial wagers are reconciled based on the outcome of the game event(s), the wagers placed, and the odds. In some embodiments reconciliation may take place on the wireless communications device 44, advantageously reducing the computational burden on the casino server computing system(s) 42. In some embodiments reconciliation may take place on the casino server computing system(s) 42, advantageously providing enhanced security.
[0151] FIG. 21 shows a method 700 that is useful for controlling remote wagering indirectly on a game occurring at a table game or on a gaming machine by a secondary player, without intermediary actions or decisions by the secondary players.
[0152] Optionally at 702, the wireless communications device 44 and/or some other device provides the primary player odds, for example providing a visual and/or audio prompt to a secondary player or potential secondary player. The primary player odds will typically vary over time, thus the primary player odds may be provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70.
[0153] At 704, the wireless communications device 44 and/or some other device announces the opening of initial wagering, for example providing a visual and/or audio prompt to a secondary player or potential secondary player. The announcement may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated when the particular gaming table is ready to accept initial wagers by the secondary player(s), typically between the end of one game or round and the start of a next game or round.
[0154] At 706, initial wagers, if any, are accepted. As discussed in more detail below, in one embodiment the wagers are accepted at the wireless communications device, while in another embodiment the wagers are accepted at the casino server computing system(s) 42 that is part of the casino communications system 70.
[0155] At 708, the wireless communications device 44 and/or some other device announces the time remaining for initial wagering, for example providing a visual and/or audio prompt to a secondary player or potential secondary player. The announcement may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated by or in response to events on or a timer associated with the particular gaming table, or may be provided in response to a timer or other clock signal generated by the wireless communications device. The announcement may be repeated from time to time, updating the amount of time remaining. Alternatively or additionally, a countdown of the remaining time may be visually and/or aurally provided for all or some portion of the period during which initial wagers are accepted.
[0156] At 710, initial wagers from the secondary player(s), if any, are accepted. As discussed in more detail below, in one embodiment the wagers are accepted at the wireless communications device, while in another embodiment the wagers are accepted at the casino server computing system(s) 42 that is part of the casino communications system 70.
[0157] At 712, the wireless communications device 44 and/or some other device announces the closure of initial wagering, for example providing a visual and/or audio prompt to a secondary player or potential secondary player, and locks out further wagers at 714. The announcement and/or lockout may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated by or in response to events on or a timer associated with the particular gaming table, or may be provided in response to a timer or other clock signal generated by the wireless communications device.
[0158] At 716, the game starts. For example, the game may start with the dealing of cards, rolling of dice, spinning of a wheel, or drawing of a number. At 718, the game stops. For example, the game may stop when hands of playing cards are resolved against each other or against a standard, when a dice comes to a stop, a wheel stops spinning or a set of numbers have been drawn. At 720, the initial primary and secondary wagers are reconciled based at least in part on the outcome of the game event(s), the primary and secondary wagers placed, and the primary odds (i.e., game odds) and secondary odds (i.e., odds for particular primary player). In some embodiments reconciliation may take place on the wireless communications device 44, advantageously reducing the computational burden on the casino server computing system(s) 42. In some embodiments reconciliation may take place on the casino server computing system(s) 42, advantageously providing enhanced security.
[0159] At 722, the casino server computer updates the primary player odds based at least in part on the outcome of the game.
[0160] FIGS. 22A-22B show a method 730 that is useful for controlling remote wagering indirectly on a game occurring at a table game or on a gaming machine with intermediary actions of decisions by the primary player(s).
[0161] Optionally at 732, the wireless communications device 44 and/or some other device provides the primary player odds, for example providing a visual and/or audio prompt to a secondary player or potential secondary player. The primary-player odds will typically vary over time, thus the primary player odds may be provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70.
[0162] At 734, the wireless communications device 44 and/or some other device announces the opening of initial wagering, for example providing a visual and/or audio prompt to a secondary player or potential secondary player. The announcement may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated when the particular gaming table is ready to accept initial wagers, typically between the end of one game or round and the start of a next game or round.
[0163] At 736, initial wagers, if any, are accepted. As discussed in more detail below, in one embodiment the wagers are accepted at the wireless communications device, while in another embodiment the wagers are accepted at the casino server computing system(s) 42 that is part of the casino communications system 70.
[0164] At 738, the wireless communications device 44 and/or some other device announces the time remaining for initial wagering, for example providing a visual and/or audio prompt to a secondary player or potential secondary player. The announcement may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated by or in response to events on or a timer associated with the particular gaming table, or may be provided in response to a timer or other clock signal generated by the wireless communications device. The announcement may be repeated from time to time, updating the amount of time remaining. Alternatively or additionally, a countdown of the remaining time may be visually and/or aurally provided for all or some portion of the period during which initial secondary wagers are accepted.
[0165] At 740, initial wagers, if any, are accepted. As discussed in more detail below, in one embodiment the wagers are accepted at the wireless communications device, while in another embodiment the wagers are accepted at the casino server computing system(s) 42 that is part of the casino communications system 70.
[0166] At 742, the wireless communications device 44 and/or some other device announces the closure of initial wagering, for example providing a visual and/or audio prompt to a secondary player or potential secondary player, and at 744 further wagers are locked out. The announcement and/or lockout may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated by or in response to events on or a timer associated with the particular gaming table, or may be provided in response to a timer or other clock signal generated by the wireless communications device.
[0167] At 746, the game starts. For example, the game may start with the dealing of cards, rolling of dice, spinning of a wheel, or drawing of a number.
[0168] At 747, the occurrence of a game event or a time is determined. For example, a game event may be the dealing of a first playing card, last playing card or other playing card, the spin of a wheel, a spinning wheel coming to a stop, a roll of dice, an action by a player, dealer, other participant, or other casino personnel. The determination may be performed using sensors at the gaming table, or based on information from such sensors. Also for example, time may be a period based on a time of day, week or year or on a period after or before the occurrence of an action or event occurring at the gaming table or elsewhere.
[0169] At 748, the wireless communications device 44 and/or some other device announces the opening of intermediary wagering, for example providing a visual and/or audio prompt to a secondary player or potential secondary player. The announcement may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated when the particular gaming table is ready to accept intermediary wagers, typically between the end of one game or round and the start of a next game or round.
[0170] At 750, intermediary wagers, if any, are accepted. As discussed in more detail below, in one embodiment the wagers are accepted at the wireless communications device, while in another embodiment the wagers are accepted at the casino server computing system(s) 42 that is part of the casino communications system 70.
[0171] At 752, the wireless communications device 44 and/or some other device announces the time remaining for intermediary wagering, for example providing a visual and/or audio prompt to a secondary player or potential secondary player. The announcement may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated by or in response to events on or a timer associated with the particular gaming table, or may be provided in response to a timer or other clock signal generated by the wireless communications device. The announcement may be repeated from time to time, updating the amount of time remaining. Alternatively or additionally, a countdown of the remaining time may be visually and/or aurally provided for all or some portion of the period during which intermediary wagers are accepted.
[0172] At 754, intermediary wagers, if any, are accepted. As discussed in more detail below, in one embodiment the wagers are accepted at the wireless communications device, while in another embodiment the wagers are accepted at the casino server computing system(s) 42 that is part of the casino communications system 70.
[0173] At 756, the wireless communications device 44 and/or some other device announces the closure of intermediary wagering, for example providing a visual and/or audio prompt to a secondary player or potential secondary player, and locks out further wagers at 758. The announcement and/or lockout may be provided in response to a signal provided to the wireless communications device 44 from or by the casino server computing system(s) 42 via the casino communications system 70, which is generated by or in response to events on or a timer associated with the particular gaming table, or may be provided in response to a timer or other clock signal generated by the wireless communications device.
[0174] At 760, the game stops. For example, the game may stop when hands of playing cards are resolved against each other or against a standard, when a dice comes to a stop, a wheel stops spinning or a set of numbers have been drawn. At 762, the initial and intermediary primary and/or secondary wagers are reconciled based at least in part on the outcome of the game event(s), the primary and secondary wagers placed, and the primary odds (i.e., game odds) and secondary odds (i.e., odds for particular primary player). In some embodiments reconciliation may take place on the wireless communications device 44 advantageously reducing the computational burden on the casino server computing system(s) 42. In some embodiments reconciliation may take place on the casino server computing system(s) 42, advantageously providing enhanced security.
[0175] At 764, the casino server computer updates the primary player odds based at least in part on the outcome of the game.
[0176] As discussed in detail below, in one embodiment wagers may be accepted if entered into the wireless communications device 44 before initial and/or intermediary wagers are locked out. Also as discussed in detail below, in another embodiment wagers may be accepted if received by a casino server computing system before initial and/or intermediary wagers are locked out. Also, while not necessary, either embodiment may advantageously employ a packet transaction concept to ensure security and reliability. These embodiments are discussed immediately below.
[0177] FIG. 23 shows a method 800 in which wagers are accepted if entered into the wireless communications device 44 before initial and/or intermediary wagers are locked out, according to one illustrated embodiment.
[0178] At 802, the wireless communications device 44 receives a proposed wager entered via a user interface (e.g., keys, joy or thumb stick, track pad, trackball, graphical icons or menus, voice recognition). At 804, the wireless communications device 44 determines whether the proposed wager is being made during a period when wagers are not locked out. If the proposed wager is occurring during a wager lockout period, at 806 the wireless communications device 44 provides an appropriate message to the user via the user interface, declining the proposed wager and/or suggesting placing a wager at a later time. Control then may return to 802, or the method 800 can terminate, relying on separate threads or instances of the method 800 to handle further proposed wagers.
[0179] If the proposed wager is occurring outside of a wager lockout period, at 808 the wireless communications device 44 creates a wager transaction packet. As discussed in more detail below, creation of the wager transaction packet may include the generation of error detection and/or error correction information. The wireless communications device 44 may employ any suitable known or later developed error detection and/or error correction algorithms.
[0180] Optionally, at 809, the wireless communications device 44 encrypts the wager transaction packet. The wireless communications device 44 may employ any suitable known or later developed encryption algorithm.
[0181] At 810, the wireless communications device provides a suitable wager accepted message (e.g., visual, aural, and/or tactile) to the user via the user interface. At 812, the wireless communications device 44 transmits a wager transaction packet to the casino server computing system 42. The wager transaction packet may be transmitted intact (i.e., all the information remains in a single packet), to help ensure that wager transactions are only completed if all required information is present in the packet, and to help ensure that an interruption on communications does not produce or provide an opportunity for a breach in security.
[0182] At 814, the wireless communications device 44 receives a wager outcome from the casino server computing system 42. In response, the wireless communications device 44 provides wager outcome information to the user via the user interface at 816. At 818, the wireless communications device 44 updates any cached information and/or display on the wireless communications device 44. The method 800 may then return to 802 to handle the next proposed wager. Alternatively, a separate thread or instance of the method 800 may be invoked for each proposed wager.
[0183] FIG. 24 shows a method 830 in which wagers are accept if received by a casino server computing system 42 before initial and/or intermediary wagers are locked out, according to one illustrated embodiment.
[0184] At 832, the wireless communications device 44 receives a proposed wager entered via a user interface (e.g., keys, joy or thumb stick, track pad, trackball, graphical icons or menus, voice recognition). At 834, the wireless communications device 44 determines whether the proposed wager is being made during a period when wagers are not locked out. If the proposed wager is occurring during a wager lockout period, at 836 the wireless communications device 44 provides an appropriate message to the user via the user interface, declining the proposed wager and/or suggesting placing a wager at a later time. Control then may return to 832, or the method 830 can terminate, relying on separate threads or instances of the method 830 to handle further proposed wagers.
[0185] If the proposed wager is occurring outside of a wager lockout period, at 838 the wireless communications device 44 creates a wager transaction packet. At 840, the wireless communications device 44 transmits the wager transaction packet to the casino server computing system 42.
[0186] At 842, the wireless communications device 44 receives a wager accepted acknowledgement from the casino server computing system 42. At 844, the wireless communications device provides a suitable wager accepted message (e.g., visual, aural, and/or tactile) to the user via the user interface.
[0187] At 846, the wireless communications device 44 receives a wager outcome from the casino server computing system 42. In response, the wireless communications device 44 provides wager outcome information to the user via the user interface at 848. At 850, the wireless communications device 44 updates any cached information and/or display on the wireless communications device 44. The method 830 may then return to 832 to handle the next proposed wager. Alternatively, a separate thread or instance of the method 830 may be invoked for each proposed wager.
[0188] FIG. 25 shows a game type selection screen 860 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The game type selection screen 860 allows a user to select a type of game for placing wagers.
[0189] The game type selection screen 860 includes a set of user-selectable game type identification icons 862a-862g which identify different types of games offered by the casino. The user may select one of the game type identification icons 862a-862g to navigate to the next screen.
[0190] FIG. 26 shows a table limit screen 870 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The table limit screen may be displayed in response to the selection of one of the game type identification icons 862a-862g (FIG. 25 ) if the selected game has associated table limits. The table limit screen 870 allows a user to select from gaming tables or machines having wagering limits with which the player is comfortable.
[0191] The table limit screen 870 includes a number of user-selectable table limit icons 872a-872g. The user may select one of the table limit icons 872a-872g to view available tables with the appropriate table limits.
[0192] FIG. 27 shows a select game screen 880 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The select game screen 880 may be displayed in response to selection of one of the table limit icons 872a-872g (FIG. 26 ). The select game screen 880 allows a user to select from one or more gaming table or gaming machines.
[0193] The select game screen 880 includes a number of user-selectable game identifier icons 882 (only one called out in Figure), which identify specific gaming tables or gaming machines from which the user may select. The select game screen 880 may additionally provide a pit identifier 884 that identifies a pit in which the gaming table or machine is located, as well as a status identifier 886 that identifies a current status of the respective games. For example, the select table screen 880 may indicate that wagers are currently being accepted (e.g., WAGER), that wagers are currently not being accepted (e.g., WAIT), that the gaming table or machine is closed (e.g., CLOSED), that the dealer is being changed (e.g., DEALER CHANGE) and hence the wait may be long, that playing cards are being shuffled (e.g., SHUFFLING) and hence the wait may be long, and/or other status. The select table screen 880 may include a scroll bar 888, for reviewing long lists of gaming tables and/or machines.
[0194] FIG. 28 shows a backline wagering screen 890 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The backline wagering screen 890 may be optional, limited to environments where and/or times when backline wagering is offered. The backline wagering screen 890 allows a user to review the odds and performance of various primary players, and to select primary players to place secondary wagers on.
[0195] The backline wagering screen 890 includes user-selectable icons 892a-892d each associated with a respective primary player. The backline wagering screen 890 also provides an odds indication 894 (only one called out in Figure) of the respective odds that are being paid on a win by each of the primary players. The backline wagering screen 890 may provide additional information such as a streak indication 896 (only one called out in Figure) indicative of a current streak the primary player is running and/or a last ten games indication 898 (only one called out in Figure) indicative of the number of wins out of the last 10 games or rounds played by the primary player.
[0196] FIG. 29 shows a place wager screen 900 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The place wager screen 900 allows a user to place wagers on selected games and/or primary players.
[0197] The place wager screen 900 provides a pit indication 902, a game indication 904 and/or a position indication 906, indicative of the selected pit, gaming table or machine, and position at the gaming table or machine, respectively. Where a backline wager is involved, the place wager screen 900 may additionally or alternatively provide a primary player indication, indicative of the identity of a selected primary player. The place wager screen 900 includes a wager amount field 908 that allows the user to enter an amount to wager, and a user-selectable submit icon 910 which the user may select to submit the wager.
[0198] FIG. 30 shows a wager accepted screen 920 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The wager accepted screen 920 is displayed to indicate that a wager has been successful submitted. The wager accepted screen 920 may include suitable information such as pit identification 922, game identification 924 and/or position identification 926 identifying the pit, table, and position, respectively. The wager accepted screen 920 may also include an identification of the amount of wagered 927 and/or date and time of wager 928.
[0199] FIG. 31 shows a wager declined screen 930 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The wager declined screen 930 is displayed to indicate that a wager has not been successful submitted, and may include suitable information such as a user-selectable option 932 to select another game or user-selectable option 934 to wait and try to place the wager again.
[0200] FIG. 32 shows a wager open screen 940 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The wager open screen 940 is displayed to indicate that a wagering period for a selected game is opened, and wagers may be submitted. The wager open screen 940 may include suitable information such as pit identification 942, game identification 944 identifying the pit, and the gaming table or machine, respectively. The wager open screen 940 may also include a display 946 of the amount of time remaining for wagering. The entire wager open screen 940 may be updated from time to time to update the amount of time remaining, or the amount of time remaining may be displayed as a running clock or countdown clock.
[0201] FIG. 33 shows a wager closing screen 950 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The wager closing screen 950 is displayed to indicate that a wagering period for a selected game will be closing shortly, and wagers may be still be submitted. The wager closing screen 950 may include suitable information such as pit identification 952 and game identification 954, identifying the pit, and the gaming table or machine, respectively. The wager closing screen 950 may additionally include a display 956 of the amount of time remaining for wagering. The entire wager closing screen 950 may be updated from time to time to update the amount of time remaining, or the amount of time remaining may be displayed as a running clock or countdown clock.
[0202] FIG. 34 shows a wager closed screen 960 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The wager closed screen 960 is displayed to indicate that a wagering period for a selected game is closed, and wagers may no longer be submitted. The wager closed screen 960 may provide a suitable message indicating that wagering is closed. The wager closed screen 960 may include suitable information such as pit identification 962 and game identification 964, identifying the pit, and the gaming table or machine, respectively. The message may further provide an indication of the time or estimated time at which wagering on the game will open.
[0203] FIG. 35 shows a game view screen 970 of a graphical user interface as displayed by a wireless communications device 44, according to one illustrated embodiment. The game view screen 970 displays a view 972 of a game being played at a selected gaming table or machine. The view 972 may be video images of the game, simulated images created based on information gathered about the game, and/or still photographs. The game view screen 970 may include suitable information such as pit identification 974 and table identification 976 identifying the pit and table, respectively. The game view screen 970 allows the user to remotely share in the experience of the game.
Wager Transaction Packets
[0204] FIG. 36 shows a data structure 1000 suitable to implement the wager transaction packet structure according to one illustrated embodiment. The data structure may temporarily or permanently reside in a memory of the wireless communications device 44, a memory of the casino server computing system 42, memory of wireless or wired access points (e.g., pit podium personal computers 36) or other medium such as the wired or wireless communications links of the network 34. In some embodiments, the data structure 1000 will be created by the wireless communications devices 44, in other embodiments the data structure 1000 is created by the wireless or wired access points.
[0205] The data structure 1000 includes a header field 1002 which in addition to typical header information associated with communications such as packet length, may include a packet identifier that uniquely identifies the wager transaction packet, and may also include an origin identifier that uniquely identifies the originating access point for the wager transaction packet (e.g., unique identifier of a wireless access point). The data structure 1000 may include a device identifier field 1004 that stores a device identifier that uniquely identifies the wireless communications device 44 originating the wager. The data structure 1000 may optionally include a player identifier field 1006, which stores a player identifier, if known, that uniquely identifies the player placing the wager. The player identifier may be based on a prior assignment of the wireless communications device 44 to a specific player. Alternatively, the player identifier may be based on one or more inputs by the player. Such inputs may, for example, include a user name and password, biometric information, and/or swipe of a credit card, debit card, drivers license or other identification card. Such information would allow sharing of wireless communications devices 44 among two or more users, and eliminate the need to track assignment of such wireless communications devices 44. Alternatively, such information can permit the comparison of the wireless communications device identifier against the player identifier to a detect misappropriation of the wireless communications device 44, for example using a database that stores relationships or assignments between the wireless communications device identifiers and the player identifiers.
[0206] The data structure 1000 may optionally include a wager type field 1008, which stores a wager type value that identifies a type of wager being placed, for example a primary wager or a secondary wager. The data structure 1000 includes a game identification field 1010. The game identification field 1010 includes information that identifies the game on which the wager is being placed. The game identification field 1010 may, for example include a game identifier that uniquely identifies a gaming table or machine, and/or a position identifier that uniquely identifies a position at the gaming table or machine.
[0207] The data structure 1000 includes a date and time field 1012 that stores a value indicative of a date and time that the wager is being placed. Such a value may advantageously be used to associate the wager with a specific round or hand of a game being played at a particular gaming table or machine identified by the game identifier and/or position identifier. Such a value may additionally, or alternatively, advantageously be used to determine whether the wager was placed before a wager lockout period. This approach may address issues that may be raised where communications are slow or not instantaneous, to ensure that players who place wagers during the allotted wagering times are given appropriate credit, and wagers are not unfairly denied due to delays in communications. In some embodiments, the date and time field 1012 may be considered part of the game identification field 1010 or subsumed therein.
[0208] The data structure 1000 includes an amount wagered field 1014 that identifies the amount being wagered.
[0209] The data structure 1000 may include an error detection/error correction field 1016. The error detection/error correction field 1016 includes error detection and/or error correction values that allows the determination of whether an error occurred during transmission of the wager transaction packet, and in some embodiments allows the correction of some or all of those errors. Error correction may, for, example, employ Reed/Solomon error correction techniques or other known error detection or error correction techniques.
[0210] FIG. 37 shows a data structure 1020 suitable to implement the wager transaction packet structure according to another illustrated embodiment. The data structure may temporarily or permanently reside in a memory of the wireless communications device 44, a memory of the casino server computing system 42, memory of wireless or wired access points (e.g., pit podium personal computers 36) or other medium such as the wired or wireless communications links of the network 34. In some embodiments, the data structure 1020 will be created by the wireless communications devices 44, in other embodiments the data structure 1020 is created by the wireless or wired access points.
[0211] The data structure 1020 includes a header field 1022 which in addition to typical header information associated with communications such as packet length, may include a packet identifier that unique identifies the wager transaction packet, and may also include an origin identifier that uniquely identifies the originating access point for the wager transaction packet (e.g., unique identifier of a wireless access point). The data structure 1020 may include a device identifier field 1024 that stores a device identifier that uniquely identifies the wireless communications device 44 originating the wager. The data structure 1020 may optionally include a player identifier field 1026, which stores a player identifier, if known, that uniquely identifies the player placing the wager. The player identifier may be based on a prior assignment of the wireless communications device 44 to a specific player. Alternatively, the player identifier may be based on one or more inputs by the player. Such inputs may, for example, include a user name and password, biometric information, and/or swipe of a credit card, debit card, drivers license or other identification card. Such information would allow sharing of wireless communications devices 44 among two or more users, and eliminate the need to track assignment of such wireless communications devices 44. Alternatively, such information can permit the comparison of the wireless communications device identifier against the player identifier to a detect misappropriate of the wireless communications device 44, for example using a database that stores relationships or assignments between the wireless communications device identifiers and the player identifiers.
[0212] The data structure 1020 may optionally include a wager type field 1028, which stores a wager type value that identifies a type of wager being placed, for example a primary wager or a secondary wager. The data structure 1020 includes a game identification field 1030. The game identification field 1030 includes information that identifies the game on which the wager is being placed. The game identification field 1030 may, for example include a game identifier that uniquely identifies a gaming table or machine, and/or a position identifier that uniquely identifies a position at the gaming table or machine, and a game number that uniquely identifiers a round or hand of the game being played at the gaming table or machine. Thus, for example, the game number may be incremented for each round of a blackjack game that is dealt during a gaming session (e.g., time while table is in use; dealer sessions, etc). The game number may advantageously be used to associate the wager with a specific round or hand of a game being played at a particular gaming table or machine identified by the game identifier and/or position identifier. By comparing the time of receipt of the wager transaction packet with a start time for a round or hand identified by the game number, it may be determined whether the wager was placed before a wager lockout period. This approach may provide enhanced security since date and time information is controlled by the casino server computing system 42 rather than the wireless communications device 44 or one or the access points.
[0213] The data structure 1020 includes an amount wagered field 1034, that identifies the amount being wagered.
[0214] The data structure 1020 may include an error detection/error correction field 1036. The error detection/error correction field 1036 includes error detection and/or error correction values that allows the determination of whether an error occurred during transmission of the wager transaction packet, and in some embodiments allows the correction of some or all of those errors. Error correction may, for, example, employ Reed/Solomon error correction techniques or other known error detection or error correction techniques.
[0215] FIG. 38 shows a method 1100 suitable for execution on a casino server computing system 42, according to one illustrated embodiment.
[0216] The method 1100 starts at 1102, for example on supplying power to the casino server computing system 42, or in response to being called by another routine. The method 1100 may run sequentially, and/or may be executed as separate threads or processes in parallel.
[0217] At 1104, the casino server computing system 42 receives a wager transaction packet. The wager transaction packet may be received via a network, over a wired or wireless communications channel.
[0218] Optionally, at 1106 the casino server computing system 42 decrypts the wager transaction packet. The casino server computing system 42 may employ any suitable known or later developed encryption/decryption scheme or algorithm.
[0219] Optionally, at 1108 the casino server computing system 42 determines whether there is an error in the wager transaction packet. For example, an error may—occur during the creation of the wager transaction packet and/or during the transmission of the wager transaction packet. The casino server computing system 42 may employ any suitable known or later developed error detection (e.g., parity) scheme or algorithm.
[0220] If an error is detected, control may pass to 1110 where the casino server computing system 42 determines if the error is correctable. Some embodiments may advantageously employ error correction to reduce the number of times information is retransmitted. If the error is not correctable, control passes to 1112 where the casino server computing system 42 rejects the wager transaction packet and/or requests retransmission of the wager transaction packet, and the method 1100 terminates at 1114. If the error is correctable, the casino server computing system 42 corrects the error at 1116. The casino server computing system 42 may employ any suitable known or later developed error correction scheme or algorithm.
[0221] Some embodiments may omit error correction to advantageously reduce the overhead associated with such. In such embodiments, upon detection of an error at 1108 control may pass directly to 1112.
[0222] At 1118, the casino server computing system 42 determines whether the wager transaction packet was received intact. This may help ensure that the information contained in the wager transaction packet is authenticated and that a power failure or interruption in communications does not present an opportunity for a breach of security. If the wager transaction packet was not received intact, the casino server computing system 42 may issue an alert or cause an alert to be issued at 1120. The wager transaction packet may then be rejected at 1112, and the method 1100 terminates at 1114.
[0223] If the wager transaction packet was received intact, control passes to 1122 where the casino server computing system 42 determines whether the wireless communications device 44 sending the wager transaction packet is an authorized device. The casino server computing system 42 may verify that the wireless communications device 44 is authorized using a lookup table or other database. The database may reflect the status of wireless communications devices provided by the casino or registered with the casino. If the wireless communications device 44 is not authorized, an alert is issued at 1120, the wager packet is rejected at 1112, and the method 1100 terminates at 1114. If the wireless communications device 44 is not authorized, control passes to 1124.
[0224] At 1124, the casino server computing system 42 determines whether the user submitting the wager is authorized to use the particular wireless communications device 44 that is generating or originating the wager transaction packet. The casino server computing system 42 may verify that the wireless communications device 44 is authorized using a lookup table or other database. The database may reflect the relationship between wireless communications devices and users. If the user is not authorized to use the particular wireless communications device 44, an alert is issued at 1120, the wager packet is rejected at 1112, and the method 1100 terminates at 1114. If the user is authorized to use the particular wireless communications device 44, control passes to 1126.
[0225] At 1126, casino server computing system 42 determines whether the wager was placed within a period during which wagers on the game were or are being accepted. This may be in addition to or as a substitute for the check or verification performed by the wireless communications device 44. The casino server computing system 42 may use the time that the wager was entered into or sent by the wireless communications device 44 as the time the wager is placed. Alternatively, the casino server computing system 42 may use the time that the wager transaction packet was received at a wireless remote access point of the network as the time the wager is placed. Alternatively, the casino server computing system 42 may use the time that the wager transaction packet was received by the casino server computing system 42 as the time the wager is placed.
[0226] The casino server computing system 42 may employ a “real-time” approach, only accepting wagers received at the casino server computing system 42 while the respective wagering period is actually open. Additionally or alternatively, the casino server computing system 42 may accept wagers which are received at the casino server computing system 42 after the respective wagering period is closed, if the casino server computing system 42 determines that the wager was placed while the respective wagering period was open. This advantageously addresses possible issues related to delays in communications over the network. To achieve such, the casino server computing system 42 may temporarily keep a database or other record of time periods during which wagering is allowed for different games, hands or rounds.
[0227] If the wager is not placed during an open wagering period, the casino server computing system 42 transmits a notice at 1128 to the respective wireless communications device 44, and the method 1100 terminates at 1114. Otherwise, the casino server computing system 42 optionally sends an acknowledgement to the respective wireless communications device 44 at 1130.
[0228] At 1132, the casino server computing system 42 determines the game outcome. The casino server computing system 42 may rely on information received by one or more sensors and/or computing systems associated with the particular gaming table or machine. At 1134, the casino server computing system 42 determines the outcome of the wager, based at least in part on the outcome of the game, the wager amount in the wager transaction packet and any odds associated with the game or wager. At 1136, the casino server computing system 42 transmits a notice of the wager outcome to the respective wireless communications device 44, and the method 1100 terminates at 1114.
Summary
[0229] The wireless communications devices 44 allow casino personnel to timely enter information into the computing system regarding employees and/or players. Thus, data may be collected for games that have not yet been automated. This allows real time tracking and management of the various aspects of the casino, and eliminates a potential source of errors since data is manually entered at most only once. This also allows awarding of comps in real time, encouraging further play by the players. This also allows players to redeem the comps in real time. Further, players who are issued or purchase the wireless communications devices may play, track their own performance and/or comps, and may order merchandise and/or services as soon as sufficient comps are awarded, and without having to leave the table, hotel room or other facility. The use of location determination such as GPS, permits services and/or merchandise to be delivered directly to the player without any need for the player to identify a delivery location. Thus, a player may, for example, order and receive a drink or snack without having to leave the table, or to request that their car or transportation be ready at an appointed time and location.
[0230] All of the above U.S. patents, U.S. patent application publications, U.S. patent applications, foreign patents, foreign patent applications and non-patent publications referred to in this specification and/or listed in the Application Data Sheet, including but not limited to U.S. Provisional Patent Application Ser. No. 60/791,397 filed Apr. 12, 2006; U.S. Pat. Nos. 6,460,848, issued Oct. 8, 2002, and entitled “METHOD AND APPARATUS FOR MONITORING CASINOS AND GAMING”; U.S. Pat. No. 6,652,379, issued Nov. 25, 2003, and entitled “METHOD, APPARATUS AND ARTICLE FOR VERIFYING CARD GAMES, SUCH AS BLACKJACK”; and U.S. Pat. No. 6,685,568, issued Feb. 3, 2004, and entitled “METHOD, APPARATUS AND ARTICLE FOR EVALUATING CARD GAMES, SUCH AS BLACKJACK”; and U.S. Patent Publication Nos. 2002/0187821, published Dec. 12, 2002, and entitled “METHOD, APPARATUS AND ARTICLE FOR RANDOM SEQUENCE GENERATION AND PLAYING CARD DISTRIBUTION”; and 2003/0176209, published Sep. 18, 2003, and entitled “METHOD, APPARATUS AND ARTICLE EMPLOYING MULTIPLE MACHINE-READABLE INDICIA ON PLAYING CARDS”; are incorporated herein by reference, in their entirety.
[0231] Although specific embodiments and examples are described herein for illustrative purposes, various equivalent modifications can be made without departing from the spirit and scope of the invention, as will be recognized by those skilled in the relevant art. The teachings provided herein can be applied to other systems for casino communications, not necessarily the handheld PDA based system generally described above. For example, the teachings can employ wireless communications devices such as cellular telephones, and cellular systems. Additionally, the teachings can employ networks other than dedicated Extranets, for example, the teachings may employ a network such as the Worldwide Web portion on the Internet, to interconnect some or all of the various described components. The various embodiments described above can be combined to provide further embodiments. The illustrated methods can omit some acts, can add other acts, and can execute the acts in a different order than that illustrated to achieve the advantages of the invention.
[0232] These and other changes can be made to the invention in light of the above detailed description. In general, in the following claims, the terms used should not be construed to limit the invention to specific embodiments disclosed in the specification, but should be construed to include all computers, networks, databases, and wireless communications devices that operate in accordance with the claims. Accordingly, the invention is not limited by the disclosure, but instead its scope is to be determined entirely by the following claims.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
I claim:
1. A method of operating a server computing system to facilitate remote wagering on table games with wireless communications devices located in a casino, the method comprising:
receiving a wager transaction packet including device information indicative of a device identifier that identifies a wireless communications device, located in a casino, that produced the wager transaction packet, player information indicative of a player identifier that identifies a player authorized to use the wireless communications device that produced the wager transaction packet, a wager, a game occurring at a gaming table on which the wager is being placed, and an indication of a date and time when the wager was entered into the wireless communications device;
determining an outcome of the wager based on at least one gaming event occurring at the gaming table;
transmitting outcome information indicative of the outcome of the wager to the wireless communications device that produced the wager transaction packet;
determining based at least in part on the indication of the date and time when the wager was entered into the wireless communications device, whether the date and time the wager was entered into the wireless communications device is within a period during which wagers on the game were being accepted;
verifying that the wireless communications device identified by the device identifier is presently authorized for use at the casino based at least on the device information contained in the wager transaction packet for each received wager transaction packet; and
verifying that a respective player is presently authorized to use the wireless communications device identified by the device identifier to wager on the game based at least on a respective player identifier for each received wager transaction packet, wherein the respective player is identified by the respective player identifier based at least on the player information contained in the wager transaction packet.
2. The method of claim 1, further comprising:
determining whether the wager transaction packet was received intact at the server computing system.
3. The method of claim 2, further comprising:
denying the wager if the wager transaction packet is determined to have not been received intact at the server computing system; and
producing an alert if the wager transaction packet is determined to have not been received intact at the server computing system.
5. The method of claim 1, further comprising:
accepting the wager if the date and time the wager was entered into the wireless communications device is within the period during which wagers on the game were being accepted;
rejecting the wager if the date and time the wager was entered into the wireless communications device is not within the period during which wagers on the game were being accepted.
6. The method of claim 5, further comprising:
providing an indication of rejection to the wireless communications device if the wager is rejected.
7. The method of claim 1, further comprising:
determining whether the wager transaction packet was received by a wireless access point within the period during which wagers on the game were being accepted.
8. The method of claim 1, further comprising:
determining whether the wager transaction packet was received by the server computing system within the period during which wagers on the game were being accepted.
9. The method of claim 1, further comprising:
transmitting an acknowledgment of receipt of the wager transaction packet to the wireless communications device that produced the wager transaction packet.
10. The method of claim 1, further comprising:
determining whether an error has occurred during transmission of the wager transaction packet.
11. The method of claim 1, further comprising:
correcting an error that has occurred during transmission of the wager transaction packet based at least in part on error correction information from the wager transaction packet.
12. The method of claim 1, further comprising:
verifying that the wager transaction packet was received via a wireless access point located within a defined geographic boundary.
13. The method of claim 1 wherein the wager transaction packet includes an indication of geographic location of the wireless communications device when the wager was entered into the wireless communications device, and further comprising:
determining based at least in part on the indication of the geographic location of the wireless communications device when the wager was entered into the wireless communication device, whether the wireless communications device was located within a defined geographic boundary when the wager was entered into the wireless communications device.
14. A system to facilitate remote wagering on table games, the system comprising:
a server computing system comprising at least one processor and at least one processor-readable memory that stores instructions executable by the processor to cause the processor to process wager transaction packets by:
receiving a plurality of wager transaction packets, each wager transaction packet including information indicative of an identity of a wireless communications device, at the casino, that produced the wager transaction packet and player information indicative of an identity of a respective player, a wager amount, and a game occurring at a gaming table on which the wager is being placed;
for each of the wagers, determining an outcome of the wagers based on at least one gaming event occurring at the gaming table;
verifying that the wireless communications device identified by the device identifier is presently authorized for use at the casino based at least on the device information contained in the wager transaction packet for each received wager transaction packet; and
verifying that a respective player is presently authorized to use the wireless communications device identified by the device identifier to wager on the game based at least on a respective player identifier for each received wager transaction packet, wherein the respective player is identified by the respective player identifier based at least on the player information contained in the wager transaction packet; and
for at least some of the wagers, transmitting information indicative of the outcome of the wager to the wireless communications device that produced the respective wager transaction packet; and
wherein the instructions cause the processor to process wager transaction packets further by:
determining whether wagers are being accepted; and
providing a message to a user of the wireless communications device indicative of an amount of time remaining during which wagers are being accepted.
15. The system of claim 14, further comprising: a plurality of wireless communications devices, each comprising at least one respective processor and at least one respective processor-readable memory that stores instructions executable by the respective processor of the respective wireless communications device to cause the processor of the respective wireless communications device to generate wager transaction packets by:
receiving user input at the respective wireless communications device indicating a respective wager to be placed on the game occurring at the gaming table;
in response, creating one of the wager transaction packets including information indicative of the respective identity of the respective wireless communications device, the respective wager amount, and the game on which the respective wager is placed; and
transmitting the respective wager transaction packet intact to the server computing system via a network, where the respective wager transaction packet remains intact during transmission between the respective wireless communications device and the server computing system.
16. The system of claim 14 wherein wireless communications devices cause the processor of the server to process wager transaction packets further by: including information indicative of a respective date and time at which the respective wager is placed.
17. The system of claim 14, further comprising:
a plurality of wireless access points positioned at respective locations in a casino property, the wireless access points having a geographical range limited to within a boundary of the casino property.
Patent Citations (438)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3766452(A) | 1973-10-01 | Burpee et al. | Applicant |
| US3787660(A) | 1974-01-01 | Meyers et al. | Applicant |
| US3810172(A) | 1974-05-01 | Burpee et al. | Applicant |
| US4026309(A) | 1977-05-01 | Howard | Applicant |
| US4108361(A) | 1978-08-01 | Krause | Applicant |
| US4339798(A) | 1982-07-01 | Hedges et al. | Examiner |
| US4373726(A) | 1983-02-01 | Churchill et al. | Applicant |
| US4467424(A) | 1984-08-01 | Hedges et al. | Applicant |
| US4531187(A) | 1985-07-01 | Uhland | Applicant |
| US4592377(A) | 1986-06-01 | Paulsen et al. | Applicant |
| US4636846(A) | 1987-01-01 | Villarreal | Applicant |
| US4656463(A) | 1987-04-01 | Anders et al. | Applicant |
| US4693480(A) | 1987-09-01 | Smith | Applicant |
| US4725079(A) | 1988-02-01 | Koza et al. | Applicant |
| US4755941(A) | 1988-07-01 | Bacchi | Applicant |
| US4802218(A) | 1989-01-01 | Wright et al. | Applicant |
| US4814589(A) | 1989-03-01 | Storch et al. | Applicant |
| US4832341(A) | 1989-05-01 | Muller et al. | Applicant |
| US4861041(A) | 1989-08-01 | Jones et al. | Applicant |
| US4926996(A) | 1990-05-01 | Eglise et al. | Applicant |
| US4948138(A) | 1990-08-01 | Pease et al. | Applicant |
| US5007641(A) | 1991-04-01 | Seidman | Applicant |
| US5053612(A) | 1991-10-01 | Pielemeier et al. | Applicant |
| US5083800(A) | 1992-01-01 | Lockton | Applicant |
| US5103081(A) | 1992-04-01 | Fisher et al. | Applicant |
| US5156397(A) | 1992-10-01 | Valenza, Jr. | Applicant |
| US5166502(A) | 1992-11-01 | Rendleman et al. | Applicant |
| US5179517(A) | 1993-01-01 | Sarbin et al. | Applicant |
| US5199710(A) | 1993-04-01 | Lamle | Applicant |
| US5216234(A) | 1993-06-01 | Bell | Applicant |
| US5258837(A) | 1993-11-01 | Gormley | Applicant |
| US5265874(A) | 1993-11-01 | Dickinson et al. | Applicant |
| US5273281(A) | 1993-12-01 | Lovell | Applicant |
| US5283422(A) | 1994-02-01 | Storch et al. | Applicant |
| US5324035(A) | 1994-06-01 | Morris et al. | Applicant |
| US5326104(A) | 1994-07-01 | Pease et al. | Applicant |
| US5361885(A) | 1994-11-01 | Modler | Applicant |
| US5364104(A) | 1994-11-01 | Jones et al. | Applicant |
| US5386103(A) | 1995-01-01 | DeBan et al. | Applicant |
| US5397133(A) | 1995-03-01 | Penzias | Applicant |
| US5398932(A) | 1995-03-01 | Eberhardt et al. | Applicant |
| US5406264(A) | 1995-04-01 | Plonsky et al. | Applicant |
| US5416308(A) | 1995-05-01 | Hood et al. | Applicant |
| US5458333(A) | 1995-10-01 | Takemoto et al. | Applicant |
| US5470079(A) | 1995-11-01 | LeStrange et al. | Applicant |
| US5472194(A) | 1995-12-01 | Breeding et al. | Applicant |
| US5487544(A) | 1996-01-01 | Clapper, Jr. | Applicant |
| US5505449(A) | 1996-04-01 | Eberhardt et al. | Applicant |
| US5505461(A) | 1996-04-01 | Bell et al. | Applicant |
| US5507489(A) | 1996-04-01 | Reibel et al. | Applicant |
| US5562284(A) | 1996-10-01 | Stevens | Applicant |
| US5575474(A) | 1996-11-01 | Rossides | Applicant |
| US5580311(A) | 1996-12-01 | Haste, III | Applicant |
| US5586936(A) | 1996-12-01 | Bennett et al. | Applicant |
| US5595538(A) | 1997-01-01 | Haste, III | Applicant |
| US5605334(A) | 1997-02-01 | McCrea, Jr. | Applicant |
| US5605506(A) | 1997-02-01 | Hoorn et al. | Applicant |
| US5613680(A) | 1997-03-01 | Groves et al. | Applicant |
| US5613912(A) | 1997-03-01 | Slater | Applicant |
| US5643086(A) | 1997-07-01 | Alcorn et al. | Applicant |
| US5643088(A) | 1997-07-01 | Vaughn et al. | Applicant |
| US5645486(A) | 1997-07-01 | Nagao et al. | Applicant |
| US5651548(A) | 1997-07-01 | French et al. | Applicant |
| US5655961(A) | 1997-08-01 | Acres et al. | Applicant |
| US5676376(A) | 1997-10-01 | Valley | Applicant |
| US5679077(A) | 1997-10-01 | Pocock et al. | Applicant |
| US5707287(A) | 1998-01-01 | McCrea, Jr. | Applicant |
| US5735525(A) | 1998-04-01 | McCrea, Jr. | Applicant |
| US5735742(A) | 1998-04-01 | French | Applicant |
| US5737418(A) | 1998-04-01 | Saffari et al. | Applicant |
| US5741183(A) | 1998-04-01 | Acres et al. | Applicant |
| US5742656(A) | 1998-04-01 | Mikulak et al. | Applicant |
| US5755618(A) | 1998-05-01 | Mothwurf | Applicant |
| US5757876(A) | 1998-05-01 | Dam et al. | Applicant |
| US5759102(A) | 1998-06-01 | Pease et al. | Applicant |
| US5759103(A) | 1998-06-01 | Freels et al. | Applicant |
| US5770533(A) | 1998-06-01 | Franchi | Applicant |
| US5779545(A) | 1998-07-01 | Berg et al. | Applicant |
| US5781647(A) | 1998-07-01 | Fishbine et al. | Applicant |
| US5785321(A) | 1998-07-01 | van Putten et al. | Applicant |
| US5788574(A) | 1998-08-01 | Ornstein et al. | Applicant |
| US5800268(A) | 1998-09-01 | Molnick | Examiner |
| US5801766(A) | 1998-09-01 | Alden | Applicant |
| US5803808(A) | 1998-09-01 | Strisower | Applicant |
| US5809482(A) | 1998-09-01 | Strisower | Applicant |
| US5813912(A) | 1998-09-01 | Shultz | Applicant |
| US5820463(A) | 1998-10-01 | O'Callaghan | Applicant |
| US5823879(A) | 1998-10-01 | Goldberg et al. | Applicant |
| US5830067(A) | 1998-11-01 | Graves et al. | Examiner |
| US5830068(A) | 1998-11-01 | Brenner et al. | Applicant |
| US5831669(A) | 1998-11-01 | Adrain | Applicant |
| US5842921(A) | 1998-12-01 | Mindes et al. | Applicant |
| US5850447(A) | 1998-12-01 | Peyret | Applicant |
| US5851149(A) | 1998-12-01 | Xidos et al. | Examiner |
| US5890963(A) | 1999-04-01 | Yen | Applicant |
| US5895321(A) | 1999-04-01 | Gassies et al. | Applicant |
| US5902983(A) | 1999-05-01 | Crevelt et al. | Applicant |
| US5909876(A) | 1999-06-01 | Brown | Applicant |
| US5911626(A) | 1999-06-01 | McCrea, Jr. | Applicant |
| US5919090(A) | 1999-07-01 | Mothwurf | Applicant |
| US5931731(A) | 1999-08-01 | Chwalisz | Applicant |
| US5936527(A) | 1999-08-01 | Isaacman et al. | Applicant |
| US5941769(A) | 1999-08-01 | Order | Applicant |
| US5957776(A) | 1999-09-01 | Hoehne | Applicant |
| US5971851(A) | 1999-10-01 | Pascal et al. | Applicant |
| US5999808(A) | 1999-12-01 | LaDue | Examiner |
| US6001016(A) | 1999-12-01 | Walker et al. | Applicant |
| US6021949(A) | 2000-02-01 | Boiron | Applicant |
| US6029891(A) | 2000-02-01 | Freeman et al. | Applicant |
| US6042150(A) | 2000-03-01 | Daley | Applicant |
| US6048269(A) | 2000-04-01 | Burns et al. | Applicant |
| US6062481(A) | 2000-05-01 | Storch et al. | Applicant |
| US6068553(A) | 2000-05-01 | Parker | Applicant |
| US6077161(A) | 2000-06-01 | Wisler | Applicant |
| US6080063(A) | 2000-06-01 | Khosla | Applicant |
| US6083105(A) | 2000-07-01 | Ronin et al. | Applicant |
| US6089980(A) | 2000-07-01 | Gauselmann | Applicant |
| US6093103(A) | 2000-07-01 | McCrea, Jr. | Applicant |
| US6102799(A) | 2000-08-01 | Stupak | Applicant |
| US6104815(A) | 2000-08-01 | Alcorn et al. | Applicant |
| US6106396(A) | 2000-08-01 | Alcorn et al. | Applicant |
| US6110041(A) | 2000-08-01 | Walker et al. | Applicant |
| US6110043(A) | 2000-08-01 | Olsen | Applicant |
| US6117012(A) | 2000-09-01 | McCrea, Jr. | Applicant |
| US6126166(A) | 2000-10-01 | Lorson et al. | Applicant |
| US6135887(A) | 2000-10-01 | Pease et al. | Applicant |
| US6142876(A) | 2000-11-01 | Cumbers | Applicant |
| US6146273(A) | 2000-11-01 | Olsen | Applicant |
| US6149522(A) | 2000-11-01 | Alcorn et al. | Applicant |
| US6152824(A) | 2000-11-01 | Rothschild et al. | Applicant |
| US6154131(A) | 2000-11-01 | Jones, II et al. | Applicant |
| US6165069(A) | 2000-12-01 | Sines et al. | Applicant |
| US6166763(A) | 2000-12-01 | Rhodes et al. | Applicant |
| US6168523(B1) | 2001-01-01 | Piechowiak et al. | Applicant |
| US6179711(B1) | 2001-01-01 | Yoseloff | Applicant |
| US6183366(B1) | 2001-02-01 | Goldberg et al. | Applicant |
| US6186892(B1) | 2001-02-01 | Frank et al. | Applicant |
| US6186895(B1) | 2001-02-01 | Oliver | Applicant |
| US6190256(B1) | 2001-02-01 | Walker et al. | Applicant |
| US6200218(B1) | 2001-03-01 | Lindsay | Applicant |
| US6210277(B1) | 2001-04-01 | Stefan | Applicant |
| US6217447(B1) | 2001-04-01 | Lofink et al. | Applicant |
| US6219836(B1) | 2001-04-01 | Wells et al. | Applicant |
| US6227972(B1) | 2001-05-01 | Walker et al. | Applicant |
| US6234898(B1) | 2001-05-01 | Belamant et al. | Applicant |
| US6244958(B1) | 2001-06-01 | Acres | Applicant |
| US6251014(B1) | 2001-06-01 | Stockdale et al. | Applicant |
| US6254484(B1) | 2001-07-01 | McCrea, Jr. | Applicant |
| US6264109(B1) | 2001-07-01 | Chapet et al. | Applicant |
| US6264561(B1) | 2001-07-01 | Saffari et al. | Applicant |
| US6267671(B1) | 2001-07-01 | Hogan | Applicant |
| US6275586(B1) | 2001-08-01 | Kelly | Applicant |
| US6283856(B1) | 2001-09-01 | Mothwurf | Applicant |
| US6287202(B1) | 2001-09-01 | Pascal et al. | Applicant |
| US6299534(B1) | 2001-10-01 | Breeding et al. | Applicant |
| US6313871(B1) | 2001-11-01 | Schubert | Applicant |
| US6346044(B1) | 2002-02-01 | McCrea, Jr. | Applicant |
| US6347738(B1) | 2002-02-01 | Crevelt et al. | Applicant |
| US6352261(B1) | 2002-03-01 | Brown | Applicant |
| US6394900(B1) | 2002-05-01 | McGlone et al. | Applicant |
| US6394907(B1) | 2002-05-01 | Rowe | Applicant |
| US6400272(B1) | 2002-06-01 | Holtzman et al. | Applicant |
| US6409602(B1) | 2002-06-01 | Wiltshire et al. | Applicant |
| US6425817(B1) | 2002-07-01 | Momemy | Applicant |
| US6435970(B1) | 2002-08-01 | Baerlocher et al. | Applicant |
| US6439996(B2) | 2002-08-01 | LeMay et al. | Applicant |
| US6443839(B2) | 2002-09-01 | Stockdale et al. | Applicant |
| US6446864(B1) | 2002-09-01 | Kim et al. | Applicant |
| US6457715(B1) | 2002-10-01 | Friedman | Applicant |
| US6460848(B1) | 2002-10-01 | Soltys et al. | Applicant |
| US6464584(B2) | 2002-10-01 | Oliver | Applicant |
| US6478676(B1) | 2002-11-01 | Dayan | Applicant |
| US6488581(B1) | 2002-12-01 | Stockdale | Applicant |
| US6488585(B1) | 2002-12-01 | Wells et al. | Applicant |
| US6503147(B1) | 2003-01-01 | Stockdale et al. | Applicant |
| US6505772(B1) | 2003-01-01 | Mollett et al. | Applicant |
| US6508709(B1) | 2003-01-01 | Karmarkar | Applicant |
| US6508710(B1) | 2003-01-01 | Paravia et al. | Applicant |
| US6514140(B1) | 2003-02-01 | Storch | Applicant |
| US6517435(B2) | 2003-02-01 | Soltys et al. | Applicant |
| US6517436(B2) | 2003-02-01 | Soltys et al. | Applicant |
| US6517437(B1) | 2003-02-01 | Wells et al. | Applicant |
| US6520857(B2) | 2003-02-01 | Soltys et al. | Applicant |
| US6527271(B2) | 2003-03-01 | Soltys et al. | Applicant |
| US6527638(B1) | 2003-03-01 | Walker et al. | Examiner |
| US6530836(B2) | 2003-03-01 | Soltys et al. | Applicant |
| US6530837(B2) | 2003-03-01 | Soltys et al. | Applicant |
| US6532297(B1) | 2003-03-01 | Lindquist | Applicant |
| US6533276(B2) | 2003-03-01 | Soltys et al. | Applicant |
| US6533662(B2) | 2003-03-01 | Soltys et al. | Applicant |
| US6547131(B1) | 2003-04-01 | Foodman et al. | Applicant |
| US6567159(B1) | 2003-05-01 | Corech | Applicant |
| US6575829(B2) | 2003-06-01 | Coleman et al. | Applicant |
| US6575833(B1) | 2003-06-01 | Stockdale | Applicant |
| US6575834(B1) | 2003-06-01 | Lindo | Applicant |
| US6578847(B1) | 2003-06-01 | Hedrick et al. | Applicant |
| US6579179(B2) | 2003-06-01 | Poole et al. | Applicant |
| US6579180(B2) | 2003-06-01 | Soltys et al. | Applicant |
| US6579181(B2) | 2003-06-01 | Soltys et al. | Applicant |
| US6581747(B1) | 2003-06-01 | Charlier et al. | Applicant |
| US6582301(B2) | 2003-06-01 | Hill | Applicant |
| US6585598(B2) | 2003-07-01 | Nguyen et al. | Applicant |
| US6595857(B2) | 2003-07-01 | Soltys et al. | Applicant |
| US6607441(B1) | 2003-08-01 | Acres | Applicant |
| US6609978(B1) | 2003-08-01 | Paulsen | Applicant |
| US6620046(B2) | 2003-09-01 | Rowe | Applicant |
| US6628939(B2) | 2003-09-01 | Paulsen | Applicant |
| US6629184(B1) | 2003-09-01 | Berg et al. | Applicant |
| US6629591(B1) | 2003-10-01 | Griswold et al. | Applicant |
| US6629889(B2) | 2003-10-01 | Mothwurf | Applicant |
| US6638161(B2) | 2003-10-01 | Soltys et al. | Applicant |
| US6638169(B2) | 2003-10-01 | Wilder et al. | Applicant |
| US6638170(B1) | 2003-10-01 | Crumby | Applicant |
| US6641484(B2) | 2003-11-01 | Oles et al. | Applicant |
| US6645077(B2) | 2003-11-01 | Rowe | Applicant |
| US6652378(B2) | 2003-11-01 | Cannon et al. | Applicant |
| US6652379(B2) | 2003-11-01 | Soltys et al. | Applicant |
| US6663490(B2) | 2003-12-01 | Soltys et al. | Applicant |
| US6675152(B1) | 2004-01-01 | Prasad et al. | Applicant |
| US6676522(B2) | 2004-01-01 | Rowe et al. | Applicant |
| US6682421(B1) | 2004-01-01 | Rowe et al. | Applicant |
| US6682423(B2) | 2004-01-01 | Brosnan et al. | Applicant |
| US6685564(B2) | 2004-02-01 | Oliver | Applicant |
| US6685567(B2) | 2004-02-01 | Cockerille et al. | Applicant |
| US6685568(B2) | 2004-02-01 | Soltys et al. | Applicant |
| US6688979(B2) | 2004-02-01 | Soltys et al. | Applicant |
| US6699128(B1) | 2004-03-01 | Beadell et al. | Applicant |
| US6702672(B1) | 2004-03-01 | Angell et al. | Applicant |
| US6712696(B2) | 2004-03-01 | Soltys et al. | Applicant |
| US6726099(B2) | 2004-04-01 | Becker et al. | Applicant |
| US6728740(B2) | 2004-04-01 | Kelly et al. | Applicant |
| US6729956(B2) | 2004-05-01 | Wolf et al. | Applicant |
| US6739975(B2) | 2004-05-01 | Nguyen et al. | Applicant |
| US6746330(B2) | 2004-06-01 | Cannon | Applicant |
| US6752312(B1) | 2004-06-01 | Chamberlain et al. | Applicant |
| US6755741(B1) | 2004-06-01 | Rafaeli | Applicant |
| US6758751(B2) | 2004-07-01 | Soltys et al. | Applicant |
| US6811488(B2) | 2004-11-01 | Paravia et al. | Applicant |
| US6817948(B2) | 2004-11-01 | Pascal et al. | Applicant |
| US6823419(B2) | 2004-11-01 | Berg et al. | Applicant |
| US6846238(B2) | 2005-01-01 | Wells | Applicant |
| US6848994(B1) | 2005-02-01 | Knust et al. | Applicant |
| US6866581(B2) | 2005-03-01 | Martinek et al. | Applicant |
| US6866586(B2) | 2005-03-01 | Oberberger et al. | Applicant |
| US6896618(B2) | 2005-05-01 | Benoy et al. | Applicant |
| US6899627(B2) | 2005-05-01 | Lam et al. | Applicant |
| US6905411(B2) | 2005-06-01 | Nguyen et al. | Applicant |
| US6962530(B2) | 2005-11-01 | Jackson | Applicant |
| US6971956(B2) | 2005-12-01 | Rowe et al. | Applicant |
| US6991544(B2) | 2006-01-01 | Soltys et al. | Applicant |
| US6997803(B2) | 2006-02-01 | LeMay et al. | Applicant |
| US7005985(B1) | 2006-02-01 | Steeves | Applicant |
| US7029009(B2) | 2006-04-01 | Grauzer et al. | Applicant |
| US7035626(B1) | 2006-04-01 | Luciano, Jr. | Examiner |
| US7062470(B2) | 2006-06-01 | Prasad et al. | Applicant |
| US7063617(B2) | 2006-06-01 | Brosnan et al. | Applicant |
| US7077332(B2) | 2006-07-01 | Verschuur et al. | Applicant |
| US7112138(B2) | 2006-09-01 | Hedrick et al. | Applicant |
| US7114718(B2) | 2006-10-01 | Grauzer et al. | Applicant |
| US7179170(B2) | 2007-02-01 | Martinek et al. | Applicant |
| US7198571(B2) | 2007-04-01 | LeMay et al. | Applicant |
| USRE39644(E) | 2007-05-01 | Alcorn et al. | Examiner |
| US7213812(B2) | 2007-05-01 | Schubert et al. | Applicant |
| US7222852(B2) | 2007-05-01 | Soltys et al. | Applicant |
| US7271727(B2) | 2007-09-01 | Steeves | Applicant |
| US7309065(B2) | 2007-12-01 | Yoseloff et al. | Applicant |
| US7311605(B2) | 2007-12-01 | Moser | Applicant |
| US7351147(B2) | 2008-04-01 | Stockdale et al. | Applicant |
| US7384339(B2) | 2008-06-01 | LeMay et al. | Applicant |
| US7390256(B2) | 2008-06-01 | Soltys et al. | Applicant |
| US7399226(B2) | 2008-07-01 | Mishra | Applicant |
| US7404765(B2) | 2008-07-01 | Soltys et al. | Applicant |
| US7407438(B2) | 2008-08-01 | Schubert et al. | Applicant |
| US7419428(B2) | 2008-09-01 | Rowe | Applicant |
| US7422522(B2) | 2008-09-01 | Fujimoto et al. | Applicant |
| US7434805(B2) | 2008-10-01 | Grauzer et al. | Applicant |
| US7435179(B1) | 2008-10-01 | Ford | Examiner |
| US7438643(B2) | 2008-10-01 | Brosnan et al. | Applicant |
| US7455591(B2) | 2008-11-01 | Nguyen | Applicant |
| US7460863(B2) | 2008-12-01 | Steelberg et al. | Examiner |
| US7510186(B2) | 2009-03-01 | Fleckenstein | Applicant |
| US7510194(B2) | 2009-03-01 | Soltys et al. | Applicant |
| US7534169(B2) | 2009-05-01 | Amaitis et al. | Examiner |
| US7549576(B2) | 2009-06-01 | Alderucci et al. | Examiner |
| US7577847(B2) | 2009-08-01 | Nguyen et al. | Examiner |
| US7611407(B1) | 2009-11-01 | Itkis et al. | Examiner |
| US7611409(B2) | 2009-11-01 | Muir et al. | Examiner |
| US7637810(B2) | 2009-12-01 | Amaitis et al. | Examiner |
| US7644861(B2) | 2010-01-01 | Alderucci et al. | Examiner |
| US7699703(B2) | 2010-04-01 | Muir et al. | Examiner |
| US2001/0016515(A1) | 2001-08-01 | Oliver | Applicant |
| US2001/0034237(A1) | 2001-10-01 | Garahi | Examiner |
| US2001/0036858(A1) | 2001-11-01 | McNutt et al. | Examiner |
| US2001/0041612(A1) | 2001-11-01 | Garahi et al. | Examiner |
| US2002/0025851(A1) | 2002-02-01 | Frankulin et al. | Examiner |
| US2002/0049909(A1) | 2002-04-01 | Jackson et al. | Applicant |
| US2002/0084587(A1) | 2002-07-01 | Bennett et al. | Applicant |
| US2002/0103027(A1) | 2002-08-01 | Rowe et al. | Examiner |
| US2002/0111213(A1) | 2002-08-01 | McEntee et al. | Examiner |
| US2002/0116615(A1) | 2002-08-01 | Nguyen et al. | Applicant |
| US2002/0138594(A1) | 2002-09-01 | Rowe | Applicant |
| US2002/0147042(A1) | 2002-10-01 | Vuong et al. | Applicant |
| US2002/0147049(A1) | 2002-10-01 | Carter, Sr. | Examiner |
| US2002/0187821(A1) | 2002-12-01 | Soltys et al. | Applicant |
| US2002/0187825(A1) | 2002-12-01 | Tracy et al. | Applicant |
| US2002/0187830(A1) | 2002-12-01 | Stockdale et al. | Applicant |
| US2003/0022714(A1) | 2003-01-01 | Oliver | Applicant |
| US2003/0027625(A1) | 2003-02-01 | Rowe | Applicant |
| US2003/0028480(A1) | 2003-02-01 | Rowe | Applicant |
| US2003/0032474(A1) | 2003-02-01 | Kaminkow | Applicant |
| US2003/0036425(A1) | 2003-02-01 | Kaminkow et al. | Applicant |
| US2003/0045354(A1) | 2003-03-01 | Giobbi | Examiner |
| US2003/0054881(A1) | 2003-03-01 | Hedrick et al. | Applicant |
| US2003/0064774(A1) | 2003-04-01 | Fujimoto et al. | Applicant |
| US2003/0064798(A1) | 2003-04-01 | Grauzer et al. | Applicant |
| US2003/0064805(A1) | 2003-04-01 | Wells | Examiner |
| US2003/0069074(A1) | 2003-04-01 | Jackson | Applicant |
| US2003/0078103(A1) | 2003-04-01 | LeMay et al. | Applicant |
| US2003/0083126(A1) | 2003-05-01 | Paulsen | Applicant |
| US2003/0104865(A1) | 2003-06-01 | Itkis et al. | Examiner |
| US2003/0130032(A1) | 2003-07-01 | Martinek et al. | Applicant |
| US2003/0137968(A1) | 2003-07-01 | Lareau et al. | Applicant |
| US2003/0144965(A1) | 2003-07-01 | Prasad et al. | Applicant |
| US2003/0162588(A1) | 2003-08-01 | Brosnan et al. | Applicant |
| US2003/0171145(A1) | 2003-09-01 | Rowe | Applicant |
| US2003/0176218(A1) | 2003-09-01 | LeMay et al. | Applicant |
| US2003/0186733(A1) | 2003-10-01 | Wolf et al. | Applicant |
| US2003/0186739(A1) | 2003-10-01 | Paulsen et al. | Applicant |
| US2003/0195037(A1) | 2003-10-01 | Vuong et al. | Applicant |
| US2003/0199320(A1) | 2003-10-01 | Nguyen et al. | Applicant |
| US2003/0203755(A1) | 2003-10-01 | Jackson | Applicant |
| US2003/0212597(A1) | 2003-11-01 | Ollins | Applicant |
| US2003/0220136(A1) | 2003-11-01 | Soltys et al. | Applicant |
| US2003/0224858(A1) | 2003-12-01 | Yoseloff et al. | Applicant |
| US2003/0228912(A1) | 2003-12-01 | Wells et al. | Applicant |
| US2003/0232647(A1) | 2003-12-01 | Moser | Applicant |
| US2003/0232651(A1) | 2003-12-01 | Huard et al. | Applicant |
| US2004/0002379(A1) | 2004-01-01 | Parrott et al. | Applicant |
| US2004/0002385(A1) | 2004-01-01 | Nguyen | Applicant |
| US2004/0005920(A1) | 2004-01-01 | Soltys et al. | Applicant |
| US2004/0029635(A1) | 2004-02-01 | Giobbi | Applicant |
| US2004/0043820(A1) | 2004-03-01 | Schlottmann | Applicant |
| US2004/0048671(A1) | 2004-03-01 | Rowe | Applicant |
| US2004/0068654(A1) | 2004-04-01 | Cockerille et al. | Applicant |
| US2004/0082385(A1) | 2004-04-01 | Silva et al. | Applicant |
| US2004/0087375(A1) | 2004-05-01 | Gelinotte | Applicant |
| US2004/0092310(A1) | 2004-05-01 | Brosnan et al. | Applicant |
| US2004/0106452(A1) | 2004-06-01 | Nguyen et al. | Applicant |
| US2004/0110557(A1) | 2004-06-01 | Rowe | Applicant |
| US2004/0132532(A1) | 2004-07-01 | Brosnan et al. | Applicant |
| US2004/0142744(A1) | 2004-07-01 | Atkinson et al. | Examiner |
| US2004/0147314(A1) | 2004-07-01 | LeMay et al. | Applicant |
| US2004/0219982(A1) | 2004-11-01 | Khoo et al. | Applicant |
| US2004/0229682(A1) | 2004-11-01 | Gelinotte | Applicant |
| US2005/0026680(A1) | 2005-02-01 | Gururajan | Applicant |
| US2005/0026682(A1) | 2005-02-01 | Grauzer et al. | Applicant |
| US2005/0051955(A1) | 2005-03-01 | Schubert et al. | Applicant |
| US2005/0051965(A1) | 2005-03-01 | Gururajan | Applicant |
| US2005/0054408(A1) | 2005-03-01 | Steil et al. | Applicant |
| US2005/0059479(A1) | 2005-03-01 | Soltys et al. | Applicant |
| US2005/0062226(A1) | 2005-03-01 | Schubert et al. | Applicant |
| US2005/0062227(A1) | 2005-03-01 | Grauzer et al. | Applicant |
| US2005/0070358(A1) | 2005-03-01 | Angell et al. | Examiner |
| US2005/0073102(A1) | 2005-04-01 | Yoseloff et al. | Applicant |
| US2005/0101367(A1) | 2005-05-01 | Soltys et al. | Applicant |
| US2005/0116020(A1) | 2005-06-01 | Smolucha et al. | Applicant |
| US2005/0164761(A1) | 2005-07-01 | Tain | Applicant |
| US2005/0176507(A1) | 2005-08-01 | Ephrati et al. | Examiner |
| US2005/0227760(A1) | 2005-10-01 | Vlazny et al. | Applicant |
| US2005/0258597(A1) | 2005-11-01 | Soltys et al. | Applicant |
| US2005/0266919(A1) | 2005-12-01 | Rowe et al. | Applicant |
| US2005/0288083(A1) | 2005-12-01 | Downs, III | Applicant |
| US2005/0288084(A1) | 2005-12-01 | Schubert | Applicant |
| US2005/0288085(A1) | 2005-12-01 | Schubert et al. | Applicant |
| US2006/0019739(A1) | 2006-01-01 | Soltys et al. | Applicant |
| US2006/0019745(A1) | 2006-01-01 | Benbrahim | Applicant |
| US2006/0035707(A1) | 2006-02-01 | Nguyen et al. | Examiner |
| US2006/0046849(A1) | 2006-03-01 | Kovacs | Examiner |
| US2006/0066444(A1) | 2006-03-01 | Steeves | Applicant |
| US2006/0121970(A1) | 2006-06-01 | Khal | Examiner |
| US2006/0211481(A1) | 2006-09-01 | Soltys et al. | Applicant |
| US2007/0004500(A1) | 2007-01-01 | Soltys et al. | Applicant |
| US2007/0006329(A1) | 2007-01-01 | Morrow et al. | Applicant |
| US2007/0015583(A1) | 2007-01-01 | Tran | Applicant |
| US2007/0054725(A1) | 2007-03-01 | Morrow et al. | Applicant |
| US2007/0060259(A1) | 2007-03-01 | Pececnik | Examiner |
| US2007/0082737(A1) | 2007-04-01 | Morrow et al. | Applicant |
| US2007/0111775(A1) | 2007-05-01 | Yoseloff | Applicant |
| US2007/0111791(A1) | 2007-05-01 | Arbogast et al. | Applicant |
| US2007/0243927(A1) | 2007-10-01 | Soltys | Examiner |
| US2007/0243935(A1) | 2007-10-01 | Huizinga | Applicant |
| US2007/0287535(A1) | 2007-12-01 | Soltys | Applicant |
| US2007/0298868(A1) | 2007-12-01 | Soltys | Applicant |
| US2008/0076536(A1) | 2008-03-01 | Shayesteh | Applicant |
| US2008/0076572(A1) | 2008-03-01 | Nguyen et al. | Examiner |
| US2008/0096659(A1) | 2008-04-01 | Kreloff et al. | Examiner |
| US2008/0113764(A1) | 2008-05-01 | Soltys | Applicant |
| US2008/0113781(A1) | 2008-05-01 | Soltys et al. | Applicant |
| US2008/0146337(A1) | 2008-06-01 | Halonen et al. | Applicant |
| US2008/0153599(A1) | 2008-06-01 | Atashband et al. | Applicant |
| US2008/0153600(A1) | 2008-06-01 | Swarna | Applicant |
| US2008/0154916(A1) | 2008-06-01 | Atashband | Applicant |
| US2008/0155665(A1) | 2008-06-01 | Ruppert et al. | Applicant |
| US2008/0162729(A1) | 2008-07-01 | Ruppert | Applicant |
| US2008/0171588(A1) | 2008-07-01 | Atashband | Applicant |
| US2008/0171598(A1) | 2008-07-01 | Deng | Applicant |
| US2008/0182651(A1) | 2008-07-01 | Marshall et al. | Examiner |
| US2008/0200255(A1) | 2008-08-01 | Eisele | Applicant |
| US2009/0115133(A1) | 2009-05-01 | Kelly et al. | Applicant |
| US2009/0117994(A1) | 2009-05-01 | Kelly et al. | Applicant |
| US2009/0118001(A1) | 2009-05-01 | Kelly et al. | Applicant |
| US2009/0118005(A1) | 2009-05-01 | Kelly et al. | Applicant |
| US2009/0118006(A1) | 2009-05-01 | Kelly et al. | Applicant |
| US2009/0124392(A1) | 2009-05-01 | Ruppert et al. | Applicant |
| US2009/0124394(A1) | 2009-05-01 | Swarna | Applicant |
| US2009/0125603(A1) | 2009-05-01 | Atashband et al. | Applicant |
| US2009/0131144(A1) | 2009-05-01 | Allen | Applicant |
| US2009/0131163(A1) | 2009-05-01 | Arbogast et al. | Applicant |
| US2009/0132720(A1) | 2009-05-01 | Ruppert et al. | Applicant |
| US2009/0163279(A1) | 2009-06-01 | Hermansen et al. | Applicant |
| US2009/0170594(A1) | 2009-07-01 | Delaney et al. | Applicant |
| US2009/0181776(A1) | 2009-07-01 | Deng | Applicant |
| DE4439502(C1) | 1995-09-01 | Applicant | |
| DE19748930(A1) | 1998-05-01 | Applicant | |
| DE19940954(A1) | 2001-03-01 | Applicant | |
| EP327069(A2) | 1989-08-01 | Applicant | |
| EP790848 | 1997-08-01 | Applicant | |
| EP1291045(A2) | 2003-03-01 | Applicant | |
| FR2775196 | 1999-08-01 | Applicant | |
| GB2380143(A) | 2003-04-01 | Applicant | |
| GB2382034(A) | 2003-05-01 | Applicant | |
| WO96/03188 | 1996-02-01 | Applicant | |
| WO96/36253 | 1996-11-01 | Applicant | |
| WO97/13227 | 1997-04-01 | Applicant | |
| WO/22585 | 2000-04-01 | Applicant | |
| WO2/05914(A1) | 2002-01-01 | Applicant | |
| WO3/060846(A2) | 2003-07-01 | Applicant | |
| WO2007/033207(A2) | 2007-03-01 | Applicant |
Non-Patent Literature (64)
- US 6,599,191, 07/2003, Breeding et al. (withdrawn)Applicant
- U.S. Appl. No. 11/030,609, filed Jan. 5, 2005, Soltys et al.Applicant
- U.S. Appl. No. 11/337,375, filed Jan. 23, 2006, Soltys et al.Applicant
- U.S. Appl. No. 11/408,862, filed Apr. 21, 2006, Soltys et al.Applicant
- U.S. Appl. No. 11/428,264, filed Jun. 30, 2006, Soltys.Applicant
- U.S. Appl. No. 11/437,590, filed May 19, 2006, Soltys et al.Applicant
- U.S. Appl. No. 11/479,930, filed Jun. 30, 2006, Soltys et al.Applicant
- U.S. Appl. No. 11/479,988, filed Jun. 30, 2006, Shayesteh.Applicant
- U.S. Appl. No. 11/480,273, filed Jun. 30, 2006, Soltys.Applicant
- U.S. Appl. No. 11/480,275, filed Jun. 30, 2006, Fleckenstein.Applicant
- U.S. Appl. No. 11/480,321, filed Jun. 30, 2006, Soltys.Applicant
- U.S. Appl. No. 11/480,345, filed Jun. 30, 2006, Fleckenstein.Applicant
- U.S. Appl. No. 11/480,349, filed Jun. 30, 2006, Soltys et al.Applicant
- U.S. Appl. No. 11/519,244, filed Sep. 11, 2006, Soltys et al.Applicant
- U.S. Appl. No. 60/501,489, filed Sep. 8, 2003, Soltys et al.Applicant
- U.S. Appl. No. 60/554,090, filed Mar. 17, 2004, Soltys et al.Applicant
- U.S. Appl. No. 60/838,280, filed Aug. 17, 2006, Soltys et al.Applicant
- U.S. Appl. No. 60/847,331, filed Sep. 26, 2006, Shayesteh.Applicant
- Bulaysky, J., “Tracking the Tables,” Casino Journal, May 2004, pp. 44-47, accessed Dec. 21, 2005, URL = http://www.ascendgaming.com/cj/vendors—manufacturers—table/Trackin916200411141AM.htm, 5 pages.Applicant
- Burke, A., “Tracking the Tables,” reprinted from International Gaming & Wagering Business, Aug. 2003, 4 pages.Applicant
- Gros, R., “All You Ever Wanted to Know About Table Games,” reprinted from Global Gaming Business, Aug. 1, 2003, 2 pages.Applicant
- Pro, L.V., “Book Review—The Card Counter's Guide to Casino Surveillance,” Blackjack Insider Newsletter, May 2003, #40, accessed Aug. 25, 2006, URL = http:/bjinsider.com/newsletter—40—surveillance.shtml, 5 pages.Applicant
- Snyder, A., “The High-Tech Eye.”excerpt from Blackjack Forum, Spring 1997, accessed Dec. 21, 2005, from Casino Software & Services, LLC, URL = http://www.casinosoftware.com/bj—forum.html.Applicant
- Terdiman, D., “Who's Holding the Aces Now?”, reprinted from Wired News, Aug. 18, 2003, 2 pages.Applicant
- Ward, K., “BJ Tracking System has Players Down for the Count,” Gaming Today, Mar. 5, 2002, accessed Dec. 21, 2005, from Casino Software & Services, LLC, URL = http://www.casinosoftware.com/gaming—today.html.Applicant
- Winkler, C., “Product Spotlight: MindPlay,” reprinted from Gaming and Leisure Technology, Fall 2003, 2 pages.Applicant
- Bally TMS, “MP21—Automated Table Tracking/Features,” 2 pages, Nov. 2005.Applicant
- Bally TMS, “MPBacc—Specifications/Specifications,” 2 pages, Nov. 2005.Applicant
- Bally TMS, “MPLite—Table Management System/Features,” 2 pages, Nov. 2005.Applicant
- Bravo Gaming Systems, “Casino Table Wager Analysis and Player Tracking System—Table Operations/Unique Features,” accessed Apr. 11, 2005, URL = http://genesisgaming.com, 4 pages.Applicant
- Casino Software & Services, LLC., accessed Aug. 25, 2006, URL = http:/casinosoftware.com/home.html, 6 pages.Applicant
- Gambling Magazine, “Gaming Company Takes RFID to the Casino,” Dec. 27, 2004, accessed Aug. 25, 2006, URL = http:/www.gamblingmagazine.com/managearticle.asp?C=290&A=13186, 4 pages.Applicant
- Hewlett Packard Handhelds, accessed Sep. 8, 2003, URL = http:/www.shopping.hp.com/cgi-bin/hpdirect/shopping/scripts/home/store—access.jsp?temp..., 2 pages.Applicant
- International Guild of Hospitality & Restaurant Managers, “Shuffle Master, Inc. (NasdaqNM:SHFL),” accessed Dec. 30, 2003, URL = http://hospitalityguide.com/Financial/Casinos/Shuffle.htm, 3 pages.Applicant
- Linksys WAP11 “Wireless Network Access Point,” accessed Sep. 8, 2003, URL = http:/www.linksys.com/products/product.asp?prid=157&grid=, 4 pages.Applicant
- Mikohn, “Mikohn Tablelink—The Industry's Premier Table Tracking Solution Delivers Improvements Straight to the Bottom Line,” 2 pages, before Jan. 1, 2004.Applicant
- Mikohn, “Tablelink™, The New Standard in Table Games,” before Jan. 1, 2004, 14 pages.Applicant
- Semtek PDA & Handheld Devices, Compaq iSwipe™ Magnetic Card Reader, accessed Sep. 8, 2003, URL = http:/www.semtek.com/products/iswipe.html, 3 pages.Applicant
- Shuffle Master, Inc., “Shuffle Master Announces New Products; Intelligent Table System to Be Debuted at G2E,” Sep. 10, 2003, 2 pages.Applicant
- Shuffle Master, Inc., “Shuffle Master Gaming Presents the Ultimate Player Rating System . . . Bloodhound Sniffs Out the Pros and Cons,” Dec. 31, 1997, 6 pages.Applicant
- English Translation of German Patent No. DE 197 48 930, publication date of May 14, 1998, inventor: Markeev.Applicant
- U.S. Appl. No. 11/558,409, filed Nov. 9, 2006, Soltys.Applicant
- U.S. Appl. No. 60/887,092, filed Jan. 29, 2007, Shayesteh.Applicant
- U.S. Appl. No. 12/112,231, filed Apr. 30, 2008, Morrow et al.Applicant
- U.S. Appl. No. 12/112,410, filed Apr. 30, 2008, McMahan et al.Applicant
- U.S. Appl. No. 12/112,501, filed Apr. 30, 2008, Nelson.Applicant
- U.S. Appl. No. 12/112,582, filed Apr. 30, 2008, Kelly et al.Applicant
- U.S. Appl. No. 12/112,691, filed Apr. 30, 2008, Backover et al.Applicant
- U.S. Appl. No. 12/112,740, filed Apr. 30, 2008, Kisenwether et al.Applicant
- U.S. Appl. No. 12/112,770, filed Apr. 30, 2008, Rehm et al.Applicant
- U.S. Appl. No. 12/112,928, filed Apr. 30, 2008, Young et al.Applicant
- U.S. Appl. No. 12/113,005, filed Apr. 30, 2008, McAllister et al.Applicant
- U.S. Appl. No. 12/113,021, filed Apr. 30, 2008, Singh et al.Applicant
- U.S. Appl. No. 12/113,038, filed Apr. 30, 2008, Arbogast et al.Applicant
- U.S. Appl. No. 12/269,673, filed Nov. 12, 2008, Ruppert et al.Applicant
- U.S. Appl. No. 12/271,337, filed Nov. 14, 2008, Singh et al.Applicant
- U.S. Appl. No. 12/271,736, filed Nov. 14, 2008, Crowder.Applicant
- U.S. Appl. No. 12/473,617, filed May 28, 2009, Jones.Applicant
- U.S. Appl. No. 12/500,298, filed Jul. 9, 2009, Rajaraman et al.Applicant
- Bally Technologies, Inc., iVIEW, http://ballytech.com/systems/product.cfm?id=9, download date Nov. 6, 2007, 2 pages.Applicant
- Richard Soltys, “Wireless Gaming Environment,” Non-Final Office Action mailed Oct. 27, 2009, for U.S. Appl. No. 11/734,639, 10 pages.Applicant
- Richard Soltys, “Wireless Gaming Environment,” Amendment filed Jan. 19, 2010, for U.S. Appl. No. 11/734,639, 14 pages.Applicant
- Richard Soltys, “Wireless Gaming Environment,” Final Office Action mailed Mar. 22, 2010, for U.S. Appl. No. 11/734,639, 14 pages.Applicant
- Richard Soltys, “Wireless Gaming Environment,” Amendment filed Jul. 22, 2010, for U.S. Appl. No. 11/734,639, 16 pages.Applicant