throbber
Case 2:17-cv-00517-JRG Document 81 Filed 09/17/18 Page 1 of 9 PageID #: 1054
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`
`AGIS SOFTWARE DEVELOPMENT,
`LLC,
`
`
`
`
`
`ZTE CORPORATION, ZTE (USA) INC.,
`AND ZTE (TX), INC.,
`
`
`
`
`Plaintiff,
`
`
`
`v.
`
`
`
`Defendants.
`
`
`
`
`
`
`Case No. 2:17-CV-00517-JRG
`
`
`
`
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`
`
`DEFENDANTS’ OPPOSED MOTION TO SUPPLEMENT THE RECORD IN
`SUPPORT OF MOTION TO DISMISS FOR IMPROPER VENUE,
`OR IN THE ALTERNATIVE, TO TRANSFER
`
`
`
`
`
`
`

`

`Case 2:17-cv-00517-JRG Document 81 Filed 09/17/18 Page 2 of 9 PageID #: 1055
`
`Defendants ZTE (USA) Inc. and ZTE (TX), Inc. (“ZTA” and “ZTX,” respectively and
`
`collectively, “ZTE”) 1 respectfully submit this opposed motion to supplement the record in
`
`support of their pending Motion to Dismiss for Improper Venue or, in the alternative, Motion to
`
`Transfer to the Northern District of California (the “Motion to Transfer Venue”). Dkt. 38.
`
`I.
`
`BACKGROUND
`
`On November 21, 2017, ZTE moved to transfer the above-captioned action filed by
`
`AGIS Software Development LLC (“Plaintiff” or “AGIS”) to the Northern District of California.
`
`See Dkt. 38. In support of a change in venue, Defendants submitted evidence that the core of the
`
`accused applications in this case is provided by third-party Google LLC (“Google”), and the
`
`relevant witnesses and information about those functionalities are located in and around Northern
`
`California. See Dkt. 38 at 24; see also Dkt. 51 at 8-10. ZTE submitted declarations from Google
`
`witnesses establishing that, for the accused functionality for Google Maps for Mobile application
`
`(“GMM”) and Google’s Find My Device (formerly known as Android Device Manager), the
`
`relevant source code and other information regarding these applications is confidential and
`
`proprietary, and that those documents and relevant Google witnesses are located in the Northern
`
`District of California. Dkt. 51-4 ¶¶ 2-3 and 51-5 ¶¶ 2-3. AGIS itself confirmed that these were
`
`the core accused applications for the case when it served its Disclosure of Asserted Claims and
`
`Infringement Contentions on January 19, 2018. 514 Dkt. 27, Ex. 1.
`
`At the time of briefing for the Motion to Transfer Venue, AGIS dismissed the relevance,
`
`location and convenience of non-party Google, arguing that “much of that information
`
`
`1 Defendant ZTE Corporation has not yet been served or appeared, and thus the Motion to
`Dismiss for Improper Venue or in the Alternative to Transfer is on behalf of ZTX and ZTA only.
`
`
`2
`
`
`
`

`

`Case 2:17-cv-00517-JRG Document 81 Filed 09/17/18 Page 3 of 9 PageID #: 1056
`
`[concerning the accused functionality related to Google’s Android Operating System] is publicly
`
`available through either open source code or public application programming interfaces (‘API’).”
`
`Dkt. 46 at 2, 24. In fact, AGIS explicitly disputed Google’s possible role as a non-party” and
`
`took the position that any discovery into Google’s confidential and proprietary source code and
`
`other information for GMM and Find My Device is irrelevant to the claims asserted against the
`
`Android defendants, such as ZTE.2 Dkt. 46 at 25. Plaintiff further argued that:
`
`• “To the extent Google witnesses may have relevant information--which AGIS believes
`they do not have--Defendants’ suggestion that relevant Google witnesses are located in
`California is mere speculation.” Dkt. 46 at 7.
`• “Defendants’ statements that . . . third-party employees with relevant knowledge, including
`Google witnesses, are located in or near California, without more, is insufficient.” Dkt. 52
`at 7.
`• “As discussed above, the relevance of the listed [Google witnesses] is doubtful.” Dkt. 46
`at 26.
`• “Google’s possible role as a non-party in this case--the extent of which is disputed by
`AGIS--should not be a determining factor to transfer venue of a case.” Dkt. 46 at 25.
`• “Although AGIS has accused functionality related to Google’s Android Operating System,
`AGIS expects to submit infringement contentions that do not invoke Local Patent Rule 3-
`1(g), and that they rely only on publicly-available open source code or public APIs.” Dkt.
`46 at 24.
`• “As for Google, to date, AGIS has not relied on any confidential Google code in its
`infringement contentions, but rather, relied upon publicly available source code.” Dkt. 52
`at 8.
`• “The Northern District of California is not appreciably closer to the sources of proof than
`the Eastern District of Texas.” Dkt. 46 at 25.3
`
`New evidence has recently emerged confirming Defendants’ argument that the location
`
`and convenience of non-party Google weighs in favor of transfer to the Northern District of
`
`
`2 AGIS asserts the same claims against all Android Defendants LG Electronics, Inc. (“LGEKR”),
`Huawei Device USA Inc. et al. (“Huawei”), HTC Corporation (“HTC”), and ZTE in the two
`consolidated cases (Case No. 17-cv-513 (Huawei) and Case No. 17-cv-514 (LGEKR, HTC, and
`ZTE).
`
` As of August 14, 2018, AGIS has offered its own source code for inspection outside the Eastern
`District of Texas, specifically in New York City, New York. Alternatively, since May 23, 2018,
`source code from ZTE has been available for inspection in California.
`3
`
` 3
`
`
`
`

`

`Case 2:17-cv-00517-JRG Document 81 Filed 09/17/18 Page 4 of 9 PageID #: 1057
`
`California. On August 23, 2018 and August 29, 2018, AGIS served deposition and document
`
`subpoenas on Google in both of the consolidated cases against Android Defendants, AGIS
`
`Software Development LLC v. Huawei Device USA Inc., et al., No. 2:17-cv-513-JRG (E.D. Tex.)
`
`and AGIS Software Development LLC v. HTC Corp., No. 2:17-cv-514-JRG (E.D. Tex.). See
`
`Notice of Subpoenas to Google LLC attached as Exhibit A.
`
`AGIS’s subpoena undermines the credibility of its previous efforts to discount the
`
`relevance of Google’s witnesses, source code and other information to this action.
`
`Notwithstanding AGIS’s representations that AGIS’s infringement contentions rely only on
`
`“publicly available open source code or public APIs,” Dkt. 46 at 24 and Dkt. 52 at 8, AGIS’s
`
`subpoenas seek the confidential and proprietary source code for Google Maps and Find My
`
`Device. AGIS also seeks from Google other technical documents that show the operation,
`
`design, development, functionality, features, testing, and manufacture of Google Maps and Find
`
`My Device. Furthermore, AGIS also seeks the communication protocols used with Android
`
`Applications between one or more Google Servers and/or one or more other Android Devices
`
`and the source code for Google Servers.
`
`Indeed, the subpoenas confirm that the key sources of evidence regarding the operation,
`
`design, and function of the applications identified in AGIS’s Infringement Contentions reside
`
`with Google in and around the Northern District of California. Because Google’s documents and
`
`witness testimony helps resolve critical issues regarding the accused applications, ZTE
`
`respectfully submit that AGIS’s service of the subpoenas on Google confirms the
`
`appropriateness of transferring the present litigation to the Northern District of California
`
`pursuant to 28 U.S.C. § 1404(a).
`
`
`
`4
`
`

`

`Case 2:17-cv-00517-JRG Document 81 Filed 09/17/18 Page 5 of 9 PageID #: 1058
`
`II.
`
`ARGUMENT
`
`When resolving a challenge to the propriety of venue, this Court enjoys broad discretion
`
`to allow the moving party to supplement the record with additional facts and evidence. See, e.g.,
`
`Murungi v. Touro Infirmary, No. 6:11-cv-0411, 2011 WL 3206859, at *2 (W.D. La. June 29,
`
`2011) (noting the broad discretion to consider supplemental evidence when ruling on a motion to
`
`transfer venue); accord Ambraco, Inc. v. Bossclip B.V., 570 F.3d 233, 238 (5th Cir. 2009) (noting
`
`the Court’s broad discretion to consider supplemental evidence when ruling on a Rule 12(b)(1)
`
`or 12(b)(3) motion). Exercise of such discretion is appropriate when new information emerges
`
`that can assist the Court’s consideration of the transfer motion. See, e.g., Nationwide Mutual Ins.
`
`Co. v. The Overlook, LLC, No. 4:10-cv-00069, 2010 WL 2520973, at *10 (E.D. Va. June 17,
`
`2010) (granting motion to supplement a transfer motion because it assisted the court’s
`
`consideration of the matter).
`
`In the present matter, Defendants respectfully submit that the subpoena on Google will
`
`advance the Court’s consideration of the Motion to Transfer Venue by, inter alia, demonstrating
`
`that the relative ease of access to sources of proof and convenience for witnesses factors favor
`
`transfer, and confirming that AGIS’s arguments downplaying the relevance of Google’s
`
`documents and witnesses was an argument of convenience during transfer briefing that AGIS has
`
`abandoned now that it actually must litigate the merits of its claims.
`
`In Defendants’ Motion to Transfer Venue, Defendants argued that relevant documents,
`
`including highly proprietary source code, and witnesses with knowledge relating to the
`
`operation, design, and function of the third-party Accused Applications are located in the
`
`Northern District of California or at locations far more convenient to the Northern District of
`
`California than to the Eastern District of Texas. See Dkt. 38 at 24; see also Dkt. 51 at 8-10. In its
`
`
`
`5
`
`

`

`Case 2:17-cv-00517-JRG Document 81 Filed 09/17/18 Page 6 of 9 PageID #: 1059
`
`opposition, Plaintiff repeatedly suggested that the relevant Google documents are already
`
`publicly available, and thus should not be considered under the access to sources of proof factor.
`
`Dkt. 46 at 24 (“Although AGIS has accused functionality related to Google’s Android Operating
`
`System, AGIS expects to submit infringement contentions that do not invoke Local Patent Rule
`
`3-1(g), and that they rely only on publicly-available open source code or public APIs.”); Dkt. 52
`
`at 8 (“As for Google, to date, AGIS has not relied on any confidential Google code in its
`
`infringement contentions, but rather, relied upon publicly available source code.”)
`
`The subpoenas to Google, however, establish that Plaintiff’s arguments should not be
`
`credited. Specifically, the document subpoena seeks, among other requests, the source code
`
`related to the accused functionalities of Google Maps, Find My Device, and Android Device
`
`Manager, and documents sufficient to show the structure, operation, design, development,
`
`functionality, features, testing, and manufacture of the accused functionalities of Google Maps,
`
`Find my Device, and Android Device Manager. These document requests confirm that AGIS
`
`does not actually believe that its infringement case will rely solely on publicly available Google
`
`documents, regardless of whatever AGIS put in its initial infringement contentions. Moreover,
`
`AGIS seeks the production of such documents in the Northern District of California, further
`
`confirming that the relevant documents in the instant case are located in the Northern District of
`
`California.
`
`ZTE has consistently emphasized the importance of third party discovery in this case,
`
`especially from Google. With respect to the convenience of the parties and witnesses factor, ZTE
`
`made it clear that “evidence from third-parties, like Google, will be relevant” because the cited
`
`Google functionalities are “non-public code, and are maintained internally by Google engineers
`
`in California.” Dkt. 51 at 9. In its Opposition, Plaintiff again dismissed the relevance of Google
`
`
`
`6
`
`

`

`Case 2:17-cv-00517-JRG Document 81 Filed 09/17/18 Page 7 of 9 PageID #: 1060
`
`witnesses as “mere speculation.” Dkt. 46 at 7, 26. Furthermore, AGIS suggested that many of
`
`Google’s potential witnesses reside in Texas. Dkt. 46 at 25; see also Dkt. 52 at 7. Nevertheless,
`
`AGIS’s deposition subpoena, which was noticed in the Northern District of California, seeks
`
`testimony explaining the source code for Google Maps and Find My Device, as well as
`
`testimony on the structure, operation, design, development, functionality, features, testing, and
`
`manufacture for the accused features of Google Maps and Find My Device. Thus, the deposition
`
`subpoena shows that Google’s witnesses are not only relevant but crucial to understand the
`
`operation of the accused features of Google Maps and Find My Device, and that those witnesses
`
`are located in the Northern District of California.
`
`When considered in this context, AGIS’s position that it “has no sources of proof in the
`
`proposed transferee district,” Dkt. 46 at 25, is simply not true. AGIS does have a source of proof
`
`in the Northern District of California--Google--and the evidence AGIS now seeks is precisely the
`
`evidence ZTE identified in its transfer motion and continues to point to. It is not appropriate for
`
`AGIS to discount relevant Google documents and testimony for purposes of the transfer analysis,
`
`yet simultaneously seek a deposition and documents from Google through a subpoena. See In re
`
`Microsoft Corp., 630 F.3d 1361, 1364 (Fed. Cir. 2011) (“The Supreme Court has long urged
`
`courts to ensure that the purposes of jurisdictional and venue laws are not frustrated by a party’s
`
`attempt at manipulation.”). Accordingly, the Google subpoena demonstrates that relevant
`
`evidence in this action resides in the Northern District of California and only further confirms the
`
`appropriateness of transferring the present litigation to the United States District Court for the
`
`Northern District of California pursuant to 28 U.S.C. § 1404(a).
`
`
`
`7
`
`

`

`Case 2:17-cv-00517-JRG Document 81 Filed 09/17/18 Page 8 of 9 PageID #: 1061
`
`III. CONCLUSION
`
`For the foregoing reasons, Defendants respectfully submit that the Court grant their
`
`motion to supplement the record in support of its pending Motion to Transfer Venue.
`
`
`
`Dated: September 17, 2018
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
`/s/ Lionel M. Lavenue
`Lionel M. Lavenue
`Bradford C. Schulz
`FINNEGAN, HENDERSON, FARABOW,
`GARRETT & DUNNER, LLP
`Two Freedom Square
`11955 Freedom Drive
`Reston, VA 20190
`Phone: (571) 203-2700
`Fax: (202) 408-4400
`
`ATTORNEY FOR DEFENDANTS
`ZTE (USA) Inc. and ZTE (TX), Inc.
`
`
`
`8
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 2:17-cv-00517-JRG Document 81 Filed 09/17/18 Page 9 of 9 PageID #: 1062
`
`
`CERTIFICATE OF CONFERENCE
`
`Pursuant to Local Rule CV-7, the undersigned certifies that counsel have conferred, on
`
`September 14, 2018, on whether Plaintiff opposes the motion and relief requested herein. Plaintiff
`
`opposes the motion.
`
`
`
`/s/ Lionel M. Lavenue
`Lionel M. Lavenue
`
`
`CERTIFICATE OF SERVICE
`
`
`
`The undersigned hereby certifies that all counsel of record who are deemed to have
`
`consented to electronic service are being served with a copy of this document via the Court’s
`
`CM/ECF system per Local Rule CV-5(a)(3) on this September 17th of 2018. All other counsel not
`
`deemed to have consented to service in such manner will be served via facsimile transmission
`
`and/or first class mail.
`
`
`
`
`
`
`
`
`
`
`/s/ Lionel M. Lavenue
`Lionel M. Lavenue
`
`
`
`
`9
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket