DCT

1:19-cv-02118

Visible Connections LLC v. Citrix Systems Inc

Key Events
Complaint
complaint

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 1:19-cv-02118, D. Del., 11/12/2019
  • Venue Allegations: Venue is alleged to be proper in the District of Delaware because both Defendants are Delaware corporations and are therefore deemed to reside in the district.
  • Core Dispute: Plaintiff alleges that Defendants’ GoToMeeting online conferencing and collaboration products infringe two patents related to associating telephone and data connections and to simplified application sharing interfaces.
  • Technical Context: The technology at issue addresses methods for integrating voice-based telephone conferencing with web-based data interactions to provide enhanced user control and collaboration features.
  • Key Procedural History: The complaint notes that in prior litigation involving the '392 Patent (Visible Connections, LLC v. Zoho Corporation), a motion to dismiss on patentable subject matter grounds was denied by the Western District of Texas. The complaint also details the corporate history of the accused product, explaining that LogMeIn acquired the GoToMeeting business from Citrix in a transaction that concluded around February 2017, which forms the basis for naming both entities as defendants.

Case Timeline

Date Event
1999-05-05 '392 Patent Priority Date
1999-07-27 '203 Patent Priority Date
2003-12-16 '392 Patent Issue Date
2007-10-16 '203 Patent Issue Date
2013-01-01 Alleged first date of infringement by Citrix's GoToMeeting
2017-02-01 LogMeIn acquires GoToMeeting business from Citrix
2019-11-12 Complaint Filing Date

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

U.S. Patent No. 6,665,392 - “Associating Data Connections With Conference Call Telephone” (Issued Dec. 16, 2003)

The Invention Explained

  • Problem Addressed: The patent describes prior art conferencing systems as requiring participants to pre-register with a unique, persistent ID to associate their telephone line with their data connection (e.g., a web browser) (Compl. ¶28; '392 Patent, col. 1:49-55). This approach was identified as cumbersome, creating barriers to access and preventing the identification of unregistered participants (Compl. ¶31; '392 Patent, col. 1:55-59).
  • The Patented Solution: The invention provides a method to dynamically link a user's telephone and data connections without pre-registration. The system generates a "unique temporary code" when a participant establishes a data connection to the conference system, displays this code on the participant's computer, and instructs the participant to enter the code via their telephone keypad to complete the association (Compl. ¶33; '392 Patent, col. 2:35-45). The complaint includes a flowchart from the patent, Figure 3, illustrating this process for a "web, then dial-in" scenario (Compl. p. 5, ¶21).
  • Technical Importance: This method sought to streamline conference entry by replacing static, pre-assigned user IDs with dynamically generated, single-use codes, thereby increasing flexibility for organizers and participants (Compl. ¶24).

Key Claims at a Glance

  • The complaint asserts independent claim 1 and dependent claim 5 (Compl. ¶¶36, 37).
  • Essential elements of independent claim 1 include:
    • A method for "operationally associating" a participant's telephone connection and data connection within a conference call system.
    • Generating a "unique temporary code" when the data connection is established.
    • Displaying the code to the participant on their computer screen via the data connection.
    • Instructing the participant to enter that code over their telephone connection.
  • The complaint reserves the right to assert other claims, as indicated in the prayer for relief (Compl. p. 26).

U.S. Patent No. 7,284,203 - “Method and Apparatus for Application Sharing Interface” (Issued Oct. 16, 2007)

The Invention Explained

  • Problem Addressed: The patent asserts that existing application sharing programs were complex, requiring users to have technical knowledge to configure them for conferencing (Compl. ¶46; '203 Patent, col. 1:39-42). Furthermore, these systems allegedly lacked robust status information, making it difficult for a host to know who was actively viewing a shared document or to assess audience size (Compl. ¶45).
  • The Patented Solution: The invention claims an "interface program" that simplifies application sharing into a two-step process: selecting one or more documents and selecting one or more participants (Compl. ¶49; '203 Patent, col. 1:64-2:7). This interface operates in cooperation with a "call manager" to automatically establish the sharing session and maintain status information, such as the current number of active participants (Compl. ¶48; '203 Patent, Abstract). The complaint references Figure 11F, which depicts a user interface displaying a list of active participants in a call (Compl. p. 17, ¶53).
  • Technical Importance: The invention aimed to make document-specific sharing more accessible to non-technical users and to provide hosts with better real-time information for managing a conference (Compl. ¶¶45, 47).

Key Claims at a Glance

  • The complaint asserts independent claim 34 and dependent claims 35 through 39 (Compl. ¶¶50, 88).
  • Essential elements of independent claim 34 include:
    • A system for application sharing comprising a "call manager" which has an "interface program."
    • A plurality of "communication devices" for communicating with the call manager.
    • The call manager is configured to "manage calls" to establish connectivity for sharing.
    • The interface program, in "cooperation with the call manager," is configured to "maintain status information" including the "current number of active participants."
  • The complaint reserves the right to assert other claims (Compl. p. 26).

III. The Accused Instrumentality

Product Identification

The complaint identifies the accused instrumentality as the "GoToMeeting" family of products, including versions made, used, and sold by Citrix and later by LogMeIn (Compl. ¶¶62, 67, 88).

Functionality and Market Context

  • GoToMeeting is described as an online meeting, video conferencing, and collaboration product that allows users to join meetings, deliver presentations, and share documents from various devices (Compl. ¶¶63, 64).
  • The complaint alleges that Citrix offered the product from at least 2013 until February 2017, at which point LogMeIn acquired the business and continued to offer the product (Compl. ¶¶55-60). The allegations cover product versions offered by both defendants in the six years preceding the complaint's filing (Compl. ¶62).

IV. Analysis of Infringement Allegations

'392 Patent Infringement Allegations

Claim Element (from Independent Claim 1) Alleged Infringing Functionality Complaint Citation Patent Citation
A method of operationally associating a participant's telephone connection to a conference call system with a data connection... GoToMeeting is alleged to operationally associate a user's telephone and computer connections when they join a conference. ¶69 col. 2:35-38
generating a unique temporary code when a data connection is established... The complaint alleges that upon a user joining a meeting from a computer, GoToMeeting generates an "audio PIN unique to the conference." ¶77 col. 2:38-41
displaying said code over said data connection to said participant on that participant's computer screen GoToMeeting allegedly "displays the Audio PIN to the participant over the participant’s computer screen." ¶80 col. 2:41-43
instructing said participant to enter said code over his telephone connection to the conference call system GoToMeeting is alleged to display dialing instructions and use voice prompts to instruct the participant to enter an Access Code and the Audio PIN via their telephone. ¶¶79, 81 col. 2:43-45
  • Identified Points of Contention:
    • Scope Questions: A central question may be whether GoToMeeting's alleged use of two identifiers—a meeting-specific "Access Code" and a participant-specific "Audio PIN" (Compl. ¶¶76, 78)—satisfies the claim limitation of "a unique temporary code." The defense may argue that the claim requires a single, unitary code, whereas the Plaintiff may argue the "Audio PIN" itself is the claimed code.
    • Technical Questions: The infringement read will depend on the precise sequence of operations in the accused product. The claim requires the code to be generated "when a data connection is established." The evidence presented will need to demonstrate that the generation of the "Audio PIN" in GoToMeeting aligns with this claimed timing.

'203 Patent Infringement Allegations

Claim Element (from Independent Claim 34) Alleged Infringing Functionality Complaint Citation Patent Citation
A system for application sharing, comprising: a call manager, the call manager having an interface program The complaint alleges that the "GoToMeeting downloadable software" functions as the claimed "call manager having an interface program." ¶91 col. 4:32-34
a plurality of communication devices for electrical communication with the call manager GoToMeeting is alleged to be used with a plurality of devices, such as computers, mobile phones, and tablets, that communicate with the system. ¶94 col. 4:26-29
the call manager configured to manage calls to and from the plurality of communication devices for establishing connectivity for the application sharing The GoToMeeting system is alleged to manage connections (both dial-in and VoIP) from user devices to facilitate document and application sharing. ¶95 col. 4:29-32
the interface program in cooperation with the call manager configured to maintain status information...including current number of active participants GoToMeeting is alleged to have an "Attendees" tab that lists the number and names of participants, thereby maintaining the claimed status information. The complaint provides an exemplary screenshot, Figure 11F, showing a participant list (Compl. p. 17). ¶¶53, 96 col. 4:32-37
  • Identified Points of Contention:
    • Scope Questions: A potential dispute may arise over the interpretation of "call manager" and "interface program." The defense may contend that the modern, integrated architecture of a cloud-based service like GoToMeeting does not contain the distinct structural components contemplated by the patent, which was filed in 1999.
    • Technical Questions: The claim requires the "interface program in cooperation with the call manager" to maintain status information. The infringement analysis may turn on whether the evidence shows this specific cooperative action or merely that the GoToMeeting system as a whole provides the information.

V. Key Claim Terms for Construction

For the '392 Patent

  • The Term: "unique temporary code" (Claim 1)
  • Context and Importance: This term is fundamental to the patent's proposed solution for dynamic association. Its construction will be critical in determining whether the accused product's use of a meeting-specific "Access Code" and a participant-specific "Audio PIN" falls within the claim's scope.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification discusses different types of codes, including a "PIN...unique to the specific conference" (col. 2:62-63) and a "temporary match code unique across all conferences" (col. 3:21-22), which could support an argument that the term is functional and not limited to a single structural form.
    • Evidence for a Narrower Interpretation: The claim phrasing "a unique temporary code" is singular. The patent's abstract and summary repeatedly refer to solving the association problem by generating and entering "the code" (singular), suggesting a single, self-contained identifier is what was invented and claimed ('392 Patent, Abstract; col. 2:38-45).

For the '203 Patent

  • The Term: "call manager" (Claim 34)
  • Context and Importance: This term defines a core architectural component of the claimed system. Whether the GoToMeeting software architecture includes a "call manager" as defined by the patent will be a key point of the infringement analysis.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent does not provide a rigid definition, describing the "call manager" functionally as managing calls to establish connectivity (col. 4:29-32). Plaintiff may argue this term should encompass any software module, regardless of its name, that performs this function in a distributed conferencing system.
    • Evidence for a Narrower Interpretation: The patent describes the "interface program in cooperation with the call manager," suggesting two distinct but interacting components ('203 Patent, col. 4:32-34). Figure 13 of the patent depicts a Call Manager 280 as a central component communicating with separate clients, which may support a narrower construction requiring a specific client-server architecture that may not map onto the accused product.

VI. Other Allegations

  • Indirect Infringement: The complaint does not plead specific counts for indirect or induced infringement, nor does it allege the requisite elements of knowledge and intent with specificity.
  • Willful Infringement: The complaint does not contain an explicit allegation of willful infringement. It requests a declaration that the case is "exceptional" for the purpose of recovering attorneys' fees under 35 U.S.C. § 285, but does not plead the facts typically required to support a claim for enhanced damages based on willfulness (Compl. p. 26).

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

  1. Definitional Scope vs. Technical Implementation ('392 Patent): A primary issue will be one of claim construction and mapping. Can the term "a unique temporary code" be construed to read on a system that allegedly uses a combination of a persistent meeting access code and a unique-per-participant PIN? The outcome will depend on whether the court views the term functionally or as requiring a specific, unitary structure.
  2. Architectural Equivalence ('203 Patent): The case raises a classic question of whether claim terms rooted in a late-1990s client-server paradigm ("call manager," "interface program") can be mapped onto a modern, integrated cloud-based service. The dispute will likely focus on whether the GoToMeeting architecture has components that correspond, either structurally or functionally, to the distinct elements required by the claims.
  3. Validity and the Prior Art Landscape: While the complaint highlights a successful defense against a patent eligibility challenge for the '392 Patent, the core validity dispute in this case may focus on novelty and non-obviousness. Given the crowded nature of the teleconferencing field, a key question for the court will be whether the specific combination of features recited in the claims was truly unconventional and non-obvious in light of the prior art at the time of the inventions.