DCT

1:26-cv-00771

Usconnect LLC v. Cantaloupe LLC

Log In
Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 1:26-cv-00771, M.D.N.C., 08/06/2026
  • Venue Allegations: Venue is alleged to be proper in the Middle District of North Carolina because a substantial part of the events, including the development and offering of Plaintiff's accused software, occurred in the district, and because Defendant transacts substantial business in the state.
  • Core Dispute: Plaintiff USConnect, LLC seeks a declaratory judgment that its retail operating system does not infringe, and that it is not liable for infringing, eight U.S. patents owned by Defendant Cantaloupe, LLC, and further seeks a declaration that the patents are invalid.
  • Technical Context: The technology relates to the remote management, service scheduling, and data integration for unattended retail environments, such as vending machines and self-service kiosks.
  • Key Procedural History: The dispute arises in the context of a prior commercial relationship governed by a services agreement. The parties are currently in a pending arbitration where Defendant Cantaloupe attempted to assert the patent infringement claims at issue. The arbitrator denied Cantaloupe's request to add the patent claims to the arbitration, prompting Plaintiff USConnect to file this declaratory judgment action in federal court to resolve the controversy.

Case Timeline

Date Event
2005-03-31 Priority Date ('380, '588, '867, '705, '938, '158 Patents)
2011-02-22 '938 Patent Issues
2011-08-30 Priority Date ('280, '341 Patents)
2012-01-24 '380 Patent Issues
2012-11-13 '867 Patent Issues
2013-10-29 '705 Patent Issues
2013-11-12 '280 Patent Issues
2014-07-22 '341 Patent Issues
2016-03-15 '588 Patent Issues
2018-05-15 '158 Patent Issues
2020-07-15 Services Agreement executed between parties Compl. ¶11
2021-04-01 Cantaloupe, Inc. rebranding occurs (approximate date) Compl. ¶5
2026-05-08 Cantaloupe converts to an LLC (approximate date) Compl. ¶5
2026-08-06 Complaint for Declaratory Judgment filed Compl. p. 1

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

U.S. Patent No. 8,103,380 - "Remote management of vending machines"

  • Patent Identification: U.S. Patent No. 8,103,380, "Remote management of vending machines," issued January 24, 2012.

The Invention Explained

  • Problem Addressed: The patent addresses the inefficiency of managing vending machine systems where audit systems primarily retrieve and transmit data, which requires operators to physically visit machines to perform configuration adjustments, software updates, or hardware installations '380 Patent, col. 1:44-50
  • The Patented Solution: The invention provides a method and system where a central host remotely sends "control data" to an audit system within a vending machine '380 Patent, col. 2:1-5 This control data can either modify "data collection parameters" (such as alert conditions or reporting schedules) or consist of new executable code for the audit system, enabling remote configuration and updates '380 Patent, col. 2:5-13 '380 Patent, abstract
  • Technical Importance: The technology aimed to reduce operating expenses and minimize the need for skilled technicians to perform on-site service visits for routine configuration and software management tasks '380 Patent, col. 10:37-43

Key Claims at a Glance

  • The complaint seeks a declaratory judgment of non-infringement and invalidity as to all claims of the '380 Patent and does not identify specific claims Compl. ¶¶25-35 Independent claim 1 is representative of the patent's core method.
  • Independent Claim 1 recites a method with the following essential elements:
    • At a selected audit system, receiving control data from a remote management system, where the control data is a command to modify a data collection parameter.
    • In response, modifying the data collection parameter.
    • Using the audit system to collect data from a vending machine controller (VMC) according to the modified parameter.
    • Transmitting from the audit system an error detection code (checksum) representing a status of a "status code management list" to a host system to detect if an updated list is present.
    • Updating the status code management list in the host system if a mismatch is found.
      '380 Patent, col. 11:15-41
  • The complaint does not explicitly reserve the right to assert dependent claims, as it is a DJ action denying infringement of all claims.

U.S. Patent No. 8,311,867 - "Vending machine service scheduling taking into account hardness data indicating importance of minimizing the number of service visits to a vending machine and/or to the vending machine's location"

  • Patent Identification: U.S. Patent No. 8,311,867, "Vending machine service scheduling taking into account hardness data indicating importance of minimizing the number of service visits to a vending machine and/or to the vending machine's location," issued November 13, 2012.

The Invention Explained

  • Problem Addressed: The patent identifies that conventional vending machine service scheduling can be inefficient, as it may not be justifiable to service machines that do not meet standard selection rules, even if they are at a location that is already being visited '867 Patent, col. 2:4-9 This is especially true for locations that are difficult to access.
  • The Patented Solution: The invention introduces the concept of "hardness data," which indicates the importance of minimizing service visits to a particular machine or location '867 Patent, col. 2:15-20 The patented scheduling method uses this hardness data to determine whether to service additional, otherwise non-priority machines at a location, thereby optimizing service routes and reducing unnecessary travel '867 Patent, abstract '867 Patent, col. 11:12-21
  • Technical Importance: This approach provides a more sophisticated and economically efficient method for scheduling service routes compared to simple inventory-based prioritization.

Key Claims at a Glance

  • The complaint seeks a declaratory judgment of non-infringement and invalidity as to all claims of the '867 Patent Compl. ¶¶47-57 Independent claim 1 is representative.
  • Independent Claim 1 recites a method with the following essential elements:
    • Selecting vending machines for service according to "one or more first selection rules."
    • For a location with at least one selected machine (VM1) and one unselected machine (VM2), determining if "one or more second selection rules apply" to VM2.
    • The second selection rules take into account "hardness data" associated with the machine or its location, which is "indicative of at least one hardness factor h which indicates... hardness of reaching the vending machine's location."
    • The rule applies if the hardness data indicates the hardness factor is greater than a threshold.
    • Selecting the unselected machine (VM2) for service if the second selection rules apply.
      '867 Patent, col. 15:1-42
  • The complaint does not explicitly reserve the right to assert dependent claims.

Multi-Patent Capsule: U.S. Patent No. 9,286,588 - "Vending machine service scheduling"

  • Patent Identification: U.S. Patent No. 9,286,588, "Vending machine service scheduling," issued March 15, 2016 Compl. ¶17
  • Technology Synopsis: The complaint does not provide the patent text for analysis. Based on its title and family relationship to other asserted patents, it appears to concern methods for optimizing the scheduling of service visits to vending machines.
  • Asserted Claims: All claims are at issue Compl. ¶¶36-46
  • Accused Features: The complaint alleges that Plaintiff's "ConnectHQ" system does not practice the claimed invention Compl. ¶38

Multi-Patent Capsule: U.S. Patent No. 8,571,705 - "Vending machine service scheduling"

  • Patent Identification: U.S. Patent No. 8,571,705, "Vending machine service scheduling," issued October 29, 2013 Compl. ¶19
  • Technology Synopsis: This patent describes a method for generating a service schedule by dividing machines into "subroutes" and selecting subroutes and machines for service based on a calculated service priority, or "Points" '705 Patent, abstract '705 Patent, col. 1:55-2:4 The goal is to create more efficient service routes than simply servicing the most-needy machines, which may be geographically scattered.
  • Asserted Claims: All claims are at issue Compl. ¶¶58-68
  • Accused Features: The complaint alleges that Plaintiff's "ConnectHQ" system does not practice the claimed invention Compl. ¶60

Multi-Patent Capsule: U.S. Patent No. 7,894,938 - "Vending machine service scheduling"

  • Patent Identification: U.S. Patent No. 7,894,938, "Vending machine service scheduling," issued February 22, 2011 Compl. ¶20
  • Technology Synopsis: This patent, a parent to several others in the suit, discloses a method for scheduling vending machine service by organizing machines into "subroutes" '938 Patent, col. 1:55-63 A service schedule is generated by selecting a high-priority subroute and then selecting machines within it, with the option to select additional subroutes if time permits '938 Patent, abstract
  • Asserted Claims: All claims are at issue Compl. ¶¶69-79
  • Accused Features: The complaint alleges that Plaintiff's "ConnectHQ" system does not practice the claimed invention Compl. ¶71

Multi-Patent Capsule: U.S. Patent No. 8,788,341 - "Vending machine systems using standard inventory control system components"

  • Patent Identification: U.S. Patent No. 8,788,341, "Vending machine systems using standard inventory control system components," issued July 22, 2014 Compl. ¶21
  • Technology Synopsis: This patent describes a system using standard vending components to implement advanced features like promotional discounts, user-specific promotions, and problem reporting, all managed through a user interface on the machine '341 Patent, abstract '341 Patent, col. 5:4-13 It also discloses tracking and recording user interactions with these features for analysis.
  • Asserted Claims: All claims are at issue Compl. ¶¶80-89
  • Accused Features: The complaint alleges that Plaintiff's "ConnectHQ" system does not practice the claimed invention Compl. ¶82

Multi-Patent Capsule: U.S. Patent No. 8,583,280 - "Vending machine nutritional information display system using standard inventory control system components"

  • Patent Identification: U.S. Patent No. 8,583,280, "Vending machine nutritional information display system using standard inventory control system components," issued November 12, 2013 Compl. ¶22
  • Technology Synopsis: The patent describes a system where inventory data from a vending machine is transmitted to a management technology, merged with nutrition data from a separate data server, and the resulting merged data is sent back to the vending machine for display to consumers prior to purchase '280 Patent, abstract '280 Patent, col. 4:8-24
  • Asserted Claims: All claims are at issue Compl. ¶¶90-100
  • Accused Features: The complaint alleges that Plaintiff's "ConnectHQ" system does not practice the claimed invention Compl. ¶92

Multi-Patent Capsule: U.S. Patent No. 9,972,158 - "Method and device of automatically determining a planogram in vending"

  • Patent Identification: U.S. Patent No. 9,972,158, "Method and device of automatically determining a planogram in vending," issued May 15, 2018 Compl. ¶23
  • Technology Synopsis: The complaint does not provide the patent text for analysis. Based on its title, the patent appears to disclose a method for automatically identifying the layout of products (the "planogram") within a vending machine, likely using image processing or other sensor technology.
  • Asserted Claims: All claims are at issue Compl. ¶¶101-111
  • Accused Features: The complaint alleges that Plaintiff's "ConnectHQ" system does not practice the claimed invention Compl. ¶103

III. The Accused Instrumentality

  • Product Identification: The accused instrumentality is Plaintiff's "ConnectHQ" system Compl. ¶2
  • Functionality and Market Context:
    • The complaint describes "ConnectHQ" as a "comprehensive enterprise operating system that integrates accounting and operational aspects of an operator's business" in the convenience services industry Compl. ¶10
    • Plaintiff USConnect provides services to operators of micro markets, kiosks, and vending machines, which include "telemetry connectivity, inventory tracking, a national account sales program, advertising, data analytics and a proprietary loyalty/rewards program" Compl. ¶10
    • The complaint provides minimal specific technical detail about the "ConnectHQ" system's operation, focusing instead on categorical denials of infringement for each of the asserted patents Compl. ¶27 Compl. ¶38 Compl. ¶49 Compl. ¶60 Compl. ¶71 Compl. ¶82 Compl. ¶92 Compl. ¶103

No probative visual evidence provided in complaint.

IV. Analysis of Infringement Allegations

The complaint is for declaratory judgment and as such contains no affirmative infringement allegations or claim charts. The following tables outline the core elements of a representative independent claim for each lead patent and the corresponding functionality the "ConnectHQ" system would need to possess to form the basis of an infringement controversy.

  • '380 Patent Infringement Allegations
Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
at a selected one of the audit control systems, receiving control data from the remote management system... wherein the control data comprises a command to modify a data collection parameter... The complaint does not detail this functionality, but for an infringement controversy to exist, the "ConnectHQ" system would need to be capable of receiving commands from a central server to modify its operational parameters. ¶27 col. 11:20-27
transmitting by a selected one of the plurality of audit systems an error detection code comprising a checksum representing a status of a status code management list to a host system... The complaint does not detail this functionality. An infringing system would need to use a checksum-based method to communicate the version status of its internal code or data lists to a server. ¶27 col. 11:31-37
updating the status code management list with a status code management list in the host system when there is a mismatch... The complaint does not detail this functionality. An infringing system would need to receive and apply updates to its code or data lists from the host server upon detection of a version mismatch. ¶27 col. 11:38-41
  • '867 Patent Infringement Allegations
Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
selecting, by the system controlled by the circuitry, vending machines according to one or more first selection rules... The complaint does not detail this functionality. For an infringement controversy to exist, the "ConnectHQ" system would need to use a set of rules to generate a baseline service schedule. ¶49 col. 15:1-6
determining, by the system controlled by the circuitry, if one or more second selection rules apply to the vending machine VM2, each second selection rule... taking into account hardness data associated with the vending machine or the vending machine's location... The complaint does not detail this functionality. An infringing system would need to employ a secondary set of rules that considers a factor representing the difficulty of service for a given location or machine. ¶49 col. 15:12-25
selecting, by the system controlled by the circuitry, the vending machine VM2 for being serviced... if the one or more second selection rules apply... The complaint does not detail this functionality. An infringing system would need to add machines to a service schedule based on the outcome of the "hardness data" analysis. ¶49 col. 15:39-42
  • Identified Points of Contention:
    • Technical Questions ('380 Patent): A central question will be whether the "ConnectHQ" system, described as an "enterprise operating system" Compl. ¶10, uses the highly specific method of synchronizing a "status code management list" via a "checksum" as required by claim 1 of the '380 Patent. The analysis may focus on whether "ConnectHQ"'s general data synchronization and software update mechanisms are technically equivalent to this specific claimed process.
    • Scope Questions ('867 Patent): The dispute may turn on the definition of "hardness data." A key question will be whether any factors used by "ConnectHQ" to optimize "accounting and operational aspects" Compl. ¶10 fall within the patent's concept of "hardness," which is described in the context of minimizing physical service visits due to factors like travel difficulty ('867 Patent, col. 2:10-20).

V. Key Claim Terms for Construction

  • Term from the '380 Patent: "status code management list"

    • The Term: status code management list
    • Context and Importance: This term appears in independent claim 1 and is central to the claimed method of remote management and synchronization. The viability of an infringement claim may depend on whether any data list within the "ConnectHQ" system qualifies as a "status code management list" and whether it is managed using the specific checksum method recited in the claim.
    • Intrinsic Evidence for Interpretation:
      • Evidence for a Broader Interpretation: The patent does not provide an explicit definition of the term, which may support an argument that it should be given its plain and ordinary meaning, potentially covering any list of codes used to manage system status.
      • Evidence for a Narrower Interpretation: The specification provides specific examples of such lists, including an "Error Code Device Watch List" for filtering DEX file entries and "Error Code Translations" tables for interpreting them '380 Patent, FIGS. 4B-4C '380 Patent, col. 9:1-24 A party may argue that the term is limited to these specific types of lists used for parsing and translating machine error codes.

  • Term from the '867 Patent: "hardness data"

    • The Term: hardness data
    • Context and Importance: This term is the central inventive concept of the '867 Patent. The infringement analysis will likely focus on whether any data point or metric used by the "ConnectHQ" system to optimize operations constitutes "hardness data" as claimed.
    • Intrinsic Evidence for Interpretation:
      • Evidence for a Broader Interpretation: The patent functionally defines the term as data "which indicates the importance of minimizing the number of service visits to the location or a machine at the location" ('867 Patent, col. 2:15-18). This could support a broad construction covering any data used to reduce trips, such as traffic conditions, site access hours, or even business-related operational constraints.
      • Evidence for a Narrower Interpretation: The specification provides concrete examples of hardness, such as a location being "far from the nearest parking spot" or being hard to reach "due to heavy traffic" '867 Patent, col. 2:10-12 '867 Patent, col. 13:59-62 This may support an argument that the term is limited to factors concerning the physical difficulty and time required to travel to and access a machine.

VI. Other Allegations

  • Indirect Infringement: The complaint includes boilerplate denials of having contributed to or induced infringement of any of the asserted patents Compl. ¶27 Compl. ¶38 It does not provide any specific facts from Cantaloupe's underlying accusations that would form the basis for an indirect infringement claim.
  • Willful Infringement: The complaint makes no mention of willful infringement, as is typical for a declaratory judgment action seeking a declaration of non-infringement.

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

  • Definitional Scope: A core issue for several patents, particularly the '867 Patent, will be whether the general-purpose operational and accounting data used by the "ConnectHQ" system falls within the scope of more specific claim terms like "hardness data," which the patent describes in the physical context of optimizing service routes.
  • Technical Equivalence: For patents like the '380 Patent, the dispute may focus on a question of technical operation: does the accused "ConnectHQ" system perform the highly specific functions recited in the claims, such as using a checksum to manage a "status code management list," or does it achieve similar high-level goals (like remote management) using a fundamentally different and non-infringing technical method?
  • System-level Infringement: A central theme across the eight asserted patents is whether Plaintiff's modern, integrated "enterprise operating system" Compl. ¶10 can be shown to practice a collection of discrete features patented over more than a decade, or if the "ConnectHQ" system represents a distinct, non-infringing technological paradigm for managing unattended retail operations.
Loading Complaint