DCT

6:23-cv-00582

Patent Armory Inc v. Enterprise Holdings Inc

Key Events
Complaint
complaint

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 6:23-cv-00582, W.D. Tex., 08/11/2023
  • Venue Allegations: Venue is alleged to be proper based on Defendant maintaining an established place of business in the Western District of Texas.
  • Core Dispute: Plaintiff alleges that Defendant’s customer service and vehicle reservation systems infringe five patents related to intelligent call routing and auction-based resource matching.
  • Technical Context: The technology at issue involves optimizing call center operations by using algorithms to match incoming communications with the most suitable agents, considering factors like agent skills, economic efficiency, and training opportunities.
  • Key Procedural History: The complaint does not specify any prior litigation, licensing history, or administrative challenges involving the patents-in-suit.

Case Timeline

Date Event
2002-03-07 Priority Date for ’979 and ’253 Patents
2003-03-07 Priority Date for ’420 and ’086 Patents
2006-04-03 Priority Date for ’748 Patent
2006-04-04 ’979 Patent Issued
2007-09-11 ’253 Patent Issued
2016-09-27 ’086 Patent Issued
2019-03-19 ’420 Patent Issued
2019-11-26 ’748 Patent Issued
2023-08-11 Complaint Filed

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 10,237,420: “Method and system for matching entities in an auction” (Issued Mar. 19, 2019)

The Invention Explained

  • Problem Addressed: The patent describes the technical challenge of efficiently managing call centers, which must balance customer service quality with resource utilization ('420 Patent, col. 1:26-34). It notes the limitations of conventional systems that use simple "first-come-first-served" routing or static "skill-based" routing, which can result in mismatches between callers and agents or inefficient use of highly skilled personnel ('420 Patent, col. 3:1-4:54).
  • The Patented Solution: The invention proposes a system that treats the matching of a "first entity" (e.g., a caller) with a "second entity" (e.g., an agent) as an economic optimization problem ('420 Patent, Abstract). The system defines parameters for both entities using "multivalued scalar data" and performs an "automated optimization" that considers not only the "economic surplus" of a potential match but also the "opportunity cost" of making that specific agent unavailable for other potential matches ('420 Patent, Abstract). This allows for more dynamic and globally optimized resource allocation than prior art methods ('420 Patent, col. 18:8-23).
  • Technical Importance: The claimed approach purports to move beyond static, rule-based call distribution to a dynamic, economically-driven optimization model, intended to improve overall call center efficiency and effectiveness ('420 Patent, col. 18:8-23).

Key Claims at a Glance

  • The complaint asserts infringement of "one or more claims" without specification (Compl. ¶15). Independent claim 1 is representative and includes the following essential elements:
    • A method for matching a first entity with at least one second entity selected from a plurality of second entities.
    • Defining a plurality of multivalued scalar data representing inferential targeting parameters for the first entity.
    • Defining a plurality of multivalued scalar data for each of the plurality of second entities, representing their characteristic parameters.
    • Performing an automated optimization with respect to an economic surplus of a match and an opportunity cost of the unavailability of the second entity for an alternate match.

U.S. Patent No. 10,491,748: “Intelligent communication routing system and method” (Issued Nov. 26, 2019)

The Invention Explained

  • Problem Addressed: This patent, from the same family as the ’420 patent, addresses the same technical problems of call center inefficiency and the limitations of prior art routing systems ('748 Patent, col. 1:22-34).
  • The Patented Solution: The invention is a system and method for intelligent communication routing that operates at a low level within the computer-telephony integration (CTI) architecture ('748 Patent, col. 18:8-14). It uses a "call classification vector" to represent the needs of an incoming communication and a table of "agent characteristic vectors" to represent the capabilities of available agents ('748 Patent, Claim 1). The system applies a table of "skill weights" to these vectors to determine an "optimum agent selection" and control call routing accordingly ('748 Patent, Claim 1). This integration of the optimization logic into the low-level switching system is described as a way to reduce latencies and communication burdens associated with high-level external management software ('748 Patent, col. 25:46-54).
  • Technical Importance: By integrating the intelligent routing logic directly into the low-level communications server, the invention aims to enable real-time, inferential routing decisions that are more responsive and efficient than systems relying on separate, high-level management platforms ('748 Patent, col. 18:8-23).

Key Claims at a Glance

  • The complaint asserts infringement of "one or more claims" without specification (Compl. ¶21). Independent claim 1 is representative and includes the following essential elements:
    • A method for routing communications.
    • Receiving a call classification vector.
    • Receiving a table of agent characteristic vectors.
    • Determining an optimum agent selection based on a correspondence of the call and agent vectors.
    • Controlling call routing based on the determination.
    • Maintaining and applying a table of skill weights to determine the optimum selection.

Multi-Patent Capsules

U.S. Patent No. 7,023,979: “Telephony control system with intelligent call routing” (Issued Apr. 4, 2006)

  • Technology Synopsis: This patent describes a telephony control system that provides for intelligent call routing. The system performs an optimization to match incoming calls with agents based on a variety of factors, including agent skills and call characteristics, to improve upon simple first-in, first-out queuing systems (Compl. ¶11; ’979 Patent, Abstract).
  • Asserted Claims: The complaint asserts "one or more claims" without further specification (Compl. ¶30).
  • Accused Features: The complaint alleges infringement by the "Exemplary Defendant Products" identified in an incorporated chart that was not provided (Compl. ¶30).

U.S. Patent No. 7,269,253: “Telephony control system with intelligent call routing” (Issued Sep. 11, 2007)

  • Technology Synopsis: This patent discloses a telephony control system that performs a combinatorial optimization to match communications with potential targets. The system determines an optimal routing by considering a cost-benefit analysis based on the characteristics of the communication and the available targets (’253 Patent, Abstract).
  • Asserted Claims: The complaint asserts "one or more claims" without further specification (Compl. ¶39).
  • Accused Features: The complaint alleges infringement by the "Exemplary Defendant Products" identified in an incorporated chart that was not provided (Compl. ¶39).

U.S. Patent No. 9,456,086: “Method and system for matching entities in an auction” (Issued Sep. 27, 2016)

  • Technology Synopsis: This patent relates to a method for matching a first entity with a second entity by performing an automated optimization. The optimization considers the "economic surplus" of a potential match as well as the "opportunity cost" of making a resource unavailable for an alternative match, framing the matching process as an auction (’086 Patent, Abstract).
  • Asserted Claims: The complaint asserts "one or more claims" without further specification (Compl. ¶45).
  • Accused Features: The complaint alleges infringement by the "Exemplary Defendant Products" identified in an incorporated chart that was not provided (Compl. ¶45).

III. The Accused Instrumentality

Product Identification

The complaint does not identify specific accused products or services by name. It refers generally to "the Defendant products identified in the charts incorporated into this Count below (among the ‘Exemplary Defendant Products’)" (Compl. ¶15, ¶21, ¶30, ¶39, ¶45).

Functionality and Market Context

The complaint does not provide sufficient detail for analysis of the accused instrumentality's specific functionality. As Defendant is a vehicle rental company, the accused instrumentalities are presumably its customer service, reservation, and communication systems used to interact with customers (Compl. ¶3). The complaint alleges Defendant makes, uses, sells, offers to sell, and/or imports these products and has its employees internally test and use them (Compl. ¶15-16). No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

The complaint makes infringement allegations by incorporating by reference claim chart exhibits (Exs. 6, 7, 8, 9, 10) that were not publicly filed with the complaint (Compl. ¶17, ¶26, ¶35, ¶41, ¶50). The complaint does not contain a narrative description of the accused functionality sufficient to construct a claim chart summary.

Identified Points of Contention

Based on the language of the patents and the general nature of the dispute, the infringement analysis may raise the following questions:

  • Scope Questions: A central question may be whether patent terms rooted in economic and auction theory, such as "auction," "economic surplus," and "opportunity cost" ('420 Patent, Abstract), can be construed to cover the Defendant’s alleged process for assigning customer communications to available agents. The analysis may explore whether a conventional system of prioritizing or assigning resources meets the specific definitions required by the claims.
  • Technical Questions: The patents-in-suit claim methods involving "multifactorial optimization" and the creation and use of specific data structures like a "call classification vector" ('748 Patent, Claim 1). A key evidentiary question may be what proof exists that Defendant's systems perform these specific, computationally complex optimizations, as opposed to employing more conventional skill-based or longest-idle routing methods described as prior art in the patents ('420 Patent, col. 4:10-34).

V. Key Claim Terms for Construction

The Term: "automated optimization" (from ’420 Patent, Claim 1)

  • Context and Importance: This term is central to the inventive concept of moving beyond simple routing rules to a dynamic, goal-oriented matching process. Practitioners may focus on this term because the infringement case could turn on whether Defendant's system merely applies pre-set rules or performs a genuine "optimization" as defined by the patent.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification suggests the optimization can be based on various factors, including "training opportunities" in addition to pure economics, potentially broadening the term to include any automated process that selects an agent to advance a business goal ('420 Patent, col. 21:3-6).
    • Evidence for a Narrower Interpretation: The abstract and Claim 1 explicitly tie the "automated optimization" to calculations involving "an economic surplus" and "an opportunity cost," which may support a narrower construction requiring the system to perform specific economic calculations rather than a general-purpose selection ('420 Patent, col. 20:36-46).

The Term: "call classification vector" (from ’748 Patent, Claim 1)

  • Context and Importance: The existence and use of this specific data structure is a required element of the asserted claim. The dispute may focus on whether the data Defendant's system collects and uses for routing qualifies as the claimed "vector."
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent specification describes this vector as potentially comprising basic call data, such as information gathered from an interactive voice response system or the caller's telephone number, which could support a broad reading on any system that uses such data for routing ('748 Patent, col. 35:48-60).
    • Evidence for a Narrower Interpretation: The patent links the vector to a "multifactorial optimization" and a table of "skill weights," suggesting it is not merely a collection of data points but a structured input for a specific type of algorithm, potentially supporting a narrower definition that requires a specific format and use ('748 Patent, col. 31:54-66).

VI. Other Allegations

Indirect Infringement

For the ’748, ’979, and ’086 patents, the complaint alleges induced infringement. The allegations are based on Defendant selling the accused products and distributing "product literature and website materials inducing end users and others to use its products in the customary and intended manner that infringes" the patents (Compl. ¶24, ¶33, ¶48).

Willful Infringement

The complaint does not contain an explicit allegation of willful infringement. It alleges that "service of this Complaint, in conjunction with the attached claim charts and references cited, constitutes actual knowledge of infringement" for the ’748, ’979, and ’086 patents (Compl. ¶23, ¶32, ¶47). This allegation may form a basis for seeking enhanced damages for any post-filing infringement but does not allege the pre-suit knowledge typically required for a finding of willfulness.

VII. Analyst’s Conclusion: Key Questions for the Case

  • A core issue will be one of definitional scope: can patent terms rooted in economic theory, such as "auction" and "economic surplus," be construed to cover the Defendant’s alleged customer-to-agent matching system, which may operate on different principles?
  • A key evidentiary question will be one of technical operation: does the complaint, which relies entirely on unfiled exhibits for its infringement theories, provide sufficient factual support to plausibly demonstrate that Defendant's systems perform the specific "multifactorial optimization" and utilize the claimed "vector"-based data structures, or do they employ more conventional call-routing logic?