Source: https://patents.google.com/patent/US8845422B2/en
Timestamp: 2019-06-19 11:33:10
Document Index: 610216556

Matched Legal Cases: ['art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 500', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 700', 'art 700', 'art 700', 'art 700', 'art 700']

US8845422B2 - Remote login for a wagering game machine - Google Patents
Remote login for a wagering game machine Download PDF
US8845422B2
US8845422B2 US13/606,872 US201213606872A US8845422B2 US 8845422 B2 US8845422 B2 US 8845422B2 US 201213606872 A US201213606872 A US 201213606872A US 8845422 B2 US8845422 B2 US 8845422B2
US13/606,872
US20130244772A1 (en
Justin C. Weber
2011-09-09 Priority to US201161532899P priority Critical
2012-09-07 Application filed by WMS Gaming Inc filed Critical WMS Gaming Inc
2012-09-07 Priority to US13/606,872 priority patent/US8845422B2/en
2012-10-01 Assigned to WMS GAMING, INC. reassignment WMS GAMING, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: WEBER, JUSTIN C.
2013-09-19 Publication of US20130244772A1 publication Critical patent/US20130244772A1/en
2014-09-30 Publication of US8845422B2 publication Critical patent/US8845422B2/en
A method includes receiving a login request to an account at a wagering game machine. In response to the login request, the method includes displaying a security token on a display of the wagering game machine. Also in response to the login request, the method includes transmitting the security token to a server, wherein the server is communicatively coupled to the wagering game machine and a mobile device. Also in response to the login request, the method includes receiving, back from the server and at the wagering game machine, authorization for login to the account at the wagering machine, wherein the authorization is based on an earlier login to the account from the mobile device using the login credentials. After receiving the authorization, the method includes logging into the account at the wagering game machine, wherein the logging occurs without inputting of the login credentials at the wagering game machine.
This application claims the priority benefit of U.S. Provisional Application Ser. No. 61/532,899 filed Sep. 9, 2011.
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. Copyright 2012, WMS Gaming, Inc.
Embodiments of the inventive subject matter relate generally to wagering game systems, and more particularly to wagering game systems including remote login for a wagering game machine.
FIG. 1 depicts a system for performing remote login at the wagering game machine, according to some example embodiments.
FIG. 2 depicts a Graphical User Interface (GUI) being displayed on a display of a wagering game machine for providing the option for performing remote login at the wagering game machine, according to some example embodiments.
FIG. 3 depicts a block diagram illustrating a mobile device architecture, according to some example embodiments.
FIG. 4 depicts a Graphical User Interface (GUI) on a display of a mobile device for inputting a security token for remote login at a wagering game machine, according to some example embodiments.
FIG. 5 depicts a flowchart for operations performed at a wagering game machine for performing remote login at the wagering game machine, according to some example embodiments.
FIG. 6 depicts a flowchart for operations performed at a wagering game server for performing remote login at the wagering game machine, according to some example embodiments.
FIG. 7 depicts a flowchart for operations performed at a device for performing remote login at the wagering game machine, according to some example embodiments.
FIG. 8 depicts a block diagram illustrating a wagering game machine architecture, according to some example embodiments.
FIG. 9 depicts a block diagram illustrating a wagering game network, according to some example embodiments.
FIG. 10 depicts a perspective view of a wagering game machine, according to some example embodiments.
This description of the embodiments is divided into seven sections. The first section provides an introduction to some example embodiments, while the second section provides a system environment. The third section describes an example mobile device. The fourth section describes example operations performed by some example embodiments. The fifth section describes an example wagering game machine architecture and network environment. The sixth section describes an example wagering game machine and the seventh section presents some general comments.
This section provides an introduction to some example embodiments. Some example embodiments provide protection for wagering game players having their login credentials (e.g., username and password) being stolen during login to their account at wagering game machines at wagering game establishments. In particular, some example embodiments provide protection from persons shoulder surfing of wagering game players who are logging to their player accounts at wagering game machines. Some example embodiments enable a wagering game player to provide their login credentials using a mobile device instead of inputting these credentials at the wagering game machine.
In some example embodiments, in response to a wagering game player requesting to perform a remote login to one or more of their player accounts at a wagering game machine, a security token is displayed to the wagering game player on a display of the wagering game machine. For example, the security token can be displayed in response to the wagering game player selecting a login button. The security token can be any alphanumeric value that uniquely identifies the wagering game machine. In some example embodiments, the security token uniquely identifies the wagering game machine for a defined time period (e.g., 10 minutes, 30 minutes, etc.). This security token can be generated locally or remotely at a wagering game server that is communicatively coupled to the wagering game machine. If generated locally at the wagering game machine, the security token is transmitted to the wagering game server.
The wagering game player can then input their login credentials along with the security token (displayed on a display of the wagering game machine) using a device that is separate from the wagering game machine. Using a separate device can be less susceptible to shoulder surfing and other techniques for stealing login credentials. Examples of this separate device can be a mobile device associated with the wagering game player (e.g., smartphone, Personal Digital Assistant (PDA), etc.), a kiosk at the wagering game establishment, etc. Embodiments herein are described with reference to a mobile device associated with the wagering game player. However, some example embodiments are applicable to any device that is separate from the wagering game machine. If the wagering game player is already logged into their player account on their mobile device, the wagering game player can then input the security token on their mobile device. The mobile device then uploads the login credentials and the security token provided by the wagering game player back to the wagering game server.
In response, the wagering game server can authenticate the login credentials for the player account. If authentic, the wagering game server can associate the security token with the player account. Also, the wagering game server can then provide authentication to the wagering game machine to enable account access by the wagering game player at the wagering game machine. Alternatively or in addition, the wagering game server can download a player profile associated with the player account to the wagering game machine. Accordingly, the wagering game player can access their player profile and account at the wagering game machine without requiring the wagering game player to provide their login credentials at the wagering game machine. Therefore, some example embodiments provide protection for wagering game players having their login credentials being stolen during login.
This section describes example system environments and presents structural aspects of some example embodiments. This section includes an example system and GUI displayed on a wagering game machine for performing remote login at the wagering game machine from a separate device (e.g., a mobile device of the wagering game player) using a security token. This section will discuss FIGS. 1-2. The discussion of FIG. 1 will describe a system that provides remote login at the wagering game machine from a separate device. The discussion of FIG. 2 will describe a GUI displayed on a display of a wagering game machine for performing remote login at the wagering game machine. While FIGS. 1-2 are illustrated using a mobile device for remote login at a wagering game machine, some example embodiments can incorporate any device separate from the wagering game machine for remote login at the wagering game machine.
FIG. 1 depicts a system for performing remote login at the wagering game machine, according to some example embodiments. In particular, FIG. 1 depicts a system 100 that includes a wagering game machine 102, a mobile device 104, and a wagering game server 106. The wagering game machine 102, the mobile device 104, and the wagering game server 106 are communicatively coupled together. A wagering game player 114 is in front of the wagering game machine 102. In this example, the mobile device 104 is associated with the wagering game player 114. In some example embodiments, any device separate from the wagering game machine 102 and that has network connectivity can be used to communicate with the wagering game server 106 (e.g., a different person's mobile device, a kiosk in the wagering game establishment, etc.).
The wagering game machine 102 includes a display 116 having a GUI that includes a login button 120 and a display box for displaying a security token 118. A more detailed description of an example GUI for logging into a player account at a wagering game machine is set forth below and described in reference to FIG. 2, which is described in more detail below. A more detailed description of an example of the mobile device 104 is set forth below and described in reference to FIGS. 3-4, which is described in more detail below. Examples of the mobile device 104 can include a smartphone, Personal Digital Assistant (PDA), etc.
The wagering game server 106 includes a server credential module 108 and a nonvolatile machine-readable media 110 that are communicatively coupled together through a communication bus 112. The server credential module 108 can be software, firmware, hardware or a combination thereof. For example, the server credential module 108 can be software executing on a processor (not shown).
The remote login as described herein can be for one or more of a number of player accounts that are accessible at the wagering game machine. The player account can be an account that is specific to the vendor of the wagering game machine. Such an account enables the accrual of achievements, points, awards, etc. based on wagering game play across multiple wagering game sessions. A wagering game player can have an incentive to login to this player account because accrual of achievements, points, awards, etc. unlocks content, advances levels as part of the wagering game play. Such an account can be accessible external to the wagering game machines but is associated with wagering game play of such machines. For example, the account can be accessible through a web-based interface that can be accessible through a mobile-based application. The wagering game player can play nonwagering game activity through this web-based interface to the account that provides for accrual of achievements, points, awards, etc. that can affect wagering game play at the wagering game machines. In some example embodiments, the player account can also be an account that is specific to the wagering game establishment. Such an account can enable the player to perform account-based wagering based on game credits that are associated with the player account. In some example embodiments, this remote login can enable access to all or a multiple of the player accounts.
FIG. 1 illustrates different communications among the different components in the system 100 to provide for remote login at the wagering game machine 102. There are four different communications—a communication 130, a communication 132, a communication 134, a communication 136, and a communication 138. In this example, the wagering game player selects an option to login from their mobile device. As an example, instead of inputting their login credentials at the wagering game machine 102, the wagering game player 114 can select a button at the wagering game machine 102 to perform a login from a separate device. The wagering game player 114 can select the login button 120.
In response to receiving the request from the wagering game player 114 to perform a remote login, the wagering game machine 102 transmits the communication 130 to the wagering game server 106 (shown as reference point A). The communication 130 can include an indicator that a remote login request is being made and the value of the security token 118.
Also, after the communication 130 is transmitted to the wagering game server 106, the wagering game machine 102 can begin polling the wagering game server 106 to determine whether a remote login request from a separate device has been authenticated (the communication 132 shown as reference point B).
Also, after the security token 118 is displayed on the display 116 of the wagering game machine 102, the wagering game player 114 inputs the value of the security token 118 into the mobile device 104. In some example embodiments, the wagering game player 114 is already logged in or logins to their player account at the mobile device 104 using their login credentials (e.g., username and password). Once logged into their player account, the wagering game player 114 can input the security token 118 at the mobile device 104. For example, the wagering game player 114 can go to an option in their player account to perform a remote login. An example of such a GUI on the mobile device 104 for remote login is illustrated in FIG. 4, which is described in more detail below.
In response to inputting the value the security token 118 into the mobile device 104, the mobile device 104 transmits the communication 134 to the wagering game server 106 (shown as reference point C). The communication 134 can include the login credentials associated with the player account and the value of the security token 118.
In response to receipt of the communication 130 and the communication 134, the server credential module 108 can validate the login credentials for the wagering game player 114 if the wagering game player 114 is not yet logged in. Also, the server credential module 108 can match the value of the security token 118 received from the wagering game machine 102 with the value of the security token 118 received from the mobile device 104. Once these values are matched, the server credential module 108 can associate the value of the security token 118 with the player account for the wagering game player 114. The server credential module 108 can store this association between the value of the security token 118 and the player account in the nonvolatile machine-readable media 110.
After validation, the server credential module 108 in the wagering game server 106 can transmit the communication 136 (shown as reference point D) back to the mobile device 104 that indicates that the remote login is validated for the wagering game machine 102 using the mobile device 104. Also after validation, the server credential server 108 can transmit the communication 138 (shown as reference point E) back to the wagering game machine 102 that provides validation of login of the player account for the wagering game player 114. Alternatively or in addition, the communication 136 can include a player profile for the wagering game player 114 that is associated with their player account that is stored in the nonvolatile machine-readable media 110. The player profile can include the different achievements, points, awards, current level available for the wagering game player for this wagering game machine, current unlocked content available for the wagering game player for this wagering game machine, etc.
Upon receipt of the communication 136, the wagering game player 114 is logged into their player account at the wagering game machine 102 through a remote login. Accordingly, some example embodiments enable a wagering game player to provide their login credentials using a mobile device instead of inputting these credentials at the wagering game machine. Therefore, some example embodiments provide protection for wagering game players having their login credentials (e.g., username and password) being stolen during login into their account at wagering game machines at wagering game establishments.
Accordingly as described, in some example embodiments, a wagering game player can provide the security token through any device that has network access. In some example embodiments, a wagering game player can dictate which device is to be used. In particular, as part of selecting the remote login, the wagering game player 114 can be given the option to provide an identification of the device where the remote login must occur. For example, the wagering game player 114 can indicate that a mobile device is to be used and the telephone number of the mobile device. In another example, the wagering game player 114 can indicate that a kiosk at the wagering game establishment where wagering game machine 102 is located is to be used. Such embodiments provide further security by enabling the wagering game player 114 to specify the separate device to be used for the remote login. In such embodiments, the communication 130 can include the identification of the device to be used for the remote login. The server credential module 108 at the wagering game server 106 can verify that this device is being used for the remote login.
FIG. 2 depicts a Graphical User Interface (GUI) being displayed on a display of a wagering game machine for providing the option for performing remote login at the wagering game machine, according to some example embodiments. In particular, FIG. 2 depicts a GUI being displayed on a display 200. The GUI includes an interface to allow the wagering game player to login using remote login (as described herein) or a standard login (where the wagering game player inputs their login credentials at the wagering game machine). A section 202 provides for the remote login, and a section 204 provides for the standard login. The section 202 includes a login button 208 and a display box for presenting the security token 206. Accordingly, upon selection of the login button 208 by the wagering game player, a value of the security token 206 is presented in the display box.
Alternatively, the wagering game player can perform a standard login using the inputs in section 204. The section 204 includes a create button 210 that enables the wagering game player to create a player account. In response to selection of the create button 210, a different screen (not shown) can be displayed to enable the wagering game player to create their player account. The section 204 also includes an input box 212 for inputting a username and an input box 214 for inputting a password for an existing player account for the wagering game player. The section 204 also includes a login button 216. Accordingly, the wagering game player can perform a standard login by inputting their username into the input box 212 and their password into the input box 214. The wagering game player can then select the login button 214 to provide their username and password for authentication.
This section describes an example mobile device and presents structural aspects of some embodiments. This section will discuss FIGS. 3-4. The discussion of FIG. 3 will describe a block diagram of relevant parts of a mobile device architecture. The discussion of FIG. 4 will describe a Graphical User Interface (GUI) for inputting a security token and that is presented on a display of a mobile device. While FIGS. 3-4 illustrate a mobile device for inputting a security token for remote login at a wagering game machine, some example embodiments can incorporate any device separate from the wagering game machine for inputting of the security token.
FIG. 3 depicts a block diagram illustrating a mobile device architecture, according to some example embodiments. FIG. 3 depicts a mobile device 300 that can be representative of the mobile device 104 of FIG. 1. The mobile device 300 includes a mobile credential module 302, an Input/Output (I/O) module 304, a nonvolatile machine-readable media 306, and an antenna 308 that are communicatively coupled together through a communication bus 310.
The mobile credential module 302 and the I/O module 304 can be software, firmware, hardware or a combination thereof. For example, the mobile credential module 302 and the I/O module 304 can be software executing on a processor or other type of hardware (not shown). The mobile credential module 302 can perform the operations for providing remote login at a wagering game machine at the mobile device 300 (as described herein). The I/O module 304 can receive and transmit data communications for remote login (as described herein). For example, the I/O module 304 can use the antenna 308 to receive and transmit communications from and to the wagering game server. The nonvolatile-machine-readable media 306 can store data that identifies the mobile device (e.g., the associated telephone number). In some example embodiments, this identification can be provided to the wagering game server as part of the authentication for the remote login.
FIG. 4 depicts a Graphical User Interface (GUI) on a display of a mobile device for inputting a security token for remote login at a wagering game machine, according to some example embodiments. In particular, FIG. 4 illustrates a mobile device 400 that includes a display 402 having a GUI for remote login to a wagering game machine. The mobile device 400 can be representative of the mobile device 104 of FIG. 1. The mobile device 400 includes a speaker 414 and a microphone 412. The GUI shown in FIG. 4 can be displayed after the wagering game player has logged into their player account through their mobile device 400.
The GUI includes an input box 404 to input the security token that was displayed on the display of the wagering game machine. The GUI also includes an information point 410 that instructs the wagering game player to enter the security token in the input box 404. The GUI includes an OK button 406 and a cancel button 408. After inputting the security token into the input box 404, the wagering game player can select the OK button 406 to transmit the security token along with the login credentials for the wagering game player back to the wagering game server (as described above).
This section describes operations associated with some example embodiments. In the discussion below, the flow charts will be described with reference to the block diagrams presented above. However, in some example embodiments, the operations can be performed by logic not described in the block diagrams.
The section will discuss FIGS. 5-7. The discussion of FIGS. 5-7 will describe operations for performing remote login at a wagering game machine using a security token. The three different flowcharts in FIGS. 5-7 are from three different perspectives (a wagering game machine, a wagering game server, and a mobile device). In particular, the discussion of FIG. 5 will describe operations performed at a wagering game machine for performing remote login at the wagering game machine using a security token. The discussion of FIG. 6 will describe operations performed at a wagering game server for performing remote login at the wagering game machine using a security token. The discussion of FIG. 7 will describe operations performed at a mobile device for performing remote login at the wagering game machine using a security token.
FIG. 5 depicts a flowchart for operations performed at a wagering game machine for performing remote login at the wagering game machine, according to some example embodiments. The operations of a flowchart 500 are described in reference to FIG. 1. In some example embodiments, the operations are performed by a wagering game module (not shown) within the wagering game machine 102 of FIG. 1. An example of the wagering game module in a wagering game machine is illustrated in FIG. 8, which is described in more detail below. The operations of the flowchart 500 begin at block 502.
At block 502, the wagering game module in the wagering game machine 102 receives a remote login request to an account at the wagering game machine 102. With reference to FIG. 1, the wagering game module in the wagering game machine 102 receives the remote login request for the player account for the wagering game player 114 based on input from the wagering game player. With reference to FIG. 2, the wagering game player 114 can select the login button 208 for login into their account from their mobile device. Operations of the flowchart 500 continue at block 504.
At block 504, the wagering game module displays a security token on a display of the wagering game machine. With reference to FIG. 1, the wagering game module can generate the security token locally at the wagering game machine 102 or request and receive the security token from the wagering game server 106. The wagering game module can then display the security token 118 on the display 116 of the wagering game machine 102. Operations of the flowchart 500 continue at block 506.
At block 506, the wagering game module transmits the security token to a wagering game server communicatively coupled to the wagering game machine and communicatively coupled to a mobile device of a wagering game player attempting to login to the account based on the login request at the wagering game machine. With reference to FIG. 1, the wagering game module in the wagering game machine 102 transmits the value of the security token 118 to the wagering game server 106. Operations of the flowchart 500 continue at block 508.
At block 508, the wagering game module receives, back from the wagering game server, authorization for login to the account at the wagering machine based on login using the login credentials provided at the mobile device back to the wagering game server. With reference to FIG. 1, the wagering game module in the wagering game machine 102 receives, back from the wagering game server 106 authorization for login to the account for the wagering game player 114 (shown as the communication 138). The wagering game module can receive this authorization in response to polling of the wagering game server 106 (shown as the communication 132). Operations of the flowchart 500 continue at block 510.
At block 510, the wagering game module logs into the account at the wagering game machine, in response to receiving the authorization from the wagering game server based on the login using the login credentials provided at the mobile device back to the wagering game server, without inputting of the login credentials at the wagering game machine. With reference to FIG. 1 after receiving the authorization, the wagering game module enables the wagering game player 114 to access their player account at the wagering game machine 102 without requiring the wagering game player 114 to login to their player account at the wagering game machine 102. Operations of the flowchart 500 continue at block 510.
At block 512, the wagering game module receives, from the wagering game server and at the wagering game machine, player account data for the account. With reference to FIG. 1, the wagering game module in the wagering game machine 102 receives player account data from the wagering game server 106. The player account data can include a player profile for the wagering game player 114 (that can include the different achievements, points, awards, current level available for the wagering game player for this wagering game machine, current unlocked content available for the wagering game player for this wagering game machine, etc.). Operations of the flowchart 500 are complete.
FIG. 6 depicts a flowchart for operations performed at a wagering game server for performing remote login at the wagering game machine, according to some example embodiments. The operations of a flowchart 600 are described in reference to FIG. 1. In some example embodiments, the operations are performed by the server credential module 108 within the wagering game server 106 of FIG. 1. The operations of the flowchart 600 begin at block 602.
At block 602, the server credential module 108 receives from a wagering game machine, a security token associated with a login request to an account at the wagering game machine that was displayed on a display at the wagering game machine in response to an attempt to login to the account at the wagering game machine. With reference to FIG. 1, the server credential module 108 in the wagering game server 106 receives from the wagering game machine the security token 118 (shown as the communication 130). Operations of the flowchart 600 continue at block 604.
At block 604, the server credential module 108 receives, from a device that is separate from the wagering game machine, login credentials for logging into the account and the security token. With reference to FIG. 1, the server credential module 108 receives, from the mobile device 104, login credentials for logging into the player account for the wagering game player 114 along with the value of the security token 118 (that was input to the mobile device 104 by the wagering game player 114) (shown as the communication 134). Operations of the flowchart 600 continue at block 606.
At block 606, the server credential module 108 authenticates the login credentials for the account. With reference to FIG. 1, the server credential module 108 authenticates the login credentials for the player account. For example, the server credential module 108 verifies that the username and password are correct. Operations of the flowchart 600 continue at block 608.
At block 608, the server credential module 108 determines whether the login credentials are authentic. If the login credentials are not authentic, operations of the flowchart 600 continue at block 610. Otherwise, operations of the flowchart 600 continue at block 612.
At block 610, the server credential module 108 requests, from the device from the wagering game player, the login credentials again. With reference to FIG. 1, the server credential module 108 requests the login credentials from the wagering game player 114 again (based on a communication transmitted back to the mobile device 104). The mobile device 104 can display an indication that the login was incorrect and a request to reentry the login credentials for their player account. This request to reenter the login credentials can continue for a defined number of times until the wagering game player 114 is locked out of their account (thereby requiring the wagering game player 114 to take steps to unlock their account). Operations of the flowchart 600 continue at block 612.
At block 612, the server credential module 108 transmits, to the wagering game machine, authorization for login to the account at the wagering game machine, without inputting of the login credentials at the wagering game machine. With reference to FIG. 1, the server credential module 108 transmits authorization to the wagering game machine 102 for login to the player account for the wagering game player 114 (shown as the communication 138). Operations of the flowchart 600 continue at block 614.
At block 614, the server credential module 108 transmits, to the wagering game machine, player account data for the account. With reference to FIG. 1, the server credential module 108 transmits the player account data for the player account for the wagering game player 114. Operations of the flowchart 600 are complete.
FIG. 7 depicts a flowchart for operations performed at a device for performing remote login at the wagering game machine, according to some example embodiments. The operations of a flowchart 700 are described in reference to FIGS. 1 and 3. In some example embodiments, the operations are performed by the mobile credential module 302 in the mobile device 300 of FIG. 3. The operations of the flowchart 700 begin at block 702.
At block 702, the mobile credential module 302 receives, as input at the mobile device, login credentials for an account for logging in at a wagering game machine. With reference to FIGS. 1 and 3, the mobile credential module 302 receives, as input at the mobile device 104, login credentials for the player account for the wagering game player 114 (based on input from the wagering game player 114). In some example embodiments, the wagering game player 114 may already been logged into their player account at the mobile device 104. In such embodiments, this operation is not required at this point. Operations of the flowchart 700 continue at block 704.
At block 704, the mobile credential module 302 receives, as input at the mobile device, a security token displayed on a display of the wagering game machine in response to a remote login request to the account at the wagering game machine. With reference to FIGS. 1 and 3, the mobile credential module 302 receives, as input at the mobile device 104 by the wagering game player 114, the value of the security token 118 displayed at the wagering game machine 102. Operations of the flowchart 700 continue at block 706.
At block 706, the mobile credential module 302 transmits, from the mobile device to a server communicatively coupled the mobile device and the wagering game machine, the login credentials for the account and the security token for authentication of the account at the wagering game server without inputting of the login credentials at the wagering game machine. With reference to FIGS. 1 and 3, the mobile credential module 302 transmits the login credentials and the value of the security token 118 to the wagering game server 106 for authentication (shown as the communication 134). Operations of the flowchart 700 are complete.
Wagering Game Machine Architecture and Network Environment
This section describes an example wagering game architecture and network environment of some example embodiments.
FIG. 8 depicts a block diagram illustrating a wagering game machine architecture, according to some example embodiments. As shown in FIG. 8, the wagering game machine architecture 800 includes a wagering game machine 806, which includes a central processing unit (CPU) 826 connected to main memory 828. The CPU 826 can include any suitable processor, such as an Intel® Pentium processor, Intel® Core 2 Duo processor, AMD Opteron™ processor, or UltraSPARC processor. The main memory 828 includes a wagering game module 832. In one embodiment, the wagering game module 832 can present wagering games, such as video poker, video black jack, video slots, video lottery, etc., in whole or part. The wagering game module 832 can also perform operations for performing the remote login request to a player account at the wagering game machine 806 (as described above).
The CPU 826 is also connected to an input/output (I/O) bus 822, which can include any suitable bus technologies, such as an AGTL+frontside bus and a PCI backside bus. The I/O bus 822 is connected to a payout mechanism 808, primary display 810, secondary display 812, value input device 814, player input device 816, information reader 818, and storage unit 830. The player input device 816 can include the value input device 814 to the extent the player input device 816 is used to place wagers. The I/O bus 822 is also connected to an external system interface 824, which is connected to external systems 804 (e.g., wagering game networks).
In one embodiment, the wagering game machine 806 can include additional peripheral devices and/or more than one of each component shown in FIG. 8. For example, in one embodiment, the wagering game machine 806 can include multiple external system interfaces 824 and/or multiple CPUs 826. In one embodiment, any of the components can be integrated or subdivided.
Any component of the architecture 800 can include hardware, firmware, and/or machine-readable media including instructions for performing the operations described herein. Machine-readable media includes any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine (e.g., a wagering game machine, computer, etc.). For example, tangible machine-readable media includes read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory machines, etc. Machine-readable media also includes any media suitable for transmitting software over a network.
While FIG. 8 describes an example wagering game machine architecture, this section continues with a discussion of wagering game networks.
FIG. 9 depicts a block diagram illustrating a wagering game network, according to some example embodiments. As shown in FIG. 8, the wagering game network 900 includes a plurality of casinos 912 connected to a communications network 914. In some example embodiments, operations for the remote login for a wagering game machine (as described herein) can be performed in the wagering game network 900.
Each casino 912 includes a local area network 916, which includes an access point 904, a wagering game server 906, and wagering game machines 902. The access point 9304 provides wireless communication links 910 and wired communication links 908. The wired and wireless communication links can employ any suitable connection technology, such as Bluetooth, 802.11, Ethernet, public switched telephone networks, SONET, etc. In some embodiments, the wagering game server 906 can serve wagering games and distribute content to devices located in other casinos 912 or at other locations on the communications network 914.
The wagering game machines 902 described herein can take any suitable form, such as floor standing models, handheld mobile units, bartop models, workstation-type console models, etc. Further, the wagering game machines 902 can be primarily dedicated for use in conducting wagering games, or can include non-dedicated devices, such as mobile phones, personal digital assistants, personal computers, etc. In one embodiment, the wagering game network 900 can include other network devices, such as accounting servers, wide area progressive servers, player tracking servers, and/or other devices suitable for use in connection with embodiments of the invention.
In some embodiments, wagering game machines 902 and wagering game servers 906 work together such that a wagering game machine 902 can be operated as a thin, thick, or intermediate client. For example, one or more elements of game play may be controlled by the wagering game machine 902 (client) or the wagering game server 906 (server). Game play elements can include executable game code, lookup tables, configuration files, game outcome, audio or visual representations of the game, game assets or the like. In a thin-client example, the wagering game server 906 can perform functions such as determining game outcome or managing assets, while the wagering game machine 902 can present a graphical representation of such outcome or asset modification to the user (e.g., player). In a thick-client example, the wagering game machines 902 can determine game outcomes and communicate the outcomes to the wagering game server 906 for recording or managing a player's account.
In some embodiments, either the wagering game machines 902 (client) or the wagering game server 906 can provide functionality that is not directly related to game play. For example, account transactions and account rules may be managed centrally (e.g., by the wagering game server 906) or locally (e.g., by the wagering game machine 902). Other functionality not directly related to game play may include power management, presentation of advertising, software or firmware updates, system quality or security checks, etc.
Any of the wagering game network components (e.g., the wagering game machines 902) can include hardware and machine-readable media including instructions for performing the operations described herein.
FIG. 10 depicts a perspective view of a wagering game machine, according to some example embodiments. Referring to FIG. 9, a wagering game machine 1000 is used in gaming establishments, such as casinos. According to embodiments, the wagering game machine 1000 can be any type of wagering game machine and can have varying structures and methods of operation. For example, the wagering game machine 1000 can be an electromechanical wagering game machine configured to play mechanical slots, or it can be an electronic wagering game machine configured to play video casino games, such as blackjack, slots, keno, poker, blackjack, roulette, etc.
The value input devices 1018 can take any suitable form and can be located on the front of the housing 1012. The value input devices 1018 can receive currency and/or credits inserted by a player. The value input devices 1018 can include coin acceptors for receiving coin currency and bill acceptors for receiving paper currency. Furthermore, the value input devices 1018 can include ticket readers or barcode scanners for reading information stored on vouchers, cards, or other tangible portable storage devices. The vouchers or cards can authorize access to central accounts, which can transfer money to the wagering game machine 1000.
The operation of the basic wagering game can be displayed to the player on the primary display 1014. The primary display 1014 can also display a bonus game associated with the basic wagering game. The primary display 1014 can include a cathode ray tube (CRT), a high resolution liquid crystal display (LCD), a plasma display, light emitting diodes (LEDs), or any other type of display suitable for use in the wagering game machine 1000. Alternatively, the primary display 1014 can include a number of mechanical reels to display the outcome. In FIG. 10, the wagering game machine 1000 is an “upright” version in which the primary display 1014 is oriented vertically relative to the player. Alternatively, the wagering game machine can be a “slant-top” version in which the primary display 1014 is slanted at about a thirty-degree angle toward the player of the wagering game machine 1000. In yet another embodiment, the wagering game machine 1000 can exhibit any suitable form factor, such as a free standing model, bartop model, mobile handheld model, or workstation console mode
In some embodiments, the wagering game machine 1000 can also include an information reader 1052, which can include a card reader, ticket reader, bar code scanner, RFID transceiver, or computer readable storage medium interface. In some embodiments, the information reader 1052 can be used to award complimentary services, restore game assets, track player habits, etc.
receiving a login request to an account at a wagering game machine; and
in response to the login request,
displaying a security token on a display of the wagering game machine;
transmitting the security token to a server, wherein the server is communicatively coupled to the wagering game machine and a mobile device;
receiving, back from the server and at the wagering game machine, authorization for login to the account at the wagering machine, wherein the authorization is based on an earlier login to the account from the mobile device using the login credentials; and
after receiving the authorization, logging into the account at the wagering game machine, wherein the logging occurs without inputting of the login credentials at the wagering game machine.
2. The method of claim 1, wherein the security token comprises a unique identifier for the wagering game machine for a defined time period.
3. The method of claim 1, further comprising generating the security token by a module within the wagering game machine.
4. The method of claim 1, wherein the mobile device is associated with a wagering game player attempting to login to the account based on the login request at the wagering game machine.
5. The method of claim 1, further comprising receiving, from the server and at the wagering game machine, player account data for the account.
6. The method of claim 1, further comprising receiving the security token from the wagering game server in response to the login request.
receiving, at a server and from a wagering game machine, an indication of a login request to an account at the wagering game machine, wherein a security token was displayed on a display at the wagering game machine in response to an attempt to login to the account at the wagering game machine;
receiving, at the server and from a device that is separate from the wagering game machine, the security token and login credentials for logging into the account;
authenticating, at the server, the login credentials for the account; and
responsive to the login credentials being authentic for the account, transmitting, from the server to the wagering game machine, authorization for login to the account at the wagering game machine, without receipt of the login credentials at the wagering game machine.
responsive to the login credentials being authentic for the account, transmitting, from the server to the wagering game machine, player account data for the account.
9. The method of claim 7, wherein the device that is separate from the wagering game machine comprises a mobile device.
10. The method of claim 7, wherein the security token comprises a unique identifier for the wagering game machine for a defined time period.
generating, at the server, the security token; and
transmitting, from the server and to the wagering game machine, the security token.
12. One or more machine-readable storage media including instructions which, when executed by one or more processors, cause the one or more processors to perform operations comprising:
receiving, as input at a mobile device, login credentials for an account for logging in at a wagering game machine;
receiving, as input at the mobile device, a security token displayed on a display of the wagering game machine in response to an attempt to perform a remote login to the account at the wagering game machine; and
transmitting, from the mobile device to a server communicatively coupled the mobile device and the wagering game machine, the login credentials for the account and the security token for authentication of the account at the server without inputting of the login credentials at the wagering game machine.
13. The one or more machine-readable storage media of claim 12, wherein the security token comprises a unique identifier for the wagering game machine for a defined time period.
14. The one or more machine-readable storage media of claim 12, wherein the mobile device is associated with a wagering game player attempting to login to the account based on the login request at the wagering game machine.
15. The one or more machine-readable storage media of claim 12, wherein the operations are configured to transmit, from the mobile device to the server, an identification of the mobile device, wherein the server is configured to use the identification of the mobile device as part of the authentication of the account.
16. A wagering game machine comprising:
a wagering game module operable on the processor, the wagering game module configured to:
present a wagering game on which monetary value can be wagered;
receive a login request to an account at the wagering game machine; and
display a security token on a display of the wagering game machine;
transmit the security token to a server, wherein the server is communicatively coupled to the wagering game machine and a mobile device;
receive, back from the server, authorization for login to the account at the wagering machine, wherein the authorization is based on an earlier login to the account from the mobile device using the login credentials; and
after receipt of the authorization, log into the account at the wagering game machine, wherein the logging occurs without inputting of the login credentials at the wagering game machine.
17. The wagering game machine of claim 16, wherein the security token comprises a unique identifier for the wagering game machine for a defined time period.
18. The wagering game machine of claim 16, further comprising generating the security token by a module within the wagering game machine.
19. The wagering game machine of claim 16, wherein the mobile device is associated with a wagering game player attempting to login to the account based on the login request at the wagering game machine.
20. The wagering game machine of claim 16, further comprising receiving, from the server, player account data for the account.
means for receiving, at a server and from a wagering game machine, an indication of a login request to an account at the wagering game machine, wherein a security token was displayed on a display at the wagering game machine in response to an attempt to login to the account at the wagering game machine;
means for receiving, at the server and from a device that is separate from the wagering game machine, the security token and login credentials for logging into the account;
means for authenticating, at the server, the login credentials for the account; and
responsive to the login credentials being authentic for the account, means for transmitting, from the server to the wagering game machine, authorization for login to the account at the wagering game machine, without receipt of the login credentials at the wagering game machine.
responsive to the login credentials being authentic for the account, means for transmitting, from the server to the wagering game machine, player account data for the account.
23. The apparatus of claim 21, wherein the device that is separate from the wagering game machine comprises a mobile device.
24. The apparatus of claim 21, wherein the security token comprises a unique identifier for the wagering game machine for a defined time period.
means for generating, at the server, the security token; and
means for transmitting, from the server and to the wagering game machine, the security token.
US13/606,872 2011-09-09 2012-09-07 Remote login for a wagering game machine Active 2033-01-11 US8845422B2 (en)
US201161532899P true 2011-09-09 2011-09-09
US13/606,872 US8845422B2 (en) 2011-09-09 2012-09-07 Remote login for a wagering game machine
US20130244772A1 US20130244772A1 (en) 2013-09-19
US8845422B2 true US8845422B2 (en) 2014-09-30
ID=49158132
US13/606,872 Active 2033-01-11 US8845422B2 (en) 2011-09-09 2012-09-07 Remote login for a wagering game machine
US (1) US8845422B2 (en)
US20160225226A1 (en) * 2010-09-30 2016-08-04 Jesus Pereo-OcHoa Method and System of Playing Game through Communication Tool
US10057245B2 (en) * 2015-07-15 2018-08-21 Google Llc Using temporary credentials in guest mode
US7285046B2 (en) * 2004-04-13 2007-10-23 Zolotoy Arbuz Mobile gaming system
US20090328182A1 (en) 2008-04-17 2009-12-31 Meher Malakapalli Enabling two-factor authentication for terminal services
US20110212772A1 (en) 2006-11-15 2011-09-01 Alderucci Dean P Accessing information associated with a mobile gaming device to verify the mobile gaming device is in communications with an intended server
US20110269436A1 (en) 2008-10-21 2011-11-03 Mobilotto Systems, Inc. Method and system for enabling gaming via a mobile device
2012-09-07 US US13/606,872 patent/US8845422B2/en active Active
US20130244772A1 (en) 2013-09-19
RU2321067C9 (en) 2008-06-20 Device, system and method for conducting a game using wireless communications
AU2009267176B2 (en) 2012-07-19 Wagering game with shared outcome providing individual awards to players
AU2004232158A1 (en) 2004-11-04 Method and apparatus for limiting access to games using biometric data
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WEBER, JUSTIN C.;REEL/FRAME:029055/0120