DCT

2:23-cv-00522

Snap One v. Ava

Log In
Key Events
Amended Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 2:23-cv-00522, D. Utah, 04/18/2024
  • Venue Allegations: Venue is alleged to be proper in the District of Utah because a substantial part of the events giving rise to the claims occurred there, defendants allegedly committed acts of patent infringement in the district, and defendant AVA has its principal place of business in the district. The complaint also cites a forum selection clause in a prior agreement between Plaintiff and defendant Josh.ai.
  • Core Dispute: Plaintiff alleges that Defendants' smart home remote controls and related automation products infringe five patents, misappropriate trade secrets, and violate prior contractual agreements, leveraging intellectual property developed by or acquired by Plaintiff.
  • Technical Context: The lawsuit concerns the high-end custom smart home installation market, where integrated remote controls and voice command systems manage a wide array of household electronics and automation systems.
  • Key Procedural History: Plaintiff Snap One acquired NEEO AG, the original developer of the "Neeo Remote," in 2019. Defendant AVA was subsequently co-founded by former NEEO and Snap One employees. The complaint alleges that prior to the lawsuit, Snap One sent a demand letter to AVA in March 2022 regarding trademark usage and intellectual property infringement. A separate Software Development Kit (SDK) agreement from 2017 and a Distributor Agreement from 2021 are alleged to exist between Snap One and Josh.ai, forming the basis for breach of contract claims. This filing is a First Amended Complaint.

Case Timeline

Date Event
2006-10-06 Priority Date for '338 Patent
2007-06-18 Priority Date for '623 Patent
2008-07-22 Priority Date for '137 Patent
2010-08-04 Priority Date for '237 Patent
2011-02-08 '338 Patent Issued
2013-02-12 '137 Patent Issued
2015-01-01 Neeo Remote first announced for presale (approx.)
2015-09-01 '237 Patent Issued
2017-04-03 Snap One and Josh.ai enter SDK Agreement
2018-07-13 Priority Date for '426 Patent
2019-02-01 Snap One acquires NEEO AG
2019-11-01 Snap One releases upgraded Neeo Remote (approx.)
2020-09-30 Mr. Oberholzer (NEEO founder) terminates employment with Snap One
2020-12-29 '623 Patent Issued
2021-03-31 Consultancy Agreement with Mr. Oberholzer's company terminates
2021-08-01 Snap One and Josh.ai enter Distributor Agreement (approx.)
2021-10-05 '426 Patent Issued
2022-03-01 Snap One sends demand letter to AVA (approx.)
2022-09-01 Josh.ai and AVA form partnership (approx. "fall of 2022")
2023-06-27 Josh.ai announces the "Josh Remote"
2023-07-14 Snap One sends letter to Josh.ai regarding alleged SDK violation
2023-10-01 AVA introduces AVA Cinema Remote and AVA Nano Brain (approx.)
2024-04-18 First Amended Complaint Filed

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

U.S. Patent No. 10,877,623 - "Dynamic interface for remote control of a home automation network"

  • Patent Identification: U.S. Patent No. 10,877,623, issued December 29, 2020 Compl. ¶156

The Invention Explained

  • Problem Addressed: The patent describes the challenge of controlling a complex home automation network, where a remote control with limited memory and display size must manage a large number of devices and functions without overwhelming the user with complex menus or buttons '623 Patent, col. 1:21-47
  • The Patented Solution: The invention proposes a system where the remote control does not store the entire menu structure locally Compl. ¶160 Instead, it communicates with a central automation controller and dynamically receives small "database extracts" representing only the necessary menu items as the user navigates the interface '623 Patent, abstract '623 Patent, col. 4:1-20 This allows for a fluid, context-sensitive user interface on a resource-constrained remote device.
  • Technical Importance: This method enables the creation of sophisticated, yet simple-to-use, smart remotes with smaller memory footprints, which can reduce hardware costs and improve performance in the home automation market Compl. ¶160

Key Claims at a Glance

  • The complaint asserts at least independent claim 24 Compl. ¶165
  • Independent Claim 24 of the '623 Patent requires:
    • A remote control for a home automation network.
    • A display device.
    • A transceiver for wireless communication with an automation controller.
    • Memory and a processor.
    • The processor is configured to:
      • Present a first menu item from the automation controller.
      • In response to a first user input (e.g., scrolling), present a second menu item.
      • In response to a second user input (e.g., selecting), communicate with the controller to control a home automation device (e.g., lighting, audio/visual equipment, or climate control).

U.S. Patent No. 8,375,137 - "System and method for streaming audio using a send queue"

  • Patent Identification: U.S. Patent No. 8,375,137, issued February 12, 2013 Compl. ¶185

The Invention Explained

  • Problem Addressed: The patent addresses latency and interruptions in streaming audio, particularly the initial delay (lag) a user experiences between requesting a media stream and when playback actually begins '137 Patent, col. 1:21-44
  • The Patented Solution: The invention uses a "send queue" on the media server that pre-stores a defined length of the audio stream '137 Patent, abstract Upon an "activation event" from a client device (e.g., a user pressing play), the server can immediately transfer multiple frames from this queue in a single packet to instantly fill the client's local buffer, thus minimizing startup delay Compl. ¶189 '137 Patent, col. 5:49-65
  • Technical Importance: This technique creates a more responsive, "instant-on" user experience for media streaming, which is a critical factor for perceived quality and user satisfaction in multi-room audio systems Compl. ¶189

Key Claims at a Glance

  • The complaint asserts at least independent claim 1 Compl. ¶194
  • Independent Claim 1 of the '137 Patent requires:
    • A streaming media system for initial presentation.
    • A media server that sends media packets at periodic intervals.
    • A framer to divide the media stream into packets.
    • A media client to receive the packets.
    • A "send queue" in the server that stores a defined length of programming.
    • The send queue must be able to "immediately fill a client's user buffer when an activation event occurs by transferring multiple frames in a single packet."

Multi-Patent Capsules

  • U.S. Patent No. 11,140,426

    • Patent Identification: 11,140,426, "Streaming media multiplexing with a media proxy," issued October 5, 2021 Compl. ¶213
    • Technology Synopsis: The patent describes a method for managing multi-device communication, such as an intercom system. It allows a calling device to use a media multiplexer and proxy to initiate a broadcast to several "callee" devices and subsequently switch to an exclusive, one-to-one communication with a single device that responds '426 Patent, abstract Compl. ¶217
    • Asserted Claims: At least claim 1 Compl. ¶222
    • Accused Features: The "Josh User Communication Features," specifically the intercom functionality in Josh.ai products like the Josh Core, Josh Nano, and Josh Micro, which allegedly enable two-way communication between devices in a home Compl. ¶¶219, 223-224

  • U.S. Patent No. 7,886,338

    • Patent Identification: 7,886,338, "System and method for controlling access to local services without losing failover capibilty [sic]," issued February 8, 2011 Compl. ¶240
    • Technology Synopsis: The patent discloses a method for ensuring a networked device remains functional even if it loses connection with its central controller. It teaches putting a device into a restricted state and using a timer procedure to allow it to change state (e.g., become fully operational) without permission from the controller after a predetermined time, providing "failover capability" '338 Patent, abstract Compl. ¶244
    • Asserted Claims: At least claim 1 Compl. ¶249
    • Accused Features: The Josh Control Devices (e.g., Josh Core), which allegedly can be put into a specific state (e.g., "volume control state") and use timer procedures to switch back to a regular operational mode Compl. ¶¶246, 251

  • U.S. Patent No. 9,123,237

    • Patent Identification: 9,123,237, "Controlling a remote electronic device in a control state," issued September 1, 2015 Compl. ¶266
    • Technology Synopsis: The patent describes an electronic device entering a special low-power "control state" that is distinct from "power-on" or "power-off." While in this state, the device can still generate and transmit control messages to other remote devices without performing its own main function, thereby saving power while retaining control capabilities '237 Patent, abstract Compl. ¶270
    • Asserted Claims: At least claim 1 Compl. ¶275
    • Accused Features: The "sleep mode" of the Josh Micro device, where it allegedly enters a state waiting to be "woken" and, while not performing its main voice recognition function, can continue to send control messages to other devices Compl. ¶277

III. The Accused Instrumentality

Product Identification

The complaint collectively defines the "Infringing Remotes" as the AVA Home Remote, the Josh Remote, and the AVA Cinema Remote Compl. ¶10, fn. 1 Additional accused products include the AVA Nano Brain, AVA Streamer, and Josh.ai's Josh Core, Josh Micro, and Josh Nano devices Compl. ¶¶99-100

Functionality and Market Context

The accused remotes are presented as high-end controllers for the custom installation industry, featuring touchscreens and physical buttons for managing integrated smart home systems (Compl. ¶¶2-3, 36). The complaint alleges that the AVA and Josh remotes are "strikingly similar" to Snap One's own Neeo Remote, which it acquired in 2019 (Compl. ¶52). A side-by-side comparison image in the complaint shows the physical resemblance between the Neeo Remote and the AVA Home Remote Compl. p. 2 The AVA Streamer is identified as a system for multi-room audio streaming (Compl. ¶190), while the various Josh.ai devices provide voice control and intercom functionality (Compl. ¶¶30, 218). The partnership between AVA and Josh.ai is alleged to enable the AVA remotes to run Josh.ai's software, thereby gaining unauthorized interoperability with Plaintiff's Control4 platform (Compl. ¶¶6, 73).

IV. Analysis of Infringement Allegations

10,877,623 Patent Infringement Allegations

Claim Element (from Independent Claim 24) Alleged Infringing Functionality Complaint Citation Patent Citation
a remote control for a home automation network, comprising: a display device that is configured to present menu items to a user of the remote control, wherein the menu items can be used with an automation controller; The accused AVA and Josh remotes include a display that presents menus to the user for controlling a home automation system (Compl. ¶167). A screenshot in the complaint depicts the AVA remote's user interface displaying control options (Compl. p. 41). ¶167 col. 4:1-20
a transceiver for wirelessly communicating with the automation controller; The accused remotes are integrated with a home automation network and communicate with a controller to manage various devices (Compl. ¶¶161, 168). ¶168 col. 7:1-4
a processor... configured to: present, on the display device, a first menu item from the automation controller; in response to a first user input, present, on the display device, a second menu item from the automation controller, wherein the second menu item is different from the first menu item; The remote's processor allegedly displays different menu items as the user scrolls or navigates through the interface (Compl. ¶160, Compl. ¶168). ¶168 col. 5:1-13
and in response to a second user input to the remote control, communicate with the automation controller to control one of the group consisting of: a lighting dimmer, a lighting switch, audio/visual equipment, and climate control. Upon user selection, the remote sends control messages to the automation controller to operate devices such as lighting, AV equipment, and climate control (Compl. ¶169). ¶169 col. 6:15-22

8,375,137 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
A streaming media system configured to prepare the streaming media for initial presentation, comprising: a media server...; a media client... The accused "AVA System" comprises the AVA Streamer (acting as the media server) and integrated speakers (acting as media clients) to stream audio (Compl. ¶¶195-196). An image from AVA's website illustrates this multiroom capability (Compl. p. 49). ¶¶195-196 col. 2:30-40
a framer located with the media server to divide frames of the media stream into media packets; The complaint alleges, on information and belief, that the AVA Streamer contains a framer that divides the audio stream into packets for transmission (Compl. ¶197). ¶197 col. 5:12-14
a send queue in the server, the send queue being configured to store a defined length of programming from the media stream, wherein the send queue can immediately fill a client's user buffer when an activation event occurs by transferring multiple frames in a single packet. The complaint alleges, on information and belief, that the AVA Streamer uses a send queue to transfer multiple frames in a single packet to fill the speaker's buffer upon an activation event, enabling a fast start to playback (Compl. ¶198). ¶198 col. 5:49-65

Identified Points of Contention

  • '623 Patent: The infringement analysis for the '623 patent may focus on the term "from the automation controller." A central question is whether the accused remotes dynamically receive and present menu data served by the controller in real-time, as detailed in the patent's specification, or if they merely display a locally stored menu that sends commands to the controller. The complaint alleges dynamic configuration Compl. ¶160, but the evidence required to prove this specific operational method will be a key point of discovery.
  • '137 Patent: The allegations mapping to the "framer" and "send queue" limitations are made "on information and belief" (Compl. ¶¶197-198). A significant technical question will be whether the AVA Streamer's architecture actually includes a component that performs the specific function of a "send queue" as claimed-namely, storing a defined program length and filling a client buffer via a multi-frame, single-packet transfer upon an activation event. Proving this specific mechanism without internal product documentation presents an evidentiary challenge.

V. Key Claim Terms for Construction

For the '623 Patent

  • The Term: "present... a menu item from the automation controller" (from Claim 24)
  • Context and Importance: The case may turn on whether this phrase requires the menu content itself to be actively and dynamically served by the controller, or if it can be read more broadly to cover a remote that simply displays a pre-loaded menu used to issue commands to the controller. Practitioners may focus on this term because it goes to the heart of the patent's purported novelty over conventional remotes.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The plain language of the claim itself does not explicitly require a "dynamic" or "just-in-time" transfer of menu data. One could argue that any menu item whose selection results in a command to the controller is functionally "from the automation controller."
    • Evidence for a Narrower Interpretation: The patent's abstract and detailed description repeatedly emphasize the concept of the controller sending "database extracts" to the remote "in response to menu navigation by the user" to overcome the remote's memory limitations '623 Patent, abstract '623 Patent, col. 4:1-20 This context suggests the term implies a specific client-server relationship for menu generation, not just command execution.

For the '137 Patent

  • The Term: "send queue" (from Claim 1)
  • Context and Importance: The existence and function of a "send queue" is the core technical element of claim 1. The infringement question will depend entirely on whether the AVA Streamer has a component that meets the definition of this term.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: A defendant might argue that any server-side buffer that holds data before transmission qualifies as a "send queue," attempting to broaden the term to cover conventional streaming architectures.
    • Evidence for a Narrower Interpretation: The claim itself provides a functional definition: it must be able to "store a defined length of programming" and "immediately fill a client's user buffer when an activation event occurs by transferring multiple frames in a single packet" '137 Patent, cl. 1 The specification further describes this as a way to "startup quickly without waiting for a series of packets to be sent through the normal clocking cycles" '137 Patent, col. 5:60-64, suggesting the term is limited to a component specifically designed for fast-start functionality, not a generic transmit buffer.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges induced infringement for all asserted patents, stating that Defendants encourage and instruct customers on the infringing uses of the accused products through marketing, advertising, and user documentation Compl. ¶¶172, 200, 227, 253, 279
  • Willful Infringement: Willfulness is alleged for all asserted patents. The complaint claims Defendants had pre-suit knowledge based on the employment history of AVA's founders, who previously worked at Snap One and its predecessor NEEO and were allegedly aware of the relevant intellectual property Compl. ¶¶96-98 The complaint also asserts that Defendants had actual knowledge of the patents at least as of the filing of the lawsuit and continued their infringing activities, constituting willful infringement Compl. ¶¶181-182, 209-210, 236-237, 262-263, 288-289

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

This dispute appears to center on more than just patent claims, with significant allegations of trade secret theft and breach of contract tied to the shared history of the parties' founders. From a patent perspective, the case will likely turn on the following key questions:

  • A core issue will be one of technical implementation: did the defendants, allegedly leveraging proprietary knowledge from their time at Snap One, replicate the specific and nuanced software architectures claimed in the patents (e.g., the dynamic menu-generation of the '623 patent and the "send queue" of the '137 patent), or did they develop products that achieve a similar external appearance and user experience through technically distinct, non-infringing methods?
  • A second key question will be one of evidentiary proof: can the plaintiff substantiate its technical allegations, many of which are made "on information and belief," through discovery? The outcome may depend heavily on whether internal documents and source code from the defendants validate the complaint's theories about how the accused products function internally.
  • Finally, the case presents a question of claim scope versus specification: will the court construe the asserted claims broadly based on their plain language, or will it tether the scope of the claims to the specific problems and solutions described in the patent specifications? This determination will be critical in deciding whether the accused products, even if functionally similar, are legally infringing.
Loading Amended Complaint