throbber
Case 6:21-cv-00569-ADA Document 59 Filed 05/11/22 Page 1 of 9
`Case 6:21-cv-00569-ADA Document 59 Filed 05/11/22 Page 1 of 9
`
`FILED UNDER SEAL
`FILED UNDER SEAL
`
`EXHIBIT 1
`EXHIBIT 1
`
`

`

`Case 6:21-cv-00569-ADA Document 59 Filed 05/11/22 Page 2 of 9
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`TOUCHSTREAM TECHNOLOGIES,
`INC.
`
`
`Plaintiff,
`
`v.
`
`
`GOOGLE LLC
`
`
`Defendant.
`
`
`
`
`
`
`
`
`Civil Action No. 6:21-cv-569-ADA
`
`JURY TRIAL DEMANDED
`
`
`TOUCHSTREAM’S SUR-REPLY IN OPPOSITION TO GOOGLE’S MOTION TO
`TRANSFER VENUE
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 6:21-cv-00569-ADA Document 59 Filed 05/11/22 Page 3 of 9
`
`I.
`
`INTRODUCTION
`
`Google has already fallen far short of its burden to prove that the Northern District of
`
`California is a clearly more convenient forum for the parties. Now, in response to Touchstream’s
`
`abundant proof of this case’s ties to WDTX, Google lodges a last-ditch request for intra-district
`
`transfer to Austin—even though the parties did not conduct venue discovery or briefing on that
`
`issue. The Court should decline to hear this tardy request, or alternatively should deny it and let
`
`the case proceed here in WDTX where it has been moving forward for almost a year.
`
`Google’s request not only reflects the strength of Touchstream’s argument that this case
`
`belongs in WDTX, but also evinces Google’s true goal: to delay a trial on the merits that now
`
`looms less than ten months away. Indeed, after waiting more than six months to file its inter-district
`
`transfer motion, Google waited another four months—until after venue discovery closed—to
`
`request intra-district transfer to Austin. The Court should deny Google’s request due to this
`
`delay—as well as the unfair prejudice to Touchstream of dealing with a second belated transfer
`
`request after Google has already raised, litigated, and fallen short on its initial transfer gambit.
`
`
`
`But Google’s request also fails on the merits. Put simply, Waco is a more appropriate venue
`
`for this case than Austin. While it is true that most of Google’s relevant witnesses reside in Austin,
`
`most of the non-party witnesses reside in Dallas. Conveniently, Waco is about halfway between
`
`Dallas and Austin and lies within 100 miles of each (and thus within the subpoena limits of Rule
`
`45(c)(1)(A)). In contrast, Austin is far less convenient for the Dallas witnesses—over a three-hour
`
`drive, and nearly 200 miles away. These facts alone compel keeping this case in Waco.
`
`
`
`Further, transfer to Austin would prejudice Touchstream and waste judicial resources. This
`
`case has been pending for nearly a year, and the parties have complied with the Court’s contention
`
`requirements, venue discovery rules, and interim protective order. The parties have also followed
`
`
`
`
`2
`
`

`

`Case 6:21-cv-00569-ADA Document 59 Filed 05/11/22 Page 4 of 9
`
`this Court’s guidelines for claim construction briefing, which was completed more than three
`
`months ago, and have been negotiating ESI and protective orders based on this Court’s default
`
`orders for many months. Google still has a partial 12(b)(6) motion pending before this Court. There
`
`is no reason at this stage―just over nine months from trial―to transfer to Austin, which would
`
`require spending both time and money bringing a new court up to speed, as well as adjusting to
`
`new rules and procedures. Google’s request should be denied.
`
`II.
`
`ARGUMENT
`
`A.
`
`Google’s request for transfer to Austin should be denied due to Google’s delay.
`
`As Touchstream pointed out in its opposition brief, significant delay in requesting transfer
`
`supports denial. Dkt. 46 at 12-13. Google still provides no excuse for its prejudicial delay, nor any
`
`contrary case law. Dkt. 61. While Google delayed its transfer motion to NDCA by around six
`
`months, its new request for intra-district transfer to Austin comes almost a full year after this case
`
`was filed. Notably, Google waited until after venue discovery had closed on Google’s request for
`
`inter-district transfer—and after Touchstream proved there are significant connections to
`
`WDTX—before making its belated intra-district transfer request, which is pieced together from
`
`discovery conducted on a different issue not disclosed to Touchstream. Unsurprisingly, during
`
`venue discovery, Touchstream was focused on Google’s connections to WDTX generally, rather
`
`than to Waco specifically. Google’s decision to wait until after the close of venue discovery
`
`deprives Touchstream of the ability to fully explore why Waco is a more appropriate venue than
`
`Austin, and Google’s request should be denied on this basis alone.
`
`B. Waco is far more convenient when considering all of the relevant Texas
`witnesses.
`
`Setting aside whether an hour-and-a-half drive from Austin to Waco is truly such an
`
`inconvenience for Google’s employees that it merits intra-district transfer, the evidence shows that
`3
`
`
`
`
`

`

`Case 6:21-cv-00569-ADA Document 59 Filed 05/11/22 Page 5 of 9
`
`Austin is far from a “clearly more convenient” venue when considering all of the witnesses.
`
`Predictably, Google’s transfer request to Austin focuses only on convenience for Google’s
`
`witnesses and ignores the many non-party witnesses located in Dallas, including:
`
`
`
`
`
`meetings (
`
`, the Touchstream consultant who attended Touchstream-Google
` Texas, just north of Dallas);1
`
`Texas);2
`
` who helped Touchstream’s initial hospitality launch (Dallas,
`
` Witnesses associated with
`partnerships and
`
` who Touchstream pursued heavily for
` (Dallas, Texas);3
`
` Witnesses associated with
`who is
`
`, who Touchstream also pursued and
` (Dallas, Texas);4
`
` Witnesses associated with
`hospitality product (Dallas, Texas);5 and
`
` where Touchstream first debuted its
`
` Witnesses associated with
`, one of Touchstream’s major business
`partners (with relevant personnel in Dallas, Texas).6
`
`Compulsory process will likely be required to secure attendance of these witnesses at trial, and
`
`only Waco―which is roughly 90 miles from Dallas―is within the 100-mile subpoena radius of
`
`Rule 45(c)(1)(A). The Austin courthouse, by contrast, is nearly 200 miles from Dallas.7
`
`Even if these third-party witnesses are willing, Waco is the most convenient place for trial:
`
`Waco is almost exactly halfway between Austin and Dallas, and about an hour-and-a-half drive
`
`
`1 Ex. A at 25:12-15; Dkt. 46, Ex. B at 16.
`2 Ex. A at 53:10-54:7.
`3 Ex. A at 78:11-79:15; Dkt. 50 at 3.
`4 Dkt. 46, Ex. J at 98:5-17.
`5 Ex. A 55:8-56:3.
`6 Ex. A at 60:2-6 (“Q. So they hired, you know, sales executives from around the country,
`Atlanta, Dallas,
` in LA, to handle their sales within the United States? A. Correct…”).
`7 Dec., ¶ 6.
`
`4
`
`
`
`
`

`

`Case 6:21-cv-00569-ADA Document 59 Filed 05/11/22 Page 6 of 9
`
`from each.8 In contrast, the Austin courthouse is nearly a 3-hour drive each way.9There are also
`
`several relevant witnesses in Houston, including one of Touchstream’s lead programmers and
`
`various knowledgeable personnel from
`
` (which was Touchstream’s largest
`
`business partner, generating
`
` in revenue).10 Waco is no more inconvenient for
`
`Houston witnesses than Austin, with each city almost exactly a three-hour drive from Houston.11
`
`Finally, the
`
`—25 miles south of
`
`Dallas. Although Google’s Rule 30(b)(6) witness was unable to testify as to whether
`
`
`
`12 if any Chromecast-related documents or data are ultimately
`
`found to reside in Texas, they will be closer to Waco than to Austin.
`
`C.
`
`Transfer to Austin would unfairly prejudice Touchstream and negate judicial
`economy.
`
`Transfer to Austin after Google’s significant delay would prejudice Touchstream and
`
`obviate much of the work this Court, and the parties, have already done in this case during
`
`Google’s unexplained delay. This case is at an advanced stage. Fact discovery closes in just four
`
`months, and trial is less than a year away. This Court has already gained familiarity with the case
`
`through Google’s pending 12(b)(6) motion on willful infringement, through resolving venue
`
`discovery disputes, and through the parties’ claim construction briefing. The parties have already
`
`expended significant resources under this Court’s rules, including this Court’s early deadlines for
`
`
`8 Bergsten Dec., ¶¶ 4-5.
`9 Dec., ¶ 6.
`10 Dkt. 46 at 8.
`11 Dec., ¶¶ 7-8.
`12 Dkt. 46, Ex. A at 185:2-18
`
`
`
`
`5
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 6:21-cv-00569-ADA Document 59 Filed 05/11/22 Page 7 of 9
`
`infringement and invalidity contentions and for claim construction briefing. Google has benefitted
`
`from receiving the early infringement contentions required by this Court, and Touchstream should
`
`not now be denied the benefit of this Court’s efficient trial schedule. If this case is transferred to
`
`Austin, delay is all but inevitable given the need for a new judge to review the status of the case,
`
`read the claim construction briefs, and set a new schedule (including finding a time for trial). All
`
`of this prejudice is the result of Google’s delay—first in requesting inter-district transfer, then in
`
`its 11th-hour request for intra-district transfer. The Court should deny Google’s intra-district
`
`transfer request accordingly.
`
`III. CONCLUSION
`
`Google has failed to timely request transfer to Austin, and has failed to meet its burden to
`
`show that either the NDCA or Austin is a “clearly more convenient” forum for this dispute.
`
`Accordingly, Touchstream respectfully requests that the Court deny Google’s Motion to Transfer
`
`Venue.
`
`Date: May 4, 2022
`
`
`
`
`Respectfully submitted,
`
`SHOOK, HARDY & BACON L.L.P.
`
`/s/ Jordan T. Bergsten
`Jordan T. Bergsten, pro hac vice
`B. Trent Webb, pro hac vice
`Ryan D. Dykal, pro hac vice
`Samuel J. LaRoque, pro hac vice
`Shook, Hardy & Bacon, LLP
`2555 Grand Boulevard
`Kansas City, MO 64108
`(816) 474-6550/F: (816) 421-5547
`Email: slaroque@shb.com
`Email: bwebb@shb.com
`Email: rdykal@shb.com
`Email: jbergsten@shb.com
`
`
`
`6
`
`

`

`Case 6:21-cv-00569-ADA Document 59 Filed 05/11/22 Page 8 of 9
`
`Fiona A. Bell (TX Bar No. 24052288)
`Shook, Hardy & Bacon LLP
`600 Travis Street, Suite 3400
`Houston, TX 77002
`(713) 227-2008/F: (713)-227-9508
`Email: fbell@shb.com
`
`Counsel for Plaintiff
`Touchstream Technologies, Inc.
`
`
`
`
`7
`
`
`
`
`
`
`
`
`

`

`Case 6:21-cv-00569-ADA Document 59 Filed 05/11/22 Page 9 of 9
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that the foregoing was electronically filed with the Clerk of the Court using
`
`the CM/ECF system, which will send a notification of such filing (“NEF”) to all counsel of record
`
`who have appeared in this case per Local Rule CV-5(b) on May 4, 2022.
`
`
` /s/ Jordan T. Bergsten
` Attorney for Plaintiff
`
`
`
`
`
`
`8
`
`

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