throbber
Case 5:19-cv-00036-RWS Document 107 Filed 10/22/19 Page 1 of 11 PageID #: 4769
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`TEXARKANA DIVISION
`
`
`Plaintiff,
`
`Case No. 5:19-cv-00036-RWS
`
`JURY TRIAL DEMANDED
`
`
`
`
`MAXELL, LTD.,
`
`v.
`
`APPLE INC.,
`
`Defendant.
`
`
`
`MAXELL, LTD.’S OPPOSITION TO APPLE INC.’S
`MOTION TO STAY PENDING DECISION ON ITS
`MOTION TO TRANSFER VENUE PURSUANT TO 28 U.S.C. § 1404(a)
`
`Plaintiff Maxell, Ltd. (“Maxell”), by and through its undersigned counsel, hereby submits
`
`this response in opposition to Defendant Apple Inc.’s (“Apple”) Motion to Stay Pending Decision
`
`on its Motion to Transfer Venue Pursuant to 28 U.S.C. § 1404(a) (“Motion to Stay”) (D.I. 97).
`
`I.
`
`INTRODUCTION
`
`Apple’s motion is nothing more than Apple’s formal request that its practice in this case of
`
`delay, delay, delay be approved and encouraged. Although explicitly prohibited by this Court’s
`
`rules, Apple has essentially already implemented a unilateral stay. It has been stonewalling
`
`discovery and has attempted to delay every effort by Maxell to move this case forward to resolution
`
`on the merits. Nowhere is this more plainly stated than in Apple’s opposition to Maxell’s Motion
`
`for Leave to Supplement Infringement Contentions (D.I. 96)—which even Apple has admitted it
`
`does not oppose on its merits.
`
`Apple has finally acknowledged its practice by now moving the Court seeking an
`
`unnecessary stay. It does so under the guise of conserving resources on proceedings that may have
`
`to be redone in the Northern District of California. Given the Court’s indication that it will issue
`
`
`
`

`

`Case 5:19-cv-00036-RWS Document 107 Filed 10/22/19 Page 2 of 11 PageID #: 4770
`
`
`an Order in the short term, and the stage of the case, however, there is no such efficiency to be
`
`gained by a stay. The work the parties are currently doing on the case—discovery and claim
`
`construction—will have to be done regardless of location, and there is no reason to believe it would
`
`have to be redone if the case were transferred. Further, should the case remain in this District,
`
`which Maxell believes is appropriate, there is also no reason to pause case activities. Apple does
`
`not want to conserve resources. It simply wants to delay the case by any means possible.
`
`Contrary to the substance of Apple’s Motion to Stay, Apple is not entitled to a stay merely
`
`because it filed a motion to transfer. In fact, this Court’s discovery order requires active
`
`participation in discovery, even when motions to transfer are pending. See D.I. 42, Discovery
`
`Order at ¶ 10 (“No Excuses…Absent court order to the contrary, a party is not excused from
`
`disclosure because there are pending motions to dismiss, to remand or to change venue.”)
`
`(emphasis added). Nevertheless, Apple has failed to establish that any of the relevant factors weigh
`
`in favor of a stay. Rather, Maxell will suffer significant prejudice if the stay is granted because,
`
`among other things, a stay will delay Maxell’s day in court while Apple continues to infringe on
`
`Maxell’s patents, causing Maxell and its licensees substantial harm. Apple cannot complain that it
`
`is being prejudiced by continuing case preparation before this Court. Whether or not this case is
`
`transferred, discovery and claim construction must proceed. In other words, the stay would prevent
`
`nothing because everything that needs to be done (e.g., discovery and claim construction) will still
`
`need to be done whether the case is transferred or not. All a stay would do is delay getting these
`
`thing done. Because Apple has not articulated any need to stay this case, the Court should deny
`
`Apple’s Motion.
`
`II.
`
`APPLICABLE LAW
`
`“The district court has the inherent power to control its own docket, including the power
`
`to stay proceedings.” Soverain Software LLC v. Amazon.com, Inc., 356 F. Supp. 2d 660, 662 (E.D.
`2
`
`
`
`

`

`Case 5:19-cv-00036-RWS Document 107 Filed 10/22/19 Page 3 of 11 PageID #: 4771
`
`
`Tex. 2005). In deciding whether to stay a proceeding, the Court “must weigh competing interests
`
`and maintain an even balance.” Landis v. North American Co., 299 U.S. 248, 254-255 (1936). In
`
`particular, the Court “must first identify a pressing need for the stay, and then balance those
`
`interests against interests frustrated by the action.” In re Sacramento Mun. Util. Dist., 395
`
`Fed.Appx. 684, 687–88 (Fed. Cir. 2010) (citing Cherokee Nation of Okla. v. United States, 124
`
`F.3d 1413, 1416 (Fed. Cir. 1997)). In the Fifth Circuit, “the moving party bears a heavy burden to
`
`show why a stay should be granted absent statutory authorization.” Coastal (Bermuda) Ltd. v. E.W.
`
`Saybolt & Co., Inc., 761 F.2d 198, 203 n.6 (5th Cir. 1985). In deciding whether to stay litigation,
`
`courts typically consider: (1) whether a stay will unduly prejudice or present a clear tactical
`
`disadvantage to the nonmoving party, (2) whether a stay will simplify the issues in question and
`
`trial of the case, and (3) whether discovery is complete and whether a trial date has been set.
`
`Soverain Software, 356 F. Supp. 2d at 662. “Absent court order to the contrary, a party is not
`
`excused from disclosure because there are pending motions to dismiss, to remand or to change
`
`venue.” D.I. 42, Discovery Order at ¶ 10.
`
`III. ARGUMENT
`A.
`
`Apple Does Not Cite to Any Case Law that Supports its Motion
`
`None of the cases cited by Apple support its request for a stay in this case. In fact, Apple’s
`
`Motion to Stay does not cite to a single case that states “all proceedings should be stayed pending
`
`disposition of a transfer motion,” as Apple asserts. Motion at 3. For example, in In re Fusion-IO,
`
`petitioner requested that the Federal Circuit transfer a case from the Eastern District of Texas to
`
`the District of Utah. 489 F. Appx. 465 (Fed. Cir. 2012). The district court had not addressed the
`
`merits of petitioner’s motion for transfer; it had only severed petitioner’s claims from the claims
`
`against other defendants and denied petitioner’s motion to transfer without prejudice to refile the
`
`same motion in the new case. Id. The Federal Circuit declined to transfer the case before the district
`
`
`
`3
`
`

`

`Case 5:19-cv-00036-RWS Document 107 Filed 10/22/19 Page 4 of 11 PageID #: 4772
`
`
`court had weighed the facts and considerations relevant to petitioner’s transfer motion, and stated
`
`that it “fully expect[ed]” petitioner “to promptly request transfer in the lead case along with a
`
`motion to stay proceedings pending disposition of the transfer motion, and for the district court to
`
`act on those motions before proceeding to any motion on the merits of the action.” Id. at 465-466.
`
`Thus, In re Fusion-IO stands only for the proposition that pending motions to transfer should be
`
`promptly resolved. But that proposition is not in dispute here, as neither Maxell nor this Court
`
`have ever suggested otherwise. It certainly does not hold that all proceedings should be stayed
`
`pending disposition of a transfer motion, no matter how Apple spins the case.
`
`The liberties Apple takes with the case law continue with its citation to In re Google Inc.,
`
`2015 WL 5294800 (Fed. Cir. July 16, 2015). In this case, petitioner filed a motion to transfer
`
`venue, and the district court proceeding continued for eight months without a ruling on the motion
`
`to transfer. Id. at *1. The Federal Circuit emphasized the importance of addressing motions to
`
`transfer in a timely manner and stated that the district court’s refusal to consider the merits of its
`
`transfer motion was improper. Id. at *1-2. Therefore, the Federal Circuit ordered the magistrate to
`
`rule on the motion to transfer within 30 days and to stay all proceedings pending completion of
`
`the transfer matter. Id. at *2. Here, however, the motion to transfer has not been pending for eight
`
`months, or anything near that. Apple filed its motion to transfer on August 9, 2019, and briefing
`
`was complete on September 6, 2019. (D.I. 57. 65, 69, and 76). The Court promptly held a hearing
`
`concerning Apple’s motion to transfer on September 17, 2019, less than two weeks after briefing
`
`on the motion was complete. (D.I. 80). There is no evidence that this Court has delayed or refused
`
`to consider the merits of Apple’s transfer motion. If there has been any delay, it has been on
`
`Apple’s part, as this case was filed on March 15, 2019 but Apple did not move to transfer until
`
`nearly 5 months later on August 9, 2019 after previously requesting this Court to rule on its
`
`substantive motion to dismiss. Importantly, In re Google also does not hold that all proceedings
`4
`
`
`
`

`

`Case 5:19-cv-00036-RWS Document 107 Filed 10/22/19 Page 5 of 11 PageID #: 4773
`
`
`should be stayed pending disposition of a transfer motion.
`
`In In re Nintendo Co., petitioners moved to sever and stay the claims against Nintendo’s
`
`retailers and transfer the case against Nintendo from the Eastern District of Texas to the Western
`
`District of Washington. 544 F. Appx. 934, 936 (Fed. Cir. 2013). Petitioners then filed a second
`
`motion to sever, this time seeking to sever all non-Nintendo product claims. Id. The district court
`
`rejected the motion to sever the non-Nintendo claims against the retailers and found the motion to
`
`sever the retailers and transfer the case against Nintendo moot. Id. The Federal Circuit noted that
`
`the district court made these judgments without considering the merits (i.e., without considering
`
`whether the transferee venue was clearly more convenient for trial of the claims against Nintendo).
`
`Id. at 941. As a result, the Federal Circuit ordered the district court to analyze whether the litigation
`
`had any meaningful connection to the Eastern District of Texas. A proper reading of In re Nintendo
`
`Co. (and the cases cited therein) again stands for the proposition that motions to transfer should be
`
`addressed promptly—something not in contention here. It does not hold that all proceedings should
`
`be stayed pending disposition of a transfer motion. Similarly, In re EMC Corp. stands solely for
`
`the proposition that transfer motions should be addressed “at the outset of litigation” (501 F. Appx.
`
`973, 975 (Fed. Cir. 2013)), not that cases should be stayed pending disposition of a transfer motion.
`
`In Nexus Display Technologies LLC v. Dell, Inc., the Court merely stated that Dell “could
`
`have requested a stay” pending a ruling on its transfer motion. 2015 WL 5043069, at *5, n. 4 (E.D.
`
`Tex. Aug. 25, 2015). A party’s ability to request a stay and whether a court should actually grant
`
`a stay are two entirely different matters, and Nexus Display says nothing about whether such a stay
`
`was actually warranted. Accordingly, none of the cases Apple cited support the contention that
`
`“all proceedings should be stayed pending disposition of its transfer motion,” as Apple states.
`
`Motion to Stay at 3.
`
`
`
`5
`
`

`

`Case 5:19-cv-00036-RWS Document 107 Filed 10/22/19 Page 6 of 11 PageID #: 4774
`
`
`B. Maxell Will Be Prejudiced by a Stay
`
`Apple has no intention of complying with its discovery obligations or of litigating this case
`
`on the merits. As a result, Apple does not see a failure to move this case forward as any sort of
`
`prejudice. Yet Apple’s suggestion that Maxell will not be prejudiced or disadvantaged by a stay
`
`(Motion to Stay at 4) is contradicted by the undisputed facts. This case has been pending for over
`
`seven months, and further delay of the discovery schedule would interfere with the “just, speedy,
`
`and inexpensive determination” of this action. Fed. R. Civ. P. 1. The prejudice that would result
`
`from even a short delay is obvious—the current case schedule would be destroyed, and Apple will
`
`be able to further defer its discovery obligations, as it has attempted to do throughout this case
`
`(with woefully deficient document and source code productions). Moreover, the Markman process,
`
`which has been under way for weeks, would come to a complete stop. The parties are already set
`
`to complete claim construction discovery, including expert depositions, by November 6, 2019, just
`
`as briefing on Apple’s Motion to Stay would be finished. Moreover, there is no doubt that, were
`
`transfer granted, Apple will attempt to spin a stay in this case into an argument before the Northern
`
`District of California that an extended case schedule is somehow warranted because of the work
`
`left to be done in the case. To the contrary, were Apple finally to comply with its discovery
`
`obligations, document production and interrogatory responses would be nearing completion. Even
`
`if a transfer were warranted (and it is not), the interests of justice will be best served by dealing
`
`with that contingency when and if it occurs, rather than putting inevitable litigation tasks
`
`pointlessly on hold.
`
`Apple’s argument that Maxell will not be prejudiced because Maxell does not practice the
`
`asserted patents or otherwise compete with Apple is similarly unavailing. First, this Court has
`
`acknowledged that entities which do not compete are nevertheless prejudiced by a stay. Realtime
`
`Data LLC v. Actian Corporation, No. 6:15-cv-463, 2016 WL 3277259, at *2 (E.D. Tex. June 14,
`6
`
`
`
`

`

`Case 5:19-cv-00036-RWS Document 107 Filed 10/22/19 Page 7 of 11 PageID #: 4775
`
`
`2016) (stating that plaintiff, a non-practicing entity, would be prejudiced by a stay because plaintiff
`
`“has an interest in the timely enforcement of its patent rights.”). Moreover, Maxell’s licensees, the
`
`users of the technology of the Asserted Patents, compete for market share with Apple. These
`
`licensees took a license from Maxell so that they could rely on the advantages of the technology
`
`of the asserted patents in order to gain a competitive edge in the marketplace. A stay would allow
`
`Apple additional time to use the technology of the asserted patents without a license, further
`
`threatening and eroding the market share of Maxell’s licensees. This in turn causes direct and
`
`substantial harm to Maxell as a licensor, including but not limited to damaged relationships with
`
`Maxell’s licensees who paid for the competitive advantage of the asserted patents. By contrast,
`
`Apple fails to identify any prejudice that would be caused by continuing trial preparations here.
`
`See Evolutionary Intelligence LLC v. Facebook, Inc., No. 6:12-cv-784, 2013 WL 12144118, at *2
`
`(E.D. Tex. Feb. 27, 2013) (denying motion to stay pending motion to transfer in part because
`
`“Defendants have not identified any hardship or inequity that would result if these actions are not
`
`stayed”). Maxell is prepared to proceed under the existing case schedule, and further delay of the
`
`proceedings will prejudice Maxell and not further the ultimate resolution of this matter.1
`
`C.
`
`A Stay Will Not Simplify the Issues
`
`Apple’s motion to transfer is not a motion to dismiss. Even if Apple’s motion to transfer is
`
`granted, this litigation will continue, and Apple’s discovery burden will remain the same. Fed. R.
`
`Civ. P. 26(b)(1). Document productions, fact depositions, and the claim construction process must
`
`occur in this action, whether the case is tried here or in California. The substance of each of these
`
`activities will not change if the case is transferred to California, nor will the substantive issues of
`
`
`1 Indeed, Apple has been trying to delay resolution of this dispute since 2013. Apple employed its delay tactics first
`through disingenuous negotiations, then through insincere offers to discuss business prospects, and now with
`discovery misconduct. This is just another step in Apple’s years-long effort to avoid paying for the intellectual
`property it has been knowingly using for over 6 years.
`
`7
`
`
`
`

`

`Case 5:19-cv-00036-RWS Document 107 Filed 10/22/19 Page 8 of 11 PageID #: 4776
`
`
`infringement, validity, and damages. Even if this case were to be transferred, continuing to work
`
`now will permit the case to be transferred with more of the discovery out of the way. Indeed,
`
`should it be transferred, discovery will continue until the case schedule is later modified by the
`
`transferee court. See Mondis Tech. Ltd. v. LG Elecs., Inc., No. 2:14-cv-702-JRG, 2015 WL
`
`11117316, at *1 (E.D. Tex. June 9, 2015) (explaining that, before and after transfer, “all pending
`
`deadlines—except those for hearings and trial—will remain in effect until [the transferee] court
`
`enters an order altering such deadlines”).
`
`Moreover, the Northern District of California’s local patent rules are “nearly identical” to
`
`this District’s local patent rules, meaning that the discovery conducted in this District will be
`
`equally applicable if the case is ultimately transferred. See Edward D. Ioli Trust v. Avigilon Corp.,
`
`No. 2:10-cv-605, 2012 WL 5830711, at *2 (E.D. Tex. Nov. 16, 2012) (stating that the scope of the
`
`Northern District of California’s Patent Local Rule 3.4 governing document discovery “is nearly
`
`identical to this District’s P.R. 3-4(a) and was the source from which this District’s P.R. 3-4(a)
`
`was originally crafted.”). The same is true of claim construction. There is absolutely no reason
`
`why transfer of the case should alter the parties’ claim construction positions. A stay would do
`
`nothing other than create delay by pushing discovery and claim construction down the road,
`
`procrastinating on necessary work with no resource savings or efficiency gains for anyone.
`
`D.
`
`The Stage of the Case Disfavors a Stay
`
`In accordance with the Local Rules and the Docket Control Order, Maxell has expended
`
`significant time, resources, and expense engaging in discovery with Apple, including substantially
`
`completing its document production, reviewing Apple’s document production, reviewing source
`
`code, exchanging initial and supplemental infringement contentions, invalidity contentions,
`
`interrogatory responses, and privilege logs, and noticing and beginning the process of scheduling
`
`30(b)(6) depositions. Both parties have also served significant third-party discovery. And the
`8
`
`
`
`

`

`Case 5:19-cv-00036-RWS Document 107 Filed 10/22/19 Page 9 of 11 PageID #: 4777
`
`
`parties have already exchanged preliminary proposed claim construction and extrinsic evidence
`
`supporting the same pursuant to P.R. 4-2, exchanged expert declarations in support of their claim
`
`construction positions pursuant to P.R. 4-3(b), prepared and filed the Joint Claim Construction and
`
`Prehearing Statement pursuant to P.R. 4-3(a), and scheduled and begun conducting expert
`
`depositions on claim construction issues. The Court has held a case management conference, set a
`
`date for a Markman hearing (January 8, 2020), and set a date for trial (October 26, 2020). The
`
`well-developed posture of the case weighs against a stay. Cummins-Allison Corp. v. SBM Co.,
`
`Ltd., No. 9:07-cv-196, 2008 WL 11348281, at *2 (E.D. Tex. May 21, 2008) (denying stay where
`
`parties exchanged infringement contentions, invalidity contentions, and preliminary proposed
`
`claim construction, and the court set aside dates for a Markman hearing and trial); Alacritech, Inc.
`
`v. CenturyLink, Inc., No. 2:16-cv-00693, 2017 WL 4231459, at *2 (E.D. Tex. Sept. 22, 2017)
`
`(denying stay because a stay would “clearly affect the parties’ ability to prepare for trial” which
`
`was nine months away).
`
`IV. CONCLUSION
`
`It is abundantly clear that the only effect a stay would have is to delay resolution of this
`
`case, prejudicing Maxell and confirming for Apple that delay, delay, delay is a viable litigation
`
`strategy. The Court should make clear to Apple that this is not so. Maxell is entitled to timely
`
`enforcement of its patent rights, and Apple has not shown that it will suffer any prejudice if the
`
`stay is denied. None of the cases cited by Apple support its request for a stay in this case.
`
`Accordingly, Maxell respectfully requests that the Court deny Apple’s Motion to Stay.
`
`Dated: October 22, 2019
`
`By:
`
`/s/ Jamie B. Beaber
`Geoff Culbertson
`Kelly Tidwell
`Patton, Tidwell & Culbertson, LLP
`2800 Texas Boulevard (75503)
`Post Office Box 5398
`Texarkana, TX 75505-5398
`
`
`
`9
`
`

`

`Case 5:19-cv-00036-RWS Document 107 Filed 10/22/19 Page 10 of 11 PageID #: 4778
`
`
`Telephone: (903) 792-7080
`Facsimile: (903) 792-8233
`gpc@texarkanalaw.com
`kbt@texarkanalaw.com
`
`Jamie B. Beaber
`Alan M. Grimaldi
`Kfir B. Levy
`James A. Fussell, III
`Baldine B. Paul
`Tiffany A. Miller
`Saqib J. Siddiqui
`Bryan C. Nese
`William J. Barrow
`Alison T. Gelsleichter
`Clark S. Bakewell
`MAYER BROWN LLP
`1999 K Street, NW
`Washington, DC 20006
`Telephone: (202) 263-3000
`Facsimile: (202) 263-3300
`jbeaber@mayerbrown.com
`agrimaldi@mayerbrown.com
`klevy@mayerbrown.com
`jfussell@mayerbrown.com
`bpaul@mayerbrown.com
`tmiller@mayerbrown.com
`ssiddiqui@mayerbrown.com
`bnese@mayerbrown.com
`wbarrow@mayerbrown.com
`agelsleichter@mayerbrown.com
`cbakewell@mayerbrown.com
`
`Robert G. Pluta
`Amanda Streff Bonner
`MAYER BROWN LLP
`71 S. Wacker Drive
`Chicago, IL 60606
`(312) 782-0600
`rpluta@mayerbrown.com
`asbonner@mayerbrown.com
`
`Counsel for Plaintiff Maxell, Ltd.
`
`
`
`10
`
`

`

`Case 5:19-cv-00036-RWS Document 107 Filed 10/22/19 Page 11 of 11 PageID #: 4779
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned certifies that all counsel of record who are deemed to have consented to
`electronic service are being served this 22nd day of October, 2019, with a copy of this document
`via the Court’s CM/ECF system.
`
`
`
`
`/s/ Jamie B. Beaber
`Jamie B. Beaber
`
`
`
`
`
`
`
`
`
`

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