2:25-cv-00593
Damaka Inc v. Cisco Systems Inc
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Damaka, Inc. (Texas)
- Defendant: Cisco Systems, Inc. (Delaware)
- Plaintiff's Counsel: FABRICANT LLP
- Case Identification: 2:25-cv-00593, E.D. Tex., 09/08/2025
- Venue Allegations: Venue is alleged to be proper based on Defendant's regular and established places of business in the district, including a 162,000 square foot data center in Allen, Texas, and alleged acts of infringement within the district.
- Core Dispute: Plaintiff alleges that Defendant's Cisco Webex applications and Software Development Kits (SDKs) infringe six patents related to a software architecture for providing additional functionality to an existing application in an integrated manner.
- Technical Context: The technology concerns a method for adding features (e.g., audio/video calling) to a primary software application via an integrated "function block" (akin to an SDK) to avoid the performance degradation and negative user experience of switching between separate applications on a device.
- Key Procedural History: The filing is a First Amended Complaint, following an original complaint filed on May 30, 2025. The complaint also notes that Plaintiff and Defendant have had "business dealings in the past," which may be relevant to the allegations of pre-suit knowledge for willful infringement.
Case Timeline
| Date | Event |
|---|---|
| 2013-07-16 | Priority Date for all Patents-in-Suit |
| 2015-05-05 | U.S. Patent No. 9,027,032 Issues |
| 2016-02-23 | U.S. Patent No. 9,270,744 Issues |
| 2017-02-21 | U.S. Patent No. 9,578,092 Issues |
| 2019-01-01 | Alleged Infringement by Accused Products Begins (approx.) |
| 2023-02-07 | U.S. Patent No. 11,576,046 Issues |
| 2024-03-12 | U.S. Patent No. 11,930,362 Issues |
| 2025-04-15 | U.S. Patent No. 12,279,116 Issues |
| 2025-05-30 | Original Complaint Filed |
| 2025-09-08 | First Amended Complaint Filed |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 9,027,032 - "System And Method For Providing Additional Functionality To Existing Software In An Integrated Manner"
- Patent Identification: U.S. Patent No. 9027032 ("System And Method For Providing Additional Functionality To Existing Software In An Integrated Manner"), issued May 5, 2015. Compl. ¶7
The Invention Explained
- Problem Addressed: The patent's background describes the inefficiency and resource-intensive nature of "context switching" between separate applications on mobile devices, which can negatively impact performance, battery life, and user experience '032 Patent, col. 3:7-30
- The Patented Solution: The invention proposes a software architecture where a "function block" (e.g., a software developer's kit or SDK) is compiled or integrated directly into a primary "superblock" application '032 Patent, col. 4:60-67 This allows the superblock application to call upon new services (such as video or email) from the function block via an application programming interface (API) without leaving the primary application's user interface or switching to a separate program, thereby avoiding an OS-level context switch '032 Patent, abstract '032 Patent, col. 4:5-12 Figure 2B of the patent illustrates this concept by showing functionality from the function block being displayed within the superblock application's screen '032 Patent, Fig. 2B
- Technical Importance: This architectural approach allows for the creation of richer, more integrated applications on resource-constrained devices by avoiding the performance and user experience penalties associated with managing multiple, separate processes '032 Patent, col. 4:5-12
Key Claims at a Glance
- The complaint asserts at least independent claim 15 Compl. ¶23
- The essential elements of method claim 15 include:
- Receiving, by a function block stored in memory, a request for an audio/video (A/V) call from a superblock application also stored in memory.
- Determining, by the function block, that the superblock application is authorized to access the A/V call functionality.
- Determining, by the function block, that the A/V call requires access to a resource external to the mobile device.
- Establishing, by the function block, the A/V call between the superblock application and the external resource via a network interface, where such establishing is not supported by the superblock application.
- Providing, by the function block, video output for the A/V call to a video window that is displayed simultaneously with the display window of the superblock application.
- Providing, by the function block, audio for the A/V call via the mobile device.
- The complaint does not explicitly reserve the right to assert dependent claims for this patent, but makes a general prayer for relief covering one or more claims of the Patents-in-Suit Compl. p. 36
U.S. Patent No. 9,578,092 - "System And Method For Providing Additional Functionality To Existing Software In An Integrated Manner"
- Patent Identification: U.S. Patent No. 9578092 ("System And Method For Providing Additional Functionality To Existing Software In An Integrated Manner"), issued February 21, 2017. Compl. ¶8
The Invention Explained
- Problem Addressed: The '092 Patent, part of the same family as the '032 Patent, addresses the same problem of inefficient and disruptive context switching between applications on mobile and other computing devices '092 Patent, col. 3:7-30
- The Patented Solution: The solution is materially the same as in the '032 Patent: a "function block" is integrated into a "superblock" application, allowing new services to be provided via API calls without leaving the primary application's context '092 Patent, abstract '092 Patent, col. 4:5-12 The patent describes the function block as containing instructions to provide capabilities not otherwise possessed by the superblock application '092 Patent, col. 4:42-46
- Technical Importance: This architecture enables more seamless and efficient integration of diverse functionalities within a single application, which is particularly valuable for the user experience on mobile devices '092 Patent, col. 4:5-12
Key Claims at a Glance
- The complaint asserts at least independent claim 1 Compl. ¶36
- The essential elements of computer program product claim 1, directed to the operations of the function block, include:
- (a) receive from a superblock application a request for an audio/video (A/V) service;
- (ii) determine that the superblock application is authorized to access the A/V service functionality;
- (iii) determine that the A/V service requires access to a resource that is external to the data processing system;
- (iv) establish the A/V service between the superblock application and the resource via the network interface, wherein establishing is not otherwise supported by the superblock application;
- (v) provide video output for the A/V service to a video window within a display window, with the video window being displayable simultaneously with the superblock application's display window; and
- (vi) provide audio for the A/V service.
- The complaint does not explicitly reserve the right to assert dependent claims for this patent.
Multi-Patent Capsules
Patent Identification: U.S. Patent No. 9270744, "System And Method For Providing Additional Functionality To Existing Software In An Integrated Manner," issued February 23, 2016 Compl. ¶9
Technology Synopsis: The '744 Patent describes the same superblock/function block architecture. The invention aims to provide new communication services to a primary application by integrating a function block that can access external resources without forcing the user to switch to a different application, thereby preserving the application context.
Asserted Claims: At least independent claim 20 is asserted Compl. ¶51
Accused Features: The complaint alleges that the Cisco Webex App (as the superblock) and Webex SDK (as the function block) infringe by providing communication services that require external resources without switching application contexts Compl. ¶¶50-55
Patent Identification: U.S. Patent No. 11576046, "System And Method For Providing Additional Functionality To Existing Software In An Integrated Manner," issued February 7, 2023 Compl. ¶10
Technology Synopsis: The '046 Patent covers a method where a function block, accessible only to a specific superblock application, provides a service by accessing a network resource. The key innovation is providing this service, which is not natively supported by the superblock, without switching context to another application.
Asserted Claims: At least independent claim 11 is asserted Compl. ¶63
Accused Features: The accused features are the Webex App and its corresponding Webex SDK, which allegedly accesses Webex Cloud servers to provide A/V calls within the app without requiring an application switch Compl. ¶¶64-66
Patent Identification: U.S. Patent No. 11930362, "System And Method For Providing Additional Functionality To Existing Software In An Integrated Manner," issued March 12, 2024 Compl. ¶11
Technology Synopsis: The '362 Patent describes a method for enabling a real-time, end-to-end communication session between two users. It involves creating superblock applications for each user with a function block compiled therein, where the applications communicate with their respective function blocks via API calls to establish and render the session.
Asserted Claims: At least independent claim 1 is asserted Compl. ¶74
Accused Features: The accused feature is the Cisco Webex product, which is alleged to allow two users to communicate in real-time by using the Webex App and compiled-in SDK to initiate, notify, and render the communication session Compl. ¶¶75-81
Patent Identification: U.S. Patent No. 12279116, "System And Method For Providing Additional Functionality To Existing Software In An Integrated Manner," issued April 15, 2025 Compl. ¶12
Technology Synopsis: The '116 Patent describes a method centered on providing a function block that is specifically configured to be compiled into a third-party superblock application. The function block adds real-time communication functionality using one or more servers and interacts with the superblock via API calls.
Asserted Claims: At least independent claim 1 is asserted Compl. ¶89
Accused Features: The accused feature is the Cisco Webex SDK, which the complaint alleges is designed to be compiled into applications (like Webex or third-party apps) to provide real-time A/V sessions using Cisco's cloud servers, all managed through API calls Compl. ¶¶90-92
III. The Accused Instrumentality
Product Identification
The accused instrumentalities are, at a minimum, all versions and variants of the "Cisco Mobile and Web Application ('Webex,' 'Webex App(s),' or 'Webex Application(s)') including Webex SDKs" Compl. ¶15
Functionality and Market Context
- The complaint alleges that the Webex App acts as a "superblock application" and the Webex SDK acts as a corresponding "function block" Compl. ¶19 The function of the SDK is to provide audio/video (A/V) calling capabilities that can be integrated into an application Compl. ¶24 The complaint includes a screenshot from Cisco's developer documentation for the Webex iOS SDK that lists "Make and receive audio/video calls" as a feature Compl. p. 8
- The infringement theory is that the Webex App, using the Webex SDK, can initiate and conduct A/V calls by accessing external resources (e.g., Cisco's servers) without requiring the user to leave the Webex App and switch to a different application (Compl. ¶¶19; Compl. ¶55). The complaint provides a code snippet allegedly showing how an application would use the SDK to initiate a call with the command
webex.phone.dial(...)Compl. p. 12 - The complaint alleges Cisco is a "major telecom and technology company" Compl. ¶17, but does not provide further specific allegations regarding the market positioning of the Webex products.
IV. Analysis of Infringement Allegations
9,027,032 Infringement Allegations
| Claim Element (from Independent Claim 15) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| receiving, by a function block stored in the memory of a mobile device, a request for an audio/video (A/V) call from a superblock application stored in the memory... | The Webex iOS SDK (the alleged function block) provides a function that can be called by an application (the alleged superblock) to "Make and receive audio/video calls." | ¶24 | col. 15:30-34 |
| determining, by the function block, that the superblock application is authorized to access A/V call functionality provided by the function block | The Webex SDK allegedly performs a remote validation to authorize the user and application, as shown in a diagram of an authorization flow. | ¶25; ¶39 | col. 10:42-51 |
| determining, by the function block, that the A/V call requires access to a resource that is external to the mobile device | The Webex SDK requires access to a remote Cisco server to perform validation and establish the call. | ¶25; ¶40 | col. 5:35-45 |
| establishing, by the function block, the A/V call between the superblock application and the resource via a network interface, wherein such establishing is not supported by the superblock application | The Webex SDK is alleged to establish the A/V call over a network (e.g., 5G or internet) with a remote resource, a functionality not natively supported by the main application. | ¶26 | col. 5:46-6:5 |
| providing, by the function block, video output for the A/V call to a video window within a display window ... wherein the video window is displayed simultaneously... | The Webex SDK is alleged to create a video window within the window of the main application (Cisco's Webex), as depicted in a photograph of a mobile device during a video call. | ¶27 | col. 4:55-59 |
| providing, by the function block, audio for the A/V call via the mobile device | The Webex SDK offers the function to establish an A/V call via a mobile device. | ¶28 | col. 4:45-54 |
9,578,092 Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| a computer program product... instructions comprising a function block... operative... to: (a) receive from a superblock application a request for an audio/video (A/V) service | The Webex App (superblock) allegedly makes a request to the Webex SDK A/V service (function block). | ¶38 | col. 15:30-34 |
| (ii) determine that the superblock application is authorized to access the A/V service functionality | To use Webex SDK A/V resources, the user must allegedly be validated remotely as an authorized user, with the SDK validating the application. | ¶39 | col. 10:42-51 |
| (iii) determine that the A/V service requires access to a resource that is external to the data processing system | The Webex SDK allegedly requires authorization via an external Cisco server to function. The complaint includes an authorization flow diagram to support this. | ¶40 | col. 5:35-45 |
| (iv) establish the A/V service between the superblock application and the resource via the network interface, wherein establishing is not otherwise supported by the superblock application | The Webex SDK allows the Webex App to establish an A/V call with a resource over a network (e.g., 5G or internet), a service not natively supported by the app. | ¶41 | col. 5:46-6:5 |
| (v) provide video output for the A/V service to a video window within a display window... the video window being displayable simultaneously with the display window of the superblock application | The Webex SDK is alleged to create a video window that is displayable simultaneously with the display window of the Cisco Webex Application. | ¶42 | col. 4:55-59 |
| (vi) provide audio for the A/V service | The Webex SDKs provide for audio and video calls for the Webex App. | ¶43 | col. 4:45-54 |
Identified Points of Contention
- Scope Questions: The complaint's theory relies on mapping the patent terms "superblock application" and "function block" to the "Webex App" and "Webex SDK", respectively Compl. ¶19 A central question for the court will be whether the technical relationship between Cisco's products fits the specific architecture described and claimed in the patents. For instance, claim limitations requiring the function block to be "compiled into the superblock application" (e.g.,'116 Patent, claim 1) or that establishing a connection is "not supported by the superblock application" (e.g.,'032 Patent, claim 15) may be focal points of dispute over the scope and meaning of these architectural terms.
- Technical Questions: Several claims require the service to be performed "without switching context" (e.g.,'744 Patent, claim 20). The complaint alleges the Webex SDKs are embedded and do not require switching applications Compl. ¶55 The defense may raise the technical question of whether the operation of the Accused Products, even if seamless to a user, still constitutes a form of context switching at the operating system level that falls outside the patent's definition. The complaint's use of a diagram illustrating an "Authorization Code Flow" Compl. p. 9 to show a determination of authorization and access to an external resource may also be contested as to whether it technically meets the functional steps recited in the claims.
V. Key Claim Terms for Construction
The Term: "superblock application"
Context and Importance: This term is the foundation of the claimed architecture, representing the main application to which functionality is added. The infringement case hinges on whether the accused Webex App qualifies as a "superblock application" as the patents define it. Practitioners may focus on this term because its definition relative to the "function block" is central to the novelty of the claimed system.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The specification provides a general definition, stating a superblock "may be a set of executable instructions used to perform one or more functions" and "may be an application" '092 Patent, col. 3:1-5 This language could support a broad interpretation covering many types of software applications.
- Evidence for a Narrower Interpretation: The problem-solution narrative of the patent consistently frames the superblock as an application that lacks certain functionality, which is then provided by the function block '092 Patent, col. 3:45-54 This suggests a narrower definition where the "superblock" is defined in part by its functional deficiencies that the "function block" remedies.
The Term: "function block"
Context and Importance: This term defines the component that provides the additional, integrated functionality (allegedly, the Webex SDK). Its structural and functional relationship with the "superblock application" is a critical aspect of the infringement analysis.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The patent describes the function block as containing "instructions for providing the superblock 104 with one or more functions... that are not otherwise possessed by the superblock 104" '092 Patent, col. 4:42-46 This could be read broadly on any software library or module that adds features.
- Evidence for a Narrower Interpretation: The specification repeatedly states the function block "may be provided as a software developer's kit (SDK)" and is intended to be "compiled or otherwise included" in the superblock application '092 Patent, col. 4:60-67 This suggests a specific, tightly-coupled integration model, not merely any form of inter-process communication, which could support a narrower construction.
The Term: "without switching context"
Context and Importance: This term, appearing explicitly in asserted claim 20 of the '744 Patent, is central to the invention's stated goal of avoiding the inefficiencies of traditional multi-app workflows. The technical meaning of this phrase will be critical to determining if the Accused Products operate in an infringing manner.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: This could be interpreted from a user-experience perspective to mean any operation that does not visibly close the primary application and launch another.
- Evidence for a Narrower Interpretation: The patent's background explicitly contrasts the invention with the process where a device must "swap instructions into and out of physical memory" when a user "switches between applications" '092 Patent, col. 3:21-27 This suggests "without switching context" has a specific technical meaning tied to avoiding this OS-level memory management process and operating within the memory space of a single application, a concept visually supported by the timeline in Figure 4 of the patent showing concurrent instruction execution '092 Patent, Fig. 4
VI. Other Allegations
- Indirect Infringement: The complaint alleges inducement of infringement, stating that Cisco knowingly and intentionally encourages its customers and end-users to infringe by providing the Accused Products, particularly the Webex SDKs, along with "instructions, documentation, and other information" that suggest infringing use Compl. ¶¶29-30 Compl. ¶¶44-45 Contributory infringement is also alleged on the basis that the accused components are specially made for an infringing use and are not staple articles of commerce with substantial non-infringing uses Compl. ¶31 Compl. ¶46
- Willful Infringement: The complaint alleges willfulness based on both pre- and post-suit knowledge. Pre-suit knowledge is alleged based on Cisco's status as a major technology company that monitors patents, past "business dealings" between the parties, and a theory of willful blindness Compl. ¶17 Post-suit willfulness is alleged based on Cisco's knowledge of the patents "at least as of the May 30, 2025 filing of Damaka's original Complaint" Compl. ¶18
VII. Analyst's Conclusion: Key Questions for the Case
- A central issue will be one of architectural definition: does the technical relationship between the Cisco Webex App and the Webex SDK map to the patents' specific "superblock"/"function block" model, particularly the requirements that the function block is compiled into the superblock and provides functionality "not otherwise supported" by it?
- A key evidentiary question will be one of operational equivalence: does the accused system's method for providing A/V calls function "without switching context" as that term is defined by the patents, or can Cisco show that its system uses standard operating system-level processes that fall outside the claimed invention's specific architectural solution?
- A significant question for willfulness and potential damages enhancement will be the nature and timing of Cisco's knowledge: can Damaka establish that alleged pre-suit "business dealings" or general industry monitoring gave Cisco actual knowledge of the patents, or does potential liability for willful infringement only attach from the date Cisco was served with the original complaint?