Wagering system and method

A wagering system may include a server, an application server, a client device, and a terminal. The wagering system may issue a voucher or a wagering ticket to a client device. Wagers may be placed against the voucher balance and redeemed at the terminal.

BACKGROUND

In certain wagering systems, paper vouchers and tickets may be used to place wagers. However, a user may accumulate many pieces of paper for a single wager. For example, a user may receive a paper voucher, a paper ticket, and an additional paper voucher if the wager is successful. The amount of paper may be multiplied if a user conducts multiple wagers.

DETAILED DESCRIPTION

FIG. 1illustrates an overview of a wagering system100according to one aspect of the disclosure. The system100may include a server110, an application server130, a client device150, and a terminal170.

The server110, application server130, client device150, and terminal170may communicate by the links120,140,160, and180. The links120-180may be any type of communication method or channel, such as a wired or wireless connection. For example, a wired communication channel may be Ethernet, Universal Serial Bus (“USB”), or any other such wired communication channels. A wireless communication channel may be Bluetooth, any type of connection in compliance with IEEE 802.11 (e.g., IEEE 802.11a, IEEE 802.11b, etc.), and other such wireless technologies (e.g., any wireless technology operating in the industrial, scientific, and medical (“ISM”) radio bands). The links may also include communication according to various protocols, including wide area networks, local area networks, personal area networks, virtual private networks, private networks using communication protocols proprietary to one or more companies, cellular and wireless networks such as 3G, 4G LTE and Wi-Fi networks, and various combinations of the foregoing. The links120-180may be over private or public network connections.

The server110may store all active wagers and vouchers currently in use in the wagering system100. The server110may be any type of computer, such as a general purpose computer, and may include a processor112and memory114. The memory114may store information that may be accessed by the processor112. The information may include instructions and data that may be executed or otherwise used by the processor112. The memory114may be any type of memory capable of storing information to be accessed by the processor112. The memory112may be a computer-readable medium, or any other medium that stores data that may be read with the aid of an electronic device, such as a hard-drive, memory card, ROM, RAM, DVD or other optical disks, as well as other write-capable and read-only memories. Systems and methods may include different combinations of the foregoing, whereby different portions of the instructions and data are stored on different types of media.

The data may be retrieved, stored or modified by processor112in accordance with the instructions. For instance, although the system and method is not limited by any particular data structure, the data may be stored in computer registers, in a relational database as a table having a plurality of different fields and records, XML documents or flat files. The data may also be formatted in any computer-readable format. The data may comprise any information sufficient to identify the relevant information, such as numbers, descriptive text, proprietary codes, references to data stored in other areas of the same memory or different memories (including other network locations) or information that is used by a function to calculate the relevant data.

The processor112may be any conventional processor, such as processors in commercially available routers. Alternatively, the processor may be a dedicated controller such as an ASIC or other hardware-based processor. The processor and memory may actually comprise multiple processors and memories that may or may not be stored within the same physical housing. For example, memory may be a hard drive or other storage media located in a server farm of a data center. Accordingly, references to a processor, memory, or computer will be understood to include references to a collection of processors, memories or computers that may or may not operate in parallel.

The server110may also include a transaction database116. In one example, the transaction database116may be stored at the memory114. In another example, the transaction database116may be stored at a separate memory of the server, or may be stored at a separate device apart from the server, such as a remote hard drive. The transaction database116may store all information relating to wagering transactions, which will be described in greater detail below.

The application server130may receive transaction information from the server110and may communicate with the client device150. The application server may be a general-purpose computer, such as the general-purpose computer described above with respect to server110. The application server130may include a processor132and memory134. The processor132and memory134may be any type of processor and memory, such as the processor112and memory114described above. The application server130may be communicatively connected to a client device150by the link140. The link140may be any type of communication channel, such as the wired and/or wireless communication channels described above.

The application server130may also include an application database136. In one example, the application database136may be stored at the memory134. In another example, the transaction database136may be stored at a separate memory of the server, or may be stored at a separate device apart from the server, such as a remote hard drive. In one example, the application database136may store the same information as transaction database116. In another example, the application database may store less than that stored by the transaction database116, which will be discussed in greater detail below.

According to one implementation, the application server130and the server110may be a single device.

The client device150may receive transaction information from the application server. The client device150may be any type of computing device, such as a general-purpose computer or a personal computer. In another example, the client device150may be a mobile device, such as a tablet, a mobile phone, or any other type of handheld wired or wireless device. In this way, the mobile device may have additional components and features in addition to the components described above. For example, the mobile device may have a global positioning component and an orientation component to allow the position and direction of the mobile device. The mobile device may have speech recognition components to allow a user to interact by voice. Additionally, the mobile device may be configured to send and/or receive phone calls, text messages, image messages, and e-mails.

The client device may include a processor152and memory154, such as the processor and memory described above. The client device may be communicatively connected to a terminal170by the link160. In addition to the communication methods and protocols describe above, the link160may include the terminal170scanning machine-readable information displayed on the client device150, and vice versa, as will be described in greater detail below.

The client device150may also include a display156. The display may be any type of display capable of displaying information to a user of the client device, such as an LCD display. The display156may be any size or shape. In one example, the display156may be a touchscreen, such as a capacitive or resistive-type display. In another alternative, the display156may not include a touchscreen input, and the client device may include a separate input, such as a keyboard.

The client device150may also include an imaging device158. The imaging device158may be any type of imaging device, such as a camera. The camera may be any type of camera, such as a CCD- or CMOS-type camera. The imaging device may be capable of taking photographs or reading bar codes, such as linear or 2D bar codes.

The client device150may also store applications in the memory154, such as a wagering application. The wagering application may include a graphic user interface (GUI) that displays information to a user. Such information may include displaying vouchers, tickets, balances, etc. A user may interact with the GUI by a touchscreen or by any other input of the client device.

The client device150may be associated with a Unique Identifier (UID). The UID may be any string of characters that is capable of identifying the client device. The characters may be any type of characters, including alphanumeric or non-alphanumeric characters, and may be arranged according to any base, such as decimal, binary, or hexadecimal. For example, the UID may be a manufacturer's serial number provided with each device. In another example, the UID may be any random string of characters. In yet another example, the UID may be a Rewards Number identifying the user. The wagering application may determine the UID associated with the client device150, or in another example, a user may provide the UID to the wagering application.

The terminal170may be any type of computer, such as a general-purpose computer, as is described above. The terminal170may include a processor172and memory174, such as the processor and memory described above. The terminal may be communicatively connected to the server by the link180, as is described above.

The terminal170may also include a display176. The display176may be any type of display capable of displaying information to a user of the client device, such as an LCD display. The display176may be any size or shape. In one example, the display176may be a touchscreen, such as a capacitive or resistive-type display. In another alternative, the display176may not include a touchscreen input, and the terminal170may include a separate input, such as a keyboard.

The terminal may include an imaging device178. The imaging device178may be any type of imaging device, such as a camera. The camera may be any type of camera, such as a CCD- or CMOS-type camera. The imaging device may be capable of taking photographs or reading bar codes, such as linear or 2D bar codes. According to one implementation, the imaging device178may be a bar code reader. The bar code reader may be a stationary bar code reader, or may be a hand-held bar code reader that may be moved or adjusted with respect to the terminal170.

The terminal170may also include a currency management mechanism182. The currency management mechanism182may include a mechanism to receive, dispense, and store any type of currency, such as paper or coin. The currency management mechanism may also detect an amount of currency deposited or withdrawn by any method, such as visual detection, magnetic detection, or any other detection technique. Additionally, the currency management mechanism may include a card reader to process credit card, debit card, or other card-based transactions. The card reader may also read a Player Rewards Card. The currency management mechanism182may conduct transactions according to many protocols or methods, such as by ACH, PayPal, or PINpocket.

The terminal170may include a wagering program stored at the memory174. The wagering program may be a set of instructions that cause the display176to display a GUI such that a user may interact with the terminal170. For example, the GUI may include a user-account interface, a voucher interface, a wagering interface, and a redemption interface. The user-account interface may display information about a user's wagering account, including the amount of funds available in the user's wagering account. The voucher interface may instruct a user to deposit money and may display an amount of money deposited. The wagering interface may display any number of wagering events, possible outcomes, and potential wagers to be made. The redemption interface may allow a user to redeem any wagers. The GUI may also display current balance information. A user may interact with the GUI by an input, such as a touchscreen on the display176, or any other type of input, such as a keyboard, keypad, arrow buttons, or the like.

The terminal170may be a stand-alone kiosk located near a physical location of a wagering event. In another example, the terminal170may have any geographic location and may not be limited by a physical location of a wagering event. In another example, the terminal170may be a cash register and a bar code scanner, such as those found in a department or convenience store.

FIG. 2is a flow chart illustrating a method200of wagering according to one aspect of the disclosure. While the description below refers to a number of blocks of the method200in a particular order, it should be understood that the order in which the blocks are performed may be modified, and blocks may be added or omitted.

At block202, a voucher may be issued. For example, a user may deposit currency and a voucher valued at the amount of currency deposited may be issued. At block204, a wager may be placed against the value of the voucher, or any other pre-existing balance. At block206, the wager may be redeemed. For example, if a wager is successful, the ticket may have a value according to the type of wager. This wager may be redeemed for currency or an additional voucher.

FIG. 3is a flow chart300illustrating a method of issuing a voucher according to one aspect of the disclosure. While the description below refers to a number of blocks of the method300in a particular order, it should be understood that the order in which the blocks are performed may be modified, and blocks may be added or omitted.

At block302, a user may initiate the wagering application at a client device, such as the client device150. The wagering application may determine the UID of the client device150. In one example, a user may provide the UID to the client device150. In another example, the wagering application may query the memory154of the client device to determine the UID.

The client device150may communicate a query regarding the status of the UID to the application server130. The application server130may query the application database136to ascertain any information associated with the UID. For example, the application database136may store active voucher information, active ticket information, and a voucher balance associated with the UID. The ticket information may include ticket value, ticket price, and the wager outcomes. The application server130may transmit such information to the client device150, where it may be displayed by the wagering application GUI on the display156.

At block304, the link160may be initiated between the client device150and a terminal, such as the terminal170. At this block, the link160between the client device170and the terminal170may be temporarily initiated in order to transmit the UID associated with the client device150to the terminal170. The link160may be established according to any of the communication methods described above. In addition to the methods described above, the imaging device of the terminal170may scan a bar code displayed on the display156of a client device150. The bar code may be any type of bar code, such as a linear or two-dimensional bar code, or any other type of machine-readable bar code. In one example, the bar code may be a QR® or Aztec two-dimensional type bar code. The bar code may represent a UID associated with the client device150.

When the imaging device176scans the bar code displayed on the client device150, the UID associated with the client device150may be transmitted to the terminal170. The terminal170may then communicate the UID to the server110to query the transaction database116as to a current balance associated with the UID. When the UID is transmitted to the server110, any future transactions may be associated with the UID until the terminal170terminates the session associated with the UID. The server110may communicate the balance associated with the UID to the terminal170, and the balance may be displayed at a GUI displayed on the display of the terminal170. Once displayed at the terminal170, a user may determine a balance associated with the client device150.

At block306, currency may be deposited at the terminal170. The currency may be deposited using the currency management mechanism182described above. Such currency may be any combination of cash or coins. Upon deposit of the currency, the current management mechanism may determine the total value of the currency deposited, and the value of the currency may be displayed at the terminal170. The terminal170may securely store the currency until an authorized terminal operator safely removes excess currency from the terminal. In another implementation, a credit card may be used to deposit funds. The terminal170may transmit the value of the added currency to the server110.

At block308, a voucher may be generated at the server based on the currency added at the terminal. The voucher may include a value and a transaction identifier (TID), and may be associated with a UID in the transaction database116. The TID may be any string of characters that is capable of identifying the voucher. The characters may be any type of characters, including alphanumeric or non-alphanumeric characters, and may be arranged according to any base, such as decimal, binary, or hexadecimal. The TID may be generated by the server110.

The voucher may also be associated with a UID, such as the UID provided at block302. The server110may update the transaction database116with an updated balance associated with the UID. For example, if a UID associated with the client device170has a zero balance, a deposit of $50 would result in the issuance of a $50 voucher and a new balance of $50 associated with the UID. The transaction will also associate the TID of the voucher with the UID in the transaction database116.

At block310, the server110may communicate the TID and value of the voucher, as well as the UID, to the application server130. In one implementation, the server110may not communicate certain transaction information stored at the transaction database116, such as transaction time, transaction location, or the like. According to another implementation, the server110may transmit all available information to the application server130. The server110may designate the voucher associated with the TID as locked in the transaction database116such that it may not be accessed at a separate terminal.

The application server130may update the application database136based on the voucher value and may communicate the TID and value of the voucher to the client device150associated with the UID. The client device150associated with the UID may receive the voucher, TID, and value and subsequently display the voucher to a user at block312. The voucher may then be designated as active once transmitted to the client device150such that wagers may be made against the voucher balance by the client device150associated with the UID.

At block314, the server110may transmit updated balance information to the terminal170. The updated balance information may be an updated balance associated with the UID, based on the deposited currency and issued voucher. Once received at the terminal, the terminal may display the updated balance as part of the wagering program GUI at block316.

With the active voucher, a user may place a wager against the balance of the voucher, as will be describe below. Alternatively, a user may log out of one or both of the wagering application or the wagering program. If a user logs out of the wagering program at the terminal170, the terminal170may disconnect the link180. Any active vouchers may be designated as unlocked at the transaction database116such that they may be accessed at a later time.

In another implementation, the link160between the client device150and the terminal170may be initiated by a bar code displayed on the display176of the terminal170. In this way, the display176may display a machine-readable code, such as a linear or two-dimensional bar code. In one example, the displayed bar code may represent a TID. In another example, the bar code may identify the particular terminal170. The imaging device158of the client device150may scan the bar code and may query the application server130regarding the TID as well as the UID associated with the client device150. The application server130may then query the server110regarding the TID and the UID. The server110may query the transaction database116regarding the TID and the UID. The server110may then communicate active voucher, active ticket information, and any other information to the terminal170. The terminal170may then display such information by the wagering program GUI via display176.

FIG. 4illustrates a client device170displaying a voucher400according to one aspect of the disclosure. The voucher400may be displayed on the display of a client device170. As described above, the voucher400may include a value402and a TID404, which may be displayed as part of the voucher400. As shown inFIG. 4, the TID may be represented either as a set of characters, such as the alphanumeric characters shown, or as a bar code, such as the 2D Aztec-style bar code shown. The voucher400may be a virtual, digital, or electronic voucher, and may be displayed at the client device150. The voucher400may include additional information, such as time of issue, place of issue, any brand names or logos associated with the issuing entity, advertisements, or any other type of information. The wagering application may also display application navigation buttons, such as a logout button, directional arrows, menu options, or the like.

FIG. 5is a flow chart illustrating a method500of placing a wager according to one aspect of the disclosure. While the description below refers to a number of blocks of the method500in a particular order, it should be understood that the order in which the blocks are performed may be modified, and blocks may be added or omitted.

At block502, a user may initiate the wagering application at a client device150, as described above.

At block504, a user may select an active voucher. A user may navigate the wagering application GUI displayed on the client device170. For example, a user may navigate the GUI to display any active vouchers. In some instances, a user may have more than one active voucher. In this example, a user may navigate to determine which voucher to display. Such navigation may be done by swiping a touchscreen, or any other input, such as by keyboard, keypad, arrow buttons, or user voice.

If a user does not have an active voucher, or has an active voucher with a zero balance, the method300of issuing a voucher, as described above, may be used to obtain a voucher at the client device150.

At block506, a link between the client device and the terminal may be initiated, according to any of the methods described above. For example, the imaging device178of the terminal170may scan a TID associated with an active voucher that is displayed on the client device150.

At block508, the terminal170may query the server110regarding a balance associated with the UID or TID provided by the client device170. As described above, the server110may query the transaction database116to determine a balance associated with the UID, as well as any active vouchers or wagers. The server110may communicate an updated balance, as well as any active voucher or wager information, to the terminal170. The terminal may receive the information from the server110and may display the information at a GUI on the display176of the terminal170.

According to one implementation, the method300of issuing a voucher may be conducted, and a user may wish to place a wager once an active voucher is displayed on the client device150. In this regard, a voucher may be displayed at block312, and the user may proceed to block510, as described below, without having to duplicate blocks502-508.

At block510, a user may navigate the wagering program GUI at the terminal170and place a wager. For example, the user may provide an input to the terminal170, such as by touchscreen, keyboard, etc. The user may select a wagering event. The GUI may display the participants of the wagering event, possible outcomes, and potential wagers to make regarding the wagering event. For example, the wagering event may be a horse race, with the participants being particular horses with unique names. A wager may be placed on a particular horse to win the race. Any other type of wager may be made including, but not limited to, all wagers listed in the ARCI model rules for racing. The price of the wager may be any value, such as a predetermined value, or a value that changes as additional wagers are made.

At block512, the terminal170may communicate wager information to the server110. Such information may include the wagering event and the particular outcome wagered on, as described above. Such information may also include the terminal location at which the wager was placed, the time of the wager, and any additional information associated with the transaction.

The server110may store the wager information at the transaction database116and update the transaction database116based on the wager information. The terminal170may reduce a balance associated with a particular UID based on the price of the wager.

At block514, the server110may generate a ticket and may generate a new voucher based on the updated balance associated with the UID. The ticket may include a TID that may uniquely identify the ticket. The ticket may also include a price, wagering event information, a wagered outcome, and a potential value if the wagered outcome occurs.

At block516, the server110may communicate ticket information and the updated voucher to the application server130, where the application server130may update an application database136, and the ticket and voucher may be communicated to and displayed at the client device150at block518.

At block520, the server110may communicate updated balance information to the terminal170, where it may be displayed on the terminal170at block522.

FIG. 6illustrates a client device150displaying a ticket600according to one aspect of the disclosure. The ticket600may include wager602, a unique TID604, and a price606paid for the ticket600. The TID may be represented as a machine-readable code, such as a bar code, and/or as a set of characters, such as alphanumeric characters. The ticket600may also include additional information, such as wagering venue, wagering event, wagering time, etc.

FIG. 7is a flow chart illustrating a method700of redeeming a wager according to one aspect of the disclosure.

At block702, the conclusion of a wagering event may occur. For example, this may be the conclusion of a race, sporting event, or any other type of wagering event. The conclusion of the wagering event may result in an outcome. The outcome of the wagering event may be a particular placement order of participants in the wagering event. For example, a wagering event may be a horse race. At the conclusion of the race, a particular horse may finish in first. The remainder of the participating horses may finish in other places.

At block704, the outcome of a wagering event may be ascertained by the server110. For example, the outcome may be communicated to the server110and/or application server130in an automated fashion. Alternatively, the outcome may be communicated to the server110by a wagering administrator. In this way, a wagering administrator may enter details about the outcome of a wagering event by inputting the details into the server110, either by an input of the server110, or by another computing device capable of communication with the server110. The server110may update the transaction database116to update the value of each active ticket for the wagering event.

At block706, a user may initiate the wagering application, as described above.

At block708, a user may select an active ticket. This may be done in the same way as described above in the context of selecting an active voucher.

At block710, a link between the client device and the terminal may be initiated, according to any of the methods described above. For example, the terminal may scan a TID associated with an active ticket that is displayed on the client device.

At block712, the terminal may query the server110regarding a value of the ticket based on the outcome of the wagering event. The server110may retrieve the stored ticket value from the transaction database116and communicate the value to the terminal170. For example, each participant of the wagering event may have a predetermined probability of achieving a particular outcome, e.g., odds. For example, a certain horse may have 7-1 odds of finishing first. If a $1.00 wager is made that the horse will win, that ticket would be worth $8.00.

At block714, the server110may generate a voucher based on the previous value of any vouchers as well as any winning ticket values.

At block716, the server110may transmit the updated voucher information to the application server130, where it may be stored at the application database136and transmitted to the client device150. The client device may then display the updated voucher at block718. The user may then place a wager against the voucher value according to the method500describe above, or may redeem the voucher for the cash equivalent at the terminal170or at a teller window.

At block720, the server110may transmit the updated balance information to the terminal170, where it may be displayed at the terminal170at block722. As described above, the user may bet against the balance or may redeem the cash value of the balance at the terminal170or some other location, such as a teller window.

According to another implementation, the server110may ascertain the value of all active tickets associated with the wagering event at the conclusion of the wagering event. In this way, the server110may communicate the values of the active tickets and may issue updated vouchers to the application server130, where the application server130may update the transaction database136and provide the ticket values and updated vouchers to the client devices150associated with the UID for each ticket. In this example, a client device150need not initiate the link with the terminal170in order to ascertain the value of the ticket and obtain an updated voucher. In this way, a user may initiate a wagering application at the client device150. The wagering application may communicate with the application server130and receive the updated ticket value and updated voucher. When a user displays a ticket associated with a completed wagering event, the ticket may display the value on the face of the ticket, such as shown inFIGS. 8A and 8B.

In one example, a client device may share the ticket and the associated value with others. For example, a user may initiate the client device150to take a screenshot of the displayed ticket and/or ticket value, thereby generating an image of the ticket that may be stored on the client device. The image of the ticket may be uploaded to the internet, such as an image hosting website or a social media website, and the image may be displayed according to a user's security preferences. For example, an image hosting website may display the image publicly, while a social media website may only display the image to friends or connections of the user. In another example, a user may share the image by email, text message, Bluetooth, or any file sharing method typically accessible by a client device, e.g., a mobile device.

FIGS. 8A and 8Billustrate a client device150displaying tickets800with the corresponding value according to one aspect of the disclosure. The tickets800may include a wager802, a TID804, and a price806as described above. Additionally, the value808of the tickets may be displayed on the ticket, and may be overlaid atop other portions of the ticket. For example, the value808may overlay portions of the ticket800, but may not overlay a machine-readable portion of the TID804. In the example ofFIG. 8A, the wagering outcome did not occur, and therefore the value808of the ticket800is designated as “Lost,” since it has no value. In the example ofFIG. 8B, the wagered outcome did occur, and the value808of the ticket is displayed as “Win $50.”

While the wagering system100described above includes vouchers and tickets that may be displayed on a client device170, the wagering system100is compatible with a paper-based wagering system as well. For example, the terminal170may include a printing mechanism for printing a physical voucher or ticket and dispensing the voucher or ticket to a user. A player may scan the voucher or ticket at the terminal to either place wagers or to receive an additional voucher for redemption at a teller.

According to another aspect of the disclosure, the UID of the device may be associated with an account stored in the transaction database of the server110. In this example, a user may opt to store identifying information at the server110, such as name, address, bank account information, credit card number, player rewards account information, as well as any other demographic information. In this regard, a wagering system may include a server, an application server, and a client device. The function of the terminal may be performed at the client device, for example, by an application stored on the client device. The client device may communicate transaction information directly with the server.