Defending an Infringement Claim

English · Deutsch · Français

A UPC infringement defence must protect the litigation position and keep the business operational. The first response should bring legal, engineering, commercial and document-management teams together. A good defence addresses the asserted product version, the patent’s validity, the claimant’s requested remedies and the practical options for continued supply.

In this guide: Control the first response · Develop a coherent non-infringement position · Decide whether and how to challenge validity · Address licences, exhaustion and territorial limits · Prepare operational alternatives without conceding liability

Control the first response

Record how and when proceedings were served, identify every defendant and verify the procedural timetable immediately. Preserve relevant technical and commercial records, including product versions, design decisions, purchase documents and licence correspondence. Give the legal team a reliable description of the accused implementation. Internal assumptions such as ‘our supplier owns the technology’ or ‘we have our own patent’ do not answer the infringement allegation. Separate urgent procedural decisions from the longer technical investigation, but run both workstreams at once.

Develop a coherent non-infringement position

Start with the claims actually asserted and interpret them using the patent description and drawings. Identify which features are absent, implemented differently or attributed to the wrong entity. Explain the technical consequence of the difference; a different name or appearance is rarely enough. Preserve a representative sample and the relevant software configuration. Where confidential source code or manufacturing information is needed, plan a protection request before disclosure. Assess literal infringement and any argument based on equivalents separately.

Decide whether and how to challenge validity

A revocation counterclaim requires a substantiated case, not a general assertion that the invention was already known. Search the relevant field, establish publication dates and analyse novelty, inventive step, sufficiency and amendments against the applicable legal standards. Older products, standards contributions and archived manuals may be more valuable than a large collection of loosely related patents. Check how a possible amended claim would affect the infringement defence. A successful attack on one claim does not necessarily dispose of every asserted claim.

Address licences, exhaustion and territorial limits

Review the chain of authorised sales and any licences covering the accused activity. A supplier’s contractual indemnity allocates risk between businesses but does not itself establish permission from the patent owner. Exhaustion, prior use and statutory exceptions require their own facts and may have territorial limits. Map where manufacturing, offers, imports, sales and use occur. Challenge relief that goes beyond the proven conduct or applicable patent rights, while avoiding broad assumptions that a foreign manufacturing location resolves the dispute.

Prepare operational alternatives without conceding liability

A design-around, standstill, limited licence or supply adjustment can reduce exposure while the case proceeds. Have engineers document the changed technical features and assess the revised product against the claims. Keep version control so that legacy inventory is not confused with the new implementation. Model the cost of an injunction, information order and damages alongside legal spend. Settlement discussions should address existing stock, customer commitments, affiliates and future product generations, not only the immediate court deadline.

Four practical examples

These hypothetical examples explain typical decisions and evidence issues. They do not describe client matters or predict a court outcome.

1. A missing sensor function

A claim requires two sensor signals to be combined in a particular control step. The accused device stores both signals but uses only one for that step. Engineers produce architecture documents and controlled tests to explain the distinction. The defence focuses on the claimed operation, rather than the superficial fact that both sensors are physically present.

2. Supplier indemnity with a narrow scope

A retailer receives a claim covering a component sourced from a third party. The supply agreement includes an indemnity limited to certain territories and subject to prompt notice. The retailer notifies the supplier, preserves its own defence deadlines and investigates whether any upstream patent licence exists. The indemnity and the infringement defence remain separate workstreams.

3. An earlier public demonstration

A company remembers displaying similar technology before the patent’s priority date. Its technical team locates dated brochures, visitor records and a surviving demonstration unit. Counsel examines exactly what was made available to the public and whether confidentiality restrictions applied. The resulting evidence may support a specific validity attack; recollection alone would be inadequate.

4. A controlled product redesign

A possible injunction threatens a major customer contract. A revised product removes the contested technical relationship while keeping commercial performance. The company obtains a fresh claim analysis, separates inventory and updates installation instructions. This creates a practical continuity option without assuming that a cosmetic change will avoid the patent.

Related guidance

Revocation Counterclaims · Protective Letters · Claim Construction and Equivalents · Permanent Injunctions, Recall and Destruction

Legal framework and sources

Articles 25–29, 47, 54, 58 and 65 UPCA.

Agreement on a Unified Patent Court · Current UPC legal documents and Rules of Procedure

Discuss your patent matter

For an initial enquiry, identify the patent, the product or process and any known court or launch deadline. Please leave out confidential technical details until conflicts have been checked.