MEMORANDUM AND ORDER GRANTING MOTION FOR SUMMARY JUDGMENT

Plaintiff Business Objects, S.A. (“Business Objects”) and defendant Microstrate-gy, Inc. (“Microstrategy”) produce software products which allow users to query a relational database without learning the complex syntax of the query language. Business Objects brought this patent action against Microstrategy alleging that defendant’s products infringe U.S. Patent No. 5,555,403 (“the ’403 patent”) literally and under the doctrine of equivalents. Now before the Court is defendant’s post-remand motion for summary judgment that the accused products do not infringe claim 4 of the ’403 patent under the doctrine of equivalents. After carefully considering the papers submitted by the parties and having had the benefit of oral argument, the Court hereby GRANTS the motion for summary judgment.

BACKGROUND

The subject matter of the ’403 patent and the structure of the accused products have been explained in detail in this Court’s prior order and by the Federal Circuit and will not be repeated here. See Business Objects, S.A., v. Microstrategy, Inc., 393 F.3d 1366, 1367-71 (Fed.Cir.2005).

This Court previously granted defendant’s motion for summary judgment that the accused products do not infringe claims 1, 2 or 4 of the ’403 patent literally or under the doctrine of equivalents. On appeal, the Federal Circuit affirmed each of these holdings except this Court’s determination that the accused products do not infringe claim 4 under the doctrine of equivalents. With respect to that claim, the Federal Circuit reversed and remanded, finding that this Court erred in determining that an amendment during prosecution to the term “predefined query language” estopped plaintiff from claiming equivalents of the function of the query engine means of claim 4. See Business Objects, 393 F.3d at 1375-76 . Defendant now moves for summary judgment with respect to the remaining claim, arguing first that the Federal Circuit’s holdings resolve the remaining issue of equivalence and second, that in any event no reasonable trier of fact could find equivalence.

I. Summary Judgment Standard

Summary judgment is appropriate when the “pleadings, depositions, answers to interrogatories, and admissions on file, together with the affidavits, if any, show that there is no genuine issue as to any material fact and that the moving party is entitled to judgment as a matter of law.” Fed.R.Civ.P. 56(c). An issue is “genuine” only if there is sufficient evidence for a reasonable fact finder to find for the non-moving party. See Anderson v. Liberty Lobby, Inc., 477 U.S. 242, 248-49 , 106 S.Ct. 2505 , 91 L.Ed.2d 202 (1986). A fact is “material” if the fact may affect the outcome of the case. See id. at 248 , 106 S.Ct. 2505 . “In considering a motion for summary judgment, the court may not weigh the evidence or make credibility determinations, and is required to draw all inferences in a light most favorable to the non-moving party.” Freeman v. Arpaio, 125 F.3d 732, 735 (9th Cir.1997). A principal purpose of the summary judgment procedure is to identify and dispose of factually unsupported claims. See Celotex Corp. v. Catrett, 477 U.S. 317, 323-24 , 106 S.Ct. 2548 , 91 L.Ed.2d 265 (1986).

The party moving for summary judgment bears the initial burden of identifying those portions of the pleadings, discovery, and affidavits which demonstrate the absence of a genuine issue of material fact. See id. at 323 , 106 S.Ct. 2548 . Where the moving party will have the burden of proof on an issue at trial, it must affirmatively demonstrate that no reasonable trier of fact could find other than for the moving party. See id. Once the moving party meets this initial burden, the non-moving party must go beyond the pleadings and by its own evidence “set forth specific facts showing that there is a genuine issue for trial.” Fed.R.Civ.P. 56(e). The non-moving party must “identify with reasonable particularity the evidence that precludes summary judgment.” Keenan v. Allan, 91 F.3d 1275, 1279 (9th Cir.1996) (quoting Richards v. Combined Ins. Co., 55 F.3d 247, 251 (7th Cir.1995), and noting that it is not a district court’s task to “scour the record in search of a genuine issue of triable fact”). If the non-moving party fails to make this showing, the moving party is entitled to judgment as a matter of law. See Celotex, 477 U.S. at 323 , 106 S.Ct. 2548 .

II. Infringement Under the Doctrine of Equivalents

A. The Doctrine of Equivalents Standard

Under the doctrine of equivalents, a product that does not literally infringe a patent claim may still infringe if each and every limitation of the claim is literally or equivalently present in the accused device. See Warner-Jenkinson Co. v. Hilton Davis Chem. Co., 520 U.S. 17, 40 , 117 S.Ct. 1040 , 137 L.Ed.2d 146 (1997) (“In our view, the particular linguistic framework used is less important than whether the test is probative of the essential inquiry: Does the accused product or process contain elements identical or equivalent to each claimed element of the patented invention?”).

Whether an element of an accused product (or the product itself in its entirety) infringes under the doctrine of equivalents depends in part on whether that component (and the device overall) performs substantially the same function as the claimed limitation in substantially the same way to achieve substantially the same result. See Ethicon Endo-Surgery, Inc. v. United States Surgical Corp., 149 F.3d 1309, 1315 (Fed.Cir.1998); Pennwalt Corp. v. Durand-Wayland, Inc., 833 F.2d 931, 934-35 (Fed.Cir.1987) (en banc) (“Under the doctrine of equivalents, infringement may be found (but not necessarily) if an accused device performs substantially the same overall function or work, in substantially the same way, to obtain substantially the same overall result as the claimed invention.”)- If the differences between a claim and an accused device are “insubstantial” to one with ordinary skill in the art, the product may infringe under the doctrine of equivalents. See Ethicon, 149 F.3d at 1315 ; Sage Prods., Inc. v. Devon Indus., Inc., 126 F.3d 1420, 1423 (Fed.Cir.1997). The doctrine prevents an accused infringer from avoiding infringement by changing minor details of a claimed invention while retaining its essential functionality. See id. at 1424 . “Although equivalence is a factual matter normally reserved for a fact finder, the trial court should grant summary judgment in any case where no reasonable fact finder could find equivalence.” See Sage, 126 F.3d at 1424-26 (citation omitted).

B. The Impact of the Federal Circuit’s Opinion

Microstrategy argues that the Federal Circuit’s opinion conclusively establishes that the accused products do not infringe claim 4 under the doctrine of equivalents. This Court disagrees.

1. 35 U.S.C. § 112 (6)

Microstrategy first claims that the Federal Circuit’s ruling that the accused products do not infringe the patent under 35 U.S.C. section 112 paragraph 6 is dis-positive with respect to infringement under the doctrine of equivalents. The Federal Circuit has explained that the relationship between equivalents for the purposes of section 112(6) and the doctrine of equivalents is based on the function-way-result test. See Kemco Sales, Inc. v. Control Papers Co., Inc. 208 F.3d 1352, 1364 (Fed.Cir.2000). As described above, under that test the accused device infringes where the accused structure performs “substantially the same function, in substantially the same way to achieve substantially the same result, as the disclosed structure.” Id. In contrast, “[lateral infringement of a § 112 ¶ 6 [means-plus-function] claim requires that the relevant structure in the accused device perform the identical function recited in the claim and be identical or equivalent to the corresponding structure in the specification.” Lockheed Martin Corp. v. Space Systems/Loral, Inc., 324 F.3d 1308, 1320 (Fed.Cir.2003). Therefore, “[a] key feature that distinguishes ‘equivalents’ under section 112, paragraph 6 and ‘equivalents’ under the doctrine of equivalents is that section 112, paragraph 6 equivalents must perform the identical function of the disclosed structure ... while equivalents under the doctrine of equivalents need only perform a substantially similar function.” Kemco Sales, 208 F.3d at 1364 (citations omitted).

This Court previously ruled that there was no literal infringement of claim 4 because the “predetermined query language” of that claim requires the association of a SELECT clause with a familiar name during the associating step. See Business Objects, S.A. v. Microstrategy, Inc., 280 F.Supp.2d 1000, 1004 (N.D.Cal.2003). This Court based its ruling on the narrow basis that “the accused device does not include the identical function.” Id. (emphasis in original). The Federal Circuit affirmed. Business Objects, 393 F.3d at 1374 . That court did not discuss equivalents and therefore there is no basis to assume that the court’s ruling reached any further than did this Court’s. Therefore, the only finding that has been made is that the accused products do not practice the identical function to the invention of claim 4 under section 112(6) and plaintiff is not legally precluded from arguing that there is infringement under the doctrine of equivalents because the accused devices practice a substantially equivalent function and possess a substantially equivalent structure to the invention of claim 4. See Kemco Sales, 208 F.3d at 1364 .

2. Prosecution History Estoppel

Microstrategy also argues that the Federal Circuit’s finding of prosecution history estoppel with respect to claim l’s “associating step” limitation also applies to claim 4’s “predetermined query language.” The Federal Circuit affirmed that the terms “predefined query language” and “predetermined query language” in claims 1 and 4 have the same meaning and require the association of a SELECT clause to a familiar name during the associating step. See id. at 1373 . The parties also agree that the accused products do not associate a SELECT clause with a familiar name. Therefore, if plaintiff were estopped from claiming equivalents to this association by the narrowing amendment to claim l’s associating step, plaintiff would be precluded from claiming equivalents to claim 4. See Southwall Tech., Inc. v. Cardinal IG Co., 54 F.3d 1570, 1579 (Fed.Cir.1995) (“[Arguments made during prosecution regarding the meaning of a claim term are relevant to the interpretation of that term in every claim of the patent absent a clear indication to the contrary.”). However, plaintiff is only estopped from claiming equivalents to the association of a WHERE clause with a familiar name. See Business Objects, 393 F.3d at 1374 . Neither this Court nor the Federal Circuit has ruled that the estoppel flowing from the narrowing amendment creating the “associating step” limitation also encompasses the association of a SELECT clause with a familiar name. Therefore, prosecution history estoppel does not apply.

C. Substantial Differences Between Claim 4 and the Accused Products

Although the Court finds that the Federal Circuit’s ruling is not determinative with respect to plaintiffs present motion, even a cursory comparison of the accused devices to the “query engine means” of claim 4 reveals that no reasonable finder of fact could find equivalence. See Business Objects, 393 F.3d at 1368-71 (describing the differences in the structure of the claimed invention and the “much more sophisticated approach to generating queries” used by the accused products).

The patent discloses an eight-step process for converting the patent’s “business objects” — i.e. familiar names associated with SELECT and WHERE clauses — to SQL queries. See Business Objects, 393 F.3d at 1373 (affirming that the “query engine means” of claim 4 corresponds with the algorithm described at Col. 4:42-52; Col. 7:48-54; Col. 8:21-23; Col. 9:14-40; and Col. 9:52-Col. 13:2). There is no dispute that the accused products contain none of these steps. Nonetheless plaintiffs argue that analogues can be found in the accused products to each step such that the two query engines are unsubstan-tially different as a whole. This proves too much. The Court agrees with Business Objects that the query engine algorithms of the two systems must be compared as a whole and a single difference in one step of the algorithm is not necessarily sufficient to find the entire algorithm substantially different. See Odetics, Inc. v. Storage Tech. Corp., 185 F.3d 1259, 1268 (Fed.Cir.1999). However, when the two systems are evaluated as a whole, their nonequiva-lence becomes apparent. Indeed, the differences in the structures of the two systems are so numerous and substantial that reasoned comparison is nearly precluded.

1. Use of Different Metadata

The central difference between the system claimed in the ’403 patent and the accused products is that the ’403 system stores the data regarding the tables in the underlying database in strings of SELECT and WHERE clauses associated with familiar names while the accused products store this information in a multilevel hierarchy of data that models the underlying database. See Business Objects, 393 F.3d at 1368-71 . This difference is important because it means that both the function and the structure of the accused query engine algorithm is not identical to the algorithm of claim 4. The function is different because the ’403 query engine converts combinations of the patent’s business objects into the final query language, see id. 393 F.3d at 1373-74 (finding that the functions of the two systems are not identical because the query engine means requires the association of a SELECT clause with a familiar name during the associating step), while the accused devices convert combinations of objects coded in Microstrategy’s metadata into the final query. Obviously the structures of the two devices are also different because each algorithm is structured to process the particular metadata that it was created to convert. These differences mean that the two query engines are not interchangeable, which is itself an important gauge of the substantialness of the differences. See Multiform Desiccants, Inc. v. Medzam, Ltd., 133 F.3d 1473, 1480 (Fed.Cir.1998). The lack of interchangeability is undisputed.

That the query engine means of claim 4 is structured for the specific purpose of converting the metadata described by the patent into the final query is reflected at several places in the description of the structure of the algorithm. The query engine requires inputs such as a predefined list of joins, Col. 7: 48-41, 10:40-42, 11:25-29, 12:11-25, SELECT clauses associated with familiar names, Col. 10:12-15, Business Objects, 393 F.3d at 1373 , contexts, Col. 10:50-67, 11:25-28, and WHERE clause conditions associated with familiar names, Col. 11:31-32. See also Business Objects, 393 F.3d at 1368-71 (describing the differences in the structure of the ’403 patent’s metadata and Microstra-tegy’s metadata). However, Microstrate-gy’s metadata is not structured in this manner and therefore could not be translated into a SQL query by the ’403 patent algorithm. In order to convert Microstra-tegy’s metadata into a the final query, the accused products’ algorithm operates in a way that is entirely different from the claimed process. See id. at 1371 .

For example, because Microstrategy’s metadata is not tied to the specific tables and columns of the underlying database (as is the metadata of the ’403 patent) the specific tables that will be accessed in a particular query are not determined until the query generation step and are influenced by factors other than the familiar names selected by the user making the query. Id.; see also GTE Wireless v. Qualcomm, Inc., 188 F.Supp.2d 1201, 1214-15 (S.D.Cal.2002) (finding substantial differences in the structure of a patented phone algorithm which “blindly searchfed] the same ... frequencies every time” and an algorithm which searched different frequencies depending on other contextual information). In addition, unlike the system of the patent which always produces a single, unified query, Microstrategy’s metadata and query algorithm are structured to conduct multi-pass queries along different join trees. With respect to some portions of the final query, such as the generation of an ORDERBY clause, Mi-crostrategy’s query engine can only produce the final SQL syntax through these multi-pass queries.

The consequence of the greater complexity of Microstrategy’s metadata and query engine, see id. at 1370 (“the accused products use a much more sophisticated approach”), is greater and improved functionality than the system in the ’403 patent. An example of this improved functionality is the accused products’ ability to search multiple groups of tables in order to minimize the number of tables accessed. This creates faster and more efficient queries. A second example is that by using metadata independent of the form and syntax of the final query language, Microstrategy’s query engine has the ability to combine and organize data in a manner that is not allowed by the constraints of the final query language. Such increased functionality includes the ability to perform a standard deviation function and to more efficiently sort data contained in the query. See Reddy Dec. ¶ 31.

Business Objects argues that the asserted differences are not substantial as a matter of law because each of them only results in the accused products being able to perform functions in addition to common functions of the two systems. The fallacy of this argument is that it assumes that undisputed differences in structures are insubstantial if those differences result in the device performing additional functions, or the same function in a better and more useful manner. Business Objects has cited no authority that supports such a narrow definition of substantiality. Indeed, it is hard to imagine a substantial change in the structure of a device that would not have some effect on its functionality. The appropriate test for infringement under the doctrine of equivalents is that the accused products must have substantially the same function and substantially the same structure. See Conopco, Inc. v. May Dep’t Stores Co., 46 F.3d 1556 , 1562 (Fed.Cir.1994) (“The doctrine of equivalents cannot be used to erase’ ‘meaningful structural and functional limitations of the claim on which the public is entitled to rely in avoiding infringement.’ ” (internal citations omitted)); Network Appliance, Inc. v. Bluearc Corp., No. C 03-5665 MHP, 2005 WL 1530222 *9 (N.D.Cal. June 27, 2005) (“[Hjaving patented an invention that includes [clear] structural limitations, plaintiff cannot rely on the ‘functional interchangeability’ of substantially different structures in order to sweep any computer architecture that is functionally equivalent to that invention into the scope of the patent’s claims.”). This Court finds that the numerous differences in structure of the two query engines are substantial.

2. Joins

One example of the ways in which the difference in metadata makes a substantial difference in the structure of the two systems is their treatment of joins. The ’403 patent requires the manager to predefine a list of all the potential joins that might be used in a query. In contrast, the accused products do not utilize such a predefined list and instead automatically generate joins based on common column names.

In the ’403 system, the creation of the list of joins is required by a portion of the specification that this Court has identified as being associated with the query engine means. See Col. 7:48-54 (“the Manager defines the list of all the potential joins between the tables involved in a Universe.”); see also Business Objects 393 F.3d at 1373 (affirming that this portion of the patent is part of the query engine means). The specification itself states that “the list of Joins is an important part of the Universe definition.” Col. 7:55-56 (emphasis added). This is demonstrated by the fact that the list of joins is used by the patent’s query engine algorithm sever al times. See Col. 10:40-42; 11:25-29; 12:11-25. In fact, if a list of joins has not been specified, the query will be invalid. See Col. 10:44^5.

From a practical standpoint, the fact that the accused products do not require a list of joins is important because it saves the consumer the burden of having the Manager manually specify all possible joins in a particular database. For large databases that are common in commercial uses of these products, that bui'den would be onerous. The patent’s use of a list of joins, however, has some advantages over the accused devices’ system. While the accused system may save time because joins can be determined by careful labeling of columns when the underlying database is created (rather than through a separate step of creating a list of joins), it also may be more error prone since columns may be erroneously joined or not joined because of a failure to label them correctly. It also obviously requires that the underlying database be created in a manner that is compatible with the Microstrategy algorithm. The accused products therefore contain a distinct design that makes a difference in how the product may be used.

Business Objects’ expert does nothing to contradict the fact that the treatment of joins in the two systems is substantially different. He states only that in the accused products the definitions of the attributes in the schema “includes an implicit list of joins to represent possible join paths.” Rudd Dec. ¶ 89. Dr. Rudd does not identify any structure in the metadata that corresponds to a physical list of joins, even though such an actual list is a necessary component in the ’403 patent’s query engine algorithm. See Col. 10:40^2; 11:25-29; see also Rudd Depo, 349:9-11 (admitting that there is not “a single data structure that lists all of the pairs of tables in it”). Nor does Dr. Rudd explain how it can be an insubstantial difference for the accused devices to automatically generate join paths while the ’403 system requires the Manager to “define[ ] the list of all the potential joins between the tables involved in the Universe.” Col. 7:50-51.

Because the ’403 patent itself labels the list of joins to be “an important part of the Universe definition,” and because there is no dispute that the accused products eliminate the burden of creating such a list, it is a substantial difference.

CONCLUSION

For all of the foregoing reasons, defendant’s motion for summary judgment is GRANTED.

IT IS SO ORDERED.

. Business Objects has moved to strike the Declarations of Drs. Reddy and Keller. The motion is denied. The Court finds that the portions of the Reddy declaration that it has relied upon to be a summary of Dr. Reddy's observations of the software code at issue and that the declaration was based on admissible and reliable information. The Court has not relied on Dr. Keller's declaration and therefore need not rule on its admissibility. . Related to the fact that the accused products do not incorporate a list of joins, is that the accused products also do not utilize "contexts.” See Col. 4:50-51; 5:40, 7:59-66, 15:64-67. As defined in the ’403 patent, contexts resolve the problem that multiple join paths may be generated from a single query. In contrast, the accused products resolve this type of problem by choosing the first join path found by the program. See Rudd Decl. 353:5-25. This is an additional undisputed difference that supports the substantiality of the differences between the two systems.