Inventor Removed From Patent May Be Restored Due to Claim Construction

Knobbe Martens
Contact

Knobbe Martens

EGENERA, INC. v. CISCO SYSTEMS, INC.

Before Prost, Stoll, and Reyna. Appeal from the United States District Court for the District of Massachusetts.

Summary: A patentee that successfully petitioned to correct a patent’s inventorship by removing a named inventor was permitted to seek a second correction to restore the same inventor, based on an intervening claim construction that the patentee had opposed.

Egenera sued Cisco Systems for patent infringement. In response, Cisco petitioned for inter partes review (IPR) of Egenera’s patent. Seeking an earlier invention date for the patent so it could swear behind prior art in the IPR, Egenera successfully petitioned to remove one of the named inventors from the patent. The Patent Trial and Appeal Board declined to institute the IPR for reasons unrelated to the inventorship change.

After the inventor was removed, the district court construed the claim language “logic to modify” as a means-plus-function limitation, over Egenera’s opposition. The court found that the structure in the specification corresponding to this claim language was what the parties called the “tripartite structure.”

Following claim construction, Cisco argued that the removed inventor had invented the tripartite structure, and because he was no longer listed as an inventor, the patent was invalid for incorrect inventorship. Egenera responded that the patent’s inventorship should simply be corrected under 35 U.S.C. § 256 to restore the removed inventor. The district court found that Egenera was judicially estopped from restoring the removed inventor, and thus held the patent invalid. Egenera appealed, challenging the claim construction and the invalidity ruling.

Reviewing the claim construction, the Federal Circuit explained that claim terms lacking the word “means” are presumed not to be means-plus-function terms. However, this presumption is rebutted if a claim term recites “function without reciting sufficient structure for performing that function.” Egenera argued that the claim at issue recited structure in the form of “software, firmware, circuitry, or a combination thereof.” However, the Federal Circuit clarified that “the question is not whether a claim term recites any structure but whether it recites sufficient structure” for performing the recited function. In Egenera’s claim, the alleged structure was not sufficient to perform the functions attributed to the “logic to modify.” Thus, the Federal Circuit affirmed the district court’s means-plus-function construction.

Turning to invalidity, the Federal Circuit stated that judicial estoppel exists to prevent a litigant from taking a litigation position inconsistent with one successfully asserted in an earlier court proceeding. Egenera did not advance any “clearly inconsistent” positions because its petition to remove the inventor was consistent with the claim construction it was asserting at the time of the petition. Further, no other factors weighed in favor of judicial estoppel. Thus, the Court vacated the district court’s invalidity judgment and remanded for further proceedings.

Editor: Paul Stewart

DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Knobbe Martens | Attorney Advertising

Written by:

Knobbe Martens
Contact
more
less

Knobbe Martens on:

Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
- hide
- hide

This website uses cookies to improve user experience, track anonymous site usage, store authorization tokens and permit sharing on social media networks. By continuing to browse this website you accept the use of cookies. Click here to read more about how we use cookies.