Gaming device docking station for authorized game play

Information

  • Patent Grant
  • 10755523
  • Patent Number
    10,755,523
  • Date Filed
    Monday, October 30, 2017
    7 years ago
  • Date Issued
    Tuesday, August 25, 2020
    4 years ago
Abstract
In one embodiment, a system to authorize a mobile electronic device to play games of chance includes a gaming system manager and a docking station, The docking station can be configured to: (i) detect whether the mobile electronic device is connected to a receiver of the docking station; (ii) receive device information from the mobile electronic device if it is detected that the mobile electronic device is connected to the receiver; (iii) determine whether a game of chance can be played on the mobile electronic device based on the received device information; (iv) authorize the mobile electronic device to play the game of chance; and (v) transmit gaming data to the mobile electronic device if it is determined that the game of chance can be played on the mobile electronic device and if the mobile electronic device is authorized.
Description
BACKGROUND OF THE INVENTION

It is often the case that people go with friends to gaming establishments for the purpose of being social and enjoying playing games of chance in one another's company. However, more than likely, at least one person in the group will disagree in which activities to engage in. In gaming establishments, one person may want to play video poker while another would want to play a game of craps. Several other people in the group may even want to play different slot machines. This can be particularly troublesome when the purpose of the excursion is to be social, yet the people separate in order to engage in their respective preferred activities.


There may be times when at least one person in the group is disappointed with the activity in which the group is engaged in, and it is likely that significant compromises must be made in order to accommodate all members of a group. This can lead to people spending less money in a gaming establishment by reducing the desire to engage in the current activity for at least one person in the group and/or by quickly taxing the overall patience of the group which would otherwise be willing to engage in gaming activities for longer periods of time. It may be preferable to allow at least one or more of the group members to play their preferred game of chance on a mobile or portable gaming device in order to prevent such issues.


SUMMARY

The present invention relates to docking stations, such as docking stations configured for use in gaming establishments. The docking stations can be configured to create trusted mobile electronic devices which can be used to play games of chance in gaming establishments.


In one embodiment, a docking station configured to authorize a mobile electronic device to play games of chance may have a receiver configured to receive the mobile electronic device, and a processor configured to: (i) detect whether the mobile electronic device has been received by the receiver; (ii) receive device information from the mobile electronic device if it is detected that the mobile electronic device is received by the receiver; (iii) determine whether the games of chance can be played on the mobile electronic device based on the received device information; (iv) authorize the mobile electronic device to play the games of chance; and (v) transmit gaming data to the mobile electronic device if it is determined that the games of chance can be played on the mobile electronic device and if the mobile electronic device is authorized.


In one embodiment, a method for authorizing a mobile electronic device to play games of chance using a docking station may include detecting that the mobile electronic device is coupled to the portable docking station, receiving device information from the mobile electronic device after it is detected that the mobile electronic device has been coupled to the portable docking station, determining whether the games of chance can be played on the mobile electronic device based on the received device information, authorizing the mobile electronic device for playing the games of chance, and transmitting gaming data to the mobile electronic device if it is determined that the games of chance can be played on the mobile electronic device and if the mobile electronic device is authorized.


In another embodiment, a method for converting a mobile electronic device to a trusted mobile electronic device using a portable docking station may include detecting that the mobile electronic device is coupled to the portable docking station, receiving device information from the mobile electronic device after it is detected that the mobile electronic device has been coupled to the portable docking station, determining whether games of chance can be played on the mobile electronic device based on the received device information, authorizing a user to play the games of chance on the mobile electronic device, converting the mobile electronic device to the trusted mobile electronic device if the user is authorized to play the games of chance on the mobile electronic device, and transmitting gaming data to the trusted mobile electronic device if the mobile electronic device is converted to a trusted mobile electronic device.


In one embodiment, a system to authorize a mobile electronic device to play games of chance may include a gaming system manager and a portable docking station configured to communicate with the gaming system manager and the mobile electronic device, the portable docking station further configured to: (i) detect whether the mobile electronic device is connected to a receiver of the portable docking station; (ii) receive device information from the mobile electronic device if it is detected that the mobile electronic device is connected to the receiver; (iii) determine whether the games of chance can be played on the mobile electronic device based on the received device information; (iv) authorize the mobile electronic device to play the games of chance; and (v) transmit gaming data to the mobile electronic device if it is determined that the games of chance can be played on the mobile electronic device and if the mobile electronic device is authorized, wherein once the mobile electronic device is authorized to play the games of chance, the mobile electronic device is deemed a trusted gaming device for use within the gaming system manager of a gaming establishment.





BRIEF DESCRIPTION OF THE DRAWINGS

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:



FIG. 1 illustrates a block diagram of an example system to authorize a portable electronic device to play games of chance.



FIG. 2 illustrates a flowchart of an example method for authorizing a mobile electronic device to play games of chance using a docking station.



FIGS. 3A-3B illustrate flowcharts of an example method for converting a mobile electronic device to a trusted mobile electronic device using a docking station.



FIG. 4 illustrates a flowchart of an example method for authorizing a mobile electronic device using a docking station.



FIG. 5 illustrates an example docking station.



FIG. 6 illustrates a block diagram of an example docking station.



FIGS. 7A-7B illustrate an example authorization of a mobile electronic device to play a game of chance.



FIGS. 8A-8B illustrate an example use of a docking station.



FIGS. 9A-9B illustrate another example use of a document station.



FIGS. 10A-10B illustrate still another example use of a docking station.



FIGS. 11A-11D Illustrate yet another example use of the docking station.





DESCRIPTION OF EXAMPLE EMBODIMENTS

Embodiments are described herein in the context of a gaming device docking station. 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.


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 may be used to carry out the invention. 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 gaming device docking station, or other hardware and/or software stored in a machine-readable medium (e.g., a tangible storage medium), can perform associated methods or processes. These and other features will be presented in more detail in the following the description of the invention and the associated figures.



FIG. 1 illustrates a block diagram of an example system to authorize a portable electronic device to play games of chance. The system 100 may have a gaming server 102, a gaming system manager 104, a network 106, a plurality of docking stations 108a-n (where n is an integer), and a plurality of mobile or portable electronic devices 110a-n.


Mobile electronic devices 110a-n may be any portable electronic device such as mobile telephones, tablet computers, laptop computers, handheld gaming devices, media players, or any other mobile electronic device having the capability to play a game of chance.


The docking station 108a-n may be configured to receive and/or detect whether the mobile electronic device 110a-n is connected to the docking station 108a-n. In one embodiment, the docking station 108a-n may have a receiver configured to physically receive the mobile electronic device 110a-n. In another embodiment, the mobile electronic device may be detected by the docking station via any wired or wireless means. For example, an external connector or dongle may be used to connect or couple the docking stations 108a-n and the mobile electronic device 110a-n. In another example, the mobile electronic device 110a-n may be detected by the docking station 108a-n via any known wireless methods or device such as a 3G wireless technology, 4G wireless technology, Bluetooth, Wireless USB, Near-field magnetic, Fire Wire, WiMax, IEEE 802.11x technology, radio frequency, and the like. Detection of the mobile electronic device 110a-n may be initiated by a graphical user interface on the docking station 108a-n or the mobile electronic device 110a-n.


Once the mobile electronic device 110a-n is detected by the docking station 108a-n, mobile device information may be transmitted from the mobile electronic device 110a-n to the docking station 108a-n. Mobile device information may be any information necessary to determine whether the mobile device has the capability to play games of chance, authenticate the mobile electronic device 110a-n, validate or authenticate the user of the mobile electronic device 110a-n, or any other desired information may be transmitted to the docking station 108a-n. For example, mobile device information may include the mobile electronic device 110a-n capabilities such as power capacity, display resolution, memory capacity, processor capacity, disk space, software versions, and the like. Mobile device information may also include identification information such as model information, user information, user preferences, game history, bookmarks for specific games of chance, favorite websites and/or games of chance, favorite meals, shows, buffets, and the like. The mobile device information may allow the gaming establishment to determine the user interests. Knowing the user's interests may allow the gaming establishment to transmit any marketing, promotions, coupons, and the like to the mobile electronic device. For example, if a user's interest is playing poker games on the mobile electronic device, the user may be notified of a poker tournament at the gaming establishment. In another example, the user may show an interest in gourmet food. The gaming establishment may transmit, to the mobile electronic device, a coupon for 50% off at their steak house.


The docking station 108a-n may be configured to determine whether games of chance can be played on the mobile electronic device 110a-n based on the received mobile device information. For example, the docking station 108a-n may determine whether the mobile electronic device 110a-n is compatible with software residing of the docking station 108a-n, the gaming system manager 104, or the gaming server 102 in order to play the game of chance. The docking station 108a-n may also be configured to determine whether the mobile electronic device 110a-n has enough memory to play the games of chance.


In one embodiment, if the mobile electronic device 110a-n is physically connected to docking station 108a-n either wired, by a connector, or received by the receiver of the docking station 108a-n, docking station 108a-n may be configured to provide a charge to the mobile electronic device 110a-n. In another embodiment, if the mobile electronic device 110a-n is physically connected to docking station 108a-n wirelessly, the charge to the mobile electronic device 110a-n may be transmitted via electromagnetic induction or any other similar methods used to provide charges wirelessly.


Docking station 108a-n may be configured to authenticate the mobile electronic device 110a-n to play games of chance based upon the received mobile device information. In one embodiment, using a user interface either on the docking station 108a-n and/or on the mobile electronic device 110a-n, the user may be requested to enter a username, password, account number, player tracking information, facial recognition information, voice recognition information, or any other desired user information. In another embodiment, the desired user information necessary to authenticate the mobile electronic device 110a-n and/or user may be embedded in the mobile electronic device 110a-n such that authentication may be completed automatically without any user interaction.


To authenticate the mobile electronic device and the user, the received mobile device information may be compared to information stored on the gaming system manager 104. The docking station 108a-n may be configured to communicate with the gaming system manager 104 by any known means such as wired or wirelessly. The gaming system manager 104 may have a player tracking server 103 having a player database 105 configured to store all user information, player tracking information, and any other desired player information. If the received mobile electronic information matches the information stored in the player tracking server 103, the docking station 108a-n may authenticate the mobile electronic device 110a-n such that the mobile electronic device 110a-n then becomes a trusted gaming electronic device.


In one embodiment, the comparison of the received mobile device information and the information stored on the player tracking server 103 may be conducted at the docking station 108a-n. In this embodiment, the docking station 108a-n may be configured to receive the player tracking information from the gaming system manager 104. In another embodiment, the comparison of the received mobile device information and the information stored on the player tracking server 103 may be conducted by the gaming system manager 104. In this embodiment, the docking station 108a-n may be configured to transmit the received mobile device information to the gaming system manager 104 for comparison. If the information match, the gaming system manager 104 may transmit an authentication signal to the docking station 108a-n. If the information does not match, the gaming system manager 104 may transmit a rejection signal to the docking station 108a-n.


Once authenticated, the docking station 108a-n may receive a request to play a game of chance from the mobile electronic device 110a-n. If the docking station 108a-n determined that the mobile electronic device 110a-n is capable of playing games of chance, in one embodiment, the docking station 108a-n may transmit the request for the game of chance to the gaming system manager 104. The requested game of chance data may be obtained from the gaming server 102 and transmitted to the mobile electronic device 110a-n. In another embodiment, the docking station 108a-n may determine whether the requested game of chance is stored on the docking station 108a-n. If the docking station 108a-n determined that the requested game of chance is stored on the docking station 108a-n, the docking station 108a-n may transmit the requested game of chance data to the mobile electronic device 110a-n.


The game of chance data may be downloaded and stored on the mobile electronic device 110a-n. In another embodiment, the game of chance data may be streamed to the mobile electronic device 110a-n, either from the docking station 108a-n or the gaming system manager 104. In this embodiment, user input used to play the game of chance may be transmitted to the docking station 108a-n or the gaming system manager 104. User input may be received from the mobile electronic device 110a-n and/or the docking station 108a-n.


As the game of chance is played, game session data may periodically transmitted to the docking station 108a-n. Game session data may be transmitted at any desired time. For example, game session data may be transmitted every thirty seconds, every minute, every fifteen minutes, every hour, or at designated time intervals such as between 1 pm-3 pm, and the like. In one embodiment, game session data may be stored at the docking station 108a-n. In another embodiment, the game session data may be received by the docking station 108a-n and transmitted to the gaming system manager 104. In still another embodiment, the game session data may be directly received by the gaming system manager 104 from the mobile electronic device 110a-n. Game session data may include any data produced during the game play such as game state data, game history data, account data, coins in and out, credits obtained or used, bonuses received, and any other game data. Game session data may be used in case of a power failure by the docking station or mobile electronic device, malfunction of the docking station or mobile electronic device, or any other reasons. The game session data may be used recreate the gaming sessions to determine if the player won or lost, the amount of credits remaining, if the player was cheating, or any other game session information.


Since a player may want to move about the gaming establishment (e.g. to see a show, eat dinner, watch their friends play at a table game or other gaming machine, etc.) the mobile electronic device 110a-n may be automatically authenticated or received at another docking station 108a-n located near the player. For example, if the player was originally authenticated by a docking station 108a-n located at the bar and is now eating dinner at the buffet, the mobile electronic device 110a-n may be automatically authenticated by a docking station located nearest the buffet. Thus, once a mobile electronic device 110a-n has been authenticated by one docking station 108a-n, the mobile electronic device 110a-n is now deemed a trusted gaming device and may be automatically authenticated when connecting to another docking station 108a-n within the gaming establishment.


The mobile electronic device 110a-n may be configured to communicate with the second docking station 108a-n similar to how it was configured to communicate with the original docking station 108a-n (i.e. wirelessly, wired, physically received in a receiver, and/or use of an external connector). The second docking station 108a-n may also be configured to receive mobile device information from the mobile electronic device 110a-n, transmit the received mobile device information to the gaming system manager 104, transmit and receive gaming session data, and any other desired operations. The second docking station 108a-n and/or gaming system manager 104 may determine whether the mobile electronic device 110a-n was previously connected to another portable docking station 108a-n within the gaming establishment based upon the received mobile device information.



FIG. 2 illustrates a flowchart of an example method for authorizing a mobile electronic device to play games of chance using a docking station. A mobile electronic device must be authorized, authenticated, and/or validated by a docking station prior to becoming a trusted device that may be used to play games of chance. Mobile electronic devices may be any portable electronic device such as mobile telephones, tablet computers, laptop computers, handheld gaming devices, media players, or any other mobile electronic device having the capability to play a game of chance.


Method 200 starts with detecting a mobile electronic device at 202. The docking station (e.g. docking station 108a-n illustrated in FIG. 1) may be configured to receive and/or detect whether the mobile electronic device is connected to the docking station. In one embodiment, the docking station may have a receiver configured to physically receive the mobile electronic device. In another embodiment, the mobile electronic device may be detected by the docking station via any wired or wireless means. For example, an external connector or dongle may be used to connect or couple the docking stations and the mobile electronic device. In another example, the mobile electronic device may be detected by the docking station via any known wireless methods or device such as a 3G wireless technology, 4G wireless technology, Bluetooth, Wireless USB, Near-field magnetic, Fire Wire, WiMax, IEEE 802.11x technology, radio frequency, and the like. Detection of the mobile electronic device may be initiated by a graphical user interface on the docking station or the mobile electronic device.


Device information may be obtained from the mobile electronic device at 204. Mobile device information may be any information necessary to determine whether the mobile device has the capability to play games of chance, authenticate the mobile electronic device, validate or authenticate the user of the mobile electronic device, or any other desired information may be transmitted to the docking station. For example, mobile device information may include the mobile electronic device capabilities such as power capacity, display resolution, memory capacity, processor capacity, disk space, software versions, and the like. Mobile device information may also include identification information such as model information, user information, user preferences, game history, bookmarks for specific games of chance, favorite websites and/or games of chance, favorite meals, shows, buffets, and the like. The mobile device information may allow the gaming establishment to determine the user interests. Knowing the user's interests may allow the gaming establishment to transmit any marketing, promotions, coupons, and the like to the mobile electronic device. For example, if a user's interest is playing poker games on the mobile electronic device, the user may be notified of a poker tournament at the gaming establishment. In another example, the user may show an interest in gourmet food. The gaming establishment may transmit, to the mobile electronic device, a coupon for 50% off at their steak house.


A determination of whether the mobile electronic device is acceptable may be made at 206. In other words, a determination of whether games of chance can be played on the mobile electronic device based on the received mobile device information. The docking station can determine whether the mobile electronic device is acceptable in terms of its technical specifications to play games of chance based on the mobile device information provided by the mobile electronic device. For example, the docking station and/or gaming system manager (e.g. gaming system manager 104 illustrated in FIG. 1) may determine whether the mobile electronic device is compatible with software residing of the docking station, the gaming system manager, or the gaming server (e.g. gaming server 102 illustrated in FIG. 1) in order to play the game of chance. The docking station may also be configured to determine whether the mobile electronic device has enough memory to play the games of chance. In another example, a game of chance may require that a mobile electronic device run a Macintosh operating system, have at least two gigabytes of memory, and have at least four hundred seventy kilobytes of drive space free. If the mobile electronic device cannot satisfy those requirements, the mobile electronic device may not be allowed to play games of chance and thus, not be an acceptable mobile electronic device.


If the mobile electronic device is determined to be an acceptable device at 206 a determination of whether the mobile electronic device is currently authenticated may be made at 208. The mobile electronic device may have been previously authenticated by another docking station within the gaming establishment. Since a player may want to move about the gaming establishment (e.g. to see a show, eat dinner, watch their friends play at a table game or other gaming machine, etc.) the mobile electronic device may be automatically authenticated or received at a second docking station located near the player. For example, if the player was originally authenticated by a docking station located at the bar and is now eating dinner at the buffet, the mobile electronic device may be automatically authenticated by a docking station located nearest the buffet. Thus, once a mobile electronic device has been authenticated by one docking station, the mobile electronic device is now deemed a trusted gaming device and may be automatically authenticated when connecting to another docking station within the gaming establishment.


The mobile electronic device may be configured to communicate with the second docking station similar to how it was configured to communicate with the original docking station (i.e. wirelessly, wired, physically received in a receiver, and/or use of an external connector). The second docking station may also be configured to receive mobile device information from the mobile electronic device, transmit the received mobile device information to the gaming system manager, transmit and receive gaming session data, and any other desired operations. The second docking station and/or gaming system manager may determine whether the mobile electronic device was previously connected to another portable docking station within the gaming establishment based upon the received mobile device information.


If the mobile electronic device is determined to be currently authenticated at 208, a gaming session may be created for the mobile electronic device at 214 at the second docking station. If the mobile electronic device is determined to not be currently authenticated at 208, the mobile electronic device may be authenticated at 210.


Docking station may be configured to authenticate the mobile electronic device to play games of chance based upon the received mobile device information. In one embodiment, using a user interface either on the docking station and/or on the mobile electronic device, the user may be requested to enter a username, password, account number, player tracking information, facial recognition information, voice recognition information, or any other desired user information. In another embodiment, the desired user information necessary to authenticate the mobile electronic device and/or user may be embedded in the mobile electronic device such that authentication may be completed automatically without any user interaction.


To authenticate the mobile electronic device and the user, the received mobile device information may be compared to information stored on the gaming system manager. The docking station may be configured to communicate with the gaming system manager by any known means such as wired or wirelessly. The gaming system manager may have a player tracking server (e.g. player tracking server 103 illustrated in FIG. 1) having a player database configured to store all user information, player tracking information, and any other desired player information. A determination of whether the mobile electronic device is authenticated may be made at 211. If the received mobile electronic information matches the information stored in the player tracking server, the docking station may authenticate the mobile electronic device at 211 such that the mobile electronic device then becomes a trusted gaming electronic device that may be used to play games of chance. If the received mobile electronic information does not match the information stored in the player tracking server, the docking station may not authenticate the mobile electronic device at 211 and the method 200 may end.


In one embodiment, the comparison of the received mobile device information and the information stored on the player tracking server may be conducted at the docking station. In this embodiment, the docking station may be configured to receive the player tracking information from the gaming system manager. In another embodiment, the comparison of the received mobile device information and the information stored on the player tracking server may be conducted by the gaming system manager. In this embodiment, the docking station may be configured to transmit the received mobile device information to the gaming system manager for comparison. A determination of whether the mobile electronic device is authenticated may be made at 211. If the information matches, the gaming system manager may transmit an authentication signal to the docking station and the mobile electronic device may be authenticated at 211. If the information does not match, the gaming system manager may transmit a rejection signal to the docking station and the mobile electronic device may not be authenticated at 211 and the method 200 may end.


If the mobile electronic device is authenticated at 211, docking station may configure the mobile electronic device to play the games of chance at 212. In one example, space in the memory of the mobile electronic device may be dedicated for use to play the game of chance. In another example, secure software to prevent cheating, hacking, and/or to comply with any gaming regulations or laws may be required to be downloaded to the mobile electronic device.


A gaming session may then be created for the mobile electronic device at 214. For example, creating a gaming session may include creating a player tracking account, if no player traction account was created for the user. In another example, creating a gaming session may include creating an account for the mobile electronic device to save and store game session data. The game session data stored in the gaming database may include game state data, game history data, account data, and the like. Game state data may show a position in a game, game progress, a current account balance, active bets placed, pending game outcomes, and the like. The game history data may include games of chance played, wagers made, past account balances, game progress, outcomes of games of chance, and the like. Game session data may be used in case of a power failure by the docking station or mobile electronic device, malfunction of the docking station or mobile electronic device, or any other reasons. The game session data may be used recreate the gaming sessions to determine if the player won or lost, the amount of credits remaining, if the player was cheating, or any other game session information.


In still another example, creating the gaming session may include transmitting a list of the games of chance, establishing a link to a player tracking account, and any other desired actions to create a gaming session. The list of games of chance may be customized based upon the user interests, randomly provided, include a summary of each game of chance, and any other information about each of the games of chance. The list of the games of chance may be presented on either the mobile electronic device or the docking station.


Creating the gaming session may also allow the user to easily access and transfer funds to play the game of chance and/or cash out the remaining funds in the gaming session. For example, the gaming session may store the amount of funds received and remaining for the gaming session.


In one embodiment, the funds stored in the gaming session may be used to play the games of chance. In another embodiment, the funds stored in the gaming session may be used for non-gaming purposes, such as paying for a hotel stay, watch a movie, eat at the buffet, play bowling, and any other purchases.


At least one game of chance may be selected at 216. Using the mobile electronic device and/or the docking station, the player may select a game of chance to play. If selected using the mobile electronic device, a request for the selected game of chance may be received by the docking station at 217. If selected using the docking station, a request for the selected game of chance may be received by to the gaming system manager at 217.


The requested game of chance may be transmitted to the mobile electronic device at 218. The requested game of chance data may be obtained from the gaming server and transmitted to the mobile electronic device. In another embodiment, the docking station may determine whether the requested game of chance is stored on the docking station. If the docking station determines that the requested game of chance is stored on the docking station, the docking station may transmit the requested game of chance data to the mobile electronic device.


The game of chance data may be downloaded and stored on the mobile electronic device. In another embodiment, the game of chance data may be streamed to the mobile electronic device, either from the docking station or the gaming system manager. In this embodiment, user input used to play the game of chance may be transmitted to the docking station or the gaming system manager. User input may be received from the mobile electronic device and/or the docking station.



FIGS. 3A-3B illustrate flowcharts of an example method for converting a mobile electronic device to a trusted mobile electronic device using a docking station. As illustrated in FIG. 3A, the method 300 may start with detecting a mobile electronic device at 302. A mobile electronic device must be authorized, authenticated, and/or validated by a docking station in order to become a trusted device capable of being used to play games of chance. Mobile electronic devices may be any portable electronic device such as mobile telephones, tablet computers, laptop computers, handheld gaming devices, media players, or any other mobile electronic device having the capability to play a game of chance.


Method 300 starts with detecting a mobile electronic device at 302. The docking station (e.g. docking station 108a-n illustrated in FIG. 1) may be configured to receive and/or detect whether the mobile electronic device is connected to the docking station. In one embodiment, the docking station may have a receiver configured to physically receive the mobile electronic device. In another embodiment, the mobile electronic device may be detected by the docking station via any wired or wireless means. For example, an external connector or dongle may be used to connect or couple the docking stations and the mobile electronic device. In another example, the mobile electronic device may be detected by the docking station via any known wireless methods or device such as a 3G wireless technology, 4G wireless technology, Bluetooth, Wireless USB, Near-field magnetic, Fire Wire, WiMax, IEEE 802.11x technology, radio frequency, and the like. Detection of the mobile electronic device may be initiated by a graphical user interface on the docking station or the mobile electronic device.


Mobile device information may be obtained from the mobile electronic device at 304. Mobile device information may be any information necessary to determine whether the mobile device has the capability to play games of chance, authenticate the mobile electronic device, validate or authenticate the user of the mobile electronic device, or any other desired information may be transmitted to the docking station. For example, mobile device information may include the mobile electronic device capabilities such as power capacity, display resolution, memory capacity, processor capacity, disk space, software versions, and the like. Mobile device information may also include identification information such as model information, user information, user preferences, game history, bookmarks for specific games of chance, favorite websites and/or games of chance, favorite meals, shows, buffets, and the like. The mobile device information may allow the gaming establishment to determine the user interests. Knowing the user's interests may allow the gaming establishment to transmit any marketing, promotions, coupons, and the like to the mobile electronic device. For example, if a user's interest is playing poker games on the mobile electronic device, the user may be notified of a poker tournament at the gaming establishment. In another example, the user may show an interest in gourmet food. The gaming establishment may transmit, to the mobile electronic device, a coupon for 50% off at their steak house.


A determination of whether the mobile electronic device is acceptable may be made at 306. In other words, a determination of whether games of chance can be played on the mobile electronic device based on the received mobile device information. The docking station can determine whether the mobile electronic device is acceptable in terms of its technical specifications to play games of chance based on the mobile device information provided by the mobile electronic device. For example, the docking station and/or gaming system manager (e.g. gaming system manager 104 illustrated in FIG. 1) may determine whether the mobile electronic device is compatible with software residing of the docking station, the gaming system manager, or the gaming server (e.g. gaming server 102 illustrated in FIG. 1) in order to play the game of chance. The docking station may also be configured to determine whether the mobile electronic device has enough memory to play the games of chance. In another example, a game of chance may require that a mobile electronic device run a Macintosh operating system, have at least two gigabytes of memory, and have at least four hundred seventy kilobytes of drive space free. If the mobile electronic device cannot satisfy those requirements, the mobile electronic device may not be allowed to play games of chance and thus, not be an acceptable mobile electronic device.


If the mobile electronic device is determined to be an acceptable device at 306 a determination of whether the mobile electronic device is currently authenticated may be made at 308. The mobile electronic device may have been previously authenticated by another docking station within the gaming establishment. Since a player may want to move about the gaming establishment (e.g. to see a show, eat dinner, watch their friends play at a table game or other gaming machine, etc.) the mobile electronic device may be automatically authenticated or received at a second docking station located near the player. For example, if the player was originally authenticated by a docking station located at the bar and is now eating dinner at the buffet, the mobile electronic device may be automatically authenticated by a docking station located nearest the buffet. Thus, once a mobile electronic device has been authenticated by one docking station, the mobile electronic device is now deemed a trusted gaming device and may be automatically authenticated when connecting to another docking station within the gaming establishment.


The mobile electronic device may be configured to communicate with the second docking station similar to how it was configured to communicate with the original docking station (i.e. wirelessly, wired, physically received in a receiver, and/or use of an external connector). The second docking station may also be configured to receive mobile device information from the mobile electronic device, transmit the received mobile device information to the gaming system manager, transmit and receive gaming session data, and any other desired operations. The second docking station and/or gaming system manager may determine whether the mobile electronic device was previously connected to another portable docking station within the gaming establishment based upon the received mobile device information.


A determination of whether the mobile electronic device is authenticated may be made at 310. Docking station may be configured to authenticate the mobile electronic device to play games of chance based upon the received mobile device information. In one embodiment, using a user interface either on the docking station and/or on the mobile electronic device, the user may be requested to enter a username, password, account number, player tracking information, facial recognition information, voice recognition information, or any other desired user information. In another embodiment, the desired user information necessary to authenticate the mobile electronic device and/or user may be embedded in the mobile electronic device such that authentication may be completed automatically without any user interaction.


To authenticate the mobile electronic device and the user, the received mobile device information may be compared to information stored on the gaming system manager. The docking station may be configured to communicate with the gaming system manager by any known means such as wired or wirelessly. The gaming system manager may have a player tracking server (e.g. player tracking server 103 illustrated in FIG. 1) having a player database configured to store all user information, player tracking information, and any other desired player information. If the received mobile electronic information matches the information stored in the player tracking server, the docking station may determine that the mobile electronic device is authenticated at 310. If the received mobile electronic information does not match the information stored in the player tracking server, the mobile electronic device is not authenticated at 310 and the method 300 may end.


In one embodiment, the comparison of the received mobile device information and the information stored on the player tracking server may be conducted at the docking station. In this embodiment, the docking station may be configured to receive the player tracking information from the gaming system manager. In another embodiment, the comparison of the received mobile device information and the information stored on the player tracking server may be conducted by the gaming system manager. In this embodiment, the docking station may be configured to transmit the received mobile device information to the gaming system manager for comparison. If the information matches, the gaming system manager may transmit an authentication signal to the docking station and a determination of whether the mobile electronic device is a trusted device may be made at 312. If the information does not match, the gaming system manager may transmit a rejection signal to the docking station and the method 300 may end.


In order to become a trusted device, the mobile electronic device must be authenticated and secured. Thus, if the mobile electronic device is determined to be authenticated at 310, a determination of whether the mobile electronic device is trusted may be made at 312. To be configured to play games of chance, the mobile electronic device must provide for security features to prevent cheating, hacking, and/or to comply with any gaming regulations or laws. In one embodiment, the security features may deny access to all programs or applications on the mobile electronic device except the programs or applications necessary to play the game of chance. If the mobile electronic device contains the desired security features, the mobile electronic device may be considered a trusted device at 312.


If the desired security features are not located on the mobile electronic device, the device is deemed to not be a trusted device at 312. If not a trusted device at 312, the mobile electronic device may be converted to a trusted mobile electronic device at 314. The docking station and/or the gaming system manager may determine what secure software and/or applications are necessary for the mobile electronic device to have to become a trusted device. The secure software may then be downloaded to the mobile electronic device. Once the secured software and/or applications are downloaded and saved to the mobile electronic device, the mobile electronic device may be converted to a trusted device at 314.


If the mobile electronic device is already trusted, the docking station may create a gaming session for the trusted mobile electronic device at 316. For example, creating a gaming session may include creating a player tracking account, if the player did not have an existing player tracking account. In another example, creating a gaming session may include creating an account for the mobile electronic device to save and store game session data. The game session data stored in the gaming database may include game state data, game history data, account data, and the like. Game session data may be used in case of a power failure by the docking station or mobile electronic device, malfunction of the docking station or mobile electronic device, or any other reasons. The game session data may be used recreate the gaming sessions to determine if the player won or lost, the amount of credits remaining, if the player was cheating, or any other game session information.


Game state data may show a position in a game, game progress, a current account balance, active bets placed, pending game outcomes, and the like. The game history data may include games of chance played, wagers made, past account balances, game progress, outcomes of games of chance, and the like. In still another example, creating the gaming session may include transmitting a list of the games of chance that may be played on the mobile electronic device, establishing a link to a player tracking account, and any other desired actions to create a gaming session. The list of games of chance may be customized based upon the user interests, randomly provided, include a summary of each game of chance, and any other information about each of the games of chance. The list of the games of chance may be presented on either the mobile electronic device or the docking station.


A request for a fund transfer may be received at 318 by the docking station. The fund transfer amount may include a fund amount, the amount requested to be transferred and used to play the game of chance, and a fund account. The fund account may be a bank, the gaming establishment where the player has a player tracking account, or any other fund account or source from where the fund amount may be obtained. The fund amount may also be used for non-gaming purposes, such as purchasing drinks, paying for a hotel stay, and the like. The fund amount may be monetary or non-monetary, such as credits, player tracking points, and the like.


In one embodiment, the docking station may transmit the fund transfer request to the fund account. In another embodiment, the docking station may transmit the fund transfer request to the gaming management server. The gaming management server may then transmit the fund transfer request to the fund account.


A determination of whether funds were transferred may be made at 320. If the docking station receives the fund amount, the fund amount may be saved to a player account at 322. The player account may be the player's tracking account, the gaming session account, or any other player account. If no fund amount was received at the docking station, the method 300 may end. The docking station may not receive the fund amount for various reasons such as an insufficient account balance, the player leaves the gaming establishment prior to the transfer of funds, the mobile electronic device is no longer a trusted device, the player using the mobile electronic device is underage, the mobile electronic device is incapable of playing games of chance, the request fund amount is prohibited by law, the player has already requested the maximum amount allowed by law, the mobile electronic device has a low battery charge, or any other reasons.


Having created the gaming session at 316, the user may easily access and transfer funds to play the game of chance and/or cash out the remaining funds in the gaming session. For example, the gaming session may store the amount of funds received and remaining for the gaming session.


At least one game of chance selection may be detected at 324. A player may select a game of chance to play on the mobile electronic device using controls on the mobile electronic device and/or the docking station. If selected using the mobile electronic device, a request for the selected game of chance may be transmitted at 217 to the docking station. If selected using the docking station, a request for the selected game of chance may be transmitted at 217 to the gaming system manager.


The requested game of chance may be transmitted to the mobile electronic device at 332. The requested game of chance data may be obtained from the gaming server and transmitted to the mobile electronic device. In another embodiment, the docking station may determine whether the requested game of chance is stored on the docking station. If the docking station determines that the requested game of chance is stored on the docking station, the docking station may transmit the requested game of chance data to the mobile electronic device.


The game of chance data may be downloaded and stored on the mobile electronic device. In another embodiment, the game of chance data may be streamed to the mobile electronic device, either from the docking station or the gaming system manager. In this embodiment, user input used to play the game of chance may be transmitted to the docking station or the gaming system manager. User input may be received from the mobile electronic device and/or the docking station.


Game session data may be transmitted at 334. Game session data may include any data produced during the game play such as game state data, game history data, account data, coins in and out, credits obtained or used, bonuses received, and any other game data. Game session data may be used in case of a power failure by the docking station or mobile electronic device, malfunction of the docking station or mobile electronic device, or any other reasons. The game session data may be used recreate the gaming sessions to determine if the player won or lost, the amount of credits remaining, if the player was cheating, or any other game session information. Game state data may show a position in a game, game progress, a current account balance, active bets placed, pending game outcomes, and the like. The game history data may include games of chance played, wagers made, past account balances, game progress, outcomes of games of chance, and the like. As the game of chance is played, game session data may periodically transmitted to the docking station. Game session data may be transmitted at any desired time. For example, game session data may be transmitted every thirty seconds, every minute, every fifteen minutes, every hour, or at designated time intervals such as between 1 pm-3 pm, and the like. In one embodiment, game session data may be stored at the docking station. In another embodiment, the game session data may be received by the docking station and transmitted to the gaming system manager. In still another embodiment, the game session data may be directly received by the gaming system manager from the mobile electronic device.


A determination of whether the gaming session should end may be made at 336. The gaming session may end for a variety of reasons such as no more credits to play the game of chance, insufficient account balance, the player leaves the vicinity in which the mobile electronic device is trusted, the mobile electronic device is no longer capable of playing the game of chance, the mobile electronic device is in an area where playing games of chance is prohibited, the battery charge of the mobile electronic device is low, or for any legal reasons.


If it is determined that the gaming session should end at 336, any game of chance data stored on the mobile electronic device may be deleted at 338. Any game session data as well as security software downloaded on the mobile electronic device may also be deleted. If it is determined that the gaming session should not end at 336, game of chance data may continue to be provided to the mobile electronic device at 332.



FIG. 4 illustrates a flowchart of an example method for authorizing a mobile electronic device using a docking station. The method 400 may begin by connecting a mobile electronic device to a docking station at 402. The mobile electronic device may be any device such as mobile telephones, tablet computers, laptop computers, handheld gaming devices, media players, and the like. The connection to the docking station may be via a wired, wireless, or a physical connection to the docking station. In one embodiment, a connector on a receiver of the docking station may be used to connect the mobile electronic device to the docking station. The connector may be designed to receive the mobile electronic device and configured to detect whether the mobile electronic device is physically connected to the docking station. The connector may be designed or configured to allow the mobile electronic device to communicate with the docking station.


In another embodiment, an intermediary connector (e.g. intermediary connector 502 described in detail with reference to FIG. 5A) may be used to connect the mobile electronic device to the receiver. The intermediary connector may be a universal connector to allow all types of mobile electronic devices to communicate with the docking station. The intermediary connector 502 may have a plurality of inputs configured to receive the mobile electronic device or a wire connection to the mobile electronic device. Each of the plurality of inputs may have a different configuration to receive different mobile electronic devices. The intermediary connector 502 may also have an external wire 512 configured to be received by a mobile electronic device. This allows connection to the docking station 500 to be a wired connection.


In another embodiment, the docking station may have a wireless receiver (as illustrated in FIG. 6) to connect the mobile electronic device to the docking station wirelessly. Any known wireless methods may be used such as a 3G wireless technology, 4G wireless technology, Bluetooth, Wireless USB, Near-field magnetic, Fire Wire, WiMax, IEEE 802.11x technology, radio frequency, and the like.


Device information may be transmitted to the docking station at 404. Mobile device information may be any information necessary to determine whether the mobile device has the capability to play games of chance, authenticate the mobile electronic device, validate or authenticate the user of the mobile electronic device, or any other desired information may be transmitted to the docking station. For example, mobile device information may include the mobile electronic device capabilities such as power capacity, display resolution, memory capacity, processor capacity, disk space, software versions, and the like. Mobile device information may also include identification information such as model information, user information, user preferences, game history, bookmarks for specific games of chance, favorite websites and/or games of chance, favorite meals, shows, buffets, and the like. The mobile device information may allow the gaming establishment to determine the user interests. Knowing the user's interests may allow the gaming establishment to transmit any marketing, promotions, coupons, and the like to the mobile electronic device. For example, if a user's interest is playing poker games on the mobile electronic device, the user may be notified of a poker tournament at the gaming establishment. In another example, the user may show an interest in gourmet food. The gaming establishment may transmit, to the mobile electronic device, a coupon for 50% off at their steak house.


A determination of whether the mobile electronic device is authenticated may be made at 406 based on the transmitted mobile device information. Docking station may be configured to authenticate the mobile electronic device to play games of chance based upon the received mobile device information. In one embodiment, using a user interface either on the docking station and/or on the mobile electronic device, the user may be requested to enter a username, password, account number, player tracking information, facial recognition information, voice recognition information, or any other desired user information. In another embodiment, the desired user information necessary to authenticate the mobile electronic device and/or user may be embedded in the mobile electronic device such that authentication may be completed automatically without any user interaction.


To authenticate the mobile electronic device and the user, the received mobile device information may be compared to information stored on the gaming system manager. The docking station may be configured to communicate with the gaming system manager by any known means such as wired or wirelessly. The gaming system manager may have a player tracking server (e.g. player tracking server 103 illustrated in FIG. 1) having a player database configured to store all user information, player tracking information, and any other desired player information. If the received mobile electronic information matches the information stored in the player tracking server, the docking station may determine that the mobile electronic device is authenticated at 310. If the received mobile electronic information does not match the information stored in the player tracking server, the mobile electronic device is not authenticated at 310 and the method 400 may end.


In one embodiment, the comparison of the received mobile device information and the information stored on the player tracking server may be conducted at the docking station. In this embodiment, the docking station may be configured to receive the player tracking information from the gaming system manager. In another embodiment, the comparison of the received mobile device information and the information stored on the player tracking server may be conducted by the gaming system manager. In this embodiment, the docking station may be configured to transmit the received mobile device information to the gaming system manager for comparison. If the information matches, the gaming system manager may transmit an authentication signal to the docking station and a determination of whether the mobile electronic device is a trusted device may be made at 408. If the information does not match, the gaming system manager may transmit a rejection signal to the docking station and the method 400 may end.


In order to become a trusted device, the mobile electronic device must be authenticated and secured. Thus, if the mobile electronic device is determined to be authenticated at 406, a determination of whether the mobile electronic device is trusted may be made at 408 based on the transmitted mobile device information. To be configured to play games of chance, the mobile electronic device must provide for security features to prevent cheating, hacking, and/or to comply with any gaming regulations or laws. In one embodiment, the security features may deny access to all programs or applications on the mobile electronic device except the programs or applications necessary to play the game of chance. If the mobile electronic device contains the desired security features, based on the received mobile device information, the mobile electronic device may be considered a trusted device at 408.


If the desired security features are not located on the mobile electronic device, the device is deemed to not be a trusted device at 408, the required security software or applications may be received by the mobile electronic device at 410. The mobile electronic device may then be converted to a trusted mobile electronic device. The docking station and/or the gaming system manager may determine what secure software and/or applications are necessary for the mobile electronic device to have to become a trusted device. The secure software may then be downloaded to the mobile electronic device. Once the secured software and/or applications are downloaded and saved to the mobile electronic device, the mobile electronic device may be converted to a trusted device and a list of a plurality of games of chance may be received at the mobile gaming device at 416.


Once selected by the user, a request for a selected game of chance may be transmitted at 414 to the docking station and/or gaming system manager. The game of chance data for the selected game of chance may be received at 416. The requested game of chance data may be obtained from the gaming server and transmitted to the mobile electronic device. In another embodiment, the docking station may determine whether the requested game of chance is stored on the docking station. If the docking station determines that the requested game of chance is stored on the docking station, the docking station may transmit the requested game of chance data to the mobile electronic device.


The game of chance data may be downloaded and stored on the mobile electronic device. In another embodiment, the game of chance data may be streamed to the mobile electronic device, either from the docking station or the gaming system manager. In this embodiment, user input used to play the game of chance may be transmitted to the docking station or the gaming system manager. User input may be received from the mobile electronic device and/or the docking station.


A determination of whether the gaming session should end may be made at 418. The gaming session may end for a variety of reasons such as no more credits to play the game of chance, insufficient account balance, the player leaves the vicinity in which the mobile electronic device is trusted, the mobile electronic device is no longer capable of playing the game of chance, the mobile electronic device is in an area where playing games of chance is prohibited, the battery charge of the mobile electronic device is low, or for any legal reasons.


If it is determined that the gaming session should end at 418, any game of chance data stored on the mobile electronic device may be deleted. Any game session data as well as security software downloaded on the mobile electronic device may also be deleted. If it is determined that the gaming session should not end at 418, game of chance data may continue to be received at 416.



FIG. 5 illustrates an example docking station. The docking station 520520 may have a housing 508, a receiver 514, and a connector 516. The housing 508 may be made from any material, such as metal, plastic, and any other desired material. The housing, although illustrated as a rectangular shape, may be formed as any desired shape such as a circular, cube, square, cube, triangle, prism, and the like. The housing 508 may be formed from any known process such as being molded or any other known methods.


The receiver 514 may be designed to receive any mobile electronic device. The receiver 514 may be designed to be set into or recessed into the housing 508. In another embodiment, the receiver may extend outwardly from the housing. In still another embodiment, the receiver 514 may be flush with the housing 508 of the docking station 520.


Receiver 514 may include a connector 516 positioned in the center of the receiver 514 and extending outwardly from the receiver 514. The connector 516 may be designed to receive a mobile electronic device and configured to detect whether the mobile electronic device is physically connected to the docking station 520. The connector 516 may be designed or configured to allow the mobile electronic device to communicate with the docking station 520. As illustrated, connector 516 may have different shapes and be different types of connectors to receive different types of mobile electronic devices. Although depicted as a physical connection, the connector 516 maybe a wireless connection between the docking station and the mobile electronic device. A wireless connection is convenient to allow connection between the docking station and the mobile electronic device without having to find a matching physical connector-pair. Wireless communication technology such as WiFi (802.11x), BlueTooth, Near Field Communication, Zigbee, and the like are known in the art and can be implemented. Additionally, the charging function may also be implemented without a physical connection using a wireless charging technology. For example, wireless charging via electromagnetic induction utilizes two induction coils, one in the charging station and one in the portable electronic device, to transfer energy via alternating electromagnetic field.


In one embodiment, the detection may occur when the mobile electronic device is physically connected or coupled to the receiver 514. In another embodiment, detection may occur when an intermediary connector (not shown) may be used to connect the mobile electronic device to the receiver 514. The intermediary connector 502 may be a universal connector to allow all types of mobile electronic devices to communicate with the docking station, such as, for example, the portable intermediary trusted device discussed in U.S. application Ser. No. 13/833,116, filed Mar. 15, 2013, which is incorporated by reference. The mobile electronic device may be any device such as mobile telephones, tablet computers, laptop computers, handheld gaming devices, media players, and the like.


The intermediary connector may have a plurality of inputs configured to receive the mobile electronic device or a wire connection to the mobile electronic device. Each of the plurality of inputs may have a different configuration to receive different mobile electronic devices. The intermediary connector—may also have an external wire configured to be received by a mobile electronic device. This allows connection to the docking station 520 to be a wired connection. Although depicted as a physical connection, the intermediary connector maybe replaced with a wireless connection between the docking station and the mobile electronic device. A wireless connection is convenient to allow connection between the docking station and the mobile electronic device without having to find a matching physical connector-pair. Wireless communication technology such as WiFi (802.11x), BlueTooth, Near Field Communication, Zigbee, and the like are known in the art and can be implemented.


In one embodiment, when the mobile electronic device is connected to the docking station 520, the docking station may be configured to provide an electronic charge to the mobile electronic device thereby charging the battery of the mobile electronic device. Charging maybe implemented as a wired connection. Additionally, the charging function may also be implemented without a physical connection using a wireless charging technology. For example, wireless charging via electromagnetic induction utilizes two induction coils, one in the charging station and one in the portable electronic device, to transfer energy via alternating electromagnetic field.


Once connected to or in communication with the docking station, any data may be transferred from the mobile electronic device to the docking station and vice versa using connector 516. In one example, the docking station 520 may detect whether the mobile electronic device is received by receiver 514 upon the initial transfer of information from the mobile electronic device to the docking station. Mobile device information may be any information necessary to determine whether the mobile device has the capability to play games of chance, authenticate the mobile electronic device, validate or authenticate the user of the mobile electronic device, or any other desired information may be transmitted to the docking station. For example, mobile device information may include the mobile electronic device capabilities such as power capacity, display resolution, memory capacity, processor capacity, disk space, software versions, and the like. Mobile device information may also include identification information such as model information, user information, user preferences, game history, bookmarks for specific games of chance, favorite websites and/or games of chance, favorite meals, shows, buffets, and the like. The mobile device information may allow the gaming establishment to determine the user interests. Knowing the user's interests may allow the gaming establishment to transmit any marketing, promotions, coupons, and the like to the mobile electronic device. For example, if a user's interest is playing poker games on the mobile electronic device, the user may be notified of a poker tournament at the gaming establishment. In another example, the user may show an interest in gourmet food. The gaming establishment may transmit, to the mobile electronic device, a coupon for 50% off at their steak house.


In another example, game session data may be periodically transferred from the mobile electronic device to the docking station and game of chance data may be transmitted from the docking station to the mobile electronic device as the player plays the game of chance. Game session data may be used in case of a power failure by the docking station or mobile electronic device, malfunction of the docking station or mobile electronic device, or any other reasons. The game session data may be used recreate the gaming sessions to determine if the player won or lost, the amount of credits remaining, if the player was cheating, or any other game session information. Game session data and/or game of chance data may be transmitted at any desired time. For example, game session data and/or game of chance data may be transmitted every thirty seconds, every minute, every fifteen minutes, every hour, or at designated time intervals such as between 1 pm-3 pm, and the like. Game session data may include any data produced during the game play such as game state data, game history data, account data, coins in and out, credits obtained or used, bonuses received, and any other game data. Game state data may show a position in a game, game progress, a current account balance, active bets placed, pending game outcomes, and the like. The game history data may include games of chance played, wagers made, past account balances, game progress, outcomes of games of chance, and the like. In one embodiment, game session data may be stored at the docking station. In another embodiment, the game session data may be received by the docking station and transmitted to the gaming system manager. In still another embodiment, the game session data may be directly received by the gaming system manager from the mobile electronic device.


Also feasible is a wireless connection for communication as well as for charging. Docking station may also have a variety of inputs, outputs, controls, peripherals, and other external devices. For example, docking station may have a plurality of user controls speaker, camera, printer, microphone, card reader, and display.


The plurality of user controls 610 may be used to transmit an input and/or output to the mobile electronic device and/or to the docking station. The plurality of user controls may be any type of user controls such as a keypad, keyboard, button panel, buttons, joystick, and any other user controls able to provide input and/or output. For example, the user controls may be used to input username, account number, request for drinks, request restaurant reservation, request a fund transfer, and any other requests and/or data. The user controls 610 may also be used to play the game of chance.


The speaker may be used to provide audio such as music, audio instructions, and any other audio sounds such as bells, whistles, and the like. For example, if the player wins a bonus play, the speaker may output a distinctive sound that alerts the player a bonus game is about to begin.


Microphone 618 may be configured to receive audio sounds from the user. For example, in lieu of using the plurality of user controls, the user may use the microphone to verbally input requests and data, such as username, account number, request for drinks, request restaurant reservation, request a fund transfer, and any other requests and/or data. In another example, microphone may be configured to recognize the voice of the player using voice recognition information previously provided by the player.


Camera may be used to detect images, such as the user's image to authenticate the user. For example, camera may be configured to conduct facial recognition to authenticate the player in order to convert the mobile electronic device to a trusted device. In another example, camera may also be used by the gaming establishment to communicate with the user and/or allow the user to play the games of chance. In another example, camera may be configured to recognize gestures. For example, if the player is playing blackjack, the player may use gestures to “Hit” or “Stand”. In another example, the player may use gestures to request a fund amount. Thus, camera may be used for any gaming or non-gaming purposes.


Printer may be configured to print any information or data. For example, printer may be used to print vouchers, coupons, receipts, documents, and the like. As stated above with reference to FIG. 1, mobile device information may also include identification information such as model information, user information, user preferences, game history, bookmarks for specific games of chance, favorite websites and/or games of chance, favorite meals, shows, buffets, and the like. The mobile device information may allow the gaming establishment to determine the user interests. Knowing the user's interests may allow the gaming establishment to transmit any marketing, promotions, coupons, and the like to the mobile electronic device. For example, if a user's interest is playing poker games on the mobile electronic device, the user may be notified of a poker tournament at the gaming establishment by printing out a flyer notifying the player of the poker tournament. In another example, the user may show an interest in gourmet food. The gaming establishment may transmit, to the docking station, a coupon for 50% off at their steak house that may be printed using printer 616.


Card reader may be configured to read data from a storage medium, such as a credit card, player tracking card, and the like. Card reader may be used to access to a player tracking account, transfer funds from a credit card or banking card, transfer user information, or any other desired requests, uses, and the like. In another example, card reader may be used to read data from a card to authenticate and/or validate the mobile electronic device.


Display may be any type of known display such as a liquid crystal display, touch screen, and the like. Display may be used for any known purposes such as displaying or presenting gaming establishment information (e.g., list of games of chance that may be played on the mobile electronic device, tournament information, movie times, and the like) to the player, display funds in the player tracking account, display remaining credits to play the game of chance. In another example, display may be used as a touch screen to input user information, such as username, password, play games of chance, and any other information. Display may be used to present or display any other gaming or non-gaming information.


In use, a player may select to play a game of chance using a variety of methods. For example, the player may select a game of chance using the touch-screen display, one of the plurality of user inputs, both the display and at least one of the plurality of user inputs, verbally requesting the game of chance using the microphone, gesture recognition using the camera.


As discussed in detail above, the game of chance may be downloaded or streamed to the mobile electronic device. Either way, the user may play the game of chance using a variety of devices or peripherals on the docking station. For example, the user may play the game of chance using controls on the mobile electronic device. In another example, the user may play the game of chance using the plurality of user controls, display, microphone, gesture recognition on camera, a combination of peripherals, or any other method.


After playing the game of chance, the user may want to cash out any remaining credits. The user may transmit a request to cash out using the user controls, display, microphone, camera, card reader, a combination of peripherals, or any other input methods to transmit the request to cash out. In one example, when the docking station receives the request to cash out, a credit voucher may be printed using printer. In another example, the player may verbally request to cash out using microphone and that the remaining balance be transferred to a credit card using card reader. In yet another example, user may request to cash out using display.



FIG. 6 illustrates a block diagram of an example docking station. Docking station 800 may have a processor 802, memory 828, and a plurality of peripherals. Although only a few of the peripherals will be discussed herein, it will now be known that the docking station may have and use a variety of peripherals as described herein or desired by the user. For example, processor 802 may be configured to determine whether the games of chance can be played on the mobile electronic device based on received device information. In another example, processor 802 may be configured to transmit game session data, accounting data, mobile device information, and the like to the gaming system manager and/or the mobile electronic device. In yet another example, processor may be configured to delete all gaming session data, game of chance data, and any other desired data, application, and information from the mobile electronic device. Processor 802 may be configured to communicate with the docking station 800 peripherals, mobile electronic device, gaming server, and other servers in order to carry out the necessary desired functions. For example, processor 802 may receive a game of chance request from the mobile electronic device. In turn, processor 802, may transmit the game of chance request to the gaming system manager (e.g. gaming system manager 104 illustrated in FIG. 1) via the network interface 804.


Docking station 800 may detect a mobile electronic device. In one embodiment, the docking station 800 may detect the mobile electronic device when physically connected to the receiver 808 of the docking station 800. Receiver 808 may be designed to receive any mobile electronic device and may have a connector (e.g. connector 506 illustrated in FIGS. 5A and 5B) designed to receive a mobile electronic device and configured to detect whether the mobile electronic device is physically connected to the docking station 800.


In another embodiment, the mobile electronic device may be detected when an intermediary connector (e.g. a portable intermediary trusted device) is connected to receiver 808. In still another embodiment, mobile electronic device may communicate wireless with docking station 800 via wireless interface 801 using any known wireless technology such as such as a 3G wireless technology, 4G wireless technology, Bluetooth, Wireless USB, Near-field magnetic, Fire Wire, WiMax, IEEE 802.11x technology, radio frequency, and the like.


Once detected, mobile device information may be obtained from the mobile electronic device. Mobile device information may be any information necessary to determine whether the mobile device has the capability to play games of chance, authenticate the mobile electronic device, validate or authenticate the user of the mobile electronic device, or any other desired information may be transmitted to the docking station. For example, mobile device information may include the mobile electronic device capabilities such as power capacity, display resolution, memory capacity, processor capacity, disk space, software versions, and the like. Mobile device information may also include identification information such as model information, user information, user preferences, game history, bookmarks for specific games of chance, favorite websites and/or games of chance, favorite meals, shows, buffets, and the like. The mobile device information may allow the gaming establishment to determine the user interests. Knowing the user's interests may allow the gaming establishment to transmit any marketing, promotions, coupons, and the like to the mobile electronic device. For example, if a user's interest is playing poker games on the mobile electronic device, the user may be notified of a poker tournament at the gaming establishment. In another example, the user may show an interest in gourmet food. The gaming establishment may transmit, to the mobile electronic device, a coupon for 50% off at their steak house.


Mobile device information may be stored in memory 828. Memory 828 may be configured to store any type of data such as, game of chance data, secure software, applications, game session data, and any other desired data or information. Memory 828 may be any type of memory including random access memory (RAM), read only memory (ROM), non-volatile random access memory (NVRAM), disk memory, magnetic tapes, paper tapes, laser storage and the like. Independently, random access memory requires power in order to maintain stored data. Battery backed RAM may store variable if the power goes down. ROM cannot be adjusted once written but does not require power in order to store information. NVRAM does not require power in order to maintain variables and can be written to. Disk memory and tape memory may be a bit slower but can store variables without power. ROM may be useful for storing games of chance on the docking station. RAM and NVRAM may also be useful for storing games on the docking station, especially if the docking station only temporarily stores games during a particular gaming session.


Docking station 800 may have a variety of peripherals such as user controls 801, card reader 814, microphone 822, camera 824, and display 826. User controls 801 may be used to transmit an input and/or output to the mobile electronic device and/or to the docking station. User controls 801 may be any type of user controls such as a keypad, keyboard, button panel, buttons, joystick, and any other user controls able to provide input and/or output. For example, user controls 801 may be used to input username, account number, request for drinks, request restaurant reservation, request a fund transfer, and any other requests and/or data. The user controls 801 may also be used to play the game of chance.


Microphone 822 may be configured to receive audio sounds from the user. For example, in lieu of using user controls 801, the user may use the microphone 822 to verbally input requests and data, such as username, account number, request for drinks, request restaurant reservation, request a fund transfer, and any other requests and/or data. In another example, microphone 822 may be configured to recognize the voice of the player using voice recognition information previously provided by the player.


Camera 824 may be used to detect images, such as the user's image to authenticate the user. For example, camera 824 may be configured to conduct facial recognition to authenticate the player in order to convert the mobile electronic device to a trusted device. In another example, camera 824 may also be used by the gaming establishment to communicate with the user and/or allow the user to play the games of chance. In another example, camera 824 may be configured to recognize gestures. For example, if the player is playing blackjack, the player may use gestures to “Hit” or “Stand”. In another example, the player may use gestures to request a fund amount. Thus, camera 824 may be used for any gaming or non-gaming purposes.


Printer 816 may be configured to print any information or data. For example, printer 816 may be used to print vouchers, coupons, receipts, documents, and the like. As stated above with reference to FIG. 1, mobile device information may also include identification information such as model information, user information, user preferences, game history, bookmarks for specific games of chance, favorite websites and/or games of chance, favorite meals, shows, buffets, and the like. The mobile device information may allow the gaming establishment to determine the user interests. Knowing the user's interests may allow the gaming establishment to transmit any marketing, promotions, coupons, and the like to the mobile electronic device. For example, if a user's interest is playing poker games on the mobile electronic device, the user may be notified of a poker tournament at the gaming establishment by printing out a flyer notifying the player of the poker tournament. In another example, the user may show an interest in gourmet food. The gaming establishment may transmit, to the docking station, a coupon for 50% off at their steak house that may be printed using printer 816.


Card reader 814 may be configured to read data from a storage medium, such as a credit card, player tracking card, and the like. Card reader 814 may be used to access to a player tracking account, transfer funds from a credit card or banking card, transfer user information, or any other desired requests, uses, and the like. In another example, card reader 814 may be used to read data from a card to authenticate and/or validate the mobile electronic device.


Display 826 may be any type of known display such as a liquid crystal display, touch screen, and the like. Display 826 may be used for any known purposes such as displaying or presenting gaming establishment information (e.g., list of games of chance that may be played on the mobile electronic device, tournament information, movie times, and the like) to the player, display funds in the player tracking account, display remaining credits to play the game of chance. In another example, display 826 may be used as a touch screen to input user information, such as username, password, play games of chance, and any other information. Display 826 may be used to present or display any other gaming or non-gaming information.


Docking station 800 may also have a notification device 812. Notification device 812 may be a light, light rope, light pipe, candle (e.g. candle 1210 illustrated in FIGS. 10A and 10B), multicolor LED's, a speaker which makes noise, and any other notification device to notify service personnel that a service request is desired by the player. In another example, notification device 812 may notify service personnel of the gaming establishment that the docking station has a failure or malfunction. In another example, if a player would like to ordered a drink, a yellow light can flash to notify a waitress. In another example, a red light can flash to indicate a malfunction.


Docking station 800 may also have a scanner 818. Scanner may be used to scan documents, bar codes, and the like. For example, the scanner may be used by the player to scan a voucher printed from another gaming machine. The credits remaining on the voucher may then be used to play the games of chance. In another example, the player may scan a voucher to participate in a poker tournament without having to be at the exact location of where the poker tournament is being played.


Docking station 800 may also have a motion tracking device 820. The motion tracking device 820 may be used to play the games of chance. The motion tracking device 820 may be any device configured to determine the orientation, produce motion, and the like on the docking station 800 and/or the mobile electronic device. For example, the motion tracking device 820 may be a gyroscope to determine orientation, a laser, haptic transducers, and/or an accelerometer to determine acceleration magnitude and vectors. For example, if playing a car racing simulation game of chance, the docking station 800 may be tilted to the right in order to turn the car to the right. When the docking station 800 is turned to the right, the motion tracking device 820 may determine the orientation and turn the car in the simulation game of chance to the right. If the car crashes, haptic transducers in the docking station 800 may cause the docking station to vibrate in response to the crash.



FIGS. 7A-7B illustrate an example authorization of a mobile electronic device to play a game of chance. The mobile electronic device 902 may be inserted into the receiver 906 of the docking station 904. The receiver 906 may have a connector (e.g. connector 516 illustrated in FIG. 5) configured to connect the mobile electronic device to the docking station. The connector may be designed to receive the mobile electronic device and configured to detect whether the mobile electronic device is physically connected to the docking station. The connector may be designed or configured to allow the mobile electronic device to communicate with the docking station. As previously discussed in FIG. 5, the connection maybe implemented as a wired or a wireless connection.


Referring to FIG. 7A, once the mobile electronic device 902 is physically connected to the docking station 904, the docking station 904 may detect the mobile electronic device. The mobile electronic device may have a display 918 displaying a battery life indicator 914. As illustrated, the battery life indicator 914 may indicate that the mobile electronic device 902 is not fully charged. If not fully charged, the docking station 904 may transmit a charge to the battery of the mobile electronic device 902 to recharge the battery of the mobile electronic device. In one embodiment, the mobile electronic device may indicate that it is being charged with a message displayed on display 918. For example, “Charging” 912 may be displayed on display 918.


Docking station may transmit an authentication request to the mobile electronic device to authenticate the mobile electronic device 902 and/or the user. In one embodiment, a request for a user identification 920 and password 922 may be displayed on display 918. The player may then enter the button 924 on the display 902 to gain authorization.


Referring now to FIG. 7B, after a period of time being physically connected to the gaming, the battery life indicator 914 indicates that the battery is being recharged. If the mobile electronic device is authenticated an authentication notification may be transmitted to the mobile gaming device 902 and presented on display 912. For example, FIG. 8B may display a “Welcome To Our Gaming Network!!!” 932 message on display 918. This indicates that the mobile gaming device 902 and/or user is authenticated.



FIGS. 8A-8B illustrate an example use of a docking station. FIG. 8A illustrates the mobile electronic device 1002 docked in the docking station 1004 while playing a game of chance presented on display 1018. The display 1018 may present a plurality of user interface controls 1006. The user interface controls 1006 may be any type of displayed user controls used to play the game of chance such as to select a wager amount, spin, cash out, and the like. The amount of credits remaining 1022 may also be presented on display 1018.


In one embodiment, docking station 1004 may have a joystick 1010. The joystick may also be used to play the game of chance 1009. As illustrated, joystick 1010 may be used to spin the reels 1008 of the game of chance presented on display 1018. The joystick may be in a first position indicating that no action has been taken. Referring to FIG. 8B, the player may move the joystick 1010 to a second position indicating that the player would like to spin the reel 1008 using the joystick 1010 and not the user interface controls 1006.



FIGS. 9A-9B illustrate another example use of a document station. If the user would like to end the game session, the user may want to cash out his remaining credits. FIG. 9A illustrates the mobile electronic device 1102 connected to docking station 1104. In one embodiment, the player may use user interface controls (e.g. user interface controls 1006 illustrated in FIGS. 8A and 8B) to cash out. In another embodiment, the player may use user controls 1103 (e.g., user controls 610 illustrated in FIG. 6) to cash out.


Once a request to cash out is transmitted to the docking station 1104, the player may be questioned to determine whether the player would like to print a voucher for the remaining credit. For example, a message “Would You Like To Cash Out And Print A Voucher?” 1106 may be displayed on display 1118. A “No” indicator 1108 and a “Yes” indicator 1110 may be simultaneously displayed on display 1118. Although the inquiry is illustrated as being presented on the display 1118 of the mobile electronic device 1102, this is not intended to be limiting as the inquiry may also be presented on a display of the docking station 1104 (e.g. display 622 illustrated in FIG. 6).


Referring now to FIG. 9B, if the player would like a voucher printed out for the remaining credit balance, printer 1112 may print the voucher 1124. Once the voucher is printed, display 1118 may present a completion notification 1122 such as, for example, “THANKS FOR PLAYING! Please Come Back Soon”.



FIGS. 10A-10B illustrate still another example use of a docking station. Referring to FIGS. 10A and 10B, while the player is playing the game of chance 1208, waiting for the mobile electronic device 1202 to charge, or for any other reason, player may want to order a drink, food, or any other type of service. Thus, the docking station 1204 may be used to make service calls. The user may use either the user interface controls 1206 displayed on display 1218 or the user controls 1212 on the docking station 1204 to indicate he would like to make a service request. The request for service may be transmitted to the docking station 1204 and a candle 1210 on the docking station may be illuminated (as illustrated in FIG. 10B) to alert the customer service personnel that the player would like to make a service request.



FIGS. 11A-11D Illustrate yet another example use of the docking station. Some players may desire to work while playing games of chance for entertainment, such as while on vacation. The docking station may provide the flexibility for business people to work while on vacation (or not on vacation) and may also be used as a work station. As illustrated in FIG. 11A, if the mobile electronic device 1302 is able to receive electronic mail (e-mail), display 1318 may indicate that the player has a new email message 1306.


Referring now to FIG. 11B, the e-mail message may be displayed 1322 on display 1318. The email message may contain a document 1324 that the player may need to print out to review. As illustrated in FIG. 11C, the user may be provided the option 1334 to print the document using the docking station 1304. In one embodiment, the user may be charged per page for each page printed out and may use the docking station to pay for the printouts. In another embodiment, the user is not charged for the printout. If the user would like to print the document using the docking station, as illustrated in FIG. 11D, the document 1344 may be printed using printer 1312. Upon completion of the printing, display 1318 may display a completion notification 1342, for example, a “Printing Complete!” message.


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.

Claims
  • 1. A docking station configured to authorize a player's mobile electronic device to play one or more games of chance, the docking station comprising: a detector configured to detect whether the player's mobile electronic device is coupled to the docking station; anda processor operatively coupled to the detector and configured to: detect whether the player's mobile electronic device has been detected via the detector;receive device information from the player's mobile electronic device if it is detected that the player's mobile electronic device is detected by the detector;determine whether the player's mobile electronic device is permitted to participate in the one or more games of chance based on the received device information;authorize the player's mobile electronic device to participate in the one or more games of chance after it is determined that the player's mobile electronic device is permitted to participate in the one or more games of chance; andreceive participation data from the player's mobile electronic device if it is determined that the player's mobile electronic device is permitted to participate in the one or more games of chance and if the player's mobile electronic device is authorized,wherein once the player's mobile electronic device is authorized to participate in the one or more games of chance, the player's mobile electronic device is deemed a trusted gaming device for use within a gaming establishment and is automatically authenticated when coupled to another docking station within the gaming establishment, andwherein the player's mobile electronic device is able to be used by the player independent of the gaming establishment.
  • 2. A docking station as recited in claim 1, wherein the player brings the player's mobile electronic device to the gaming establishment.
  • 3. A docking station as recited in claim 1, wherein the docking station comprises a recess configured to receive the player's mobile electronic device when the player's mobile electronic device is coupled to the docking station.
  • 4. A docking station as recited in claim 1, wherein the player's mobile electronic device is a mobile telephone.
  • 5. A docking station as recited in claim 1, wherein the one or more games of chance are managed at a gaming server that is separate and distinct from the docking station.
  • 6. A docking station configured to authorize a player's mobile electronic device to play one or more games of chance, the docking station comprising: a processor operatively coupled to a detector and configured to: detect whether the player's mobile electronic device is coupled to the docking station;receive information from the player's mobile electronic device if it is detected that the player's mobile electronic device is coupled to the docking station;determine whether the player's mobile electronic device is permitted to participate in the one or more games of chance based on the received information;authorize the player's mobile electronic device to participate in the one or more games of chance after it is determined that the player's mobile electronic device is permitted to participate in the one or more games of chance; andreceive participation data from the player's mobile electronic device if it is determined that the player's mobile electronic device is authorized,wherein once the player's mobile electronic device is permitted to participate in the one or more games of chance, the player's mobile electronic device is deemed a trusted gaming device for use within a gaming establishment and is automatically authorized when coupled to another docking station within the gaming establishment.
  • 7. A docking station as recited in claim 6, wherein the player's mobile electronic device is able to be used by the player for uses other than participation in the one or more games of chance, even while coupled to the docking station.
  • 8. A docking station as recited in claim 6, wherein the docking station comprises one or more of: a card reader, a printer, a scanner, a camera, a wireless transceiver, a display, a button, a motion sensor, wired charging technology, wireless induction charging technology, or a near-field wireless technology.
  • 9. A docking station as recited in claim 6, wherein the docking station comprises: a charging technology for charging the player's mobile electronic device while coupled to the docking station.
  • 10. A docking station as recited in claim 9, wherein the charging technology provides wireless, induction charging.
  • 11. A docking station as recited in claim 6, wherein the docking station configured to permits a funds transfer using at least one of a card reader, a printer, a scanner, a wireless transceiver or a near-field communication device, and wherein the funds transfer renders funds available for use in playing the one or more games of chance using the player's mobile electronic device.
  • 12. A docking station as recited in claim 6, wherein the docking station configured to facilitate funds transfer, and wherein the funds transfer renders funds available for use in playing the one or more games of chance using the player's mobile electronic device.
  • 13. A docking station as recited in claim 6, wherein the received information comprise one or more of a user identification, user preference information, game history, player tracking account information, or mobile device information.
  • 14. A docking station as recited in claim 6, wherein while the player's mobile electronic device is deemed a trusted gaming device, the player's mobile electronic device is permitted to transfer funds into or out of a fund account for use by the player for gaming or non-gaming use.
  • 15. A docking station as recited in claim 6, wherein the processor is further configured to: after the player's mobile electronic device has been authorized, detect whether the player's mobile electronic device is no longer in a detection range of the docking station.
  • 16. A docking station as recited in claim 6, wherein the docking station further comprises: a display operatively coupled to the processor and configured to display status and transaction messages.
  • 17. A docking station as recited in claim 6, wherein the docking station further comprises: a user interface control operatively coupled to the processor and configured to provide player input for use in playing the one or more games of chance.
  • 18. A docking station as recited in claim 17, wherein at least one of the one or more games of chance uses one or more reels, and wherein the user interface control is configured to signal a request by the player to cause the one or more reels to spin.
  • 19. A docking station as recited in claim 17, wherein the user interface control is further configured to generate a service request.
  • 20. A docking station as recited in claim 6, wherein the docking station is configured to facilitate electronic funds transfer to a player account.
  • 21. A docking station as recited in claim 6, wherein the docking station comprises a card reader or a near-field communication interface to facilitate electronic funds transfer to a player account.
  • 22. A docking station as recited in claim 6, wherein the docking station is further configured to connect to a player tracking server to obtain player information or to facilitate a fund transfer transaction.
  • 23. A docking station as recited in claim 6, wherein the processor is further configured to: determine whether the mobile electronic device that was previously authorized is no longer authorized; anddeauthorize the player's mobile electronic device when it is determined that the player's mobile electronic device is no longer authorized.
  • 24. A docking station as recited in claim 6, wherein the processor is further configured to: detect whether the mobile electronic device is no longer in a detection range of the docking station; anddeauthorize the mobile electronic device when it is determined that the mobile electronic device is no longer authorized.
  • 25. A docking station as recited in claim 6, wherein at least a portion of the game data is transmitted to the player's mobile electronic device by streaming data to the player's mobile electronic device via the docking station.
  • 26. A docking station as recited in claim 6, wherein the player's mobile electronic device is coupled to the docking station by being wirelessly connected therebetween.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 15/270,333, filed Sep. 20, 2016, and entitled “GAMING DEVICE DOCKING STATION FOR AUTHORIZED GAME PLAY,” which is hereby incorporated by reference herein in its entirety for all purposes, which in turn is a continuation of 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. This application is related to U.S. application Ser. No. 13/833,116, filed Mar. 15, 2013, and entitled “PORTABLE INTERMEDIARY TRUSTED DEVICE,” which is hereby incorporated by reference herein in its entirety for all purposes.

US Referenced Citations (582)
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 Beni 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 Globbi 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 et al. 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 Speers 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 Homik 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 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
20060148551 Walker et al. Jul 2006 A1
20060189382 Muir 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
20080126529 Kim et al. 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
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 Speers et al. Sep 2010 A1
20100227670 Arezine et al. Sep 2010 A1
20100227671 Laaroussi Sep 2010 A1
20100227687 Speers 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 Speers 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
20130281188 Guinn 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
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, III 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
Foreign Referenced Citations (11)
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
Non-Patent Literature Citations (262)
Entry
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.
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, dated 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, dated 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. 13/843,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.
Related Publications (1)
Number Date Country
20180053378 A1 Feb 2018 US
Continuations (2)
Number Date Country
Parent 15270333 Sep 2016 US
Child 15798363 US
Parent 13833953 Mar 2013 US
Child 15270333 US