Smart cards and communication networks for betting or gaming systems

Abstract

A betting or gaming system is disclosed that includes a token having a portal identification and an account identification stored thereon, and a user device configured to retrieve the portal identification from the token, access the portal, retrieve the account identification from the token, log on to the account using the identification, and present the account on a display for use along with a value associated with the account, thereby enabling a user of the user device to engage in betting or gaming activity using the portal.

Description

[Technical Field]

[0001] The present invention relates to betting or gaming systems, and in particular to the integration of tokens such as smart cards in betting or gaming systems. [Background technology]

[0002] Betting or gaming systems are known that are offered in betting shops or casinos, online or via call centers.

[0003] Within a betting shop or casino, a betting or gaming system may include betting or gaming terminals into which users may make payments (cash or debit / credit card) to place bets or wagers, or users may make payments by cash or debit / credit card to a betting shop or casino employee and place bets or wagers at the counter.

[0004] In an online betting or gaming system, a user may log on to a website and place bets or wagers using payments via credit / debit cards.

[0005] Typically within a betting or gaming system, the provider provides separate systems for the betting shop environment or casino and for the online environment. Summary of the Invention [Problem to be solved by the invention]

[0006] It is an object of the present invention to provide an improved betting or gaming system. [Means for solving the problem]

[0007] The invention will now be described with reference to the following drawings. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 illustrates an exemplary betting system architecture. [Figure 2] FIG. 1 illustrates an exemplary smart card. [Figure 3A] This diagram shows the message flow in the example. [Figure 3B] This diagram shows the message flow in the example. [Figure 3C] This diagram shows the message flow in the example. [Figure 3D] This diagram shows the message flow in the example. [Figure 4] FIG. 1 illustrates an exemplary portal. DETAILED DESCRIPTION OF THE INVENTION

[0009] A betting or gaming system is provided that includes a token having a unique identification of an account stored thereon, and a betting or gaming terminal configured to read the token to retrieve account information, access the account information to retrieve a value associated with the account, and authorize betting or gaming activity at the betting or gaming terminal depending on the value of the account.

[0010] The betting or gaming system further comprises a local server connected to the betting or gaming terminal, the local server communicating with the central server to retrieve values.

[0011] A betting or gaming system is provided that includes a token having a portal identification and an account identification stored thereon, and a user device configured to retrieve the portal identification from the token, access the portal, retrieve the account identification from the token, log on to the account using the identification, and present the account on a display for use along with a value associated with the account, thereby enabling a user of the user device to engage in betting or gaming activity using the portal. The presented account may be a logged-on account or simply an account facilitating betting or gaming activity.

[0012] A betting or gaming system may have a local network and a central network, and a user device connects to the betting or gaming system through the local network. A betting or gaming system may have a local network and a central network, and a user device connects to the betting or gaming system through the central network. A user device may connect to the local network if it is in close proximity to the local network.

[0013] The account identifier retrieved from the token can be provided as an input to an alias table in the central server and can be mapped to an account associated with a value used for betting or gaming operations. Thus, the central network can store an alias table that maps unique addresses / account identifiers stored on the token to unique account identifiers associated with betting or gaming values. The unique account identifier associated with the betting or gaming value may identify an account associated with a user. The unique account identifier associated with the betting or gaming value may identify an account that is anonymous.

[0014] The betting or gaming system may further comprise a point of sale terminal configured to retrieve account identification information from the token and access the identified account.

[0015] The point of sale terminal may be configured to increase or decrease the value associated with the account in response to a discrete value transaction at the point of sale terminal. The discrete value transaction may be a cash or card purchase, in which case the account value is increased. The discrete value transaction may be a payment of the account value to a user, in which case the account value is decreased.

[0016] A method of operating a betting or gaming system is provided, comprising the steps of storing identifying information for an account on a token, reading the token at a betting or gaming terminal, retrieving the account information, accessing the account information to retrieve a value associated with the account, and authorizing betting activity at the betting or gaming terminal depending on the value of the account.

[0017] The betting or gaming server can communicate with the local server to look up values.

[0018] A method of operating a betting or gaming system is provided that includes the steps of storing a portal identification and an account identification on a token, retrieving the portal identification from the token at a user device, accessing the portal, retrieving the account identification from the token, logging on to the account using the account identification, and presenting the account on a display for use with a value associated with the account, thereby enabling a user of the user device to engage in betting or gaming activity using the portal. The presented account may be a logged-on account or simply an account facilitating betting or gaming activity.

[0019] A User Device may connect to a betting or gaming system through a local network. A User Device may connect to a betting or gaming system through a central network. A User Device may connect to a local network if it is in close proximity to the local network.

[0020] The method further includes retrieving account identification information from the token and accessing the identified account at a point of sale terminal.

[0021] The method further includes increasing or decreasing a value associated with the account in response to a distinct value transaction at the point of sale terminal. The distinct value transaction can be a cash or card purchase, where the account value is increased. The distinct value transaction can be a payment of the account value to the user by cash or card, where the account value is decreased.

[0022] A token is provided for use with a betting or gaming account, the token storing an identifier that identifies the betting or gaming account and configured to be read by a point of sale terminal associated with a betting or gaming system, the point of sale system adding value to the betting or gaming account dependent on financial transactions at the point of sale, the token being used for betting or gaming transactions dependent on the value associated with the account whereby the account value is decreased according to bet value or gaming and increased according to winning bet value or gaming value, and the point of sale terminal removing value from the betting or gaming account and removing value from the card dependent on the value associated with the account dependent on financial transactions at the point of sale.

[0023] The gaming value may be a wager.

[0024] The token may be for use with a betting or gaming terminal and may be configured to communicate with a betting or gaming terminal.

[0025] The token may be for use with a user device, the user device being configured to access a betting or gaming system portal.

[0026] A token can be a physical token or a virtual token. A physical token can be a smart card or any other physical element capable of storing information electronically and that is electronically readable and adjustable. A virtual token can be a virtual token stored on a physical device such as a mobile phone.

[0027] Description of the Preferred Embodiment The present invention is described below with reference to examples and embodiments in a betting system environment. The present invention is not limited to a betting system environment and may be implemented in a gaming system environment, such as a casino system environment. The following description and drawings are merely illustrative. The scope of protection is defined by the appended claims.

[0028] 1, there is shown an example architecture 100 of an example betting system comprising a local network 102 and a central network 104. The local network 102 and the central network 104 are connected via a switching network 106, such as a private or public network, such as the Internet.

[0029] In practice, multiple local networks in communication with the central network 104 may be provided.

[0030] The central network 104 comprises a central controller 136 and one or more central servers 134 connected to the central controller 136. The central network 104 is connected to the switching network 106 via lines 146. The central network 104 may facilitate online operation of the betting system.

[0031] A local network 102 may be provided within a betting shop of a betting system. The local network includes a computer system 125 having a controller 126, one or more local servers 122 connected to the controller on line 142, a location module 128 connected to the controller on line 141, and a wireless interface 130 connected to the controller on line 140. The controller is connected to a switching network 106 on line 144. The local network further includes a point of sale terminal 124 connected to the controller 126 on line 138 and a betting terminal 118 connected to the controller 126 on line 120.

[0032] A betting system is associated with multiple users, and in the example of Figure 1, each user is associated with a user device, such as a mobile phone. Two user devices are shown in Figure 1: device 108a and device 108b. Device 108a is located within the betting shop and is connected to local network 102. User device 108b is located outside the betting shop and is connected to central network 104.

[0033] Users of the betting system are associated with smart cards. In the example of Figure 1, users of user devices 108a and 108b are each associated with a respective smart card 110a and 110b. Each smart card is provided to facilitate use by the user of the betting system.

[0034] Referring to Figure 2, an exemplary smart card 110 is shown. Each smart card has a unique account identifier encoded therein. The smart card additionally preferably stores the IP address of a portal associated with the betting system, such as the URL of the betting system's website. Thus, as shown in Figure 2, the smart card is configured to store a unique account identifier 202 and a betting system portal address 206.

[0035] The smart card 110a is preferably brought within range of a smart card reader 127 provided on the point of sale terminal 124 in order for the point of sale terminal 124 to read the information stored on the smart card 110a during a purchase operation. The smart card may be connected within wireless range of the point of sale terminal 124 by touching it to the point of sale terminal 124, by fitting it into a slot in the point of sale terminal 124, or by connecting it to a peripheral device.

[0036] A user may purchase a smart card within a betting shop. The smart card may be purchased with a value that is fully allocated to the betting account associated with the smart card. Alternatively, the smart card may be purchased with a value that includes the cost of purchasing the smart card plus the amount allocated to the account. Additionally, the smart card may be associated with additional value provided for use with the smart card that is not linked to the purchase value of the smart card, such as a free bet.

[0037] 3A, an exemplary message flow associated with the purchase of a smart card is shown, including smart card 110a or 110b, point-of-sale terminal 124, computer system 125, and central network 104. A user presents smart card 110a, 110b to a point-of-sale terminal, as indicated by dashed arrow 300, and payment (cash or credit / debit card) for the purchase of the smart card, as indicated by dashed arrow 302. The point-of-sale terminal sends an activation message to computer system 125 identifying the account identifier retrieved from the smart card and the value to be credited to the account, as indicated by message 304, which then sends an activation message to central network 104 identifying the account identifier and the value to be credited to the account, as indicated by message 306.

[0038] The central network preferably stores an alias table, for example in the central server 134. The alias table can map account identifiers provided on the smart card to user accounts. For security purposes, user account details are not stored on the smart card itself. The unique identifier on the smart card can also be mapped to an anonymous account, and any value added to the smart card purchase need not be associated with an identifiable user account. The smart card and use of the smart card can be anonymous.

[0039] The central network assigns the listed value associated with the smart card from the alias table to the identified account, stores it, and returns an authorization message 308 to the computer system 125, which then sends an authorization message 310 to the point of sale terminal 124. Optionally, the value may be returned with the authorization message for storage within the local server 122 of the computer system 125. A local alias table may be provided within the local computer 25, or the local computer may temporarily store the account value associated with the account identifier on the smart card when the smart card is used.

[0040] Additional value for allocation to a betting account associated with a smart card can be purchased at the point of sale following a process similar to Figure 3A. The unique identifier retrieved from the smart card is sent to a central server along with the value of any purchased credits, which then allocates this credit to the account using an alias table.

[0041] The purchase of smart cards and the application of additional value to smart cards need not be limited to betting shop point-of-sale terminals: this functionality may be provided within other retail establishments that have the appropriate communications configuration with the betting system in place.

[0042] A first example of smart card use will be described with reference to smart card 110a. Referring to Figure 3B, an exemplary message flow associated with the first example is shown.

[0043] According to a first example, a user uses a betting terminal 118 in a betting shop. The user brings a smart card 110a within proximity of a smart card reader 119 provided on the betting terminal 118, thereby enabling the betting terminal 118 to read the smart card 110a. Communication is established as shown by line 314. The betting terminal 118 is configured to retrieve a unique account identifier and access the account associated with the identifier over a local network.

[0044] The smart card can be connected to the betting terminal via near field communication, via contact with a pad on the betting terminal, via insertion into a slot on the betting terminal, or via a peripheral device. The requirement is that communication be established, which can be by various means.

[0045] Referring to FIG. 3B, message 312 represents the provision of information from smart card 110a to betting terminal 118, and message 314 represents the provision of a request from the betting terminal for information from smart card 110a.

[0046] The betting terminal 118 sends message 316 to the controller 126 to retrieve the value associated with the account, including the account identifier. The controller forwards this information to the central network 104 with a request message 318. The central network accesses the account value through use of an alias table and returns it to the local server 122 in message 320. The local server 122 provides this value to the controller 126 of the computer system 125 in message 322, which then provides the value to the betting terminal in message 324.

[0047] The betting terminal then operates to facilitate the user placing bets depending on the value associated with the account as indicated by step 301. The monetary value of the account is then made available to the user for use on the betting terminal and to place bets.

[0048] Use of the smart card is terminated when the communication link on line 114 is broken, i.e., when smart card 110a is removed from betting terminal 118. In configurations, the betting terminal may present an option on the user interface for the user to terminate a session with the smart card, and the connection on line 314 need not be maintained during operation. The session may time out after a sustained period of inactivity.

[0049] Upon completion of the session, the betting terminal 118 forwards a message 326 identifying the remaining account balance to the local server 122 of the computer system 125, which then forwards this message 328 to the central network 104. The central network uses the identifier in the message to access an alias table and update the account value associated with the account.

[0050] A second example of smart card use will now be described with reference to user device 108a and smart card 110a located within a betting shop. Referring to Figure 3C, an exemplary message flow associated with the second example is shown.

[0051] According to a second example, a user uses their user device 108a in a betting shop. The user brings a smart card 110a within proximity of the user device 108a, allowing a near-field reader 149a provided in the user device 108a to read the smart card 110a. Communication is established as indicated by dashed line 112a. The user device 108a is configured to retrieve a URL (or more generally, an IP address) stored on the smart card 110a and access a portal page, such as a web page, associated with the URL over a local network. The user device also retrieves a unique account identifier and uses password credentials also retrieved from the smart card to access the account associated with the identifier over the local network. The portal for the betting system is then displayed on the display 148a of the user device 108a. The monetary value of the account is then made available to the user for use on the betting system portal and for placing bets.

[0052] The smart card 110a can connect to the user device 108a via near field communication, via contact with a pad on the user device, via insertion into a slot on the user device, or via a peripheral device. The requirement is that communication be established, which can be by various means.

[0053] Referring to Figure 4, an example of a portal 402 is shown. Reference numeral 404 indicates the URL of the portal. Reference numeral 406 indicates an account identifier that may be displayed, and reference numeral 408 indicates an account value that is preferably displayed. Reference numeral 410 indicates a general window in which betting options are offered.

[0054] The user device 108 a establishes a wireless connection with the local network, as indicated by connection 150 a to the wireless interface 130 of the computer system 125 .

[0055] Referring to FIG. 3C, message 330 represents a provision of information from smart card 110a to user device 108a, and message 332 represents a provision of a request from smart card 110a for information from user device 108a.

[0056] The user device 108a sends message 334 to the wireless interface 130, which then sends message 336 to the controller 126 requesting a value associated with the account, including the account identifier. The controller 126 forwards this information to the central network 104 in a request message 338. The central network 104 uses the account identifier and alias table to access the account value and returns it to the local server 122 in message 340. The local server 122 provides this value to the controller 126 in message 342, which then provides the value to the wireless interface 130 in message 344, which then provides the value to the user device 108a in message 348.

[0057] The user device 108 a then accesses the portal (or web address) associated with the information retrieved from the smart card as shown in message 350 .

[0058] The user device 108a then operates to facilitate the user placing a bet based on the value associated with the account. The monetary value of the account is then made available to the user for use on the betting terminal and for placing a bet. This is indicated by operation step 303.

[0059] Use of the smart card is terminated when the communication link on line 112a is broken, i.e., when the smart card 110a is moved away from the user device 108a. In configurations, the user device 108a can present an option on the display 148a for the user to terminate a session with the smart card, and the link on line 112 need not be maintained during use. The session can be timed out after inactivity.

[0060] Upon completion of the session, the user device 108a forwards a message 352 to the wireless interface 130, which then forwards a message 354 to the local server 122, which then forwards the message to the central server 354. The remaining account balance is then stored by the central server.

[0061] A third example will be described with reference to a user device 108b and smart card 110b located outside a betting shop.

[0062] According to a third example, a user uses their user device 108b. The user brings a smart card 110b within proximity of the user device 108b, allowing a near-field reader 149b provided within the user device 108b to read the smart card 110b. Communication is established as indicated by dashed line 112b. The user device 108b is configured to retrieve the URL stored on the smart card and access a portal page, such as a web page, associated with the URL via a centralized network. The user device 108b also retrieves the unique account identifier and accesses the account associated with the identifier via an alias table in the central network. The portal for the betting system is then displayed on the display 148b of the user device 108b. The monetary value of the account is then made available to the user for use on the betting system portal and for placing bets.

[0063] The smart card 110b can connect to the user device 108b via near field communication, via contact with a pad on the user device, via insertion into a slot on the user device, or via a peripheral device. The requirement is that communication be established, which can be by various means.

[0064] User device 108b establishes a wireless connection with the central network as indicated by connection 150b.

[0065] Referring to FIG. 3D, message 356 represents a provision of information from smart card 110b to user device 108b, and message 358 represents a provision of a request for information from user device 108b from smart card 110b.

[0066] The user device 108b sends message 360 ​​to the central server 134 to retrieve the value associated with the account, including the account identifier. The central server 134 uses an alias table to access the account value and returns it to the user device 108b in message 362.

[0067] The user device 108b then accesses the portal (or web address) associated with the information retrieved from the smart card as shown in message 364.

[0068] The user device 108b then operates to facilitate the user placing a bet based on the value associated with the account. The monetary value of the account is then made available to the user to use on the user device 108b to place a bet. This is indicated by operation 305.

[0069] Use of the smart card is terminated when the communication link on dashed line 112b is broken, i.e., when the smart card 110b is moved away from the user device 108b. In configurations, the user device 108b can display an option on the display 148b for the user to terminate a session with the smart card; the link on dashed line 112 need not be maintained during use. A session may time out due to inactivity.

[0070] Upon completion of the session, the user device 108b forwards a message 366 to the central server 134. The remaining account balance is then stored by the central server, again through the use of an alias table.

[0071] Any stored data may be encrypted. Data stored on smart cards, such as unique address identifiers or IP addresses, may be encrypted. Data stored anywhere in the betting system, such as within a local network or on a central network, may be encrypted.

[0072] If the user device 108a or 108b is located within a betting shop and can therefore connect wirelessly to a local network, this is preferable to connecting the device to a central network. The location module 128 is configured to determine the location of the user device to force connection via the local network, if connectable to the local network. A geofence 132 may be provided to assist in this operation.

[0073] In the above example, smart cards 110a, 110b are physical smart cards and may be any physical token. Alternatively, a virtual smart card may be provided in the wallet of the user device, which may be considered a virtual token. The above-described process may operate identically for a virtual smart card or token as for a physical smart card or token, and may be generally defined as operating with a token.

[0074] In the first example described above with reference to FIG. 3A, no user device is required and the example provides for operation with a physical smart card.

[0075] In the second example mentioned above, the user device is connected in a local network and communicates with a smart card. The smart card can be a physical or virtual smart card. The local network communicates with a central network. The local network and the central network are the same betting system network, which is a private network of the betting system that connects to a public mobile network or other public connector network. The local network is provided within the betting shop.

[0076] In the third example described above, the user device is connected within a central network and communicates with a smart card. The smart card can be a physical or virtual smart card. The user device can be located anywhere that allows connection to the betting track or the central network of user devices. The central network is a private network of the betting system.

[0077] Any monetary value associated with placing a bet is automatically deducted from the account associated with the unique account identifier on the smart card.

[0078] Any monetary value associated with winning a bet is automatically credited to the account associated with the unique account identifier on the smart card.

[0079] The smart card can be presented at a point of sale terminal 124 so that the user can redeem the value associated with the account to which the smart card is linked for an appropriate payment, for example, either a payment to the user's bank card or a cash payment.

[0080] Although preferred embodiments of the present invention have been described above with reference to a betting system environment, as noted above the present invention may be applied within a gaming system environment such as a casino.

[0081] The betting system environment and gaming system environment may be considered synonymous; bets are placed within the betting system environment, wagers are placed (or made) within the casino system environment, and both bets and wagers have assigned values.

[0082] Any of the processes described herein may be implemented as computer software on a computer system that includes the transmitted message. A computer program product may be provided with the computer software that, when executed by a computer, may perform any of the processes described.

[0083] The present invention has been described by way of examples and embodiments. The present invention is not limited to the details of any of the example embodiments given.

Claims

1. a token having a unique identifier for the account stored thereon; a betting or gaming terminal configured to read the token to retrieve the account information, access the account information to retrieve a value associated with the account, and authorize betting activity at the betting or gaming terminal dependent on the value of the account; 1. A betting or gaming system comprising:

2. 2. A betting or gaming system as claimed in claim 1, further comprising a local server connected to said betting or gaming terminal, said local server communicating with a central server to retrieve said values.

3. a token having stored thereon an identification of the portal and an identification of the account; a user device configured to retrieve the identification information of the portal from the token, access the portal, retrieve the identification information of the account from the token, log on to the account using the identification information, and present the account on a display for use with a value associated with the account, thereby enabling a user of the user device to engage in betting or gaming activities using the portal; 1. A betting or gaming system comprising:

4. 4. A betting or gaming system as described in claim 3, comprising a local network and a central network, wherein the user device connects to the betting or gaming system via one of the local network and the central network, and wherein the user device connects to the local network when in proximity to the local network.

5. 5. A betting or gaming system according to claim 3 or 4, further comprising a point of sale terminal configured to retrieve the account identification information from the token and access the identified account.

6. 6. A betting or gaming system according to claim 5, wherein the point of sale terminal is configured to increase or decrease value associated with the account in response to a transaction of discrete value at the point of sale terminal.

7. 7. A betting or gaming system as claimed in claim 6, wherein said separate value transactions are cash or card purchases and said account value is increased.

8. 8. A betting or gaming system according to claim 6 or 7, wherein the separate value transaction is a payment of the account value to a user by cash or card, and the account value is reduced.

9. On the token, storing an identification of the account; At a betting or gaming terminal: reading the token; retrieving the account information; accessing the account information to retrieve a value associated with the account; authorizing betting activity at the betting or gaming terminal depending on the value of the account; 1. A method of operating a betting or gaming system, comprising:

10. 10. A method of operating a betting system as claimed in claim 9, wherein the betting or gaming server communicates with a local server to retrieve the value.

11. On the token, storing a portal identification and an account identification; At the user device, retrieving the identification information of the portal from the token; accessing the portal; retrieving the identification information of the account from the token; logging on to the account using the account identification information; presenting the account on a display for use along with a value associated with the account, thereby enabling a user of the user device to engage in betting or gaming activities using the portal; 1. A method of operating a betting or gaming system, comprising:

12. 12. A method of operating a betting or gaming system according to claim 11, wherein the user devices connect to the betting or gaming system via a local network or a central network.

13. 13. A method of operating a betting or gaming system as claimed in claim 12, wherein said user device connects to said local network when in proximity to said local network.

14. 14. A method of operating a betting or gaming system as claimed in any one of claims 9 to 13, further comprising the steps of retrieving the account identification information from the token and accessing the identified account at a point of sale terminal.

15. 15. A method of operating a betting or gaming system as claimed in claim 14, further comprising the step of increasing or decreasing a value associated with said account in response to a transaction of discrete value at said point of sale terminal.

16. 16. A method of operating a betting or gaming system as claimed in claim 15, wherein the separate value transaction is a cash or card purchase and the account value is increased.

17. 17. A method of operating a betting or gaming system as claimed in claim 15 or 16, wherein the separate value transaction is a payment of the account value to a user by cash or card, and the account value is reduced.

18. 1. A token for use with a betting or gaming account, the token storing an identifier that identifies the betting or gaming account and configured to be read by a point of sale terminal associated with a betting or gaming system, the point of sale system adding value to the betting or gaming account dependent on financial transactions at the point of sale, the token being used for betting or gaming transactions dependent on the value associated with the account, whereby the account value is decreased according to bet value or gaming value and increased according to winning bet value or gaming value, and the point of sale terminal removing value from the betting or gaming account and removing value from the card dependent on the value associated with the account dependent on financial transactions at the point of sale.

19. 20. The token of claim 18, for use with a betting or gaming terminal, the token configured for communication with the betting or gaming terminal.

20. 20. The token of claim 18 or 19, for use with a user device, the user device configured for accessing a betting or gaming system portal.

Images