Results for "Fair use limitations"
Subscribe to Results for "Fair use limitations"'s Posts

Logic to Modify: Even Deceptive Intent Does Not Bar Inventorship Correction

The US Court of Appeals for the Federal Circuit vacated a district court invalidity determination finding that judicial estoppel prevented a patent owner from relisting an inventor previously removed for strategic litigation purposes. Egenera, Inc. v. Cisco Sys., Inc., Case Nos. 19-2015, -2387 (Fed. Cir. Aug. 28, 2020) (Prost, C.J.).

Egenera sued Cisco for infringement of a patent directed to a reconfigurable virtual network that included a “logic to modify” and transmit received messages. In response Cisco petitioned for inter partes review (IPR). During the IPR’s pendency, Egenera realized that all claim limitations were conceived of before inventor Schulter began working at the company, and petitioned the US Patent and Trademark Office (PTO) to remove Schulter as a listed inventor. The Patent and Trial Appeal Board (PTAB) declined to institute Cisco’s IPR, and the PTO granted Egenera’s petition to remove Schulter shortly thereafter.

During the litigation, the district court construed the patent claims’ “logic” terms as means-plus-function elements and concluded that the “logic to modify” limitation corresponded to a “tripartite structure” described in the specification. Cisco then asserted invalidity under pre-America Invents Act (AIA) § 102(f), contending that Schulter invented the tripartite structure, and that the patent therefore did not list all inventors. Egenera attempted to re-correct inventorship to include Schulter, but the court rejected the attempt. The district court found the patent invalid under § 102(f), reasoning that judicial estoppel precluded Egenera from “resurrecting” Schulter’s inventorship. Egenera appealed both the means-plus-function construction and the judicial estoppel finding.

The Federal Circuit first addressed whether Egenera could correct inventorship absent any judicial estoppel. The Court looked to the plain meaning of post-AIA § 256, which provides that “the error of omitting inventors . . . shall not invalidate the patent . . . if it can be corrected.” Notably, post-AIA § 256 removed the requirement that an inventorship error occur “without . . . deceptive intent.” The Federal Circuit stated it plainly: “‘Error’ is simply the incorrect listing of inventors” and does not exclude even deceptive intention. The Court explained that the inequitable conduct rules provide a safety valve for such actions, not § 256. The Court also noted that at the time Egenera removed Schulter as an inventor, no one had argued that “logic to modify” was means-plus-function language, which it presumptively was not. Egenera’s preferred construction of that term was consistent with its assertion that Schulter was not an inventor. The omission of Schulter as inventor was thus an “error” within the scope of § 256.

The Federal Circuit next turned to whether Egenera was judicially estopped from relisting Schulter as an inventor. Applying the First Circuit’s New Hampshire factors, the Federal Circuit looked to whether Egenera’s positions were inconsistent, whether its first position was successfully accepted by the court, and whether Egenera would derive an unfair advantage if not estopped. The Federal Circuit found that the district court erred in finding Egenera’s changing inventorship positions inconsistent. The Court explained that inventorship is complex and can depend on claim [...]

Continue Reading




read more

Liability for Copyright Infringement Attaches if Conduct Exceeds Scope of License

The US Court of Appeals for the Ninth Circuit revived a software owner’s copyright infringement suit because the district court erred in granting summary judgment of no infringement by failing to analyze whether the accused infringer exceeded the scope of a copyright license. Oracle America, Inc., et al. v. Hewlett Packard Enterprise Company, Case No. 19-15506 (9th Cir. Aug. 20, 2020) (Smith, J.).

Oracle owns registered copyrights for Solaris software, including copyrighted software patches. Oracle requires its customers have a prepaid annual support contract, for each server they desire to be under support, to access the software patches. Customers under a support plan can access patches through an Oracle support website.

Hewlett Packard Enterprise (HPE) provides a “one-stop-shop” for support to its customers, including HPE servers running Solaris. HPE provides this support directly and through its partners. One of HPE’s partners is Terix Computer Company. Terix arranged for joint HPE-Terix customers to have Oracle support for all of their servers through a single server support plan. Terix accomplished this by downloading Solaris software patches, using the customer’s credentials (created using a Terix-supplied credit card), to make copies for servers that were not part of the support contract.

In 2013, Oracle sued Terix for copyright infringement. The court granted Oracle summary judgment, and Terix stipulated to a judgment on the claims without admitting liability. Oracle and HPE entered into an agreement, effective May 6, 2015, to toll the statute of limitations for any claims Oracle might assert against HPE.

In 2016, Oracle sued HPE for direct copyright infringement concerning HPE’s direct support customers, and for indirect infringement concerning joint HPE-Terix customers. Oracle also sued for claims of intentional interference and unfair competition under California state law. The parties did not dispute that the tolling agreement applied, so the court considered whether the copyright infringement claims were barred for conduct before May 6, 2012. The Copyright Act provides that a copyright infringement claim is subject to a three-year statute of limitations, which runs separately for each violation. Under Ninth Circuit law, a copyright infringement claim begins to accrue “when a when a party discovers, or reasonably should have discovered, the alleged infringement.” Importantly, actual or constructive knowledge triggers the statute of limitations. The Ninth Circuit has explained that suspicion of copyright infringement places a duty on the copyright holder to investigate further into possible infringement or lose the claim.

Oracle conceded that it had concerns about Terix and suspicions about HPE as early as 2010, but argued that HPE used fraudulent means to keep Oracle unaware of its actions, so it had no duty to inquire. The district court disagreed, finding that once Oracle had constructive knowledge, the doctrine of fraudulent concealment was no longer an option to toll the limitations. Because Oracle failed to investigate HPE, the court determined that HPE was entitled to summary judgment on the infringement claims for pre-May 6, 2012, conduct. Oracle appealed.

The Ninth Circuit explained that to prove indirect infringement, Oracle had to show that [...]

Continue Reading




read more

Bad Faith Required to Prevent Speech Regarding Potential Patent Infringement

The US Court of Appeals for the Federal Circuit found that a district court abused its discretion in granting a preliminary injunction enjoining a patent holder from making claims of patent infringement without finding that those infringement claims were made in bad faith. The Federal Circuit reversed, vacated and remanded the district court’s decision. Myco Indus., Inc. v. BlephEx, LLC, Case No. 2019-2374 (Fed. Cir. Apr. 3, 2020) (O’Malley, J.).

(more…)




read more

BLOG EDITORS

STAY CONNECTED

TOPICS

ARCHIVES