throbber
Case 2:17-cv-00514-JRG Document 73 Filed 09/24/18 Page 1 of 12 PageID #: 3136
`
`
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`Civil Action No. 2:17-CV-514-JRG
`(Lead Case)
`
`
`
`Civil Action No. 2:17-CV-515-JRG
`Civil Action No. 2:17-CV-517-JRG
`
`AGIS SOFTWARE DEVELOPMENT LLC,
`
`
`Plaintiff,
`
`
`
`v.
`
`
`HTC CORPORATION,
`LG ELECTRONICS, INC.,
`ZTE CORPORATION, ZTE (USA), INC.,
`AND ZTE (TX), INC.,
`
`
`Defendants.
`
`
`

















`
`
`
`PLAINTIFF AGIS SOFTWARE DEVELOPMENT LLC’S OPPOSITION TO
`DEFENDANT LG ELECTRONICS, INC.’S MOTION TO SUPPLEMENT THE
`RECORD IN SUPPORT OF ITS MOTION TO TRANSFER VENUE TO THE
`NORTHERN DISTRICT OF CALIFORNIA
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 2:17-cv-00514-JRG Document 73 Filed 09/24/18 Page 2 of 12 PageID #: 3137
`
`
`
`I.
`
`II.
`
`TABLE OF CONTENTS
`
`BACKGROUND .............................................................................................................2
`
`ARGUMENT ..................................................................................................................4
`
`A. Supplementation of the Record Should be Denied ............................................................4
`
`B. The Proposed Additional Evidence is Not Determinative of the Outcome .........................4
`
`III.
`
`CONCLUSION ...............................................................................................................8
`
`
`
`
`
`
`
`
`
`i
`
`

`

`Case 2:17-cv-00514-JRG Document 73 Filed 09/24/18 Page 3 of 12 PageID #: 3138
`
`
`
`Cases
`
`TABLE OF AUTHORITIES
`
`
`
`Page(s)
`
`Blackberry Ltd. v. Avaya Inc.,
`No. 3:16-cv-012185-M (N.D. Tex. Oct. 10, 2017) ................................................................. 4
`
`Saint Lawrence Commns. LLC v. LG Electronics, Inc.,
`No. 2:14-cv-1044-JRG, 2015 WL 7854738 (E.D. Tex. Dec. 3, 2015) .................................... 6
`
`Vertical Comput. Sys., Inc. v. LG Elecs. MobileComm U.S.A., Inc.,
`No. 2:10-cv-490-JRG, 2013 WL 2241947 (E.D. Tex. May 21, 2013) .................................... 7
`
`In re Volkswagen AG,
`371 F.3d 201 (5th Cir. 2004) ................................................................................................. 4
`
`In re Volkswagen of America, Inc.,
`545 F.3d 304 (5th Cir. 2008) ................................................................................................. 4
`
`Statutes
`
`28 U.S.C. § 1404(a) .................................................................................................................... 2
`
`
`
`ii
`
`
`
`

`

`Case 2:17-cv-00514-JRG Document 73 Filed 09/24/18 Page 4 of 12 PageID #: 3139
`
`
`
`
`
`Plaintiff AGIS Software Development LLC (“AGIS”), by and through its undersigned
`
`counsel, submits this response in opposition to LG Electronics, Inc.’s (“LG”) Motion to
`
`Supplement the Record in Support of its Pending Motion to Dismiss Pursuant for Lack of Personal
`
`Jurisdiction or, in the Alternative, to Transfer Venue to the Northern District of California (513
`
`Dkt. 46).
`
`I.
`
`BACKGROUND
`LG’s motion to supplement the record on its motion to transfer venue should be denied
`
`because LG is seeking to capitalize on its own failure to provide adequate discovery to AGIS
`
`about the features and functionalities of the accused infringing applications. AGIS has attempted
`
`for months to obtain the information it needs from LG itself, only to be stonewalled by LG, which
`
`has failed and refused to provide the relevant discovery and denies that it has such information.
`
`Relevant portions of LG’s Objections and Responses to AGIS’s First Set of Interrogatories 1-10
`
`are annexed as Exhibit A. AGIS has effectively been forced to seek that information via
`
`deposition and document subpoenas served on non-party Google LLC (“Google”). LG now seizes
`
`upon that, disingenuously arguing that this somehow “undermines the credibility of its previous
`
`efforts to discount the relevance of Google’s witnesses, source code and other information to this
`
`action” and that this supports the transfer of this action to the Northern District of California
`
`pursuant to 28 U.S.C. § 1404(a). (514 Dkt. 66 at 3). To be clear, AGIS has not, on its own,
`
`acknowledged that Google possesses the relevant information or that Google witnesses are
`
`knowledgeable of the relevant facts. AGIS simply has had no choice but to serve Google with
`
`document and deposition subpoenas in the hope of obtaining what LG has refused to provide. LG
`
`
`
`2
`
`

`

`Case 2:17-cv-00514-JRG Document 73 Filed 09/24/18 Page 5 of 12 PageID #: 3140
`
`
`
`should not now be permitted to take advantage of its own failure to produce as a guise to
`
`strengthen its case for a transfer of venue to what LG perceives will be a more favorable forum.
`
`The thrust of LG’s motion is that AGIS’s subpoena, addressed to Google’s Mountain
`
`View, California headquarters, is proof positive that this action should be transferred to the
`
`Northern District of California. This is simply not the case. There is no evidence before this
`
`Court as to what responsive documents and witness testimony Google possesses, merely the
`
`cursory declarations from two Google employees that were submitted by LG’s co-defendant ZTE
`
`months ago. (Dkt. 51-4,5).1 Most telling is the fact that in response to AGIS’s subpoenas, Google
`
`objected and refused to produce the relevant information on the grounds that the information is or
`
`may be in LG’s possession. See Google LLC’s Objections and Responses to Plaintiff AGIS
`
`Software Development, LLC’s Deposition and Document Subpoenas (hereinafter, “Google’s
`
`Objections and Responses”), a copy of which is annexed as Exhibit B.2 AGIS is thus caught in the
`
`middle, between LG and Google, neither of whom is willing to produce information about the
`
`accused applications. To this day, LG has not identified any documents or witnesses in the
`
`proposed transferee district that are central to the outcome of this case, that so dramatically tip the
`
`balance of the public and private interest factors as to justify transfer of venue at this time.
`
`
`
`1 Declarations of Google employees Andrew Oplinger and William Luh virtually
`identical to those referred to and relied upon by LG here (517 Dkt. 51-4, 5), were already
`considered by this Court in connection with Huawei Device (Dongguan) Co., Ltd.’s (“Huawei”)
`Motion to Transfer Venue (513 Dkt. 36-4, 5). The Court found, "[n]otably, Huawei does not
`identify with any particularity any specific Google employees that they anticipating calling at
`trial or any documentation they plan to present as evidence." (513 Dkt. 140).
`
`2 Specifically, Google objected to the subpoena “to the extent that it requests documents
`or information that can be requested with much less burden from one or more parties to the
`litigation. In particular, Google objects to producing documents duplicative of those the named-
`defendants have [sic] already produced or may produce in their respective litigations.” See
`Google's Objections and Responses at ¶ 7.
`
`
`
`3
`
`

`

`Case 2:17-cv-00514-JRG Document 73 Filed 09/24/18 Page 6 of 12 PageID #: 3141
`
`
`
`Accordingly, both LG’s motion to supplement the record and its underlying motion to transfer
`
`venue should be denied.
`
`AGIS believes that the record on the motion to transfer is sufficient as is and need not be
`
`supplemented. AGIS asserts that supplementation of the record on the motion to transfer would
`
`not serve any useful purpose and should be denied. However, if the Court grants LG’s request,
`
`then AGIS should be permitted to supplement the record with Google’s response to the subpoenas
`
`to demonstrate (1) that the relevant information may not be obtainable from Google; and (2) that
`
`Google itself has stated that LG may possess the relevant information. At the very least, it appears
`
`that such information is not exclusively in Google’s possession in the proposed transferee district.
`
`II.
`
`ARGUMENT
`A. Supplementation of the Record Should be Denied
`Supplementation of the record on a pending motion may be denied where the new or
`
`additional information is not dispositive. Blackberry Ltd. v. Avaya Inc., No. 3:16-cv-012185-M
`
`(N.D. Tex. Oct. 10, 2017). Here, LG’s proposed addition of AGIS’s subpoena to Google
`
`contributes nothing to the quantum of proof before the Court on the merits of the underlying
`
`motion to transfer venue.
`
`B. The Proposed Additional Evidence is Not Determinative of the Outcome
`LG’s motion should also be denied because even if the LG was permitted to add the
`
`subpoena to Google to the record on this motion, LG has not demonstrated that this would
`
`materially affect the outcome of the decision as to transfer venue. A motion to transfer venue is
`
`determined not by any single factor but by looking at the totality of the private and public interest
`
`factors. In re Volkswagen AG, 371 F.3d 201, 203 (5th Cir. 2004); In re Volkswagen of America,
`
`Inc., 545 F.3d 304, 315 (5th Cir. 2008) (“Although the Gilbert factors are appropriate for most
`
`transfer cases, they are not necessarily exhaustive or exclusive. Moreover, we have noted that
`
`
`
`4
`
`

`

`Case 2:17-cv-00514-JRG Document 73 Filed 09/24/18 Page 7 of 12 PageID #: 3142
`
`
`
`‘none . . . can be said to be of dispositive weight.”) (citing Action Indus., Inc. v. U.S. Fid. & Guar.
`
`Corp., 358 F.3d 337, 340 (5th Cir. 2004)). Even in a case cited by LG, In re Genentech, the Court
`
`held that “[i]n patent cases, ‘the bulk of relevant evidence usually comes from the accused
`
`infringer . . .” (513 Dkt. 46 at 19), not from non-parties such as Google. In this case, LG admits
`
`that “[d]ocuments relating to the Accused Devices are maintained in South Korea, California,
`
`and/or New Jersey” and “primarily in Korea.” Id. at 20; 513 Dkt. 46-1 at ¶ 10.
`
`The lack of certainty as to the specific evidence Google possesses and where it is located
`
`further weighs against granting LG’s motion.3 In a related case before this Court, Apple argued in
`
`favor of transfer based on the presence of 13 non-party witnesses located in the Northern District
`
`of California who were the inventors of patents relied upon by Apple in its invalidity contentions.
`
`See AGIS Software Development LLC v. Apple Inc., Case No. 2:17-cv-00516-JRG (E.D. Tex.),
`
`Dkt. 76 at 12. This Court found that “Apple’s admission at argument that ‘one or two might’
`
`testify at trial, that ‘a couple of these individuals might be relevant at trial,’ and Apple’s
`
`representation that their investigation into the relevance of these individuals is ongoing and
`
`‘depending on how that goes, there is, you know, at least a good possibility that [the location of
`
`these individuals] should be afforded some weight.” Id. Ultimately however, the Court found that
`
`lack of certainty as to the potential evidence from these non-party witnesses weighed against
`
`transfer. Id. The same result should obtain here.
`
`
`
`3 In LG’s initial disclosures updated August 31, 2018, LG continues to list a “Witness
`from Google LLC who may have knowledge related to the functionality implicated in the
`accused applications” yet has not identified any specific witnesses it expected to testify regarding
`the functionality and features of the applications nor identified any documents with specificity.
`(514 Dkt. 66 at 6). AGIS is entitled to seek discovery from witnesses listed in LG’s initial
`disclosures, especially in light of the lack of relevant discovery from LG itself, without being
`punished for this by being denied its chosen forum.
`
`
`
`5
`
`

`

`Case 2:17-cv-00514-JRG Document 73 Filed 09/24/18 Page 8 of 12 PageID #: 3143
`
`
`
`LG has tried to transfer venue away from this Court in other cases on similarly shaky
`
`grounds and has lost. In Saint Lawrence Commns. LLC v. LG Electronics, Inc., No. 2:14-cv-1044-
`
`JRG, 2015 WL 7854738, at *3 (E.D. Tex. Dec. 3, 2015), LG argued that its subsidiaries have
`
`relevant information in San Diego weighing for a transfer to another district. The Court denied
`
`transfer finding that the, “evidence suggests that technical and financial documents relating to the
`
`accused products are also located in South Korea and New Jersey” and plaintiff demonstrated that
`
`it possessed relevant evidence in this district. Id. Further, LG could not demonstrate that a non-
`
`party, Qualcomm’s evidence “is clearly more accessible from San Diego . . . [and] [i]nstead LG
`
`has only shown that Qualcomm’s documents are in both Raleigh and San Diego.” Id. As a result,
`
`“LG has not shown that this factor weighs in favor of transfer . . . [and] [t]he Court finds that this
`
`factor is neutral.” Id. Like the plaintiff in Saint Lawrence, AGIS has demonstrated that relevant
`
`evidence from AGIS is located in Jupiter, Florida, Lenexa, Kansas, Austin, Texas, and Allen,
`
`Texas.
`
`LG misrepresents AGIS’s position regarding the discovery AGIS believed it might seek
`
`from Google. At no point in this matter did AGIS explicitly state that it would not seek the
`
`discovery of Google with respect to any proprietary Google application material. See Dkt. 68 at 7
`
`(“If Google proves to be a relevant third party at all. . .”) (emphasis added); see also Dkt. 82 at 1
`
`(“LGEKR does not indicate that any Google evidence, to the extent that it is necessary for this
`
`case, is inaccessible in a convenient location in or near this District.”) (emphasis added). In fact,
`
`AGIS represented that it would seek the discovery of Google if necessary and following the
`
`limited discovery regarding the relevant functionality and features of the applications. At the
`
`Evidentiary Hearing held on August 8, 2018, AGIS represented that “we don’t think we need it
`
`at this point in time, but there may be, and we may take discovery of Google with respect to any
`
`
`
`6
`
`

`

`Case 2:17-cv-00514-JRG Document 73 Filed 09/24/18 Page 9 of 12 PageID #: 3144
`
`
`
`proprietary Google application material that’s not in the [] public information.” (513 Dkt. 176 at
`
`70:18-22) (emphasis added). At the time of its briefing and the Evidentiary Hearing, AGIS did
`
`not feel the need to serve a subpoena on Google. However, as this matter progressed, because
`
`LG did not produce the necessary and relevant information regarding the functionality and
`
`features of the accused applications, AGIS was forced to seek this information from Google.
`
`Even if at some point in the future it was determined that Google in fact possesses relevant
`
`proof, which is by no means certain, this too would not justify transfer. Motions to transfer venue
`
`“are not decided on a series of changing facts, but instead should be evaluated based on the
`
`situation which existed when suit was filed.” Vertical Comput. Sys., Inc. v. LG Elecs.
`
`MobileComm U.S.A., Inc., No. 2:10-cv-490-JRG, 2013 WL 2241947, at *3 (E.D. Tex. May 21,
`
`2013) (citing In re EMC Corp., 2013 WL 324154, at *2 (Fed. Cir. Jan. 29, 2013)); see also Dkt.
`
`176 at 57 (“[A]s I understand the law, [transfer is decided] at the time the complaint was filed . .
`
`. not the time the motion to transfer was filed.”). At the time of the filing of the Complaint,
`
`AGIS believed the relevant source code was publicly available or within the possession of LG
`
`and that relevant proof would therefore likely be available without the need for Google as a non-
`
`party witness. AGIS believed and continues to believe that this is the case. Google itself appears
`
`to have confirmed that LG has the relevant information about the accused applications,
`
`objecting to AGIS’s subpoena on the grounds and to the extent that such information is available
`
`from LG. See Exh. B at ¶7. The fact that more than a year after the case was filed, AGIS has
`
`had to seek that information from Google as a result of LG’s continued failure and refusal to
`
`produce it, should not be held against AGIS and be used as a reason to transfer venue.
`
`
`
`
`
`
`
`7
`
`

`

`Case 2:17-cv-00514-JRG Document 73 Filed 09/24/18 Page 10 of 12 PageID #: 3145
`
`
`
`III. CONCLUSION
`For the foregoing reasons, AGIS respectfully requests that the Court deny LG’s Motion to
`
`Supplement the Record in Support of its Motion to Transfer Venue to the Northern District of
`
`California. In the alternative, should the Court grant LG’s motion, AGIS should be permitted to
`
`supplement the record on this motion with Googles Objections and Responses to AGIS’s
`
`subpoenas.
`
`Dated: September 24, 2018
`
`
`
`
`
`
`
`Respectfully submitted
`
`
`
`
`
`BROWN RUDNICK LLP
`
` /s/ Alfred R. Fabricant
`
`Alfred R. Fabricant
`NY Bar No. 2219392
`Email: afabricant@brownrudnick.com
`Peter Lambrianakos
`NY Bar No. 2894392
`Email: plambrianakos@brownrudnick.com
`Vincent J. Rubino, III
`NY Bar No. 4557435
`Email: vrubino@brownrudnick.com
`Joseph Mercadante
`NY Bar No. 4784930
`Email: jmercadante@brownrudnick.com
`Alessandra C. Messing
`NY Bar No. 5040019
`Email: amessing@brownrudnick.com
`John A. Rubino
`NY Bar No. 5020797
`Email: jrubino@brownrudnick.com
`Enrique W. Iturralde
`NY Bar No. 5526280
`Email: eiturralde@brownrudnick.com
`Daniel J. Shea Jr.
`NY Bar No. 5430558
`dshea@brownrudnick.com
`BROWN RUDNICK LLP
`7 Times Square
`New York, NY 10036
`Telephone: 212-209-4800
`
`8
`
`

`

`Case 2:17-cv-00514-JRG Document 73 Filed 09/24/18 Page 11 of 12 PageID #: 3146
`
`
`
`
`
`Facsimile: 212-209-4801
`
`Samuel F. Baxter
`Texas State Bar No. 01938000
`sbaxter@mckoolsmith.com
`Jennifer L. Truelove
`Texas State Bar No. 24012906
`jtruelove@mckoolsmith.com
`MCKOOL SMITH, P.C.
`104 E. Houston Street, Suite 300
`Marshall, Texas 75670
`Telephone: (903) 923-9000
`Facsimile: (903) 923-9099
`
`ATTORNEYS FOR PLAINTIFF, AGIS
`SOFTWARE DEVELOPMENT LLC
`
`9
`
`

`

`Case 2:17-cv-00514-JRG Document 73 Filed 09/24/18 Page 12 of 12 PageID #: 3147
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that, on September 24, 2018, 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).
`
`
`
`/s/ Alfred R. Fabricant
`
` Alfred R. Fabricant
`
`
`
`
`
`

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