Software Archives - IP UPDATE

Rimini, Meeny, Miny, Moe: Ninth Circuit Affirms Most PI Violation Findings, Reverses Others

Addressing the boundaries of a permanent injunction awarded to a major software developer, the US Court of Appeals for the Ninth Circuit largely agreed that the defending developer was in contempt for violating the order but reversed on certain issues where the district court overextended the injunction. Oracle USA, Inc. v. Rimini St., Inc., Case No. 22-15188 (9th Cir. Aug. 24, 2023) (Bybee, Bumatay, JJ.; Bennett, Dist. J., sitting by designation).

Oracle creates enterprise software to carry out business functions. Oracle’s customers buy licenses to its products, which require updates and technical support. These necessary support services can be outsourced to third-party vendors, such as Rimini.

This case is the byproduct of a 13-year battle that Oracle initiated on the grounds that Rimini’s support services constituted copyright infringement. Rimini made generic versions of Oracle software on Rimini computers to develop updates and bug fixes (local hosting) and supported clients by using development environments created pursuant to a different client’s license (cross-use). After multiple appeals and remands, the case resulted in a permanent injunction prohibiting Rimini from reproducing or cross-using Oracle software unless pursuant to a customer license. Rimini revamped its support services and sought a declaratory judgment of noninfringement. After Oracle was permitted to conduct discovery into potential violations of the injunction, the district court held a bench trial on 10 possible violations. The district court found Rimini in contempt for five of the 10 alleged violations (issues 1–4 and 8). On two others (issues 7 and 9), the district court found no contempt but enjoined Rimini from continuing a specific copying practice. The district court sanctioned Rimini $630,000, calculated according to statutory damages available under the Copyright Act.

Rimini appealed each contempt finding, the injunction and the sanctions.

First, the Ninth Circuit addressed the five contempt findings, sorted into three groups:

Local hosting (issue 1)
Cross-use (issues 2–4)
Database copying (issue 8).

On issue 1, the Ninth Circuit affirmed. The lower court had found that Rimini received copyrighted files from its clients. Instead of following internal policies requiring them to quarantine or report these files, Rimini employees forwarded and saved them locally. Based on the plain language of the PI, this was a clear violation.

On issues 2–4, regarding cross-use, the Ninth Circuit also affirmed. Rimini used one client’s environment to modify and test updates that the client did not need and were intended for other clients. Since the injunction specifically prohibited cross-use, this was a violation. Rimini lodged multiple failed arguments, including that the injunction only prohibited cross-use in “generic” (non-client) environments, so its use of one client’s environment to support another client was allowed. The Court disagreed that the injunction was so specific.

On issue 8 (database copying), however, the Ninth Circuit reversed. The district court held Rimini in contempt for making copies of an Oracle database file on Rimini systems. When the client uploaded the file to Salesforce for Rimini to provide technical assistance, a copy was automatically created on Rimini’s system. Here, the [...]

Continue Reading

Too Good to Be True? Federal Circuit Demands Evidence of Reliance on Favorable Ruling, Stipulation

The US Court of Appeals for the Federal Circuit held that notwithstanding a stipulation on claim construction, a party may still induce infringement absent proof that it actually relied on the stipulation, and that mere inaction, absent an affirmative act to encourage infringement, cannot be the basis for a claim of inducement. The Federal Circuit also affirmed the district court’s reduction of the jury’s damages award to $0 despite a finding of direct infringement because the plaintiff failed to prove damages. TecSec, Inc. v. Adobe Inc., Case Nos. 19-2192, -2258 (Fed. Cir. Oct. 23, 2020) (Taranto, J.).

TecSec owns several patents on systems and methods for multi-level security for network-distributed files. TecSec sued Adobe (among other defendants) in this now-10-year-old-case, which the Federal Circuit has considered several times. As relevant here, the district court entered a claim construction in 2011 that led to a stipulation of non-infringement, and the Federal Circuit reversed that claim construction in 2013. On remand, the district court barred TecSec from introducing evidence of inducement in the 2011–2013 period on the grounds that it was reasonable for Adobe to have relied on the district court’s ruling and the stipulation. On the new claim construction, Adobe stipulated to one act of direct infringement. Adobe also moved for summary judgment of patent ineligibility, which the district court denied, stating that its rationale supported judgment for TecSec that the patents claimed eligible subject matter. At trial, the jury found that the claims were valid and that Adobe directly infringed but did not induce infringement. The jury awarded TecSec $1.75 million in damages. On Adobe’s post-trial motion, the district court reduced the damages award to $0 because TecSec had not proved inducement and had proved no damages associated with the single act of direct infringement. Both parties appealed.

Inducement

The Federal Circuit reversed the district court’s decision on Adobe’s motion in limine barring inducement evidence for the 2011–2013 period. The district court’s primary rationale for granting the motion had been the reasonableness of Adobe’s reliance on the claim construction order and stipulation of non-infringement. However, the Federal Circuit reasoned that the intent prong of inducement is a subjective inquiry, and that inducement could still be found upon a showing that Adobe subjectively believed that the claim construction order was wrong and would subsequently be reversed.

Jury Instructions

The Federal Circuit next addressed two challenges by TecSec to jury instructions. The first instruction was predicated on three facts: (i) that Adobe had admitted that a certain sequence of steps constituted direct infringement, (ii) that Adobe had performed the steps on at least one occasion, and (iii) that “the parties agree that the one time for which Adobe had admitted infringement . . . occurred before TecSec filed its lawsuit.” The Court found that this instruction was factually accurate and therefore not erroneous. The second instruction explained that inducement required “an affirmative act to encourage infringement,” and that “[e]vidence of mere inaction, or a failure to stop or prevent infringement, does not [...]

Continue Reading