Product Glossary: A Patent Enforcement Tool

Product Glossary: A Patent Enforcement Tool

Event Date

Location

Introduction: Why Terminology Becomes a Battleground 

In patent enforcement, the dispute is rarely about whether a product exists. It is about what the product is, what it does, and what its parts are called. A claim term may appear to describe a feature in an accused product, yet the manufacturer’s documentation may describe that feature using entirely different words. Once litigation begins, that gap can become the centre of the case. 

A product glossary is more than a list of technical terms for researchers. When built properly, it becomes a strategic, evidence-backed knowledge repository that helps patent enforcement teams identify terminology differences, investigate product functionality, and prepare for disputes over claim interpretation before they arise. 

Why Does Terminology Create Risk in Litigation? 

Patents are drafted using language selected for breadth and legal precision. Commercial documentation, by contrast, is written for customers, engineers, and marketers. A patent may claim a “data synchronization module”, while product materials refer to a “cloud sync engine”, a “background updater”, or a “connectivity service”. The terminology differs, even when the underlying functions may overlap. 

When a matter enters litigation, an accused infringer may take one of three positions: 

  • Deny that the feature exists: The product, it argues, does not contain the claimed functionality. 
  • Dispute the claim term’s meaning: The term, it contends, has a different meaning in the context of its product. 
  • Describe a different operation: The technology, it maintains, works differently from the way the patent describes. 

Without prior preparation, each position can slow the development of infringement contentions, complicate claim charts, and leave the enforcement team reacting to technical arguments rather than anticipating them. 

Investigators may struggle to identify how a claimed concept appears under different terminology. Team members may describe the same component inconsistently, while evidentiary gaps may surface only after important litigation deadlines have passed. 

A structured product glossary helps address these challenges by bringing terminology, functionality, and supporting evidence together in one accessible repository. 

What Should a Product Glossary Contain? 

A litigation-readiness glossary goes well beyond a simple collection of terms and definitions. Its core elements should include: 

  • Product-specific terminology: Official, internal, marketing, and version-specific names for features and components. 
  • Alternative technical expressions: Synonyms, abbreviations, and legacy names used across datasheets, manuals, and developer documentation. 
  • Underlying functionality: A technically grounded description of what a feature does, independent of the terminology used to describe it. 
  • Component relationships: Information about how modules and subsystems connect, including their hierarchy, data flows, and dependencies. 
  • Potential claim-term relationships: Candidate mappings between patent language and product features, clearly identified as hypotheses rather than established conclusions. 
  • Supporting evidence: References to specific documents, pages, specifications, or test records, including relevant dates and product versions. 
  • Conflicting descriptions: Instances where sources disagree, such as a marketing page that describes a function differently from a technical manual. 
  • Unresolved questions: Open issues requiring further investigation, testing, or discovery. 

Together, these elements create a reusable repository that supports consistent analysis across products, patent claims, and enforcement investigations. 

How Does a Product Glossary Connect Patent Claims to Products? 

A product glossary acts as a bridge between three essential elements: patent claim language, real-world product functionality, and supporting evidence. 

Consider an investigator analysing a claim element that recites a “processing unit configured to prioritize requests”. The product documentation does not use the phrase “processing unit” or explicitly state that the system “prioritizes” requests. 

A well-developed glossary entry might look like this: 

Claim term: “Processing unit configured to prioritize requests” 

Product term: “Request scheduler”, identified in the version 4.2 administrator guide, page 31. 

Functionality: Orders queued requests according to configurable priority rules. 

Candidate mapping: Hypothesis that the request scheduler corresponds to the claimed processing unit. 

Supporting evidence: Administrator guide and developer documentation describing rule-based queue ordering. 

Conflicting evidence: A marketing page describes scheduling as “first come, first served”. 

Open question: Do priority rules apply by default, or only after configuration? 

This entry allows the investigator to identify a potential mapping quickly, examine the evidence supporting it, recognise conflicting descriptions that the opposing party may rely on, and identify what additional proof is required. 

The resulting claim chart can therefore be developed using documented technical evidence rather than unsupported assumptions. 

Does a Product Glossary Prove That Different Terms Mean the Same Thing? 

No. This distinction is essential to the integrity of the approach. 

A product glossary should not presume that different terms describe identical functionality, nor should it imply that a manufacturer is deliberately disguising a feature. Differences in terminology are often ordinary. Engineering teams, marketing departments, and patent drafters use language for different purposes and audiences. 

The value of a glossary lies in its disciplined neutrality. It records potential relationships as hypotheses to be tested, distinguishes established facts from working assumptions, and preserves evidence that challenges a proposed mapping as carefully as evidence that supports it. 

This balanced approach helps enforcement teams evaluate alternative explanations before they become contested issues in litigation. 

A team that has already considered counterarguments is better positioned to address them than one encountering them for the first time during a hearing or claim construction dispute. 

How Should Teams Build and Maintain a Product Glossary? 

A product glossary delivers the greatest value when development begins early and follows a consistent methodology. 

  1. Start during the investigation

Build the glossary before a complaint is filed, where practical. Use a standard entry template to ensure that each record captures the same essential information. 

  1. Gather evidence from multiple sources

Review publicly available documentation, technical manuals, developer guides, release notes, regulatory filings, and information obtained through lawful testing where available. 

  1. Record the provenance of every entry

Document the source, publication date, relevant product version, and method by which the information was obtained. This makes it easier to verify findings and establish the context in which a description was used. 

  1. Maintain version control

Product functionality and terminology can change between releases. Version control helps ensure that proposed mappings relate to the specific accused product and version under investigation. 

  1. Assign technical and legal review

Technical specialists should assess whether the descriptions accurately reflect product functionality, while legal reviewers evaluate their relevance to the patent claims and enforcement strategy. 

  1. Apply appropriate protection measures

Because the glossary may incorporate attorney analysis or litigation strategy, counsel should guide its preparation and handling, including consideration of applicable privilege and work-product protections. 

Common pitfalls include treating the glossary as a one-time deliverable, recording conclusions without supporting evidence, overlooking contradictory material, relying too heavily on marketing language, and allowing untested hypotheses to become accepted assumptions. 

Regular review helps keep the repository accurate, relevant, and useful as investigations progress. 

A Quick Product Glossary Readiness Check 

Patent enforcement teams can assess their preparedness by asking five questions: 

  1. Have we identified the different names the manufacturer uses for the relevant product features? 
  2. Can we trace each description to a dated source and the correct product version? 
  3. Have we identified and documented conflicts between different sources? 
  4. Do our claim-term mappings distinguish hypotheses from established facts? 
  5. Could a new team member use the glossary to prepare a consistent, evidence-supported claim chart? 

If several answers are “no”, there is meaningful scope to strengthen litigation readiness before terminology disputes arise. 

Conclusion: From Reference Document to Strategic Resource 

A product glossary approached superficially is simply a list of terms. Approached strategically, it becomes a litigation-readiness resource that connects patent claim language, real-world product functionality, and supporting evidence in one structured, reusable repository. 

Its value does not lie in proving that different words mean the same thing. Instead, it ensures that when terminology is challenged, the enforcement team already understands the product, has documented the relevant evidence, has identified gaps, and has considered alternative explanations. 

This preparation can support more comprehensive claim charts, better-supported infringement theories, earlier identification of evidentiary gaps, and more informed responses to technical disputes. 

For patent enforcement teams dealing with complex products and contested claim interpretation, building and maintaining a product glossary before a dispute begins is a practical step towards stronger, better-prepared enforcement. 

Author

Related Posts