Configurable virtual gaming zone

Abstract
In one embodiment, zone-based gaming activity within a gaming establishment can be configured. The method can, for example, include: setting a location within the gaming establishment for the zone-based gaming activity, the location being at least one defined region within the gaming establishment; configuring a virtual gaming zone for the location within the gaming establishment for the zone-based gaming activity; identifying one or more gaming devices that are within the virtual gaming zone; and permitting the identified one or more gaming devices that are within the virtual gaming zone to participate in the zone-based gaming activity.
Description
BACKGROUND OF THE INVENTION

Casinos have long sought new ways to induce play on the gaming devices. They try to increase player time on gaming devices, average wager amount, and speed of play. Various techniques have been used in attempts to gain higher casino profits. One such technique in the casino gaming industry is the addition of bonus opportunities. This usually takes the form of an additional bonus game in conjunction with a base game of a gaming device.


As another avenue to encourage play, casinos adopted a new technology in the form of player tracking systems. In a player tracking systems a player registers for a player-tracking card at a registration desk. The player is typically given a plastic magnetic strip player card for use while playing gaming devices on the casino floor or at the card tables. Each player card has an ID on it that associates it with a player record in a player tracking database. Players are awarded loyalty points, credits or other representations of value. Such awards can then be redeemed at a later time.


More recent additions to the casino player loyalty systems provide bonus prizes or prize pools that are periodically given to players on a random basis (e.g. mystery bonusing, mystery jackpot). This gives the player a more instantaneous and larger reward versus the slow accrual of loyalty points. This is done for several reasons: to help induce play on the gaming device, to encourage players to become carded players; to create player loyalty for the casino, and to provide bonus prizes without modifying the base gaming device software.


However, these methods of awarding bonuses have several limitations. They may require that a player become a member of a club when they wish to remain anonymous. Also, these methods require that a casino patron be engaged in wagering activities.


Group games involving many players are known to be implemented in a predefined area, where a number of gaming machines on the casino floor are roped off for the special event. Only machines within the enclosed area are eligible for participating in a group game or a bonusing award. One popular game type set up in this manner is the slot tournament game. From the casino operator's perspective, such a rigid physical configuration is time-consuming to set up, tying up valuable assets, and lack the flexibility to be reconfigured quickly. From the player's perspective, such an approach also requires them to move around to find the sweet spot—the location where the special machines and awards are set up. Not only this is inconvenient for some players, it interrupts their wagering activities.


With the advent of mobile technology, additional opportunities for accommodating casino patrons have arisen. Handheld gaming devices allow players to participate in wagering activities in traditional, as well as non-traditional gaming areas, such as a hotel room, a restaurant, or next to a pool. Certain restrictions apply to handheld gaming devices, in which the device's location determines the eligibility of the device to conduct wagering activities or particular game-related features.


There is a continuing need to provide new and different gaming devices and gaming systems as well as new and flexible ways to provide awards to players on mobile and traditional gaming devices, including bonus awards and special game features that enhance their playing experiences.


SUMMARY

Embodiments are described herein in the context of a reconfigurable gaming zone. The present disclosure relates generally to gaming systems, more specifically to game events control systems with in a gaming system, and even more specifically to game events control systems to reconfigure gaming zones in gaming systems.


In one embodiment, a method of operating a zone-based gaming activity includes generating, in response to a request, a reconfigurable zone, determining one or more eligible participants, and modifying said zone to change the number of eligible participants.


In another embodiment, a method for configuring the operating constraints of a zone-based gaming activity including defining a location for deploying the zone, defining the size of a zone, defining one or more criteria for selecting eligible participants, and defining one or more criteria for modifying the zone.


In still another embodiment, a method of operating a zone-based gaming activity includes randomly generating, in response to a request, a location of a reconfigurable zone, randomly determining one or more eligible participants, and modifying said zone to change the number of eligible participants.


The present invention provides other hardware configured to perform the methods of the invention, as well as software stored in a machine-readable medium (e.g., a tangible storage medium) to control devices to perform these methods. These and other features will be presented in more detail in the following detailed description of the invention and the associated figures.





BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more example embodiments and, together with the description of example embodiments, serve to explain the principles and implementations.


In the drawings:



FIG. 1 illustrates an example schematic of a gaming network.



FIG. 2 illustrates an example method for configuring zone-based game play.



FIG. 3 illustrates an example flow chart for zone modification.



FIG. 4 illustrates an example flow chart for the zone reduction step.



FIGS. 5A-5D illustrate example zone configurations and zone reductions.





DESCRIPTION OF EXAMPLE EMBODIMENTS

Embodiments are described herein in the context of a reconfigurable award zone. The following detailed description is illustrative only and is not intended to be in any way limiting. Other embodiments will readily suggest themselves to such skilled persons having the benefit of this disclosure. Reference will now be made in detail to implementations as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts.


In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application- and business-related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.


In accordance with the present invention, the components, process steps, and/or data structures may be implemented using various types of operating systems, computing platforms, computer programs, and/or general purpose machines. In addition, those of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein.



FIG. 1 illustrates an example schematic of a gaming system. The gaming system, identified in its broadest aspects as 100, may be configured to communicate and/or control a plurality of gaming devices or electronic gaming machines (EGMs) 135 and a plurality of mobile gaming devices (MGDs) 125. The gaming system 100 may have a game server 130 configured to communicate with a zone controller 140, location tracker 110, player tracking server 150, configuration database 160, and accounting server 170.


Zone Controller


The zone controller 140 conducts the operation of the reconfigurable award zone game. In one embodiment, the zone controller 140 may be a standalone local controller networked with the plurality of EGMs 135 within a specific area (e.g., such as a carousel of slot machines, gaming devices near the door, and the like) and/or a number of MGDs 125 that are grouped together in a logical group (e.g., spinning reels slot machines, video poker devices, table games, progressive slots, mobile gaming devices, and the like). In another embodiment, the zone controller may be integrated in the EGMs 135. When integrated in EGMs 135, the zone controller is a software application that runs inside the gaming device or slot machine, leveraging hardware available within the slot machine to perform its functions. Regardless of whether the zone controller is implemented as a standalone device or a software application, the zone controller can be located near the EGMs 135 to simplify network connections, or can be located remotely from the EGMs 135 and communicating over a suitable network.


The zone controller 140 may communicate with the MGD 125 and EGM 135 via either a wireless link, a wired connection, or an optical connection. The network architecture maybe that of a client-server network, a token-ring network, a peer-to-peer network, or an ad-hoc wireless network. Though not a requirement, it is desirable for the zone controller to be able to have both wired and wireless capabilities. In one embodiment, the zone controller may be configured for networking with fixed gaming devices over a wired Ethernet network, networking with mobile gaming devices over a short range Bluetooth wireless network, and networking with the system servers (such as Player Tracking server, Location Tracking server, etc.) over a longer range WiFi, WiMax, or Cellular connection. In another embodiment, the entire network connection may be wireless.


When using wireless communication, any type of standard or protocol may be used to implement the communication. Examples of acceptable wireless communication protocols include CDMA, GSM, and related derivatives. In one example, the zone controller 140 uses a wireless communication standard such as Bluetooth™ to communicate with portable wireless devices, although other wireless communication protocols such as IrDA (Infrared Direct Access), IEEE 802.11n, IEEE 802.11b, IEEE 802.11x (e.g. other IEE802.11 standards), Zigbee, Wireless USB, Ultra Wide Band, Near Field Communication (NFC), and HomeRF may also be used. Any type of wireless transmission may be implemented as well, including but not limited to optical, electromagnetic energy, radio or other frequency communication and infrared-type communications.


In a typical deployment cycle, the zone controller 140 retrieves the operating parameters of the award zone, implements the parameters to create an award zone, provisions the zone-based game feature, selects the eligible participants, notifies them, operates the periodic zone modification, determines the new number of participants, notifies them, stores the game states, monitors for the zone modification signal, decides if the gaming ending condition occurred, and awards the prize(s) to the remaining eligible participant(s) when the game ends, if applicable.


Antenna and Wireless Interface


In one embodiment, zone controller 140 may be configured to communicate with MGD 125 and EGM 135 via an antenna 115. Antenna 115 may receive and transmit signals to and from the game system 100 and receive and transmit signals from a wireless interface 145 of the MGD 125 or EGMs 135. As is known in the art, the wireless interface 145 may also operate to demodulate, decode and otherwise process information to and from remote locations. Any known wire or optical communication system may be used and are well known in the art and will not be discussed in detail herein.


Gaming Devices


Both the EGMs 135 and MGDs 125 may be referred to as gaming devices. The electronic gaming machines (EGMs) 135 may correspond to gaming devices typically found in the gaming environment such as slot machines, video poker machines, video blackjack machines, video keno machines, video bingo machines, pachinko machines, and video lottery terminals. In one embodiment, the EGMs may be positioned at or near play table games so that for players who prefer to play table games, the zone controller 140 may communicate with the gaming devices associated with players at the gaming tables. The EGM 135 may also be smart TVs, kiosks, or electronic game tables such as electronic tables made by well known gaming manufacturers such as Digideal Corporation, Elektroncek, Shuffle Master, Pokertek, and others.


The mobile gaming devices (MGDs) 125 may be any portable electronic device such as a cell phone, a smart phone, a portable media player, a laptop computer, a tablet computer, a portable gaming device, a personal digital assistant or the like.


Thus, it is contemplated that communication between the zone controller 140 and EGM 135 and MGD 125 may be located within the gaming establishment where players are allowed by gaming regulations to participate in a gaming activity. When a zone controller 140 notifies EGM 135 and MGD 125 that they are eligible to participate in the zone play, the notification goes to all devices in the manner that is appropriate for that device. By looking up the EGM's 135 and MGD's 125 registry database, or by querying the device itself, the message can be tailored to the device's capabilities. For example, a slot machine's or EGM's notification may go through the Player Tracking device installed on the machine, while the MGD 125 may receive a text message.


Game Server


Game server 130 may be configured to manage and control the operation of games of chance played on gaming devices 135 and MGDs 125. The game server 130 may be configured to store and download games, transmit game software and outcomes relating to the game of chance being played, or, alternatively, be configured to determine a winning game outcome and/or appropriate payout. The game server may be configured to perform any other function desired by the user such as determining bonus events, payouts, and the like.


Accounting Server


Accounting server 170 may be configured to receive, store and transmit accounting information relating to a player's account. Accounting information may include any accounting information such as the amount of input of monies, payment of monies, wagers and similar financial events occurring at the MGD 125 or the EGM 135. The accounting server 170 may also be configured to store award amounts or running totals associated with particular groups or categories of player preferences, interests or attributes.


Player Tracking Server


Player tracking server 150 may be configured to store player tracking information. Player tracking information may include player tracking points/credits accumulated by the player, the amount of wins and losses by the player, and any other player account information desired to be tracked. The player tracking information may be combined or associated with other player information. For example, a player may be enrolled in the gaming establishment's player club and may be awarded certain complimentary offers as that player accumulates points/credits. In use, after the player registers with the gaming device (e.g. swiping a player tracking card, bumping an NFC-capable smart phone, entering authentication information such as an identification and/or personal identification numbers), the player tracking server 150 can record the player's wagering activity.


Alternative Servers


Although not illustrated in FIG. 1, gaming system may have other additional servers such as a marketing/promotion server to transmit marketing and promotional information to MGD 125 and/or EGM 135, auditing server to audit gaming information stored in the various databases, authentication server to authenticate the MGD 125, EGM 135, software, and/or players, an administrative server to track expenditures by a player during his visit to the gaming establishment, a game history server to serve up the game's historical track records, a concierge server to assist in making reservations at restaurants or purchasing tickets for entertainment events, and other similar servers.


Configuration Database


Configuration database 160 may be configured to store a plurality of zone information and operating parameters associated with each plurality of zone information. The operating parameters may include information such as the initial zone size, frequency of game deployment, modification type (e.g., expansion or contraction), frequency of game modification, the number of desired participants, eligibility requirements of participants, rate of modification of the zone, game features (e.g., win multipliers, free spins, mystery bonus, jackpots, and the like) associated with the zone, gaming awards, and any other operating parameters desired by the gaming establishment. The value for each of the plurality of parameters may be predefined or randomly selected. For example, the zone location can be predefined at a specific area within the gaming establishment, such as at coordinate (x, y, z) on a casino floor. The zone location may be any predefined area such as a sphere having a radius of 15 yards. In another example, the radius of the sphere may be randomly selected using a random number generator. In yet another example, the range of the zone location may be randomly chosen within a predefined range appropriate for the gaming establishment such as 1 yard to 25 yards.


Configuration database 160 may also be configured to store gaming data such as game state data and operating data of the reconfigurable award zone game. Storing gaming data of the award zone game allows recovery of the gaming activity and information when unexpected events such as a power failure, a sudden loss of communication on a mobile gaming device 125, and the like occur. The stored gaming data allows for recovery of the game of chance after unexpected or expected pauses, such as a prescribed half-time break for the players. Furthermore, the game state and operating data can also be used to reconstruct the game for the purposes of auditing, game analysis, player dispute resolution, and the like. Example game states include initialization state, zone modification state, players notification state, award state, participant determination state, and the like. Example operating data may include the current number of participant in the game, player identification, game of chance selected, the amount of rewards remaining, current zone size and location, current number of zone modification, current time, and the like.


Location Tracker and Database


The location of gaming devices 135 and MGD 125 within the gaming establishment may be determined using location tracker 110. Location tracker 110 may determine the location of the EGM 135 and MGD 125 within an active zone, time at the specification location, amount of time spent at the location, and any other location information and data. The location information and data may be stored in location database 120. Although location tracking for fixed devices, such as traditional gaming machines or game tables, may not be necessary, the gaming establishment may still desire to record the location information and data. For mobile gaming devices 125, location tracker 110 may periodically update the location of each MGD 125. For example, the location of each MGD 125 may be tracked and updated every ten (10) seconds, thirty (30) seconds, thirty (30) minutes, or any other desired time period. The tracking of both fixed 135 and mobile gaming devices 125 within a zone is important to assure fairness to each of the players.


Any known tracking technology may be used to track the location of the EGM 135 and MGD 125. For example, U.S. Pat. No. 7,580,995 entitled “Systems and methods for locating mobile computer users in a wireless network” describes a WLAN technology for locating and tracking mobile devices, which is hereby incorporated by reference.


Location and detection of the EGM 135 and/or MGD 125 may be determined as a function of received signal strength indicator (RSSI) values obtained from the EGM 135 and/or MGD 125. As a general rule, the higher the signal strength at an access point (AP), the closer a transmitting wireless device is presumed to be to the AP. Changes in the signal strength as the wireless device moves about the gaming establishment allows for tracking the wireless device. For example, if there are at least three APs that receive a signal from the wireless device, trilateration/triangulation can be used to determine the location of the device within the gaming establishment. Trilateration is a method of determining the position of the wireless device as a function of the distances between the wireless device and each of the APs. A detailed explanation of trilateration will not be described further to prevent obfuscation of the invention. However, various locationing methods that may be used with the present invention are described in “Location Systems: An Introduction to the Technology Behind Location Awareness,” by Anthony LaMarca and Eyal de Lara, Morgan & Claypool Publishers, 2008, ISBN #978-1598295825, which is incorporated herein by reference for all purposes.


Additionally, EGMs 135 and/or MGDs 125 may be operable to include conventional position location hardware and software. For example, the mobile device 125 may include one or more of positioning technologies such as global position system (GPS), wireless assisted GPS (A-GPS), cell identifier (CELL ID), Forward Link Trilateration (FLT), wireless assisted protocol (WAP) based location, geography markup language (GML) based location, and the like. Location tracker 110 may store the location of every EGMs 135 and/or MGDs 125 in database 120. Location tracking server 110 may track the location of all gaming devices on the casino floor in substantially real time (or as close as possible), and feed the data to database 120. Location database 120, in addition to having a live location feed of all gaming devices on the casino floor may also contain a layout of the gaming establishment. This allows the gaming system 100 to know where each EGMs 135 and/or MGDs 125 is within the gaming establishment at any desirable granularity of time. The gaming establishment may be any location where games of chance may be played such as a casino, hotel, sports bar, riverboat, grocery store, sports stadium, airplane, or the like.


In one embodiment, the gaming devices themselves may determine their own location and transmit its location to the location tracker 110. Each EGMs 135 and/or MGDs 125 may detect its location within the gaming establishment and transmit its location to location tracker 110 for storage in the location database 120. In another embodiment, an external, trusted gaming device (e.g. an external device that is registered and authenticated) such as, for example, an intermediary gaming trusted device maybe attached to the gaming device and independently detect and transmit the gaming device's location to the location database 120. The location of the gaming devices 125, 135 may be determined periodically or on-demand at any desired time interval. In another embodiment, location tracker 110 may ping the gaming devices 125, 135 for their locations. Once pinged, gaming devices 125, 135 may transmit their locations to location tracker 110.



FIG. 2 illustrates an example method for configuring zone-based game play. The process may begin with determining the activity configuration 202. This includes determining the operating constraints such as the various attributes of the zone, participants, and any other gaming related constraints. For example, the location and initial size of the zones are operating constraints. Additional operating constraints will be discussed below. In one embodiment the operating constraints are determined prior to initiation of the activity and stored in a database, such as configuration database 160 illustrated in FIG. 1. In other embodiments, some of the operating constraints may be determined as needed or desired after initiation of the activity. For example, eligible participant criteria could be selected after initiation if insufficient eligible participants are available with the current criteria. Furthermore, the operating constraints can be preset, or randomly set at the time of deployment of the award or game of chance.


Zone Request


A zone request may be processed at 210. The zone request may be processed by, for example, a zone controller 140 as illustrated in FIG. 1. The zone request may be made directly and manually by a venue staff member. Alternatively, a venue operator may define zone requests in advance of a zone start time that are stored until the start time, or shortly before the start time, at which point they are processed. The zone initiation process may be scheduled to occur periodically, randomly, or when a predetermined condition is satisfied. For example, when an aggregated bet amount has been wagered in the zone, when there has been two (2) or more four-of-a-kind in the previous two (2) hours, when there were more than 50 game losses within one (1) minute in the zone, when the number of players in an area exceeds 100, or any other similar predetermined conditions.


In another embodiment, the zone request may be processed by a gaming server, such as, for example, gaming server 130 illustrated in FIG. 1. The gaming server may be programmed to automatically generate and process zone requests based on a specific time, the location of gaming devices 125, 135, preference information obtained from a player tracking server, such as, for example, player tracking server 150 illustrated in FIG. 1, or any other predefined criteria. For example, a zone initiation request may be generated only if the density of active gaming devices in a particular area reaches a predefined threshold value.


The zone initiation request may be associated with configuration parameters for the zone-based game features to be played. The associated parameters may be retrieved when needed, such as, for example, from database server 160 illustrated in FIG. 1. In an alternative embodiment, the parameters may be retrieved from a memory in the zone controller 140 if the configuration parameter are pre-emptively pushed to the gaming server.


The configuration parameters may be predefined or randomly chosen. The parameters may be within a range of permissible values or operating constraints. The permissible values or operating constraints may be presented by a server, such as, for example, game server 130 or zone controller 140 as illustrated in FIG. 1. The parameters, whether predefined or defined in a zone request, may include at least the identification of the type of game event to be conducted (i.e., progressive jackpot, mystery bonus, promotional award, free game vouchers give out, upcoming events, win/loss trend for the area, and the like), criteria for starting the game (e.g., a minimum number of participants), zone parameter information, game times (e.g., start and end times), participant eligibility criteria, prize identification, and the like.


The parameters can be grouped into zone initialization parameters (i.e., size, location), game feature parameters (type of game features, casino promotions being conducted, and how they operate), players parameters (i.e., who is eligible, at what level, for how long), zone operating parameters (i.e., contracting zone, expanding zone), and the like.


These above groups may also include parameters such as the initial zone size, frequency of deployment, modification type (expansion or contraction), frequency of modification, the number of desired participants, eligibility requirements of participants, the rate of modification of the zone, the game feature (such as win multipliers, free spins, mystery bonus, jackpots, etc.) to be provisioned for the zone, the one or more awards, and the likes. The value of each parameter can be preset, or randomly chosen. For example, the zone location can be preset at coordinate (x,y,z) on a casino floor, the zone size to be spherical, and the radius of the sphere is 15 yards. These values, when randomly chosen, can be generated by a random number generator to be within one or more ranges that are appropriate for the casino's particular size.


Once the parameters are set, the parameters may be stored in a database, such as, for example, configuration database server 160 as illustrated in FIG. 1, for later retrieval by the zone controller. Alternatively, the parameters may also be pushed from the database to the appropriate zone controller, prior to the activation of the zone activity, for use when triggered by a predefined event (e.g., when there are more than 10 players at 7 pm on or near a game machine carousel).


Zone Activation


A zone must be selected and activated at 220. In one embodiment, the zone may be selected and activated upon receipt of an activate request. The zone selection can be randomly selected from a set of stored, pre-determined locations. The selection can be made by casino personnel or other individuals with the proper authority. The selection can be made based on past and/or current conditions. For example, areas with low traffic or newly installed gaming machines may be chosen. Another example would be to identify particular areas on days of the week or time of the day and randomly select a location within those areas.


Zone activation for a given activity request may be made by a controller, such as, for example, the zone controller 140 illustrated in FIG. 1. First, a geographic position may be selected from available space or gaming machines, henceforth designated as the focus. The focus will form the approximate center around which a zone is created. The focus needs not to be one dimensional. The focus can be a point, a line, an area, or a volume. It should be understood that because the zone can have an arbitrary shape, the term focus is not restricted to its geometric definition. The focus can be randomly selected or determined by parameters in the zone request. The focus can coincide with a specific gaming device or an arbitrary geographic location. In one embodiment, more than one focus may be selected.


The available space can be defined by a venue operator to be the whole of their property or some subset. Gaming regulations may also restrict the allowable available space. In addition, a casino operator may desire to prevent particular areas from being allowed to be included in a zone. The available area can be predetermined or be set by one of the zone request parameters. The available space does not need to be restricted to one contiguous area. Various embodiments of zone configurations will be discussed in greater detail below.


After the focus is selected an initial zone may be generated based on focus position. The zone can be a predetermined size/shape or obtained from the zone request. Information supplied by the location database server 120 can be used for the generation of the zone. For instance, the casino floor map where gaming devices are located can be provided when the zone is being specified, whether randomly or predefined. The zone can be of any arbitrary shape, such as a circle, triangle, rectangle, spiral, or any other shape. For example, by specifying a radius associated with the selected geographic position, a circular zone is created. In another example, a line is drawn on the floor map, and locations within 20 feet of the line may be defined to be within the zone (i.e., defining a rectangle centering on the initially drawn line to be the logical boundaries of an active game-event zone).


The zone can be implicitly defined by selecting specific gaming devices near the focus. If more than one focus has been selected, a zone for each focus will be generated. A zone may be associated with a geographic boundary such as the perimeter of a casino floor or banks of gaming devices. A zone may be associated with a logical boundary, corresponding to access points in a wireless network. Optionally, zone parameters may be predetermined and stored in a database, such as, for example, the configuration database server 160 illustrated in FIG. 1. In this embodiment, the zone parameters may be pushed, pulled, selected, randomly or otherwise, and supplied with the zone request and activation.


Participant Determination


With a preliminary zone created, the potential participants may be determined at 230. The potential participants may be determined by calculating the number of individuals within, near, or adjacent the zone. This may be determined via any known methods. For example, individuals at stationary gaming devices can be located, even if they remain anonymous. Mobile individuals can be located using a location monitoring system, such as a monitoring system described in U.S. Pat. No. 6,353,390, entitled “Method and system of configuring a boundary and tracking an object thereby”, which is incorporated by reference herein. It should be understood that any method for locating individuals can be applied.


Depending on the zone request parameters, all individuals may be eligible for participation in the game. Optionally, the zone request parameters may require that only a subset of all individuals within the zone to be eligible, such as players who have been actively playing the gaming device for more than ten (10) minutes. The parameters could be related to player memberships (e.g., Gold Club members), play history (e.g., aggregate expenditures at the venue over the last month), and the like. Such determination may depend on being able to identify the potential participants via a player database, such as, for example, player tracking server 140. Optionally, an invitation to participate in the game may be transmitted to the gaming devices. The players at the gaming devices may then be required to respond within a specific time interval in order to participate in the event.


A determination of whether gaming rules are satisfied may be made at 240. If the gaming rules are not satisfied, the method may return to step 220 to re-activate the zone. For example, the number of potential participants may be evaluated. If there are too many potential participants (e.g. as required in the zone request parameters) which does not satisfy the gaming rules at 220, a zone reduction may occur at 220. Several methods can be used to reduce the zone. In one embodiment, the physical dimension of the zone can be decreased. For example, the radius of the zone may be decreased. In another example, an area based on a logical unit, such as a bank of gaming machines can be removed. In another example, the number of gaming devices may be removed randomly from the zone.


Alternatively, in another embodiment, the rules may not be satisfied at 240 if there are insufficient potential participants. In this embodiment, the zone may be enlarged at 220. A physical dimension of the zone can be increased, such as to include more gaming devices. In another example, the area may be based on a logical unit, for example, a bank of gaming machines can be added.


The process of participant determination and zone reconfiguration repeats until the number of potential participants required in the zone request parameters is satisfied. This number does not necessarily have to be a specific number; the zone request parameter could consist of a range of participants. For example, a minimum and maximum number could be specified.


As illustrated above, the players and gaming devices inside of a zone may participate in the zone activity. However, the reverse is also possible. In other words, in one embodiment, only participants and gaming devices outside a zone can participant. In another embodiment, other hybrid approaches may be possible. In one example, a certain percentage of players from outside the zone and a certain percentage of players inside the zone may participate in the game.


Saving Game Event State


The state of the game zones and their events may be saved at 250. The state of the zone may be saved in order to restore the game at a later time. For instance, a power interruption could require that a zone and its associated gaming event be restored when power is re-instituted. In another example, the zone play event maybe partitioned into multiple time segments, and needs to be restored upon resumption of the zone activity. The state of a zone and its associated events may be saved periodically and/or at any predetermined time interval. The time interval may be every thirty (30) seconds, every ten (10) seconds, every hour, or any other desired time interval.


The game state information may include the foci, zone parameters, participant information, zone request parameters and any other information required in order to complete the game. The saved data may reside in a database, such as, for example, the configuration database server 160 illustrated in FIG. 1 or in zone controller's 140 memory.


Zone Modification


The zone may be modified at 260. The zone may be modified for any number of reasons. For example, a modification can be made to decrease or to increase the number of participants playing the game. The zone may be increased or decreased at various intervals. The intervals may be predetermined or determined by the game state parameters. For example, in a zone reduction approach, participants that are outside the zone will automatically be removed. In another example, participants can gain access to the zone activity by moving into the zone in order to increase participants in the zone.


A notification may be transmitted to the participants informing them of the zone modification. For example, participants losing eligibility to play the game may be transmitted a removal notification. In another example, participants gaining eligibility, may be transmitted an acceptance notification to be included in the game.


Various indicators can also help the participant identify their current status. For example, pop up window on the player terminal, sounds, screen color change, flashing symbols, and the like may help to indicate whether the participant is part of or not part of the game. Maps of the game floor that include graphical depiction of the zone, the active players, and the eliminated players can also be displayed in the venue and/or at the player terminals as desired.


In one particular implementation that uses the zone reduction approach, after the zone is reduced in size, any participants located outside the zone may be eliminated from the game, either temporarily or permanently eliminated. In another embodiment, a participant may re-enter the activity by moving and playing a gaming device in the modified zone. In yet another embodiment, a participant may be required to satisfy a condition in to re-enter the zone. For example, the condition may be that the participant is offered a chance to buy their way back into the activity. Another condition may require the participant to begin a wagering activity within the zone to again become an eligible participant.


Trigger Condition


A determination of whether a trigger condition has occurred may be made at 270. A trigger condition may be time-based (i.e., the zone-based event expires after 5 minutes, and the like), event-based (i.e., terminate the zone-based activity when a player hits a jackpot, when there is less than a predetermined number of remaining players after a zone reduction, when there is more than 100 players after a zone expansion, when there is at least 10 zone modification iterations, and the like), or randomly chosen at some point in time. The triggering conditions may be predefined or, for example, specified in the zone request parameters.


If the condition is triggered at 270 prizes may be awarded at 280. If the trigger condition is not satisfied, the process returns to the zone modification step 360. In the event that an insufficient number of participants remain after a zone reduction, for example, zero participants remain in the current zone, the most recent set of participants may be used. For example, all remaining participants may be awarded the prize. In another example, a random subset of participates may be selected to receive the award.


Award Prizes


Prizes may be awarded at 280. In one embodiment, independent of how the winning participants are determined, the award may be provided to each winning participant. In one embodiment, a notification may be transmitted to either all the participants or just the winning participants. The notification may be transmitted to the gaming devices from a server, such as, for example, zone controller 140, game server 130, player tracking server 150, accounting server 170, configuration database server 160, or any other desired server.


The award may include at least the prize won, identifies the winner or list of winners, how to claim the prize, and any other information desired. Optionally, the notification sent to non-winners may include information that they did not win and a suggestion that they try again. In either case, the notification may include an invitation to play another game. The game results may also be reported at 290 to all the participants.



FIG. 3 illustrates an example flow chart for zone configuration. The method 300 may start with retrieving the zone parameters at 310. The zone parameters may be retrieved from a server or database, such as zone controller 140 illustrated in FIG. 1. In one embodiment, the zone parameters may be based upon or associated with a zone request. The zone request may include the zone location, the zone area, and the zone shape, as further described and illustrated in FIG. 5.


The zone geometry may be generated at 320. The zone geometry may be generated by determining a virtual boundary calculated from the configuration parameters (i.e., focal point and a radius for a circular zone, and the like). The virtual boundary may then be mapped onto a physical area of the casino floor thereby translating the zone area/volume data of the virtual boundary into physical coordinates.


The location of all gaming devices within the zone geometry may be obtained at 320. The location of the gaming device may be obtained, for example, from zone controller 140 illustrated in FIG. 1. The physical coordinates of the gaming machines may be obtained. This is feasible since, as discussed above, the physical location of the gaming machine, map of the casino floor, and any other locations, may be stored in a database, such as the location database 120 illustrated in FIG. 1.


The number of eligible participants may be determined at 340. Each mobile gaming device associated with a participant within the zone geometry may be considered an eligible participant. Additionally, any gaming machine being played by a player or a player playing at a gaming table may be considered an eligible participant. In one embodiment, the eligibility of a participant may be dependent on the zone request parameters.


A determination of whether there are enough participants may be made at 350. A minimum or a maximum number of participants may, for example, be one of the parameters included in the zone request. If there is not a sufficient number of eligible participants at 350, the zone geometry may be re-initialized at 355. In one embodiment, the zone area may be increased (not enough participants) or may be decreased (too many participants) by a pre-defined amount. In other embodiment, an estimate of the necessary zone size is calculated based on the current number of eligible participants and the minimum number of allowed eligible participants. In yet another embodiment, the re-initialized zone may include a different shape. In another embodiment, the zone request may be cancelled and a new one may be generated. If the number of eligible participants satisfies the configuration limit of eligible participants, the method 300 may continue with saving the state of the game at 360 or step 250 illustrated in FIG. 2.


Monitor Activities



FIG. 4 illustrates an example flow chart for zone modification. The zone-based activity may be initiated at 410 by, for example, the zone controller 140 illustrated in FIG. 1. The positions of the participants, as determined from the mobile and stationary devices, described above, may be monitored. The participant activities may also be monitored at 420. The activities may include wagering actions, bonus activity, and any other action that may be relevant for determining participant eligibility to play the game.


Zone Modification


In addition to monitoring player activities at 420, the zone controller may also track the time the game activity begun. A determination of whether to modify the zone may be made at 430. The determination of whether to modify the zone may be made periodically or at predetermined period of time after the game activity began. In one embodiment, the determination of whether to modify the zone may be predefined in the zone request. If such time has not occurred, the participants' positions and activities continue to be monitored at 420. However, if it is determined that it is time to modify the zone at 430, then the zone modification parameters may be implemented at 440.


Implement Zone Modification Parameter


Although discussed in detail with reference to FIG. 5, the zone may be modified by either being decreased or increased, thereby decreasing or increasing the number of eligible participants, respectively. In some zone activity, it may be desirable to decrease the zone and thereby decreasing the number of participants to heighten the excitement for the remaining players. Yet, in another implementation, it may be desirable to increase the zone to include more and more players in a viral fashion, inducing excitement throughout the entire floor. In this case, the initial players who were included in the zone activity gains additional advantage of being able to enjoy the zone privilege for a longer amount of time compared to latter induced members.


Notification


Participants may be notified of their status at 450. In one embodiment, all participants that were eligible before the zone modification are transmitted a notification notifying them of their current eligibility. In another embodiment, only currently eligible participants are transmitted a notification. The notification may be transmitted to the players through any known methods, such as a text message to the mobile gaming device, a flashing and/or colored indicator at the gaming device, pop-up message at the gaming device, or any other notification means. For example, a flashing green indicator on the gaming device's screen may indicate that a participant is still eligible to play the game while a steady red indicator may indicate that a participant is no longer eligible. Audible tones, sound effects or even music clips may also be used to indicate status. Various combinations of notifications may be possible. In one embodiment, the participant may be given the option to select how they would like to receive the notification.


End of Zone Activity


A determination of whether an ending trigger has been detected may be made at 460. A trigger condition may be time-based (i.e., the zone-based event expires after five (5) minutes, and the like), event-based (i.e., terminate the zone-based activity when a player hits a jackpot, when there is less than three (3) remaining players after a zone reduction, when there is more than 100 players after a zone expansion, when there is at least 10 zone modification iterations, and the like), or randomly chosen condition at some arbitrary point in time. If an ending trigger has been detected at 460, the participants may be notified of the winners and prizes at 470. If the ending trigger is not detected at 460, the method 400 may continue to monitor and save player activities at 420.


Zone Modification Examples



FIGS. 5A-5D illustrate example zone configurations and zone reductions. FIG. 5a illustrates an example circular zone. The circular zone is denoted by solid line 502. It has radius R and is centered around gaming device 504, which is also the focus. As mentioned previously, the focus is not restricted to a gaming device but can be selected to be any point on the casino floor. Located inside the zone 502 are gaming devices 506a-n and located outside the zone 502 is gaming device 525. In this example, only participants associated with gaming devices located within the zone 502 at the initiation of the game are eligible for an award. In another embodiment, only players outside the zone 502 are eligible for an award. In yet another implementation, only players within a predefine proximity to the zone 502 are eligible to participate in the zone activity.


In one example, as the zone is modified, the circular zone may be decreased. The radius R may be decreased by small segments, as illustrated by letter “x”. This has the effect of sequentially removing annular regions 1, 2, 3, indicated in the figure with dotted lines, from the zone. In one embodiment, the radius may be decreased by any length and need not be the same length. This allows greater variability in the evolution of the zone.


The decrements of the radium may occur at time intervals, regular, irregular, predefined, or based on predefined conditions. As the zone area is reduced, gaming devices may be eliminated from the zone 502, and thus the number of eligible participants is reduced. A trigger condition may interrupt this process at any step, depending on the zone request parameters. Similarly, the order of the removal of the annular regions does not need to proceed from the perimeter of the zone inward. Any order can be chosen, either randomly or predefined.



FIG. 5b illustrates another example circular zone having the focus centered on an arbitrary point on the casino floor. In this implementation, a zone 502 reduction process may take place where the future zone is within the boundary of the current zone 502.


Zone modification is also illustrated by illustrating a decrease the circular zone 502. In this embodiment the zone 502 is decreased by a specified area. The resulting area is then used to create a reduced circular zone, formed entirely within the zone 502. The focus of the reduced zone is different than the focus of the zone illustrated in FIG. 5a. The location of the new focus can be chosen using any method with the restriction that the reduced zone falls entirely within zone 502. With this embodiment, eligible participants may not be able to determine the location of the reduced zone.



FIG. 5c illustrates an example zone consisting of two separate, non-contiguous areas. In this example each zone 510 has a rectangular shape. However, the shape of the zone is not meant to be limiting as any shape may be used. Additionally, the area of each zone 510 may be different.


As illustrated in FIG. 5c, each zone 510 may have quadrilateral sections 512a-n, indicated by dotted lines. To modify the zone 510, each quadrilateral section may be removed sequentially to decrease the zone 510 size. The sections may be removed in any order and/or multiple sections may be removed simultaneously. For example, section 512a may be removed prior to or simultaneously with 512b. Additionally, the time intervals between section removal can be the same or different, based on an ordered sequence, or at random intervals.



FIG. 5d illustrates a random-type of zone 530. In this embodiment, an area around one group of gaming machines was omitted, as indicated by dashed line 534, thereby creating a “holes” in the zone 530. In addition, FIG. 5d illustrates two player stations 532 at a gaming table 545 that is omitted from the zone 530. The ability to create this type of zone is advantageous when, for example, one or more gaming machines are inoperative (e.g., players not betting enough, or not otherwise eligible). Alternatively, if two player stations are unoccupied when the activity begins, the players may not be permitted to participate in the gaming activity.


While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein.

Claims
  • 1. A method for configuring a zone-based gaming activity within a gaming establishment, the method comprising: setting a location within the gaming establishment for the zone-based gaming activity, the location being at least one defined region within the gaming establishment;configuring a virtual gaming zone formed from a geographic position being a focus randomly selected in the location within the gaming establishment for the zone-based gaming activity based on a random number generated by a random number generator;identifying one or more gaming devices that are within the virtual gaming zone eligible to participate in the zone-based gaming activity;enlarging the virtual gaming zone from the geographic position when the one or more gaming devices identified to be eligible to participate in the zone-based gaming activity is below a threshold, resulting in an enlarged virtual gaming zone; andpermitting the one or more gaming devices that are identified within the enlarged virtual gaming zone to participate in the zone-based gaming activity.
  • 2. The method of claim 1, further comprising selecting the enlarged virtual gaming zone based on data retrieved from a configuration database.
  • 3. The method of claim 1, further comprising selecting the enlarged virtual gaming zone based on eligibility data transmitted from the one or more gaming devices.
  • 4. The method of claim 1, wherein the threshold comprises at least one of a range of participating gaming devices, and a specified number of participating gaming devices.
  • 5. The method of claim 1, further comprising determining the one or more gaming devices to participate in the zone-based gaming activity based on one of whether the one or more gaming devices have been active for a period of time, memberships of players at the one or more gaming devices, and play history of players at the one or more gaming devices.
  • 6. The method of claim 1, further comprising enlarging the virtual gaming zone at a predetermined rate.
  • 7. The method of claim 1, further comprising displaying on the one or more gaming devices an indicator when the one or more gaming devices are determined to be eligible for the virtual gaming zone.
  • 8. A gaming system for configuring a zone-based gaming activity within a gaming establishment, the gaming system comprising: a plurality of gaming devices; andat least one server coupled to the gaming devices, and having at least one processor and memory storing a plurality of configuration parameters and computer programs, which, when executed, cause the at least one processor to at least: initiate a zone request based on the configuration parameters,configure a virtual gaming zone formed from a geographic position focused about a location randomly selected in the gaming establishment based on a random number generated by a random number generator and the zone request,initiate the zone-based gaming activity within the gaming establishment defined by the virtual gaming zone with at least one of the gaming devices within the virtual gaming zone that are eligible to participate in the zone-based gaming activity,enlarge the virtual gaming zone from the geographic position when the at least one of the gaming devices that are eligible to participate in the zone-based gaming activity is below a threshold, resulting in an enlarged virtual gaming zone, andinitiate the at least one of the gaming devices within the enlarged virtual gaming zone to participate in the zone-based gaming activity.
  • 9. The gaming system of claim 8, wherein the computer programs, when executed, cause the at least one processor to select the enlarged virtual gaming zone based on the configuration parameters retrieved.
  • 10. The gaming system of claim 8, wherein the computer programs, when executed, cause the at least one processor to select the enlarged virtual gaming zone based on eligibility data transmitted from the at least one of the gaming devices.
  • 11. The gaming system of claim 8, wherein the threshold comprises at least one of a range of participating gaming devices, and a specified number of participating gaming devices.
  • 12. The gaming system of claim 8, wherein the computer programs, when executed, cause the at least one processor to determine the at least one of the gaming devices to participate in the zone-based gaming activity based on one of whether the at least one of the gaming devices have been active for a period of time, memberships of players at the at least one of the gaming devices, and play history of players at the at least one of the gaming devices.
  • 13. The gaming system of claim 8, wherein the computer programs, when executed, cause the at least one processor to enlarge the virtual gaming zone at a predetermined rate.
  • 14. The gaming system of claim 8, wherein the computer programs, when executed, cause the at least one of the gaming devices to display an indicator when the at least one of the gaming devices are determined to be eligible for the virtual gaming zone.
  • 15. A non-transitory computer-readable medium comprising configuration parameters and computer programs for conducting a zone-based gaming activity within a gaming establishment that includes a plurality of gaming devices and at least one server coupled to the gaming devices, the at least one server having at least one processor, and the computer programs, which, when executed, cause the at least one processor to perform the steps of: setting a location in a define region within the gaming establishment for the zone-based gaming activity based on the configuration parameters;forming a virtual gaming zone from a geographic position randomly selected about the location based on a random number generated by a random number generator;determining a subset of the plurality of gaming devices within the virtual gaming zone that are eligible to participate in the zone-based gaming activity; andenlarging the virtual gaming zone from the geographic position when the subset of the plurality of gaming devices eligible to participate in the zone-based gaming activity is below a threshold, resulting in an enlarged virtual gaming zone that includes a different subset of the plurality of gaming devices.
  • 16. The non-transitory computer-readable medium of claim 15, wherein the computer programs, when executed, cause the at least one processor to perform the step of selecting the enlarged virtual gaming zone based on data retrieved from a configuration database.
  • 17. The non-transitory computer-readable medium of claim 15, wherein the computer programs, when executed, cause the at least one processor to perform the step of selecting the enlarged virtual gaming zone based on eligibility data transmitted from the different subset of the plurality of gaming devices.
  • 18. The non-transitory computer-readable medium of claim 15, wherein the threshold comprises at least one of a range of participating gaming devices, and a specified number of participating gaming devices.
  • 19. The non-transitory computer-readable medium of claim 15, wherein the computer programs, when executed, cause the at least one processor to perform the step of determining the different subset of the plurality of gaming devices to participate in the zone-based gaming activity based on one of whether the different subset of the plurality of gaming devices have been active for a period of time, memberships of players at the different subset of the plurality of gaming devices, and play history of players at the different subset of the plurality of gaming devices.
  • 20. The non-transitory computer-readable medium of claim 15, wherein the computer programs, when executed, cause the at least one processor to perform the step of enlarging the virtual gaming zone at a predetermined rate.
CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No. 15/427,308, filed Feb. 8, 2017, and entitled “RECONFIGURABLE VIRTUAL GAMING ZONE,” which is hereby incorporated herein by reference, and which in turn is a continuation of U.S. application Ser. No. 13/801,271, filed Mar. 13, 2013, and entitled “RECONFIGURABLE GAMING ZONE,” now U.S. Pat. No. 9,607,474, which is hereby incorporated herein by reference. This application is related to U.S. patent application Ser. No. 12/797,610, filed Jun. 10, 2010, entitled “LOCATION-BASED REAL-TIME CASINO DATA,” the content of which is incorporated in its entirety for all purposes.

US Referenced Citations (654)
Number Name Date Kind
2033638 Koppl Mar 1936 A
2062923 Nagy Dec 1936 A
4741539 Sutton et al. May 1988 A
4948138 Pease et al. Aug 1990 A
4969183 Reese Nov 1990 A
5067712 Georgilas Nov 1991 A
5275400 Weingardt Jan 1994 A
5429361 Raven et al. Jul 1995 A
5489103 Okamoto Feb 1996 A
5618232 Martin Apr 1997 A
5630757 Gagin May 1997 A
5655961 Acres et al. Aug 1997 A
5704835 Dietz, II Jan 1998 A
5727786 Weingardt Mar 1998 A
5833537 Barrie Nov 1998 A
5842921 Mindes Dec 1998 A
5919091 Bell et al. Jul 1999 A
5947820 Morro et al. Sep 1999 A
5997401 Crawford Dec 1999 A
6001016 Walker et al. Dec 1999 A
6039648 Guinn et al. Mar 2000 A
6059289 Vancura May 2000 A
6089977 Bennett Jul 2000 A
6095920 Sudahiro Aug 2000 A
6110041 Walker et al. Aug 2000 A
6142872 Walker et al. Nov 2000 A
6146271 Kadici Nov 2000 A
6146273 Olsen Nov 2000 A
6165071 Weiss Dec 2000 A
6231445 Acres May 2001 B1
6244958 Acres Jun 2001 B1
6270412 Crawford et al. Aug 2001 B1
6290600 Glasson Sep 2001 B1
6293866 Walker et al. Sep 2001 B1
6353390 Beri et al. Mar 2002 B1
6364768 Acres et al. Apr 2002 B1
6404884 Marwell et al. Jun 2002 B1
6416406 Duhamel Jul 2002 B1
6416409 Jordan Jul 2002 B1
6443452 Brune Sep 2002 B1
6491584 Graham et al. Dec 2002 B2
6500067 Luciano Dec 2002 B1
6505095 Kolls Jan 2003 B1
6508710 Paravia et al. Jan 2003 B1
6561900 Baerlocker et al. May 2003 B1
6592457 Frohm et al. Jul 2003 B1
6612574 Cole et al. Sep 2003 B1
6620046 Rowe Sep 2003 B2
6641477 Dietz, II Nov 2003 B1
6645078 Mattice Nov 2003 B1
6675152 Prasad Jan 2004 B1
6699128 Beadell Mar 2004 B1
6719630 Seelig et al. Apr 2004 B1
6749510 Globbi Jun 2004 B2
6758757 Luciano, Jr. et al. Jul 2004 B2
6773345 Walker et al. Aug 2004 B2
6778820 Tendler Aug 2004 B2
6780111 Cannon et al. Aug 2004 B2
6799032 McDonnell et al. Sep 2004 B2
6800027 Giobbi et al. Oct 2004 B2
6804763 Stockdale et al. Oct 2004 B1
6811486 Luciano, Jr. Nov 2004 B1
6843725 Nelson Jan 2005 B2
6846238 Wells Jan 2005 B2
6848995 Walker et al. Feb 2005 B1
6852029 Baltz et al. Feb 2005 B2
6869361 Sharpless et al. Mar 2005 B2
6875106 Weiss et al. Apr 2005 B2
6884170 Rowe Apr 2005 B2
6884172 Lloyd et al. Apr 2005 B1
6902484 Idaka Jun 2005 B2
6908390 Nguyen et al. Jun 2005 B2
6913532 Bearlocher et al. Jul 2005 B2
6923721 Luciano et al. Aug 2005 B2
6935958 Nelson Aug 2005 B2
6949022 Showers et al. Sep 2005 B1
6955600 Glavich et al. Oct 2005 B2
6971956 Rowe et al. Dec 2005 B2
6984174 Cannon et al. Jan 2006 B2
6997803 LeMay et al. Feb 2006 B2
7018292 Tracy et al. Mar 2006 B2
7032115 Kashani Apr 2006 B2
7033276 Walker et al. Apr 2006 B2
7035626 Luciano Apr 2006 B1
7037195 Schneider et al. May 2006 B2
7048628 Schneider May 2006 B2
7048630 Berg et al. May 2006 B2
7063617 Brosnan et al. Jun 2006 B2
7076329 Kolls Jul 2006 B1
7089264 Guido et al. Aug 2006 B1
7094148 Bearlocher et al. Aug 2006 B2
7105736 Laakso Sep 2006 B2
7111141 Nelson Sep 2006 B2
7144321 Mayeroff Dec 2006 B2
7152783 Charrin Dec 2006 B2
7169041 Tessmer et al. Jan 2007 B2
7169052 Beaulieu et al. Jan 2007 B2
7175523 Gilmore et al. Feb 2007 B2
7181228 Boesch Feb 2007 B2
7182690 Giobbi et al. Feb 2007 B2
7198571 LeMay Apr 2007 B2
RE39644 Alcorn et al. May 2007 E
7217191 Allen et al. May 2007 B2
7243104 Bill Jul 2007 B2
7247098 Bradford et al. Jul 2007 B1
7259718 Patterson et al. Aug 2007 B2
7275989 Moody Oct 2007 B2
7285047 Gielb et al. Oct 2007 B2
7311608 Danieli Dec 2007 B1
7314408 Cannon et al. Jan 2008 B2
7316615 Soltys et al. Jan 2008 B2
7316619 Nelson Jan 2008 B2
7318775 Brosnan et al. Jan 2008 B2
7326116 O'Donovan et al. Feb 2008 B2
7330108 Thomas Feb 2008 B2
7346358 Wood et al. Mar 2008 B2
7355112 Laakso Apr 2008 B2
7384338 Rothschild et al. Jun 2008 B2
7387571 Walker et al. Jun 2008 B2
7393278 Gerson et al. Jul 2008 B2
7396990 Lu et al. Jul 2008 B2
7415426 Williams et al. Aug 2008 B2
7425177 Rodgers et al. Sep 2008 B2
7427234 Soltys et al. Sep 2008 B2
7427236 Kaminkow et al. Sep 2008 B2
7427708 Ohmura Sep 2008 B2
7431650 Kessman Oct 2008 B2
7448949 Kaminkow et al. Nov 2008 B2
7500913 Baerlocher Mar 2009 B2
7510474 Carter Mar 2009 B2
7513828 Nguyen et al. Apr 2009 B2
7519838 Suurballe Apr 2009 B1
7559838 Walker et al. Jul 2009 B2
7563167 Walker et al. Jul 2009 B2
7572183 Olivas et al. Aug 2009 B2
7585222 Muir Sep 2009 B2
7602298 Thomas Oct 2009 B2
7607174 Kashchenko et al. Oct 2009 B1
7611409 Muir et al. Nov 2009 B2
7637810 Amaitis et al. Dec 2009 B2
7644861 Alderucci et al. Jan 2010 B2
7653757 Fernald et al. Jan 2010 B1
7693306 Huber Apr 2010 B2
7699703 Muir 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
8622823 Huynh Jan 2014 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
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
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
20030104860 Cannon et al. Jun 2003 A1
20030104865 Itkis et al. Jun 2003 A1
20030148809 Nelson Aug 2003 A1
20030148812 Paulsen Aug 2003 A1
20030162588 Brosnan et al. Aug 2003 A1
20030195024 Slattery Oct 2003 A1
20030199295 Vancura Oct 2003 A1
20030224852 Walker et al. Dec 2003 A1
20030224854 Joao Dec 2003 A1
20040002386 Wolfe et al. Jan 2004 A1
20040005919 Walker et al. Jan 2004 A1
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
20040116115 Ertel 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
20050125244 Schneider Jun 2005 A1
20050130728 Nguyen et al. Jun 2005 A1
20050130731 Englman Jun 2005 A1
20050136949 Barnes 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
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
20070155465 Walker Jul 2007 A1
20070159301 Hirt et al. Jul 2007 A1
20070161402 Ng et al. Jul 2007 A1
20070184896 Dickerson Aug 2007 A1
20070184904 Lee Aug 2007 A1
20070191109 Crowder et al. Aug 2007 A1
20070207852 Nelson et al. Sep 2007 A1
20070207854 Wolf et al. Sep 2007 A1
20070235521 Mateen Oct 2007 A1
20070238505 Okada Oct 2007 A1
20070241187 Alderucci et al. Oct 2007 A1
20070248036 Nevalainen Oct 2007 A1
20070257430 Hardy et al. Nov 2007 A1
20070259713 Fiden et al. Nov 2007 A1
20070259716 Mattice Nov 2007 A1
20070259717 Mattice et al. Nov 2007 A1
20070265984 Santhana Nov 2007 A1
20070270213 Nguyen et al. Nov 2007 A1
20070275777 Walker et al. Nov 2007 A1
20070275779 Amaitis et al. Nov 2007 A1
20070281782 Amaitis et al. Dec 2007 A1
20070281785 Amaitas et al. Dec 2007 A1
20070298858 Toneguzzo Dec 2007 A1
20070298873 Nguyen et al. Dec 2007 A1
20080015032 Bradford et al. Jan 2008 A1
20080020824 Cuddy et al. Jan 2008 A1
20080020845 Low Jan 2008 A1
20080032787 Low et al. Feb 2008 A1
20080058105 Combs Mar 2008 A1
20080070652 Nguyen et al. Mar 2008 A1
20080070681 Marks et al. Mar 2008 A1
20080076505 Nguyen Mar 2008 A1
20080076506 Nguyen et al. Mar 2008 A1
20080076548 Paulsen Mar 2008 A1
20080076572 Nguyen et al. Mar 2008 A1
20080096650 Baerlocher Apr 2008 A1
20080102916 Kovacs May 2008 A1
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
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
20090265105 Davis 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
20100113161 Walker May 2010 A1
20100115591 Kane-Esrig May 2010 A1
20100120486 DeWaal May 2010 A1
20100124967 Lutnick et al. May 2010 A1
20100130276 Fiden May 2010 A1
20100160035 Herrmann Jun 2010 A1
20100160043 Fujimoto et al. Jun 2010 A1
20100178977 Kim et al. Jul 2010 A1
20100184509 Sylla Jul 2010 A1
20100197383 Rader et al. Aug 2010 A1
20100197385 Aoki et al. Aug 2010 A1
20100203955 Sylla Aug 2010 A1
20100203957 Enzminger Aug 2010 A1
20100203963 Allen Aug 2010 A1
20100224681 Triplett Sep 2010 A1
20100227662 Speers et al. Sep 2010 A1
20100227670 Arezine et al. Sep 2010 A1
20100227671 Laaroussi Sep 2010 A1
20100227687 Speers et al. Sep 2010 A1
20100234091 Baerlocher et al. Sep 2010 A1
20100279764 Allen et al. Nov 2010 A1
20100323780 Acres Dec 2010 A1
20100325703 Etchegoyen Dec 2010 A1
20110009181 Speers et al. Jan 2011 A1
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
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
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
20130231192 Walker Sep 2013 A1
20130252730 Joshi Sep 2013 A1
20130281187 Skelton Oct 2013 A1
20130316808 Nelson Nov 2013 A1
20130337878 Shepherd Dec 2013 A1
20130337889 Gagner Dec 2013 A1
20140006129 Heath Jan 2014 A1
20140057716 Massing et al. Feb 2014 A1
20140087862 Burke Mar 2014 A1
20140094295 Nguyen Apr 2014 A1
20140094316 Nguyen Apr 2014 A1
20140121005 Nelson May 2014 A1
20140179431 Nguyen Jun 2014 A1
20140235332 Block 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
20160125695 Nguyen May 2016 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
20170154497 Nguyen Jun 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 (309)
Entry
Advisory Action for U.S. Appl. No. 13/632,828, dated Feb. 25, 2016.
Benston, Liz, “Harrahs Launches iPhone App; Caesars Bypasses Check-in,” Las Vegas Sun, Las Vegas, NV. Jan. 8, 2010.
Finnegan, Amanda, “Casinos Connecting with Customers via iphone Apps”, May 27, 2010, Las Vegas Sun, Las Vegas, NV.
Gaming Today Staff, “Slots showcased at 2009 National Indian Gaming Assoc.”, GamingToday.com, Apr. 14, 2009.
Green, Marian, “Testing Texting Casino Journal”, Mar. 2, 2009.
Hasan, Ragib, et al., “A Survey of Peer-to-Peer Storage Techniques for Distributed File Systems”, National Center for Supercomputing Applications, Department of Computer Science, University of Illinois at Urbana Champaign, Jun. 27, 2005.
Jones, Trahern, “Telecon-equipped drones could revolutionize wireless market”, azcentral.com, http://www.azcentral.com/business/news/articles/20130424telecom-equipped-drones-could-revolutionize-wireless-market.html, downloaded Jul. 2, 2013, 2 pages.
Yancey, Kitty Bean, “Navigate Around Vegas with New iPhone Apps”, USA Today, Jun. 3, 2010.
IAPS, Daily Systems LLC, 2010.
U.S. Appl. No. 12/945,888, filed Nov. 14, 2010.
U.S. Appl. No. 12/945,889, filed Nov. 14, 2010.
U.S. Appl. No. 13/622,702, filed Sep. 19, 2012.
U.S. Appl. No. 13/800,917, filed Mar. 13, 2013.
U.S. Appl. No. 13/296,182, filed Nov. 15, 2011.
U.S. Appl. No. 13/801,234, filed Mar. 13, 2013.
U.S. Appl. No. 13/801,171, filed Mar. 13, 2013.
U.S. Appl. No. 13/843,192, filed Mar. 15, 2013.
U.S. Appl. No. 13/843,087, filed Mar. 15, 2013.
U.S. Appl. No. 13/632,743, filed Oct. 1, 2012.
U.S. Appl. No. 13/632,828, filed Oct. 1, 2012.
U.S. Appl. No. 13/833,953, filed Mar. 15, 2013.
U.S. Appl. No. 12/619,672, filed Nov. 16, 2009.
U.S. Appl. No. 13/801,121, filed Mar. 13, 2013.
U.S. Appl. No. 12/581,115, filed Oct. 17, 2009.
U.S. Appl. No. 13/801,076, filed Mar. 13, 2013.
U.S. Appl. No. 13/617,717, filed Nov. 12, 2009.
U.S. Appl. No. 13/633,118, filed Oct. 1, 2012.
U.S. Appl. No. 12/797,610, filed Jun. 10, 2010.
U.S. Appl. No. 13/801,256, filed Mar. 13, 2013.
U.S. Appl. No. 12/757,968, filed Apr. 9, 2010.
U.S. Appl. No. 12/797,616, filed Jun. 10, 2010.
U.S. Appl. No. 13/557,063, filed Jul. 24, 2012.
U.S. Appl. No. 13/833,116, filed Mar. 15, 2013.
U.S. Appl. No. 13/801,271, filed Mar. 13, 2011.
Office Action for U.S. Appl. No. 12/945,888 dated Apr. 10, 2012.
Final Office Action for U.S. Appl. No. 12/945,888 dated Sep. 21, 2012.
Advisory Action for U.S. Appl. No. 12/945,888 dated Jan. 30, 2013.
Office Action for U.S. Appl. No. 12/581,115 dated Dec. 20, 2011.
Final Office Action for U.S. Appl. No. 12/581,115 dated Sep. 13, 2012.
Notice of Allowance for U.S. Appl. No. 12/581,115 dated May 24, 2013.
Office Action for U.S. Appl. No. 12/619,672 dated Dec. 20, 2011.
Final Office Action for U.S. Appl. No. 12/619,672 dated Nov. 6, 2012.
Office Action for U.S. Appl. No. 12/619,672 dated Mar. 7, 2013.
Office Action for U.S. Appl. No. 12/617,717 dated Oct. 4, 2011.
Office Action for U.S. Appl. No. 12/617,717 dated Apr. 4, 2012.
Advisory Action for U.S. Appl. No. 12/617,717 dated Jun. 12, 2011.
Office Action for U.S. Appl. No. 12/617,717 dated Jun. 17, 2013.
Office Action for U.S. Appl. No. 12/797,610 dated Dec. 8, 2011.
Final Office Action for U.S. Appl. No. 12/797,610 dated Jun. 6, 2012.
Office Action for U.S. Appl. No. 12/797,610 dated Feb. 26, 2013.
Office Action for U.S. Appl. No. 12/757,968, dated May 9, 2012.
Final Office Action for U.S. Appl. No. 12/757,968, dated Nov. 29, 2012.
Office Action for U.S. Appl. No. 12/757,968, dated Apr. 25, 2013.
Office Action for U.S. Appl. No. 12/797,616 dated Mar. 15, 2012.
Final Office Action for U.S. Appl. No. 12/797,616 dated Oct. 13, 2012.
Office Action for U.S. Appl. No. 12/797,616 dated Feb. 13, 2013.
Final Office Action for U.S. Appl. No. 12/797,616 dated May 8, 2013.
Office Action for U.S. Appl. No. 13/296,182 dated Dec. 5, 2012.
Brochure, 5000 Ft. Inc., 1 page, Nov. 2010.
Frontier Fortune game, email notification, MGM Resorts Intl., Aug. 9, 2013.
“Getting Back in the Game: Geolocation Can Ensure Compliance with New iGaming Regulations”, White Paper, Quova, Inc., 2010.
Notice of Allowance of U.S. Appl. No. 12/619,672, dated Aug. 23, 2013.
Office Action for U.S. Appl. No. 13/633,118, dated Sep. 20, 2013.
Office Action for U.S. Appl. No. 13/801,256, dated Jul. 2, 2013.
Notice of Allowance for U.S. Appl. No. 12/619,672, dated Oct. 3, 2013.
Notice of Allowance for U.S. Appl. No. 12/757,968, dated Oct. 11, 2013.
Final Office Action for U.S. Appl. No. 12/797,610, dated Jul. 10, 2013.
Notice of Allowance for U.S. Appl. No. 12/757,968, dated Dec. 18, 2013.
Office Action for U.S. Appl. No. 12/945,889, dated Dec. 18, 2013.
Office Action for U.S. Appl. No. 13/632,828, dated Jul. 30, 2013.
Restriction Requirement for U.S. Appl. No. 13/801,256, dated Dec. 30, 2013.
Office Action for U.S. Appl. No. 13/801,171, dated Dec. 26, 2013.
Office Action for U.S. Appl. No. 13/801,234, dated Jan. 10, 2014.
Final Office Action for U.S. Appl. No. 13/296,182, dated Feb. 12, 2014.
Office Action for U.S. Appl. No. 12/617,717, dated Feb. 25, 2014.
Office Action for U.S. Appl. No. 13/801,076, dated Mar. 28, 2014.
Final Office Action for U.S. Appl. No. 13/633,118, dated Apr. 3, 2014.
Office Action for U.S. Appl. No. 13/843,192, dated Apr. 3, 2014.
Office Action for U.S. Appl. No. 13/632,743, dated Apr. 10, 2014.
Office Action for U.S. Appl. No. 13/801,121, dated Apr. 11, 2014.
Final Office Action for U.S. Appl. No. 12/945,889, dated Jun. 30, 2014.
Notice of Allowance for U.S. Appl. No. 12/617,717, dated Jul. 14, 2014.
Office Action for U.S. Appl. No. 13/801,121, dated Sep. 24, 2014.
Office Action for U.S. Appl. No. 13/801,171, dated Sep. 22, 2014.
Office Action for U.S. Appl. No. 13/801,234, dated Oct. 1, 2014.
Office Action for U.S. Appl. No. 13/801,271, dated Oct. 31, 2014.
Final Office Action for U.S. Appl. No. 13/843,192, dated Oct. 21, 2014.
Office Action for U.S. Appl. No. 13/632,743, dated Oct. 23, 2014.
Office Action for U.S. Appl. No. 12/945,889, dated Oct. 23, 2014.
Office Action for U.S. Appl. No. 13/632,828, dated Nov. 7, 2014.
Office Action for U.S. Appl. No. 12/797,610, dated Dec. 15, 2014.
Final Office Action for U.S. Appl. No. 12/945,889, dated Feb. 12, 2015.
Final Office Action for U.S. Appl. No. 13/801,171, dated Mar. 16, 2015.
Office Action for U.S. Appl. No. 13/833,116, dated Mar. 27, 2015.
Office Action for U.S. Appl. No. 13/632,828, dated Apr. 10, 2015.
Final Office Action for U.S. Appl. No. 13/801,121, dated Apr. 21, 2015.
Final Office Action for U.S. Appl. No. 13/557,063, dated Apr. 28, 2015.
Office Action for U.S. Appl. No. 13/296,182, dated Jun. 5, 2015.
Office Action for U.S. Appl. No. 13/843,192, dated Jun. 19, 2015.
Office Action for U.S. Appl. No. 12/797,610, dated Jul. 14, 2015.
Final Office Action for U.S. Appl. No. 12/945,889, 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. 13/557,063, 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.
Notice of Allowance for U.S. Appl. No. 13/843,192, dated Aug. 10, 2016.
Office Action for U.S. Appl. No. 14/217,066, dated Dec. 22, 2016.
Final Office Action for U.S. Appl. No. 14/216,986, dated Sep. 23, 2016.
Office Action for U.S. Appl. No. 14/017,159, dated Sep. 23, 2016.
Office Action for U.S. Appl. No. 13/632,743, dated Sep. 23, 2016.
Final Office Action for U.S. Appl. No. 13/801,234, dated Oct. 14, 2016.
Final Office Action for U.S. Appl. No. 13/843,087, dated Oct. 13, 2016.
Final Office Action for U.S. Appl. No. 13/622,702, dated Oct. 13, 2016.
Office Action for U.S. Appl. No. 14/189,948, dated Nov. 7, 2016.
Final Office Action for U.S. Appl. No. 14/211,536, dated Mar. 14, 2014.
Notice of Allowance for U.S. Appl. No. 13/833,116, dated Oct. 11, 2016.
Notice of Allowance for U.S. Appl. No. 13/801,271, dated Dec. 2, 2016.
Notice of Allowance for U.S. Appl. No. 12/797,610, dated Dec. 7, 2016.
Notice of Allowance for U.S. Appl. No. 13/632,828, dated Dec. 16, 2016.
Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 19, 2016.
Notice of Allowance for U.S. Appl. No. 14/211,536, dated Dec. 28, 2016.
Notice of Allowance for U.S. Appl. No. 13/801,256, dated Jan. 20, 2017.
Office Action for U.S. Appl. No. 13/800,917, dated Feb. 3, 2017.
Final Office Action for U.S. Appl. No. 12/797,616, dated Feb. 10, 2017.
Office Action for U.S. Appl. No. 14/189,948, 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. 13/801,121, 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. 15/400,840, dated Mar. 10, 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. 13/801,256, 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/402,945 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/801,171, dated Oct. 3, 2018.
Office Action for U.S. Appl. No. 13/801,171, dated Apr. 6, 2017.
Notice of Allowance for U.S. Appl. No. 13/801,171, dated Oct. 31, 2018.
Final Office Action for U.S. Appl. No. 15/835,448, dated Nov. 2, 2018.
Final Office Action for U.S. Appl. No. 15/480,295, dated Nov. 7, 2018.
Final Office Action for U.S. Appl. No. 14/963,106, dated Dec. 14, 2018.
Final Office Action for U.S. Appl. No. 14/993,055, dated Dec. 14, 2018.
Office Action for U.S. Appl. No. 16/162,358, dated Dec. 31, 2018.
Office Action for U.S. Appl. No. 13/622,702, dated Oct. 3, 2018.
Office Action for U.S. Appl. No. 15/293,751, dated Apr. 6, 2017.
Office Action for U.S. Appl. No. 14/017,159, dated Jan. 11, 2019.
Office Action for U.S. Appl. No. 15/495,973, 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. 16/870,802, dated Sep. 22, 2021.
Decision on Appeal for U.S. Appl. No. 15/427,308, dated Sep. 10, 2021.
Related Publications (1)
Number Date Country
20220139152 A1 May 2022 US
Continuations (2)
Number Date Country
Parent 15427308 Feb 2017 US
Child 17511532 US
Parent 13801271 Mar 2013 US
Child 15427308 US