Patent Grant
10878662
The present disclosure relates generally to the field of gaming systems, and more particularly to preserving or saving game state data for bonus games in gaming machines.
In gaming machines, an award is based on the player obtaining a winning symbol or symbol combination and on the amount of the wager (e.g., the higher the wager, the higher the award). Generally, symbols or symbol combinations that are less likely to occur provide higher awards. Secondary or bonus games usually provide an additional award to the player.
Secondary or bonus games usually do not require an additional wager by the player to be activated and are generally activated by a triggering symbol or a triggering symbol combination in the primary or base game. For instance, bonus symbols occurring in specific patterns on reels of a slot machine may trigger a secondary bonus game.
Certain awards may also be available to multiple gaming machines or groups of gaming machines, such as progressive awards. In one form, a progressive award is an award amount that includes an initial amount funded by a casino and an additional amount funded through a portion of each wager made on the progressive award associated with the gaming machine. For example, one percent of each wager on the primary game of the gaming machine may be allocated to the progressive award or progressive award fund.
Certain types of game play data from gaming machines are often stored in gaming machines such as games won, credits remaining, prizes paid out. Such data may be necessary to calculate revenue and profits, to calculate a machine's hold percentage, reconcile accounting, and to address disputes that players may have with a casino over whether or not a winning combination occurred, the amount of payout due, and the like. Further, casino operators and/or gaming regulators may sometime need the same or related information for other reasons such as examining the sequence of events prior to a malfunction, verifying the electronic “signature” of software and/or firmware; reviewing the complete history of past games, and the like.
Among the types of commonly preserved data is so-called “critical data” or “critical game information,” which must be maintained by casinos. Such data as game state, credits bet, number of lines bet, credits remain, random number generator results, number of games played, and the like may be stored as simple text and/or graphics inside the slot machine. In some cases, entire frames of video data may be captured and stored. Gaming regulators, such as the Nevada Gaming Commission, may require that gaming machines save critical data for a certain length of time or a set number of games before allowing older critical data to be overwritten or purged from a gaming machine or network server. To this end, gaming machine manufacturers sometimes store such data in battery-backed non-volatile random access memory. This allows critical data to be preserved even in the event of a loss of primary power, during transport or relocation, or while the machine is intentionally turned off for service.
In the recent years, casino games where multiple players sharing a bonus game was also introduced. Typically, five to eight slot machines surround a shared bonus screen. Occasionally, when the bonus game is triggered, and one or more players may optionally participate in the bonus game. However, the bonus game lasts for only a few seconds, and the passive player(s) do not interact with the bonus game. Without interaction with the bonus game, without interaction between players, and with the brief nature of the group bonus game and the small number of players in a group participating simultaneously, the group bonus game is the same as the single player game, and the critical data is stored locally at the slot machine.
A system, apparatus, and method for preserving persistent bonus game state data for an asynchronous persistent group bonus game are discussed. The system may have a plurality of gaming machines configured to communicate with at least one network server through a network, which allows players to play the asynchronous persistent group bonus game. The asynchronous persistent group bonus game may last for any period of time and players can enter, pause and exit the bonus game asynchronously. Persistent bonus game state data such as player's game states and history, team's state and history, player relationships, player conversations, transactions between players or teams, assets collected, local game environments, global game state, game accounting data, and the like, may be modified and saved on one or more network servers, or alternatively on one or more slot machines in a peer-to-peer distributed storage manner. This allows the persistent bonus game state and other data to be recalled when needed, such as when a player plays another individual bonus game session in the asynchronous persistent group bonus game. The triggering events that cause the saving of the asynchronous persistent group bonus game data may be any change in the data themselves, the end of the bonus session for each player, or any other conditions depending on the game or jurisdictional requirements. When a player drops out of the asynchronous persistent group bonus game, or when the asynchronous persistent group bonus game terminates, any credits or items the player has collected may be converted and redeemed for monetary, non-monetary prizes, and/or roll over to equivalent features in another group game.
In a first embodiment, a system for preserving persistent bonus game state and other data for an asynchronous persistent group bonus game is described. The system includes a plurality of gaming machines associated with the asynchronous persistent group bonus game. Each of the plurality of gaming machines includes at least one processor, at least one input device, at least one display, and at least one local non-volatile memory. The local non-volatile memory may be configured to store a plurality of instructions and data. The at least one processor may execute the plurality of instructions to operate with the at least one display and the at least one input device. This enables a player to play a primary game of chance upon receipt of a wager. The system also includes at least one network server having at least one processor and at least one non-volatile memory. The at least one processor may be configured to communicate with each of the plurality of gaming machines via a network. The at least one network server may determine whether a bonus game session is triggered on any of the plurality of gaming machines. If a bonus game session is triggered, the at least one network server may cause the asynchronous persistent group bonus game to be displayed for any gaming machine that has triggered the bonus game session. The network server will also determine whether the player is a new player to the asynchronous persistent group bonus game, create new player record in the game database, modify the persistent bonus game state data when an event occurs in the asynchronous persistent group bonus game, and periodically save the persistent bonus game state data (representative of all individual players' progress) on the at least one non-volatile memory.
In another embodiment, a method for preserving persistent bonus game state and other data for an asynchronous persistent group bonus game on at least one network server configured to communicate with a plurality of gaming machines is described. The plurality of gaming machines may be configured to receive a wager from a player to play a primary game of chance. The method includes receiving a request to play the primary game of chance and determining if a bonus game session is triggered. The triggering of the bonus game session may cause persistent bonus game state data for an asynchronous persistent group bonus game to be recalled from at least one non-volatile memory on at least one network server. The at least one network server may receive an input to use at least one bonus game play asset in the asynchronous persistent group bonus game during the bonus game session, to track progress the player's progress, and to update the persistent bonus game state data on the at least one network server, and determine whether a bonus ending event has occurred to end the bonus game session for the player. When a bonus ending event has occurred for the player, at least one persistent bonus player data may be saved on the at least one non-volatile memory on the at least one network server.
In yet another embodiment, a method for preserving persistent bonus game state and other data for an asynchronous persistent group bonus game on at least one network server configured to communicate with a plurality of gaming machines is described. The plurality of gaming machines may be configured to receive a wager from a player to play a primary game of chance. The method includes operating an asynchronous persistent group bonus game from at least one network server upon receipt of a request from at least one of the plurality of gaming machines to play the asynchronous persistent group bonus game. The method further includes displaying the asynchronous persistent group bonus game on a display visible to the player or group of players, detecting an event in the asynchronous persistent group bonus game that modifies the persistent bonus game state and other data for an asynchronous persistent group bonus game, and periodically saving the persistent bonus game state and other data on at least one non-volatile memory stored on the at least one network server.
In yet another embodiment, a method for preserving the persistent bonus game state and other data for an asynchronous persistent group bonus game are collected and stored in a distributed manner on a peer-to-peer storage network. In a peer-to-peer storage network, data may be distributed among member nodes instead of concentrated on a server. Such a distributed storage system is highly available, scalable, has redundant capability, and thus can avoid the single-point-of-failure issue associated with a client/server network. The method further includes displaying the asynchronous persistent group bonus game on a display visible to the player or group of players, detecting events in the asynchronous persistent group bonus game that modifies the persistent bonus game state and other data for an asynchronous persistent group bonus game, and periodically saving the persistent bonus game state and other data on at least one non-volatile memory stored on the at least one slot machine in a peer-to-peer storage network.
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:
Embodiments are described herein in the context of preserving game state data for asynchronous persistent group bonus games. 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.
A system, apparatus, and method for preserving persistent bonus game state and other data (e.g. player account data) for an asynchronous persistent group bonus game are discussed. The system may have a plurality of gaming machines configured to communicate with at least one network server through a network, which allows players to play the asynchronous persistent group bonus game. The asynchronous persistent group bonus game may last for any period of time and players can enter and exit the bonus game asynchronously. Persistent bonus game state data (e.g. player's primary and bonus game states and history, team's states and history, player relationships, player conversations, transactions between players or teams, assets collected, local game environments, global game state, game accounting data, and the like) and other data may be modified and saved on the at least one network server when an event occurs in the asynchronous persistent group bonus game, allowing the persistent bonus game state and other data to be recalled when needed, such as when a player resumes play in the asynchronous persistent group bonus game. The triggering events that cause the saving of the data may be any change in the data themselves, or the end of the bonus session for each player, or other conditions depending on the game or jurisdictional requirements. When a player drops out of the asynchronous persistent group bonus game, or when the asynchronous persistent group bonus game terminates, any credits or items the player has collected may be converted and redeemed for monetary, non-monetary prizes, and/or used as rollover credits to play a game of chance on another gaming machine.
A gaming machine can be a fixed gaming machine such as a slot machine, an electronic table with multiple gaming stations, or a wireless mobile equivalent device such as a tablet computer or a smart phone.
The gaming machine 100 may have a player interface to play the primary game of chance. In the embodiment illustrated in
The gaming machine 100 may also have a TITO (Ticket In, Ticket Out) system. TITO uses tickets encoded with monetary amounts, which can be converted into credits to be played in the gaming machine 100 when inserted into the gaming machine 100. The gaming machine 100 may have a bill acceptor 116 configured to receive the tickets. The gaming machine 100 may also have a ticket printer 124 configured to print out similar tickets encoded with the amount of credits remaining on the gaming machine 100 when the player desires to no longer play the gaming machine 100 and cash out.
The bill acceptor 116 may also be configured to receive currency, for example paper bills. The gaming machine 100 may also have a mechanism to accept currency in other forms such as coins, vouchers, smart cards, electronic funds, and the like. The currency can then be converted into credits to be played on the gaming machine 100. The gaming machine 100 may have a credit dispenser 120 where the credits on the gaming machine 100 can be cashed out when the player desires to no longer play the gaming machine 100.
The gaming machine 100 may have a player tracking device 118 configured to receive a player loyalty card. Casinos may issue players a player loyalty card for player tracking and rewarding purposes. The player loyalty card may be associated with a player account. Player account data may be stored on a network server, which may be on a network database server configured to communicate with the gaming machines in the casino. The network may be a client-server network, a peer-to-peer network, a wired or wireless network, a wide area network (WAN), a local area network (LAN), or any other type of network. The player may insert his or her player loyalty card into the player tracking device 118 to log into the player's account, as further discussed below with reference to
The gaming machine 100 may have a secondary display 108 which may display information about an asynchronous persistent group bonus game separate from the primary game of chance. The asynchronous persistent group bonus game may be a bonus game triggered by an outcome in the primary game of chance, randomly triggered independent of the primary game, or by any other triggering event. The secondary display 108 may display bonus game environment 102 for the asynchronous persistent group bonus game. The secondary display 108 may also display bonus game information 106. The bonus game information 106 may be information such as scores, leader boards, rankings, team progress, statistics, messages, or any other information related to the asynchronous persistent group bonus game.
The bonus game environment 102 may have avatars 104a, 104b, 104n (where n is an integer). The avatars 104a-n may be graphical representations of each player or team that is participating in the group bonus game. For example, the avatars 104a-n may graphically depict characters, vehicles, boats or other images used to play the bonus game. In some embodiments, players may be allowed to select an avatar they wish to use in the bonus game environment 102.
In one embodiment, multiple players who each play a primary game of chance, on different gaming machines 100, may form a team and work toward an overall team goal in the asynchronous persistent group bonus game. Having an overall team goal may promote competition between teams and collaboration or camaraderie between team members, as team members strive to reach the overall team goal together. This may enhance the enjoyment of the players in playing the asynchronous persistent group bonus game, which may also increase the amounts the player decides to wager. It may also provide a social environment where friends can play with or against each other to augment their gaming experience.
In one embodiment, players may be prompted to create a new team, join an existing team, or be randomly assigned to a team. In another embodiment, a team may consist of only one player. Teams may or may not be competing with each other, depending on the game design. When not competing, team members collaborate together to achieve one or more common goals such as a total score, catching a predetermined pound of fish, or any other goals determined by the teams and/or game type. When competing, teams may be balanced such that competition between teams is fair. If the teams were not balanced, all players might choose to be a part of the same team and there would be no competition against another team. For example, if one team has only five members and another team has 20 members, the team with 20 members might have a better chance of accomplishing the overall team goal, which would decrease the enjoyment of players on the smaller team. Thus, a new player may be prompted to join the team with five members as opposed to the team with 20 members. By ensuring that teams have comparable numbers of members, players may feel that they have a more equal chance of attaining the overall group goal. In one embodiment, balancing the teams may be accomplished by allowing players to only join a team with the fewest number of members. In another embodiment, factors such as the level of experience a player has (e.g. rank), tools a player has access to, previous teams the player has played on, and the like make be used to balance the teams. More complex formulas with appropriate weights, statistics, and probabilities are assigned to each factor so that the aggregate team's capability is balanced to ensure a level playing field for all participating teams. Other methods to balance the teams are also possible depending on the design of the games and the associated rules.
In another embodiment, a player may prefer to play in the same group game environment, but not participate with a group or team. Thus, the group or team may be formed with 1 person and no load balancing required. The solo player keeps all the wins she is entitled to. However, the possibility of getting additional prizes when a group achieves a bonus is not available. Thus, a hybrid game environment where single players and teams can simultaneously participate can accommodate every player's preference, resulting in higher earnings for the game.
The asynchronous persistent group bonus game may last for a longer period of time than traditional bonus games. For example, the asynchronous persistent group bonus game may continue for several minutes, hours, weeks, months or in perpetuity as designed by the game developer and configured by the game operators. The asynchronous persistent group bonus game may be played asynchronously, i.e. players may not be playing with all of the other members of their team simultaneously. For example, player 1104a may enter the bonus game environment 102 in the morning, but his friend (player 2104b) may not enter the bonus game environment 102 until the evening, even though both may be on the same team. On another example, player 2104b may enter the bonus game environment 102 while player 1104a is already playing his bonus game session.
The asynchronous persistent group game data may comprise the global game environment data, individual game player data, team data, player and team relationship data, historical data, and any other relevant data needed to maintain the integrity of the asynchronous persistent group game environment.
Asynchronous persistent group game data can be partitioned into global and local game states since the asynchronous persistent group game can take place at multiple casino locations, in different cities and states, with multiple sets of regulations. Global game data states are states and data that involve the overall world game environment such as the various groups participating in the asynchronous persistent group games, the group's identification, each location of the players on the asynchronous persistent group game, individual team members, team scores, team goals and progresses, prizes won, prizes remaining, leaderboard information, global game time and calendar, time elapsed, game stage (start, on going, end), and any other global game data. Local game states and data involves the local data associated with nearby players at the same casino, at the same game carousel, or even at the same virtual location (e.g. players grouped to be at the same virtual location but not the same physical location). Examples of local asynchronous persistent group game states and data are date and time of the local bonus game, gaming machine identification, player identification, a player's accumulated tools, local viewport (versus a global map) size and position, virtual location of participating players within the asynchronous persistent group game world, absolute location of the gaming machine and the controlling jurisdiction, nearby activities (virtual or absolute), last known set of good data for each players, and the like. The global and local asynchronous persistent group game states and data are used to maintain world and players/teams statuses, store players and teams progresses, keep track of game accountings, help with recalling of games to resolve a dispute, help a player review her recent or past activities, provide a method for disaster recovery of game data, and the like.
In one embodiment, local asynchronous persistent group bonus data may be collected and stored temporarily at a local server. Periodically, the data may pushed to a global asynchronous persistent group bonus game server to update the global game states. Similarly, global asynchronous persistent group bonus game data, relevant to the local server, may be pulled from the global asynchronous persistent group bonus game server periodically to update local machines of changes (e.g. leaderboard information, jackpot status, prizes won, and the like). In between the data updates, the local server monitors, interacts, serves up data, save local game states, and generally controls the gaming machines assigned to it. Such a system architecture minimizes network activities generated by the myriads of micro-transactions that are not relevant to the global bonus game states such as when a player moves two yards in the West direction. It also allows the asynchronous persistent group bonus game to proceed locally even if communication is temporarily cut off from the global asynchronous persistent group bonus game server.
In another embodiment, global and local asynchronous persistent group bonus data are stored at a central server. Although this generates more data traffic on the network, such an architecture is easy to maintain and all participating games are assured to have the most updated game states. This embodiment may work for certain game types, such as real-time car races.
In another embodiment, global and local asynchronous persistent group bonus data are stored in a hybrid peer-to-peer distributed file storage system. With this approach, each gaming machine (i.e. node) can act as a client requesting data or a server sending data to a requesting machine. Additionally, designated machines (i.e. nodes) can be equipped with software to be both a global asynchronous persistent group bonus data server and a local asynchronous persistent group bonus data server. Other gaming machines (i.e. nodes) may store primarily local asynchronous persistent group bonus data, periodically push the local data to the designated global/local asynchronous persistent bonus group data nodes, and pull global asynchronous persistent bonus group data from the designated nodes as needed. Since each designated global/local asynchronous persistent group bonus data server node may receive different updates from nearby nodes, the designated global/local nodes may periodically communicate with each other separately at the application level to keep their databases in synchronization with each other. Such a hybrid peer-to-peer distributed storage architecture provides data to other nodes in a fast, resilient, scalable, load balanced, and asynchronous persistent manner. For instance, a network of fixed gaming machines configured in this manner can scale up, on demand, to include new mobile gaming terminals such as the mobile smart phones. The distributed file storage approach also keeps the costs low while minimizing communication bandwidth across the network.
The community secondary display 208 may display the bonus game environment 202 for the asynchronous persistent group bonus game. The bonus game environment 202 may have avatars 204a-n individual players may use to play the asynchronous persistent group bonus game. In the embodiment illustrated in
Once a bonus game session is triggered on the gaming machine 100, the asynchronous persistent group bonus game begins and may be displayed on the secondary display 108 (
The asynchronous persistent group bonus game may be a fishing game where the bonus game environment may be a pond 220 and the avatars 204a-n may be fishermen. Each player may have bonus assets 226 to use when playing the bonus game. Such assets may be displayed on a first portion 234 of the community display 218 or on the secondary display 108 (
Each avatar 204a-n may be labeled by team 222 and/or the player's name 224. However, this is not intended to be limiting as each player may be identified by any other means, such as the color of the avatar, use of other identifiers, such as flags, and the like. Furthermore, the bonus game environment and the avatars 204a-n can have any design or any characteristics as needed for a player to play the asynchronous persistent group bonus game.
The player may select from a row boat 238a, ski boat 238b, or a racing boat 238c. Each boat may allow the player the move around the pond faster to provide a better chance of catching fish. The player may also select to use a worm 240a, shrimp 240b, or a minnow 240c as a lure. For a fishing rod, the player may elect to use the basic fishing rod 242a, the super rod 242b, or the professional rod 242c. The type of lure and/or fishing rod selected may determine the type and/or weight of fish caught as well as the speed at which the player catches the fish. By using superior tools or having better or more experience than other participating players, the player may have a better probability that a winning random number is drawn. For instance, the player may be assigned a number ranging between 1-5 when a random number is drawn between 1-100 by a random number generator, compared to other less experienced players who may be assigned a number ranging between 1-3.
In one embodiment, for each asset, the player may elect to choose the quantity 252 desired. Additionally, the amount of credits 254 required to obtain each asset may be displayed.
As the asynchronous persistent group bonus game is played, events may occur that can change the state of the bonus game environment 102. Each player may move their fishermen avatar around the pond 220 and attempt to catch fish using bonus game play assets 226. For example, fish might be caught while playing in the bonus game environment 102, boats might be moved around the pond to different locations, a player may have entered the pond or left the pond, a team may have completed its objective, scores and game statistics may be updated, or any other gaming related events. As these events occur, the new state of the bonus game environment 102 may be saved to the network server, a local server, a slot machine, or any combination of these. The asynchronous persistent group bonus game displays are updated so that new players coming into the bonus game environment 102 will see the current state of the asynchronous persistent group bonus game displayed and begin their new bonus game session in the current state of the bonus game environment 102. While the network server may usually be a bonus server, a player tracking server or any other local or network server may also be used.
The asynchronous persistent group bonus game may terminate at any predefined event, such as at a certain time (i.e., one week tournament), a certain event (i.e., top 10 teams completed their objectives or goals), or the asynchronous persistent group bonus game may continue perpetually, depending on the design of the game.
Throughout the asynchronous persistent group bonus game, the global game environment can be saved so that entering players will be in the most current state of the asynchronous persistent group bonus game. Some example of global environment data that may be saved periodically (the saving may occur based upon a time snap shot, an event(s), or both) are: 1) game time stamp; 2) rules in effect at the actual (physical) casino; 3) active player identification (ID) and/or active team's ID; 4) global map of players, their virtual locations, and their activities; 5) active rules set for the virtual location and time; 6) current scores and prizes accumulated by each player and their composite teams; 7) game state (e.g. start, end, paused, running); 8) indication of the status of the leaders, individuals and/or teams; 9) prize distribution parameters (i.e., where, how much, what it takes to reveal a prize); 10) relationships between teams (friendly, hostile, indifference); or any other global game environment data.
In addition to the global game state data, the micro state data of each player can also be saved or stored. Each player can have an account recorded in the asynchronous persistent group bonus game database, as well as the player's historical activities such as time, date, location, cumulated amount of time spent in the asynchronous persistent group bonus game, prizes won, current score, assets/tools remained, participation state (e.g. enter, exit, pause, drop out, and the like), and the like.
In another embodiment, an asynchronous persistent group bonus game may have an overall team goal each team is to achieve. For example, the team goal might be to catch a certain amount of fish, such as 300 pounds of fish. Each team would complete to be the first team to catch 300 pounds of fish. This is only one example of an overall team goal, as the overall team goal can vary depending on the characteristics of the asynchronous persistent group bonus game. The first team to complete the overall team goal would win the asynchronous persistent group bonus game, and an overall prize can be distributed among all the members of the winning team. In addition to the overall prize, each player may also win an individual prize(s) based on the amount of fish the player caught.
Within the asynchronous persistent group bonus game environment, multiple tournaments, that are independent of each other, may occur concurrently. Thus, the termination of one local fishing tournament between five local teams does not terminate all the other parallel tournaments. The global game termination is often set by the casino operators or game designers to take place at a pre-defined or certain time, when large prizes have been exhausted, when the progressive prizes have been won, or any other criteria.
The player's activities in the asynchronous persistent group bonus game during the bonus game session may be applied towards the overall progress of the player's team in reaching the overall team goal of the asynchronous persistent group bonus game. The player's individual bonus gaming session may end prior to the termination of the asynchronous persistent group bonus game such that the player may play several individual bonus gaming sessions in the asynchronous persistent group bonus game before the asynchronous persistent group bonus game terminates. Additionally, the player may enter and exit the asynchronous persistent group bonus game independent of and without regard to whether other players are playing or exiting or entering the asynchronous persistent group bonus game.
The asynchronous persistent group bonus game may continue to run until an overall team goal is reached by one or more of the teams, regardless of the number of players playing the asynchronous persistent group bonus game at any one time. In another embodiment, the asynchronous persistent group bonus game may continue to run until a timer has expired, or some other ending condition or event has occurred.
Each of the at least one network servers 302 in the networked multi-player system 300 illustrated in
The non-volatile memory 306 at the network server 302 may store various types of game state data to allow asynchronousity and the persistence nature of the game over a period of time. Saving game state data on the network server 302 may allow the casino to restore either a primary game of chance or an asynchronous persistent group bonus game to the state it was in prior to a power loss or malfunction. For example, if a player is playing a video poker game when the power goes out, the casino can resume the video poker game in the exact state it was in immediately prior to the loss of power, with the same cards displayed, the same amount of credits in the player's account, and the same wagered amount. The player can then continue his game as if the power loss never happened. The network server 302 may also store prior versions of the game state data for a predetermined period of time to assist in verification of previous game outcomes. For example, if a player claims that he or she won a prize on a gaming machine but was not awarded his or her credits, the casino may be able to review the game state data from the network server 302 and confirm or disprove the player's claim. Additionally, game state data may need to be saved and retained for a predetermined period of time to comply with certain local regulations that casinos and other gaming operators must follow. Furthermore, saving game state data allows a player to enter an asynchronous persistent group bonus game at its current game state, as discussed above in Example 1.
Game state data stored for these purposes may include several different components, such as primary player data, persistent bonus player data, persistent bonus group data, and persistent bonus world data. The primary player data may include information and statistics about a player's play of a primary game of chance. For example, player tracking data about the type of games the player likes to play, denomination amount, time between plays, and any other player tracking and/or account data may be stored as part of primary player data.
Another component of the game state data that may be saved may be persistent bonus player data. Persistent bonus player data may be information about each player's play in the asynchronous persistent group bonus game as well as the relationship (e.g. friends, foes, acquaintances of the player with others inside or outside of the team, and the like). Referring back to Example 1, such information might include the amount of fish caught, the bonus game play assets acquired and used, the last location of the player's boat, or any other data or statistic about the player's play in the asynchronous persistent group bonus game.
The persistent bonus player data may be saved in a bonus game database 312. The persistent bonus player data may be recalled from the bonus game database, for example, when the player triggers another bonus game session while playing the primary game of chance. This allows the player to start the bonus game session with all of the bonus game play assets and/or data from the last previously saved bonus game session in the asynchronous persistent group bonus game.
Another component of the game state data that is saved may be persistent bonus group data. Persistent bonus group data may include data about the current state of at least one group of players on a team. For example, players may join together to form teams to play toward an overall group goal. In another example, groups may challenge one another in a tournament environment. In one embodiment, the persistent bonus group data may include a roster of the team members on the team, the team's progress toward the overall group goal, the amount of time that the team has been playing the asynchronous persistent group bonus game, and any other information that is desired to be saved about the team.
Interspersed among teams may be individual players (e.g. a team or group having 1 player) who chose not to join any team, but still want to participate and possibly win the grand prize without having to share or split the winnings with other players.
Another component of the game state data that may be saved on the network server 302 may be persistent bonus world data. The persistent bonus world data may include information about the asynchronous persistent bonus game environment. For example, in Example 1 discussed above, the persistent bonus world data may be information about the location of fish, the overall team scores, start time, end time, pay tables, probabilities of catching fish in certain locations on the pond, total prizes already paid out, and any other information that is desired to be saved about the overall asynchronous persistent bonus game environment.
A plurality of gaming machines 410a-n may be configured to communicate with the network server 402 via the network 408. Each of the plurality of gaming machines 410a-n may have a local non-volatile memory 412a-n configured to communicate with a processor 414a-n. The processor 414a-n may also be configured to communicate with at least one input/output device 416a-n and at least one display device 418a-n.
The local non-volatile memory 412a-n may store data related to the primary game of chance played on the respective gaming machine 410a-n, such as object code, game history, pay tables, local game states, global game states and any other gaming data. In one embodiment, a decentralized peer-to-peer storage environment may be used to store data. Each gaming node in the decentralized peer-to-peer storage environment may be configured to store at least a portion of the total asynchronous persistent game environment data. The peer-to-peer distributed storage system can have a self-organizing characteristic as storage nodes can come and go and the peer-to-peer storage network adapts accordingly. In an asynchronous persistent group bonus game environment, the robustness of a distributed storage system is a viable implementation that will allow players to continue to play even if a network disruption occurred. Various known look-up algorithms can be implemented to allow data to be retrieved by any node regardless of where the data were stored. The technical paper “A Survey of Peer to Peer Storage Techniques for Distributed File Systems” by the Department of Computer Science of the University of Illinois, Urbana Champaign, which is incorporate herein by reference in its entirety for all purposes, discussed these methods in details. The processor 414a-n may use software or may be programmed to run the operation of each of the plurality of gaming machines 410a-n, including operation of the primary game of chance.
The at least one input/output device 416a-n may be any device that can accept commands from a player (input device) or provides feedback to the player (output device). For example, the buttons 112, the microphone (not shown), and the lever 114 (
Each of the plurality of gaming machines 522a-n may have a processor 526a-n. Each of the plurality of gaming machines 522a-n may also have a local non-volatile memory 524a-n configured to communicate with the processor 526a-n. Each of the plurality of gaming machines 522a-n may also have an input/output device 528a-n and/or a display device 530a-n configured to communicate with the processor 526a-n. A locator device or location determination device 532a-n may also be configured to communicate with the processor 526a-n. The locator device 532a-n may determine the general physical geographic location of the casino, or the specific location on the casino floor of each of the plurality of gaming machines 522a-n. Location information can be used to enforce local jurisdictional requirements (e.g., minimum payout percentage, bet size, and the like), or to modify the asynchronous persistent group bonus game (e.g., game rules, localization features for the city, the casino brands, prizes, and the like). In one embodiment, a Global Positioning System (GPS), a cellular towers triangulation or trilateration system, a WiMax triangulation or trilateration system, a WiFi triangulation or trilateration system, or some combination of these triangulation and trilateration system may be used. In another embodiment, IP address analysis may be used. In still other embodiments, the location determination device 532a-n may use any known method, system, or device to determine the physical location of each of the plurality of gaming machines 522a-n (some of which may also be gaming machine mobile devices such as smart phones), such as a nearby access point, signal strength analysis, time difference of arrival, or other RF location methods.
The gaming server 534 may store data or information related to the primary game of chance. For example, the gaming server 534 may store the object code for running a primary game of chance on a gaming machine. The gaming server 534 may have a processor 538 and a memory 536 configured to communicate with the processor 538. The memory 536 may be any type of memory, but is illustrated as a non-volatile memory. The processor 538 on the gaming server 534 may be configured to run the operation of the primary game of chance. The processor 538 may receive requests and/or commands from any of the plurality of gaming machines 522a-n, execute such requests or commands, and save game state data on the non-volatile memory 536. The gaming server 534 may also be configured to download a plurality of primary games to any of the plurality of gaming machines 522a-n via network 520. This may allow a player to choose from a variety of primary games of chance to be played on each of the plurality of gaming machines 522a-n.
The bonus server 502 may execute and store data or information related to the asynchronous persistent group bonus game. In one embodiment, the bonus server 502 may be configured to store game state data specific to the asynchronous persistent group bonus game. Such game state data may include persistent bonus player data, persistent bonus group data, and/or persistent bonus world data. The bonus server 502 may have a processor 506 configured to communicate with a memory 504. The memory 504 may be any type of memory, although illustrated as a non-volatile memory. The processor 506 on the bonus server 502 may be configured to run the operation of the asynchronous persistent group bonus game. The processor 506 may receive requests and/or commands from any of the plurality of gaming machines 522a-n, update the bonus gaming environment 102 based on the commands, and save or update game state data on the non-volatile memory 504 and any active local or global environment displays.
The player tracking server 508 may store data or information related to player accounts. In one embodiment, the player tracking server 508 may be specialized to store data about each individual player's play in a primary game of chance and/or the asynchronous persistent group bonus game. The player tracking server 508 may have a processor 512 configured to communicate with a memory 510. The memory 510 may be any type of memory, although illustrated as a non-volatile memory. The player tracking server 508 may identify individual players when players insert their player loyalty cards into a gaming machine, such as through the use of a player tracking device 118 (
In one embodiment, a location tracking server 514 may be used to determine the location of each of the gaming machines 522a-n. A game's characteristic may varied due to its location. The location tracking server 514 may be used in addition to the location determination device 532a-n in each of the gaming machines 522a-n or may be used if there is no location determination device 532a-n in the gaming machines 522a-n. Once the location of each of the gaming machines 522a-n is determined, the information may be transmitted via the network 520 to the gaming server 534 and/or the bonus server 502. The gaming server 534 and/or the bonus server 502 may then configure the primary game of chance and/or the asynchronous persistent group bonus game to comply with rules, laws, or regulations of local government jurisdictions, local game rules created by the casino operator, themes created by the game designer, localization features associated with the city, casino brands, and the like, based upon the location of each of the gaming machines 522a-n.
The location tracking server 514 may have a processor 518 configured to communicate with a memory 516. The memory 516 may be any type of memory, although illustrated as a non-volatile memory. The physical location of each of the plurality of gaming machines 522a-n may be stored in the memory 516 at the location tracking server 514.
A bonus game session may be a bonus game played by a player in the asynchronous persistent group bonus game. In one embodiment, the bonus game session may be played for a pre-determined amount of time and/or until the player meets an objective of the bonus game session. For example, an objective of the game described in Example 1 discussed above may be once the player catches a fish. In another embodiment, the amount of time the player may play the bonus game session may be based on the player's score in the primary game of chance. The time a player is allowed to play the bonus game session may be pre-determined, such as for two minutes, or based on any other criteria.
If a bonus game session has not been triggered at 606, and a wager is received to play a primary game of chance on the gaming machine at 602, another primary game of chance is operated on the gaming machine at 604. If the bonus game session has been triggered for the player at 606, then a determination of whether the player is new to the asynchronous persistent group bonus game at 608.
To determine whether the player is new to the asynchronous persistent group bonus game at 608, in one embodiment, the player might be asked to input a player identification number or insert their player loyalty card into the player tracking device on the gaming machine if the player has not previously done so. A player tracking server or bonus server may check player game data stored in memory to determine if the player has previously played the asynchronous persistent group bonus game for the asynchronous persistent group bonus game session.
Referring now to
The player account data may then be saved on a memory of the bonus server and/or player tracking device at 612. The player account data may be any information, including, but not limited to, a player identification, player password, contact information for the player, associating the player with a team, wager amount, and other data.
Referring back to
An input may be received to use at least one bonus game play asset in the asynchronous persistent group bonus game at 616. A bonus game play asset may be any asset or tool that a player may utilize in playing the asynchronous persistent group bonus game. Bonus game play assets may either be won in the primary game of chance, purchased with credits from the virtual bonus store, and/or obtained while playing the bonus game session. Assets can also be transferred from another player. In the example described above in Example 1, a bonus game play asset may include a fishing rod, boat, a lure, or any other item(s) to assist a player in catching more and bigger fish in the asynchronous persistent group bonus game. Bonus game play assets may also be implemented as a default set of assets so all players can be on an equal footing on the play field. In case of a default set of assets, a request to use a tool is not needed.
At 617, if the bonus game play assets were not a default set, a player's request to use a certain asset or tool is executed. The bonus game session may be operated at 618. The bonus game session may be displayed on a display of the local gaming machine and/or on a community display. The bonus game session continues until the bonus session ends at 620. In one embodiment, the bonus game session may end after a predetermined amount of time has elapsed. In another embodiment, the bonus game session ends when the player or team reaches a team goal. In still another embodiment, the bonus game session may end when any other bonus ending event occurs, such as the player catching a fish or completing a task. Once the bonus game session ends for the player at 620, the persistent bonus game state and other data may be updated at 622. The bonus game state data may be updated in the bonus server, player tracking server, and/or on the gaming machine itself. The bonus game state data may then be saved to the non-volatile memory on the bonus server at 624. As discussed previously, the triggering events that cause the saving of the data may be any change in the data themselves, end of the bonus session for each player, or any other conditions depending on the game or jurisdictional requirements.
In another embodiment, the game state data may also be saved to the memory on the player tracking server, the gaming machine itself, or any other network server. The persistent bonus game state and other data may include the persistent bonus player data, which may be updated with any new prizes the player has won while playing the asynchronous persistent group bonus game. Persistent bonus game state and other data may also include the persistent bonus group data, which may represent the current state of each team competing in the asynchronous persistent group bonus game, as well as the list of players associated with each team or group. Furthermore, the persistent bonus game state and other data may include persistent bonus world data that represents the current state of the asynchronous persistent group bonus game.
In the example discussed above in Example 1, the persistent bonus world data can include data such as total amount of fish caught by the players of each team, location of fish remaining to be caught (which may or may not be revealed to active players), and other data representing the operation of the asynchronous persistent group bonus game. All the data may be updated at 622 and saved at 624 after each individual bonus game session ends for each player. Thus, when another player enters the bonus game environment to play a bonus game session, the current state of the asynchronous persistent group bonus game may be up-to-date.
The asynchronous persistent group bonus game may be displayed on a display at 704. The asynchronous persistent group bonus game may be displayed on a community display and/or on a display of a gaming machine. In another embodiment, the display may occur on a plurality of game machines, in a synchronized manner.
An event in the asynchronous persistent group bonus game may be detected that modifies the persistent bonus game state and other data at 706. As discussed before, the triggering events that cause the saving of the data may be any change in the data themselves, the end of the bonus session for each player, or other conditions depending on the game or jurisdictional requirements. Since persistent bonus game state and other data may include data on each player, groups, their interactions, and the entire bonus world environment, any changes to the data may qualify as an event that modifies the persistent bonus game state and other data. For example, a new player may enter or exit the asynchronous persistent group bonus game, a player may be added to (or removed from) a group, or a goal or objective of the asynchronous persistent group bonus game may be attained. Other events may occur that modifies the persistent bonus game state and other data.
The bonus game state data may be saved at 708. In one embodiment, the bonus game state data may be saved each time an event is detected at 706. In another embodiment, the bonus game state data may be saved based upon a predetermined time limit, such as every five minutes. In yet another embodiment, the constant changes in the player's local game environment (such as moving from location to location) is accumulated in the local machine's nonvolatile memory. When a significant event occurs, such as when a player catches a fish, the accumulated data for the environment is uploaded to the server in a client-server network or to designated peer machines in a peer to peer storage network.
If an asynchronous persistent group bonus game termination event has not occurred at 710, the asynchronous persistent group bonus game may continue at 702. However, if an asynchronous persistent group bonus game termination event has occurred at 710, the asynchronous persistent group bonus game ends. There are multiple levels of termination. Termination may occur at the player's level, team level, tournament level, or at the global level. The termination event may be a predetermined amount of time has elapsed, a player or group has reached the overall group goal, or any other event that terminates the asynchronous persistent group bonus game. For example, the asynchronous persistent group bonus game may continue for three months, three weeks, or three days. In another example, as described in Example 1 above, the asynchronous persistent group bonus game may continue until a team has caught 300 pounds of fish. Once the asynchronous persistent group bonus game is terminated and saved, another asynchronous persistent group bonus game may automatically start.
The location of each of the plurality of gaming machines may be saved at 804. The location may be saved on a memory at a gaming server, a bonus server, a player tracking server, a location tracking server, or any other type of network server. In one embodiment, the location may also be save on a local game machine node of a peer to peer distributed storage network.
The saved location information may then be used to configure each of the plurality of gaming machines to comply with any applicable regulations and location-based game rules at 806 based on the determined location. For example, a state may have a $500 limit on the maximum amount of money a player can lose in any given day. Each gaming machine may then be configured to comply with the state law to, whether it be to play a primary game of chance or the asynchronous persistent group bonus game, refuse a player's wager to play additional games of chance after the player has lost $500 within a 24 hour period. In another example, the specific location of the gaming machine may cause the rules of the asynchronous persistent group bonus game to change, the game theme to change, localization features (e.g., city scape, casino brands) to be added or displayed on the gaming machine. For example, certain sections of the casino floor may be designated as a promotional zone where game machines are entitled to additional game benefits such as more powerful tools or additional prizes given out by 3rd party sponsors.
If the player was granted a persistent bonus award at 904, the persistent bonus award may be converted into at least one credit at 906. The player may use the credit to play additional primary games of chance, purchase additional bonus game assets, cash out the credits, or even rolling the credits over to another game.
The player's account data may then be updated at 908 and saved in a memory at 910. The player's account data may be saved on a memory on the bonus server, player tracking server, one or more gaming machines, and/or on a gaming server. The player account data may include information such as amount of credits, assets obtained from the bonus game session, or any other player gaming or account data.
If a persistent bonus award was not granted at 904, a determination is made whether the player elected to cash out at 912 and no longer play the game of chance on the gaming machine. If the player elected to cash out at 912, the credits may be redeemed or rollover the credits to another game at 914. The credits may be redeemed for cash or non-cash assets, such as entertainment shows, food, concierge services, or any other item. If the player does not elected to cash out at 912, the player may continue to play the primary game of chance at 916 on the gaming machine.
If the asynchronous persistent group bonus game ends at 1002, then a determination is made as to whether a team award is granted at 1004 for the team. If a team award is granted at 1004, the team award is distributed among each of the members of the team at 1008. If no team award is granted at 1004, the bonus award distribution phase may end.
The team award may be any award granted to a team at the conclusion of the asynchronous persistent group bonus game. For example, a team may be awarded a team award for being the first team to reach the overall team goal of the asynchronous persistent group bonus game. In Example 1, the team goal may be to catch 300 pounds of fish, and the first team to reach this goal may win the team award. In one embodiment, teams that come in second or third place, or any other rank, may also be awarded smaller award amounts. In other embodiments, team awards may also be awarded prior to the conclusion of the asynchronous persistent group bonus game upon certain event. For example, team awards may be obtained if a team member catches a rare fish, obtains a specific bonus game play asset, or any other criteria.
In another embodiment, any bonus game asset each team member acquired while playing the asynchronous persistent bonus game may be converted and added to the team award or to the individual player's distributed team award amount. For example, based on Example 1, if the team has three racing boats, the team award may be increased by a predetermined amount, such as $1,000.00. Alternatively, each player having the race boat may have an additional predetermined amount added to their distributed team amount, such as an additional $500.00.
The team award may be distributed among the members of the team at 1008 based on any criteria, such as, the proportional contribution of each team member towards the overall team goal, the amount of time played by each player, the amount of bonus game play assets accumulated by each player, randomly, or any other criteria.
Once the team award is distributed, each player's account data may be updated at 1010 and saved at 1012. The player account data may be saved on a memory at the gaming server, player tracking server, bonus server, gaming machine, or any other network server. The player's account data may include any information as discussed above.
There could be many collaboration games, competition games between teams, or individual games occurring simultaneously in the same asynchronous persistent bonus group game environment. Thus, a termination of one local competition tournament does not necessarily terminate the global asynchronous persistent group bonus game.
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 continuation of U.S. patent application Ser. No. 15/293,751, filed Oct. 14, 2016, and entitled “ASYNCHRONOUS PERSISTENT GROUP BONUS GAMES WITH PRESERVED GAME STATE DATA”, which is hereby incorporated herein by reference for all purposes, and which in turn is continuation of U.S. patent application Ser. No. 13/801,076, filed Mar. 13, 2013, and entitled “ASYNCHRONOUS PERSISTENT GROUP BONUS GAMES WITH PRESERVED GAME STATE DATA”, which is hereby incorporated herein by reference for all purposes, and which in turn is continuation of U.S. patent application Ser. No. 12/581,115, filed Oct. 17, 2009, and entitled “PRESERVING GAME STATE DATA FOR ASYNCHRONOUS PERSISTENT GROUP BONUS GAMES”, 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 et al. | Mar 2004 | B1 |
| 6719630 | Seelig et al. | Apr 2004 | B1 |
| 6749510 | Giobbi | 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 | Sep 2005 | B1 |
| 6955600 | Glavich et al. | Oct 2005 | B2 |
| 6971956 | Rowe et al. | Dec 2005 | B2 |
| 6984174 | Cannon et al. | Jan 2006 | B2 |
| 6997803 | LeMay et al. | Feb 2006 | B2 |
| 7018292 | Tracy et al. | Mar 2006 | B2 |
| 7032115 | Kashani | Apr 2006 | B2 |
| 7033276 | Walker et al. | Apr 2006 | B2 |
| 7035626 | Luciano | Apr 2006 | B1 |
| 7037195 | Schneider et al. | May 2006 | B2 |
| 7048628 | Schneider | May 2006 | B2 |
| 7048630 | Berg et al. | May 2006 | B2 |
| 7063617 | Brosnan et al. | Jun 2006 | B2 |
| 7076329 | Kolls | Jul 2006 | B1 |
| 7089264 | Guido et al. | Aug 2006 | B1 |
| 7094148 | Bearlocher et al. | Aug 2006 | B2 |
| 7105736 | Laakso | Sep 2006 | B2 |
| 7111141 | Nelson | Sep 2006 | B2 |
| 7144321 | Mayeroff | Dec 2006 | B2 |
| 7152783 | Charrin | Dec 2006 | B2 |
| 7169041 | Tessmer et al. | Jan 2007 | B2 |
| 7169052 | Beaulieu et al. | Jan 2007 | B2 |
| 7175523 | Gilmore et al. | Feb 2007 | B2 |
| 7181228 | Boesch | Feb 2007 | B2 |
| 7182690 | Giobbi et al. | Feb 2007 | B2 |
| 7198571 | LeMay | Apr 2007 | B2 |
| RE39644 | Alcorn et al. | May 2007 | E |
| 7217191 | Allen et al. | May 2007 | B2 |
| 7243104 | Bill | Jul 2007 | B2 |
| 7247098 | Bradford et al. | Jul 2007 | B1 |
| 7259718 | Patterson et al. | Aug 2007 | B2 |
| 7275989 | Moody | Oct 2007 | B2 |
| 7285047 | Gielb et al. | Oct 2007 | B2 |
| 7311608 | Danieli | Dec 2007 | B1 |
| 7314408 | Cannon et al. | Jan 2008 | B2 |
| 7316615 | Soltys et al. | Jan 2008 | B2 |
| 7316619 | Nelson | Jan 2008 | B2 |
| 7318775 | Brosnan et al. | Jan 2008 | B2 |
| 7326116 | O'Donovan et al. | Feb 2008 | B2 |
| 7330108 | Thomas | Feb 2008 | B2 |
| 7346358 | Wood et al. | Mar 2008 | B2 |
| 7355112 | Laakso | Apr 2008 | B2 |
| 7384338 | Rothschild et al. | Jun 2008 | B2 |
| 7387571 | Walker et al. | Jun 2008 | B2 |
| 7393278 | Gerson et al. | Jul 2008 | B2 |
| 7396990 | Lu et al. | Jul 2008 | B2 |
| 7415426 | Williams et al. | Aug 2008 | B2 |
| 7425177 | Rodgers et al. | Sep 2008 | B2 |
| 7427234 | Soltys et al. | Sep 2008 | B2 |
| 7427236 | Kaminkow et al. | Sep 2008 | B2 |
| 7427708 | Ohmura | Sep 2008 | B2 |
| 7431650 | Kessman | Oct 2008 | B2 |
| 7448949 | Kaminkow et al. | Nov 2008 | B2 |
| 7500913 | Baerlocher | Mar 2009 | B2 |
| 7510474 | Carter | Mar 2009 | B2 |
| 7513828 | Nguyen et al. | Apr 2009 | B2 |
| 7519838 | Suurballe | Apr 2009 | B1 |
| 7559838 | Walker et al. | Jul 2009 | B2 |
| 7563167 | Walker et al. | Jul 2009 | B2 |
| 7572183 | Olivas et al. | Aug 2009 | B2 |
| 7585222 | Muir | Sep 2009 | B2 |
| 7602298 | Thomas | Oct 2009 | B2 |
| 7607174 | Kashchenko et al. | Oct 2009 | B1 |
| 7611409 | Muir et al. | Nov 2009 | B2 |
| 7637810 | Amaitis et al. | Dec 2009 | B2 |
| 7644861 | Alderucci et al. | Jan 2010 | B2 |
| 7653757 | Fernald et al. | Jan 2010 | B1 |
| 7693306 | Huber | Apr 2010 | B2 |
| 7699703 | Muir et al. | Apr 2010 | B2 |
| 7722453 | Lark et al. | May 2010 | B2 |
| 7742996 | Kwan | Jun 2010 | B1 |
| 7758423 | Foster et al. | Jul 2010 | B2 |
| 7771271 | Walker et al. | Aug 2010 | B2 |
| 7780529 | Rowe et al. | Aug 2010 | B2 |
| 7780531 | Englman et al. | Aug 2010 | B2 |
| 7785192 | Canterbury et al. | Aug 2010 | B2 |
| 7811172 | Asher et al. | Oct 2010 | B2 |
| 7819749 | Fish | Oct 2010 | B1 |
| 7822688 | Labron | Oct 2010 | B2 |
| 7828652 | Nguyen et al. | Nov 2010 | B2 |
| 7828654 | Carter | Nov 2010 | B2 |
| 7828661 | Fish | Nov 2010 | B1 |
| 7850528 | Wells | Dec 2010 | B2 |
| 7874919 | Paulsen et al. | Jan 2011 | B2 |
| 7877798 | Saunders et al. | Jan 2011 | B2 |
| 7883413 | Paulsen | Feb 2011 | B2 |
| 7892097 | Muir et al. | Feb 2011 | B2 |
| 7909692 | Nguyen et al. | Mar 2011 | B2 |
| 7909699 | Parrott et al. | Mar 2011 | B2 |
| 7918728 | Nguyen et al. | Apr 2011 | B2 |
| 7927211 | Rowe et al. | Apr 2011 | B2 |
| 7927212 | Hedrick et al. | Apr 2011 | B2 |
| 7951008 | Wolf et al. | May 2011 | B2 |
| 8057298 | Nguyen et al. | Nov 2011 | B2 |
| 8057303 | Rasmussen | Nov 2011 | B2 |
| 8087988 | Nguyen et al. | Jan 2012 | B2 |
| 8117608 | Slettehaugh | Feb 2012 | B1 |
| 8133113 | Nguyen | Mar 2012 | B2 |
| 8182326 | Speers et al. | May 2012 | B2 |
| 8210927 | Hedrick | Jul 2012 | B2 |
| 8221245 | Walker | Jul 2012 | B2 |
| 8226459 | Barrett | Jul 2012 | B2 |
| 8226474 | Nguyen et al. | Jul 2012 | B2 |
| 8231456 | Zielinski | Jul 2012 | B2 |
| 8235803 | Loose et al. | Aug 2012 | B2 |
| 8282475 | Nguyen et al. | Oct 2012 | B2 |
| 8323099 | Durham et al. | Dec 2012 | B2 |
| 8337290 | Nguyen et al. | Dec 2012 | B2 |
| 8342946 | Amaitis | Jan 2013 | B2 |
| 8393948 | Allen et al. | Mar 2013 | B2 |
| 8403758 | Homik | Mar 2013 | B2 |
| 8430745 | Agarwal et al. | Apr 2013 | B2 |
| 8461958 | Saenz | Jun 2013 | B2 |
| 8469813 | Joshi | Jun 2013 | B2 |
| 8529345 | Nguyen | Sep 2013 | B2 |
| 8597108 | Nguyen | Dec 2013 | B2 |
| 8602875 | Nguyen | Dec 2013 | B2 |
| 8613655 | Kisenwether | Dec 2013 | B2 |
| 8613659 | Nelson et al. | Dec 2013 | B2 |
| 8678901 | Kelly | Mar 2014 | B1 |
| 8696470 | Nguyen | Apr 2014 | B2 |
| 8745417 | Huang et al. | Jun 2014 | B2 |
| 8834254 | Buchholz et al. | Sep 2014 | B2 |
| 8858323 | Nguyen et al. | Oct 2014 | B2 |
| 8864586 | Nguyen | Oct 2014 | B2 |
| 8942995 | Kerr | Jan 2015 | B1 |
| 9039507 | Allen et al. | May 2015 | B2 |
| 9235952 | Nguyen | Jan 2016 | B2 |
| 9292996 | Davis et al. | Mar 2016 | B2 |
| 9325203 | Nguyen | Apr 2016 | B2 |
| 9466171 | Hornik | Oct 2016 | B2 |
| 9483901 | Nguyen | Nov 2016 | B2 |
| 9486697 | Nguyen | Nov 2016 | B2 |
| 9486704 | Nguyen | Nov 2016 | B2 |
| 9530277 | Nelson et al. | Dec 2016 | B2 |
| 9576425 | Nguyen | Feb 2017 | B2 |
| 9626826 | Nguyen | Apr 2017 | B2 |
| 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 |
| 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 |
| 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 |
| 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 |
| 20050130728 | Nguyen et al. | Jun 2005 | A1 |
| 20050130731 | Englman | Jun 2005 | A1 |
| 20050137014 | Vetelaninen | Jun 2005 | A1 |
| 20050170883 | Muskin et al. | Aug 2005 | A1 |
| 20050181865 | Luciano | Aug 2005 | A1 |
| 20050181870 | Nguyen et al. | Aug 2005 | A1 |
| 20050181875 | Hoehne | Aug 2005 | A1 |
| 20050187020 | Amaitis et al. | Aug 2005 | A1 |
| 20050202875 | Murphy et al. | Sep 2005 | A1 |
| 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 |
| 20070159301 | Hirt et al. | Jul 2007 | A1 |
| 20070161402 | Ng et al. | Jul 2007 | A1 |
| 20070184896 | Dickerson | Aug 2007 | A1 |
| 20070184904 | Lee | Aug 2007 | A1 |
| 20070191109 | Crowder et al. | Aug 2007 | A1 |
| 20070207852 | Nelson et al. | Sep 2007 | A1 |
| 20070207854 | Wolf et al. | Sep 2007 | A1 |
| 20070238505 | Okada | Oct 2007 | A1 |
| 20070241187 | Alderucci et al. | Oct 2007 | A1 |
| 20070248036 | Nevalainen | Oct 2007 | A1 |
| 20070257430 | Hardy et al. | Nov 2007 | A1 |
| 20070259713 | Fiden et al. | Nov 2007 | A1 |
| 20070259717 | Mattice et al. | Nov 2007 | A1 |
| 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 |
| 20080070652 | Nguyen et al. | Mar 2008 | A1 |
| 20080070681 | Marks et al. | Mar 2008 | A1 |
| 20080076505 | Nguyen | Mar 2008 | A1 |
| 20080076506 | Nguyen et al. | Mar 2008 | A1 |
| 20080076548 | Paulsen | Mar 2008 | A1 |
| 20080076572 | Nguyen et al. | Mar 2008 | A1 |
| 20080096650 | Baerlocher | Apr 2008 | A1 |
| 20080102916 | Kovacs | May 2008 | A1 |
| 20080102956 | Burman et al. | May 2008 | A1 |
| 20080102957 | Burnman et al. | May 2008 | A1 |
| 20080113772 | Burrill et al. | May 2008 | A1 |
| 20080119267 | Denlay | May 2008 | A1 |
| 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 | 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 |
| 20080268959 | Bryson | Oct 2008 | A1 |
| 20080300058 | Sum et al. | Dec 2008 | A1 |
| 20080305864 | Kelly et al. | Dec 2008 | A1 |
| 20080305865 | Kelly et al. | Dec 2008 | A1 |
| 20080305866 | Kelly et al. | Dec 2008 | A1 |
| 20080311994 | Amaitas et al. | Dec 2008 | A1 |
| 20080318669 | Buchholz | Dec 2008 | A1 |
| 20080318686 | Crowder et al. | Dec 2008 | A1 |
| 20090005165 | Arezina et al. | Jan 2009 | A1 |
| 20090011822 | Englman | Jan 2009 | A1 |
| 20090017906 | Jackson | Jan 2009 | A1 |
| 20090021381 | Higuchi | Jan 2009 | A1 |
| 20090029766 | Lutnick et al. | Jan 2009 | A1 |
| 20090054149 | Brosnan et al. | Feb 2009 | A1 |
| 20090077396 | Tsai et al. | Mar 2009 | A1 |
| 20090088258 | Saunders et al. | Apr 2009 | A1 |
| 20090098925 | Gagner et al. | Apr 2009 | A1 |
| 20090104977 | Zielinski | Apr 2009 | A1 |
| 20090104983 | Okada | Apr 2009 | A1 |
| 20090118002 | Lyons | May 2009 | A1 |
| 20090118013 | Finnimore et al. | May 2009 | A1 |
| 20090118022 | Lyons et al. | May 2009 | A1 |
| 20090124366 | Aoki et al. | May 2009 | A1 |
| 20090124390 | Seelig et al. | May 2009 | A1 |
| 20090131146 | Arezina et al. | May 2009 | A1 |
| 20090131151 | Harris et al. | May 2009 | A1 |
| 20090132163 | Ashley et al. | May 2009 | A1 |
| 20090137255 | Ashley et al. | May 2009 | A1 |
| 20090138133 | Buchholz et al. | May 2009 | A1 |
| 20090143141 | Wells | Jun 2009 | A1 |
| 20090149245 | Fabbri | Jun 2009 | A1 |
| 20090149261 | Chen et al. | Jun 2009 | A1 |
| 20090153342 | Thorn | Jun 2009 | A1 |
| 20090156303 | Kiely et al. | Jun 2009 | A1 |
| 20090163272 | Baker | Jun 2009 | A1 |
| 20090176578 | Herrmann et al. | Jul 2009 | A1 |
| 20090191962 | Hardy et al. | Jul 2009 | A1 |
| 20090197684 | Arezina et al. | Aug 2009 | A1 |
| 20090216547 | Canora et al. | Aug 2009 | A1 |
| 20090219901 | Bull et al. | Sep 2009 | A1 |
| 20090221342 | Katz et al. | Sep 2009 | A1 |
| 20090227302 | Abe | Sep 2009 | A1 |
| 20090239666 | Hall et al. | Sep 2009 | A1 |
| 20090264190 | Davis et al. | Oct 2009 | A1 |
| 20090270170 | Patton | Oct 2009 | A1 |
| 20090271287 | Halpern | Oct 2009 | A1 |
| 20090275410 | Kisenwether et al. | Nov 2009 | A1 |
| 20090275411 | Kisenwether et al. | Nov 2009 | A1 |
| 20090280910 | Gagner et al. | Nov 2009 | A1 |
| 20090282469 | Lynch | Nov 2009 | A1 |
| 20090298468 | Hsu | Dec 2009 | A1 |
| 20100002897 | Keady | Jan 2010 | A1 |
| 20100004058 | Acres | Jan 2010 | A1 |
| 20100016069 | Herrmann | Jan 2010 | A1 |
| 20100049738 | Mathur et al. | Feb 2010 | A1 |
| 20100056248 | Acres | Mar 2010 | A1 |
| 20100062833 | Mattice et al. | Mar 2010 | A1 |
| 20100062840 | Herrmann et al. | Mar 2010 | A1 |
| 20100079237 | Falk | Apr 2010 | A1 |
| 20100081501 | Carpenter et al. | Apr 2010 | A1 |
| 20100081509 | Burke | Apr 2010 | A1 |
| 20100099499 | Amaitis et al. | Apr 2010 | A1 |
| 20100105454 | Weber et al. | Apr 2010 | A1 |
| 20100106612 | Gupta | Apr 2010 | A1 |
| 20100115591 | Kane-Esrig | May 2010 | A1 |
| 20100120486 | DeWaal | May 2010 | A1 |
| 20100124967 | Lutnick et al. | May 2010 | A1 |
| 20100130276 | Fiden | May 2010 | A1 |
| 20100160035 | Herrmann | Jun 2010 | A1 |
| 20100160043 | Fujimoto et al. | Jun 2010 | A1 |
| 20100178977 | Kim et al. | Jul 2010 | A1 |
| 20100184509 | Sylla | Jul 2010 | A1 |
| 20100197383 | Rader et al. | Aug 2010 | A1 |
| 20100197385 | Aoki et al. | Aug 2010 | A1 |
| 20100203955 | Sylla | Aug 2010 | A1 |
| 20100203963 | Allen | Aug 2010 | A1 |
| 20100227662 | Speer et al. | Sep 2010 | A1 |
| 20100227670 | Arezine et al. | Sep 2010 | A1 |
| 20100227671 | Laaroussi | Sep 2010 | A1 |
| 20100227687 | Speer 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 et al. | Jan 2011 | A1 |
| 20110039615 | Acres | Feb 2011 | A1 |
| 20110053679 | Canterbury et al. | Mar 2011 | A1 |
| 20110065492 | Acres | Mar 2011 | A1 |
| 20110105216 | Cohen | May 2011 | A1 |
| 20110111827 | Nicely et al. | May 2011 | A1 |
| 20110111843 | Nicely et al. | May 2011 | A1 |
| 20110111860 | Nguyen | May 2011 | A1 |
| 20110118010 | Brune | May 2011 | A1 |
| 20110159966 | Gura et al. | Jun 2011 | A1 |
| 20110183732 | Block | Jul 2011 | A1 |
| 20110183749 | Allen | Jul 2011 | A1 |
| 20110207525 | Allen | Aug 2011 | A1 |
| 20110212711 | Scott | Sep 2011 | A1 |
| 20110212767 | Barclay et al. | Sep 2011 | A1 |
| 20110223993 | Allen et al. | Sep 2011 | A1 |
| 20110244952 | Schueller | Oct 2011 | A1 |
| 20110263318 | Agarwal et al. | Oct 2011 | A1 |
| 20110269548 | Barclay et al. | Nov 2011 | A1 |
| 20110306400 | Nguyen | Dec 2011 | A1 |
| 20110306426 | Novak et al. | Dec 2011 | A1 |
| 20120015709 | Bennett et al. | Jan 2012 | A1 |
| 20120028703 | Anderson et al. | Feb 2012 | A1 |
| 20120028718 | Barclay et al. | Feb 2012 | A1 |
| 20120034968 | Watkins et al. | Feb 2012 | A1 |
| 20120046110 | Amaitis | Feb 2012 | A1 |
| 20120094769 | Nguyen et al. | Apr 2012 | A1 |
| 20120100908 | Wells | Apr 2012 | A1 |
| 20120108319 | Caputo et al. | May 2012 | A1 |
| 20120122561 | Hedrick | May 2012 | A1 |
| 20120122567 | Gangadharan et al. | May 2012 | A1 |
| 20120122584 | Nguyen | May 2012 | A1 |
| 20120122590 | Nguyen | May 2012 | A1 |
| 20120172130 | Acres | Jul 2012 | A1 |
| 20120184362 | Barclay et al. | Jul 2012 | A1 |
| 20120184363 | Barclay et al. | Jul 2012 | A1 |
| 20120190426 | Acres | Jul 2012 | A1 |
| 20120194448 | Rothkopf | Aug 2012 | A1 |
| 20120208618 | Frerking | Aug 2012 | A1 |
| 20120231885 | Speer, II | Sep 2012 | A1 |
| 20120239566 | Everett | Sep 2012 | A1 |
| 20120322563 | Nguyen et al. | Dec 2012 | A1 |
| 20120330740 | Pennington et al. | Dec 2012 | A1 |
| 20130005433 | Holch | Jan 2013 | A1 |
| 20130005443 | Kosta | Jan 2013 | A1 |
| 20130005453 | Nguyen et al. | Jan 2013 | A1 |
| 20130059650 | Sylla et al. | Mar 2013 | A1 |
| 20130065668 | LeMay | Mar 2013 | A1 |
| 20130103965 | Golembeski | Apr 2013 | A1 |
| 20130104193 | Gatto et al. | Apr 2013 | A1 |
| 20130130766 | Harris et al. | May 2013 | A1 |
| 20130132745 | Schoening et al. | May 2013 | A1 |
| 20130165210 | Nelson | Jun 2013 | A1 |
| 20130185559 | Morel | Jul 2013 | A1 |
| 20130196756 | Nguyen | Aug 2013 | A1 |
| 20130196776 | Nguyen | Aug 2013 | A1 |
| 20130210513 | Nguyen | Aug 2013 | A1 |
| 20130210514 | Nguyen | Aug 2013 | A1 |
| 20130210530 | Nguyen | Aug 2013 | A1 |
| 20130225279 | Patceg | Aug 2013 | A1 |
| 20130225282 | Williams et al. | Aug 2013 | A1 |
| 20130252730 | Joshi | Sep 2013 | A1 |
| 20130281188 | Guinn | Oct 2013 | A1 |
| 20130316808 | Nelson | Nov 2013 | A1 |
| 20130337878 | Shepherd | Dec 2013 | A1 |
| 20130337889 | Gagner | Dec 2013 | A1 |
| 20140006129 | Heath | Jan 2014 | A1 |
| 20140057716 | Massing et al. | Feb 2014 | A1 |
| 20140087862 | Burke | Mar 2014 | A1 |
| 20140094295 | Nguyen | Apr 2014 | A1 |
| 20140094316 | Nguyen | Apr 2014 | A1 |
| 20140121005 | Nelson | May 2014 | A1 |
| 20140179431 | Nguyen | Jun 2014 | A1 |
| 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 |
| 20170116823 | Nguyen | Apr 2017 | A1 |
| 20170144071 | Nguyen | May 2017 | A1 |
| 20170148259 | Nguyen | May 2017 | A1 |
| 20170148261 | Nguyen | May 2017 | A1 |
| 20170148263 | Nguyen | May 2017 | A1 |
| 20170206734 | Nguyen | Jul 2017 | A1 |
| 20170228979 | Nguyen | Aug 2017 | A1 |
| 20170337770 | Nguyen | Nov 2017 | A1 |
| 20180144581 | Nguyen | May 2018 | A1 |
| 20190005773 | Nguyen | Jan 2019 | A1 |
| 20190122490 | Nguyen | Apr 2019 | A1 |
| 20190122492 | Nguyen | Apr 2019 | A1 |
| 20190213829 | Nguyen | Jul 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 2033638 | May 1980 | GB |
| 2062923 | May 1981 | GB |
| 2096376 | Oct 1982 | GB |
| 2097570 | Nov 1982 | GB |
| 2335524 | Sep 1999 | GB |
| 12005000454 | May 2007 | PH |
| WO 05073933 | Aug 2005 | WO |
| WO 2008027621 | Mar 2008 | WO |
| WO 2009026309 | Feb 2009 | WO |
| WO 2009062148 | May 2009 | WO |
| WO 2010017252 | Feb 2010 | WO |
| Entry |
|---|
| Benston, Liz, “Harrahs Launches iPhone App; Caesars Bypasses Check-in,” Las Vegas Sun, Las Vegas, NV. Jan. 8, 2010. |
| Finnegan, Amanda, “Casinos Connecting with Customers via iPhone Apps”, May 27, 2010, Las Vegas Sun, Las Vegas, NV. |
| Gaming Today Staff, “Slots showcased at 2009 National Indian Gaming Assoc.”, GamingToday.com, Apr. 14, 2009. |
| Green, Marian, “Testing Texting Casino Journal”, Mar. 2, 2009. |
| Hasan, Ragib, et al., “A Survey of Peer-to-Peer Storage Techniques for Distributed File Systems”, National Center for Supercomputing Applications, Department of Computer Science, University of Illinois at Urbana Champaign, Jun. 27, 2005. |
| Jones, Trahern, “Telecon-equipped drones could revolutionize wireless market”, azcentral.com, http://www.azcentral.com/business/news/articles/20130424telecom-equipped-drones-could-revolutionize-wireless-market.html, downloaded Jul. 2, 2013, 2 pages. |
| Yancey, Kitty Bean, “Navigate Around Vegas with New iPhone Apps”, USA Today, Jun. 3, 2010. |
| IAPS, Daily Systems LLC, 2010. |
| U.S. Appl. No. 12/945,888, filed Nov. 14, 2010. |
| U.S. Appl. No. 12/945,889, filed Nov. 14, 2010. |
| U.S. Appl. No. 13/622,702, filed Sep. 19, 2012. |
| U.S. Appl. No. 13/800,917, filed Mar. 13, 2013. |
| U.S. Appl. No. 13/296,182, filed Nov. 15, 2011. |
| U.S. Appl. No. 13/801,234, filed Mar. 13, 2013. |
| U.S. Appl. No. 13/801,171, filed Mar. 13, 2013. |
| U.S. Appl. No. 13/843,192, filed Mar. 15, 2013. |
| U.S. Appl. No. 13/843,087, filed Mar. 15, 2013. |
| U.S. Appl. No. 13/632,743, filed Oct. 1, 2012. |
| U.S. Appl. No. 13/632,828, filed Oct. 1, 2012. |
| U.S. Appl. No. 13/833,953, filed Mar. 15, 2013. |
| U.S. Appl. No. 12/619,672, filed Nov. 16, 2009. |
| U.S. Appl. No. 13/801,121, filed Mar. 13, 2013. |
| U.S. Appl. No. 12/581,115, filed Oct. 17, 2009. |
| U.S. Appl. No. 13/801,076, filed Mar. 13, 2013. |
| U.S. Appl. No. 13/617,717, filed Nov. 12, 2009. |
| U.S. Appl. No. 13/633,118, filed Oct. 1, 2012. |
| U.S. Appl. No. 12/797,610, filed Jun. 10, 2010. |
| U.S. Appl. No. 13/801,256, filed Mar. 13, 2013. |
| U.S. Appl. No. 12/757,968, filed Apr. 9, 2010. |
| U.S. Appl. No. 12/797,616, filed Jun. 10, 2010. |
| U.S. Appl. No. 13/557,063, filed Jul. 24, 2012. |
| U.S. Appl. No. 13/833,116, filed Mar. 15, 2013. |
| U.S. Appl. No. 13/801,271, filed Mar. 13, 2011. |
| Office Action for U.S. Appl. No. 12/945,888 dated Apr. 10, 2012. |
| Final Office Action for U.S. Appl. No. 12/945,888 dated Sep. 21, 2012. |
| Advisory Action for U.S. Appl. No. 12/945,888 dated Jan. 30, 2013. |
| Office Action for U.S. Appl. No. 12/581,115 dated Dec. 20, 2011. |
| Final Office Action for U.S. Appl. No. 12/581,115 dated Sep. 13, 2012. |
| Notice of Allowance for U.S. Appl. No. 12/581,115 dated May 24, 2013. |
| Office Action for U.S. Appl. No. 12/619,672 dated Dec. 20, 2011. |
| Final Office Action for U.S. Appl. No. 12/619,672 dated Nov. 6, 2012. |
| Office Action for U.S. Appl. No. 12/619,672 dated Mar. 7, 2013. |
| Office Action for U.S. Appl. No. 12/617,717 dated Oct. 4, 2011. |
| Office Action for U.S. Appl. No. 12/617,717 dated Apr. 4, 2012. |
| Advisory Action for U.S. Appl. No. 12/617,717 dated Jun. 12, 2011. |
| Office Action for U.S. Appl. No. 12/617,717 dated Jun. 17, 2013. |
| Office Action for U.S. Appl. No. 12/797,610 dated Dec. 8, 2011. |
| Final Office Action for U.S. Appl. No. 12/797,610 dated Jun. 6, 2012. |
| Office Action for U.S. Appl. No. 12/797,610 dated Feb. 26, 2013. |
| Office Action for U.S. Appl. No. 12/757,968, dated May 9, 2012. |
| Final Office Action for U.S. Appl. No. 12/757,968, dated Nov. 29, 2012. |
| Office Action for U.S. Appl. No. 12/757,968, dated Apr. 25, 2013. |
| Office Action for U.S. Appl. No. 12/797,616 dated Mar. 15, 2012. |
| Final Office Action for U.S. Appl. No. 12/797,616 dated Oct. 13, 2012. |
| Office Action for U.S. Appl. No. 12/797,616 dated Feb. 13, 2013. |
| Final Office Action for U.S. Appl. No. 12/797,616 dated May 8, 2013. |
| Office Action for U.S. Appl. No. 13/296,182 dated Dec. 5, 2012. |
| Brochure, 5000 Ft. Inc., 1 page, Nov. 2010. |
| Frontier Fortune game, email notification, MGM Resorts Intl., Aug. 9, 2013. |
| “Getting Back in the Game: Geolocation Can Ensure Compliance with New iGaming Regulations”, White Paper, Quova, Inc., 2010. |
| Notice of Allowance of U.S. Appl. No. 12/619,672, dated Aug. 23, 2013. |
| Office Action for U.S. Appl. No. 13/633,118, dated Sep. 20, 2013. |
| Office Action for U.S. Appl. No. 13/801,256, dated Jul. 2, 2013. |
| Notice of Allowance for U.S. Appl. No. 12/619,672, dated Oct. 3, 2013. |
| Notice of Allowance for U.S. Appl. No. 12/757,968, dated Oct. 11, 2013. |
| Final Office Action for U.S. Appl. No. 12/797,610, dated Jul. 10, 2013. |
| Notice of Allowance for U.S. Appl. No. 12/757,968, dated Dec. 18, 2013. |
| Office Action for U.S. Appl. No. 12/945,889, dated Dec. 18, 2013. |
| Office Action for U.S. Appl. No. 13/632,828, dated Jul. 30, 2013. |
| Restriction Requirement for U.S. Appl. No. 13/801,256, dated Dec. 30, 2013. |
| Office Action for U.S. Appl. No. 13/801,171, dated Dec. 26, 2013. |
| Office Action for U.S. Appl. No. 13/801,234, dated Jan. 10, 2014. |
| Final Office Action for U.S. Appl. No. 13/296,182, dated Feb. 12, 2014. |
| Office Action for U.S. Appl. No. 12/617,717, dated Feb. 25, 2014. |
| Office Action for U.S. Appl. No. 13/801,076, dated Mar. 28, 2014. |
| Final Office Action for U.S. Appl. No. 13/633,118, dated Apr. 3, 2014. |
| Office Action for U.S. Appl. No. 13/843,192, dated Apr. 3, 2014. |
| Office Action for U.S. Appl. No. 13/632,743, dated Apr. 10, 2014. |
| Office Action for U.S. Appl. No. 13/801,121, dated Apr. 11, 2014. |
| Final Office Action for U.S. Appl. No. 12/945,889, dated Jun. 30, 2014. |
| Notice of Allowance for U.S. Appl. No. 12/617,717, dated Jul. 14, 2014. |
| Office Action for U.S. Appl. No. 13/801,121, dated Sep. 24, 2014. |
| Office Action for U.S. Appl. No. 13/801,171, dated Sep. 22, 2014. |
| Office Action for U.S. Appl. No. 13/801,234, dated Oct. 1, 2014. |
| Office Action for U.S. Appl. No. 13/801,271, dated Oct. 31, 2014. |
| Final Office Action for U.S. Appl. No. No. 13/843,192, dated Oct. 21, 2014. |
| Office Action for U.S. Appl. No. 13/632,743, dated Oct. 23, 2014. |
| Office Action for U.S. Appl. No. 12/945,889, dated Oct. 23, 2014. |
| Office Action for U.S. Appl. No. 13/632,828, dated Nov. 7, 2014. |
| Office Action for U.S. Appl. No. 12/797,610, dated Dec. 15, 2014. |
| Final Office Action for U.S. Appl. No. 12/945,889, dated Feb. 12, 2015. |
| Final Office Action for U.S. Appl. No. 13/801,171, dated Mar. 16, 2015. |
| Office Action for U.S. Appl. No. 13/833,116, dated Mar. 27, 2015. |
| Office Action for U.S. Appl. No. 13/632,828, dated Apr. 10, 2015. |
| Final Office Action for U.S. Appl. No. 13/801,121, dated Apr. 21, 2015. |
| Final Office Action for U.S. Appl. No. 13/557,063, dated Apr. 28, 2015. |
| Office Action for U.S. Appl. No. 13/296,182, dated Jun. 5, 2015. |
| Office Action for U.S. Appl. No. 13/843,192, dated Jun. 19, 2015. |
| Office Action for U.S. Appl. No. 12/797,610, dated Jul. 14, 2015. |
| Final Office Action for U.S. Appl. No. 13/833,953, dated Jul. 17, 2015. |
| Notice of Allowance for U.S. Appl. No. 12/945,889, dated Jul. 22, 2015. |
| Office Action for U.S. Appl. No. 12/797,616, dated Aug. 10, 2015. |
| Final Office Action for U.S. Appl. No. 13/801,234, dated Aug. 14, 2015. |
| Final Office Action for U.S. Appl. No. 13/833,116, dated Sep. 24, 2015. |
| Office Action for U.S. Appl. No. 13/801,121, dated Oct. 2, 2015. |
| Office Action for U.S. Appl. No. 14/017,150, dated Oct. 7, 2015. |
| Office Action for U.S. Appl. No. 14/017,159, dated Oct. 7, 2015. |
| Office Action for U.S. Appl. No. 13/801,271 dated Oct. 19, 2015. |
| Office Action for U.S. Appl. No. 14/211,536 dated Oct. 19, 2015. |
| Final Office Action for U.S. Appl. No. 13/632,828, dated Oct. 22, 2015. |
| Office Action for U.S. Appl. No. 14/217,066, dated Dec. 17, 2015. |
| Notice of Allowance for U.S. Appl. No. 13/557,063, dated Dec. 23, 2015. |
| Office Action for U.S. Appl. No. 13/296,182, dated Dec. 23, 2015. |
| Final Office Action for U.S. Appl. No. 13/843,192, dated Dec. 30, 2015. |
| Office Action for U.S. Appl. No. 13/801,076, dated Jan. 11, 2016. |
| Office Action for U.S. Appl. No. 12/945,888, dated Jan. 22, 2016. |
| Final Office Action for U.S. Appl. No. 12/797,616, dated Jun. 12, 2016. |
| Office Action for U.S. Appl. No. 13/843,087, dated Feb. 25, 2016. |
| Office Action for U.S. Appl. No. 13/800,917, dated Feb. 25, 2016. |
| Advisory Action for U.S. Appl. No. 13/632,828, dated Feb. 25, 2016. |
| Office Action for U.S. Appl. No. 13/801,234, dated Mar. 8, 2016. |
| Office Action for U.S. Appl. No. 14/216,986, dated Mar. 9, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,271, dated Mar. 11, 2016. |
| Office Action for U.S. Appl. No. 13/622,702, dated Mar. 22, 2016. |
| Final Office Action for U.S. Appl. No. 13/633,118, dated Mar. 24, 2016. |
| Final Office Action for U.S. Appl. No. 14/189,948, dated Apr. 6, 2016. |
| Final Office Action for U.S. Appl. No. 12/797,610, dated Apr. 21, 2016. |
| Final Office Action for U.S. Appl. No. 14/017,150, dated Apr. 26, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,121, dated May 11, 2016. |
| Final Office Action for U.S. Appl. No. 14/017,159, dated Jun. 6, 2016. |
| Office Action for U.S. Appl. No. 13/801,171, dated Jun. 6, 2016. |
| Office Action for U.S. Appl. No. 13/843,192, dated Jun. 9, 2016. |
| Final OA for U.S. Appl. No. 12/945,888, dated Jun. 28, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/833,953, dated Jul. 6, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,171, dated May 21, 2014. |
| Final Office Action for U.S. Appl. No. 13/801,234, dated May 22, 2014. |
| Office Action for U.S. Appl. No. 14/211,536, dated Jul. 13, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/801,076, dated Jul. 11, 2016. |
| Office Action for U.S. Appl. No. 13/296,182, dated Jul. 20, 2016. |
| Restriction Requirement for U.S. Appl. No. 13/296,182, dated Oct. 12, 2012. |
| Advisory Action for U.S. Appl. No. 13/296,182, dated May 8, 2014. |
| Advisory Action for U.S. Appl. No. 13/843,192, dated May 8, 2014. |
| Notice of Allowance for U.S. Appl. No. 13843,192, dated Aug. 10, 2016. |
| Office Action for U.S. Appl. No. 14/217,066, dated Dec. 22, 2016. |
| Final Office Action for U.S. Appl. No. 14/216,986, dated Sep. 23, 2016. |
| Office Action for U.S. Appl. No. 14/017,159, dated Sep. 23, 2016. |
| Office Action for U.S. Appl. No. 13/632,743, dated Sep. 23, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,234, dated Oct. 14, 2016. |
| Final Office Action for U.S. Appl. No. 13/843,087, dated Oct. 13, 2016. |
| Final Office Action for U.S. Appl. No. 13/622,702, dated Oct. 13, 2016. |
| Office Action for U.S. Appl. No. 14/189,948, dated Nov. 7, 2016. |
| Final Office Action for U.S. Appl. No. 14/211,536, dated Mar. 14, 2014. |
| Notice of Allowance for U.S. Appl. No. 13/833,116, dated Oct. 11, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/801,271, dated Dec. 2, 2016. |
| Notice of Allowance for U.S. Appl. No. 12/797,610, dated Dec. 7, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/632,828, dated Dec. 16, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 19, 2016. |
| Notice of Allowance for U.S. Appl. No. 14/211,536, dated Dec. 28, 2016. |
| Notice of Allowance for U.S. Appl. No. 13/801,256, dated Jan. 20, 2017. |
| Office Action for U.S. Appl. No. 13/800,917, dated Feb. 3, 2017. |
| Final Office Action for U.S. Appl. No. 12/797,616, dated Feb. 10, 2017. |
| Office Action for U.S. Appl. No. 12/945,888, dated Feb. 28, 2017. |
| Final Office Action for U.S. Appl. No. 14/189,948, dated Mar. 17, 2017. |
| Office Action for U.S. Appl. No. 15/400,840, dated Mar. 10, 2017. |
| Notice of Allowance for U.S. Appl. No. 13/801,121, dated Mar. 29, 2017. |
| Office Action for U.S. Appl. No. 15/270,333, dated Mar. 30, 2017. |
| Office Action for U.S. Appl. No. 15/402,945, dated Apr. 5, 2017. |
| Office Action for U.S. Appl. No. 15/271,488, dated Apr. 19, 2017. |
| Final Office Action for U.S. Appl. No. 14/217,066, dated Apr. 21, 2017. |
| Office Action for U.S. Appl. No. 14/216,986 dated Apr. 26, 2017. |
| Office Action for U.S. Appl. No. 13/801,171, dated Jun. 14, 2017. |
| Office Action for U.S. Appl. No. 14/017,159, dated Jun. 29, 2017. |
| Notice of Allowance for U.S. Appl. No. 15/270,333, dated Jul. 5, 2017. |
| Final Office Action for U.S. Appl. No. 13/800,917, dated Jul. 13, 2017. |
| Notice of Allowance for U.S. Appl. No. 13/801,234, dated Jul. 5, 2017. |
| Notice of Allowance for U.S. Appl. No. 14/217,066, dated Jul. 14, 2017. |
| Final Office Action for U.S. Appl. No. 14/518,909, dated Jul. 19, 2017. |
| Final Office Action for U.S. Appl. No. 13/801,121, dated Sep. 15, 2016. |
| Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 17, 2015. |
| Advisory Action for U.S. Appl. No. 13/801,121, dated Jul. 19, 2016. |
| Notice of Allowance for U.S. Appl. No. 15/293,751, dated Aug. 4, 2017. |
| Advisory Action for U.S. Appl. No. 14/189,948, dated Jul. 28, 2017. |
| Final OA for U.S. Appl. No. 13/801,256, dated Aug. 15, 2014. |
| Final OA for U.S. Appl. No. 13/801,256, dated Feb. 18, 2015. |
| Advisory Action for U.S. Appl. No. 13/801,256, dated Dec. 5, 2014. |
| Office Action for U.S. Appl. No. 13/801,256, dated Jan. 12, 2016. |
| Final Office Action for U.S. Appl. No. 13/801,256, dated Aug. 16, 2016. |
| Office Action for U.S. Appl. No. 13/622,702, dated Aug. 31, 2017. |
| Office Action for U.S. Appl. No. 12/945,888, dated Sep. 1, 2017. |
| Office Action for U.S. Appl. No. 14/017,150, dated Sep. 7, 2017. |
| Notice of Allowance for U.S. Appl. No. 14/189,948, dated Sep. 13, 2017. |
| Office Action for U.S. Appl. No. 15/138,086, dated Oct. 19, 2017. |
| Notice of Allowance for U.S. Appl. No. 15/402,945 dated Nov. 21, 2017. |
| Final Office Action for U.S. Appl. No. 13/801,171, dated Dec. 13, 2017. |
| Final Office Action for U.S. Appl. No. 15/271,488, dated Dec. 21, 2017. |
| Office Action for U.S. Appl. No. 15/671,133, dated Dec. 22, 2017. |
| Final Office Action for U.S. Appl. No. 14/216,986, dated Dec. 26, 2017. |
| Restriction Requirement for U.S. Appl. No. 15/427,307, dated Jan. 17, 2018. |
| Office Action for U.S. Appl. No. 15/798,363, dated Jan. 26, 2018. |
| Office Action for U.S. Appl. No. 15/427,291, dated Jan. 29, 2018. |
| Final Office Action for U.S. Appl. No. 14/017,159, dated Feb. 1, 2018. |
| Final Office Action for U.S. Appl. No. 13/622,702, dated Feb. 22, 2018. |
| Office Action for U.S. Appl. No. 15/811,654, dated Feb. 22, 2018. |
| Final Office Action for U.S. Appl. No. 13/622,702, dated Feb. 27, 2018. |
| Final Office Action for U.S. Appl. No. 15/427,308, dated Mar. 19, 2018. |
| Office Action for U.S. Appl. No. 15/876,095, dated Apr. 3, 2018. |
| Office Action for U.S. Appl. No. 15/835,448, dated Apr. 4, 2018. |
| Office Action for U.S. Appl. No. 15/427,307, dated Apr. 9, 2018. |
| Office Action for U.S. Appl. No. 14/216,986, dated Apr. 6, 2018. |
| Office Action for U.S. Appl. No. 15/426,898 dated Apr. 16, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/402,945, dated May 25, 2018. |
| Office Action for U.S. Appl. No. 15/495,973, dated Jun. 4, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/427,291 dated Jun. 18, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/271,488, dated Jun. 19, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/480,295, dated Jun. 20, 2018. |
| Office Action for U.S. Appl. No. 14/963,106, dated Jun. 22, 2018. |
| Office Action for U.S. Appl. No. 14/993,055, dated Jun. 22, 2018. |
| Final Office Action for U.S. Appl. No. 15/427,307, dated Jul. 9, 2018. |
| Notice of Allowance for U.S. Appl. No. 13/633,118, dated Aug. 3, 2018. |
| Office Action for U.S. Appl. No. 15/671,133, dated Aug. 9, 2018. |
| Office Action for U.S. Appl. No. 15/427,308, dated Aug. 15, 2018. |
| Office Action for U.S. Appl. No. 15/798,363, dated Aug. 29, 2018. |
| Office Action for U.S. Appl. No. 15/428,922 dated Sep. 17, 2018. |
| Office Action for U.S. Appl. No. 15/495,975, dated Sep. 21, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/271,488, dated Sep. 24, 2018. |
| Notice of Allowance for U.S. Appl. No. 15/876,095, dated Sep. 24, 2018. |
| Office Action for U.S. Appl. No. 13/622,702, dated Oct. 3, 2018. |
| Office Action for U.S. Appl. No. 15/293,751, dated Apr. 6, 2017. |
| Notice of Allowance for U.S. Appl. No. 13/801,171, dated Oct. 31, 2018. |
| Final Office Action for U.S. Appl. No. 15/835,448, dated Nov. 2, 2018. |
| Final Office Action for U.S. Appl. No. 15/480,295, dated Nov. 7, 2018. |
| Final Office Action for U.S. Appl. No. 14/963,106, dated Dec. 14, 2018. |
| Final Office Action for U.S. Appl. No. 14/993,055, dated Dec. 14, 2018. |
| Office Action for U.S. Appl. No. 16/162.358, dated Dec. 31, 2018. |
| Office Action for U.S. Appl. No. 14/017,159, dated Jan. 11, 2019. |
| Office Action for U.S. Appl. No. 15/426,898, dated Jan. 11, 2019. |
| Final Office Action for U.S. Appl. No. 15/495,973, dated Jan. 11, 2019. |
| Office Action for U.S. Appl. No. 14/216,986, dated Jan. 14, 2019. |
| Office Action for U.S. Appl. No. 15/427,307, dated Jan. 18, 2019. |
| Final Office Action for U.S. Appl. No. 15/798,363, dated Feb. 4, 2019. |
| Office Action for U.S. Appl. No. 16/125,614, dated Feb. 25, 2019. |
| Final Office Action for U.S. Appl. No. 15/495,975, dated Apr. 18, 2019. |
| Office Action for U.S. Appl. No. 15/671,133, dated May 1, 2019. |
| Notice of Allowance for U.S. Appl. No. 14/216,986, dated May 17, 2019. |
| Notice of Allowance for U.S. Appl. No. 14/518,909, dated May 17, 2019. |
| Office Action for U.S. Appl. No. 12/797,616, dated Jun. 5, 2019. |
| Office Action for U.S. Appl. No. 15/427,308, dated Jun. 14, 2019. |
| Office Action for U.S. Appl. No. 15/811,654, dated Jun. 14, 2019. |
| Office Action for U.S. Appl. No. 15/674,480, dated Jun. 20, 2019. |
| Notice of Allowance for U.S. Appl. No. 15/835,448, dated Jul. 3, 2019. |
| 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. |
| 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. 16/190,050, dated Jun. 1, 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. |
| Number | Date | Country | |
|---|---|---|---|
| 20190051115 A1 | Feb 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15293751 | Oct 2016 | US |
| Child | 16162358 | US | |
| Parent | 13801076 | Mar 2013 | US |
| Child | 15293751 | US | |
| Parent | 12581115 | Oct 2009 | US |
| Child | 13801076 | US |
