throbber
Case 6:20-cv-00212-ADA Document 36 Filed 08/14/20 Page 1 of 8
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`NEODRON, LTD.,
`
`Plaintiff,
`
`v.
`
`APPLE INC.,
`
`Case No. 6:20-cv-00212-ADA
`
`PATENT CASE
`
`Defendant.
`
`JURY TRIAL DEMANDED
`
`APPLE INC.’S MOTION TO STAY PENDING TRANSFER
`
`WEST\291505239.4
`
`

`

`Case 6:20-cv-00212-ADA Document 36 Filed 08/14/20 Page 2 of 8
`
`Apple respectfully moves for a stay pending a decision on Apple’s pending Motion to
`
`Transfer to the Northern District of California (“the NDCAL”) (Dkt. No. 27).
`
`I.
`
`INTRODUCTION
`
`Both the Federal Circuit and the Fifth Circuit have instructed district courts to prioritize
`
`transfer motions and to address transfer before addressing other substantive issues. However, in
`
`this case, the current schedule calls for the parties to complete time-consuming and expensive
`
`patent disclosures and claim construction activities from September through January. In light of
`
`the appellate mandate to make transfer a “top priority,” these other activities should be stayed
`
`pending a decision on transfer.
`
`II.
`
`BACKGROUND
`
`Neodron is asserting three patents against Apple relating to touch sensing technology and
`
`has accused numerous Apple products as infringing those patents, including fifteen iPhone
`
`models, eleven iPad models, and six Macbook models. The Court held a CMC on June 19, 2020,
`
`and set the Markman hearing in this case for January 15, 2021. On July 2, 2020, Apple timely
`
`filed its Motion to Transfer this case to the NDCAL. After not receiving an opposition brief on
`
`the original due date, Apple contacted Neodron to ascertain the status of the response. Shortly
`
`after the contact from Apple, Neodron filed its opposition and sought Apple’s consent to an
`
`extension of time to July 28, 2020, which Apple provided. Apple filed its Reply brief on August
`
`11th and then promptly filed this Motion to Stay – after confirming Neodron would oppose.
`
`WEST\291505239.4
`
`1
`
`

`

`Case 6:20-cv-00212-ADA Document 36 Filed 08/14/20 Page 3 of 8
`
`III.
`
`ALL CASE ACTIVITY UNRELATED TO TRANSFER SHOULD BE STAYED
`PENDING RESOLUTION OF APPLE’S MOTION TO TRANSFER
`
`A.
`
`The Court Has Inherent Authority to Stay the Case
`
`“The power to stay proceedings is incidental to the power inherent in every court to
`
`control the disposition of the cases on its docket with economy of time and effort for itself, for
`
`counsel, and for litigants.”). Landis v. N. Am. Co., 299 U.S. 248, 254–55, 57 S. Ct. 163 (1936).
`
`Both the Federal Circuit and the Fifth Circuit have noted that transfer motions should be
`
`given “top priority” and should therefore be decided before other substantive issues are
`
`addressed. In re EMC Corp., 501 Fed. Appx. 973, 975-76 (Fed. Cir. 2013) (recognizing “the
`
`importance of addressing motions to transfer at the outset of litigation”); In re Horseshoe Entm’t,
`
`337 F.3d 429, 433 (5th Cir. 2003) (“[I]n our view disposition of that [transfer] motion should
`
`have taken a top priority in handling of this case by the . . . District Court.”); see also In re
`
`Fusion-IO, Inc., 489 Fed. Appx. 465, 466 (Fed. Cir. 2012) (“We fully expect, however, for
`
`Fusion-IO 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”).
`
`To effectuate this appellate mandate, district courts have agreed to stay cases pending
`
`decisions on transfer. See Secure Axcess, LLC v. Nintendo of Am., Inc., No. 2:13-cv-00032, Dkt.
`
`No. 133 (E.D. Tex. Feb. 10, 2014) (granting a stay pending resolution of severance and transfer
`
`issues where case was in early stages and claim construction briefing had just begun); DSS Tech.,
`
`Mgmt. Inc., v. Apple Inc., No. 6:13-cv-919, Dkt. No. 83 (E.D. Tex. Oct. 28, 2014); Anza Tech.,
`
`Inc., v. Xilinx, Inc., 17-cv-687, 2017 WL 10379350 (D. Col. Oct. 16, 2017); Univ. of S. Florida
`
`Res. Found. Inc. v. Fujifilm Med. Sys. USA, Inc., No. 8:16-cv-1194, 2017 WL 4155344, at *1
`
`(M.D. Fla. Aug. 29, 2017) (granting motion to stay deadlines pending resolution of whether
`
`WEST\291505239.4
`
`2
`
`

`

`Case 6:20-cv-00212-ADA Document 36 Filed 08/14/20 Page 4 of 8
`
`venue was proper in the district); B.E. Tech., LLC v. Sony Computer Entm’t Am., LLC, No. 12-
`
`cv-2828, 2013 WL 524893, at*1 (W.D. Tenn. Feb. 11, 2013) (“Staying the proceedings--
`
`including the Local Patent Rule disclosures and fact discovery--will allow the Court to properly
`
`decide the pending Motions to Change Venue in light of judicial economy and comity.”)1
`
`The Federal Circuit has recognized the importance of staying cases during the pendency
`
`of transfer motions as a means of upholding 28 U.S.C. 1404(a)’s intent to “prevent the waste ‘of
`
`time, energy, and money’ and protect litigants, witnesses and the public against unnecessary
`
`inconvenience and expense [. . . ] when defendants are forced to expend resources litigating
`
`substantive matters in an inconvenient venue while a motion to transfer lingers unnecessarily on
`
`the docket.” In re Google Inc., 2015 WL 5294800, at *1-2 (Fed. Cir. 2015) (internal citation
`
`omitted) (granting writ of mandamus and ordering a magistrate judge in the Eastern District of
`
`Texas to stay proceedings pending final resolution of a transfer motion filed 8 months prior and
`
`issue a decision on transfer within 30 days).
`
`B.
`
`All Relevant Factors Favor a Stay Pending a Decision on Transfer
`
`In this District, courts typically consider three factors in determining whether a stay is
`
`warranted: (1) any potential prejudice to the non-moving party; (2) the hardship and inequity to
`
`the moving party if the action is not stayed; and (3) the judicial resources saved by avoiding
`
`duplicative litigation. Yeti Coolers, LLC v. Home Depot U.S.A., Inc., 1:17-cv-342, 2018 WL
`
`2122868, at *1 (W.D. Tex. Jan. 8, 2018); B & D Produce Sales, LLC v. Packman1, Inc., No. SA-
`
`16-CV-99-XR, 2016 WL 4435275, at *1 (W.D. Tex. Aug. 19, 2016). Here, all three factors
`
`favor a stay.
`
`1 This Court has similarly recognized the utility of a stay pending transfer in the context of multi-
`district litigation. See also Sparling v. Doyle, 2014 WL 12489985 (March 3, 2014) (granting
`temporary stay until MDL panel renders decision on motion for transfer and consolidation).
`
`WEST\291505239.4
`
`3
`
`

`

`Case 6:20-cv-00212-ADA Document 36 Filed 08/14/20 Page 5 of 8
`
`1.
`
`Factor One: A Stay Will Not Prejudice Neodron
`
`Neodron will not suffer any prejudice as a result of a stay pending a decision on transfer.
`
`In fact, should the case be transferred, Neodron will benefit from proceeding once under the
`
`Markman procedures employed by the transferee forum. Avoiding duplication will benefit both
`
`Apple and Neodron.
`
`Should Neodron claim that the short stay sought here would cause it prejudice, any such
`
`argument lacks merit. First, a delay in Neodron’s attempt to recover money damages cannot, of
`
`itself, constitute sufficient prejudice to deny a stay because a plaintiff will always face that
`
`possibility when a stay is ordered. SanDisk Corp. v. Phison Elecs. Corp., 538 F. Supp. 2d 1060,
`
`1067 (W.D. Wisc. 2008) (“plaintiff’s only real ‘injury’ is that it will have to wait for any money
`
`damages, which is always the case when a stay is imposed.”). Second, Apple is seeking a stay of
`
`a very limited duration so that transfer issues are decided before other substantive issues are
`
`addressed. Even assuming the Court takes 60 days to resolve the transfer issue, this case could
`
`still go to trial within two years of filing. Neodron cannot seriously claim that a two year
`
`schedule to trial is prejudicial. Therefore, this factor strongly favors a stay.
`
`2.
`
`Factor Two: Apple Will Suffer Hardship Absent a Stay
`
`The Federal Circuit and Fifth Circuit agree that deciding transfer should be the Court’s
`
`top priority in handling the case. EMC Corp., 501 Fed. Appx. at 975-76; Horseshoe Entm’t, 337
`
`F.3d at 433. Moving forward now with patent disclosures and claim construction activities in
`
`this case will risk the very same “waste of time, energy and money” the Federal Circuit
`
`cautioned against in EMC. EMC Corp., 501 Fed. Appx. at 975-76. Indeed, if this case is
`
`transferred to the NDCAL, that court has its own local rules and Markman procedures that differ
`
`from those employed by this Court. In all likelihood, Apple will need to redo its claim
`
`construction submissions to comply with the NDCAL rules. In addition, should this Court issue
`
`WEST\291505239.4
`
`4
`
`

`

`Case 6:20-cv-00212-ADA Document 36 Filed 08/14/20 Page 6 of 8
`
`claim constructions before deciding transfer, the transferee court may wish to conduct its own
`
`analysis and hearing, thus causing additional burden and expense. Conversely, by staying the
`
`Markman activity in this case for a short period of time while first deciding transfer, the risk of
`
`undue hardship is completely eliminated.
`
`3.
`
`Factor Three: A Stay Will Conserve Judicial Resources
`
`A stay pending a decision on transfer will conserve judicial resources as it eliminates the
`
`risk that the Markman proceedings will be conducted twice in two different courts. A stay will
`
`also avoid potential confusion as, absent a stay, a decision on transfer could be issued during the
`
`middle of claim construction briefing in this case. That could leave Apple and Neodron in a
`
`situation where one set of briefs is filed in accordance with this Court’s Order Governing
`
`Proceedings only to have subsequent briefing procedures governed by the NDCAL patent local
`
`rules, which differ from this Court’s. A stay would also eliminate this likely confusion and
`
`uncertainty.
`
`IV.
`
`CONCLUSION
`
`For the foregoing reasons, the Court should stay all case activity unrelated to transfer
`
`until a decision on transfer is rendered.
`
`Dated: August 14, 2020
`
`Respectfully submitted,
`
`/s/ John M. Guaragna
`John M. Guaragna
`Texas Bar No 24043308
`Brian K. Erickson
`Texas Bar No. 24012594
`DLA PIPER LLP (US)
`401 Congress Avenue, Suite 2500
`Austin, TX 78701-3799
`Tel: 512.457.7125
`Fax: 512.457.7001
`john.guaragna@dlapiper.com
`
`5
`
`WEST\291505239.4
`
`

`

`Case 6:20-cv-00212-ADA Document 36 Filed 08/14/20 Page 7 of 8
`
`brian.erickson@dlapiper.com
`
`Mark Fowler (pro hac vice)
`Robert Buergi (pro hac vice)
`DLA Piper LLP (US)
`2000 University Avenue
`East Palo Alto, CA 94303
`Tel: 650-833-2000
`Fax: 650-833-2100
`
`Erin Gibson (pro hac vice)
`DLA Piper LLP (US)
`401 B Street, Suite 1700
`San Diego, CA 92101
`Tel: 619-699-2700
`Fax: 619-699-2701
`
`James M. Heintz (pro hac vice)
`DLA Piper LLP (US)
`One Fountain Square
`11911 Freedom Drive, Suite 300
`Reston, VA 20190
`Tel: 703-773-4000
`Fax: 703-773-5000
`
`Nandan Padmanabhan (pro hac vice)
`DLA Piper LLP (US)
`2000 Avenue of the Stars, Suite 400
`North Tower
`Los Angeles, CA 90067
`Tel: 310-595-3000
`Fax: 310-595-3300
`
`Erin McLaughlin (pro hac vice)
`DLA Piper LLP (US)
`1251 Avenue of the Americas, 27th Floor
`New York, NY 10020
`Tel: 212-335-4500
`Fax: 212-335-4501
`
`ATTORNEYS FOR DEFENDANT APPLE INC.
`
`WEST\291505239.4
`
`6
`
`

`

`Case 6:20-cv-00212-ADA Document 36 Filed 08/14/20 Page 8 of 8
`
`CERTIFICATE OF CONFERENCE
`
`Pursuant to Local Rule CV-7(i), counsel for Apple has conferred with counsel for
`
`Neodron in a good-faith effort to resolve the matter presented herein. Counsel for Neodron
`
`opposes the instant Motion.
`
`/s/ John M. Guaragna
`John M. Guaragna
`
`CERTIFICATE OF SERVICE
`
`The undersigned certifies that on this 14th day of August 2020, all counsel of record who
`
`are deemed to have consented to electronic service are being served with a copy of this document
`
`by electronic mail.
`
`/s/ John M. Guaragna
`John M. Guaragna
`
`WEST\291505239.4
`
`7
`
`

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