Atomic IP LLC v. Fortinet Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Atomic IP LLC (Texas)
  • Defendant: Fortinet, Inc. (Delaware)
  • Plaintiff's Counsel: Findlay Craft, P.C.
• Case Identification: 2:26-cv-00435, E.D. Tex., 05/27/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Eastern District of Texas because Defendant maintains a regular and established place of business in the district and has allegedly committed acts of infringement there.
• Core Dispute: Plaintiff alleges that Defendant's FortiAIOps network management platform and related services infringe a patent directed to a server-side system for generating and delivering customizable display widgets to a browser interface.
• Technical Context: The technology relates to generating dynamic, data-driven visual elements (widgets) on a server and delivering them for display in a user's web browser, a foundational technology for modern web-based dashboards and graphical user interfaces.
• Key Procedural History: The complaint alleges that Plaintiff sent correspondence to Defendant on May 7, 2026, identifying the patent-in-suit and notifying Defendant of its alleged infringement. This pre-suit notice is asserted as a basis for willful infringement.

Case Timeline

Date	Event
2005-08-12	U.S. Patent No. 8,924,869 Priority Date
2006-08-14	U.S. Patent No. 8,924,869 Application Filing Date
2014-12-30	U.S. Patent No. 8,924,869 Issue Date
2026-05-07	Plaintiff allegedly sent notice of infringement to Defendant
2026-05-27	Complaint Filing Date

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

• Patent Identification: U.S. Patent No. 8,924,869 ("Service for Generation of Customizable Display Widgets"), issued December 30, 2014. Compl. ¶6

The Invention Explained

• Problem Addressed: The patent describes a need for systems that can present an increasing amount of data in a "visually compelling manner" to an "image-focused society," as traditional text-based information is becoming less effective. '869 Patent, col. 1:21-65
• The Patented Solution: The invention is a server-based system for creating and delivering customizable visual elements, or "widgets," to a user's computing device. The system stores different types of data (image data, user-defined data, real-time data) on a server, uses a "generation module" to combine them into a visual element, and then sends this element to the client's browser in response to a request. '869 Patent, abstract '869 Patent, col. 2:4-17 A key aspect is that this is accomplished "without requiring any installation of specialized software on the user's computer," enabling cross-platform compatibility through a standard web browser. '869 Patent, col. 4:31-34
• Technical Importance: This server-side approach was designed to improve the distribution, compatibility, and reliability of dynamic user interface elements by centralizing the generation logic and avoiding the complexities of client-side software installation. Compl. ¶13

Key Claims at a Glance

• The complaint asserts independent claim 1 and dependent claims 2 and 25. Compl. ¶30
• Independent claim 1 of the '869 Patent recites a system with the following essential elements:
  • A data storage system configured to store "visual element defining data," which includes image data, user-defined data, and real-time data.
  • A "client definition interface" that receives user input selecting which data to associate with a visual element.
  • A "generation module" that generates the visual element based on the user-selected data.
  • A "network interface module" that receives requests from and sends the generated visual element to the client.
  • The system is "operative to define and deliver" the visual element to the client device "independent of the operating system of the client computing device."
• The complaint does not explicitly reserve the right to assert other claims.

III. The Accused Instrumentality

Product Identification

• The complaint identifies the accused instrumentality as the "Fortinet Accused Platform," which includes FortiAIOps and related functionalities like Wi-Fi Maps, Map Management, RF Planner, Heat Maps, and browser-delivered dashboards. Compl. ¶17

Functionality and Market Context

• The Accused Instrumentality is a web-based platform for managing and visualizing wireless networks. Compl. ¶18 The complaint alleges that users access the platform through a standard web browser to create custom "Wi-Fi Maps." Compl. ¶7 Compl. ¶18 This involves uploading a graphic map of a floor plan (a base image), adding and positioning icons representing network access points (APs), and viewing real-time network status and performance data (e.g., throughput, signal strength) as overlays or heat maps on the floor plan. Compl. ¶¶18-22 The complaint alleges these features allow users to define, generate, and view dynamic visualizations based on a combination of stored images, user configurations, and live network data. Compl. ¶23 A screenshot from Fortinet's documentation shows the "Service Assurance" dashboard, which presents various network metrics in discrete components that the complaint characterizes as widgets. Compl. ¶27 Compl. p. 31

IV. Analysis of Infringement Allegations

'869 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
a data storage system... configured to store visual element defining data... the data comprising: image data... user-defined data... and real-time data...	The FortiAIOps system allegedly stores configuration data including: uploaded floor-map images ('.jpg', '.png'); user-defined data like AP names and locations; and real-time data like AP status, throughput, and other wireless metrics.	¶19; ¶20; ¶21; ¶22	col. 2:5-11
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 the visual element	The platform's workflow allegedly allows users to define a visual element by uploading a floor-map image, entering names for sites and floors, placing AP icons, and selecting which statistics (e.g., throughput, signal strength) to display as a heat map.	¶23	col. 15:30-38
a generation module configured to generate the visual element based on the user-selected visual element defining data	Fortinet's RF Planner and Heat Maps features are alleged to be generation modules. For example, the RF Planner generates a heat map of predicted signal strength based on user placement of APs, and the Heat Maps feature generates an updated visualization based on the user's selection of a floor, RF band, and refresh command. A screenshot depicts the RF Planner generating a heat map based on user-placed APs. (Compl. p. 24).	¶24	col. 2:12-14
a network interface module configured to receive requests from the client computing device related to the generated visual element, and send the generated visual element that is responsive to the request	The FortiAIOps application portal is allegedly accessed via a web browser using an HTTPS URL. This interface receives user requests for map views and dashboards and transmits the requested visualizations back to the client's browser for display.	¶25	col. 2:15-17
wherein the system is operative to define and deliver to the client computing device independent of the operating system of the client computing device making the requests	The complaint alleges that users access the FortiAIOps platform through standard web browsers (e.g., Chrome, Firefox, Safari) without installing a separate application, making the delivery independent of the client's specific operating system.	¶26	col. 15:42-47

• Identified Points of Contention:
  • Scope Questions: A potential issue is whether the complex network visualization tools of FortiAIOps constitute a "widget service" as contemplated by the patent. The patent's examples focus on simpler, discrete elements like clocks, to-do lists, and package trackers '869 Patent, Fig. 6, raising the question of whether the patent's scope extends to integrated, enterprise-grade network management dashboards.
  • Technical Questions: The meaning of "generate the visual element" will likely be a central technical dispute. The complaint alleges that applying a data overlay (like a heat map) to a user-uploaded background image constitutes "generation." Compl. ¶24 The defense may argue this is merely a data filtering or display function, and that "generation" requires a more fundamental composition of a new image from distinct components (e.g., a base image and sub-images), as described in the patent specification. '869 Patent, col. 5:1-9

V. Key Claim Terms for Construction

• The Term: "widget"

• Context and Importance: This term's construction is critical because it determines whether the accused maps and dashboard components fall within the patent's subject matter. The complaint alleges the visual components in the FortiAIOps dashboard are "widgets." Compl. ¶27

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The specification provides a broad definition: "a widget is an interface component with which a computer user interacts in a graphical user interface." '869 Patent, col. 4:45-48
  • Evidence for a Narrower Interpretation: The patent's figures and detailed examples primarily show small, discrete, and often standalone applications like a clock, a to-do list, and an RSS feed reader. '869 Patent, Fig. 6 A court could find these embodiments suggest a narrower meaning than a large, integrated dashboard for network management.

• The Term: "generate the visual element based on the user-selected visual element defining data"

• Context and Importance: The interpretation of "generate" is central to the infringement analysis. The dispute will likely focus on whether the accused system's act of creating a heat map overlay or placing data points on a map is the same as the "generation" process claimed.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The flowchart in Figure 4A shows a process of receiving a request, retrieving data, "(re)generating" image data based on the received data, and sending it to the client. '869 Patent, Fig. 4A This could be argued to cover any server-side process that creates an updated view.
  • Evidence for a Narrower Interpretation: The specification describes generating a "dynamically generated widget image" by combining a "base image component" and "sub-images... along with real-time data and/or other user-specified alphanumeric data." '869 Patent, col. 5:1-9 This language may support an argument that "generation" requires more than simply applying a data-driven color overlay to a static background image.

VI. Other Allegations

• Indirect Infringement: The complaint alleges active inducement of infringement, stating that Fortinet provides documentation, user guides, and tutorials that instruct customers and end-users on how to use the allegedly infringing features of the Accused Instrumentality. Compl. ¶33
• Willful Infringement: The complaint alleges willful infringement based on Fortinet's alleged continued infringement after receiving a notice letter from Atomic on May 7, 2026, which allegedly identified the '869 Patent. Compl. ¶32 Compl. ¶34

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

• A core issue will be one of definitional scope: Can the term "widget," which the patent illustrates with discrete consumer-level applications like clocks and to-do lists, be construed to cover the integrated, professional-grade network maps and dashboard visualizations within the FortiAIOps enterprise platform?
• A key evidentiary question will be one of technical operation: Does the accused platform's functionality-such as applying a heat-map overlay to a user-uploaded floor plan based on real-time network data-perform the specific step of "generating" a visual element as claimed, or does the patent require a more fundamental server-side composition of distinct image components that is technically different from the accused method?
• The case may also turn on the interpretation of the "client definition interface": Does a user's action of placing AP icons on a map and selecting a data view (e.g., "throughput") constitute the "user selection of... visual element defining data" for the purpose of generation, or is it merely interaction with a pre-configured application that does not rise to the level of defining a new visual element as claimed?