Location-based mobile gaming system and method

Information

  • Patent Grant
  • 11636732
  • Patent Number
    11,636,732
  • Date Filed
    Friday, September 24, 2021
    2 years ago
  • Date Issued
    Tuesday, April 25, 2023
    a year ago
Abstract
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, a mobile gaming system can concern an application program operating on a portable electronic device that supports multiple modes of operation depending upon whether the portable electronic device is in a location where betting or games of chance are permitted.
Description
BACKGROUND OF THE INVENTION

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 need for improved approaches to enhance mobile betting or gaming opportunities.


SUMMARY

Embodiments disclosed herein concern mobile gaming environments. Portable electronic devices can be supported by the mobile gaming environments. The locations of the portable electronic devices can influence how the portable electronic devices operate and/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. A betting opportunity that has been secured can later be activated when the portable electronic device associated with the individual later resides in a location where betting or games of chance are permitted.


According to another embodiment, a mobile gaming system can concern an application program operating on a portable electronic device that supports multiple modes of operation depending upon whether the portable electronic device is in a location where betting or games of chance are permitted. The application can adapt or transform itself (i.e., switch modes), automatically or with user assistance, depending upon whether the portable electronic device is in a location where betting or games of chance are permitted. When the portable electronic device is in a location where betting or games of chance are not permitted, the application program can still operate (i.e., permit non-wagering usage) and enable its user to earn rewards, advantages, tools, etc. without actually betting (e.g., wagering). Further, the rewards, advantages, tools, etc. being earned can be used directly or can be used following a conversion to something useable in betting/games of chance when the portable electronic device is later located where betting or games of chance is permitted. The application program can also allow the user to play a betting/game of chance for practice or for simulation of virtual betting.


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 non-transitory computer readable medium including at least computer program code for an application program stored thereon, where the application program is executable by a computing device, one embodiment can, for example, include at least: computer program code for determining whether the computing device is in a gaming authorized location or a gaming unauthorized location; computer program code for operating the application program in a non-gaming mode if the location of the computing device is located in a gaming unauthorized location; and computer program code for operating the application program in a gaming mode if the location of the computing device is located in a gaming authorized location.


As a method for facilitating gaming via portable electronic devices, one embodiment can, for example, include at least: causing a betting opportunity to be presented to a user via a portable electronic device associated with the user; receiving, at a gaming server, a bet amount for the betting opportunity from the portable electronic device; determining whether the portable electronic device is in a betting authorized location; placing a bet corresponding to the betting opportunity in the bet amount for the user if the determining determines that the portable electronic device is in a betting authorized location; and deferring placing of the bet corresponding to the betting opportunity in the bet amount for the user if the determining determines that the portable electronic device is not in a betting authorized location.


As a non-transitory computer readable medium including at least computer program code for an application program stored thereon, where the application program is executable by a computing device, one embodiment can, for example, include at least: computer program code for causing presentment of a betting opportunity via the application program; computer program code for determining whether a user of the application program desires to pursue the betting opportunity; computer program code for determining whether the computing device is in a gaming authorized location or a gaming unauthorized location; and computer program code for initiating locking in the betting opportunity for future execution for the user of the computing device is determined to be in a gaming unauthorized location.


As a method for provided a betting opportunity using a portable electronic device, one embodiment can, for example, include at least: causing presentment of a betting opportunity via the portable electronic device; determining whether a user of the portable electronic device desires to pursue the betting opportunity; determining whether the portable electronic device is in a gaming authorized location or a gaming unauthorized location; and initiating locking in the betting opportunity for future execution if the portable electronic device subsequently is determined to be in a gaming authorized location.


As a method for facilitating gaming via portable electronic devices, one embodiment can, for example, include at least: displaying a betting opportunity to a user via a portable electronic device associated with the user; receiving, using the portable electronic device, a bet amount for the betting opportunity; displaying a bet option fee for locking in a bet option to make the bet amount; receiving, using the portable electronic device, an acceptance of the bet option fee; and initiating locking of the option to make the bet amount for the user.


Other aspects and advantages of the invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the invention.





BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like elements, and in which:



FIG. 1 is a block diagram of a mobile gaming/betting system according to one embodiment.



FIG. 2A is a flow diagram of an application mode process according to one embodiment.



FIG. 2B is a flow diagram of a pre-wager mode process according to one embodiment.



FIG. 2C is a flow diagram of a pre-wager scheduling process according to one embodiment.



FIG. 3 is a flow diagram of a location-based betting process according to one embodiment.



FIGS. 4A and 4B illustrate a flow diagram of a bet locking process according to one embodiment.



FIG. 5 illustrates an exemplary computer device suitable for use with at least one embodiment of the invention.



FIG. 6 is a block diagram of an example computing device.





DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS

Embodiments disclosed herein concern mobile gaming environments. Portable electronic devices can be supported by the mobile gaming environments. The locations of the portable electronic devices 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. A betting opportunity that has been secured can later be activated when the portable electronic device associated with the individual later resides in a location where betting or games of chance are permitted.


According to another embodiment, a mobile gaming system can concern an application program operating on a portable electronic device that supports multiple modes of operation depending upon whether the portable electronic device is in a location where betting or games of chance are permitted. The application can adapt or transform itself (i.e., switch modes), automatically or with user assistance, depending upon whether the portable electronic device is in a location where betting or games of chance are permitted. When the portable electronic device is in a location where betting or games of chance are not permitted, the application program can still operate (i.e., permit non-wagering usage) and enable its user to earn rewards, advantages, tools, etc. without actually betting (e.g., wagering). Further, the rewards, advantages, tools, etc. being earned can be used directly or can be used following a conversion to something useable in betting/games of chance when the portable electronic device is later located where betting or games of chance is permitted. The application program can also allow the user to play a betting/game of chance for practice or for simulation of virtual betting.


Embodiments of various aspects of the invention are discussed below with reference to FIGS. 1-6. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the invention extends beyond these limited embodiments.



FIG. 1 is a block diagram of a mobile gaming/betting system 100 according to one embodiment. The mobile gaming/betting system 100 includes a one or more gaming/betting server machines 102. The one or more gaming/betting server machines 102 can manage, coordinate or process gaming/betting with respect to a plurality of portable electronic devices. The gaming/betting server machines 102 can also manage, coordinate or process gaming/betting with respect to other electronic devices, including various games of chance, including stationary gaming machines or stationary table games. The mobile gaming/betting server machines 102 can couple to a network 104. The network 104 can include one or more private networks or public networks, including wired and/or wireless networks. The mobile gaming/betting system 100 can also support a plurality of portable electronic devices (PEDs). As illustrated in FIG. 1, the depicted plurality of PEDs can, in a simplified representative situation, include PED-1 106, PED-2 108, PED-3 110 and PED-4 112. In general, although the PEDs of FIG. 1 can also be referred to as Portable Gaming Devices (PGDs) since they can support gaming/betting.


Given various legal restrictions on gaming or betting, it is often the case that gaming/betting is only available in certain locations. These locations can correspond to states, Indian reservations, casino establishments, or specific areas (such as rooms, floors, tables) at casino establishments or cruise ships. Accordingly, it can be advantageous for the mobile gaming/betting system 102 to control gaming/betting by PEDs based upon the location of the PEDs. As illustrated in FIG. 1, the mobile gaming/betting system 100 can also illustrate a gaming/betting authorized region 114, which represents a location where gaming/betting is permissible. As illustrated in FIG. 1, the PED-1 106 and the PED-2 108 are currently within the gaming/betting authorized region 114. Consequently, the PET-1 106 and the PET-2 108 are permitted to perform gaming/betting activities with assistance of the one or more gaming/betting server machines 102. However, since the PED-3 110 and the PED-4 112 are presently not within a gaming/betting authorized region, these mobile devices are not permitted to participate in gaming/betting activities at this time. It should be understood that at some future point in time, if the PED-3 110 and/or the PED-4 112 are then located in a gaming/betting authorized region, these PEDs 110 and 112 would then be able to participate in gaming/betting activities.


Nevertheless, when the PEDs are not within a gaming/betting authorized region, the PEDs can still operate to facilitate user participation or interaction with users even though gaming/betting activities are not permitted. For example, a player can play along, without placing a monetary wager, with a live table game taking place at a casino. While entertaining, such a practice mode also allows a player to get familiar with a new game, to practice back betting (e.g., betting on the active live players, not on the games), to hone his game strategies, to play along with a friend who is at the casino, etc. The participation or interaction with the PEDs when gaming/betting is unavailable can yield awards, benefits or advantages. In some cases, the awards, benefits or advantages can be used when the PEDs are later in a location where gaming/betting activities are permitted. This participation or interaction can vary depending upon implementation.


In one implementation, an application program operating on a corresponding PED dynamically adjusts (e.g., transforms) its operation depending upon whether gaming/betting activities are permitted. In the case in which gaming/betting activities are not permitted, the application program can allow non-gaming play in which a user can accrue awards or other benefits (e.g., coupons, points, tools, virtual goods, secret prizes, etc.) that may or may not be able to be used directly in the application program when the PED is later within a gaming/betting authorized region. One example of a tool that could be accrued is a gaming tool to give the user a guide or hint as to desirable location, machines or action within a casino establishment. Virtual goods are game assets (e.g., game currency) that normally do not have value outside of the game or outside of a designated gaming location. Secret prizes maybe awarded in play-along game mode, but can only be revealed and redeemed by the user at designated gaming locations.


In another implementation, a PED, or an application program operating on the PED, can permit a user to secure a bet opportunity even while in a location that is not a gaming/betting authorized region. For example, the PED can facilitate the user in securing an option to later activate a bet when the PED is within a gaming/betting authorized region. In effect, the PED can operate to provide deferred betting (e.g., sports betting), whereby a bet is reserved until the PED and its user are in a location that is gaming/betting authorized.



FIG. 2A is a flow diagram of an application mode process 200 according to one embodiment. The application mode process 200 can be performed by a computing device. For example, the computing device can be a personal computing device, such as a mobile computing device (or portable electronic device), that is capable of operating application programs. One example of such a mobile computing device is a smart phone. Another example of such a mobile computing device is a tablet computer or notebook computer.


The application mode process 200 can determine 202 If the computing device is in a gaming authorized location. The gaming authorized location has a geographic significance. For example, the gaming authorized location can be a state wide location, an establishment wide location, or an internal area within an establishment. A decision 204 can evaluate whether the computing device is in a gaming authorized location. When the decision 204 determines that the computing device is in a gaming authorized location, the computing device can operate 206 the application program in a gaming mode. For example, when the application is operated in a gaming mode, the application program can operate to provide a game of chance for a user of the computing device and/or provide an ability to place a bet (e.g., sports betting) via the computing device.


On the other hand, when the decision 204 determines that the computing device is not in a gaming authorized location, the application program can operate 208 in a non-gaming mode. In the non-gaming mode, the application program does not permit operating of a game of chance or placing of a bet. However, in one embodiment, the application program can offer a non-gaming alternative, which can enable the user to still interact with the application program. In one embodiment, the operation of the application program in the non-gaming mode can allow the user to win or accrue awards, assets, tools, features or benefits that are usable or convertible either for use with the application program when operating in the gaming mode or for use with another device (e.g., stationary gaming machine).


In another embodiment, the user can play along by executing the application as intended, but without actually placing a monetary bet (e.g., simulation mode). The user can practice to gain experience on a game, to test his skills, to gain familiarity with a new game, etc. For example, a user in a non-gaming location can monitor a live video broadcast of a game of Craps taking place at the gaming location. The user can join in and bet with virtual chips in a simulated game and see the real result of his virtual wager in the context of the real, live game. Thus, the user stays engaged by learn to play without risking money. The user can be at or distant from the gaming location.


Following the blocks 206 or 208, a decision 210 can determine whether the application program should end. When the decision 210 determines that the application program should not end, the application process 200 can return to repeat the block 202 and subsequent blocks so that the operation of the application program can dynamically alter its operation, such as switching between the gaming mode and the non-gaming mode, based on the location of the computing device. In some embodiments, switching from gaming mode to non-gaming mode (e.g., switch to play-along or free-play mode) maybe allowed even when the user is at an authorized gaming location so that the user can practice without risking money until she is ready. Mode switching can be automatically performed without user participation, or can switch only on user request or authorization. Alternatively, when the decision 210 determines that the application mode process 200 should end, the application mode process 200 can end.



FIG. 2B is a flow diagram of a pre-wager mode process 220 according to one embodiment. The pre-wager mode process 220 can be performed when the application program operates in a non-gaming mode, such as within block 208 of FIG. 2A. In the pre-wager mode process 220, a decision 222 can determine whether pre-wager play is being requested. When the decision 222 determines that pre-wager play is not requested, the application program can be operated 224 in a free play mode. In the free play mode, the user can operate the application program without any wagering or cost to the player. Free play mode can be applied to any casino game. A special case of free play is the play along mode where a user at a non-gaming location plays along with a live game (e.g., Roulette) at a gaming-authorized location as if he was there, although no monetary betting takes place. On the other hand, when the decision 222 determines that the pre-wager play has been requested, the application program can operate 226 in a pre-wager mode. In the pre-wager mode, the application program allows a user to configure a wager that may be activated in the future. In other words, the user can schedule a wager to occur in the future. Following the blocks 224 or 226, the pre-wager mode process 220 can, for example, return to block 208 (or decision 210) of the application mode process 200 illustrated in FIG. 2A.



FIG. 2C is a flow diagram of a pre-wager scheduling process 240 according to one embodiment. The pre-wager scheduling process 240 can be performed when the application program operates in the pre-wager mode, such as associated with the block 226 illustrated in FIG. 2B. According to the pre-wager scheduling process 240, a decision 242 can determine whether a pre-wager is to be scheduled. When the decision 242 determines that a pre-wager is to be scheduled, pre-wager data can be queued 244 for subsequent processing. Next, a decision 246 can determine whether the pre-wager mode is to end. When the decision 246 determines that the pre-wager mode is not to end, the pre-wager scheduling process 240 returns to repeat the decision 242 and subsequent blocks. On the other hand, when the decision 246 determines that the pre-wager mode is to end, the pre-wager scheduling process 240 can and processing can, for example, return to the block 208 (or the decision 210) of the application mode process 200 illustrated in FIG. 2A. Additionally, it should be noted that when the decision 242 determines that a pre-wager is not to be scheduled, the block 244 can be bypassed.



FIG. 3 is a flow diagram of a location-based betting process 300 according to one embodiment. The location-based betting process 300 can facilitate initiation of bets using a portable electronic device, even if the portable electronic device is in a location where gaming is not authorized.


The location-based betting process 300 illustrated in FIG. 3 can display 302 a betting opportunity. Here, the betting opportunity can be displayed on a display associated with the portable electronic device. The betting opportunity can be provided to the portable electronic device from a server computer (e.g., gaming/betting server machine). The portable electronic device can operate an application program that can receive and display information on the betting opportunity.


Next, a decision 304 can determine whether the betting opportunity has been accepted. Here, a user of the portable electronic device can review the betting opportunity being displayed 302 and decide whether to accept or decline the betting opportunity. When the decision 304 determines that the betting opportunity has not been accepted (i.e., declined), the location-based betting process 300 can end.


Alternatively, when the decision 304 determines that the betting opportunity has been accepted, a decision 306 can determine whether the portable electronic device is in a gaming authorized location. When the decision 306 determines that the portable electronic device is in a gaming authorized location, the bet corresponding to the betting opportunity can be executed 308. Here, a user of the portable electronic device can accept the betting opportunity so long as the portable electronic device is in a gaming authorized location. The betting opportunity being accepted can be selected, customized or altered in view of desires of the user. In any case, after a bet corresponding to the betting opportunity has been executed 308 for the user, the location-based betting process 300 can end.


On the other hand, when the decision 306 determines that the portable electronic device is not in a gaming authorized location, a bet corresponding to the betting opportunity is not permitted to be executed. However, in this situation, the betting opportunity can be locked in 310 for possible future execution. By locking in 310 the betting opportunity, the user of the portable electronic device can effectively secure the betting opportunity for future execution so long as the portable electronic device reaches a gaming authorized location in a timely manner. In this case, the user secured the right to place the bet at a future time. The bet option must be exercised prior to execution of the game or prior to the presentation of the game result. Otherwise, the bet option expires and becomes worthless. In one example, a user may secure an option to place a $100 bet, at a given odd and pay out schedule. The bet can be premised on any of a variety of betting opportunities. As one example, the bet might be premised on the San Francisco 49ers winning the Super Bowl. As another example, the bet might be premised on the National Lottery's grand prize not having a winner over the next two drawings. If the bet option isn't exercised (e.g., by placing the actual bet at an authorized location) before the cut-off deadline (e.g., before the start of the game, before the next two drawings, etc.), the bet option expires.


The location-based betting process 300 can further include a decision 312 that determines whether the portable electronic device is in a gaming authorized location. When the decision 312 determines that the portable electronic device is not in a gaming authorized location, a decision 314 can determine whether the locked betting opportunity has expired. Typically, after the betting opportunity is locked in 310, the locking thereof can have a time limit (e.g., predetermined expiration or predetermined duration) after which the locked betting opportunity expires. Hence, when the decision 314 determines that the locked betting opportunity has not expired, the location-based betting process 300 can return to repeat the decision 312 so that the location monitoring can continue. In this example, the location monitoring can be dynamically performed by the portable electronic device without the request for assistance of the user. However, in an alternative embodiment, it should be understood that the portable electronic device could check its location on request from the user of the portable electronic device. In the case where the decision 314 determines that the locked betting opportunity has expired, the location-based betting process 300 can end.


Alternatively, when the decision 312 determines that the portable electronic device is in a gaming authorized location, a decision 316 can determine whether the bet associated with the locked betting opportunity is confirmed. Here, the location-based betting process 300 can allow the user of the portable electronic device to confirm that the bet corresponding to the locked betting opportunity is still to be made. When the decision 316 determines that the bet has been confirmed, the location-based betting process 300 can proceed to the block 308 where a bet corresponding to the locked betting opportunity can be executed. On the other hand, when the decision 316 determines that the user has not confirmed (i.e., declined) the bet corresponding to the locked betting opportunity, the locked betting opportunity can be canceled 318. After the locked betting opportunity has been canceled 318, the location-based betting process 300 can end.


The scope or size of a gaming authorized location can vary depending on implementation. In one implementation, the gaming authorized location can be associated with an area or zone established by a wireless network. In another implementation, the gaming authorized location can be established by a registration site, which can established physical presence or close proximity of the portable gaming device. In still another implementation, the gaming authorized location can be established by both a wireless network and/or a registration site. The gaming authorized location can be implemented by or proximate to a kiosk, a bank of gaming machines (e.g., bank of slot machines or video gaming machines), a table game, a room, or an area (e.g., stadium, casino floor, convention center).


There are various approaches for determining whether a portable electronic device (e.g., PED) is in a gaming authorized location. Any one or more of these techniques can be used for the block 204 of FIG. 2A or the blocks 306 or 312 of FIG. 3.


The location of a portable electronic device can be determined by various techniques. In one embodiment, the detection of a mobile electronic device within a gaming authorized location can be achieved using the wireless technologies (e.g., wireless geofencing). For example, relatively short range wireless technologies such as Bluetooth, near field communications (NFC), or radio frequency identification (RFID) can be used to evaluate whether the portable electronic device is within a gaming authorized location. As an example, placing one or more device registration sites within a gaming authorized location, such as an authorized gaming zone, can be used to determine the location of portable electronic devices. In one embodiment, in order to be recognized as within a gaming authorized location, the portable electronic device must be within wireless range of a wireless source provided by the device registration sites within the gaming authorized location. In one implementation, the wireless technologies being used for this purpose can be provided for this specific purpose of establishing a gaming authorized location. In another implementation, the wireless technologies can be generally provided within an establishment or larger area but can also be used to establish the position of the mobile electronic device (i.e., whether within the gaming authorized location). Examples of wireless technologies for mobile device locating in larger areas include Wi-Fi, WiMax, LTE, Cellular, and the like. Satellite-based location technology such as GPS can also be used. In one approach, some combinations of these wireless technologies are used at the same time, depending on which signal is available, to increase the accuracy of the locating technique.


In another embodiment, the detection of a mobile electronic device within a gaming authorized location can be achieved using a physical event between the mobile electronic device and device registration sites within a gaming authorized location. For example, the mobile electronic device associated with the user that is desirous of participating in games of chance, or otherwise wagering, can physically contact their mobile electronic device to a device registration site within a gaming authorized location. This can establish a pairing or registration of the mobile electronic device, if desired, and can confirm its presence within the gaming authorized location. The physical contact can establish physical presence. For example, the physical contact can be achieved using a registration site that can receive a “bump” from a portable electronic device. Additional details on a “bump” event and its processing can be found in (i) U.S. patent application Ser. No. 13/622,702, filed Sep. 19, 2012 and entitled “Multi-Functional Peripheral Device,” which is hereby incorporated herein by reference; and (ii) U.S. patent application Ser. No. 12/945,888, filed Nov. 14, 2010 and entitled “Multi-Functional Peripheral Device,” which is hereby incorporated herein by reference. As an alternative, the device registration site can also be implemented as a docking station. In such an implementation, a mobile gaming device can dock itself into the docking station to provide a pairing or registration and/or to confirm its presence.


As previously noted, the location of a portable electronic device can be determined by various techniques. Additionally, in some embodiments, it may be advantageous to make use of a plurality of different techniques to establish and/or maintain knowledge of the location of a portable electronic device. The advantages offered by using multiple techniques can include redundancy, enhanced reliability and improved security. In one implementation, a localized location detection technique, whether dedicated or not, could be utilized to establish initial authorized location of a portable electronic device. Then, for subsequent location monitoring, a wider location detection technique could be utilized to monitor the location of the portable electronic device. One example of this combine technique could be to use a short range wireless technique (e.g., Bluetooth, RFID, NFC) initially, followed by a midrange wireless technique (e.g., Wi-Fi, WiMax, LTE).


Further still, in other embodiments, it may be useful to utilize one wireless technique for location monitoring, and a separate wireless technique for wireless communication. For example, the location monitoring could utilize a localized wireless technique (e.g., Bluetooth) but for data communication a more pervasive network, such as Wi-Fi or cellular networks, could utilized.


In some embodiments, it may be required or useful to subsequently re-determine whether a portable electronic device (e.g., PED) is in a gaming authorized location. For example, if the block 204 determines that the computing device (i.e., portable electronic device) is in a gaming authorized location, then at block 206, the application program can operate 206 in a gaming mode. The ability of the application program to operate 206 in a gaming mode can be controlled at (i) the device or application level, (ii) the server level which provides or supports the gaming via the application program, or (iii) a combination thereof. After the gaming mode of the application program is made available on the computing device, it may be required or useful to determine whether the computing device is still within the gaming authorized location. Any one or more of the above-noted techniques for determining whether the computing device is within a gaming authorized location can be used for such re-determining. It should also be understood that the frequency or rate of re-determining can vary with implementation. As one example, the re-determining can be done on a periodic basis. As another example, the re-determining can be performed when a gaming action is requested.


In one embodiment, a remote server can be utilized to store information on whether portable electronic devices are in gaming authorized locations. That is, with the assistance of other computing devices, a remote server (that is, a server machine) can manage the storage of such gaming authorization data in a database that is maintained and frequently updated. As a result, when a determination is needed to evaluate whether a particular portable electronic device is within a gaming authorized location, the remote server can itself or on request query the database and rapidly determine whether the particular portable electronic device is within a gaming authorized location.



FIGS. 4A and 4B illustrate a flow diagram of a bet locking process 400 according to one embodiment. The bet locking process 400 can be performed by a computing device. The computing device can be a personal computing device, such as a mobile computing device (or portable electronic device).


The bet locking process 400 can display 402 a betting opportunity. Typically, the betting opportunity can be displayed 402 on a display associated with a mobile computing device used by a user. A decision 404 can then determine whether the user has accepted the betting opportunity. Typically, a user can interact with the mobile computing device to indicate their acceptance of the betting opportunity. Alternatively, the user can elect to decline the betting opportunity. If the user has elected to decline the betting opportunity, the bet locking process 400 can end.


However, if the user has elected to accept the betting opportunity, following the decision 404, the bet locking process 400 continues to process the betting opportunity. In this regard, a bet amount can be received 406. For example, the user can interact with the mobile computing device to enter or select a bet amount. Next, a bet option fee can be displayed 408. The bet option fee (or bet lock fee) can represent a fee or charge that is associated with the locking of the betting opportunity. The locked bet opportunity can also be referred to as an option to later activate a bet. In an alternative embodiment, the bet option fee maybe collected without the bet amount received in 406. In this case, the user purchased the right to place the bet later. The bet option must be exercised prior to execution of the game or prior to the presentation of the game result. Otherwise, the bet option expires and becomes worthless. In one example, a user may buy an option to place a $100 bet, at a given odd and pay out schedule. The bet can be premised on any of a variety of betting opportunities. As one example, the bet might be premised on the San Francisco 49ers winning the Super Bowl. As another example, the bet might be premised on the National Lottery's grand prize not having a winner over the next two drawings. If the bet option isn't exercised (e.g., by placing the actual bet at an authorized location) before the cut-off deadline (e.g., before the start of the game, before the next two drawings, etc.), the bet option expires. The bet option fee can be displayed on a display associated with the mobile computing device. A decision 410 can then determine whether the user has accepted the bet option fee. For example, the user can interact with the mobile computing device to indicate their acceptance of the bet option fee. When the decision 410 determines that the user has not accepted, but declined, the bet option fee, the bet locking process 400 can end.


On the other hand, when the decision 410 determines that the user has accepted the bet option fee, a locked bet confirmation request can be displayed 412. The locked bet confirmation request presents information concerning the betting opportunity to be locked. The information concerning the betting opportunity to be locked can be displayed 412 on a display associated with the mobile computing device. The user of the mobile computing device can then evaluate whether the information is correct and whether they want to confirm the locking of the betting opportunity. Next, a decision 414 can determine whether the locked betting opportunity has been confirmed. When the locked betting opportunity has not been confirmed, but denied, the debt locking process 400 can end. Alternatively, when the decision 414 determines that the locked betting opportunity has been confirmed, a locked bet request can be sent 416. Here, the locked bet request can be sent 416, for example, to a remote server computer (e.g., gaming/betting server machine(s) 102) for processing of the locked bet request.


A decision 418 can then determine whether the locked bet has been accepted. Here, in response to the locked bet request, the locked bet being requested can be accepted or decline by a remote processing system, which can operate on the remote server computer. When the decision 418 determines that the locked bet request has been accepted, a locked bet acceptance can be displayed 420. For example, the locked bet acceptance can provide confirmation information that the locked bet being requested has been accepted. The locked bet confirmation can be displayed 420 on a display associated with the mobile computing device. Alternatively, when the decision 418 determines that the locked bet request has not been accepted, but declined, a locked bet failed message can be displayed 422. For example, the locked bet failed message can be displayed 422 on a display associated with the mobile computing device. For example, the locked bet failed message, might indicate failure due to insufficient funds. Following the blocks 420 and 422, the bet locking process 400 can end.


In one embodiment, a database can be used by a server computer to manage availability, acceptance and execution of betting opportunities.


According to another embodiment, an application program in operation, such as on a PED, can provide gaming assets or awards. When transitioning the application program between a gaming authorized mode and a gaming unauthorized mode, such assets or awards can be converted. For example, the conversion can be from currency (e.g., points) to another currency (e.g., cash), or can be converted to functionally-different assets or awards (e.g., game tools, virtual goods) or value-equivalent digital goods (e.g., 2× multiplier bonus for all payouts in the next 10 spins of a slot game, virtual chips).


According to another embodiment, an application program in operation, such as on a PED, can provide games symbols that dynamically change. This creates continuity, as well as progress, that links on-site (authorized gaming location) and off-site (unauthorized gaming location) user experiences. For example, gaming symbols can dynamically change over time, due to game play, due to events, due to location, due to user satisfying participation criteria, etc. For example, a gaming symbol (such as for an award) can initially be an apple seed. Then through continued game play or play time, the apple seed can grow into a tree, and then eventually produce one or more apples. The apples can then be redeemed for benefits which can vary. For example, an apple could be redeemed for a free spin or enhancement (e.g., 2× multiplier) on a game of chance (e.g., slot machine or table wagering game), or for a discounted admission ticket, free extra bonus spin or hotel room upgrade. In one scenario, apple seeds can be acquired at a gaming establishment, which can distribute the apple seeds based on user performance play, random or even virally distributed. Once a user has a seed, the development of the apple tree and the yielding of apples can be facilitated through user actions (e.g., via PED), either at a gaming establishment or while not at a gaming establishment, such as well as at home.


Although betting/wagering can pertain to sports betting, there are various other games that can also offer a betting or wagering opportunity. For example, Keno is a game of change that can involve betting/wagering. For example, an application program can allow users to play a Keno game for “free”, but when in a gaming authorized zone, the application program can allow users to play a game of Keno for money. The application program can transform to or from a game mode automatically or only after user permission.


In one embodiment, pre-play can be performed in advance of reaching a gaming authorized area. For example, with pre-play a user can interact with an application program operating on a portable gaming device to schedule (e.g., queue) a bet or wager regardless of their location, and then when the user (and the portable electronic device) reach a gaming authorized area, the application program can initiate auto-play of the scheduled gaming actions. That is, a Bingo player can pre-configure her Bingo card with her “lucky” numbers at home, or a Keno player can preset several lucky number sets (groups of 6 numbers, groups of 7 numbers, etc.) to be activated when the player is at an authorized location for betting, and the like.


In another embodiment, pre-play can be implemented as pre-play lottery using an application to pre-order one or more lottery tickets. The application program can record your request [e.g., specific type, quantity, numbers, etc.]. Later, when the application program is in an “authorization” location (e.g., at an authorized gas station or store) to buy the lottery tickets, the application can initiate the buying of the pre-ordered lottery tickets. The tickets can be e-purchased at an authorized location directly with the application program. Alternatively, the application program can communicate with a point of sale (POS) terminal at the authorized location to make the purchase.


In one embodiment, the application program can also monitor wins and notify the user via the application program, email message or text. The application program can also can keep track of usage history, play and/or performance.



FIG. 5 illustrates an exemplary computer device 500 suitable for use with at least one embodiment of the invention. The methods, processes and/or graphical user interfaces discussed above can be provided by a computer device. Although the computing device 500 is depicted as a desktop computer, the computer device 500 can represent computing device of different form factors, such as a server machine or a portable electronic device. The computer device 500 can includes a display monitor 502 having a single or multi-screen display 504 (or multiple displays), a housing 506, a keyboard 508, and a mouse 510. The mouse 510 is representative of one type of pointing device. The housing 506 can house a processing unit (or processor), system memory and a hard drive (not shown). The housing 506 can also house a drive 512, such as a DVD, CD-ROM or floppy drive. The drive 512 can also be a removable hard drive, a Flash or EEPROM device, etc. Regardless, the drive 512 may be utilized to store and retrieve software programs incorporating computer code that implements some or all aspects of the invention, data for use with the invention, and the like. Although CD-ROM 514 is shown as an exemplary computer readable storage medium, other computer readable storage media including floppy disk, tape, Flash or EEPROM memory, memory card, system memory, and hard drive may be utilized. In one implementation, a software program for the computer system 500 is provided in the system memory, the hard drive, the drive 512, the CD-ROM 514 or other computer readable storage medium and serves to incorporate the computer code that implements some or all aspects of the invention.



FIG. 6 is a block diagram of an example computing device 600. The computing device 600 can be the gaming/betting server machine(s) 112 or portable electronic devices 106-112 illustrated in FIG. 1, or any other server or computing device used to carry out the various embodiments disclosed herein. The computing device 600 can include a processor 602 that pertains to a microprocessor or controller for controlling the overall operation of the computing device 600. The computing device 600 can store any type of data and information as discussed above in a file system 604 and a cache 606. The file system 604 is, typically, a storage disk or a plurality of disks, and/or solid-state Flash drive. The file system 604 typically provides high capacity storage capability for the computing device 600. However, since the access time to the file system 604 is relatively slow, the computing device 600 can also include a cache 606. The cache 606 is, for example, Random-Access Memory (RAM) provided by semiconductor memory. The relative access time to the cache 606 is substantially shorter than for the file system 604. However, the cache 606 does not have the large storage capacity of the file system 604. Further, the file system 604, when active, consumes more power than does the cache 606. The computing device 600 also includes a RAM 620 and a Read-Only Memory (ROM) 622. The ROM 622 can store programs, utilities or processes to be executed in a non-volatile manner. The RAM 620 provides volatile data storage, such as for the cache 606.


The computing system 600 also includes a user input device 608 that allows a user of the computing system 600 to interact with the computing system 600. For example, the user input device 608 can take a variety of forms, such as a button, keypad, touch screen, dial, and the like. Still further, the computing system 600 includes a display 610 (screen display) that can be controlled by the processor 602 to display information to the user. A data bus 611 can facilitate data transfer between at least the file system 604, the cache 606, the processor 602, and the CODEC 612.


The computing system 600 can also include a network/bus interface 616 that couples to a data link 618. The data link 618 allows the computing system 600 to couple to a host computer or data network, such as the Internet. The data link 618 can be provided over a wired connection or a wireless connection. In the case of a wireless connection, the network/bus interface 616 can include a wireless transceiver.


Additional details on social gaming and the like are provided in U.S. patent application Ser. No. 13/296,182, filed Nov. 14, 2011 and entitled “Social Gaming,” which is hereby incorporated herein by reference in its entirety for all purposes.


Additional details on viral events and distribution and the like are provided in U.S. patent application Ser. No. 12/617,717, filed Nov. 12, 2009 and entitled “Gaming System Including A Viral Event,” which is hereby incorporated herein by reference in its entirety for all purposes.


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.

Claims
  • 1. A method for facilitating gaming on a portable electronic device, comprising: determining whether the portable electronic device is in a wagering authorized location or a wagering unauthorized location;operating a software program in a non-wagering mode if the determining determines that the location of the portable electronic device is located in a wagering unauthorized location, and wherein, when the software program is operated in the non-wagering mode, the software program supports operation of a non-wagering game and at least one player account of the non-wagering game is able to earn a reward or advantage from its play of the non-wagering game; andoperating the software program in a wagering mode if the determining determines that the location of the portable electronic device is located in a wagering authorized location, and wherein, when the software program is operated in the wagering mode, the software program supports operation of a wagering game and the at least one player account of the wagering game is able to utilize the reward or advantage that the at least one player account previously earned from its play of the non-wagering game.
  • 2. A non-transitory computer readable medium including at least computer program code for an software program stored thereon, the software program being executable by a computing device, comprising: computer program code for determining whether the computing device is in a wagering authorized location or a wagering unauthorized location;computer program code for operating a software program in a non-wagering mode if the location of the portable electronic device is located in a wagering unauthorized location, and wherein, when the software program is operated in the non-wagering mode, the software program supports operation of a non-wagering game and at least one player account of the non-wagering game is able to earn a reward or advantage from its play of the non-wagering game; andcomputer program code for operating the software program in a wagering mode if the location of the portable electronic device is located in a wagering authorized location, and wherein, when the software program is operated in the wagering mode, the software program supports operation of a wagering game and the at least one player account of the wagering game is able to utilize the reward or advantage that the at least one player account previously earned from its play of the non-wagering game.
  • 3. The method as recited in claim 1, wherein the reward or advantage is non-monetary.
  • 4. The method as recited in claim 1, wherein the reward or advantage is non-numerical.
  • 5. The method as recited in claim 1, wherein the reward or advantage is an earned reward that is earned when the software program is in the non-wagering mode.
  • 6. The method as recited in claim 1, wherein the software program is configured to receive a virtual wager when the software program is in the non-wagering mode.
  • 7. The method as recited in claim 6, wherein the virtual wager is based on virtual currency or virtual chips.
  • 8. The method as recited in claim 7, wherein the reward or advantage is an earned reward that is earned when the software program is in the non-wagering mode, and wherein the earned reward is based on the virtual currency or the virtual chips.
  • 9. The method as recited in claim 1, wherein the method comprises converting at least one of the reward or advantage that the at least one player account previously earned from its play of the software program in the non-wagering mode to a game play asset that is able to be used in play of the software program in a wagering mode.
  • 10. The method as recited in claim 9, wherein the converting is automatically performed when the software switches from the non-wagering mode to the wagering mode.
  • 11. The non-transitory computer readable medium as recited in claim 2, wherein the computing device is a portable electronic device, and wherein the reward or advantage utilized by the software program is modified when the software program switches between the wagering mode and the non-wagering mode.
  • 12. The non-transitory computer readable medium as recited in claim 11, wherein the modification is automatically performed when the software program switches from the non-wagering mode to the wagering mode.
  • 13. The non-transitory computer readable medium as recited in claim 2, wherein the reward or advantage is non-monetary.
  • 14. The non-transitory computer readable medium as recited in claim 2, wherein the reward or advantage is non-numerical.
  • 15. The non-transitory computer readable medium as recited in claim 2, wherein the reward or advantage is an earned reward that is earned when the software program is in the non-wagering mode.
  • 16. An electronic gaming system comprising: a portable electronic device operable to support mobile gaming; anda game controller comprising a processor and memory, the memory storing program code including instructions, the game controller executing the instructions which cause the game controller to, at least: determine whether the portable electronic device is in a wagering authorized location or a wagering unauthorized location;operate a software program in a non-wagering mode if the determining determines that the location of the portable electronic device is located in a wagering unauthorized location or a wagering authorized location, and wherein, when the software program is operated in the non-wagering mode, the software program is able to earn a reward or advantage from its play of the software program in the non-wagering mode; andoperate the software program in a wagering mode if the determining determines that the location of the portable electronic device is located in a wagering authorized location, and wherein, when the software program is operated in the wagering mode, the software program is able to utilize the reward or advantage previously earned from play of the software program in the non-wagering mode.
  • 17. The electronic gaming system as recited in claim 16, wherein the game controller is further operable to execute instructions which cause the game controller to convert the reward or advantage previously earned from the software program in the non-wagering mode to a game play asset that is able to be used in play of the software program in the wagering mode.
  • 18. The electronic gaming system as recited in claim 17, wherein the converting is automatically performed when the software switches from the non-wagering mode to the wagering mode.
  • 19. The electronic gaming system as recited in claim 16, wherein the game controller is further operable to execute instructions which cause the game controller to convert the reward or advantage previously earned from the software program in the non-wagering mode to a game play enhancement that is able to be used in play of the software program in the wagering mode.
  • 20. The electronic gaming system as recited in claim 16, wherein the game controller is further operable to execute instructions which cause the game controller to: present a plurality of conversion options for the reward or advantage previously earned from play of the software program in the non-wagering mode;receive a selection of at least one of the conversion options; andconvert, based on the selected at least one of the conversion options, the reward or advantage previously earned from its play of the software program in the non-wagering mode to a game play asset or enhancement that is able to be used in play of the software program in the wagering mode.
CROSS-REFERENCE TO OTHER APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/449,717, filed Jun. 24, 2019, and entitled “LOCATION-BASED MOBILE GAMING SYSTEM AND METHOD”, which in turn is a divisional application of U.S. patent application Ser. No. 15/427,307, filed Feb. 8, 2017, and entitled “ADAPTIVE MOBILE DEVICE GAMING SYSTEM”, which is hereby incorporated by reference herein, and which is in turn a divisional application of U.S. patent application Ser. No. 14/211,536, filed Mar. 14, 2014, and entitled “ADAPTIVE MOBILE DEVICE GAMING SYSTEM”, which is hereby incorporated by reference herein, and which in turn claim 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 also incorporates by reference herein the following applications: (i) U.S. patent application Ser. No. 14/017,159 filed Sep. 3, 2013, and entitled “METHOD AND SYSTEM FOR LOCALIZED MOBILE GAMING”; and (ii) U.S. Provisional patent application Ser. No. 14/017,150 filed Sep. 3, 2013, and entitled “METHOD AND SYSTEM FOR LOCALIZED MOBILE GAMING”.

US Referenced Citations (660)
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 Rolls 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 Rolls 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 Cohen et al. Jul 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
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
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 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
20080013906 Matsuo Jan 2008 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
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
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 Heinnann 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
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 et al. May 2013 A1
20130132745 Schoening et al. May 2013 A1
20130165210 Nelson Jun 2013 A1
20130185559 Morel Jul 2013 A1
20130196052 Pokropinski, Jr. et al. Aug 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
20140080578 Nguyen Mar 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 Barwicz Jan 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
Foreign Referenced Citations (11)
Number Date Country
2033638 May 1980 GB
2062923 May 1981 GB
2096376 Oct 1982 GB
2097570 Nov 1982 GB
2335524 Sep 1999 GB
12005000454 May 2007 PH
WO 05073933 Aug 2005 WO
WO 2008027621 Mar 2008 WO
WO 2009026309 Feb 2009 WO
WO 2009062148 May 2009 WO
WO 2010017252 Feb 2010 WO
Non-Patent Literature Citations (314)
Entry
Benston, Liz, “Harrahs Launches iPhone App; Caesars Bypasses Check-in,” Las Vegas Sun, Las Vegas, NV. Jan. 8, 2010.
Finnegan, Amanda, “Casinos Connecting with Customers via iPhone Apps”, May 27, 2010, Las Vegas Sun, Las Vegas, NV.
Gaming Today Staff, “Slots showcased at 2009 National Indian Gaming Assoc.”, GamingToday.com, Apr. 14, 2009.
Green, Marian, “Testing Texting Casino Journal”, Mar. 2, 2009.
Hasan, Ragib, et al., “A Survey of Peer-to-Peer Storage Techniques for Distributed File Systems”, National Center for Supercomputing Applications, Department of Computer Science, University of Illinois at Urbana Champaign, Jun. 27, 2005.
Jones, Trahern, “Telecon-equipped drones could revolutionize wireless market”, azcentral.com, http://www.azcentral.com/business/news/articles/20130424telecom-equipped-drones-could-revolutionize-wireless-market.html, downloaded Jul. 2, 2013, 2 pages.
Yancey, Kitty Bean, “Navigate Around Vegas with New iPhone Apps”, USA Today, Jun. 3, 2010.
IAPS, Daily Systems LLC, 2010.
U.S. Appl. No. 12/945,888, filed Nov. 14, 2010.
U.S. Appl. No. 12/945,889, filed Nov. 14, 2010.
U.S. Appl. No. 13/622,702, filed Sep. 19, 2012.
U.S. Appl. No. 13/800,917, filed Mar. 13, 2013.
U.S. Appl. No. 13/296,182, filed Nov. 15, 2011.
U.S. Appl. No. 13/801,234, filed Mar. 13, 2013.
U.S. Appl. No. 13/801,171, filed Mar. 13, 2013.
U.S. Appl. No. 13/843,192, filed Mar. 15, 2013.
U.S. Appl. No. 13/843,087, filed Mar. 15, 2013.
U.S. Appl. No. 13/632,743, filed Oct. 1, 2012.
U.S. Appl. No. 13/632,828, filed Oct. 1, 2012.
U.S. Appl. No. 13/833,953, filed Mar. 15, 2013.
U.S. Appl. No. 12/619,672, filed Nov. 16, 2009.
U.S. Appl. No. 13/801,121, filed Mar. 13, 2013.
U.S. Appl. No. 12/581,115, filed Oct. 17, 2009.
U.S. Appl. No. 13/801,076, filed Mar. 13, 2013.
U. S. U.S. Appl. No. 13/617,717, filed Nov. 12, 2009.
U. S. 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. 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. U.S. Appl. No. 12/797,610 dated Dec. 8, 2011.
Final Office Action for U. S. U.S. Appl. No. 12/797,610 dated Jun. 6, 2012.
Office Action for U. S. U.S. Appl. No. 12/797,610 dated Feb. 26, 2013.
Office Action for U.S. Appl. No. 12/757,968, dated May 9, 2012.
Final Office Action for U.S. Appl. No. 12/757,968, dated Nov. 29, 2012.
Office Action for U.S. Appl. No. 12/757,968, dated Apr. 25, 2013.
Office Action for U.S. Appl. No. 12/797,616 dated Mar. 15, 2012.
Final Office Action for U.S. Appl. No. 12/797,616 dated Oct. 13, 2012.
Office Action for U.S. Appl. No. 12/797,616 dated Feb. 13, 2013.
Final Office Action for U.S. Appl. No. 12/797,616 dated May 8, 2013.
Office Action for U.S. Appl. No. 13/296,182 dated Dec. 5, 2012.
Brochure, 5000 Ft. Inc., 1 page, Nov. 2010.
Frontier Fortune game, email notification, MGM Resorts Intl., Aug. 9, 2013.
“Getting Back in the Game: Geolocation Can Ensure Compliance with New iGaming Regulations”, White Paper, Quova, Inc., 2010.
Notice of Allowance of U.S. Appl. No. 12/619,672, dated Aug. 23, 2013.
Office Action for U.S. Appl. No. 13/633,118, dated Sep. 20, 2013.
Office Action for U.S. Appl. No. 13/801,256, dated Jul. 2, 2013.
Notice of Allowance for U.S. Appl. No. 12/619,672, dated Oct. 3, 2013.
Notice of Allowance for U.S. Appl. No. 12/757,968, dated Oct. 11, 2013.
Final Office Action for U.S. Appl. No. 12/797,610, dated Jul. 10, 2013.
Notice of Allowance for U.S. Appl. No. 12/757,968, dated Dec. 18, 2013.
Office Action for U.S. Appl. No. 12/945,889, dated Dec. 18, 2013.
Office Action for U.S. Appl. No. 13/632,828, dated Jul. 30, 2013.
Restriction Requirement for U.S. Appl. No. 13/801,256, dated Dec. 30, 2013.
Office Action for U.S. Appl. No. 13/801,171, dated Dec. 26, 2013.
Office Action for U.S. Appl. No. 13/801,234, dated Jan. 10, 2014.
Final Office Action for U.S. Appl. No. 13/296,182, dated Feb. 12, 2014.
Office Action for U.S. Appl. No. 12/617,717, dated Feb. 25, 2014.
Office Action for U.S. Appl. No. 13/801,076, dated Mar. 28, 2014.
Final Office Action for U.S. Appl. No. 13/633,118, dated Apr. 3, 2014.
Office Action for U.S. Appl. No. 13/843,192, dated Apr. 3, 2014.
Office Action for U.S. Appl. No. 13/632,743, dated Apr. 10, 2014.
Office Action for U.S. Appl. No. 13/801,121, dated Apr. 11, 2014.
Final Office Action for U.S. Appl. No. 12/945,889, dated Jun. 30, 2014.
Notice of Allowance for U.S. Appl. No. 12/617,717, dated Jul. 14, 2014.
Office Action for U.S. Appl. No. 13/801,121, dated Sep. 24, 2014.
Office Action for U.S. Appl. No. 13/801,171, dated Sep. 22, 2014.
Office Action for U.S. Appl. No. 13/801,234, dated Oct. 1, 2014.
Office Action for U.S. Appl. No. 13/801,271, dated Oct. 31, 2014.
Final Office Action for U.S. Appl. No. 13/843,192, dated Oct. 21, 2014.
Office Action for U.S. Appl. No. 13/632,743, dated Oct. 23, 2014.
Office Action for U.S. Appl. No. 12/945,889, dated Oct. 23, 2014.
Office Action for U.S. Appl. No. 13/632,828, dated Nov. 7, 2014.
Office Action for U.S. Appl. No. 12/797,610, dated Dec. 15, 2014.
Final Office Action for U.S. Appl. No. 12/945,889, dated Feb. 12, 2015.
Final Office Action for U.S. Appl. No. 13/801,171, dated Mar. 16, 2015.
Office Action for U.S. Appl. No. 13/833,116, dated Mar. 27, 2015.
Office Action for U.S. Appl. No. 13/632,828, dated Apr. 10, 2015.
Final Office Action for U.S. Appl. No. 13/801,121, dated Apr. 21, 2015.
Final Office Action for U.S. Appl. No. 13/557,063, dated Apr. 28, 2015.
Office Action for U.S. Appl. No. 13/296,182, dated Jun. 5, 2015.
Office Action for U.S. Appl. No. 13/843,192, dated Jun. 19, 2015.
Office Action for U.S. Appl. No. 12/797,610, dated Jul. 14, 2015.
Final Office Action for U.S. Appl. No. 13/833,953, dated Jul. 17, 2015.
Notice of Allowance for U.S. Appl. No. 12/945,889, dated Jul. 22, 2015.
Office Action for U.S. Appl. No. 12/797,616, dated Aug. 10, 2015.
Final Office Action for U.S. Appl. No. 13/801,234, dated Aug. 14, 2015.
Final Office Action for U.S. Appl. No. 13/833,116, dated Sep. 24, 2015.
Office Action for U.S. Appl. No. 13/801,121, dated Oct. 2, 2015.
Office Action for U.S. Appl. No. 14/017,150, dated Oct. 7, 2015.
Office Action for U.S. Appl. No. 14/017,159, dated Oct. 7, 2015.
Office Action for U.S. Appl. No. 13/801,271 dated Oct. 19, 2015.
Office Action for U.S. Appl. No. 14/211,536 dated Oct. 19, 2015.
Final Office Action for U.S. Appl. No. 13/632,828, dated Oct. 22, 2015.
Office Action for U.S. Appl. No. 14/217,066, dated Dec. 17, 2015.
Notice of Allowance for U.S. Appl. No. 13/557,063, dated Dec. 23, 2015.
Office Action for U.S. Appl. No. 13/296,182, dated Dec. 23, 2015.
Final Office Action for U.S. Appl. No. 13/843,192, dated Dec. 30, 2015.
Office Action for U.S. Appl. No. 13/801,076, dated Jan. 11, 2016.
Office Action for U.S. Appl. No. 12/945,888, dated Jan. 22, 2016.
Final Office Action for U.S. Appl. No. 12/797,616, dated Jun. 12, 2016.
Office Action for U.S. Appl. No. 13/843,087, dated Feb. 25, 2016.
Office Action for U.S. Appl. No. 13/800,917, dated Feb. 25, 2016.
Office Action for U.S. Appl. No. 13/801,234, dated Mar. 8, 2016.
Office Action for U.S. Appl. No. 14/216,986, dated Mar. 9, 2016.
Final Office Action for U.S. Appl. No. 13/801,271, dated Mar. 11, 2016.
Office Action for U.S. Appl. No. 13/622,702, dated Mar. 22, 2016.
Final Office Action for U.S. Appl. No. 13/633,118, dated Mar. 24, 2016.
Final Office Action for U.S. Appl. No. 14/189,948, dated Apr. 6, 2016.
Final Office Action for U.S. Appl. No. 12/797,610, dated Apr. 21, 2016.
Final Office Action for U.S. Appl. No. 14/017,150, dated Apr. 26, 2016.
Final Office Action for U.S. Appl. No. 13/801,121, dated May 11, 2016.
Final Office Action for U.S. Appl. No. 14/017,159, dated Jun. 6, 2016.
Office Action for U.S. Appl. No. 13/801,171, dated Jun. 6, 2016.
Office Action for U.S. Appl. No. 13/843,192, dated Jun. 9, 2016.
Final OA for U.S. Appl. No. 12/945,888, dated Jun. 28, 2016.
Notice of Allowance for U.S. Appl. No. 13/833,953, dated Jul. 6, 2016.
Final Office Action for U.S. Appl. No. 13/801,171, dated May 21, 2014.
Final Office Action for U.S. Appl. No. 13/801,234, dated May 22, 2014.
Office Action for U.S. Appl. No. 14/211,536, dated Jul. 13, 2016.
Notice of Allowance for U.S. Appl. No. 13/801,076, dated Jul. 11, 2016.
Office Action for U.S. Appl. No. 13/296,182, dated Jul. 20, 2016.
Restriction Requirement for U.S. Appl. No. 13/296,182, dated Oct. 12, 2012.
Advisory Action for U.S. Appl. No. 13/296,182, dated May 8, 2014.
Advisory Action for U.S. Appl. No. 13/843,192, dated May 8, 2014.
Office Action for U.S. Appl. No. 14/217,066, dated Dec. 22, 2016.
Final Office Action for U.S. Appl. No. 14/216,986, dated Sep. 23, 2016.
Office Action for U.S. Appl. No. 14/017,159, dated Sep. 23, 2016.
Office Action for U.S. Appl. No. 13/632,743, dated Sep. 23, 2016.
Final Office Action for U.S. Appl. No. 13/801,234, dated Oct. 14, 2016.
Final Office Action for U.S. Appl. No. 13/843,087, dated Oct. 13, 2016.
Final Office Action for U.S. Appl. No. 13/622,702, dated Oct. 13, 2016.
Office Action for U.S. Appl. No. 14/189,948, dated Nov. 7, 2016.
Final Office Action for U.S. Appl. No. 14/211,536, dated Mar. 14, 2014.
Notice of Allowance for U.S. Appl. No. 13/833,116, dated Oct. 11, 2016.
Notice of Allowance for U.S. Appl. No. 13/801,271, dated Dec. 2, 2016.
Notice of Allowance for U.S. Appl. No. 12/797,610, dated Dec. 7, 2016.
Notice of Allowance for U.S. Appl. No. 13/632,828, dated Dec. 16, 2016.
Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 19, 2016.
Notice of Allowance for U.S. Appl. No. 14/211,536, dated Dec. 28, 2016.
Notice of Allowance for U.S. Appl. No. 13/801,256, dated Jan. 20, 2017.
Office Action for U.S. Appl. No. 13/800,917, dated Feb. 3, 2017.
Final Office Action for U.S. Appl. No. 12/797,616, dated Feb. 10, 2017.
Office Action for U.S. Appl. No. 12/945,888, dated Feb. 28, 2017.
Final Office Action for U.S. Appl. No. 14/189,948, dated Mar. 17, 2017.
Office Action for U.S. Appl. No. 15/400,840, dated Mar. 10, 2017.
Notice of Allowance for U.S. Appl. No. 13/801,121, dated Mar. 29, 2017.
Office Action for U.S. Appl. No. 15/270,333, dated Mar. 30, 2017.
Office Action for U.S. Appl. No. 15/402,945, dated Apr. 5, 2017.
Office Action for U.S. Appl. No. 15/271,488, dated Apr. 19, 2017.
Final Office Action for U.S. Appl. No. 14/217,066, dated Apr. 21, 2017.
Office Action for U.S. Appl. No. 14/216,986 dated Apr. 26, 2017.
Office Action for U.S. Appl. No. 13/801,171, dated Jun. 14, 2017.
Office Action for U.S. Appl. No. 14/017,159, dated Jun. 29, 2017.
Notice of Allowance for U.S. Appl. No. 15/270,333, dated Jul. 5, 2017.
Final Office Action for U.S. Appl. No. 13/800,917, dated Jul. 13, 2017.
Notice of Allowance for U.S. Appl. No. 13/801,234, dated Jul. 5, 2017.
Notice of Allowance for U.S. Appl. No. 14/217,066, dated Jul. 14, 2017.
Final Office Action for U.S. Appl. No. 14/518,909, dated Jul. 19, 2017.
Final Office Action for U.S. Appl. No. 13/801,121, dated Sep. 15, 2016.
Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 17, 2015.
Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 19, 2016.
Notice of Allowance for U.S. Appl. No. 15/293,751, dated Aug. 4, 2017.
Advisory Action for U.S. Appl. No. 14/189,948, dated Jul. 28, 2017.
Final OA for U.S. Appl. No. 13/801,256, dated Aug. 15, 2014.
Final OA for U.S. Appl. No. 13/801,256, dated Feb. 18, 2015.
Advisory Action for U.S. Appl. No. 13/801,256, dated Dec. 5, 2014.
Office Action for U.S. Appl. No. 13/801,256, dated Jan. 12, 2016.
Final Office Action for U.S. Appl. No. 13/801,256, dated Aug. 16, 2016.
Office Action for U.S. Appl. No. 13/622,702, dated Aug. 31, 2017.
Office Action for U.S. Appl. No. 12/945,888, dated Sep. 1, 2017.
Office Action for U.S. Appl. No. 14/017,150, dated Sep. 7, 2017.
Notice of Allowance for U.S. Appl. No. 14/189,948, dated Sep. 13, 2017.
Office Action for U.S. Appl. No. 15/138,086, dated Oct. 19, 2017.
Notice of Allowance for U.S. Appl. No. 15/402,945 dated Nov. 21, 2017.
Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 13, 2017.
Final Office Action for U.S. Appl. No. 15/271,488, dated Dec. 21, 2017.
Office Action for U.S. Appl. No. 15/671,133, dated Dec. 22, 2017.
Final Office Action for U.S. Appl. No. 14/216,986, dated Dec. 26, 2017.
Restriction Requirement for U.S. Appl. No. 15/427,307, dated Jan. 17, 2018.
Office Action for U.S. Appl. No. 15/798,363, dated Jan. 26, 2018.
Office Action for U.S. Appl. No. 15/427,291, dated Jan. 29, 2018.
Final Office Action for U.S. Appl. No. 14/017,159, dated Feb. 1, 2018.
Final Office Action for U.S. Appl. No. 13/622,702, dated Feb. 22, 2018.
Office Action for U.S. Appl. No. 15/811,654, dated Feb. 22, 2018.
Final Office Action for U.S. Appl. No. 13/622,702, dated Feb. 27, 2018.
Final Office Action for U.S. Appl. No. 15/427,308, dated Mar. 19, 2018.
Office Action for U.S. Appl. No. 15/876,095, dated Apr. 3, 2018.
Office Action for U.S. Appl. No. 15/835,448, dated Apr. 4, 2018.
Office Action for U.S. Appl. No. 15/427,307, dated Apr. 9, 2018.
Office Action for U.S. Appl. No. 14/216,986, dated Apr. 6, 2018.
Office Action for U.S. Appl. No. 15/426,898 dated Apr. 16, 2018.
Notice of Allowance for U.S. Appl. No. 15/402,945, dated May 25, 2018.
Office Action for U.S. Appl. No. 15/495,973, dated Jun. 4, 2018.
Notice of Allowance for U.S. Appl. No. 15/427,291 dated Jun. 18, 2018.
Notice of Allowance for U.S. Appl. No. 15/271,488, dated Jun. 19, 2018.
Notice of Allowance for U.S. Appl. No. 15/480,295, dated Jun. 20, 2018.
Office Action for U.S. Appl. No. 14/963,106, dated Jun. 22, 2018.
Office Action for U.S. Appl. No. 14/993,055, dated Jun. 22, 2018.
Final Office Action for U.S. Appl. No. 15/427,307, dated Jul. 9, 2018.
Notice of Allowance for U.S. Appl. No. 13/633,118, dated Aug. 3, 2018.
Office Action for U.S. Appl. No. 15/671,133, dated Aug. 9, 2018.
Office Action for U.S. Appl. No. 15/427,308, dated Aug. 15, 2018.
Office Action for U.S. Appl. No. 15/798,363, dated Aug. 29, 2018.
Office Action for U.S. Appl. No. 15/428,922 dated Sep. 17, 2018.
Office Action for U.S. Appl. No. 15/495,975, dated Sep. 21, 2018.
Notice of Allowance for U.S. Appl. No. 15/271,488, dated Sep. 24, 2018.
Notice of Allowance for U.S. Appl. No. 15/876,095, dated Sep. 24, 2018.
Office Action for U.S. Appl. No. 13/622,702, dated Oct. 3, 2018.
Office Action for U.S. Appl. No. 15/293,751, dated Apr. 6, 2017.
Notice of Allowance for U.S. Appl. No. 13/801,171, dated Oct. 31, 2018.
Final Office Action for U.S. Appl. No. 15/835,448, dated Nov. 2, 2018.
Final Office Action for U.S. Appl. No. 15/480,295, dated Nov. 7, 2018.
Final Office Action for U.S. Appl. No. 14/963,106, dated Dec. 14, 2018.
Final Office Action for U.S. Appl. No. 14/993,055, dated Dec. 14, 2018.
Office Action for U.S. Appl. No. 16/162,358, dated Dec. 31, 2018.
Office Action for US Patent Application No. 16/162.358, dated Dec. 31, 2018.
Office Action for U.S. Appl. No. 14/017,159, dated Jan. 11, 2019.
Office Action for U.S. Appl. No. 15/426,898, dated Jan. 11, 2019.
Final Office Action for U.S. Appl. No. 15/495,973, dated Jan. 11, 2019.
Office Action for U.S. Appl. No. 14/216,986, dated Jan. 14, 2019.
Office Action for U.S. Appl. No. 15/427,307, dated Jan. 18, 2019.
Final Office Action for U.S. Appl. No. 15/798,363, dated Feb. 4, 2019.
Office Action for U.S. Appl. No. 16/125,614, dated Feb. 25, 2019.
Final Office Action for U.S. Appl. No. 15/495,975, dated Apr. 18, 2019.
Office Action for U.S. Appl. No. 15/671,133, dated May 1, 2019.
Notice of Allowance for U.S. Appl. No. 14/216,986, dated May 17, 2019.
Notice of Allowance for U.S. Appl. No. 14/518,909, dated May 17, 2019.
Office Action for U.S. Appl. No. 12/797,616, dated Jun. 5, 2019.
Office Action for U.S. Appl. No. 15/427,308, dated Jun. 14, 2019.
Office Action for U.S. Appl. No. 15/811,654, dated Jun. 14, 2019.
Office Action for U.S. Appl. No. 15/674,480, dated Jun. 20, 2019.
Notice of Allowance for U.S. Appl. No. 15/835,448, dated Jul. 3, 2019.
Final Office Action for U.S. Appl. No. 16/162,358, dated Jul. 11, 2019.
Office Action for U.S. Appl. No. 16/190,050, dated Sep. 19, 2019.
Office Action for U.S. Appl. No. 14/017,150, dated Oct. 9, 2019.
Final Office Action for U.S. Appl. No. 15/671,133, dated Oct. 18, 2019.
Office Action for U.S. Appl. No. 15/835,448 dated Oct. 12, 2019.
Notice of Allowance for U.S. Appl. No. 15/495,975, dated Oct. 23, 2019.
Notice of Allowance for U.S. Appl. No. 14/993,005, dated Nov. 27, 2019.
Final Office Action for U.S. Appl. No. 15/427,308, dated Nov. 27, 2019.
Office Action for U.S. Appl. No. 15/798,363, dated Jan. 8, 2020.
Office Action for U.S. Appl. No. 15/835,448, dated Mar. 5, 2020.
Office Action for U.S. Appl. No. 15/495,975, dated Mar. 17, 2020.
Office Action for U.S. Appl. No. 16/248,759, dated Apr. 1, 2020.
Final Office Action for U.S. Appl. No. 14/017,150, dated Apr. 17, 2020.
Notice of Allowance for U.S. Appl. No. 15/798,363, dated May 12, 2020.
Office Action for U.S. Appl. No. 16/357,316, dated May 21, 2020.
Office Action for U.S. Appl. No. 15/674,480, dated Jun. 5, 2020.
Notice of Allowance for U.S. Appl. No. 15/480,295, dated Jun. 15, 2020.
Office Action for U.S. Appl. No. 13/622,702, dated Jun. 22, 2020.
Office Action for U.S. Appl. No. 15/811,654, dated Jun. 26, 2020.
Office Action for U.S. Appl. No. 16/579,754, dated Jul. 22, 2020.
Office Action for U.S. Appl. No. 16/219,940, dated Jul. 22, 2020.
Office Action for U.S. Appl. No. 16/559,553, dated Sep. 11, 2020.
Office Action for U.S. Appl. No. 16/794,212, dated Sep. 11, 2020.
Restriction Requirement for U.S. Appl. No. 16/600,395, dated Sep. 18, 2020.
Final Office Action for U.S. Appl. No. 16/248,759, dated Oct. 6, 2020.
Final Office Action for U.S. Appl. No. 15/671,133, dated Oct. 7, 2020.
Final Office Action for U.S. Appl. No. 16/357,316, dated Oct. 8, 2020.
Final Office Action for U.S. Appl. No. 16/183,632, dated Oct. 9, 2020.
Office Action for U.S. Appl. No. 16/590,347, dated Oct. 13, 2020.
Office Action for U.S. Appl. No. 16/449,717, dated Nov. 9, 2020.
Final Office Action for U.S. Appl. No. 13/622,702, dated Nov. 30, 2020.
Final Office Action for U.S. Appl. No. 15/674,480, dated Dec. 7, 2020.
Office Action for U.S. Appl. No. 16/168,813, dated Dec. 8, 2020.
Office Action for U.S. Appl. No. 16/600,395, dated 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, dated Jan. 21, 2021.
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. 16/183,632, dated May 4, 2021.
Office Action for U.S. Appl. No. 16/559,553, dated Jun. 1, 2021.
Notice of Allowance for U.S. Appl. No. 16/579,754, dated Jul. 16, 2021.
Office Action for U.S. Appl. No. 13/622,702, dated Jul. 19, 2021.
Office Action for U.S. Appl. No. 16/357,316, dated Jul. 20, 2021.
Office Action for U.S. Appl. No. 16/993,154, dated Jul. 28, 2021.
Final Office Action for U.S. Appl. No. 16/351,416, dated Sep. 1, 2021.
Office Action for U.S. Appl. No. 15/671,133, dated Sep. 2, 2021.
Notice of Allowance for U.S. Appl. No. 16/794,212, dated Sep. 3, 2021.
Office Action for U.S. Appl. No. 17/020,761, dated Sep. 9, 2021.
Office Action for U.S. Appl. No. 16/916,001, dated Sep. 17, 2021.
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.
Advisory Action for U.S. Appl. No. 13/632,828, dated Feb. 25, 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 (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 (Non-Final Rejection) dated Oct. 6, 2022 for U.S. Appl. No. 17/160,343 (pp. 1-15).
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).
Related Publications (1)
Number Date Country
20220012982 A1 Jan 2022 US
Provisional Applications (2)
Number Date Country
61873300 Sep 2013 US
61799862 Mar 2013 US
Divisions (2)
Number Date Country
Parent 15427307 Feb 2017 US
Child 16449717 US
Parent 14211536 Mar 2014 US
Child 15427307 US
Continuations (1)
Number Date Country
Parent 16449717 Jun 2019 US
Child 17485289 US