throbber
Case 2:17-cv-00514-JRG Document 71 Filed 09/19/18 Page 1 of 9 PageID #: 3067
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`AGIS SOFTWARE DEVELOPMENT, LLC,
`
`Plaintiff,
`
`v.
`
`HTC CORPORATION,
`
`Defendant.
`
`CASE NO. 2:17-CV-0514-JRG
`
`JURY TRIAL DEMANDED
`
`
`
`HTC CORPORATION’S OPPOSED MOTION TO
`SUPPLEMENT THE RECORD IN SUPPORT OF MOTION TO DISMISS
`PURSUANT TO FED. R. CIV. P. 12(B)(2) OR, IN THE ALTERNATIVE,
`TO TRANSFER VENUE TO THE NORTHERN DISTRICT OF CALIFORNIA
`
`
`
`

`

`Case 2:17-cv-00514-JRG Document 71 Filed 09/19/18 Page 2 of 9 PageID #: 3068
`
`
`Defendant HTC Corporation (“HTC” or “Defendant”) respectfully submits this opposed
`
`motion to supplement the record in support of its pending Motion to Dismiss Pursuant to Fed. R.
`
`Civ. P. 12(b)(2) or, in the Alternative, to Transfer Venue to the Northern District of California.
`
`D.I. 29.
`
`I.
`
`BACKGROUND
`
`On January 22, 2018, HTC moved to transfer the above-captioned action filed by AGIS
`
`Software Development LLC (“Plaintiff” or “AGIS”) to the Northern District of California. See
`
`D.I. 29. In support of a change in venue, HTC 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 D.I. 29 at 6, 17-18; see also D.I. 47 at 2-6. HTC submitted declarations from
`
`Google witnesses establishing that, for the accused functionality for Google Maps for Mobile
`
`application 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. D.I. 29 at 6 (citing 2:17-cv-00513-JRG, D.I. 36-6, ¶¶ 1, 6-8); D.I. 29 at 5
`
`(citing 2:17-cv-00513-JRG, D.I. 36-4 at ¶¶ 1, 4; 2:17-cv-00513-JRG, D.I. 36-5 at ¶ 1; and 2:17-
`
`cv-00513-JRG, D.I. 36-6 at ¶¶ 6-8). 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. D.I. 29-33.
`
`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
`
`[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’).”
`
`
`
`- 1 -
`
`

`

`Case 2:17-cv-00514-JRG Document 71 Filed 09/19/18 Page 3 of 9 PageID #: 3069
`
`
`D.I. 40 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 Google Maps and Find My Device is irrelevant. D.I. 40 at 24-25. Plaintiff
`
`further argued that:
`
` “HTC also contends that potential non-party witnesses, such as Google, are
`located in and around the Northern District of California. [] However, HTC fails
`to identify how any evidence or testimony from Google witnesses will be relevant
`to this action.” D.I. 40 at 6.
`
` “HTC’s argument regarding the relevance of Google generally [] also fails. HTC
`contends that ‘Google’s publicly available open-source code is not what is
`actually relevant’ to this action. [] This argument is entirely ignores that AGIS’s
`infringement contentions rely significantly on Google’s publicly available source
`code.” D.I. 49 at 5.
`
` “In this case, AGIS accuses HTC’s mobile phone devices of infringing the
`Patents-in-Suit––not Google’s devices. Even if Google possesses relevant
`documents and employs individuals who have knowledge about the Accused
`Products and functionality, HTC has not demonstrated why any specific Google
`witness or document would necessitate transfer to the Northern District of
`California.” D.I. 40 at 2.
`
` “HTC has failed to meet this burden. HTC . . . failed to identify third party
`witnesses from . . . Google, let alone provide evidence as to the relevant and
`materiality of each witness or set forth evidence by each witness identifying any
`purported inconvenience.” D.I. 40 at 19.
`
` “HTC fails to identify any witnesses employed by Google, or provide evidence of
`their relevance and materiality.” D.I. 40 at 20.
`
`New evidence has recently emerged confirming HTC’s argument that the location and
`
`convenience of non-party Google weighs in favor of transfer to the Northern District of
`
`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 Ex.
`
`A; see also D.I. 66-2 (Google subpoena submitted in 513 matter against Huawei).
`
`
`
`- 2 -
`
`

`

`Case 2:17-cv-00514-JRG Document 71 Filed 09/19/18 Page 4 of 9 PageID #: 3070
`
`
`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,” D.I. 40 at 24 and D.I. 49 at 7, 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, HTC
`
`respectfully submits 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).
`
`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)
`
`
`
`- 3 -
`
`

`

`Case 2:17-cv-00514-JRG Document 71 Filed 09/19/18 Page 5 of 9 PageID #: 3071
`
`
`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, HTC respectfully submits that the subpoena on Google will
`
`advance the Court’s consideration of the transfer venue motion 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 HTC’s Motion to Transfer Venue, HTC 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 D.I. 29 at 6; see also D.I. 47 at 3-6. In its 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. 40 at 2 (“While AGIS
`
`has accused functionality related to Google’s Android Operating System, much of that
`
`information is publicly available through either open source code or public application
`
`programming interfaces (‘API’).”); id. at 24-25 (“AGIS’s infringement contentions rely on
`
`Google’s open source code and/or application programming interfaces which are publicly
`
`
`
`- 4 -
`
`

`

`Case 2:17-cv-00514-JRG Document 71 Filed 09/19/18 Page 6 of 9 PageID #: 3072
`
`
`available”); D.I. 49 at 7 (“AGIS’s infringement contentions rely on Google’s open source code
`
`and/or application programing interfaces, which are publicly available.”)
`
`The subpoenas to Google, however, establishes 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.
`
`HTC 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,
`
`HTC made it clear that “[t]he functionality and operation of Google’s apps are critical, and
`
`central, to AGIS’s infringement claim,” and that “Google’s source code for its apps is closed”
`
`and not publicly available. D.I. 29 at 17. In its Opposition, Plaintiff dismissed the relevance of
`
`Google witnesses. D.I. 40 at 6. 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
`
`
`
`- 5 -
`
`

`

`Case 2:17-cv-00514-JRG Document 71 Filed 09/19/18 Page 7 of 9 PageID #: 3073
`
`
`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,” D.I. 40 at 27, 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 HTC 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).
`
`III. CONCLUSION
`
`For the foregoing reasons, HTC respectfully submits that the Court grant its motion to
`
`supplement the record in support of its motion to dismiss or, in the alternative, transfer venue.
`
`
`
`
`
`- 6 -
`
`

`

`Case 2:17-cv-00514-JRG Document 71 Filed 09/19/18 Page 8 of 9 PageID #: 3074
`
`
`Dated: September 19, 2018
`
`Respectfully submitted,
`
`/s/ Miguel Bombach
`Matthew C. Bernstein, (Lead Attorney)
`CA State Bar No. 199240
`mbernstein@perkinscoie.com
`Miguel J. Bombach
`CA State Bar No. 274287
`mbombach@perkinscoie.com
`James Young Hurt (Pro Hac Vice)
`CA State Bar No. 312390
`jhurt@perkinscoie.com
`PERKINS COIE LLP
`11988 El Camino Real, Suite 350
`San Diego, CA 92130-2594
`Tel: (858) 720-5700
`Fax: (858) 720-5799
`
`Eric Findlay
`State Bar No. 00789886
`efindlay@findlaycraft.com
`FINDLAY CRAFT, P.C.
`102 N. College Ave., Suite 900
`Tyler, TX 75702
`Tel: (903) 534-1100
`Fax: (903) 534-1137
`
`ATTORNEYS FOR DEFENDANT
`HTC CORPORATION
`
`
`- 7 -
`
`
`
`
`
`

`

`Case 2:17-cv-00514-JRG Document 71 Filed 09/19/18 Page 9 of 9 PageID #: 3075
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that a true and correct copy of the above and foregoing
`
`document has been served on September 19, 2018, to all counsel of record who are deemed to
`
`have consented to electronic service via the Court’s CM/ECF system per Local Rule CV-5(a)(3).
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/ Miguel J. Bombach
` Miguel J. Bombach
`
`
`
`
`
`
`CERTIFICATE OF CONFERENCE
`
`Pursuant to L.R. CV-7(i), the undersigned hereby certifies that counsel for HTC
`
`Corporation conferred with counsel for AGIS via phone on September 19, 2018 regarding
`
`whether AGIS opposes the motion and relief requested herein. Plaintiff opposes this motion.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`/s/ Miguel J. Bombach
`Miguel J. Bombach
`
`
`
`- 1 -
`
`

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