throbber
Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 1 of 20
`
`UNITED STATES DISTRICT COURT
`WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`
`
`Civil Action No.: 6:21-cv-1296-ADA
`
`JURY TRIAL DEMANDED
`
`
`
`
`
`IOENGINE, LLC,
`
` Plaintiff,
`v.
`
`ROKU, INC.,
`
` Defendant.
`
`
`
`
`
`
`
`
`
`
`
`
`
`DEFENDANT’S OPPOSED MOTION TO TRANSFER VENUE
`TO THE NORTHERN DISTRICT OF CALIFORNIA UNDER 28 U.S.C. § 1404(a)
`
`{ROKUIN/00009/00604617}
`
`
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 2 of 20
`
`TABLE OF CONTENTS
`
`I.
`
`II.
`
`III.
`
`IV.
`
`INTRODUCTION .............................................................................................................. 1
`
`FACTUAL BACKGROUND ............................................................................................. 2
`
`LEGAL STANDARD ......................................................................................................... 4
`
`THE NORTHERN DISTRICT OF CALIFORNIA IS A CLEARLY MORE
`CONVENIENT VENUE FOR THE CURRENT DISPUTE.............................................. 5
`
`A.
`
`B.
`
`This Action Could Have Been Brought in the Northern District
` of California. .......................................................................................................... 5
`
`The Private Interest Factors Weigh Heavily in Favor of Transfer to
`the Northern District of California. ......................................................................... 6
`
`1.
`
`2.
`
`3.
`
`4.
`
`The Convenience of Willing Witnesses Strongly Favors Transfer ............ 6
`
`The Relative Ease of Access to Sources of Proof Favors Transfer ............ 9
`
`The Availability of Compulsory Process Favors Transfer or is Neutral. . 10
`
`There Are No Practical Problems Weighing Against Transfer ................ 10
`
`C.
`
`The Public Interest Factors Favor Transfer to the Northern District
`of California. ......................................................................................................... 11
`
`1.
`
`2.
`
`3.
`
`The Local Interest Factor Weighs Heavily In Favor of Transfer. ............. 11
`
`Court Congestion is Neutral...................................................................... 13
`
`The Remaining Public Interest Factors Are Neutral ................................. 14
`
`CONCLUSION ................................................................................................................. 14
`
`V.
`
`
`
`
`
`
`
`
`
`
`
`i
`
`{ROKUIN/00009/00604617}
`
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 3 of 20
`
`TABLE OF AUTHORITIES
`
`
`
`
`
`Cases
`
`Page(s)
`
`10Tales, Inc. v. Tiktok Inc.,
`2021 U.S. Dist. LEXIS 96694 (W.D. Tex. May 21, 2021)............................................6, 10, 14
`
`In re Acer Am. Corp.,
`626 F.3d 1252, 1256 (Fed. Cir. 2010)......................................................................................12
`
`In re Adobe Inc.,
`823 F. App’x 929 (Fed. Cir. 2020) ..........................................................................................13
`
`Airbus S.A.S. v. Aviation Partners, Inc.,
`No. 11-1030, 2012 U.S. Dist. LEXIS 91463 (W.D. Tex. June 29, 2012) .................................4
`
`In re Apple Inc.,
`979 F.3d 1332 (Fed. Cir. 2020)........................................................................................ passim
`
`In re Cray Inc.,
`871 F.3d 1355 (Fed. Cir. 2017)..................................................................................................5
`
`DataQuill Ltd. v. Apple Inc.,
`No. 13-706, 2014 U.S. Dist. LEXIS 82410 (W.D. Tex. June 13, 2014) .......................4, 13, 14
`
`Decapolis Sys., LLC v. eClinicalWorks, LLC,
`No. 6:21-cv-00502, Dkt. No. 30 (W.D. Tex. Mar. 1, 2022) ........................................1, 8, 9, 11
`
`In re Genentech, Inc.,
`566 F.3d 1338 (Fed. Cir. 2009)........................................................................................ passim
`
`In re Google LLC,
`2021 U.S. App. LEXIS 29137 (Fed. Cir. Sep. 27, 2021) ..........................................................8
`
`In re Google LLC,
`2021 U.S. App. LEXIS 33789 (Fed. Cir. Nov. 15, 2021) ..........................................................9
`
`In re Google,
`2021 WL 4427899 ...................................................................................................................12
`
`In re Hoffmann-La Roche Inc.,
`587 F.3d 1333 (Fed. Cir. 2009)................................................................................................12
`
`In re Hulu, LLC,
`2021 U.S. App. LEXIS 22723 (Fed. Cir. Aug. 2, 2021) ........................................................6, 8
`
`{ROKUIN/00009/00604617}
`
`
`ii
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 4 of 20
`
`In re Juniper Networks, Inc.,
`14 F.4th 1313 (Fed. Cir. 2021) ..................................................................................................8
`
`Koss Corp. v. Plantronics, Inc.,
`No. 6:20-cv-00663, 2021 U.S. Dist. LEXIS 97597 (W.D. Tex. May 20, 2021) .....................14
`
`Media Chain, LLC v. Roku, Inc.,
`No. 1:21-cv-27, 2021 U.S. Dist. LEXIS 243562 (W.D. Tex. Dec. 7, 2021) ................... passim
`
`In re Nitro Fluids L.L.C.,
`978 F.3d 1308 (Fed. Cir. 2020)................................................................................................13
`
`Piper Aircraft Co. v. Reyno,
`454 U.S. 235, 241 n.6 (1981) .....................................................................................................5
`
`In re Samsung Elecs. Co.,
`2 F.4th 1371 (Fed. Cir. 2021) ............................................................................................12, 13
`
`Super Interconnect Techs. v. Google LLC,
`2021 U.S. Dist. LEXIS 242299 (W.D. Tex. Nov. 5, 2021) .....................................................13
`
`Triller, Inc. v. Bytedance, Ltd.,
`No. 6-20-cv-00693, 2021 U.S. Dist. LEXIS 168441 (W.D. Tex. July 9, 2021)......................14
`
`In re TS Tech USA,
`551 F.3d at 1321 ................................................................................................................13, 14
`
`Uniloc USA Inc. v. Box, Inc.,
`No. 17-754, 2018 U.S. Dist. LEXIS 94966 (W.D. Tex. June 6, 2018) .....................................5
`
`In re Volkswagen AG,
`371 F.3d 201 (5th Cir. 2004) .................................................................................................4, 5
`
`In re Volkswagen of America, Inc.,
`545 F.3d 304 (5th Cir. 2008) (en banc) .....................................................................4, 5, 13, 14
`
`Rules
`
`Fed. R. Civ. P. 45(c)(1) ..................................................................................................................10
`
`Statutes
`
`28 U.S.C. § 1400(b) .........................................................................................................................5
`
`28 U.S.C. § 1404(a) .................................................................................................................1, 2, 4
`
`
`
`{ROKUIN/00009/00604617}
`
`
`iii
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 5 of 20
`
`I.
`
`INTRODUCTION
`
`Defendant Roku, Inc. (“Roku”) moves under 28 U.S.C. § 1404(a) to transfer this action
`
`to the Northern District of California (“NDCA”), as NDCA is the most convenient and
`
`appropriate venue for this dispute.
`
`Roku’s personnel, facilities, and infrastructure involved in the engineering, design,
`
`development, marketing, and financial aspects for the accused Roku streaming players are based
`
`in NDCA: the home of Roku’s headquarters and its principal place of business. Roku’s token
`
`connection to the Western District of Texas (“WDTX”) is its Austin office, which is of no
`
`relevance to this case. In fact, Roku is not aware of a single piece of evidence or likely fact
`
`witness coming out of the Austin office or elsewhere in WDTX.
`
`Plaintiff IOENGINE, LLC (“IOENGINE”) is a non-practicing entity with no ties to this
`
`District. IOENGINE’s basis for venue boils down to nothing more than the general allegation
`
`that Roku has a presence in this District and has sold streaming players here. But the Federal
`
`Circuit has made clear that presence in a district alone is insufficient to defeat transfer. See e.g.,
`
`In re Apple Inc., 979 F.3d 1332 (Fed. Cir. 2020). In Apple, despite the movant having more than
`
`8,000 employees and multiple retail stores in WDTX, including an under-development hotel for
`
`employees visiting Austin, the Court found that, even under the heightened standards for
`
`mandamus relief, NDCA was clearly more convenient. Id. at 1339-46, 1351. Consistent with
`
`this, another Court in this District recently transferred a patent infringement action against Roku
`
`to NDCA when venue, like here, was based on similarly generic allegations of infringement
`
`occurring in the District. See Media Chain, LLC v. Roku, Inc., No. 1:21-cv-27, 2021 U.S. Dist.
`
`LEXIS 243562 (W.D. Tex. Dec. 7, 2021) (Yeakel, J.); see also Decapolis Sys., LLC v.
`
`{ROKUIN/00009/00604617}
`
`
`1
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 6 of 20
`
`eClinicalWorks, LLC, No. 6:21-cv-00502, Dkt. No. 30 (W.D. Tex. Mar. 1, 2022) (finding general
`
`presence in this District insufficient to defeat transfer).
`
`Roku’s argument and evidence for transfer in the present dispute is at least as strong as
`
`that in Apple and Media Chain. Roku’s headquarters and principal place of business is within
`
`NDCA in San Jose, California. Roku’s relevant employees, including engineers, financial
`
`analysts, and marketing staff, are located in Roku’s San Jose office. The accused streaming
`
`players (“Accused Products”) were also designed, developed, and tested in NDCA. Because the
`
`private and public interest factors show that NDCA is clearly more convenient, Roku respectfully
`
`requests that this case be transferred to NDCA under 28 U.S.C. § 1404(a).
`
`II.
`
`FACTUAL BACKGROUND
`
`On December 14, 2021, IOENGINE filed a Complaint against Roku alleging
`
`infringement of U.S. Patent Nos. 10,447,819 (“the ’819 Patent”) and 10,972,584 (“the ’584
`
`Patent”) (collectively, “the Asserted Patents”). The Asserted Patents are generally directed to a
`
`portable device configured to communicate with a communications network through an access
`
`terminal, using specific components and software programming. IOENGINE appears to allege
`
`that the way the Accused Products: (1) are used in conjunction with a display device, like a TV;
`
`(2) communicate with online servers to provide access to media content and services, whether
`
`free or paid for using Roku Pay; and (3) are controlled through the use of a graphical user
`
`interface (“Accused Functionalities”), infringe the ’819 patent’s claims 184-192 and the ’584
`
`patent’s claims 1-99.
`
`Roku is headquartered in San Jose, California, and Roku’s business relevant to the
`
`Accused Products and Functionalities takes place in NDCA. Roku’s streaming player hardware,
`
`as well the Roku operating system (“OS”) that runs on that hardware, including source code, was
`
`{ROKUIN/00009/00604617}
`
`
`2
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 7 of 20
`
`principally designed and developed at Roku’s headquarters in California.1 (Declaration of
`
`Prateek Tandon (“Tandon Decl.”),2 ¶ 6.) Similarly, the information and Roku employees that
`
`work most closely with, and have the most specialized knowledge of, the technical aspects
`
`relating to the Accused Products and Functionalities are located in NDCA. (Id., ¶¶ 2-3, 8-12.)
`
`The same is true for the financial aspects of the case, as the information and persons
`
`knowledgeable about the current and historical market and sales relating to the Accused Products
`
`are also in San Jose, California. (Id., ¶¶ 13-14.) And although Roku documents relating to the
`
`Accused Products and Functionalities are stored on cloud servers, these documents are managed
`
`by Roku’s IT group based in San Jose. (Id., ¶ 7.)
`
`IOENGINE points to Roku Senior Vice President of Product Engineering and
`
`Operations, Mr. Scott de Haas’s presence in Texas (Compl., ¶ 13) as an alleged basis to remain
`
`in this District but, as was the case in Media Chain, there is no special connection between Mr.
`
`de Haas and IOENGINE’s infringement allegations. See Media Chain, 2021 U.S. Dist. LEXIS
`
`243562, at *5. In fact, Roku is not aware of any employee based out of Roku’s Austin office
`
`with specialized knowledge of the Accused Products and Functionalities. (Tandon Decl., ¶ 8.)
`
`Indeed, Roku’s Austin office has no connection with the current dispute. IOENGINE
`
`points to a truncated statement made by Gergely Timar in a different case about the engineering
`
`work that occurs in Austin as allegedly supporting venue in this District (Compl., ¶ 13), but that
`
`case involves Roku’s OneView advertising platform and Mr. Timar’s comment merely confirms
`
`the work carried out on Roku TVs in Austin is not related to the OneView advertising platform.
`
`(See Dkt. No. 18, ¶13 (reproducing full quote from Mr. Timar).) Notably, neither Roku TVs nor
`
`OneView are implicated in this case. As with Roku’s other offices, Austin is also home to a
`
`
`1 This includes prior headquarters in Saratoga and Los Gatos, both in NDCA.
`2 The Tandon Declaration is attached hereto as Exhibit 1.
`{ROKUIN/00009/00604617}
`3
`
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 8 of 20
`
`small number of sales and marketing professionals, but none of these individuals have any
`
`specialized knowledge of Roku’s streaming business that may be relevant to the current dispute.
`
`Apart from filing the present suit in WDTX, IOENGINE has no relevant ties to Texas.
`
`IOENGINE is a limited liability company organized under the laws of Delaware, with a principal
`
`place of business in Connecticut. (Compl., ¶ 2.) All prior lawsuits filed by IOENGINE were
`
`filed in Delaware. (See Declaration of Alec Royka (“Royka Decl.”),3 Ex. 2A (IOENGINE
`
`district court case list).) The alleged inventor of the Asserted Patents and sole member of
`
`IOENGINE, Mr. Scott McNulty, appears to reside in Connecticut. (Id. at Ex. 2B (property
`
`record for 22 Ensign Rd., Norwalk, CT 06853); Id. at Ex. 2C (Scott McNulty LinkedIn profile).)
`
`Further, there is no evidence that IOENGINE owns any land in Texas, makes any products in
`
`Texas, or employs anyone in Texas, let alone in this District.
`
`III. LEGAL STANDARD
`
`The decision of whether to transfer this case under 28 U.S.C. § 1404(a) centers on two
`
`inquiries: (1) whether NDCA is a district where IOENGINE could have brought the action, and
`
`(2) “whether private and public interest factors favor transfer” such that NDCA is “clearly more
`
`convenient.” Airbus S.A.S. v. Aviation Partners, Inc., No. 11-1030, 2012 U.S. Dist. LEXIS
`
`91463, at *10 (W.D. Tex. June 29, 2012). Here, Roku “need not show the [factors] substantially
`
`outweigh [IOENGINE’s] choice of venue—it is enough to show the new venue is clearly more
`
`convenient than the original one.” DataQuill Ltd. v. Apple Inc., No. 13-706, 2014 U.S. Dist.
`
`LEXIS 82410, at *7 (W.D. Tex. June 13, 2014) (citing In re Volkswagen of America, Inc.
`
`(“Volkswagen II”), 545 F.3d 304, 314 (5th Cir. 2008) (en banc)).
`
`To determine if another district is clearly more convenient, the Fifth Circuit weighs a
`
`number of private and public factors, none of which is dispositive. In re Volkswagen AG
`
`3 The Royka Declaration is attached hereto as Exhibit 2.
`{ROKUIN/00009/00604617}
`4
`
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 9 of 20
`
`(“Volkswagen I”), 371 F.3d 201, 203 (5th Cir. 2004). The private factors are: (1) the relative ease
`
`of access to sources of proof; (2) the availability of compulsory process to secure the attendance
`
`of witnesses; (3) the cost of attendance for willing witnesses; and (4) all other practical problems
`
`that make a trial easy, expeditious, and inexpensive. Id. (citing Piper Aircraft Co. v. Reyno, 454
`
`U.S. 235, 241 n.6 (1981)); see also Uniloc USA Inc. v. Box, Inc., No. 17-754, 2018 U.S. Dist.
`
`LEXIS 94966, *4 (W.D. Tex. June 6, 2018). The public factors are: (1) the administrative
`
`difficulties flowing from court congestion; (2) the local interest in having localized interests
`
`decided at home; (3) the familiarity of the forum with the law that will govern the case; and (4)
`
`the avoidance of unnecessary problems of conflict of laws of the application of foreign law.
`
`Volkswagen I, 371 F.3d at 203. And although IOENGINE’s choice of venue is not a distinct
`
`factor in the Fifth Circuit’s venue transfer analysis, it is nonetheless taken into account by
`
`placing the burden to show good cause for the transfer on Roku. Volkswagen II, 545 F.3d at 314
`
`n. 10.
`
`IV. THE NORTHERN DISTRICT OF CALIFORNIA IS A CLEARLY MORE
`CONVENIENT VENUE FOR THE CURRENT DISPUTE.
`
`A. This Action Could Have Been Brought in the Northern District of California.
`
`IOENGINE could have properly brought this suit against Roku in NDCA. Venue is
`
`proper under § 1400(b) in the district where the defendant “resides” or “where the defendant has
`
`committed acts of infringement and has a regular and established place of business.” 28 U.S.C. §
`
`1400(b); In re Cray Inc., 871 F.3d 1355, 1360 (Fed. Cir. 2017). It is undisputed that Roku
`
`maintains its principal place of business in San Jose, California, and therefore has a regular and
`
`established place of business in NDCA. See Compl., ¶ 3. Likewise, because sales of the
`
`Accused Products take place throughout the country and within NDCA, the acts alleged by
`
`{ROKUIN/00009/00604617}
`
`
`5
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 10 of 20
`
`IOENGINE to constitute infringement also occurred in NDCA. Accordingly, venue is proper in
`
`NDCA and this case against Roku could have been brought there.
`
`
`
`B. The Private Interest Factors Weigh Heavily in Favor of Transfer to the
`Northern District of California.
`
`1. The Convenience of Willing Witnesses Strongly Favors Transfer.
`
`The convenience of willing witnesses overwhelmingly favors transfer to NDCA. This
`
`factor is the single most important factor in the transfer analysis. In re Genentech, Inc., 566 F.3d
`
`1338, 1342 (Fed. Cir. 2009); 10Tales, Inc. v. Tiktok Inc., 2021 U.S. Dist. LEXIS 96694, at *10
`
`(W.D. Tex. May 21, 2021). And under this factor, courts should consider all potential material
`
`and relevant witnesses, including party witnesses. See In re Hulu, LLC, 2021 U.S. App. LEXIS
`
`22723, at *12-14 (Fed. Cir. Aug. 2, 2021).
`
`The Roku witnesses with knowledge of the Accused Products and Functionalities,
`
`whether from a technical or financial perspective, are in NDCA. Specifically, based on Roku’s
`
`investigation of the case to date, the following people have the most relevant knowledge relating
`
`to the Accused Products and Functionalities and are each located at Roku’s headquarters in San
`
`Jose, California:
`
`• Prateek Tandon, Vice President, Software Engineering: Mr. Tandon is a senior
`Roku employee with specific knowledge about the following Roku features
`implicated by IOENGINE’s allegations—on-device setup, home screen and home
`menu, movies and TV store, and settings—and, more generally, is knowledgeable
`about Roku’s streaming players, the Roku OS, and how Roku’s software is used
`in conjunction with a display device and the Internet to access media content and
`services. In addition to the foregoing, Mr. Tandon is also knowledgeable about
`
`{ROKUIN/00009/00604617}
`
`
`6
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 11 of 20
`
`the graphical user interface (“GUI”) interactions and communication protocols
`used by the Roku Pay application4 (Tandon Decl., ¶¶ 2-3);
`• Wade Brown, Senior System Architect: Mr. Brown is knowledgeable about
`Roku’s streaming players, the Roku OS, how Roku’s software is used in
`conjunction with a display device and the Internet to access media content and
`services, and the High-Definition Multimedia Interface (“HDMI”) used by Roku
`streaming players to display content on a television (Id., ¶ 9);
`• Wim Michiels, Principal Engineer: Mr. Michiels is knowledgeable about Roku’s
`streaming players, the Roku OS, and how Roku’s software is used in conjunction
`with a display device and the Internet to access media content and services (Id., ¶
`10);
`• Cameron Baharloo, Director, Software Engineering: Mr. Baharloo
`is
`knowledgeable about Roku’s streaming players and associated GUI interactions
`involved with the Accused Functionalities (Id., ¶ 11);
`• Robert Burdick, Director, Developer Platform: As an open streaming platform,
`Roku maintains a “Developers” website and certain Developer tools to assist
`publishers and developers in creating custom streaming channels operable on the
`Roku OS.5 Mr. Burdick, as the Director in charge of this platform, is
`knowledgeable about this subject matter (Tandon Decl., ¶ 12);
`• Steve Sprich, Senior Director, Global Product Marketing and Insights: Mr.
`Sprich is knowledgeable about the marketing and advertising of the Accused
`Products (Id., ¶ 13); and
`• Kevin Bright, Senior Director, Financial Planning & Analysis: Mr. Bright is
`knowledgeable about the sales and revenue information related to the Accused
`Products (Id., ¶ 14).
`
`
`
`Each of the Roku witnesses identified above would have to travel approximately 1,450
`
`miles to attend trial and testify in this District, requiring at least six hours of travel time each
`
`4 IOENGINE’s Complaint, in certain instances, cites to the Accused Products’ ability to facilitate
`purchases through Roku Pay. (See, e.g., Compl., ¶¶ 25, 87, 94, 99, 159.)
`5 As alleged support for its direct and indirect infringement allegations, IOENGINE relies upon
`Roku’s Developers website and platform. (See, e.g., Compl., ¶¶ 25, 94-98, 100, 166-170.)
`{ROKUIN/00009/00604617}
`7
`
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 12 of 20
`
`way, meals, and lodging expenses, in addition to time lost from work. (See Royka Decl., Ex. 2D
`
`(Google Maps printout from San Jose, CA to Waco, TX).)
`
`Conversely, there are no willing witnesses that reside within this District. IOENGINE
`
`has no employees or identified witnesses within Texas. Mr. McNulty, IOENGINE’s sole
`
`member and purported sole inventor of the Asserted Patents, lives in Connecticut, and thus will
`
`have to travel a significant distance to testify whether trial is held in this District or NDCA. See
`
`In re Apple Inc., 979 F.3d at 1342 (finding error in giving too much weight to the location of a
`
`few witnesses that “will be required to travel a significant distance no matter where they
`
`testify”).
`
`Because “a substantial number of material witnesses reside within the transferee venue
`
`and the state of California, and no witnesses reside within” WDTX, this factor “weigh[s]
`
`substantially in favor of transfer” to NDCA. Genentech, 566 F.3d at 1345. See also In re
`
`Google LLC, 2021 U.S. App. LEXIS 29137, at *12 (Fed. Cir. Sep. 27, 2021) (“[o]ur cases have
`
`emphasized that when there are numerous witnesses in the transferee venue and the only other
`
`witnesses are far outside the plaintiff’s chosen forum, the witness-convenience factor favors
`
`transfer”); Decapolis Sys., LLC, 6:21-cv-00502, Dkt. No. 30 at 5-7 (finding this factor to favor
`
`transfer where no potential witnesses live in this District and movant’s employees identified as
`
`likely to testify reside in the transferee venue). Moreover, this factor strongly favors transfer
`
`notwithstanding the fact that all Roku-identified witnesses are Roku employees. As the Federal
`
`Circuit noted in Hulu, “[a]lthough an employer’s cooperation in allowing an employee to testify
`
`may diminish certain aspects of inconvenience to the employee witness (for instance, the
`
`employee is not acting contrary to their employer’s wishes), it hardly eliminates the
`
`inconvenience.” In re Hulu, LLC, 2021 U.S. App. LEXIS 22723, at *13; see also In re Juniper
`
`{ROKUIN/00009/00604617}
`
`
`8
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 13 of 20
`
`Networks, Inc., 14 F.4th 1313, 1319 (Fed. Cir. 2021) (finding error where the district court
`
`discounted party witnesses in the transferee district).
`
`2. The Relative Ease of Access to Sources of Proof Favors Transfer.
`
`The relevant evidence in this case was created at Roku’s headquarters in NDCA, not in
`
`Austin. As the accused infringer, Roku’s documents are likely to be the main sources of proof in
`
`this case, used by both parties. And “[c]onsequently, … [this] weighs in favor of transfer [to
`
`NDCA].” In re Genentech, Inc., 566 F.3d 1338, 1345 (Fed. Cir. 2009).
`
`As explained by Mr. Tandon (Tandon Decl., ¶ 7), although Roku stores its documents on
`
`cloud servers, those servers are managed and maintained by Roku’s IT group based in San Jose,
`
`California. This includes documents relating to Roku’s NDCA-based research, design, and
`
`development of the Accused Products, as well as marketing, sales, and financial information for
`
`the Accused Products. Because “the location of document custodians and location where
`
`documents are created and maintained, which may bear on the ease of retrieval,” should be
`
`considered under this factor, the location of sources of proof favors transfer to NDCA. In re
`
`Google LLC, 2021 U.S. App. LEXIS 33789, at *7 (Fed. Cir. Nov. 15, 2021).
`
`In addition, there are no documents stored in Roku’s Austin office or elsewhere in this
`
`District relevant to this case. See Media Chain, LLC, 2021 U.S. Dist. LEXIS 243562, at *5 (this
`
`factor favors transfer where, as here, neither plaintiff nor the inventor of the asserted patents is
`
`based in Texas and the relevant documents are maintained in California). Accordingly, this
`
`private interest factor favors transfer of this case. See Decapolis Sys., LLC, 6:21-cv-00502, Dkt.
`
`No. 30 at 4-5 (finding this factor to favor transfer where “[m]ore sources of proof likely reside
`
`in, and are likely more easily accessed in” the transferee venue).
`
`{ROKUIN/00009/00604617}
`
`
`9
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 14 of 20
`
`3. The Availability of Compulsory Process Favors Transfer or is
`Neutral.
`
`This Court lacks subpoena power over witnesses in California. Under Rule 45 of the
`
`
`
`Federal Rules of Civil Procedure, a court may subpoena a witness to attend trial only: (1) within
`
`100 miles of where the person resides, is employed, or regularly transacts business in person, or
`
`(2) within the state where the person resides, is employed, or regularly transacts business in
`
`person. Fed. R. Civ. P. 45(c)(1). The second private interest factor focuses on “the availability
`
`of compulsory process to secure the attendance of witnesses, particularly non-party witnesses
`
`whose attendance may need to be secured by court order.” 10Tales, Inc., U.S. Dist. LEXIS
`
`96694, at *7-8.
`
`Here, unlike the NDCA, this District lacks subpoena power over any relevant potential
`
`witness in this case. For example, as the Accused Products were designed and developed in
`
`NDCA, subpoena power may be necessary to compel the participation of any former Roku
`
`employees located in that district. Roku is not aware of a single relevant witness located within
`
`the subpoena power of this District. As explained above, although IOENGINE points to Mr.
`
`Scott de Haas in its Complaint, there is no special connection between Mr. de Haas and the
`
`infringement allegations or the Accused Products and Functionalities at issue in this case.
`
`Accordingly, this factor favors transfer to NDCA or is neutral.
`
`4. There Are No Practical Problems Weighing Against Transfer.
`
`The final private interest factor favors transfer because there are no practical problems
`
`weighing against transfer to NDCA. “This factor carries greater weight in cases for which ‘there
`
`is co-pending litigation before the trial court involving the same patent and underlying
`
`technology’ and cases where the trial court is familiar with the underlying patent from prior
`
`litigation.” 10Tales, Inc., 2021 U.S. Dist. LEXIS 96694, at *12. Here, there is no co-pending, or
`
`{ROKUIN/00009/00604617}
`
`
`10
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 15 of 20
`
`prior, litigation before this Court involving IOENGINE’s patents that would potentially weigh
`
`against transfer. IOENGINE currently has separate suits (nearing trial) in the District of
`
`Delaware against PayPal and Ingenico involving patents related to the Asserted Patents, but the
`
`accused technology in those cases does not involve streaming players; rather, it involves
`
`PayPal’s mobile card readers and payment technology. IOENGINE’s separate actions in
`
`Delaware should have no impact on this Court’s analysis of transfer.
`
`Additionally, this case is in its early stages. Roku has responded to the Complaint,
`
`IOENGINE responded to Roku’s Counterclaims, and there has been no substantive motion
`
`practice or claim construction activity that would potentially weigh against transfer. Because
`
`there are no other practical problems that might arise by transferring the case to NDCA, this
`
`factor also favors transfer. See Media Chain, LLC, 2021 U.S. Dist. LEXIS 243562, at * 8
`
`(finding this factor to favor transfer when the case is still in its early stages and notwithstanding
`
`any COVID-19 considerations that may attach in the transferee forum).
`
`C. The Public Interest Factors Favor Transfer to the Northern District of
`California.
`
`1. The Local Interest Factor Weighs Heavily In Favor of Transfer.
`
`The local interest factor weighs heavily in favor of transfer because the Accused Products
`
`and Functionalities were principally designed and developed in NDCA. IOENGINE’s claims,
`
`therefore, implicate the hard work of Roku’s NDCA-based engineers that designed and
`
`developed these products. See Decapolis Sys., LLC, 6:21-cv-00502, Dkt. No. 30 at 11-13
`
`(finding this factor to favor transfer when “the alleged infringing products were likely developed
`
`in the [transferee venue], and th[e] case will call into question the work and reputation of
`
`[movant] and its employees, both of which have a presence in the [transferee venue]”).
`
`{ROKUIN/00009/00604617}
`
`
`11
`
`

`

`Case 6:21-cv-01296-ADA-DTG Document 27 Filed 04/12/22 Page 16 of 20
`
`“This factor most notably regards not merely the parties’ significant connections to each
`
`forum writ large, but rather the ‘significant connection between a particular venue and the events
`
`that gave rise to a suit.’” In re Apple, 979 F.3d at 1344 (quoting In re Acer Am. Corp., 626 F.3d
`
`1252, 1256 (Fed. Cir. 2010)) (emphasis in original). IOENGINE alleges that “Roku’s Streaming
`
`Players…; the Roku OS, and the Roku [GUI] used with the Roku streaming players; products
`
`and systems incorporating the foregoing; and reasonably similar Roku portable products with
`
`streaming capabilities” infringe the Asserted Patents. (Compl., ¶ 23.) As set forth above, the
`
`development of Roku’s streaming players, including their hardware, associated OS and source
`
`code, primarily occurred at Roku’s NDCA headquarters, years prior to Roku’s Austin office
`
`opening in 2014. (Tandon Decl., ¶ 6.) Accordingly, the events that give rise to this suit—
`
`Roku’s research, design, and development of its streaming players—occurred at Roku’s Bay-
`
`area headquarters, giving the NDCA a significant and legitimate interest in this case. See In re
`
`Samsung Elecs. Co., 2 F.4th 1371, 1380 (Fed. Cir. 2021) (finding that the location of research,
`
`design and development are significant factors giving rise to a legitimate localized interest).
`
`Conversely, and apart from filing the present suit in Waco, WDTX has no true
`
`connection to this dispute between IOENGINE and Roku. Not only does IOENGINE and its
`
`sole member, Mr. McNulty, have no ties to Texas, but Roku’s Austin office—IOENGINE’s
`
`alleged venue “hook”—was not even open when the accused Roku streaming players were
`
`developed. This office, therefore, and any engineers employed therefrom, does not give rise to
`
`any local interest in this particular dispute. In re Apple, 979 F.3d at 1345; In re Google, 2021
`
`WL 4427899, at *5.
`
`Further, the fact that Roku streaming playe

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