DCT

1:26-cv-01044

EGLA Corp v. Stingray Group Inc

Key Events
Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 1:26-cv-01044, W.D. Tex., 04/22/2026
  • Venue Allegations: Venue is asserted against Mood Media LLC based on its residency and established place of business within the Western District of Texas. For Stingray Group Inc., a Canadian corporation, venue is premised on its status as a foreign defendant. For Stingray Music USA, Inc., venue is based on alleged acts of infringement in the district and a regular and established place of business derived from assets and operations acquired from Mood Media's former Austin-based business.
  • Core Dispute: Plaintiff alleges that Defendants' cloud-based multimedia streaming platforms infringe a patent related to the automated generation and delivery of media streams for television operators.
  • Technical Context: The technology concerns systems for delivering multimedia content from cloud-based sources to cable, satellite, and IPTV operators, replacing legacy hardware-intensive and satellite-dependent delivery methods with a more flexible, software-defined architecture.
  • Key Procedural History: The complaint details a complex business history, alleging that the patented technology, developed by Dr. Edwin Hernandez for a predecessor to Defendant Mood Media, was improperly accessed and incorporated by Defendant Stingray following its acquisition of Mood Media's DMX music division in 2014. The complaint also alleges that Plaintiff engaged in licensing discussions with Stingray between 2017 and 2019, during which it provided copies of parent patents from the same family as the patent-in-suit.

Case Timeline

Date Event
2012-03-01 Plaintiff EGLA CORP and DMX Music (later acquired by Mood Media) enter a Mutual Non-Disclosure Agreement.
2013-12-18 EGLA CORP and Mood Media sign a term sheet to license the inventor's platforms.
2014-03-01 Stingray acquires Mood Media's DMX music division.
2014-12-22 Priority date for U.S. Patent No. 12,075,116.
2015-03-31 Stingray had deployed the accused UbiquiCAST OSE2 platform no later than this date.
2017-09-15 EGLA CORP and Stingray enter a Mutual Non-Disclosure Agreement for licensing discussions.
2024-08-27 U.S. Patent No. 12,075,116 is issued.
2026-04-22 Complaint is filed.

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

  • Patent Identification: U.S. Patent No. 12,075,116, "Method, System and Apparatus for Multimedia Content Delivery to Cable TV and Satellite Operators," issued August 27, 2024.

The Invention Explained

  • Problem Addressed: The patent's background describes the challenges of delivering media to cable and satellite operators, which traditionally relied on dedicated hardware encoders, transcoding systems, and satellite infrastructure that were often inflexible and costly '116 Patent, col. 1:47-54
  • The Patented Solution: The invention proposes a system, centered around a "MediaPlug" device, that bridges cloud-based content sources with a cable operator's headend infrastructure '116 Patent, Fig. 1 This system can receive a request for a media stream, obtain source content from the internet (e.g., an audio file), and automatically generate a corresponding video component by rendering a webpage and capturing it as a series of images '116 Patent, col. 7:1-34 The resulting multimedia file is then formatted into a transport stream compatible with the operator's network and delivered for broadcast '116 Patent, abstract A key aspect is a "self-refreshing" workflow where the system detects changes to the source website and automatically updates the media stream Compl. ¶32 '116 Patent, cl. 1
  • Technical Importance: This approach provided a software-driven, cloud-based alternative that was more flexible and scalable than prior methods that relied on proprietary hardware and satellite feeds Compl. ¶27

Key Claims at a Glance

  • The complaint asserts independent claims 1 (a method) and 18 (a system) Compl. ¶61
  • The essential elements of independent claim 1 include:
    • Receiving a request for a media stream at a caching unit.
    • Obtaining content from the internet, which includes retrieving an audio file and generating a plurality of screen captures of a rendered webpage using a headless rendering engine.
    • Generating multimedia items by assembling a video component from the screen captures, combining it with the audio file, and saving the item at the caching unit.
    • Providing the media stream to a content provider by assembling it from the saved multimedia items.
    • Detecting a change at the source website corresponding to a saved multimedia item.
    • In response to the change, retrieving new screen captures and reassembling the item to create an updated multimedia item.
  • The complaint reserves the right to assert dependent claims 2 through 17 and 19 through 34 Compl. ¶62

III. The Accused Instrumentality

Product Identification

  • The complaint identifies two sets of accused instrumentalities: (1) Defendant Stingray's "UbiquiCAST OSE2" platform and related services; and (2) Defendant Mood Media's "Mood Harmony Platform," which includes its "Mood Visuals" offering, "Harmony CMS," and "ProFusion" line of media players Compl. ¶39 Compl. ¶45 Compl. ¶61

Functionality and Market Context

  • The complaint alleges that both platforms are cloud-based systems used to deliver streaming music and audio-visual channels to cable, IPTV, and other service providers Compl. ¶39 Compl. ¶45 Their functionality is alleged to include receiving requests for media, obtaining content from the internet, rendering webpages via a headless rendering engine to create video components, assembling and providing media streams for multicasting, and automatically updating content in response to detected changes at the source Compl. ¶41 Compl. ¶46
  • The complaint points to internal project management records, such as JIRA and Trello boards, as evidence of the UbiquiCAST OSE2 platform's technical architecture, alleging they document components like a "StillPict" caching system and FFMPEG-based encoding Compl. ¶42

IV. Analysis of Infringement Allegations

'116 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
receiving, at the caching unit, a request from the at least one multicasting server for at least one media stream for playback on a broadcast media channel... The accused platforms receive requests at a caching unit from one or more multicasting servers for a media stream for playback. ¶41a col. 7:51-54
obtaining, at the caching unit, content from the internet corresponding to a plurality of multimedia items from at least one website... The accused platforms obtain content from the internet corresponding to a plurality of multimedia items. ¶41b col. 7:62-65
retrieving, for each multimedia item... at least one audio file corresponding to an audio component and a plurality of screen captures corresponding to a video component... The accused platforms retrieve, for each multimedia item, an audio file and a plurality of screen captures. ¶41c col. 7:1-9
rendering a webpage by a browser... and generating a plurality of screen captures of the rendered web page using a headless rendering engine... The accused platforms render a webpage using a browser and generate screen captures of the webpage using a headless rendering engine. ¶41d col. 7:25-29
generating, at the caching unit, the plurality of multimedia items... by assembling a video component from the plurality of screen captures, combining the screen captures and the audio file... and saving the multimedia item at the caching unit... The accused platforms generate multimedia items at a caching unit by assembling a video component from screen captures, combining them with an audio file, and saving the result. ¶41e col. 8:10-21
providing at least one media stream to a content provider for multicasting on a broadcast media channel, including by assembling the media stream... using the plurality of multimedia items saved at the caching unit... The accused platforms provide a media stream for multicasting by assembling it from the saved multimedia items. ¶41f col. 8:21-25
detecting a change at the websites corresponding to the multimedia items saved at the caching unit... The accused platforms detect changes at the source websites corresponding to the saved multimedia items. ¶41g col. 9:7-12
in response to detecting a change, retrieves new screen captures and reassembles the multimedia item using the new screen captures, thereby creating an updated multimedia item. In response to a detected change, the accused platforms retrieve new screen captures and reassemble the multimedia item, creating an updated version. ¶41h col. 15:25-31

Identified Points of Contention

  • Scope Questions: The complaint alleges that the claimed "caching unit" reads on both centralized cloud components and "locally-cached content on the Harmony media players themselves" Compl. ¶46 This raises the question of whether the patent's description of the caching unit as a central storage and processing component '116 Patent, col. 5:5-14 can be construed to cover such a distributed architecture.
  • Technical Questions: Claim 1 requires "detecting a change at the... website." The complaint alleges this function is performed Compl. ¶41g but does not specify the technical mechanism. The patent specification mentions using the "rsync" protocol for file synchronization '116 Patent, col. 9:7-12 An issue for the court may be whether the detection method used in the accused products aligns with the method contemplated by the patent.

V. Key Claim Terms for Construction

The Term: "headless rendering engine"

  • Context and Importance: This term is critical for the claimed process of automatically generating video from web content. Infringement will depend on whether the accused systems utilize a component that meets this definition. Practitioners may focus on this term because it connects the abstract web content to a concrete video stream.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The claim language itself is functional. A party could argue it covers any software component that renders web content into a non-GUI format (e.g., an image file) without requiring a visible display.
    • Evidence for a Narrower Interpretation: The specification provides examples, including "PhantomJS (Webkit-based headless engine for rendering images) or QtCapture, or simply capturing screen frame buffers" '116 Patent, col. 7:25-29 A party could argue the term should be limited to these specific technologies or those with functionally identical characteristics.

The Term: "detecting a change at the at least one website"

  • Context and Importance: This limitation is central to the "self-refreshing" workflow that the complaint highlights as a key inventive concept Compl. ¶32 The outcome of the infringement analysis may depend on the construed scope of this functional step.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The claim language is not specific as to the method of detection. A party may argue that it covers any means of determining that source content has been altered, including API calls, periodic re-crawling, or even manual update triggers.
    • Evidence for a Narrower Interpretation: The specification discloses using the "rsync" protocol to "synchronize multimedia files that are newly updated" '116 Patent, col. 9:7-12 A party may argue this disclosure limits the scope of "detecting a change" to file-level synchronization, as opposed to detecting dynamic content changes within a webpage itself.

VI. Other Allegations

Indirect Infringement

  • The complaint alleges induced infringement, asserting that Defendants provide instructions, documentation, and technical support that direct their customers and end users to use the accused platforms in a manner that infringes the '116 Patent Compl. ¶65 Contributory infringement is also alleged on the basis that the accused systems are especially made for this use and are not staple articles of commerce Compl. ¶66

Willful Infringement

  • The willfulness allegation is based on alleged pre-suit knowledge of the patented technology. The complaint alleges that Stingray gained knowledge as early as January 2014 through its hiring of former Mood Media executives who had worked directly with the inventor, and again through direct licensing negotiations with the Plaintiff from 2017 to 2019 Compl. ¶67 Mood Media's knowledge is alleged to stem from its direct contractual relationship and work with the inventor beginning in 2012 Compl. ¶67 The complaint asserts that Defendants continued to infringe after the patent issued, despite this knowledge Compl. ¶67

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

  • A central issue will be one of architectural mapping: can the patent's "caching unit," described as a core component for storage and media processing, be construed to cover the allegedly distributed architecture of the accused products, which includes caching capabilities both in the cloud and on local, end-user media players?
  • A key evidentiary question will concern the scope of the "self-refreshing" function: does the claimed step of "detecting a change at the at least one website" require a specific method of automated content monitoring, or can it be read more broadly to encompass the file synchronization or other update mechanisms that discovery may reveal are used by the Defendants?
  • A third pivotal issue relates to knowledge and intent: what evidence will support the allegation that knowledge of the inventor's pre-patent technology, allegedly possessed by executives who moved between the defendant companies, translates to pre-suit knowledge of the specific subject matter claimed in the subsequently issued '116 Patent, sufficient to support a finding of willfulness?
Loading Complaint