Gaming establishments continually try new methods to keep patrons in its establishment in order to increase profits. With more and more patrons using PEDs, mobile gaming is one way to increase profits. However, games of chance may not be played on unknown and untrusted PEDs.
A network-based gaming system may support interaction between intermediary gaming trusted devices and PEDs and/or gaming machines so that games of chance are able to be securely presented to the user(s). The intermediary gaming trusted device is able to support a secure and controlled interaction between a gaming apparatus and an associated unknown, untrusted PED so that the associated untrusted PED, when coupled to the intermediary gaming trusted device, becomes a trusted PED and can execute gaming software.
In one embodiment, an intermediary gaming trusted electronic device for use with an associated untrusted PED may include a position sensor configured to acquire position information of the untrusted PED, a memory configured to store at least game session data, a wireless transceiver, and a processor configured to at least: (i) securely communicate with a gaming apparatus via the wireless transceiver; (ii) securely communicate with the associated untrusted PED; (iii) determine whether a gaming session is permitted based on the position information; (iv) receive gaming data from the gaming apparatus if it is determined that the gaming session is permitted; and (v) transmit presentation data to the associated untrusted PED for presentation on a display of the associated PED, the presentation data associated with the received gaming data, wherein the intermediary gaming trusted device is able to support interaction between the gaming apparatus and the associated untrusted PED so that the associated untrusted PED, when coupled to the intermediary gaming trusted device, can execute a gaming software.
In another embodiment, an intermediary gaming trusted device for use with an associated untrusted portable electronic device (PED), the device including a position sensor configured to acquire position information of the PED, a memory configured to store at least game session data, a wireless transceiver, and a processor configured to at least: (i) securely communicate with the gaming apparatus via the wireless transceiver; (ii) securely communicate with the associated untrusted PED; (iii) determine whether a gaming session is permitted based on the position information; (iv) receive gaming data from the gaming apparatus if it is determined that the gaming session is permitted; and (v) transmit presentation data to the associated untrusted PED for presentation on a display of the associated PED, the presentation data being associated with the received gaming data, wherein the associated untrusted PED can be trusted to display presentation data so long as the intermediary gaming trusted device is coupled thereto.
In one embodiment, a system for playing a wagering game includes a portable electronic device (PED) having a display to display presentation data associated with gaming data, an intermediary gaming trusted device configured to securely communicate with the PED via a physical or wireless means, and a gaming apparatus configured to securely communicate with the intermediary gaming trusted device to transmit the gaming data to the intermediary gaming trusted device, wherein the intermediary gaming trusted device is configured to transmit the presentation data to the PED to allow a user of the PED to execute gaming software.
The present invention provides other hardware configured to perform the methods of the invention, as well as software stored in a machine-readable medium (e.g., a tangible storage medium) to control devices to perform these methods. These and other features will be presented in more detail in the following detailed description of the invention and the associated figures.
The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more example embodiments and, together with the description of example embodiments, serve to explain the principles and implementations.
In the drawings:
The present disclosure relates generally to gaming systems. More particularly, the present disclosure relates to use of a portable electronic device (PED) in a gaming system and even more particularly use of a PED in a gaming system with an intermediary trusted device.
Embodiments are described herein in the context of a portable intermediary trusted device. The following detailed description is illustrative only and is not intended to be in any way limiting. Other embodiments will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts.
In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application- and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.
In accordance with the present invention, the components, process steps, and/or data structures may be implemented using various types of operating systems, computing platforms, computer programs, and/or general purpose machines. In addition, those of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein.
The network-based gaming system 100 may include at least one intermediary gaming trusted device 114a-n (where n is an integer). The intermediary gaming trusted device 114a-n may be associated with a PED 112a-n via a physical or wireless connection. Although each intermediary gaming trusted device is illustrated as connecting to one PED, the intermediary gaming trusted device may connect to more than one PED and thus acts as a trusted connection hub for multiple PED's. The PED 112a-n may be any portable device having a display such as, for example, portable telephones, laptops, computers, notebooks, tablets, media players, and the like. Wireless connections may be any known wireless methods such as a 3G wireless technology, 4G wireless technology, Bluetooth, wireless universal serial bus, near-field magnetic or communication sensor, Fire Wire, WiMax, IEEE 802.11x technology, radio frequency, narrow-beam infrared (IR) sensor, RFID tag, WiFi, vibration sensor or any other known wireless methods. Wired connections may be any known connection using a wire. The connection between the intermediary gaming trusted device and PED creates a secured pairing environment. Once paired, either a short-range (e.g. Bluetooth) or a long-range (e.g. WiFi) wireless communication tether (e.g. wireless leash) may be established and maintained during the wireless communication session.
The intermediary gaming trusted device 114a-n may be configured to communicate with a gaming server 102 via a network 106 through a wired or wireless connection. In the same or another embodiment, the intermediary gaming trusted device 118 associated with the PED 120 may also be configured to communicate with a gaming machine 104 through a wired or wireless connection. The gaming machine 104 may then connect to the gaming server 102 via network 106 also through a wired or wireless connection. Wireless connections may be any known wireless methods such as a 3G wireless technology, 4G wireless technology, Bluetooth, wireless universal serial bus, near-field magnetic, Fire Wire, WiMax, IEEE 802.11 technology, radio frequency, or any other known wireless methods. Wired connections may be any known connection using a wire.
The gaming server 102 may be configured to communicate with a player tracking server 108, location server 120, and an authentication server 116. The player tracking server 108 may communicate with a player tracking database 110 to obtain tracked player information such as player preferences, games of chance the player likes to play, entertainment the player enjoys, accumulated and used points, number of wins and losses, and any other similar player information.
The authentication sever 116 may be used to authenticate and/or verify the player, the intermediary gaming trusted device 114a-n, 118, the PED 112a-n, 120, the gaming machine 104, or perform any other authentication or verification functions. Any known authentication method may be used, such as public-private key authentication algorithms, random number generators, authentication keys, location authentication, and the like.
Each intermediary gaming trusted device 114a-n, 120 may be assigned to at least one PED 112a-n, 118. Although each intermediary gaming trusted device 114a-n, 118 is illustrated as being associated with one PED 112a-n, 120, this is not meant to be limiting as the intermediary gaming trusted device 114a-n, 118 may be assigned to more than one PED 112a-n, 120 and acts as a trusted gaming hub. Initially, PEDs are unknown and untrusted devices not capable of playing games of chance. However, once connected to an intermediary gaming trusted device, the PED becomes or is otherwise transformed into a trusted PED and is able to be used to play games of chance. Each intermediary gaming trusted device 114a-n, 118 may have a connector to connect to the PED 112a-n, 120. The connector is further illustrated and described in detail with reference to
The intermediary gaming trusted device 114a-n, 118 may be configured to communicate with the authentication server 116. The intermediary gaming trusted device 114a-n, 118 may then, in turn, authenticate or verify the user of PED 112a-n, 120. The user of the PED 112a-n, 120 may be authenticated and/or verified though any known authentication and verification methods such as, for example, biometric verification (i.e. voice recognition, retinal scan, fingerprint verification, and the like), username, password, account number, and the like. Authentication of the user may also include authentication via a web-application associated with the gaming establishment and/or uploading authentication software from the intermediary gaming trusted device 114a-n, 118 to the PED 112a-n, 120. In another embodiment, the user of the PED 112a-n, 120 may also obtain the intermediary gaming trusted device 114a-n, 118 from a gaming establishment personnel. The gaming establishment personnel may then authenticate and/or verify the user as well as associate the intermediary gaming trusted device 114a-n, 118 to the PED 112a-n, 120.
Once authenticated, the intermediary gaming trusted device 114a-n, 118 may receive gaming data from the gaming server 102. The gaming data may include gaming information or gaming establishment information. Gaming information may include, for example, player tracking information, gaming options, data to play a game of chance, funding information or options in order to play the games of chance, pay tables, and the like. The gaming establishment information may include, for example, advertisements (e.g. buffet coupons, movie trailers, and the like), tournament information, room booking information, entertainment information, and the like.
The intermediary gaming trusted device 114a-n, 118 may control and review the communication between the PED and the gaming server 102. The intermediary gaming trusted device 114a-n, 118 may be configured to determine if the communication meets any desired rules or regulations. For example, if the user selects a “Cash Out” option on the PED 112a-n, 120 for $100,000.00, but the maximum amount to be cashed out is $2,000, the intermediary gaming trusted device 114a-n, 118 may prevent the user from cashing out.
The intermediary gaming trusted device 114a-n, 118 may transmit the gaming data to the PED 114a-n, 120 or to the gaming machine 104. The intermediary gaming trusted device 114a-n, 118 may enable the PED 112a-n, 120 or the gaming machine 104 to display the gaming data. For example, if the gaming data is to play a game of chance, the game of chance may be displayed on a display of the PED 112a-n, 120 or the gaming machine 104. The game of chance may be, for example, poker, black jack, roulette, bingo, keno, video slot machine games, or any other game of chance. The intermediary gaming trusted device 114a-n, 118 may be configured to receive data from the PED 114a-n, 120 or the gaming machine 104 that is inputted by the user. The received data may then be transmitted from the intermediary gaming trusted device 114a-n, 118 to the gaming server 102 via the network 106 for processing. The received data may be transmitted to the gaming server 102 dynamically or periodically. In other words, the received data may be transmitted to the gaming server 102 dynamically or in real-time as it is received by the intermediary gaming trusted device 114a-n, 118. Alternatively, the received data may be buffered and transmitted to the gaming server 102 periodically such as every minute, ten (10) minutes, hour, or any other pre-defined time period.
The gaming server 102 may then process and store the gaming data received from the intermediary gaming trusted device 114a-n, 118. The stored gaming data may be used in case of a power outage, weak or lost signals, or any other loss of gaming data. Once the received gaming data is processed, the gaming server 102 may transmit additional gaming data in response to the processed gaming data. The additional gaming data may be transmitted, in real-time on an as needed basis or in a bulk transfer mode for batch operations, to the intermediary gaming trusted device 114a-n, 118 for display on the PED 114a-n, 120 or the gaming machine 104 so that the player can continue to play the game of chance or receive additional gaming information. For instance, a video poker game on the gaming machine 104 may receive one card at a time, or five cards at a time, or ten cards at a time. In another example, a 5-reel slot game may receive one random number seed at a time, or 100 random number seeds for the next 20 games. Player input may include a selection of one of a plurality of games of chance, player preference options, selection of advertisement information, or the like.
The gaming server 102 may be configured to determine the location of the intermediary gaming trusted device 114a-n, 118 using location server 120. Any known position or location methods may be used to determine the location of the intermediary gaming trusted device 114a-n, 118 such as cellular positioning, triangulation, global positioning systems, or any other location or positioning determining method. The position or location of the intermediary gaming trusted device 114a-n, 118 may be obtained periodically or at any pre-defined time period. For example, the intermediary gaming trusted device 114a-n, 118 may be pinged every thirty (30) seconds, minute, ten minutes, hour, or any periodic time interval for its location.
A user may be prevented from playing a game or using the intermediary trusted gaming device 114a-n, 118 due to location, time, establishment rules, government rules, or any other restrictions the gaming establishment may have or impose. For example, if the user decides to leave the gaming establishment and the location server 120 determines that the intermediary gaming trusted device 114a-n, 118 is outside the gaming establishment, the gaming server 102 may cause to the intermediary gaming trusted device to cease performing any gaming activities. In another embodiment, if the intermediary trusted gaming device 114a-n, 118 is in a restricted location such as the kids club, the intermediary trusted gaming device 114a-n may cease performing any gaming activities. In still another example, if the player has played or lost a certain amount of money, the intermediary trusted gaming device 114a-n may cease performing any gaming activities.
Intermediary trusted gaming device 200 may have connector 206 configured to connect to a PED, such as PED 112a-n, 118 illustrated in
In one embodiment, display 224 may be a projector. For example, if the image on the display of the PED is too small, the player may want to view a larger image to play the game of chance. The display may be configured to project the game of chance in a larger image and allow the player to play the game of chance. The image may be projected on a table, wall, or any other surface or non-surface.
The microphone 228 may be configured to receive audio input, such as, for example, voice input. For example, if the user is unable to input his password on the PED, for any reason, the user may speak his password into the microphone. In another example, the microphone 228 may be used to receive the user's voice to authenticate the user. Instead of the microphone 228, other biometric sensors such as a camera or a fingerprint sensor may also be used for authenticating the user of the PED.
Buttons 226a-n may be used for any desired purpose or reason. For example, buttons 226a-n may be used to turn the intermediary trusted gaming device 220 on or off. In another example, button 226a-n may be used to signal a gaming establishment personnel that the player would like to order a drink. In another embodiment, buttons 226a-n maybe a numeric keypad, or an alphanumeric keypad, or a directional keypad, and the like.
Although intermediary trusted gaming device 200, 220, 240 is illustrated as having a rectangular shape, this is for illustrating purposes and is not intended to be limiting. Intermediary trusted gaming device 200, 220, 240 may be formed of any desired shape such as a circle, triangle, star, shape of the gaming establishment's logo, and the like. Additionally, indicia may be printed anywhere on the housing of intermediary trusted gaming device 200, 220, 240. For example, the intermediary trusted gaming device 200, 220, 240 may be personalized for the player. In another example, the intermediary trusted gaming device 200, 220, 240 may include indicia of any sponsor, the gaming establishment, or any other desired indicia.
Referring now to
In another embodiment, intermediary trusted gaming device 310 may be coupled to the gaming machine 320 itself at I/O port 324. For example, the PED 300 may be low on batteries but the player would like to continue to play his game of chance. Thus, the intermediary trusted gaming device 310 may be coupled to the gaming machine 320 at I/O port 324. Although the I/O port is illustrated on housing 326 of gaming machine 320, this is for illustrative purposes only and not meant to be limiting. For example, I/O port 324 may also be positioned on a player tracking device 322 or in any other position on housing 326.
Whether connected to the PED 300 or gaming machine 320, intermediary trusted gaming device 310 may transmit or receive gaming data to or from gaming server 325 via any known wireless methods. If the intermediary trusted gaming device 310 is connected to the PED 300, the gaming data may be displayed on display 302 of the PED 300. If the intermediary trusted gaming device 310 is connected to the gaming machine 320, the gaming data may be displayed on display 328 or secondary display 330.
Intermediary trusted gaming device 400 may also have at least one transceiver 412. In one embodiment, the intermediary trusted gaming device 400 may have a long-range transceiver, short-range transceiver, or both. The transceiver 412 may be designed to locate the position of the intermediary trusted gaming device 400 through use of any known positioning methods as discussed in detail above. As stated above, intermediary trusted gaming device 400 may communicate wirelessly and therefore may have a wireless sensor 422.
Intermediary trusted gaming device 400 may have at least one memory 406. The memory 406 may be any type of memory configured to store gaming applications, game logic, game session data, authentication software, and the like. For example, the memory may be a non-volatile random access memory (NVRAM), flash memory, dynamic random access memory (“DRAM”)), and the like.
The intermediary trusted gaming device 400 may have a power source 424. The power source 424 may be any known power source such as a battery and may be powered through any known means. For example, the power source 424 may be powered when physically connected to a PED or plugged into a power outlet. When the power source 424 is an internal battery, it maybe recharged when connected to an external power source such as a power outlet. Having an internal battery onboard the intermediary trusted device 400 may maintain communication to another device in the network such as a location server or a game server even when the PED is not powered on. In one embodiment, the intermediary trusted device 400's connection to the location server persists so that its location can be accounted for at all time.
In one embodiment, intermediary trusted gaming device 400 may also have a cryptographic module 418 to decrypt communication received from a gaming server and/or PED and to encrypt communication transmitted to the PED and/or gaming server.
The associated untrusted PED may be detected at 504 by the intermediary gaming trusted device. If physically coupled to the untrusted PED, detection of the untrusted PED may occur when the intermediary gaming trusted device is coupled to the PED via the connector of the intermediary gaming trusted device. If communication of the untrusted PED is wireless, detection may occur when the intermediary gaming trusted device connects wirelessly with the untrusted PED.
A determination of whether the user of the untrusted PED is authenticated is made at 506. If the user is not authenticated, the method 500 may end. Authentication and/or verification of the user may be through any known authentication and verification methods such as, for example, biometric verification (i.e. voice recognition, retinal scan, fingerprint verification, and the like), username, password, account number, and the like. Authentication of the user may also include authentication via a web-application associated with the gaming establishment and/or uploading authentication software from the intermediary gaming trusted device to the untrusted PED. In another embodiment, the user of the untrusted PED may also obtain the intermediary gaming trusted device from a gaming establishment personnel. The gaming establishment personnel may then authenticate and/or verify the user as well as associate the intermediary gaming trusted device to the untrusted PED.
If the user of the untrusted PED is authenticated, the intermediary gaming trusted device may be authenticated at 508. If the intermediary gaming trusted device is not authenticated, the method 500 may end. Authentication of the intermediary gaming trusted device may be made by any known means. For example, a unique identifier of the intermediary gaming trusted device may be compared to identifiers stored at a gaming server. In one embodiment, the intermediary gaming trusted device may automatically connect to the gaming server and authenticate itself when turned on or powered up.
If the intermediary gaming trusted device is authenticated at 508, the intermediary gaming trusted device may receive gaming data at 510 from a gaming server. The gaming data may include a plurality of options. The gaming data may include gaming information or gaming establishment information. Gaming information may include, for example, player tracking information, gaming options, data to play a game of chance, funding information or options in order to play the games of chance, pay tables, and the like. The gaming establishment information may include, for example, advertisements (e.g. buffet coupons, movie trailers, and the like), tournament information, room booking information, entertainment information, and the like.
The untrusted PED becomes or is otherwise transformed into a trusted PED and the gaming data may then be transmitted to the associated trusted PED. As stated above, the gaming data may include a plurality of gaming options, such as, for example, a list of games of chance the user may select to play. The games of chance may be any game of chance such as blackjack, poker, roulette, craps, bingo, keno, video slot machines, and the like. Each list may also include a logo or any other indicia with each option, a summary of what the option is, a number of times the player has played each game of chance, the last time the selection was made by the player, or any other desired information.
A selection of one of the gaming options may be detected at 514. For example, the player may want and select to play a game of black jack. In one embodiment, selection of one of the gaming options may be executed by the user on the trusted PED. In another embodiment, selection of one of the gaming options may be selected on the intermediary gaming trusted device. Once a selection has been made, the intermediary gaming trusted device may transmit the selected gaming option to the gaming server at 516.
Referring now to
If the displayed data was to play a game of chance, the gaming session data may be generated at 524. In one embodiment, the intermediary gaming trusted device may generate the gaming session data at 524. For instance, the number of games played, by whom, where and when, and the aggregate amount of wager since the start of the game session maybe calculated and recorded by the intermediary gaming trusted device. In still another embodiment, the gaming session data may be generated from the gaming server and transmitted to the intermediary gaming trusted device. For instance, a random bonus amount and the associated triggering event maybe generated by the gaming server and sent to the intermediary gaming trusted device. In yet another embodiment, the gaming session data maybe generated from the user's inputs at the PED during the gaming session. Gaming session data may include any information the user inputs while playing a game, number of wins or losses, amount of funds remaining or added, clicking on advertisements, and any other gaming information generated during the game session. The gaming session data may be stored at 526. The gaming session data may be stored on the intermediary gaming trusted device periodically or dynamically in real-time. For example, the gaming session data may be stored or saved at predefined intervals such as every minute, every hour, every ten (10) seconds, and the like. In another example, the gaming session data may be stored dynamically as the gaming session data is generated.
The gaming session data may be transmitted to the gaming server at 528. The gaming session data may be transmitted to the gaming server periodically or dynamically in real-time. For example, the gaming session data may be buffered and transmitted at predefined intervals such as every minute, every hour, every ten (10) seconds, and the like. In another example, the gaming session data may be transmitted dynamically in real-time as the gaming session data is generated.
A determination of whether the gaming session is still permitted is made at 530. Gaming sessions may be permitted based on various factors such as location of the intermediary gaming trusted device, duration of play, time of day, user information, gaming regulations, amount played, and the like. For example, if the intermediary gaming trusted device is determined to be in the parking lot where playing games of chance are not permitted, the gaming session will end and the intermediary gaming trusted device may cease to perform any gaming activities. In another example, if gaming regulations prohibit game play after the loss of $500 within a 24-hr period, the gaming session will end and the intermediary gaming trusted device may cease to perform any gaming activities.
If the gaming session is permitted at 530, a determination of whether gaming information is requested is made at 532. If a request for gaming information is detected at 532, the intermediary gaming trusted device may transmit the request to the gaming server and the method 500 may continue at step 512 of
If the gaming session is determined to end at 534, the gaming session data may be transmitted to the gaming server at 536. Once the gaming session data is transmitted to the gaming server at 536, all gaming session data, gaming data, gaming software, and any other gaming related information and data are deleted from the associated trusted PED at 538. All gaming related information and data are deleted from the associated trusted PED to prevent fraud, hacking, and the like.
An authentication and/or verification request may be received at 604. The untrusted PED may receive the authentication request from detected intermediary gaming trusted electronic device. Authentication and/or verification of the user may be through any known authentication and verification methods such as, for example, biometric verification (i.e. voice recognition, retinal scan, fingerprint verification, and the like), username, password, account number, and the like. Authentication of the user may also include authentication via a web-application associated with the gaming establishment and/or uploading authentication software from the intermediary gaming trusted device to the untrusted PED. In another embodiment, the user of the untrusted PED may also obtain the intermediary gaming trusted device from a gaming establishment personnel. The gaming establishment personnel may then authenticate and/or verify the user as well as associate the intermediary gaming trusted device to the untrusted PED. In still another embodiment, the authentication request may require the untrusted PED to download software or an authentication application. The software may request the user of the untrusted PED to input authentication and/or verification information to authenticate and/or verify the user.
If the untrusted PED is not authenticated at 606, the intermediary gaming trusted device will cease to perform any tasks and the method 600 may end. If the untrusted PED is authenticated at 606, the untrusted PED then becomes or is otherwise converted to a trusted PED. The trusted PED may then receive gaming data from the intermediary gaming trusted electronic device at 608. The gaming data may have a plurality of gaming options. The gaming data may include gaming information or gaming establishment information. Gaming information may include, for example, player tracking information, gaming options, data to play a game of chance, funding information or options in order to play the games of chance, pay tables, and the like. The gaming establishment information may include, for example, advertisements (e.g. buffet coupons, movie trailers, and the like), tournament information, room booking information, entertainment information, and the like. The gaming options may include a list of games of chance the player may like to play such as, blackjack, poker, video slot machines, video games, keno, and the like. Each list may also include a logo or any other indicia with each option, a summary of what the option is, a number of times the player has played each game of chance, the last time the selection was made by the player, or any other desired information.
The gaming data may then be displayed on a display of the trusted PED at 610. The user of the trusted PED may select an option associated with the displayed gaming data which is then transmitted to the intermediary gaming trusted device at 612. The selection may be made using the trusted PED and/or the intermediary gaming trusted device. For example, if the gaming data was a list of games of chance the play may play, the list may be displayed on the display of the trusted PED and the use may select one of the games of chance to play. The selected game of chance may be transmitted to the intermediary gaming trusted device. In another example, if the gaming data was a coupon for the buffet, the option may be to accept or decline the coupon which the user may select. The selection may then be transmitted to the intermediary gaming trusted device.
If the user selected a game of chance to play using the trusted PED, gaming data may be received at 614 to start a gaming session for the player. The gaming data may be associated with the selected game of chance. For example, gaming data to play black jack may be received if the black jack option was selected. The gaming data may then be transmitted to the associated trusted PED for display on a display of the associated trusted PED at 616. Once displayed, any input associated with the displayed gaming data may be detected and transmitted to the intermediary gaming trusted device at 618. For example, if the data displayed was to play a game of chance, inputs associated with playing the game of chance may be detected such as a wagering amount, spin, hold, and the like. In another example, if the data displayed was a poker tournament, the input may be to register for the tournament. In still another example, if the displayed data was a coupon to the buffet, the input may be to add the coupon to the player tracking account, print the coupon, or a cancel the coupon. The user input may be detected from the PED or the intermediary gaming trusted device.
A determination of whether the gaming session is permitted is made at 620. Gaming sessions may be permitted based on various factors such as location of the intermediary gaming trusted device, duration of play, time of day, user information, gaming regulations, amount played, and the like. For example, if the intermediary gaming trusted device is determined to be in the parking lot where playing games of chance are not permitted, the gaming session will end and the intermediary gaming trusted device may cease to perform any gaming activities. In another example, if gaming regulations prohibit game play after the loss of $500 within a 24-hr period, the gaming session will end and the intermediary gaming trusted device may cease to perform any gaming activities.
If the gaming session is permitted at 620, a determination of whether the gaming session should end is made at 622. For example, if a cash-out input was detected, the gaming session may end. In another example, if the PED has been determined to have been moved out of the allowed area, the gaming session may also end. In yet another example, if there are no credits to play the game of chance, the gaming session may end. If the gaming session did not end at 622, the method may continue at step 608.
If the gaming session is determined to end at 622, the gaming session data may be transmitted to the intermediary gaming trusted device at 624. Once the gaming session data is transmitted to the intermediary gaming trusted device at 624, all gaming session data, gaming data, gaming software, and any other gaming related information and data are deleted from the associated trusted PED at 626. All gaming related information and data are deleted from the associated trusted PED to prevent fraud, hacking, and the like.
Authentication and/or verification of the untrusted PED may be through any known authentication and verification methods such as, for example, biometric verification (i.e. voice recognition, retinal scan, fingerprint verification, and the like) of the user, username, password, account number, device identifier, digital signature of the operating system and/or the software application, and the like. Authentication of the untrusted PED may also include authentication via a web-application associated with the gaming establishment and/or uploading authentication software from the intermediary gaming trusted device to the untrusted PED. The information received by the gaming server may be authenticated with information stored in a database, such as, for example, a player tracking base 110 illustrated in
Once authenticated at 704, gaming data may be sent to the intermediary gaming trusted device at 706. The gaming data may include gaming information or gaming establishment information. Gaming information may include, for example, player tracking information, gaming options, data to play a game of chance, funding information or options in order to play the games of chance, pay tables, and the like. The gaming establishment information may include, for example, advertisements (e.g. buffet coupons, movie trailers, and the like), tournament information, room booking information, entertainment information, and the like. The gaming data may include a plurality of gaming options, such as, for example, a list of games of chance the user may select to play. The games of chance may be any game of chance such as blackjack, poker, roulette, craps, sicbo, bingo, keno, video slot machines, and the like. Each list may also include a logo or any other indicia with each option, a summary of what the option is, a number of times the player has played each game of chance, the last time the selection was made by the player, or any other desired information.
A selected gaming option may be received at 708 from the intermediary gaming trusted device. Gaming data associated with the received selected gaming option may be transmitted at 710 to the intermediary gaming trusted device. For example, if the received selected gaming option is to play black jack, the transmitted gaming data may be associated with black jack. In another example, if the selected gaming option is to obtain movie tickets, the gaming data may be a list of movies playing at the theater.
The gaming server may periodically or dynamically receive gaming session data at 712 from the intermediary gaming trusted device. Gaming session data may be any session data resulting from playing a game of chance such as number of wins or losses, amount of funds remaining or added, clicking on advertisements, and any other gaming information generated during the game session. The gaming session data may be received periodically or dynamically in real-time. For example, the gaming session data may be received at predefined intervals such as every minute, every hour, every ten (10) seconds, and the like. In another example, the gaming session data may be received dynamically in real-time as the gaming session data is generated.
A determination of whether the gaming session is permitted is made at 714. Gaming sessions may be permitted based on various factors such as location of the intermediary gaming trusted device, duration of play, time of day, user information, gaming regulations, amount played, and the like. For example, if the intermediary gaming trusted device is determined to be in the parking lot where playing games of chance are not permitted, the gaming session will end and the intermediary gaming trusted device may cease to perform any gaming activities. In another example, if gaming regulations prohibit game play after the loss of $500 within a 24-hr period, the gaming session will end and the intermediary gaming trusted device may cease to perform any gaming activities.
In no gaming session is permitted at 714, the method 700 may end. If the gaming session is permitted at 714, a determination of whether gaming information is requested is made at 716. If a request for gaming information is detected at 716, the method may return to step 706. If a request for gaming information is not detected at 716, the method 700 may end.
While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein.
This application is continuation of U.S. patent application Ser. No. 15/876,095, filed Jan. 19, 2018, and entitled “PORTABLE INTERMEDIARY TRUSTED DEVICE”, which is hereby incorporated herein by reference for all purposes, and which in turn is a continuation of U.S. patent application Ser. No. 15/400,840, filed Jan. 6, 2017, and entitled “PORTABLE INTERMEDIARY TRUSTED DEVICE”, which is hereby incorporated herein by reference for all purposes, and which in turn is a continuation of U.S. patent application Ser. No. 13/833,116, filed Mar. 15, 2013, and entitled “PORTABLE INTERMEDIARY TRUSTED DEVICE”, which is hereby incorporated herein by reference for all purposes. This application is also related to U.S. application Ser. No. 13/833,953, filed Mar. 15, 2013, and entitled “GAMING DEVICE DOCKING STATION,” which is hereby incorporated by reference herein in its entirety for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
2033638 | Koppl | Mar 1936 | A |
2062923 | Nagy | Dec 1936 | A |
4741539 | Sutton et al. | May 1988 | A |
4948138 | Pease et al. | Aug 1990 | A |
5067712 | Georgilas | Nov 1991 | A |
5275400 | Weingardt | Jan 1994 | A |
5429361 | Raven et al. | Jul 1995 | A |
5489103 | Okamoto | Feb 1996 | A |
5630757 | Gagin | May 1997 | A |
5655961 | Acres et al. | Aug 1997 | A |
5704835 | Dietz, II | Jan 1998 | A |
5727786 | Weingardt | Mar 1998 | A |
5833537 | Barrie | Nov 1998 | A |
5842921 | Mindes | Dec 1998 | A |
5919091 | Bell et al. | Jul 1999 | A |
5947820 | Morro et al. | Sep 1999 | A |
5997401 | Crawford | Dec 1999 | A |
6001016 | Walker et al. | Dec 1999 | A |
6039648 | Guinn et al. | Mar 2000 | A |
6059289 | Vancura | May 2000 | A |
6089977 | Bennett | Jul 2000 | A |
6095920 | Sudahiro | Aug 2000 | A |
6110041 | Walker et al. | Aug 2000 | A |
6142872 | Walker et al. | Nov 2000 | A |
6146271 | Kadici | Nov 2000 | A |
6146273 | Olsen | Nov 2000 | A |
6165071 | Weiss | Dec 2000 | A |
6231445 | Acres | May 2001 | B1 |
6244958 | Acres | Jun 2001 | B1 |
6270412 | Crawford et al. | Aug 2001 | B1 |
6290600 | Glasson | Sep 2001 | B1 |
6293866 | Walker et al. | Sep 2001 | B1 |
6353390 | Beri et al. | Mar 2002 | B1 |
6364768 | Acres et al. | Apr 2002 | B1 |
6404884 | Marwell et al. | Jun 2002 | B1 |
6416406 | Duhamel | Jul 2002 | B1 |
6416409 | Jordan | Jul 2002 | B1 |
6443452 | Brune | Sep 2002 | B1 |
6491584 | Graham et al. | Dec 2002 | B2 |
6505095 | Kolls | Jan 2003 | B1 |
6508710 | Paravia et al. | Jan 2003 | B1 |
6561900 | Baerlocker et al. | May 2003 | B1 |
6592457 | Frohm et al. | Jul 2003 | B1 |
6612574 | Cole et al. | Sep 2003 | B1 |
6620046 | Rowe | Sep 2003 | B2 |
6641477 | Dietz, II | Nov 2003 | B1 |
6645078 | Mattice | Nov 2003 | B1 |
6719630 | Seelig et al. | Apr 2004 | B1 |
6749510 | Giobbi | Jun 2004 | B2 |
6758757 | Luciano, Jr. et al. | Jul 2004 | B2 |
6773345 | Walker et al. | Aug 2004 | B2 |
6778820 | Tendler | Aug 2004 | B2 |
6780111 | Cannon et al. | Aug 2004 | B2 |
6799032 | McDonnell et al. | Sep 2004 | B2 |
6800027 | Giobbi et al. | Oct 2004 | B2 |
6804763 | Stockdale et al. | Oct 2004 | B1 |
6811486 | Luciano, Jr. | Nov 2004 | B1 |
6843725 | Nelson | Jan 2005 | B2 |
6846238 | Wells | Jan 2005 | B2 |
6848995 | Walker et al. | Feb 2005 | B1 |
6852029 | Baltz et al. | Feb 2005 | B2 |
6869361 | Sharpless et al. | Mar 2005 | B2 |
6875106 | Weiss et al. | Apr 2005 | B2 |
6884170 | Rowe | Apr 2005 | B2 |
6884172 | Lloyd et al. | Apr 2005 | B1 |
6902484 | Idaka | Jun 2005 | B2 |
6908390 | Nguyen et al. | Jun 2005 | B2 |
6913532 | Bearlocher et al. | Jul 2005 | B2 |
6923721 | Luciano et al. | Aug 2005 | B2 |
6935958 | Nelson | Aug 2005 | B2 |
6949022 | Showers et al. | Sep 2005 | B1 |
6955600 | Glavich et al. | Oct 2005 | B2 |
6971956 | Rowe et al. | Dec 2005 | B2 |
6984174 | Cannon et al. | Jan 2006 | B2 |
6997803 | LeMay et al. | Feb 2006 | B2 |
7018292 | Tracy et al. | Mar 2006 | B2 |
7032115 | Kashani | Apr 2006 | B2 |
7033276 | Walker et al. | Apr 2006 | B2 |
7035626 | Luciano | Apr 2006 | B1 |
7037195 | Schneider et al. | May 2006 | B2 |
7048628 | Schneider | May 2006 | B2 |
7048630 | Berg et al. | May 2006 | B2 |
7063617 | Brosnan et al. | Jun 2006 | B2 |
7076329 | Kolls | Jul 2006 | B1 |
7089264 | Guido et al. | Aug 2006 | B1 |
7094148 | Bearlocher et al. | Aug 2006 | B2 |
7105736 | Laakso | Sep 2006 | B2 |
7111141 | Nelson | Sep 2006 | B2 |
7144321 | Mayeroff | Dec 2006 | B2 |
7152783 | Charrin | Dec 2006 | B2 |
7169041 | Tessmer et al. | Jan 2007 | B2 |
7169052 | Beaulieu et al. | Jan 2007 | B2 |
7175523 | Gilmore et al. | Feb 2007 | B2 |
7181228 | Boesch | Feb 2007 | B2 |
7182690 | Giobbi et al. | Feb 2007 | B2 |
7198571 | LeMay | Apr 2007 | B2 |
RE39644 | Alcorn et al. | May 2007 | E |
7217191 | Allen et al. | May 2007 | B2 |
7243104 | Bill | Jul 2007 | B2 |
7247098 | Bradford et al. | Jul 2007 | B1 |
7259718 | Patterson et al. | Aug 2007 | B2 |
7275989 | Moody | Oct 2007 | B2 |
7285047 | Gielb et al. | Oct 2007 | B2 |
7311608 | Danieli | Dec 2007 | B1 |
7314408 | Cannon et al. | Jan 2008 | B2 |
7316615 | Soltys et al. | Jan 2008 | B2 |
7316619 | Nelson | Jan 2008 | B2 |
7318775 | Brosnan et al. | Jan 2008 | B2 |
7326116 | O'Donovan et al. | Feb 2008 | B2 |
7330108 | Thomas | Feb 2008 | B2 |
7346358 | Wood et al. | Mar 2008 | B2 |
7355112 | Laakso | Apr 2008 | B2 |
7384338 | Rothschild et al. | Jun 2008 | B2 |
7387571 | Walker et al. | Jun 2008 | B2 |
7393278 | Gerson et al. | Jul 2008 | B2 |
7396990 | Lu et al. | Jul 2008 | B2 |
7415426 | Williams et al. | Aug 2008 | B2 |
7425177 | Rodgers et al. | Sep 2008 | B2 |
7427234 | Soltys et al. | Sep 2008 | B2 |
7427236 | Kaminkow et al. | Sep 2008 | B2 |
7427708 | Ohmura | Sep 2008 | B2 |
7431650 | Kessman | Oct 2008 | B2 |
7448949 | Kaminkow et al. | Nov 2008 | B2 |
7500913 | Baerlocher | Mar 2009 | B2 |
7510474 | Carter | Mar 2009 | B2 |
7513828 | Nguyen et al. | Apr 2009 | B2 |
7519838 | Suurballe | Apr 2009 | B1 |
7559838 | Walker et al. | Jul 2009 | B2 |
7563167 | Walker et al. | Jul 2009 | B2 |
7572183 | Olivas et al. | Aug 2009 | B2 |
7585222 | Muir | Sep 2009 | B2 |
7602298 | Thomas | Oct 2009 | B2 |
7607174 | Kashchenko et al. | Oct 2009 | B1 |
7611409 | Muir et al. | Nov 2009 | B2 |
7637810 | Amaitis et al. | Dec 2009 | B2 |
7644861 | Alderucci et al. | Jan 2010 | B2 |
7653757 | Fernald et al. | Jan 2010 | B1 |
7693306 | Huber | Apr 2010 | B2 |
7699703 | Muir et al. | Apr 2010 | B2 |
7722453 | Lark et al. | May 2010 | B2 |
7758423 | Foster et al. | Jul 2010 | B2 |
7771271 | Walker et al. | Aug 2010 | B2 |
7780529 | Rowe et al. | Aug 2010 | B2 |
7780531 | Englman et al. | Aug 2010 | B2 |
7785192 | Canterbury et al. | Aug 2010 | B2 |
7811172 | Asher et al. | Oct 2010 | B2 |
7819749 | Fish | Oct 2010 | B1 |
7822688 | Labron | Oct 2010 | B2 |
7828652 | Nguyen et al. | Nov 2010 | B2 |
7828654 | Carter | Nov 2010 | B2 |
7828661 | Fish | Nov 2010 | B1 |
7850528 | Wells | Dec 2010 | B2 |
7874919 | Paulsen et al. | Jan 2011 | B2 |
7877798 | Saunders et al. | Jan 2011 | B2 |
7883413 | Paulsen | Feb 2011 | B2 |
7892097 | Muir et al. | Feb 2011 | B2 |
7909692 | Nguyen et al. | Mar 2011 | B2 |
7909699 | Parrott et al. | Mar 2011 | B2 |
7918728 | Nguyen et al. | Apr 2011 | B2 |
7927211 | Rowe et al. | Apr 2011 | B2 |
7927212 | Hedrick et al. | Apr 2011 | B2 |
7951008 | Wolf et al. | May 2011 | B2 |
8057298 | Nguyen et al. | Nov 2011 | B2 |
8057303 | Rasmussen | Nov 2011 | B2 |
8087988 | Nguyen et al. | Jan 2012 | B2 |
8117608 | Slettehaugh et al. | Feb 2012 | B1 |
8133113 | Nguyen | Mar 2012 | B2 |
8182326 | Speer et al. | May 2012 | B2 |
8210927 | Hedrick | Jul 2012 | B2 |
8221245 | Walker | Jul 2012 | B2 |
8226459 | Barrett | Jul 2012 | B2 |
8226474 | Nguyen et al. | Jul 2012 | B2 |
8231456 | Zielinski | Jul 2012 | B2 |
8235803 | Loose et al. | Aug 2012 | B2 |
8282475 | Nguyen et al. | Oct 2012 | B2 |
8323099 | Durham et al. | Dec 2012 | B2 |
8337290 | Nguyen et al. | Dec 2012 | B2 |
8342946 | Amaitis | Jan 2013 | B2 |
8393948 | Allen et al. | Mar 2013 | B2 |
8403758 | Hornik et al. | Mar 2013 | B2 |
8430745 | Agarwal et al. | Apr 2013 | B2 |
8461958 | Saenz | Jun 2013 | B2 |
8469813 | Joshi | Jun 2013 | B2 |
8529345 | Nguyen | Sep 2013 | B2 |
8597108 | Nguyen | Dec 2013 | B2 |
8602875 | Nguyen | Dec 2013 | B2 |
8613655 | Kisenwether et al. | Dec 2013 | B2 |
8613659 | Nelson et al. | Dec 2013 | B2 |
8696470 | Nguyen | Apr 2014 | B2 |
8745417 | Huang et al. | Jun 2014 | B2 |
8834254 | Buchholz et al. | Sep 2014 | B2 |
8858323 | Nguyen et al. | Oct 2014 | B2 |
8864586 | Nguyen | Oct 2014 | B2 |
8942995 | Kerr | Jan 2015 | B1 |
9039507 | Allen et al. | May 2015 | B2 |
9235952 | Nguyen | Jan 2016 | B2 |
9292996 | Davis et al. | Mar 2016 | B2 |
9325203 | Nguyen | Apr 2016 | B2 |
9466171 | Hornik | Oct 2016 | B2 |
9483901 | Nguyen | Nov 2016 | B2 |
9486697 | Nguyen | Nov 2016 | B2 |
9486704 | Nguyen | Nov 2016 | B2 |
9530277 | Nelson et al. | Dec 2016 | B2 |
9576425 | Nguyen | Feb 2017 | B2 |
9626826 | Nguyen | Apr 2017 | B2 |
9666021 | Nguyen | May 2017 | B2 |
9672686 | Nguyen | Jun 2017 | B2 |
9741205 | Nguyen | Aug 2017 | B2 |
9811973 | Nguyen | Nov 2017 | B2 |
9814970 | Nguyen | Nov 2017 | B2 |
9842462 | Nguyen | Dec 2017 | B2 |
9875606 | Nguyen | Jan 2018 | B2 |
9875609 | Nguyen | Jan 2018 | B2 |
9981180 | Koyanagi et al. | May 2018 | B2 |
10068429 | Gagner et al. | Sep 2018 | B2 |
10115270 | Gagner et al. | Oct 2018 | B2 |
10140816 | Nguyen | Nov 2018 | B2 |
10325447 | Malek | Jun 2019 | B2 |
10421010 | Nguyen | Sep 2019 | B2 |
10438446 | Nguyen | Oct 2019 | B2 |
10445978 | Nguyen | Oct 2019 | B2 |
20010004607 | Olsen | Jun 2001 | A1 |
20010016516 | Takatsuka | Aug 2001 | A1 |
20010024971 | Brossard | Sep 2001 | A1 |
20010031659 | Perrie | Oct 2001 | A1 |
20010047291 | Garahi | Nov 2001 | A1 |
20020006822 | Krintzman | Jan 2002 | A1 |
20020042295 | Walker et al. | Apr 2002 | A1 |
20020043759 | Vancura | Apr 2002 | A1 |
20020045474 | Singer | Apr 2002 | A1 |
20020107065 | Rowe | Aug 2002 | A1 |
20020111210 | Luciano, Jr. et al. | Aug 2002 | A1 |
20020111213 | McEntee et al. | Aug 2002 | A1 |
20020113369 | Weingardt | Aug 2002 | A1 |
20020116615 | Nguyen et al. | Aug 2002 | A1 |
20020133418 | Hammond et al. | Sep 2002 | A1 |
20020137217 | Rowe et al. | Sep 2002 | A1 |
20020142825 | Lark et al. | Oct 2002 | A1 |
20020147047 | Letovsky et al. | Oct 2002 | A1 |
20020147049 | Carter, Sr. | Oct 2002 | A1 |
20020151366 | Walker et al. | Oct 2002 | A1 |
20020152120 | Howington | Oct 2002 | A1 |
20020167536 | Valdes et al. | Nov 2002 | A1 |
20020177483 | Cannon | Nov 2002 | A1 |
20020183105 | Cannon et al. | Dec 2002 | A1 |
20030001338 | Bennett et al. | Jan 2003 | A1 |
20030003996 | Nguyen | Jan 2003 | A1 |
20030004871 | Rowe et al. | Jan 2003 | A1 |
20030008696 | Abecassis et al. | Jan 2003 | A1 |
20030027635 | Walker et al. | Feb 2003 | A1 |
20030064805 | Wells | Apr 2003 | A1 |
20030064807 | Walker et al. | Apr 2003 | A1 |
20030092480 | White et al. | May 2003 | A1 |
20030100361 | Sharpless et al. | May 2003 | A1 |
20030104860 | Cannon et al. | Jun 2003 | A1 |
20030104865 | Itkis et al. | Jun 2003 | A1 |
20030148809 | Nelson | Aug 2003 | A1 |
20030162588 | Brosnan et al. | Aug 2003 | A1 |
20030195024 | Slattery | Oct 2003 | A1 |
20030199295 | Vancura | Oct 2003 | A1 |
20030224852 | Walker et al. | Dec 2003 | A1 |
20030224854 | Joao | Dec 2003 | A1 |
20040002386 | Wolfe et al. | Jan 2004 | A1 |
20040005919 | Walker et al. | Jan 2004 | A1 |
20040023709 | Beaulieu et al. | Feb 2004 | A1 |
20040023716 | Gauselmann | Feb 2004 | A1 |
20040038736 | Bryant | Feb 2004 | A1 |
20040048650 | Mierau et al. | Mar 2004 | A1 |
20040068460 | Feeley | Apr 2004 | A1 |
20040082385 | Silva et al. | Apr 2004 | A1 |
20040106449 | Walker et al. | Jun 2004 | A1 |
20040127277 | Walker | Jul 2004 | A1 |
20040127290 | Walker et al. | Jul 2004 | A1 |
20040137987 | Nguyen et al. | Jul 2004 | A1 |
20040147308 | Walker et al. | Jul 2004 | A1 |
20040152508 | Lind | Aug 2004 | A1 |
20040199631 | Natsume | Oct 2004 | A1 |
20040214622 | Atkinson | Oct 2004 | A1 |
20040224753 | Odonovan et al. | Nov 2004 | A1 |
20040229671 | Stronach | Nov 2004 | A1 |
20040256803 | Ko | Dec 2004 | A1 |
20040259633 | Gentles et al. | Dec 2004 | A1 |
20050003890 | Hedrick et al. | Jan 2005 | A1 |
20050004980 | Vadjinia | Jan 2005 | A1 |
20050026696 | Hashimoto et al. | Feb 2005 | A1 |
20050054446 | Kammler | Mar 2005 | A1 |
20050101376 | Walker et al. | May 2005 | A1 |
20050101383 | Wells | May 2005 | A1 |
20050130728 | Nguyen et al. | Jun 2005 | A1 |
20050130731 | Englman | Jun 2005 | A1 |
20050137014 | Vetelaninen | Jun 2005 | A1 |
20050170883 | Muskin et al. | Aug 2005 | A1 |
20050181865 | Luciano | Aug 2005 | A1 |
20050181870 | Nguyen et al. | Aug 2005 | A1 |
20050181875 | Hoehne | Aug 2005 | A1 |
20050187020 | Amaitis et al. | Aug 2005 | A1 |
20050202875 | Murphy et al. | Sep 2005 | A1 |
20050209002 | Blythe et al. | Sep 2005 | A1 |
20050221881 | Lannert | Oct 2005 | A1 |
20050223219 | Gatto et al. | Oct 2005 | A1 |
20050239546 | Hedrick | Oct 2005 | A1 |
20050255919 | Nelson | Nov 2005 | A1 |
20050273635 | Wilcox et al. | Dec 2005 | A1 |
20050277471 | Russell et al. | Dec 2005 | A1 |
20050282637 | Gatto et al. | Dec 2005 | A1 |
20060009283 | Englman et al. | Jan 2006 | A1 |
20060036874 | Cockerille | Feb 2006 | A1 |
20060046822 | Kaminkow et al. | Mar 2006 | A1 |
20060046830 | Webb | Mar 2006 | A1 |
20060046849 | Kovacs | Mar 2006 | A1 |
20060068893 | Jaffe et al. | Mar 2006 | A1 |
20060073869 | LeMay et al. | Apr 2006 | A1 |
20060073897 | Englman et al. | Apr 2006 | A1 |
20060079317 | Flemming et al. | Apr 2006 | A1 |
20060121972 | Walker | Jun 2006 | A1 |
20060126529 | Hardy | Jun 2006 | A1 |
20060148551 | Walker et al. | Jul 2006 | A1 |
20060189382 | Muir et al. | Aug 2006 | A1 |
20060217170 | Roireau | Sep 2006 | A1 |
20060217193 | Walker et al. | Sep 2006 | A1 |
20060247028 | Brosnan et al. | Nov 2006 | A1 |
20060247035 | Rowe et al. | Nov 2006 | A1 |
20060252530 | Oberberger et al. | Nov 2006 | A1 |
20060253481 | Guido et al. | Nov 2006 | A1 |
20060281525 | Borissov | Dec 2006 | A1 |
20060281541 | Nguyen et al. | Dec 2006 | A1 |
20060287106 | Jensen | Dec 2006 | A1 |
20070004510 | Underdahl et al. | Jan 2007 | A1 |
20070026935 | Wolf et al. | Feb 2007 | A1 |
20070026942 | Kinsley | Feb 2007 | A1 |
20070054739 | Amaitis et al. | Mar 2007 | A1 |
20070060254 | Muir | Mar 2007 | A1 |
20070060306 | Amaitis et al. | Mar 2007 | A1 |
20070060319 | Block et al. | Mar 2007 | A1 |
20070060358 | Amaitas et al. | Mar 2007 | A1 |
20070077981 | Hungate et al. | Apr 2007 | A1 |
20070087833 | Feeney et al. | Apr 2007 | A1 |
20070087834 | Moser et al. | Apr 2007 | A1 |
20070093299 | Bergeron | Apr 2007 | A1 |
20070129123 | Eryou et al. | Jun 2007 | A1 |
20070129148 | Van Luchene | Jun 2007 | A1 |
20070149279 | Norden et al. | Jun 2007 | A1 |
20070149286 | Bemmel | Jun 2007 | A1 |
20070159301 | Hirt et al. | Jul 2007 | A1 |
20070161402 | Ng et al. | Jul 2007 | A1 |
20070184896 | Dickerson | Aug 2007 | A1 |
20070184904 | Lee | Aug 2007 | A1 |
20070191109 | Crowder et al. | Aug 2007 | A1 |
20070207852 | Nelson et al. | Sep 2007 | A1 |
20070207854 | Wolf et al. | Sep 2007 | A1 |
20070238505 | Okada | Oct 2007 | A1 |
20070241187 | Alderucci et al. | Oct 2007 | A1 |
20070248036 | Nevalainen | Oct 2007 | A1 |
20070257430 | Hardy et al. | Nov 2007 | A1 |
20070259713 | Fiden et al. | Nov 2007 | A1 |
20070259717 | Mattice et al. | Nov 2007 | A1 |
20070270213 | Nguyen et al. | Nov 2007 | A1 |
20070275777 | Walker et al. | Nov 2007 | A1 |
20070275779 | Amaitis et al. | Nov 2007 | A1 |
20070281782 | Amaitis et al. | Dec 2007 | A1 |
20070281785 | Amaitas et al. | Dec 2007 | A1 |
20070298873 | Nguyen et al. | Dec 2007 | A1 |
20080015032 | Bradford et al. | Jan 2008 | A1 |
20080020824 | Cuddy et al. | Jan 2008 | A1 |
20080020845 | Low | Jan 2008 | A1 |
20080032787 | Low et al. | Feb 2008 | A1 |
20080070652 | Nguyen et al. | Mar 2008 | A1 |
20080070681 | Marks et al. | Mar 2008 | A1 |
20080076505 | Nguyen | Mar 2008 | A1 |
20080076506 | Nguyen et al. | Mar 2008 | A1 |
20080076548 | Paulsen | Mar 2008 | A1 |
20080076572 | Nguyen et al. | Mar 2008 | A1 |
20080096650 | Baerlocher | Apr 2008 | A1 |
20080102916 | Kovacs | May 2008 | A1 |
20080102956 | Burman et al. | May 2008 | A1 |
20080102957 | Burnman et al. | May 2008 | A1 |
20080113772 | Burrill et al. | May 2008 | A1 |
20080119267 | Denlay | May 2008 | A1 |
20080013906 | Lutnick | Jun 2008 | A1 |
20080146321 | Parente | Jun 2008 | A1 |
20080146344 | Rowe et al. | Jun 2008 | A1 |
20080150902 | Edpalm et al. | Jun 2008 | A1 |
20080153583 | Huntley et al. | Jun 2008 | A1 |
20080161110 | Campbell | Jul 2008 | A1 |
20080167106 | Lutnick et al. | Jul 2008 | A1 |
20080182667 | Davis et al. | Jul 2008 | A1 |
20080207307 | Cunningham, II et al. | Aug 2008 | A1 |
20088020025 | Alderucci | Aug 2008 | |
20080214258 | Brosnan et al. | Sep 2008 | A1 |
20080215319 | Lu | Sep 2008 | A1 |
20080234047 | Nguyen | Sep 2008 | A1 |
20080238610 | Rosenbereg | Oct 2008 | A1 |
20080248849 | Lutnick | Oct 2008 | A1 |
20080248865 | Cole | Oct 2008 | A1 |
20080252419 | Batchelor | Oct 2008 | A1 |
20080254878 | Sauders et al. | Oct 2008 | A1 |
20080254881 | Lutnick et al. | Oct 2008 | A1 |
20080254883 | Patel et al. | Oct 2008 | A1 |
20080254891 | Sauders et al. | Oct 2008 | A1 |
20080254892 | Sauders et al. | Oct 2008 | A1 |
20080254897 | Sauders et al. | Oct 2008 | A1 |
20080263173 | Weber et al. | Oct 2008 | A1 |
20080300058 | Sum et al. | Dec 2008 | A1 |
20080305864 | Kelly et al. | Dec 2008 | A1 |
20080305865 | Kelly et al. | Dec 2008 | A1 |
20080305866 | Kelly et al. | Dec 2008 | A1 |
20080311994 | Amaitas et al. | Dec 2008 | A1 |
20080318669 | Buchholz | Dec 2008 | A1 |
20080318686 | Crowder et al. | Dec 2008 | A1 |
20090005165 | Arezina et al. | Jan 2009 | A1 |
20090011822 | Englman | Jan 2009 | A1 |
20090017906 | Jackson | Jan 2009 | A1 |
20090021381 | Higuchi | Jan 2009 | A1 |
20090029766 | Lutnick et al. | Jan 2009 | A1 |
20090054149 | Brosnan et al. | Feb 2009 | A1 |
20090077396 | Tsai et al. | Mar 2009 | A1 |
20090088258 | Saunders et al. | Apr 2009 | A1 |
20090098925 | Gagner et al. | Apr 2009 | A1 |
20090104977 | Zielinski | Apr 2009 | A1 |
20090104983 | Okada | Apr 2009 | A1 |
20090118002 | Lyons | May 2009 | A1 |
20090118013 | Finnimore et al. | May 2009 | A1 |
20090118022 | Lyons et al. | May 2009 | A1 |
20090124366 | Aoki et al. | May 2009 | A1 |
20090124390 | Seelig et al. | May 2009 | A1 |
20090131146 | Arezina et al. | May 2009 | A1 |
20090131151 | Harris et al. | May 2009 | A1 |
20090132163 | Ashley et al. | May 2009 | A1 |
20090137255 | Ashley et al. | May 2009 | A1 |
20090138133 | Buchholz et al. | May 2009 | A1 |
20090143141 | Wells | Jun 2009 | A1 |
20090149245 | Fabbri | Jun 2009 | A1 |
20090149261 | Chen et al. | Jun 2009 | A1 |
20090153342 | Thorn | Jun 2009 | A1 |
20090156303 | Kiely et al. | Jun 2009 | A1 |
20090163272 | Baker | Jun 2009 | A1 |
20090176578 | Herrmann et al. | Jul 2009 | A1 |
20090191962 | Hardy et al. | Jul 2009 | A1 |
20090197684 | Arezina et al. | Aug 2009 | A1 |
20090216547 | Canora et al. | Aug 2009 | A1 |
20090219901 | Bull et al. | Sep 2009 | A1 |
20090221342 | Katz et al. | Sep 2009 | A1 |
20090227302 | Abe | Sep 2009 | A1 |
20090239666 | Hall et al. | Sep 2009 | A1 |
20090264190 | Davis et al. | Oct 2009 | A1 |
20090270170 | Patton | Oct 2009 | A1 |
20090271287 | Halpern | Oct 2009 | A1 |
20090275410 | Kisenwether et al. | Nov 2009 | A1 |
20090275411 | Kisenwether et al. | Nov 2009 | A1 |
20090280910 | Gagner et al. | Nov 2009 | A1 |
20090282469 | Lynch | Nov 2009 | A1 |
20090298468 | Hsu | Dec 2009 | A1 |
20100002897 | Keady | Jan 2010 | A1 |
20100004058 | Acres | Jan 2010 | A1 |
20100016069 | Herrmann | Jan 2010 | A1 |
20100049738 | Mathur et al. | Feb 2010 | A1 |
20100056248 | Acres | Mar 2010 | A1 |
20100062833 | Mattice et al. | Mar 2010 | A1 |
20100062840 | Herrmann et al. | Mar 2010 | A1 |
20100079237 | Falk | Apr 2010 | A1 |
20100081501 | Carpenter et al. | Apr 2010 | A1 |
20100081509 | Burke | Apr 2010 | A1 |
20100099499 | Amaitis et al. | Apr 2010 | A1 |
20100106612 | Gupta | Apr 2010 | A1 |
20100115591 | Kane-Esrig | May 2010 | A1 |
20100120486 | DeWaal | May 2010 | A1 |
20100124967 | Lutnick et al. | May 2010 | A1 |
20100130276 | Fiden | May 2010 | A1 |
20100160035 | Herrmann | Jun 2010 | A1 |
20100160043 | Fujimoto et al. | Jun 2010 | A1 |
20100178977 | Kim et al. | Jul 2010 | A1 |
20100184509 | Sylla | Jul 2010 | A1 |
20100197383 | Rader et al. | Aug 2010 | A1 |
20100197385 | Aoki et al. | Aug 2010 | A1 |
20100203955 | Sylla | Aug 2010 | A1 |
20100203963 | Allen | Aug 2010 | A1 |
20100227662 | Speer et al. | Sep 2010 | A1 |
20100227670 | Arezine et al. | Sep 2010 | A1 |
20100227671 | Laaroussi | Sep 2010 | A1 |
20100227687 | Speer et al. | Sep 2010 | A1 |
20100234091 | Baerlocher et al. | Sep 2010 | A1 |
20100279764 | Allen et al. | Nov 2010 | A1 |
20100323780 | Acres | Dec 2010 | A1 |
20100325703 | Etchegoyen | Dec 2010 | A1 |
20110009181 | Speer et al. | Jan 2011 | A1 |
20110039615 | Acres | Feb 2011 | A1 |
20110053679 | Canterbury et al. | Mar 2011 | A1 |
20110065492 | Acres | Mar 2011 | A1 |
20110105216 | Cohen | May 2011 | A1 |
20110111827 | Nicely et al. | May 2011 | A1 |
20110111843 | Nicely et al. | May 2011 | A1 |
20110111860 | Nguyen | May 2011 | A1 |
20110118010 | Brune | May 2011 | A1 |
20110159966 | Gura et al. | Jun 2011 | A1 |
20110183732 | Block | Jul 2011 | A1 |
20110183749 | Allen | Jul 2011 | A1 |
20110207525 | Allen | Aug 2011 | A1 |
20110212711 | Scott | Sep 2011 | A1 |
20110212767 | Barclay et al. | Sep 2011 | A1 |
20110223993 | Allen et al. | Sep 2011 | A1 |
20110244952 | Schueller | Oct 2011 | A1 |
20110263318 | Agarwal et al. | Oct 2011 | A1 |
20110269548 | Barclay et al. | Nov 2011 | A1 |
20110306400 | Nguyen | Dec 2011 | A1 |
20110306426 | Novak et al. | Dec 2011 | A1 |
20120015709 | Bennett et al. | Jan 2012 | A1 |
20120028703 | Anderson et al. | Feb 2012 | A1 |
20120028718 | Barclay et al. | Feb 2012 | A1 |
20120034968 | Watkins et al. | Feb 2012 | A1 |
20120046110 | Amaitis | Feb 2012 | A1 |
20120094769 | Nguyen et al. | Apr 2012 | A1 |
20120100908 | Wells | Apr 2012 | A1 |
20120108319 | Caputo et al. | May 2012 | A1 |
20120122561 | Hedrick | May 2012 | A1 |
20120122567 | Gangadharan et al. | May 2012 | A1 |
20120122584 | Nguyen | May 2012 | A1 |
20120122590 | Nguyen | May 2012 | A1 |
20120172130 | Acres | Jul 2012 | A1 |
20120184362 | Barclay et al. | Jul 2012 | A1 |
20120184363 | Barclay et al. | Jul 2012 | A1 |
20120190426 | Acres | Jul 2012 | A1 |
20120194448 | Rothkopf | Aug 2012 | A1 |
20120208618 | Frerking | Aug 2012 | A1 |
20120231885 | Speer, II | Sep 2012 | A1 |
20120239566 | Everett | Sep 2012 | A1 |
20120322563 | Nguyen et al. | Dec 2012 | A1 |
20120330740 | Pennington et al. | Dec 2012 | A1 |
20130005433 | Holch | Jan 2013 | A1 |
20130005443 | Kosta | Jan 2013 | A1 |
20130005453 | Nguyen et al. | Jan 2013 | A1 |
20130059650 | Sylla et al. | Mar 2013 | A1 |
20130065668 | LeMay | Mar 2013 | A1 |
20130103965 | Golembeski | Apr 2013 | A1 |
20130104193 | Gatto et al. | Apr 2013 | A1 |
20130130766 | Harris et al. | May 2013 | A1 |
20130132745 | Schoening et al. | May 2013 | A1 |
20130165210 | Nelson | Jun 2013 | A1 |
20130185559 | Morel | Jul 2013 | A1 |
20130196756 | Nguyen | Aug 2013 | A1 |
20130196776 | Nguyen | Aug 2013 | A1 |
20130210513 | Nguyen | Aug 2013 | A1 |
20130210514 | Nguyen | Aug 2013 | A1 |
20130210530 | Nguyen | Aug 2013 | A1 |
20130225279 | Patceg | Aug 2013 | A1 |
20130225282 | Williams et al. | Aug 2013 | A1 |
20130252730 | Joshi | Sep 2013 | A1 |
20130281188 | Guinn | Oct 2013 | A1 |
20130316808 | Nelson | Nov 2013 | A1 |
20130337878 | Shepherd | Dec 2013 | A1 |
20140006129 | Heath | Jan 2014 | A1 |
20140057716 | Massing et al. | Feb 2014 | A1 |
20140087862 | Burke | Mar 2014 | A1 |
20140094295 | Nguyen | Apr 2014 | A1 |
20140094316 | Nguyen | Apr 2014 | A1 |
20140121005 | Nelson | May 2014 | A1 |
20140179431 | Nguyen | Jun 2014 | A1 |
20140274306 | Crawford | Sep 2014 | A1 |
20140274309 | Nguyen | Sep 2014 | A1 |
20140274319 | Nguyen | Sep 2014 | A1 |
20140274320 | Nguyen | Sep 2014 | A1 |
20140274342 | Nguyen | Sep 2014 | A1 |
20140274357 | Nguyen | Sep 2014 | A1 |
20140274360 | Nguyen | Sep 2014 | A1 |
20140274367 | Nguyen | Sep 2014 | A1 |
20140274388 | Nguyen | Sep 2014 | A1 |
20150089595 | Telles | Mar 2015 | A1 |
20150133223 | Carter | May 2015 | A1 |
20150143543 | Phegade | Aug 2015 | A1 |
20160125695 | Nguyen | May 2016 | A1 |
20170016819 | Nguyen | Apr 2017 | A1 |
20170116823 | Nguyen | Apr 2017 | A1 |
20170144071 | Nguyen | May 2017 | A1 |
20170148259 | Nguyen | May 2017 | A1 |
20170148261 | Nguyen | May 2017 | A1 |
20170148263 | Nguyen | May 2017 | A1 |
20170206734 | Nguyen | Jul 2017 | A1 |
20170228979 | Nguyen | Aug 2017 | A1 |
20170337770 | Nguyen | Nov 2017 | A1 |
20180144581 | Nguyen | May 2018 | A1 |
20190005773 | Nguyen | Jan 2019 | A1 |
20190122490 | Nguyen | Apr 2019 | A1 |
20190122492 | Nguyen | Apr 2019 | A1 |
20190213829 | Nguyen | Jul 2019 | A1 |
Number | Date | Country |
---|---|---|
2033638 | May 1980 | GB |
2062923 | May 1981 | GB |
2096376 | Oct 1982 | GB |
2097570 | Nov 1982 | GB |
2335524 | Sep 1999 | GB |
12005000454 | May 2007 | PH |
WO 05073933 | Aug 2005 | WO |
WO 2008027621 | Mar 2008 | WO |
WO 2009026309 | Feb 2009 | WO |
WO 2009062148 | May 2009 | WO |
WO 2010017252 | Feb 2010 | WO |
Entry |
---|
Benston, Liz, “Harrahs Launches iPhone App; Caesars Bypasses Check-in,” Las Vegas Sun, Las Vegas, NV. Jan. 8, 2010. |
Finnegan, Amanda, “Casinos Connecting with Customers via iPhone Apps”, May 27, 2010, Las Vegas Sun, Las Vegas, NV. |
Gaming Today Staff, “Slots showcased at 2009 National Indian Gaming Assoc.”, GamingToday.com, Apr. 14, 2009. |
Green, Marian, “Testing Texting Casino Journal”, Mar. 2, 2009. |
Hasan, Ragib, et al., “A Survey of Peer-to-Peer Storage Techniques for Distributed File Systems”, National Center for Supercomputing Applications, Department of Computer Science, University of Illinois at Urbana Champaign, Jun. 27, 2005. |
Jones, Trahern, “Telecon-equipped drones could revolutionize wireless market”, azcentral.com, http://www.azcentral.com/business/news/articles/20130424telecom-equipped-drones-could-revolutionize-wireless-market.html, downloaded Jul. 2, 2013, 2 pages. |
Yancey, Kitty Bean, “Navigate Around Vegas with New iPhone Apps”, USA Today, Jun. 3, 2010. |
iAPS, Daily Systems LLC, 2010. |
U.S. Appl. No. 12/945,888, filed Nov. 14, 2010. |
U.S. Appl. No. 12/945,889, filed Nov. 14, 2010. |
U.S. Appl. No. 13/622,702, filed Sep. 19, 2012. |
U.S. Appl. No. 13/800,917, filed Mar. 13, 2013. |
U.S. Appl. No. 13/296,182, filed Nov. 15, 2011. |
U.S. Appl. No. 13/801,234, filed Mar. 13, 2013. |
U.S. Appl. No. 13/801,171, filed Mar. 13, 2013. |
U.S. Appl. No. 13/843,192, filed Mar. 15, 2013. |
U.S. Appl. No. 13/843,087, filed Mar. 15, 2013. |
U.S. Appl. No. 13/632,743, filed Oct. 1, 2012. |
U.S. Appl. No. 13/632,828, filed Oct. 1, 2012. |
U.S. Appl. No. 13/833,953, filed Mar. 15, 2013. |
U.S. Appl. No. 12/619,672, filed Nov. 16, 2009. |
U.S. Appl. No. 13/801,121, filed Mar. 13, 2013. |
U.S. Appl. No. 12/581,115, filed Oct. 17, 2009. |
U.S. Appl. No. 13/801,076, filed Mar. 13, 2013. |
U.S. Appl. No. 13/617,717, filed Nov. 12, 2009. |
U.S. Appl. No. 13/633,118, filed Oct. 1, 2012. |
U.S. Appl. No. 12/797,610, filed Jun. 10, 2010. |
U.S. Appl. No. 13/801,256, filed Mar. 13, 2013. |
U.S. Appl. No. 12/757,968, filed Apr. 9, 2010. |
U.S. Appl. No. 12/797,616, filed Jun. 10, 2010. |
U.S. Appl. No. 13/557,063, filed Jul. 24, 2012. |
U.S. Appl. No. 13/833,116, filed Mar. 15, 2013. |
U.S. Appl. No. 13/801,271, filed Mar. 13, 2011. |
Office Action for U.S. Appl. No. 12/945,888 dated Apr. 10, 2012. |
Final Office Action for U.S. Appl. No. 12/945,888 dated Sep. 21, 2012. |
Advisory Action for U.S. Appl. No. 12/945,888 dated Jan. 30, 2013. |
Office Action for U.S. Appl. No. 12/581,115 dated Dec. 20, 2011. |
Final Office Action for U.S. Appl. No. 12/581,115 dated Sep. 13, 2012. |
Notice of Allowance for U.S. Appl. No. 12/581,115 dated May 24, 2013. |
Office Action for U.S. Appl. No. 12/619,672 dated Dec. 20, 2011. |
Final Office Action for U.S. Appl. No. 12/619,672 dated Nov. 6, 2012. |
Office Action for U.S. Appl. No. 12/619,672 dated Mar. 7, 2013. |
Office Action for U.S. Appl. No. 12/617,717 dated Oct. 4, 2011. |
Office Action for U.S. Appl. No. 12/617,717 dated Apr. 4, 2012. |
Advisory Action for U.S. Appl. No. 12/617,717 dated Jun. 12, 2011. |
Office Action for U.S. Appl. No. 12/617,717 dated Jun. 17, 2013. |
Office Action for U.S. Appl. No. 12/797,610 dated Dec. 8, 2011. |
Final Office Action for U.S. Appl. No. 12/797,610 dated Jun. 6, 2012. |
Office Action for U.S. Appl. No. 12/797,610 dated Feb. 26, 2013. |
Office Action for U.S. Appl. No. 12/757,968, dated May 9, 2012. |
Final Office Action for U.S. Appl. No. 12/757,968, dated Nov. 29, 2012. |
Office Action for U.S. Appl. No. 12/757,968, dated Apr. 25, 2013. |
Office Action for U.S. Appl. No. 12/797,616 dated Mar. 15, 2012. |
Final Office Action for U.S. Appl. No. 12/797,616 dated Oct. 13, 2012. |
Office Action for U.S. Appl. No. 12/797,616 dated Feb. 13, 2013. |
Final Office Action for U.S. Appl. No. 12/797,616 dated May 8, 2013. |
Office Action for U.S. Appl. No. 13/296,182 dated Dec. 5, 2012. |
Brochure, 5000 Ft. Inc., 1 page, Nov. 2010. |
Frontier Fortune game, email notification, MGM Resorts Intl., Aug. 9, 2013. |
“Getting Back in the Game: Geolocation Can Ensure Compliance with New iGaming Regulations”, White Paper, Quova, Inc., 2010. |
Notice of Allowance of U.S. Appl. No. 12/619,672, ated Aug. 23, 2013. |
Office Action for U.S. Appl. No. 13/633,118, dated Sep. 20, 2013. |
Office Action for U.S. Appl. No. 13/801,256, dated Jul. 2, 2013. |
Notice of Allowance for U.S. Appl. No. 12/619,672, dated Oct. 3, 2013. |
Notice of Allowance for U.S. Appl. No. 12/757,968, dated Oct. 11, 2013. |
Final Office Action for U.S. Appl. No. 12/797,610, dated Jul. 10, 2013. |
Notice of Allowance for U.S. Appl. No. 12/757,968, dated Dec. 18, 2013. |
Office Action for U.S. Appl. No. 12/945,889, dated Dec. 18, 2013. |
Office Action for U.S. Appl. No. 13/632,828, dated Jul. 30, 2013. |
Restriction Requirement for U.S. Appl. No. 13/801,256, dated Dec. 30, 2013. |
Office Action for U.S. Appl. No. 13/801,171, dated Dec. 26, 2013. |
Office Action for U.S. Appl. No. 13/801,234, dated Jan. 10, 2014. |
Final Office Action for U.S. Appl. No. 13/296,182, dated Feb. 12, 2014. |
Office Action for U.S. Appl. No. 12/617,717, dated Feb. 25, 2014. |
Office Action for U.S. Appl. No. 13/801,076, dated Mar. 28, 2014. |
Final Office Action for U.S. Appl. No. 13/633,118, dated Apr. 3, 2014. |
Office Action for U.S. Appl. No. 13/843,192, dated Apr. 3, 2014. |
Office Action for U.S. Appl. No. 13/632,743, dated Apr. 10, 2014. |
Office Action for U.S. Appl. No. 13/801,121, dated Apr. 11, 2014. |
Final Office Action for U.S. Appl. No. 12/945,889, dated Jun. 30, 2014. |
Notice of Allowance for U.S. Appl. No. 12/617,717, dated Jul. 14, 2014. |
Office Action for U.S. Appl. No. 13/801,121, dated Sep. 24, 2014. |
Office Action for U.S. Appl. No. 13/801,171, dated Sep. 22, 2014. |
Office Action for U.S. Appl. No. 13/801,234, dated Oct. 1, 2014. |
Office Action for U.S. Appl. No. 13/801,271, dated Oct. 31, 2014. |
Final Office Action for U.S. Appl. No. 13/843,192, dated Oct. 21, 2014. |
Office Action for U.S. Appl. No. 13/632,743, dated Oct. 23, 2014. |
Office Action for U.S. Appl. No. 12/945,889, dated Oct. 23, 2014. |
Office Action for U.S. Appl. No. 13/632,828, dated Nov. 7, 2014. |
Office Action for U.S. Appl. No. 12/797,610, dated Dec. 15, 2014. |
Final Office Action for U.S. Appl. No. 12/945,889, dated Feb. 12, 2015. |
Final Office Action for U.S. Appl. No. 13/801,171, dated Mar. 16, 2015. |
Office Action for U.S. Appl. No. 13/833,116, dated Mar. 27, 2015. |
Office Action for U.S. Appl. No. 13/632,828, dated Apr. 10, 2015. |
Final Office Action for U.S. Appl. No. 13/801,121, dated Apr. 21, 2015. |
Final Office Action for U.S. Appl. No. 13/557,063, dated Apr. 28, 2015. |
Office Action for U.S. Appl. No. 13/296,182, dated Jun. 5, 2015. |
Office Action for U.S. Appl. No. 13/843,192, dated Jun. 19, 2015. |
Office Action for U.S. Appl. No. 12/797,610, dated Jul. 14, 2015. |
Final Office Action for U.S. Appl. No. 13/833,953, dated Jul. 17, 2015. |
Notice of Allowance for U.S. Appl. No. 12/945,889, dated Jul. 22, 2015. |
Office Action for U.S. Appl. No. 12/797,616, dated Aug. 10, 2015. |
Final Office Action for U.S. Appl. No. 13/801,234, dated Aug. 14, 2015. |
Final Office Action for U.S. Appl. No. 13/833,116, dated Sep. 24, 2015. |
Office Action for U.S. Appl. No. 13/801,121, dated Oct. 2, 2015. |
Office Action for U.S. Appl. No. 14/017,150, dated Oct. 7, 2015. |
Office Action for U.S. Appl. No. 14/017,159, dated Oct. 7, 2015. |
Office Action for U.S. Appl. No. 13/801,271 dated Oct. 19, 2015. |
Office Action for U.S. Appl. No. 14/211,536 dated Oct. 19, 2015. |
Final Office Action for U.S. Appl. No. 13/632,828, dated Oct. 22, 2015. |
Office Action for U.S. Appl. No. 14/217,066, dated Dec. 17, 2015. |
Notice of Allowance for U.S. Appl. No. 13/557,063, dated Dec. 23, 2015. |
Office Action for U.S. Appl. No. 13/296,182, dated Dec. 23, 2015. |
Final Office Action for U.S. Appl. No. 13/843,192, dated Dec. 30, 2015. |
Office Action for U.S. Appl. No. 13/801,076, dated Jan. 11, 2016. |
Office Action for U.S. Appl. No. 12/945,888, dated Jan. 22, 2016. |
Final Office Action for U.S. Appl. No. 12/797,616, dated Jun. 12, 2016. |
Office Action for U.S. Appl. No. 13/843,087, dated Feb. 25, 2016. |
Office Action for U.S. Appl. No. 13/800,917, dated Feb. 25, 2016. |
Advisory Action for U.S. Appl. No. 13/632,828, dated Feb. 25, 2016. |
Office Action for U.S. Appl. No. 13/801,234, dated Mar. 8, 2016. |
Office Action for U.S. Appl. No. 14/216,986, dated Mar. 9, 2016. |
Final Office Action for U.S. Appl. No. 13/801,271, dated Mar. 11, 2016. |
Office Action for U.S. Appl. No. 13/622,702, dated Mar. 22, 2016. |
Final Office Action for U.S. Appl. No. 13/633,118, dated Mar. 24, 2016. |
Final Office Action for U.S. Appl. No. 14/189,948, dated Apr. 6, 2016. |
Final Office Action for U.S. Appl. No. 12/797,610, dated Apr. 21, 2016. |
Final Office Action for U.S. Appl. No. 14/017,150, dated Apr. 26, 2016. |
Final Office Action for U.S. Appl. No. 13/801,121, dated May 11, 2016. |
Final Office Action for U.S. Appl. No. 14/017,159, dated Jun. 6, 2016. |
Office Action for U.S. Appl. No. 13/801,171, dated Jun. 6, 2016. |
Office Action for U.S. Appl. No. 13/843,192, dated Jun. 9, 2016. |
Final OA for U.S. Appl. No. 12/945,888, dated Jun. 28, 2016. |
Notice of Allowance for U.S. Appl. No. 13/833,953, dated Jul. 6, 2016. |
Final Office Action for U.S. Appl. No. 13/801,171, dated May 21, 2014. |
Final Office Action for U.S. Appl. No. 13/801,234, mailed May 22, 2014. |
Office Action for U.S. Appl. No. 14/211,536, dated Jul. 13, 2016. |
Notice of Allowance for U.S. Appl. No. 13/801,076, dated Jul. 11, 2016. |
Office Action for U.S. Appl. No. 13/296,182, dated Jul. 20, 2016. |
Restriction Requirement for U.S. Appl. No. 13/296,182, dated Oct. 12, 2012. |
Advisory Action for U.S. Appl. No. 13/296,182, dated May 8, 2014. |
Advisory Action for U.S. Appl. No. 13/843,192, dated May 8, 2014. |
Notice of Allowance for U.S. Appl. No. 13843,192, dated Aug. 10, 2016. |
Office Action for U.S. Appl. No. 14/217,066, dated Dec. 22, 2016. |
Final Office Action for U.S. Appl. No. 14/216,986, dated Sep. 23, 2016. |
Office Action for U.S. Appl. No. 14/017,159, dated Sep. 23, 2016. |
Office Action for U.S. Appl. No. 13/632,743, dated Sep. 23, 2016. |
Final Office Action for U.S. Appl. No. 13/801,234, dated Oct. 14, 2016. |
Final Office Action for U.S. Appl. No. 13/843,087, dated Oct. 13, 2016. |
Final Office Action for U.S. Appl. No. 13/622,702, dated Oct. 13, 2016. |
Office Action for U.S. Appl. No. 14/189,948, dated Nov. 7, 2016. |
Final Office Action for U.S. Appl. No. 14/211,536, dated Mar. 14, 2014. |
Notice of Allowance for U.S. Appl. No. 13/833,116, dated Oct. 11, 2016. |
Notice of Allowance for U.S. Appl. No. 13/801,271, dated Dec. 2, 2016. |
Notice of Allowance for U.S. Appl. No. 12/797,610, dated Dec. 7, 2016. |
Notice of Allowance for U.S. Appl. No. 13/632,828, dated Dec. 16, 2016. |
Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 19, 2016. |
Notice of Allowance for U.S. Appl. No. 14/211,536, dated Dec. 28, 2016. |
Notice of Allowance for U.S. Appl. No. 13/801,256, dated Jan. 20, 2017. |
Office Action for U.S. Appl. No. 13/800,917, dated Feb. 3, 2017. |
Final Office Action for U.S. Appl. No. 12/797,616, dated Feb. 10, 2017. |
Office Action for U.S. Appl. No. 12/945,888, dated Feb. 28, 2017. |
Final Office Action for U.S. Appl. No. 14/189,948, dated Mar. 17, 2017. |
Office Action for U.S. Appl. No. 15/400,840, dated Mar. 10, 2017. |
Notice of Allowance for U.S. Appl. No. 13/801,121, dated Mar. 29, 2017. |
Office Action for U.S. Appl. No. 15/270,333, dated Mar. 30, 2017. |
Office Action for U.S. Appl. No. 15/402,945, dated Apr. 5, 2017. |
Office Action for U.S. Appl. No. 15/271,488, dated Apr. 19, 2017. |
Final Office Action for U.S. Appl. No. 14/217,066, dated Apr. 21, 2017. |
Office Action for U.S. Appl. No. 14/216,986 dated Apr. 26, 2017. |
Office Action for U.S. Appl. No. 13/801,171, dated Jun. 14, 2017. |
Office Action for U.S. Appl. No. 14/017,159, dated Jun. 29, 2017. |
Notice of Allowance for U.S. Appl. No. 15/270,333, dated Jul. 5, 2017. |
Final Office Action for U.S. Appl. No. 13/800,917, dated Jul. 13, 2017. |
Notice of Allowance for U.S. Appl. No. 13/801,234, dated Jul. 5, 2017. |
Notice of Allowance for U.S. Appl. No. 14/217,066, dated Jul. 14, 2017. |
Final Office Action for U.S. Appl. No. 14/518,909, dated Jul. 19, 2017. |
Final Office Action for U.S. Appl. No. 13/801,121, dated Sep. 15, 2016. |
Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 17, 2015. |
Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 19, 2016. |
Notice of Allowance for U.S. Appl. No. 15/293,751, dated Aug. 4, 2017. |
Advisory Action for U.S. Appl. No. 14/189,948, dated Jul. 28, 2017. |
Final OA for U.S. Appl. No. 13/801,256, dated Aug. 15, 2014. |
Final OA for U.S. Appl. No. 13/801,256, dated Feb. 18, 2015. |
Advisory Action for U.S. Appl. No. 13/801,256, dated Dec. 5, 2014. |
Office Action for U.S. Appl. No. 13/801,256, dated Jan. 12, 2016. |
Final Office Action for U.S. Appl. No. 13/801,256, dated Aug. 16, 2016. |
Office Action for U.S. Appl. No. 13/622,702, dated Aug. 31, 2017. |
Office Action for U.S. Appl. No. 12/945,888, dated Sep. 1, 2017. |
Office Action for U.S. Appl. No. 14/017,150, dated Sep. 7, 2017. |
Notice of Allowance for U.S. Appl. No. 14/189,948, dated Sep. 13, 2017. |
Office Action for U.S. Appl. No. 15/138,086, dated Oct. 19, 2017. |
Notice of Allowance for U.S. Appl. No. 15/402,945 dated Nov. 21, 2017. |
Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 13, 2017. |
Final Office Action for U.S. Appl. No. 15/271,488, dated Dec. 21, 2017. |
Office Action for U.S. Appl. No. 15/671,133, dated Dec. 22, 2017. |
Final Office Action for U.S. Appl. No. 14/216,986, dated Dec. 26, 2017. |
Restriction Requirement for U.S. Appl. No. 15/427,307, dated Jan. 17, 2018. |
Office Action for U.S. Appl. No. 15/798,363, dated Jan. 26, 2018. |
Office Action for U.S. Appl. No. 15/427,291, dated Jan. 29, 2018. |
Final Office Action for U.S. Appl. No. 14/017,159, dated Feb. 1, 2018. |
Final Office Action for U.S. Appl. No. 13/622,702, dated Feb. 22, 2018. |
Office Action for U.S. Appl. No. 15/811,654, dated Feb. 22, 2018. |
Final Office Action for U.S. Appl. No. 13/622,702, dated Feb. 27, 2018. |
Final Office Action for U.S. Appl. No. 15/427,308, dated Mar. 19, 2018. |
Office Action for U.S. Appl. No. 15/876,095, dated Apr. 3, 2018. |
Office Action for U.S. Appl. No. 15/835,448, dated Apr. 4, 2018. |
Office Action for U.S. Appl. No. 15/427,307, dated Apr. 9, 2018. |
Office Action for U.S. Appl. No. 14/216,986, dated Apr. 6, 2018. |
Office Action for U.S. Appl. No. 15/426,898 dated Apr. 16, 2018. |
Notice of Allowance for U.S. Appl. No. 15/402,945, dated May 25, 2018. |
Office Action for U.S. Appl. No. 15/495,973, dated Jun. 4, 2018. |
Notice of Allowance for U.S. Appl. No. 15/427,291 dated Jun. 18, 2018. |
Notice of Allowance for U.S. Appl. No. 15/271,488, dated Jun. 19, 2018. |
Notice of Allowance for U.S. Appl. No. 15/480,295, dated Jun. 20, 2018. |
Office Action for U.S. Appl. No. 14/963,106, dated Jun. 22, 2018. |
Office Action for U.S. Appl. No. 14/993,055, dated Jun. 22, 2018. |
Final Office Action for U.S. Appl. No. 15/427,307, dated Jul. 9, 2018. |
Notice of Allowance for U.S. Appl. No. 13/633,118, dated Aug. 3, 2018. |
Office Action for U.S. Appl. No. 15/671,133, dated Aug. 9, 2018. |
Office Action for U.S. Appl. No. 15/427,308, dated Aug. 15, 2018. |
Office Action for U.S. Appl. No. 15/798,363, dated Aug. 29, 2018. |
Office Action for U.S. Appl. No. 15/428,922 dated Sep. 17, 2018. |
Office Action for U.S. Appl. No. 15/495,975, dated Sep. 21, 2018. |
Notice of Allowance for U.S. Appl. No. 15/271,488, dated Sep. 24, 2018. |
Notice of Allowance for U.S. Appl. No. 15/876,095, dated Sep. 24, 2018. |
Office Action for U.S. Appl. No. 13/622,702, dated Oct. 3, 2018. |
Office Action for U.S. Appl. No. 15/293,751, dated Apr. 6, 2017. |
Notice of Allowance for U.S. Appl. No. 13/801,171, dated Oct. 31, 2018. |
Final Office Action for U.S. Appl. No. 15/835,448, dated Nov. 2, 2018. |
Final Office Action for U.S. Appl. No. 15/480,295, dated Nov. 7, 2018. |
Final Office Action for U.S. Appl. No. 14/963,106, dated Dec. 14, 2018. |
Final Office Action for U.S. Appl. No. 14/993,055, dated Dec. 14, 2018. |
Office Action for U.S. Appl. No. 16/162,358, dated Dec. 31, 2018. |
Office Action for U.S. Appl. No. 14/017,159, dated Jan. 11, 2019. |
Office Action for U.S. Appl. No. 15/426,898, dated Jan. 11, 2019. |
Final Office Action for U.S. Appl. No. 15/495,973, dated Jan. 11, 2019. |
Office Action for U.S. Appl. No. 14/216,986, dated Jan. 14, 2019. |
Office Action for U.S. Appl. No. 15/427,307, dated Jan. 18, 2019. |
Final Office Action for U.S. Appl. No. 15/798,363, dated Feb. 4, 2019. |
Office Action for U.S. Appl. No. 16/125,614, dated Feb. 25, 2019. |
Final Office Action for U.S. Appl. No. 15/495,975, dated Apr. 18, 2019. |
Office Action for U.S. Appl. No. 15/671,133, dated May 1, 2019. |
Notice of Allowance for U.S. Appl. No. 14/216,986, dated May 17, 2019. |
Notice of Allowance for U.S. Appl. No. 14/518,909, dated May 17, 2019. |
Office Action for U.S. Appl. No. 12/797,616, dated Jun. 5, 2019. |
Office Action for U.S. Appl. No. 15/427,308, dated Jun. 14, 2019. |
Office Action for U.S. Appl. No. 15/811,654, dated Jun. 14, 2019. |
Office Action for U.S. Appl. No. 15/674,480, dated Jun. 20, 2019. |
Notice of Allowance for U.S. Appl. No. 15/835,448, dated Jul. 3, 2019. |
Final Office Action for U.S. Appl. No. 16/162,358, dated Jul. 11, 2019. |
Office Action for U.S. Appl. No. 16/190,050, dated Sep. 19, 2019. |
Office Action for U.S. Appl. No. 14/017,150, dated Oct. 9, 2019. |
Final Office Action for U.S. Appl. No. 15/671,133, dated Oct. 18, 2019. |
Office Action for U.S. Appl. No. 15/835,448 dated Oct. 12, 2019. |
Notice of Allowance for U.S. Appl. No. 15/495,975, dated Oct. 23, 2019. |
Notice of Allowance for U.S. Appl. No. 14/993,005, dated Nov. 27, 2019. |
Final Office Action for U.S. Appl. No. 15/427,308, dated Nov. 27, 2019. |
Office Action for U.S. Appl. No. 15/798,363, dated Jan. 8, 2020. |
Office Action for U.S. Appl. No. 15/835,448, dated Mar. 5, 2020. |
Office Action for U.S. Appl. No. 15/495,975, dated Mar. 17, 2020. |
Office Action for U.S. Appl. No. 16/248,759, dated Apr. 1, 2020. |
Number | Date | Country | |
---|---|---|---|
20190108726 A1 | Apr 2019 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15876095 | Jan 2018 | US |
Child | 16214123 | US | |
Parent | 15400840 | Jan 2017 | US |
Child | 15876095 | US | |
Parent | 13833116 | Mar 2013 | US |
Child | 15400840 | US |