Patent Grant
12347268
Today, mobile betting is available at designated sports betting areas of casinos. However, this means that mobile betting is not available when one is not at a designated sports betting area. This is a burden to customer and leads to limited opportunities for sports betting. Mobile gaming has been contemplated but gaming regulations hinder its implementation.
Portable electronic devices represent an alternative means to desktop computers to allow users to more conveniently interact with a variety of multimedia services. For example, many portable electronic devices may be configured to allow for the user to interact with multimedia services, messaging services, internet browsing services, telephone services, and the like. Furthermore, the software of portable electronic devices may be configured to be updated so as allow for the presentation of additional multimedia services or applications. Portable electronic devices may also be configured to have wireless transmission and receiving capabilities so as to permit communication with one or more other sources.
Hence, there is a continuing need for improved approaches to enhance mobile betting or gaming opportunities.
Embodiments disclosed herein concern mobile gaming environments. Portable electronic devices can be supported by the mobile gaming environments. The locations of the portable electronic device can influence how the portable electronic devices operate or what services or features are available to the portable electronic device or their users. According to one embodiment, a mobile gaming system can concern gaming/betting opportunities that can be secured using a portable electronic device even when an individual is located in a location where betting or games of chance are not permitted. According to another embodiment, wagers are advantageously configured, managed or otherwise processed such that they can be deferred, conditional and/or proxy assisted. Electronic gaming kiosks, personal mobile electronic devices, and/or gaming devices can be provided, and used individually or in combination, to facilitate entry, receipt and/or management of wagers.
The invention can be implemented in numerous ways, including as a method, system, device, apparatus (including computer readable medium and graphical user interface). Several embodiments of the invention are discussed below.
As a gaming system for wager-based games, one embodiment can, for example, include at least: a plurality of conditional wager terminals configured to permit players to make conditional wagers for wager-based games; a conditional wager management system configured to electronically receive the conditional wagers from players operating the conditional wager terminals, evaluate conditions of the conditional wagers, and determine when to activate the conditional wagers; and an authorized gaming system for executing wager-based games for the conditional wagers once the conditional wager management system determines that the conditional wagers are to be activated.
As a gaming system for wager-based games, another embodiment can, for example, include at least: a conditional wager management system configured to electronically receive a multi-conditional wager from a player, evaluate conditions of the multi-conditional wager, and determine when to invoke the conditional wager; and a gaming management system configured to interact with an authorized gaming apparatus to cause a conditional wager for a wager-based game to be performed on the authorized gaming apparatus once the conditional wager management system determines that the conditional wager is to be invoked, and to acquire a result of the conditional wager for the wager-based games. The conditional wager management system can receive gaming status information associated with the authorized gaming apparatus, and the conditional wager management system can operate to valuate the conditions of the multi-conditional wager based on the gaming status information.
As a method for managing conditional wagers for wager-based games, one embodiment can, for example, include at least: receiving a conditional wager of a player, the conditional wager being conditional on a plurality of conditions; subsequently evaluating the plurality of conditions; determining whether the plurality of conditions are satisfied; activating the conditional wager if the determining has determined that the plurality of conditions are satisfied; receiving a result of the conditional wager; and facilitating notification of the wager result to the player via electronic message.
As a method for managing conditional wagers for wager-based games, one embodiment can, for example, include at least: receiving a proxy play request from a player, the proxy play request being a request for a proxy to effect a wager on a wager-based game; requiring that the player have a player account; assigning and instructing a proxy to place the wager on the wager-based game for the player; awaiting wager results from the wager on play of the wager-based game by the proxy for the player; and notify the player of the wager results from the proxy play request.
As a computer readable medium including at least computer program code tangibly stored thereon for managing conditional wagers for wager-based games, one embodiment can, for example, include at least: computer program code for receiving a conditional wager of a player, the conditional wager being conditional on a plurality of conditions; computer program code for subsequently evaluating the plurality of conditions; computer program code for determining whether the plurality of conditions are satisfied; computer program code for activating the conditional wager if the computer program code for determining has determined that the plurality of conditions are satisfied; computer program code for receiving a result of the conditional wager; and computer program code for facilitating notification of the wager result to the player via electronic message.
As a computer readable medium including at least computer program code tangibly stored thereon for managing wagers for wager-based games, one embodiment can, for example, include at least: computer program code for receiving a proxy play request from a player, the proxy play request being a request for a proxy to effect a wager on a wager-based game; computer program code for requiring that the player have a player account; computer program code for assigning and instructing a proxy to place the wager on the wager-based game for the player; computer program code for awaiting wager results from the wager on play of the wager-based game by the proxy for the player; and computer program code for notify the player of the wager results from the proxy play request.
The present invention will be readily understood by the following detailed descriptions in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:
Embodiments disclosed herein concern mobile gaming environments. Portable electronic devices can be supported by the mobile gaming environments. The locations of the portable electronic device can influence how the portable electronic devices operate or what services or features are available to the portable electronic device or their users. According to one embodiment, a mobile gaming system can concern gaming/betting opportunities that can be secured using a portable electronic device even when an individual is located in a location where betting or games of chance are not permitted. According to another embodiment, wagers are advantageously configured, managed or otherwise processed such that they can be deferred, conditional and/or proxy assisted. Electronic gaming kiosks, personal mobile electronic devices, and/or gaming devices can be provided, and used individually or in combination, to facilitate entry, receipt and/or management of wagers.
Embodiments disclosed herein concern mobile, local and/or remote gaming environments.
In any event, following the receipt of a conditional wager via the conditional wager terminal 102, the conditional wager terminal 102 that has received the conditional waiver can provide the conditional wager to a conditional wager management system 104 by way of one or more networks 106. The conditional wager management system 104 is a computer implemented system that serves to receive the conditional wagers for one or more players and manages activation of such conditional wagers. For example, a conditional wager can be dependent on one or more conditions. As a result, the wager denoted by the conditional wager is not activated until the one or more conditions have been satisfied. It may be that the conditions are never satisfied and thus the conditional wager is never activated. However, when the conditions are properly satisfied, the conditional wager can be activated. The conditional wager management system 104 performs processing to evaluate when and whether conditions of various conditional wagers have been satisfied. Thereafter, for those conditional wagers that have had their condition satisfied, the conditional wager management system 104 can activate the conditional wagers.
In activating the conditional wagers, the conditional wager management system 104 provides the corresponding wagers to an authorized gaming system 108. The authorized gaming system 108 is a gaming system that has been authorized to permit wager-based games. The authorization may be based on compliance to gaming rules governing the country, the state, the city, the casino, etc. The authorized gaming system 108 can restrict gaming by preventing or limiting wagers based on location of the wager transaction, the age of a player, the agency representing a player or a group of players, the agency's jurisdictional license, the source of funds, the size of the wager, the time of the wager, and/or the like. In one implementation, the authorized gaming system 108 can be associated with a gaming establishment, such as a casino. In another implementation, the authorizing gaming system 108 can be associated with a governmental compliance or enforcement agency. Further, the authorizing gaming system 108 can be located at a gaming site, or can be a secured virtual system residing in a computing cloud such as cloud products offered by Amazon, Microsoft, IBM, Equinix, Dell EMC, etc. In general, a cloud-based gaming system is convenient as it provides a robust, centralized control point to connect, monitor, and control multiple gaming jurisdictions. Regardless, the authorized gaming system 108 receives the wagers and then formally places the wagers at gaming apparatus available to the authorized gaming system 108.
The gaming management system 210 can be a computer implemented system that serves to manage gaming operations for one or more gaming apparatus. Typically, the gaming apparatus being managed by the gaming management system 210 are associated with a particular gaming establishment. For example, the particular gaming establishment can correspond to a particular location of the gaming establishment, such as a casino. The conditional wager management system 202 can also interact with a player account management system 212 to provide or receive information and funds concerning a particular player or an agent.
For processing a particular conditional wager, the conditional wager management system 202 can receive condition data from the gaming management system 210. Conditional wagers can be dependent upon various conditions. Some of these conditions can be associated with a gaming environment managed by the gaming management system 210. Hence, the condition data provided to the conditional wager management system 202 from the gaming management system 210 can provide condition data that is associated with the gaming environment being managed by the gaming management system 210.
The conditional wager management system 202 can use the condition data to determine whether the one or more conditions for a given conditional wager have been satisfied. When the conditional wager management system 202 determines that a particular conditional wager has had its condition satisfied, the particular conditional wager can be invoked. When being invoked, the conditional wager is directed to the gaming management system 210 for processing. The gaming management system 210 can receive the incoming conditional wager and cause the conditional wager to be formally placed. In doing so, the gaming management system 210 can interact with the player account management system 212 to confirm that the player has the requisite monetary funds stored and available in a player's account. The placement of the conditional wager can cause a wager to be placed with respect to various different gaming apparatus and gaming events (e.g., sports, e-sports, horse races, a lottery drawing, and the like) that are managed by the gaming management system 210.
As shown in
The conditional wager process 300 can begin with a decision 302 that determines whether a conditional wager has been received. When the decision 302 determines that a conditional wager has not been received, the conditional wager process 300 can await such a wager. Alternatively, when the decision 302 determines that a conditional wager has been received, one or more conditions of the conditional wager can be identified 304. Typically, a conditional wager is a wager that is dependent upon one or more conditions. The identification 304 of the one or more conditions of the conditional wager can involve a parsing of the conditional wager to extract the one or more conditions. Then, the conditional wager process 300 can evaluate 306 the one or more conditions associated with the conditional wager.
Next, a decision 308 can determine whether the one or more conditions associated with the conditional wager have been satisfied. When the decision 308 determines that all of the one or more conditions for the conditional wager have not been satisfied, the conditional wager process 300 can return to repeat the block 306 so that the one more conditions can continue to be evaluated.
On the other hand, when the decision 308 determines that the all the one or more conditions for the conditional wager have been satisfied, the conditional wager can be activated 310. Note that activation of a conditional wager may require that the triggering condition(s) for the conditional wager to be satisfied in addition to the jurisdictional compliance rules associated with the location where the conditional wager is being transacted. Typically, the activation 310 of the conditional wager causes the conditional wager to be made. After the conditional wager has been activated 310, a decision 312 can then determine whether a wager result has been received. When the decision 312 determines that a wager result for the conditional wager has not yet been received, the conditional wager process 300 can await such a wager result. Alternatively, when the decision 312 determines that the wager result for the conditional wager has been received, the conditional wager process 300 can facilitate 314 a notification of the wager result. Typically, the notification of the wager result would be an electronic notification provided to the player that initially placed the conditional wager. Following the block 314, the conditional wager process 300 can end since the conditional wager was activated and the resulting wager result was provided to the corresponding player.
The conditional wager request process 400 can initially identify 402 a player. The player being identified 402 is a player that is attempting to make a conditional wager with respect to a game of chance, such as a wager-based game performed by or at a gaming apparatus. After the player has been identified 402, a decision 404 can determine whether the player has available funds that can be utilized for the conditional wager being attempted. For example, the player can be required to have an account in which monetary funds for the player have been previously deposited. The decision 404 can then determine whether the player has sufficient funds in its account to place the particular conditional wager being attempted. When the decision 404 determines that the player does not have sufficient available funds, the player can be notified 406 that the attempted conditional wager is not permitted due to lack of funds in the player's account. After the player is been notified 406, the conditional wager request process 400 can end as the particular conditional wager being attempted by the player is declined because the player does not have sufficient available funds.
On the other hand, when the decision 404 determines that the player does have sufficient available funds, a wager destination for the conditional wager can be identified 408. In one embodiment, the wager destination can be identified 408 using a graphical user interface (GUI). For example, a GUI can present a plurality of available wager destinations and permit a player to select one or more destinations for their wager. The wager destination can be a particular casino, gaming location, wager-based table game, wager-based gaming machine (e.g., slot machine), etc. Here, for example, a wager destination can represent a gaming establishment where the conditional wager is to be placed. For example, the wager destination could be Crazy A's casino in Las Vegas, Nevada. As another example, the wager destination could be a live table game in Caesar's casino in Las Vegas, Nevada. As still another example, the wager destination could be any wheel of Fortune slot machine in Nevada.
After the wager destination has been identified 408, available conditional wagers associated with the wager destination can be determined 410. Here, different wager destinations can support different conditional wagers. In one embodiment, the conditional wager request process 400 can include a search assistant to allow a player to search for suitable eager destinations depending on the type of game, gaming device, location, performance, pay-out, odds, etc.
After the available conditional wagers have been determined 410, a user interface can then be presented 412 for placing of conditional wagers. The user interface can be displayed to the player attempting to make the conditional wager using, for example, an electronic device such as an electronic gaming device. For example, an electronic device can include a display screen, and the user interface can be displayed on the display screen. The electronic device can, for example, be a mobile device or a conditional wager terminal.
Next, a decision 414 can determine whether a conditional wager has been received. When the decision 414 determines that a conditional wager has not yet been received, the conditional wager request process 400 can await such a wager. Alternatively, when the decision 414 determines that a conditional wager has been received, the conditional wager request process 400 can submit 416 the conditional waiver. For example, the conditional waiver can be submitted 416 to a conditional wager management system, such as a conditional wager management system 104 illustrated in
Thereafter, a decision 418 can determine whether the conditional wager request process 400 is done. In other words, the player can signal to the conditional wager request process 400 whether the player is done making conditional wagers or whether an additional conditional waiver (or modification to a prior conditional wager) is still requested. When the decision 418 determines that the conditional waiver request process 400 is not done, the conditional waiver request process 400 can return to repeat the decision 414 and subsequent blocks so that another conditional wager can be requested. Alternatively, when the decision 418 determines that the conditional waiver request process 400 is done, the conditional waiver request process 400 can end.
The wager management system 500 includes a plurality of conditional wager terminals 502. The conditional wager terminal 502 can, for example, be a kiosk or other electronic device such as noted in
Those of the wager terminal 608 that are positioned in the gaming authorized region 604 can receive and place wagers, namely, conditional wagers, can be receive and actively placed. Once placed, the conditional wager management system 606 can monitor the wagers for satisfaction of any associated conditions on the wager. When the conditional wager management system 606 determines that a conditional wager is ready to be placed (i.e., all conditions are satisfied), the wager is directed to one of the gaming locations 610-614 for invoking or participating in a wager-based game at the gaming location 610-614. Here, in this embodiment, the wager-based games are provided by authorized gaming establishments. The wager-based games can be provided on gaming devices available at the gaming establishments. Alternatively, a gaming server computer can operate a wager-based game on which the wager can be placed.
When the wager terminal 608 is positioned in the gaming unauthorized region 602, the wager terminal 608 is able to receive a wager request, but does not cause any wagers to be placed. Hence, in one embodiment, for wager requests received at the wager terminals 608 that are positioned in the gaming unauthorized region 602, the various wager requests receive at such wager terminal can first be transported to the gaming authorized region 604. For example, a particular wager terminal 608, or a removable data storage device therefrom, can be transported into the gaming authorized region 604 where the various wager requests can then be submitted to the conditional wager management system 606. The transportation of the particular wager terminal 608 (or a removable data storage device therefrom) can, for example, be by a motor vehicle, airplane, train, or carried by a person.
In the embodiment shown in
Players seeking to enter a conditional wager can interact with a bet terminal (BT). The wager management system 700 can support a plurality of bet terminals BT1-BT5. As shown in
Those of the bet terminals that are positioned in the gaming authorized region 704, can receive and actively place bets, namely, conditional bets. Once place, a player and game management system 706 can manage the invocation of the bets and also processing execution of the bets. The player and game management system 706 can include a conditional wager management system 708 that can monitor the bets for satisfaction of any associated conditions on the bets. When the conditional wager management system 708 determines that a conditional bet is ready to be placed (i.e., all conditions are satisfied), the bet is managed by the player and game management system 706. In one embodiment, the player and game management system 706 couples to various gaming locations 708, 710 and 712 to interact with local gaming management systems. For example, the gaming location 712 can include a local gaming management system 714. The player and game management system 706 can interact with the local gaming management system 714 via a gaming interface 716. The local gaming management system 714 supports and manages a plurality of gaming devices, such as gaming tables T1 and T2 as well as gaming machines GM1 and GM2. Gaming data pertaining to wager-based games operating on any of the gaming devices can be stored at the local gaming management system 714. Hence, the player and game management system 706 can process a conditional bet using any of the gaming devices at the gaming location 712 though interaction with the local gaming management system 714.
The local gaming management system 714 can also optionally couple to a player management system 718. The player management system 718 can maintain player accounts for player. Bets can be funded from a player account, and any winnings can be deposited in a player account. Hence, conditions on a bet that are based on a player's account can be evaluated using data available from the player management system 718.
Optionally, the local gaming management system 714 can also couple to a conditional wager manager 720. Hence, instead of using the conditional wager manager 708 which is centrally located, one or more or all conditions of a conditional bet can be evaluated at the gaming location 712 through use of the conditional wager manager 720.
When the bet terminal is positioned in the gaming unauthorized region 702, the bet terminal is able to receive a bet request, but does not cause any bets to be placed. Hence, in one embodiment, for bet requests received at the bet terminals that are positioned in the gaming unauthorized region 702, the various bet requests received at such bet terminal can first be transported to the gaming authorized region 704. For example, a particular bet terminal BT1, or a removable data storage device therefrom, can be transported into the gaming authorized region 704 where the various bet requests can then be submitted to the player and game management system 706. The transportation of the particular bet terminal (or a removable data storage device therefrom) can be by a motor vehicle, airplane, train, or carried by a person. At the player and game management system 706 the bet requests can become conditional bets. For example, any bet requests acknowledged at bet terminal BT1 can become conditional bets after the bet terminals has been transported into the gaming authorized region 704. The player and game management system 706 can manage processing of the bets in accordance with the bet conditions. The bets can be processed using gaming play data provided from a gaming establishment, such as via the gaming management system 714, or provided by a gaming computer provided centrally, such as at the player and game management system.
The wager terminal 800 is suitable for use as a conditional wager terminal 102, 502 illustrated in
In one embodiment, the wager terminal 800 is mobile and can be moved and placed at different locations. For example, the wager terminal 800 can be moved in accordance with a schedule from an unauthorized gaming location to an authorized gaming location. For example, the wager terminal 800 can be placed in a location where bets cannot be made but where bets requests can be received, then later the wager terminal 800 can be moved to a location where wagers can be placed. Thus, when at the authorized wagering location, the wager terminal 800 can facilitate the activation or placement of the requested bets that had been previously received by the wager terminal 800. In such an embodiment, it can be advantageous for the wager terminal 800 to include a location detection subsystem. The location detection subsystem can be used to verify the location of the wager terminal 800, such as to ensure that the wager terminal 800 is indeed at an authorized gaming location. For example, the location detection subsystem can be a GPS subsystem.
In still another embodiment, a personal digital assistant (e.g., smartphone, tablet computer, smart watch, etc.) can be used in place of the wager terminal. In such an embodiment, the personal digital assistance can operate as a wager terminal. By running an application program, the personal digital assistant can provided the functionality and user interface for facilitating a user in entering, configuring, funding, and/or managing wagers.
For security or audit purposes, the wager terminal 800 can record (i) its location when a wager is received or received, (ii) its location when a wager's conditions are satisfied, and/or (iii) its location when a wager is activated. Such data can be recorded in a log file or a database.
The type of wager being permitted by the wager terminal 800 can be controlled or managed. For example, the wager terminal 800 might support wagers that are conditional wagers, primary wagers, back bet wagers, auxiliary wagers, related or parleyed wagers, or any combination thereof.
The wager terminal control system 900 also includes a wager builder 904, and a wager submission manager 906. Using the wager builder 904, the wager terminal can present a graphical user interface for the user so that through interaction therewith the user can enter one or more desired wagers. In one implementation, a wager being entered is a conditional wager that is dependent upon one or more conditions. The wager can also be part of a plurality of related wagers, which can pertain to a script. The script can be commands or instructions for carrying out the related wagers. One or more of the related wagers can be conditioned upon various conditions. The related wagers can also implement a parley wager.
In the case of parleyed wagers, the wager builder 904 can facilitate interrelating of conditional wagers for obtaining greater potential winnings. The wager builder 904 can provide visual assistance to a user in selecting or creating a parley wager, such as from a series of conditional wagers. For example, a first conditional bet can be entered, and then a second conditional bet can be entered and funded (or funded differently) if the first conditional bet is successful.
After the one or more wagers have been entered using the wager builder 904, the wager submission manager 906 can manage submission of the requested wagers to an appropriate wager management system to carry out the wagers. The wager submission manager 906 can, in one embodiment, directly submit the wagers to the appropriate wager management system once the wager have been entered or received via the wager builder 904. Alternatively, in another embodiment, the wager submission manager 906 can retain the wagers until certain conditions are met. For example, one condition might be a location of the wager terminal being utilized to receive the wagers, where the wager terminal is a mobile wager terminal. In such case, the wager terminal might retain the wagers until the wager terminal 900 is in a location that permits the requested wagers. In this regard, the wager terminal control system 900 can include a position detecting unit 910. The position detecting unit 910 can use location detection techniques, such as triangulation, GPS, network (Wi-Fi, cellular, and the like), etc. to determine the location of the wager terminal.
In an alternative embodiment, the wager terminal might support a removable electronic wager storage device. The removable electronic wager storage device could be removed from the wager terminal and moved to a different location where the previously received wagers are eligible to be placed. This, advantageously, would permit the wager terminal to remain in an unauthorized gaming location while the previously received wagers are able to be moved to an authorized gaming location by moving the removable electronic wager storage device.
The wager terminal of the wager terminal control system 900 is particularly suitable for conditional wagers which are wagers that are dependent upon one or more conditions. In such case, the wager builder 904 can be referred to as a conditional wager builder, and the wager submission manager 906 can be referred to as a conditional wager submission manager.
In a first state 1002, the user can interact with a user interface to identify a player account. The player account is the account that is used to identify the player seeking to make a wager. In the event that the player account is not already established, the first state 1002 can also assist the user in making a player account.
After the player account has been identified in the first state 1002, the state diagram 1000 proceeds to a second state 1004. At the second state 1004, money can be added to the player account. The second state 1004 is optional because the user may not need or desire to add money to the player account at this time.
Following the second state 1004, the state diagram 1000 can return to the first state 1002. Additionally, following the first state 1002, the state diagram 1000 can also proceed to a third state 1006. At the third state 1006, the user can browse available conditional wagers. Although the available wagers are identified as being conditional, it should be recognized that in other embodiments, the available wagers need not be conditional. In any event, in the third state 1006, the user can interact with the user interface to browse through the available conditional wagers. The available conditional wagers can be searched or browsed or filtered to assist a user in locating the particular type of conditional wager that is desired.
Following the third state 1006, the state diagram 1000 can proceed to a fourth state 1008. At the fourth state 1008, the user can select or create a conditional wager. Here, based on the available conditional wagers, the user can select one or more of the available conditional wagers as the selected conditional wager. Alternatively, the user could create a particular conditional wager from the available conditional wagers or from wagering opportunities that are made available to the user using the user interface.
After the conditional wager has been selected or created, the state diagram 1000 can proceed to a fifth state 1010. At the fifth state 1010, the selected conditional wager can be submitted. For example, the selected conditional wager can be submitted to a conditional wager management system, such as a conditional wager management system 202 illustrated in
The state diagram 1000 also includes a sixth state 1012. The sixth state 1012 is a wait state in which the state diagram 1000 waits for the user to desire to make a conditional wager or desire to receive results of previously made wagers.
Furthermore, the state diagram 1000 includes a seventh state 1014. At the seventh state 1014, wager results can be retrieved. Here, for example, for previously submitted conditional wagers, the state diagram 1000 can provide a user interface that allows the user or player to receive the results of such wagers. Hence, at the seventh state 1014, the wager results are retrieved from a conditional wager management system, such as the condition wager management system 202 illustrated in
In one embodiment, a graphical user interface enables a player to direct its conditional bet to a particular gaming establishment. The gaming establishments can make wager opportunities available to players that are authorized for gaming. For example, the available gaming establishments can be dependent on an actual or anticipated location of the player. If the conditional bet is destined for game play in Nevada, then the conditional bet can be made with any authorized gaming establishment in Nevada that is participating with the condition betting system.
The available bet conditions can be controlled or managed by participating gaming establishments. This enables a gaming establishment to motivate game play on certain games at particular times, particular machines, particular locations or establishments, etc.
Another aspect of one or more embodiments is a graphical user interface. The graphical user interface is provided to facilitate the placing of a wager, such as a conditional bet. The conditional bet can be defined by a plurality of betting conditions that are dependent on various parameters. The graphical user interface can be presented to a player via an electronic device, such as a mobile communication device (e.g., smart phone), a gaming apparatus, or some other electronic device. Typically, such devices include or associate with a display device which can present the graphical user interface.
One example of a multi-level GUI is as follows:
As noted herein, wagers (or bets) can be conditional based on one or more conditions. The conditions can vary widely based on implementation. Examples of parameters used in conditions include the following: Gaming Device Type; Game; Jackpot/Bonus Level; Performance; Environmental Conditions; Incentives; Loss Limit; Gaming Location; Gaming Establishment; and Player Confirmation.
Exemplary types of gaming devices include gaming tables (live or electronic), slot machines, and video gaming machines. These gaming devices support wager-based games or, more generally, games of chance.
Exemplary games are wager-based games, of which there can be many, including poker, blackjack, baccarat, craps, pai gow, roulette, and numerous slot machine games (e.g., Wheel of Fortune). Those particular games that are available can be dependent on a type of gaming device. For example, if the type of gaming device is a slot machine, then the available games are those games that are available on slot machines. For example, one popular slot machine game is Wheel of Fortune. As another example, if the type of gaming device is a video gaming machine, then the available games are those games that are available on video gaming machines. For example, popular games on video gaming machines include poker and keno. As another example, if the type of gaming device is a table game, then the available games are those games that are available on table games. For example, popular games on table games include poker, blackjack, baccarat, craps, pai gow, and roulette.
Another condition that can be available is a jackpot/bonus level which can be used to condition a wager on the level of an available jackpot or bonus. For example, a particular wager could be conditioned on the available jackpot being greater than a monetary amount, such as one million dollars.
Exemplary performance conditions can include last payout amount by gaming device, recent near miss, time since last jackpot or bonus, etc. The performance can also be considered relative to other gaming devices generally or restricted to same or like types of gaming devices. For example, a particular gaming device could be ranked relative to other like gaming devices. As another example, by evaluating a gaming device, the gaming device could be classified as hot, cold or neutral and then conditions could rely on the performance classifications hot, cold or neutral.
Exemplary environmental conditions can include day, time, frequency, player streak, player account level (e.g., player account balance), and player account performance.
Incentive conditions can be made available to a user. Establishments or service providers can offer incentives to play at certain times, certain locations (e.g., establishments or areas within an establishment), certain games, certain gaming device, etc. A user can thus use incentive conditions to condition a wager on such incentives. For example, a contingent wager could be placed once an incentive condition is triggered.
Exemplary loss limit conditions can include conditions to cease wagers if recent losses (hourly, daily, weekly, monthly or yearly) exceed a loss limit (monetary or percentage).
An exemplary player confirmation condition can be a user confirmation that is used as a condition to a bet. For example, a user (player) can be contacted, such as via phone, text or email, to inquire whether an available bet should be placed. If the user declines to confirm, then the bet can be delayed. In some embodiments, the confirmation condition may only be available in certain gaming jurisdictions (e.g., Nevada). In other words, the confirmation condition may only be available in jurisdictions that permit a wager to be confirmable. For example, a user could receive a text, that its wager's conditions are met can the wager is ready to be activated, and can indicate where the wager is to be played (e.g., Treasure Island Casino, Las Vegas, Slot Machine #1234), and permits the user to “decline” or “pass” the activation if they desire. Typically, the user would have to rapidly reply to the text message to stop the wager's activation. But in some situation, the wager could be default not be activated, unless the user positively reply's that the wager should be activated.
A wager that is conditional can be a back bet of a player that plays a wager-based game. The wager of the back better that is being offered in such case is dependent on the play of the player. In such case, additional conditionals such as the following might be used: Player Performance, Player Rating, and/or Gaming Device Conditions (of gaming device that player is playing). For example, Player Performance can support conditions such as recent streaks, historical performance (general, gaming session, game type, etc.). Player Rating can be assigned to provide relative rating of players. The Gaming Device Conditions can, for example, support one or more conditions dependent on a payout history, pay tables, streaks, etc. Hence, the conditions applied to a bet, such as a back bet, can be used in selecting a player or machine for use with the bet.
A wager could also be made conditional on a dealer, such as dealer's performance, in the case of a live dealer game.
In another embodiment, a multi-conditional wager can be described using a script. The script can include commands or instructions for carrying out a multi-conditional wager, which can include a plurality of bets, such as related bets, string or streak bets, or parley bets. In one implementation, a wager builder (e.g., wager builder 904) can be used to assist a player in creating a script.
The script can define a bet to be placed dependent on a plurality of conditions. A graphical user interface, such as a touch screen interface, can be used to facilitate creation of scripts. Any of the conditions discussed herein can be utilized in a script. Further, a script can be used to define a parley bet by relating together a plurality of bets. The graphical user interface could also include a visualization (e.g., animation) of a script for enhanced player understanding and excitement.
A script can be represented visually for a user. The script as provided to a conditional wager management system can be in a scripting language. For example, a series of bets can be scripted using a graphical user interface and then subsequently effectuated by the conditional betting system as appropriate. A script submitted to a conditional wager management system can define one or more distinct conditional bets, or one or more conditional bets (e.g., a parley conditional bet).
As one example, suppose a player wants to make a parley conditional bet such that a first bet of $100 is conditional on a first live table game of blackjack and on a “cold” dealer, and then if that first bet is successfully a second bet of $20, repeatable up to 5 times, on a progressive slot machine conditional on a progressive jackpot level being at least $10,000,000 and on the Wheel of Fortune game and at a frequency of not more than one bet per hour.
As another example, suppose a player want to make a parley conditional bet such that a first bet of $100 on “red” on a table game of roulette (of any kind) conditioned on player account balance greater than $1000, and then if the first bet is successful a second bet of one-half of winnings from the first bet are placed on “black” on a subsequent table game of roulette. The parley can also be designated to repeat until a bet is lost.
A server computer can process a betting script. The betting script syntax and command can be recognized by the server computer. An exemplary natural language script is:
A player can also use an application operating on a personal computing device, such as a smart phone or tablet or notebook computer, to make a bet request. If the player is in an unauthorized gaming region, then the bet request is held. The bet request can later be delivered to a bet terminal. Then, if (or when) the bet terminal is in an authorized gaming location, the bet requested can become a placed bet.
Alternatively, the bet request can be transported from an unauthorized gaming location to an authorized gaming location by a person. For example, referencing
Proxy Play
In another aspect disclosed herein, wagers (or bets) can be made on behalf of a remote player by a proxy. In this scenario, a proxy is a person that plays a wager-based game for a remote player. Various proxies can make themselves available for proxy play, where bets are placed on wager-based games by a proxy for a player.
A person desiring to serve as a proxy can be qualified to be a proxy. A proxy can specialize in particular games or locations. A proxy posts their availability to serve as a proxy with a Proxy Play Management System (PPMS). The PPMS manages assignment of proxies to play [i.e., place bets] for one or more particular remote players.
A proxy can be compensated for their efforts in assisting remote players in any of one or more of a variety of ways. A remote player can elect to tip their proxy player. A proxy can also be compensated by a percentage of winnings. The PPMS or gaming locations/establishments can also provide some form of compensation to a proxy, such as per player, per bet played, per bet won, etc. Some proxy players can also be paid greater than other proxy players, such as due to more experience, better performance, more desirable gaming locations served, or greater luck. The compensation can also differ for different wager-based games or types of wager-based games. The compensation can be fixed or dynamic based on factors.
A remote player can queue up one or more bets to one or more wager-based games. This can be done anywhere that a remote player has network assess to post his/her bets with the PPMS. The PPMS can automatically assign a proxy. Alternatively, a remote player might select from different available proxies. Proxies can have profiles, rating, reviews, etc. to assist remote players in choosing a proxy. For example, a proxy can have a general performance rating and/or a performance rating for acting as a proxy on your behalf. Also, geographical location of a proxy can impact when assignments are given.
Once a proxy is assigned or selected, the proxy is informed of a gaming assignment, including gaming destination, wager-based game and bet. The PPMS can manage the communication with the selected proxy. The proxy can also be given a time window to complete the gaming assignment.
The proxy then travels to the gaming destination and causes placement of the requested bet on the wager-based game for the associated remote player. Once the proxy causes the proxy bet to be made, the PPMS can record the game play and results. The bet amount can be withdrawn from the remote player's player account, and any winnings can be deposited in the remote player's player account.
The proxy typically carries a portable electronic device, such as a smart phone, notebook computer or tablet computer. An application program (e.g., “App”) is typically operating on the portable electronic device so that the proxy can securely interact with the PPMS. In carrying out a proxy assignment, the App can serve to guide the proxy. In one embodiment, an App can present step-by-step instructions to the proxy. For example, the App can direct the proxy to an appropriate wager-based game on which the requested bet is to be played. An identified (e.g., PPID) can be provided to the appropriate wager-based game and then the bet can be automatically played or preconfigured for confirmation and then played once confirmed.
In one embodiment, a proxy can be giving a temporary proxy player ID (“PPID”) for remote play for a particular remote player. Through use of the PPID, the proxy informs a gaming apparatus that the proxy is playing for a remote player. The PPID is linked to the remote player's player account so that the gaming apparatus understands who the real player is. The PPID can also be used by the gaming apparatus (or its management system) to retrieve the requested bet from the PPID. The PPID can be provided on a proxy card, QR code, passcode, or an electronic value. Alternatively, the gaming apparatus could communicate with the App of the proxy (or a remote server) to retrieve the requested bet.
In another embodiment, a gaming device can provide instructions to the proxy on bet to be placed. For example, the gaming device can be a slot machine and after a PPID is provided to the gaming device, the gaming device can display instructions to the proxy. For example, the gaming device can have a display that presents the instructions. The display can be part of the gaming device base devices, or can be part of a peripheral device (e.g., Ticket-In-Ticket-Out; Player Tracking Device).
In a more complicated proxy bet request, the proxy bet request might be limited or conditional on one or more conditions. Various suitable conditions are described herein. In one embodiment, a script bet sequence can be provided as a proxy bet request. In one implementation, the script can be “run” on the proxy's App and/or a gaming apparatus to guide the proxy in effectuating the proxy bet request. In another embodiment, the script can be run by the PPMS or other management system to automatically effectuate the proxy bet requests of the script. A script can, for example, be used to make a series of requested bets. The series of requested bets can be contingent on one another or can be a parley bet.
A remote player can be provided with feedback to processing of its requested bet. The feedback can include game play results. The feedback can be captured by screen capture or video of actual game play, or animated or virtualized representation of game play. The real video can be captured by the gaming device or via the proxy's app. The feedback can also include other information besides game play, such as positional feedback of the proxy when in the process of effecting the proxy bet request, electronic notifications (e.g., text notifications or in-app notifications using a player App) of relevant events (e.g., proxy accepts, proxy arrived at destination gaming location, proxy logged into gaming device having wager-based game, game results, etc.
Multi-Player Proxy Play
In one embodiment, the proxy bet request can be associated with a group of players. Each player can represent a percentage of an effectively combined remote player. The PPMS can provide feedback to each of the players in the group of players.
Real-Time Betting with Active Proxy
In one embodiment, potential remote persons can be alerted of impending bet opportunities that they might participate in. In this regard, the potential remote persons can be informed of a wager-based game about to be played and an opportunity for having the proxy also play on your behalf. The information provided to the potential remote persons can include performance information of the particular gaming device involved and/or the proxy.
The proxy play request process 1200 can begin with a decision 1202 that determines whether a proxy play request has been received. Here, the proxy play request is a play request from a player, namely, a remote player, that is being submitted so that a proxy can be assigned to perform the play request on behalf of the player. The play request is typically associated with a wager-based game. Hence, a proxy play request can also be referred to as a proxy bet request or a proxy wager request. When the decision 1202 determines that a proxy play request has not yet been received, the proxy play request process 1200 can await such a request.
Once the decision 1202 determines that a proxy play request has been received, a remote player and/or a proxy play request can be validated 1204. The validation can be provided in various different ways. In one implementation, the remote player can be validated against a player account. The proxy play request can be validated by authentication of the remote player. The proxy play request can be validated using encryption and secure communication over a network. The proxy play request can also be validated that the request proxy play is supported by the PPMS. Next, a decision 1206 determines whether the validation was successful. When the decision 1206 determines that the validation was not successful, then the proxy play request can be denied 1208. Following the denial 1208 of the proxy play request, the proxy play request process 1200 can end.
On the other hand, when the decision 1206 determines that the validation was successful, a proxy can be assigned 1210. Here, the proxy being assigned 1210 can be any of a plurality of proxies that are presently available or are available at the appropriate time for performance of a proxy play request. The available proxies are typically dependent upon location or gaming establishment to which the proxy play request is directed or assigned to be performed. However, proxy assigning can additionally or alternatively be dependent on type of game, proxy performance or rating, etc.
After a proxy has been assigned 1210, proxy instructions can be delivered 1212 to the proxy. The proxy instructions can advise or guide the proxy in performance of the proxy play request that the proxy has been assigned to perform. Next, a decision 1214 can determine whether a wager has been played. Here, the wager that is to be played is a wager associated with the proxy play request. Hence, when the decision 1214 determines that a wager is not yet been played, then the proxy play request process 1200 awaits the play of a wager by the proxy. Once the decision 1214 determines that a wager has been played by the proxy in the context of performing the proxy play request, the proxy play request process 1200 can continue. In this regard, wager results associated with the wager that is been played are stored 1216. In addition, the player account associated with the remote player that has made the proxy play request can be updated 1218. For example, the player account can be debited with any winnings that have resulted from the wager being played. Next, the remote player can be notified 1220 of the wager results.
Thereafter, a decision 1222 can determine whether the proxy play request 1200 is complete. When the decision 1222 determines that the proxy play request 1200 is not complete, the processing returns to repeat the block 1212 so that additional instructions can be provided to the proxy and/or wagers can be played. On the other hand, when the decision 1222 determines that the proxy play request 1200 is complete, the proxy play request 1200 can end.
The player application process 1300 can begin with a decision 1302 that determines whether a proxy bet is desired. When the decision 1302 determines that a proxy bet is not desired, the player application process 1300 can await the player's desire to make a proxy bet.
Once the decision 1302 determines that a proxy bet is desired, a proxy bet graphical user interface can be displayed 1304. The proxy bet graphical user interface is an interface that assists the player is arranging a proxy bet. At this point, a decision 1306 can determine whether a player selection has been made with respect to the graphical user interface. When the decision 1306 determines that a player selection has been received, the proxy bet graphical user interface can be updated 1308. Following the update 1308, the player application process 1300 can return to repeat the decision 1306 so that additional player selections can be received and processed.
On the other hand, when the decision 1306 determines that a player selection is not been received, a decision 1310 can determine whether the player is done interacting with the proxy bet graphical user interface. When the decision 1310 determines that the player is not done interacting with the proxy bet graphical user interface, the player application process 1300 can return to repeat the decision 1306 and subsequent blocks.
Alternatively, when the decision 1310 determines that the player is done interacting with the proxy bet graphical user interface, a confirmation screen can be displayed 1312. Next, a decision 1314 determines whether the proxy bet is confirmed by the player. When the decision 1314 determines that the proxy bet is not confirmed, then the player application process 1300 returns to repeat the decision 1302 and subsequent blocks so that another proxy bet, if desired, can be created. On the other hand, when the decision 1314 determines that the proxy bet is confirmed, a proxy bet request including the confirmed proxy bet can be submitted 1316 to a proxy player management system. Following the submission 1316 of the proxy bet request, the player application process 1300 can end.
The proxy application process 1400 can begin with a decision 1402 that determines whether a proxy desires to post their availability. When the decision 1402 determines that a proxy desires to post their availability, availability information of the proxy can be received 1404. Here, the proxy can interact with the proxy application to provide the availability information of the proxy. The availability information can indicate that the proxy is presently available to handle proxy assignments, and/or can indicate that the proxy will be available to handle proxy assignments according to a schedule that they have set up or approved. The available information can also restrict proxy assignments to certain games, geographical area, and/or gaming establishments. Next, the availability information can be transmitted 1406 to the proxy player management system (PPMS). Following the block 1406, the proxy application process 1400 can end.
Alternatively, when the decision 1402 determines that the proxy does not desire to post their availability, a decision 1408 can determine whether a proxy assignment has been received 1408. A proxy assignment that has been received is, for example, a proxy assignment established by the proxy player management system (PPMS) and assigned to the proxy. When the decision 1408 determines that a proxy assignment has been received, the proxy assignment can be added 1410 to a proxy assignment queue for the proxy. In some cases, the proxy can be permitted to accept or decline the proxy assignment before it is formally added to the proxy assignment queue for the proxy. In any event, after the proxy assignment has been added 1410 to the proxy assignment queue, the proxy can be notified 1412. Typically, the proxy application can present a notification that serves to notify 1412 the proxy of the proxy assignment that has been received for the proxy. Following the block 1412, the proxy assignment process 1400 can end.
Additionally, when the decision 1408 determines that a proxy assignment has not been received, a decision 1414 can determine whether the proxy desires to view proxy assignments for the proxy. When the decision 1414 determines that the proxy assignments are to be viewed, the proxy assignments can be retrieved from the proxy assignment queue associated with the proxy and displayed 1416. A decision 1418 can then determine whether the proxy has made an activation selection. An activation selection is a selection by the proxy to activate a particular one of the proxy assignments that are present in the proxy assignment queue. When the decision 1418 determines that an activation selection has not been made, the proxy application process 1400 can end.
On the other hand, when the decision 1418 determines that an activation selection has been made, additional processing can be performed to carry out the proxy assignment that is being activated. The additional processing is, for example, processing illustrated in
The additional processing can present 1420 proxy assignment information. The proxy assignment information is information that is provided to the proxy to inform the proxy of the particular proxy. The proxy assignment information can describe the proxy bet to be made, the location of the proxy bet, the game involved in the proxy bet, the time of day for the proxy bet, directions to the location or game, and the like. Next, decision 1422 can determine whether the proxy wishes to decline the proxy assignment. In this embodiment, the proxy is permitted to decline the proxy assignment. When the decision 1422 determines that the proxy desires to decline the proxy assignment, the proxy player management system can be notified 1424 of the declined proxy assignment. Alternatively, if the decision 1422 determines that the proxy is not declining the proxy assignment, then proxy assignment guidance information can be displayed 1426 to the proxy. For example, the portable electronic device associate with the proxy can include a display screen on which the proxy assignment guidance information can be displayed. The proxy assignment guidance information can include instructions on how to carry out the proxy assignment. For example, the proxy assignment guidance information can direct the proxy to the appropriate gaming apparatus, gaming establishment, etc. The proxy assignment guidance information can also inform the proxy of the particular wager to be placed.
The proxy assignment process 1400 can also record 1428 performance of the proxy assignment. The performance of the proxy assignment can include data indicating that various stages of the proxy assignment have or have not been completed. Such data can permit the proxy player management system to monitor completion of different parts or stages of performance of the proxy assignment. The performance of the proxy assignment can also record that the wager was placed and the result of the wager, such as the amount of winnings, if any. The recordation 1428 can store alphanumeric data, audio/video data, or both. Thereafter, a decision 1430 can determine whether the proxy assignment has been completed. When the decision 1430 determines that the proxy assignment has not yet completed, the proxy application process 1400 can return to repeat the block 1426 and subsequent blocks so that the proxy assignment can continue to be processed and the proxy can receive further guidance. Alternatively, when the decision 1430 determines that the proxy assignment has been completed, the proxy application process 1400 can end. Additionally, following the block 1424 where the proxy assignment was declined, the proxy application process 1400 can also directly end.
The wager control process 1500 can begin with a decision 1502 that determines whether gaming is authorized. The decision 1502 can determine whether gaming is authorized for the player application operating on a portable electronic device associated with the player. For example, gaming can be authorized if the portable electronic device and thus the player application and player are in a gaming authorized location. This can be determined based on the location of the portable electronic device. In any event, when the decision 1502 determines that gaming is not authorized, the wager control process 1500 can continue to evaluate whether gaming is authorized such that at some later point in time gaming can be authorized.
On the other hand, when the decision 1502 determines that gaming is authorized, a decision 1504 can determine whether a real-time wager is to be played. Here, if gaming is authorized, the player application can support a real-time wager. Hence, in such case, the decision 1504 can determine whether the player desires to make a real-time wager. When the decision 1504 determines that the player does desire to make a real-time wager, then a real-time wagering graphical user interface (GUI) can be displayed 1506. The real-time wagering GUI can, for example, be a multilevel GUI, similar to the multi-level condition bet GUI discussed above, though bets need not be conditional. Using the real-time wagering GUI, one or more real-time wagers can be requested and processed 1508.
On the other hand, when the decision 1504 determines that the player does not desire to make a real-time wager, then a decision 1510 can determine whether to convert a previously established proxy wager into a real-time wager. In one embodiment, the player application (or other software or systems) can allow the player to make a proxy wager. Hence, the wager control process 1500 can allow the player to convert a previously established proxy wager that has not yet been performed into a real-time wager that can be currently performed given that the player is presently at a gaming authorized location. In this regard, when the decision 1510 determines that a previously established proxy wager is to be converted into a real-time wager, then a pending proxy wager to be converted can be selected 1512. Next, the selected pending proxy wager can be converted 1514 into a real-time wager. Thereafter, the real-time wager can be processed 1516.
Further still, when the decision 1510 determines that a previously established proxy wager is not to be converted into a real-time wager, a decision 1518 can determine whether a previously deferred wager is to be activated. When the decision 1518 determines that a previously deferred wager is to be activated, then a deferred wager to be activated can be selected 1520. Then the selected deferred wager can be activated 1522. The activation of the selected deferred wager causes the previously deferred wager to be invoked and thus performed. Following the blocks 1508, 1516 and 1522, as well as following the decision 1518 when a deferred wager is not to be activated, the wager control process 1500 can end.
In other bet result notifications, the visual graphic can be a video clip, an animation, or a picture. For example, the video clip can pertain to the execution of the bet, either the entire game play or selective parts thereof. The game apparatus can be a gaming table (physical or electronic) and the game type can be poker, in which can the visual graphic pertains to the play of a hand of poker. The game apparatus might be a server computer and the game type can be a sporting event (e.g., particular play, parley bet, etc.), in which case the visual graphic can pertain to relevant play(s) of the sporting event.
Additionally, it may be that the wager is not provided to the bet/gaming server until the User's A (and/or the User A's PGD) has reached a gaming permitted jurisdiction, such as Nevada. Hence, operation 2004 could be delayed until step (3) which is when the User A's PGD enters Nevada. Alternatively, the operation 2004 could be further delayed until the User's A PGD reaches a gaming establishment, such as Casino A or Casino B, as shown as steps (5) or (7) shown in
Back Betting
In one embodiment, the conditional bet or proxy bet can also be a back bet. For example, the bet can be configured to be a back bet. The back bet can be implemented by a kiosk, a proxy, or a player. In one implementation, a conditional bet can include at least one condition that is dependent on a primary bet, primary gaming apparatus or primary player, or performance of the primary gaming apparatus or primary player (e.g., winning streak), and thus the conditional bet can be a back bet relative to the primary bet or the primary player.
Robotic Play
In another embodiment, a player, typically a remote player, can select or be assigned a robot present at a gaming location to perform actions to make wagers on behalf of the remote player. The robot can be assigned to perform a bet for a remote player. The robot can serve as a proxy. The bet can, optionally, be a conditional bet. The robot can be automated to perform a bet without player assistance, or the player can be permitted to control some or all actions of the robot. The robot can be a physical robot or a virtual robot.
Drone Play
In still another embodiment, a remote player can make use of a drone that serves as a proxy or as a device assisting a proxy.
This application claim priority of U.S. Pat. No. 9,600,976, filed Mar. 21, 2017, and entitled “ADAPTIVE MOBILE DEVICE GAMING SYSTEM”, which is hereby incorporated by reference herein.
The various aspects, features, embodiments or implementations of the invention described above can be used alone or in various combinations.
Embodiments of the invention can, for example, be implemented by software, hardware, or a combination of hardware and software. Embodiments of the invention can also be embodied as computer readable code on a computer readable medium. In one embodiment, the computer readable medium is non-transitory. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of the computer readable medium generally include read-only memory and random-access memory. More specific examples of computer readable medium are tangible and include Flash memory, EEPROM memory, memory card, CD-ROM, DVD, hard drive, magnetic tape, and optical data storage device. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
Numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will become obvious to those skilled in the art that the invention may be practiced without these specific details. The description and representation herein are the common meanings used by those experienced or skilled in the art to most effectively convey the substance of their work to others skilled in the art. In other instances, well-known methods, procedures, components, and circuitry have not been described in detail to avoid unnecessarily obscuring aspects of the present invention.
In the foregoing description, reference to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Further, the order of blocks in process flowcharts or diagrams representing one or more embodiments of the invention do not inherently indicate any particular order nor imply any limitations in the invention.
The many features and advantages of the present invention are apparent from the written description. Further, since numerous modifications and changes will readily occur to those skilled in the art, the invention should not be limited to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.
This application is a continuation-in-part of U.S. patent application Ser. No. 16/590,347, filed Oct. 1, 2019, and entitled “ADAPTIVE MOBILE DEVICE GAMING SYSTEM”, which is hereby incorporated by reference herein, and which in turn is a continuation of U.S. patent application Ser. No. 16/143,428, filed Sep. 26, 2018, and entitled “ADAPTIVE MOBILE DEVICE GAMING SYSTEM” (now U.S. Pat. No. 10,445,978, which is hereby incorporated by reference herein, and which in turn is a continuation of U.S. patent application Ser. No. 15/427,291, filed Feb. 8, 2017, and entitled “ADAPTIVE MOBILE DEVICE GAMING SYSTEM” (now U.S. Pat. No. 10,115,263), which is hereby incorporated by reference herein, and which in turn is a continuation of U.S. patent application Ser. No. 14/211,536, filed Mar. 14, 2014, and entitled “ADAPTIVE MOBILE DEVICE GAMING SYSTEM” (now U.S. Pat. No. 9,600,976), which is hereby incorporated by reference herein, and which in turn claims priority to (i) U.S. Provisional Patent Application No. 61/873,300, filed Sep. 3, 2013, and entitled “ADAPTIVE MOBILE DEVICE GAMING SYSTEM”, which is hereby incorporated by reference herein; and (ii) U.S. Provisional Patent Application No. 61/799,862, filed Mar. 15, 2013, and entitled “ADAPTIVE MOBILE DEVICE GAMING SYSTEM”, which is hereby incorporated by reference herein. This application is a divisional of U.S. patent application Ser. No. 16/248,759, filed Jan. 15, 2019, and entitled “GAME MANAGEMENT FOR MOBILE AND REMOTE GAMING DEVICES”, which is hereby incorporated by reference herein, and which in turn claims priority to U.S. Provisional Patent Application No. 62/617,579, filed on Jan. 15, 2018 and entitled “GAME MANAGEMENT FOR MOBILE AND REMOTE GAMING DEVICES,” which is hereby incorporated herein by reference.
| 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 |
| 4969183 | Reese | Nov 1990 | A |
| 5067712 | Georgilas | Nov 1991 | A |
| 5275400 | Weingardt | Jan 1994 | A |
| 5429361 | Raven et al. | Jul 1995 | A |
| 5489103 | Okamoto | Feb 1996 | A |
| 5618232 | Martin | Apr 1997 | A |
| 5630757 | Gagin | May 1997 | A |
| 5655961 | Acres et al. | Aug 1997 | A |
| 5704835 | Dietz, II | Jan 1998 | A |
| 5727786 | Weingardt | Mar 1998 | A |
| 5833537 | Barrie | Nov 1998 | A |
| 5842921 | Mindes | Dec 1998 | A |
| 5919091 | Bell et al. | Jul 1999 | A |
| 5947820 | Morro et al. | Sep 1999 | A |
| 5997401 | Crawford | Dec 1999 | A |
| 6001016 | Walker et al. | Dec 1999 | A |
| 6039648 | Guinn et al. | Mar 2000 | A |
| 6059289 | Vancura | May 2000 | A |
| 6089977 | Bennett | Jul 2000 | A |
| 6095920 | Sudahiro | Aug 2000 | A |
| 6110041 | Walker et al. | Aug 2000 | A |
| 6142872 | Walker et al. | Nov 2000 | A |
| 6146271 | Kadici | Nov 2000 | A |
| 6146273 | Olsen | Nov 2000 | A |
| 6165071 | Weiss | Dec 2000 | A |
| 6231445 | Acres | May 2001 | B1 |
| 6244958 | Acres | Jun 2001 | B1 |
| 6270412 | Crawford et al. | Aug 2001 | B1 |
| 6290600 | Glasson | Sep 2001 | B1 |
| 6293866 | Walker et al. | Sep 2001 | B1 |
| 6353390 | Beri et al. | Mar 2002 | B1 |
| 6364768 | Acres et al. | Apr 2002 | B1 |
| 6404884 | Marwell et al. | Jun 2002 | B1 |
| 6416406 | Duhamel | Jul 2002 | B1 |
| 6416409 | Jordan | Jul 2002 | B1 |
| 6443452 | Brune | Sep 2002 | B1 |
| 6491584 | Graham et al. | Dec 2002 | B2 |
| 6500067 | Luciano | Dec 2002 | B1 |
| 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 |
| 6675152 | Prasad | Jan 2004 | B1 |
| 6699128 | Beadell | Mar 2004 | 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 | 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 |
| 7742996 | Kwan | Jun 2010 | B1 |
| 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 |
| 8276010 | Vavilala | Sep 2012 | B2 |
| 8282475 | Nguyen et al. | Oct 2012 | B2 |
| 8323099 | Durham et al. | Dec 2012 | B2 |
| 8337290 | Nguyen et al. | Dec 2012 | B2 |
| 8342946 | Amaitis | Jan 2013 | B2 |
| 8393948 | Allen et al. | Mar 2013 | B2 |
| 8403758 | Hornik et al. | Mar 2013 | B2 |
| 8430745 | Agarwal et al. | Apr 2013 | B2 |
| 8461958 | Saenz | Jun 2013 | B2 |
| 8465368 | Hardy et al. | Jun 2013 | B2 |
| 8469813 | Joshi | Jun 2013 | B2 |
| 8529345 | Nguyen | Sep 2013 | B2 |
| 8597108 | Nguyen | Dec 2013 | B2 |
| 8602875 | Nguyen | Dec 2013 | B2 |
| 8613655 | Kisenwether et al. | Dec 2013 | B2 |
| 8613659 | Nelson et al. | Dec 2013 | B2 |
| 8678901 | Kelly | Mar 2014 | B1 |
| 8696470 | Nguyen | Apr 2014 | B2 |
| 8745417 | Huang et al. | Jun 2014 | B2 |
| 8821255 | Friedman | Sep 2014 | B1 |
| 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 |
| 9165422 | Barclay | Oct 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 |
| 9666015 | Acres | May 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 |
| 10796679 | Powell | Oct 2020 | B1 |
| 10818133 | Nguyen | Oct 2020 | B2 |
| 20010004607 | Olsen | Jun 2001 | A1 |
| 20010016516 | Takatsuka | Aug 2001 | A1 |
| 20010024971 | Brossard | Sep 2001 | A1 |
| 20010025272 | Mori | Sep 2001 | A1 |
| 20010031659 | Perrie | Oct 2001 | A1 |
| 20010037211 | McNutt | Nov 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 |
| 20020107799 | Hoshino | 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 |
| 20020145051 | Charrin | 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 |
| 20030003988 | Walker | Jan 2003 | A1 |
| 20030003996 | Nguyen | Jan 2003 | A1 |
| 20030004871 | Rowe et al. | Jan 2003 | A1 |
| 20030008696 | Abecassis et al. | Jan 2003 | A1 |
| 20030013531 | Rowe | Jan 2003 | A1 |
| 20030027635 | Walker et al. | Feb 2003 | A1 |
| 20030064805 | Wells | Apr 2003 | A1 |
| 20030064807 | Walker et al. | Apr 2003 | A1 |
| 20030078094 | Gatto | Apr 2003 | A1 |
| 20030092480 | White et al. | May 2003 | A1 |
| 20030100361 | Sharpless et al. | May 2003 | A1 |
| 20030103965 | Jung | Jun 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 |
| 20030176218 | Lemay | Sep 2003 | A1 |
| 20030195024 | Slattery | Oct 2003 | A1 |
| 20030195043 | Shinners | 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 |
| 20040015619 | Brown | 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 |
| 20040082384 | Walker | Apr 2004 | A1 |
| 20040082385 | Silva et al. | Apr 2004 | A1 |
| 20040094624 | Fernandes | May 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 |
| 20040142744 | Atkinson | 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 |
| 20050033651 | Kogan | Feb 2005 | A1 |
| 20050043996 | Silver | 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 |
| 20050143169 | Nguyen | Jun 2005 | A1 |
| 20050167921 | Finocchio | Aug 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 |
| 20050202865 | Kim | Sep 2005 | A1 |
| 20050202875 | Murphy et al. | Sep 2005 | A1 |
| 20050208993 | Yoshizawa | 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 |
| 20060035707 | Nguyen | Feb 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 |
| 20060068897 | Sanford | Mar 2006 | A1 |
| 20060073869 | LeMay et al. | Apr 2006 | A1 |
| 20060073888 | Nguyen | Apr 2006 | A1 |
| 20060073897 | Englman et al. | Apr 2006 | A1 |
| 20060079317 | Flemming et al. | Apr 2006 | A1 |
| 20060121972 | Walker | Jun 2006 | A1 |
| 20060126529 | Hardy et al. | Jun 2006 | A1 |
| 20060148551 | Walker et al. | Jul 2006 | A1 |
| 20060189382 | Muir et al. | Aug 2006 | A1 |
| 20060217170 | Roireau | Sep 2006 | A1 |
| 20060217193 | Walker et al. | Sep 2006 | A1 |
| 20060247028 | Brosnan et al. | Nov 2006 | A1 |
| 20060247035 | Rowe et al. | Nov 2006 | A1 |
| 20060252530 | Oberberger et al. | Nov 2006 | A1 |
| 20060253481 | Guido et al. | Nov 2006 | A1 |
| 20060256135 | Aoyama | 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 |
| 20070111777 | Amaitis | May 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 |
| 20070235521 | Mateen | Oct 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 |
| 20070259716 | Mattice | Nov 2007 | A1 |
| 20070259717 | Mattice et al. | Nov 2007 | A1 |
| 20070265984 | Santhana | 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 |
| 20070298858 | Toneguzzo | 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 |
| 20080076527 | Low | 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 |
| 20080102935 | Finnimore | May 2008 | A1 |
| 20080102956 | Burman et al. | May 2008 | A1 |
| 20080102957 | Burnman et al. | May 2008 | A1 |
| 20080108401 | Baerlocker et al. | May 2008 | A1 |
| 20080113772 | Burrill et al. | May 2008 | A1 |
| 20080119267 | Denlay | May 2008 | A1 |
| 20080126529 | Kim | May 2008 | A1 |
| 20080013906 | Lutnick | Jun 2008 | A1 |
| 20080139274 | Baerlocher | Jun 2008 | A1 |
| 20080139306 | 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 |
| 20080167118 | Kroeckel | Jul 2008 | A1 |
| 20080182667 | Davis et al. | Jul 2008 | A1 |
| 20080200251 | Alderucci | Aug 2008 | A1 |
| 20080207307 | Cunningham, II et al. | Aug 2008 | A1 |
| 20080167130 | Koreckel | Sep 2008 | A1 |
| 20080214258 | Brosnan et al. | Sep 2008 | A1 |
| 20080214310 | Brunet de Courssou | 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 |
| 20080268959 | Bryson | Oct 2008 | A1 |
| 20080274783 | Walker | Nov 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 |
| 20090061990 | Schwartz | Mar 2009 | A1 |
| 20090069063 | Thomas | Mar 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 |
| 20090131155 | Hollibaugh | 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 |
| 20090270166 | Thukral | Oct 2009 | A1 |
| 20090270170 | Patton | Oct 2009 | A1 |
| 20090271287 | Halpern | Oct 2009 | A1 |
| 20090275402 | Backover | Nov 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 |
| 20090318219 | Koustas | 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 |
| 20100069160 | Barrett | 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 |
| 20100105454 | Weber 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 |
| 20100203957 | Enzminger | Aug 2010 | A1 |
| 20100203963 | Allen | Aug 2010 | A1 |
| 20100224681 | Triplett | Sep 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 |
| 20110034252 | Morrison | Feb 2011 | A1 |
| 20110039615 | Acres | Feb 2011 | A1 |
| 20110053679 | Canterbury et al. | Mar 2011 | A1 |
| 20110065492 | Acres | Mar 2011 | A1 |
| 20110076941 | Taveau | Mar 2011 | A1 |
| 20110086696 | MacEwan | Apr 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 |
| 20120046096 | Morrison | 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 |
| 20120115591 | Palermo | 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 |
| 20120185398 | Weis | 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 | 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 |
| 20130281187 | Skelton | Oct 2013 | A1 |
| 20130316808 | Nelson | Nov 2013 | A1 |
| 20130337878 | Shepherd | Dec 2013 | A1 |
| 20130337889 | Gagner | 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 |
| 20140120999 | Graves | May 2014 | A1 |
| 20140121005 | Nelson | May 2014 | A1 |
| 20140179431 | Nguyen | Jun 2014 | A1 |
| 20140221071 | Calio | Aug 2014 | A1 |
| 20140274306 | Crawford | Sep 2014 | A1 |
| 20140274309 | Nguyen | Sep 2014 | A1 |
| 20140274319 | Nguyen | Sep 2014 | A1 |
| 20140274320 | Nguyen | Sep 2014 | A1 |
| 20140274342 | Nguyen | Sep 2014 | A1 |
| 20140274357 | Nguyen | Sep 2014 | A1 |
| 20140274360 | Nguyen | Sep 2014 | A1 |
| 20140274367 | Nguyen | Sep 2014 | A1 |
| 20140274388 | Nguyen | Sep 2014 | A1 |
| 20150089595 | Telles | Mar 2015 | A1 |
| 20150133223 | Carter | May 2015 | A1 |
| 20150143543 | Phegade | Aug 2015 | A1 |
| 20150287283 | Yarbrough | Oct 2015 | A1 |
| 20160093154 | Bytnar | Mar 2016 | A1 |
| 20160125695 | Nguyen | May 2016 | A1 |
| 20170016819 | Nguyen | Apr 2017 | A1 |
| 20170116819 | 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 |
| 20170243440 | 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 |
| 20200372753 | Nguyen | Nov 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2033638 | May 1980 | GB |
| 2062923 | May 1981 | GB |
| 2096376 | Oct 1982 | GB |
| 2097570 | Nov 1982 | GB |
| 2335524 | Sep 1999 | GB |
| 12005000454 | May 2007 | PH |
| WO 05073933 | Aug 2005 | WO |
| WO 2008027621 | Mar 2008 | WO |
| WO 2009026309 | Feb 2009 | WO |
| WO 2009062148 | May 2009 | WO |
| WO 2010017252 | Feb 2010 | WO |
| Entry |
|---|
| 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. |
| Advisory Action for U.S. Appl. No. 13/296,182, 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. 16/190,050, dated Jun. 1, 2020. |
| Final Office Action for U.S. Appl. No. 16/449,717, dated Jan. 29, 2021. |
| Notice of Allowance for U.S. Appl. No. 15/811,654, dated Feb. 3, 2021. |
| Notice of Allowance for U.S. Appl. No. 14/017,150, dated Feb. 5, 2021. |
| Final Office Action for U.S. Appl. No. 16/794,212, dated Feb. 17, 2021. |
| Office Action for U.S. Appl. No. 16/351,416, dated Feb. 23, 2021. |
| Office Action for U.S. Appl. No. 15/674,480, dated Mar. 25, 2021. |
| Final Office Action for U.S. Appl. No. 16/219,940, dated Mar. 26, 2021. |
| Office Action for U.S. Appl. No. 13/296,182, mailed Feb. 25, 2016. |
| Office Action for U.S. Appl. No. 16/183,632, dated May 4, 2021. |
| Office Action for U.S. Appl. No. 16/559,553, mailed Jun. 1, 2021. |
| Notice of Allowance for U.S. Appl. No. 16/579,754, mailed Jul. 16, 2021. |
| Office Action for U.S. Appl. No. 13/622,702, mailed Jul. 19, 2021. |
| Office Action for U.S. Appl. No. 16/357,316, mailed Jul. 20, 2021. |
| Office Action for U.S. Appl. No. 16/993,154, mailed Jul. 28, 2021. |
| Final Office Action for U.S. Appl. No. 16/351,416, mailed Sep. 1, 2021. |
| Office Action for U.S. Appl. No. 15/671,133, mailed Sep. 2, 2021. |
| Notice of Allowance for U.S. Appl. No. 16/794,212, mailed Sep. 3, 2021. |
| Office Action for U.S. Appl. No. 17/020,761, mailed Sep. 9, 2021. |
| Office Action for U.S. Appl. No. 16/916,001, mailed Sep. 17, 2021. |
| Advisory Action for U.S. Appl. No. 13/632,828, dated Feb. 25, 2016. |
| Office Action for U.S. Appl. No. 13/622,702, dated Sep. 19, 2012. |
| Office Action for U.S. Appl. No. 13/801,719, dated Jun. 6, 2016. |
| Office Action (Notice of Allowance and Fees Due (PTOL-85) dated Mar. 22, 2022 for U.S. Appl. No. 16/248,759 (pp. 1-9). |
| Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Apr. 11, 2022 for U.S. Appl. No. 16/248,759 (pp. 1-6). |
| Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Apr. 7, 2022 for U.S. Appl. No. 14/017,159 (pp. 1-8). |
| Office Action (Non-Final Rejection) dated Apr. 20, 2022 for U.S. Appl. No. 17/306,946 (pp. 1-6). |
| Office Action (Non-Final Rejection) dated Jun. 6, 2022 for U.S. Appl. No. 16/248,759 (pp. 1-10). |
| Office Action (Non-Final Rejection) dated Sep. 8, 2022 for U.S. Appl. No. 17/485,289 (pp. 1-5). |
| Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Sep. 29, 2022 for U.S. Appl. No. 17/306,946 (pp. 1-8). |
| Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Nov. 7, 2022 for U.S. Appl. No. 16/248,759 (pp. 1-9). |
| Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Dec. 27, 2022 for U.S. Appl. No. 17/485,289 (pp. 1-8). |
| Office Action (Non-Final Rejection) dated Jan. 13, 2023 for U.S. Appl. No. 17/337,393 (pp. 1-5). |
| Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Feb. 2, 2023 for U.S. Appl. No. 17/306,946 (pp. 1-7). |
| Office Action (Non-Final Rejection) dated Mar. 22, 2023 for U.S. Appl. No. 16/248,759 (pp. 1-18). |
| Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated May 25, 2023 for U.S. Appl. No. 17/337,393 (pp. 1-7). |
| Office Action (Non-Final Rejection) dated Mar. 5, 2024 for U.S. Appl. No. 18/328,259 (pp. 1-8). |
| Office Action dated Mar. 28, 2024 for U.S. Appl. No. 18/234,503 (pp. 1-10). |
| 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 March, 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, mailed Aug. 23, 2013. |
| Office Action for U.S. Appl. No. 13/633,118, mailed Sep. 20, 2013. |
| Office Action for U.S. Appl. No. 13/801,256, mailed Jul. 2, 2013. |
| Notice of Allowance for U.S. Appl. No. 12/619,672, mailed Oct. 3, 2013. |
| Notice of Allowance for U.S. Appl. No. 12/757,968, mailed Oct. 11, 2013. |
| Final Office Action for U.S. Appl. No. 12/797,610, mailed Jul. 10, 2013. |
| Office Action for U.S. Appl. No. 12/617,717, mailed Jun. 17, 2013. |
| Notice of Allowance for U.S. Appl. No. 12/757,968, mailed Dec. 18, 2013. |
| Office Action for U.S. Appl. No. 12/945,889, mailed Dec. 18, 2013. |
| Office Action for U.S. Appl. No. 13/632,828, mailed Jul. 30, 2013. |
| Restriction Requirement for U.S. Appl. No. 13/801,256, mailed Dec. 30, 2013. |
| Office Action for U.S. Appl. No. 13/801,171, mailed Dec. 26, 2013. |
| Office Action for U.S. Appl. No. 13/801,234, mailed Jan. 10, 2014. |
| Final Office Action for U.S. Appl. No. 13/296,182, mailed Feb. 12, 2014. |
| Office Action for U.S. Appl. No. 12/617,717, mailed Feb. 25, 2014. |
| Office Action for U.S. Appl. No. 13/801,076, mailed Mar. 28, 2014. |
| Final Office Action for U.S. Appl. No. 13/633,118, mailed Apr. 3, 2014. |
| Office Action for U.S. Appl. No. 13/843,192, mailed Apr. 3, 2014. |
| Office Action for U.S. Appl. No. 13/632,743, mailed Apr. 10, 2014. |
| Office Action for U.S. Appl. No. 13/801,121, mailed Apr. 11, 2014. |
| Final Office Action for U.S. Appl. No. 12/945,889, mailed Jun. 30, 2014. |
| Notice of Allowance for U.S. Appl. No. 12/617,717, mailed Jul. 14, 2014. |
| Office Action for U.S. Appl. No. 13/801,121, mailed Sep. 24, 2014. |
| Office Action for U.S. Appl. No. 13/801,171, mailed Sep. 22, 2014. |
| Office Action for U.S. Appl. No. 13/801,234, mailed Oct. 1, 2014. |
| Office Action for U.S. Appl. No. 13/801,271, mailed Oct. 31, 2014. |
| Final Office Action for U.S. Appl. No. 13/843,192, mailed Oct. 21, 2014. |
| Office Action for U.S. Appl. No. 13/632,743, mailed Oct. 23, 2014. |
| Office Action for U.S. Appl. No. 12/945,889, mailed Oct. 23, 2014. |
| Office Action for U.S. Appl. No. 13/632,828, mailed Nov. 7, 2014. |
| Office Action for U.S. Appl. No. 12/797,610, mailed Dec. 15, 2014. |
| Final Office Action for U.S. Appl. No. 12/945,889, mailed Feb. 12, 2015. |
| Final Office Action for U.S. Appl. No. 13/801,171, mailed Mar. 16, 2015. |
| Office Action for U.S. Appl. No. 13/833,116, mailed Mar. 27, 2015. |
| Office Action for U.S. Appl. No. 13/632,828, mailed Apr. 10, 2015. |
| Final Office Action for U.S. Appl. No. 13/801,121, mailed Apr. 21, 2015. |
| Final Office Action for U.S. Appl. No. 13/557,063, mailed Apr. 28, 2015. |
| Office Action for U.S. Appl. No. 13/296,182, mailed Jun. 5, 2015. |
| Office Action for U.S. Appl. No. 13/843,192, mailed Jun. 19, 2015. |
| Office Action for U.S. Appl. No. 12/797,610, mailed Jul. 14, 2015. |
| Final Office Action for U.S. Appl. No. 13/833,953, mailed Jul. 17, 2015. |
| Notice of Allowance for U.S. Appl. No. 12/945,889, mailed Jul. 22, 2015. |
| Office Action for U.S. Appl. No. 12/797,616, mailed Aug. 10, 2015. |
| Final Office Action for U.S. Appl. No. 13/801,234, mailed Aug. 14, 2015. |
| Final Office Action for U.S. Appl. No. 13/833,116, mailed Sep. 24, 2015. |
| Office Action for U.S. Appl. No. 13/801,121, mailed Oct. 2, 2015. |
| Office Action for U.S. Appl. No. 14/017,150, mailed Oct. 7, 2015. |
| Office Action for U.S. Appl. No. 14/017,159, mailed Oct. 7, 2015. |
| Office Action for U.S. Appl. No. 13/801,271 mailed Oct. 19, 2015. |
| Office Action for U.S. Appl. No. 14/211,536 mailed Oct. 19, 2015. |
| Final Office Action for U.S. Appl. No. 13/632,828, mailed Oct. 22, 2015. |
| Office Action for U.S. Appl. No. 14/217,066, mailed Dec. 17, 2015. |
| Notice of Allowance for U.S. Appl. No. 13/557,063, mailed Dec. 23, 2015. |
| Office Action for U.S. Appl. No. 13/296,182, mailed Dec. 23, 2015. |
| Final Office Action for U.S. Appl. No. 13/843,192, mailed Dec. 30, 2015. |
| Office Action for U.S. Appl. No. 13/801,076, mailed Jan. 11, 2016. |
| Office Action for U.S. Appl. No. 12/945,888, mailed Jan. 22, 2016. |
| Final Office Action for U.S. Appl. No. 12/797,616, mailed Jun. 12, 2016. |
| Office Action for U.S. Appl. No. 13/843,087, mailed Feb. 25, 2016. |
| Office Action for U.S. Appl. No. 13/800,917, mailed Feb. 25, 2016. |
| Advisory Action for U.S. Appl. No. 13/632,828, mailed Feb. 25, 2016. |
| Office Action for U.S. Appl. No. 13/801,234, mailed Mar. 8, 2016. |
| Office Action for U.S. Appl. No. 14/216,986, mailed Mar. 9, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,271, mailed Mar. 11, 2016. |
| Office Action for U.S. Appl. No. 13/622,702, mailed Mar. 22, 2016. |
| Final Office Action for U.S. Appl. No. 13/633,118, mailed Mar. 24, 2016. |
| Final Office Action for U.S. Appl. No. 14/189,948, mailed Apr. 6, 2016. |
| Final Office Action for U.S. Appl. No. 12/797,610, mailed Apr. 21, 2016. |
| Final Office Action for U.S. Appl. No. 14/017,150, mailed Apr. 26, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,121, mailed May 11, 2016. |
| Final Office Action for U.S. Appl. No. 14/017,159, mailed Jun. 6, 2016. |
| Office Action for U.S. Appl. No. 13/801,171, mailed Jun. 6, 2016. |
| Office Action for U.S. Appl. No. 13/843,192, mailed Jun. 9, 2016. |
| Final OA for U.S. Appl. No. 12/945,888, mailed Jun. 28, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/833,953, mailed Jul. 6, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,171, mailed May 21, 2014. |
| Final Office Action for U.S. Appl. No. 13/801,234, mailed May 22, 2014. |
| Office Action for U.S. Appl. No. 14/211,536, mailed Jul. 13, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/801,076, mailed Jul. 11, 2016. |
| Office Action for U.S. Appl. No. 13/296,182, mailed Jul. 20, 2016. |
| Restriction Requirement for U.S. Appl. No. 13/296,182, mailed Oct. 12, 2012. |
| Advisory Action for U.S. Appl. No. 13/296,182, mailed May 8, 2014. |
| Advisory Action for U.S. Appl. No. 13/843,192, mailed May 8, 2014. |
| Notice of Allowance for U.S. Appl. No. 13/843,192, mailed Aug. 10, 2016. |
| Office Action for U.S. Appl. No. 14/217,066, mailed Dec. 22, 2016. |
| Final Office Action for U.S. Appl. No. 14/216,986, mailed Sep. 23, 2016. |
| Office Action for U.S. Appl. No. 14/017,159, mailed Sep. 23, 2016. |
| Office Action for U.S. Appl. No. 13/632,743, mailed Sep. 23, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,234, mailed Oct. 14, 2016. |
| Final Office Action for U.S. Appl. No. 13/843,087, mailed Oct. 13, 2016. |
| Final Office Action for U.S. Appl. No. 13/622,702, mailed Oct. 13, 2016. |
| Office Action for U.S. Appl. No. 14/189,948, mailed Nov. 7, 2016. |
| Final Office Action for U.S. Appl. No. 14/211,536, mailed Mar. 14, 2014. |
| Notice of Allowance for U.S. Appl. No. 13/833,116, mailed Oct. 11, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/801,271, mailed Dec. 2, 2016. |
| Notice of Allowance for U.S. Appl. No. 12/797,610, mailed Dec. 7, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/632,828, mailed Dec. 16, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,171, mailed Dec. 19, 2016. |
| Notice of Allowance for U.S. Appl. No. 14/211,536, mailed Dec. 28, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/801,256, mailed Jan. 20, 2017. |
| Office Action for U.S. Appl. No. 13/800,917, mailed Feb. 3, 2017. |
| Final Office Action for U.S. Appl. No. 12/797,616, mailed Feb. 10, 2017. |
| Office Action for U.S. Appl. No. 12/945,888, mailed Feb. 28, 2017. |
| Final Office Action for U.S. Appl. No. 14/189,948, mailed Mar. 17, 2017. |
| Office Action for U.S. Appl. No. 15/400,840, mailed Mar. 10, 2017. |
| Notice of Allowance for U.S. Appl. No. 13/801,121, mailed Mar. 29, 2017. |
| Office Action for U.S. Appl. No. 15/270,333, mailed Mar. 30, 2017. |
| Office Action for U.S. Appl. No. 15/402,945, mailed Apr. 5, 2017. |
| Office Action for U.S. Appl. No. 15/271,488, mailed Apr. 19, 2017. |
| Final Office Action for U.S. Appl. No. 14/217,066, mailed Apr. 21, 2017. |
| Office Action for U.S. Appl. No. 14/216,986 mailed Apr. 26, 2017. |
| Office Action for U.S. Appl. No. 13/801,171, mailed Jun. 14, 2017. |
| Office Action for U.S. Appl. No. 14/017,159, mailed Jun. 29, 2017. |
| Notice of Allowance for U.S. Appl. No. 15/270,333, mailed Jul. 5, 2017. |
| Final Office Action for U.S. Appl. No. 13/800,917, mailed Jul. 13, 2017. |
| Notice of Allowance for U.S. Appl. No. 13/801,234, mailed Jul. 5, 2017. |
| Notice of Allowance for U.S. Appl. No. 14/217,066, mailed Jul. 14, 2017. |
| Final Office Action for U.S. Appl. No. 14/518,909, mailed Jul. 19, 2017. |
| Final Office Action for U.S. Appl. No. 13/801,121, mailed Sep. 15, 2016. |
| Advisory Action for U.S. Appl. No. 13/801,121, mailed Jul. 17, 2015. |
| Advisory Action for U.S. Appl. No. 13/801,121, mailed Jul. 19, 2016. |
| Notice of Allowance for U.S. Appl. No. 15/293,751, mailed Aug. 4, 2017. |
| Advisory Action for U.S. Appl. No. 14/189,948, mailed Jul. 28, 2017. |
| Final OA for U.S. Appl. No. 13/801,256, mailed Aug. 15, 2014. |
| Final OA for U.S. Appl. No. 13/801,256, mailed Feb. 18, 2015. |
| Advisory Action for U.S. Appl. No. 13/801,256, mailed Dec. 5, 2014. |
| Office Action for U.S. Appl. No. 13/801,256, mailed Jan. 12, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,256, mailed Aug. 16, 2016. |
| Office Action for U.S. Appl. No. 13/622,702, mailed Aug. 31, 2017. |
| Office Action for U.S. Appl. No. 12/945,888, mailed Sep. 1, 2017. |
| Office Action for U.S. Appl. No. 14/017,150, mailed Sep. 7, 2017. |
| Notice of Allowance for U.S. Appl. No. 14/189,948, mailed Sep. 13, 2017. |
| Office Action for U.S. Appl. No. 15/138,086, mailed Oct. 19, 2017. |
| Notice of Allowance for U.S. Appl. No. 15/402,945 mailed Nov. 21, 2017. |
| Final Office Action for U.S. Appl. No. 13/801,171, mailed Dec. 13, 2017. |
| Final Office Action for U.S. Appl. No. 15/271,488, mailed Dec. 21, 2017. |
| Office Action for U.S. Appl. No. 15/671,133, mailed Dec. 22, 2017. |
| Final Office Action for U.S. Appl. No. 14/216,986, mailed Dec. 26, 2017. |
| Restriction Requirement for U.S. Appl. No. 15/427,307, mailed Jan. 17, 2018. |
| Office Action for U.S. Appl. No. 15/798,363, mailed Jan. 26, 2018. |
| Office Action for U.S. Appl. No. 15/427,291, mailed Jan. 29, 2018. |
| Final Office Action for U.S. Appl. No. 14/017,159, mailed Feb. 1, 2018. |
| Final Office Action for U.S. Appl. No. 13/622,702, mailed Feb. 22, 2018. |
| Office Action for U.S. Appl. No. 15/811,654, Mailed Feb. 22, 2018. |
| Final Office Action for U.S. Appl. No. 13/622,702, mailed Feb. 27, 2018. |
| Final Office Action for U.S. Appl. No. 15/427,308, mailed Mar. 19, 2018. |
| Office Action for U.S. Appl. No. 15/876,095, mailed Apr. 3, 2018. |
| Office Action for U.S. Appl. No. 15/835,448, mailed Apr. 4, 2018. |
| Office Action for U.S. Appl. No. 15/427,307, mailed Apr. 9, 2018. |
| Office Action for U.S. Appl. No. 14/216,986, mailed Apr. 6, 2018. |
| Office Action for U.S. Appl. No. 15/426,898 mailed Apr. 16, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/402,945, mailed May 25, 2018. |
| Office Action for U.S. Appl. No. 15/495,973, mailed Jun. 4, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/427,291 mailed Jun. 18, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/271,488, mailed Jun. 19, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/480,295, mailed Jun. 20, 2018. |
| Office Action for U.S. Appl. No. 14/963,106, mailed Jun. 22, 2018. |
| Office Action for U.S. Appl. No. 14/993,055, mailed Jun. 22, 2018. |
| Final Office Action for U.S. Appl. No. 15/427,307, mailed Jul. 9, 2018. |
| Notice of Allowance for U.S. Appl. No. 13/633,118, mailed Aug. 3, 2018. |
| Office Action for U.S. Appl. No. 15/671,133, mailed Aug. 9, 2018. |
| Office Action for U.S. Appl. No. 15/427,308, mailed Aug. 15, 2018. |
| Office Action for U.S. Appl. No. 15/798,363, mailed Aug. 29, 2018. |
| Office Action for U.S. Appl. No. 15/428,922 mailed Sep. 17, 2018. |
| Office Action for U.S. Appl. No. 15/495,975, mailed Sep. 21, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/271,488, mailed Sep. 24, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/876,095, mailed Sep. 24, 2018. |
| Office Action for U.S. Appl. No. 13/622,702, mailed Oct. 3, 2018. |
| Office Action for U.S. Appl. No. 15/293,751, mailed Apr. 6, 2017. |
| Notice of Allowance for U.S. Appl. No. 13/801,171, mailed Oct. 31, 2018. |
| Final Office Action for U.S. Appl. No. 15/835,448, mailed Nov. 2, 2018. |
| Final Office Action for U.S. Appl. No. 15/480,295, mailed Nov. 7, 2018. |
| Final Office Action for U.S. Appl. No. 14/963,106, mailed Dec. 14, 2018. |
| Final Office Action for U.S. Appl. No. 14/993,055, mailed Dec. 14, 2018. |
| Office Action for U.S. Appl. No. 16/162,358, mailed Dec. 31, 2018. |
| Office Action for U.S. Appl. No. 14/017,159, mailed Jan. 11, 2019. |
| Office Action for U.S. Appl. No. 15/426,898, mailed Jan. 11, 2019. |
| Final Office Action for U.S. Appl. No. 15/495,973, mailed Jan. 11, 2019. |
| Office Action for U.S. Appl. No. 14/216,986, mailed Jan. 14, 2019. |
| Office Action for U.S. Appl. No. 15/427,307, mailed Jan. 18, 2019. |
| Final Office Action for U.S. Appl. No. 15/798,363, mailed Feb. 4, 2019. |
| Office Action for U.S. Appl. No. 16/125,614, mailed Feb. 25, 2019. |
| Final Office Action for U.S. Appl. No. 15/495,975, mailed Apr. 18, 2019. |
| Office Action for U.S. Appl. No. 15/671,133, mailed May 1, 2019. |
| Notice of Allowance for U.S. Appl. No. 14/216,986, mailed May 17, 2019. |
| Notice of Allowance for U.S. Appl. No. 14/518,909, mailed May 17, 2019. |
| Office Action for U.S. Appl. No. 12/797,616, mailed Jun. 5, 2019. |
| Office Action for U.S. Appl. No. 15/427,308, mailed Jun. 14, 2019. |
| Office Action for U.S. Appl. No. 15/811,654, mailed Jun. 14, 2019. |
| Office Action for U.S. Appl. No. 15/674,480, mailed Jun. 20, 2019. |
| Notice of Allowance for U.S. Appl. No. 15/835,448, mailed Jul. 3, 2019. |
| Final Office Action for U.S. Appl. No. 16/162,358, mailed Jul. 11, 2019. |
| Office Action for U.S. Appl. No. 16/190,050, mailed Sep. 19, 2019. |
| Office Action for U.S. Appl. No. 14/017,150, mailed Oct. 9, 2019. |
| Final Office Action for U.S. Appl. No. 15/671,133, mailed Oct. 18, 2019. |
| Office Action for U.S. Appl. No. 15/835,448 mailed Oct. 12, 2019. |
| Notice of Allowance for U.S. Appl. No. 15/495,975, mailed Oct. 23, 2019. |
| Notice of Allowance for U.S. Appl. No. 14/993,005, mailed Nov. 27, 2019. |
| Final Office Action for U.S. Appl. No. 15/427,308, mailed Nov. 27, 2019. |
| Office Action for U.S. Appl. No. 15/798,363, mailed Jan. 8, 2020. |
| Office Action for U.S. Appl. No. 15/835,448, mailed Mar. 5, 2020. |
| Office Action for U.S. Appl. No. 15/495,975, mailed Mar. 17, 2020. |
| Office Action for U.S. Appl. No. 16/248,759, mailed Apr. 1, 2020. |
| Final Office Action for U.S. Appl. No. 14/017,150, mailed Apr. 17, 2020. |
| Notice of Allowance for U.S. Appl. No. 15/798,363, mailed May 12, 2020. |
| Office Action for U.S. Appl. No. 16/357,316, mailed May 21, 2020. |
| Office Action for U.S. Appl. No. 15/674,480, mailed Jun. 5, 2020. |
| Notice of Allowance for U.S. Appl. No. 15/480,295, mailed Jun. 15, 2020. |
| Office Action for U.S. Appl. No. 13/622,702, mailed Jun. 22, 2020. |
| Office Action for U.S. Appl. No. 15/811,654, mailed Jun. 26, 2020. |
| Office Action for U.S. Appl. No. 16/579,754, mailed Jul. 22, 2020. |
| Office Action for U.S. Appl. No. 16/219,940, mailed Jul. 22, 2020. |
| Office Action for U.S. Appl. No. 16/559,553, mailed Sep. 11, 2020. |
| Office Action for U.S. Appl. No. 16/794,212, mailed Sep. 11, 2020. |
| Restriction Requirement for U.S. Appl. No. 16/600,395, mailed Sep. 18, 2020. |
| Final Office Action for U.S. Appl. No. 16/248,759, mailed Oct. 6, 2020. |
| Final Office Action for U.S. Appl. No. 15/671,133, mailed Oct. 7, 2020. |
| Final Office Action for U.S. Appl. No. 16/357,316, mailed Oct. 8, 2020. |
| Final Office Action for U.S. Appl. No. 16/183,632, mailed Oct. 9, 2020. |
| Office Action for U.S. Appl. No. 16/590,347, mailed Oct. 13, 2020. |
| Office Action for U.S. Appl. No. 16/449,717, mailed Nov. 9, 2020. |
| Final Office Action for U.S. Appl. No. 13/622,702, mailed Nov. 30, 2020. |
| Final Office Action for U.S. Appl. No. 15/674,480, mailed Dec. 7, 2020. |
| Office Action for U.S. Appl. No. 16/168,813, mailed Dec. 8, 2020. |
| Office Action for U.S. Appl. No. 16/600,395, mailed Dec. 22, 2020. |
| “Professional Casino Slot Machine”, Posted at www.vbtutor.net/VB.Sample/vbslot2.htm on Oct. 20, 2009. |
| Final Office Action for U.S. Appl. No. 16/559,553, mailed Jan. 21, 2021. |
| Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Jul. 31, 2024 for U.S. Appl. No. 18/328,259 (pp. 1-8). |
| Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Aug. 14, 2024 for U.S. Appl. No. 18/328,259 (pp. 1-4). |
| Number | Date | Country | |
|---|---|---|---|
| 20210150854 A1 | May 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62617579 | Jan 2018 | US | |
| 61873300 | Sep 2013 | US | |
| 61799862 | Mar 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16143428 | Sep 2018 | US |
| Child | 16590347 | US | |
| Parent | 15427291 | Feb 2017 | US |
| Child | 16143428 | US | |
| Parent | 14211536 | Mar 2014 | US |
| Child | 15427291 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16590347 | Oct 2019 | US |
| Child | 17160343 | US | |
| Parent | 16248759 | Jan 2019 | US |
| Child | 17160343 | US |
