Atomic IP LLC v. Paessler GmbH

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Atomic IP LLC (Texas)
  • Defendant: Paessler GmbH (Germany)
  • Plaintiff's Counsel: Findlay Craft, P.C.; Bradford Black P.C.
• Case Identification: 2:26-cv-00507, E.D. Tex., 06/25/2026
• Venue Allegations: Venue is alleged to be proper because the defendant is a foreign entity, and specific personal jurisdiction is asserted based on the defendant's purposeful activities directed at Texas, including offering and selling the accused products within the state.
• Core Dispute: Plaintiff alleges that Defendant's PRTG network monitoring products, which provide customizable web-based dashboards, infringe a patent related to the server-side generation and delivery of customizable display widgets.
• Technical Context: The technology at issue involves systems for creating and delivering dynamic, data-driven visual elements (widgets or dashboards) to a user's web browser from a server, reducing the need for specialized client-side software.
• Key Procedural History: The complaint alleges that Plaintiff provided Defendant with notice of infringement via correspondence on March 18, 2026, which may serve as the basis for a subsequent claim of willful infringement.

Case Timeline

Date	Event
2005-08-12	'869 Patent Priority Date
2006-08-14	'869 Patent Application Date
2014-12-30	'869 Patent Issue Date
2026-03-18	Plaintiff sends notice letter to Defendant
2026-05-20	Date of last update for a blog post cited in the complaint
2026-06-25	Complaint Filing Date

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

U.S. Patent No. 8,924,869 - "Service for Generation of Customizable Display Widgets"

• Issued: December 30, 2014

The Invention Explained

• Problem Addressed: The patent background describes a societal shift towards image-based communication, where purely text-based or numerical data presentation has "diminished impact and effectiveness." '869 Patent, col. 1:43-49 It identifies a need for systems that can present the increasing volume of available data in a "visually compelling manner." '869 Patent, col. 1:55-63
• The Patented Solution: The invention describes a server-based system that generates and delivers customizable visual elements, termed "widgets," to a client device without requiring installation of specialized software on that device '869 Patent, abstract '869 Patent, col. 4:30-39 The system stores defining data for a visual element, which includes a base image, other image components, user-defined alphanumeric data, and real-time data '869 Patent, col. 2:7-12 Upon a client request, a server-side "generation module" generates the visual element based on this data and transmits it to the client for display, often within a web browser '869 Patent, col. 2:12-18 '869 Patent, Fig. 4A
• Technical Importance: The described server-side approach was intended to provide a reliable and compatible method for distributing dynamic, data-driven visual content across a wide range of browser-capable devices, avoiding platform-specific client installations '869 Patent, col. 3:15-23

Key Claims at a Glance

• The complaint asserts independent claim 1 and dependent claims 2 and 25 '869 Patent, col. 15:20-16:53 Compl. ¶31
• Independent Claim 1 requires a system comprising:
  • A data storage system for storing "visual element defining data," which itself comprises image data (base and other components), alphanumeric data, and real-time data.
  • A "client definition interface" for receiving user selections of the defining data.
  • A "generation module" to generate the visual element based on the user-selected data.
  • A "network interface module" to receive client requests and transmit the generated visual element.
• The complaint reserves the right to assert other claims of the '869 Patent.

III. The Accused Instrumentality

Product Identification

• The complaint identifies the "Accused Instrumentality" as PRTG Network Monitor, PRTG Enterprise Monitor, PRTG Hosted Monitor, PRTG Maps, Map Designer, and related map/dashboard functionality Compl. ¶18

Functionality and Market Context

• The Accused Instrumentality is described as a web-based system that allows users to create, configure, and publish customizable "maps" and dashboards for visualizing network monitoring data Compl. ¶19 Users can define these dashboards by adding background images, static and dynamic objects (e.g., sensor status icons, graphs), custom HTML, and text Compl. ¶19 The system renders and delivers these visualizations through a web interface, displaying "live data overviews" that update based on real-time network conditions Compl. ¶19 Compl. ¶23 The complaint alleges these dashboards are delivered for display in standard web browsers and can be shared via URLs or embedded in other webpages using iframes Compl. ¶26

IV. Analysis of Infringement Allegations

'869 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
a system for defining and delivering a user modifiable visual element... comprising: a data storage system for storing visual element defining data... the data comprising: image data having a base image component and other image components; alphanumeric data representing information to be conveyed in the defined visual elements; and real-time data indicative of current conditions	The PRTG platform allegedly includes a data storage system that stores maps, dashboards, background images, map objects, and configuration data (Compl. ¶20). This data allegedly includes: (i) background images (base) and other components like device icons and graphs (Compl. ¶21); (ii) user-defined map names and custom HTML/text (Compl. ¶22); and (iii) live monitoring data reflecting current network status Compl. ¶23 The complaint provides a screenshot of a server rack visualization, which shows status icons overlaid on a background image of a server rack. Compl. p. 11	¶¶20-23	col. 2:7-12
a client definition interface configured to receive input from a client computing device indicative of a user selection of at least some of the image data, the user-defined data, and the real-time data to be associated with a visual element	The complaint identifies Paessler's "Map Designer" as the client definition interface Compl. ¶24 This browser-based interface allegedly allows users to create a map, select background images, select monitored objects from a "Device Tree," and configure how static and dynamic objects are displayed with live data Compl. ¶24 The complaint includes a screenshot titled "Map Designer General Layout" showing a user interface with a device tree, a central design area, and a properties panel. Compl. p. 15	¶24	col. 16:1-6
a generation module configured to generate the visual element based on the user-selected visual element defining data	Paessler's "View Map" and "Get HTML" functions are alleged to be the generation module Compl. ¶25 This functionality allegedly renders a configured map-including the selected background, map objects, and live sensor data-based on the user's definitions and provides links or iframe code for its delivery Compl. ¶25	¶25	col. 16:7-9
a network interface module configured to receive requests from client computing devices relating to the generated visual element and, in response, transmit the requested view containing the generated visual element to the requesting client computing device	The PRTG platform allegedly uses a network interface to receive requests and deliver the generated maps and dashboards to client browsers via a web interface, unique URLs, public links, and iframe code Compl. ¶26 The complaint provides a screenshot of the "Get HTML" interface showing options to share a map via a direct link or an iframe. Compl. p. 19	¶26	col. 16:10-16

• Identified Points of Contention:
  • Scope Questions: The patent's specification and figures describe and depict "widgets" as discrete components like clocks, to-do lists, and RSS feeds '869 Patent, Fig. 6 A potential point of contention is whether the term "visual element," or "widget" as used in the patent, can be construed to encompass the more complex, integrated "maps" and "dashboards" of the accused PRTG platform.
  • Technical Questions: The patent describes a server-side process of "(re)generating image data" and sending that "image data" to the client '869 Patent, col. 6:40-46 The complaint alleges the accused system "generates or renders" the visual elements Compl. ¶25 A key technical question may be whether the accused system's method of providing updated data to the browser for rendering constitutes "generating the visual element" on the server as required by the claim, or if there is a fundamental difference in the technical mechanism (e.g., server-side image file generation vs. client-side rendering of structured data).

V. Key Claim Terms for Construction

• The Term: "widget" / "visual element"

  • Context and Importance: The applicability of the patent hinges on whether the accused "maps" and "dashboards" fall within the scope of these terms. Practitioners may focus on this term because the defendant could argue that its complex, enterprise-grade dashboards are technically and conceptually distinct from the "small desktop application[s]" and simple components exemplified in the patent's specification '869 Patent, col. 4:49-51
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent provides a general definition of a "widget" as "an interface component with which a computer user interacts in a graphical user interface" '869 Patent, col. 4:47-49 Claim 1 uses the even broader term "visual element," which the plaintiff may argue covers any user-modifiable visual component in a GUI.
    • Evidence for a Narrower Interpretation: The specification's examples in Figure 6 primarily show simple, single-purpose components like a clock, a to-do list, and a package tracker '869 Patent, Fig. 6 A defendant may argue that these specific embodiments limit the term to similar discrete, modular components, rather than a comprehensive, integrated dashboard.

• The Term: "generation module configured to generate the visual element"

  • Context and Importance: The interpretation of "generate" is central to determining whether the accused system's technical implementation infringes. The dispute may turn on what the server creates and sends: a finished image, or structured data for the client to render.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The plaintiff may argue that "generate the visual element" refers to the entire server-side process of assembling the components-images, text, real-time values, and layout information-that collectively define the final visual output, regardless of where the final rendering occurs. The flowchart in Figure 4A shows a process of receiving a request, retrieving data, and then generating and sending "image data," which could be interpreted broadly '869 Patent, Fig. 4A
    • Evidence for a Narrower Interpretation: The patent repeatedly refers to generating "image data" based on various inputs and sending that "image data" to the client '869 Patent, col. 6:35-46 A defendant could argue this language, particularly "send image data to requesting process or device," implies the creation and transmission of a complete image file from the server, as opposed to sending structured data (like JSON or XML) that a client-side script then uses to draw the visual element.

VI. Other Allegations

• Indirect Infringement: The complaint alleges active inducement under 35 U.S.C. § 271(b), stating that Paessler publishes documentation, user guides, tutorials, and videos that instruct customers on how to use the accused features in an infringing manner Compl. ¶32 Compl. ¶34 The complaint alleges Paessler intended for users to perform these infringing acts Compl. ¶34
• Willful Infringement: The basis for the willfulness allegation is Paessler's alleged continued infringement after receiving notice of the '869 Patent on March 18, 2026 Compl. ¶33 Compl. ¶36 The complaint alleges this continued conduct demonstrates "at least reckless disregard of Atomic's patent rights" Compl. ¶35

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

This case will likely revolve around two central questions, one related to definitional scope and the other to the technical mechanism of infringement:

1. A question of definitional scope: Can the terms "visual element" and "widget," as defined and exemplified in the context of the '869 Patent with its focus on simple, discrete components, be construed to read on the complex, integrated network monitoring "maps" and "dashboards" offered by the accused PRTG platform?

2. A question of technical operation: Does the accused system's process of delivering live data to a web browser for rendering satisfy the claim limitation of a server-side "generation module configured to generate the visual element," or will the court determine that the patent requires a more specific server-side creation of a final image file, creating a potential mismatch with the accused product's architecture?