Language selection

Search

Patent 2626207 Summary

Third-party information liability

Some of the information on this Web page has been provided by external sources. The Government of Canada is not responsible for the accuracy, reliability or currency of the information supplied by external sources. Users wishing to rely upon this information should consult directly with the source of the information. Content provided by external sources is not subject to official languages, privacy and accessibility requirements.

Claims and Abstract availability

Any discrepancies in the text and image of the Claims and Abstract are due to differing posting times. Text of the Claims and Abstract are posted:

  • At the time the application is open to public inspection;
  • At the time of issue of the patent (grant).
(12) Patent Application: (11) CA 2626207
(54) English Title: SYSTEMS, APPARATUS AND METHODS FOR REDEEMING TICKETS FOR ON-LINE LOTTERIES AND ON-LINE GAMES
(54) French Title: SYSTEME, DISPOSITIF ET METHODE DE REMBOURSEMENT DE BILLETS POUR LOTERIES ET JEUX EN LIGNE
Status: Deemed Abandoned and Beyond the Period of Reinstatement - Pending Response to Notice of Disregarded Communication
Bibliographic Data
(51) International Patent Classification (IPC):
  • A63F 3/06 (2006.01)
  • G06Q 50/34 (2012.01)
  • G07C 15/00 (2006.01)
(72) Inventors :
  • RANDHAWA, BHUPINDER (Canada)
(73) Owners :
  • LOTTO CHECK CORPORATION
(71) Applicants :
  • LOTTO CHECK CORPORATION (Canada)
(74) Agent: BHUPINDER SINGH RANDHAWARANDHAWA, BHUPINDER SINGH
(74) Associate agent:
(45) Issued:
(22) Filed Date: 2007-10-11
(41) Open to Public Inspection: 2009-04-11
Availability of licence: N/A
Dedicated to the Public: N/A
(25) Language of filing: English

Patent Cooperation Treaty (PCT): No

(30) Application Priority Data: None

Abstracts

English Abstract


An on-line lottery player can create a player account with a lottery operator
and
associate on-line lottery tickets with the player account. The player may
access the
player account and obtain results for the tickets. The player may select one
or more
winning tickets and create a prize redemption voucher for the selected
tickets. Prizes
won on all of the selected tickets can be redeemed by scanning or otherwise
processing
the prize redemption voucher at a ticket vending terminal. Similarly, a player
may
purchase on-line game tickets and redeem prizes won on the on-line game
tickets using
a prize redemption voucher.


Claims

Note: Claims are shown in the official language in which they were submitted.


I claim:
1. Systems, apparatus and methods as described herein.
-83-

Description

Note: Descriptions are shown in the official language in which they were submitted.


CA 02626207 2007-10-11
Title: Systems, Apparatus and Methods for Redeeming Tickets
for On-line Lotteries and On-line Games
Field
[01] The present invention relates to on-line lotteries and on-line games.
More
particularly it relates to systems, apparatus and methods that allow a player
to redeem
tickets for on-line lotteries and on-line games.
Background
[02] Many governmentally operated or licensed authorities operate a lottery in
which a player is permitted to select a set of played numbers from a larger
set of
numbers. The lottery operators use a lottery computer system to operate the
lottery.
The processes of purchasing tickets, checking tickets to determine if they
have won a
prize and redeeming prizes have various inconveniences. In particular, the
process of
redeeming prizes requires players to present individual winning tickets to
ticket vendors
to obtain prizes won by the tickets.
[03] It is desirable to provide improved systems and methods for redeeming
prizes for on-line lottery.
[04] Similarly, some lottery operators offer on-line games in which players
select several events from a list of events and predict the outcome of the
events. If the
player's predictions are correct (or otherwise meet a criteria set by the
lottery operator),
the player wins a prize. The process of redeeming such prizes is also
inconvenient.
[05] It is also desirable to provide improved systems and methods for
redeeming prizes for on-line games.
Summary
[06] The present invention provides systems, apparatus and methods for
redeeming prizes for on-line lotteries or on-line games.
[07] In one embodiment, a player establishes a player account with a lottery
operator who operates an on-line lottery using a lottery computer system. The
player
may purchase tickets for the on-line lottery and associate the tickets with
the player's
-1-

CA 02626207 2007-10-11
account. The player may then access the player's account using a player
terminal and
review the status of tickets associated with the player's account. The player
may select
unredeemed winning tickets associated with the player's account and request a
prize
redemption voucher. A prize redemption voucher record is stored in the lottery
computer system. The prize redemption voucher record has a prize redemption
voucher code and includes a list of the selected winning tickets, associating
the
selected winning tickets with the prize redemption voucher. The player obtains
a prize
redemption voucher that includes a machine readable version of the prize
redemption
voucher code. The player may redeem all prizes for the selected winning
tickets
associated with the prize redemption voucher may scanning the prize redemption
voucher code on the prize redemption voucher at a ticket vending terminal. The
ticket
vending terminal transmits the prize redemption voucher code to the lottery
computer
system. The lottery computer system identifies each of the winning tickets
associated
with the prize redemption voucher as having been redeemed and authorizes the
ticket
vending terminal to provide all prizes for the winning tickets to the player.
[08] Another embodiment provides a lottery computer system that includes a
lottery database for recording ticket records relating to issued tickets and
prize
redemption voucher records relating to prize redemption vouchers, a ticket
server for
issuing tickets and authorizing the issuance and prizes, and a player account
server for
allowing players to create player accounts, providing a ticket checking
service and for
allowing players to create prize redemption vouchers. In the lottery database,
at least
some of the ticket records relate to winning lottery tickets. Some of the
winning tickets
are associated with a player's account. The player account server is adapted
to receive
a redemption voucher request from the player wherein the prize redemption
voucher
request identifies one or more selected unredeemed winning tickets associated
with the
player's account. In response to the prize redemption voucher request, the
player
account server is adapted to create a prize redemption voucher record having a
prize
redemption voucher code and identifying the selected winning tickets. The
player
account server is adapted to provide the player with a version of the prize
redemption
voucher code that may be transmitted or otherwise provided to a ticket vending
terminal. In some embodiments, the player receives a document that may be
printed in
-2-

CA 02626207 2007-10-11
paper form that includes a printed machine readable version of the prize
redemption
voucher code. For example, in some embodiments the printed machine readable
version of the prize redemption voucher code may be set in machine readable
characters, a single or multi-dimensional bar code or other scannable form. In
some
embodiments, the player may receive a version of the prize redemption voucher
code
that the player may display on the screen of a portable player terminal and
which may
be scanned at a ticket vending terminal from the screen. In some embodiments,
a
portable player terminal may be adapted to transmit the prize redemption
voucher code
to a ticket vending terminal in a radio frequency, optical or electronic
signal.
[09] In response to receiving the ticket vending terminal code, the ticket
vending terminal is adapted transmit the ticket purchase voucher code, or a
version of it,
to the ticket server. The ticket server, in response to receiving the prize
redemption
voucher code, is adapted to identify the selected unredeemed winning tickets
as having
been redeemed in the lottery database and to transmit a redemption
confirmation
message to the ticket vending terminal. In response to the redemption
confirmation
message, the ticket vending terminal is, in the case of ticket vendor operated
ticket
vending terminal, adapted to display an instruction to provide the prizes
associated with
the selected winning tickets to the player, or, in the case of a player
operated ticket
vending terminal, to provide the prizes associated with the selected winning
tickets to
the player.
[10] Another embodiment provides a prize redemption voucher record in a
lottery database. The prize redemption voucher has a prize redemption voucher
code
and includes a reference to at least one unredeemed winning tickets associated
with a
player account.
[11] Another embodiment provides a prize redemption voucher record having a
prize redemption voucher code. The prize redemption voucher code identifies
the prize
redemption voucher in a lottery database, wherein the prize redemption voucher
is
associated with at least one unredeemed winning ticket.
[12] The embodiments of the invention may be used to obtain prize redemption
voucher associated with winning on-line lottery or on-line game tickets. In
some
embodiments, a player may be able to use a prize redemption voucher for both
on-line
-3-

CA 02626207 2007-10-11
lottery and on-line game tickets.
[13] Additional aspects of the present invention are identified below in the
description of several example embodiments.
Brief Description of the Drawings
[14] Several exemplary embodiments of the present invention will now be
described in detail with reference to the drawings, in which:
Figure 1 is a block diagram of a system for redeeming tickets;
Figures 2 to 5 illustrate example ticket purchase voucher creation screens
and a ticket purchase vouchers according to the embodiment of Figure 1;
Figures 6a-c illustrates part of a lottery database according to the
exemplary embodiment of Figure 1;
Figure 7 is a flowchart illustrating a method of creating a player account;
Figure 8 illustrates a welcome web page of a player website of the
embodiment of Figure 1;
Figure 9 is a flowchart illustrating a method for creating and printing a
ticket purchase voucher;
Figure 10 illustrates a ticket purchase voucher selection page of the player
website;
Figure 11 is a flowchart illustrating a method for a player to purchase a
ticket and for a lottery operator to correspondingly sell the ticket to a
player;
Figure 12 illustrates a ticket purchase voucher for purchasing multiple
tickets;
Figure 13 illustrates another system for redeeming tickets;
Figure 14 illustrates a player identification device and a selection slip;
Figure 15 illustrates part of a lottery database of the embodiment of Figure
13;
Figure 16 is a flowchart illustrating a method for a player to purchase a
ticket and for a lottery operator to correspondingly sell the ticket to a
player using an
account identification device;
Figure 17 is a flowchart illustrating a method for updating draw records for
-4-

CA 02626207 2007-10-11
draws of on on-line lotteries and for checking on-line lottery tickets;
Figure 18 is a flowchart illustrating a method for updating event records for
events in on-line games and for checking on-line game tickets;
Figure 19 is a flowchart illustrating a method or providing an account
checking service;
Figure 20 illustrates a on-line lottery ticket summary report setting out
information about a player's on-line lottery tickets and allowing the player
to obtain a
prize redemption voucher;
Figure 21 is a flowchart illustrating a method by which a player may obtain
a prize redemption voucher;
Figure 22 illustrates an example prize redemption voucher; and
Figure 23 is a flowchart illustrating a method by which a player may use a
prize redemption voucher to redeem prizes for one or more winning tickets.
Detailed Description of Example Embodiments
[15] As used herein, the word "exemplary" refers to examples of various items
and does not denote a preferred or necessary feature of any embodiment or of
the
invention.
[16] A first example embodiment of the invention will be described with
reference to several exemplary on-line lotteries and on-line games.
[17] The first exemplary on-line lottery will be referred to as Lotto 7/47. In
this
on-line lottery, a lottery player selects a set of seven different played
numbers between
1 and 47 (inclusive of numbers 1 and 47). The set of seven played numbers is
referred
to as a Lotto 7/47 played number set. Subsequently, a lottery operator
conducts a draw
to select a set of winning numbers consisting of seven different regular
numbers and a
bonus number, also between 1 and 47. The bonus number is different from all of
the
winning numbers. The player may win different prizes if his played numbers
match the
winning numbers and/or the bonus number in various winning combinations, as
follows:
Winning Combination Prize Won
7/7 regular numbers Grand Prize
6/7 regular numbers and Second Prize
-5-

CA 02626207 2007-10-11
bonus number
6/7 regular numbers Third Prize
5/7 regular numbers Fourth Prize
4/7 regular numbers Fifth Prize
3/7 regular numbers and Sixth Prize
bonus number
3/7 regular numbers Free ticket
[18] Some of the prizes a player may win in this exemplary on-line lottery are
shared prizes. Shared prizes are calculated by first determining a total prize
amount for
a particular winning combination and then dividing the total prize value by
the number of
tickets that have the winning combination to determine what share of the total
prize
amount each ticket will win. The Grand Prize is a shared prize and the total
prize value
for the Grand Prize is determined by the lottery operator prior to each draw
of the on-
line lottery. For example, if the total prize value for the Grand Prize is $10
million and 4
tickets have the 7/7 regular numbers winning combination, then each ticket
wins $2.5
million. Some shared prizes may be pari-mutuel prizes, for which the total
prize amount
may be determined as a portion of the ticket sales revenue for the on-line
lottery. The
second, third, fourth, fifth and sixth prizes are pari-mutuel prizes. One of
the prizes is a
fixed prize with the same prize being awarded for each ticket having the
specified
winning combination. The free ticket prize for the 3/7 regular numbers winning
combination is a fixed prize. The present invention may be used with on-line
lotteries
and games having any type or any combination of types of prizes.
[19] For the purpose of this exemplary embodiment of the invention, the
lottery
operator conducts a draw of the Lotto 7/47 on-line lottery each week on Friday
at 9 p.m.
Eastern Standard Time.
[20] The second exemplary on-line lottery will be referred to as Tag. In this
on-
line lottery, a six digit played number is automatically selected for the
lottery player. The
played number may be referred to as a Tag played number. The single six digit
played
number is a played number set for the Tag on-line lottery and may also be
referred to as
a Tag played number set. Subsequently, the lottery operator selects a six
digit winning
number for the Tag on-line lottery. The winning number may be referred to as a
Tag
-6-

CA 02626207 2007-10-11
winning number or a Tag winning number set. The player may win different
prizes if
various winning combinations of digits in his played number match
corresponding digits
in the winning number, as follows:
Winning combination Prize Won
All six digits $250,000
Last five digits $1,000
Last four digits $100
Last three digits $25
First digit and last digit $5
First digit Free play of host on-
line lottery with Tag
Last digit Free play of host on-
line lottery with Tag
[21] This exemplary Tag on-line lottery may only be played in conjunction with
another on-line lottery, such as the Lotto 7/47 on-line lottery described
above. The
Lotto 7/47 on-line lottery is referred to as a host on-line lottery and the
Tag on-line
lottery is referred to as an associated on-line lottery. A player may request
that one or
more Tag played number sets be added to a ticket for the Lotto 7/47 on-line
lottery. On
draw dates for the Lotto 7/47 on-line lottery, the lottery operator draws a
winning
number set for the host Lotto 7/47 and also draws a winning number for the
associated
Tag on-line lottery.
[22] The prize for matching the first or the last digit of the Tag winning
number
is a free play of the host on-line lottery in the next draw after the ticket
is redeemed,
including a free played number for the Tag on-line lottery draw on the same
date.
Players who elect to play the Tag on-line lottery on a ticket may win a prize
in the Lotto
7/47 on-line lottery, the Tag on-line lottery or in both on-line lotteries.
[23] The third exemplary on-line lottery will be referred to as Keno. In this
on-
line lottery, a lottery player is asked to select a play category between two
and ten. If
the player chooses play category two, he then chooses a set of two different
played
numbers between 1 and 70 (inclusive of numbers 1 and 70). Similarly, if the
player
chooses play category ten, the player chooses a set of ten different played
numbers
-7-

CA 02626207 2007-10-11
between 1 and 70. Similarly, if the player chooses any of play categories
three to nine,
the player chooses a corresponding amount of different played numbers between
1 and
70. The player's set of played numbers is referred to as a Keno played number
set.
Subsequently, the lottery operator conducts a draw to select a winning number
set
consisting of 20 different winning numbers between 1 and 70. The player may
win a
prize depending on the play category chosen and how many of the played numbers
match the winning numbers. Various winining combinations are defined as
follows:
Play Category Winning Wager multiplier
(played numbers combination
in set)
2 2 of 20 7
3 3 of 20 25
4 4 of 20 100
5 5 of 20 250
4 of 20 5
6 6 of 20 1,000
5 of 20 25
7 7 of 20 5,000
6 of 20 50
5 of 20 5
8 8 of 20 25,000
7 of 20 200
6 of 2() 10
9 9 of 20 50,000
8 of 20 1,000
7 of 2() 100
6 of 20 5
10 of 20 250,000
9 of 20 5,000
8 of 20 200
7 of 20 25
-8-

CA 02626207 2007-10-11
O of 20 2
[24] If the player's played number set includes a winning combination, the
player is awarded a prize equal to the amount wagered by the player for the
set of
played numbers multiplied by the wager rnultiplier. For example, a player who
chooses
play category seven will choose a set of seven different played numbers
between 1 and
70. In this exemplary Keno on-line lottery, the player may wager from $1, $2,
$5 or $10
for each set of played numbers. If the seven played numbers match seven of the
twenty winning numbers, the player wins ~5,000 times the amount wagered.
[25] For the purpose of this example, the lottery operator conducts a draw of
the Keno on-line lottery every day at 9 p.m. Eastern Standard Time.
[26] The Keno on-line lottery is not a host lottery for the Tag on-line
lottery. In
an alternative embodiment of the invention, the Keno on-line lottery could
also be a host
lottery for the Tag on-line lottery.
[27] A played number set or played number for an on-line lottery that includes
a winning combination may be referred to as a winning played number set or as
a
winning played number. A ticket that includes at least one winning played
number set
or winning played number may be referred to as a winning on-line lottery
ticket, a
winning lottery ticket or more generally as; a winning ticket.
[28] Two exemplary on-line games used in this description of exemplary
embodiments of the invention will be referred to as Sports Line and
Over/Under. In
these exemplary on-line games, each week the lottery operator identifies a
number of
sporting events and sets various odds corresponding to various possible
outcomes of
the events. For example, part of a list of odds may include the following
events and
corresponding odds for the Sports Line and the Over/Under on-line games:
LIST 8845 (November 11 - November 17, 2005)
Teams Sports Line Over / Under
Event Time Visitor Home V T H 0
Saturday November 12, 2005
College Football
17 12:OOp Texas A&M Oklahoma 5.2 4.0 1.2 1.7 36.5 1.7
18 12:OOp Maryland North Carolina 2.6 .3.0 2.0 1.7 37.5 1.7
23 2:OOp Kentucky Vanderbilt 5.0 3.9 1.3 1.7 33.5 1.7
- 9 -

CA 02626207 2007-10-11
30 J 6:OOp Washington Arizona 5.2 4.0 1.2 1.7 36.5 1.7
NHL Hockey
44 j1:OOp Washington New Jersey 2.2 1 6.5 1.5 1.7 6.5 1.7
45 7:00p Toronto Montreal 2.0 J6.0 1.6 1.7 5.5 1.7
Sunday November 13, 2005
NFL Football
56 1:OOp Kansas City Buffalo 2.4 2.8 2.3 1.7 43.5 1.7
57 1:OOp San Chicago 5.2 4.0 1.2 1.7 44.5 1.7
Francisco
60 9:OOp Dallas Philadelphia 2.5 2.9 2.1 1.7 43.5 1.7
NHL Hockey
87 8:OOp Dallas Anaheim 1.7 6.0 1.9 1.7 5.5 1.7
88 10:OOp Detroit Vancouver 1.9 6.0 2.0 1.8 5.5 1.6
[29] The list of events may be referred to herein as an event list. The odds
for
the Sports Line on-line game are set out under the three columns labeled "V",
"T" and
"H" under the heading "Sports Line". For each event, three possible outcomes
may
occur: "V" means that the visiting team wins the event; "T" means that the two
teams will
tie and "H" means that the home team will win the event. The definition of a
win or tie is
set by the lottery operator and may not rnatch the rules used in the actual
event. For
example, in this exemplary Sports Line on-line game, for NFL football games
the lottery
operator has defined a tie as the teams having three or fewer points
separating them in
the final score. For some events, a tie may not be defined - such as for
baseball
games, where the rules do not provide for tie games. The odds indicate the
lottery
operator's estimate of how likely each outcome is. A higher value indicates
that the
lottery operator believes the outcome is less likely to occur.
[30] In this exemplary Sports Line on-line game, the lottery operator has
specified that a player may make a bet by selecting between three and six
events and
specifying a wager amount. If the player correctly predicts the outcome of all
of the
selected events, the player wins the bet and wins a prize. The predictions
made by the
player are collectively referred to as a Sports Line prediction set.
[31] A payout value for the Sports Line prediction set is calculated by
multiplying the player's wager by the odds for all of the predicted outcomes.
For
-10-

CA 02626207 2007-10-11
example, if a player wagers $5 and predicts that Syracuse will beat Pittsburgh
in event
12, Nashville will beat Colorado in event 33 and that Dallas will tie Tampa
Bay in event
43, then the payout value is $5 x 4.0 x 3.0 x 1.2 = $72. If the player
successfully
predicts the outcome of all three games, the player receives the payout value
as his or
her prize.
[32] The odds for the Over/Under on-line game are set out under the three
columns marked "0", "#" and "U". The value in the "#" column indicates the
threshold
number of points. A player may predict that the combined scores of the teams
in each
event will be over this threshold number of points or under it. The outcome of
the event
is "Over" if the total points scored by the teams is over the threshold. The
outcome of
the event is "Under" if the total points scored by the teams is under the
threshold. For
example, in event 32, a player who wishes to make a bet using the over/under
odds for
this event may bet that Washington and Toronto will score over or under 5.5
goals in
their hockey game. In this exemplary Over/Under on-line game, the player makes
a bet
by selecting between two and six events and predicting whether the outcome
will be
Over or Under the threshold in each event. The player also selects a wager
amount for
the bet. The predictions made by the player are collectively referred to as an
Over/Under prediction set. A payout value for the Over/Under prediction set is
determined by multiplying the player's wager by the odds of the all of the
predicted
outcomes. The player wins the bet and is entitled to receive the payout value
if all of
the player's predictions are correct.
[33] In event list 8845, each event is shown with odds for the Sports Line on-
line game and for the Over/Under on-line game. In this example, the two on-
line games
are separate and a lottery operator may optionally use different selection
slips to allow
players to make bets in the different on-line games. Alternatively, a single
selection slip
allowing bets to be made on either or both of the on-line games may be used.
In
another on-line game, players could be permitted to make bets that have both
Sports
Line and Over/Under outcomes selected.
[34] In this example system 100, the lottery operator provides event lists on
a
weekly basis. In other embodiments, the lottery operator may provide event
lists which
have time periods that overlap with other event lists, or may provide events
lists that
-11-

CA 02626207 2007-10-11
have some events in common. In other embodiments, the lottery operator may not
divide events into lists and may simply having single event list. In
embodiments in
which players will be permitted to purchase on-line game tickets using
selection slips in
addition to using the systems, apparatus and methods disclosed herein, the
lottery
operator will typically identify events as part of an event list to permit the
event list to be
identified on a selection slip.
[35] An on-line game ticket on which a player has won his or her bet may be
referred to as a winning on-line game ticket, a winning game ticket or more
generally as
a winning ticket. In both the Sports Line and Over/Under on-line games
described
above, all of the predictions made by a player in the prediction set must be
correct for
the player to win the bet. In other embodiments, an on-line game ticket will
be a
winning on-line game ticket as long as the prediction set on the ticket (or at
least one of
the prediction sets, if multiple predictions sets are permitted on a single
ticket) matches
the appropriate corresponding criteria set by the lottery operator.
[36] In system 100, a player establishes a player account with the lottery
operator. The player then purchases tickets, which are associated with the
player's
account as they are purchased. Several methods for purchasing tickets and
associating
the tickets with a player account are described below. The invention is not
limited to
any particular method of buying tickets and associating the tickets with a
player account
and methods other than those described here may be used to do so.
[37] In one method of buying a ticket and associating it with a player's
account,
the obtains a ticket purchase voucher using a player terminal. The ticket
purchase
voucher encodes information related to a proposed ticket. The player then
presents the
ticket purchase voucher to a ticket vendor, who uses the ticket purchase
voucher to sell
a ticket corresponding to the proposed ticket to the player. The player
receives a ticket
receipt setting out information about the ticket. In some embodiments, the
player may
be able to use the ticket purchase voucher to purchase the ticket at a player
operated
ticket vending terminal.
[38] Players may also use a player terminal to obtain a prize redemption
voucher that corresponds to one or more winning tickets associated with the
player's
account. The player presents the prize redemption voucher to a ticket vendor.
The
-12-

CA 02626207 2007-10-11
ticket vendor validates the prize redemption voucher using a ticket vending
terminal and
gives the player the prizes won on all of the winning tickets corresponding to
the prize
redemption voucher.
[39] The lottery operator operates a lottery computer system. In the present
embodiment, the lottery computer system includes a player account server. A
lottery
player uses a player terminal to access the player account server and to
create a player
account. Each player account has an account identification code or user name.
The
account identification code for each account is unique (with respect to the
account
identification code for all other player accounts created in the particular
embodiment)
and may consist of any combination or permutation of letters or numerals. In
this
description of the first example embodiment, several exemplary player accounts
will be
described. The account identification codes for these exemplary player
accounts
include KARINA1022, BRIAN237 and SAMANTHA.
[40] In any particular embodiment, a lottery operator may impose requirements
on the account identification codes that players may use. For example, a
lottery
operator may set a minimum or maximum number of characters for an account
identification code. In the present embodiment, an account identification code
may
include the same character (i.e. the same letter or numeral) more than once.
[41] In other embodiments, the lottery operator may require that each
character in an account identification code be different from the other
characters in an
account identification code. This requirement may be imposed in the lottery
operator
also permits players to purchase tickets using a selection slip with an
account
identification region, as is described in PCT patent application No.
PCT/CA2006/000270, International Publication Number WO 2006/092039A1.
[42] Figure 1 illustrates a system 100 that includes a lottery computer system
102, ticket vending terminals 104 and player terminals 106. A system according
to the
present embodiment will include at least one ticket vending terminal 104 and
at least
one player terminal 106.
[43] The lottery computer system 102 is operated by a lottery operator (not
shown), who may operate various types of on-line lotteries and on-line games,
including
the exemplary on-line lotteries and on-line games described above and other on-
line
-13-

CA 02626207 2007-10-11
lotteries or on-line games.
[44] Some of the ticket vending terminals 104 are operated by ticket vendors
(not shown). Some ticket vending terminals 104 may also be player operated
terminals,
which a player may use without the assistance of a ticket vendor. The
description
below is generally set out in terms of ticket vending terminals that are
operated by ticket
vendors. A player operated ticket vending terminal may be used in a manner
similar to
a ticket vendor operated ticket vending terminal.
[45] Each ticket vending terminal 104 is coupled, or is capable of being
coupled, to the lottery computer system 102 to permit data communication
between the
ticket vending terminal 104 and the lottery computer system 102. Some of the
ticket
vending terminals 104 may be coupled to the lottery computer system 102
through a
private communication network 108. The private communication network 108 may
be a
wide area network (WAN), a private data communication network comprising
proprietary
(owned, rented or leased) data lines or any other type of data network. The
private
communications network 108 may be a combination of two or more of these and
other
types of data communication networks. Ticket vending terminals 104b and 104c
are
coupled to the lottery computer system 102 through private communication
network
108.
[46] Some or all of the ticket vending terminals 104 may be coupled to the
lottery computer system 102 through dial-up telephone connections or another
type of
point-to-point connection that permits data communication between the lottery
computer
system 102 and the ticket vending terminal 104. For example, ticket vending
terminal
104a is coupled to the lottery computer system 102 through a dial-up telephone
connection 109, which may be maintained at all times or may be established
when
required to allow data communication between ticket vending terminal 104c and
lottery
computer system 102.
[47] Some or all of the ticket vending terminals 104 may be coupled to the
lottery computer system 102 through a publicly accessible communications
network (a
"public network"), such as the Internet. For example, ticket vending terminal
104d is
coupled to the lottery computer system 102 through public network 110. Ticket
vending
terminals 104 coupled to the lottery computer system 102 through the public
network
-14-

CA 02626207 2007-10-11
110 may be coupled using a virtual private network or another secure
communications
protocol or methodology.
[48] The connections between the lottery computer system 102 and the
various ticket vending terminals 104 need not be the same. Different
connections may
be made using different types of data communications networks and lines. A
ticket
vending terminal 104 may be coupled, or may be capable of being coupled, to
the
lottery computer system 102 in more than one way, to provide an alternative
method of
communication if a primary method has failed or is unavailable.
[49] The connection between lottery computer system 102 and any particular
ticket vending terminal 104 may be persistent or it may be made intermittently
as
required for data communication between the lottery computer system 102 and
the
ticket vending terminal 104. If the coupling includes a publicly accessible
network, such
as the Internet, communications between the lottery computer system 102 and
any of
the ticket vending terminals 104 may be secured using an encryption system or
other
security technique. A security technique or mechanism may optionally be used
to
secure all communications between the lottery computer system 102 and any
ticket
vending terminal 104, regardless of the type of connection between the lottery
computer
system 102 and the ticket vending terminal 104.
[50] The ticket vending terminais 104 are used to sell tickets and provide
ticket
receipts to players. Each ticket vending terminal 104 (or at least some of the
ticket
vending terminals 104) includes a scanner or scanning device capable of
reading or
scanning machine readable information from a ticket purchase voucher. The sale
of
tickets to players is further described below.
[51] Lottery computer system 102 may be coupled to some or all of the player
terminals 106 through public network 110. Some player terminals 106 may also
be
coupled to the lottery computer system 102 directly (for example, using a dial-
up
connection) or through another network. Each of the player terminals 106 is
capable of
communicating with lottery computer system 102 and typically includes several
output
devices such as a display screen and a printer. Each player terminal 106
includes a
printer that can be used to print a ticket purchase voucher or a prize
redemption
voucher. In addition, each player terminal includes one or more input devices
(such as
-15-

CA 02626207 2007-10-11
a keypad, keyboard, computer mouse or remote control device). A player
terminal 106
may be any type of device that is capable of being coupled to and
communicating with
the lottery computer system 102. For example, different player terminals 106
may be
personal computers, Internet-enabled television sets, Internet-enabled set-top-
boxes
used with cable, satellite or other digital communication systems, portable
wireless
communications devices such as personal data assistant (PDA) devices, cellular
phones and wireless portable computers.
[52] When system 100 is in operation, a player uses a player terminal 106 to
access a ticket purchase voucher creation page 112 (Figure 2) accessible on
the lottery
operator's website. The player uses the ticket purchase voucher creation page
112 to
obtain a ticket purchase voucher 113. The ticket purchase voucher 113 includes
a
ticket purchase voucher code 136 (Figure 2) on it in a machine-readable
format, such
as a bar code. The player then presents the ticket purchase voucher to a
ticket vendor
who operates a ticket vending terminal 104. The ticket vendor uses the ticket
vending
terminal 104 to process the ticket purchase voucher 113 and to issue a ticket
receipt
114 to the player. In some embodiments, the player may also be able to use a
ticket
purchase voucher 113 to purchase tickets at a player operated ticket vending
terminal
104.
[53] A player may also use a player terminal 106 to select one or more winning
tickets associated with the player's account and obtain a prize redemption
voucher 133
corresponding to the selected winning tickets. The player then presents the
prize
redemption voucher to a ticket vendor who operates a ticket vending terminal
104. The
ticket vendor uses the ticket vending terminal 104 to process the prize
redemption
voucher 133 and gives the prizes 135 corresponding to the selected winning
tickets to
the player. In some embodiments, a player may be able to use a prize
redemption
voucher 133 at a player operated ticket vending terminal 104 to obtain the
prizes 135.
[54] Reference is next made to Figure 2, which illustrates a ticket purchase
voucher creation page 116 for the Lotto 7/47 on-line lottery, a ticket
purchase voucher
117 for the Lotto 7/47 on-line lottery and a corresponding ticket receipt 118.
[55] Ticket purchase voucher creation pages 112 are web pages that are
accessible on the lottery operator's website. A lottery operator will provide
a ticket
-16-

CA 02626207 2007-10-11
purchase creation page 112 for each on-line lottery (or on-line game) with
which it uses
the present invention. A lottery operator accesses the ticket purchase voucher
creation
pages 112 using a web browser operating on the player's terminal 106. The
player
completes the ticket purchase voucher creation page 112 and then uses it to
create a
ticket purchase voucher 113.
[56] Lotto 7/47 ticket purchase voucher creation page 116 is displayed on a
display screen (not shown) of player terminal 106b, in the example of Figure
2. Lotto
7/47 ticket purchase voucher creation page 116 includes four played number
selection
boards 121, 122, 123 and 124 in which a player may manually select up to four
played
number sets for a Lotto 7/47 ticket. Ticket purchase voucher creation page 116
also
has an auto-pick selection field 126 in which a player can select from zero to
ten
additional automatically selected played number sets for the Lotto 7/47 on-
line lottery on
the ticket. Ticket purchase voucher creation page 116 also includes a tag
selection field
128 in which a player may select from zero to ten automatically selected Tag
played
number sets for the Tag on-line lottery associated with the Lotto 7/47 on-line
lottery.
Ticket purchase voucher creation page 116 also includes an advance draw
selection
field 130 in which the player may choose from one to ten draws for which the
player
wishes to purchase a ticket.
[57] A player named Karina Jones, who's player account has the account
identification code KARINA1022, has completed the Lotto 7/47 ticket purchase
voucher
creation page 116 to manually select two played number sets. The first played
number
set includes the played numbers 8, 12, 23, 29, 32, 27 and 45. The second
played
number set includes the played numbers 2, 18, 24, 28, 33, 39 and 42. The
player has
also chosen to add 1 additional automatically selected Lotto 7/47 played
number set, 2
Tag played number sets and to purchase a ticket for four draws.
[58] Once the player has completed the ticket purchase voucher creation page,
the player clicks the "Create Voucher" button 119 to create the ticket
purchase voucher
117. The process by which ticket purchase voucher 117 is generated is
described in
greater detail below in relation to method 3000. Ticket purchase voucher is
printed at
player terminal 106b using a printer attached to the player terminal 106b.
[59] Ticket purchase voucher 117 includes a ticket information section 132 and
-17-

CA 02626207 2007-10-11
a ticket purchase voucher code section 134.
[60] Various information about the ticket is set out in ticket information
section
132, including the player account with which a ticket purchased with the
ticket purchase
voucher 117 will be associated, the played number sets selected for the ticket
and other
information. In the present example, ticket information section 132 includes
information
that a lottery operator may use to confirm the details of the players
selections for the
ticket. The ticket information section need not contain any specific
information and is
optional. Preferably, the ticket information section is provided and contains
information
that a lottery player may use to understand the played numbers and other
options for
the ticket that the ticket purchase voucher can be used to purchase.
[61] The ticket purchase code section 134 includes a machine readable ticket
purchase voucher code 136 which encodes a ticket purchase voucher code. In
this
example, the ticket purchase voucher code is set out in a bar code.
Alternatively, the
ticket purchase voucher code 136 may be set out in the ticket purchase voucher
code
section 134 in any machine readable format, such as optically scannable
characters,
single or multi-dimensional bar codes or any other machine recognizable
pattern or
character set.
[62] The ticket purchase voucher code 136 for any particular ticket purchase
voucher is different from the ticket purchase voucher code for all other
ticket purchase
vouchers that are valid at the time the particular ticket purchase voucher is
issued. A
ticket purchase voucher is valid if it can be used to purchase a ticket for an
on-line
lottery or on-line game. A ticket purchase voucher may be valid indefinitely
or it may
expire at a particular time, or when a specific event occurs or a specific
condition
becomes true. Ticket purchase voucher 117 does not expire. Karina Jones can
use the
ticket purchase voucher to purchase a ticket for the next four draws of the
Lotto 7/47 on-
line lottery whenever she chooses to purchase a ticket with the ticket
purchase voucher.
[63] In any embodiment, a lottery operator may choose to make a voucher
valid for a fixed time period, a fixed number of uses, or may set some other
expiry rule
for a ticket purchase voucher. A lottery operator may choose to use any
combination of
expiry rules for the ticket purchase vouchers used with the lottery operator's
on-line
lottery and/or on-line games. For example, in another embodiment, the lottery
operator
-18-

CA 02626207 2007-10-11
may require that a ticket purchase voucher must be used within 1 week of being
printed.
In such an embodiment, the ticket purchase voucher may optionally set out the
time at
which the ticket purchase voucher expires.
[64] The ticket information section 132 of ticket purchase voucher 117
includes
the ticket purchase voucher code set out in human readable form. It is
optional to print
the ticket purchase voucher code in human readable form in the ticket
information
section 132.
[65] Figure 2 also illustrates a ticket receipt 118 that corresponds to the
player's selections on the ticket purchase voucher creation page 116 and the
ticket
purchase voucher 117. The exemplary ticket receipt 118 includes the name 140
of the
on-line lottery indicating that it is a ticket for the Lotto 7/47 lottery, a
date range 142
indicating that it is valid for four draws between June 8, 2005 and June 18,
2005. At
reference number 144, the ticket receipt 118 sets out the two Lotto 7/47
played number
sets manually chosen by the player and an automatically selected played number
set
chosen for the player by the lottery computer system 102. The automatically
selected
Lotto 7/47 played number set consists of the played numbers 12, 17, 21, 29,
32, 37 and
43. At 148, ticket receipt 118 sets out two Tag played numbers, 398587 and
957238,
for the Tag on-line lottery and the word "Played" to indicate that the player
has chosen
to participate in the associated Tag on-line lottery.
[66] At 156, the ticket receipt sets out Karina Jones' account identification
code
KARINA1022. Optionally, a ticket receipt may set out part of a player's
account
identification code or another datum related to the player such as the
player's name.
[67] Ticket receipt 118 also contains a human readable ticket code 150, which
in this example is a sixteen digit number set out in four sets of four digits:
5933-3748-
0958-3924. A ticket code is assigned by the lottery computer system 102 to
every ticket
that is issued. In this exemplary embodiment, the ticket code is printed on
the ticket
receipt 114 in a human-readable form. The ticket code is also set out in a
machine
readable bar code 158, allowing the ticket code to be scanned by a machine,
such as a
ticket vending terminal 104. In alternative embodiments, the ticket code may
be set out
in only a human readable form or a machine readable form. In alternative
embodiment,
a first ticket code for the ticket may be set out in human readable form and a
different
-19-

CA 02626207 2007-10-11
second ticket code for the ticket may be set out in machine readable form.
[68] Typically, the ticket code allows the ticket to be uniquely identified
from all
other tickets issued by the lottery operator, at least during a selected time
period prior to
the issuance of the ticket (for example, one year or five years). The lottery
operator
may select various mechanisms for assigning ticket codes for tickets,
including
mechanisms that encode information in the ticket code. Such encoded
information may
include the particular on-line lottery or on-line game that the ticket is
issued for, the
draws the ticket is issued for and check digits that can be used to ensure the
validity of
the ticket code, the ticket receipt 118 and the ticket.
[69] Ticket receipt 118 includes a vendor terminal code 152. The vendor
terminal code 152 identifies the ticket vending terminal 104 used to issue
ticket receipt
114. Alternatively, the vendor terminal code 152 may identify the ticket
vendor who
operates the ticket vending terminal, so that tickets issued at different
ticket vending
terminals operated by the same ticket vendor have the same vendor terminal
code. In
the present exemplary embodiment, the vendor terminal code 152 uniquely
identifies
the specific ticket vending terminal 104 at which the ticket was issued, and
accordingly
different ticket vending terminals operated by the same ticket vendor are
identified by
different vendor terminal codes. Other ticket receipts 114 according to the
present
invention may not include a vendor terminal code.
[70] Ticket receipt 118 includes a verification code 154. The verification
code
154 may be used to verify the integrity of ticket receipt 114. Verification
code 154 may
be generated using a formula based on other components of the ticket and other
data
(such as the date and time on which the ticket is issued) or it may be created
for the
ticket randomly, pseudo-randomly (i.e. based on a seed value or other initial
value),
using a list of rotating values or verification codes, or using any other
formula or
method. The verification code 154 may be used in the place of, or in addition
to, the
use of check digits in the ticket code 150. Other ticket receipts 114
according to the
present invention may not include a verification code.
[71] Reference is next made to Figure 3, which illustrates a ticket purchase
voucher creation page 216 and a ticket purchase voucher 218 for the Keno on-
line
lottery and a corresponding ticket receipt 218.
-20-

CA 02626207 2007-10-11
[72] Ticket purchase voucher creation page 216 has four boards 221, 222, 223
and 224. On each board, a player may enter up to ten played numbers that form
a
played number set. In boards 221-224, a player manually types in the played
numbers
that the player wishes to choose. This differs from the selection of played
number on
boards 121-124 (Figure 2), in which a player was presented with a cell for
each number
that the player could choose as a played number. A lottery operator may choose
to
provide individual cells for the different possible numbers in a player number
set or may
allow a player to manually type in the numbers on any of its ticket purchase
voucher
creation pages. The player Karina Jones has manually selected two played
number
sets in boards 221 and 222.
[73] Ticket purchase voucher creation page 216 includes an auto-pick
selection field in which a player may choose a play category and wager for up
to ten
additional automatically selected played number sets. Optionally, a player may
choose
to purchase a ticket with only automatically selected played number sets and
may leave
all of the boards 221-224 blank.
[74] Ticket purchase voucher creation page 216 also includes an advance
draw selection field 130.
[75] Ticket purchase voucher 217 includes information about the player's
selections in a ticket information section 232 and a machine readable ticket
purchase
voucher code in a ticket purchase voucher code section 234.
[76] Ticket receipt 218 sets out the details of a ticket purchase by the
player
using ticket purchase voucher 217. In this example, the automatically selected
played
number set is identified as having been automatically selected for the player.
[77] Figure 4 illustrates an exemplary ticket purchase voucher creation page
316, a ticket purchase voucher 317 and a corresponding ticket receipt 318 for
the
Sports Line on-line game.
[78] Ticket purchase voucher creation page 316 includes an event list 321. In
this embodiment, event list 321 corresponds to the events listed above in the
description of the Sports Line on-line game. Event list 321 identifies the
various
outcomes and odds for each event that a player may select as part of a bet. To
make a
bet, a player selects from three to six events and selects one outcome per
event. The
-21-

CA 02626207 2007-10-11
player selects the outcomes by clicking the radio button beside the odds for
the
outcome.
[79] Ticket purchase voucher creation page 316 also includes wager amount
field 322, in which a player can enter a wager for a bet. In this embodiment a
player
may type in a wager amount of the player's choice. In other embodiments, the
lottery
operator may permit the player to choose from a number of predetermined wager
amounts. Optionally, the iottery operator may provide options for the
predetermined
wager amounts in the form of radio button selections, a drop down list or
another
mechanism for limiting the player's choice of the wager amount. The lottery
operator
may have a number of predetermined amounts and may also allow a player to
choose a
different wager than any of the predetermined amounts.
[80] Once a player has selected a bet by marking the player's predicted
outcomes and entering a wager, the player can obtain a ticket purchase voucher
317 by
clicking the "Create Voucher" button 119. Ticket purchase voucher 317 includes
information about the player's selections in a ticket information section 332
and a
machine readable ticket purchase voucher code in a ticket purchase voucher
code
section 334. The player must purchase a ticket prior to beginning of the
earliest event
on which the player's bet is based. In this example, the voucher states that
the voucher
must be used before 11:45am on Saturday, November 12, 2005. Ticket purchase
voucher 317 expires at that time.
[81] Ticket receipt 318 sets out the player's Sports Line prediction set at
344-
347. At 349, ticket purchase voucher 317 set out the payout value based on the
wager
and the odds for the selected outcomes.
[82] Figure 5 illustrates an exemplary ticket purchase voucher creation page
416, a ticket purchase voucher 417 and a corresponding ticket receipt 418 for
the
Over/Under on-line game.
[83] Referring to Figure 1, Lottery computer system 102 includes a lottery
database 160, a player account server 162 and a ticket server 164.
[84] Lottery computer system 102 may be a single computer or may include
various interconnected computers and other devices, including communication
and data
storage devices. Lottery database 160, player account server 162 and ticket
server 164
-22-

CA 02626207 2007-10-11
may reside and operate on one or more of the computers or related systems that
comprise lottery computer system 102. For example, portions of the player
account
server may operate on different computers which may be distributed across a
large or
small geographic area. In some embodiments, portions of the lottery computer
system
may operated by the lottery operator indirectly through a third party.
[85] Player account server 162 manages the creation of player accounts and
the creation of ticket purchase vouchers 113. Lottery players use player
terminals 106
to access player account server 162. Optionally, communications between the
lottery
computer system 102 and a player terminal 106 may be secured using an
encryption
system or other security technique. A player terminal 106 used by a player may
be
referred to as the player's terminal.
[86] Player account server 162 includes one or more player interfaces 166.
Each player interface 166 facilitates communications between the player
account server
162 and one or more of the player terminals 106. In the present embodiment,
player
interface 166a includes a player website 167a, which players may access by
using a
web browser operating on a player terminal 106, such as a personal computer or
any
other web-enabled computing device. Player interface 166a communicates with
web
browsers to receive information from the player terminals 106 and to transmit
information to the player terminals 106. For example, player interface 166a
receives
information about new player accounts and creates a corresponding player
account
record 514 in the lottery database 160. This is further described below in
relation to
method 2100.
[87] Player interface 166a receives Ticket Purchase Voucher Requests 560
from player terminals 106 and transmits ticket purchase vouchers 113 to the
player
terminals allowing ticket purchase vouchers 113 to be printed at the player
terminals.
Ticket Purchase Voucher Requests 560 and the creation of ticket purchase
vouchers
are further described below in relation to method 3000.
[88] Player interface 166a also receives Prize Redemption Voucher Requests
3220 from player terminals 106 and transmits prize redemption voucher 133
allowing
prize redemption vouchers 133 to be printed at the player terminals. Prize
Redemption
Voucher Requests 3220 and the creation of prize redemption vouchers are
further
-23-

CA 02626207 2007-10-11
described below in relation to method 3200 (Figure 22).
[89] Other player interfaces 166 may be configured to allow various types of
player terminals 106 to access the player account server to create player
accounts or to
obtain information relating to tickets associated with a player account. For
example,
other player interfaces 166 may be adapted to communicate with portable
communication devices with small display screens such as portable digital
assistant
(PDA) devices or portable telephone devices. Other player interfaces 166 may
be
adapted to communicate with computer programs executing on a player terminal
106
and to control the display of information by such computer programs.
[90] Lottery database 160 is used to store information about player accounts,
draws of the on-line lotteries, events in the on-line games, ticket purchase
vouchers and
about tickets issued by the lottery operator. Many different data structures
may be used
to store information about player accounts, on-line lottery draws, on-line
game events
and tickets and the present invention is not limited to any particular data
structure or
data structures for doing so. Several exemplary data structures for storing
such
information will be described here. Skilled persons will be able to design
different data
structures to accommodate different types of on-line lotteries and games and
to
accommodate different computers, other devices, operating systems and software
that
may be used as part of a lottery computer system.
[91] Figures 6a-6c illustrate a portion of lottery database 160. Lottery
database 160 includes a player account table 502, on-line lottery draw tables
504, on-
line lottery ticket tables 506, a ticket purchase voucher table 570 and a
prize redemption
voucher table 574.
[92] Referring to Figure 6a, player account table 502 includes a player
account
record 514 for each player account. Ticket purchase voucher table 570 includes
a ticket
purchase voucher record 572 for each ticket purchase voucher 113. Prize
redemption
voucher table 574 includes a prize redemption voucher record 576 for each
prize
redemption voucher 133.
[93] Each player account record 514 contains information about one player
account. Three player account records 514 are illustrated in Figure 6a. Player
account
table 502 also contains other player account records 514. In this exemplary
-24-

CA 02626207 2007-10-11
embodiment, each player account record 514 includes the following fields:
Field Information recorded in field
Account ID Code The account identification code for the player
account.
Account A password that the player must provide to access
Password information about tickets associated with the player
account. The password may optionally be stored in
an encrypted form.
Name The player's name.
Address The player's address.
Phone The player's phone number.
Fax The player's fax number.
E-mail The player's e-mail address.
Birth Date The player's birth date.
Sex The player's sex.
Income The player's income range.
Player Ticket List This field contains a link or reference to each of the
tickets associated with the player account, allowing
the tickets to be identified.
The reference to the tickets may be any mechanism
for identifying tickets. The reference may be direct
(such as a list of ticket codes or ticket record
identifiers) or indirect (such as a pointer to or the
name of a list, index or table containing ticket codes
or ticket record identifiers).
A ticket record identifier may identify a ticket table 506
(Figure 6b) or 510 (Figure 6c) and a ticket record 524
-25-

CA 02626207 2007-10-11
Field Information recorded in field
or 538 within the ticket table that relates to a
particular ticket associated with the player account.
The structure of on-line lottery ticket records 524 and
on-line game ticket records 538 is described below.
In this embodiment, this field contains a list of ticket
codes for each ticket associated with the player
account. The on-line lottery or on-line game for each
ticket is also identified, to allow the ticket record for
each ticket to be located in the appropriate ticket table
506 or 510 (Figure 6b). For on-line games, the event
list is also identified.
In another embodiment, the field may contain a list of
ticket codes without grouping the ticket codes by on-
line lottery or on-line game. The specific on-line
lottery or on-line game and event list for which the
ticket was issued may be determined by examining
the ticket code (which may be coded to indicate the
on-line lottery or on-line game for which the ticket is
valid) or by searching the various ticket tables.
In other embodiments, this field may be omitted and
the lottery ticket records for tickets associated with a
player account may be identified by searching
through lottery ticket records using the Associated
Player Account field in the lottery ticket records.
Player Ticket This field contains a link or reference to each of the
Purchase ticket purchase vouchers associated with the player
Voucher List account, allowing the ticket purchase vouchers to be
-26-

CA 02626207 2007-10-11
Field Information recorded in field
identified.
Player Prize This field contains a link or reference to each of the
Redemption prize redemption vouchers associated with the player
Voucher List account.
[94] A player creates a player account by accessing an account creation
service. Method 2100 (Figure 7) set a method of creating an account. Referring
briefly
to Figure 8, the player website 167a (Figure 1) includes a welcome web page. A
player
may access the account creation service by clicking on a "Create Account"
button 604.
As part of creating a player account, a player selects an account
identification code. In
the present embodiment, a player's account ID code may consist of any
combination or
permutation of letter or numbers. Also, in the present embodiment, the order
of
characters is sufficient to distinguish two account identification codes. The
account
identification code KARINA1022 is distinct from the account identification
code
KARINA1202.
[95] This is different from some of the concepts described for account
identification codes in PCT patent application No. PCT/CA2006/000270. In PCT
patent
application No. PCT/CA2006/000270, some embodiments require account
identification
codes that contain different sets of characters, regardless of the order in
which a player
might prefer to set out the characters, in order to be distinct. Such
embodiments may
optionally have a field to record the player's preferred order for the
characters in the
player's account identification code. The present invention is compatible with
such
embodiments and when the present invention is combined with such an
embodiment,
player accounts may have an account identification code in which each of the
characters is different from the others to permit the account identification
code to be
marked on a selection slip as is described in that PCT application.
[96] Each player account has a password, which is stored in the Password
field in the player account record 514. The password may optionally be stored
in an
encrypted form.
[97] Personal information about a player is stored in the Name, Address,
-27-

CA 02626207 2007-10-11
Phone, Fax, E-mail, Birth Date, Sex and Income fields of the player account
record 514.
A player may choose not to provide some of this information, and the
corresponding
field may be left empty or omitted from a particular player account record
514,
depending on the data structure used to store a player account record. In any
particular
embodiment, the lottery operator may choose not to include some of the fields
set out
above. For example, a lottery operator that chooses to permit only anonymous
player
accounts may provide for only an Account ID Code field, an Account Password
field, a
Player Ticket List field, a Player Ticket Purchase Voucher List field and a
Player Prize
Redemption Voucher List field in the player account records of that
embodiment.
[98] Returning to the present example system 100, an exemplary player
account record 514 for the account identification code KARINA1022 may contain
the
following information:
Field Information recorded in field
Account ID Code KARINA1022
Account ********
Password
Name Karina Jones
Address 123 Somestreet Rd
Sometown, Somestate
84442
Phone (343)254-9348
Fax None
E-mail karina@isp.com
Birthdate October 22, 1975
Sex Female
Income $50,001-$75,000
Player Ticket List Lotto 7/47 Tickets:
5933-2245-5896-5987
5933-3748-0985-3924
5933-7812-3256-6547
-28-

CA 02626207 2007-10-11
Field Information recorded in field
Keno Tickets:
5254-6789-5656-4156
5254-0258-9963-1912
Sports Line Tickets (List 8845):
1659-8761-6573-4657
1659-6204-2340-4826
Over/Under Tickets (List 8845):
3578-5698-1598-2584
Over/Under Tickets (List 8846):
3576-1942-8572-9234
Player Ticket V1653-564-5685-165
Purchase V1654-470-8329-332
Voucher List V1655-237-8537-275
V 1656-832-2434-742
Player Prize None
Redemption
Voucher List
[99] The Player Ticket List field in the player account record 514 for Karina
Jones'
player account includes a reference to an Over/Under ticket with the ticket
code 3576-
1942-8572-9234. This ticket is valid for the Over/Under on-line game and is
based on
the events on event list 8846 (not shown). Event list 8846 is similar to event
list 8845 in
that it sets out events for the Over/Under on-line game (and for the Sports
Line on-line
game), but relates to a different time period (which may overlap with the time
period
corresponding to event list 8845) and to events that occur within that time
period.
[100] Referring to Figure 6c, lottery database 160 includes an event table and
a ticket
-29-

CA 02626207 2007-10-11
table for the Over/Under on-line game with data about events and tickets
relating to
event list 4524. In this embodiment, event tables and ticket tables relating
to different
event lists are stored as separate tables. In another embodiment, event
records relating
to different event lists may be combined in one table and ticket records
relating to
different event lists may be combined in one table. In other embodiments,
events may
not be divided into different event lists.
[101] Each ticket purchase voucher record 572 in the ticket purchase voucher
table 570 corresponds to one ticket purchase voucher created by a player. In
this
embodiment, each voucher record 572 includes the following fields and data:
Field Information recorded in field
TP Voucher Code The ticket purchase voucher code for the voucher.
Player account ID The account identification code of the player account
code with which the voucher is associated.
Ticket Type The identity of the on-line lottery or on-line game for
which a ticket will be issued with the voucher.
Proposed Ticket This field contains information required to issue a
Information ticket for the on-line lottery or on-line game identified
in the Ticket Type field.
In the case of a ticket purchase voucher for an on-line
lottery, this field includes details about the ticket a
player wishes to purchase with the voucher. The
details may include played number sets, the number
of automatically selected numbers requested, the
number of draws that for which a ticket should be
printed or other ticket information, depending on the
rules of the on-line lottery.
In the case of an on-line game, this information may
include a selection set, wager amounts, depending on
the rules of the on-line games.
-30-

CA 02626207 2007-10-11
Field Information recorded in field
The ticket information may be recorded in one or
more fields, depending on the information recorded.
[102] In this embodiment, all voucher records are maintained in a single
ticket
purchase voucher table 570. In other embodiment, voucher records may be kept
in a
different data structure. For example, voucher records for different on-line
lotteries and
on-line games may be kept in different tables or in other types of data files.
[103] The voucher records for ticket purchase vouchers 117, 217 and 317 have
the following contents:
Voucher 117:
Field Information recorded in field
TP Voucher Code V1653-564-5685-165
Player Account ID KARINA1022
Code
Ticket Type Lotto 7/47
Proposed Ticket Board A: 8, 12, 23, 29, 32, 37, 45
Information Board B: 2, 18, 24, 28, 33, 39, 42
Auto-Pick Numbers: 1
Tag: 2
Draws:4
Voucher 217:
Field Information recorded in field
TP Voucher Code V1655-237-8537-275
Player Account ID KARINA1022
Code
Ticket Type Keno
- 31 -

CA 02626207 2007-10-11
Field Information recorded in field
Proposed Ticket Board 1: 1, 2, 7, 9, 10, 16, 22; Wager: 2
Information Board 2: 12, 25, 27, 43, 46, 49, 64, 66; Wager: 10
Auto-Pick 1: Play Category: 2, Wager5
Draws: 2
Voucher 317:
Field Information recorded in field
TP Voucher Code V1654-470-8329-332
Player account ID KARINA1022
code
Ticket Type Sports Line
Proposed Ticket Event List 8845
Information Event 17: V win
Event 18: H win
Event 45: V win
Event 60: H win
Voucher 417:
Field Information recorded in field
TP Voucher Code V1656-832-2434-742
Player account ID KARINA1022
code
Ticket Type Sports Line
Proposed Ticket Event List 8845
Information Event 56: Under
Event 57: Over
Event 60: Over
-32-

CA 02626207 2007-10-11
[104] Figure 6a illustrates the associations between the player account record
514 for Karina Jones' player account and the ticket purchase voucher records
572 for
her ticket purchase vouchers. Maintaining a list of ticket purchase vouchers
associated
with a player account within the corresponding player account record 514
allows a
player's ticket purchase vouchers to be identified. A lottery operator may
permit a
player to save ticket purchase vouchers within the player's account and may
allow a
player to modify a saved ticket purchase voucher, to re-print a ticket
purchase voucher
or to delete a save ticket purchase voucher. In other embodiments, the player
account
record may not have a Player Ticket Purchase Voucher field and a player's
ticket
purchase vouchers may not be recorded in the corresponding player account
record. In
some embodiments, a player's ticket purchase vouchers may be identified by
searching
through a ticket purchase voucher table for ticket purchase voucher in which
the
player's account is identified.
[105] Each prize redemption voucher record 576 in the prize redemption
voucher table 574 corresponds to one prize redemption voucher created by a
player. In
this embodiment, each prize redemption voucher record 576 includes the
following
fields and data:
Field Information recorded in field
PR Voucher Code A prize redemption voucher code for the prize
redemption voucher.
Player account ID The account identification code for the player account
code with which the prize redemption voucher is
associated.
Winning Ticket List A list or reference to the winning tickets associated
with the prize redemption voucher.
Total Prize The total prize or prizes won by all of the winning
tickets associated with the prize redemption voucher.
If more than of the associated winning tickets has
won a cash prize, the total cash prize is recorded.
Other prizes such as free tickets or merchandise are
also recorded.
-33-

CA 02626207 2007-10-11
[106] An example prize redemption voucher record 577 may have the following
contents:
Field Information recorded in field
PR Voucher Code P9875-7829-83-29
Player account ID KARINA1022
code
Winning Ticket List 5933-2245-5896-5987
5254-0258-9963-1912
Total Prize $20
[107] Figure 6a also illustrates the associations between the player account
record 514 for Karina Jones' player account and prize redemption voucher
records 577.
The creation of prize redemption voucher record 577 is described below in
relation to
method 3200. Maintaining a list of prize redemption vouchers associated with a
player
account allows a player's prize redemption vouchers to be identified. The
lottery
operator may allow a player to modify or delete prize redemption vouchers or
to re-print
a prize redemption voucher. In other embodiments, a player account record 514
may
not have a Player Prize Redemption Voucher List field. In some embodiments, a
player's prize redemption vouchers may be identified by searching the prize
redemption
voucher table for prize redemption voucher records in which the player's
account is
identified.
[108] In the present embodiment, a player may optionally create an anonymous
account, for which personal information that could identify the player is not
recorded.
The Account ID Code, the Account Password, the Player Ticket List fields and
the
Player Ticket Purchase Voucher List are required for the operation of a player
account
in this embodiment and the information stored in these fields is required even
for an
anonymous account. However, a player may optionally not provide some or all of
the
information for the personal information fields described above. A player may
choose
not to provide his name and address, but could optionally provide sex and
income
information to allow some demographic analysis of lottery players.
Alternatively, the
-34-

CA 02626207 2007-10-11
player may not provide any personal information.
[109] In an alternative embodiment, a lottery operator may designate some
personal or other information as required information. For example, the
lottery operator
may require a lottery player to provide the player's birth date to allow the
lottery operator
to ensure that only players of a certain age access the player account. Any
combination
of information may be designated as required information or optional
information by a
lottery operator. The personal information fields described in relation to the
present
embodiment are only an example.
[110] In another alternative embodiment, a lottery operator may choose not to
collect any personal information and may make all player accounts anonymous
accounts. In such an embodiment, a player account record 514 may comprise only
an
Account ID field, an Account Password field, a Player Ticket List field, a
Player Ticket
Purchase Voucher List field and a Player Prize Redemption Purchase Voucher
List
field.
[111] In another embodiment, a lottery operator may not require a player to
enter a password when accessing a player account. In such an embodiment, a
player
account record would not include an Account Password field.
[112] Reference is next made to Figure 6b and 6c.
[113] Each draw record 518 in the draw tables 504 contains information about a
draw of an on-line lottery, such as the date of the draw, a draw number,
winning
numbers for the host on-line lottery and for any associated on-line lottery
and prize
information for the host on-line lottery and any associated on-line lottery.
[114] Each of the draw records 518 in Lotto 7/47 draw table 516 contains
information about one draw of the Lotto 7/47 on-line lottery and the
corresponding draw
of the associated Tag on-line lottery on the same draw date. In this exemplary
embodiment, a single draw record is used to maintain information about both a
host on-
line lottery and its associated on-line lottery, since the two on-line
lotteries share
information such as their draw date and since the tickets valid for the
associated on-line
lottery are a subset of those valid for the host on-line lottery.
Alternatively, separate
draw tables could be used for the two on-line lotteries.
[115] Six draw records 518 for draws between November 11, 2005 and
-35-

CA 02626207 2007-10-11
December 16, 2005 are illustrated in Figure 6a. In this exemplary embodiment,
each
draw record 518 in the Lotto 7/47 draw table includes the following fields:
Field Information recorded in field
Draw ID An identifier for the draw. This may be a draw
number, or any other type of identifier for the draw.
This field is optional, especially if the date (or date
and time) of the draw, or another field such as a
record number field, can be used to uniquely identify
the draw. In this exemplary embodiment, each draw
is assigned a numerical draw number, in sequential
order.
Draw Date The date on which the draw is scheduled to be
conducted. In another embodiment, this field may
also include the time of the draw, particularly if more
than one draw for the on-line lottery is conducted on a
particular day.
Lotto 7/47 The winning number set for this draw of the Lotto 7/47
Winning Number on-line lottery.
Set
Lotto 7/47 Prize Information about prizes for each winning
Information combination for this draw of the Lotto 7/47 on-line
lottery.
Tag Winning The winning number for the Tag associated on-line
Number lottery.
Tag Prize Information about prizes for each combination of
Information winning numbers for this draw of the Tag on-line
lottery.
Draw Ticket List This field contains a link or reference to each of the
tickets valid for the draw, allowing the tickets valid for
the draw to be identified.
-36-

CA 02626207 2007-10-11
Field Information recorded in field
The reference to the tickets may be any mechanism
for identifying the tickets valid for the draw. The
reference may be direct or indirect, as is described
above in relation to the Player Ticket List field of the
player account records 514.
In the present embodiment, this field is a pointer to an
index that contains a reference to the lottery ticket
records for all tickets that are valid for the draw. In
Figure 6a, the link between the draw record 518 and
lottery ticket records 524 for tickets valid for each
draw is illustrated by lines connecting them. Lottery
database 160 includes an index for each draw. The
index includes a reference to each ticket that is valid
for the draw.
In another embodiment, this link may be omitted and
the lottery tickets valid for a draw may be identified by
searching the Valid Draw Dates field in lottery ticket
records in the appropriate ticket table.
[116] The Lotto 7/47 Winning Number Set and Tag Winning Number fields in a
draw record 518 will not contain information about winning numbers until after
the draws
of the on-line lottery or lotteries have been conducted on the draw date and
the winning
numbers have been determined. If any of the prizes for the on-line lottery are
determined based on the number of winners, as in the case of a shared prize,
then the
prize values will only be known after the draw. If the prizes are pre-
determined, as in
the case of the Tag on-line lottery, the relevant prize information may be
filled in when
the draw record is created by the lottery operator. Where the prizes for an on-
line
lottery are the same for each draw (or for a series of draws), the
corresponding prize
-37-

CA 02626207 2007-10-11
information may be stored elsewhere in the lottery database 160 (for example
in a
lottery table (not shown), which may contain rules and other standard
information about
each on-line lottery, including any fixed or standard prizes). The
corresponding prize
information field may be omitted, or may contain a reference to the
corresponding
information stored elsewhere. In the present exemplary embodiment, the Tag
Prize
Information field is completed after a draw to record the number of winners of
each prize
offered in the Tag on-line lottery. The actual value of the prizes is recorded
separately
from the draw record 518. This information may, for example, be stored in a
Tag on-line
lottery information file or record (not shown) as another part of the lottery
database 160
and is available to the lottery computer system 102.
[117] Records in the draw table for each lottery are created by the lottery
operator to store relevant information about each draw. An exemplary draw
record 518
for the November 18, 2005 draw of the Lotto 7/47 lottery could have the
following
contents prior to the draw:
Field Information recorded in field
Draw ID 1795
Draw Date November 18, 2005
Lotto 7/47 Unknown when the record is created
Winning Number
Set
Lotto 7/47 Prize Unknown when the record is created, since most
Information Lotto 7/47 prizes are shared prizes. The fixed prize
of a free ticket for the winning combination of 3/7
regular numbers may be recorded here.
Tag Winning Unknown when the record is created
Number
Tag Prize Link or reference to pre-determined Tag on-line
Information lottery prize information stored elsewhere in the
lottery database 160.
Draw Ticket List Link or reference to an index of lottery ticket records
for tickets valid for this draw. The index includes
-38-

CA 02626207 2007-10-11
Field Information recorded in field
references to lottery ticket records for the following
ticket codes:
5933-2245-5896-5987
5933-3748-0985-3924
[118] Each on-line lottery ticket record 524 in the on-line lottery ticket
tables 506
contains information relating to a ticket issued for one or more draws of the
on-line
lottery and any associated lottery. Several ticket records 524 are shown in
each of the
ticket tables 506. Each ticket table 506 also contains additional ticket
records (not
shown) corresponding to additional tickets for the on-line lottery. In this
exemplary
embodiment, each lottery ticket record 524 includes the following fields:
Field Information recorded in field
Ticket Code The ticket code for the ticket.
Issue Date/Time The date and time at which the ticket was issued by
the lottery operator.
Host On-line The played number sets selected by the player, or
Lottery Played automatically selected for the player, for the host
Number Sets lottery.
Associated On- An indication of whether the Tag on-line lottery has
line Lottery been played on this ticket, and if so, a list of the Tag
Information played number sets. This field may contain one or
more Tag played number sets selected for the ticket,
even if the player elected not to play the Tag on-line
lottery.
Valid Draw A reference to the draws for which the ticket is valid.
Dates
In the present embodiment, the date or dates of the
draws for which the ticket is valid are set out in this
field.
-39-

CA 02626207 2007-10-11
Field Information recorded in field
In another embodiment, this field may contain a list of
draw identifiers corresponding the Draw ID field in the
draw records 518, the date of a draw or a list or range
of dates of draws for which the ticket is valid.
Vendor Terminal The vendor terminal code described above.
Code
Verification Code The verification code described above.
Associated Account identification code for the player account with
Player Account which the ticket is associated. If the ticket is not
associated with a player account, this field will be
blank or may be omitted.
Associated Prize A link or reference to a prize redemption voucher that
Redemption the ticket is associated with, if any. If the ticket is not
Voucher associated with a prize redemption voucher, this field
will indicate "None".
Prize Data Data relating to prizes won by the ticket. This field is
described in greater detail below.
Ticket Status The current status of the on-line lottery ticket with
respect to the completion of the draws for which the
ticket is valid and with respect to the redemption of
prizes won by the ticket, if any. The status may be
one of the following:
i. Draws Not Complete, indicating that at least one
draw for which ticket is valid has not been
conducted;
ii. Not A Winner, indicating that the draws for which
the ticket is valid for have been conducted and
the ticket has not won a prize;
iii. Winner-Not Redeemed, indicating that the draws
-40-

CA 02626207 2007-10-11
Field Information recorded in field
for which the ticket is valid for have been
conducted, the ticket has won at least one prize
and that the prize has not been redeemed; or
iv. Winner-Redeemed, indicating that the draws for
which the ticket is valid have been conducted, the
ticket has won at least one prize and the prizes
have been redeemed.
[119] Information that is displayed on the ticket receipt 114 may be stored in
the
format that is used on the ticket or in another corresponding format. For
example, the
played numbers in a played number set for the Lotto 7/47 on-line lottery may
be stored
as six different values, or may be stored as a code representing the played
numbers, or
both. The lottery ticket record may contain additional information, such as
the method
by which the player paid for ticket, and other information.
[120] Lottery ticket records 524 for seven tickets L1-L7 are illustrated in
Lotto
7/47 ticket table 522. The draw record 518 for the November 18, 2005 draw is
linked to
the lottery ticket records 524 for tickets L2 and L3 indicating that they are
valid for that
draw. Ticket L3 corresponds to ticket receipt 118 (Figure 2) and is also valid
for the
November 25, December 2 and December 9 draws. The ticket record 525 for ticket
L3
may contain the following information when it is first created:
Field Information recorded in field
Ticket Code 5933-3748-0985-3924
Issue Date/Time November 17, 2005 - 12:43 pm
Host On-line Set 1: 8, 12, 23, 29, 32, 37, 45
Lottery Played Set 2: 2, 18, 24, 28, 33, 39, 42
Number Sets Set 3: 12, 17, 21, 29, 32, 37, 43 (Auto-Pick)
Associated On- Played
line Lottery Played Number 1: 398587
Information Played Number 2: 957238
Valid Draw November 18, 2005
-41-

CA 02626207 2007-10-11
Field Information recorded in field
Dates November 25, 2005
December 2, 2005
December 9, 2005
Vendor Terminal 59573
Code
Verification Code 3423
Associated KARINA1022
Player Account
Associated Prize None
Redemption
Voucher
Prize Data Unknown (draws not conducted yet)
Ticket Status Draws Not Complete
[121] Keno draw table 526 and Keno ticket table 528 are similar to Lotto 7/47
draw table and Lotto 7/47 ticket table and contain information relating to
draws and
tickets for the Keno on-line lottery. Keno draw table 526 contains draw
records 518 for
daily draws of the Keno on-line lottery. Lottery ticket records 524 for six
tickets K1-K6
for the Keno on-line lottery are illustrated in the Keno Ticket table 528 in
Figure 6a. In
this example embodiment, the Keno on-line lottery is not a host lottery for
the Tag on-
line lottery. The ticket records 524 for Keno tickets do not have an
Associated On-line
Lottery Information field. If the lottery operator operates other on-line
lotteries, the
lottery database 160 will have a draw table and a ticket table for each other
on-line
lottery.
[122] Referring to Figure 6c, lottery database 160 also includes on-line game
event tables 508 and on-line game ticket tables 510. Player account table 502
is also
illustrated in Figure 6c. Lottery database 160 includes a Sports Line event
table 532, a
Sports Line ticket table 536, an Over/Under event table 540 and an Over/Under
ticket
table 542. In the present embodiment, the lottery database includes a separate
event
table 508 and on-line game ticket table 510 for each event list for each on-
line game.
-42-

CA 02626207 2007-10-11
The event tables and on-line game ticket tables in Figure 6b are for the
Sports Line and
Over/Under on-line games based on event list 8845.
[123] Each event table 508 contains one or more event records 534. Each
event record 534 contains information about an event for an on-line game, such
as the
date and time of the event, the teams participating in the event, the various
predicted
outcomes that a player may choose, the odds set by the lottery operator for
those
outcomes and other information.
[124] In this exemplary embodiment, each event record 534 in the Sports Line
event table 532 includes the following fields:
Field Information recorded in field
Event number The event number as indicated on the event list.
Date/Time The date and time of the event. This may be the time
after which a player cannot select the event for a
ticket. Typically, the lottery operator will not allow a
player to select an event less than a selected time (for
example, 15 minutes or 30 minutes) before the
beginning of an event.
Event Type The name of sport, league or other classification of
the event.
Visitor Name The name of the visiting team
Home Name The name of the home team
Visitor Odds The odds set by the lottery operator for the visiting
team winning the event according to the rules of the
Sports Line on-line game.
Home Odds The odds set by the lottery operator for the home
team winning the event according to the rules of the
Sports Line on-line game.
Tie Odds The odds set by the lottery operator for a tie in the
event according to the rules of the Sports Line on-line
game.
Actual Outcome The actual outcome of the event, according to the
-43-

CA 02626207 2007-10-11
rules of the Sports Line on-line game.
[125] In this exemplary embodiment, each event record 534 in the Over/Under
event table 540 includes the following fields:
Field Information recorded in field
Event number The event number as indicated on the event list.
Date/Time The date and time of the event. As with the event
records for the Sports Line on-line game, this may be
time after which a player cannot select the event for a
ticket.
Event Type The name of sport, league or other classification of
the event.
Event Name A description of the event. This field identifies the
teams participating in the event.
Threshold The threshold number of points.
Over Odds The odds set by the lottery operator for the teams
scoring over the threshold number of points according
to the rules of the Over/Under on-line game.
Under Odds The odds set by the lottery operator for the teams
scoring under the threshold number of points
according to the rules of the Over/Under on-line
game.
Actual Outcome The actual outcome of the event, according to the
rules of the Over/Under on-line game.
[126] The Actual Outcome field in an event record 534 will be blank until the
event has
been completed and the outcome is known. In the Sports Line event table 532,
the
event record 534 for event 87 on list 8845 has the following contents when it
is first
created:
Field Information recorded in field
-44-

CA 02626207 2007-10-11
Event number 87
Date/Time Nov 13, 2005 - 8:00 pm
Event Type NHL Hockey
Visitor Name Anaheim
Home Name Dallas
Visitor Odds 1.7
Home Odds 5.5
Tie Odds 1.7
Actual Outcome Unknown
[127] In the Over/Under event table 532, the event record 534 for event 56 on
list 8845
has the following contents when it is first created:
Field Information recorded in field
Event number 56
Date/Time Nov 13, 2005 - 1:00 pm
Event Type NFL Football
Event Name Kansas City v. Buffalo
Threshold 43.5
Over Odds 1.7
Under Odds 1.7
Actual Outcome Unknown
[128] Each on-line game ticket table 510 contains on-line game ticket records
538. Each on-line game ticket record 538 contains information relating to a
ticket sold
for an on-line game. In this exemplary embodiment, the ticket records 538 in
the Sports
Line ticket table 536 include the following fields:
Field Information recorded in field
Ticket Code The ticket code for the ticket.
Issue Date/Time The date and time at which the ticket was issued by
the lottery operator.
-45-

CA 02626207 2007-10-11
Predicted A list of the events for which the player has made a
Outcomes prediction and the player's prediction for each event.
Vendor Terminal The vendor terminal code described above.
Code
Verification Code The verification code described above.
Associated Account ID code for the player account with which the
Player Account ticket is associated. If the ticket is not associated with
a player account, this field will be blank or may be
omitted.
Associated Prize A link or reference to a prize redemption voucher that
Redemption the ticket is associated with, if any. If the ticket is not
Voucher associated with a prize redemption voucher, this field
will indicate "None".
Wager The amount that the player wagered on this ticket.
Maturation Event The event following which the on-line game ticket
"matures". An on-line game ticket matures when the
results for the wager made on the ticket can be
determined.
In the present embodiment, this is possible when all
of the events on which the wager is based are
complete. The maturation event for each ticket is the
chronologically latest event that the wager is based
on.
In other embodiments, this information may be set out
as a fixed date or fixed date and time, after the
expected completion of the maturation event for
which the player has made a predicted.
In another embodiment, this field may be omitted.
-46-

CA 02626207 2007-10-11
The lottery operator may periodically (i.e. daily) or
occasionally search the Predicted Outcomes field of
each on-line game ticket record and determine the
Ticket Status for tickets that are based on events that
have been completed.
In another embodiment, the lottery operator may
configure the ticket server to wait until a player
attempts to check or redeem an on-line game ticket
before determining whether the ticket is a winning on-
line game ticket. If the events on which the on-line
game ticket is based have been completed, the ticket
server can calculate and report the Prize Data.
Otherwise, the ticket server reports that the Prize
Data cannot be calculated yet.
Payout Value The amount the player will be paid if his predictions
meet the requirement for the particular game. In
some games, several payout values might be
recorded and one or more of them might be paid to
the player if different criteria are met.
This field is optional. The payout value may be
calculated when it is required using the odds for the
outcomes predicted by the player and the wager
chosen by the player.
Ticket Status The current status of the on-line game ticket with
respect to the completion of the draws for which the
ticket is valid and with respect to the redemption of
prizes won by the ticket, if any. The status may be
one of the following:
i. Events Not Complete, indicating that the ticket
-47-

CA 02626207 2007-10-11
has not matured because the actual outcome of
at least one event on which the ticket is based is
not known;
ii. Not A Winner, indicating that the ticket has
matured and that the player has lost the wager on
the ticket;
iii. Winner-Not Redeemed, indicating that the player
has won the wager on the ticket, but has not yet
redeemed the ticket to receive the payout value;
or
iv. Winner-Redeemed, indicating that the player has
won the wager on the ticket and has redeemed
the ticket to receive the payout value.
[129] Each on-line game ticket table 510 has a Maturation Event Index (not
shown) that provides an index of the ticket records 538 in the ticket table
ordered by the
event identified in the Maturation Event field in each of the ticket records.
The
Maturation Event Index may be used to identify ticket records 538 that
correspond to
tickets which mature after a particular event. The Sports Line ticket table
536 has a
Sports Line Maturation Event Index (not shown). The Over/Under ticket table
542 has
an Over/Under Maturation Event Index (not shown). In another embodiment,
ticket
records that have a specific maturation event may be identified by searching
through
each ticket record in a ticket table.
[130] Sports Line ticket table 536 contains seven on-line game ticket records
538 corresponding to seven Sports Line on-line game tickets SL1-SL7. Ticket
SL3
corresponds to ticket receipt 318 (Figure 4). The ticket record 539 for ticket
SL3, when
it is first created has the following contents:
Field Information recorded in field
Ticket Code 1659-8761-6573-4657
Issue Date/Time Nov 12, 2005 - 10:15 am
Predicted Event 17 - Visitor Win
-48-

CA 02626207 2007-10-11
Outcomes Event 18 - Home Win
Event 45 - Visitor Win
Event 60 - Home Win
Vendor Terminal 45678
Code
Verification Code 2344
Associated KARINA1022
Player Account
Associated Prize None
Redemption
Voucher
Wager $10.00
Maturation Event Event 60
Payout Value $124.80
Ticket Status Events Not Complete
Over/Under ticket table 542 contains six on-line game ticket records 538
corresponding
to six Over/Under on-line game ticket OU1-OU6. Ticket OU2 corresponds to on-
line
game ticket record 541 and to ticket receipt 418 (Figure 5).
[131] Player account server 162 manages the creation of player accounts and
enables
players to access their player accounts using a player terminal 106. Each
player
interface 166 facilitates communications between the player account server 162
and
one or more of the player terminals 106. In the present embodiment, player
interface
166a includes a player website 167a, which players may access by using a web
browser operating on a player terminal 106, such as a personal computer or any
other
web-enable computing device. Player interface 166a communicates with web
browsers
to receive information from the player terminals 106 and to transmit
information to the
player terminals 106. For example, player interface 166a receives information
about
new player accounts and creates a corresponding player account record 514 in
the
lottery database 160. This is further described below in relation to method
2100. Player
interface 166a obtains information relating to tickets associated with a
player account
-49-

CA 02626207 2007-10-11
from the lottery database 160 and transmits it to a player terminal 106. The
information
is displayed on the player terminal 106. This is further described below in
relation to
method 2600.
[132] Other player interfaces 166 may be configured to allow other types of
player
terminals 106 to access the player account server to create player accounts or
to obtain
information relating to tickets associated with a player account. For example,
other
player interfaces 166 may be adapted to communicate with portable
communication
devices with small display screens such as portable digital assistant (PDA)
devices or
portable telephone devices. Other player interfaces 166 may be adapted to
communicate with computer programs executing on a player terminal 106 and to
control
the display of information by such computer programs.
[133] Figure 7 illustrates a method 2100 for creating a player account. Method
2100
begins in step 2102 in which a player accesses player account server 162 by
accessing
a player interface 166. Method 2100 will be explained by way of example with
reference to player interface 166a, which includes player website 167a.
[134] Referring to Figure 8, the player website 167a (Figure 1) includes a
welcome
web page 602 that includes a "Create Account" button 604, which allows the
player to
initiate a player account creation service. The player account creation
service operates
under the control of the player account server 162.
[135] Reference is again made to Figure 7. In step 2102, the player uses a
player
terminal 106 to access the welcome page 602 and initiates the player account
creation
service by clicking on the Create Account button. In other embodiments of the
invention, a player account creation service may be initiated through the use
of any
other type of control or option that a player may select or interact with.
[136] Method 2100 next proceeds to step 2104. In step 2104, the player selects
a
player account identification code and provides other information for her
player account.
In this step, the player is presented with an account creation form. The
account
creation form is transmitted from the player website 167a to the player
terminal 106 and
is displayed on the player terminal 106. The account creation form has a
number of
fields to allow the player to enter information relating to a player account
that the player
wishes to create. The account creation form allows the player to propose an
account
-50-

CA 02626207 2007-10-11
identification code and account password for the player account. The account
creation
form also allows the player to enter the personal information described above:
the
player's name, address, phone number, fax number, e-mail address, birth date,
sex and
income range. When the player has completed the form, the information entered
by the
player is transmitted to the player account server. Method 2100 proceeds to
step 2106.
[137] In step 2106, the player account server 162 determines whether the
proposed
account identification code may be assigned to the player's account. In the
present
embodiment, the player account server 162 checks whether the proposed account
identification code is consistent with any rules the lottery operator has
specified for
account identification codes.
[138] The player account server 162 also checks the account password proposed
by
the player to ensure that it complies with any rules set by the lottery
operator. The
lottery operator may specify rules for account passwords relating to minimum
and
maximum numbers of characters, use of different cases of letters (i.e.
uppercase,
lowercase or mixed case), use of numerals in the password and other
requirements.
[139] The player account server 162 also checks the remaining information
provided
by the player to ensure that it meets any criteria set by the lottery
operator. For
example, the lottery operator may check to ensure that any required fields are
completed. In the present example, the lottery operator allows players to
create
anonymous accounts without entering any personal information. In other
embodiments,
the lottery operator may require players to provide some or all of the
personal
information described here, as well as other personal information.
[140] If the proposed identification code, password and personal information
meet all
criteria imposed by the lottery operator, method 2100 proceeds to step 2108.
Otherwise, method 2100 returns to step 2104.
[141] In step 2108, a new player account record 514 is created in the player
account
table 502 for the new player account code. The Player Ticket List field does
not contain
a reference to any tickets at this point, since the player account is newly
created and no
tickets have been associated with the account. The Player Ticket Purchase
Voucher
List field does not contain a reference to any ticket purchase vouchers. The
Player
Prize Redemption Purchase Voucher field does not contain a reference to any
prize
-51 -

CA 02626207 2007-10-11
redemption vouchers.
[142] Referring to Figure 6a, three player account records 514 are
illustrated. The
player account record 514 with player account code SAMANTHA is newly created
using
method 2100 and has not yet been associated with any tickets, ticket purchase
vouchers or prize redemption vouchers.
[143] Method 2100 proceeds to step 2110. In step 2110, the player account
server
162 confirms the creation of the new player account. The player account server
162
transmits a confirmation message to the player terminal 106 where the
confirmation
message is displayed.
[144] Method 2100 ends when step 2110 is completed.
[145] Typically, a lottery operator will allow a player to change some of the
information
recorded about the player and the player account in a player account record
514. For
example, the player may be permitted to change the password associated with
the
player account or the personal information about the player. The lottery
operator will
provide an account modification service for this purpose. A skilled person
will be able to
provide an appropriate account modification service and the account
modification is not
further described here.
[146] Figure 9 illustrates a method 3000 that allows a player to create and
print
a ticket purchase voucher 113. Method 3000 will be explained in part with
reference to
an example using the player record for Karina Jones and the Lotto 7/47 ticket
purchase
voucher creation page 116, the associated ticket purchase voucher 117 and the
associated ticket receipt 118.
[147] Method 3000 begins in step 3002 in which the player uses a player
terminal 106 access the player account server 162. The player terminal 106
communicates with a player interface 166 to allow the player to interact with
the lottery
computer system.
[148] Referring to Figure 8, the player website 167a (Figure 1) includes a
welcome web page 602. A player may access player account server 162 by
accessing
the player website 167a and accessing the welcome web page 602. Welcome web
page 602 includes player account identification code field 612, an account
password
field 614 and an "Enter" button 616. To request access to the account checking
service,
-52-

CA 02626207 2007-10-11
the player enters his account identification code in the account
identification code field
612, his account password in the account password field 614 and then clicks on
the
Enter button 616. The account identification code and account password entered
by the
player are transmitted to the player account server 162. Optionally, the
account
password may be encrypted before it is transmitted to the player account
server 162.
The account identification code may also optionally be encrypted before it is
transmitted
to the player account server 162.
[149] In the present example, a player may access player website 167a using a
player terminal 106 that operates a web browser. Player terminal 106c is a
computer
that is coupled to the Internet and operates a web browser. The welcome web
page
602 is displayed on the player terminal 106c. Karina Jones uses this player
terminal
106c to access the player website 167a. The player interface 166 can display
parts of
the player website 167a on the player terminal.
[150] In the present example, Karina Jones enters her account identification
code KARINA1022 in the account identification code field 612. She also enters
her
account password in the account password field 612 and clicks on the Enter
button 616.
[151] Method 3000 then proceeds to decision step 3004. In step 3004, the
player account server 162 attempts to authenticate the account identification
code and
account password entered by the player in step 3002. If a player account
record 514
matching the entered account identification code and account password exists
in the
player account table 512 (Figure 6), then the account identification code and
password
are authentic and method 3000 proceeds to step 3008. Otherwise, method 3000
proceeds to step 3006.
[152] Since Karina Jones correctly entered her account ID code and password,
in the example, method 3000 proceeds to step 3008.
[153] In step 3006, an error message is displayed on the player terminal 106
indicating that the player has entered an invalid account identification code
or an invalid
password (or both). Method 3000 then ends.
[154] In step 3008, the player is provided access to the ticket purchase
voucher
creation service.
[155] In system 100, the player is presented with an opportunity to use
various
-53-

CA 02626207 2007-10-11
services, such as a ticket checking service or the ticket purchase voucher
creation
service. For example, a webpage is displayed on the player's terminal
identifying the
various services and allowing the player to click a button to select the
ticket purchase
voucher creation service. The player chooses to access the ticket purchase
voucher
creation service.
[156] Referring to Figure 10, player website 167a then presents the player
with
a ticket purchase voucher selection page 620 on which the various on-line
lotteries and
on-line games for which a ticket purchase voucher can be made are identified
and can
be selected. For example, buttons 622a, 622b, 622c and 622d can be used to
select
Lotto 7/47, Keno, SportsLine and Over/Under. The player selects one of these
on-line
lotteries or on-line games by clicking on the name of the on-line lottery or
on-line
games.
[157] In the example, Karina Jones chooses Lotto 7/47.
[158] Method 3000 then proceeds to step 3010, in which the player is presented
with a ticket purchase voucher creation page 112 (Figures 2-5) for the
selected on-line
lottery or on-line game. The player then selects the played numbers, outcomes,
and/or
other choices available, depending on the on-line lottery or on-line game
selected.
When the player has completed the voucher, the player clicks to the Create
Voucher
button 119.
[159] For example, ticket purchase voucher creation page 116 for Lotto 7/47 is
displayed for Karina Jones on her player terminal 106. She completes the Lotto
7/47
ticket purchase voucher creation page as shown in Figure 2 to select two
manually
selected played number sets, one automatically selected Lotto 7/47 played
number set,
two Tag numbers and to purchase a ticket for four draws. Karina Jones then
clicks the
Create Voucher button 119.
[160] Method 3000 then proceeds to step 3012. In this step, the player
terminal
transmits a Ticket Purchase Voucher Request 560 to the player account server
162
containing proposed ticket information corresponding to the selections made by
the
player. The ticket purchase voucher generation pages 112, which are part of
the player
website 167a, are configured such that when a player clicks the Create Voucher
119
button, a Ticket Purchase Voucher Request 560 is sent to the player interface
166. The
-54-

CA 02626207 2007-10-11
Ticket Purchase Voucher Request is in the form of a message that includes
proposed
ticket information.
[161] In the present example, when Karina Jones clicks the Create Voucher
button 119 on the Lotto 7/47 ticket purchase voucher creation page, the web
browser on
her player computer 106c transmits a message to the player interface 166
containing
the following proposed ticket information:
Ticket Type: Lotto 7/47
Manually selected number sets:
08 12 23 29 32 37 45
02 18 24 28 33 39 42
Automatically selected number sets: 1
Tag Numbers: 2
Draws: 4
[162] In another embodiment, the ticket type may be implicit in the message
type or in the source of the message. For example, the message by of a type
that
indicates the on-line lottery or on-line game for which a ticket purchase
voucher is being
requested, or the message may indicate that the ticket purchase voucher
request
originated from a Lotto 7/47 ticket purchase voucher generation page.
[163] Method 3000 then proceeds to step 3014. In this step, the new ticket
purchase voucher is added to the lottery database 160. The player account
server 162
adds a new voucher record 572 to the ticket purchase voucher table 570 in
response to
the Ticket Purchase Voucher Request 560. The player account server associates
the
ticket purchase voucher record with the player's account. The player's account
is
identified in the Player Account ID Code field in the voucher record 572. The
player
account server 162 also identifies the new voucher in the Player Ticket
Voucher List in
the player record for the player's account.
[164] In the present example, the player account server 162 adds the voucher
record for voucher 117 (Figure 2) to the voucher table in response to the
Ticket
Purchase Voucher Request.
[165] Method 3000 then proceeds to step 3016, in which the player account
server 162 generates a ticket purchase voucher 113 corresponding to the Ticket
-55-

CA 02626207 2007-10-11
Purchase Voucher Request 560. The ticket purchase voucher is generated in a
format
that is suitable for printing at a player terminal and on which the machine
readable
voucher code can be scanned using a ticket vending terminal 104. In the
present
embodiment, ticket purchase vouchers 113 are generated in a portable document
format (PDF) that is used widely in computing.
[166] Method 3000 then proceeds to step 3018 in which the ticket purchase
voucher is transmitted to the player terminal 106 from which the Ticket
Purchase
Voucher Request was received and in which a paper copy of the ticket purchase
voucher is printed at the player's terminal (or another device) by the player.
The ticket
purchase voucher includes the ticket purchase voucher code in a form or
version
suitable for scanning at a ticket vending terminal.
[167] In addition to generating the ticket purchase voucher, the player
account
server may also generate a version of the ticket purchase voucher that is
suitable for
display at the player terminal from which the Ticket Purchase Voucher Request
560 was
received. This version may be generated by the player interface 166 that is
communicating with the player terminal 106. For example, "dumb" player
terminals (for
example a device connected via a telnet connection) may simply receive and
display
text from a player interface and may just detect and transmit keystrokes and
other input
from the player to the player interface. A player interface for such a dumb
terminal may
transmit text corresponding to the ticket purchase voucher to the player
terminal. The
text may include instructions for the player to download the ticket purchase
voucher,
which the player can then print at his player terminal or at another device.
When the
player follows the instructions, the ticket purchase voucher is transmitted to
the player.
[168] In the Karina Jones example, the player is communicating with player
interface 166a, which controls the display of webpages from player website
167a on her
player terminal 106c. Player interface 166a generates a webpage that includes
information corresponding to the ticket purchase voucher (which will generally
include
text setting out some or all of the contents of the ticket purchase voucher).
The
webpage is transmitted to the player interface where it is displayed. The
webpage
includes a "Print Voucher" button. When the player clicks the Print Voucher
button, the
voucher is transmitted to the player interface and player can print the
voucher at the
-56-

CA 02626207 2007-10-11
player terminal or at another device.
[169] In another embodiment, the ticket purchase voucher may be transmitted to
the player without any additional version of it. The player terminal may be
able to
display the voucher in addition to printing it. In some embodiments, the
player may only
be able to print the voucher without seeing a display of it.
[170] In the Karina Jones example, the player interface generates a webpage
that includes information on the ticket purchase voucher, as well as
additional
information, which may include instructions on how to use the voucher, other
information about the lottery operator or the lottery operator's on-line
lotteries, on-line
games and other products, and other information. Karina Jones clicks on the
"Print
Voucher" button and the voucher is printed on a printer at her player
terminal.
[171] Method 3000 then ends.
[172] After completing method 3000, the player has a printed ticket purchase
voucher 113 that corresponds to the player's selections on the ticket purchase
voucher
creation page in step 3010. The player can use the ticket purchase voucher to
purchase a ticket for an on-line lottery or on-line game in accordance with a
ticket
purchase method 3100.
[173] Figure 11 illustrates method 3100. Method 3100 allows the lottery
operator to sell a ticket to a player and correspondingly allows a player to
purchase a
ticket using a ticket purchase voucher 113. The steps in method 3100 are
explained
with reference to Karina Jones' ticket purchase voucher 117 for the Lotto7/47
on-line
lottery.
[174] Method 3100 starts in step 3102 in which the player presents a ticket
purchase voucher 113 to a ticket vendor.
[175] Method 3100 then proceeds to step 3104, in which the ticket vendor scans
the machine readable voucher code 136 (Figures 2, 3, 4) using the scanner or
scanning
device of the ticket vending terminal 104. In the present example, the machine
readable ticket purchase voucher code 136 is a barcode and the scanner is a
barcode
scanner.
[176] In other embodiments the scanner is selected such that it can scan the
machine readable ticket purchase voucher code used in such embodiments. The
ticket
-57-

CA 02626207 2007-10-11
vending terminal 104 transmits the ticket purchase voucher code of the ticket
purchase
voucher to the ticket server 164.
[177] Method 3100 then proceeds to step 3106, in which the lottery computer
system 102 issues a ticket to the player. The ticket server 164 receives the
ticket
purchase voucher code from the ticket vending terminal 104 and obtains the
corresponding ticket purchase voucher record 572 from the ticket purchase
voucher
table 570. The ticket purchase voucher record 572 contains proposed ticket
information
corresponding to the player's selections for the ticket purchase voucher. The
ticket
server 164 adds a ticket record to the appropriate ticket table corresponding
to the
Ticket Type in the proposed ticket information. The ticket server 164
associates the
ticket with the player's account by identifying the player's account in the
Associated
Player Account field of the ticket record and by identifying the new ticket
purchase
voucher in the Player Ticket Purchase Voucher List field of the corresponding
player
account record 514.
[178] The ticket server 164 transmits Ticket Receipt Data 554 to the ticket
vending terminal 104 from which the voucher code was received in step 3104.
[179] The Ticket Receipt Data 554 includes ticket information printed by the
ticket vending terminal 104 on the ticket receipt 114 for the ticket.
[180] In the Karina Jones example, the Ticket Receipt Data 554 includes the
information printed on the ticket receipt 118 (Figure 2). The Ticket Receipt
Data 554
may also include additional information, such as formatting information to
indicate how
the information printed on the ticket receipt 114 should be laid out. The
ticket vending
terminal 104 prints a ticket receipt 114 setting out the ticket information.
[181] The ticket vendor gives the ticket receipt 114 to the player and method
3100 ends.
[182] In system 100, tickets are issued to players who have created a player
account with the lottery operator at the lottery computer system. Tickets
issued to a
player in method 3100 are associated with the player's account.
[183] Reference is next made to Figure 12. In other embodiments, a single
ticket purchase voucher may be used to purchase more than one ticket. The
player is
permitted to make selections for more than one ticket and proposed ticket
information
-58-

CA 02626207 2007-10-11
for each ticket is recorded in the player account server or elsewhere in the
lottery
computer system. When the player is done making selections for tickets, the
player
requests a ticket purchase voucher for all of the tickets. The proposed ticket
information
for each of the tickets is recorded in the lottery database and associated
with a single
ticket purchase voucher record. For example, the proposed ticket information
may be
stored in the ticket purchase voucher record or the ticket purchase voucher
record may
include a reference to the proposed ticket information, which may be stored
separately.
[184] In such an embodiment, in step 3106 of method 3100, when the ticket
server receives a ticket issue request based on the multi-ticket ticket
purchase voucher,
it issues tickets corresponding to all of the proposed ticket information
associated with
the ticket purchase voucher's code. Each of the tickets is associated with the
corresponding player account.
[185] Figure 12 illustrates a ticket purchase voucher 717 that may be used in
such an embodiment to purchase more than one ticket. Ticket purchase voucher
717
has ticket information section 732 and a machine readable ticket purchase code
736 in
a ticket purchase voucher code section 734. Ticket information section 732
sets out a
player's selections for three on-line lottery tickets. In the lottery
database, proposed
ticket information for all three tickets is recorded within or accessible from
the ticket
purchase voucher record for the ticket purchase voucher 717. When ticket
purchase
voucher 717 is scanned at a ticket vending terminal 104, the ticket vending
terminal
transmits the ticket purchase voucher code to the ticket server. The ticket
server issues
all three tickets and the player receives three corresponding ticket receipts
114.
[186] In the embodiments described above, a player presents a ticket purchase
voucher 113 to a ticket vendor in step 3102 of method 3100 to purchase a
ticket. A
ticket purchase voucher may also be used to purchase a ticket from a player
operated
ticket vending terminal. The player may scan the barcode of the ticket
purchase
voucher at the player operated ticket vending terminal, which then
communicates with
the lottery computer system and prints a ticket receipt or receipts
corresponding to the
ticket vending terminal, as described above.
[187] In the embodiments described above, a player will typically pay a ticket
vendor for tickets purchased by the player in step 3106 of method 3100. In
other
-59-

CA 02626207 2007-10-11
embodiments, the player may be able to link a payment service to the player's
account.
For example, the player may be able to record a credit card number, debit card
number,
bank account or other payment service in association with the player's
account. In
some embodiments, information required to complete a payment using the payment
service may be recorded in the player account record for the player account.
When the
player uses a ticket purchase voucher to purchase a ticket or tickets, the
ticket server
may obtain payment from the payment service prior to issuing a ticket or
tickets in step
3106. Optionally, the player may be able to may be required to enter a
password or
authentication code at the ticket vending terminal before the payment is
authorized by
the payment service.
[188] In each of the embodiments described above, a player obtains a printed
ticket purchase voucher at a player terminal. The ticket purchase voucher code
is
provided to a ticket vending terminal by scanning the ticket purchase voucher
code from
the ticket purchase voucher. In other embodiments, the player may be able to
provide a
ticket purchase voucher code to a ticket vending terminal in another form.
[189] In some embodiments, in step 3018 of method 3000, the player account
server provides a version of the ticket purchase voucher in which the ticket
purchase
voucher code may be displayed on the screen of a portable player terminal such
as a
PDA or cell phone. For example, a version of the ticket purchase voucher may
be
provided which displays the ticket purchase voucher code as a bar code on the
screen.
The player may be able to store the ticket purchase voucher in the portable
player
terminal. The player may then purchase tickets by displaying the ticket
purchase
voucher on the screen of the portable player terminal and scanning the
displayed bar
code at a ticket vending terminal or allowing a ticket vendor to do so during
step 3104 of
method 3100.
[190] In other embodiments, a ticket vending terminal may be configured to
receive a ticket purchase voucher code through a radio frequency or optical
signal. For
example, in step 3018, the player account server may provide a ticket purchase
voucher
code in a numeric form or a coded form that can be transmitted by a portable
player
terminal. The ticket purchase voucher code may be stored on the portable
player
terminal. During step 3104, the player may cause the portable player terminal
to
-60-

CA 02626207 2007-10-11
transmit a radio frequency or optical signal (such as an infra-red signal)
including the
ticket purchase voucher code to a ticket vending terminal with a corresponding
receiver.
In other embodiments, the player may physically couple the portable player
terminal to
the ticket vending terminal with a cable and may transmit an electronic signal
including
the ticket purchase voucher code.
[191] Any other method may be used to input a ticket purchase voucher code
into a ticket vending terminal. For example, in some embodiments, a player or
ticket
vendor may be able to manually enter a ticket purchase voucher code into a
ticket
vending terminal using a keypad.
[192] In system 100, a player uses a ticket purchase voucher that is
associated
with the player's account to identify the player's account when purchasing
tickets.
Tickets purchased with a ticket purchase voucher are associated with the
player's
account. In other systems, players are able to use other methods of
associating a ticket
with an account in addition to or as an alternative to the use of a selection
slip 112 with
an account identification region. For example, a player may use a selection
slip that
has an account identification region, as is described in PCT patent
application No.
PCT/CA2006/000270. The player identifies the player's account on a selection
slip and
tickets purchased with the selection slip are associated with the player's
account.
[193] Reference is made to Figure 13, which illustrates another system 1400
according
to the present invention. System 1400 illustrates additional methods by which
a player
may purchase a ticket that is associated with the player's account.
[194] A player may be able to purchase a ticket associated with the player's
account
on the Internet after logging into the player's account by providing the
player's account
identification code and password. In Figure 13, direct Internet based sales
are
illustrated by dashed line 1470 in relation to player terminal 1406c. The
lottery operator
may provide a ticket purchase web page and allow a player to select played
number
sets and other options, including automatically selected number sets for a
ticket. The
player is then permitted to purchase the ticket and may be able to pay for
ticket using a
deposit account previously established with the lottery operator or using a
credit or debit
account (such as a credit card, debit card or check card). Tickets purchased
by a
player while logged into the player's account (i.e. after the player has
authenticated the
-61-

CA 02626207 2007-10-11
player's right to access the player's account by providing the player's
account
identification - code and password) are associated with the player's account.
After
purchasing a ticket in this fashion, the player may be permitted to print a
corresponding
ticket receipt 114 at the player's terminal.
[195] Another method for purchasing tickets associated with a player account
is
the use of a player account identification device. In Figure 13, ticket sales
made using a
player account identification device 1476 are illustrated in relation to
ticket vending
terminal 1404e.
[196] Figure 14 illustrates a selection slip 1512. Figure 14 also illustrates
a player
identification card 1502, which is an example of a player identification
device 1476.
Player identification card 1502 includes a card identifier 1504, which in this
example is a
bar code that is unique to the particular player identification card 1502. A
player
identification device 1476 may also optionally include other information, such
as the
name or logo of the lottery operator, the name of a player to whom the player
identification device is assigned and instructions for use of the player
identification
device 1476.
[197] A player may use an account identification device 1476 to identify the
player's
account if a lottery operator does not provide an account identification
region on the
lottery operator's selection slips.
[198] Player identification devices 1408 may take various forms. In some
cases, the
lottery operator may provide a player with an account identification card that
includes a
magnetic strip or a barcode. A card identifier is encoded onto the magnetic
strip or in
the barcode, allowing the account identification card to be identified.
Referring to Figure
15, in such an embodiment, the lottery database 1460 includes an
identification card
table 1478 containing a plurality of identification card records 1480.
Identification card
records are associated with player accounts, typically by identifying the
player account's
account identification code in the identification card record 1478. Figure 15
illustrates
three example association between an identification card record 1478, in which
a card
identifier is set out, and a player account record 514.
[199] In other embodiments, the player's account identification code is
directly encoded
onto the magnetic strip or into the bar code and an identification card table
may not be
-62-

CA 02626207 2007-10-11
required.
[200] A lottery operator may alternatively or additionally provide players
with account
identification devices such as:
- a key fob that contains a bar code, magnetic strip or a radio frequency
identification (RFID) tag;
-an RFID device;
-a proximity card; or
-any other card or device that may be identified by using a corresponding
reader
or scanner coupled to a ticket vending terminal 1404.
[201] The lottery operator may alternatively or additionally allow a player to
print an
account identification card at a player terminal. The player may access the
player's
account, by logging into the player website and may access an account
identification
card printing service. The service allows the player to print a card including
a bar code
that encodes a card identifier or the players' account identification code (or
both). The
player may use the printed account identification card to purchase tickets in
the same
manner as a card provided by a lottery operator.
[202] Reference is made to Figure 16, which illustrates a method 2800. Method
2800
allows a lottery operator to sell a ticket to a player using a player
identification card 1502
(Figure 14) and correspondingly allows a player to buy a ticket using a player
identification card.
[203] Method 2800 begin in step 2802, in which a player presents the player's
account
identification card to a ticket vendor. The player may also optionally present
the vendor
with a selection slip 1512 (Figure 14) on which the player has completed the
play region
1520, or the player may request a ticket with one or more automatically
selected played
number sets for a particular on-line lottery.
[204] Method 2800 then proceeds to step 2804, in which the ticket vendor scans
the
player's account identification card using an appropriate scanner (not shown)
coupled to
the vendor's ticket vending terminal 104. If the player has presented a
selection slip
1512, the ticket vendor scans the selection slip. If the player has requested
a ticket with
automatically selected player number sets, the ticket vendor enters the
player's request
into the ticket vending terminal.
-63-

CA 02626207 2007-10-11
[205] The ticket vending terminal transmits a Ticket Issue Request 552 to the
ticket
server 1464. The Ticket Issue Request 552 identifies the player's account
identification
card and includes details of any tickets requested by the player. In the
present
example, the player identification card 1502 includes a card identifier which
is included
in the Ticket Issue Request 552 to identify the player identification card. In
an
embodiment in which the player identification card 1502 (or more generally,
the player
identification device 1476) includes the player's account identification code
itself, the
account identification code is included in the Ticket Issue Request.
[206] Method 2800 then proceeds to step 2805, which is performed only if the
Ticket
Issue Request 552 sent in step 2804 includes a card identifier rather than an
account
identification code. In embodiments in which the Ticket Issue Request of step
2804
includes a player's account identification code, method 2800 proceeds to step
2806
after step 2804. In step 2805, the Ticket Server 1564 looks up the account
identification
code corresponding to the card identifier in the identification card table
1478.
[207] Method 2800 then proceeds to step 2806. Step 2806 corresponds to step
3106
of method 3100 and is not further described.
[208] Method 2800 allows a player to purchase a ticket using an account
identification
device 1476 and a selection slip. The ticket is associated with the player's
account in
step 2806.
[209] In different embodiments, an lottery operator may permit a player to buy
a ticket
and have the ticket associated with the player's account using any one or more
of the
methods described above, including the use of a selection slip with an account
identification region, use of a ticket purchase voucher, Internet based
purchase or with
the use of an account identification device, or by any other means that allows
a player
to identify the player's account when purchasing a ticket.
[210] Reference is next made to Figure 17. For each on-line lottery, the
lottery
operator conducts a draw of the on-line lottery at the appointed date and
time. In the
case of a host on-line lottery with an associated on-line lottery, the lottery
operator
typically conducts a draw of both the host and associated on-line lotteries,
depending on
the rules for the on-line lotteries. In the present embodiment, the lottery
operator then
checks each ticket that is valid for the draw by comparing the played number
sets for
-64-

CA 02626207 2007-10-11
each ticket valid for the draw with the corresponding winning number sets to
determine
if the ticket has won any prizes and to determine the value of any shared
prizes. Figure
9 illustrates a method 2300 that a lottery operator may use to do so. Method
2300 will
be explained using an example based on the October 31, 2003 draw date for the
host
Lotto 7/47 on-line lottery and associated Tag on-line lottery and with
reference to Lotto
7/47 ticket L3 (Figure 6a), which corresponds to ticket receipt 118 (Figure
2).
[211] Method 2300 begins in step 2302 in which the lottery operator conducts
the draw
of the on-line lottery or lotteries.
[212] In the present example based on the November 18, 2005 draw of the Lotto
7/47
on-line lottery, the lottery operator draws a winning number set for the host
Lotto 7/47
on-line lottery and a winning number for the associated Tag on-line lottery.
The winning
number set for the Lotto 7/47 on-line lottery consists of the winning numbers
8, 12, 17,
23, 32, 43, 47 and bonus number 6. The winning number for the associated Tag
on-line
lottery is 258952.
[213] Method 2300 then proceeds to step 2304, in which the lottery operator
updates
the winning number field or fields in the appropriate draw record 518 for the
draws
conducted in step 2302 in the appropriate draw table 504. In the present
example, the
lottery operator updates the draw record 518 for the October 31, 2003 draw in
the Lotto
7/47 draw table 516. The lottery operator records the Lotto 7/47 winning
number set in
the Lotto 7/47 Winning Number Set field and records the Tag winning number in
the
Tag Winning Number field as follows:
Lotto 7/47 8, 12, 17, 23, 32, 43, 47 Bonus number 6
Winning Number
Set
Tag Winning 258952
Number
[214] Method 2300 then proceeds to step 2306, in which an on-line lottery
ticket
checking program (not shown) is executed by the lottery operator. The on-line
lottery
ticket checking program is executed on the lottery computer system 102 and has
access to the lottery database 160. The on-line lottery ticket checking
program uses the
-65-

CA 02626207 2007-10-11
Draw Ticket List field in the draw record 518 for the draw conducted in step
2302 to
obtain the ticket record 524 (Figure 6a) for each ticket valid for the draw.
The on-line
lottery ticket checking program compares the played number sets on each ticket
to the
corresponding winning number sets for the draw and updates the Prize Data
field in the
ticket record for the ticket based on the comparison. The on-line lottery
ticket checking
program counts the number of winning played number sets for each different
winning
combination for each lottery to allow the lottery operator to determine the
value of any
shared prizes and for information purposes. In other embodiments, the on-line
lottery
ticket checking program may count only the number of winning number sets for
winning
combinations that have shared prizes.
[215] If a ticket is valid for more than one draw, the played number sets on
the ticket
are compared to the corresponding winning numbers sets after each draw and the
Prize
Data field in the ticket record 524 is updated to reflect the results for the
ticket as of the
most recent draw. If all of the draws for which the ticket is valid have been
conducted,
the on-line lottery ticket checking program also updates the Ticket Status
field in the
ticket record 524. If the ticket has won a prize (in the draw conducted during
the current
performance of method 2300 or in a previous draw) the ticket status is changed
to
"Winner-Not Redeemed". If the ticket has not won any prize in any draw, the
Ticket
Status is changed to "Not A Winner . If the ticket is still valid for future
draws, the Ticket
Status remains "Draws Not Complete".
[216] Typically, the on-line lottery ticket checking program will check each
ticket valid
for the draw conducted in step 2302 in turn. Referring to Figure 6b, tickets
L2 and L3
are checked for the November 18, 2005 draw. Ticket L2 is not valid for any
subsequent
draws and the Ticket Status field for that ticket will be set to "Not a
Winner" or "Winner-
Not Redeemed".
[217] When each ticket valid for the draw conducted in step 2302 has been
checked to
determine the results for the ticket in the draw, the lottery ticket checking
program
records the number of played number sets that have won prizes for each of the
winning
combinations for each draw conducted in step 2302. Method 2300 then proceeds
to
step 2308.
[218] In the present example, in step 2306, the result of comparing the played
number
-66-

CA 02626207 2007-10-11
sets to the corresponding winning numbers for the November 18, 2005 draw gives
the
following results:
Lotto 7/47 played number set 1: 4/7 regular winning numbers
Lotto 7/47 played number set 2: No winning combination
Tag played number 1: No winning combination.
[219] Based on these results, the on-line lottery ticket checking program
increments
the count of the number of played number sets that have won the fifth prize in
the
October 31, 2003 Lotto 7/47 draw and also updates the Prize Data field in
ticket record
525. The Prize Data field has the following information in it after it is
updated:
Prize Data November 18, 2005
Lotto 7/47 played number set 1: 4/7 regular numbers
Lotto 7/47 played number set 2: Not a winner
Tag played number 1: Not a winner
[220] Ticket L2 is still valid for additional draws and accordingly, the
Ticket Status for
the ticket remains Draws Not Complete.
[221] In step 2308, the lottery operator determines the value of any shared
prizes
based on the number of winners for each winning combination, according to the
rules of
each on-line lottery. The lottery operator then updates the prize information
fields in the
draw records for the completed draws.
[222] In the present example, the lottery operator calculates the value of
each prize for
the November 18, 2005 draw of the Lotto 7/47 on-line lottery and updates the
Lotto 7/47
Prize Information field in the draw record 518 for the draw. The Free Ticket
Prize and
all of the prizes for the Tag on-line lottery are fixed prizes and no
calculation is required.
These fixed prizes are also recorded in the draw record 518 for the draws.
[223] This information is stored in the draw record 518 for the November 18,
2005
draw in the following fields:
Lotto 7/47 Prize Winning Combination Prize Value Winners
Information 7/7 regular numbers $2,500,000 1
6/7 reg. numbers + bonus $342,849 5
6/7 regular numbers $6,293 203
5/7 regular numbers $146 2,839
-67-

CA 02626207 2007-10-11
4/7 regular numbers $28 10,020
3/7 reg. numbers + bonus $32 7,324
3/7 regular numbers Free Ticket 784,893
Tag Prize Prize Winners
Information All six digits 2
Last five digits 34
Last four digits 239
Last three digits 2894
First and last digits 34,230
First digit 333,902
Last digit 273,294
[224] After step 2308, method 2300 ends.
[225] Steps 2304, 2306 and 2308 may be automated using a computer program,
which
would include the on-line lottery ticket checking program described above in
reiation to
step 2306. The lottery operator may input the winning number set into the
computer
program and the total value of the shared prizes (if any), or the information
required to
calculate the total value of the shared prizes. The computer program can then
carry out
all three steps. Alternatively, the lottery operator may carry out step 2304
or 2308 or
both separately from the on-line lottery ticket checking program of step 2306.
The
lottery operator may provide the winning number set to the lottery ticket
checking
program to allow it to carry out the necessary comparisons. The on-line
lottery ticket
checking program of step 2306 may process a host on-line lottery and any
associated
on-line lottery or separate programs may be used to determine the results for
each
ticket for the different on-line lotteries. A skilled person will be capable
of providing one
or more computer programs to carry out the comparisons and data operations
required
depending on the particular structure of any particular on-line lottery or
lotteries and
data storage techniques with which the invention is used.
[226] Method 2300 allows a lottery operator to conduct a draw for an on-line
lottery and
to determine the results for each played number set on each ticket that is
valid for the
draw. The lottery operator can determine the number of winning played number
sets for
-68-

CA 02626207 2007-10-11
each winning combination for the draw. If the lottery operator has conducted a
draw for
a host on-line lottery and an associated on-line lottery, the lottery operator
may use
method 2300 to calculate the number of winning played number sets for each on-
line
lottery. In addition, the lottery operator may calculate the value of any
shared prizes
based on the total prize value allotted for a particular winning combination
and the
number of winners for that winning combination. The lottery operator may
update the
ticket record for each ticket to record the results for the ticket. The
lottery operator may
also update the draw record for the completed draw to record the number of
winning
played number sets for each winning combination, and the value of some or all
of the
prizes for each on-line lottery, depending on the information stored in the
draw records
in any particular embodiment of the invention.
[227] Reference is next made to Figure 18. For each on-line game, the lottery
operator
updates the event table 508 for the on-line game after each event is
completed.
Method 2400 illustrates a method used by the lottery operator in the present
exemplary
embodiment to update the event tables 508 for on-line games, to check on-line
game
tickets and to update on-line game ticket records 538. Method 2400 will be
explained
with reference to the Sports Line on-line game, event 60 in that on-line game
and ticket
SL3 (Figure 6b), which corresponds to ticket receipt 318 (Figure 4).
[228] Method 2400 is performed by the lottery operator for each event in an on-
line
game. Method 2400 begins in step 2402, in which the lottery operator waits for
the
event to be completed.
[229] In the present example, the lottery operator waits until the NFL
football game
between Dallas and Philadelphia on November 13, 2006 is completed.
[230] After the event has been completed, method 2400 proceeds to step 2404.
In
step 2404, the lottery operator updates the Actual Outcome field in the event
record 534
for the event that has been completed.
[231] For the purposes of the present example, the NFL football game is
assumed to
have ended with Dallas winning the game 31-18, according to the standards
rules for
NFL football. According to the rules set by the lottery operator for the
Sports Line on-
line game, the home team is the winner since Dallas won the game by more than
three
points. The Actual Outcome field of the event record 534 for event 60 in
Sports Line
-69-

CA 02626207 2007-10-11
Event Table 532 is updated as follows:
I Actual Outcome Home Win
[232] Method 2400 then proceeds to step 2406, in which the lottery operator
executes
an on-line game ticket checking program (not shown). The on-line game ticket
checking
program is executed on the lottery computer system 102 and has access to the
lottery
database 160. The on-line game ticket checking program checks each on-line
game
ticket that matured with completion of the completed event, based on the
Maturation
Event field in the ticket record 538 for the ticket. In the present
embodiment, the
Maturation Event Index for the on-line game ticket able 510 (Figure 6b) is
used to
identify each ticket record that identifies the newly completed event in the
Maturation
Record field.
[233] For each ticket that matured with the completed event, the game ticket
checking
program compares the player's prediction set (set out in the Predicted
Outcomes field in
the ticket record 538) with the actual outcomes of the corresponding events
and
determines if the player has won the bet made on the ticket. If, according to
the rules
for the on-line game, the player has won the bet, the Ticket Status field in
the ticket
record 538 is updated by changing the ticket status to "Winner-Not Redeemed".
If the
player has lost the bet, then the Ticket Status field in the ticket record 538
is updated by
changing the ticket status to "Not a Winner". If a ticket record 538
identifies the
completed event in its Maturation Event field, but some of the other events
have not
been completed when on-line game checking program is executed, then one of the
Maturation Event field is changed to identify one of the uncompleted events.
If the
expected ending time of the uncompleted events can be estimated, then the
event with
the latest expected ending time is identified in the Maturation Event field.
The ticket
status for tickets that do not mature with the completion of the completed
event is not
changed.
[234] The on-line game ticket checking program will check each ticket that
matured
with the completion of the completed event in turn. Referring to Figure 6b,
four tickets
in the Sports Line Ticket Table for List 8845 become mature with the
completion of
event 43: tickets SL2, SL3, SL4 and SL6.
-70-

CA 02626207 2007-10-11
[235] In the present example, the bet made by the player (Karina Jones) on
ticket SL3
is based on four events: event 17, event 18, event 45 and event 60 set out for
the
Sports Line on-line game in List 8845. The actual outcome for event 60 is a
Home
Wine, according to the rules for the Sports Line on-line game, as described
above at
step 2404. For the purposes of the present example, it is assumed that the
actual
outcomes of the other events are as follows: Event 17 - Visitor Win; Event 18 -
Home
Win; and Event 45 - Visitor Win. After events 17, 18 and 45, method 2400 would
have
been carried out. However, ticket SL3 would not be checked in step 2406 after
those
events, since the ticket did not mature with the completion of any of those
events. In
both cases, the ticket status would have been left as "Events Not Complete".
[236] With the completion of event 60, ticket SL3 matures and the on-line game
ticket
checking program checks ticket SL3 during step 2406. The on-line game ticket
checking program compares the prediction set for the on-line game ticket with
the actual
outcomes of the corresponding events, with the result that the player
correctly predicted
the outcome of each event. The player has won the bet on ticket SL3. The
ticket
checking program changes the Ticket Status field to "Winner-Not Redeemed". The
player is entitled to redeem the on-line game ticket for the Payout Value of
$124.80.
[237] Similarly, the ticket checking program checks tickets SL2, SL4 and SL6
and
changes their Ticket Status fields to "Winner-Not Redeemed" or "Not a Winner".
When
all the tickets maturing with the completion of event 60 has been checked by
the on-line
game ticket checking program, method 2400 ends.
[238] Event 60 in the Sports Line on-line game is also an event in the
Over/Under on-
line game. In the present exemplary embodiment, method 2400 is carried out
separately in relation to the Over/Under on-line game after the completion of
each event
for that on-line game. In an alternative embodiment, a lottery operator may
combine the
processes of checking tickets for different on-line games, particularly if the
on-line
games are based on the same events.
[239] Method 2400 allows a lottery operator to update an event record 534 for
a
completed event and to update the ticket record 538 for each ticket that
matures with
the completion of the event. In the present embodiment, a lottery operator may
choose
to perform method 2400 after the completion of each event, without regard for
the
-71-

CA 02626207 2007-10-11
completion of other events.
[240] In another embodiment, a lottery operator may choose to perform steps
2402
and 2404 in respect of two or more events, and then perform method 2406 in
respect of
each of the events. For example, a lottery operator may allow a group of
events (such a
group of sports events held on a particular day) to be completed and update
the event
record for each of the events based on the outcome of each event. After the
group of
events is complete, the lottery operator may perform step 2406 in respect of
all of the
events by configuring the ticket checking program to check any ticket that
matures with
any event in the set. This allows the lottery operator to determine the
results for all
tickets that matured with the completion of one or more the events in the
group (i.e. all
tickets that matured on a particular day) and to update the ticket records for
each of the
tickets.
[241] In another system, on-line game ticket records may have a Maturation
Date field
rather than a Maturation Event field. The lottery operator waits until all
events on a
particular day are complete and updates the event records for each such event,
effectively performing steps 2402 and 2404 in respect of each event.
Subsequently, the
lottery operator performs step 2406 and configures the on-line game ticket
checking
program to check each ticket that matures on the particular day.
[242] System 100 and other embodiments described above allow players to
purchase
tickets for on-line lotteries and on-line game and have those tickets
associated the
player's account with a lottery operator. Various methods have been described
for
allowing a player to identify the player's account when purchasing a ticket
and for
associating the ticket with the player's account.
[243] Reference is next made to Figure 19, which illustrates method 2600.
Method
2600 allows a player to access the lottery computer system 102 (Figure 1) to
obtain
information about tickets associated with the player's account.
[244] Method 2600 begins in step 2602 in which a player uses a player terminal
106 to
access the player account server 162 and to request access to an account
checking
service. The player uses a player terminal 106 to communicate with a player
interface
166 to allow the player to obtain information stored in the lottery database
160. Method
2600 will be described by way of example with reference to the exemplary
player
-72-

CA 02626207 2007-10-11
account for Karina Jones. Karina Jones uses player terminal 106c to access the
player
account server 162. Player terminal 106c is a personal computer coupled to
public
network 110 and is configured with a web browser capable of displaying web
pages,
including web pages provided by player website 167a (Figure 1).
[245] Karina Jones accesses by entering her account identification code and
password
on the welcome web page 602 (Figure 8) of the player website 167a, as is
described
above in relation to step 3002 of method 3000 and presses "Enter".
[246] Method 2600 then proceeds to decision step 2604. In step 2604, the
player
account server 162 attempts to authenticate the account identification code
and account
password entered by the player in step 2602. If a player account record 514
matching
the entered account identification code and account password exists in the
player
account table 512 (Figures 6a and 6b), then the account identification code
and
password are authentic and method 2600 proceeds to step 2608. Otherwise,
method
2600 proceeds to step 2606.
[247] In step 2606, an error message is displayed on the player terminal 106
indicating
that the player has entered an invalid account identification code or an
invalid password
(or both). Method 2600 then ends.
[248] In step 2608, the player is provided with an opportunity to use various
services,
including an account checking service. The player chooses the account checking
service, which allows the player to obtain information relating to the
player's tickets.
The player account server 162 obtains information about the player's tickets
from the
lottery database 160. The player account server 162 transmits information
about the
player's tickets to the player terminal 106 using the player interface with
which the
player terminal 106 is communicating. The information transmitted to the
player
terminal 106 is displayed for the player to view.
[249] In the present exemplary embodiment, the player interface 166 provides
several
types of reports to a player about tickets associated with the player's
account. Each
report is based on information recorded in the lottery database 160. The
different report
information about the player's account and the player's tickets in varying
levels of detail.
The player account server 162 extracts detailed information about individual
tickets from
the lottery database 160 and provides detailed ticket status reports. The
player account
-73-

CA 02626207 2007-10-11
server also provides an account summary report which includes summary
information
about the player's tickets and summary information about individual tickets.
Some of
the information provided by the player account server 162 may be calculated
based on
information recorded in the lottery database 160.
[250] In the present example, the player interface 166a formats the reports so
that they
are suitable for display in a web browser operating on Sonia Smith's player
terminal
106c. The player interface then transmits the formatted report to the player
terminal
where it is displayed.
[251] Reference is next made to Figure 20, which illustrates an on-line
lottery ticket
summary report 700 for the exemplary player account for Karina Jones. Account
summary report 700 is displayed by the web browser on the player's terminal
after she
accesses the player account server as described above in steps 2602 and 2604.
[252] Player interface 166a generates on-line lottery ticket summary report
700 as a
web page based on the contents of the lottery database 160 at the time account
summary report 700 is displayed.
[253] On the account summary report 700, the date and time that account
summary
report 700 was generated is set out at 702. The player's account
identification code is
set out at 704. The account information page 700 includes an account summary
section 706 and a ticket summary section 708.
[254] In the account summary section 706, various information relating to the
player's account and to tickets associated with the player's account is set
out. In the
present exemplary account information page 700, the prizes won by the player
in on-
line lotteries and on-line games are summarized. The summary indicates that
the
player has unredeemed prizes and has won prizes on tickets with draws
remaining.
The summary also provides information about on-line game tickets.
[255] The information presented on the account summary report 700 is
calculated based on information about the player's account and the player's
tickets
extracted from the lottery database 160. The Player Ticket List field in the
player
account record 514 for the player's account is used to identify the player's
tickets. The
corresponding on-line lottery ticket records 524 (Figure 6a) and on-line game
ticket
records 538 (Figure 6b) are reviewed to determine what prizes, if any, the
player's
-74-

CA 02626207 2007-10-11
tickets have won, if any draws or events are remaining for the tickets and
which, if any,
prizes have been redeemed. The player interface 166a calculates the summary
values
presented in the account summary section 706 based on the extracted data.
[256] In the ticket summary section 708, information about each of the on-line
lottery tickets associated with the player's account is set out.
[257] The player may view an on-line game ticket summary page (not shown) by
clicking on the "Click here to see results for you on-line game tickets"
button 760.
[258] In the present embodiment, the lottery operator allows winning tickets
to
be redeemed within one year of the on-line lottery draw or on-line game events
that the
ticket relates to. After the one year period, a ticket becomes expired and
invalid. The
account summary section 706 and the ticket summary section 708 include
information
relating to the valid tickets associated with the player's account.
[259] While viewing an on-line lottery ticket summary report or an on-line
game
ticket summary report, a player may use method 3200 (Figure 21) to obtain a
prize
redemption voucher.
[260] A player may also be able to obtain detailed information about tickets
listed in the ticket summary reports. Examples of detailed ticket status
reports are
illustrated in PCT Application No. PCT/CA2006/000270. Detailed ticket status
reports
for winning tickets may include a button to select the winning ticket to be
added to a
prize redemption voucher.
[261] While using the account checking service, a player may view information
about
the player's account as permitted by the lottery operator. The player may
navigate
between different reports, depending on the options provided by the lottery
operator.
When the player has finished accessing the player's account, method 2600 ends.
[262] Reference is made to Figure 21, which illustrates a method 3200 by which
a player can generate a prize redemption voucher 133. A player may use method
3200
during step 2608. Method 3200 will be explained with reference to player
Karina Jones
creating a prize redemption voucher to claim prizes for several tickets.
[263] Method 3200 begins in step 3202 in which a player selects one or more
tickets for which to create a prize redemption voucher 133. Ticket summary
section 708
identifies two unredeemed winning tickets that do not have any draws
remaining. The
-75-

CA 02626207 2007-10-11
player may redeem these winning tickets for the corresponding prizes. Each
winning
ticket that may be redeemed has a prize redemption voucher selection box 762
adjacent to the prize won by the ticket. The player clicks the corresponding
prize
redemption voucher selection box 762 for each ticket that the player wishes to
redeem
with a prize redemption voucher. In Figure 20, the player has chosen to redeem
both
unclaimed prizes. Alternatively, the player may have selected only one of the
unredeemed winning tickets if the player preferred to obtain a prize
redemption voucher
for only one of the tickets. When the player has selected the prizes the
player wishes to
redeem, the player clicks on the "Generate Prize Redemption Voucher" button
764.
[264] Method 3200 proceeds to step 3204, in which a Prize Redemption
Request 3220 (Figure 1) is transmitted from the player's terminal to the
player account
server 162. The Prize Redemption Voucher Request 3220 identifies the tickets
for
which the player wishes to generate a prize redemption voucher. In this
example, the
Prize Redemption Voucher Request identifies the following tickets: Lotto 7/47
ticket
5933-2245-5896-5987 and KENO ticket 5254-0258-9963-1912. The Prize Redemption
Voucher Request is transmitted from Karina Jones' player terminal 106c to the
player
interface 166a.
[265] Method 3200 proceeds to step 3206, in which the prize redemption
voucher requested by the player is added to the lottery database 160. The
player
account server 162 adds a new prize redemption voucher record 572 (Figure 6a)
to the
prize redemption voucher table 570. The player account server also identifies
the new
prize redemption voucher in the player account record 514 for the player's
account and
in the ticket record 524 (Figure 6b or 6c) for which the prize redemption
voucher is
requested.
[266] In this example, the player account server 162 creates prize redemption
voucher record 577 (Figure 6a), which has the following contents:
Field Information recorded in field
PR Voucher Code P9875-7829-83-29
Player account ID KARINA1022
code
-76-

CA 02626207 2007-10-11
Field Information recorded in field
Winning Ticket List 5933-2245-5896-5987
5254-0258-9963-1912
Total Prize $20
[267] Player account server 162 also adds the new voucher to the Player Prize
Redemption Voucher List in the player record 514 for Karina Jones' player
account.
The Player account server 162 also adds the new voucher to the Associated
Prize
Redemption Voucher field in the ticket record 524 for both of the tickets
selected by the
player.
[268] Method 3200 then proceeds to step 3208, in which the player account
server transmits a prize redemption voucher 133(Figure 1) to the player
terminal from
which the Prize Redemption Voucher Request 3220 originated in step 3204 and in
which a paper copy of the prize redemption voucher is printed at the player's
terminal
(or another device) by the player. The prize redemption voucher includes the
prize
redemption voucher code in a form or version suitable for scanning at a ticket
vending
terminal 104.
[269] In addition to generating the prize redemption voucher, the player
account
server may also generate a version of the prize redemption voucher that is
suitable for
display at the player terminal from which the Prize Redemption Voucher Request
3220
was received. This version may be generated by the player interface 166 that
is
communicating with the player terminal 106. For example, "dumb" player
terminals (for
example a device connected via a teinet connection) may simply receive and
display
text from a player interface and may just detect and transmit keystrokes and
other input
from the player to the player interface. A player interface for such a dumb
terminal may
transmit text corresponding to the prize redemption voucher to the player
terminal. The
text may include instructions for the player to download the prize redemption
voucher,
which the player can then print at his player terminal or at another device.
When the
player follows the instructions, the prize redemption voucher is transmitted
to the player.
[270] In the Karina Jones example, the player is communicating with player
interface 166a, which controls the display of webpages from player website
167a on her
-77-

CA 02626207 2007-10-11
player terminal 106c. Player interface 166a generates a webpage that iricludes
information corresponding to the prize redemption voucher (which will
generally include
text setting out some or all of the contents of the prize redemption voucher).
The
webpage is transmitted to the player interface where it is displayed. The
webpage
includes a "Print Prize Redemption Voucher" button. When the player clicks the
button,
the voucher is transmitted to the player interface and player can print the
voucher at the
player terminal or at another device. In other embodiments, the voucher may be
transmitted to the player terminal before the player clicks the button.
[271] Figure 22 illustrates an example prize redemption voucher 3224 for the
Karina Jones example. Prize redemption voucher 3224 has a prize redemption
voucher
information section 3226 and a prize redemption voucher code section 3228.
Information about the prize redemption voucher and the tickets associated with
the prize
redemption voucher is set out in the prize redemption voucher information
sectiori 3226.
No particular is needed in this section and it may contain any information the
lottery
operator chooses. In this example, the prize redemption voucher information
section
includes the player's account identification code, the total prize for tickets
associated
with the prize redemption voucher and a list of the associated tickets. Prize
redemption
voucher code section 3228 includes the prize redemption voucher code in a
machine
readable form at 3230. Optionally, the prize redemption voucher code may also
be set
out on the prize redemption voucher in a human readable, as is illustrated in
prize
redemption voucher code section 3228.
[272] In another embodiment, the prize redemption voucher may be transmitted
to the player without any additional version of it. The player terminal may be
able to
display the voucher in addition to printing it. In some embodiments, the
player may only
be able to print the voucher without seeing a display of it.
[273] Method 3000 then ends.
[274] Reference is next made to Figure 23, which illustrates a method 3300 by
which a player may use a ticket purchase voucher 133 to redeem prizes for one
or more
tickets.
[275] Method 3300 begins in step 3302, in which the prize redemption voucher
133 is scanned at a ticket vending terminal 104. A player may give the prize
-78-

CA 02626207 2007-10-11
redemption voucher 133 to a ticket vendor who then scans the prize redemption
voucher code at a ticket vending terminal. Alternatively, the player may scan
the prize
redemption voucher code using a player operated ticket vending terminal.
[276] Method 3300 then proceeds to step 3304, in which the ticket vending
terminal 104 transmits a Prize Redemption Voucher Redemption Request 3320 to
the
ticket server 164. The Prize Redemption Voucher Redemption Request 3320
identifies
the prize redemption voucher code 3230 of the prize redemption voucher.
[277] Method 3300 next proceeds to decision step 3306. In step 3306 the ticket
server 164 checks the Ticket Status fields of all tickets associated with the
prize
redemption voucher. If all of the tickets have a status of "Winner-Not
Redeemed",
method 3300 proceeds to step 3310. Otherwise, method 3300 proceeds to step
3308.
[278] In some embodiments, the lottery operator may not permit tickets that
are
associated with a prize redemption voucher to be redeemed independently. In
such
embodiments, step 3300 may optionally be omitted. Step 3300 ensures -that in
embodiments where it is possible to redeem an individual ticket by presenting
the
corresponding ticket receipt to a ticket vendor or at a player operated ticket
vending
terminal even if the ticket is associated with a prize redemption voucher, the
same ticket
is not redeemed twice - one individually and once as part of a prize
redemption voucher
redemption.
[279] Optionally, the ticket server 164 may also conduct other checks before
deciding to proceed to step 3310. For example, a lottery operator may set an
expiry
time for a prize redemption voucher. For example a prize redemption voucher
may be
valid for only a week after it is created. After that time, the prize
redemption voucher
record for the prize redemption voucher is marked as expired or removed from
the
lottery database. In such an embodiment, the ticket server 164 will ensure
that the prize
redemption voucher is still valid before proceeding to step 3310. If the prize
redemption
voucher cannot be used for any reason, method 3300 moves to step 3308.
[280] In step 3308, the ticket server transmits a Redemption Rejected Message
(not shown) to the ticket vending terminal from which the Prize Redemption
Voucher
Request 3320 originated in step 3304. Method 3300 then ends.
[281] In step 3310, the ticket server 164 changes the Ticket Status field for
all
-79-

CA 02626207 2007-10-11
tickets associated with the prize redemption voucher to "Winner-Redeemed".
[282] Method 3300 then proceeds to step 3312, in which the ticket server 164
transmits a Redemption Confirmation Message 3322 to the ticket vending
terminal from
which the Prize Redemption Voucher Request 3320 originated in step 3304.
[283] Method 3300 then proceeds to step 3314, in which the player receives the
total prize for all tickets associated with the prize redemption voucher 133.
[284] If the ticket vending terminal 104 is operated by a ticket vendor, the
ticket
vending terminal displays a prize payment authorization message to the ticket
vendor in
response to the Redemption Confirmation Message 3322. The prize payment
authorization message may set out the total amount of the prize to be paid to
the player.
The ticket vendor pays the total prize to the player. If the prizes to be
given to the
player includes any merchandise, free ticket or other non-cash prizes, the
ticket vending
terminal also provides such prizes to the player.
[285] If the ticket vending terminal 104 is operated by a player, the ticket
vending terminal provides the prizes for tickets associated with prize
redemption
voucher to the player. The ticket vending terminal may allow the player to
obtain any
free ticket prizes and any prizes the ticket vending terminal is able to
deliver. For
example, if the ticket vending terminal is configured to distribute cash, the
ticket vending
terminal may pay a cash prize to the player. Alternatively, the ticket vending
terminal
may provide the player with a coupon or coupons to obtain any cash or
merchandise
prizes from a clerk or other person at the location where the player operated
ticket
vending terminal is installed.
[286] In an embodiment in which a player is able to associate a payment
service
with the player's account, the ticket server may pay any cash prize to the
player by
depositing the prize amount to the payment service.
[287] When the player has received the prizes for tickets associated with the
prize redemption voucher, method 3300 ends.
[288] Methods 3200 and 3300 allow a player to obtain a prize redemption
voucher 133 and redeem tickets using the prize redemption voucher. These
methods
may be used to redeem prizes for any winning tickets associated with a player
account,
regardless of the method by which the ticket is associated with the player
account.
-80-

CA 02626207 2007-10-11
[289] Method 3200 and 3300 are described above in an exemplary manner in
relation to on-line lottery tickets. The methods may also be used to obtain a
prize
redemption voucher associated with on-line game tickets and to obtain prizes
won on
on-line game tickets. In some embodiments, a player may be able to select two
or more
winning tickets identified on different screens while accessing the ticket
checking
service. Each selected winning ticket is recorded and after selecting the
winning tickets,
the player may obtain a prize redemption voucher for all of the selected
tickets,, Any
method of identifying the tickets may be used.
[290] In some embodiments, the lottery operator may set limits on the prizes
that may be claimed with a prize redemption voucher. For example, the lottery
operator
may limit the total cash value of the prizes to some maximum dollar amount. In
some
embodiments, the lottery operator may allow only cash prizes to be redeemed
with a
prize redemption voucher. In other embodiments, the lottery operator may allow
only
cash a free ticket prizes to be redeemed with a prize redemption voucher.
[291] In some embodiments, in step 3208 of method 3200, the player account
server provides a version of the prize redemption voucher in which the prize
redemption
voucher code may be displayed on the screen of a portable player terminal such
as a
PDA or cell phone. For example, a version of the prize redemption voucher may
be
provided which displays the prize redemption voucher code as a bar code on the
screen. The player may be able to store the prize redemption voucher in the
portable
player terminal. The player may then purchase tickets by displaying the prize
redemption voucher on the screen of the portable player terminal and scanning
the
displayed bar code at a ticket vending terminal or allowing a ticket vendor to
do so
during step 3302.
[292] In other embodiments, a ticket vending terminal may be configured to
receive a prize redemption voucher code through a radio frequency or optical
signal.
For example, in step 3208, the player account server may provide a prize
redemption
voucher code in a numeric form or a coded form that can be transmitted by a
portable
player terminal. The prize redemption voucher code may be stored on the
portable
player terminal. During step 3302, the player may cause the portable player
terminal to
transmit a radio frequency or optical signal (such as an infra-red signal)
including the
-81-

CA 02626207 2007-10-11
prize redemption voucher code to a ticket vending terminal with a
corresponding
receiver. In other embodiments, the player may physically couple the portable
player
terminal to the ticket vending terminal with a cable and may transmit an
electronic signal
including the prize redemption voucher code.
[293] Any other method may be used to input a prize redemption voucher code
into a ticket vending terminal. For example, in some embodiments, a player or
ticket
vendor may be able to manually enter a prize redemption voucher code into a
ticket
vending terminal using a keypad.
[294] In method 3300 described above, a player is able to redeemi winning
tickets without presenting ticket receipts for the winning tickets a ticket
vendor, or
without scanning the winning ticket receipts at a player operated ticket
vending terminal.
In other embodiments, the player may be required to produce the winning ticket
receipts. For example, the lottery operator may require that ticket receipts
for all
winning tickets associated with a prize redemption voucher must be scanned at
a ticket
vending terminal contemporaneously with the prize redemption voucher before
the
prizes for the winning tickets will be awarded to a player.
[295] In any particular embodiment, a lottery operator may offer only on-line
lotteries or on-line game or may offer both on-line lotteries and on-line
game.
[296] Several embodiments of the invention have been described. In addition,
numerous alternatives embodiments and additional features of the invention
have been
described. A particular lottery operator may combine the various embodiments
and
features to develop other embodiments that utilize the inventions and fall
within the
scope of the following claims.
-82-

Representative Drawing
A single figure which represents the drawing illustrating the invention.
Administrative Status

2024-08-01:As part of the Next Generation Patents (NGP) transition, the Canadian Patents Database (CPD) now contains a more detailed Event History, which replicates the Event Log of our new back-office solution.

Please note that "Inactive:" events refers to events no longer in use in our new back-office solution.

For a clearer understanding of the status of the application/patent presented on this page, the site Disclaimer , as well as the definitions for Patent , Event History , Maintenance Fee  and Payment History  should be consulted.

Event History

Description Date
Time Limit for Reversal Expired 2013-10-11
Application Not Reinstated by Deadline 2013-10-11
Inactive: Abandon-RFE+Late fee unpaid-Correspondence sent 2012-10-11
Deemed Abandoned - Failure to Respond to Maintenance Fee Notice 2012-10-11
Inactive: IPC deactivated 2012-01-07
Inactive: IPC from PCS 2012-01-01
Inactive: IPC expired 2012-01-01
Inactive: Compliance - Formalities: Resp. Rec'd 2009-10-08
Inactive: Declaration of entitlement - Formalities 2009-10-08
Application Published (Open to Public Inspection) 2009-04-11
Inactive: Cover page published 2009-04-10
Inactive: IPC assigned 2008-05-27
Inactive: First IPC assigned 2008-05-27
Inactive: IPC assigned 2008-05-27
Inactive: IPC assigned 2008-05-27
Application Received - Regular National 2008-05-05
Filing Requirements Determined Compliant 2008-05-05
Inactive: Filing certificate - No RFE (English) 2008-05-05
Small Entity Declaration Determined Compliant 2007-10-11

Abandonment History

Abandonment Date Reason Reinstatement Date
2012-10-11

Maintenance Fee

The last payment was received on 2011-10-07

Note : If the full payment has not been received on or before the date indicated, a further fee may be required which may be one of the following

  • the reinstatement fee;
  • the late payment fee; or
  • additional fee to reverse deemed expiry.

Please refer to the CIPO Patent Fees web page to see all current fee amounts.

Fee History

Fee Type Anniversary Year Due Date Paid Date
Application fee - small 2007-10-11
MF (application, 2nd anniv.) - small 02 2009-10-13 2009-10-08
2009-10-08
MF (application, 3rd anniv.) - small 03 2010-10-12 2010-10-12
MF (application, 4th anniv.) - small 04 2011-10-11 2011-10-07
Owners on Record

Note: Records showing the ownership history in alphabetical order.

Current Owners on Record
LOTTO CHECK CORPORATION
Past Owners on Record
BHUPINDER RANDHAWA
Past Owners that do not appear in the "Owners on Record" listing will appear in other documentation within the application.
Documents

To view selected files, please enter reCAPTCHA code :



To view images, click a link in the Document Description column. To download the documents, select one or more checkboxes in the first column and then click the "Download Selected in PDF format (Zip Archive)" or the "Download Selected as Single PDF" button.

List of published and non-published patent-specific documents on the CPD .

If you have any difficulty accessing content, you can call the Client Service Centre at 1-866-997-1936 or send them an e-mail at CIPO Client Service Centre.


Document
Description 
Date
(yyyy-mm-dd) 
Number of pages   Size of Image (KB) 
Description 2007-10-11 82 3,843
Abstract 2007-10-11 1 17
Drawings 2007-10-11 18 500
Claims 2007-10-11 1 3
Representative drawing 2008-12-04 1 6
Cover Page 2009-04-07 2 39
Filing Certificate (English) 2008-05-05 1 168
Reminder of maintenance fee due 2009-06-15 1 110
Reminder - Request for Examination 2012-06-12 1 116
Courtesy - Abandonment Letter (Maintenance Fee) 2012-12-06 1 174
Courtesy - Abandonment Letter (Request for Examination) 2013-01-17 1 164
Correspondence 2008-05-05 1 18
Correspondence 2009-10-08 3 100
Fees 2009-10-08 3 100
Fees 2010-10-12 1 30
Fees 2011-10-07 1 26