Eolas Technologies Inc. v. Microsoft Corp.

457 F.3d 1279, 79 U.S.P.Q. 2d (BNA) 1597, 2006 U.S. App. LEXIS 19153, 2006 WL 2106748
Court of Appeals for the Federal Circuit·Decided July 31, 2006·No. 2006-1238·Published·Cited by 7 cases

Opinion

RADER, Circuit Judge.

On remand from an earlier decision of this court, Eolas Techs. Inc. v. Microsoft Corp., 399 F.3d 1325 (Fed.Cir.2005) (Eolas I), the United States District Court for the Northern District of Illinois denied Microsoft Corporation’s (Microsoft’s) motion seeking to have the case reassigned to a different judge. Eolas Techs. Inc. v. Microsoft Corp., No. 99 C 0626 (N.D.Ill. Oct. 26, 2005) (opinion and order denying motion to reassign) (Denial Order). Microsoft petitioned this court for permission to appeal the district court’s denial. This court granted that petition. Eolas Techs. Inc. v. Microsoft Corp., 163 Fed.Appx. 899 (Fed.Cir.2006). Because this court defers to the law of the regional circuit on the issue of reassignment and Seventh Circuit Rule 36 requires reassignment, this court *1281 reverses the district court’s denial of Microsoft’s motion to reassign the case.

I.

In 1999, Eolas Technologies Incorporated and The Regents of the University of California (collectively, Eolas) sued Microsoft, alleging that Microsoft’s Internet Explorer infringed claims of U.S. Patent No. 5,838,906 (the ’906 patent). After the district court construed the claims, a jury found that Microsoft infringed claims 1 and 6 of the ’906 patent and actively induced others to infringe claim 1 of that patent. Eolas I, 399 F.3d at 1328. Invoking 35 U.S.C. § 271(f), the district court determined that the royalty awarded to Eolas should reflect the foreign sales of Internet Explorer. Id. The district court further ruled in Eolas’ favor on Microsoft’s defenses, granting judgment as a matter of law (JMOL) against Microsoft’s invalidity defenses of anticipation and obviousness, and against its inequitable conduct defense. Id. On appeal, this court affirmed the district court’s claim construction and its damages analysis with respect to section 271(f). Id. at 1341.

At the same time, this court found that the district court erred in rejecting Microsoft’s defenses. Therefore, this court vacated the JMOL and remanded for further proceedings, including the resolution of genuine factual disputes. Id. at 1335. On Microsoft’s inequitable conduct defense, this court vacated the district court’s decision because it incorrectly excluded from its analysis a software product, which was potentially prior art. Id. Thus, this court remanded for the district court to assess inequitable conduct in light of that software product, and to, if necessary, “reconsider its findings” regarding intent to deceive the United States Patent & Trademark Office. Id. at 1336. This court’s decision in Eolas I did not mention reassignment to a different judge on remand.

After the case returned to the district court, Microsoft sought reassignment to a different judge. Microsoft did not assert any bias or misconduct on the part of the original judge, but instead urged that reassignment should occur automatically by operation of Local Rule 40.5, entitled “Remands, Procedures for Following Appeals.” That rule, applicable in the Northern District of Illinois, states:

(a) General. This rule shall not apply to remands resulting from appeals of summary judgments or interlocutory orders unless the mandate or order remanding the case indicates that it is to be reassigned to a judge other than the judge to whom the case was previously assigned (“prior judge”). Whenever a mandate from the Court of Appeals for the Federal Circuit or the Seventh Circuit is filed with the clerk indicating that the case appealed is remanded for a new trial, the case shall be assigned to the Executive Committee, except
(1) if the mandate or accompanying opinion indicates that the case is to be retried by the prior judge, then the case shall remain on that judge’s calendar ...
(c) Reassignment. When a stipulation is filed indicating that the parties wish the case assigned to the prior judge, the Executive Committee shall reassign the case to that judge. When no such stipulation is filed, the Executive Committee shall direct that the case be reassigned to a judge other than the prior judge. A case reassigned pursuant to this rule shall be treated for assignment purposes as a new case. The judge receiving the case is not authorized to transfer a similar case to the Executive Committee for reassignment to the prior judge.

*1282 N.D. Ill. Local Rule 40.5 (LR 40.5). In the Denial Order, the district court explained that LR 40.5 “has become a mostly dormant section” of the Local Rules. Denial Order at 2-3. According to the district court, that dormancy is a result of Circuit Rule 36 of The United States Court of Appeals for the Seventh Circuit. That rule provides:

Whenever a case tried in a district court is remanded by this court for a new trial, it shall be reassigned by the district court for trial before a judge other than the judge who heard the prior trial unless the remand order directs or all parties request that the same judge retry the case. In appeals which are not subject to this rule by its terms, this court may nevertheless direct in its opinion or order that this rule shall apply on remand.

7th Cir. R. 36. Thus, in the case of a remand from the Seventh Circuit, Circuit Rule 36 makes reassignment the default rule — hence the “dormant” status of LR 40.5. The district court explained that application of LR 40.5 to cases on remand from the Federal Circuit was “problematic” because the local rule does not mirror a Federal Circuit rule like Circuit Rule 36. Denial Order at 3. The district court further concluded that “the policy of the Federal Circuit is not at all like that of the Seventh Circuit.” Id. Thus, the district court concluded that application of Circuit Rule 36 would be inconsistent with “Federal Circuit policy.” Finally, the district court reasoned that even if LR 40.5 were applied, reassignment would not be required because Eolas I indicated that the case should remain with the same judge. According to the district court, when this court directed that “the district court may reconsider its findings” on remand, Eolas I, 399 F.3d at 1336, it signaled an intent to send the case back to the same judge because only the same judge could “reconsider its findings.” Denial Order at 5. Microsoft appeals, arguing that the Seventh Circuit’s Rule 36 should operate to reassign this case.

II.

Free access — add to your briefcase to read the full text and ask questions with AI

Eolas Technologies Inc. v. Microsoft Corp., 457 F.3d 1279, 79 U.S.P.Q. 2d (BNA) 1597, 2006 U.S. App. LEXIS 19153, 2006 WL 2106748 (Fed. Cir. 2006).

457 F.3d 1279 (Eolas Technologies Inc. v. Microsoft Corp.) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Ferguson v. Federal Aviation Administration
530 F. App'x 652 (Ninth Circuit, 2013)
Cohesive Technologies, Inc. v. Waters Corp.
543 F.3d 1351 (Federal Circuit, 2008)
Research Corp. Technologies, Inc. v. Microsoft Corp.
536 F.3d 1247 (Federal Circuit, 2008)