Home » UPC decisions » Local Division » Duesseldorf Local Division » LD Düsseldorf, January 15, 2026, Decision, UPC_CFI_100/2024; UPC_CFI_411/2024

LD Düsseldorf, January 15, 2026, Decision, UPC_CFI_100/2024; UPC_CFI_411/2024

4 min Reading time

Key takeaways

  • The law ensures a party seeking revocation does not bear the burden of investigating true entitlement but can rely on the national patent register.
  • Entitlement disputes generally do not shift this, preserving legal certainty for the claimant. Substitution is available (RoP 42.2, 61.2).

The infringement action failed because the accused products (phones/tablets) did not contain the claimed controller, which was located on separate accessory devices not targeted by the direct infringement claim.

A claimant cannot introduce a new cause of action with different legal requirements (e.g., subjective knowledge for indirect infringement) late in the proceedings after the defendant has already responded, consistent with active case management obligations.

Added matter, novelty and obviousness attacks failed; the asserted prior art did not disclose the update relationship (LPD1′ based on LPD1, LPD2, PAOS) or the PAOS‑based timing adjustment.

The claimant, though successful in defending the revocation counterclaim, had to bear 20% of the costs due to its confusing initial submissions regarding its proprietorship of the patent.

Division

LD Düsseldorf

UPC number

UPC_CFI_100/2024; UPC_CFI_411/2024

Type of proceedings

Infringement action, counterclaim for revocation

Parties

Claimant / Counterdefendant 1: Ona Patents SL
Counterdefendant 2: Ekahau Oy
Defendants / Counterclaimants: Google Ireland Limited and Google Commerce Limited

Patent(s)

EP 2 263 098 B1

Jurisdictions

UPC

Body of legislation / Rules

Art. 25 UPCA
Art. 26 UPCA
Art. 31 UPCA
Art. 32 UPCA
Art. 33 UPCA
Art. 69 UPCA
R. 8.6 RoP
R. 25.1 RoP
R. 36 RoP
R. 42.1 RoP
R. 152.2 RoP
R. 263 RoP


Was the article helpful?


Categories


Tags

Stay in the loop

Never miss a beat by subscribing to the email newsletter. Please see our Privacy Policy.

* = Required field