The present invention relates to awarding a bonus on a network of gaming devices, and—more particularly—awarding such a bonus on a wide area network.
Many casino operating companies own multiple casinos in several locations. It has proved to be advantageous for such companies to devise player loyalty promotions that span these properties. Historically, multi-property player management systems accumulate player activity across all properties. For example, many casinos track a player's total wagers, theoretical win, actual win, complementary balance, player point balance, and other key player behavior statistics across all casinos managed by that operator.
This information may be used to determine a global worth of the player to the operator, as opposed to a single playing location. Many casino operators accomplish this by dividing their player database into tiers, with the highest tier being the most valuable players and the lowest tier being the least valuable players from the casino's perspective. The casino typically uses a statistic such as theoretical win to establish player worth. Once this global player worth is established, casinos target promotional offers commensurate a player's worth. The promotions are designed to entice further play at one or more of the operator's casinos.
The promotions usually take advantage of the multi-property nature of the business, such as allowing redemption of promotions at all casinos; targeting redemptions to a single property that might have more capacity that other properties; and using a complementary trip to a more desirable property as a promotional offer
All of these generally rely on manual processes for communication of promotional information to the customers and for redeeming promotions. For example, promotional offers are generally communicated via direct mail to qualifying players, or via brochures, signage and literature at a casino. Further, redemption of promotional offers—whether they are cash, complementaries, etc.—is generally done manually at a players-club booth at each casino.
As used herein, the term bonus is an award, e.g., like the promotional offer, given to a player of an electronic gaming machine (EGM). The term bonus herein refers to any such award that is not paid by the device in accordance with its pay table. Such bonuses and systems for implementing them are described in U.S. Pat. No. 5,655,961 (the '961 patent) and in U.S. patent application Ser. No. 08/843,411, now U.S. Pat. No. 6,319,125,both of which are hereby incorporated herein by reference for all purposes. Also hereby incorporated by reference for all purposes is U.S. Pat. No. 6,375,569, which describes a bonus promotion like the one described herein, except implemented at a single casino. A bonus can include an award of cash or machine credits, player points, or complementary amenities.
In a first implementation of the present invention, as participating EGMs are played, a user-selected percentage of the play is added to a common bonus pool. When the pool reaches a randomly selected level of play, between specified minimum and maximum numbers, a winner is randomly selected. The award can be a fixed cash amount, a cash amount linked to the bonus pool total or a non-cash prize. Prizes that are typically smaller than the winning bonus can also be awarded to non-winning players.
In the preferred embodiment, a master server, located at one of a plurality of participating casinos, communicates over a wide area network with slave servers located at each participating casino. The preferred embodiment may support a master server, up to 32 slave servers, and may accommodate as many as 16 different bonus pools that operate to pay a bonus award to one of the EGMs associated with the respective pools. It should be appreciated that other embodiments could support more or less slave servers and bonus pools. For each bonus pool, the master server selects a winning slave server, which in turn selects a winning EGM.
The preferred embodiment is called the Random Rewards® promotion. The promotion is complete when the amount of play on participating EGMs reaches the randomly selected number between the minimum and maximum numbers, which are specified at the master server. The randomly selected number is called the lucky number. Preferably a player must be issued a player-tracking card to be eligible to participate. Although the invention is not so limited, a typical implementation is for a plurality of casinos that are commonly owned with each recognizing a player-tracking card issued by any of the others. As a result, player activity is tracked—in a known manner—across all of the casinos.
Turning now to
The same components (except for a master server, like master server 14) appear in LANs 18a, 18b, 18c, 18d and 18e (not shown) at each of the other casinos (also not shown) on the WAN. It should be appreciated that the master server may also be located at a site remote from any of the participating casinos, or—as in the present embodiment—at one of the casinos; specifically, master server 14 is located at casino 16. Although specified network structure is depicted, the invention can be implemented on any suitable network, regardless of its design or the hardware with which it is implemented.
Router 20 transmits data packets between the master server and each slave server over WAN 12. Depending on topography of the network, a hub could be used in lieu of router 20.
Concentrator 24 is a network device similar to a hub that provides communication routing for devices on the network.
As described in the '961 patent, each EGM at each casino includes a communication board. This board, among other things, receives bonus promotion and message information from bonus servers and sends EGM meter information, among other things, to network computers, including the slave server, like slave server 26.
Consideration will now be given to configuration of master server 14, which must be undertaken before play can begin. Master server 14 is configured at workstation 15 with a user-specified contribution rate that EGMs contribute to the growth of a bonus pool, which is called the current pool. In general terms, as participating EGMs are played, the current pool is incremented by the contribution rate multiplied by the total play on the EGMs. When the current pool reaches or exceeds the lucky number, the master server randomly selects a winning slave server. The winning slave server then randomly selects the winning EGM. EGMs that require different denominations to play can be incorporated into the same pool using known techniques to account for the difference in denominations from game-to-game within the pool.
In the multi-casino Random Rewards® promotion, selecting minimum and maximum numbers at master server 14 specifies the range from which the winning number is selected. The range corresponds to a level of play by the participating EGMs; the total current pool results from all plays made on all EGMs participating in the multi-casino promotion. Master server 14 is also configured with a list of all slave servers participating in the promotion. The current pool represents the combined contributions of each slave server. Each slave server pool total further represents the combined contribution of all EGMs participating in the promotion at the associated slave server's casino.
Each slayer server is also configured, primarily by designating which EGMs are linked to a particular bonus pool. The slave servers are also configured using their associated workstation, like server 26 is configured by workstation 15. Each local configuration workstation can be used to configure the master server and the associated local server, but a workstation at one location cannot be used to configure a slave server at another location.
Consideration will now be given to operation of system 10, with reference to the flow chart of
In the present example, the meter specified at master server 14 to track play is one created for this bonus, namely a carded coin-in meter. This meter counts all coin into the EGM that has a player associated with the EGM as a result of the player's player-tracking card being inserted into a card reader associated with the EGM.
Other meters, such as the coin-in meter, the game meter, the win meter, or another created meter can also be used. Each slave server is updated every half-second with data identifying each EGM whose coin-in meters advanced in the preceding half second and the amount of advance by each. From this the slave server calculates the total coin in for the period and multiplies this times the contribution rate to produce a number equal to the total accrued contribution by that slave server, and therefore its associated casino, since the current pool began accruing. This local pool value is the number transmitted over the WAN in step 40 to the master server.
The slave servers send the total accrued contribution of the casino—i.e., the local pool value—rather than incremental changes to reduce the negative effects caused by communication errors. Sending totals reduces problems arising from packets lost during transmission and obviates the need to reset or synchronize with the master server during increment processing. The master server then compares the new slave pool total with the previous slave pool total (even if power outages or other difficulties prevented transmission of packets for one or more heartbeats) to determine the amount of change, which it then adds to the current pool in step 42. When the current pool reaches the lucky number—in step 44—the winner is selected. If the lucky number is not reached, play and processing continues as shown.
Once the lucky number is reached, the master server determines a winning slave server in step 46. The winning slave server is chosen randomly among slave servers generating local pool increases responsive to the heartbeat that caused the current pool to exceed the lucky number. The random selection, however, is weighted proportionate to the local pool contribution reported by each casino when a winning slave server is chosen. In other words, casinos that generate larger wagers or more play advance the lucky number count more, and are therefore more likely to reach the lucky number.
Once the master server has randomly selected a winning slave server, the master server sends point-to-point messages to each slave server identifying the winning slave server. The winning slave server then identifies a winning EGM—in step 48—also based on a weighted random process. It selects the next half-second of updated play data (described above) to randomly choose a winning EGM from those that had a coin-in event in the selected play data. The random selection is, however, weighted to give a proportionately greater chance of winning to EGMs as a function of the amount of the wager. In other words, the bigger the wager, the more likely it is that an EGM will be selected. The winning EGM pays the bonus, in response to a command from the slave server, and updates its history record. The selected EGM may, but need not, be locked to prevent further play. The EGM may be locked in different ways, depending upon system configuration. First, the user may check a box in a panel appearing on the display of workstation 15 that requires each EGM to lock up whenever the EGM is a Random Rewards® winner. Second, if the box is not checked, an award may or may not be locked up. The EGM manufacturer configures the EGM for a maximum jackpot payable on the EGM credit meter. If the Random Rewards® payment is below that maximum, the payment is paid to the credit meter, from which it can be wagered or cashed out. If the payment is greater than the maximum, the machine is locked up.
In another aspect of the invention, one or more slave servers can be configured to award another bonus, preferably the Celebration Prizes® promotion, when a Random Rewards® winner is selected. In the Celebration Prizes® promotion, the slave server can be designated to award preselected EGMs a bonus when a Random Rewards® winner is selected. Only EGMs that are linked to the bonus pool that includes the winner are eligible for the Celebration Prizes® payment. Each slave server can be set to provide the Celebration Prizes® promotion, or not, and each property that provides it can set criteria establishing which of the eligible EGMs are awarded a Celebration Prizes® bonus. For example, of the eligible EGMs, Celebration Prizes® winners might be only those with a player's card in, or those whose last bet was a maximum bet, or those who registered a coin drop within a predetermined period of time, or some combination of these or other criteria.
Following payment to the selected EGM, the bonus promotion is continuously repeated. One or more of the bonus pools can be modified by either ending it or making changes to its parameters, such as the contribution rate and the minimum and maximum numbers that define the range from which the lucky number is randomly selected. Commands to modify a pool are entered at workstation 15. The modifications are effective immediately, modifying the current pool. In an alternative embodiment, the modifications are not implemented until after a Random Rewards® winner is selected for the current game associated with the pool to be modified. The commands set a flag, which implements a process after the current game. As a result, the modifications are made commencing with the next game associated with the modified pool.
A new bonus promotion begins by subtracting the lucky number from the current pool, and creating a new current pool by adding a base amount, which is the minimum number for the lower end of the range from which the lucky number is selected; a hidden pool; and a delayed pool (both described below) that are accrued from prior games.
For example, assume that the minimum pool level (base amount) is $1000 and the hidden pool increment rate is 2%. After $2000 of play, the hidden pool value is at $40. If the promotion selects a winner at this point, the sum of the base amount and the hidden pool is $1040, which is put into the current pool. After summing, the hidden pool is reset to zero.
After an award is given and the current pool is established as described above, the hidden pool and the current pool are each adjusted by the delayed pool (described below), and a new lucky number is set between the value of the current pool and the maximum number.
The master server and the slave servers each maintain a delayed pool, which is not displayed to bonus promotion participants and does not contribute to the growth of the current pool during the current promotion. The slave delayed pool is comprised of play on eligible EGMs that were not able to contribute to the bonus. For example, if communication between an EGM and a slave server were lost for a period of time, restoration of communication could cause an immediate large incremental contribution from the EGM resulting from sudden realization of accrued off-line contributions. The restored EGM therefore has a disproportionate opportunity to win the bonus because of the weighting of play involved in the selection of the winning EGM.
When an EGM goes off-line and shows an increment to the slave server after coming back on-line, the total increment goes into the slave server's delayed pool. In other words the delayed pool at each slave server is not multiplied by the contribution percentage; the entire amount of wagers that occurred off-line goes into each slave server's delayed pool. The value of the delayed pools is accrued at each slave server and periodically transmitted to the master server, which maintains the total accrued delayed pool.
The master server's delayed pool works much like the slave servers. The master server delayed pool is comprised of two components. The first component is the delayed pool contributions in dollars from disrupted EGMs. The second component is slave server contribution totals that were not able to contribute to the bonus, again perhaps because of communication difficulties between the slaves and the master. As will be recalled, these totals have already been multiplied by the contribution percentage. As a result, when communication is restored, this component cannot be added directly into the first component of the master server delayed pool. Rather, these totals must be divided by the contribution rate to convert them back to dollars.
The contribution rate, however, can vary from one bonus promotion to the next. The master server must therefore undo the calculation previously applied by the slave server prior to reporting to the master by dividing the slave's accrued contribution by the user-selected percentage from the previous bonus promotion to determine the actual dollars played while the slave server was off-line. The increment in these actual dollars that accrued before the slave went off-line is then added to the delayed pool.
Once the master server has the actual dollars played in the delayed pool—derived from the slave's delayed pools and from undoing the pool contribution calculations as just described—it is distributed to both the new current pool and hidden pool using increment rates defined for the current and hidden pools. As a result, the base amount, and the hidden and delayed pools provide the initial funding for the new bonus pool.
If applying the percentage of the delayed pool to the current pool puts the current pool over 90% of the range between the minimum and maximum numbers, the amount applied from the delayed pool to the current pool is set to 90% of this range. This defines the minimum number and creates a relatively narrow range from which the lucky number is selected. In other words, the current pool is likely to hit a winner in a relatively short time. As the games continue, the amount applied from the delayed pool to each new current pool is limited in the same fashion until the applied percentage from the delayed pool is less than 90% of the range.
It should be appreciated that the amount of the award can be the lucky number. Or it can be a fixed amount or a noncash award, such as a car or the like.
Consideration will now be given to the features that enhance security in system 10. Generally speaking, key distribution center 29 (KDC), manages different types of keys, which will be shortly described, to encrypt digital messages on each LAN, like LAN 18A, and between each LAN and master server 14. Generally speaking, three different types of keys are used in system 10: a setup key, a master node key, and a session key. These keys are used, as will be shortly described, to authenticate and verify messages on the WAN and the LAN. Every message between master server 14 and each of the slave servers, like slave server 27, is authenticated with a signature. Likewise, all messages that authorize a bonus payment between each of the slave servers and the communications boards in their associated slot machines, like slot machine 28, 30, are also signed to authenticate the message.
Consideration will first be given to the setup key, which is a single identical key shared by each of the participating nodes, namely, each slave server, like slave server 27; master server 14; and each of the communication boards in the slot machines, like slot machines 28, 30, that may be selected to participate in the Random Rewards® bonus. The setup key can be installed by installing it in firmware associated with each node. This installation may be accomplished in several ways, including simply including it during the manufacturing or installation process in firmware memory. Preferably, one half of the setup key is encoded on each of two separate magnetic-strip cards. The setup key is then installed by requiring two individuals to swipe each card at each of the nodes, thereby downloading the setup key at each node. This procedure enhances security of the setup keys.
Next, each participating node uses the setup keys to generate a master node key that is a private key shared only between KDC 29 and the node in question. In other words, the KDC generates and stores a private key-pair between the KDC and each participating node in the entire WAN.
Shortly after each node receives the setup key, whether installed in firmware at the outset or installed after system 10 becomes operational, the node sends a request for creation of a master node key to KDC 29. This message is authenticated using a message digest encrypted with the setup key. KDC 29 responds by randomly generating a master node key that is encrypted using the setup key and a 64-bit International Data Encryption Algorithm (IDEA™) Cyphertext Feedback (CFB). This message is also authenticated using a message digest encrypted with the setup key.
The requesting node then sends another message to the KDC, which generates a node table entry and stores the master key for that node. This message is authenticated using a message digest encrypted with the master node key. Thereafter the KDC sends a final message to the requesting node that causes it to remove all memory containing the setup key. This final message is authenticated using a message digest encrypted with the master node key.
The final key, the session key, is implemented by the KDC when it first starts up and periodically thereafter as will be shortly described. A counter, known as the session index, is associated with each session key. Each time the KDC changes session keys, it increments this counter. Whenever a node stores the session key, it associates it with the key counter and makes the key counter part of every message it encrypts. As a result, the receiving node can determine which session key was used for encryption. This is important during the time when session keys are changing, since not all nodes switch simultaneously. All nodes are periodically informed of the current session key index through a plain text message the KDC broadcasts across the entire WAN every 10 seconds. When a node detects that the broadcast session key index identifying the current key is different from the index it has stored, it requests the new session key using a session key request procedure. Once it receives the new session key, the old session key is discarded. This procedure accommodates new devices, devices that have been offline when the period for changing the session key passes (described below), and other situations in which a node does not have the current session key.
The procedure for requesting the session key starts when the requesting node sends a plain text request to KDC 29 requesting the new session key. The KDC responds with a message confirming the request authenticated using the master node key. The node responds by sending a message authenticated using the master node key. This causes the KDC to send the new session key encrypted using the master node key with a 64-bit IDEA™ CFB. It is likewise authenticated using the master node key.
In the present embodiment of the invention, the transmitting node, whether it is the master or slave server, generates the signature by computing the Secure Hash Algorithm (SHA1) over the entire contents of the message. The SHA1 results are then encrypted with a 64-bit International Data Encryption Algorithm (IDEA™) and the current session key.
It can be seen that all messages containing accumulated game play, which the master server uses to maintain the pool, and all pay commands from each slave server to its associated slot machines, are digitally verified and authenticated. As a result, the security of system 10 is greatly enhanced.
In one aspect of the present invention, the user, via configuration workstation 15 can generate an input command to set the period for changing the session key and can modify the period by preselecting a range above and below the selected period during which the session key is randomly distributed. For example, if the user selects 600 minutes as the period for changing the session key, and the range is 10, the session key remains valid for between 590 and 610 minutes. At a randomly selected time between 590 and 610 minutes after the session key is established, a new session key is distributed. This feature further improves system security.
Also, the user, via the configuration workstation, can remove a node from the system when there is a security breach. Similarly, the user can use the configuration workstation to enter a command that overrides the automated changing of the session keys just described to require that a new session key be immediately distributed. Both of these features further enhance system security.
The present embodiment has been illustrated with a single master server having multiple slave servers connected via a WAN. More than one master server could implement bonuses on the same WAN. In other words, another master server could be added to the WAN. The additional master would have its own slave servers and maintain bonus pools that are separate from the other master or master servers.
Finally, consideration will be given to payment of other bonuses, such as promotional awards, in addition to the Random Rewards® promotion described above. The present invention can implement direct payment of these rewards across multiple properties at the slot machine including, e.g., direct transfers of redeemable credits to the slot machine; direct transfers of non-redeemable credits to the slot machine (Xtra Credit®), as described in U.S. patent application Ser. No. 09/134,598, filed Aug. 14, 1998, now U.S. Pat. No. 6,371,852, which is hereby incorporated by reference for all purposes; and temporary change of the machine award schedule.
As in the existing single property implementations, the extension of bonusing concepts to the multi-property environment also allows more streamlined communication of promotional information. Instead of, or in addition to, more traditional communication methods such as direct mail or brochures, direct communication of promotional information can occur at the slot machine.
In addition, several features and functions that rely on the multi-property aspect can be implemented by the present invention. For example:
The present invention can also be implemented to automate delivery of promotional, loyalty-based bonuses at multiple casinos on a WAN as described herein. Such a system has the following characteristics:
While the invention has been shown and described with reference to a certain preferred embodiment thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
This application claims priority from provisional application U.S. 60/326,030 titled “SYSTEM FOR AWARDING A BONUS TO A GAMING DEVICE ON A WIDE AREA NETWORK”, filed Sep. 28, 2001, the contents of which are hereby incorporated herein for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
3998309 | Mandas et al. | Dec 1976 | A |
4072930 | Lucero et al. | Feb 1978 | A |
4200770 | Hellman et al. | Apr 1980 | A |
4238127 | Lucero et al. | Dec 1980 | A |
4283709 | Lucero et al. | Aug 1981 | A |
4335809 | Wain | Jun 1982 | A |
4409656 | Andersen et al. | Oct 1983 | A |
4494197 | Troy et al. | Jan 1985 | A |
4573681 | Okada | Mar 1986 | A |
4582324 | Koza et al. | Apr 1986 | A |
4624459 | Kaufman | Nov 1986 | A |
4636951 | Harlick | Jan 1987 | A |
4652998 | Koza et al. | Mar 1987 | A |
4657256 | Okada | Apr 1987 | A |
4669731 | Clarke | Jun 1987 | A |
4760527 | Sidley | Jul 1988 | A |
4764666 | Bergeron | Aug 1988 | A |
4772023 | Okada | Sep 1988 | A |
4805907 | Hagiwara | Feb 1989 | A |
4837728 | Barrie et al. | Jun 1989 | A |
4842278 | Markowicz | Jun 1989 | A |
4856787 | Itkis | Aug 1989 | A |
4871171 | Rivero | Oct 1989 | A |
4880237 | Kishishita | Nov 1989 | A |
4926327 | Sidley | May 1990 | A |
4964638 | Ishida | Oct 1990 | A |
5038022 | Lucero | Aug 1991 | A |
5048833 | Lamle | Sep 1991 | A |
5074559 | Okada | Dec 1991 | A |
5116055 | Tracy | May 1992 | A |
5123649 | Tiberio | Jun 1992 | A |
5178390 | Okada | Jan 1993 | A |
5217224 | Sincock | Jun 1993 | A |
5249800 | Hilgendorf et al. | Oct 1993 | A |
5259616 | Bergmann | Nov 1993 | A |
5275400 | Weingardt et al. | Jan 1994 | A |
5280909 | Tracy | Jan 1994 | A |
5286023 | Wood | Feb 1994 | A |
5321241 | Craine | Jun 1994 | A |
5324035 | Morris et al. | Jun 1994 | A |
5326104 | Pease et al. | Jul 1994 | A |
5332219 | Marnell, II et al. | Jul 1994 | A |
5342049 | Wichinsky et al. | Aug 1994 | A |
5344144 | Canon | Sep 1994 | A |
5351970 | Fioretti | Oct 1994 | A |
5393057 | Marnell, II | Feb 1995 | A |
5398932 | Eberhardt et al. | Mar 1995 | A |
5401024 | Simunek | Mar 1995 | A |
5423539 | Nagao | Jun 1995 | A |
5429361 | Raven et al. | Jul 1995 | A |
5470079 | LeStrange et al. | Nov 1995 | A |
5476259 | Weingardt | Dec 1995 | A |
5507489 | Reibel et al. | Apr 1996 | A |
5524888 | Heidel | Jun 1996 | A |
5544893 | Jones et al. | Aug 1996 | A |
5547192 | Ishibashi | Aug 1996 | A |
5564700 | Celona | Oct 1996 | A |
5570885 | Ornstein | Nov 1996 | A |
5580309 | Piechowiak | Dec 1996 | A |
5586937 | Menashe | Dec 1996 | A |
5611535 | Tiberio | Mar 1997 | A |
5611730 | Weiss | Mar 1997 | A |
5645486 | Nagao et al. | Jul 1997 | A |
5655961 | Acres et al. | Aug 1997 | A |
5674128 | Holch et al. | Oct 1997 | A |
5702304 | Acres et al. | Dec 1997 | A |
5707285 | Place et al. | Jan 1998 | A |
5741183 | Acres et al. | Apr 1998 | A |
5743800 | Huard et al. | Apr 1998 | A |
5752882 | Acres et al. | May 1998 | A |
5761647 | Boushy | Jun 1998 | A |
5762552 | Vuong et al. | Jun 1998 | A |
5766076 | Pease et al. | Jun 1998 | A |
RE35864 | Weingardt | Jul 1998 | E |
5779545 | Berg et al. | Jul 1998 | A |
5779547 | SoRelle et al. | Jul 1998 | A |
5788573 | Baerlocher et al. | Aug 1998 | A |
5800269 | Holch et al. | Sep 1998 | A |
5807172 | Piechowiak | Sep 1998 | A |
5816918 | Kelly et al. | Oct 1998 | A |
5820459 | Acres et al. | Oct 1998 | A |
5823874 | Adams | Oct 1998 | A |
5833538 | Weiss | Nov 1998 | A |
5833540 | Miodunski et al. | Nov 1998 | A |
5836817 | Acres et al. | Nov 1998 | A |
5848932 | Adams | Dec 1998 | A |
5851149 | Xidos et al. | Dec 1998 | A |
5855515 | Pease et al. | Jan 1999 | A |
5876284 | Acres et al. | Mar 1999 | A |
5882261 | Adams | Mar 1999 | A |
5885158 | Torango et al. | Mar 1999 | A |
5941773 | Harlick | Aug 1999 | A |
5944606 | Gerow | Aug 1999 | A |
5970143 | Schneier et al. | Oct 1999 | A |
5984779 | Bridgeman et al. | Nov 1999 | A |
6001016 | Walker et al. | Dec 1999 | A |
6003013 | Boushy et al. | Dec 1999 | A |
6012982 | Piechowiak et al. | Jan 2000 | A |
6012983 | Walker et al. | Jan 2000 | A |
6030288 | Davis et al. | Feb 2000 | A |
6039648 | Guinn et al. | Mar 2000 | A |
6048269 | Burns et al. | Apr 2000 | A |
6050895 | Luciano, Jr. et al. | Apr 2000 | A |
6059659 | Busch et al. | May 2000 | A |
6068553 | Parker | May 2000 | A |
6071190 | Weiss et al. | Jun 2000 | A |
6077162 | Weiss | Jun 2000 | A |
6080062 | Olson | Jun 2000 | A |
6082887 | Feuer et al. | Jul 2000 | A |
6089977 | Bennett | Jul 2000 | A |
6089980 | Gauselmann | Jul 2000 | A |
6099408 | Schneier et al. | Aug 2000 | A |
6110041 | Walker et al. | Aug 2000 | A |
6110043 | Olsen | Aug 2000 | A |
6117011 | Lvov | Sep 2000 | A |
6126542 | Fier | Oct 2000 | A |
6135884 | Hedrick et al. | Oct 2000 | A |
6142872 | Walker et al. | Nov 2000 | A |
6146270 | Huard et al. | Nov 2000 | A |
6146273 | Olsen | Nov 2000 | A |
6152823 | LaCoste et al. | Nov 2000 | A |
6162122 | Acres et al. | Dec 2000 | A |
6168523 | Piechowiak et al. | Jan 2001 | B1 |
6179711 | Yoseloff | Jan 2001 | B1 |
6183366 | Goldberg et al. | Feb 2001 | B1 |
6190255 | Thomas et al. | Feb 2001 | B1 |
6203010 | Jorasch | Mar 2001 | B1 |
6210275 | Olsen | Apr 2001 | B1 |
6210277 | Stefan | Apr 2001 | B1 |
6217448 | Olsen | Apr 2001 | B1 |
6219836 | Wells et al. | Apr 2001 | B1 |
6220961 | Keane et al. | Apr 2001 | B1 |
6224482 | Bennett | May 2001 | B1 |
6224484 | Okuda et al. | May 2001 | B1 |
6231445 | Acres | May 2001 | B1 |
6234896 | Walker et al. | May 2001 | B1 |
6241608 | Torango | Jun 2001 | B1 |
6244958 | Acres | Jun 2001 | B1 |
6254483 | Acres | Jul 2001 | B1 |
6257981 | Acres et al. | Jul 2001 | B1 |
6264557 | Schneier et al. | Jul 2001 | B1 |
6270409 | Shuster | Aug 2001 | B1 |
6287194 | Okada et al. | Sep 2001 | B1 |
6287202 | Pascal et al. | Sep 2001 | B1 |
6293866 | Walker et al. | Sep 2001 | B1 |
RE37414 | Harlick | Oct 2001 | E |
6302790 | Brossard | Oct 2001 | B1 |
6302793 | Fertitta, III et al. | Oct 2001 | B1 |
6302794 | Ogawa | Oct 2001 | B1 |
6309298 | Gerow | Oct 2001 | B1 |
6309300 | Glavich | Oct 2001 | B1 |
6312333 | Acres | Nov 2001 | B1 |
6319122 | Packes, Jr. et al. | Nov 2001 | B1 |
6319125 | Acres | Nov 2001 | B1 |
6322309 | Thomas et al. | Nov 2001 | B1 |
6358149 | Schneider et al. | Mar 2002 | B1 |
6361441 | Walker et al. | Mar 2002 | B1 |
6364768 | Acres et al. | Apr 2002 | B1 |
6364769 | Weiss et al. | Apr 2002 | B1 |
6371852 | Acres | Apr 2002 | B1 |
6375567 | Acres | Apr 2002 | B1 |
6375568 | Roffman et al. | Apr 2002 | B1 |
6375569 | Acres | Apr 2002 | B1 |
6393563 | Maruyama et al. | May 2002 | B1 |
6416409 | Jordan | Jul 2002 | B1 |
6419583 | Crumby et al. | Jul 2002 | B1 |
6431983 | Acres | Aug 2002 | B2 |
6435511 | Vancura et al. | Aug 2002 | B1 |
6435968 | Torango | Aug 2002 | B1 |
6456716 | Arnold | Sep 2002 | B1 |
RE37885 | Acres et al. | Oct 2002 | E |
6461241 | Webb et al. | Oct 2002 | B1 |
6511376 | Walker et al. | Jan 2003 | B2 |
6537150 | Luciano et al. | Mar 2003 | B1 |
6565434 | Acres | May 2003 | B1 |
6569013 | Taylor | May 2003 | B1 |
6589115 | Walker et al. | Jul 2003 | B2 |
6592458 | Ho | Jul 2003 | B1 |
6592460 | Torango | Jul 2003 | B2 |
6607438 | Baerlocher et al. | Aug 2003 | B2 |
6607441 | Acres | Aug 2003 | B1 |
6620046 | Rowe | Sep 2003 | B2 |
6626758 | Parham et al. | Sep 2003 | B1 |
6634941 | Olive | Oct 2003 | B2 |
6645074 | Thomas et al. | Nov 2003 | B2 |
6645077 | Rowe | Nov 2003 | B2 |
6648762 | Walker et al. | Nov 2003 | B2 |
6656048 | Olsen | Dec 2003 | B2 |
6663487 | Ladner | Dec 2003 | B1 |
6675152 | Prasad | Jan 2004 | B1 |
6682421 | Rowe et al. | Jan 2004 | B1 |
6685563 | Meekins et al. | Feb 2004 | B1 |
6702674 | De Bruin et al. | Mar 2004 | B1 |
6712695 | Mothwurf et al. | Mar 2004 | B2 |
6712697 | Acres | Mar 2004 | B2 |
6712698 | Paulsen et al. | Mar 2004 | B2 |
6722986 | Lyons | Apr 2004 | B1 |
6746328 | Cannon et al. | Jun 2004 | B2 |
6749510 | Giobbi | Jun 2004 | B2 |
6776715 | Price | Aug 2004 | B2 |
6780111 | Cannon et al. | Aug 2004 | B2 |
6786819 | Baerlocher et al. | Sep 2004 | B2 |
6786824 | Cannon | Sep 2004 | B2 |
6790141 | Muir | Sep 2004 | B2 |
6800030 | Acres | Oct 2004 | B2 |
6805634 | Wells et al. | Oct 2004 | B1 |
6832956 | Boyd et al. | Dec 2004 | B1 |
6832958 | Acres et al. | Dec 2004 | B2 |
6837788 | Cannon | Jan 2005 | B2 |
6869361 | Sharpless et al. | Mar 2005 | B2 |
6887154 | Luciano et al. | May 2005 | B1 |
6910964 | Acres | Jun 2005 | B2 |
6918834 | Vancura | Jul 2005 | B2 |
6932707 | Duhamel | Aug 2005 | B2 |
6939234 | Beatty | Sep 2005 | B2 |
RE38812 | Acres et al. | Oct 2005 | E |
6966834 | Johnson | Nov 2005 | B1 |
6984173 | Piechowiak et al. | Jan 2006 | B1 |
6984174 | Cannon et al. | Jan 2006 | B2 |
7037195 | Schneider et al. | May 2006 | B2 |
7056215 | Olive | Jun 2006 | B1 |
7108603 | Olive | Sep 2006 | B2 |
7127069 | Nguyen | Oct 2006 | B2 |
7260834 | Carlson | Aug 2007 | B1 |
20010007127 | Staring | Jul 2001 | A1 |
20010049303 | Found et al. | Dec 2001 | A1 |
20010055990 | Acres | Dec 2001 | A1 |
20020049909 | Jackson et al. | Apr 2002 | A1 |
20020068631 | Raverdy et al. | Jun 2002 | A1 |
20020071557 | Nguyen | Jun 2002 | A1 |
20020116615 | Nguyen et al. | Aug 2002 | A1 |
20020138594 | Rowe | Sep 2002 | A1 |
20020152120 | Howington | Oct 2002 | A1 |
20020165023 | Brosnan et al. | Nov 2002 | A1 |
20020187834 | Rowe et al. | Dec 2002 | A1 |
20030027625 | Rowe | Feb 2003 | A1 |
20030027630 | Kelly et al. | Feb 2003 | A1 |
20030028480 | Rowe | Feb 2003 | A1 |
20030032485 | Cockerille et al. | Feb 2003 | A1 |
20030045350 | Baerlocher et al. | Mar 2003 | A1 |
20030045353 | Paulsen et al. | Mar 2003 | A1 |
20030050111 | Saffari | Mar 2003 | A1 |
20030060279 | Torango | Mar 2003 | A1 |
20030083943 | Adams et al. | May 2003 | A1 |
20030092477 | Luciano, Jr. et al. | May 2003 | A1 |
20030092484 | Schneider | May 2003 | A1 |
20030144965 | Prasad | Jul 2003 | A1 |
20030182574 | Whitten et al. | Sep 2003 | A1 |
20030222402 | Olive | Dec 2003 | A1 |
20030228904 | Acres et al. | Dec 2003 | A1 |
20030228912 | Wells et al. | Dec 2003 | A1 |
20030232647 | Moser | Dec 2003 | A1 |
20040009811 | Torango | Jan 2004 | A1 |
20040087368 | Gauselmann | May 2004 | A1 |
20040235552 | Gauselmann | Nov 2004 | A1 |
20040242297 | Walker et al. | Dec 2004 | A1 |
20050032573 | Acres et al. | Feb 2005 | A1 |
20050070353 | Webb et al. | Mar 2005 | A1 |
20050070356 | Mothwurf et al. | Mar 2005 | A1 |
20050079911 | Nakatsu | Apr 2005 | A1 |
20050086478 | Pienado et al. | Apr 2005 | A1 |
20050101374 | Acres | May 2005 | A1 |
20050119047 | Olive | Jun 2005 | A1 |
20050143168 | Torango | Jun 2005 | A1 |
20050176488 | Olive | Aug 2005 | A1 |
20050192099 | Nguyen et al. | Sep 2005 | A1 |
20050209004 | Torango | Sep 2005 | A1 |
20050209005 | Acres et al. | Sep 2005 | A1 |
20060025210 | Johnson | Feb 2006 | A1 |
20060172804 | Acres et al. | Aug 2006 | A1 |
20060183529 | Acres et al. | Aug 2006 | A1 |
Number | Date | Country |
---|---|---|
524709 | Aug 1979 | AU |
3936378 | Mar 1980 | AU |
6668381 | Aug 1981 | AU |
542455 | Oct 1984 | AU |
555905 | Nov 1984 | AU |
589158 | Aug 1986 | AU |
628330 | Nov 1989 | AU |
630112 | Mar 1990 | AU |
649009 | Aug 1991 | AU |
655801 | Sep 1992 | AU |
633469 | Jan 1993 | AU |
680920 | Aug 1995 | AU |
7024796 | Apr 1997 | AU |
704365 | Apr 1997 | AU |
704372 | Apr 1997 | AU |
707687 | Apr 1997 | AU |
0 7780 | Jul 1997 | AU |
680602 | Jul 1997 | AU |
709724 | Aug 1997 | AU |
0 9090 | Sep 1997 | AU |
PO 9102 | Sep 1997 | AU |
716299 | Jan 1998 | AU |
199662115 | Feb 1998 | AU |
722107 | May 1998 | AU |
199743615 | May 1998 | AU |
721968 | Jun 1998 | AU |
758306 | Aug 1998 | AU |
733963 | Sep 1998 | AU |
743079 | Nov 1998 | AU |
748263 | Nov 1998 | AU |
756180 | Jan 1999 | AU |
755826 | Feb 1999 | AU |
738686 | Mar 1999 | AU |
749222 | Mar 1999 | AU |
736679 | May 1999 | AU |
728788 | Jul 1999 | AU |
1999 17318 | Sep 1999 | AU |
768285 | Sep 1999 | AU |
753102 | Nov 1999 | AU |
765084 | Nov 1999 | AU |
714299 | Dec 1999 | AU |
760617 | Jan 2000 | AU |
744569 | Mar 2001 | AU |
771847 | Mar 2001 | AU |
2001100032 | Jun 2001 | AU |
2001100033 | Jun 2001 | AU |
3415114 | Oct 1985 | DE |
0 342 797 | Nov 1989 | EP |
0420586 | Apr 1991 | EP |
0 444 932 | Oct 1995 | EP |
0770415 | May 1997 | EP |
EP 1344195 | Sep 2003 | FR |
2083936 | Mar 1982 | GB |
2 139 390 | Nov 1984 | GB |
2 147 773 | May 1985 | GB |
2 148 135 | May 1985 | GB |
2151054 | Jul 1985 | GB |
2153572 | Aug 1985 | GB |
2180087 | Mar 1987 | GB |
2191030 | Dec 1987 | GB |
2230373 | Oct 1990 | GB |
2262642 | Jun 1993 | GB |
5184709 | Jul 1993 | JP |
6335560 | Dec 1994 | JP |
7148307 | Jun 1995 | JP |
09192289 | Jul 1997 | JP |
09248384 | Sep 1997 | JP |
10033829 | Feb 1998 | JP |
WO 8002512 | Nov 1980 | WO |
WO 9412256 | Jun 1994 | WO |
WO 9522811 | Aug 1995 | WO |
WO 9530944 | Nov 1995 | WO |
WO 9612262 | Apr 1996 | WO |
WO 9624421 | Aug 1996 | WO |
WO 9712338 | Apr 1997 | WO |
WO 9712315 | Apr 1997 | WO |
WO 9727568 | Jul 1997 | WO |
WO 9807484 | Feb 1998 | WO |
WO 9818532 | May 1998 | WO |
WO 9835309 | Aug 1998 | WO |
WO 9903078 | Jan 1999 | WO |
WO 9910849 | Mar 1999 | WO |
WO 9960498 | Nov 1999 | WO |
WO 0003775 | Jan 2000 | WO |
WO 0032286 | Jun 2000 | WO |
WO 0110523 | Feb 2001 | WO |
WO 0115790 | Mar 2001 | WO |
WO 0167218 | Sep 2001 | WO |
WO 02052515 | Jul 2002 | WO |
WO 03030066 | Apr 2003 | WO |
WO 03063019 | Jul 2003 | WO |
Number | Date | Country | |
---|---|---|---|
20030092484 A1 | May 2003 | US |
Number | Date | Country | |
---|---|---|---|
60326030 | Sep 2001 | US |