UPClytics
View all cases

UPC CFI 414/2024

Jul 22, 2024·EP3821580 +2 more: METHODS AND SYSTEMS FOR EFFICIENT NETWORK PROTECTION

Case details
Status
Case Closed
Action
Infringement
Category
Main Infringement Action
Parties
Claimants
Reps: Ralph Nack
Respondents
Reps: Klaus Haft
Division
Mannheim LD
Technology
Telecoms · Network Security · Telecommunications
Language
English
First decided
Dec 5, 2025
Claims
At issue1, 16
Not infringed1, 16
Notes: Infringement action dismissed for claims 16 (direct) and 1 (indirect) of EP 3 821 580; conditional counterclaim for revocation not decided as infringement not found.
Decisions
  • 2025-12-05
    Not infringedInfringement meritsInfringement Action

    Decision of the Mannheim Local Division dated 5 December 2025 dismissing Centripetal Limited's infringement action against Keysight Technologies entities for infringement of EP 3 821 580 (methods and systems for network protection). Centripetal alleged direct infringement of claim 16 and indirect infringement of claim 1 in Germany, Italy, France and the Netherlands. The panel found that the defendants' products (AppStack, SecureStack-SSL, Threat Simulator) did not read on the claims as construed: defendants denied in the oral hearing that the source code contained functionality for threat-metadata-based routing to a CAS (a claim requirement), and Centripetal failed to substantiate its contrary position with sufficient evidence or proof under R. 171 RoP. The conditional counterclaim for revocation was not decided as the condition (infringement finding) was not met. Centripetal was ordered to bear all costs of the infringement proceedings.

    Legal issues:Direct infringement of claim 16Indirect infringement of claim 1Claim construction for network protection methods (CAS, threat metadata, gateway)Burden of proof for infringement under R. 171 RoPConditional counterclaim for revocation
  • 2025-12-05
    Infringement Action

    Procedural order from the Mannheim Local Division dated 5 December 2025 rejecting Centripetal Limited's request to reopen the oral hearing and appoint an expert to review the source code of Keysight's products, filed on 24 November 2025 after the closure of the hearing. The court held that R. 114 RoP permits reopening only in exceptional cases identified during the oral hearing itself (e.g. for necessary additional testimony or experimental evidence emerging from the hearing) and is not available as a tool to introduce new infringement allegations after closure. Claimant's argument that defendants' counsel had made false statements about source code functionality was not sufficient to trigger R. 114 RoP. The request was rejected.

    Legal issues:Reopening of oral hearing under R. 114 RoPScope and conditions for reopeningNew evidence after closure of hearingAlleged false statements by counsel
Documents
Document titleDatePublic
Other Documents2026-03-02Not public
Other Documents2026-03-02Not public
Receipt2026-01-05Not public
Cover sheet2026-01-05Not public
Application document Respondent2026-01-05Not public
Application document Respondent2026-01-05Not public
Application document Respondent2026-01-05Not public
Exhibit document Respondent2026-01-05Not public
Exhibit document Respondent2026-01-05Not public
Exhibit document Respondent2026-01-05Not public
Exhibit document Respondent2026-01-05Not public
Exhibit document Respondent2026-01-05Not public
Other Documents2025-12-15Not public
Other Documents2025-12-15Not public
Other Documents2025-12-15Not public
action.phaseChange.caseClose2025-12-05Not public
action.issueDecision.decision2025-12-05Not public
Decision2025-12-05Public
action.issueOrder.order2025-12-05Not public
Order2025-12-05Public
action.communication.general2025-12-04Not public
Cover sheet2025-12-04Not public
Further pleadings2025-12-04Not public
Receipt2025-12-04Not public
Cover sheet2025-12-03Not public
Exhibit document Defendant2025-12-03Not public
Exhibit document Defendant2025-12-03Not public
Exhibit document Defendant2025-12-03Not public
Exhibit document Defendant2025-12-03Not public
Exhibit document Defendant2025-12-03Not public
Further pleadings2025-12-03Not public
Receipt2025-12-03Not public
Other Documents2025-12-01Not public
action.issueOrder.order2025-11-26Not public
Order2025-11-26Public
Cover sheet2025-11-25Not public
Application document Defendant2025-11-25Not public
Receipt2025-11-25Not public
Cover sheet2025-11-24Not public
Application document Claimant2025-11-24Not public
Exhibit document Claimant2025-11-24Not public
Receipt2025-11-24Not public
Other Documents2025-11-05Not public
Cover sheet2025-10-24Not public
Application2025-10-24Not public
Receipt2025-10-24Not public
action.phaseChange.interimPhaseClose2025-10-02Not public
Other Documents2025-10-02Not public
action.phaseChange.writtenPhaseClose2025-10-02Not public
Other Documents2025-10-02Not public
Outcome of the Order2025-09-12Not public
wf closed2025-09-12Public
wf closed2025-09-12Public
Outcome of the Order2025-09-12Not public
WF closed2025-09-12Public
Outcome of the Order2025-09-11Not public
WF closed2025-09-11Public
Outcome of the Order2025-09-05Not public
stay denied2025-09-05Public
Panel-Appointment2025-09-05Not public
Headnote-and-Keywords2025-08-20Not public
Outcome of the Order2025-08-20Not public
final order R 333 RoP2025-08-20Public
final order R 333 RoP2025-08-20Not public
Exhibit_CL_36_EPO_Examiner_Result_of_Consultation2025-08-19Not public
2025.08.19_Noerr_Statement_re_Stay_of_Proceedings2025-08-19Not public
Acknowledgement-of-lodging2025-08-14Not public
2025-08-14_Noerr_Panel Review Application_Further_Pleading2025-08-14Not public
Exhibit_CL_35_Payment_proof2025-08-14Not public
invitation to comment2025-08-12Not public
Receipt2025-08-12Not public
Exhibit HRM 232025-08-12Not public
Request to stay proceedings2025-08-12Not public
Headnote-and-Keywords2025-08-01Not public
Outcome of the Order2025-08-01Not public
R 36 dismissed2025-08-01Public
Exhibit HRM 21_ITC Testimony Scott Register2025-07-31Not public
Comments to R. 36 Request2025-07-31Not public
Exhibit HRM 22_Demonstrative2025-07-31Not public
332025-07-28Public
r 36 c2025-07-28Not public
Receipt2025-07-25Not public
Exhibit_CL_34_Defendants_Whitepaper_AI Stack - Network Visibility for AI_ML Applications2025-07-25Not public
Exhibit_CL_32_Excerpt from Defendants_website_AI Stack Software Suite2025-07-25Not public
Exhibit_CL_33_Defendants_solution brief_AI-Powered Network Visibility2025-07-25Not public
Exhibit_CL_30_Noerr_Reply_to_Defendants_Rejoinder2025-07-25Not public
Exhibit_CL_31_Excerpt from Defendants_website_Press release2025-07-25Not public
20250725_Noerr_Request_Further_Exchange_of_Written_Pleadings_41285_20242025-07-25Not public
Art 33 UPCA2025-07-10Public
no bif2025-07-10Public
Art 33 UPCA2025-07-10Not public
Acknowledgement-of-lodging2025-06-18Not public
Exhibit HRM 16d2025-06-18Not public
Exhibit HRM 16b2025-06-18Not public
Exhibit HRM 13a2025-06-18Not public
Exhibit HRM 162025-06-18Not public
Exhibit HRM 13d2025-06-18Not public
Rejoinder2025-06-18Not public
Exhibit HRM 202025-06-18Not public
Exhibit HRM 152025-06-18Not public
Exhibit HRM 13b2025-06-18Not public
Exhibit HRM 192025-06-18Not public
Exhibit HRM 16c2025-06-18Not public
Exhibit HRM 172025-06-18Not public
Exhibit HRM 142025-06-18Not public
Exhibit HRM 132025-06-18Not public
Exhibit HRM 13e2025-06-18Not public
Exhibit HRM 13c2025-06-18Not public
Exhibit HRM 16a2025-06-18Not public
Exhibit HRM 182025-06-18Not public
Exhibit HRM 20a2025-06-18Not public
Acknowledgement-of-lodging2025-06-18Not public
Rejoinder Reference Defendant 2)2025-06-18Not public
Outcome of the Order2025-06-06Not public
final order extension2025-06-06Public
Receipt2025-06-06Not public
250606_Request_Time_Period_Extension_R_9(3)_RoP_signed2025-06-06Not public
2025.06.03_Noerr_Statement_Oral_Hearing2025-06-03Not public
Statement re R. 28 RoP2025-06-03Not public
Statement re R. 28 RoP2025-06-03Not public
comment bif2025-05-26Not public
Hearing-Dates2025-05-26Not public
hearing date2025-05-26Public
Hearing-Dates2025-05-26Not public
Panel-Appointment2025-05-16Not public
Outcome of the Order2025-05-14Not public
R 2632025-05-14Public
Outcome of the Order2025-05-14Not public
R 263 request2025-05-14Public
Statement regarding leave to amend the claim2025-04-22Not public
Statement regarding leave to amend the case2025-04-22Not public
Noerr_Statement_R263_41285_2024_App_15688_20252025-04-22Not public
Noerr_Statement_R263_41285_2024_App_15688_20252025-04-22Not public
Noerr_Statement_R263_41285_2024_App_15688_20252025-04-22Not public
Noerr_Statement_R263_41285_2024_App_15688_20252025-04-22Not public
Noerr_Statement_R263_41285_2024_App_15688_20252025-04-22Not public
Noerr_Statement_R263_41285_2024_App_15688_20252025-04-22Not public
Noerr_Statement_R263_41285_2024_App_15688_20252025-04-22Not public
Noerr_Statement_R263_41285_2024_App_15688_20252025-04-22Not public
Noerr_Statement_R263_41285_2024_App_15688_20252025-04-22Not public
Receipt2025-04-22Not public
Exhibit HRM 10 - Opposition_Exhibits_EPO2025-04-17Not public
Notification of Opposition Proceedings2025-04-17Not public
Exhibit HRM 12 - EPO Time Limite Patentee2025-04-17Not public
Exhibit HRM 11 - Accelerated Opposition Proceedings2025-04-17Not public
Outcome of the Order2025-04-10Not public
Fristverlaengerung.Duplik2025-04-10Public
Klageaenderung2025-04-05Not public
Receipt2025-04-02Not public
Receipt2025-04-02Not public
250401_Request_Time_Period_Extension_R_9(3)_RoP_signed2025-04-01Not public
250401_Request_to_be_heard_R_9(1)_RoP_signed2025-04-01Not public
Panel-Appointment2025-03-14Not public
Receipt2025-03-14Not public
Acknowledgement-of-lodging2025-03-13Not public
Exhibit_CL_MM_08_Datasheet_Vision_One2025-03-13Not public
Exhibit_CL_MM_05_Ixia_s_Definite_Guide_to_Visibility_Use_Cases2025-03-13Not public
20250313_Noerr_Reply_to_Statement_of_Defence2025-03-13Not public
Exhibit_CL_MM_09_Application_and_Threat_Intelligence_Research_Center2025-03-13Not public
Exhibit_CL_MM_07_Datasheet_AppStack2025-03-13Not public
Exhibit_CL_22_Datasheet_SecureStack_Visibility_is_security2025-03-13Not public
Exhibit_CL_MM_14_Breach_and_Attack_Simulation_for_Dummies2025-03-13Not public
Exhibit_CL_MM_11_Datasheet_SecureStack2025-03-13Not public
Exhibit_CL_27_Keysight_Threat_Simulator_MSSPs2025-03-13Not public
Exhibit_CL_MM_06_How_Keysight_Solutions_Support_the_NIST_Cybersecurity_Framework2025-03-13Not public
Exhibit_CL_MM_04_www.keysight.com_us_en_products_network-visibility_network-packet-brokers.html2025-03-13Not public
Exhibit_CL_23_How_Keysight_Solutions_Support_the_NIST_Cybersecurity_Framework2025-03-13Not public
Exhibit_CL_24_Breach_and_Attack_Simulation_for_Dummies2025-03-13Not public
Exhibit_CL_19_Mitzenmacher_Expert_Statement2025-03-13Not public
Exhibit_CL_29_Ixia_V_Five_Ways_Improve_ROI_with_NPBs2025-03-13Not public
Exhibit_CL_20_Ixia_Security_Report-20192025-03-13Not public
Exhibit_CL_25_Threat_Simulator_Breach_and_Attack_Simulation_Platform2025-03-13Not public
Exhibit_CL_MM_16_ThreatARMOR_Kicks_Cyber_Risk_to_the_Curb_Named_Marsh_Cyber_Catalyst_Solution2025-03-13Not public
Exhibit_CL_MM_12_VisionONE_UserGuide_v6_7_0_Part_12025-03-13Not public
Exhibit_CL_MM_03_Ixia_s_Inline_Security_Architecture2025-03-13Not public
Exhibit_CL_MM_15_Keysight_Threat_Simulator_for_MSSPs2025-03-13Not public
Exhibit_CL_28_Sans_fortify_your_defenses_with_on_demand_simulated_attacks2025-03-13Not public
Exhibit_CL_MM_02_Ixia_5_Ways_To_Improve_ROI_With_Network_Packet_Brokers2025-03-13Not public
Exhibit_CL_MM_10_Ixia_Security_Report_20192025-03-13Not public
Exhibit_CL_MM_12_VisionONE_UserGuide_v6_7_0_Part_22025-03-13Not public
Exhibit_CL_MM_01_CV2025-03-13Not public
Exhibit_CL_26_Excerpt_Defendants_Website_Threat_Simulator_Phishing2025-03-13Not public
Exhibit_CL_21_Excerpt_Defendants_Website_ThreatARMOR2025-03-13Not public
Exhibit_CL_MM_13_Sans_Fortify_Your_Defenses_with_on_Demand_Simulated_Attacks2025-03-13Not public
Acknowledgement-of-lodging2025-03-13Not public
20250313_Noerr_Reply_to_SoD_New_Attacked_Products_in_TC2025-03-13Not public
20250313_Noerr_Request_Rule_2632025-03-13Not public
Exhibit_CL_23_How_Keysight_Solutions_Support_the_NIST_Cybersecurity_Framework2025-03-13Not public
Exhibit_CL_MM_13_Sans_Fortify_Your_Defenses_with_on_Demand_Simulated_Attacks2025-03-13Not public
Exhibit_CL_MM_05_Ixia_s_Definite_Guide_to_Visibility_Use_Cases2025-03-13Not public
Exhibit_CL_25_Threat_Simulator_Breach_and_Attack_Simulation_Platform2025-03-13Not public
Exhibit_CL_MM_12_VisionONE_UserGuide_v6_7_0_Part_12025-03-13Not public
Exhibit_CL_MM_01_CV2025-03-13Not public
Exhibit_CL_27_Keysight_Threat_Simulator_MSSPs2025-03-13Not public
Exhibit_CL_22_Datasheet_SecureStack_Visibility_is_security2025-03-13Not public
Exhibit_CL_19_Mitzenmacher_Expert_Statement2025-03-13Not public
20250313_Noerr_Reply_to_Statement_of_Defence2025-03-13Not public
Exhibit_CL_MM_04_www.keysight.com_us_en_products_network-visibility_network-packet-brokers.html2025-03-13Not public
Exhibit_CL_MM_10_Ixia_Security_Report_20192025-03-13Not public
Exhibit_CL_MM_12_VisionONE_UserGuide_v6_7_0_Part_22025-03-13Not public
Exhibit_CL_MM_15_Keysight_Threat_Simulator_for_MSSPs2025-03-13Not public
Exhibit_CL_MM_03_Ixia_s_Inline_Security_Architecture2025-03-13Not public
Exhibit_CL_MM_16_ThreatARMOR_Kicks_Cyber_Risk_to_the_Curb_Named_Marsh_Cyber_Catalyst_Solution2025-03-13Not public
Exhibit_CL_24_Breach_and_Attack_Simulation_for_Dummies2025-03-13Not public
Exhibit_CL_29_Ixia_V_Five_Ways_Improve_ROI_with_NPBs2025-03-13Not public
Exhibit_CL_28_Sans_fortify_your_defenses_with_on_demand_simulated_attacks2025-03-13Not public
Exhibit_CL_MM_08_Datasheet_Vision_One2025-03-13Not public
Exhibit_CL_MM_14_Breach_and_Attack_Simulation_for_Dummies2025-03-13Not public
Exhibit_CL_MM_06_How_Keysight_Solutions_Support_the_NIST_Cybersecurity_Framework2025-03-13Not public
Exhibit_CL_21_Excerpt_Defendants_Website_ThreatARMOR2025-03-13Not public
Exhibit_CL_26_Excerpt_Defendants_Website_Threat_Simulator_Phishing2025-03-13Not public
Exhibit_CL_MM_07_Datasheet_AppStack2025-03-13Not public
Exhibit_CL_MM_09_Application_and_Threat_Intelligence_Research_Center2025-03-13Not public
Exhibit_CL_MM_02_Ixia_5_Ways_To_Improve_ROI_With_Network_Packet_Brokers2025-03-13Not public
Exhibit_CL_20_Ixia_Security_Report-20192025-03-13Not public
Exhibit_CL_MM_11_Datasheet_SecureStack2025-03-13Not public
Panel-Appointment2025-02-20Not public
Outcome of the Order2025-02-14Not public
333-Ruecknahme2025-02-14Public
Outcome of the Order2025-02-14Not public
Antrag-3332025-02-14Public
Receipt2025-02-04Not public
Withdrawal of application for review of a case management order2025-02-03Not public
Acknowledgement-of-lodging2025-01-28Not public
250124_EP580_R333_Application_signed2025-01-24Not public
Outcome of the Order2025-01-23Not public
FV2025-01-23Public
Receipt2025-01-14Not public
_Noerr_Request_Deadline_Extension_41285_2024_App_2082_20252025-01-13Not public
Outcome of the Order2025-01-13Not public
Gehdeimhaltung22025-01-13Public
Geheimhaltung22025-01-13Public
Noerr_Statement_RoP262A_41285_2024_App_64114_20242025-01-07Not public
Receipt2024-12-23Not public
Noerr_Request_R9_41285_2024_App_67476_20242024-12-20Not public
Noerr_Statement_RoP262A_41285_2024_App_64114_20242024-12-20Not public
262A.vorl.2024-12-10Not public
Receipt2024-12-05Not public
Application for allocating a technically qualified judge2024-12-05Not public
Formal-checks_Notification-of-positive-outcome2024-12-04Not public
Formal-checks_Notification-of-positive-outcome2024-12-04Not public
Receipt2024-12-04Not public
R. 262A Request2024-12-03Not public
R. 262.2 Request2024-12-03Not public
Acknowledgement-of-lodging2024-12-03Not public
Acknowledgement-of-lodging2024-12-03Not public
HRM_062024-12-03Not public
HRM_02d2024-12-03Not public
Statement of Defence2024-12-03Not public
HRM_08b2024-12-03Not public
HRM_02l_22024-12-03Not public
HRM_02u2024-12-03Not public
HRM_07f2024-12-03Not public
HRM_03b2024-12-03Not public
HRM_07d2024-12-03Not public
HRM_02j2024-12-03Not public
HRM_02b2024-12-03Not public
HRM_07h2024-12-03Not public
HRM_042024-12-03Not public
HRM_07a2024-12-03Not public
HRM_072024-12-03Not public
HRM_07j2024-12-03Not public
HRM_02v2024-12-03Not public
HRM_03a_22024-12-03Not public
HRM_03d2024-12-03Not public
HRM_07e2024-12-03Not public
HRM_03c_22024-12-03Not public
HRM_02l_12024-12-03Not public
HRM_02f2024-12-03Not public
HRM_072024-12-03Not public
HRM_022024-12-03Not public
HRM_08a2024-12-03Not public
HRM_08b2024-12-03Not public
HRM_02n2024-12-03Not public
HRM_02a2024-12-03Not public
HRM_07j2024-12-03Not public
HRM_07i2024-12-03Not public
HRM_042024-12-03Not public
HRM_07c2024-12-03Not public
HRM_02t_22024-12-03Not public
HRM_02g2024-12-03Not public
HRM_02e_22024-12-03Not public
Statement of Defence2024-12-03Not public
HRM_02m2024-12-03Not public
HRM_082024-12-03Not public
HRM_02e_12024-12-03Not public
HRM_03e2024-12-03Not public
HRM_07e2024-12-03Not public
HRM_08a2024-12-03Not public
HRM_02r2024-12-03Not public
HRM_07b2024-12-03Not public
HRM_02k2024-12-03Not public
HRM_03a_12024-12-03Not public
HRM_02t_12024-12-03Not public
HRM_082024-12-03Not public
HRM_02q2024-12-03Not public
HRM_02s2024-12-03Not public
HRM_07g2024-12-03Not public
HRM_052024-12-03Not public
HRM_02c2024-12-03Not public
HRM_03g2024-12-03Not public
HRM_02w2024-12-03Not public
HRM_07h2024-12-03Not public
HRM_07g2024-12-03Not public
HRM_03c_12024-12-03Not public
HRM_07j2024-12-03Not public
HRM_02h2024-12-03Not public
HRM_092024-12-03Not public
HRM_032024-12-03Not public
HRM_02i2024-12-03Not public
HRM_07d2024-12-03Not public
HRM_07f2024-12-03Not public
HRM_012024-12-03Not public
HRM_02o2024-12-03Not public
HRM_07a2024-12-03Not public
HRM_07c2024-12-03Not public
HRM_07b2024-12-03Not public
HRM_03f2024-12-03Not public
HRM_07i2024-12-03Not public
HRM_02p2024-12-03Not public
Statement of Defence_Reference Defendant22024-12-03Not public
Outcome of the Order2024-09-06Not public
Frist2024-09-06Public
Receipt2024-09-06Not public
Procedural Application2024-09-05Not public
Acknowledgement of access to case2024-09-03Not public
Notification Of Service2024-09-03Not public
Acknowledgement of access to case2024-08-20Not public
Notification Of Service2024-08-20Not public
epoUploadDocumentsWorkflow2024-08-07Not public
Document from EPO2024-08-07Not public
Panel-Appointment2024-07-25Not public
EPO-Request-for-case-pending2024-07-23Not public
Receipt2024-07-23Not public
Formal-checks_Notification-of-positive-outcome2024-07-23Not public
Acknowledgement-of-lodging2024-07-22Not public
Exhibit_CL_02_German_Keysight_Offices2024-07-22Not public
Exhibit CL 1_Company_Information_Germany2024-07-22Not public
Exhibit_CL_04_Network_Visibility_Keysight2024-07-22Not public
Exhibit_CL_09_Website_Appstack2024-07-22Not public
Exhibit_CL_07_Ixias_Inline_Security_Architecture2024-07-22Not public
Exhibit_CL_14_Product_Page_France2024-07-22Not public
Exhibit_CL_06_Network_Packet_Broker_Comparison_Keysight2024-07-22Not public
Exhibit re. Payment of Court Fees2024-07-22Not public
Exhibit_CL_10_Data_Sheet_Vision_ONE2024-07-22Not public
Exhibit_CL_15_Product_Page_Netherlands2024-07-22Not public
Exhibit_CL_05_Network_Packet_Brokers_Keysight2024-07-22Not public
Exhibit_CL_12_Application_Threat_Intelligence_Research_Center2024-07-22Not public
Noerr_Statement_of_Claim_EP_580_Keysight2024-07-22Not public
Exhibit_CL_08_AppStack2024-07-22Not public
Exhibit_CL_18_Tochtermann_ZGE_20192024-07-22Not public
Exhibit_CL_11_Whitepaper_Ixias_Guide_to_Visibility_Use_Cases2024-07-22Not public
Exhibit_CL_16_Product_Page_Italy2024-07-22Not public
Exhibit_CL_13_Product_Page_Germany2024-07-22Not public
Exhibit_CL_03_EP3821580B12024-07-22Not public
Exhibit_CL_17_Keysights_Borderless_Information_Security_Program2024-07-22Not public
Exhibit_CL_3a_Feature_Breakdown_EP_3_821_580_ B12024-07-22Not public
Plain-English summary

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.

Accepted arguments
What the court agreed with — by party.
  • Defendants' products do not incorporate the claim requirement of routing packets to a CAS (Cyber Analysis System) based on threat metadata

    RespondentLegal basis: R. 171 RoP

    Note: 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

    RespondentLegal basis: R. 263 RoP; R. 265 RoP; R. 30.1.c, 118.2.a RoP

    Note: 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

    RespondentLegal basis: R. 114 RoP; R. 245 RoP; Art. 81 UPCA

    Note: 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.

Rejected arguments
What the court did not agree with — and why.
  • Defendants' AppStack, SecureStack-SSL and Threat Simulator products directly infringe claim 16 and indirectly infringe claim 1

    ClaimantLegal basis: R. 171 RoP

    Reason: 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

    ClaimantLegal basis: R. 114 RoP

    Reason: 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.

Claim construction notes

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.