Patent Grant
7303470
The present invention relates generally to gaming machines, and more particularly, to a system and method for remotely accessing the player tracking system.
The growth and competition in the casino gaming market in recent years and the increasingly sophisticated and complex technology being integrated into the gaming environment, at the individual game, casino management, and auditing levels, presents both challenges and opportunities to game manufacturers, gaming establishment operators, and regulatory agencies. The technological capabilities and requirements of, for example, advanced electronic games, multi-site gaming operations, detailed player tracking, wide area progressive jackpots, and various alternatives to the use of currency and coins by players, all present a potentially huge pool of ever-changing data which can be of great value to casino operators (from a management standpoint) and to regulators from an audit/compliance standpoint.
Players may also be given an incentive through a player tracking club. Usually, a player is identified during play by a player tracking ID card and/or a player identification number (PIN). The player tracking system tracks the player's play and awards player tracking points according to established criteria. The player tracking points may be redeemed for prizes, such as complimentary meals or merchandise.
Typically, the player tracking system is accessed at workstation or computers which are linked to a remote server. The computer applications which are used to access the player tracking system for various functions are stored on the workstation.
However, these types systems are inflexible and do not provide the casino operator with the maximum benefit and advantages available from the information and systems now available.
The present invention is aimed at one or more of the problems as set forth above.
In one aspect of the present invention, a remote system for use with a gaming system is provided. The gaming system implements a player tracking system. The system includes a remote device and remote network interface coupled to the remote device for exchanging data between a host computer and the remote device. The data includes voucher information to issue a voucher to the player in the player tracking system. The voucher has at least one of an associated product and service.
In another aspect of the present invention, a method for implementing the player tracking system for use with a gaming system is provided. The method includes the steps of sending a fillable form to a remote device and filling out the form with data by a user on the remote device for issuing a voucher to the player in the player tracking system. The voucher has at least one of an associated service and product.
Other advantages of the present invention will be readily appreciated as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings wherein:
I. Overview
With reference to the drawings and in operation, the present invention provides a system 10 and methods related to a player tracking method or to one or more gaming devices 12.
The gaming devices 12 may be electronic or electric gaming machines 13, such as slot or video slot machines, poker or video poker machines, arcade or video arcade games, and the like, but may also include other types of devices 12A connected to the system 10, such as virtual gaming machines (for online gaming), electronic interfaces for use with table games, vending machines, token or credit dispensing machines, ticket redemption machines, or any other electric or electronic device connected to the network.
II. The Gaming System
In one embodiment, the system 10 and methods may be embodied or implemented via an entertaining management and monitoring system or gaming system 14 which is shown in block diagram form in
In the illustrated embodiment, the system 10 includes eight electronic gaming machines 13A-13H. However, it should be noted that the present invention is not limited to any number of devices 12 or machines 13. In one embodiment, the machines 13 are organized into banks (not shown), each bank containing a plurality of machines 13.
The gaming devices 12 are connected via a network 16 to one or more host computers 18, which are generally located at a remote or central location. The computer 18 includes a computer program application 20 which maintains one or more databases 22. In one embodiment, the database(s) are Oracle database(s).
The computer program application 20 and databases 22 may be used to record, track, and report accounting information regarding the gaming devices 12 and/or users of the gaming devices 12 or players of the electronic gaming machines 13. Additionally, the computer program application 20 and databases 22 may be used to maintain information related to player tracking accounts (see below).
In general, the electronic gaming machines 13 are playable by a player 24. The player 24 may select one of the electronic gaming machines 13C to play and insert a coin, credit, coupon, and/or player tracking card (not shown) into the chosen gaming machine 13C. Generally, the electronic gaming machines 13C have an associated number of credits or coins required in order to play. In the case of video slot or poker games, the game is played and an award in the form of credits may be awarded based on a pay table of the gaming machine 13.
With reference to
The machine 13C comprises a game controller 26, or central processing unit (CPU), a coin-bill management device 28, a display processor 30, a RAM 32 as a memory device and a ROM 34 (generally provided as an EPROM). The CPU 26 is mainly composed of a microprocessor unit and performs various calculations and motion control necessary for the progress of the game. The coin-bill management device 28 detects the insertion of a coin or a bill and performs a necessary process for managing the coin and the bill. The display processor 30 interprets commands issued from the CPU 26 and displays desirable images on a display 36. The RAM 32 temporarily stores programs and data necessary for the progress of the game, and the ROM 34 stores, in advance, programs and data for controlling basic operation of the machine 12C, such as the booting operation thereof, game code and graphics.
Input to the gaming device 12C may be accomplished via mechanical switches or buttons or via a touchscreen interface (not shown). Such gaming machines 12 are well known in the art and are therefore not further discussed.
The player 24 is identified via the player tracking card and/or a player identification number entered into player tracking device 38 at each gaming machine 12 (see below). Player tracking accounts may be used, generally, to provide bonuses to a player, in addition to the award designated by, in the case of a video slot or poker machine, the gaming machine's 12 paytable. These bonuses may be awarded to the player 24 based a set of criteria, including, but not limited to, a) the player's play on the machine 12C, b) the player's overall play, c) play during a predetermined period of time, and d) the player's birthday or anniversary, or e) any other definable criteria. Additionally, bonuses may be awarded on a random basis, i.e., to a randomly chosen player or randomly chosen game 12. Bonuses may also be awarded in a discretionary manner or based on other criteria, such as, purchases made at a gift shop or other affiliated location.
In one embodiment, the player tracking device 38 includes a processor 40, a player identification card reader 42 and/or a numeric keypad 44, and a display 46. In one embodiment, the display 46 is a touchscreen panel and the numeric keypad 44 is implemented thereon.
The player 24 may be identified by entry of a player tracking card into the player identification card reader 42 and/or entry of a player identification number (PIN) on the numeric key pad 46. The play tracking device 38 may also be used to communicate information between the computer 18 and the corresponding gaming machine 12C. The player tracking device 40 may also be used to track bonus points, i.e., incentive points or credits, downloaded from the computer 18.
In one aspect of the present invention, the bonuses are awarded as bonus points. In one embodiment, the bonus points are incentive points. In another embodiment, the bonus points are credits.
The incentive points may converted to credits using a predetermined ratio. The predetermined ratio may be 1 or any other desired ratio. The predetermined ratio may also be varied based on determined criteria, e.g., the gaming machine 12 being played, the player, or the time of day. Incentive points may be designated as cashable or non-cashable. The incentive points in a player account may be downloaded to one of the gaming machines 12 for play.
III. Remote System
Returning to
In the illustrated embodiment, there are four remote devices 50A, 50B, 50C, 50D, however, this is for discussion purposes only. Any number of remotes devices 50 may be included.
The remote devices 50 are connected to the network 16 through a network link 52. In one aspect of the present invention, the network link 52 is a wireless connection. In one embodiment, the wireless connection uses the IEEE 802.11 standard, e.g., 802.11b or 802.11g. However, it should be noted that wireless links using other standards may also be used where appropriate, such as a short range radio link (e.g., a link using the technology known as “Blue Tooth”). In another aspect of the present invention, the network link 52 may be a wire link.
The remote devices 50 are generally used by a user 54 and provides, as discussed below, access to various data and/or functions of the gaming system 14.
In one aspect, the user 54 is an employee of the gaming established where the gaming system 14 is operating. Typically, the user 54 has an assigned role (or type) based on their job description. Typical roles may include, but are not limited to, system administrator, supervisor, pit, pit manager, slot floor employee, patron host, player's club, security, security supervisor, slot attendant, slot director, slot shift supervisor, slot technician, sports and racebook, surveillance, and table supervisor.
In one embodiment of the present invention, the remote devices 50 provides access to one or more types of data and/or one or more functions based on the assigned role of the user 54. In one embodiment, a remote device 50 may provide access to one or more of the following functions: remote patron signup, remote patron information, remote device information, remote cash ticket processing, remote jackpot ticket processing, remote hopper fill ticket processing, remote table rating interface, remote attendance, remote surveillance, adjusting a player's bonus or comp points, issuing comp vouchers to a player, redeeming printed vouchers, listing and redeeming outstanding vouchers assigned to a player, and retrieving and displaying information related to a specific remote device 50. Each of these functions is described more fully below.
In one embodiment of the present invention, the remote device 50A may be a mobile computer based on the PALM operating system or Microsoft Windows operating system. With specific reference to
Additionally or alternatively, the remote device 50A may include an ID card reader 62 capable of reading magnetic stripe ID cards.
In another embodiment, the remote devices 50 are desktop, laptop, notebook, and/or sub-notebook computers.
Returning to
In one aspect of the present invention, all interaction with the user, including the display of data and queries and the input of data, is handled by the web client 56. The web client 56 is responsible for acquiring user input, e.g., through forms, and formatting and presenting information to the user 54. The web client 56 is a computer application which is accessed via a web browser, such as Microsoft Internet Explorer, available from Microsoft Corp., of Redmond Calif. The web client 56 may be written in Hypertext Mark-Up Language (HTML) and include one or more servlets (see below) which may be written in a computer programming language, such as Java.
As shown in
In one aspect of the present invention, the remote network interface 68 is coupled to the database 22 by one or more data objects 70. In one embodiment, data is stored in the database 22 in data tables. The data objects 70 handle requests from the remote network interface 68, abstracts the required data from the database tables and/or sets data into the database tables.
As shown, in
The first data objects 76 are coupled to the database tables and abstract specific database tables for the at least one second data object 74. The first data objects 76 handle retrieving and setting data into specific database tables.
The at least one second data object 74 is coupled to the first data objects 76 assemble multiple first data objects 76 into a single third data object 72. The at least one second data object 74 abstract the third data object 72 from the database tables.
The third data object 72 is coupled to the at least one second data object 74. The third data object receives queries from the remote network interface, retrieves responsive data from the database (through the first and second data objects 74,76), formats the responsive data and returns the responsive data to the remote network interface.
With reference to
The login layer 82 provides security. It allows the user 54 to logon to the remote system 48. In one embodiment, the user 54 enters a name and password to logon. The user 54 may also be required to enter or select the site at which the user 54 is located.
The menu layer 90 allows the user 54, once logged on, to navigate to and between servlets. The servlets are downloaded to the remote device 50 from the hose computer 18 as needed. The menu layer 90 also handles providing access to those servlets to which the user 54 has access, typically based on an assigned role (see above).
The form and servlet layers 78, 84 provides common functionality for the servlets.
A. Remote Player or Patron Signup
With reference to
If the player 24 wants to enroll, the user 54 enters sign-up information or data onto the remote device 50A and gives the player 24 a player ID card. The sign-up information is sent by the remote device 50A to the host computer 18 and stored in the database 22 along with the ID card number of the assigned player ID card.
In one embodiment, the user 54 navigates to a servlet for enrolling the player 24 using the menu layer 80. The menu layer 80 requests the servlet from the host computer 18 from which it is then downloaded to the remote device 50A.
In one embodiment, only the player's name and a player identification number (PIN) is required. The player identification number may be selected by the player 24 or be a temporary default PIN assigned to the player ID card. The player ID card number to be assigned to the player 24 may be read by the ID card reader 62 or the barcode reader 66, as appropriate.
When the user 54 selected enrollment from the menu layer, the web client 56 relays the request to the remote network interface 68. The remote network interface 68 retrieves a signup form and sends the signup form to the remote device 50A for display and interaction with the user 54 via the web client 56.
With specific reference to
With specific reference to
In a first step 96, the signup form is displayed on the remote device 50A. In a step 98, if all required information, e.g., a zip code, was entered then the method 94 proceeds to a third step 100. If all required information was not entered, then an error message is displayed in a fourth step 102 and the process returns to the first step 96.
In the third step 100, the zip code is processed, i.e., the corresponding city and state are determined. In a fifth step 104, if the zip code is not valid, then the method 94 displays an error message (fourth step 102). If the zip code is valid, then the method 94 proceeds to a sixth step 106.
In the sixth step 106, the enrollment data is stored are stored as records in the database 22 and control proceeds to a seventh step 108. In the seventh step 108, if a room number, i.e., the hotel room hotel in which the player 24 is residing was entered, then the process proceeds to an eighth step 110. Otherwise, the method 96 returns to the first step 96.
In the eighth step 110, an external system (not shown), may be notified for the creation of room lock keys. One such system In one embodiment as discussed below, the room lock keys may be used for the player tracking system and/or room locks.
An exemplary signup form 110, displayed on the remote device 50A by the web client 56 is shown in
In another embodiment, the signup form 110 requires additional information. The additional information may include, but is not limited to the following: player ID card number (from pre-printed card or left blank for system generated card), address, zip code, country, telephone number(s), room number, number of adult cards, number of child cards, signup date, and one or more notes. Child cards operate only the lock of a hotel room. Adult cards work in the player tracking system and operate the room lock.
Additionally as discussed above, the display 46 is a touchscreen display. In one embodiment, the display may capture a signature of the player 24. The player's signature may be also be sent to the host computer 18 with the enrollment data and stored in the database 22.
B. Remote Patron Information
With reference to
In the illustrated embodiment, interaction with the user 54, including receiving input and displaying the player information, is accomplished using the web client 56.
In one aspect of the present invention, the user 54 may identify the player 24 through entry of the player's ID card number into the remote device 50A. In one embodiment, the ID card number may be entered manually. In another embodiment, the ID card number may be read from the player's ID card using the card reader 62 or the barcode reader 66 as appropriate.
In another aspect of the present invention, if the player 24 is utilizing one of the devices 12 and has identified themselves to the player tracking system by entry of the ID card into the device 12 and/or entered in their PIN number, the user 54 may identify the player 24 by entered a device ID number associated with the respective device 12. As discussed below, the player tracking system has associated the ID number of the device 12 with the player 24 while the player 24 is using the device 12. Thus, using the device ID number, the host computer 18 may determine the ID number of the player 24.
In one embodiment, the user 54 navigates to a servlet for requesting player information using the menu layer 80. The menu layer 80 requests the servlet from the host computer 18 from which it is then downloaded to the remote device 50A.
The servlet displays a request form which is displayed to the user 54. As discussed above, the user 54 may either enter the player ID card number of the player 24 (manually or reading it from the ID card) or a device ID number associated with a device 12 being used by the player 24. The user 54 enters identification information (in the form of the player ID card number or the device ID number) which is returned to the host computer 18 by the web client 56. The remote network interface 68 receives the identification information, retrieves the player information and returns the player information to the remote device 50A where it is displayed.
With specific reference to
With specific reference to
In a first step 134, the request form is displayed on the remote device 50A. In a second step 136, if a player ID card number has been entered, then the method 132 proceeds to a third step 138. In the third step 138, the ID card number is validated. In a fourth step 140, if the ID card number is not valid, an error message is displayed in a fifth step 142. If the ID card number is valid, then the message proceeds to a sixth step 144.
In the sixth step 144, the query (request for player information) is processed by the host computer 18. The player (or patron) information is then returned to the remote device 50A to be displayed in an seventh step 146.
In the second step 136, if an ID card number has not been entered, then the method 132 proceeds to an eighth step 148. In the eighth step 148, if a device (or asset) number has been entered, then the method 132 proceeds to a ninth step 150. If a device number has not been entered, then the method 132 proceeds to the fifth step 142 and an error message is displayed.
In the ninth step 150, the device number is validated. In a tenth step 152, if the device number is valid, then control proceeds to the fifth step 144. Otherwise, the method 132, proceeds to the fifth step 142.
With specific reference to
C. Remote Device Information
With reference to
In the illustrated embodiment, interaction with the user 54, including receiving input and displaying the asset information is accomplished using the web client 56.
In one aspect of the present invention, the user 54 may identify the gaming device 12, such as an electronic gaming machine 13 by entering identification information. In one embodiment, the identification information is an asset or device ID number. The ID number may be manually entered by the user 54. In another embodiment, the user 54 may use the barcode reader 66 to read a barcode, located on the gaming device 12, containing the device ID number.
In one embodiment, the user navigates to a servlet for requested device information using the menu layer 80. The menu layer 80 requests the servlet from the host computer 18 from which it is then downloaded to the remote device 50A.
The servlet displays a request form (not shown) which is displayed to the user 54. After the asset or device ID number entered, the ID number is sent to the remote network interface 68, which process the query, and returns the requested device information to the remote device 50A where it is displayed.
With specific reference to
With specification reference to
In a first step 164, the request form is displayed on the remote device 50A. In a second step 166, if an asset number has been entered then the method 162 proceeds to a third step 170. Otherwise, an error message is displayed in a fourth step 168.
In the third step 170, the asset number is validated. In a fifth step 172, if the asset number is valid then the method 162 proceeds to a sixth step 174. In the sixth step 174, the query (request for asset information) is processed by the host computer 18. The device or asset information is returned to the remote device 50A to be displayed in a seventh step 176.
With specific reference to
D. Remote Cash Ticket Processing
In one embodiment, a gaming system includes a gaming machine that may issue a cash ticket. The cash ticket is issued when a player elects to quit playing a particular gaming machine after accumulating a number of credits. The number of credits is generally the sum of an original number of credits, any downloaded credits, any inserted credits, and any winnings (or losses).
With reference to
If the player 24 wants to cash out, the user 54, via the remote device 50A, requests a cash ticket form. The remote network interface 68 sends the cash ticket form to the remote device 50A.
When the user 54 selects the cash ticket form from the menu layer 80, the web client 56 relays the request to the remote network interface 68. The remote network interface 68 retrieves the cash ticket form and sends the cash ticket form to the remote device 50A for display and interaction with the user 54 via the web client 56.
The cash ticket form may include a cash ticket button for selecting by the user 54 to communicate each step of the cash ticket processing that has occurred. For example, the cash ticket button is a request button that the user 54 selects when the user 54 is approached by the player 24. The cash ticket button may be an acknowledge button selected by the user 54 after validating the cash ticket and prior to processing the cash ticket. The cash ticket button may also be a process button selected by the user 54 after confirming that the cash ticket may be paid. The cash ticket button may also be a paid button to confirm that the user 54 has paid to the player 24 the value of the cash ticket. Each time the cash ticket button is selected by the user 54, the remote device 50A sends a notification of the event and the remote network interface 68 stores the notification in the host computer 18 which then updates the data in the database 23 relating to the status of the cash ticket processing.
The cash ticket form may also include a field wherein the user 54 enters the cash ticket id such as a number. The user 54 enters cash ticket information or data onto the remote device 50A to verify that the cash ticket is valid and has not been previously processed. If the cash ticket id is invalid or the cash ticket has already been processed, an error message is displayed at the remote device 50A. The cash ticket information is sent by the remote device 50A to the host computer 18 where cash ticket information is retrieved and sent back to the remote device 50A. In one embodiment, the cash ticket id is entered manually, then the user 54 selects a cash ticket entry button to send the cash ticket form to the host computer 18. In another embodiment, the cash ticket id is encoded in a barcode printed on the cash ticket. The bar code is read by the bar code reader and sent to the host computer 18.
In one embodiment, the user 54 navigates to a servlet 24 using the menu layer 80 for inputting and retrieving cash ticket information. The menu layer 80 requests the servlet from the host computer 18 from which it is then downloaded to the remote device 50A.
After the validity of cash ticket is confirmed, the cash ticket information is retrieved from the database 22 by the remote network interface 68 and displayed to the user 54 at the remote device 50A. With specific reference to
The cash ticket information includes ticket details 168, such as a gaming machine identifier. The gaming machine identifier includes a gaming machine id and a gaming machine location to identify the gaming machine issuing the cash ticket. The ticket details 168 further include a date identifier for identifying the issue date of the cash ticket, a shift identifier for identifying the work shift during which the cash ticket was issued, and a value identifier for identifying the value of the cash ticket, thereby allowing the user 54 to confirm the value printed on the cash ticket and the value stored in the host computer 18.
With specific reference to
With specific reference to
In a first step 178, the cash ticket form is displayed on the remote device 50A. In a second step 180 a cash ticket id is entered. In a third step 182, the cash ticked id is verified. If the cash ticket id is invalid, then the method 176 proceeds to a fourth step 184. If the cash ticket id corresponds to a valid unprocessed cash ticket, then the method 178 proceeds to a fifth step 186. In the fourth step 184, an error message is displayed and the method 176 returns to the first step 178.
In the fifth step 186, the ticket details are retrieved from the database 22 and control proceeds to a seventh step 188. In the seventh step 188, the ticket details are processed and display at the remote device 50A. The user 54 may then pay the player. As discussed above, the user may be required to acknowledge through the selection of the cash ticket button at each step. Once the user has acknowledged that the player has been paid, the remote display displays a cash ticket paid message in an eighth step 190.
E. Remote Jackpot Ticket Processing
In one embodiment, a gaming system includes a gaming machine that may issue a jackpot ticket. In one embodiment, a jackpot ticket is issued by the gaming machine when a play of the game results in a win having an associated number of credits over a predetermined number of credits. Such a jackpot causes the gaming machine 12 to lock up, issue an alert and prevents the player from playing.
In another embodiment, the gaming machine 12 does not issue jackpot ticket. However, the user 54 may be required to go to the gaming machine 12 to process the jackpot
With reference to
In one embodiment, the jackpot is dispensed by the gaming machine 13, while jackpots above the threshold require interaction with an employee, i.e., the user 54. Additionally, the jackpot may be required to be paid by a cashier. If a jackpot ticket has been issued, the user 54 may be approached by a player 24 who requests to collect the value of the jackpot. Alternatively, the user 54 may have to travel to the gaming machine 13 to process the jackpot.
If the player 24 wants to collect the jackpot, the user 54, via the remote device 50A, requests a jackpot form (not shown). The remote network interface 68 sends the jackpot form to the remote device 50A.
When the user 54 selects the jackpot form from the menu layer 80, the web client 56 relays the request to the remote network interface 68. The remote network interface 68 retrieves the jackpot form and sends the jackpot form to the remote device 50A for display and interaction with the user 54 via the web client 56.
The jackpot form includes a jackpot button for selecting by the user 54 to communicate each step of the jackpot processing that has occurred. For example, the jackpot button is a request button that the user 54 selects when a jackpot is announced and the user 54 is approached by the player 24 to collect the jackpot. The jackpot button may be an acknowledge button selected by the user 54 after validating the jackpot and prior to processing the jackpot. The jackpot button may also be a process button selected by the user 54 after confirming that the jackpot may be paid. The jackpot button may also be a paid button to confirm that the user 54 has paid to the player 24 the value of the jackpot. Each time the jackpot button is selected by the user 54, the remote device 50A sends a notification of the event and the remote network interface 68 stores the notification in the host computer 18 which then updates the data in the database 22 relating to the jackpot status in the jackpot processing.
In one embodiment, the jackpot form lists several fields having jackpot information, including the jackpot identifier, fill detail and jackpot status, for all active jackpots. The user 54 may select either the jackpot identifier or the jackpot status. If the user 54 selects the jackpot identifier, then jackpot detail is displayed on the remote device 50A. If the user 54 selects jackpot status, then the jackpot status advances to an advanced jackpot status, a notification is sent to the host computer 18 to update the database 22 and the remote device 50A displays the updated jackpot status on the jackpot form.
In another embodiment, the jackpot form includes a field wherein the user 54 enters the jackpot id such as a number. The user 54 enters jackpot information or data onto the remote device 50A to verify that the jackpot is valid and has not been previously processed. If the jackpot id is invalid or the jackpot has already been processed, an error message is displayed at the remote device 50A. The jackpot information is sent by the remote device 50A to the host computer 18 where jackpot information is retrieved and sent back to the remote device 50A.
In one embodiment, the jackpot id is entered manually, then the user 54 selects a jackpot entry button to send the jackpot form to the host computer 18. In another embodiment, the jackpot id is read by the bar code reader and sent to the host computer 18.
In one embodiment, the user 54 navigates to a servlet 24 using the menu layer 80 for inputting and retrieving jackpot information. The menu layer 80 requests the servlet from the host computer 18 from which it is then downloaded to the remote device 50A.
After the validity of jackpot is confirmed, the jackpot information is retrieved from the database 22 by the remote network interface 68 and displayed to the user 54 at the remote device 50A. With specific reference to
The jackpot information includes fill detail 198, such as a gaming machine identifier. The gaming machine identifier includes a gaming machine id and a gaming machine location to identify the gaming machine issuing the jackpot. The fill detail 198 further includes a gaming date for identifying the issue date of the jackpot, a gaming shift for identifying the work shift during which the jackpot was issued, and a jackpot value for identifying the value of the jackpot, thereby allowing the user 54 to confirm the value printed on the jackpot and the value stored in the host computer 18.
If the user 54 selects the jackpot identifier field on the jackpot form, jackpot detail 200 as a function of the jackpot identifier is retrieved from the host computer 18 and displayed at the remote device 50A. Jackpot detail 200 may include the gaming machine id and the gaming machine location to identify the gaming machine issuing the jackpot. The jackpot detail 200 may further include a gaming machine name for identifying the particular game issuing the jackpot, a gaming denomination for identifying the particular type of credit issued, the gaming date for identifying the issue date of the jackpot, and the gaming shift for identifying the work shift during which the jackpot was issued.
With specific reference to
With specific reference to
F. Remote Hopper Fill Ticket Processing
With reference to
Once an alert is issued, the user 54, via the remote device 50A, may acknowledge the alert and request a hopper fill form (not shown). The remote network interface 68 sends the hopper fill form to the remote device 50A.
When the user 54 selects the hopper fill form from the menu layer 80, the web client 56 relays the request to the remote network interface 68. The remote network interface 68 retrieves the hopper fill form and sends the hopper fill form to the remote device 50A for display and interaction with the user 54 via the web client 56.
In one embodiment, the hopper fill form includes a hopper fill button (not shown) for selecting by the user 54 to communicate each step of the hopper fill processing that has occurred. For example, the hopper fill button is a request button that the user 54 selects when an alert is announced and the user 54 approaches the gaming machine 13 to process the hopper fill. The hopper fill button may also be an acknowledge button selected by the user 54 after validating the hopper fill and prior to processing the hopper fill. The hopper fill button may also be a process button selected by the user 54 after confirming that the hopper is being restocked. The hopper fill button may also be a fill button to confirm that the user 54 has completed restocking the hopper. Each time the hopper fill button is selected by the user, the remote device 50A sends a notification of the event and the remote interface stores the notification in the host computer 18 which then updates the data in the database 22 relating to the credit status in the hopper fill processing.
In one embodiment, the hopper fill form lists several fields having hopper fill information, including the hopper fill identifier, fill detail and credit status, for all active hopper fills. The user 54 may select either the hopper fill identifier or the credit status. If the user 54 selects the hopper fill identifier, then hopper fill detail is displayed on the remote device 50A. If the user 54 selects credit status, then the credit status advances to an advanced credit status, a notification is sent to the host computer to update the database and the remote device displays the updated credit status on the hopper fill form.
In another embodiment, the hopper fill includes a field wherein the user 54 enters the hopper id, such as a number. The user 54 enters hopper fill information or data onto the remote device 50A to verify that the hopper id is valid and has not been previously processed. If the hopper id is invalid or the hopper fill has already been processed, an error message is displayed at the remote device 50A. The entered hopper fill information is sent by the remote device 50A to the host computer 18 where additional hopper fill information is retrieved and sent back to the remote device 50A. In one embodiment, the hopper id is entered manually, then the user 54 selects a hopper fill entry button to send the hopper fill form to the host computer 18. In another embodiment, the hopper id is read from a barcode on the hopper or on the game machine 13 by the bar code reader 66 and sent to the host computer 18.
In one embodiment, the user 54 navigates to a servlet 24 using the menu layer 80 for inputting and retrieving hopper fill information. The menu layer 80 requests the servlet from the host computer 18 from which it is then downloaded to the remote device 50A.
After the validity of hopper is confirmed, the hopper fill information is retrieved from the database 22 by the remote network interface 68 and displayed to the user 54 at the remote device 50A. With specific reference to
The hopper fill information includes fill detail 248, such as a gaming machine identifier. The gaming machine identifier includes a gaming machine id and a gaming machine location to identify the gaming machine requiring the hopper fill. The fill detail 248 may further include a gaming date for identifying the issue date of the fill, a gaming shift for identifying the work shift during which the fill was issued, and/or a credit value for identifying the value of the credits supplied.
If the user 54 selects the hopper fill identifier field on the hopper fill form, hopper fill detail as a function of the hopper fill identifier is retrieved from the host computer 18 and displayed at the remote device 50A. In one embodiment, the hopper fill detail includes the gaming machine id and the gaming machine location to identify the gaming machine requiring the credit or hopper fill. The hopper fill detail may further include a gaming machine game for identifying the particular game issuing the credits, a gaming denomination for identifying the particular type of credit issued, the gaming date for identifying the fill date of the hopper, and/or the gaming shift for identifying the work shift during which the hopper was filled.
With specific reference to
With specific reference to
In a first step 260, the remote device 50A displays selectable hopper fill information, including pending fills having a credit status and hopper fill identifier. In an alternate embodiment, the hopper fill form or gaming machines 13 having hopper fill information, is displayed on the remote device 50A. In one embodiment, the hopper fill information is selectable. In another embodiment the hopper fill information is fillable requiring credit refill.
In a second step 262, the user 54 selects a pending fill. If the user 54 selects the hopper fill identifier, control proceeds to a third step 264, the fill detail is displayed and control returns to the first step 260. If the user 54 selects the credit status, then the credit status advances to an advanced credit status and control returns to the first step 260. If all required information was not entered, then an error message is displayed and the hopper fill form is displayed again.
Then he hopper id is verified. If the hopper id is not valid, then the method 258 displays an error message (fourth step 266). If the hopper id is valid, then the fill detail is retrieved from the database 22 and displayed at the remote device 50A.
After the hopper is filled with credits by the user 54, the remote display displays a credit filled message.
If the user selects another hopper fill identifier, the hopper fill detail is retrieved from the host computer and displayed on the remote device 50A.
If the user selects a credit status, the credit status advances to an advanced credit status which is then displayed at the remote device 50A.
G. Remote Table Rating Interface
With reference to
In the illustrated embodiment, interaction with the user 54, including receiving input and displaying the player information, is accomplished using the web client 56.
In one aspect of the present invention, the user 54 may identify the player 24 through entry of the player's ID card number into the remote device 50A. In one embodiment, the ID card number may be entered manually. In another embodiment, the ID card number may be read from the player's ID card using the card reader 62 or the barcode reader 66 as appropriate.
In another aspect of the present invention, if the player 24 is utilizing one of the devices 12 and has identified themselves to the gaming system by entry of the ID card into the device 12 and/or entered in their PIN number, the user 54 may identify the player 24 by entering a device ID number associated with the respective device 12. As discussed below, the gaming system has associated the ID number of the device 12 with the player 24 while the player 24 is using the device 12. Thus, using the device ID number, the host computer 18 may determine the ID number of the player 24.
In one embodiment, the user 54 navigates to a servlet for requesting player information using the menu layer 80. The menu layer 80 requests the servlet from the host computer 18 from which it is then downloaded to the remote device 50A.
The servlet displays a table rating form which is displayed to the user 54. As discussed above, the user 54 may either enter the player ID card number of the player 24 (manually or reading it from the ID card) or a device ID number associated with a device 12 being used by the player 24. The user 54 enters the player information (in the form of the player ID card number or the device ID number) which is returned to the host computer 18 by the web client 56. The remote network interface 68 receives the player information, retrieves the table rating information 450 and returns the table rating information 450 to the remote device 50A where it is displayed. With specific reference to
When the player information is entered, the remote network interface 68 determines whether the information is valid. If valid, the table rating information 450 is stored in or retrieved from the database 22 as a function of the identification information. If invalid, an error message is displayed on the remote device 50A. The player information 450 includes a player identifier such as a player number, player name and address, and the like.
The purpose of the table rating information 450 is to register and display a patron's risk or ranking at a particular gaming machine. The risk or ranking informs the user 54 about the player's 24 spending or risk habits during a given session of play at a gaming machine.
The player information includes a table rating status of open or closed for a particular gaming machine 13. If the status is open, the player is currently playing the particular gaming machine 13, thereby enabling the user to generate a table rating. When the player 24 decides to discontinue playing, the user 54 swipes the player's 24 ID card and brings up the table rating status in a closed status form (not shown) having fillable fields and a status button. The user 54 enters table rating information about the session, including but not limited to the player name, the gaming machine 13, the gaming machine location, the time the player 24 began play, the time the player 24 ceased play, the average bet by the player 24, and the amount won by the player 24 when leaving the gaming machine 13. The user 54 selects the status button and the table rating is established, sent to the database via the remote network interface and stored therein. Thereafter, any remote devices displaying a table rating form relating to the particular gaming machine 13 displays the newly entered table rating information.
If, after swiping the player's card, the player 24 does not have an open table rating, an open table form is displayed on the remote device. The open table form is fillable by the user 54 with table rating details which may include the player's name, the zone information (gaming machine location), a selectable list of the bank information (gaming machines 13) available at that location, a seat identifier at which the player 24 is seated, the estimated average bet by the player 24, the bet value the player is opening the gaming machine 13 with. The zone information entered by the user 54 may also include bank information as a function of the zone information. The bank information associated with the zone information is displayed and the user 54 selects the appropriate banking information associated with the particular gaming machine 13.
Once the information is entered, the user 54 selects the status button to send and store the table rating details to the database 22 and update the table rating status to open. The updated table rating status is sent to all remote devices displaying information for the particular gaming table. The update may be sent automatically or upon request.
With specific reference to
With specific reference to
In a first step 460, the table rating form is displayed on the remote device 50A.
In a second step, if a player ID card number is entered, then the method proceeds to a third step. The table rating status is then returned to the remote device 50A to be displayed in the third step 464.
In a fourth step 466, if the table rating status is open, the closed status form is displayed on the remote device.
In a fifth step 468, t the table rating is closed and control returns to the first step 460. In the third step 464, if the table rating status is not open, then the method 458 proceeds to a sixth step 470.
In the sixth step 470, the system determines if the remote network interface is a casino. System view shows the zones of the system and control proceeds to a seventh step 472. If the system view shows the zones then control proceeds to a seventh step 472, otherwise control proceeds to a ninth step 476.
In the seventh step 472, zone information is displayed.
In an eighth step 474, zone is selected and control proceeds to the ninth step 476.
In the ninth step 476, the system determines if the remote network interface shows the zone view and control proceeds to a tenth step 478.
If the system shows the zone view, then bank information is shown in the tenth step 478 and control proceeds to an eleventh step 480. Otherwise, control proceeds to a twelfth step 482.
In the eleventh step 480, a bank is entered, and control proceeds to the twelfth step 482.
In the twelfth step 482, the open rating form is displayed and control proceeds to a thirteenth step 484.
In the thirteenth step 484, the user 54 enters table rating information.
In the fourteenth step 486, the table rating is opened and control returns to the first step 460.
H. Remote Attendance
With reference to
In the illustrated embodiment, interaction with the user 54, including receiving input and displaying the player attendance information, is accomplished using the web client 56.
In one aspect of the present invention, the user 54 may identify the player 24 through entry of the player's ID card number into the remote device 50A. In one embodiment, the ID card number may be entered manually. In another embodiment, the ID card number may be read from the player's ID card using the card reader 62 or the barcode reader 66 as appropriate.
In another aspect of the present invention, if the player 24 is utilizing one of the devices 12 and has identified themselves to the gaming system by entry of the ID card into the device 12 and/or entered in their PIN number, the user 54 may identify the player 24 by entering a device ID number associated with the respective device 12. As discussed below, the gaming system has associated the ID number of the device 12 with the player 24 while the player 24 is using the device 12. Thus, using the device ID number, the host computer 18 may determine the ID number of the player 24.
In one embodiment, the user 54 navigates to a servlet for requesting player attendance information using the menu layer 80. The menu layer 80 requests the servlet from the host computer 18 from which it is then downloaded to the remote device 50A.
The servlet displays an attendance form which is displayed to the user 54. As discussed above, the user 54 may either enter the player ID card number of the player 24 (manually or reading it from the ID card) or a device ID number associated with a device 12 being used by the player 24. The user 54 enters identification information (in the form of the player ID card number or the device ID number) which is returned to the host computer 18 by the web client 56. The remote network interface 68 receives the identification information, retrieves the player attendance information 350 and returns the player attendance information 350 to the remote device 50A where it is displayed. With specific reference to
When the identification information is entered, the remote network interface 68 determines whether the identification is valid. If valid, the gaming machine information is stored in or retrieved from the database 22 as a function of the identification information. If invalid, an error message is displayed on the remote device. 50A. The gaming machine information includes a device identification number, and the player attendance information is retrieved from the database 22 as a function of the device identification number. The player attendance information 350 includes a player identifier such as a player number, player name and address, and the like. The player attendance information 350 includes a gaming machine identifier which indicates what gaming machines the player 24 has attended on a particular day.
The purpose of the player attendance information 350 is to register and display a patrons attendance at a particular gaming machine or marketing event. Attempting to register a player 24 already registered will generate and display an error.
With specific reference to
With specific reference to
In a first step 364, the attendance form is requested by the user 54 on the remote device 50A.
In a second step 366, the user 54 selects and enters an event or gaming via machine and control proceeds to a fourth step 370.
In a third step 368, an error message is displayed if the user does not enter or select an event and control returns to the first step 364.
In the fourth step 370, if a player ID card number is entered, then the method 362 proceeds to a fifth step 372.
In the fifth step 372, the ID card number is validated.
In a sixth step 374, if system determines if the ID card number is not valid, and control proceeds to the third step 368 where an error message is displayed. If the ID card number is valid, then the method proceeds to a seventh step 376.
In the seventh step 376, if the player 24 is not marked as attending the event, the control proceeds to an eighth step 378.
In the eight step 378, the player's attendance at the gaming machine is registered by the system, and control returns to the first step 264.
I. Remote Surveillance
With reference to
In the illustrated embodiment, interaction with the user 54, including receiving input and displaying the alert information, is accomplished using the web client 56.
In one aspect of the present invention, an alert form displays all active alerts and displays the alerts on the remote device 50A in an alert form as a function of the user role information. The alert form displays the alert and the date and time it occurred. The user 54 may identify the alert and select the alert via an alert button to acknowledge that the user 54 is addressing the alert and will clear the alert after it is addressed. After the user 54 addresses the alert and acknowledges that it is addressed, the database 22 is updated and the alert form is refreshed with updated alert information.
In the illustrated embodiment, the user 54 selects the alert from the alert form and alert details 300 are displayed. The alert details may include, but are not limited to, an alert type for describing the alert and an alert date for describing the date and time that the alert occurred. The alert details 300 may further include a device identifier for describing the gaming device the alert occurred on, a zone name for describing the zone of the gaming floor that the device is located in, and a bank name for describing the bank of the gaming floor that the device is located in. Additional alert details 300 may include a repository identifier for describing the repository the alert occurred on, a document identifier for describing a document created by the alert, an alert value for describing the value of the alert, and an alert point describing the point value of the alert. The alert details 300 may also further include an employee identifier for describing the employee that initiated the alert and an alert message providing a text description of the alert.
In one embodiment, the user 54 navigates to a servlet for requesting alert information using the menu layer 80. The menu layer 80 requests the servlet from the host computer 18 from which it is then downloaded to the remote device 50A.
In one embodiment, the servlet displays the alert form which is displayed to the user 54. As discussed above, the user 54 may select the alert displayed on the alert form to retrieve the alert detail 300 which is returned to the host computer 18 by the web client 56. The remote network interface 68 receives the alert information, retrieves the alert detail 300 and returns the alert detail 300 to the remote device 50A where it is displayed. With specific reference to
With specific reference to
With specific reference to
In a first step 312, the alert information is retrieved as a function of the user role.
In a second step 314, the retrieved alert information is displayed on the remote device 50A.
In a third step 316, the user selects an alert, then the method 310 proceeds to a fourth step 318.
In the fourth step 318, alert detail is retrieved and displayed as a function of the selected alert.
In a fifth step 320, the user selects an alert button for refreshing the alert information stored in the system 10.
In a sixth step 322, the user acknowledges the alert.
In a seventh step 324, the system determines if the alert has already been acknowledged.
In an eighth step 326, if the alert was previously acknowledged, an error message is displayed and the method returns to the first step 312. If the acknowledgement is valid, then the message proceeds to the ninth step 328.
In the ninth step 328, the alert is processed by the host computer 18, notification is sent to other processes in the system, including the database and control returns to the first step 312.
In the third step 316, the user selects the alert button to refresh the alert information displayed at the remote device 50A.
Obviously, many modifications and variations of the present invention are possible in light of the above teachings. The invention may be practiced otherwise than as specifically described within the scope of the appended claims.
J. Patron Point Adjustment
With reference to
In one embodiment, the data includes a point management form (not shown) which is sent from the remote network interface 68 to the remote device 50A. The point management form is fillable with player information by the user 54. The remote device 50 sends the player information to the remote network interface 68. Once the player 24 has been identified, the remote network interface 68 sends a point adjustment request from to the remote device 50A.
With specific reference to
With specific reference to
In a second step 514, if a card number was entered, then the method 510 proceeds to a third step 516. If a card number was not entered, then the method 510 proceeds to a fourth step 516 and an error message is displayed. In the third step 516, the card number is validated. In a fifth step 518, if the card number is valid then the method 510 proceeds to a sixth step 520. In the sixth step 520, approval for the requested transaction is processed. In a seventh step 522 if the user or employee 54 has the necessary rights to adjust the player or patron's points then the method 512 proceeds to an eighth step 524. Otherwise, the method proceeds to the fourth step 516 and an error message is displayed. In the eighth step 524, the points are adjusted and the process returns the first step 512.
K. Comp Point Vouchers
With reference to
In one embodiment of the present invention, the remote network interface 68 exchanges data between the host computer 18 and the remote device 50A. The data includes voucher information to issue a voucher to the player 24 in the player tracking system. The voucher has at least one of an associated product and service. For example, the voucher may be redeemed for the associated product at a related retail store or redeemed for the associated service. Exemplary products includes free dinners and/or drinks.
As discussed below the remote network interface 68 may send a request form to the remote device 50A. The user 54 enters data onto the request form and the remote device sends the data to the remote network interface 68.
With specific reference to
The user 54 may enter the player ID card number associated with the player 24 on the request form. In one embodiment, the player ID card number is entered manually. In another embodiment, the player ID card is read from the player ID card by the ID card reader 62 or the bar code reader 66. After the player has been identified, a list of the vouchers for which the patron has enough comp points to purchase are listed. With specific reference to
With specific reference to
L. Redemption of Printed Vouchers
With reference to
As discussed below in one embodiment, the remote network interface 68 generates and delivers to the remote device 50A a request form. The user 54 may enter a voucher ID number onto the form. By pressing a continue button, the voucher ID may be validated and processed. A status may then be returned to the user 54.
With reference to
With specific reference to
With specific reference to
M. Voucher Information Retrieval
With reference to
In one aspect of the present invention, at least one voucher is assigned to the player 24 in the player tracking system. The voucher has at least one of the good and/or service for which it may be exchanged. The remote network interface 68 may be used for exchanging data between the host computer 18 and the remote device 50A. The data includes voucher information associated with the voucher assigned to the player 24 in the player tracking system.
In one embodiment, the data exchange between the remote device 50A and the remote network interface 68 includes a request form. The remote network interface 68 sends the request form to the remote device 50A. The request form may be used by the user 54 for entering information related to the player. The remote device 50A sends the player information to the remote interface 68. As discussed below, in one embodiment of the present invention, the player information includes the player ID card number. The player ID card number may be entered manually or may be read by the player ID card reader 62 or the bar code reader 66, as appropriate. The player ID card number is relayed to the remote network interface 68. The remote network interface 68 returns a list of outstanding vouchers associated with the player 24. The user 54 may view details related to each voucher. The user 54 may select one of the vouchers to accept, i.e., redeem for the associated service or good.
With specific reference to
With specific reference to
In the sixth step 592, if the player 24 does not have any outstanding vouchers, then the method 580 proceeds to the fourth step 586 and an error message is displayed. Otherwise, the method 580 proceeds to a seventh step 594.
In the seventh step 594, any outstanding vouchers associated with the player 24 are retrieved from the database 22. In an eighth step 596, the retrieved outstanding vouchers are displayed on the remote device 50A. As discussed above, each voucher in the list has an associated detail button (not shown).
In a ninth step 598, if the detail button for one of the listed vouchers was pressed or selected, then the method 580 proceeds to a tenth step 600. Otherwise, the method 580 returns to the first step 592. In the tenth step 600, voucher details for the selected voucher are retrieved from the database 22. In eleventh step 602, the voucher details for the selected voucher are displayed on the remote device 50A. In a twelfth step 604, if the accept button for the selected voucher was pressed or selected, then the method 580 proceeds to a thirteenth step 606. Otherwise, the method 580 returns to the seventh step 594.
In the thirteenth step 606, the selected voucher is marked as being accepted and the method returns to the seventh step 594.
N. System Information
In another aspect of the present invention, the database 22 may store information related to the remote devices 50, including the current state of the remote device 50. As discussed below, this information may be retrieved and displayed on the remote device 50A, for example, for purposes of tech support. In one embodiment, the user 54 selects the servlet or applet from the menu layer 80. The remote network interface 68 produces an HTML form that displays the information related to the remote device 50 to the user 54.
In one embodiment, the data includes information which is associated with a current client being utilized on the remote device 50A. For example, the data may include but is not limited to a TCP/IP address of the current client. An HTTP context of the current client for the current session, an IOP ID of the current client as defined in the database 22 and an IOP name of the current client is defined in the database. IOP or input output point is a designator to represent a point of data input or output such as a dedicated terminal, hand held device, etc., that is distinguished usually by its IP address on the network. The IOP ID and name are used to tie transactions that are generated to a particular entity or device.
The data may also include information related to a current user 54 of the remote device 50. For example, the data may include an employee ID number and/or the employee name.
Obviously, many modifications and variations of the present invention are possible in light of the above teachings. The invention may be practiced otherwise than as specifically described within the scope of the appended claims.
The present application claims priority to U.S. Provisional Application Ser. No. 60/502,179, filed Sep. 11, 2003 and is a continuation-in-part application of U.S. patent application Ser. No. 09/967,571, filed Sep. 28, 2001 now abandoned.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4283709 | Lucero et al. | Aug 1981 | A |
| 4339798 | Hedges et al. | Jul 1982 | A |
| 4636951 | Harlick | Jan 1987 | A |
| 4764666 | Bergeron | Aug 1988 | A |
| 4782468 | Jones et al. | Nov 1988 | A |
| 4948138 | Pease et al. | Aug 1990 | A |
| 5038022 | Lucero | Aug 1991 | A |
| 5116055 | Tracy | May 1992 | A |
| 5133076 | Hawkins et al. | Jul 1992 | A |
| 5249800 | Hilgendorf et al. | Oct 1993 | A |
| 5265874 | Dickinson et al. | Nov 1993 | A |
| 5280909 | Tracy | Jan 1994 | A |
| 5321241 | Craine | Jun 1994 | A |
| 5332076 | Ziegert | Jul 1994 | A |
| 5342047 | Heidel et al. | Aug 1994 | A |
| 5457306 | Lucero | Oct 1995 | A |
| 5470079 | LeStrange et al. | Nov 1995 | A |
| 5472194 | Breeding et al. | Dec 1995 | A |
| 5547202 | Tsumura | Aug 1996 | A |
| 5559312 | Lucero | Sep 1996 | A |
| 5564700 | Celona | Oct 1996 | A |
| 5586937 | Menashe | Dec 1996 | A |
| 5598572 | Tanikoshi et al. | Jan 1997 | A |
| 5611730 | Weiss | Mar 1997 | A |
| 5613912 | Slater | Mar 1997 | A |
| 5655961 | Acres et al. | Aug 1997 | A |
| 5655966 | Werdin, Jr. et al. | Aug 1997 | A |
| 5674128 | Holch et al. | Oct 1997 | A |
| 5702304 | Acres et al. | Dec 1997 | A |
| 5707287 | McCrea, Jr. | Jan 1998 | A |
| 5735525 | McCrea, Jr. | Apr 1998 | A |
| 5741183 | Acres et al. | Apr 1998 | A |
| 5752882 | Acres et al. | May 1998 | A |
| 5762552 | Vuong et al. | Jun 1998 | A |
| 5766076 | Pease et al. | Jun 1998 | A |
| 5770533 | Franchi | Jun 1998 | A |
| 5797796 | Dickinson | Aug 1998 | A |
| 5800268 | Molnick | Sep 1998 | A |
| 5800269 | Holch et al. | Sep 1998 | A |
| 5804803 | Cragun et al. | Sep 1998 | A |
| 5811772 | Lucero | Sep 1998 | A |
| 5819901 | Filiberti | Oct 1998 | A |
| 5820459 | Acres et al. | Oct 1998 | A |
| 5833540 | Miodunski et al. | Nov 1998 | A |
| 5836817 | Acres et al. | Nov 1998 | A |
| 5851149 | Xidos | Dec 1998 | A |
| 5855515 | Pease et al. | Jan 1999 | A |
| 5867688 | Simmon et al. | Feb 1999 | A |
| 5876284 | Acres et al. | Mar 1999 | A |
| 5885158 | Torango et al. | Mar 1999 | A |
| 5902983 | Crevelt et al. | May 1999 | A |
| 5911626 | McCrea, Jr. | Jun 1999 | A |
| 5919091 | Bell et al. | Jul 1999 | A |
| 5935004 | Tarr et al. | Aug 1999 | A |
| 5944608 | Reed et al. | Aug 1999 | A |
| 5952640 | Lucero | Sep 1999 | A |
| 5959277 | Lucero | Sep 1999 | A |
| 5967896 | Jorasch et al. | Oct 1999 | A |
| 5984786 | Ehrman | Nov 1999 | A |
| 6001016 | Walker et al. | Dec 1999 | A |
| 6012984 | Roseman | Jan 2000 | A |
| 6019283 | Lucero | Feb 2000 | A |
| 6024641 | Sarno | Feb 2000 | A |
| 6039648 | Guinn et al. | Mar 2000 | A |
| 6048269 | Burns et al. | Apr 2000 | A |
| 6068552 | Walker et al. | May 2000 | A |
| 6071190 | Weiss et al. | Jun 2000 | A |
| 6077162 | Weiss | Jun 2000 | A |
| 6080062 | Olson | Jun 2000 | A |
| 6089982 | Holch et al. | Jul 2000 | A |
| 6093103 | McCrea, Jr. | Jul 2000 | A |
| 6110043 | Olsen | Aug 2000 | A |
| 6110044 | Stern | Aug 2000 | A |
| 6113495 | Walker et al. | Sep 2000 | A |
| 6117011 | Lvov | Sep 2000 | A |
| 6117012 | McCrea, Jr. | Sep 2000 | A |
| 6126546 | Reed et al. | Oct 2000 | A |
| 6146273 | Olsen | Nov 2000 | A |
| 6154738 | Call | Nov 2000 | A |
| 6162122 | Acres et al. | Dec 2000 | A |
| 6183362 | Boushy | Feb 2001 | B1 |
| 6183366 | Goldberg et al. | Feb 2001 | B1 |
| 6203010 | Jorasch et al. | Mar 2001 | B1 |
| 6206782 | Walker et al. | Mar 2001 | B1 |
| 6210275 | Olsen | Apr 2001 | B1 |
| 6210277 | Stefan | Apr 2001 | B1 |
| 6240444 | Fin et al. | May 2001 | B1 |
| 6267671 | Hogan | Jul 2001 | B1 |
| 6302793 | Fertitta, III et al. | Oct 2001 | B1 |
| 6435968 | Torango | Aug 2002 | B1 |
| 6582310 | Walker et al. | Jun 2003 | B1 |
| 6592460 | Torango | Jul 2003 | B2 |
| 6633914 | Baych et al. | Oct 2003 | B1 |
| 6645077 | Rowe | Nov 2003 | B2 |
| 6650346 | Jaeger et al. | Nov 2003 | B1 |
| 6681984 | Brunner | Jan 2004 | B2 |
| 6682421 | Rowe et al. | Jan 2004 | B1 |
| 6712695 | Mothwurf et al. | Mar 2004 | B2 |
| 6712698 | Paulsen et al. | Mar 2004 | B2 |
| 6763998 | Miodunski et al. | Jul 2004 | B1 |
| 6800029 | Rowe et al. | Oct 2004 | B2 |
| 6830515 | Rowe | Dec 2004 | B2 |
| 6962531 | Pace et al. | Nov 2005 | B2 |
| 20010003100 | Yacenda | Jun 2001 | A1 |
| 20010029528 | Coutts et al. | Oct 2001 | A1 |
| 20010036857 | Mothwurf et al. | Nov 2001 | A1 |
| 20010036858 | McNutt et al. | Nov 2001 | A1 |
| 20010056386 | O'Halloran et al. | Dec 2001 | A1 |
| 20020002075 | Rowe | Jan 2002 | A1 |
| 20020042297 | Torango | Apr 2002 | A1 |
| 20020058550 | Pace et al. | May 2002 | A1 |
| 20020094869 | Harkham | Jul 2002 | A1 |
| 20020107715 | Pace et al. | Aug 2002 | A1 |
| 20020142825 | Lark et al. | Oct 2002 | A1 |
| 20020142846 | Paulsen | Oct 2002 | A1 |
| 20020155887 | Criss-Puszkiewicz et al. | Oct 2002 | A1 |
| 20020165023 | Brosnan et al. | Nov 2002 | A1 |
| 20020173354 | Winans et al. | Nov 2002 | A1 |
| 20020177483 | Cannon | Nov 2002 | A1 |
| 20030023516 | Sharrow et al. | Jan 2003 | A1 |
| 20030028480 | Rowe | Feb 2003 | A1 |
| 20030054868 | Paulsent et al. | Mar 2003 | A1 |
| 20030054878 | Benoy et al. | Mar 2003 | A1 |
| 20030054881 | Hedrick et al. | Mar 2003 | A1 |
| 20030055948 | Wang | Mar 2003 | A1 |
| 20030057269 | Brunner | Mar 2003 | A1 |
| 20030064805 | Wells | Apr 2003 | A1 |
| 20030092477 | Luciano, Jr. et al. | May 2003 | A1 |
| 20040002386 | Wolfe et al. | Jan 2004 | A1 |
| 20040127277 | Walker et al. | Jul 2004 | A1 |
| 20040209692 | Schober et al. | Oct 2004 | A1 |
| 20040229683 | Mothwurf et al. | Nov 2004 | A1 |
| 20050070356 | Mothwurf et al. | Mar 2005 | A1 |
| 20050150946 | Miodunski et al. | Jul 2005 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20040132531 A1 | Jul 2004 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60502179 | Sep 2003 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 09967571 | Sep 2001 | US |
| Child | 10661390 | US |
