UPC_CFI_414/2024

METHODS AND SYSTEMS FOR EFFICIENT NETWORK PROTECTION

VerletzungHauptverletzungsklageMannheim LDInfringementCase Closed

Übersicht Entscheidungen Begründung Zitate Dokumente Zeitverlauf

Zusammenfassung in einfacher Sprache

Centripetal Limited sued Keysight Technologies at the Mannheim Local Division for direct infringement of claim 16 and indirect infringement of claim 1 of EP 3 821 580 B1 (network security threat-metadata routing system) in Germany, Italy, France and the Netherlands. The action was dismissed because, after defendants clearly denied at oral hearing that their products (AppStack, SecureStack-SSL, Threat Simulator) contained the claim-required threat-metadata-based CAS routing functionality, Centripetal failed to provide sufficient evidence to the contrary under R. 171 RoP. A post-hearing application to reopen proceedings for source code review was also dismissed.

Angenommene Argumente

Was das Gericht akzeptiert hat — nach Partei.

Defendants' products do not incorporate the claim requirement of routing packets to a CAS (Cyber Analysis System) based on threat metadata
BeklagterRechtsgrundlage: R. 171 RoP
Hinweis: Defendants denied in precise terms at oral hearing that any functionality for threat-metadata-based CAS routing exists in the source code; Centripetal provided no adequate substantiation or proof in response.
Conditional counterclaim for revocation is procedurally permissible under UPC Rules of Procedure
BeklagterRechtsgrundlage: R. 263 RoP; R. 265 RoP; R. 30.1.c, 118.2.a RoP
Hinweis: Court confirmed that a conditional counterclaim dependent on an infringement finding is procedurally allowable; since infringement was not found, the counterclaim was not decided.
R. 114 RoP does not permit reopening of oral hearing to introduce new infringement allegations after closure
BeklagterRechtsgrundlage: R. 114 RoP; R. 245 RoP; Art. 81 UPCA
Hinweis: Court held R. 114 is reserved for situations identified during the hearing itself requiring additional testimony or experimental evidence; it is not available to introduce new infringement reads post-hearing.

Zurückgewiesene Argumente

Was das Gericht nicht akzeptiert hat — und warum.

Defendants' AppStack, SecureStack-SSL and Threat Simulator products directly infringe claim 16 and indirectly infringe claim 1
KlägerRechtsgrundlage: R. 171 RoP
Begründung: Centripetal failed to substantiate with sufficient evidence or proof (R. 171 RoP) that the products contain the claim-required functionality for threat-metadata-based CAS routing after defendants clearly denied it at oral hearing.
Oral hearing should be reopened to allow expert review of defendants' source code, and defendants should produce source code
KlägerRechtsgrundlage: R. 114 RoP
Begründung: Centripetal could have pursued source code access during the written procedure; defendants had contested the infringement read since their SoD; reaching out to a US proceedings expert only after oral hearing closure was too late; R. 114 is not a tool for post-hearing supplementation.

Zentrale Rechtsgrundsätze

In der Begründung herangezogene Doktrinen und Regeln.

Indirect infringement of claim 1 and direct infringement of claim 16 assessed separately Claimant bears burden to substantiate and prove factual infringement allegations, particularly when defendants deny them precisely at oral hearing (R. 171 RoP)R. 114 RoP for post-hearing evidence is available only for issues identified during the hearing as requiring specific additional investigation; it is not a tool for new infringement allegations Conditional counterclaim for revocation is procedurally admissible where the condition is an internal procedural outcome (infringement finding)Front-loaded written procedure requires all infringement contentions to be raised during the written phase R. 245 and Art. 81 UPCA: rehearing is an extraordinary remedy, not a supplement to the merits

Weitere Fälle zu diesem Grundsatz ansehen.

Hinweise zur Anspruchsauslegung

The court construed claim 16 and claim 1 of EP 3 821 580 B1 (network protection method) as requiring a gateway generating threat metadata and routing packets to a CAS (Cyber Analysis System) based on the specific threat metadata associated with each packet. This 'threat-metadata-based CAS routing' feature was the determinative element; defendants denied its presence in any of their products.