Patent Grant
9120007
Embodiments of the present disclosure relate generally to wagering games and, more particularly, to network gaming architectures, gaming systems, and related methods.
Global internet access has revolutionized electronic gaming, and in particular, participation in on-line gambling games and related websites offering such games. Such internet gaming platforms have enabled players to participate in gambling and other gaming events through personal computers or other electronic devices, wherever the player may be and at all times. Implementations of on-line gambling may include typical gambling elements, such as permitting one or more users to bet against the House in wagering games that are similar to those found in traditional casinos. In fact, many casinos have an on-line presence and offer on-line gambling operations. Such on-line gambling operations generally enable users to choose a wagering game, enter the wagering game by either downloading a computer application or through a web browser, place bets on one or more possible outcomes of the game, and win or lose money according to the outcome of the bets. With most on-line gambling applications, the House controls the computer application or web site through which a player bets. The House is generally in control of both managing the game and all associated financial transactions.
It is not surprising that security of such on-line gambling platforms is of utmost importance. Hackers may attempt to cheat and gain an unfair advantage in a variety of ways that would cause the House to lose significant sums of money by paying on bets that should not have been paid on, by allowing bets to be placed when the game outcome can be already be determined by unauthorized access, or by redirecting payments to parties that are not entitled to such payments. For example, a hacker may attempt to gain unauthorized access to view and in some cases even alter game information. In addition, individuals employed to work on the on-line gaming platform may be tempted to use their access to cheat the system.
Another consideration of on-line gambling platforms is that considerable resources are used in complying with regulatory requirements and in meeting increasing player demand. The inventors have appreciated the need for improved network gaming architectures, systems, and related methods to address various deficiencies of conventional approaches.
In the following description, reference is made to the accompanying drawings in which is shown, by way of illustration, specific embodiments of the present disclosure. The embodiments are intended to describe aspects of the disclosure in sufficient detail to enable those skilled in the art to practice that which is claimed. Other embodiments may be utilized and changes may be made without departing from the scope of the disclosure. The following detailed description is not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.
Furthermore, specific implementations shown and described are only examples and should not be construed as the only way to implement or partition the embodiments of the present disclosure into functional elements unless specified otherwise herein. It will be readily apparent to one of ordinary skill in the art that the various embodiments of the present disclosure may be practiced by numerous other partitioning solutions.
In the following description, elements, circuits, and functions may be shown in block diagram form in order not to obscure the present disclosure in unnecessary detail. Additionally, block definitions and partitioning of logic between various blocks is exemplary of a specific implementation. It will be readily apparent to one of ordinary skill in the art that the present disclosure may be practiced by numerous other partitioning solutions. Those of ordinary skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. Some drawings may illustrate signals as a single signal for clarity of presentation and description. It will be understood by a person of ordinary skill in the art that the signal may represent a bus of signals, wherein the bus may have a variety of bit widths and the present disclosure may be implemented on any number of data signals including a single data signal.
The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general-purpose processor, a special-purpose processor, an embedded processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A general-purpose processor may be considered a special-purpose processor while the general-purpose processor executes instructions (e.g., software code) stored on a computer-readable medium. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
Also, it is noted that the embodiments may be described in terms of a process that may be depicted as a flowchart, a flow diagram, a structure diagram, or a block diagram. Although a process may describe operational acts as a sequential process, many of these acts can be performed in another sequence, in parallel, or substantially concurrently. In addition, the order of the acts may be re-arranged. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. Furthermore, the methods disclosed herein may be implemented in hardware, software, or both. If implemented in software, the functions may be stored or transmitted as one or more instructions or code on computer readable media. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another.
It should be understood that any reference to an element herein using a designation such as “first,” “second,” and so forth does not limit the quantity or order of those elements, unless such limitation is explicitly stated. Rather, these designations may be used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements may be employed or that the first element must precede the second element in some manner. In addition, unless stated otherwise, a set of elements may comprise one or more elements.
The terms “gaming,” “gambling,” or the like, refer to activities, games, sessions, rounds, hands, rolls, operations, and other events related to wagering games such as web games, casino games, card games, dice games, and other games of chance for which wagers may be placed by a player. In addition, the word “wager,” “bet,” “bid” or the like, refer to any type of wagers, bets or gaming ventures that are placed on random events, whether of monetary or non-monetary value. Points, credits, and other items of value may be purchased, earned, or otherwise issued prior to beginning the wagering game. In some embodiments, purchased points, credits, or other items of value may have an exchange rate that is not one-to-one to the currency used by the user. For example, a wager may include money, points, credits, symbols, or other items that may have some value related to a wagering game. Wagers may be placed in wagering games that are play for pay as well as play for fun, as will be described in more detail below.
Embodiments of the present disclosure include a network architecture for a gaming system that provides end users access to proprietary game content through client servers. Although the examples below generally describe a gaming system that may be used for administering card games (e.g., Hold 'Em poker variants, pai gow poker, blackjack, etc.), the gaming system may be configured to administer other types of wagering games such as dice games, big wheel games, roulette, scratch off games, and any other wagering game that uses a fixed set of game pieces for a particular round or cycle of the game and randomly selects game pieces to determine the game outcome. The use of card games as examples of wagering games is done for simplicity of the description, and not as a limitation. Modification of the gaming system to support non card-based games, or other card-based games that are not specifically described herein, is considered to be within the scope of this disclosure, as such will be apparent to those of ordinary skill in the art, given the present disclosure.
Embodiments of the present disclosure may include traditional gambling games in which money or other items of value may be cashed out at the end of a game session. In addition, embodiments of the present disclosure may include “play for fun” wagering games, in which credits (or other symbols) may be issued to a player to be used for the wagers. For example, credits may be purchased by a player or issued through other methods. While credits may be won or lost, the ability of the player to cash out the credits may be restricted or prevented. In other words, while the credits may be purchased, the credits in a play for fun embodiment may be non-monetary credits in terms of the ability of the play to cash out of the wagering game. Exemplary systems that operate play for fun games may issue free credits. In some embodiments, a limited number free credits may be issued in order to entice players to play the games. Credits may be won or lost, but credit balances may not be cashed out. In exchange for identifying friends who may want to play, the system may issue additional credits. Often, additional credits may be issued after a period of time has elapsed to encourage the player to resume playing the game. The system may enable players to buy friends or additional game credits to allow the player to resume play for fun play. However, neither credits earned nor credits remaining may be cashed in exchange for something of monetary value. It is contemplated that objects of value may be awarded to play for fun players, but not in a direct exchange for credits. For example, the client may award a prize for a highest scoring play for fun player during a defined time interval. Enabling players to buy fake friends, extra credits, and/or game pieces that allow the player to advance through the game levels with more speed may provide an additional source of revenue to the host of the gaming system.
Embodiments of the present disclosure may include wagering games in which a single player is present at a virtual table competing against the house, while other embodiments include wagering games in which multiple players are present at the virtual table competing against the house, each other, or a combination thereof. Therefore, while examples provided herein describe a player or a user, the singular use of such terms should not be interpreted to preclude embodiments in which multiple players may access one or more client servers to access the gaming system.
In some embodiments, the client server 110 may not be part of the gaming system 100, in that the client server 110 may be operated by a different administrator than operates the other servers of the gaming system 100. In other words, the client server 110 may be part of a third-party system that does not administer the gaming system 100. For example, a gaming entity (e.g., a casino) may operate the client server 110 to provide its customers access to game content managed by a different entity. In some embodiments, the client server 110 may offer and/or provide access to content in addition to what is supported by the gaming system 100. As a result, the client server 110 may establish communication between the client and the gaming system 100, as well as the client and other content that is unrelated to the gaming system 100, including multiple different gaming systems that are not part of the gaming system 100. For example, a gaming entity may have a client server 110 that accesses game content from a plurality of different game administrators that provide access to different gaming systems (not shown).
It is also contemplated that in some embodiments, the client server 110 may be part of the gaming system 100, such as being operated by the same administrator as the gaming system 100. In addition, the client server 110 may be dedicated to access only game content that is supported by the gaming system 100. For example, a gaming entity (e.g., a casino) may elect to perform each of these functions in-house, such as providing both the access to the client server 110 and the actual game content and the organization, as well as providing administration of the other servers of the gaming system 100 as well.
The gaming system 100 includes a game routing server 112, an asset server 114, an output format server 116, a metrics server 118, a game rules server 120, a deck server 122, a deck database server 124, an archive server 126, a messages server 128, and an account server 130. Other servers 132 are also contemplated as being included within the gaming system 100. The various servers of the gaming system 100 may be configured to perform the described functions and communicate with each other in the manner that is described in more detail below. In addition, the various servers of the gaming system 100 may be organized in a plurality of different sub-systems that may group the servers according to similar levels of communication and security.
The gaming system 100 may include a first sub-system 101 and a second sub-system 103, such that the various servers may be organized and separated to communicate through a plurality of firewalls 102, 104. The first sub-system 101 may be configured to communicate with the client server 110 through the first firewall 102. For example, the first sub-system 101 may include the game routing server 112, the asset server 114, the output format server 116, and the metrics server 118. The second sub-system 103 may be configured to communicate with the first sub-system 101 through the second firewall 104. The second sub-system 103 may include the game rules server 120, the deck server 122, the deck database server 124, the archive server 126, the account server 130, the messages server 128, as well as one or more other servers 132. In other words, the first firewall 102 separates the client server 110 from the game routing server 112, the asset server 114, the output format server 116, and the metrics server 118.
The second sub-system 103 may be isolated from the client server 110 by the first sub-system 101. As a result, therefore, the client server 110 and the servers of the second sub-system 103 may be configured to communicate with each other only through the first sub-system 101 (and the first firewall 102 and/or second firewall 104, if provided). In other words, the second firewall 104 may further separate the game rules server 120, deck server 122, the deck database server 124, the archive server 126, the messages server 128, the account server 130, as well as other servers 132.
The various servers may be organized with respect to the first firewall 102 and the second firewall 104 in a variety of different combinations according to the different levels of security desired for each server. In other words, the specific organization of the servers with respect to the plurality of firewalls 102, 104 should not be viewed as limiting the scope of present disclosure unless specifically described as such. In addition, the gaming system 100 may include additional sub-systems (not shown) separated by additional firewalls (not shown). For example, a third sub-system, if provided, may be configured to communicate with the second sub-system 103 and this communication may be through a third firewall. In some embodiments, the third sub-system may include external accounts servers (not shown). In addition, more or fewer firewalls may be implemented.
As will be understood, therefore, the first sub-system 101 provides an interface (e.g., a gateway) through which the second sub-system 103 and optionally the third sub-system may communicate with the client server 110. The third sub-system is not shown in
The gaming system 100 provides gaming content and enables secure on-line gaming from the client server 110. In some embodiments, the gaming system 100 does not take wagers or issue payouts. In other words, the gaming system 100 may facilitate on-line casino gaming, but may not be an on-line casino itself. Instead, the gaming system 100 facilitates the play of proprietary card game content owned and controlled by a company offering games and gaming products and services, such as Shuffle Master, Inc. In such an embodiment, the client server 110 may interface with an end user through a web page, an application (e.g., a smartphone or tablet application such as those), or other computer program in order to access the gaming system 100. The client server 110 may be operated by a third party, such as a casino, that links to the gaming system 100 through the client server 110 via a network, such as the internet. As will be described in further detail below, the account server 130 may communicate with an external entity (e.g., a casino) that maintains end user accounts to take bets and make payout distributions. In such an embodiment, the gaming system 100 merely verifies the existence of funds for wagering, and instructs the external end user accounts to execute debits and credits. In some embodiments, the gaming system 100 may take bets and make payout distributions, such as in the case where administrator of the gaming system 100 operates as a casino. As discussed above, the gaming system 100 may be integrated within the operations of a casino rather than separating out functionality (e.g., game content, game play, credits, debits, etc.) among different entities. In addition, for “play for fun” wagering games, the gaming system 100 may issue credits, take bets, manage the balance of the credits according to the game outcomes, but may not permit payout distributions or be linked to play for fun client servers 110 that permit payout distributions. Such credits may be issued for free, through purchase, or for other reasons, without the ability for the player to cash out. Such play for fun wagering games may be played on platforms that do not permit traditional gambling, such as to comply with jurisdictions that do not permit on-line gambling.
The client server 110 may be provided with a relatively small amount of script 111 (
The game routing server 112 is configured to communicate between the client server 110 and the other various servers of the gaming system 100. The game routing server 112 may be further configured to only permit external communication through the first firewall 102 to come from the client server 110. In other words, authorized client servers 110 may be the only outside servers that are authorized (e.g., white listed) through the first firewall 102 to communicate with the game routing server 112. In addition, the client server 110 may not be permitted to communicate directly with any of the other servers of the gaming system 100 other than the game routing server 112 or, in some cases, the asset server 114.
A primary function of game routing server 112 is to route game outcome information to the client server 110 via the first firewall 102 and to further communicate with the other servers of the gaming system 100. In other words, when the client communicates with the client server 110, the client server 110 communicates with the other servers of the gaming system 100 through the game routing server 112. At times, the client server 110 may communicate directly with the asset server 114 as will be described with more detail below. Although direct communication paths are shown in
Referring still to
The game routing server 112 receives inputs into the gaming system 100 from the client server 110. For example, the client server 110 may send data indicating which wagering game is to be played, and game inputs such as player moves (e.g., bets, card requests, holds, etc.). Such inputs may be routed to the appropriate location, such as the game rules server 120 associated with the appropriate wagering game. The game routing server 112 may be scaled (e.g., the number of servers may be increased) to handle different games as new wagering games are released and supported by the gaming system 100 with the addition of additional game rules servers 120. Thus, a plurality of game rules servers 120 may share the game routing server 112. As a result, the more games that are added to the system, the more the cost per player per game may be reduced because resources will be shared among games. Also, as the number of clients and client servers 110 increase the number of game routing servers 112 may be increased. This approach of scaling individual servers according to need for that particular function is unlike that of conventional gaming systems, which tend to duplicate server resources for individual games (e.g., a Texas Hold 'Em variant, blackjack, etc.), which may result greater equipment and hosting expenses.
The game rules server 120 includes game rule information for at least one wagering game stored thereon. The game rules server 120 may be thought of as the game engine that controls the order of game play. For example, game rule information may include the game rules of a particular wagering game and the various stages of play. For example, the game rules include the number and order of cards to be dealt to various positions, such as the different player positions, common card positions, dealer card positions, whether cards may be shown, etc. The game rules may further include the relative ranking of hands in a card game (e.g., poker), whether the player hand is played against a dealer hand or against pay tables, and the pay tables themselves that are used to determine the amount of a payout award. In addition, the game rules may further include wager requirements such as whether wagers are mandatory or optional, the relative size of the wagers, the wager election choices, a comparison of the wager amounts made to table limits, and the like. Through the game rules server 120, the game rules ultimately determine whether the end user wins or loses, while the game routing server 112 determines what to do with such information.
As discussed briefly above, each wagering game supported by the gaming system 100 may have at least one different game rules server 120 associated therewith. In other words, in some embodiments, a set of game rules for any one game may be administered on the game rules server 120. For example, there may be at least one game rules server 120 for blackjack, at least one game rules server 120 for a Texas Hold 'Em variant, and so on. Each game rules server 120 may include game rules dedicated to a specific wagering game and does not comingle such information used by other games. Of course, the scale of the gaming system 100 and the complexity of the games may require a plurality of game rules servers 120 that are dedicated to a particular wagering game. In other embodiments, multiple sets of game rules are administered by the same game rules server 120. In other words, sets of game rules for a plurality of games may be administered by the same game rules server 120. For example, the same game rules server 120 may administer a set of game rules for the Texas Hold 'Em variant as well as a set of game rules for blackjack.
The deck server 122 is configured to provide the processing for generating the random game pieces (i.e., game piece indication) from a defined set of game pieces for the wagering game. For example, the deck server 122 includes a random number generator (RNG) 123 that is configured to randomly generate the game pieces in response to requests made from the game rules server 120 according to the rules of the wagering game being played by the end user. The random number generator 123 may be hardware based, software based, or a combination thereof. The term “random” also includes semi-random and pseudo-random events. The random number generator 123 employed shall pass a sufficient test of randomness. For example, The random number generator 123 may be created at a low-level programming level in order to sufficiently reduce or avoid language specific bugs. In operation, the random numbers may be appropriately seeded, and requests for numbers may not be done sequentially in order to ensure that the number pass an appropriate threshold test for randomness. The deck server 122 may compile a virtual deck of cards by indexing all the possible card values for a desired deck, and selecting at random one of those cards and placing it in a “shuffled” virtual deck. This process of card selection may be continued until all of the virtual cards have been placed in the virtual deck. The random number generator 123 may be implemented through one of a number of public domain and licensable random number generation algorithms, such as the CONVERSE Pseudorandom Number Generator (PRNG) developed by the University of Illinois at Urbana-Champaign of Champaign. Another example is the Park-Miller “minimal standard” PRNG, developed by Stephen K. Park and Keith W. Miller. Other methods are contemplated for ensuring that the random number generator generates a random number that passes the appropriate standard for randomness. In addition, it is recognized that standards for randomness may change over time, and that additional random number generators 123 may be developed for use with the gaming system 100.
The term “deck” is used because many common wagering games employ the use of playing cards, such as poker, Texas Hold 'Em variants, blackjack, among others. As discussed above, a non card-based game may be played that is supported by the gaming system 100. Thus, the term “deck” is not to be interpreted as requiring card deck information unless specifically stated to have such according to the game rules of the specific wagering game to be played. As the gaming system 100 includes an on-line gaming platform, the randomly selected game pieces may be thought of as virtual game pieces, such as virtual cards, virtual dice, virtual wheel positions, etc. Thus, the deck server 122 is configured to output a game piece indication which may comprise the identifier of a virtual card (e.g. the ten of hearts), a random number, one or more dice faces, a virtual wheel position, a number, a color, or the like, as well as combinations thereof. A “virtual shoe” may be referred to herein to describe the functionality of creating a virtual card deck and dispensing virtual cards as requested by the game rules server 120. In other words, the deck server 122 may generate a data file that represents the entire set of game pieces, and track the removal of cards delivered to the game such that the composition of the unused cards is also known at all times. This accounting function may prevent a card of a certain rank and suit from being dealt into the game so that the mathematics of the game is identical to a live card game and is not altered.
Using the example of a card-based game, the random number generator 123 may be used to generate one or more numbers that is used to select the card (or cards) from among the set of cards. One or more numbers may select the number and the suit of the cards. In other words, the deck server 122 serves the function of a virtual shoe to create the deck, and to hold and administer the card data for the wagering game. For example, such card data may include the initial number of cards in the set, the current number of cards in the set, the rank and suit of cards that have been removed from the set and dealt into the wagering game, the number of special cards such as promotional cards inserted into the set, the number of standard cards removed from the set to construct a special set (e.g., for the Spanish 21 game, Canasta, etc.), the number and color combination of hands dealt, the number of cards dealt to each player, the number of players in a round, etc. For poker variants, the set of cards is generally a standard deck of fifty-two cards having four standard suits. If desired, one or more jokers may be included. Blackjack games may be played with one or more combined decks of cards belonging to the set of cards. Common examples of blackjack games include one, two, four, six, or eight decks of cards. Baccarat is usually played with six or eight decks of cards belonging to the set. In the example of a non card-based game (e.g., roulette), the random number generator 123 may generate a number that is used according to the game rules of that wagering game. In creating the deck and administering the wagering game, or otherwise randomly generating the game pieces, the data may be encrypted and stored in the deck database server 124, as described below.
The deck server 122 and the game rules server 120 are separate and distinct servers. As a result, the card deck data is segregated from the game rules data on different servers. In addition, the deck server 122 and the game rules server 120 may be separated to have different access privileges to different sets of employees. Doing so may increase the security of the gaming system 100 as it limits the chances that a single employee has access to both sets of information associated with the game rules server 120 and the deck server 122. Separating the game rules data and the deck data into different servers further adds another level for a hacker to penetrate in order to obtain both sets of data during game play.
Data that is stored in the deck server 122 may be encrypted and is sent to the game rules server 120 in encrypted form, where it is decrypted and used by the game rules server 120. The encryption provides a higher level of security to the gaming system 100. In addition, data generated by the deck server 122 may be withheld from the game rules server 120 until such information is required for the determination of the game outcome, at certain intermediate game determinations, or at a time where it is required to make such information known to the end user.
An example of a wagering game supported by the gaming system 100 is a Hold 'Em poker variant game (also referred to as “Ultimate Texas Hold 'Em” ®) as described in U.S. patent application Ser. No. 11/156,352, filed on Jun. 17, 2005, and published as U.S. Patent Publication No. US 2006/0284376 A1, the entire disclosure of which is incorporated herein by this reference. In such an Ultimate Texas Hold 'Em game, there may be multiple rounds of betting, and multiple steps of card distribution and revelation of cards to the player. The gaming system 100 may be configured to wait to transfer intermediate game information, such as additional card rank and suit information from the deck server 122 to the game rules server 120 and/or the game routing server 112 on an as-needed basis. Additional game information may include, but is not limited to, extra wagers made, decisions to withdraw a wager, decisions to buy a card, decisions to fold, set a hand, a selection of a multiplier, a decision to participate in a bonus event, decisions to take hit cards, roll dice, spin wheels, activate a virtual shuffler to dispense more cards, exchange all or part of a hand with new cards, and any other decision that may be made during play of a wagering game and before conclusion of play.
As cards (or other game pieces) are needed, the game rules server 120 may request them. For example, the game rules server 120 may verify that the appropriate wager has been placed before requesting the next set of information. For example, after confirming an initial wager, the gaming system 100 deals an initial partial hand of cards to each player, whereupon the player may be asked to place another wager prior to receiving a full hand of cards. After receiving verification that the additional wager has been made, additional card data is provided to the game rules server 120. Thus, a game may require a first wager prior to the game routing server 112 delivering partial hand information in a card game to the game rules server 120, or to the client via the client server 110 according to the rules of the wagering game. The partial hand information may be considered intermediate game information. The game may also require information indicating a second wager has been made before delivering additional card information to complete the hand. This additional card information may also be considered intermediate game information.
Some of the intermediate game information may be withheld from the client server 110 as well as the game rules server 120 until all wagers have been completed and the withheld information is needed for the final game outcome determination. In addition, even if a person were to access (e.g., hack) the client server 110 or the game rules server 120 prior to that time, the person would not have access to that card information. As a result, cheating may be more difficult for such unauthorized users. Upon receiving confirmation that the game outcome (or an appropriate intermediate step) to be determined, the game rules server 120 may request the card information regarding the intermediate game information. Preventing the transmission of intermediate game information to the game rules server 120 prior to receiving a wager confirmation ensures that the gaming system 100 does not make a payout on a wager that was not received, and further reduces the risk of the game results being viewed and wagered upon if a person successfully hacks into the client server 110 or even the game rules server 120 for the purpose of retrieving card information or game results in advance of making a wager.
The asset server 114 includes asset data that is to be retrieved and used in the presentation of the wagering games on the client interfaces. In other words, the asset server 114 may deliver content to the client through the client server 110 related to the presentation of the wagering game. For example, asset data may include image data, audio data, video data, and other similar data that may be used by a particular wagering game. As an example, image data may include the appearance of the background layout for a wagering game. For a wagering game such as a Texas Hold 'Em variant, the background layout may appear as a casino table surface. In addition, image data may include including a copyrighted and/or trademarked game games and logos of the wagering game or an entity (e.g., a specific casino, website, application, etc.), as well as the desired appearance of the card backs and card faces. The various types of asset data requested by the client server 110 may depend on the wagering game, the entity, or other desires. Although the asset server 114 is shown as being behind the first firewall 102, in some embodiments, the asset server 114 may be communicate with the client server 110 outside of the first firewall 102.
The output format server 116 is configured to format the game data, wagering data, and graphics files to accommodate different end user devices of the client such that the client receives all data in a format that the client can process. For example, end user devices may include personal computers (PCs), smart phones (e.g., an iPhone, Android, Blackberry, etc.), laptops, tablets, gaming machines, and other electronic devices that may communicate with the client server 110 for a user to play a wagering game. The output format server 116 may detect the type of end user device, as well as the operating system, and configure the data as appropriate for the client to process.
The metrics server 118 is a business intelligence control system that analyzes usage of each server of the gaming system 100, enables data mining, generates reports, and detects system weaknesses and/or system failures. Each of the various servers of the gaming system 100 may communicate with the metrics server 118. The client server 110 may also communicate with the metrics server 118 regardless of whether or not the client server 110 is part of the gaming system 100. Each of the various servers self report information regarding its actions to the metrics server 118. For example, the client server 110 may send information regarding its actions to the metrics server 118. For example, the client server 110 may send information of actions such as “began load,” “load complete,” “started,” and “ended action” along with payload data containing the time started, system specifications, and any other information that a business intelligence group may deem relevant. As another example, the game rules server 120 may self report information regarding its actions at the end of each hand, such as reporting the game outcome along with payload data like the amount wagered, the amount won, any bonuses, and any other information the business intelligence group may deem relevant. The other various servers of the gaming system 100 may likewise self report information regarding their actions. The data stored by the metrics server 118 may be mined to generate reports for review by the business intelligence group. Such reports may be available on demand, or according to a set schedule.
The deck database server 124 is configured to receive and store game piece indications (e.g., deck data) from the deck server 122 to maintain an historical record. Thus, the deck database server 124 may communicate directly with the deck server 122 without routing through the game routing server 112. The deck data that is stored in the deck database server 124 may be data that is desired to persist during the operation of the wagering game or that is not resolved in a single client communication. For example, in a Texas Hold 'Em variant game, multiple turns are performed prior to finishing a game. Deck data from intermediate turns may be stored in the deck database server 124. The deck data stored in the deck database server 124 may be analyzed, as a security measure. For example, the client server 110 may want a running report confirming that each virtual shoe used to deal blackjack was verified as having a complete set of cards at the beginning of the deal, that the correct cards remain in the virtual shoe after the cut card appears, and that the dispensed cards equal the composition of the set of cards used by the virtual shoe. The deck data stored in the deck database server 124 may be stored independently from deck data stored elsewhere in the gaming system 100. The deck database server 124 may also be used to retain card information (e.g., card sets, card usage, etc.) from current or previous rounds of play to verify jackpot hands. This card information may also be transferred to the archive server 126 described below.
The messages server 128 is configured to store a list of messages for display to the end user, and send the appropriate message to the client server 110 upon request. Examples of system messages for display to end users may include an indication that a particular wager made was not placed, unavailable, is deficient, an indication regarding the status of the game, that an award has been earned, as well as other messages. The various servers of the gaming system 100 may request that messages be sent to the client. The game routing server 112 may process these message requests, route the message requests to the messages server 128, and receive the appropriate messages. The game routing server 112 may determine when to deliver the messages to the client server 110, such as prioritizing the transmission of a plurality of received messages to ensure that critical messages are transmitted first.
The account server 130 includes data such as user information (e.g., user names, passwords, email address, other user information, etc.), user validation (e.g., logging in, logging out, timing out, etc.), as well as user financial information (e.g., account balance, currency conversion, credits, debits, etc.). As discussed above, in some embodiments the gaming system 100 may not actually perform the transfers of funds. In such an embodiment, the account server 130 acts as an intermediary with an external account to confirm that funds are available for wagering and to communicate whether funds should be debited or credited and the end of the wagering game. The account server 130 may integrate with multiple different account platforms (e.g., Ongame, CyberArts, OpenBet, etc.) for communicating with the external accounts. The gaming system 100 may include a separate account server 130 for each account platform type. Therefore, depending on the integrated partner (if any) of the gaming system 100, the account server 130 may be an internal account system or an abstracted library to an external account system. The account server 130 also manages player accounts in play for fun wagering activities that do not permit a player to cash out won credits. For example, the account server 130 may communicate with external accounts that support play for fun wagering activities, which may be different than the external accounts that support wagering activities.
The account server 130 may cache certain types of player data for repeat access. For example, basic information that can uniquely identify a player might be stored for a period (e.g., days). The account balance of the external account may not be cached, and may be retrieved on demand at each wager.
The archive server 126 may include various data collected from the gaming system 100. For example, the deck data generated in the deck server 122 may be stored in an archived deck database of the archive server 126 after a full wagering game is resolved. Because the full wagering game is completed, the deck data stored in the archive server 126 may be unsecured. For example, the deck data may be decrypted and stored in the archive server 126 along with other game data. The archive server 126 may be selectively accessible to customer service and business intelligence employees. As an example, if a customer service representative receives a call, they may need unsecured access to verify and check the deck data and the game data to see if there was a mistake in the game play, and resolving player and/or casino client payout disputes. The data stored in the archive server 126 may be held independently of any corresponding data held in other parts of the gaming system 100. In other embodiments, the data stored in the archive server 126 may be secured.
The archive server 126 may also perform post processing of the deck data to detect cheating by comparing deck data stored in the archive server 126 with deck data stored in a secured location, such as the deck server 122 or the deck database server 124. The archive server 126 may also have the ability to call for “shift keys” from each of the servers of the gaming system 100, and in the absence of receiving the keys from the other processors (indicating an acceptable game state), the archive server 126 may shut down the gaming system 100 as a further security measure. Arrows 127 are shown to indicate that the archive server 126 may communicate with each of the servers of the gaming system 100.
Other servers 132 are also contemplated that may be part of the gaming system 100. An example of such another server 132 includes a social server. A social server may be configured to receive information regarding the game outcome and share that information with a social media platform (e.g., Facebook, Google Plus, Twitter, etc.). For example, if an end user wins a poker hand, that information may be posted on the end user's Facebook wall. Another example of another server 132 is a player's club server. A player's club server may credit the end user with rewards such as reward points for certain events, such as frequent gaming.
As discussed above, the client server 110 may be a “thin client.” As that term is used herein, the client server 110 may be little more than a script player. The client server 110 may simply send requests to the gaming system 100 rather than performing logic itself. In other words, the script stored in the client server 110 may merely include calls to functions that are externally defined. While the client may receive player inputs, the inputs are merely passed on to the game routing server 112, and the bulk of the processing of the game play is performed in the game rules server 120 and the deck server 122 described more fully below. The client may receive intermediate data and final game outcome information to display after such is determined by the game rules server 120. In addition, the externally defined functions may determine what information is displayed by the client as well as how it is displayed. Also, the assets are stored separately from the client server 110 on the asset server 114, which the client server 110 downloads while running the script. As a result, if certain features and displays are desired to be changed, the administrator of the gaming system 100 may do so without needing access to each and every client server 110 that may access the gaming system 100. As a result, modifications to the gaming system 100 may be done more efficiently, particularly for embodiments that include a third party entity that runs the client server 110 as a business partner with the administrator of the gaming system 100.
General operation of the gaming system 100 will now be discussed. The script for the client may be initiated, such as by being embedded in a webpage, opened by a computer file, opened as an application on a mobile device, etc. The end user interfaces with the client server 110 to play the wagering game. As discussed above, the script driver stored in the client server 110 enables the client server 110 communicate with the gaming system 100 to begin a wagering game. The client server 110 may initiate a game by communicating with the game rules server 120 through the game routing server 112. In response to initiating the desired wagering game, the script driver further enables the client server 110 to receive asset files (e.g., images, video, audio, etc.) from a game library in the asset server 114, and to transfer the corresponding asset files to the client server 110 to be presented by the end-user's game display. As an example, the client server 110 may inform the game routing server 112 that a game is to be initiated. The game routing server 112 may query the asset server 114 to determine what assets are needed to run the desired wagering game and return the asset list to the client server 110. The client server 110 may receive an asset list from the game routing server 112 for the particular wagering game selected. The client server 110 may request the assets directly from the asset server 114 according to the asset list provided. Given such an asset list, the game routing server 112 may cache the asset list for future use if contacted by the client server 110 or another client server 110 to initiate another wagering game of the same type.
Once set up of the wagering game is complete, the client server 110 may communicate to the game routing server 112 that the wagering game is ready to begin. The end user may play wagering game according to the game rules stored in the game rules server 120. As discussed above, the game routing server 112 may route information between the client server 110 and between the various servers of the gaming system 100. For example, the end user may input information (i.e., press buttons on the display) that communicate to the game routing server 112 the desired actions. As a thin client, the client server 110 may not have the logic to know what the actions mean, just that a certain button is selected. The game rules server 120 is configured to interpret that information for the particular wagering game being played. Also, as discussed above, the game rules server 120 and the deck server 122 communicate to request the random game pieces according to the game play as defined in the game rules of the wagering data stored in the game rules server 120. The random game pieces (e.g., deck data) may be shared with the game rules server 120 and the client server 110 at the appropriate times according to the game play, wagers, and other factors. Accordingly, the game rule data and game outcome data are kept separate and not accessible without authorization.
As an example of game play, the game rules server 120 may include a plurality of different states that are moved between depending on the game. A first state may include the selection of the wagering game to be played. The next state may be to wait for the bet to be placed. If it has not done so already, the account server 130 may communicate with the external accounts to verify the funds for a player (i.e. an end user) are available to be bet. After the bet is placed, a game piece (e.g., such as one or more cards) may be issued to the player. Depending on the specific game rules, additional bets may be made and intermediate game pieces may be issued. Another state may be to do a final verification of the bets for sufficient funds for the player, after which the final game pieces may be sent to the game rules server 120 and the game outcome may be determined. Credits or debits are made to the end user's account through the account server 130 depending on the outcome of the wagering game and the bet and/or additional bet placed by the end user.
The gaming system 100 includes a plurality of different server components, each serving a separate function. The gaming system 100 is also separated in different levels of sub-systems 101, 103 that have limited communication therebetween. For example, communication from the client server 110 to the servers of the second sub-system 103 may occur through the game routing server 112 adding an extra level (and extra firewall) of security to the more sensitive components of the gaming system 100, such as the game rules server 120, the deck server 122 and the account server 130. These sensitive components of the gaming system 100 are, therefore, isolated from the client server 110, and any attempts that may be made to gain unauthorized access to the second sub-system 103 via the client server 110, also require passing the security measures implemented for the first sub-system 101. Therefore, the risks of an anomaly caused by an intruder being undetected may be reduced because an intruder may need to access multiple servers undetected in order to successfully hide any alterations made to one of the servers (such as the deck server 122, the game rules server 120, or the account server 130).
In addition to the security benefits described above, embodiments of the present disclosure may result in cost benefits as well. For example, scaling of the gaming system 100 may be performed in a more efficient manner according to the embodiments of the present disclosure. By separating the data and functions performed into separate servers, some of the servers may be duplicated to increase the scale of the gaming system 100 without the need to duplicate or replace other servers having other functions. For example, the game rules server 120 may be duplicated as additional games are added to the gaming system 100, as additional client servers 110 are added to the gaming system 100, or when additional players access the gaming system 100. On the other hand, other system servers may not require scaling (e.g., duplication) at the same time the game rules server 120 demand increases. As another example, changing the assets stored on the asset server 114 may be accomplished with only minor modifications (if any) to the other servers of the first sub-system 101 (such as updating the list of assets available), and without any of the servers of the second sub-system 103 requiring modification.
Servers may also be scaled at different rates. For example, the account server 130 may need to increase in scaling prior to the need to increase the scaling of the asset server 114. As another example, as different end user devices are developed, the output format server 116 may require reconfiguration, but not the balance of the gaming system 100. Scaling may occur as new features or information are changed by the administrator. Increasing and decreasing the scaling of the individual servers of the gaming system 100 may also be performed as a result of a need to keep up with the changing demand during player usage of the gaming system 100. Conventional approaches that essentially combine functions of all of the above servers into a single non-separated server may result in unnecessary duplication of data as the system is scaled to meet demand.
It is contemplated that embodiments of the present disclosure include architectures wherein at least some of the functionality of the various servers may be combined. Doing so, however, may at least partially reduce some of the efficiencies of scalability described above. An example of such includes a server that at least partially combines the functionality of two or more of the metrics server 118, the messages server 128, and the account server 130. Another example includes a server that at least partially includes the functionality of two or more of the game routing server 112, the game rules server 120, and the output format server 116.
In addition, another method of segregating data and functions into a plurality of different servers may include segregation of servers by whether or not the data or software code is regulated by gaming regulation authorities. Such segregation may reduce costs associated with satisfying regulatory requirements over time.
As discussed above, the gaming system 100 may include wagering games on a play for pay basis, wherein the gaming system 100 manages accounts (whether internal or external to the gaming system 100) that are adjusted according to the game outcome, and that permit a player to cash out. In some embodiments, the gaming system 100 may include wagering games on a play for fun basis, wherein the gaming system 100 manages accounts (whether internal or external to the gaming system 100) that are adjusted according to the game outcome, and that do not permit a player to cash out. For example, a player may be issued (e.g., through purchase) credits (or another symbol) that may be used to place wagers during the wagering game. During game play, the credits may be increased or decreased according to the game outcome. As the credits expire, the player may need additional credits before continuing additional play. The additional credits may be purchased or issued through other methods, as described above.
The play for pay feature and the play for fun feature may be at least partially integrated into the same gaming system 100. In other words, the gaming system 100 may be configured as a dual-purpose internet platform such that the various servers (e.g., game routing server 112, game rules server 120, deck server 122, etc.) of the gaming system 100 may be shared by client servers 110 simultaneously running play for pay and play for fun wagering games. The dual-purpose internet gaming platform is configured to run a play for pay wagering game and a play for fun wagering game according to an at least partially integrated architecture that manages player accounts. The play for pay wagering game enables a user to cash out from the player accounts, and the play for fun wagering game does not enable the user to cash out from the player accounts. Partial integration means that at least two of the servers of the gaming system 100 are shared for performing play for pay and play for fun features. For example, the game rules server 120 and the deck server 122 may be used to perform both play for pay and play for fun features. In some embodiments, full integration may be achieved for all servers of the gaming system 100 to perform play for pay and play for fun features. Of course, in some embodiments, the play for pay and the play for fun features may have their own separate gaming systems 100. In other words, each gaming system 100 may be configured as a single-purpose platform to run the play for pay and the play for fun features, if both sets of features are present. Other embodiments may include at least a partial integration of gaming systems 100 that run both play for pay and play for fun features, such that one or more servers are shared.
In some embodiments, the client servers 110 that run the play for pay features of the dual-use internet platform may be separate from the client servers 110 that run the play for fun features of the dual-purpose platform. For example, the dual-purpose internet gaming platform may receives function calls from different client servers 110 to run the play for pay wagering game and the play for fun wagering game. In other embodiments, the client servers 110 that run the play for pay and the play for fun features may be the same. For example, the client servers 110 may be configured to send functions calls associated with both the play for pay wagering game and the play for fun wagering game from the same client server 110.
As discussed above, the client server 110 may communicate with the servers of the first sub-system 101, such as through the first firewall 102. For example, the client server 110 may be authorized to communicate with the game routing server 112, the asset server 114, the output format server 116, and the metrics server 118, whereas other servers may not be authorized for such communication. The asset server 114 may receive requests from the client server 110 for delivering assets to the client as discussed above. The game routing server 112 may receive instructions from the client server 110 related to playing a particular wagering game supported by the gaming system 100B. Communication from the game routing server 112 back to the client server 110 may flow through the output format server 116, which may be configured to prepare the data in an appropriate format to be processed by the end user device coupled with the client server 110. The client server 110 may include a client program embedded in a web page (e.g., casino web page) that is operable in a web browser. The client program may be supported by an inline floating frame (iFrame) or div elements. The client program may be written in an appropriate language such as HTML or Flash. As discussed above, the client server 110 may be provided with a relatively small amount of script 111 (e.g., JavaScript), also referred to as a “script driver,” including scripting language that controls the interfacing of the client server 110 with the gaming system 100. The client server 110 may be a thin client to provide the client with the ability to communicate with the gaming system 100 by sending requests to the gaming system 100 rather than performing logic itself. In other words, the script 111 may merely include calls to functions that are externally defined.
As further discussed above, the game routing server 112 may communicate with the servers of the second sub-system 103, such as through the second firewall 104. For example, the game routing server 112 may be authorized to communicate with the game rules server 120, the messages server 128, the account server 130, and possibly the other servers 132, whereas non-authorized servers may not be permitted for such communication. In some embodiments, the deck server 122 may not be configured to communicate directly with the game routing server 112. Instead, the game rules server 120 may be authorized to communicate with the deck server 122.
The other servers 132 shown in
The deck database server 124 and the archive server 126 are not shown in
The game routing server 112 may route information between the servers of the second sub-system 103 and the client server 110 during game play. The game rules server 120 may include rules for one or more wagering games, such as the Ultimate Texas Hold 'Em® (UTH) poker game, Three Card Poker (3CP) game, and other games. The wagering games may be card based, or non-card based as previously discussed. The game rules server 120 may communicate with the deck server 122 to generate the game piece indication as requested by the game rules server 120. The deck server 122 is configured to generate and output the game piece indication to the game rules server 120 in response to the request, such that the game piece indication is unavailable to the game rules server 120 until requested. In other words, the game piece indication information may not be available to the game rules server 120 until required for determining game outcome information at the desired time. For example, the deck server 122 may share the game piece indication information with the game rules server 120 after the game rules server 120 verifies that a proper wager has been made, and that advancing the game to the next decision by the player is appropriate, or that determining the final game outcome information is appropriate. Prior to such a determination, the deck server 122 may wait to provide such data to the game rules server 120. The verification of a proper wager may include the game rules server 120 communicating with the account server 130 to verify that the user account has sufficient funds to cover the wager.
As discussed above, the account server 130 may communicate with external accounts (e.g., casino account servers 140) that perform the actual maintenance of the user accounts, including executing debits, credits, and maintaining the funds of the end user. Thus, the casino account servers 140 and other external servers may be operated by one or more third parties to the gaming system 100B and may be considered part of a third sub-system 105, which may not be part of the gaming system 100B. In addition, the account server 130 may communicate with the casino account servers 140 and other external servers through a third firewall 106. In some embodiments, such as when a casino may operate the entire operations including the game play, content, client support, and account management and activity, the casino account servers 140 may be included as part of the gaming system 100B. The casino account servers and other external servers may be considered a third sub-system 105 of the gaming system 100B.
The unregulated servers 202, 203 may include one or more of the asset server 114, the output format server 116, the metrics server 118, the deck database server 124, the archive server 126, the messages server 128, the account server 130, and other servers 132, which are individually shown and described with respect to
The embodiments of the present disclosure are described in terms of the various servers of the gaming system 100 (
Each of the various server functions of the gaming system may be hosted by at least one of the plurality of servers 310, 320, 330, 340, 350; however, only a portion of the various servers of the gaming system is actually shown, for convenience. For example, only the game routing server 112, the asset server 114, the output format server 116, the metrics server 118, the game rules server 120, and the deck server 122 are shown. It should be understood, however, that the plurality of servers 310, 320, 330, 340, 350, as a whole, host the other servers of the gaming systems described above. In addition, each of the plurality of servers 310, 320, 330, 340, 350 are to be understood as being physical servers of the server architecture 300, whereas the servers (e.g., 112, 114, 116, 118, 120, 122, and others) of the gaming system are to be understood as “virtual servers.” That is, the server architecture 300 generates instances of the servers of the gaming system to have the relationships with each other as described above. For example, a first server 310 may generate virtual servers (i.e., instances) for the game routing server 112, the asset server 114, the output format server 116, the metrics server 118, while a third server 330 may generate virtual servers for the game rules server 120, and the deck server 122. The other servers (e.g., second server 320, fourth server 340, fifth server 350, and so on) may generate and host virtual servers for the other server functions of the gaming system. When the virtual servers are generated, the server architecture 300 does so according to the communication rules and logical separation set by the architecture rules. As a result, the various servers of the gaming system may share physical resources with each other while still maintaining the logical separation and communication relationships described above.
The specific configuration shown is to be understood as an example of one embodiment, and individual server functions may be combined within the same physical server according to any combination of the various servers of the gaming system. For example, even through the first server 310 is shown to generate virtual servers for the game routing server 112, the asset server 114, the output format server 116, the metrics server 118, another combination may include another combination such as the account server 130, the game routing server 112, the game rules server 120, the deck server 122, and the messages server 128. Thus, virtual servers for the first sub-system 101 may be combined with virtual servers for the second sub-system 103. Therefore, each of the physical servers 310, 320, 330, 340, 350 may generate and host virtual servers of any number or combination according to the capacity of the server.
During operation of the gaming system, the usage may vary such that one or more of the individual virtual servers may fluctuate in needed capacity. For example, at one point in time, the third server 330A may host a single instance each of the game rules server 120 and the deck server 122. At this point in time, the third server 330A may have unused server space 335 that is available for use, if needed. At another point in time, the usage of the gaming system may increase. The server architecture 300 may determine that another instance for each of the game rules server 120 and the deck server 122 is needed to meet the increased usage demand of the gaming system. As a result, the third server 330B may generate another instance for each of the game rules server 120 and the deck server 122 to occupy the unused server space 335 during that time of increased demand. As usage fluctuates over time, the server architecture 300 may increase and decrease the number of instances of the virtual servers for the gaming system to adjust in real time to the demands of the gaming system.
Embodiments of the present disclosure include a gaming system for enabling secure on-line gaming through a client server. The gaming system comprises a gaming platform to communicate with a client server to support play of a wagering game by an end user. The gaming platform comprises a game rules server configured to administer a set of game rules for the wagering game, and a deck server to randomly select game pieces according to the set of game rules.
Another embodiment of the present disclosure includes a network gaming architecture. The network gaming architecture comprises a plurality of regulated servers that require validation from gaming authorities for reconfiguration of each of the plurality of regulated servers, and at least one unregulated server that does not require validation from gaming authorities for reconfiguration of the at least one unregulated server. The regulated servers include a game rules server storing game rules for a wagering game, and a deck server coupled with the game rules server. The deck server is configured to randomly select game pieces for the wagering game in response to requests received from the game rules server. The at least one unregulated server is configured to support an additional function of the gaming system.
Another embodiment of the present disclosure includes a client server for accessing a remote gaming engine, the client server comprising a computer readable medium having instructions stored thereon. When executed by a processor, the instructions cause the processor to establish a communication link with a remote gaming engine to execute a wagering game, and receive inputs from an end user and transmit the inputs to the remote gaming engine during play of the wagering game. The client server acts as a thin client to the remote gaming engine such that the remote gaming engine performs game play processing.
In another embodiment of the present disclosure, a method of enabling the play of on-line wagering games is disclosed. The method comprises providing code on an external client server to enable access to an on-line wagering platform having a game rules server and a deck server, receiving at least an indication of a placed wager from the external client server, randomly generating at least one number in the deck server, the at least one number used for selecting a virtual game piece for an on-line wagering game, determining a game outcome on the on-line wagering platform according to game rules stored in the game rules server, and transmitting the game outcome information to the external client server.
In another embodiment of the present disclosure, a dual-purpose internet gaming platform is configured to run both a play for pay wagering game and a play for fun wagering game according to an at least partially integrated architecture that manages player accounts. The play for pay wagering game enables a user to cash out from the player accounts, and the play for fun wagering game does not enable the user to cash out from the player accounts.
In another embodiment, a system for the provision of gaming over a network is disclosed. The system comprises a game rules server configured to receive an input associated with a game and to output a game outcome based on one or more game rules and a game piece indication, and a deck server separate from, and in communication with, the game rules server. The game rules server is further configured to request the game piece indication from the deck server. The deck server is configured to generate and output the game piece indication to the game rules server in response to the request, such that the game piece indication is unavailable to the game rules server until requested.
In another embodiment, a method for the provision of gaming over a network is disclosed. The method comprises receiving, at a game rules server, an input associated with a game. The method further comprises outputting, from the game rules server, a game outcome based on one or more game rules and a game piece indication. The method further comprises requesting, at the game rules server, the game piece indication from a deck server, and generating and outputting the game piece indication to the game rules server from the deck server in response to the request, such that the game piece indication is unavailable to the game rules server until requested, wherein the deck server is separate from and in communication with the game rules server.
Another embodiment includes a gaming system for enabling secure on-line gaming through a client server. The gaming system comprising a gaming platform to communicate with a client server to support play of a wagering game by an end user. The gaming platform includes a game engine configured to administer a set of game rules for the wagering game and to randomly select game pieces according to the set of game rules, and a game routing server separate from the game engine. The game routing server is configured to route communication between the client server and the game engine.
While the present disclosure has been described herein with respect to certain illustrated embodiments, those of ordinary skill in the art will recognize and appreciate that the present disclosure is not so limited. Rather, many additions, deletions, and modifications to the illustrated and described embodiments may be made without departing from the scope of the invention as hereinafter claimed along with their legal equivalents. In addition, features from one embodiment may be combined with features of another embodiment while still being encompassed within the scope of the invention as contemplated by the inventors.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4339798 | Hedges et al. | Jul 1982 | A |
| 4373726 | Churchill et al. | Feb 1983 | A |
| 4592377 | Paulsen et al. | Jun 1986 | A |
| 4725079 | Koza et al. | Feb 1988 | A |
| 4832341 | Muller et al. | May 1989 | A |
| 4948138 | Pease et al. | Aug 1990 | A |
| 5007649 | Richardson | Apr 1991 | A |
| 5083800 | Lockton | Jan 1992 | A |
| 5179517 | Sarbin et al. | Jan 1993 | A |
| 5199710 | Lamle | Apr 1993 | A |
| 5258837 | Gormley | Nov 1993 | A |
| 5275400 | Weingardt et al. | Jan 1994 | A |
| 5321241 | Craine | Jun 1994 | A |
| 5324035 | Morris et al. | Jun 1994 | A |
| 5326104 | Pease et al. | Jul 1994 | A |
| 5386103 | DeBan et al. | Jan 1995 | A |
| 5398932 | Eberhardt et al. | Mar 1995 | A |
| 5413353 | Demarest et al. | May 1995 | A |
| 5472194 | Breeding et al. | Dec 1995 | A |
| 5493613 | Denno et al. | Feb 1996 | A |
| 5505449 | Eberhardt et al. | Apr 1996 | A |
| 5507489 | Reibel et al. | Apr 1996 | A |
| 5562284 | Stevens | Oct 1996 | A |
| 5580311 | Haste, III | Dec 1996 | A |
| 5603502 | Nakagawa | Feb 1997 | A |
| 5605334 | McCrea, Jr. | Feb 1997 | A |
| 5605506 | Hoorn et al. | Feb 1997 | A |
| 5613680 | Groves et al. | Mar 1997 | A |
| 5613912 | Slater | Mar 1997 | A |
| 5643086 | Alcorn et al. | Jul 1997 | A |
| 5655961 | Acres et al. | Aug 1997 | A |
| 5707286 | Carlson | Jan 1998 | A |
| 5707287 | McCrea, Jr. | Jan 1998 | A |
| 5737418 | Saffari et al. | Apr 1998 | A |
| 5741183 | Acres et al. | Apr 1998 | A |
| 5745110 | Ertemalp | Apr 1998 | A |
| 5759102 | Pease et al. | Jun 1998 | A |
| 5770533 | Franchi | Jun 1998 | A |
| RE35864 | Weingardt | Jul 1998 | E |
| 5779545 | Berg et al. | Jul 1998 | A |
| 5800268 | Molnick | Sep 1998 | A |
| 5813912 | Shultz | Sep 1998 | A |
| 5823879 | Goldberg et al. | Oct 1998 | A |
| 5830067 | Graves et al. | Nov 1998 | A |
| 5830068 | Brenner et al. | Nov 1998 | A |
| 5830069 | Soltesz et al. | Nov 1998 | A |
| 5850447 | Peyret | Dec 1998 | A |
| 5851149 | Xidos et al. | Dec 1998 | A |
| 5890963 | Yen | Apr 1999 | A |
| 5895451 | Yamade et al. | Apr 1999 | A |
| 5905847 | Kobayashi et al. | May 1999 | A |
| 5911626 | McCrea, Jr. | Jun 1999 | A |
| 5957776 | Hoehne | Sep 1999 | A |
| 5971851 | Pascal et al. | Oct 1999 | A |
| 5974135 | Breneman et al. | Oct 1999 | A |
| 5999808 | LaDue | Dec 1999 | A |
| 6001016 | Walker et al. | Dec 1999 | A |
| 6042150 | Daley | Mar 2000 | A |
| 6047322 | Vaid et al. | Apr 2000 | A |
| 6068553 | Parker | May 2000 | A |
| 6077161 | Wisler | Jun 2000 | A |
| 6080063 | Khosla | Jun 2000 | A |
| 6089980 | Gauselmann | Jul 2000 | A |
| 6093103 | McCrea, Jr. | Jul 2000 | A |
| 6102799 | Stupak | Aug 2000 | A |
| 6104815 | Alcorn et al. | Aug 2000 | A |
| 6106396 | Alcorn et al. | Aug 2000 | A |
| 6110041 | Walker et al. | Aug 2000 | A |
| 6110043 | Olsen | Aug 2000 | A |
| 6117012 | McCrea, Jr. | Sep 2000 | A |
| 6135887 | Pease et al. | Oct 2000 | A |
| 6142872 | Walker et al. | Nov 2000 | A |
| 6146273 | Olsen | Nov 2000 | A |
| 6149522 | Alcorn et al. | Nov 2000 | A |
| 6152824 | Rothschild et al. | Nov 2000 | A |
| 6165069 | Sines et al. | Dec 2000 | A |
| 6166763 | Rhodes et al. | Dec 2000 | A |
| 6168523 | Piechowiak et al. | Jan 2001 | B1 |
| 6183366 | Goldberg et al. | Feb 2001 | B1 |
| 6185184 | Mattaway et al. | Feb 2001 | B1 |
| 6186892 | Frank et al. | Feb 2001 | B1 |
| 6210274 | Carlson | Apr 2001 | B1 |
| 6210277 | Stefan | Apr 2001 | B1 |
| 6217447 | Lofink et al. | Apr 2001 | B1 |
| 6219836 | Wells et al. | Apr 2001 | B1 |
| 6234898 | Belamant et al. | May 2001 | B1 |
| 6244958 | Acres | Jun 2001 | B1 |
| 6251014 | Stockdale et al. | Jun 2001 | B1 |
| 6254483 | Acres | Jul 2001 | B1 |
| 6254484 | McCrea, Jr. | Jul 2001 | B1 |
| 6256651 | Tuli | Jul 2001 | B1 |
| 6264561 | Saffari et al. | Jul 2001 | B1 |
| 6272223 | Carlson | Aug 2001 | B1 |
| 6275586 | Kelly | Aug 2001 | B1 |
| 6279910 | de Keller | Aug 2001 | B1 |
| 6287202 | Pascal et al. | Sep 2001 | B1 |
| 6302793 | Fertitta, III et al. | Oct 2001 | B1 |
| 6312332 | Walker et al. | Nov 2001 | B1 |
| 6319125 | Acres | Nov 2001 | B1 |
| 6325375 | Potter et al. | Dec 2001 | B1 |
| 6336859 | Jones et al. | Jan 2002 | B2 |
| 6346044 | McCrea, Jr. | Feb 2002 | B1 |
| 6362836 | Shaw et al. | Mar 2002 | B1 |
| 6380953 | Mizuno | Apr 2002 | B1 |
| 6383076 | Tiedeken | May 2002 | B1 |
| 6389126 | Bjornberg et al. | May 2002 | B1 |
| 6394900 | McGlone et al. | May 2002 | B1 |
| 6400272 | Holtzman et al. | Jun 2002 | B1 |
| 6401099 | Koppolu et al. | Jun 2002 | B1 |
| 6409602 | Wiltshire et al. | Jun 2002 | B1 |
| 6439996 | LeMay et al. | Aug 2002 | B2 |
| 6443839 | Stockdale et al. | Sep 2002 | B2 |
| 6459882 | Palermo et al. | Oct 2002 | B1 |
| 6460848 | Soltys et al. | Oct 2002 | B1 |
| 6464584 | Oliver | Oct 2002 | B2 |
| 6488581 | Stockdale | Dec 2002 | B1 |
| 6488585 | Wells et al. | Dec 2002 | B1 |
| 6490285 | Lee et al. | Dec 2002 | B2 |
| 6503147 | Stockdale et al. | Jan 2003 | B1 |
| 6505772 | Mollett et al. | Jan 2003 | B1 |
| 6508709 | Karmarkar | Jan 2003 | B1 |
| 6508710 | Paravia et al. | Jan 2003 | B1 |
| 6516350 | Lumelsky et al. | Feb 2003 | B1 |
| 6517435 | Soltys et al. | Feb 2003 | B2 |
| 6517436 | Soltys et al. | Feb 2003 | B2 |
| 6520857 | Soltys et al. | Feb 2003 | B2 |
| 6527271 | Soltys et al. | Mar 2003 | B2 |
| 6527638 | Walker et al. | Mar 2003 | B1 |
| 6530836 | Soltys et al. | Mar 2003 | B2 |
| 6530837 | Soltys et al. | Mar 2003 | B2 |
| 6533276 | Soltys et al. | Mar 2003 | B2 |
| 6533658 | Walker et al. | Mar 2003 | B1 |
| 6533662 | Soltys et al. | Mar 2003 | B2 |
| 6575833 | Stockdale | Jun 2003 | B1 |
| 6578847 | Hedrick et al. | Jun 2003 | B1 |
| 6579180 | Soltys et al. | Jun 2003 | B2 |
| 6579181 | Soltys et al. | Jun 2003 | B2 |
| 6581747 | Charlier et al. | Jun 2003 | B1 |
| 6595857 | Soltys et al. | Jul 2003 | B2 |
| 6607441 | Acres | Aug 2003 | B1 |
| 6609978 | Paulsen | Aug 2003 | B1 |
| 6612928 | Bradford et al. | Sep 2003 | B1 |
| 6629184 | Berg et al. | Sep 2003 | B1 |
| 6638170 | Crumby | Oct 2003 | B1 |
| 6641484 | Oles et al. | Nov 2003 | B2 |
| 6645077 | Rowe | Nov 2003 | B2 |
| 6652378 | Cannon et al. | Nov 2003 | B2 |
| 6656048 | Olsen | Dec 2003 | B2 |
| 6663490 | Soltys et al. | Dec 2003 | B2 |
| 6675152 | Prasad et al. | Jan 2004 | B1 |
| 6676522 | Rowe et al. | Jan 2004 | B2 |
| 6682421 | Rowe et al. | Jan 2004 | B1 |
| 6682423 | Brosnan et al. | Jan 2004 | B2 |
| 6685564 | Oliver | Feb 2004 | B2 |
| 6685567 | Cockerille et al. | Feb 2004 | B2 |
| 6688979 | Soltys et al. | Feb 2004 | B2 |
| 6699128 | Beadell et al. | Mar 2004 | B1 |
| 6702291 | Grebler et al. | Mar 2004 | B2 |
| 6712695 | Mothwurf et al. | Mar 2004 | B2 |
| 6712696 | Soltys et al. | Mar 2004 | B2 |
| 6712702 | Goldberg et al. | Mar 2004 | B2 |
| 6718361 | Basani et al. | Apr 2004 | B1 |
| 6722985 | Criss-Puszkiewicz et al. | Apr 2004 | B2 |
| 6728740 | Kelly et al. | Apr 2004 | B2 |
| 6743102 | Fiechter et al. | Jun 2004 | B1 |
| 6746330 | Cannon | Jun 2004 | B2 |
| 6749510 | Giobbi | Jun 2004 | B2 |
| 6752312 | Chamberlain et al. | Jun 2004 | B1 |
| 6755741 | Rafaeli | Jun 2004 | B1 |
| 6758751 | Soltys et al. | Jul 2004 | B2 |
| 6795858 | Jain et al. | Sep 2004 | B1 |
| 6800029 | Rowe et al. | Oct 2004 | B2 |
| 6811488 | Paravia et al. | Nov 2004 | B2 |
| 6817948 | Pascal et al. | Nov 2004 | B2 |
| 6823419 | Berg et al. | Nov 2004 | B2 |
| 6837789 | Garahi et al. | Jan 2005 | B2 |
| 6846238 | Wells | Jan 2005 | B2 |
| 6848994 | Knust et al. | Feb 2005 | B1 |
| 6854085 | Morse | Feb 2005 | B1 |
| 6866581 | Martinek et al. | Mar 2005 | B2 |
| 6866586 | Oberberger et al. | Mar 2005 | B2 |
| 6884170 | Rowe | Apr 2005 | B2 |
| 6884173 | Gauselmann | Apr 2005 | B2 |
| 6884174 | Lundy et al. | Apr 2005 | B2 |
| 6896618 | Benoy et al. | May 2005 | B2 |
| 6899627 | Lam et al. | May 2005 | B2 |
| 6899628 | Leen et al. | May 2005 | B2 |
| 6901440 | Bimm et al. | May 2005 | B1 |
| 6905411 | Nguyen et al. | Jun 2005 | B2 |
| 6908387 | Hedrick et al. | Jun 2005 | B2 |
| 6962530 | Jackson | Nov 2005 | B2 |
| 6971956 | Rowe et al. | Dec 2005 | B2 |
| 6972682 | Lareau et al. | Dec 2005 | B2 |
| 6993587 | Basani et al. | Jan 2006 | B1 |
| 6997803 | LeMay et al. | Feb 2006 | B2 |
| 7013469 | Smith et al. | Mar 2006 | B2 |
| 7025674 | Adams et al. | Apr 2006 | B2 |
| 7027996 | Levinson | Apr 2006 | B2 |
| 7035626 | Luciano, Jr. | Apr 2006 | B1 |
| 7050056 | Meyringer | May 2006 | B2 |
| 7051101 | Dubrovsky et al. | May 2006 | B1 |
| 7062470 | Prasad et al. | Jun 2006 | B2 |
| 7086947 | Walker et al. | Aug 2006 | B2 |
| 7099035 | Brooks et al. | Aug 2006 | B2 |
| 7100184 | Kahn | Aug 2006 | B1 |
| 7112138 | Hedrick et al. | Sep 2006 | B2 |
| 7114718 | Grauzer et al. | Oct 2006 | B2 |
| 7116782 | Jackson et al. | Oct 2006 | B2 |
| 7120879 | Gutberlet et al. | Oct 2006 | B2 |
| 7128652 | Lavoie et al. | Oct 2006 | B1 |
| 7140964 | Walker et al. | Nov 2006 | B2 |
| 7147558 | Giobbi | Dec 2006 | B2 |
| 7168089 | Nguyen et al. | Jan 2007 | B2 |
| 7179170 | Martinek et al. | Feb 2007 | B2 |
| 7186181 | Rowe | Mar 2007 | B2 |
| 7189161 | Wiltshire et al. | Mar 2007 | B1 |
| 7197765 | Chan et al. | Mar 2007 | B2 |
| 7198571 | LeMay et al. | Apr 2007 | B2 |
| 7203841 | Jackson et al. | Apr 2007 | B2 |
| RE39644 | Alcorn et al. | May 2007 | E |
| 7246799 | Snow | Jul 2007 | B2 |
| 7260834 | Carlson | Aug 2007 | B1 |
| 7291068 | Bryant et al. | Nov 2007 | B2 |
| 7293282 | Danforth et al. | Nov 2007 | B2 |
| 7297062 | Gatto et al. | Nov 2007 | B2 |
| 7300352 | Rowe | Nov 2007 | B2 |
| 7303473 | Rowe | Dec 2007 | B2 |
| 7303475 | Britt et al. | Dec 2007 | B2 |
| 7309065 | Yoseloff et al. | Dec 2007 | B2 |
| 7311605 | Moser | Dec 2007 | B2 |
| 7329185 | Conover et al. | Feb 2008 | B2 |
| 7330822 | Robson et al. | Feb 2008 | B1 |
| 7331520 | Silva et al. | Feb 2008 | B2 |
| 7337330 | Gatto et al. | Feb 2008 | B2 |
| 7346682 | Basani et al. | Mar 2008 | B2 |
| 7349920 | Feinberg et al. | Mar 2008 | B1 |
| 7351147 | Stockdale et al. | Apr 2008 | B2 |
| 7353183 | Musso | Apr 2008 | B1 |
| 7356770 | Jackson | Apr 2008 | B1 |
| 7363342 | Wang et al. | Apr 2008 | B1 |
| 7364510 | Walker et al. | Apr 2008 | B2 |
| 7370282 | Cary | May 2008 | B2 |
| 7384339 | LeMay et al. | Jun 2008 | B2 |
| 7398327 | Lee | Jul 2008 | B2 |
| 7410422 | Fine | Aug 2008 | B2 |
| 7419428 | Rowe | Sep 2008 | B2 |
| 7427233 | Walker et al. | Sep 2008 | B2 |
| 7427236 | Kaminkow et al. | Sep 2008 | B2 |
| 7434805 | Grauzer et al. | Oct 2008 | B2 |
| 7435179 | Ford | Oct 2008 | B1 |
| 7438221 | Washington et al. | Oct 2008 | B2 |
| 7438295 | Aida | Oct 2008 | B2 |
| 7438643 | Brosnan et al. | Oct 2008 | B2 |
| 7455591 | Nguyen | Nov 2008 | B2 |
| 7460863 | Steelberg et al. | Dec 2008 | B2 |
| 7465231 | Lewin et al. | Dec 2008 | B2 |
| 7473178 | Boyd et al. | Jan 2009 | B2 |
| 7483394 | Chang et al. | Jan 2009 | B2 |
| 7484207 | Sato | Jan 2009 | B2 |
| 7500915 | Wolf et al. | Mar 2009 | B2 |
| 7510474 | Carter, Sr. | Mar 2009 | B2 |
| 7510478 | Benbrahim et al. | Mar 2009 | B2 |
| 7515718 | Nguyen et al. | Apr 2009 | B2 |
| 7516959 | Huard et al. | Apr 2009 | B2 |
| 7534169 | Amaitis et al. | May 2009 | B2 |
| 7537456 | Snow | May 2009 | B2 |
| 7549576 | Alderucci et al. | Jun 2009 | B2 |
| 7559080 | Bhargavan et al. | Jul 2009 | B2 |
| 7566274 | Johnson et al. | Jul 2009 | B2 |
| 7575234 | Soltys et al. | Aug 2009 | B2 |
| 7577847 | Nguyen et al. | Aug 2009 | B2 |
| 7578739 | Gauselmann | Aug 2009 | B2 |
| 7581256 | Cockerille et al. | Aug 2009 | B2 |
| 7585217 | Lutnick et al. | Sep 2009 | B2 |
| 7594030 | Teodosiu et al. | Sep 2009 | B2 |
| 7607976 | Baerlocher et al. | Oct 2009 | B2 |
| 7607977 | Baerlocher et al. | Oct 2009 | B2 |
| 7610549 | Vignet | Oct 2009 | B2 |
| 7611404 | Hilf et al. | Nov 2009 | B1 |
| 7611407 | Itkis et al. | Nov 2009 | B1 |
| 7611409 | Muir et al. | Nov 2009 | B2 |
| 7617151 | Rowe | Nov 2009 | B2 |
| 7618317 | Jackson | Nov 2009 | B2 |
| 7621809 | Baerlocher et al. | Nov 2009 | B2 |
| 7629886 | Steeves | Dec 2009 | B2 |
| 7634550 | Wolber et al. | Dec 2009 | B2 |
| 7637810 | Amaitis et al. | Dec 2009 | B2 |
| 7644861 | Alderucci et al. | Jan 2010 | B2 |
| 7648414 | McNutt et al. | Jan 2010 | B2 |
| 7666081 | Baerlocher et al. | Feb 2010 | B2 |
| 7666095 | Van Luchene | Feb 2010 | B2 |
| 7674179 | Baerlocher et al. | Mar 2010 | B2 |
| 7682249 | Winans et al. | Mar 2010 | B2 |
| 7684874 | Schlottmann et al. | Mar 2010 | B2 |
| 7684882 | Baerlocher et al. | Mar 2010 | B2 |
| 7685516 | Fischer | Mar 2010 | B2 |
| 7685593 | Solomon et al. | Mar 2010 | B2 |
| 7686688 | Friedman et al. | Mar 2010 | B2 |
| 7688322 | Kapler et al. | Mar 2010 | B2 |
| 7689302 | Schlottmann et al. | Mar 2010 | B2 |
| 7690995 | Frankulin et al. | Apr 2010 | B2 |
| 7699697 | Darrah et al. | Apr 2010 | B2 |
| 7699703 | Muir et al. | Apr 2010 | B2 |
| 7702719 | Betz et al. | Apr 2010 | B1 |
| 7706895 | Callaghan | Apr 2010 | B2 |
| 7712050 | Gutberlet et al. | May 2010 | B2 |
| 7722453 | Lark et al. | May 2010 | B2 |
| 7730198 | Ruppert et al. | Jun 2010 | B2 |
| 7744452 | Cimring et al. | Jun 2010 | B2 |
| 7744462 | Grav et al. | Jun 2010 | B2 |
| 7747741 | Basani et al. | Jun 2010 | B2 |
| 7753790 | Nguyen et al. | Jul 2010 | B2 |
| 7769877 | McBride et al. | Aug 2010 | B2 |
| 7778635 | Crookham et al. | Aug 2010 | B2 |
| 7780525 | Walker et al. | Aug 2010 | B2 |
| 7780526 | Nguyen et al. | Aug 2010 | B2 |
| 7780529 | Rowe et al. | Aug 2010 | B2 |
| 7783881 | Morrow et al. | Aug 2010 | B2 |
| 7785204 | Wells et al. | Aug 2010 | B2 |
| 7787972 | Schlottmann et al. | Aug 2010 | B2 |
| 7788503 | Gatto et al. | Aug 2010 | B2 |
| 7794319 | Luciano, Jr. et al. | Sep 2010 | B2 |
| 7805719 | O'Neill | Sep 2010 | B2 |
| 7824255 | Lutnick et al. | Nov 2010 | B2 |
| 7824267 | Cannon et al. | Nov 2010 | B2 |
| 7828649 | Cuddy et al. | Nov 2010 | B2 |
| 7828661 | Fish et al. | Nov 2010 | B1 |
| 7841946 | Walker et al. | Nov 2010 | B2 |
| 7844944 | Gutberlet et al. | Nov 2010 | B2 |
| 7846018 | Baerlocher | Dec 2010 | B2 |
| 7846020 | Walker et al. | Dec 2010 | B2 |
| 7850528 | Wells | Dec 2010 | B2 |
| 7857702 | Hilbert | Dec 2010 | B2 |
| 7862425 | Cavagna | Jan 2011 | B2 |
| 7867081 | Schneider et al. | Jan 2011 | B2 |
| 7867091 | Moshal | Jan 2011 | B2 |
| 7871323 | Walker et al. | Jan 2011 | B2 |
| 7874920 | Hornik et al. | Jan 2011 | B2 |
| 7874921 | Baszucki et al. | Jan 2011 | B2 |
| 7886288 | Breckner et al. | Feb 2011 | B2 |
| 7892093 | Kniesteadt et al. | Feb 2011 | B2 |
| 7898679 | Brack et al. | Mar 2011 | B2 |
| 7901294 | Walker et al. | Mar 2011 | B2 |
| 7905770 | Snow | Mar 2011 | B2 |
| 7905780 | Morrow et al. | Mar 2011 | B2 |
| 7908486 | Gatto et al. | Mar 2011 | B2 |
| 7909689 | Lardie | Mar 2011 | B2 |
| 7918735 | Inamura | Apr 2011 | B2 |
| 7921026 | O'Cull et al. | Apr 2011 | B2 |
| 7921405 | Gupta et al. | Apr 2011 | B2 |
| 7931533 | LeMay et al. | Apr 2011 | B2 |
| 7937464 | Ruppert et al. | May 2011 | B2 |
| 7946911 | Vang et al. | May 2011 | B2 |
| 7963847 | Baerlocher | Jun 2011 | B2 |
| 7980954 | Gagner et al. | Jul 2011 | B2 |
| 7988554 | LeMay et al. | Aug 2011 | B2 |
| 7993199 | Iddings et al. | Aug 2011 | B2 |
| 8025574 | Hilbert | Sep 2011 | B2 |
| 8028046 | Elliott et al. | Sep 2011 | B2 |
| 8033913 | Cockerille et al. | Oct 2011 | B2 |
| 8037313 | Hamalainen et al. | Oct 2011 | B2 |
| 8051180 | Mazzaferri et al. | Nov 2011 | B2 |
| 8057294 | Pacey et al. | Nov 2011 | B2 |
| 8057297 | Silvestro | Nov 2011 | B2 |
| 8062134 | Kelly et al. | Nov 2011 | B2 |
| 8070583 | Baerlocher et al. | Dec 2011 | B2 |
| 8073657 | Moore, III et al. | Dec 2011 | B2 |
| 8075403 | O'Brien et al. | Dec 2011 | B2 |
| 8092289 | Mai | Jan 2012 | B2 |
| 8092307 | Kelly | Jan 2012 | B2 |
| 8092309 | Bickley | Jan 2012 | B2 |
| 8100753 | Soltys | Jan 2012 | B2 |
| 8117461 | Bigelow, Jr. et al. | Feb 2012 | B2 |
| 8135793 | Ruppert et al. | Mar 2012 | B2 |
| 8147316 | Arezina et al. | Apr 2012 | B2 |
| 8147334 | Gatto et al. | Apr 2012 | B2 |
| 8171155 | Ruppert | May 2012 | B2 |
| 8172661 | Hein | May 2012 | B1 |
| 8177634 | Herrmann et al. | May 2012 | B2 |
| 8182346 | Herrmann et al. | May 2012 | B2 |
| 8185423 | Brook et al. | May 2012 | B2 |
| 8187087 | Herrmann et al. | May 2012 | B2 |
| 8187101 | Herrmann et al. | May 2012 | B2 |
| 8192283 | Ruppert et al. | Jun 2012 | B2 |
| 8192289 | Herrmann et al. | Jun 2012 | B2 |
| 8195825 | Ruppert et al. | Jun 2012 | B2 |
| 8195826 | Ruppert et al. | Jun 2012 | B2 |
| 8197340 | Garvey et al. | Jun 2012 | B2 |
| 8197344 | Rathsack et al. | Jun 2012 | B2 |
| 8201229 | Ruppert et al. | Jun 2012 | B2 |
| 8241111 | Manfredi et al. | Aug 2012 | B2 |
| 8246466 | Herrmann et al. | Aug 2012 | B2 |
| 8266213 | Crowder | Sep 2012 | B2 |
| 8272945 | Kelly et al. | Sep 2012 | B2 |
| 8277324 | Herrmann et al. | Oct 2012 | B2 |
| 8280777 | Mengerink et al. | Oct 2012 | B2 |
| 8285740 | Graham et al. | Oct 2012 | B2 |
| 8308554 | Rowe et al. | Nov 2012 | B2 |
| 8360870 | Herrmann et al. | Jan 2013 | B2 |
| 8366550 | Herrmann et al. | Feb 2013 | B2 |
| 8512150 | Herrmann et al. | Aug 2013 | B2 |
| 8628422 | Allen et al. | Jan 2014 | B2 |
| 8974305 | Costello et al. | Mar 2015 | B2 |
| 20010019966 | Idaka | Sep 2001 | A1 |
| 20010044337 | Rowe et al. | Nov 2001 | A1 |
| 20020004824 | Cuan et al. | Jan 2002 | A1 |
| 20020049909 | Jackson et al. | Apr 2002 | A1 |
| 20020111213 | McEntee et al. | Aug 2002 | A1 |
| 20020113371 | Snow | Aug 2002 | A1 |
| 20020115487 | Wells | Aug 2002 | A1 |
| 20020119824 | Allen | Aug 2002 | A1 |
| 20020142844 | Kerr | Oct 2002 | A1 |
| 20020144115 | Lemay et al. | Oct 2002 | A1 |
| 20020147047 | Letovsky et al. | Oct 2002 | A1 |
| 20020151363 | Letovsky et al. | Oct 2002 | A1 |
| 20020152120 | Howington | Oct 2002 | A1 |
| 20030004871 | Rowe | Jan 2003 | A1 |
| 20030032474 | Kaminkow | Feb 2003 | A1 |
| 20030042679 | Snow | Mar 2003 | A1 |
| 20030064798 | Grauzer et al. | Apr 2003 | A1 |
| 20030075869 | Breeding et al. | Apr 2003 | A1 |
| 20030090064 | Hoyt et al. | May 2003 | A1 |
| 20030104865 | Itkis et al. | Jun 2003 | A1 |
| 20030130024 | Darby | Jul 2003 | A1 |
| 20030134675 | Oberberger | Jul 2003 | A1 |
| 20030182414 | O'Neill | Sep 2003 | A1 |
| 20030185229 | Shachar et al. | Oct 2003 | A1 |
| 20030203755 | Jackson | Oct 2003 | A1 |
| 20030206548 | Bannai et al. | Nov 2003 | A1 |
| 20030224858 | Yoseloff et al. | Dec 2003 | A1 |
| 20030228912 | Wells et al. | Dec 2003 | A1 |
| 20030232651 | Huard et al. | Dec 2003 | A1 |
| 20040002386 | Wolfe et al. | Jan 2004 | A1 |
| 20040002388 | Larsen et al. | Jan 2004 | A1 |
| 20040023712 | Oliver | Feb 2004 | A1 |
| 20040029635 | Giobbi | Feb 2004 | A1 |
| 20040043815 | Kaminkow | Mar 2004 | A1 |
| 20040043820 | Schlottmann | Mar 2004 | A1 |
| 20040048669 | Rowe | Mar 2004 | A1 |
| 20040048671 | Rowe | Mar 2004 | A1 |
| 20040064817 | Shibayama et al. | Apr 2004 | A1 |
| 20040082385 | Silva et al. | Apr 2004 | A1 |
| 20040092310 | Brosnan et al. | May 2004 | A1 |
| 20040106452 | Nguyen et al. | Jun 2004 | A1 |
| 20040110119 | Riconda et al. | Jun 2004 | A1 |
| 20040127291 | George et al. | Jul 2004 | A1 |
| 20040133485 | Schoonmaker et al. | Jul 2004 | A1 |
| 20040142744 | Atkinson et al. | Jul 2004 | A1 |
| 20040166940 | Rothschild | Aug 2004 | A1 |
| 20040180722 | Giobbi | Sep 2004 | A1 |
| 20040185936 | Block et al. | Sep 2004 | A1 |
| 20040204231 | Martin et al. | Oct 2004 | A1 |
| 20040229684 | Blackburn et al. | Nov 2004 | A1 |
| 20040254993 | Mamas | Dec 2004 | A1 |
| 20040259640 | Gentles et al. | Dec 2004 | A1 |
| 20050032564 | Sines | Feb 2005 | A1 |
| 20050043094 | Nguyen et al. | Feb 2005 | A1 |
| 20050054438 | Rothschild et al. | Mar 2005 | A1 |
| 20050070358 | Angell et al. | Mar 2005 | A1 |
| 20050080898 | Block | Apr 2005 | A1 |
| 20050119052 | Russell et al. | Jun 2005 | A1 |
| 20050143166 | Walker et al. | Jun 2005 | A1 |
| 20050153778 | Nelson et al. | Jul 2005 | A1 |
| 20050164762 | Smith et al. | Jul 2005 | A1 |
| 20050171808 | Saenz et al. | Aug 2005 | A1 |
| 20050192092 | Breckner et al. | Sep 2005 | A1 |
| 20050222891 | Chan et al. | Oct 2005 | A1 |
| 20050239542 | Olsen | Oct 2005 | A1 |
| 20060003828 | Abecassis | Jan 2006 | A1 |
| 20060004618 | Brixius | Jan 2006 | A1 |
| 20060009282 | George et al. | Jan 2006 | A1 |
| 20060015716 | Thornton et al. | Jan 2006 | A1 |
| 20060026499 | Weddle | Feb 2006 | A1 |
| 20060031763 | Yeung | Feb 2006 | A1 |
| 20060035707 | Nguyen et al. | Feb 2006 | A1 |
| 20060040745 | Wells et al. | Feb 2006 | A1 |
| 20060046849 | Kovacs | Mar 2006 | A1 |
| 20060052169 | Britt et al. | Mar 2006 | A1 |
| 20060068899 | White et al. | Mar 2006 | A1 |
| 20060080175 | Rowe et al. | Apr 2006 | A1 |
| 20060116208 | Chen et al. | Jun 2006 | A1 |
| 20060121970 | Khal | Jun 2006 | A1 |
| 20060172804 | Acres et al. | Aug 2006 | A1 |
| 20060183541 | Okada et al. | Aug 2006 | A1 |
| 20060189381 | Daniel et al. | Aug 2006 | A1 |
| 20060195847 | Amano et al. | Aug 2006 | A1 |
| 20060205508 | Green | Sep 2006 | A1 |
| 20060217202 | Burke et al. | Sep 2006 | A1 |
| 20060247013 | Walker et al. | Nov 2006 | A1 |
| 20060247057 | Green et al. | Nov 2006 | A1 |
| 20060252530 | Oberberger et al. | Nov 2006 | A1 |
| 20060253702 | Lowell et al. | Nov 2006 | A1 |
| 20060259604 | Kotchavi et al. | Nov 2006 | A1 |
| 20060277487 | Poulsen et al. | Dec 2006 | A1 |
| 20060284376 | Snow | Dec 2006 | A1 |
| 20060287098 | Morrow et al. | Dec 2006 | A1 |
| 20070004501 | Brewer et al. | Jan 2007 | A1 |
| 20070015583 | Tran | Jan 2007 | A1 |
| 20070026923 | Muir | Feb 2007 | A1 |
| 20070026935 | Wolf et al. | Feb 2007 | A1 |
| 20070026942 | Kinsley et al. | Feb 2007 | A1 |
| 20070032288 | Nelson et al. | Feb 2007 | A1 |
| 20070033247 | Martin | Feb 2007 | A1 |
| 20070054740 | Salls et al. | Mar 2007 | A1 |
| 20070055753 | Robb | Mar 2007 | A1 |
| 20070057453 | Soltys et al. | Mar 2007 | A1 |
| 20070057454 | Fleckenstein | Mar 2007 | A1 |
| 20070057469 | Grauzer et al. | Mar 2007 | A1 |
| 20070060225 | Hosogai et al. | Mar 2007 | A1 |
| 20070060259 | Pececnik | Mar 2007 | A1 |
| 20070060307 | Mathis et al. | Mar 2007 | A1 |
| 20070060320 | Kelly et al. | Mar 2007 | A1 |
| 20070060354 | Themer et al. | Mar 2007 | A1 |
| 20070060365 | Tien et al. | Mar 2007 | A1 |
| 20070072677 | Lavoie et al. | Mar 2007 | A1 |
| 20070077995 | Oak et al. | Apr 2007 | A1 |
| 20070093298 | Brunet | Apr 2007 | A1 |
| 20070105628 | Arbogast et al. | May 2007 | A1 |
| 20070111775 | Yoseloff | May 2007 | A1 |
| 20070111786 | Snow | May 2007 | A1 |
| 20070111791 | Arbogast et al. | May 2007 | A1 |
| 20070111794 | Hogan et al. | May 2007 | A1 |
| 20070117608 | Roper et al. | May 2007 | A1 |
| 20070118844 | Huang et al. | May 2007 | A1 |
| 20070123346 | Perez et al. | May 2007 | A1 |
| 20070124483 | Marples et al. | May 2007 | A1 |
| 20070129141 | Walker et al. | Jun 2007 | A1 |
| 20070129145 | Blackburn et al. | Jun 2007 | A1 |
| 20070155490 | Phillips et al. | Jul 2007 | A1 |
| 20070167235 | Naicker | Jul 2007 | A1 |
| 20070173331 | Crawford et al. | Jul 2007 | A1 |
| 20070184905 | Gatto et al. | Aug 2007 | A1 |
| 20070191102 | Coliz et al. | Aug 2007 | A1 |
| 20070192748 | Martin et al. | Aug 2007 | A1 |
| 20070197294 | Gong | Aug 2007 | A1 |
| 20070197298 | Rowe | Aug 2007 | A1 |
| 20070198418 | MacDonald et al. | Aug 2007 | A1 |
| 20070202941 | Miltenberger et al. | Aug 2007 | A1 |
| 20070208816 | Baldwin et al. | Sep 2007 | A1 |
| 20070213116 | Crawford et al. | Sep 2007 | A1 |
| 20070214030 | Shear et al. | Sep 2007 | A1 |
| 20070214058 | Rouhi | Sep 2007 | A1 |
| 20070218998 | Arbogast et al. | Sep 2007 | A1 |
| 20070225061 | Naobayashi | Sep 2007 | A1 |
| 20070235521 | Mateen et al. | Oct 2007 | A1 |
| 20070238526 | Chandranmenon | Oct 2007 | A1 |
| 20070241497 | Soltys et al. | Oct 2007 | A1 |
| 20070241498 | Soltys | Oct 2007 | A1 |
| 20070243925 | LeMay et al. | Oct 2007 | A1 |
| 20070243927 | Soltys | Oct 2007 | A1 |
| 20070243935 | Huizinga | Oct 2007 | A1 |
| 20070259709 | Kelly et al. | Nov 2007 | A1 |
| 20070259711 | Thomas | Nov 2007 | A1 |
| 20070265092 | Betteridge | Nov 2007 | A1 |
| 20070298868 | Soltys | Dec 2007 | A1 |
| 20080004108 | Klinkhammer | Jan 2008 | A1 |
| 20080009344 | Graham et al. | Jan 2008 | A1 |
| 20080026832 | Stevens et al. | Jan 2008 | A1 |
| 20080026848 | Byng | Jan 2008 | A1 |
| 20080032763 | Giobbi | Feb 2008 | A1 |
| 20080038035 | Shuldman et al. | Feb 2008 | A1 |
| 20080039192 | Laut | Feb 2008 | A1 |
| 20080039208 | Abrink et al. | Feb 2008 | A1 |
| 20080045341 | Englman | Feb 2008 | A1 |
| 20080045342 | Crowder et al. | Feb 2008 | A1 |
| 20080058105 | Combs et al. | Mar 2008 | A1 |
| 20080064501 | Patel | Mar 2008 | A1 |
| 20080065590 | Castro et al. | Mar 2008 | A1 |
| 20080073840 | Comeau | Mar 2008 | A1 |
| 20080076572 | Nguyen et al. | Mar 2008 | A1 |
| 20080090651 | Baerlocher | Apr 2008 | A1 |
| 20080096656 | LeMay et al. | Apr 2008 | A1 |
| 20080096659 | Kreloff et al. | Apr 2008 | A1 |
| 20080102919 | Rowe et al. | May 2008 | A1 |
| 20080102932 | Anderson et al. | May 2008 | A1 |
| 20080108405 | Brosnan et al. | May 2008 | A1 |
| 20080108433 | DiMichele et al. | May 2008 | A1 |
| 20080113764 | Soltys | May 2008 | A1 |
| 20080113772 | Burrill et al. | May 2008 | A1 |
| 20080113773 | Johnson et al. | May 2008 | A1 |
| 20080119284 | Luciano, Jr. et al. | May 2008 | A1 |
| 20080126803 | Ginter et al. | May 2008 | A1 |
| 20080127174 | Johnson | May 2008 | A1 |
| 20080136102 | Hoover | Jun 2008 | A1 |
| 20080138773 | Lathrop | Jun 2008 | A1 |
| 20080146337 | Halonen et al. | Jun 2008 | A1 |
| 20080153599 | Atashband | Jun 2008 | A1 |
| 20080153600 | Swarna | Jun 2008 | A1 |
| 20080154916 | Atashband | Jun 2008 | A1 |
| 20080155665 | Ruppert | Jun 2008 | A1 |
| 20080162729 | Ruppert | Jul 2008 | A1 |
| 20080165771 | Gainey et al. | Jul 2008 | A1 |
| 20080171588 | Atashband | Jul 2008 | A1 |
| 20080171598 | Deng | Jul 2008 | A1 |
| 20080176627 | Lardie | Jul 2008 | A1 |
| 20080200255 | Eisele | Aug 2008 | A1 |
| 20080243697 | Irving et al. | Oct 2008 | A1 |
| 20080244565 | Levidow et al. | Oct 2008 | A1 |
| 20080248875 | Beatty | Oct 2008 | A1 |
| 20080252011 | Bickley et al. | Oct 2008 | A1 |
| 20080261699 | Topham et al. | Oct 2008 | A1 |
| 20080261701 | Lewin et al. | Oct 2008 | A1 |
| 20080287197 | Ruppert et al. | Nov 2008 | A1 |
| 20080293494 | Adiraju et al. | Nov 2008 | A1 |
| 20080300046 | Gagner et al. | Dec 2008 | A1 |
| 20080311971 | Dean | Dec 2008 | A1 |
| 20080313282 | Warila et al. | Dec 2008 | A1 |
| 20080318655 | Davies | Dec 2008 | A1 |
| 20080318685 | Oak et al. | Dec 2008 | A9 |
| 20090005176 | Morrow et al. | Jan 2009 | A1 |
| 20090005177 | Kishi et al. | Jan 2009 | A1 |
| 20090011833 | Seelig et al. | Jan 2009 | A1 |
| 20090054139 | Anderson | Feb 2009 | A1 |
| 20090063309 | Stephens | Mar 2009 | A1 |
| 20090069090 | Moser et al. | Mar 2009 | A1 |
| 20090100409 | Toneguzzo | Apr 2009 | A1 |
| 20090115133 | Kelly et al. | May 2009 | A1 |
| 20090118001 | Kelly et al. | May 2009 | A1 |
| 20090118005 | Kelly et al. | May 2009 | A1 |
| 20090118006 | Kelly et al. | May 2009 | A1 |
| 20090121434 | Baerlocher et al. | May 2009 | A1 |
| 20090124329 | Palmisano | May 2009 | A1 |
| 20090124385 | Cuddy et al. | May 2009 | A1 |
| 20090124392 | Ruppert et al. | May 2009 | A1 |
| 20090124394 | Swarna | May 2009 | A1 |
| 20090125603 | Atashband et al. | May 2009 | A1 |
| 20090131144 | Allen | May 2009 | A1 |
| 20090131163 | Arbogast et al. | May 2009 | A1 |
| 20090132720 | Ruppert et al. | May 2009 | A1 |
| 20090156310 | Fargo | Jun 2009 | A1 |
| 20090156313 | Blackburn et al. | Jun 2009 | A1 |
| 20090170594 | Delaney et al. | Jul 2009 | A1 |
| 20090176578 | Herrmann et al. | Jul 2009 | A1 |
| 20090181776 | Deng | Jul 2009 | A1 |
| 20090239667 | Rowe et al. | Sep 2009 | A1 |
| 20090270170 | Patton | Oct 2009 | A1 |
| 20090275394 | Young et al. | Nov 2009 | A1 |
| 20090275400 | Rehm et al. | Nov 2009 | A1 |
| 20090275401 | Allen et al. | Nov 2009 | A1 |
| 20090275402 | Backover et al. | Nov 2009 | A1 |
| 20090276341 | McMahan et al. | Nov 2009 | A1 |
| 20090298575 | Hopkins et al. | Dec 2009 | A1 |
| 20090298577 | Gagner et al. | Dec 2009 | A1 |
| 20090298583 | Jones | Dec 2009 | A1 |
| 20090307069 | Meyerhofer | Dec 2009 | A1 |
| 20090315264 | Snow et al. | Dec 2009 | A1 |
| 20090325708 | Kerr | Dec 2009 | A9 |
| 20090325716 | Harari | Dec 2009 | A1 |
| 20100016050 | Snow et al. | Jan 2010 | A1 |
| 20100016067 | White et al. | Jan 2010 | A1 |
| 20100016068 | White et al. | Jan 2010 | A1 |
| 20100048291 | Warkentin | Feb 2010 | A1 |
| 20100048304 | Boesen | Feb 2010 | A1 |
| 20100058320 | Milligan et al. | Mar 2010 | A1 |
| 20100062835 | Hopkins | Mar 2010 | A1 |
| 20100062838 | Nguyen et al. | Mar 2010 | A1 |
| 20100069155 | Schwartz et al. | Mar 2010 | A1 |
| 20100093440 | Burke | Apr 2010 | A1 |
| 20100093441 | Rajaraman et al. | Apr 2010 | A1 |
| 20100125851 | Singh et al. | May 2010 | A1 |
| 20100131772 | Atashband et al. | May 2010 | A1 |
| 20100178987 | Pacey | Jul 2010 | A1 |
| 20100197410 | Leen et al. | Aug 2010 | A1 |
| 20100210353 | Gagner et al. | Aug 2010 | A1 |
| 20100234110 | Clarkson | Sep 2010 | A1 |
| 20100240440 | Szrek et al. | Sep 2010 | A1 |
| 20100255899 | Paulsen | Oct 2010 | A1 |
| 20110009184 | Byng | Jan 2011 | A1 |
| 20110074107 | Rowe | Mar 2011 | A1 |
| 20110105208 | Bickley | May 2011 | A1 |
| 20110111826 | Baerlocher et al. | May 2011 | A1 |
| 20110124417 | Baynes et al. | May 2011 | A1 |
| 20110130190 | Hamman et al. | Jun 2011 | A1 |
| 20110159952 | Kerr | Jun 2011 | A1 |
| 20110159953 | Kerr | Jun 2011 | A1 |
| 20110165936 | Kerr | Jul 2011 | A1 |
| 20110172008 | Alderucci | Jul 2011 | A1 |
| 20110179409 | Yoseloff et al. | Jul 2011 | A1 |
| 20110183748 | Wilson et al. | Jul 2011 | A1 |
| 20110230268 | Williams | Sep 2011 | A1 |
| 20110269529 | Baerlocher | Nov 2011 | A1 |
| 20110269534 | Kelly et al. | Nov 2011 | A1 |
| 20110275430 | Walker et al. | Nov 2011 | A1 |
| 20110287829 | Clarkson et al. | Nov 2011 | A1 |
| 20120015724 | Ocko et al. | Jan 2012 | A1 |
| 20120015725 | Ocko et al. | Jan 2012 | A1 |
| 20120015743 | Lam et al. | Jan 2012 | A1 |
| 20120015747 | Ocko et al. | Jan 2012 | A1 |
| 20120021835 | Keller et al. | Jan 2012 | A1 |
| 20120034977 | Kammler | Feb 2012 | A1 |
| 20120110649 | Murphy | May 2012 | A1 |
| 20120115616 | Phillips et al. | May 2012 | A1 |
| 20120203692 | Olliphant et al. | Aug 2012 | A1 |
| 20120295691 | Walker | Nov 2012 | A1 |
| 20130053117 | Snow | Feb 2013 | A1 |
| 20130184060 | Costello et al. | Jul 2013 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 529 076 | Jun 2006 | CA |
| 19940954 | Mar 2001 | DE |
| 1074955 | Feb 2001 | EP |
| 1463008 | Sep 2004 | EP |
| 2380143 | Apr 2003 | GB |
| 8255059 | Oct 1996 | JP |
| 2001-0084838 | Sep 2001 | KR |
| 2002-0061793 | Jul 2002 | KR |
| 2003-0091635 | Dec 2003 | KR |
| 0205914 | Jan 2002 | WO |
| 0360846 | Jul 2003 | WO |
| 2005035084 | Apr 2005 | WO |
| 2007033207 | Mar 2007 | WO |
| WO2007047223 | Apr 2007 | WO |
| 2011109454 | Sep 2011 | WO |
| Entry |
|---|
| International Search Report and Written Opinion for co-pending application PCT/US13/21959, dated May 10, 2013. |
| International Search Report and Written Opinion for co-pending application PCT/US13/22153, dated Apr. 8, 2013. |
| United States Office Action, U.S. Appl. No. 13/624,743, Jan. 29, 2013, 7 pages. |
| U.S. Appl. No. 13/860,991, filed Apr. 11, 2013, and titled “Interactive Financial Transactions,” to Andrew Costello. |
| U.S. Appl. No. 13/609,031, filed Sep. 10, 2012, and titled “Network Gaming Architecture, Gaming Systems, and Related Methods,” to Costello et al. |
| U.S. Appl. No. 13/624,743, filed Sep. 21, 2012, and titled “Play for Fun Network Gaming System and Method,” to Costello et al. |
| U.S. Appl. No. 13/864,069, filed Apr. 16, 2013, and titled “Administering Wagering Games Having Supplemental Pot,” to Louis J. Castle, II. |
| U.S. Appl. No. 13/871,824, filed Apr. 26, 2013, and titled “Distributing Supplemental Pot in Wagering Games Based on Predetermined Event,” to Castle et al. |
| “BOB and LDAP,” Gaming Standards Association, Fremont, California, 7 pages, Oct. 26, 2003. |
| “GSA Point-to-Point SOAP/HTTPS Transport and Security Specification v1.0.3,” Gaming Standards Association TRANSPORT Technical Committee, 16 pages, Jun. 5, 2007. |
| Bally Technologies, Inc., iVIEW, http://ballytech.com/systems/product.cfm?id=9, download date Nov. 6, 2007, 2 pages. |
| Bally TMS, “MP21—Automated Table Tracking/Features,” 2 pages, Nov. 2005. |
| Bally TMS, “MPBacc—Specifications/Specifications,” 2 pages, Nov. 2005. |
| Bally TMS, “MPLite—Table Management System/Features,” 2 pages, Nov. 2005. |
| Bulavsky, J., “Tracking the Tables,” Casino Journal, May 2004, pp. 44-47, accessed Dec. 21, 2005, URL = http://www.ascendgaming.com/cj/vendors—manufacturers—table/Trackin916200411141AM.htm, 5 pages. |
| Burke, A., “Tracking the Tables,” reprinted from International Gaming & Wagering Business, Aug. 2003, 4 pages. |
| Costello et al., “Network Gaming Architecture, Gaming Systems, and Related Methods,” Office Action mailed Mar. 27, 2014, for U.S. Appl. No. 13/609,031, 11 pages. |
| Costello et al., “Network Gaming Architecture, Gaming Systems, and Related Methods,” Amendment dated Jul. 25, 2014, for U.S. Appl. No. 13/609,031, 12 pages. |
| Costello et al., “Network Gaming Architecture, Gaming Systems, and Related Methods,” Notice of Allowance mailed Nov. 3, 2014, for U.S. Appl. No. 13/609,031, 7 pages. |
| Costello et al., “Play for Fun Network Gaming System and Method,” Office Action mailed Jan. 29, 2013, for U.S. Appl. No. 13/624,743, 7 pages. |
| Costello et al., “Play for Fun Network Gaming System and Method,” Amendment dated Apr. 29, 2013, for U.S. Appl. No. 13/624,743, 12 pages. |
| Costello et al., “Play for Fun Network Gaming System and Method,” Office Action mailed Nov. 12, 2013, for U.S. Appl. No. 13/624,743, 15 pages. |
| Costello et al., “Play for Fun Network Gaming System and Method,” Amendment dated Jan. 13, 2014, for U.S. Appl. No. 13/624,743, 9 pages. |
| Costello et al., “Play for Fun Network Gaming System and Method,” Advisory Action mailed Feb. 25, 2014, for U.S. Appl. No. 13/624,743, 5 pages. |
| Costello et al., “Play for Fun Network Gaming System and Method,” Amendment dated Apr. 14, 2014, for U.S. Appl. No. 13/624,743, 10 pages. |
| Costello et al., “Play for Fun Network Gaming System and Method,” Office Action mailed Jan. 30, 2015, for U.S. Appl. No. 13/624,743, 14 pages. |
| Gros, R., “All You Ever Wanted to Know About Table Games,” reprinted from Global Gaming Business, Aug. 1, 2003, 2 pages. |
| Gwyddion User Guide, “False Color Mapping: Chapter 3. Getting Started,” retrieved from URL=http://sourceforge.net/projects/gwyddion/files/user-guide/2007-06-28/gwyddion-user-guide-xhtm1-2007-06-28.tar.gz/download, retrieved on Nov. 21, 2012, 2 pages. |
| Hung et al., “Performance Evaluation of the Least Conflict Sharable Spreading Code Assignment Algorithm,” IEEE, 1996, 5 pages. |
| MagTek, “Port Powered Swipe Reader,” Technical Reference Manual, Manual Part No. 99875094 Rev 12, Jun. 2003, 20 pages. |
| Mikohn, “Mikohn Tablelink—The Industry's Premier Table Tracking Solution Delivers Improvements Straight to the Bottom Line,” 2 pages, before Jan. 1, 2004. |
| Olesiejuk, “Discovery Services for Gaming Devices on a Casino Floor,” Gaming Standards Association, 3 pages, Mar. 12, 2007. |
| Requirements document, “Game Authentication Terminal Program (GAT3),” to Gaming Standards Association, Aug. 2005, 27 pages. |
| Standards document, “Technical Standards for Gaming Devices and On-Line Slot Systems,” to Nevada Gaming Commission and State Gaming Control Board, Aug. 17, 2005, 15 pages. |
| Terdiman, D., “Who's Holding the Aces Now?”, reprinted from Wired News, Aug. 18, 2003, 2 pages. |
| Winkler, C., “Product Spotlight: MindPlay,” reprinted from Gaming and Leisure Technology, Fall 2003, 2 pages. |
| PCT Written Opinion of the International Preliminary Examining Authority, PCT Application No. PCT/US2013/021959, Jan. 30, 2014, 4 pages. |
| United States Office Action, U.S. Appl. No. 13/624,743, Nov. 12, 2013, 15 pages. |
| United States Office Action, U.S. Appl. No. 13/609,031, Mar. 27, 2014, 11 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20130184079 A1 | Jul 2013 | US |
