Enforcement and litigation of software patents

Understanding the enforcement and litigation of software patents is essential, given the unique challenges and considerations in protecting these intangible assets.

Types of infringement in the software context

The three traditional types of patent infringement—direct, induced, and contributory—take on specific nuances in the context of software:

• Direct infringement: This occurs when an accused software product or system, as a whole, performs all the steps of a patented method or incorporates all the features of a patented apparatus. In software cases, this can be complex when the software’s functionality is distributed across multiple systems or users.
• Induced infringement: This occurs when someone induces another to infringe a patent. In the software context, this could involve providing software tools or instructions that enable users to infringe a software patent, such as by enabling the circumvention of a patented security feature.
• Contributory infringement: This occurs when someone sells or offers to sell a component of a patented invention, knowing it to be especially adapted for use in an infringement, and that component is not a staple article or commodity of commerce suitable for substantial non-infringing use. In the software context, this might involve distributing a software module specifically designed to interact with a patented system in an infringing manner.

Types of evidence in software patent litigation

The evidence used to establish software patent infringement often goes beyond that used in traditional patent cases. Here’s a breakdown of key types of evidence and their specific considerations for software:

• Source code analysis: This involves comparing the source code of the accused software with the claims of the patent. While potentially compelling, access to source code may be limited due to trade secret👉 Protects confidential business info for competitive advantage. protection or licensing👉 Permission to use a right or asset granted by its owner. agreements. Moreover, even with access, demonstrating equivalence between different code implementations of the same functionality can be technically challenging and time-consuming.
• Functional analysis: This focuses on demonstrating that the accused software performs the steps or functions claimed in the patent, regardless of the underlying code. This often involves reverse engineering or expert analysis to map the software’s behavior to the patent claims.
• Expert witness testimony: Given the complexity of software, expert witnesses are crucial in software patent litigation. They can explain intricate software concepts to the court, interpret patent claims in the context of software technology, and provide opinions on whether the accused software infringes the patent. The selection of highly qualified experts with specific expertise in the relevant area of software is therefore essential.
• Digital forensics: In some cases, digital forensics techniques may be necessary to uncover evidence of infringement. This could involve analyzing data logs, network traffic, or storage media to demonstrate unauthorized use or copying of patented software.

Claim construction in software cases

Claim construction, the process of interpreting the meaning and scope of patent claims, is particularly critical in software patent litigation. Software patents often employ functional language, and the court’s interpretation of such language can significantly impact the outcome of the case. While the fundamental goal of claim construction—to determine what the claims mean to a person skilled in the art—is consistent across jurisdictions, the specific rules and practices vary. Here’s how claim construction is approached in Europe, the US, and China:

• Europe: Claim construction at the European Patent Office (EPO) and in national courts focuses on determining the meaning of the terms in the context of the patent as a whole, including the description and drawings. The emphasis is on identifying the technical features of the invention. While functional language is permitted, the scope of protection may be limited to the specific examples and their equivalents disclosed in the specification. The EPO Boards of Appeal have developed principles to ensure a fair balance between the patentee’s rights and the interests of third parties.
• United States: In the US, claim construction is a matter of law for the court, guided by precedent from the Court of Appeals for the Federal Circuit. The court considers both the intrinsic evidence (the patent itself, including the claims, specification, and prosecution history) and extrinsic evidence (expert testimony, dictionaries, and technical treatises). A key feature of US claim construction is the treatment of “means-plus-function” claims (35 U.S.C. § 112(f)), which are commonly used in software patents. These claims are construed to cover the corresponding structure, material, or acts described in the specification and their equivalents.
• China: Claim construction in China is conducted by the courts and guided by the interpretation rules issued by the Supreme People’s Court (SPC). Similar to other jurisdictions, the claims are interpreted in light of the specification and drawings. Emphasis is placed on the technical features of the invention and their contribution to the claimed technical solution. Functional language is permitted but must be supported by a sufficiently clear description of how the function is implemented.

Injunctive relief

Both preliminary and permanent injunctions are crucial tools for enforcing software patents. They serve to prevent further infringement and protect the patent holder’s exclusive rights. However, courts may consider the following factors, which are particularly salient in software cases, when granting such relief:

• The nature of the infringing software: If the infringing software is a small component of a larger, complex system, particularly one with significant public benefit (e.g., a medical device or critical infrastructure), the court may be less inclined to grant a broad injunction that could disrupt essential services or harm the public. The court will weigh the potential harm to the patent holder against the potential harm to the public.
• The public interest: If the infringing software is used in critical infrastructure or public services, the court must balance the patent holder’s right to exclude with the potential disruption to the public. In such cases, the court may tailor the injunction to minimize disruption, such as by granting a limited injunction or allowing continued use under a compulsory license with reasonable royalties.
• The potential for design-arounds: Courts may also consider the feasibility and time frame for the infringer to design around the patented feature. If a design-around is readily available, the court may be more willing to grant an injunction, whereas if a design-around would require a complete system overhaul, the court may be less inclined to do so.

Monetary damages

Monetary damages are awarded to compensate the patent holder for the economic harm caused by the infringement. Calculating damages in software patent cases can be particularly complex. Traditional methods for determining damages, such as lost profits and reasonable royalties, must be adapted to the specific characteristics of software:

• Lost profits: To recover lost profits, the patent holder must demonstrate that, but for the infringement, they would have made the sales that were made by the infringer. This can be difficult in software cases, especially if the patented software is one of many features in a larger software product, as it can be challenging to isolate the portion of lost sales attributable to the infringement.
• Reasonable royalties: When lost profits cannot be proven, courts may award damages based on a reasonable royalty. This involves determining the amount a willing licensor and a willing licensee would have agreed upon in a hypothetical negotiation at the time the infringement began. Factors considered may include:
  • The importance of the patented feature to the infringing software’s functionality and commercial success.
  • The cost incurred by the patent holder in developing the patented technology.
  • The presence of alternative, non-infringing solutions.
  • Industry licensing practices and rates for similar software technologies.
  • The remaining term of the patent.
• Valuing the patented component: Software is often integrated into larger systems, such as complex enterprise software suites or cloud-based platforms, making it difficult to isolate the value of the patented component. Expert testimony from economists and technical experts is often crucial in these cases to disentangle the value contributions of the patented feature from the overall product.
• Determining the contribution of the patented invention: Courts must determine how much the patented software feature contributes to the overall value of the infringing product. This can involve analyzing:
  • User demand: How much of the product’s appeal is attributable to the patented feature?
  • Market share: Did the patented feature give the infringing product a competitive advantage and increase its market share?
  • Functionality: How essential is the patented feature to the overall functionality of the infringing software?

The presence of non-infringing alternatives: Could users have easily switched to a non-infringing product?

Enhanced damages

Enhanced damages, typically up to three times the amount of compensatory damages, may be awarded for willful infringement. While available in software patent cases as in other patent cases, determining willfulness in the software context can be complex.

It’s important to note that the specifics of how “willfulness” is determined and what factors are considered can vary significantly between different legal systems. The description here is generally most applicable to U.S. law.

Factors that courts consider include:

• The infringer’s knowledge of the patent: Did the infringer have actual knowledge of the patent and intentionally infringe it, or were they merely negligent?
• The infringer’s conduct: Did the infringer take reasonable steps to avoid infringement, such as obtaining a legal opinion from competent counsel, conducting a thorough freedom-to-operate analysis, or attempting to design around the patent? Or did they proceed recklessly despite a known risk👉 The probability of adverse outcomes due to uncertainty in future events. of infringement? The timing of the infringement is also relevant. Infringement that began after the infringer had knowledge of the patent is more likely to be deemed willful.