The invention is directed towards a method and apparatus for solving an optimization problem.
Design engineers design IC's by transforming logical or circuit descriptions of IC's into geometric descriptions, called layouts. IC layouts typically include circuit modules with pins, and interconnect lines that connect the circuit-module pins. A net is typically defined as a collection of pins that need to be connected. A list of all or some of the nets in a layout is referred to as a net list.
To create layouts, design engineers typically use electronic design automation (“EDA”) applications. These applications provide sets of computer-based tools for creating, editing, and analyzing IC design layouts. Routers are one type of EDA tool. A router defines routes for interconnect lines that connect the pins of nets.
A router typically receives a routing problem that requires it to identify a route for each net in a net list. Some routers solve such a routing problem by first identifying multiple routes for each net. These routers then try to select a combination of routes that includes one route for each net and that optimizes a particular objective function. The objective function typically expresses one or more metric costs, such as length of routes, congestion in the design, etc.
Routers of this sort use different techniques to select the combination of routes from the set of identified solutions. One technique is randomized rounding. Generally, this technique is a probabilistic method that converts an exact solution of a relaxed problem into an approximate solution to an original problem. With randomized rounding, an EDA router interprets fractional routing solutions (e.g., solutions provided by a linear program) as probabilities for rounding the solutions. Numerous examples of this technique can be found in the literature. One such reference is disclosed in Randomized Algorithms, by Rajeev Motwani and Prabhakar Raghavan, Cambridge University Press (1995, 1997).
Randomized rounding works well in certain situations but not in others. For instance, one type of routing is global routing. Global routing typically identifies routes between cells, which partition the layout into several regions. Such cells are called Gcells. In global routing, randomized rounding works well when the Gcells are large, but does not work as well when the Gcells are small. Therefore, there is a need in the art for a better method for selecting a combination of routes from a set of routes that includes one or more routes for each net in a net list. More generally, there is a need for a better method for solving optimization problems.
Some embodiments of the invention provide a method of solving an optimization problem. The problem includes a plurality of elements, and one or more solutions have been previously identified for each element. The method specifies a first solution set that has one identified solution for each element. In some embodiments, the method then iteratively examines all the elements of the problem. During the examination of each particular element, the method iteratively examines all the identified solutions for the particular element. During the examination of each particular solution, the method replaces the current solution for the particular element in the first solution set with a previously unexamined solution for the particular element if the replacement would improve the first set.
The novel features of the invention are set forth in the appended claims. However, for the purpose of explanation, several embodiments of the invention are set forth in the following figures.
In the following description, numerous details are set forth for the purpose of explanation. However, one of ordinary skill in the art will realize that the invention may be practiced without the use of these specific details. In other instances, well-known structures and devices are shown in block diagram form in order not to obscure the description of the invention with unnecessary detail.
The process 100 solves the routing problem by first identifying several global routes for each net and then exploring the solution space to find an optimal solution. The process 100 can quickly and flexibly identify a good combination of routes for a set of nets. To explore the solution space, the process has three nested loops: an outer loop, a middle loop, and an inner loop. Generally (1) each iteration of the outer loop (which starts at 110) explores the solution space from a different starting group of routes, (2) for a particular starting group of routes, each iteration of the middle loop (which starts at 115) explores the solution space for a particular order of the nets, and (3) for each particular order of the nets, each iteration of the inner loop (which starts at 120) iteratively examines the routes of different nets. These loops are further described below.
The process 100 initially identifies (at 105) several sets of global routes. Each set has one global route for each net in the net list. Different embodiments use different techniques to identify these sets. For instance, some embodiments use techniques like those described in U.S. patent application Ser. No. 10/013,819, filed on Dec. 7, 2001, published as U.S. Patent Application 2003/0079193. Other embodiments use techniques like those described in U.S. patent application Ser. No. 10/334,690, entitled “Method and Apparatus for Routing”, published as U.S. Patent Application 2004/0098695, filed concurrently with the present application. This concurrently filed application is incorporated herein by reference.
Each identified global route connects several Gcells. Some or all of the Gcells connected by a global route for a net contain routable elements (e.g., pins) of the net.
After identifying several sets of global routes at 105, the process specifies (at 110) a current group of routes. The specified group includes a route for each net in the net list. In some embodiments, all the routes in the specified group are from one set of global routes that the process identified at 105. In other embodiments, the routes of the specified group are from two or more of the sets identified at 105. For instance, if the netlist included eight nets, the specified group of routes might include five routes from one identified set and three routes from another identified set.
After 110, the process specifies (at 115) an order for the nets. Different embodiments use different techniques to specify such an order. For instance, some embodiments specify an order based on descending entropies of the nets, others based on Steiner tree lengths of the nets, and yet others based on bounding boxes of the nets. Still other embodiments randomly order the nets at 115.
The process 100 iterates through 115 several times for a particular starting group of routes that it selects at 110. In one or more of the iterations through 115, the process might specify an order for the nets that is based on the frequency of occurrence of the routes for the nets in the identified set of routes. Specifically, in some embodiments, a net can have the same route in two or more of the sets identified at 105. Accordingly, a frequency parameter (e.g., a probability) can be specified for each identified route of each net. For instance, the process might specify eight sets of routes at 105. However, for a particular net, the eight sets might only include three different routes, a first that is in five sets, a second that is in two sets, and a third that is in only one set. Based on the times that the first, second, and third routes appear in the identified sets, probability values ⅝, ¼, and ⅛ can be respectively assigned to the first, second, and third routes.
One order that can be specified in an iteration through 115 is an order that is based on descending maximum probability values of the nets. For instance, in a simple example, the net list might include three nets, with the first net having a route that appears in 90% of the identified solutions (specified at 105), the second net having a route that appears in 70% of the identified solutions, and the third net having a route that appears in 55% of the identified solutions. In this example, an order that is based on descending maximum probability values would specify the first net, followed by the second net, followed by the third net. One of ordinary skill will realize that other orders can be specified that are derived from probability values relating to frequency of routes in the identified sets of routes.
After 115, the process 100 selects (at 120) a net according to the order specified at 115. For the net selected at 120, the process then determines (at 122) whether the identified sets of routes include at least two unique routes for the selected net. If not, the process transitions to 145, which is further described below.
Otherwise, the process selects (at 125) a route that is one of the identified routes for the selected net but is not the current route for this net in the current group of routes. The process next determines (at 130) whether replacing the selected net's route in the current group with the route selected at 125 would improve the quality of the routing. This determination entails computing two metric scores. One metric score quantifies the quality of the current group of routes. The other metric score quantifies the quality of the current group of routes with the selected net's route in the current group replaced with the route selected at 125.
Different embodiments of the invention use different objective functions to compute a metric score. Some embodiments use the following function (A), which has two components, a first (congestion) component and a second (length) component.
In this function, (1) j represents one of m edges between Gcells, (2) e is the base of the natural logarithm, (3) ε1 and ε2 are user-adjustable parameters, (4) usage(j) is the number of routes in the group of routes that use the edge j, (5) capacity(j) is the estimated maximum number of available tracks along the edge j, (6) goal(layer(j)) is a target upper bound on the congestion ratio on the design-layout layer that contains edge j, (7) n is one of the p nets in the netlist, (8) length(n) is the length of the route of net n in the group of nets, (9) lower_bound(n) is a lower bound for the route length of the net n, and (10) Yj and Yl are constants that normalize the length and congestion components. When this function is used, a smaller metric score means better quality.
In some embodiments, an edges j in function (A) can be a planar or non-planar edge. A non-planar edge represents a via, which typically is a transition between two adjacent layers within a Gcell. Accordingly, in these embodiments, the congestion component of function (A) not only accounts for planar congestion, but also accounts for via (non-planar) congestion. Instead of merging the via congestion cost into the overall congestion cost, the function (A) in other embodiments can have a third component that expresses the via congestion cost. Having a third component would allow the user-adjustable epsilon parameter ε for via congestion to be different than the user-adjustable epsilon parameter for the planar wire congestion.
If the quality (i.e., the metric score) of the current group of routes does not improve with the route selected at 125, the process transitions from 130 to 140, which is further described below. On the other hand, if the quality of the current group of routes improves with the route selected at 125, the process replaces (at 135) the selected net's current route in the group with the route selected at 125, and then transitions to 140.
At 140, the process determines whether, during its current loop through 120–145 (i.e., during the current instance of the inner loop), it has examined all the routes that it identified at 105 for the selected net. If not, the process transitions back to 125 to select, for the selected net, a route that it has not yet examined in its current loop through 120–145.
Otherwise, the process determines (at 145) whether it has examined all the nets in the netlist during its current loop through 115–150 (i.e., during the current instance of the middle loop). If not, the process transitions back to 120 to select another net according to the order specified at 115.
When the process determines (at 145) that it has examined all the nets in the netlist during its current loop through 115–150, it determines (at 150) whether it has examined enough permutations of routes based on the same initial group of routes that were specified at 110. Different embodiments base the determination at 150 on different criteria. Examples of such criteria include the number of iterations, the percentage of improvement in the routing quality between the last two or more iterations, etc. Some embodiments might base this determination on different criteria during different iterations through 150.
If the process determines (at 150) that it has not examined enough permutations, the process transitions back to 115 to specify an order for the nets. In some embodiments, this new order is different from all the orders that the process set in its previous iterations through 115, while, in other embodiments, this order might be the same as one of the previously set ones. For the newly specified order, the process then performs operations 120–150 as described above.
Once the process 100 determines (at 150) that it has done enough iterations through the nets for the starting solution specified at 110, the process compares (at 155) the metric score of the current group of routes with a Best_Score that represents the score of the best group of routes that the process has identified up to this stage. If the current group's score is better than the Best_Score, the process stores (at 155) the current group of routes as the Best_Solution that it has encountered up to this stage. At the start of the process 100, some embodiments initialize the Best_Score to a very large number.
Next, the process determines (at 160) whether it has started its exploration of the solution space from a sufficient number of different starting points. If not, the process transitions back to 110 to specify another initial group of routes as the current group of routes. In some embodiments, this group of routes is different from all the groups that the process previously specified in its previous iteration through 110. For the newly specified group, the process then performs operations 115–160 as described above. When the process determines (at 160) that it has examined enough starting points for its search, the process identifies (at 165) the Best_Solution as the solution to the routing problem. The process then terminates.
The process 500 iteratively selects one identified route for each net. Specifically, during each iteration, the process selects the identified route that least increases an exponential tracking cost, as further described below. The process 500 initially orders the nets based on decreasing maximum probability values of the routes for the nets. Such probability values and orders based on such values were described above in connection with operation 115 of process 100.
After 505, the process 500 selects (at 510) the first net according to the order specified at 505. It then selects (at 515) the route for the first net that has the best metric score. In some embodiments, the process uses the following objective function (B) to compute the metric scores of each route for the first net.
In this function, (1) j represents one of m edges between Gcells, (2) e is the base of the natural logarithm, (3) ε1 and ε2 are user-adjustable parameters, (4) usages) indicates whether the route uses the edge j, (5) capacity(j) is the estimated maximum number of available tracks along the edge j, (6) goal(layer(j)) is a target upper bound on the congestion ratio on the design-layout layer that contains edge j, (7) net is the selected first net, (8) length(net) is the length of the route for the net, (9) lower_bound(net) is the lower bound for the route length of the net, and (10) Yj and Yl are constants that normalize the length and congestion components.
The process then selects (at 520) the next net according to the order specified at 505. From the set of routes identified for the selected net, the process then selects (at 525) the route that results in the smallest exponential tracking metric score. Some embodiments use the following function (C), which is similar to the above-described function (A).
In this function, (1) j represents one of m edges between Gcells, (2) e is the base of the natural logarithm, (3) ε1 and ε2 are user-adjustable parameters, (4) usages) is the number of routes that have been selected thus far that use the edge j, (5) capacity(j) is the estimated maximum number of available tracks along the edge j, (6) goal(layer(j)) is a target upper bound on the congestion ratio on the design-layout layer that contains edge j, (7) n is one of the p nets selected thus far, (8) length(n) is the length of the route of net n, (9) lower_bound(n) is a lower bound for the route length of the net n, and (10) Yj and Yl are constants that normalize the length and congestion components.
To select (at 525) the route for the selected net, some embodiments compute the value of function (C) for each route in the set of routes identified for the selected net. For each particular route of the selected net, the function (C) is computed for a set of routes that includes the particular route and all routes previously selected (at 510 or 525) for previously selected nets.
After 525, the process determines (at 530) whether it has selected a route for each net. If not, the process selects (at 520) the next net according to the specified order, and then selects (at 525) the route (from the set of routes identified for the selected net) that results in the smallest exponential tracking metric score. When the process determines at 530 that it has selected a route for each net, it terminates.
The bus 605 collectively represents all system, peripheral, and chipset buses that support communication among internal devices of the computer system 600. For instance, the bus 605 communicatively connects the processor 610 with the read-only memory 620, the system memory 615, and the permanent storage device 625.
From these various memory units, the processor 610 retrieves instructions to execute and data to process in order to execute the processes of the invention. The read-only-memory (ROM) 620 stores static data and instructions that are needed by the processor 610 and other modules of the computer system. The permanent storage device 625, on the other hand, is a read-and-write memory device. This device is a non-volatile memory unit that stores instruction and data even when the computer system 600 is off. Some embodiments of the invention use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive) as the permanent storage device 625. Other embodiments use a removable storage device (such as a floppy disk or zip® disk, and its corresponding disk drive) as the permanent storage device.
Like the permanent storage device 625, the system memory 615 is a read-and-write memory device. However, unlike storage device 625, the system memory is a volatile read-and-write memory, such as a random access memory. The system memory stores some of the instructions and data that the processor needs at runtime. In some embodiments, the invention's processes are stored in the system memory 615, the permanent storage device 625, and/or the read-only memory 620.
The bus 605 also connects to the input and output devices 630 and 635. The input devices enable the user to communicate information and select commands to the computer system. The input devices 630 include alphanumeric keyboards and cursor-controllers. The output devices 635 display images generated by the computer system. For instance, these devices display IC design layouts. The output devices include printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD).
Finally, as shown in
While the invention has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention. For instance, some embodiments might use different cost functions than those described above. Several of the above-described cost functions divide the length of each net's route by a lower-bound for the route length of the net. Instead of the lower-bound, other embodiments might use as a divisor another estimate of route length for the net. For example, some embodiments might use the length of a congestion-unaware route for the net. The generation of a congestion-unaware route is described in the above-incorporated application.
Also, the cost function of some embodiments might include only congestion components and not include any wirelength components. Alternatively, some embodiments might use a different wirelength component, such as
where T. E. L. is the total length of the estimated routes (e.g., congestion-unaware routes) for the p nets. The estimated lengths could be the lower-bound lengths or some other estimated lengths. Other embodiments might use an equation that uses both this wirelength component and the wirelength component of the above-described equations.
Still other embodiments might slightly modify the wirelength component of the above-described equations slightly. For instance, some embodiments described above express the wirelength component as
Instead of this formulation, some embodiments might use
where B is a factor related to the importance of the net. This factor B is smaller (e.g., it is 1) for important critical nets (e.g., time critical nets) that need shorter routes, while it is larger (e.g., it is 3) for non-critical nets that can have longer routes. Accordingly, this factor causes the selection of shorter routes for critical nets, by increasing the wirelength cost of these nets much faster than the wirelength cost of non-critical nets. One of ordinary skill will realize that the net-importance factor B can also be multiplied by the net's route length (i.e., by length(n)). In this situation, the factor B is larger for an important time-critical net, and is smaller for a non-critical net.
Several embodiments were described above for solving a global routing optimization problem. One of ordinary skill will realize, however, that other embodiments can be used to solve other classes of optimization problems. In addition, the process 100 initially identifies (at 105) sets of solutions, where each set includes a global route for each net in the net list. Other embodiments, however, might not identify such sets. For instance, some embodiments might just identify (at 105) one or more routes for each net, and then specify (at 110) different starting groups of routes by selecting different routes for some or all of the nets. Thus, one of ordinary skill in the art would understand that the invention is not to be limited by the foregoing illustrative details, but rather is to be defined by the following claims.
This patent application claims the benefit of U.S. Provisional Patent Application 60/427,131, filed Nov. 18, 2002.
Number | Name | Date | Kind |
---|---|---|---|
4615011 | Linsker | Sep 1986 | A |
4673966 | Shimoyama | Jun 1987 | A |
4777606 | Fournier | Oct 1988 | A |
4782193 | Linsker | Nov 1988 | A |
4855929 | Nakajima | Aug 1989 | A |
5224057 | Igarashi et al. | Jun 1993 | A |
5360948 | Thornberg | Nov 1994 | A |
5375069 | Satoh et al. | Dec 1994 | A |
5519836 | Gawlick et al. | May 1996 | A |
5532934 | Rostoker | Jul 1996 | A |
5550748 | Xiong | Aug 1996 | A |
5578840 | Scepanovic et al. | Nov 1996 | A |
5618744 | Suzuki et al. | Apr 1997 | A |
5633479 | Hirano | May 1997 | A |
5634093 | Ashida et al. | May 1997 | A |
5635736 | Funaki et al. | Jun 1997 | A |
5636125 | Rostoker et al. | Jun 1997 | A |
5637920 | Loo | Jun 1997 | A |
5650653 | Rostoker et al. | Jul 1997 | A |
5657242 | Sekiyama et al. | Aug 1997 | A |
5659484 | Bennett et al. | Aug 1997 | A |
5663891 | Bamji et al. | Sep 1997 | A |
5717600 | Ishizuka | Feb 1998 | A |
5723908 | Fuchida et al. | Mar 1998 | A |
5742086 | Rostoker et al. | Apr 1998 | A |
5757089 | Ishizuka | May 1998 | A |
5757656 | Hershberger et al. | May 1998 | A |
5777360 | Rostoker et al. | Jul 1998 | A |
5811863 | Rostoker et al. | Sep 1998 | A |
5822214 | Rostoker et al. | Oct 1998 | A |
5838583 | Varadarajan et al. | Nov 1998 | A |
5856927 | Greidinger et al. | Jan 1999 | A |
5859449 | Kobayashi et al. | Jan 1999 | A |
5877091 | Kawakami | Mar 1999 | A |
5880969 | Hama et al. | Mar 1999 | A |
5889329 | Rostoker et al. | Mar 1999 | A |
5889677 | Yasuda et al. | Mar 1999 | A |
5898597 | Scepanovic et al. | Apr 1999 | A |
5914887 | Scepanovic et al. | Jun 1999 | A |
5973376 | Rostoker et al. | Oct 1999 | A |
5978572 | Toyonaga et al. | Nov 1999 | A |
5980093 | Jones et al. | Nov 1999 | A |
6006024 | Guruswamy et al. | Dec 1999 | A |
6035108 | Kikuchi | Mar 2000 | A |
6038383 | Young et al. | Mar 2000 | A |
6058254 | Scepanovic et al. | May 2000 | A |
6067409 | Scepanovic et al. | May 2000 | A |
6068662 | Scepanovic et al. | May 2000 | A |
6088519 | Koford | Jul 2000 | A |
6110222 | Minami et al. | Aug 2000 | A |
6111756 | Moresco | Aug 2000 | A |
6123736 | Pavisic et al. | Sep 2000 | A |
6128767 | Chapman | Oct 2000 | A |
6154873 | Takahashi | Nov 2000 | A |
6154874 | Scepanovic et al. | Nov 2000 | A |
6155725 | Scepanovic et al. | Dec 2000 | A |
6166441 | Geryk | Dec 2000 | A |
6175950 | Scepanovic et al. | Jan 2001 | B1 |
6209123 | Maziasz et al. | Mar 2001 | B1 |
6216252 | Dangelo et al. | Apr 2001 | B1 |
6219823 | Hama et al. | Apr 2001 | B1 |
6219832 | Buzbee | Apr 2001 | B1 |
6226560 | Hama et al. | May 2001 | B1 |
6230306 | Raspopovic et al. | May 2001 | B1 |
6247167 | Raspopovic et al. | Jun 2001 | B1 |
6247853 | Papadopoulou et al. | Jun 2001 | B1 |
6253363 | Gasanov et al. | Jun 2001 | B1 |
6260179 | Ohsawa et al. | Jul 2001 | B1 |
6262487 | Igarashi et al. | Jul 2001 | B1 |
6286128 | Pileggi et al. | Sep 2001 | B1 |
6289490 | Boyd et al. | Sep 2001 | B1 |
6289495 | Raspopovic et al. | Sep 2001 | B1 |
6292929 | Scepanovic et al. | Sep 2001 | B2 |
6295634 | Matsumoto | Sep 2001 | B1 |
6301686 | Kikuchi et al. | Oct 2001 | B1 |
6324674 | Andreev et al. | Nov 2001 | B2 |
6324675 | Dutta et al. | Nov 2001 | B1 |
6327693 | Cheng et al. | Dec 2001 | B1 |
6327694 | Kanazawa | Dec 2001 | B1 |
6330707 | Shinomiya et al. | Dec 2001 | B1 |
6349403 | Dutta et al. | Feb 2002 | B1 |
6363319 | Hsu | Mar 2002 | B1 |
6378121 | Hiraga | Apr 2002 | B2 |
6385758 | Kikuchi et al. | May 2002 | B1 |
6401234 | Alpert et al. | Jun 2002 | B1 |
6405358 | Nuber | Jun 2002 | B1 |
6407434 | Rostoker et al. | Jun 2002 | B1 |
6412097 | Kikuchi et al. | Jun 2002 | B1 |
6412102 | Andreev et al. | Jun 2002 | B1 |
6415427 | Nitta et al. | Jul 2002 | B2 |
6434730 | Ito et al. | Aug 2002 | B1 |
6436804 | Igarashi et al. | Aug 2002 | B2 |
6442745 | Arunachalam et al. | Aug 2002 | B1 |
6449761 | Greidinger et al. | Sep 2002 | B1 |
6463575 | Takahashi | Oct 2002 | B1 |
6473891 | Shively | Oct 2002 | B1 |
6490713 | Matsumoto | Dec 2002 | B2 |
6505331 | Bracha et al. | Jan 2003 | B1 |
6519751 | Sriram et al. | Feb 2003 | B2 |
6526555 | Teig et al. | Feb 2003 | B1 |
6543043 | Wang et al. | Apr 2003 | B1 |
6546540 | Igarashi et al. | Apr 2003 | B1 |
6557145 | Boyle et al. | Apr 2003 | B2 |
6567967 | Greidinger et al. | May 2003 | B2 |
6586281 | Gabara et al. | Jul 2003 | B1 |
6601227 | Trimberger | Jul 2003 | B1 |
6609237 | Hamawaki et al. | Aug 2003 | B1 |
6645842 | Igarashi et al. | Nov 2003 | B2 |
6656644 | Hasegawa et al. | Dec 2003 | B2 |
6665852 | Xing et al. | Dec 2003 | B2 |
6779169 | Singh et al. | Aug 2004 | B1 |
6898774 | Alpert et al. | May 2005 | B2 |
20010003843 | Scepanovic et al. | Jun 2001 | A1 |
20010038612 | Vaughn et al. | Nov 2001 | A1 |
20020043988 | Or-Bach et al. | Apr 2002 | A1 |
20020100009 | Xing et al. | Jul 2002 | A1 |
20020104061 | Xing et al. | Aug 2002 | A1 |
20020107711 | Xing et al. | Aug 2002 | A1 |
20020174413 | Tanaka | Nov 2002 | A1 |
20020182844 | Igarashi et al. | Dec 2002 | A1 |
20030004672 | Thurman | Jan 2003 | A1 |
20030005399 | Igarashi et al. | Jan 2003 | A1 |
20030009737 | Jan 2003 | A1 | |
20030014725 | Sato et al. | Jan 2003 | A1 |
20030025205 | Shively | Feb 2003 | A1 |
20030028852 | Thurman et al. | Feb 2003 | A1 |
20030121017 | Andreev et al. | Jun 2003 | A1 |
20030188281 | Oct 2003 | A1 | |
20030217338 | Holmes et al. | Nov 2003 | A1 |
20040015805 | Kidd et al. | Jan 2004 | A1 |
20040040007 | Harn et al. | Feb 2004 | A1 |
20040044979 | Aji et al. | Mar 2004 | A1 |
20040088670 | Stevens et al. | May 2004 | A1 |
Number | Date | Country |
---|---|---|
64-15947 | Jan 1989 | JP |
02-262354 | Oct 1990 | JP |
03-173471 | Jul 1991 | JP |
04-000677 | Jan 1992 | JP |
05-102305 | Apr 1993 | JP |
05-243379 | Sep 1993 | JP |
07-086407 | Mar 1995 | JP |
09-162279 | Jun 1997 | JP |
11-296560 | Oct 1999 | JP |
2000-082743 | Mar 2000 | JP |
Number | Date | Country | |
---|---|---|---|
20040098678 A1 | May 2004 | US |
Number | Date | Country | |
---|---|---|---|
60427131 | Nov 2002 | US |