Unwired Global Systems LLC v. SAP America Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Unwired Global Systems LLC (Delaware)
  • Defendant: SAP America, Inc. (Delaware)
  • Plaintiff's Counsel: Silverman, McDonald & Friedman
• Case Identification: 1:26-cv-00926, D. Del., 07/29/2026
• Venue Allegations: Venue is alleged to be proper in the District of Delaware because the Defendant is incorporated in Delaware, maintains an established place of business in the district, and has committed the alleged acts of infringement in the district.
• Core Dispute: Plaintiff alleges that Defendant's unspecified products infringe a patent related to a middleware interface for translating data between different network communication protocols.
• Technical Context: The technology addresses the challenge of interoperability in heterogeneous network environments, such as home automation, by using a universal middleware to abstract protocol-specific data into a standardized, platform-independent format.
• Key Procedural History: The complaint does not reference any prior litigation, inter partes review proceedings, or licensing history related to the patent-in-suit.

Case Timeline

Date	Event
2009-09-23	'624 Patent Priority Date
2010-09-22	'624 Patent Application Filing Date
2013-07-16	'624 Patent Issue Date
2026-07-29	Complaint Filing Date

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

• Patent Identification: U.S. Patent No. 8,488,624, "Method and apparatus for providing an area network middleware interface," issued July 16, 2013.

U.S. Patent No. 8,488,624 - "Method and apparatus for providing an area network middleware interface"

The Invention Explained

• Problem Addressed: The patent's background describes the difficulty of integrating various household devices (e.g., thermostats, security systems) into a single home area network (HAN) Compl. ¶9 '624 Patent, col. 1:19-29 Many of these devices use specialized, low-power communication protocols (like ZigBee or Bluetooth) that are incompatible with the common TCP/IP protocol used by personal computers and the internet, creating significant programming overhead for developers trying to create integrated control systems '624 Patent, col. 1:30-59
• The Patented Solution: The invention proposes a middleware system, centered on a "frame engine," that acts as a universal translator '624 Patent, col. 3:11-21 This engine receives a data packet in a "first communication protocol," uses a "machine-readable set of protocol frame definitions" (essentially a metadata map) to decode the packet's contents into a set of "platform independent data objects," and can then re-encode those universal objects for transmission in a "second communication protocol" '624 Patent, abstract '624 Patent, claim 1 This process, illustrated in Figure 1, abstracts away the specific protocol details, allowing a single application to interact with diverse devices through a standardized interface '624 Patent, Fig. 1 '624 Patent, col. 3:36-44
• Technical Importance: The described solution aims to reduce development complexity and enable interoperability in the growing field of device networking (e.g., Internet of Things) by creating a protocol-agnostic layer for applications '624 Patent, col. 1:56-62

Key Claims at a Glance

• The complaint alleges infringement of one or more claims without specifying them, but reserves the right to assert claims including those identified in its (unprovided) claim charts '624 Patent, claim 1 Compl. ¶11 Independent claim 1 is representative of the patented method.
• Independent Claim 1:
  • A method for implementing a network interface in a computer network performed by a special-purpose computer programmed by a frame engine comprising:
  • receiving one or more data packets encoded in a first communication protocol;
  • decoding the data packets into a set of data objects wherein the data packets are decoded in accordance with a machine-readable set of protocol frame definitions containing one or more sub-fields for parsing of the data packets; and
  • encoding the data objects into a second communication protocol wherein the data objects are encoded in accordance with the machine-readable set of protocol frame definitions.

III. The Accused Instrumentality

Product Identification

• The complaint does not identify any specific accused products by name. It refers generally to "Exemplary Defendant Products" that are identified in charts attached as Exhibit 2, which was not filed with the complaint Compl. ¶11 Compl. ¶16

Functionality and Market Context

• The complaint does not provide any description of the functionality or market context of the accused products. It alleges that the products "practice the technology claimed" and that their functionality is detailed in the unprovided Exhibit 2 Compl. ¶16 Compl. ¶17

IV. Analysis of Infringement Allegations

The complaint's infringement allegations are made entirely by reference to claim charts in an unprovided "Exhibit 2" Compl. ¶16 Compl. ¶17 The complaint contains no narrative description of how any specific feature of a Defendant product maps to the limitations of the asserted patent claims. Therefore, a claim chart summary cannot be constructed.

No probative visual evidence provided in complaint.

• Identified Points of Contention: Given the absence of specific infringement allegations, any litigation will first need to establish the basic facts of infringement. Key questions will likely include:
  • Evidentiary Question: What specific SAP products are accused of infringement, and what evidence will Plaintiff present to demonstrate that these products perform the steps of receiving, decoding, and encoding data packets as recited in the claims?
  • Architectural Question: Do the accused products utilize a middleware architecture that decodes data into an intermediate, "platform independent" format, or do they employ a different method of data translation that may not align with the specific steps of the asserted claims?
  • Scope Question: Does the functionality of the accused products fall within the scope of a "special-purpose computer programmed by a frame engine," as required by the preamble of claim 1 '624 Patent, claim 1?

V. Key Claim Terms for Construction

The construction of the following terms from independent claim 1 will likely be central to resolving the dispute.

• The Term: "frame engine"

• Context and Importance: This term defines the core software component that performs the claimed method. The scope of this term will be critical in determining whether the accused software architecture infringes. Practitioners may focus on whether this term is limited to the specific embodiments shown or covers any software that performs a similar translation function.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The patent describes the frame engine functionally as a component that "parses the data packets 126 and translates them into one or more platform independent data objects 119" and provides an Application Programming Interface (API) for accessing them '624 Patent, col. 3:11-13 '624 Patent, col. 3:40-44
  • Evidence for a Narrower Interpretation: The detailed description links the frame engine to specific operations, such as processing "nested blocks of data used by many communication protocols," using hierarchical naming conventions, and utilizing "decoder classes" for specific protocols like ZigBee, which could suggest a more limited scope '624 Patent, col. 3:50-54 '624 Patent, col. 4:62-67 '624 Patent, col. 5:27-32

• The Term: "machine-readable set of protocol frame definitions"

• Context and Importance: This term describes the data structure or metadata used to guide the decoding and encoding processes. Whether the accused system's configuration files or similar data structures meet this definition will be a key point of infringement analysis.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: Claim 1 itself provides a functional definition, stating the definitions contain "one or more sub-fields for parsing of the data packets" '624 Patent, claim 1 This could be argued to cover any file or data structure that provides parsing rules.
  • Evidence for a Narrower Interpretation: The specification provides specific examples of these definitions as XML files with particular tags and structure, and refers to them as "metadata maps" '624 Patent, col. 4:65-67 '624 Patent, col. 7:47-52 '624 Patent, col. 8:19-27 An argument could be made that the term is limited to such structured, declarative metadata configurations.

VI. Other Allegations

• Indirect Infringement: The complaint alleges induced infringement, stating that Defendant sells its products to customers and provides "product literature and website materials" that instruct them to use the products in an infringing manner Compl. ¶14 Compl. ¶15 The evidence for these materials is referenced as being in the unprovided Exhibit 2 Compl. ¶14
• Willful Infringement: The complaint asserts that service of the complaint itself provides Defendant with "actual knowledge" of the '624 Patent and its infringement Compl. ¶13 It alleges that Defendant's continued infringement despite this knowledge is willful, forming a basis for seeking enhanced damages for post-filing conduct Compl. ¶14 Compl. ¶4(D)

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

This case, as currently pled, will be defined by the information that is not yet present. The central questions for the court will be:

• An Evidentiary Question of Fact: What is the specific technology at issue? The primary and immediate question is which of Defendant's products are accused and what evidence Plaintiff will adduce to show that they perform the claimed method of protocol translation.
• A Definitional Question of Scope: How should the core components of the invention be defined? The case will likely turn on the construction of "frame engine" and "machine-readable set of protocol frame definitions" and whether these terms are broad enough to cover the architecture of Defendant's accused systems.
• A Technical Question of Equivalence: Assuming evidence is presented, does the accused system's method of data handling align with the patent's specific two-step "decode-then-encode" process using an intermediate "platform independent" object? A key point of contention may be whether the accused technology operates in a fundamentally different manner that falls outside the literal scope of the claims.