Patent Grant
11990005
Early gaming machines presented a single wagering game. For example, early slot machines presented a single game in which a set of reels were spun and the stopping positions of the reels define the outcome of the game. Later, video gaming machines were developed. These gaming machines were configured to present slot games in a video format, as well as other games such as video poker.
In order to increase the excitement associated with these games, various secondary game events have been developed. For example, gaming machines have been outfitted with rotating wheels. When a player receives a particular winning result of a base game, such as a particular slot reel outcome, the wheel may spin and stop on a segment which defines a bonus award. Similarly, video gaming machines have been configured to present various video secondary events. These events may comprise a variety of animated sequences which provide entertainment and the potential for awards.
Also, as gaming machines have been linked to gaming systems, awards have been developed which increase the number of participating players. For example, gaming machines may be linked to a jackpot system. If a player of one of the gaming machines of the system obtains a particular winning outcome, they may be awarded the jackpot. In order to increase the level of excitement of such a system, the players of other gaming machines at which the jackpot was not won may be awarded a consolation prize.
Still, these secondary events or awards have limitations, and new and exciting gaming events remain desirable.
Electronic gaming devices such as slot machines, videos poker machines, and keno machines account for almost 70% of the revenue generated by a casino. There are numerous gaming themes that are in casinos and in development. As these trends continue, players will be bombarded by a bewildering array of gaming choices. As casinos become larger and more crowed, locating desired games becomes more difficult and frustrating for individual players.
A primary objective of a casino is to entice players to play for longer time periods. A personalized gaming experience may compel players to extend gaming sessions. Making it easier for players to locate and access casino services will provide a more compelling and enjoyable casino experience. With the recent growth of technologies associated with wireless networks, software as a service, and personal electronic devices such as smart phones, mobile media devices, tablet computing devices, and the like, increasingly the portable electronic devices have become the main device for users to access information and services. Many of the information and services are based on the location of the users.
While software applications for handheld devices are beginning to surface for casino environments, these applications are mostly geared towards simple data access. Intelligent location-based and player-based data are non-existent as indoor-locationing technology is still in its infancy. Additionally, the locational precision that's required of an indoor-locationing system to pinpoint a device or a person, and the sheer number of wireless devices carried by people who are next each other in a confined space, cause the accuracy to plunge, while cost of the system to ascend. A simple and robust system, method, and apparatus to reliably deliver player-relevant data to mobile devices in the crowded, secured, highly regulated, casino environment is desired.
According to one aspect, some embodiments can be associated with distribution of viral events, such as viral gaming events, amongst devices. The devices can present the viral events. The devices can, for example, be gaming machines and/or mobile devices. In accordance with one aspect, a viral gaming event is triggered and is first presented at one or more first gaming machines at a time T1. The viral gaming event then spreads to one or more second gaming machines at a time T2 which is later than the time T1. The viral gaming event may comprise a gaming event such as a bonus event, or a non-gaming event such as a promotional message from the casino or an alert. The viral gaming event may be the same or different at each gaming machine. The viral gaming event may comprise a single player event (i.e. played by the player of the particular machine) or be a group event (wherein multiple players participate in the event).
According to another aspect, some embodiments concern a system, method, and apparatus capable of acquiring, transmitting, and presenting location based real-time casino data. In one embodiment, a portable electronic device, comprising a processor configured to receive real-time casino data associated with the location of the portable electronic device, an indoor location identifying device configured to indicate a location of the portable electronic device, a software application operative with the processor and configured to transmit a location of the portable electronic device and receive real-time casino data, an authentication device configured to verify and grant data access privileges to the at least one portable electronic device's software application, and a display configured to present the real-time casino data.
The present invention provides other hardware configured to perform the methods of the invention, as well as software stored in a machine-readable medium (e.g., a tangible storage medium) to control devices to perform these methods. These and other features will be presented in more detail in the following detailed description of the invention and the associated figures.
The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more example embodiments and, together with the description of example embodiments, serve to explain the principles and implementations.
In the drawings:
In general, one aspect disclosed herein concerns viral game events, methods of game play (“games”) including such events, and gaming machines and systems configured to present such events or features. A viral gaming event comprises a gaming event, such as a bonus or secondary event, which spreads from one or more first gaming machines to one or more additional gaming machines.
Content associated with a viral game event could be a game feature such as a bonus, a game symbol, a message from the server, a promotional message from the casino, an informational alert, and the like. The viral game event could be implemented as a software module. The software module monitors game events, gathers data, views files, processes logic, displays animation, etc., at the gaming devices. In one implementation, the viral game software is a self-contained distributed software application that's constructed with popular programming and languages such as C, C++, Java, C#, Perl, Javascript, Python, etc. The software module is transferred to a gaming device for execution. In another implementation, the viral game event is built as a web service to be executed at a remote server.
In one embodiment, the gaming machine 100 defines a generally enclosed interior space for housing one or more components. As illustrated, the gaming machine 100 generally comprises a housing or cabinet 102 for supporting and/or enclosing various components required for operation of the gaming machine. In the embodiment illustrated, the housing 102 includes a door located at a front thereof, the door capable of being moved between an open position which allows access to the interior, and a closed position in which access to the interior is generally prevented. The configuration of the gaming machine 100 may vary. In the embodiment illustrated, the gaming machine 100 has an “upright” configuration. However, the gaming machine 100 could have other configurations, shapes or dimensions (such as being of a “slant”-type, “bar-top” or other configuration as is well known to those of skill in the art).
The gaming machine 100 preferably includes at least one display device 104 configured to display game information. The display device 104 may be a mechanical, electro-mechanical or electronic display, such as one or more rotating reels, a video display or the like. When the display device 104 is an electronic video display, it may comprise a cathode ray tube (CRT), high resolution flat panel liquid crystal display (LCD), projection LCD, plasma display, field emission display, digital micro-mirror display (DMD), digital light processing display (DLP), multilayer LCD display, an E-ink display, a light emitting display (LED, OLED) or other suitable displays now known or later developed, in a variety of resolutions, sizes and formats (e.g. 4:3, widescreen or the like). The display 104 may be capable of projecting or displaying a wide variety of information, including images, symbols and other indicia or information associated with game play, game promotion or other events. The gaming machine 100 may include two or more display devices. For example, a secondary display device might be associated with the housing or cabinet 102 along with the main display device 104, or might be associated with a top box or the like, as illustrated in
The gaming machine 100 may be configured to present a wide variety of games. Such games might be Class III type games such as slot games and video poker games, or Class II type games such as bingo, pull-tab games, lotto or instant lottery style games. In one embodiment, certain game outcomes may be designated as winning outcomes. Prizes or awards may be provided for winning outcomes, such as monetary payments (or representations thereof, such as prize of credits), or the like. As detailed below, one or more of the awards may have certain characteristics or features.
The gaming machine 100 also preferably includes one or more player input devices 108 (such as input buttons, plunger mechanisms, a touch-screen display, joystick, touch-pad or the like) that may be utilized by the player to facilitate game play. Also included in the player input devices 108 is a means for accepting monetary value. As illustrated in
In one preferred embodiment, the gaming machine 100 includes a microprocessor or controller (not shown) for controlling the gaming machine, including receiving player input and sending output signals for controlling the various components of the machine 100 (such as generating game information for display by the display 104). The controller may be arranged to receive input such as a purchase/bet signal when a purchase/bet button is depressed, and a currency insert signal when a player inserts bills or coins. The controller may be arranged to send signals for determining winning combinations, for causing the coin hopper/dispenser, or printer, or an electronic fund transfer (EFT), to pay winnings, and to cause the display to display winning amount information. In addition, the controller is preferably arranged to determine if a round of game play has resulted in a win, and if so, the prize to be awarded to the player for that win.
The controller may be configured to execute machine readable code or “software” or otherwise process information, such as obtained from a remote server. Software or other instructions may be stored on a memory or data storage device. The memory may also store other information, such as pay table information. The gaming machine 100 may also include one or more random number generators for generating random numbers for generating random game outcomes, or such might be located remotely. For example, if the gaming machine 100 is a stand-alone machine configured to present a slot game or a video poker game, the random number generator(s) might be located at the machine. However, if the gaming machine 100 is used to present server-based or networked games, such as bingo games, the random number generator(s) might be located at the server.
In operation, the player may initiate game play by providing value, such as a wager. The wager may be made by activating one of the player input devices 108 such as a one credit button 116 which places a single credit purchase or wager or a max credit button 118 which places a maximum purchase or wager for that round of game play. The maximum purchase or wager is commonly defined as playing or betting an amount comprising a multiple of the value of a single purchase or wager up to a predefined upper purchase or bet limit or threshold. When the player actuates either the one credit button 116 or the max credit button 118, a wager is placed or purchase is made in that amount and the player's credit base is decreased by the number of credits wagered. The player's remaining credit base is typically displayed to the player by way of the display device 104. Upon making a purchase or placing a wager, the game may begin automatically or the player may join a game already in progress, or the player may initiate the game by activating another player input device, upon which the gaming machine 100 presents one or more game elements which are used to determine if the player has received a winning combination.
The gaming machine 100 generally includes a means for awarding a player a prize or winnings accumulated during game play. When a player obtains a winning outcome, the player is preferably paid prizes or awards in the form of stored credits, the amount of which is indicated to the player on the display 104. A “cash out” button may be provided for permitting a player to be paid the winnings or redeeming any credits initially paid into the gaming machine 100. The term “cash out” is used herein to define an event initiated by the player wherein the player receives a number of coins or currency that is equivalent to the value of the player's accrued credit base.
Typically, when a player cashes out, the gaming machine 100 is configured to dispense a media or voucher, such as via a printer 114, which represents the cash-out value. The player may utilize this voucher at other gaming machine or convert the voucher to currency, such as at a cashier's station. However, depending upon the configuration of the gaming machine 100, the player might receive a cash or coin disbursement. For example, the gaming machine 100 might be configured to activate a coin hopper or coin handling device (not shown) which physically counts and delivers the proper number of coins to the player. The coin handling device is commonly configured to transport coins from a supply source (hopper or bin filled with coins) to a coin tray 124 or payout receptacle where the player physically receives the coins.
As indicated above, the gaming machine 100 may be configured as a stand-alone device, such as when the machine is configured to present a slot game or a video poker game. As detailed below, however, the gaming machine 100 may be a server-based or networked machine. For example, the gaming machine 100 may be configured to obtain game code or game outcome information from a remote server 130. The gaming machine 100 may also communicate with a remote accounting server and/or player tracking server, as is well known in the art.
It will be appreciated that the gaming machine and system described and illustrated in
One aspect disclosed herein is a viral gaming event or feature. Such an event may be presented at a gaming machine or device 100 such as described above.
The viral gaming event of an embodiment has two primary components: a viral gaming event trigger and viral gaming event spread or transmission. The viral gaming event is initiated by a trigger. The trigger may be random and/or be a particular event. For example, the trigger may be generated randomly at a server or a gaming machine. Alternatively, the trigger might occur when a particular game result occurs. Such an outcome might be the appearance of a particular symbol or a group of symbols, one or more winning game outcomes, certain non-winning outcomes, or various other events at a gaming machine or groups of gaming machines. Other events might comprise a certain number of credits wagered or a certain number of games played at a gaming machine or across a gaming system, or a group of symbols or outcomes received at a bank, or a jackpot received at one or more gaming machines, or a predefined time, place, or machine designated by the casino manager, for example.
Upon the trigger, the viral gaming event is initiated at one or more first gaming machines. Initiation of the event at a gaming machine is akin to “infection” of the machine with the viral gaming event. In one embodiment in which the trigger is a particular event at a gaming machine, the viral gaming event is initiated at that gaming machine. However, the event might be initiated at more than one gaming machine, such as gaming machines spread across the floor of a casino, the gaming machines of a bank of gaming machines or the like. Another salient characteristic is that the viral gaming event can “hop” to other qualified games or machines even before the event is consummated at the “infected” game or machine. Like a biological flu, this viral propagation during the incubation period speeds up the propagation and create more excitement for the players because of the multiple potential payouts that overlap and sequentially occurring all around the players. Even when multiple games are being played simultaneously at one gaming machine, the concurrent games can be susceptible to “infection” if they meet the criteria.
The viral gaming event may be coupled with or comprise content related to any number of events. For example, the viral gaming event might comprise a game, a bonus event, a secondary game or the like. Other contents such as a notification of a 3rd-party sponsored prize, a bonus alert, a promotional message, an advertisement, a group message, music, video, and the like can also be coupled with a viral gaming event. The viral gaming event might be the same for each gaming machine regardless of the type or manufacturer of the gaming machine. For example, the viral gaming event might comprise a particular animated bonus event, regardless of whether the gaming machine is a spinning reel slot machine or video poker machine. In other embodiment, the viral gaming event might vary depending upon the gaming machine, the game being played, the player, time, and/or other parameters. For example, the viral gaming event might comprise a bonus opportunity for a 1000 credit payout. At a video poker machine the viral gaming event might be presented as a poker game having the opportunity for a 1000 credit payout if a particular win is achieved, while at a slot machine the viral gaming event might be presented as a spin of the reels with the opportunity for a 1000 credit payout if a particular symbol or combination of symbols is achieved. The configuration of a game on a gaming machine can also cause a variation of viral gaming event. For example, a viral gaming event may present an opportunity for a player of a gaming machine to win a $10,000 progressive jackpot (a traveling progressive) at a $5-denominated slot game, and may present a $1,000 jackpot at a $0.25 denominated game. Such a traveling progressive jackpot offers a player of the infected gaming machine a limited time (the infection period) to win a portion of its funds, scaled up or down proportionately with the amount that a player bets.
The viral gaming event might comprise a single player/machine event or it might comprise a group play type event. In a group play implementation, a community bonus event could cause multiple viral bonus events to be subsequently generated at nearby slot machines associated with the group game. For example, when a community bonus wheel is spinning in a group game, it could generate a viral bonus event that “infects” nearby associated gaming machines and cause them to have bonus spins at a later time. The viral gaming event continues to hop or spread to other qualified games until a termination event occurs. Also, the viral gaming event might result in an award, such as a bonus award, or it might have one or more outcomes that do not result in any additional award. The value of the awards that may be won at a particular machine may be based upon the size of player's wager, a side wager, a random event, or the like.
The viral gaming event may be presented via the main display of a gaming machine, via a secondary display or by one or more displays or devices common to one or more gaming machines. The viral gaming event might require one or more player inputs. The viral gaming event might be presented without a requirement for a further wager or might require a player to place a wager or an additional wager. In one embodiment, a player may be required to place a side wager in order to be eligible for the viral gaming event to spread to their machine.
In accordance with the embodiment, the viral gaming event preferably spreads from one or more first gaming machines to one or more other gaming machines over time. In particular, after the viral gaming event is initiated at the one or more first gaming machines at a first time T1, it spreads to and is initiated at one or more additional gaming machines at a time T2. The time delay between when the viral gaming event is initiated at the one or more first gaming machines and the one or more additional gaming machines may vary. For example, the time delay could be very short (seconds) or long (minutes, hours, etc.).
In addition, the viral gaming event may spread beyond one or more second gaming machines to other gaming machines. As one example, the total number of gaming machines “infected” over time may be bell curved (i.e. one or more gaming machines at time T1, increasing to a higher number of gaming machines at a time T2 and then decreasing to a fewer number of machines at a time T3). The number of gaming machines which are infected may also be random or have various other patterns, such as increasing linearly, geometrically, or exponentially over time until an end time.
It will also be appreciated that the rate of spread of the viral gaming event may vary. For example, the viral gaming event may spread from one or more first gaming machines at a time T1 to one or more second gaming machines in a time T2, and from the one or more second gaming machines to one or third gaming machines in a time T3, where the time intervals between T2/T1 and T3/T2 differ.
In one embodiment, the viral gaming event preferably ends or stops spreading at some point in time. When the viral gaming event ends, it preferably no longer spreads to additional gaming machines. The spread of the viral gaming event may end after a certain number of gaming machines have been infected, after a period of time from when the one or more first gaming machines were infected, until a pool of award money has been exhausted, or based upon various other criteria. In a preferred embodiment, the viral gaming event ends before all gaming machines in a particular location or environment are infected, whereby the viral gaming event is perceived as a special or bonus event as to those machines which receive it (compared to those which do not).
The viral gaming event may end at a particular machine once the event has been played or presented at that machine (though the event may still be spreading to other machines and/or games before the consummation of the viral gaming event at the current gaming machine/game). If the viral gaming event has a long duration, such as a group-type event, then the viral gaming event might end at each machine at a termination time. For example, once a viral gaming event is initiated at a gaming machine it may continue until the entire viral gaming event is terminated at all machines, as detailed below.
Once each gaming machine is infected, the viral gaming event is presented at that gaming machine. As indicated, the viral gaming event which is presented at each machine may be unique (i.e., tailored to a player or a game), or may be similar the event presented at other gaming machines.
In a preferred embodiment, the viral gaming event is implemented in a gaming system including multiple gaming machines. Preferably, the event is controlled by one or more system controllers. The system controller might comprise a server which is in communication with the gaming machines.
The system 200 preferably comprises a controller or server 222. The server 222 may comprise a computing device configured to execute machine readable code. In a preferred embodiment, the server 222 is in communication with the gaming machines 220 via one or more communication links 224. Such links 224 might comprise wired or wireless links, or combinations thereof.
In one embodiment, the server 222 may initiate a viral gaming event trigger. For example, the server 222 might monitor coin-in/credit wager data at the gaming machines 220. If a certain threshold is met, the server 222 may initiate the viral gaming event. Following the decision to instantiate the viral gaming event, the server 222 may determine a propagation pattern, one or more seed gaming machines, and the direction and rate of propagation. The server 222 might select one or more gaming machines 220 at which the event is to be initiated. The server 222 might receive feedback that the triggers that took place, and then spread the viral gaming event to other gaming machines 220.
In another embodiment, a viral gaming event might be triggered at a gaming machine or machines 220. The server 222 is then notified of the triggering event. The server 222 might then determine the propagation pattern, and spread the viral gaming event to other gaming machines 220. This is a hybrid implementation in which the triggering event is initiated by a game or gaming machine and then propagates by a server.
In one embodiment, the server 222 might utilize an existing communication network which links the gaming machines 220, such as a player tracking or accounting system. However, in environments where gaming machines are associated with different systems (such as those of different manufacturers), the server 222 might communicate with each of those different gaming machines via other communication links. Such links might be direct to the gaming machines or might be via the servers of the other systems. If the game or gaming machine supports a standard communication protocol, no protocol translation is needed. However, if the game or gaming machine does not support a standard protocol, a protocol mediator server may be needed to translate the communication commands to the language that the gaming machine supports.
It is also possible for the viral gaming event to be presented by gaming machines in a peer-to-peer environment. In this configuration, each gaming machine may be configured with a viral gaming event application. Each application may determine if a viral gaming event trigger has occurred. If so, that gaming machine may initiate the viral gaming event and then send a message directly to one or more other selected gaming machines to spread the viral gaming event. In a peer-to-peer communication approach, the triggering event takes place at a game and then propagates directly to other qualified games or gaming machines without the need for a central server. A manual approach in which a casino manager initiates the triggering event can take place whether the viral gaming event is constructed via a client-server or a peer-to-peer architecture.
A variety of additional aspects will now be described.
In one embodiment, spread of the viral gaming event may be random. In other configurations, it may be controlled, such as based upon various criteria. For example, the viral gaming event may be spread from one or more first gaming machines to other gaming machines that have or are experiencing a lower rate of game play. A player tracking or other system may be used to monitor game play at gaming machines across a system. Certain machines, such as in certain areas of a casino, may experience lower rates of play. This information may be provided to the viral gaming event server and the viral gaming event server may cause the viral gaming event to be initiated at or spread to those machines. The viral gaming event may thus be used as a tool to entice players to play gaming machines which are otherwise not being played.
Patterns of infection or rates of infection may also be varied by other factors. For example, the spread of a viral gaming event may be a different rate during the day versus night, or during periods of high gaming activity versus low activity.
In another embodiment, other sensors or devices may be used to provide information to the viral gaming event system for use in controlling the spread of the viral gaming event. For example, instead of using game play information from a player tracking system, the viral gaming system might obtain information from one or more cameras. These cameras may provide visual information regarding the gaming floor, such as information regarding patterns of patron movement, gaming machine occupancy and the like. This information may be analyzed and used by the viral gaming event server in determining the propagation of the viral gaming event. Such camera or other gathered information may also be used during the spread of the gaming event to determine if desired goals are being met (i.e. a feedback control) and, as detailed below, used to change various viral gaming event metrics during the event to achieve those goals.
The viral gaming server may utilize various control strategies. For example, the viral gaming server may employ a pre-programmed strategy in determining the viral gaming event. This strategy might comprise, for example, locating gaming machines which are inactive and spreading the viral gaming event to those machines. The control strategy might include a learning component. For example, the viral gaming event server may employ strategies and feedback in order to modify control strategies. Such strategies might be used and modified, for example, to achieve certain goals such as even player distribution across a gaming floor, maximized gaming machine occupancy or the like.
As one aspect of viral gaming event spread, different viral gaming events may be presented at different times and to different machines. As indicated above, different viral gaming events may be presented at different gaming machines. For example, viral gaming events offering differing levels of awards may be offered at different gaming machines, such as to manipulate play patterns. As one example, viral gaming events with low awards may be initiated at gaming machines that are active and viral gaming events with high awards may be initiated at gaming machines that are inactive (so as to attempt to draw new players to those inactive machines).
As indicated, the spread of the viral gaming event from machine to machine may be based upon various criteria or controls. As other examples, the viral gaming event might spread based upon a geometric progression (a randomly selected or predetermined geometric pattern). Such a pattern might comprise a propagation direction and rate of propagation. The viral gaming event might also spread to proximate gaming machines or the like. In another embodiment, the viral gaming event may spread to players in certain groups or meeting certain qualifications. For example, the viral gaming event may spread to all players having certain common metrics associated with the player tracking/profile information.
In one embodiment, the viral gaming event may only spread to gaming machines which are in active play or may spread based upon other criteria. For example, the viral gaming event might only spread to games where players have met certain qualifying requirements (such as duration of play, minimum player loyalty points, Gold Club members, etc.).
However, in other embodiments, the viral gaming event may spread to inactive gaming machines or may spread based upon other/external criteria than player qualification. As indicated, for example, the viral gaming event may be spread to gaming machines with a low level of game play. In the event a gaming machine is inactive, it is possible that the viral gaming event permits a player to achieve winnings without a wager. For example, a player might travel to a gaming machine which has been infected and the player may be permitted to play a bonus viral gaming event with the opportunity for winnings without any wager.
In one embodiment, when a gaming machine is infected with the viral gaming event (or the event is initiated at that gaming machine), notification may be provided to the player thereof and/or potential players via various messaging technologies. For example, various types of visible, audible or other alerts such as email, text messages to a player's mobile device (such as a phone or PDA) may be provided. Such alerts might comprise notification via the main display of the gaming machine, a secondary display, various lights or speakers. In one embodiment, the alert might comprise an audible notification that the gaming machine has been “infected”. Preferably, such alerts can be used by players or potential players to track or monitor to the spread of the viral gaming event.
In one embodiment, path lighting or other elements might be used to display the spread of the viral gaming event. Path lighting in a floor, ceiling or the like may define multiple paths between gaming machines of a casino. The particular paths of spread may be illuminated, thus providing players with a visual indication of how the viral gaming event is spreading. Other types of alerts or indicators may be provided, such as laser light, sound propagation, synchronized vibration of the chairs, vibrating the player's mobile device, text messaging to the player's mobile device, and the like.
In one embodiment, it is possible for there to be a time delay between when a gaming machine is infected with the viral gaming event and when it is presented at the gaming machine. This might be referred to as an incubation period. For example, the viral gaming event might spread to one or more second gaming machines. An alert may be provided to the players thereof that the gaming machines have been infected. However, the viral gaming event itself might be presented immediately or after some period of time. In this manner, a player knows that the machine is infected and the viral gaming event will be presented, but does not know when. This entices the player to continue to play the gaming machine in anticipation of the viral gaming event being presented. During the incubation period, the viral gaming event may continue to propagate and infect other games. Thus, the viral gaming event may overlap at two or more games/gaming machines (as compared to an embodiment wherein the virus spreads sequentially and an event at one or more games/gaming machines must end before another event starts at other games/gaming machines).
As one aspect of an embodiment, viral gaming event data may be gathered and analyzed. Information may be gathered regarding the results of viral gaming events at each individual machine, the number of viral gaming events initiated vs. those which were played (i.e. were inactive machines played when the event was initiated at the machine), etc. This information may be used to determine how future viral gaming events are initiated or spread, the awards to be offered and the like.
It will be appreciated that the various features disclosed herein may be utilized in various combinations. For example, the viral gaming event may be configured to spread at differing rates over time, coupled with feedback control which causes the viral gaming event to spread to particular gaming machines based upon rate of game play. Further, multiple viral gaming events can occur on a casino floor, allowing such hybrid events as a game being infected with more than one viral gaming event at one time. This allows the player to be eligible for multiple bonuses, for instance.
In accordance with the aspect, numerous advantages are realized. The aspect substantially increases the excitement of playing games, including wagering games. In particular, players know that a bonus or other gaming event which is additional to their base gaming event may be triggered and presented at any time. More importantly, even if such an event is not initiated at their gaming machine, if that event is initiated at another gaming machine it may still spread to their gaming machine. Once a gaming machine is infected, players can anticipate infection of other machines. Thus, substantial anticipation is created while the viral gaming event spreads through the various gaming machines.
An additional advantage of the viral gaming event is that it may be used to increase gaming play. Aside from the inherent excitement that the event presents, the viral gaming event may be particularly spread to gaming machines having low gaming activity. This spread may entice players to follow the spread of the viral gaming event to those machines. As players move to those machines, game play is increased on those gaming machines.
Another aspect disclosed herein concerns other embodiments in the context of a location-based real-time casino data system. 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 aspect, 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.
In another embodiment, the at least one gaming device 402 can be configured to detect the location of each portable electronic device 404a, 404n, 406a, and 406n, and transmit the real-time casino data to the at least one portable electronic device 404a, 404n, 406a, and 406n based on the location, access privilege, preset personal preference, spontaneous preference, etc., of the at least one portable electronic device 404a, 404n, 406a, and 406n. The at least one gaming device 402 can be configured to periodically receive and update the location of the at least one portable electronic device 404a, 404n, 406a, and 406n.
For example, the location acquisition unit may acquire the location of the portable electronic device by using radio frequency (RF) wireless location tracking between the portable electronic device and at least one wireless access point distributed throughout the gaming establishment environment. In another example, an RF transceiver within the portable electronic device may be located by its position relative to the closest access point. In yet another example, triangulation or trilateration methods may be used in conjunction with multiple stationary access points to determine the location of the portable electronic device. RF fingerprinting location appliances, such as the Cisco Wireless Location Appliance™ manufactured by Cisco Systems, Inc. (San Jose, California, US), may be used to determine the location of the portable electronic device. RF fingerprinting may further refine the location data associated with the portable electronic device by comparing the live-captured RF characteristic of the current location of the portable electronic device to a known or predicted RF characteristic of a point or zone within the gaming establishment environment. In another example, location data may be determined visually by a plurality of smart cameras distributed throughout the gaming establishment environment. The smart cameras may recognize the portable electronic device by, for example, reading a 2D barcode displayed on the portable electronic device's display, and tracks its location and movement within the gaming establishment environment based on known location data of barcode reader, or nearby fixed objects. Using the portable electronic device to scan for nearby RF beacons and simply decodes their location is yet another method used when exact location is unnecessary.
The portable electronic device 500 can further comprise an authentication device configured to verify and authorize data access privileges of the portable electronic device 500's software application. In one embodiment, the authentication device can be a casino data access server configured to authenticate the software as well as verify and authorize access privileges of a software application. The portable electronic device 500 can transmit the user identifier code and the software application's digital signature information to a server for authentication and verification. When the portable electronic device transmits encrypted device identifier, user identifier, software digital signature, and other information to the server, the server is configured to decrypt the message and identifier information. The server then checks for correct values of the user identifier code, the software application's authenticity, and/or the device's identifier information.
The portable electronic device 500 further includes a processor 502 configured to receive real-time casino data associated with the location of the portable electronic device 500. The portable electronic device may further include a display 506 configured to present the real-time casino data. In one embodiment, the real-time casino data includes at least one gaming device data associated with the location of the portable electronic device 500. The gaming device maybe a slot machine, a table game, for example, blackjack, poker, craps, and the like, a mobile device, a smart phone, a computer, a tablet computer, and/or an interactive TV (iTV).
The portable electronic device 500 can also include at least one input device 510 configured to allow navigation of the real-time casino data. The input device 510 can include, but is not limited to, a plurality of buttons, a keyboard, a touch screen display, voice, gesture, and the like. The portable electronic device 500 can also include a data transceiver interface 508 configured to transmit data, including but not limited to, real-time casino data, authentication or verification data or both, and the like.
In one embodiment, the processor 502 can be configured to operate with the casino data application to receive real-time casino data associated with the location, access privileges, preferences, and/or spontaneous preferences of the portable electronic device 500. The casino data application may further organize and/or prioritize the real-time casino data according to the preferences of the player, of the casino, of a third-party sponsor of the application data, of the location of portable electronic device, or some combination of these. In another embodiment, the processor 502 can be configured to interact with a casino data center to receive real-time casino data associated with the location, access privileges, preset preferences, and/or spontaneous preference of the portable electronic device 500. The casino data application may further organize and/or prioritize the real-time casino data according to the preferences of the player, of the casino, of a third-party sponsor of the application data, of the location of portable electronic device, or some combination of these.
The casino data center can be configured to receive and store the gaming machine information transmitted from all gaming machines in the casino. The casino data center can also be configured to store data associated with the connection, history, operating states of hardware and software, and the session data with the portable electronic devices. Such a back-up storage capability helps in restoring an interrupted communication session between the casino data center and the portable electronic devices due to unforeseen events such as loss of battery power, loss of signals, corrupted memory, inadvertent delete, etc., on the portable electronic devices. In such a recovery process, the entire session is restored to the last known state (display, memory stack, communication, operating system, applications, data, history, input, output, etc.) on the portable electronic device using backup data from the casino data center. A new location data acquisition is performed. An opportunity to update the data, based on current location, is then offered to the user. Thus, the user is afforded an option to continue the previous session, or to start anew.
In yet another embodiment, the processor 502 can be configured to present a visual representation of a particular gaming zone on the display 506. A zone maybe a physical area or volume of the casino where one or more gaming devices or points of interest that share some common characteristics exist for at least a time period. For example, penny slots zone, high-limit gaming zone, poker zone, mystery bonus zone, and the like. In another illustrative example, the entire second floor of a casino can be a mystery bonus zone on Tuesdays. A zone may also be a virtual area/space where physically separated gaming devices maybe logically grouped for a common function or purpose, such as a slot tournament, group games, bonusing, progressives, and the like. Whether a zone is a physical location with gaming devices, or a logical group of gaming devices, a zone may have its own server dedicated to serving that zone and the gaming devices connected to it. The advantage of zone-based architecture is that the location services can be deployed in a piecemeal manner and scale up one zone at a time. Such a distributed architecture could be more desirable than a monolithic architecture of a property-wide location-based service. Another advantage is that the precise location of a device is not required once a portable electronic device is determined to be within a zone. As long as the portable electronic device is somewhere inside the zone, zone-based service and data can be provided. Precise location is no longer required, lowering the cost of a location tracking system.
In one embodiment, the visual representation includes at least one indicator configured to identify at least one gaming machine based on at least one criterion, such as an access privilege. The indicator may be any visual representation such as an icon, a picture, a border around an object of interest, a descriptive text string, a visual pattern unique to the gaming machine or particular gaming zone, and the like. In one embodiment, the indicator is a semi-transparent object overlaying a region of interest in a background image. For example, a computer-generated semi-transparent mask overlaying a small area of the casino floor, highlighting a slot machine that is currently unoccupied and available players. The visual representation can be a line map, or a video camera image of a casino floor, or a hybrid representation where the line map overlays a still or a video camera image, identifying at least one gaming machine. In another embodiment, Augmented Reality technology, where one or more computer generated indicators are superimposed over a live video camera image, could be implemented. In this case, the player points the portable electronic device (equipped with a camera) in the general direction of interest. The video stream is analyzed, recognized, annotated and displayed, live, on the portable electronic device. As the player moves around the casino floor, annotations of gaming machines or other points of interest are dynamically updated.
The method further includes verifying the capabilities, authenticating and granting data access privileges to the portable electronic device's software application at 606, receiving real-time casino data based on the location and capabilities of the portable electronic device at 608, and presenting the real-time casino data on a display of the at least one portable electronic device at 610. Capabilities of the portable electronic device include screen display size, screen resolution, computing capability, memory available, operating system type, software installed, and the like.
In one embodiment, the method further comprises periodically updating the location of the portable electronic device, transmitting an updated location of the portable electronic device to the gaming device; and receiving updated real-time casino data based on the updated location, preset preferences, spontaneous preferences, and access privileges of the portable electronic device.
In another embodiment, the presenting at 610 further comprises identifying at least one gaming machine that is generating revenue over a predetermined period of time. In yet another embodiment, the presenting further comprises displaying a visual representation of the predefined zone within the casino floor. Prior to presenting the real-time casino data on the display of the portable electronic device, the data may be organized and/or prioritized according to the preference of the user, of the casino, of a third-party sponsor of the application data, of the location of the portable electronic device, or some combination of these. In still another embodiment, the visual representation includes at least one indicator configured to identify at least one gaming machine based on at least one criterion. The visual representation can be a line map, or a video image of the casino floor, or a hybrid representation where the line map overlays a still or video camera image, identifying at least one gaming machine based on at least one criterion.
The real-time casino data may include gaming machine data. In one embodiment the gaming machine data includes pay-in data acquired over a predetermined period of time, pay-out data acquired over a predetermined period of time, game session duration data, or player entertainment preferences and play history. In another embodiment, the real-time casino data can be associated with the predefined zone of the casino floor. Real-time casino data acquisition maybe periodically updated and/or prioritized when a triggering event occurs, such as when the user moved to a different zone, at a predetermined time interval, when the user manually requests a data refresh, and the like. Using the acquired data, a casino manager may evaluate a player's value to the casino, and may award spontaneous perks such as cash back, bonus spins, food/drink vouchers, etc.
The location of the at least one portable electronic device at 660 may be periodically updated as described above. After the updated location of the portable electronic device is calculated, the updated location of the at least one portable electronic device may be transmitted to a gaming device at 652 and the remaining steps of the method 650 may repeat thereafter. If there is no updated location of the portable electronic device at 660, then detect whether there are any updated interest criteria at 662. If there is updated interest criteria, the updated interest criteria may be transmitted to the gaming device at 654 and the remaining steps of the method 650 may be repeated thereafter.
From the player's perspective, interest criteria may include gaming machine data such as the time period since the most recent pay-out, gaming machines within a user-preferred predefined zone of the casino floor, gaming machines that share a particular theme, gaming machines that have linked progressives jackpots, a predefined zone of the casino floor having a particular denomination, and the like. From the casino operator's perspective, interest criteria may include players who have spent $50 or more in the last hour, winning players, losing players, gaming machines that generated the least revenue in the past month, top 10 games that received the most plays this week, players who have been at one machine for at least one hour, zones that are most active right now, and the like.
The location of the portable electronic device may be transmitted to a gaming device within the gaming establishment environment. The gaming device may be a central gaming server, a slot machine, a table game, a portable computer, a smartphone, a tablet computer, an interactive television, and the like. The gaming device that receives the location of the portable electronic device may then authenticate the portable electronic device as a member of the gaming establishment environment network and grant the portable electronic device access privileges sufficient to receive real-time casino data.
After acquiring the location information, a verification of the device capabilities, authentication of the device's software and authentication of the device's access privileges are performed at 703. Real-time casino data and access privileges associated with the location of the portable electronic device may be determined at 704 by the gaming device, transcoded to conform to the portable electronic device's inherent capabilities (display size and resolution, processing and storage capacity, etc.), and transmitted to the portable electronic device from the gaming device at 706. Prior to transmitting, the real-time casino data may further be organized and/or prioritized according to the preference of the user, of the casino, of a third-party sponsor of the application data, of the location of the portable electronic device, or some combination of these. The preference maybe preset or spontaneous. The real-time casino data associated with the location of the portable electronic device may include gaming machine data such as player gaming preferences, player entertainment preferences, gaming machine pay-in data acquired over a predetermined period of time, gaming machine pay-out data acquired over a predetermined period of time, and game session duration data. The gaming machine pay-in and pay-out data acquired over a predetermined period of time may be obtained from a central gaming server or recorded over a predefined period of time from a particular gaming machine of interest to a player.
The real-time casino data may be presented on a display of the portable electronic device. The real-time casino data may be displayed using text, graphical symbols, or augmented reality techniques. The displayed text, graphical symbols, or augmented reality techniques may indicate the location of a gaming machine that has characteristics which an individual player may find desirable. For example, the displayed real-time casino data may indicate the location of gaming machines that have recently paid out a jackpot, gaming machines that have not recently paid out, zones with most payout in the last hour, zones that offer mystery bonuses, and/or the location of particular themed gaming machines the player prefers such as Wheel of Fortune™. The real-time casino data presented on the display of the portable electronic device may also indicate a location of amenities and attractions within the gaming establishment environment, such as restrooms, concierge services, restaurants, shows, and the like.
The real-time casino data may be presented such that at least one gaming machine generating revenue over a predefined period of time may be identified. The gaming machine revenue generation data may also identify at least one gaming machine that has not generated revenue over the predefined period of time.
The augmented reality techniques that present the real-time casino data on the display of the portable electronic device may comprise overlaying a map of the gaming establishment environment, annotations and other indicators, onto real-time video captured and displayed by the portable electronic device. The overlaid map, annotations, and other indicators generated from the real-time casino data may indicate gaming machines that have desired characteristics, suggested rewards to casino managers for high value players, amenities within the gaming establishment environment and/or players that have generated a predefined amount of revenue for the casino, and the like. The overlaid map may be referred to as an augmented reality map, and the augmented reality map may be periodically updated when the portable electronic device acquires new real-time casino data and/or when the location, or other triggering events, of the portable electronic device changes as described below.
The real-time casino data associated with the portable electronic device may be periodically updated at 708. Several events may trigger updates of the real-time casino data associated with the portable electronic device. For example, the real-time casino data associated with the portable electronic device may update after a predefined period of time has elapsed, or upon a manual request by the user, or upon a change in the location of the portable electronic device, or when a new data set is available such as new bonus offers by the bonusing controller at the current location. After the location of the portable electronic device changes, the method for acquiring the location of the portable electronic device may be repeated.
The location of the portable electronic device may be associated at 754 with a predefined zone within the gaming establishment environment casino floor. The casino floor may be divided into at least one predefined zone. Certain features of the casino floor may be grouped together within the predefined zones. For example, one zone may contain at least one slot machine and another zone may contain at least one table game. In another example, a predefined zone may contain casino amenities such as at least one restaurant, concierge kiosk, theatre, and the like. As previously discussed, a zone can be physical, virtual (logically grouped), or some combinations of both. Further, each zone can have a dedicated server catering to the gaming devices within the zone, making it easy to implement a location-based function one area at a time on the casino floor.
A gaming machine may determine at 756 real-time casino data associated with the predefined zone on the casino floor that may contain the portable electronic device. The gaming machine may then transmit at 758 the real-time casino data associated with the predefined zone on the casino floor to the portable electronic device. Prior to transmitting, the real-time casino data may further be organized and/or prioritized according to the preference of the user, of the casino, of a third-party sponsor of the application data, of the location of the portable electronic device, or some combination of these. The preference maybe preset or spontaneous. The real-time casino data associated with the predefined zone on the casino floor may include gaming machine data such as player gaming preferences, player entertainment preferences, gaming machine pay-in data acquired over a predetermined period of time, gaming machine pay-out data acquired over a predetermined period of time, and game session duration data. The gaming machine data may be organized by each machine's location on the casino floor, or logically grouped. The gaming machine pay-in and pay-out data acquired over a predetermined period of time may be obtained from a central gaming server or recorded over a predefined period of time from a particular gaming machine or predefined zone on the casino floor of interest to a player. Real-time casino data acquisition maybe periodically updated when a triggering event occurs, such as when the user moved to a different zone, at a predetermined time interval, when the user manually requests a data refresh, and the like. Using the acquired data, a casino manager may evaluate a player's value to the casino, and may award spontaneous perks such as cash back, bonus spins, food/drink vouchers, etc.
The real-time casino data associated with the predefined zone on the casino floor may be presented on a display of the portable electronic device. The real-time casino data associated with the predefined zone on the casino floor may be displayed using text, graphical symbols, or augmented reality techniques such as an augmented reality map where annotations and other indicators are superimposed on a live video stream. The displayed text, graphical symbols, or augmented reality techniques may indicate the location of gaming machines within a predefined zone on the casino floor that have characteristics, which an individual player may find desirable. For example, the displayed real-time casino data may indicate the location of gaming machines within the predefined zone that have recently paid out a jackpot, gaming machines that have not recently paid out, hot players, bonus zones, and/or the location of particular themed gaming machines within the predefined zone the player prefers. The real-time casino data associated with the predefined zone on the casino floor presented on the display of the portable electronic device may also indicate the location of amenities and attractions within the gaming establishment environment, such as restrooms, concierge services, restaurants, shows, and the like.
The real-time casino data may be presented such that at least one gaming machine associated with the predefined zone on the casino floor generating revenue over the predefined period of time may be identified. The gaming machine revenue data may also identify at least one gaming machine within the predefined zone that has not generated revenue over the predefined period of time.
The augmented reality techniques used to present the real-time casino data on the display of the portable electronic device may comprise overlaying a map of the predefined zone, computer generated annotations and other indicators, within the gaming establishment environment onto real-time video captured and displayed by the portable electronic device. The overlaid map and notes may indicate gaming machines within the predefined zone that have desired characteristics, amenities within the gaming establishment environment and/or players within the predefined zone that have generated a predefined amount of revenue for the casino. The overlaid map may be referred to as an augmented reality map, and the augmented reality map may be periodically updated when the portable electronic device acquires new real-time casino data and/or when the location of the portable electronic device changes as described above.
The real-time casino data associated with the predefined zone on the casino floor containing the portable electronic device may be periodically updated and/or reprioritized at 760. For example, the real-time casino data associated with the portable electronic device may update after the predefined period of time has elapsed, upon a change in the location of the portable electronic device, or when a new offer/event has been initiated. The update may initiate when the portable electronic device moves from one predefined zone on the casino floor to another predefined zone on the casino floor. After the location of the portable electronic device changes, the method for acquiring the location of the portable electronic device may be repeated.
The real-time casino data associated with the at least one predefined zone on the casino floor may be visually represented as a map of the casino floor within the gaming establishment environment. The map may display an icon 854 denoting the current location of the portable electronic device that may be carried by the user. The map may also display icons representing at least one predefined zone on the casino floor. For example, the map may display a predefined zone 848 that contains mainly table games. In another example, the map may display a predefined zone 850 that contains mainly slot machines with mystery bonus feature. In yet another example, the map may display a predefined zone 852 that contains mainly casino amenities such as a bar or restaurant. In still yet another example, the relative locations of the predefined zones 848, 850, and 852 may be displayed relative to the icon 854 denoting the current location of the portable electronic device. The relative locations of the predefined zones 848, 850, and 852 may be denoted by unique graphical representations on the map such as color highlights, annotations, contours, and other textual or graphical indicators. For example, zone 848 may be denoted by an open rectangle drawn with dotted lines while zone 850 may be denoted by a cross-hatched rectangle drawn with dotted lines. Zone 852 may be similarly denoted by a hatched rectangle drawn with dotted lines. The respective shadings of the rectangles representing zones 848, 850, and 852 may allow the user to quickly and easily identify zones of interest on the casino floor.
The real-time casino data associated with the at least one predefined zone on the casino floor may be visually represented as the gaming color heat map of the casino floor within the gaming establishment environment. The gaming color heat map may be defined as a visual representation of real-time casino data that can be translated to activities associated with predefined zones on the casino floor wherein desired features of the gaming establishment environment are prioritized and depicted visually according to their priority. For example, a player may desire to locate gaming machines within proximal predefined zones on the casino floor that have not paid out within a predefined period of time. The real-time casino data displayed on the portable electronic device may display the gaming color heat map of the casino floor with an icon representing the player 868 centered on the gaming heat map. The gaming color heat map may also display the at least one predefined zone 878 and 880 on the casino floor that contain gaming machines that have not paid out within the predefined period of time. The real-time casino data representing at least one gaming machine that has not paid out within the predefined period of time may be ranked by longest time since the last pay-out and displayed as color gradients or contours according to the ranking where the longest amount of time has elapsed since gaming machine 870 paid out, less time has elapsed since gaming machine 872 has paid out, and still less time has elapsed since gaming machines 874 paid out.
The gaming color heat map may depict at least one zone 878 and 880, and may also depict different game genres and other features such as bonus and progressives on one map. In another example, slot machines in zones 878 and 880 may be directly compared with a group game 884. In this example, an approximately equivalent amount of time has elapsed since slot machines 874 and group game 876 has paid out. The gaming heat map may also depict other predefined zones on the casino floor such as zones 882 and 886 devoted to table gaming machines.
The portable electronic device 902 may have a display 912 that can present the gaming heat map 914. The display 912 can be a liquid crystal display screen, organic light-emitting diode screen or any other type of display device found in portable electronic devices. The display 912 can have touch screen capabilities that may allow a user to manipulate the gaming heat map 914. The portable electronic device 902 may also have physical buttons or keys that can also allow the user to manipulate the gaming heat map 914.
The gaming color heat map 914 can include a casino map 916. The casino map 916 may be a scaled line drawing, photograph, live video or any other type of map. The casino map 916 may have labels and other annotations for gaming machines, game features, gaming tables, restaurants, bars, amenities, and other structures that appear within the casino map 916. In one embodiment, the casino map 916 may display a portion of the casino floor within a predefined radius around a location of the portable electronic device 902. The predefined radius may be user or casino defined. In another embodiment, the casino map 916 may display a predefined zone that the location of the portable electronic device 902 is within. The casino map 916 may refresh and display a different portion of the casino floor based upon an updated location of the portable electronic device 902 or when a new offer/event has been initiated.
The gaming heat map 914 can have an indicator 906 for the location of the portable electronic device. The indicator 906 for the location of the portable electronic device may be an icon, shape, symbol, picture, numeral, character, text or the like. The indicator 906 for the location of the portable electronic device may include location data such as coordinates and orientation. In one embodiment, the location data may be represented by the indicator 906 for the location of the portable electronic device. For example, the indicator 906 for the location of the portable electronic device can be an arrowhead, where a position of the arrowhead represents coordinates and a direction the arrowhead points represents orientation. In another embodiment, the location data can be represented by additional text adjoining the indicator 906.
The gaming color heat map 914 may have a search mechanism 904 that accepts input of at least one criterion. The search mechanism 904 can be a text input box, drop down menu, or any other mechanism that accepts user input. The user can input the at least one criterion into the search mechanism 904 via the display 912 with touch screen capabilities, the physical buttons or keys, or any other input device on the portable electronic device 902. The at least one criterion can be slot machine type, wager amount, game type, game theme, mystery bonus zone, game promotional zone, upcoming promotional zone, gaming machine data, player entertainment preferences or any other user criteria. The gaming machine data may include game session duration data, periodic pay-in data, and periodic pay-out data. The periodic pay-out data may include length of time since the last pay-out, frequency of pay-outs, amount of pay-outs, and the like.
The gaming heat map 914 may identify at least one slot machine based on the at least one criterion. The identified at least one slot machine can be represented on the gaming heat map 914 by an icon, shape, symbol, picture, numeral, character, text or other such indicia. In one embodiment, the identified at least one slot machine may be represented by a concentric ring symbol or contour lines. A slot machine represented by a concentric ring symbol with three rings 910 or tight contour lines may be a closer match to the at least one criterion then a slot machine represented by a concentric ring symbol with two rings 908 or sparse contour lines. Although the degree of correlation between a particular identified slot machine and the at least one criterion is illustrated here by the number of concentric rings, this is not intended to be limiting. The degree of correlation may be represented not only by the number of indicia but also indicia size, indicia type, color, letter grade, percentage, and the like.
The portable electronic device 952 may have a display 954 that can present the entertainment query 974. The display 954 can be a liquid crystal display screen, organic light-emitting diode screen or any other type of display device found in portable electronic devices. The display 954 can have touch screen capabilities that may allow a user to manipulate the entertainment query 974. The portable electronic device 952 may also have physical buttons or keys that can also allow the user to manipulate the entertainment query 974.
The entertainment query 974 may have a search mechanism 958 that accepts input of at least one criterion. The search mechanism 958 can have a single or multiple text input boxes, drop down menus, or the like. In one example, where the entertainment query 974 is for restaurants, the search mechanism 958 may contain a genre text input box 970, a max distance text input box 956, and a price range text input box 972. The genre text input box 970 can accept user food genre preferences such as pizza, Italian, vegetarian burrito, Asian cuisine, and any other food preferences the user may have. The max distance text input box 956 may accept a maximum distance for a restaurant location from a current location of the portable electronic device 952. The price range text input box 972 can accept user price range preferences. The at least one criterion may also include restaurant ratings. The user can input the at least one criterion into the search mechanism 958 via the display 954 with touch screen capabilities, the physical buttons or keys, or any other input device on the portable electronic device 952.
The entertainment query 974 may have a search results dialogue 960. The search results dialogue 960 may contain a plurality of search result items 962. Each search result item may include a name for a particular search result item and a distance from the particular search result item to the current location of the portable electronic device 952. The plurality of search result items 962 may be arranged in a list based upon degree of correlation to the at least one criterion, distance, price, alphabetical order, or any other sorting or ordering method.
The entertainment query 974 may have a map it function 964. The map it function 964 may present a casino map on the display 954. The casino map may be a scaled line drawing, photograph, or any other type of map. The casino map may have labels for gaming machines, gaming tables, restaurants, bars, amenities, and other structures that appear within the casino map. The casino map may indicate the current location of the portable electronic device 952 and the location of a selected search result item. The map it function 964 may also present navigation directions from the current location of the portable electronic device 952 to a location of the selected search result item on the display 954.
The entertainment query 974 may have a more info function 966. The more info function 966 may present additional information associated with the selected search result item on the display 954. The additional information may include menus, price range, recommended dishes, specials, sales, pictures, show programs, theater maps, casino promotions, and the like. The entertainment query 974 may have an edit query function 968. The edit query function 968 may facilitate editing of the at least one criterion. Editing may be performed via the display 954 with touch screen capabilities, the physical buttons or keys, or any other input device on the portable electronic device 952.
The portable electronic device 1002 may have a display 1004 that can present the player compensation visual representation 1016. The display 1004 can be a liquid crystal display screen, organic light-emitting diode screen or any other type of display device found in portable electronic devices. The display 1004 can have touch screen capabilities that may allow a user to manipulate the compensation visual representation 1016. The portable electronic device 1002 may also have physical buttons or keys that can also allow the user to manipulate the compensation visual representation 1016.
The player compensation visual representation 1016 can have an indicator 1010 denoting a location of the portable electronic device. The indicator 1010 denoting the location of the portable electronic device may be an icon, shape, symbol, picture, numeral, character, text or the like. The indicator 1010 denoting the location of the portable electronic device may include location data such as coordinates and orientation. In one embodiment, the location data may be represented by the indicator 1010 denoting the location of the portable electronic device. For example, the indicator 1010 denoting the location of the portable electronic device can be an arrowhead, where a position of the arrowhead represents coordinates and a direction the arrowhead points represents orientation. In another embodiment, the location data can be represented by additional text adjoining the indicator 1010.
The player compensation visual representation 1016 can include a casino map 1018. The casino map 1018 may be a scaled line drawing, photograph, still image, live video, or any other type of map. The casino map 916 may have labels for gaming machines, gaming tables, restaurants, bars, amenities, and other structures that appear within the casino map 1018. In one embodiment, the casino map 1018 may display a portion of the casino floor within a predefined radius around a location of the portable electronic device 1002. The predefined radius may be user or casino defined. In another embodiment, the casino map 1018 may display a predefined zone that the location of the portable electronic device 1002 is within. The casino map 1018 may refresh and display a different portion of the casino floor based upon an updated location of the portable electronic device 1002 or when a new offer/event has been initiated.
The player compensation visual representation 1016 may have an indicator 1008 for slot machines currently being played. Although the indicator 1008 may be illustrated by a blacked out square, this illustration is not intended to be limiting as the indicator can be an icon, shape, symbol, picture, numeral, character, text or the like. The indicator 1008 for slot machines currently being played may also comprise additional text 1006. The additional text 1006 may include slot machine coordinates, slot machine revenue, suggested comps for a player based upon slot machine revenue, and other information relevant to player comps. The indicator 1008 may also comprise a more info button 1014. The more info button 1014 may present information such as preferred slot machine type, preferred game features, wager amount, game type, game theme, player entertainment preferences, game session duration data, pay-in data, length of time since the last pay-out, frequency of pay-outs, amount of pay-outs, and the like on the display 1004.
The compensation visual representation 1016 may have a status notification dialogue 1012. The status notification dialogue 1012 can display coordinates for the location of the portable electronic device, the number of slot machines currently being played, how many comps should be granted, and other information important to a casino host.
The portable electronic device 1052 may have a display 1072 that can present the revenue heat map 1070. The display 1072 can be a liquid crystal display screen, organic light-emitting diode screen or any other type of display device found in portable electronic devices. The display 1072 can have touch screen capabilities that may allow a user to manipulate the revenue heat map 1070. The display 1072 may have a touch screen View button 1062 that may change views for the revenue heat map 1070.
In one embodiment, changing views may entail switching revenue heat map types from line drawing maps to image maps. In another embodiment, changing views may entail switching to a first person perspective of the casino floor with information overlaid upon the visual representation. For example, the first person perspective of the casino floor may be represented by an augmented reality map. In yet another embodiment changing views may entail altering the scope of the presented casino floor.
The display 1072 may have a touch screen Bookmark Slot Machine button 1064 that may bookmark a slot machine of interest and its location to a casino host and players alike. In one embodiment, bookmarking will allow the casino host to recall a location of the slot machine of interest. In another embodiment, the casino host can bookmark a player of interest, such as a high value player who should be pampered, by associating the portable electronic device ID with the player status and value. The display 1072 may have a touch screen “More Information” button 1066 that displays additional information 1054 for a particular slot machine (or a player). The additional information 1054 may include location, amount of revenue, and duration of gaming session. The portable electronic device 1052 may have physical buttons 1068 or keys that can also allow the user to manipulate the revenue heat map 1070. The physical buttons 1068 can be a keyboard, number pad, arrow keys, and the like.
The revenue heat map 1070 can include a casino map 1074. The casino map 1074 may be a scaled line drawing, photograph, or any other type of map. The casino map 1074 may have labels for gaming machines, gaming tables, restaurants, bars, amenities, and other structures that appear within the casino map 1074. In one embodiment, the casino map 1074 may display a portion of the casino floor within a predefined radius around a location of the portable electronic device 1052. The predefined radius may be defined by the casino host or the casino. In another embodiment, the casino map 1074 may display a predefined zone that the location of the portable electronic device 1052 is within. The casino map 1074 may refresh and display a different portion of the casino floor based upon an updated location of the portable electronic device 1052.
The revenue heat map 1070 can have an indicator 1076 denoting the location of the portable electronic device 1052. The indicator 1076 denoting the location of the portable electronic device 1052 may be an icon, shape, symbol, picture, numeral, character, text or the like. The indicator 1076 denoting the location of the portable electronic device 1052 may include location data such as coordinates and orientation. Although the indicator 1076 denoting the location of the portable electronic device 1052 is illustrated at the center of the casino map 1074, this illustration is not intended to be limiting as the indicator 1076 may be anywhere within the casino map 1074.
The revenue heat map 1070 may identify at least one slot machine or player of interest to the casino host. The interest of the casino host may depend upon slot machine revenue, gaming session duration, player's data, and/or any other criteria of interest to the casino host. The identified at least one slot machine can be represented on the revenue heat map 1070 by an icon, shape, symbol, picture, numeral, character, text or other such indicia.
In one embodiment, the identified at least one slot machine may be represented by a concentric ring symbol or contour lines. A slot machine represented by a two concentric ring symbol 1058 may have generated little revenue over a long gaming session duration. A slot machine represented by a four concentric ring symbol 1060 may have generated a large amount of revenue during a short gaming session duration. A slot machine represented by a three concentric ring symbol 1056 may have generated a moderate amount of revenue, where the moderate amount of revenue is less than the slot machine represented by a four concentric ring 1060 symbol and more than the slot machine represented by a two concentric ring symbol 1058. Although the interest level of a particular identified slot machine to the casino host is illustrated here by the number of concentric rings, this illustration is not intended to be limiting. The degree of correlation may be represented not only by the number of indicia but also indicia size, indicia type, density of contour lines, color, letter grade, percentage, and the like.
Additional information on gaming systems, including gaming device and viral gaming events, can be found in U.S. Pat. No. 8,864,586, which is hereby incorporated herein by reference.
Additional information on gaming systems, including location based real-time casino data, can be found in U.S. Pat. No. 9,626,826, which is hereby incorporated herein by reference.
While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein.
This application is a continuation-in-part of U.S. application Ser. No. 16/559,553, filed Sep. 3, 2019, and entitled “GAMING SYSTEMS INCLUDING VIRUAL BENEFIT DISTRIBUTION,” which is hereby incorporated herein by reference, and which in turn is a continuation of U.S. application Ser. No. 14/518,909, filed Oct. 20, 2014, and entitled “VIRUAL BENEFIT DISTRIBUTION USING ELECTRONIC DEVICES,” which is hereby incorporated herein by reference, and which in turn is a continuation of U.S. application Ser. No. 12/617,717, filed Nov. 12, 2009, and entitled “GAMING SYSTEMS INCLUDING VIRAL GAMING EVENTS,” now U.S. Pat. No. 8,864,586), which is hereby incorporated herein by reference. This application is continuation-in-part of U.S. patent application Ser. No. 15/480,295, filed Apr. 5, 2017, and entitled “LOCATION BASED REAL-TIME CASINO DATA”, which is hereby incorporated herein by reference for all purposes, which in turn is a divisional of U.S. patent application Ser. No. 13/801,256, filed Mar. 13, 2013, and entitled “LOCATION BASED REAL-TIME CASINO DATA”, which is hereby incorporated herein by reference for all purposes, which in turn is a continuation of U.S. patent application Ser. No. 12/797,610, filed Jun. 10, 2010, and entitled “LOCATION BASED REAL-TIME CASINO DATA”, now U.S. Pat. No. 9,626,826, which is hereby incorporated herein by reference for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2033638 | Koppl | Mar 1936 | A |
| 2062923 | Nagy | Dec 1936 | A |
| 4741539 | Sutton et al. | May 1988 | A |
| 4948138 | Pease et al. | Aug 1990 | A |
| 5067712 | Georgilas | Nov 1991 | A |
| 5275400 | Weingardt | Jan 1994 | A |
| 5429361 | Raven et al. | Jul 1995 | A |
| 5489103 | Okamoto | Feb 1996 | A |
| 5630757 | Gagin | May 1997 | A |
| 5655961 | Acres et al. | Aug 1997 | A |
| 5704835 | Dietz, II | Jan 1998 | A |
| 5727786 | Weingardt | Mar 1998 | A |
| 5833537 | Barrie | Nov 1998 | A |
| 5842921 | Mindes | Dec 1998 | A |
| 5919091 | Bell et al. | Jul 1999 | A |
| 5947820 | Morro et al. | Sep 1999 | A |
| 5997401 | Crawford | Dec 1999 | A |
| 6001016 | Walker et al. | Dec 1999 | A |
| 6039648 | Guinn et al. | Mar 2000 | A |
| 6059289 | Vancura | May 2000 | A |
| 6089977 | Bennett | Jul 2000 | A |
| 6095920 | Sudahiro | Aug 2000 | A |
| 6110041 | Walker et al. | Aug 2000 | A |
| 6142872 | Walker et al. | Nov 2000 | A |
| 6146271 | Kadici | Nov 2000 | A |
| 6146273 | Olsen | Nov 2000 | A |
| 6165071 | Weiss | Dec 2000 | A |
| 6231445 | Acres | May 2001 | B1 |
| 6244958 | Acres | Jun 2001 | B1 |
| 6270412 | Crawford et al. | Aug 2001 | B1 |
| 6290600 | Glasson | Sep 2001 | B1 |
| 6293866 | Walker et al. | Sep 2001 | B1 |
| 6353390 | Beri et al. | Mar 2002 | B1 |
| 6364768 | Acres et al. | Apr 2002 | B1 |
| 6404884 | Marwell et al. | Jun 2002 | B1 |
| 6416406 | Duhamel | Jul 2002 | B1 |
| 6416409 | Jordan | Jul 2002 | B1 |
| 6443452 | Brune | Sep 2002 | B1 |
| 6491584 | Graham et al. | Dec 2002 | B2 |
| 6505095 | Kolls | Jan 2003 | B1 |
| 6508710 | Paravia et al. | Jan 2003 | B1 |
| 6561900 | Baerlocker et al. | May 2003 | B1 |
| 6592457 | Frohm et al. | Jul 2003 | B1 |
| 6612574 | Cole et al. | Sep 2003 | B1 |
| 6620046 | Rowe | Sep 2003 | B2 |
| 6641477 | Dietz, II | Nov 2003 | B1 |
| 6645078 | Mattice | Nov 2003 | B1 |
| 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 |
| 8282475 | Nguyen et al. | Oct 2012 | B2 |
| 8323099 | Durham et al. | Dec 2012 | B2 |
| 8337290 | Nguyen et al. | Dec 2012 | B2 |
| 8342946 | Amaitis | Jan 2013 | B2 |
| 8393948 | Allen et al. | Mar 2013 | B2 |
| 8403758 | Hornik et al. | Mar 2013 | B2 |
| 8430745 | Agarwal et al. | Apr 2013 | B2 |
| 8461958 | Saenz | Jun 2013 | B2 |
| 8469813 | Joshi | Jun 2013 | B2 |
| 8529345 | Nguyen | Sep 2013 | B2 |
| 8597108 | Nguyen | Dec 2013 | B2 |
| 8602875 | Nguyen | Dec 2013 | B2 |
| 8613655 | Kisenwether et al. | Dec 2013 | B2 |
| 8613659 | Nelson et al. | Dec 2013 | B2 |
| 8622823 | Huynh | Jan 2014 | B2 |
| 8678901 | Kelly | Mar 2014 | B1 |
| 8696470 | Nguyen | Apr 2014 | B2 |
| 8745417 | Huang et al. | Jun 2014 | B2 |
| 8758102 | Block | Jun 2014 | B2 |
| 8834254 | Buchholz et al. | Sep 2014 | B2 |
| 8858323 | Nguyen et al. | Oct 2014 | B2 |
| 8864586 | Nguyen | Oct 2014 | B2 |
| 8942995 | Kerr | Jan 2015 | B1 |
| 9039507 | Allen et al. | May 2015 | B2 |
| 9235952 | Nguyen | Jan 2016 | B2 |
| 9292996 | Davis et al. | Mar 2016 | B2 |
| 9325203 | Nguyen | Apr 2016 | B2 |
| 9466171 | Hornik | Oct 2016 | B2 |
| 9483901 | Nguyen | Nov 2016 | B2 |
| 9486697 | Nguyen | Nov 2016 | B2 |
| 9486704 | Nguyen | Nov 2016 | B2 |
| 9530277 | Nelson et al. | Dec 2016 | B2 |
| 9576425 | Nguyen | Feb 2017 | B2 |
| 9626826 | Nguyen | Apr 2017 | B2 |
| 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 |
| 10818133 | Nguyen | Oct 2020 | B2 |
| 11704971 | Nguyen | Jul 2023 | 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 |
| 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 |
| 20030027635 | Walker et al. | Feb 2003 | A1 |
| 20030064805 | Wells | Apr 2003 | A1 |
| 20030064807 | Walker et al. | Apr 2003 | A1 |
| 20030092480 | White et al. | May 2003 | A1 |
| 20030100361 | Sharpless et al. | May 2003 | A1 |
| 20030104860 | Cannon et al. | Jun 2003 | A1 |
| 20030104865 | Itkis et al. | Jun 2003 | A1 |
| 20030148809 | Nelson | Aug 2003 | A1 |
| 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 |
| 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 |
| 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 |
| 20050170883 | Muskin et al. | Aug 2005 | A1 |
| 20050181865 | Luciano | Aug 2005 | A1 |
| 20050181870 | Nguyen et al. | Aug 2005 | A1 |
| 20050181875 | Hoehne | Aug 2005 | A1 |
| 20050187020 | Amaitis et al. | Aug 2005 | A1 |
| 20050202875 | Murphy et al. | Sep 2005 | A1 |
| 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 |
| 20060036874 | Cockerille | Feb 2006 | A1 |
| 20060046822 | Kaminkow et al. | Mar 2006 | A1 |
| 20060046830 | Webb | Mar 2006 | A1 |
| 20060046849 | Kovacs | Mar 2006 | A1 |
| 20060068893 | Jaffe et al. | Mar 2006 | A1 |
| 20060073869 | LeMay et al. | Apr 2006 | A1 |
| 20060073897 | Englman et al. | Apr 2006 | A1 |
| 20060079317 | Flemming et al. | Apr 2006 | A1 |
| 20060121972 | Walker | Jun 2006 | A1 |
| 20060126529 | Hardy | Jun 2006 | A1 |
| 20060148551 | Walker et al. | Jul 2006 | A1 |
| 20060189382 | Muir et al. | Aug 2006 | A1 |
| 20060217170 | Roireau | Sep 2006 | A1 |
| 20060217193 | Walker et al. | Sep 2006 | A1 |
| 20060247028 | Brosnan et al. | Nov 2006 | A1 |
| 20060247035 | Rowe et al. | Nov 2006 | A1 |
| 20060252530 | Oberberger et al. | Nov 2006 | A1 |
| 20060253481 | Guido et al. | Nov 2006 | A1 |
| 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 |
| 20070238505 | Okada | Oct 2007 | A1 |
| 20070241187 | Alderucci et al. | Oct 2007 | A1 |
| 20070243925 | LeMay | 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 |
| 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 |
| 20080102956 | Burman et al. | May 2008 | A1 |
| 20080102957 | Burnman et al. | May 2008 | A1 |
| 20080108401 | Baerlocher | May 2008 | A1 |
| 20080113772 | Burrill et al. | May 2008 | A1 |
| 20080119267 | Denlay | May 2008 | A1 |
| 20080013906 | Lutnick | Jun 2008 | A1 |
| 20080146321 | Parente | Jun 2008 | A1 |
| 20080146344 | Rowe et al. | Jun 2008 | A1 |
| 20080150902 | Edpalm et al. | Jun 2008 | A1 |
| 20080153583 | Huntley et al. | Jun 2008 | A1 |
| 20080161110 | Campbell | Jul 2008 | A1 |
| 20080167106 | Lutnick et al. | Jul 2008 | A1 |
| 20080182667 | Davis et al. | Jul 2008 | A1 |
| 20080200251 | Alderucci et al. | Aug 2008 | A1 |
| 20080207307 | Cunningham II et al. | Aug 2008 | A1 |
| 20080214258 | Brosnan et al. | Sep 2008 | A1 |
| 20080215319 | Lu | Sep 2008 | A1 |
| 20080234047 | Nguyen | Sep 2008 | A1 |
| 20080238610 | Rosenbereg | Oct 2008 | A1 |
| 20080248849 | Lutnick | Oct 2008 | A1 |
| 20080248865 | Cole | Oct 2008 | A1 |
| 20080252419 | Batchelor | Oct 2008 | A1 |
| 20080254878 | Sauders et al. | Oct 2008 | A1 |
| 20080254881 | Lutnick et al. | Oct 2008 | A1 |
| 20080254883 | Patel et al. | Oct 2008 | A1 |
| 20080254891 | Sauders et al. | Oct 2008 | A1 |
| 20080254892 | Sauders et al. | Oct 2008 | A1 |
| 20080254897 | Sauders et al. | Oct 2008 | A1 |
| 20080263173 | Weber et al. | Oct 2008 | A1 |
| 20080300058 | Sum et al. | Dec 2008 | A1 |
| 20080305864 | Kelly et al. | Dec 2008 | A1 |
| 20080305865 | Kelly et al. | Dec 2008 | A1 |
| 20080305866 | Kelly et al. | Dec 2008 | A1 |
| 20080311994 | Amaitas et al. | Dec 2008 | A1 |
| 20080318669 | Buchholz | Dec 2008 | A1 |
| 20080318686 | Crowder et al. | Dec 2008 | A1 |
| 20090005165 | Arezina et al. | Jan 2009 | A1 |
| 20090011822 | Englman | Jan 2009 | A1 |
| 20090017906 | Jackson | Jan 2009 | A1 |
| 20090021381 | Higuchi | Jan 2009 | A1 |
| 20090029766 | Lutnick et al. | Jan 2009 | A1 |
| 20090054149 | Brosnan et al. | Feb 2009 | A1 |
| 20090077396 | Tsai et al. | Mar 2009 | A1 |
| 20090088258 | Saunders et al. | Apr 2009 | A1 |
| 20090098925 | Gagner et al. | Apr 2009 | A1 |
| 20090104977 | Zielinski | Apr 2009 | A1 |
| 20090104983 | Okada | Apr 2009 | A1 |
| 20090118002 | Lyons | May 2009 | A1 |
| 20090118013 | Finnimore et al. | May 2009 | A1 |
| 20090118022 | Lyons et al. | May 2009 | A1 |
| 20090124366 | Aoki et al. | May 2009 | A1 |
| 20090124390 | Seelig et al. | May 2009 | A1 |
| 20090131146 | Arezina et al. | May 2009 | A1 |
| 20090131151 | Harris et al. | May 2009 | A1 |
| 20090132163 | Ashley et al. | May 2009 | A1 |
| 20090137255 | Ashley et al. | May 2009 | A1 |
| 20090138133 | Buchholz et al. | May 2009 | A1 |
| 20090143141 | Wells | Jun 2009 | A1 |
| 20090149245 | Fabbri | Jun 2009 | A1 |
| 20090149261 | Chen et al. | Jun 2009 | A1 |
| 20090153342 | Thorn | Jun 2009 | A1 |
| 20090156303 | Kiely et al. | Jun 2009 | A1 |
| 20090163272 | Baker | Jun 2009 | A1 |
| 20090176578 | Herrmann et al. | Jul 2009 | A1 |
| 20090191962 | Hardy et al. | Jul 2009 | A1 |
| 20090197684 | Arezina | 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 |
| 20090239648 | Acres | 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 |
| 20090275410 | Kisenwether et al. | Nov 2009 | A1 |
| 20090275411 | Kisenwether et al. | Nov 2009 | A1 |
| 20090280910 | Gagner et al. | Nov 2009 | A1 |
| 20090282469 | Lynch | Nov 2009 | A1 |
| 20090298468 | Hsu | Dec 2009 | A1 |
| 20100002897 | Keady | Jan 2010 | A1 |
| 20100004058 | Acres | Jan 2010 | A1 |
| 20100016069 | Herrmann | Jan 2010 | A1 |
| 20100049738 | Mathur et al. | Feb 2010 | A1 |
| 20100056248 | Acres | Mar 2010 | A1 |
| 20100062833 | Mattice et al. | Mar 2010 | A1 |
| 20100062840 | Herrmann et al. | Mar 2010 | A1 |
| 20100079237 | Falk | Apr 2010 | A1 |
| 20100081501 | Carpenter et al. | Apr 2010 | A1 |
| 20100081509 | Burke | Apr 2010 | A1 |
| 20100099499 | Amaitis et al. | Apr 2010 | A1 |
| 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 |
| 20100203963 | Allen | Aug 2010 | A1 |
| 20100227662 | Speers et al. | Sep 2010 | A1 |
| 20100227670 | Arezine et al. | Sep 2010 | A1 |
| 20100227671 | Laaroussi | Sep 2010 | A1 |
| 20100227687 | Speers et al. | Sep 2010 | A1 |
| 20100234091 | Baerlocher et al. | Sep 2010 | A1 |
| 20100279764 | Allen et al. | Nov 2010 | A1 |
| 20100323780 | Acres | Dec 2010 | A1 |
| 20100325703 | Etchegoyen | Dec 2010 | A1 |
| 20110009181 | Speer, II | Jan 2011 | A1 |
| 20110039615 | Acres | Feb 2011 | A1 |
| 20110053679 | Canterbury et al. | Mar 2011 | A1 |
| 20110065492 | Acres | Mar 2011 | A1 |
| 20110105216 | Cohen | May 2011 | A1 |
| 20110111827 | Nicely et al. | May 2011 | A1 |
| 20110111843 | Nicely et al. | May 2011 | A1 |
| 20110111860 | Nguyen | May 2011 | A1 |
| 20110118010 | Brune | May 2011 | A1 |
| 20110159966 | Gura et al. | Jun 2011 | A1 |
| 20110183732 | Block | Jul 2011 | A1 |
| 20110183749 | Allen | Jul 2011 | A1 |
| 20110207525 | Allen | Aug 2011 | A1 |
| 20110212711 | Scott | Sep 2011 | A1 |
| 20110212767 | Barclay et al. | Sep 2011 | A1 |
| 20110223993 | Allen et al. | Sep 2011 | A1 |
| 20110244952 | Schueller | Oct 2011 | A1 |
| 20110263318 | Agarwal et al. | Oct 2011 | A1 |
| 20110269548 | Barclay et al. | Nov 2011 | A1 |
| 20110306400 | Nguyen | Dec 2011 | A1 |
| 20110306426 | Novak et al. | Dec 2011 | A1 |
| 20120015709 | Bennett et al. | Jan 2012 | A1 |
| 20120028703 | Anderson et al. | Feb 2012 | A1 |
| 20120028718 | Barclay et al. | Feb 2012 | A1 |
| 20120034968 | Watkins et al. | Feb 2012 | A1 |
| 20120046110 | Amaitis | Feb 2012 | A1 |
| 20120094769 | Nguyen et al. | Apr 2012 | A1 |
| 20120100908 | Wells | Apr 2012 | A1 |
| 20120108319 | Caputo et al. | May 2012 | A1 |
| 20120122561 | Hedrick | May 2012 | A1 |
| 20120122567 | Gangadharan et al. | May 2012 | A1 |
| 20120122584 | Nguyen | May 2012 | A1 |
| 20120122590 | Nguyen | May 2012 | A1 |
| 20120172130 | Acres | Jul 2012 | A1 |
| 20120184362 | Barclay et al. | Jul 2012 | A1 |
| 20120184363 | Barclay et al. | Jul 2012 | A1 |
| 20120190426 | Acres | Jul 2012 | A1 |
| 20120194448 | Rothkopf | Aug 2012 | A1 |
| 20120208618 | Frerking | Aug 2012 | A1 |
| 20120231885 | Speer, II | Sep 2012 | A1 |
| 20120231888 | Abe | 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 |
| 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 |
| 20170016819 | Nguyen | Apr 2017 | A1 |
| 20170116823 | Nguyen | Apr 2017 | A1 |
| 20170144071 | Nguyen | May 2017 | A1 |
| 20170148259 | Nguyen | May 2017 | A1 |
| 20170148261 | Nguyen | May 2017 | A1 |
| 20170148263 | Nguyen | May 2017 | A1 |
| 20170206734 | Nguyen | Jul 2017 | A1 |
| 20170228979 | Nguyen | Aug 2017 | A1 |
| 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 |
| 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 |
| 2010002897 | Jan 2010 | WO |
| WO 2010017252 | Feb 2010 | WO |
| Entry |
|---|
| Benston, Liz, “Harrah Launches iPhone Appl 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 wirelss market”, azcentral.com, http://www.azcentral.com/business/news/articles/20130424telecom-equipped-drones-could-revolutionize-wireless-market.html, downloaded Jul. 2, 2013, 2 pages. |
| Yancey, Kitty Bean, “Navigate Around Vegas with New iPhone Apps”, USA Today, Jun. 3, 2010. |
| IAPS, Daily Systems LLC, 2010. |
| U.S. Appl. No. 12/945,888, filed Nov. 14, 2010. |
| U.S. Appl. No. 12/945,889, filed Nov. 14, 2010. |
| U.S. Appl. No. 13/622,702, filed Sep. 19, 2012. |
| U.S. Appl. No. 13/800,917, filed Mar. 13, 2013. |
| U.S. Appl. No. 13/296,182, filed Nov. 15, 2011. |
| U.S. Appl. No. 13/801,234, filed Mar. 13, 2013. |
| U.S. Appl. No. 13/801,171, filed Mar. 13, 2013. |
| U.S. Appl. No. 13/843,192, filed Mar. 15, 2013. |
| U.S. Appl. No. 13/843,087, filed Mar. 15, 2013. |
| U.S. Appl. No. 13/632,743, filed Oct. 1, 2012. |
| U.S. Appl. No. 13/632,828, filed Oct. 1, 2012. |
| U.S. Appl. No. 13/833,953, filed Mar. 15, 2013. |
| U.S. Appl. No. 12/619,672, filed Nov. 16, 2009. |
| U.S. Appl. No. 13/801,121, filed Mar. 13, 2013. |
| U.S. Appl. No. 12/581,115, filed Oct. 17, 2009. |
| U.S. Appl. No. 13/801,076, filed Mar. 13, 2013. |
| U.S. Appl. No. 13/617,717, filed Nov. 12, 2009. |
| U.S. Appl. No. 13/633,118, filed Oct. 1, 2012. |
| U.S. Appl. No. 12/797,610, filed Jun. 10, 2010. |
| U.S. Appl. No. 13/801,256, filed Mar. 13, 2013. |
| U.S. Appl. No. 12/757,968, filed Apr. 9, 2010. |
| U.S. Appl. No. 12/797,616, filed Jun. 10, 2010. |
| U.S. Appl. No. 13/557,063, filed Jul. 24, 2012. |
| U.S. Appl. No. 13/833,116, filed Mar. 15, 2013. |
| U.S. Appl. No. 13/801,271, filed Mar. 13, 2011. |
| Office Action for U.S. Appl. No. 12/945,888 dated Apr. 10, 2012. |
| Final Office Action for U.S. Appl. No. 12/945,888 dated Sep. 21, 2012. |
| Advisory Action for U.S. Appl. No. 12/945,888 dated Jan. 30, 2013. |
| Office Action for U.S. Appl. No. 12/581,115 dated Dec. 20, 2011. |
| Final Office Action for U.S. Appl. No. 12/581,115 dated Sep. 13, 2012. |
| Notice of Allowance for U.S. Appl. No. 12/581,115 dated May 24, 2013. |
| Office Action for U.S. Appl. No. 12/619,672 dated Dec. 20, 2011. |
| Final Office Action for U.S. Appl. No. 12/619,672 dated Nov. 6, 2012. |
| Office Action for U.S. Appl. No. 12/619,672 dated March, 7, 2013. |
| Office Action for U.S. Appl. No. 12/617,717 dated Oct. 4, 2011. |
| Office Action for U.S. Appl. No. 12/617,717 dated Apr. 4, 2012. |
| Advisory Action for U.S. Appl. No. 12/617,717 dated Jun. 12, 2011. |
| Office Action for U.S. Appl. No. 12/617,717 dated Jun. 17, 2013. |
| Office Action for U.S. Appl. No. 12/797,610 dated Dec. 8, 2011. |
| Final Office Action for U.S. Appl. No. 12/797,610 dated Jun. 6, 2012. |
| Office Action for U.S. Appl. No. 12/797,610 dated Feb. 26, 2013. |
| Office Action for U.S. Appl. No. 12/757,968, dated May 9, 2012. |
| Final Office Action for U.S. Appl. No. 12/757,968, dated Nov. 29, 2012. |
| Office Action for U.S. Appl. No. 12/757,968, dated Apr. 25, 2013. |
| Office Action for U.S. Appl. No. 12/797,616 dated Mar. 15, 2012. |
| Final Office Action for U.S. Appl. No. 12/797,616 dated Oct. 13, 2012. |
| Office Action for U.S. Appl. No. 12/797,616 dated Feb. 13, 2013. |
| Final Office Action for U.S. Appl. No. 12/797,616 dated May 8, 2013. |
| Office Action for U.S. Appl. No. 13/296,182 dated Dec. 5, 2012. |
| Brochure, 5000 Ft. Inc., 1 page, Nov. 2010. |
| Frontier Fortune game, email notification, MGM Resorts Intl., Aug. 9, 2013. |
| “Getting Back in the Game: Geolocation Can Ensure Compliance with New iGaming Regulations”, White Paper, Quova, Inc., 2010. |
| Notice of Allowance of U.S. Appl. No. 12/619,672, dated Aug. 23, 2013. |
| Office Action for U.S. Appl. No. 13/633,118, dated Sep. 20, 2013. |
| Office Action for U.S. Appl. No. 13/801,256, dated Jul. 2, 2013. |
| Notice of Allowance for U.S. Appl. No. 12/619,672, dated Oct. 3, 2013. |
| Notice of Allowance for U.S. Appl. No. 12/757,968, dated Oct. 11, 2013. |
| Final Office Action for U.S. Appl. No. 12/797,610, dated Jul. 10, 2013. |
| Notice of Allowance for U.S. Appl. No. 12/757,968, dated Dec. 18, 2013. |
| Office Action for U.S. Appl. No. 12/945,889, dated Dec. 18, 2013. |
| Office Action for U.S. Appl. No. 13/632,828, dated Jul. 30, 2013. |
| Restriction Requirement for U.S. Appl. No. 13/801,256, dated Dec. 30, 2013. |
| Office Action for U.S. Appl. No. 13/801,171, dated Dec. 26, 2013. |
| Office Action for U.S. Appl. No. 13/801,234, dated Jan. 10, 2014. |
| Final Office Action for U.S. Appl. No. 13/296,182, dated Feb. 12, 2014. |
| Office Action for U.S. Appl. No. 12/617,717, dated Feb. 25, 2014. |
| Office Action for U.S. Appl. No. 13/801,076, dated Mar. 28, 2014. |
| Final Office Action for U.S. Appl. No. 13/633,118, dated Apr. 3, 2014. |
| Office Action for U.S. Appl. No. 13/843,192, dated Apr. 3, 2014. |
| Office Action for U.S. Appl. No. 13/632,743, dated Apr. 10, 2014. |
| Office Action for U.S. Appl. No. 13/801,121, dated Apr. 11, 2014. |
| Final Office Action for U.S. Appl. No. 12/945,889, dated Jun. 30, 2014. |
| Notice of Allowance for U.S. Appl. No. 12/617,717, dated Jul. 14, 2014. |
| Office Action for U.S. Appl. No. 13/801,121, dated Sep. 24, 2014. |
| Office Action for U.S. Appl. No. 13/801,171, dated Sep. 22, 2014. |
| Office Action for U.S. Appl. No. 13/801,234, dated Oct. 1, 2014. |
| Office Action for U.S. Appl. No. 13/801,271, dated Oct. 31, 2014. |
| Final Office Action for U.S. Appl. No. 13/843,192, dated Oct. 21, 2014. |
| Office Action for U.S. Appl. No. 13/632,743, dated Oct. 23, 2014. |
| Office Action for U.S. Appl. No. 12/945,889, dated Oct. 23, 2014. |
| Office Action for U.S. Appl. No. 13/632,828, dated Nov. 7, 2014. |
| Office Action for U.S. Appl. No. 12/797,610, dated Dec. 15, 2014. |
| Final Office Action for U.S. Appl. No. 12/945,889, dated Feb. 12, 2015. |
| Final Office Action for U.S. Appl. No. 13/801,171, dated Mar. 16, 2015. |
| Office Action for U.S. Appl. No. 13/833,116, dated Mar. 27, 2015. |
| Office Action for U.S. Appl. No. 13/632,828, dated Apr. 10, 2015. |
| Final Office Action for U.S. Appl. No. 13/801,121, dated Apr. 21, 2015. |
| Final Office Action for U.S. Appl. No. 13/557,063, dated Apr. 28, 2015. |
| Office Action for U.S. Appl. No. 13/296,182, dated Jun. 5, 2015. |
| Office Action for U.S. Appl. No. 13/843,192, dated Jun. 19, 2015. |
| Office Action for U.S. Appl. No. 12/797,610, dated Jul. 14, 2015. |
| Final Office Action for U.S. Appl. No. 13/833,953, dated Jul. 17, 2015. |
| Notice of Allowance for U.S. Appl. No. 12/945,889, dated Jul. 22, 2015. |
| Office Action for U.S. Appl. No. 12/797,616, dated Aug. 10, 2015. |
| Final Office Action for U.S. Appl. No. 13/801,234, dated Aug. 14, 2015. |
| Final Office Action for U.S. Appl. No. 13/833,116, dated Sep. 24, 2015. |
| Office Action for U.S. Appl. No. 13/801,121, dated Oct. 2, 2015. |
| Office Action for U.S. Appl. No. 14/017,150, dated Oct. 7, 2015. |
| Office Action for U.S. Appl. No. 14/017,159, dated Oct. 7, 2015. |
| Office Action for U.S. Appl. No. 13/801,271 dated Oct. 19, 2015. |
| Office Action for U.S. Appl. No. 13/632,828 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/843,192, 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/633,118, 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. 14/017,159, 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/833,953, dated Jun. 9, 2016. |
| Final OA for U.S. Appl. No. 13/833,953, dated Jun. 28, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/833,953, dated Jul. 6, 2016. |
| Office Action for U.S. Appl. No. 13/801,076, 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. |
| Office Action for U.S. Appl. No. 13/296,182, dated Dec. 23, 2015. |
| Advisory Action for U.S. Appl. No. 13/843,192, dated May 8, 2014. |
| Office Action for U.S. Appl. No. 14/217,066, dated Dec. 22, 2016. |
| Final Office Action for U.S. Appl. No. 14/216,986, dated Sep. 23, 2016. |
| Office Action for U.S. Appl. No. 14/017,159, dated Sep. 23, 2016. |
| Office Action for U.S. Appl. No. 13/632,743, dated Sep. 23, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,234, dated Oct. 14, 2016. |
| Final Office Action for U.S. Appl. No. 13/843,087, dated Oct. 13, 2016. |
| Final Office Action for U.S. Appl. No. 13/622,702, dated Oct. 13, 2016. |
| Office Action for U.S. Appl. No. 14/189,948, dated Nov. 7, 2016. |
| Final Office Action for U.S. Appl. No. 14/211,536, dated Mar. 14, 2014. |
| Notice of Allowance for U.S. Appl. No. 13/833,116, dated Oct. 11, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/801,271, dated Dec. 2, 2016. |
| Notice of Allowance for U.S. Appl. No. 12/797,610, dated Dec. 7, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/632,828, dated Dec. 16, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 19, 2016. |
| Notice of Allowance for U.S. Appl. No. 14/211,536, dated Dec. 28, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/801,256, dated Jan. 20, 2017. |
| Office Action for U.S. Appl. No. 13/800,917, dated Feb. 3, 2017. |
| Final Office Action for U.S. Appl. No. 12/797,616, dated Feb. 10, 2017. |
| Office Action for U.S. Appl. No. 12/945,888, dated Feb. 28, 2017. |
| Final Office Action for U.S. Appl. No. 14/189,948, dated Mar. 17, 2017. |
| Office Action for U.S. Appl. No. 15/400,840, dated Mar. 10, 2017. |
| Notice of Allowance for U.S. Appl. No. 13/801,121, dated Mar. 29, 2017. |
| Office Action for U.S. Appl. No. 15/270,333, dated Mar. 30, 2017. |
| Office Action for U.S. Appl. No. 15/402,945, dated Apr. 5, 2017. |
| Office Action for U.S. Appl. No. 15/271,488, dated Apr. 19, 2017. |
| Final Office Action for U.S. Appl. No. 14/217,066, dated Apr. 21, 2017. |
| Office Action for U.S. Appl. No. 14/216,986 dated Apr. 26, 2017. |
| Office Action for U.S. Appl. No. 13/801,171, dated Jun. 14, 2017. |
| Office Action for U.S. Appl. No. 14/017,159, dated Jun. 29, 2017. |
| Notice of Allowance for U.S. Appl. No. 15/270,333, dated Jul. 5, 2017. |
| Final Office Action for U.S. Appl. No. 13/800,917, dated Jul. 13, 2017. |
| Notice of Allowance for U.S. Appl. No. 13/801,234, dated Jul. 5, 2017. |
| Notice of Allowance for U.S. Appl. No. 14/217,066, dated Jul. 14, 2017. |
| Final Office Action for U.S. Appl. No. 14/518,909, dated Jul. 19, 2017. |
| Final Office Action for U.S. Appl. No. 13/801,121, dated Sep. 15, 2016. |
| Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 17, 2015. |
| Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 19, 2016. |
| Notice of Allowance for U.S. Appl. No. 15/293,751, dated Aug. 4, 2017. |
| Advisory Action for U.S. Appl. No. 14/189,948, dated Jul. 28, 2017. |
| Final OA for U.S. Appl. No. 13/801,256, dated Aug. 15, 2014. |
| Final OA for U.S. Appl. No. 13/801,256, dated Feb. 18, 2015. |
| Advisory Action for U.S. Appl. No. 13/801,256, dated Dec. 5, 2014. |
| Office Action for U.S. Appl. No. 13/801,256, dated Jan. 12, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,256, dated Aug. 16, 2016. |
| Office Action for U.S. Appl. No. 13/622,702, dated Aug. 31, 2017. |
| Office Action for U.S. Appl. No. 12/945,888, dated Sep. 1, 2017. |
| Office Action for U.S. Appl. No. 14/017,150, dated Sep. 7, 2017. |
| Notice of Allowance for U.S. Appl. No. 14/189,948, dated Sep. 13, 2017. |
| Office Action for U.S. Appl. No. 15/138,086, dated Oct. 19, 2017. |
| Notice of Allowance for U.S. Appl. No. 15/402,945 dated Nov. 21, 2017. |
| Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 13, 2017. |
| Final Office Action for U.S. Appl. No. 15/271,488, dated Dec. 21, 2017. |
| Office Action for U.S. Appl. No. 14/216,986, 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. 14/017,159, 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/427,291, dated Jun. 4, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/427,291 dated Jun. 18, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/271,488, dated Jun. 19, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/480,295, dated Jun. 20, 2018. |
| Office Action for U.S. Appl. No. 14/963,106, dated Jun. 22, 2018. |
| Office Action for U.S. Appl. No. 14/993,055, dated Jun. 22, 2018. |
| Final Office Action for U.S. Appl. No. 15/427,307, dated Jul. 9, 2018. |
| Notice of Allowance for U.S. Appl. No. 13/633,118, dated Aug. 3, 2018. |
| Office Action for U.S. Appl. No. 15/671,133, dated Aug. 9, 2018. |
| Office Action for U.S. Appl. No. 15/427,308, dated Aug. 15, 2018. |
| Office Action for U.S. Appl. No. 15/798,363, dated Aug. 29, 2018. |
| Office Action for U.S. Appl. No. 15/428,922 dated Sep. 17, 2018. |
| Office Action for U.S. Appl. No. 15/495,975, dated Sep. 21, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/271,488, dated Sep. 24, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/876,095, dated Sep. 24, 2018. |
| Office Action for U.S. Appl. No. 13/622,702, dated Oct. 3, 2018. |
| Office Action for U.S. Appl. No. 15/293,751, dated Apr. 6, 2017. |
| Notice of Allowance for U.S. Appl. No. 13/801,171, dated Oct. 31, 2018. |
| Final Office Action for U.S. Appl. No. 15/835,448, dated Nov. 2, 2018. |
| Final Office Action for U.S. Appl. No. 15/480,295, dated Nov. 7, 2018. |
| Final Office Action for U.S. Appl. No. 14/963,106, dated Dec. 14, 2018. |
| Final Office Action for U.S. Appl. No. 14/993,055, dated Dec. 14, 2018. |
| Office Action for U.S. Appl. No. 16/162,358, dated Dec. 31, 2018. |
| Office Action for No. U.S. Appl. No. 15/428,922 dated Sep. 17, 2018. |
| Office Action for U.S. Appl. No. 14/017,159, dated Jan. 11, 2019. |
| Office Action for U.S. Appl. No. 15/426,898, dated Jan. 11, 2019. |
| Final Office Action for U.S. Appl. No. 15/495,973, dated Jan. 11, 2019. |
| Office Action for U.S. Appl. No. 14/216,986, dated Jan. 14, 2019. |
| Office Action for U.S. Appl. No. 15/427,307, dated Jan. 18, 2019. |
| Final Office Action for U.S. Appl. No. 15/798,363, dated Feb. 4, 2019. |
| Office Action for U.S. Appl. No. 16/125,614, dated Feb. 25, 2019. |
| Final Office Action for U.S. Appl. No. 15/495,975, dated Apr. 18, 2019. |
| Office Action for U.S. Appl. No. 15/671,133, dated May 1, 2019. |
| Notice of Allowance for U.S. Appl. No. 14/216,986, dated May 17, 2019. |
| Notice of Allowance for U.S. Appl. No. 14/518,909, dated May 17, 2019. |
| Office Action for U.S. Appl. No. 12/797,616, dated Jun. 5, 2019. |
| Office Action for U.S. Appl. No. 15/427,308, dated Jun. 14, 2019. |
| Office Action for U.S. Appl. No. 15/811,654, dated Jun. 14, 2019. |
| Office Action for U.S. Appl. No. 15/674,480, dated Jun. 20, 2019. |
| Notice of Allowance for U.S. Appl. No. 15/835,448, dated Jul. 3, 2019. |
| Final Office Action for U.S. Appl. No. 16/162,358, dated Jul. 11, 2019. |
| Office Action for U.S. Appl. No. 16/190,050, dated Sep. 19, 2019. |
| Office Action for U.S. Appl. No. 14/017,150, dated Oct. 9, 2019. |
| Final Office Action for U.S. Appl. No. 15/671,133, dated Oct. 18, 2019. |
| Office Action for U.S. Appl. No. 15/835,448 dated Oct. 12, 2019. |
| Notice of Allowance for U.S. Appl. No. 15/495,975, dated Oct. 23, 2019. |
| Notice of Allowance for U.S. Appl. No. 14/993,005, dated Nov. 27, 2019. |
| Final Office Action for U.S. Appl. No. 15/427,308, dated Nov. 27, 2019. |
| Office Action for U.S. Appl. No. 15/798,363, dated Jan. 8, 2020. |
| Office Action for U.S. Appl. No. 15/835,448, dated Mar. 5, 2020. |
| Office Action for U.S. Appl. No. 15/495,975, dated Mar. 17, 2020. |
| Office Action for U.S. Appl. No. 16/248,759, dated Apr. 1, 2020. |
| Final Office Action for U.S. Appl. No. 14/017,150, dated Apr. 17, 2020. |
| Notice of Allowance for U.S. Appl. No. 15/798,363, dated May 12, 2020. |
| Office Action for U.S. Appl. No. 16/357,316, dated May 21, 2020. |
| Office Action for U.S. Appl. No. 15/674,480, dated Jun. 5, 2020. |
| Notice of Allowance for U.S. Appl. No. 15/480,295, dated Jun. 15, 2020. |
| Office Action for U.S. Appl. No. 13/622,702, dated Jun. 22, 2020. |
| Office Action for U.S. Appl. No. 15/811,654, dated Jun. 26, 2020. |
| Office Action for U.S. Appl. No. 16/579,754, dated Jul. 22, 2020. |
| Office Action for U.S. Appl. No. 16/219,940, dated Jul. 22, 2020. |
| Office Action for U.S. Appl. No. 16/559,553, dated Sep. 11, 2020. |
| Office Action for U.S. Appl. No. 16/794,212, dated Sep. 11, 2020. |
| Restriction Requirement for U.S. Appl. No. 16/600,395, dated Sep. 18, 2020. |
| Final Office Action for U.S. Appl. No. 16/248,759, dated Oct. 6, 2020. |
| Final Office Action for U.S. Appl. No. 15/671,133, dated Oct. 7, 2020. |
| Final Office Action for U.S. Appl. No. 16/357,316, dated Oct. 8, 2020. |
| Final Office Action for U.S. Appl. No. 16/183,632, dated Oct. 9, 2020. |
| Office Action for U.S. Appl. No. 16/590,347, dated Oct. 13, 2020. |
| Advisory Action for U.S. Appl. No. 13/632,828, dated Feb. 25, 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. |
| Advisory Action for U.S. Appl. No. 13/296,182, dated May 8, 2014. |
| Notice of Allowance for U.S. Appl. No. 13/843,192, dated Aug. 10, 2016. |
| Office Action (Final Rejection) dated May 5, 2022 for U.S. Appl. No. 17/080,808 (pp. 1-10). |
| Office Action (Non-Final Rejection) dated Sep. 9, 2022 for U.S. Appl. No. 17/080,808 (pp. 1-11). |
| Office Action (Notice of Allowance and Fees Due (PTOL-85) dated Mar. 9, 2023 for U.S. Appl. No. 17/080,808 (pp. 1-5). |
| Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Mar. 23, 2023 for U.S. Appl. No. 17/080,808 (pp. 1-2). |
| Number | Date | Country | |
|---|---|---|---|
| 20210005047 A1 | Jan 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13801256 | Mar 2013 | US |
| Child | 15480295 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14518909 | Oct 2014 | US |
| Child | 16559553 | US | |
| Parent | 12797610 | Jun 2010 | US |
| Child | 13801256 | US | |
| Parent | 12617717 | Nov 2009 | US |
| Child | 14518909 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16559553 | Sep 2019 | US |
| Child | 17020761 | US | |
| Parent | 15480295 | Apr 2017 | US |
| Child | 16559553 | US |
