U.S. patent application number 10/661140 was filed with the patent office on 2004-05-13 for system and method for retrieving player attendance information in a gaming system.
Invention is credited to George, Jeffrey, Huang, Zhiguo, Huber, Doug, Pochin, John-Paul.
Application Number | 20040092305 10/661140 |
Document ID | / |
Family ID | 25512990 |
Filed Date | 2004-05-13 |
United States Patent
Application |
20040092305 |
Kind Code |
A1 |
George, Jeffrey ; et
al. |
May 13, 2004 |
System and method for retrieving player attendance information in a
gaming system
Abstract
A remote system and method retrieves player attendance
information in a gaming system. A remote system for use with the
gaming system, the gaming system having at least one gaming machine
playable by a player and having gaming machine information
associated with the at least one gaming machine. A host computer is
coupled to the at least one gaming machine by a network. The host
computer includes a database for maintaining the player attendance
information. The remote system includes a remote device for
receiving identification information input by a user, and a remote
network interface coupled to the remote device for receiving the
identification information from the remote device. The remote
network interface sends gaming machine information from the gaming
machine to the database for storing the gaming machine information
as a function of the identification information, and returns the
player attendance information to the remote device.
Inventors: |
George, Jeffrey; (North Las
Vegas, NV) ; Huang, Zhiguo; (Henderson, NV) ;
Huber, Doug; (Louisville, KY) ; Pochin,
John-Paul; (Christchurch, NZ) |
Correspondence
Address: |
HOWARD & HOWARD ATTORNEYS, P.C.
THE PINEHURST OFFICE CENTER, SUITE #101
39400 WOODWARD AVENUE
BLOOMFIELD HILLS
MI
48304-5151
US
|
Family ID: |
25512990 |
Appl. No.: |
10/661140 |
Filed: |
September 12, 2003 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
10661140 |
Sep 12, 2003 |
|
|
|
09967571 |
Sep 28, 2001 |
|
|
|
Current U.S.
Class: |
463/29 ;
463/42 |
Current CPC
Class: |
G07F 17/3239 20130101;
G07F 17/3227 20130101; G07F 17/3237 20130101; G07F 17/32 20130101;
G07F 17/3234 20130101 |
Class at
Publication: |
463/029 ;
463/042 |
International
Class: |
A63F 013/00; A63F
009/24 |
Claims
What is claimed is:
1. A remote system for use with a gaming system, the gaming system
having at least one gaming machine playable by a player and having
gaming machine information associated with the at least one gaming
machine, a host computer coupled to the at least one gaming machine
by a network, the host computer including a database for
maintaining the player attendance information, the remote system
comprising: a remote device for receiving identification
information input by a user; and, a remote network interface
coupled to the remote device for receiving the identification
information from the remote device, sending gaming machine
information from the gaming machine to the database for storing the
gaming machine information as a function of the identification
information, and returning the player attendance information to the
remote device.
2. A remote system, as set forth in claim 1, wherein the remote
device is coupled to the remote network interface by a wireless
connection.
3. A remote system, as set forth in claim 2, wherein the wireless
connection uses an IEEE 802.11 standard.
4. A remote system, as set forth in claim 3, wherein the wireless
connection is IEEE 802.11b.
5. A remote system, as set forth in claim 3, wherein the wireless
connection is IEEE 802.11g.
6. A remote system, as set forth in claim 1, the remote device
having a processor and a web client for interaction with the
user.
7. A remote system, as set forth in claim 6, the web client for
acquiring input from the user and formatting and presenting data to
the user.
8. A remote system, as set forth in claim 1, the remote network
interface for sending an attendance form to the remote device.
9. A remote system, as set forth in claim 8, the attendance form
being fillable with the identification information by the user.
10. A remote system, as set forth in claim 9, the remote device
having a processor and a web client for interaction with a user,
the attendance form being accessible through the web client.
11. A remote system, as set forth in claim 10, the attendance form
accepting the identification information.
12. A remote system, as set forth in claim 11, the identification
information including an identification card number.
13. A remote system, as set forth in claim 11, the identification
information including an identification card number, the remote
network interface for receiving the identification card number and
determining if the identification card number is valid.
14. A remote system, as set forth in claim 13, the remote network
interface for sending the gaming machine information to the
database for storing as a function of the identification
information if the identification card number is valid.
15. A remote system as set forth in claim 13, further comprising a
card reader connected to the remote device, the card reader for
reading the identification card number from a player identification
card.
16. A remote system, as set forth in claim 11, remote network
interface for determining if the identification information is
valid, the gaming machine information including a device
identification number associated with the gaming machine if the
identification information is valid.
17. A remote system, as set forth in claim 16, the remote network
interface for receiving the device identification number and
retrieving the player attendance information from the database as a
function of the device identification number.
18. A remote system, as set forth in claim 1, the remote network
interface coupled to the database for retrieving and storing data
therein.
19. A remote system, as set forth in claim 18, the database for
storing data in database tables.
20. A remote system, as set forth in claim 19, further comprising a
plurality of first data object coupled to the database tables for
retrieving and storing data in the database tables.
21. A remote system, as set forth in claim 20, further comprising
at least one second data object coupled to the first data objects
for assembling multiple first data objects into a third data
object.
22. A remote system, as set forth in claim 21, the third object
coupled to the remote network interface for receiving queries from
the remote network interface, retrieving responsive data from the
database, formatting the responsive data and returning the
responsive data to the remote network interface.
23. A remote system, as set forth in claim 22, the remote network
interface for receiving the responsive data and transmitting the
responsive data to the remote device.
24. A remote system, as set forth in claim 23, the remote device
having a processor and a web client for interaction with a user,
the remote network interface for formatting the responsive data
into a hyper text mark-up language response for display by the web
client.
25. A remote system, as set forth in claim 6, the web client
including a plurality of servlets for providing functionality to a
user.
26. A remote system, as set forth in claim 25, the web client
including a login layer for identifying the user.
27. A remote system, as set forth in claim 26, the web client
including a menu layer for allowing the user to navigate to and
access the servlets.
28. A remote system, as set forth in claim 27, the user having an
assigned type, the menu layer for allowing accessing to servlets
and restricting access to servlets as a function of the assigned
type.
29. A remote system, as set forth in claim 17, wherein the player
attendance information includes a player identifier.
30. A remote system, as set forth in claim 17, wherein the player
attendance information includes a gaming machine identifier.
31. A remote system, as set forth in claim 17, the remote network
interface for instructing the remote device to display the player
attendance information.
32. A remote system, as set forth in claim 16, the remote network
interface for instructing the remote display to display an error
message if the identification information is invalid.
33. A method using a remote device for retrieving player attendance
information related to a player for use with a gaming system, the
gaming system including at least one gaming machine playable by the
player and a host computer coupled to the at least one gaming
machine by a network, the host computer including a database for
maintaining the player attendance information, the method including
the steps of: receiving identification information at the remote
device; receiving the identification information from the remote
device at the host computer; sending gaming machine information
from the gaming machine to the database or storing the gaming
machine information as a function of the identification
information; and, returning the player attendance information to
the remote device.
34. A method, as set forth in claim 33, the gaming system having a
remote network interface for coupling the remote device to the host
computer, the method including the step of providing a wireless
connection between the remote device and the remote network
interface.
35. A method, as set forth in claim 34, wherein the wireless
connection uses an IEEE 802.11 standard.
36. A method, as set forth in claim 35, wherein the wireless
connection is IEEE 802.11b.
37. A method, as set forth in claim 35, wherein the wireless
connection is IEEE 802.11g.
38. A method, as set forth in claim 33, the remote device having a
processor and a web client for interaction with a user, the method
including the steps of: acquiring input via the web client from the
user; and, formatting and presenting data to the user.
39. A method, as set forth in claim 33, the method including the
step of sending an attendance form by the remote network interface
to the remote device.
40. A method, as set forth in claim 39, the attendance form being
fillable with the identification information by a user.
41. A method, as set forth in claim 40, the attendance form being
accessible through a web client.
42. A method, as set forth in claim 41, the method including the
step of accepting by the attendance form the identification
information.
43. A method, as set forth in claim 42, the identification
information including an identification card number.
44. A method, as set forth in claim 42, the identification
information including an identification card number, the method
including the steps of receiving the identification card number by
the remote network interface and determining if the identification
card number is valid.
45. A method, as set forth in claim 44, the method including the
step of sending the gaming machine information to the database for
storing as a function of the identification information if the
identification card number is valid.
46. A method as set forth in claim 44, the remote device having a
card reader, the method including the step of reading the
identification card number from a player identification card by the
card reader.
47. A method, as set forth in claim 44, the identification
information including a device identification number associated
with the gaming machine.
48. A method, as set forth in claim 47, including the steps of
receiving the device identification number at the remote network
interface and retrieving player attendance information from the
database as a function of the device identification number, the
player attendance information associated with the player playing
the gaming machine.
49. A method, as set forth in claim 33, the remote network
interface coupled to the database for retrieving and storing data
therein.
50. A method, as set forth in claim 49, the database for storing
data in database tables.
51. A method, as set forth in claim 50, including the step of
providing a plurality of first data object coupled to the database
tables for retrieving and storing data in the database tables.
52. A method, as set forth in claim 51, including the step of
providing at least one second data object coupled to the first data
objects for assembling multiple first data objects into a third
data object.
53. A method, as set forth in claim 52, the third object coupled to
the remote network interface, the method including the step of
receiving queries from the remote network interface at the third
object, retrieving responsive data from the database, formatting
the responsive data and returning the responsive data to the remote
network interface.
54. A method, as set forth in claim 53, including the steps of
receiving the responsive data and transmitting the responsive data
to the remote device.
55. A method, as set forth in claim 54, the remote device having a
processor and a web client for interaction with a user, the method
including the step of formatting the responsive data, at the remote
network interface, into a hyper text mark-up language response for
display by the web client.
56. A method, as set forth in claim 38 the web client including a
plurality of servlets for providing functionality to a user.
57. A method, as set forth in claim 56, the web client including a
login layer for identifying the user.
58. A method, as set forth in claim 57, the web client including a
menu layer for allowing the user to navigate to and access the
servlets.
59. A method, as set forth in claim 58, the user having an assigned
type, the menu layer for allowing accessing to servlets and
restricting access to servlets as a function of the assigned
type.
60. A method, as set forth in claim 45, the method including the
step of retrieving the player attendance information from the
database if the identification card number is valid.
61. A method, as set forth in claim 33, wherein the player
information includes a player name.
62. A method, as set forth in claim 33, wherein the player
attendance information includes a player identifier.
63. A method, as set forth in claim 33, wherein the player
attendance information includes a gaming machine identifier.
64. A method, as set forth in claim 33, the method including the
step of instructing the remote device to display the player
attendance information.
65. A method, as set forth in claim 32, the including the step of
instructing the remote display to display an error message if the
identification information is invalid.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] The present application claims priority to U.S. Provisional
Application Serial No.(not assigned), filed Sep. 11, 2003 (Attorney
Docket No: 60518,169) and is a continuation-in-part application of
U.S. patent application Ser. No. 09/967,571, filed Sep. 28,
2001.
FIELD OF THE INVENTION
[0002] The present invention relates generally to gaming machines,
and more particularly, to a system and method for remotely
accessing the player tracking system.
BACKGROUND OF THE INVENTION
[0003] 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.
[0004] 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.
[0005] 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.
[0006] 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.
[0007] The present invention is aimed at one or more of the
problems as set forth above.
SUMMARY OF THE INVENTION
[0008] In one aspect of the present invention, a remote system for
use with a gaming system, is provided. The remote system and method
retrieves player attendance information in a gaming system. A
remote system for use with the gaming system, the gaming system
having at least one gaming machine playable by a player and having
gaming machine information associated with the at least one gaming
machine. A host computer is coupled to the at least one gaming
machine by a network. The host computer includes a database for
maintaining the player attendance information. The remote system
includes a remote device for receiving identification information
input by a user, and a remote network interface coupled to the
remote device for receiving the identification information from the
remote device. The remote network interface sends gaming machine
information from the gaming machine to the database for storing the
gaming machine information as a function of the identification
information, and returns the player attendance information
[0009] In another aspect of the present invention, a method using a
remote device for retrieving player attendance information related
to a player in a gaming system, is provided. The gaming system
includes at least one gaming machine playable by the player and a
host computer coupled to the at least one gaming machine by a
network. The host computer includes a database for maintaining the
player attendance information. The method includes the steps of
receiving identification information at the remote device,
receiving the identification information from the remote device at
the host computer, sending gaming machine information from the
gaming machine to the database or storing the gaming machine
information as a function of the identification information and
returning the player attendance information to the remote
device.
BRIEF DESCRIPTION OF THE DRAWINGS
[0010] 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:
[0011] FIG. 1 is a block diagram of a remote system for use with a
gaming system, according to an embodiment of the present
invention;
[0012] FIG. 2 is block diagram of an gaming machine and a remote
device, according to an embodiment of the present invention;
[0013] FIG. 3 is a more detailed block diagram of the remote device
of FIG. 2 and a computer program application, according to an
embodiment of the present invention;
[0014] FIG. 4 is a block diagram of a web client operating on the
remote device of FIG. 2, according to an embodiment of the present
invention;
[0015] FIG. 5A is a first flow diagram of a method for enrolling a
player in a player tracking system, according to an embodiment of
the present invention;
[0016] FIG. 5B is a second flow diagram of a method for enrolling a
player in a player tracking system, according to a second
embodiment of the present invention;
[0017] FIG. 6 is a diagrammatic illustration of a remote player
signup form according to an embodiment of the present
invention;
[0018] FIG. 7A is a first flow diagram of a method for remotely
accessing player information, according to an embodiment of the
present invention;
[0019] FIG. 7B is a second flow diagram of a method for remotely
accessing player information, according to a second embodiment of
the present invention;
[0020] FIG. 8 is a diagrammatic illustration of a remote player
information screen, according to an embodiment of the present
invention;
[0021] FIG. 9A is a first flow diagram of a method for remotely
accessing information related to a device, according to an
embodiment of the present invention;
[0022] FIG. 9B is a second flow diagram of a method for remotely
accessing information related to a device, according to a second
embodiment of the present invention;
[0023] FIG. 10 is a diagrammatic illustration of a remote asset
information screen, according to an embodiment of the present
invention;
[0024] FIG. 11A is a first flow diagram of a method for remotely
processing jackpot tickets, according to an embodiment of the
present invention;
[0025] FIG. 11B is a second flow diagram of a method for remotely
processing jackpot tickets, according to a second embodiment of the
present invention;
[0026] FIG. 12 is a diagrammatic illustration of a cash ticket
information screen, according to an embodiment of the present
invention;
[0027] FIG. 13A is a first flow diagram of a method for remotely
processing jackpot tickets, according to an embodiment of the
present invention;
[0028] FIG. 13B is a second flow diagram of a method for remotely
processing jackpot tickets, according to a second embodiment of the
present invention;
[0029] FIG. 14A is a diagrammatic illustration of a jackpot
information screen, according to an embodiment of the present
invention;
[0030] FIG. 14B is a diagrammatic illustration of a fill
information screen, according to an embodiment of the present
invention;
[0031] FIG. 15A is a first flow diagram of a method for remotely
processing hopper fills, according to an embodiment of the present
invention;
[0032] FIG. 15B is a second flow diagram of a method for remotely
processing hopper fills, according to a second embodiment of the
present invention;
[0033] FIG. 16A is a diagrammatic illustration of a hopper fill
information screen, according to an embodiment of the present
invention;
[0034] FIG. 16B is a diagrammatic illustration of a fill
information screen according to an embodiment of the present
invention;
[0035] FIG. 17A is a first flow diagram of a method for remotely
providing a table rating interface, according to an embodiment of
the present invention;
[0036] FIG. 17B is a second flow diagram of a method for remotely
providing a table rating interface, according to a second
embodiment of the present invention;
[0037] FIG. 18A is a diagrammatic illustration of an open table
rating screen, according to an embodiment of the present
invention;
[0038] FIG. 19A is a first flow diagram of a method for remotely
providing an attendance interface, according to an embodiment of
the present invention;
[0039] FIG. 19B is a second flow diagram of a method for remotely
providing an attendance interface, according to a second embodiment
of the present invention;
[0040] FIG. 20 is a diagrammatic illustration of a player
attendance information screen, according to an embodiment of the
present invention;
[0041] FIG. 21A is a first flow diagram of a method for remotely
providing a surveillance interface, according to an embodiment of
the present invention;
[0042] FIG. 21B is a second flow diagram of a method for remotely
providing a surveillance interface, according to a second
embodiment of the present invention;
[0043] FIG. 22 is a diagrammatic illustration of an alert
information screen, according to an embodiment of the present
invention;
[0044] FIG. 23A is a flow diagram of a first method for adjusting
points assigned to a player in a player tracking system, according
to an embodiment of the present invention;
[0045] FIG. 23B is flow diagram of a second method for adjusting
points assigned to a player in a player tracking system, according
to another embodiment of the present invention;
[0046] FIG. 24 is a diagrammatical illustration of a point
adjustment request form, according to an embodiment of the present
invention;
[0047] FIG. 25A is a flow diagram of a method for issuing vouchers
to a player, according to an embodiment of the present
invention;
[0048] FIG. 25B is a flow diagram of a second method for issuing
vouchers to a player, according to another embodiment of the
present invention;
[0049] FIG. 26 is a diagrammatic illustration of a voucher
information screen, according to an embodiment of the present
invention;
[0050] FIG. 27A is a flow diagram of a method for redeeming printed
vouchers using a remote device, according to an embodiment of the
present invention;
[0051] FIG. 27B is a flow diagram of a second method for redeeming
printed vouchers using a remote device, according to an embodiment
of the present invention;
[0052] FIG. 28 is a diagrammatic illustration of a voucher
information form, according to an embodiment of the present
invention;
[0053] FIG. 29A is a first flow diagram of a method for displaying
a list of outstanding vouchers for a selected player, according to
a first embodiment of the present invention;
[0054] FIG. 29B is a second flow diagram of a method for displaying
a list of outstanding vouchers for a selected patron, according to
a second embodiment of the present invention; and
[0055] FIG. 30 is a diagrammatic illustration of a voucher
information dialogue, according to an embodiment of the present
invention.
DETAILED DESCRIPTION OF INVENTION
I. Overview
[0056] 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.
[0057] 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
[0058] 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 FIG. 1.
The entertainment and monitoring system 14 may include may
additional functions such as, real-time multi-site, slot
accounting, player tracking, cage credit and vault, sports book
data collection, Point of Sale (POS) accounting, keno accounting,
bingo accounting, and table game accounting, a wide area
progressive jackpot, and electronic funds transfer (EFT). Two
exemplary systems are disclosed in U.S. patent application Ser. No.
09/967,571, filed Sep. 28, 2001, and U.S. Provisional Patent
Application Serial (Not Assigned), filed Sep. 11, 2003 (Attorney
Docket No. 60,518-169), both of which are hereby incorporated by
reference.
[0059] 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.
[0060] 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).
[0061] 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).
[0062] 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.
[0063] With reference to FIG. 2, a block diagram of a suitable
electronic gaming machine 13C is shown.
[0064] 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.
[0065] 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.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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.
[0070] 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
[0071] Returning to FIG. 1, the present invention provides a remote
system 48 for use with the gaming system 14. The remote system 48
provides access to various features or functions of the gaming
system 14 by one or more remote devices 50.
[0072] 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.
[0073] 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.
[0074] 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.
[0075] 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.
[0076] 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.
[0077] 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 FIG. 3 in one embodiment of the present invention, the
remote device 50A includes a processor 58, a memory 60 for storing
applications and data, and a display 64. The display 64 may be a
touchscreen display. The remote device 50A may also include a bar
code reader 66. The bar code reader 66 may be used to read a player
ID card number from the ID card or to read a device ID number from
a device 12 (see below). One such mobile computer is available from
Symbol Technologies, Inc. of Holtsville, N.Y. as model number SPT
1800.
[0078] Additionally or alternatively, the remote device 50A may
include an ID card reader 62 capable of reading magnetic stripe ID
cards.
[0079] In another embodiment, the remote devices 50 are desktop,
laptop, notebook, and/or sub-notebook computers.
[0080] Returning to FIG. 3, in one embodiment of the present
invention, the remote device 50A includes a web client 56 which is
stored in the memory 60 and run on the processor 58. The web client
56 is connected to the computer program application 20 running on
the host computer 18 through the network link 52.
[0081] 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.
[0082] As shown in FIG. 3, the computer program application 20
implements a remote network interface 66. The remote network
interface 68 couples the web client 56 with the database 22. In one
embodiment, the remote network interface 68 obtains data from the
database 22, formats the data, e.g., into an HTML response, and
returns the formatted data to the web client 56.
[0083] 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.
[0084] As shown, in FIG. 3, the data objects 70 include a plurality
of first data object (DBOBJECTS) 76, at least one second data
object (VDBOBJECTS) 74, and a third data object (BUSINESS OBJECT)
72.
[0085] 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.
[0086] 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.
[0087] 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.
[0088] With reference to FIG. 4 in one embodiment, the web client
56 is written in HTML. In the illustrated embodiment, the web
client 56 includes a form layer 78, a menu layer 80, a login layer
82, and a servlet layer 84.
[0089] 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.
[0090] 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).
[0091] The form and servlet layers 78, 84 provides common
functionality for the servlets.
A. Remote Player or Patron Signup
[0092] With reference to FIGS. 5A, 5B, and 6, the remote system 48
allows the user 54, such as a slot floor employee or patron host to
quickly and remotely enroll a player or patron in the player
tracking system. The user 54 will generally have a number of
unassigned player ID cards (not shown). The user 54 may be
approached by a player 24 who requests to enroll or may approach
the player 24 and ask if they would want to enroll.
[0093] 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.
[0094] 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.
[0095] 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.
[0096] 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.
[0097] With specific reference to FIG. 5A, a first method 88 for
enrolling the player 24 in the player tracking system using the
remote device 50A, according to a first embodiment of the present
invention is shown. In a first step 90, a fillable signup form is
sent to the remote device 50A. In a second step 92, the player
information (or enrollment data) is entered on the signup form via
the remote device 50A.
[0098] With specific reference to FIG. 5B, a second method 94 for
enrolling the player 24 in the player tracking system using the
remote device 50A, according to a second embodiment of the present
invention is shown.
[0099] 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.
[0100] 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.
[0101] 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.
[0102] 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.
[0103] An exemplary signup form 110, displayed on the remote device
50A by the web client 56 is shown in FIG. 6. As discussed above, in
one embodiment the only information required is the player's name
and a PIN number. The exemplary signup form 110 includes an entry
box for the player's first, middle, and last names 112, 114, 116
and a PIN entry box 118. After the required information has been
entered, the user 54 selects a save player button 120 to send the
data to the host computer 18.
[0104] 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.
[0105] 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
[0106] With reference to FIGS. 7A, 7B, and 8, the remote system 48
allows the user 54, such as a slot floor employee or patron host to
quickly and remotely request and receive player information related
to a specific player 24. This may be done prior to approaching the
player 24 who is using a specification gaming machine 13 or after
the user 54 has been approached by the player 24.
[0107] In the illustrated embodiment, interaction with the user 54,
including receiving input and displaying the player information, is
accomplished using the web client 56.
[0108] 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.
[0109] 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.
[0110] 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.
[0111] 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.
[0112] With specific reference to FIG. 7A, a first method 124 for
remotely requesting information relating to a player 24 is
provided. In a first step 126, identification information is
received at the remote device. In a second step 128, the
identification information is received at the host computer. In a
third step 130, the player information is retrieved from the
database 22 as a function of the identification information.
[0113] With specific reference to FIG. 7B, a second method 132 for
remotely requesting player information using the remote device 50A
is shown, according to a second embodiment of the present
invention.
[0114] 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.
[0115] 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.
[0116] 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.
[0117] 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.
[0118] With specific reference to FIG. 8, in one embodiment the
returned player information is displayed on the remote device 50A
in a player information screen 152. In the illustrated embodiment,
the player information may include, but is not limited to, a player
name, a player address, a patron host name, at least one
anniversary date, e.g., birthday, wedding anniversary, sign-up
date, any meters tracked by the player tracking system, such as
bonus points (incentive points or credits), jackpots, coin-out,
coin-in, and win/(loss).
C. Remote Device Information
[0119] With reference to FIGS. 9A, 9B and 10, the remote system 48
allows the user 54, such as a slot floor employee or a slot
technician, to quickly remotely request and receive asset or device
information related to an gaming device 12.
[0120] In the illustrated embodiment, interaction with the user 54,
including receiving input and displaying the asset information is
accomplished using the web client 56.
[0121] 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.
[0122] 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.
[0123] 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.
[0124] With specific reference to FIG. 9A, a first method 154 for
remotely requesting information related to a specific gaming device
12 is provided. In a first step 156, identification information is
received at the remote device 50A. In a second step 158, the
identification information is received at the host computer 18. In
a third step 160, the device information is retrieved from the
database 22 as a function of the identification information.
[0125] With specification reference to FIG. 9B, a second method 162
is for remotely requesting device information using the remote
device 50A is shown, according to an embodiment of the present
invention.
[0126] 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.
[0127] 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.
[0128] With specific reference to FIG. 10, in one embodiment the
returned asset information is displayed on the remote device 50A in
a remote asset information screen 178. In the illustrated
embodiment, the asset information may include, but is not limited
to, an asset number, a device number, a denomination (the base
denomination the device accepts), a manufacturer, a model, a master
prom identifier, a game prom identifier, an online MAC address, an
online TCP/IP address, a date on floor, and any or all available
system meters, such as, coin in, coin out, games player, and
jackpots.
D. Remote Cash Ticket Processing
[0129] 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).
[0130] With reference to FIGS. 11A, 11B and 12, the remote system
48 allows the user 54, such as a slot floor employee or patron host
to quickly and remotely process a cash ticket issued by a
particular gaming machine 13. The cash ticket issued by the gaming
machine 13 includes cash ticket information such as a cash ticket
id and a value printed on the cash ticket. The user 54 may be
approached by a player 24 who requests to cash out a cash ticket
and receive the value of the cash ticket.
[0131] 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.
[0132] 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.
[0133] 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.
[0134] 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.
[0135] 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.
[0136] 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 FIG. 12, in one embodiment
the returned cash ticket information is displayed on the remote
device 50A in a cash ticket information screen 196.
[0137] 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.
[0138] With specific reference to FIG. 11A, a first method 170 for
processing a cash ticket using the remote device 50A, according to
a first embodiment of the present invention is shown. In a first
step 172, a fillable cash ticket form is sent to the remote device
50A. In a second step 174, the cash ticket information is entered
on the cash ticket form via the remote device 50A.
[0139] With specific reference to FIG. 11B, a second method 176 for
processing the cash ticket using the remote device 50A, according
to a second embodiment of the present invention is shown.
[0140] 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.
[0141] 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
[0142] 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.
[0143] 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
[0144] With reference to FIGS. 13A, 13B and 14A, the remote system
48 allows the user 54, such as a slot floor employee, to quickly
and remotely process a jackpot issued by a particular gaming
machine 13. The jackpot issued by the gaming machine 13 has
associated jackpot information such as a jackpot id and a value of
the jackpot.
[0145] 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.
[0146] 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.
[0147] 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.
[0148] 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.
[0149] 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.
[0150] 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.
[0151] 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.
[0152] 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.
[0153] 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 FIG. 14A, in one embodiment the returned
jackpot information is displayed on the remote device 50A in a
jackpot information screen 238. With reference to FIG. 14B, in
another embodiment, the returned fill information is displayed on
the remote device 50A in a fill information screen 240.
[0154] 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.
[0155] 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.
[0156] With specific reference to FIG. 13A, a first method 202 for
processing a jackpot using the remote device 50A, according to a
first embodiment of the present invention is shown. In a first step
204, a selectable jackpot form is sent to the remote device 50A. In
a second step 206, the jackpot information is entered on the
jackpot form via the remote device 50A.
[0157] With specific reference to FIG. 13B, in another aspect of
the present invention, a method 208 for displaying or processing
jackpots is shown. In a first step 210, all pending jackpots are
displayed. In one embodiment, the list of pending jackpots includes
at least a jackpot id and a jackpot status. In a second step 214,
if the user 54 selects jackpot id of a jackpot, the method 208
proceeds to a third step 222. If the user 54 selects the jackpot
status, the method 208 proceeds to a fourth step 236. In the third
step 222, jackpot details are displayed on the remote device 50A.
In the fourth step 236, the selected jackpot is processed by the
user 54.
F. Remote Hopper Fill Ticket Processing
[0158] With reference to FIGS. 15A, 15B, 16A and 16B, the remote
system 48 allows the user 54, such as a slot floor employee to
quickly and remotely process a hopper fills in a particular gaming
machine 13, i.e., insert credits or coins into the game machine's
hopper to be dispensed to the player 24 when a jackpot has been
won, when the game machine has run out or is low on credits. The
number of credits remaining in the hopper (not shown) are tracked
by the host computer 18 (or game machine 13 and relayed to the host
computer)which issues an alert when the number of credits remaining
reaches a certain amount so that the hopper may be restocked with
credits such as coins, tokens, paper money, or the like.
[0159] 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.
[0160] 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.
[0161] 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.
[0162] 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.
[0163] 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.
[0164] 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.
[0165] 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 FIG. 16A, in one embodiment the returned
hopper fill information is displayed on the remote device 50A in a
hopper fill information screen 288. With reference to FIG. 16B, in
another embodiment, the returned fill information is displayed on
the remote device 50A in a fill information screen 290.
[0166] 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.
[0167] 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.
[0168] With specific reference to FIG. 15A, a first method 252 for
processing a hopper fill using the remote device 50A, according to
a first embodiment of the present invention is shown. In a first
step 254, a selectable hopper fill form is sent to the remote
device 50A. In a second step 256, the hopper fill information is
entered on the hopper fill form via the remote device 50A.
[0169] With specific reference to FIG. 15B, a second method 258 for
processing the hopper fill using the remote device 50A, according
to a second embodiment of the present invention is shown.
[0170] 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.
[0171] 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.
[0172] 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.
[0173] After the hopper is filled with credits by the user 54, the
remote display displays a credit filled message.
[0174] 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.
[0175] 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
[0176] With reference to FIGS. 17A, 17B, and 18, the remote system
48 allows the user 54, such as a slot floor employee or patron
host, to quickly and remotely process a table rating and, send and
receive table rating information 450 related to a specific player
24. A table rating allows the gaming system 10 to rate or rank the
player 24 by determining his or her given session or play,
determine his or her worth to the casino, and assign a point
award.
[0177] In the illustrated embodiment, interaction with the user 54,
including receiving input and displaying the player information, is
accomplished using the web client 56.
[0178] 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.
[0179] 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.
[0180] 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.
[0181] 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 FIG. 18, in one embodiment
the returned table rating information is displayed on the remote
device 50A in an open table rating form screen 486.
[0182] 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.
[0183] 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.
[0184] 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.
[0185] 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.
[0186] 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.
[0187] With specific reference to FIG. 17A, a first method 452 for
remotely requesting table rating information relating to a player
24 is provided. In a first step 454, a fillable form is sent to a
remote device for receiving table rating information. In a second
step 456, the table rating information is received at the host
computer for processing a table rating for the player.
[0188] With specific reference to FIG. 17B, a second method 458 for
remotely processing a table rating using the remote device 50A is
shown, according to a second embodiment of the present
invention.
[0189] In a first step 460, the table rating form is displayed on
the remote device 50A.
[0190] 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.
[0191] In a fourth step 466, if the table rating status is open,
the closed status form is displayed on the remote device.
[0192] 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.
[0193] 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.
[0194] In the seventh step 472, zone information is displayed.
[0195] In an eighth step 474, zone is selected and control proceeds
to the ninth step 476.
[0196] 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.
[0197] 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.
[0198] In the eleventh step 480, a bank is entered, and control
proceeds to the twelfth step 482.
[0199] In the twelfth step 482, the open rating form is displayed
and control proceeds to a thirteenth step 484.
[0200] In the thirteenth step 484, the user 54 enters table rating
information.
[0201] In the fourteenth step 486, the table rating is opened and
control returns to the first step 460.
H. Remote Attendance
[0202] With reference to FIGS. 19A, 19B, and 20, the remote system
48 allows the user 54, such as a slot floor employee or patron
host, to quickly and remotely request, send and receive player
attendance information 350 related to a specific player 24. For
example, a marketing or special event may be targeted to patrons or
players meeting defined criteria. Each player who attends the event
is identified as their attendance is stored in the player tracking
system.
[0203] 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.
[0204] 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.
[0205] 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.
[0206] 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.
[0207] 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 FIG. 20, in one embodiment the returned player
attendance information is displayed on the remote device 50A in an
player attendance information screen 384.
[0208] 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.
[0209] 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.
[0210] With specific reference to FIG. 19A, a first method 352 for
remotely requesting information relating to a player 24 is
provided. In a first step 354, identification information is
received at the remote device. In a second step 356, the
identification information is received at the host computer. In a
third step 358, identification information is stored in the
database, i.e., the player before is marked as the player attending
the event. In a fourth step 360, the player attendance information
is retrieved from the database 22 as a function of the
identification information.
[0211] With specific reference to FIG. 19B, a second method 362 for
remotely requesting player information using the remote device 50A
is shown, according to a second embodiment of the present
invention.
[0212] In a first step 364, the attendance form is requested by the
user 54 on the remote device 50A.
[0213] 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.
[0214] 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.
[0215] In the fourth step 370, if a player ID card number is
entered, then the method 362 proceeds to a fifth step 372.
[0216] In the fifth step 372, the ID card number is validated.
[0217] 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.
[0218] In the seventh step 376, if the player 24 is not marked as
attending the event, the control proceeds to an eighth step
378.
[0219] 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
[0220] With reference to FIGS. 21A, 21B, and 22, the remote system
48 allows the user 54, such as a slot floor employee or patron host
to quickly and remotely process an alert having data including user
role information, alert information and alert detail issued by a
gaming machine 13. The user role information is a system where each
user 54 is assigned a role in a hierarchy of roles. The user's role
and level on the hierarchy determines which functions and
information the user can access and the operations the user can
perform.
[0221] In the illustrated embodiment, interaction with the user 54,
including receiving input and displaying the alert information, is
accomplished using the web client 56.
[0222] 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.
[0223] 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.
[0224] 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.
[0225] 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 FIG. 22, in one embodiment the returned alert
information is displayed on the remote device 50A in an alert
information screen 330.
[0226] With specific reference to FIG. 21A, a first method 302 for
remotely processing an alert is provided. In a first step 304,
alert information is received at the remote device. In a second
step 306, the user selects the alert. In a third step 308, the
alert information is retrieved from the database 22 as a function
of the selected alert.
[0227] With specific reference to FIG. 21B, a second method 310 for
remotely requesting player information using the remote device 50A
is shown, according to a second embodiment of the present
invention.
[0228] In a first step 312, the alert information is retrieved as a
function of the user role.
[0229] In a second step 314, the retrieved alert information is
displayed on the remote device 50A.
[0230] In a third step 316, the user selects an alert, then the
method 310 proceeds to a fourth step 318.
[0231] In the fourth step 318, alert detail is retrieved and
displayed as a function of the selected alert.
[0232] In a fifth step 320, the user selects an alert button for
refreshing the alert information stored in the system 10.
[0233] In a sixth step 322, the user acknowledges the alert.
[0234] In a seventh step 324, the system determines if the alert
has already been acknowledged.
[0235] 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.
[0236] 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.
[0237] In the third step 316, the user selects the alert button to
refresh the alert information displayed at the remote device
50A.
[0238] 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
[0239] With reference to FIGS. 23A, 23B and 24, the remote devices
50 allow a user 54 to display and/or increase a player's point,
e.g., bonus points, or comp point balance. In one embodiment, the
remote network interface 68 exchanges data between the host
computer 18 and the remote device 50. The data includes adjustment
information to adjust the points associated with a player 24 in the
player tracking system.
[0240] 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.
[0241] With specific reference to FIG. 24, a sample point
adjustment request form 506, according to one embodiment, is shown.
In the illustrated embodiment, the point adjustment request form
allows the user 54 to enter the type of points, the number of
points, the reason for the adjustment, and the player ID card
number associated with the player 54. When finished, the user 54
may select an ISSUE button to send the date to the host computer is
where the database 22 is updated.
[0242] With specific reference to FIG. 23B, a second method 510 for
adjusting points associated with a player 24 in a player tracking
system is shown. In a first step 512, a request is displayed on the
remote device 50A. The user 54 may then fill out the form and send
the form back to the host computer 18. In one embodiment, a player
ID card number is manually entered on the remote device 59A. In
another embodiment, the player ID card number is read from the ID
card by the bar code reader 66 or the ID card reader 62.
[0243] 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
[0244] With reference to FIGS. 25A, 25B and 26, the remote device
50 may be used to issue point vouchers or comp point vouchers to a
player 24. The vouchers may be embodied in a paper voucher which is
printed on a remote printer carried by the user 54 or may be
embodied in a pre-printed voucher having a voucher ID number which
is carried by the user 54, and assigned to the player 24 in the
player tracking system. Alternatively, the voucher may be embodied
in a record stored in the database 22.
[0245] 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.
[0246] 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.
[0247] With specific reference to FIG. 25, in one embodiment of the
present invention, a method 530 implements a player tracking system
for use with the gaming system. In a first step 532 a fillable form
is sent to the remote device 50A. In a second step 534, the form is
filled with data for issuing a voucher to the player 24.
[0248] 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 FIG.
26, a player voucher form 536, according to an embodiment of the
present invention, is shown. The player voucher form 536 displays
the patron name, the player ID card number, the type of voucher
being selected and the points associated with the patron in the
player tracking system. The player voucher form 536 also lists the
vouchers for which the patron may purchase based on the number of
comp points they have.
[0249] With specific reference to FIG. 25B, a flow diagram of a
second method 536 for assigning vouchers to a player in a player
tracking system is shown. In a first step 540, a first request form
is displayed on the remote device 50A. The first request form
allows the user 54 to select the type of voucher, i.e., either
point or comp point and to enter the card number of the player or
patron 24. In a second step 542, if a card number was entered then
the process proceeds to a third step 546. Otherwise, the method 538
proceeds to a fourth step 544 and an error message is displayed. In
the third step 546, the player's ID card number is validated. In a
fourth step 548, if the ID card number is valid, then the method
538 proceeds to a fifth step 550. Otherwise, the method 538
proceeds to the third step 544 and an error message is displayed.
In the fifth step 550, if the player 24 has any points in the
player tracking system, then the method 538 proceeds to a sixth
step 552. Otherwise, the method 538 proceeds to the third step 544
and an error message is displayed. In the sixth step 552, if there
are any active comps or vouchers that the player 24 can afford
based on the number of points associated with the player 24 in the
patron tracking system, then the method 538 proceeds to the seventh
step 554. Otherwise, the method proceeds to the third step 544 and
an error message is displayed. In the seventh step 554, a request
form or player voucher form 548 is displayed on the remote device
50A. As discussed above, the player voucher form 548 displays a
list of vouchers that the player can afford. If the user 54 selects
one of the vouchers and selects the issue button, then the voucher
or comps are issued in the eighth step 556. In a ninth step 558, if
the comp or voucher was issued without errors then the method
returns to the first step 540. Otherwise, the method returns to the
third step 544 and an error message is displayed.
L. Redemption of Printed Vouchers
[0250] With reference to FIGS. 27A, 27B and 28, the remote device
50 may be used to validated and process, i.e., redeem, printed
vouchers. A printer voucher may be distributed for any number of
reasons, for example, including a promotional event. Typically, the
voucher may be redeemed for an associated service or product. For
example, a printer voucher may be redeemed for a free dinner or
drink.
[0251] 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.
[0252] With reference to FIG. 27A, in one embodiment a method 540
is used to redeem a voucher. In a first step 542, a fillable form
is sent to the remote device 50A. In a second step 544, the
fillable form is filled out without voucher information by the user
54A. In one embodiment, the voucher information includes a voucher
ID number which may be entered manually or by reading a code on the
voucher. For example, the code may be a bar code printed on the
voucher which is read by the bar code reader 66. In a third step
546, the voucher ID number is validated and redeemed.
[0253] With specific reference to FIG. 28, in one embodiment, once
a voucher has been identified by the remote network interface 68, a
voucher information form 548 is displayed on the remote device 50A.
The voucher information form 548 in the illustrated embodiment
includes the voucher ID number, a good for field which identifies
the product or service for which the voucher may be redeemed, an
issued date, and an expiration date. Once the user 54 verifies the
data displayed on the voucher information form, the user 54 may
press the continue button to validate and except the voucher.
[0254] With specific reference to FIG. 27B, a method 550 for
validating and processing and redeeming printed vouchers according
to another embodiment of the present invention is shown. In a first
step 552, a request form is displayed on the remote device 50A. The
request form allows the user 54 to enter a voucher number or a
voucher ID number. In one embodiment, the voucher ID number is
entered manually. In another embodiment, the voucher number is read
from the printed voucher. For example, the voucher ID number may be
encoded into a bar code which is read by the bar code reader 66. In
a second step 554, if the voucher ID number has been entered then
the method proceeds to a third step 556. Otherwise, the method 550
proceeds to a fourth step 558 and an error message is displayed. In
the third step 556, the voucher number is validated. In a fifth
step 560, if the voucher number is valid, then the method proceeds
to a sixth step 562. Otherwise, the method proceeds to the fourth
step 558 and an error message is displayed. In the sixth step 562,
if the voucher has already or previously been accepted, then the
method 550 proceeds to the fourth method step 558 and an error
message is displayed. Otherwise, the method 550 proceeds to a
seventh method step 564 and the voucher is marked as accepted
within the database 22.
M. Voucher Information Retrieval
[0255] With reference to FIGS. 29A, 29B and 30, the remote device
50A may be used to display a list of outstanding vouchers for a
selected player or patron 24 and allow the user 54 to accept a
specific voucher. Typically the voucher has an associated good,
i.e., product, or service for which it may be redeemed. For
example, a specific voucher may be redeemed for a free dinner
and/or drink. In one embodiment, each voucher has a unique voucher
ID number and is stored as a record in the database 22. In another
embodiment, the voucher may be embodied in a printed ticket having
the voucher ID printed or encoded thereon. The voucher ID number
would be associated with the player 24 in the database 22.
[0256] 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.
[0257] 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.
[0258] With specific reference to FIG. 29A, a first method 570 for
redeeming outstanding vouchers for a selected player 24 is shown.
In a first step 572, a fillable form is sent to the remote device
50A. In a second step 574, the form is filled out by the user 54
for identifying the player. In a third step 576, voucher
information is retrieved through the remote network interface 68.
As discussed above, once the player has been identified, a list of
outstanding vouchers is returned to the remote device 50A. A
details button (not shown) associated with each voucher in the list
may be selected by the user 54 to display voucher information
related to the selected voucher. For example, with reference to
FIG. 30, an exemplary voucher information screen 578 is shown. The
voucher information screen 578 may display the voucher ID number,
the good or service for which it may be redeemed, the date it was
issued, and the date the voucher expires. The voucher information
screen 578 also includes an accept button which may be selected by
the user to accept the voucher as it is redeemed.
[0259] With specific reference to FIG. 29B, second method 580 for
displaying and redeeming outstanding vouchers associated with the
player 24 is shown. In a first step 582, a request form is
displayed on the remote device 50A. In one embodiment, the user 54
may enter a player ID card number on the request form. In one
embodiment, the player ID card number is entered manually. In
another embodiment, the player ID card number may be read from the
player ID card by the ID card reader 62 or the bar code reader 66.
In a second step 584, if an ID card number has been entered, then
the method 580 proceeds to a third step 588. Otherwise, the method
580 proceeds to a fourth step 586 and an error message is
displayed. In the third step 588, the ID card number is validated.
In a fifth step 590, if the ID card number is not valid, then the
method 580 proceeds to the third step 586 and an error message is
displayed. Otherwise, the method proceeds to a sixth step 592.
[0260] 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.
[0261] 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).
[0262] 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.
[0263] 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
[0264] 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.
[0265] 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.
[0266] 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.
[0267] 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.
* * * * *