U.S. patent application number 14/089450 was filed with the patent office on 2014-03-27 for systems, methods, and devices for providing purchases of instances of game play at a hybrid ticket/currency game machine.
This patent application is currently assigned to Bally Gaming, Inc.. The applicant listed for this patent is Bally Gaming, Inc.. Invention is credited to Nate Burkett, Mick Delaney, Travis Green, Doug Harvey, Dale Hermansen, Eugene Malina, Dale Shepherd, Warren White.
Application Number | 20140087850 14/089450 |
Document ID | / |
Family ID | 40799159 |
Filed Date | 2014-03-27 |
United States Patent
Application |
20140087850 |
Kind Code |
A1 |
Delaney; Mick ; et
al. |
March 27, 2014 |
SYSTEMS, METHODS, AND DEVICES FOR PROVIDING PURCHASES OF INSTANCES
OF GAME PLAY AT A HYBRID TICKET/CURRENCY GAME MACHINE
Abstract
Systems, methods, and devices may be capable of allowing a
player to purchase an instance of game play at a game system with a
pre-paid ticket or with another item of value. The game system may
determine a denomination of a unit of a currency and generate a
session request indicative of the denomination. The game system may
also determine a ticket code of a ticket and generate a session
request indicative of the ticket code. A remote authorizer may
provide the game system with game authorization indicative of a
number of entertainment credits in response to receiving a session
request.
Inventors: |
Delaney; Mick; (Reno,
NV) ; White; Warren; (Tacoma, WA) ; Hermansen;
Dale; (Reno, NV) ; Green; Travis; (Washoe
Valley, NV) ; Harvey; Doug; (Reno, NV) ;
Burkett; Nate; (Washoe Valley, NV) ; Malina;
Eugene; (Reno, NV) ; Shepherd; Dale; (Fort
Collins, CO) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Bally Gaming, Inc. |
Las Vegas |
NV |
US |
|
|
Assignee: |
Bally Gaming, Inc.
Las Vegas
NV
|
Family ID: |
40799159 |
Appl. No.: |
14/089450 |
Filed: |
November 25, 2013 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
11966840 |
Dec 28, 2007 |
8597107 |
|
|
14089450 |
|
|
|
|
Current U.S.
Class: |
463/25 |
Current CPC
Class: |
G07F 17/3244 20130101;
G07F 17/32 20130101; G06Q 20/045 20130101; G07F 17/329 20130101;
G07F 17/42 20130101 |
Class at
Publication: |
463/25 |
International
Class: |
G07F 17/32 20060101
G07F017/32 |
Claims
1. A game system communicatively coupled to a game-session
authorizer that provides account information indicative of a number
of entertainment credits based at least on one received valid item
of value, comprising: an item of value receiver configured to
receive a purported item of value, the purported item of value
being one of a unit of a currency or a ticket; a validator operable
to determine whether the purported item of value is a valid or
invalid item of value for the purpose of purchasing the session of
game play and operable to determine whether the validated item of
value is a respective ticket or a respective unit of a respective
currency and operable to provide a ticket code indicative of unique
ticket identification information for the respective ticket if the
validated item of value is the respective ticket, wherein the
ticket code is formatted in accordance with a defined format, and
operable to provide currency information indicative of a
denomination of the respective unit of a respective currency if the
validated item of value is the respective unit of a respective
currency; a pseudo ticket code generator communicatively coupled to
the validator and operable to generate a pseudo ticket code
indicative of the denomination of the unit of a respective currency
based at least on the currency information, wherein the pseudo
ticket code is formatted in accordance with the defined format of
the ticket code; a session requester communicatively coupled to the
validator and the pseudo ticket code generator and operable to
generate a game-session request carrying the ticket code if the
validated item of value is the respective ticket and carrying the
pseudo ticket code if the validated item of value is different from
the respective ticket; and a game controller configured to receive
a session authorization indicative of a number of available
entertainment credits and operable to provide a first instance game
play if, and only if, the number of available entertainment credits
indicated by the session authorization is above a threshold.
2. The game system of claim 1 wherein the pseudo ticket code is
further indicative of the respective currency of the unit.
3. The game system of claim 1 wherein the item of value receiver is
further configured to receive a financial card, wherein the
validator is further operable to determine whether the validated
item of value is a respective financial medium and operable to
provide financial medium information indicative of a monetary
amount if the validated item of value is the respective financial
card, and wherein the pseudo ticket code generator is further
operable to generate a respective pseudo ticket code indicative of
the monetary amount based at least on the financial medium
information.
4. The game system of claim 1 wherein the validator is further
configured to read from the respective ticket a machine-readable
symbol encoding the unique ticket identification information for
the respective ticket.
5. The game system of claim 1 wherein the pseudo ticket code
generator is further operable to generate the respective pseudo
ticket code to be indicative of the denomination of the unit of a
respective currency and to be indicative of a number of units of a
respective currency validated by the validator based at least on
the currency information.
6. A game system communicatively coupled to a game-session
authorizer that provides account information indicative of a number
of entertainment credits based at least on one received valid item
of value, comprising: means for validating a purported item of
value as being one of a valid ticket having a ticket identifier
indicative of a ticket code or a unit of a currency having a
denomination, the means for validating a purported item of value
configured to provide the ticket code if the purported item of
value is a respective valid ticket and configured to provide
currency information indicative of at least the denomination if the
purported item of value is a respective valid unit of a respective
currency; means for generating a pseudo ticket code indicative of
the denomination of the respective unit of a respective currency
based at least on the currency information; means for generating a
session request having a defined format based at least on one of
the ticket code provided by the means for validating the purported
item of value or the pseudo ticket code indicative of the
denomination of the respective unit of a respective currency
provided by the means for generating a pseudo ticket code; means
for sending a session request to a remote game session authorizer;
means for receiving authorization indicative of a number of
entertainment credits from the remote authorizer; and means for
controlling access to a game configured to deny access to a game
whenever the means for controlling access to a game receives
information indicative of a respective unit of a respective
currency being provided to purchase an instance of game play and
configured to provide access to the game only upon receiving
authorization indicative of a respective number of entertainment
credits from the remote controller via the means for receiving
authorization.
7. The game system of claim 6, further including: means for
counting a number of validated units of a respective currency,
wherein the pseudo ticket code is further indicative of the number
of validated units of a respective currency.
8. The game system of claim 6 wherein if the purported item of
value is the respective unit of a respective currency, the session
request is indicative of the denomination of the respective unit of
a respective currency.
9. The game system of claim 8 wherein if the purported item of
value is the respective ticket, the session request is indicative
of the ticket code.
10. The game system of claim 9, further comprising: means for
reading a machine-readable symbol encoding the ticket code from the
ticket, wherein the ticket code is indicative of unique ticket
identification information.
11. A method of purchasing a session of game play at a gaming
machine having a game device configured to otherwise deny a
respective session of game play when the game device receives
information indicative of a unit of a currency being presented for
the purpose of the purchase of the session of game play,
comprising: receiving a purported item of value; determining
whether the purported item of value is a valid unit of a currency,
a valid ticket, or invalid for the purposes of purchasing an
instance of game play at the gaming machine; if the purported item
of value is the respective unit of a respective currency,
determining a denomination of the respective unit of a respective
currency, generating a first pseudo ticket code indicative of at
least the denomination of the respective unit of a respective
currency based at least in part on the denomination of the
respective unit of a currency, and providing the first pseudo
ticket code indicative of at least the denomination of the
respective unit of a respective currency to a request generator in
a defined ticket code format; generating in accordance with a
defined format a session request based at least on one of a ticket
code or the first pseudo ticket code, wherein the session request
is indicative of a ticket code if the session request is based at
least on the ticket code for a ticket, and wherein the session
request is indicative of the denomination of the respective unit of
a respective currency if the session request is based at least on
the first pseudo ticket code; sending the session request to a
remote entertainment credit manager; receiving session
authorization indicative of a number of entertainment credits the
remote entertainment credit manager; determining an available
entertainment credit amount based at least on the received session
authorization at a game controller; determining whether the
available entertainment credit amount is above a threshold level at
a game controller; and providing an instance of game play if, and
only if, the available entertainment credit amount is above the
threshold level.
12. The method of claim 11 wherein providing an instance of game
play if, and only if, the available entertainment credit amount is
above the threshold level further comprises denying access to an
instance of game play whenever the game controller receives an
indication that the respective unit of a respective currency was
received by the game machine.
13. The method of claim 11, further comprising: incrementing a
counter in response to the respective unit of a respective currency
being valid, and wherein generating a first pseudo ticket code
indicative of at least the denomination of the respective unit of a
respective currency based at least in part on the denomination of
the respective unit of a currency further includes generating the
first pseudo ticket code indicative of at least a count of the
counter and the denomination of the respective unit of a respective
currency based at least in part on the denomination of the
respective unit of a currency and the count of the counter.
14. The method of claim 11 wherein generating a first pseudo ticket
code indicative of at least the denomination of the respective unit
of a respective currency based at least in part on the denomination
of the respective unit of a currency further comprises formatting
the first pseudo ticket code in accordance with the defined ticket
code format.
15. The method of claim 14, further comprising: receiving a
financial medium associated with a financial account; receiving an
indication of a monetary amount payable from the financial account;
generating a second pseudo ticket code indicative of at least the
monetary amount based at least in part on the monetary amount;
providing the second pseudo ticket code indicative of at least the
monetary amount to the request generator in the defined ticket code
format, and wherein generating in accordance with a defined format
a session request based at least on one of a ticket code or the
first pseudo ticket code, wherein the session request is indicative
of a ticket code if the session request is based at least on a
ticket code for a ticket, and wherein the session request is
indicative of the denomination of the respective unit of a
respective currency if the session request is based at least on the
first pseudo ticket code further includes, generating in accordance
with the defined format a session request based at least on one of
the ticket code, the first pseudo ticket code, or the second pseudo
ticket code, wherein the session request is indicative of the
monetary amount if the session request is based at least on the
second pseudo ticket code.
16. The method of claim 11, further comprising: if the purported
item of value is the respective ticket, reading a ticket identifier
indicative of the ticket code from the respective ticket; providing
the ticket code to a request generator in a defined ticket code
format;
Description
BACKGROUND
[0001] 1. Technical Field
[0002] This disclosure generally relates to systems allowing ticket
based purchases and more particularly to game-entertainment systems
allowing both ticket based purchases and units of currency based
purchases.
[0003] 2. Description of the Related Art
[0004] A game-entertainment system such as a casino or other
entertainment establishment may have various game machines that are
configured to provide an instance of game play when a player
inserts a ticket into the game machine. A ticket normally has a
ticket identifier and may be associated with a nominal amount of
credit or money. A central computer/server may have a data base of
ticket account records, where a ticket account is associated with
one ticket. The ticket account record includes a number of credits
that may be used to purchase an instance of game play at a game
machine and/or redeemed for a monetary amount.
[0005] When a player redeems a ticket in a game machine, the game
machine reads the ticket identifier and sends information
indicative of the ticket identifier to the central computer/server.
The central computer/server determines the number of credits
associated with the ticket, and provides the game machine with an
indication of the number of credits associated with the ticket. If
the number of credits associated with the ticket is sufficient for
purchasing an instance of game play, the game machine allows the
player to purchase an instance of game play. If the number of
credits associated with the ticket is not sufficient for purchasing
an instance of game play, the game machine prevents the player from
purchasing an instance of game play until the player redeems a
sufficient number of tickets.
[0006] Some game machines are ticket-only game machines. These game
machines are configured to allow a player to purchase an instance
of game play only when the player makes the purchase with a ticket.
These machines may include software, firmware, or hardware that
prevents the player from making a purchase of an instance of game
with any instrument other than a ticket.
[0007] There is a need for systems, methods, and devices that allow
a player to make a purchase of an instance of game with a ticket
and with other instruments such as units of a currency and/or
financial media such as credit cards, debit cards, gift cards,
smart cards, etc.
BRIEF SUMMARY
[0008] In one aspect, a game system communicatively coupled to a
game-session authorizer that provides account information
indicative of a number of entertainment credits based at least on
one received valid item of value includes: an item of value
receiver configured to receive a purported item of value, the
purported item of value being one of a unit of a currency or a
ticket; and a validator configured to receive the purported item of
value from the validator and operable to determine whether the
purported item of value is a valid or invalid item of value for the
purpose of purchasing the session of game play. The validator is
operable to determine whether the validated item of value is a
respective ticket or a respective unit of a respective currency and
operable to provide a ticket code indicative of unique ticket
identification information for the respective ticket if the
validated item of value is the respective ticket, wherein the
ticket code is formatted in accordance with a defined format, and
operable to provide currency information indicative of a
denomination of the respective unit of a respective currency if the
validated item of value is the respective unit of a respective
currency. A pseudo ticket code generator communicatively coupled to
the validator and operable to generate a pseudo ticket code
indicative of the denomination of the unit of a respective currency
based at least on the currency information, wherein the pseudo
ticket code is formatted in accordance with the defined format of
the ticket code. The game system may further include: a session
requester communicatively coupled to the validator and the pseudo
ticket code generator and operable to generate a game-session
request carrying the ticket code if the validated item of value is
the respective ticket and carrying the pseudo ticket code if the
validated item of value is different from the respective ticket;
and a game controller configured to receive a session authorization
indicative of a number of available entertainment credits and
operable to provide a first instance game play if, and only if, the
number of available entertainment credits indicated by the session
authorization is above a threshold.
[0009] In one aspect, a game system communicatively coupled to a
game-session authorizer that provides account information
indicative of a number of entertainment credits based at least on
one received valid item of value includes: means for validating a
purported item of value as being one of a valid ticket having a
ticket identifier indicative of a ticket code or a unit of a
currency having a denomination, the means for validating a
purported item of value configured to provide the ticket code if
the purported item of value is a respective valid ticket and
configured to provide currency information indicative of at least
the denomination if the purported item of value is a respective
valid unit of a respective currency; means for generating a pseudo
ticket code indicative of the denomination of the respective unit
of a respective currency based at least on the currency
information; means for generating a session request having a
defined format based at least on one of the ticket code provided by
the means for validating the purported item of value or the pseudo
ticket code indicative of the denomination of the respective unit
of a respective currency provided by the means for generating a
pseudo ticket code; means for sending a session request to a remote
authorizer; means for receiving authorization indicative of a
number of entertainment credits from the remote authorizer; and
means for controlling access to a game configured to deny access to
a game whenever the means for controlling access to a game receives
information indicative of a respective unit of a respective
currency being provided to purchase an instance of game play and
configured to provide access to the game only upon receiving
authorization indicative of a respective number of entertainment
credits from the remote controller via the means for receiving
authorization.
[0010] In another aspect, a method of purchasing a session of game
play at a gaming machine having a game device configured to
otherwise deny a respective session of game play when the game
device receives information indicative of a unit of a currency
being presented for the purpose of the purchase of the session of
game play includes: receiving a purported item of value;
determining whether the purported item of value is a valid unit of
a currency, a valid ticket, or invalid for the purposes of
purchasing an instance of game play at the gaming machine. If the
purported item of value is the respective unit of a respective
currency, the method may further include: determining a
denomination of the respective unit of a respective currency;
generating a first pseudo ticket code indicative of at least the
denomination of the respective unit of a respective currency based
at least in part on the denomination of the respective unit of a
currency; providing the first pseudo ticket code indicative of at
least the denomination of the respective unit of a respective
currency to the request generator in a defined ticket code format.
In addition, the method may further include: generating in
accordance with a defined format a session request based at least
on one of the ticket code or the first pseudo ticket code, wherein
the session request is indicative of a ticket code if the session
request is based at least on the ticket code for a ticket, and
wherein the session request is indicative of the denomination of
the respective unit of a respective currency if the session request
is based at least on the first pseudo ticket code; sending the
session request to a remote entertainment credit manager; receiving
session authorization indicative of a number of entertainment
credits at the remote entertainment credit manager; determining an
available entertainment credit amount based at least on the
received session authorization at a game controller; determining
whether the available entertainment credit amount is above a
threshold level at a game controller; and providing an instance of
game play if, and only if, the available entertainment credit
amount is above the threshold level.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
[0011] FIG. 1 is a block diagram of a game-entertainment system
according to one non-limiting illustrated embodiment.
[0012] FIG. 2 is a block diagram of a ticket for purchasing an
instance of game play at the game-entertainment system according to
one non-limiting illustrated embodiment.
[0013] FIG. 3 is an isometric view of a game system of the
game-entertainment system according to one non-limiting illustrated
embodiment.
[0014] FIG. 4A is a block diagram of a game system of the
game-entertainment system according to one non-limiting illustrated
embodiment.
[0015] FIG. 4B is a block diagram of another game system of the
game-entertainment system according to one non-limiting illustrated
embodiment.
[0016] FIG. 4C is a block diagram of retrofitted game system of the
game-entertainment system according to one non-limiting illustrated
embodiment.
[0017] FIG. 5A is a block diagram of a game session request
template according to one non-limiting illustrated embodiment.
[0018] FIG. 5B is a block diagram of a game session request data
structure for a ticket based purchase according to one non-limiting
illustrated embodiment.
[0019] FIG. 5C is a block diagram of a game session request data
structure for a unit of a currency based purchase according to one
non-limiting illustrated embodiment.
[0020] FIGS. 6A-6B are flow diagrams of processes to open an
account according to one respective non-limiting illustrated
embodiment.
[0021] FIGS. 7A-7B are flow diagrams of processes to close an
account according to one respective non-limiting illustrated
embodiment.
[0022] FIG. 8 is a flow diagram of a session of game play purchased
with an item of value that is not a ticket according to one
non-limiting illustrated embodiment.
[0023] FIG. 9 is a flow diagram of a process for providing a
session of game play to a user at a game system according to one
non-limiting illustrated embodiment.
[0024] FIG. 10 is a flow diagram of a process for initiating a
session of game play at the game system according to one
non-limiting illustrated embodiment.
[0025] FIG. 11 is a flow diagram of a process for granting/denying
session authorization at a game system according to one
non-limiting illustrated embodiment.
[0026] In the drawings, identical reference numbers identify
similar elements or acts. The sizes and relative positions of
elements in the drawings are not necessarily drawn to scale. For
example, the shapes of various elements and angles are not drawn to
scale, and some of these elements are arbitrarily enlarged and
positioned to improve drawing legibility. Further, the particular
shapes of the elements as drawn, are not intended to convey any
information regarding the actual shape of the particular elements,
and have been solely selected for ease of recognition in the
drawings.
DETAILED DESCRIPTION
[0027] In the following description, certain specific details are
set forth in order to provide a thorough understanding of various
disclosed embodiments. However, one skilled in the relevant art
will recognize that embodiments may be practiced without one or
more of these specific details, or with other methods, components,
materials, etc. In other instances, well-known structures
associated with ticket/currency validators, machine-readable
symbols readers, and/or with game subsystems have not been shown or
described in detail to avoid unnecessarily obscuring descriptions
of the embodiments.
[0028] Unless the context requires otherwise, throughout the
specification and claims which follow, the word "comprise" and
variations thereof, such as, "comprises" and "comprising" are to be
construed in an open, inclusive, sense that is as "including, but
not limited to."
[0029] Reference throughout this specification to "one embodiment"
or "an embodiment" means that a particular feature, structure or
characteristic described in connection with the embodiment is
included in at least one embodiment. Thus, the appearances of the
phrases "in one embodiment" or "in an embodiment" in various places
throughout this specification are not necessarily all referring to
the same embodiment. Further more, the particular features,
structures, or characteristics may be combined in any suitable
manner in one or more embodiments.
[0030] As used in this specification and the appended claims, the
singular forms "a," "an," and "the" include plural referents unless
the content clearly dictates otherwise. It should also be noted
that the term "or" is generally employed in its sense including
"and/or" unless the content clearly dictates otherwise.
[0031] The headings and Abstract of the Disclosure provided herein
are for convenience only and do not interpret the scope or meaning
of the embodiments.
[0032] Any process descriptions or blocks in flowcharts described
below may be understood as representing modules, segments, or
portions of code which include one or more executable instructions
for implementing specific logical functions, acts. In alternative
embodiments, various logical functions, steps, or acts may be
executed out of order from that shown or discussed, including
substantially concurrently or in reverse order, and/or manually,
depending on the functionality involved, as would be understood by
those reasonably skilled in the art. Certain acts in the processes
or process flow described in all of the logic flow diagrams
referred to below must naturally precede others to function as
described. However, the various embodiments are not limited to the
order of the acts described if such order or sequence does not
alter the functionality of one or more of the embodiments. That is,
it is recognized that some acts may be performed before, after, or
in parallel with other acts. Further, some embodiments, may include
additional acts and/or omit other acts.
[0033] FIG. 1 shows a game-entertainment system 100 according to
one non-limiting illustrated embodiment. The game-entertainment
system 100 may include various games of chance and/or of skill that
may be played for entertainment and/or for monetary wagers. Games
of chance may include slot machines, roulette, etc. Games of skill
may include poker, blackjack, arcade games, etc. In some
embodiments, the game-entertainment system 100 may provide players
with the opportunity to place monetary wagers on, among other
things, the outcome of a game using tickets, referenced
individually as 110a, 110b, and 110c and collectively as 110, and
units of a currency, referenced individually as 112a, 112b, 112c
and collectively as 112. In some instances such wagers may use
pretend money, that has no actual value outside of the game. Such
may, for example, be used at charitable "casino night" type
events.
[0034] The game-entertainment system 100 may include a front end
102 and a back end 104. The front end 102 includes game systems 106
and may include a ticket dispenser/redeemer 108. The ticket
dispenser/redeemer 108 may be an automated device, kiosk, and/or a
cashier's booth. A player (not shown) may purchase a ticket 110a
by, among other ways, providing the ticket dispenser/redeemer 108
with a unit 112a of a currency having a first monetary value or by
providing a financial medium 114a such as, but not limited to,
credit card, debit card, gift card, smart card, etc.
[0035] In some embodiments, a nominal number of entertainment
credits may be associated with the ticket 110a. An entertainment
credit may be associated with a monetary value, and as such, the
ticket 110a may be redeemable at the ticket dispenser/redeemer 108.
The amount of money for which the ticket 110a may be redeemed may
depend on the number of entertainment credits associated with the
ticket 110a and the monetary value of an entertainment credit. In
some embodiments, the ticket 110a may only be redeemable for
entertainment credit and not for money such may be particularly
useful where tickets are distributed as an incentive (e.g.,
comp).
[0036] In addition to being redeemable, an entertainment credit may
be used to purchase an instance, or instances, of game play at the
game systems 106 and/or other services and goods offered at the
game-entertainment system 100.
[0037] The first time a player uses the game-entertainment system
100, or any time thereafter, the player may purchase the ticket
110a from the ticket dispenser/redeemer 108. After the ticket
dispenser/redeemer 108 receives the unit 112a of a currency and/or
the financial medium 114a, the ticket dispenser/redeemer 108 may
provide a purchase request to the back end 104. The purchase
request may include a purchase amount that generally corresponds to
the monetary value of the unit 112a of the currency, an amount to
be charged to the financial medium 114a, an aggregate of an amount
to be charged to the financial medium 114a and the monetary value
of the unit 112a of the currency, and/or some other amount of
money. The purchase request may further include time-stamps and an
indication of an identity of the terminal for example, a terminal
identifier.
[0038] The game systems 106 may be of various types such as, wager
game systems and non-wager game systems. Non-wager game systems
include various arcade type games such as pinball, in which a
player may attempt to accumulate a number of points which may, or
may not, have actual value. Wager game systems may include various
games such as poker, blackjack, etc. The game systems 106 may
include electronic based devices where a player plays a virtual
game. For example, in a game of virtual poker, virtual cards are
dealt and displayed to a player, and the player may play against
the game system 106. Some of the game stations 106 may be a hybrid
electro-mechanical game such as a game system with electronic
payment and accounting components and mechanical game
components.
[0039] A player may commence a session of game play by purchasing
an instance of game play from the game system 106 using a ticket
110b and/or a unit 112b of the currency and/or a financial medium
114b. In some embodiments, the player may accrue entertainment
credits from an instance of game play. Some or all of the
entertainment credits may be used to purchase another instance of
game play during the session of game play or some or all of the
entertainment credits may be saved for later redemption.
[0040] When the player has finished the session of game play, the
game system 106 may provide the player with a ticket 110c. The
ticket 110c may be associated a number of entertainment credits.
The number of entertainment credits associated with the ticket 110c
may be depend at least on a number of entertainment credits
initially associated with the ticket 110b (or the monetary value of
the unit 112b of the currency or the amount of funds charged-to,
debited-from, financial medium 114b) and the total number of
available entertainment credits saved during the session of game
play.
[0041] In some embodiments, the game system 106 may return the
ticket 110b to the player when the player terminates a session of
game play. Information associated with the ticket 110b may be
updated based at least in part on the number of instances of game
play purchased during the session of game play and/or the number of
entertainment credits received by the player during the session of
game play.
[0042] The back end 104 may include a system controller 116 which
may be communicatively coupled to the game systems 106 and to the
ticket dispenser/redeemer 108 by communication links 118. The
communication links 118 may be a network such as a wire, wireless,
or combination thereof, network. The system controller 116 may
include an authorizer subsystem 120 and an account manager
subsystem 122 and may be embodied in a computing system,
distributed computing system, servers, etc. The authorizer
subsystem 120 is configured to respond to game session requests and
to selectively grant or deny permission for a session of game play.
The session request may include information indicative of a
purchase amount and/or information indicative of unique ticket
identification information, time-stamps and terminal identity.
[0043] The account manager subsystem 122 may include account
records 124. Each one of the account records may include a unique
account identifier 126 and a credit amount 128, which may generally
correspond to the purchase amount and/or a number of entertainment
credits. The unique account identifier 126 of a respective account
record 124 may associate the respective account record 124 with one
of the tickets 110a, 110b, 110c, and the credit amount 128 of the
respective account record 124 may be indicative of the number of
entertainment credits associated with the same ticket 110a, 110b,
110c.
[0044] In some embodiments, when a player uses the ticket 110b to
purchase an instance of game play at the game system 106, the game
system 106 may provide the system controller 116 with information
indicative of unique ticket identification information. Based at
least in part on the information indicative of unique ticket
identification information, the account manager 122 may determine
with which one of the account records 124 the ticket 110b is
associated. The determination may also be based at least in part on
the respective account identifier 126 for the accounts records 124.
Having determined the account record 124 with which the ticket 110b
may be associated, the account manager 122 may determine a number
of entertainment credits associated with the ticket 110b based at
least in part on the credit amount 128 of the respective account
record 124. The system controller 116 may then provide the game
system 106 with information indicative of the number of
entertainment credits associated with the ticket 110b. The game
system 106 may determine whether to provide an instance of game
play based at least in part on the information indicative of the
number of entertainment credits associated with the ticket
110b.
[0045] In some embodiments, the tickets 110 may be single-use only
tickets. For example, a player may purchase the ticket 110a from
the ticket dispenser/redeemer 108. An account record 124 may be
created and associated with the ticket 110b. The player may
commence a session of game play at one of the game systems 106 by
purchasing an instance of game play with the ticket 110b. During
the session of game play, the game system 106 audits entertainment
credits for the player, e.g., available entertainment credits=a
number of entertainment credits initially associated with the
ticket 110a plus a number of available entertainment credits
accrued during the session of game play minus a number of
entertainment credits used to purchase instances of game play. At
the end of the session of game play, the game system 106 may
provide the system controller 116 with information indicative of
the number of available entertainment credits and provide the
player with a new ticket 110c. The new ticket 110c may be
associated with a newly created account record 124. The player may
take the new ticket 110c to another game system 106 to commence
another session of game play or redeem the ticket 110 at the ticket
dispenser/redeemer 108.
[0046] In some embodiments, the tickets 110 may be multi-use
tickets. For example, a player may commence a session of game play
at one of the game systems 106 by purchasing an instance of game
play with the ticket 110b. During the session of game play, the
game system 106 audits entertainment credits for the player, e.g.,
available entertainment credits=a number of entertainment credits
initially associated with the ticket 110b plus a number of
entertainment credits accrued during the session of game play minus
a number of entertainment credits used to purchase instances of
game play. At the end of the session of game play, the game system
106 may provide the system controller 116 with information
indicative of the number of available entertainment credits and
provide the player with the same ticket 110b. The system controller
116 may update account information based at least on the
information indicative of the number of available entertainment
credits. The player may take the ticket 110b to another game system
106 to commence another session of game play or redeem the ticket
110 at the ticket dispenser/redeemer 108.
[0047] In some embodiments, the account manager subsystem 122 may
create an account record 124 when a player purchases the ticket
110a at the ticket dispenser/redeemer 108. The credit amount 128 of
the account record 124 may be based at least in part on the
purchase amount of the ticket 110a. The account manager subsystem
122 may provide the ticket dispenser/redeemer 108 with information
indicative of a ticket identifier that may be associated with the
newly created account record 124. Alternatively, in some
embodiments, the account manager subsystem 122 may receive from the
ticket dispenser/redeemer 108 information indicative of a ticket
identifier or information indicative of ticket identification
information that may be encoded by a ticket identifier, and the
received information may be associated with the newly created
account record 124.
[0048] In some embodiments, the ticket dispenser/redeemer 108 may
generate ticket identification information and print a ticket
identifier that encodes the ticket identification information on a
surface of a ticket. In some embodiments, the ticket
dispenser/redeemer 108 may receive information indicative of ticket
identification information and print a ticket identifier that
encodes the ticket identification information on a surface of a
ticket. In some embodiments, the ticket dispenser/redeemer 108 may
provide the system controller 116 with information indicative of
ticket identification information.
[0049] In some embodiments, the account manager subsystem 122 may
create an account record 124 when a player purchases an instance of
game play at the game system 106 with an item of value that is not
a ticket 110. The credit amount 128 of the newly created account
record 124 may be based at least in part on the monetary value of
the unit 112b of the currency and/or the amount of money to be
charged-to, or debited-from, financial medium 114b. The account
manager subsystem 120 may provide the game system 106 with
information indicative of a ticket identifier that is associated
with the newly created account record 124. Alternatively, in some
embodiments, the account manager subsystem 120 may receive
information indicative of a ticket identifier that is associated
with the newly created account record 124 from the game system
106.
[0050] In some embodiments, the account manager subsystem 122 may
create an account record 124 after a player has ended a session of
game play at the game system 106. For example, the credit amount
128 of the newly created account record 124 associated with ticket
110c may reflect a number of entertainment credits based at least
in part on the number of available entertainment credits at the end
of the session of game play by the player.
[0051] In some embodiments, the account manager subsystem 122 may
update an account record 124 after a player has ended a session of
game play at the game system 106. For example, the credit amount
128 of the account record 124 associated with ticket 110b may be
updated to reflect a change in a monetary value or a change in a
number of entertainment credits based at least in part on the
number of available entertainment credits at the end of the session
of game play.
[0052] FIG. 2 shows a ticket 110 according to one non-limiting
illustrated embodiment. The ticket 110 may be made of paper or
similar material and/or other pliable material. The ticket 110
includes a ticket identifier 130. In some embodiments, the ticket
identifier 130 may be one or more machine-readable symbols (e.g.,
bar code symbols, stack code symbols, area or matrix code symbols)
that encode a ticket code that may be indicative of unique ticket
identification information. In such embodiments, the game system
106 and the ticket dispenser/redeemer 108 may include one or more
machine-readable symbol readers, such as scanners or imagers that
read bar codes, stacked codes, and/or area or matrix codes, and the
game system 106 and the ticket dispenser/redeemer 108 may include
instructions for decoding such machine-readable symbols. The ticket
identifier 130 may be associated with the account identifier 126 of
a respective account record 124. The ticket may also include
human-readable information, for example, an indication of a current
value or worth of the ticket in currency or credits
[0053] FIG. 3 shows a game system 106 according to one non-limiting
embodiment. The game system 106 includes a display device 132 and a
user interface 134. The user interface 134 may include various
buttons, keys, track wheel, track ball, joy stick, key pad, number
pad, touch pad, touch screen, user selectable icons, etc. A player
may use the user interface 134 to, among other things, select a
game or virtual game, control and play a game or virtual game, and
to select an amount to be charged-to, or debited-from, financial
medium 114b.
[0054] The gaming machine 106 also includes an item of value (IOV)
receiver 136 and a financial medium receiver 138. The IOV receiver
136 may receive items that are purportedly of value. The IOV
receiver 136 is configured to receive units 112b of a respective
currency and tickets 110b. In some embodiments, the IOV receiver
136 may receive units 112b of a currency of various denominations
and of various currencies, e.g., a Canadian ten dollar bill and a
U.S. ten dollar bill.
[0055] The financial medium receiver 138 may receive financial
media 114b such as credit cards, debit cards, gift cards, smart
cards, etc. A user of the game system 106 may use the IOV receiver
136 and/or the financial medium receiver 138 along with ticket 110b
and/or the unit 112a of the currency and/or financial medium 114b
to commence a session of game play. In some embodiments, the IOV
receiver 136 may be adapted to receive the financial medium 114b,
which may negate the need for the financial medium receiver
138.
[0056] FIG. 4A is a block diagram of a game system 106 according to
one non-limiting illustrated embodiment. The game system 106
includes an IOV subsystem 140, a game session subsystem 142, and a
game subsystem 144. The game subsystem 144 may be configured to
provide an instance of a game to the user. In some embodiments, the
game system 106 may be configured to provide an instance of game
play only if the instance of game play was purchased by a ticket
110.
[0057] The IOV subsystem 140 includes an IOV receiver 146, a
validator 148, and an IOV receptacle 150. The IOV receiver 146
receives items that are purportedly items of value such as tickets
110 and units 112 of a respective currency. The IOV receiver 146
provides the validator 148 with the received items.
[0058] The validator 148 may be configured to validate purported
items of value. The validator 148 may determine whether a purported
item of value is a valid ticket and/or a valid unit of a currency.
For example, the validator 148 may determine whether a purported
item of value is a valid unit of a currency, such as, but not
limited to, a United States (U.S.) dollar bill, a U.S. five-dollar
bill, a U.S. ten-dollar bill, a U.S. twenty-dollar bill, etc. Such
may include optically, magnetically, inductively, capacitively, or
otherwise sensing various characteristics of the purported item of
value and comparing the sensed characteristics to defined values
representative of valid characteristics. In some embodiments, the
validator 148 may be configured to validate units of currency for
multiple currencies. The validator 148 may be also configured to
validate received tickets 110. Among other things, the validator
148 may read the ticket identifier 130 on a ticket 110. If the
validator 148 determines that a purported item of value is valid,
the validator 148 provides the validated item of value to the IOV
receptacle 150. In some embodiments, if the validator 148 cannot
validate a purported item of value, the purported item of value may
be rejected and may be ejected the game system 106 via the IOV
receiver 146 or with or without notifying appropriate
personnel.
[0059] The IOV receptacle 150 may be configured to receive and
securely hold validated items of value. In some embodiments,
validated items of value may be held in a lock box or the like. In
some embodiments, the IOV receptacle 150 may include an optional
cash holder 152 and an optional ticket holder 154. The cash holder
152 may be used to hold validated units 112 of a currency
separately from validated tickets 110, which may be held in the
ticket holder 154.
[0060] The validator 148 may be configured to provide item of value
information to the game session subsystem 142. For example, if the
validated item is a unit of a currency, item of value information
may include, among other things, a denomination of the unit of the
currency, at least a portion of a serial number of the unit of the
currency, and/or a currency indication for the unit of the
currency, e.g., United States currency or Canadian currency. As
another example, if the validated item is a ticket, item of value
information may include a ticket code. Non-limiting examples of
information that may be carried by a ticket code include at least a
portion of ticket identification information encoded by the ticket
identifier 130 of the ticket 110, information indicative of the
ticket identifier 130, information indicative of the unique ticket
identification information encoded by the ticket identifier 130,
among other things.
[0061] The financial medium receiver 156 may be configured to
receive financial media such as credit cards, debit cards, gift
cards, smart cards, etc., and communicate with a financial
institution such as a credit card company, a bank, a credit union,
etc. The financial medium receiver 156 may provide item of value
information to the game session subsystem 142. Item of value
information for the case of a financial medium may include an
indication of a monetary value, information indicative of the
received financial card, etc.
[0062] The game session subsystem 142 may include a pseudo ticket
code generator 158, a session requester 160, a session controller
162, and an IOV generator 164. The pseudo ticket code generator 158
receives item of value information from either the validator 148 or
the financial medium receiver 156, when a validated item of value
is not a unit of a currency. The pseudo ticket code generator 158
may generate a pseudo ticket code based at least in part on the
received item of value information. The pseudo ticket code
generator 158 may include a counter (not shown) that may be
incremented whenever the pseudo ticket code generator 158 generates
a pseudo ticket code. In some embodiments, the pseudo ticket code
generator 158 may include multiple counters, and each one of the
counters may be associated with a different type of validated item
of value, e.g., a counter for units of a currency and another
counter for financial media, etc.
[0063] When a validated item of value is a ticket 110, the session
requester 160 may receive a ticket code from the validator 148; and
when a validated item of value is not a ticket, the session
requester 160 may receive a pseudo ticket code from the pseudo
ticket code generator 158. The session requester 160 may generate a
session request based at least in part on the received ticket code
or the received pseudo ticket code. For example, if the validated
item of value is a ticket 110, the session request may include
information indicative of the unique ticket identification
information encoded by the ticket identifier 130 of the ticket 110.
As another example, if the validated item of value is a unit of a
currency, the session request may include information indicative of
a count of a counter associated with the unit of the currency, the
denomination of the unit of the currency, the currency, etc. The
session requester 160 sends the session request to the system
controller 116.
[0064] In some embodiments, the ticket code information and the
pseudo ticket code information may be formatted essentially
identically such that the session requester 160 cannot determine
whether the validated item of value is a valid ticket or not. For
example, in some embodiments, both ticket code information and
pseudo ticket code information may be of equal fixed length.
[0065] The session controller 162 may receive session authorization
information from the system controller 116. Session authorization
information may include, among other things, information indicative
of a number of entertainment credits. In addition, session
authorization information may include, among other things,
information indicative of a grant of permission or a denial of
permission to an instance of game play. In some embodiments, a
denial of permission to an instance of game play may be inferred
from the number of entertainment credits, e.g., if zero
entertainment credits, then denial of permission.
[0066] Based at least in part on the session authorization
information from the system controller 116, the session controller
162 may grant a player an instance of game play and determine a
total number of available entertainment credits that may be used to
purchase an instance(s) of game play. Each time the player
purchases another instance of game play, the session controller 162
may debit a number of entertainment credits from the total number
of available entertainment credits. Each time the player is awarded
or receives a number of entertainment credits, the session
controller 162 may add the number of received entertainment credits
to the total number of available entertainment credits. In some
embodiments, at the end of the session of game play, the session
controller 162 may provide the system controller 116 with session
information indicative of the total number of available
entertainment credits and provide the player with the ticket 110c,
which may now be associated the total number of available
entertainment credits. The system controller 116 may provide the
game system with information indicative of ticket identification
information encoded by the ticket identifier 130 of ticket 110c. In
some embodiments, the ticket 110c may be the same ticket 110b that
the player used to purchase an instance of game play.
[0067] The session controller 162 may be communicatively coupled to
the IOV generator 164 and may provide the IOV generator 164 with
information indicative of identification information. When a player
ends a session of game play, the IOV generator 164 may generate a
new ticket 110c based at least in part on the information
indicative of ticket identification information encoded by the
ticket identifier 130. The IOV generator 164 may provide the ticket
110c to the player.
[0068] In some embodiments, the IOV generator 164 may print the
ticket identifier 130 on a surface of the ticket 110. In other
embodiments, the ticket identifier 130 may be pre-printed on a
surface of the ticket 110. In that case, the IOV generator 164 may
read the ticket identifier 130 on the ticket 110 may provide the
session controller 162 with information indicative of the ticket
identification information encoded by the ticket identifier 130.
The session controller 162 may provide the system controller 116
with information indicative of the ticket identification
information encoded by the ticket identifier 130.
[0069] Various ones of the modules and/or subsystems described
above such as the validator 148, financial medium receiver 156,
pseudo ticket code generator 158, session requestor 160, session
controller 162, IOV generator 164, and game subsystem may be
individually or collectively embodied in one or more logical
devices such as a custom made or commercially available processor,
a central processing unit (CPU), a semiconductor based
microprocessor (in the form of a microchip or chip set), or
generally any device for executing software instructions and/or may
be individually or collectively embodied in firmware that is stored
in a memory and that is executed by a suitable instruction
execution system. If implemented in hardware, as in an alternative
embodiment, the any one or all of the aforementioned modules and
subsystem may be individually or collectively implemented with any
or a combination of the following technologies: a discrete logic
circuit(s) having logic gates for implementing logic functions upon
data signals, an application specific integrated circuit (ASIC)
having appropriate combinational logic gates, a programmable gate
array(s) (PGA), a field programmable gate array (FPGA), etc.
[0070] FIG. 4B shows a game system 106 according to another
non-limiting illustrated embodiment. The game system 106 includes
an IOV subsystem 166, a session subsystem 168, and a game subsystem
170. The game subsystem 170 is similar in at least some respects to
the game subsystem 144 and will not be discussed in detail for the
sake of brevity. In FIG. 4B, the various labels having both a
reference numeral and a letter "a" identify components and/or
features that are similar in at least some respects as those shown
in FIG. 4A that are labeled with the same reference numeral. The
detailed description of such components are initially provided with
respect to the embodiment of FIG. 4A and, for the sake of brevity,
the description of such components in the context of their
subsequent "a" labeled counterparts in FIG. 4B are abbreviated or
omitted.
[0071] The session subsystem 168 includes a processor 172, a memory
174, input/output devices 176, and network interface 180, which are
communicatively coupled by one or more buses 182.
[0072] The processor 172 may be a device for executing software,
particularly that stored in a memory 174. The processor 172 may be
a custom made or commercially available processor, a central
processing unit (CPU), a semiconductor based microprocessor (in the
form of a microchip or chip set), or generally any device for
executing software instructions.
[0073] The memory 174 is communicatively coupled to the processor
172. The memory 174 may include any one or combination of volatile
memory elements such as a read-only memory (ROM) and a random
access memory (RAM). The random access memory (RAM) may include
dynamic random-access memory (DRAM), static random-access memory
(SRAM), synchronous dynamic random-access memory (SDRAM), flash
RAM, etc.
[0074] The memory 174 may store one or more logic modules or logic
routines, each of which may comprise an ordered listing of
executable instructions for implementing logical functions. In
particular, the memory 174 includes an operating system 194 and
session controller logic 184. The execution of the operating system
194 by the processor 172 essentially controls the execution of
other logic, such as session controller 184 and provides
scheduling, input-output control, file and data management, memory
management, and communication control and related services.
[0075] The session controller logic 194 may include various logic
modules or logic routines, each of which may comprise an ordered
listing of executable instructions for implementing logical
functions. In particular, the session controller logic 194 may
include pseudo ticket code generator logic 186, session requestor
logic 188, IOV generator logic 190, and credit manager logic 192.
The pseudo ticket code generator logic 186 includes logic for
generating a pseudo ticket code based at least in part on
information from the validator 166. The session requestor logic 188
includes logic for sending a session request to the control system
116 based at least in part on a ticket code from the validator 148a
or a pseudo ticket code from the pseudo ticket code generator logic
186. The IOV generator logic 190 includes logic for generating a
ticket. The credit manager logic 192 includes logic for monitoring
and accounting of a number of available entertainment credits
during a session of game play.
[0076] The I/O devices 176 may include user interface devices such
as a display and various user selections devices such as buttons,
keys, track wheel, track ball, joy stick, key pad, number pad,
touch pad, touch screen, user selectable icons, etc.
[0077] The network interface 180 may include network cards and/or
wireless communication devices that provide a communication link
with the system controller 116.
[0078] In some embodiments, the session controller logic 184 or a
portion of the session controller logic 184 may be implemented in
firmware that is stored in a memory and that is executed by a
suitable instruction execution system. If implemented in hardware,
as in an alternative embodiment, the session controller logic 184
and/or various logic modules or logic routines of the session
controller logic 184 can be implemented with any or a combination
of the following technologies: a discrete logic circuit(s) having
logic gates for implementing logic functions upon data signals, an
application specific integrated circuit (ASIC) having appropriate
combinational logic gates, a programmable gate array(s) (PGA), a
field programmable gate array (FPGA), etc.
[0079] Referring to FIG. 4C, in some embodiments, the game system
106 may include a retrofitted item of value subsystem 178, and a
ticket-only game system 196. In FIG. 4C, the various labels having
both a reference numeral and a letter "b" identify components
and/or features that are similar in at least some respects as those
shown in FIG. 4B that are labeled with the same reference numeral
and/or with the same reference numeral with a letter "a"
concatenated thereto. The detailed description of such components
are initially provided with respect to the embodiment of FIG. 4B
and, for the sake of brevity, the description of such components in
the context of their subsequent "b" labeled counterparts in FIG. 4C
are abbreviated or omitted.
[0080] The ticket-only game system 196 may include the session
subsystem 168b and the game subsystem 170 and may be configured to
commence a session of game play only if a valid ticket is used to
purchase the initial instance of game play. Prior to being
retrofitted, if a player attempted to purchase an instance of game
play with a unit of a currency, the ticket-only game system 196
would reject the unit of the currency or such would not even be
insertable into the ticket-only game system 196. When a
pre-retrofitted validator (not shown) received a unit of a
currency, the pre-retrofitted validator (not shown) would provide
the session controller 162 with game purchase information such as a
denomination of the unit of the currency. In a ticket-only game
system, the session controller logic 174 may be configured to
reject all purchases of an instance of game play for currency based
purchases. In that case, the processor 172 may prompt the
pre-retrofitted validator (not shown) to reject the unit of the
currency, which may be ejected via the IOV receiver 146a.
[0081] The retrofitted IOV subsystem 178 may include the validator
148b and a pseudo ticket code generator 198. In some embodiments,
the pseudo ticket code generator 198 may receive a ticket code from
the validator 148b when the purported item of value received by the
validator 148b is a valid ticket 110. The pseudo ticket code
generator 198 may provide the ticket code to the ticket-only game
system 196. In other embodiments, the validator 148b may provide
the ticket code to the ticket-only game system 196 when the
purported item of value received by the validator 148b is a valid
ticket 110.
[0082] When the purported item of value received by the validator
148b is not a ticket 110, the pseudo ticket code generator 198 may
receive, among other things, an indication of a denomination of a
unit of currency. Based at least in part on the indication of a
denomination of a unit of currency, the pseudo ticket code
generator 198 may generate a pseudo ticket code and provide the
pseudo ticket code to the ticket-only game system 196. The
ticket-only game system 196 will use the pseudo ticket code to
request a session of game play which may be carried on or by a
computer-readable medium.
[0083] FIG. 5A shows a game session request template 200a according
to one illustrated embodiment. The game session request template
200a includes a ticket code field 202a, which may be of fixed or
variable length. The ticket code field 202a includes a number of
data carrier elements 204a. A respective one of the data carrier
elements 204a may be sized to carry a bit, a byte, a word, etc., of
information. In the embodiment illustrated in FIG. 5A, there are
eighteen (18) data carrier elements 204a shown. In other
embodiments, the number of data carrier elements 204a may be fewer
or more. In the illustrated embodiment, the first seventeen data
carrier elements may carry information indicative of a ticket code
and/or information indicative of a pseudo ticket code, and in the
illustrated embodiment, the eighteenth data carrier element may
carry error detection information such as a checksum of the first
seventeen data carrier elements.
[0084] The session requester 158 may populate the ticket code field
202a based at least in a ticket code provided by the item of value
subsystem 140. FIG. 5B shows an exemplary game session request 200b
data structure for the case where a player purchases an instance of
game play with a valid ticket 110.
[0085] The validator 148 reads the ticket identifier 130 of the
ticket 110. The ticket identifier 130 may be a machine-readable
symbol encoding unique ticket identification information. The
validator 148 may provide a ticket code, which may be indicative of
the unique ticket identification information and/or indicative of
the ticket identifier 130, to the session requestor 160. Based at
least in part on the ticket code, the session requester 160
populates the ticket code field 202b. The information carried by
the ticket code field 202b may be indicative of the ticket
identifier 130 and/or indicative of the unique ticket
identification information. For example, the ticket identifier 130
may be a machine-readable symbol encoding a sequence of seventeen
numbers. Each one of the first seventeen data carrier elements 204b
may be a respective one of the seventeen numbers encoded by the
ticket identifier 130. The eighteenth data carrier element 204b may
carry error detection information such as a checksum and/or error
correction.
[0086] FIG. 5C shows an exemplary session request 200c data
structure for the case where the player purchases an instance of
game play with a validated unit of a currency. In this case, the
pseudo ticket code generator 158 generates a pseudo ticket code
based at least in part on item of value information from the
validator 148. Based at least in part on the pseudo ticket code,
the session requester 160 populates the ticket code field 202b. The
information carried by the ticket code field 202c may be indicative
of a denomination for the validated unit of currency and/or
indicative of a count of a counter associated with the validated
unit of currency. As one non-limiting example, the ticket code
field 204c may be conceptualized as having four segments 206a-206d
having seven, four, six, and 1 data carrier elements, respectively.
The seven data carrier elements 204 in segment 206a may be set to
identify the game session request 200c as being a currency based
request and may also be indicative of the respective currency,
e.g., U.S. currency, Canadian currency, etc. The four data carrier
elements 204 in the second segment 206b may carry information
indicative of a count of a number of validated units of currency.
The six data carrier elements 204 in the third segment 206c may
carry information indicative of a denomination of the validated
unit of currency. The data carrier element 204 in the fourth
segment 206d may carry error detection and/or error correction
information. As a non-limiting example, if the purported item of
value received by the validator 148 is a valid U.S. fifty-dollar
bill, the first seven data carrier elements 204 may be set to all
zeros to signify that the validated item of value is U.S. currency.
The eighth and ninth data carrier elements 204 may be set to a
count of a currency counter, and for redundancy, the tenth and
eleventh data carrier elements 204 may be set to the count of a
currency counter. The 12.sup.th-14.sup.th the data carrier elements
204 may be set to carry information that indicates the denomination
(fifty dollars) of the validated unit of currency, and for
redundancy, the 15.sup.th-17.sup.th data carrier elements 204 may
be set to carry information that indicates the denomination (fifty
dollars) of the validated unit of currency. The eighteenth data
carrier elements 204 may carry error detection information.
[0087] FIG. 6A shows a flow diagram 600 of an account being created
according to one illustrated embodiment.
[0088] A player 602 may use cash, i.e., a unit of a currency, or a
financial medium or other financial instrument 604 to purchase a
ticket at a ticket dispenser/redeemer 606. The ticket
dispenser/redeemer may provide purchase information 608 that may be
indicative of a monetary amount to a system controller 610. The
system controller 610 may open an account 612 based at least in
part on the purchase information 608 provided by the ticket
dispenser/redeemer 606.
[0089] The system controller 610 may provide the ticket
dispenser/redeemer 604 with account information 614 that may be
indicative of an available number of entertainment credits and/or
identification information. The identification information may be
related to the account 612 and/or may be related to a ticket
identifier.
[0090] The ticket dispenser/redeemer 606 may provide a ticket 616
to the player 602. The ticket 616 may include a ticket identifier
that may encode the identification information related to the
account 612 or may encode information indicative of unique ticket
identification information.
[0091] FIG. 6B shows a flow diagram 620 of an account being created
according to another illustrated embodiment.
[0092] A player 622 may provide input 624 for ending a session of
game play at a game system 626. The game system 626 may determine a
number of available entertainment credits at the end of the session
of game play. Entertainment credits may be purchased or awarded or
otherwise received, e.g., compliments of the game-entertainment
system 100, during game play. The game system 626 may provide
session information 628 which may be indicative of the number of
available entertainment credits to a system controller 630.
[0093] The system controller 630 may open an account 632 based at
least in part on the session information 628. The system controller
630 may provide the game system 626 with account information 634
which may be indicative of an available number of entertainment
credits and/or identification information. The identification
information may be related to the account 632 and/or may be related
to a ticket identifier.
[0094] The game system 626 may provide the player 622 with a ticket
636. The ticket 636 may include a ticket identifier that may encode
the identification information related to the account 632 or may
encode information indicative of unique ticket identification
information.
[0095] The player 622 may redeem the ticket 636 at another game
system or at the ticket dispenser/redeemer.
[0096] FIG. 7A shows a flow diagram 700 of an account being closed
according to one illustrated embodiment.
[0097] A player 702 may provide a ticket dispenser/redeemer 706
with a ticket 704 having a ticket identifier. The ticket identifier
may encode ticket identification information or a ticket code.
[0098] The ticket dispenser/redeemer 706 may provide the ticket
code 708 and/or an indication of the ticket code to a system
controller 710. The ticket code 708 may be indicative of unique
ticket identification information.
[0099] The system controller 710 may close an account 712 based at
least in part on the ticket code 708. The system controller 710 may
determine a number of available entertainment credits associated
with the account 712. The system controller may provide the ticket
dispenser/redeemer 706 an account indicator 714 indicative of a
number of available entertainment credits.
[0100] The ticket dispenser/redeemer 706 may provide the player 702
with units of currency or credits 716 based at least in part on the
account indicator 714. If the player does not receive units of
currency, credits 716 may be applied to a financial card, or funds
may be deposited into a financial account specified by the player.
In some embodiments, credits may not be redeemed for cash or a
monetary value, but rather are only redeemable for game play. Such
credits may also have an associated time limit, that limits a
period during which such credits must be used or are otherwise lost
or forfeited.
[0101] FIG. 7B shows a flow diagram 720 of an account being closed
according to another illustrated embodiment.
[0102] A player 722 may provide a ticket 724 having a ticket
identifier to a game system 726. Prior to the game system 726
receiving the ticket 724, there are no entertainment credits
available for a session of game play at the game system 726.
[0103] The game system 726 may read the ticket identifier from the
ticket 724. The ticket identifier may encode ticket identification
information or a ticket code.
[0104] The game system 726 may provide the ticket code 728 and/or
an indication of the ticket code to a system controller 730. The
ticket code 728 may be indicative of unique ticket identification
information.
[0105] The system controller 730 may close an account 732 based at
least in part on the ticket code 728. The system controller 730 may
determine a number of available entertainment credits associated
with the account 732. The system controller 730 may provide the
game system 726 an account indicator 734 indicative of the number
of available entertainment credits.
[0106] The game system 726 may include a credit manager. The credit
manager may indicate that the game system 726 is ready to play if
the number of available entertainment credits is above a threshold
amount.
[0107] FIG. 8 shows a flow diagram 800 of a session of game play
purchased with an item of value that is not a ticket according to
one illustrated embodiment.
[0108] A player 802 may provide a game system 806 with cash, i.e.,
a unit of a currency, a financial card, or other financial
instrument 804 to purchase an instance of game play at the game
system 806. Prior to the player 802 providing the unit of a
currency, financial card, or other financial instrument 804 to the
game system 806, there are no entertainment credits available for
the player at the game system 806. The game system 806 may provide
purchase information 808 which may, for example, be indicative of a
monetary amount, e.g., a purchase amount, to a system controller
810.
[0109] The system controller 810 may open an account 812 based at
least in part on the purchase information 808. The system
controller 810 may close the account 812 and provide the game
system 806 with an account indicator 814 which may indicative of a
number of available entertainment credits. The opening and closing
of account 812 may be done for accounting purposes, and/or so that
non-ticket transactions may be processed in a manner consistent
with ticket transactions.
[0110] If the account indicator 814, which may be indicative of the
number of available entertainment credits, is sufficient for a
purchase of an instance of game play at the game system 806, then a
session of game play 816 may be commenced at the game system 806.
It should be understood that the player 802 may continue to provide
the game system 806 with further cash, i.e., another unit of a
currency, and/or financial card(s), and/or other financial
instrument(s) to increase the player's total number of available
entertainment credits. Each time the player provides a valid item
of value, the game system 806 will receive another account
indicator, and the game system will determine a total number of
available entertainment credits based at least in part on the
received account indicators.
[0111] During the session of game play 816, the player 802 may be
awarded or receive entertainment credits and may also spend
entertainment credits to purchase further instances of game play.
Assuming that at the end of the session of game play that the
player has some available entertainment credits, i.e., the player
did not spend every entertainment credit, the game system 806 may
provide the system controller 810 with session information 818
which may be indicative of a number of available entertainment
credits at the end of the session of game play.
[0112] The system controller 810 may open an account 820. The
system controller 810 may provide the game system 806 with account
information 822 that may be indicative of identification
information related to the account 820. The identification
information may be indicative of an identifier for the account
820.
[0113] The game system 806 may generate a ticket 824 based at least
in part on the account information 822. The ticket 824 may carry a
ticket identifier that is indicative of the identification
information related to the account 820. The game system 806 may
provide the ticket 824 to the player 802.
[0114] FIG. 9 shows a flow diagram 900 of a process for providing a
session of game play to a user at a game system.
[0115] At 902, the game system is idle or paused waiting on a
player to provide the game system with a purported item of
value.
[0116] At 904, the game system receives a purported item of
value.
[0117] At 906, the game system validates the purported item of
value. If the purported item of value is not successfully
validated, the purported item of value may be ejected from the game
system, and the process returns to 902. If the purported item of
value is a valid item, the process continues to 908.
[0118] At 908, the game system provides or sends an authorization
request to the system controller.
[0119] At 910, the game system receives account information
indicative of an entertainment credit amount.
[0120] At 912, the game system totals a number of available
entertainment credits. The game system determines whether the total
number of available entertainment credits is above a threshold, and
if so, enables the player to commence a session of game play.
Otherwise, the game system may provide the player with an
indication of the current total number of available entertainment
credits and return to 902.
[0121] At 914, a session of game play is commenced. The player
purchases a first instance of game play from the total number of
entertainment credits purchased by the player. The game system
debits the player's total number of available entertainment credits
for the purchase of the first instance of game play and for each
instance of game play purchased thereafter. The game system adds
entertainment credits received by the player during the session of
game play to the player's total number of available entertainment
credits.
[0122] At 916, responsive to user input, the game system ends the
session of game play. In some situations, the session of game play
ends when the player no longer has a sufficient number of
entertainment credits to purchase another instance of game play. If
the player has zero entertainment credits, the process continues at
902.
[0123] At 918, the game system provides the system controller with
an available entertainment credit amount indicator.
[0124] At 920, the game system receives from the system controller
a ticket identifier indication. The ticket identifier indication
may be indicative of unique ticket identification information
and/or related to an account.
[0125] At 922, the game system provides a ticket with a ticket
identifier to the player.
[0126] FIG. 10 shows a process 1000 for initiating a session of
game play at the game system.
[0127] At 1002, the game system 106 receives a purported item of
value from a player.
[0128] At 1004, the validator 148 validates the purported item of
value. If the purported item of value is not valid, then at 1006
the purported item of value is rejected. The process then continues
at 1002.
[0129] However, if the purported item of value is valid, the
validator 148 determines whether the item of value is a unit of a
currency, a financial card, or a ticket. If the validated item of
value is a ticket, the process continues at 1008 where the
validator 148 determines a ticket code from the validated ticket.
The ticket code may be a portion of the ticket identifier which is
read by the validator 148 or may be indicative of the ticket
identifier.
[0130] Referring back to 1004, if the validated item of value is a
unit of currency, the process continues 1010. At 1010, the pseudo
ticket code generator 158 receives currency IOV information.
Currency IOV information may be indicative of, among other things,
a denomination for the validated unit of a currency, the respective
currency of the unit of a currency, and other information such as a
serial number or a portion of a serial number for the unit of a
currency.
[0131] At 1012, the pseudo ticket code generator increments/rolls a
currency counter. The currency counter may be incremented from zero
to ninety-nine, and then roll to zero.
[0132] Referring back to 1004, if the validated item of value is a
financial card, the process continues 1014. At 1014, the pseudo
ticket code generator 158 receives financial medium IOV
information. Financial medium IOV information may be indicative of,
among other things, a monetary amount, a financial account, and
other information such as a transaction confirmation from a
financial institution associated with the financial card.
[0133] At 1016, the pseudo ticket code generator increments/rolls a
financial medium counter. The financial medium counter may be
incremented from zero to ninety-nine, and then roll to zero. In
some embodiments, block 1016 may be optional.
[0134] At 1018, the pseudo ticket code generator 158 generates a
pseudo ticket code. The generated pseudo ticket code may be based
at least in part on the currency IOV information and/or the count
of the currency counter if the validated item of value is a unit of
a currency. However, if the validated item of value is a financial
card, the pseudo ticket code generator 158 generates a pseudo
ticket code that may be based at least in part on the financial
medium IOV information and/or the count of the financial medium
counter. In some embodiments, one counter may be used to count the
number of selected types of non-ticket based purchases, and an
indication of the count of that counter may be included in a pseudo
ticket code.
[0135] At 1020, the session requester 160 generates a session
request. If the validated item of value is a ticket, the session
request may be based at least in part on the ticket code from the
validator 148. However, if the validated item of value is not a
ticket, the session request may be based at least in part on the
pseudo ticket code from the pseudo ticket code 158.
[0136] At 1022, the session requester 160 sends the session request
to the system controller 116.
[0137] At 1024, the session controller 162 receives game
authorization from the system controller 116. The game
authorization may indicate whether the game system 106 should or
should not provide an instance of game play to the player. If the
game authorization indicates the game system 106 should not provide
an instance of game play to the player, the process continues at
1002. A denial of an instant of game play may be based at least on
an account associated with the validated ticket having insufficient
credits for an instance of game play, e.g., the ticket may have
already been redeemed. However, if the game authorization indicated
that an instance of game play was authorized, the process continues
at 1026 where a session of game play is started.
[0138] FIG. 11 shows a process 1100 for granting/denying session
authorization at a game system.
[0139] At 1102, the system controller 116 receives a session
request from a game system 106.
[0140] At 1104, the system controller 116 determines the identity
of the item of value provided to the game system 106. In some
embodiments, the session request may include a ticket code field
having a number of data carrier elements. Certain ones of the data
carrier elements may be set to indicate that the item of value
provided to the game system 106 is a unit of a currency, and, in
some embodiments, the currency of the unit of a currency, or a
financial card. Similarly, certain ones of the data carrier
elements may be set to indicate a financial amount or a
denomination, and may also indicate a count. In addition, the
ticket code field may be indicative of a ticket code such as unique
ticket identification information encoded by a ticket identifier.
If the system controller 116 determines the identity of the item of
value provided to the game system 106 was a ticket, the process
continues at 1106.
[0141] At 1106, the system controller 116 identifies a credit
account associated with the ticket provided to the game system 106.
The identification of the credit account may be based at least in
part on information carried by the ticket code field. The carried
information may be indicative of a ticket code and/or indicative of
unique ticket identification information.
[0142] Referring back to 1104, if the system controller 116
determines the identity of the item of value provided to the game
system 106 was a unit of a currency based at least in part on the
received session request, the process continues at 1108. At 1108,
the system controller 116 identifies a currency for the received
unit of a currency based at least in part on the received session
request. In some embodiments, the system controller 116 can
selectively determine that some currencies may be used to purchase
an instance of game play and that other currencies may not be used
to purchase an instance of game play. For example, the currency of
the United States of America may be permitted, but the currency of
Cuba may not be permitted. If the system controller 116 determines
that the currency of the unit of a currency is not permitted, the
process continues at 1118, where the control system 116 may
determine that there are zero available entertainment credits.
Otherwise, the process continues at 1110.
[0143] At 1110, the system controller 116 determines an exchange
rate between the currency of the unit of a currency and another
currency, which may be the local currency. It should be noted that
in some embodiments, the game-entertainment system 100 may accept
only one type of currency, and consequently block 1110 may be
optional in those embodiments.
[0144] At 1112, the system controller 116 determines a denomination
of the unit of a currency based at least in part on the received
session request. In some embodiments, the system controller 116 can
selectively determine that some denominations may be used to
purchase an instance of game play and that other denominations may
not be used to purchase an instance of game play. For example, a
denomination of 50 for a U.S. fifty dollar bill may be permitted,
but a denomination of 100 for a U.S. one-hundred dollar bill may
not be permitted. If the system controller 116 determines that the
denomination of the unit of a currency is not permitted, the
process continues at 1118, where the control system 116 may
determine that there are zero available entertainment credits. In
some situations, an operator of the game-entertainment system 100
may want to reject certain denominations while permitting other
denominations such as when the operator has reason to suspect
counterfeit bills of a certain denomination are currently being
circulated.
[0145] Referring back to 1104, if the system controller 116
determines the identity of the item of value provided to the game
system 106 was a financial medium based at least in part on the
received session request, the process continues at 1114. In some
situations, the system controller 116 might determine an exchange
rate if the financial medium employs a currency different from a
local currency.
[0146] At 1114, the system controller 116 may determine a purchase
amount based at least in part on the determined denomination and
the determined exchange rate if the item of value provided to the
game system 106 was a unit of a currency. However, if the item of
value provided to the game system 106 was a financial card, the
system controller 116 may determine a purchase amount based at
least in part on the received session request.
[0147] At 1116, the system controller 116 opens an account and may
associate the account with a number of entertainment credits based
at least in part on the determined purchase amount.
[0148] At 1118, the system controller 116 determines a number of
available entertainment credits. The number of available
entertainment credits may be associated with the newly opened
account if the item of value received at the game system 106 was
not a ticket. However, if the item of value received at the game
system 106 was a ticket, the number of available entertainment
credits may the credit amount of the account that is associated
with the ticket. In some situations, the ticket may have already
been redeemed and improperly thrown away. In that case, the number
of available entertainment credits may be zero.
[0149] At 1120, the system controller 116 sends a session
authorization to the game system. The session authorization may be
indicative of a grant or denial of authorization for access to an
instance of game play. The session authorization may be indicative
of a number of available entertainment credits.
[0150] At 1122, the system controller 116 zeros the number of
entertainment credits associated with the account and closes the
account.
[0151] The above description of illustrated embodiments, including
what is described in the Abstract, is not intended to be exhaustive
or to limit the embodiments to the precise forms disclosed.
Although specific embodiments of and examples are described herein
for illustrative purposes, various equivalent modifications can be
made without departing from the spirit and scope of the disclosure,
as will be recognized by those skilled in the relevant art. The
teachings provided herein of the various embodiments can be applied
to ticket payment systems, not necessarily the exemplary
game-entertainment system generally described above.
[0152] For instance, the foregoing detailed description has set
forth various embodiments of the devices and/or processes via the
use of block diagrams, schematics, and examples. Insofar as such
block diagrams, schematics, and examples contain one or more
functions and/or operations, it will be understood by those skilled
in the art that each function and/or operation within such block
diagrams, flowcharts, or examples can be implemented, individually
and/or collectively, by a wide range of hardware, software,
firmware, or virtually any combination thereof. In one embodiment,
the present subject matter may be implemented via Application
Specific Integrated Circuits (ASICs). However, those skilled in the
art will recognize that the embodiments disclosed herein, in whole
or in part, can be equivalently implemented in standard integrated
circuits, as one or more computer programs running on one or more
computers (e.g., as one or more programs running on one or more
computer systems), as one or more programs running on one or more
controllers (e.g., microcontrollers) as one or more programs
running on one or more processors (e.g., microprocessors), as
firmware, or as virtually any combination thereof, and that
designing the circuitry and/or writing the code for the software
and or firmware would be well within the skill of one of ordinary
skill in the art in light of this disclosure.
[0153] In addition, in one embodiment, the IOV subsystem may be
communicatively coupled to a remote server/computer system, and the
remote server/computer system may generate a pseudo ticket code
when an item of value is not a ticket. The remote server/computer
system may provide the pseudo ticket code to the IOV subsystem
which may then provide the pseudo ticket code to the game session
subsystem.
[0154] In addition, those skilled in the art will appreciate that
the mechanisms of taught herein are capable of being distributed as
a program product in a variety of forms, and that an illustrative
embodiment applies equally regardless of the particular type of
signal bearing media used to actually carry out the distribution.
Examples of signal bearing media include, but are not limited to,
the following: recordable type media such as floppy disks, hard
disk drives, CD ROMs, digital tape, and computer memory; and
transmission type media such as digital and analog communication
links using TDM or IP based communication links (e.g., packet
links).
[0155] The various embodiments described above can be combined to
provide further embodiments. To the extent that they are not
inconsistent with the specific teachings and definitions herein,
all of the U.S. patents, U.S. patent application publications, U.S.
patent applications, foreign patents, foreign patent applications
and non-patent publications referred to in this specification
and/or listed in the Application Data Sheet are incorporated herein
by reference, in their entirety. Aspects of the embodiments can be
modified, if necessary, to employ systems, circuits and concepts of
the various patents, applications and publications to provide yet
further embodiments.
[0156] These and other changes can be made to the embodiments in
light of the above-detailed description. In general, in the
following claims, the terms used should not be construed to limit
the claims to the specific embodiments disclosed in the
specification and the claims, but should be construed to include
all possible embodiments along with the full scope of equivalents
to which such claims are entitled. Accordingly, the claims are not
limited by the disclosure.
* * * * *