throbber
Case 1:21-cv-00044-ADA Document 30 Filed 04/20/21 Page 1 of 5
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`FINTIV, INC.
`
`v.
`
`Movant,
`
`STMICROELECTRONICS, INC.,
`
`Respondent.
`
`NO. 1:21-CV-00044-ADA
`
`ORDER
`
`Before the Court is Fintiv, Inc.’s Expedited Motion to Compel Compliance with
`
`Subpoena Directed to Non-Party STMicroelectronics, Inc. (Dkt. No. 1). STMicroelectronics
`
`filed a response (Dkt. No. 17), and included a request for fees under Fed. R. Civ. P. 45(d)(1) and
`
`Fed. R. Civ. P. 37(a)(5)(B) (Dkt. No. 17 at 15). Fintiv filed a reply (Dkt. No. 22). The Court held
`
`a telephonic hearing on January 26, 2021. Having considered the pleadings and counsels’
`
`argument, and for the reasons set forth below, the Court finds that Fintiv’s motion should be
`
`denied, and that under the specific facts of this case STMicroelectronics should recover its
`
`reasonable attorney’s fees and costs incurred in opposing the motion.
`
`Fintiv’s subpoena sought information that is not relevant to its suit against Apple. Under
`
`Rule 26(b)(1), “[p]arties may obtain discovery regarding any nonprivileged matter that is
`
`relevant to any party’s claim or defense and proportional to the needs of the case.” Fed. R. Civ.
`
`P. 26(b)(1) (emphasis added). In the underlying action,1 Fintiv accuses Apple of infringing U.S.
`
`1 Fintiv, Inc. v. Apple, Inc., Case No. 1:19-cv-01238-ADA (W.D. Tex.).
`
`

`

`Case 1:21-cv-00044-ADA Document 30 Filed 04/20/21 Page 2 of 5
`
`Patent No. 8,843,125. The accused technology is the mobile-wallet functionality on Apple
`
`devices, including what is referred to as Near Field Communication (NFC) technology. As
`
`discussed below, from the beginning of the underlying action through discovery in that action,
`
`and even during briefing and hearing in the current action, no evidence has shown that Apple’s
`
`accused functionality uses chips from STMicroelectronics,.
`
`At the August 29, 2019 hearing on Apple’s venue-transfer motion in the underlying
`
`action, Mr. Ravel, counsel for Apple, made it clear that “STMicroelectronics does not supply any
`
`NFC secure element chip or controller used by Apple Pay, Apple Wallet”:2
`
`During discovery in the underlying case—which was substantially completed before
`
`Fintiv filed its motion to compel STMicroelectronics in December 2020—Fintiv did not uncover
`
`any evidence to the contrary. During briefing on this motion, Fintiv admitted that “[t]he answers
`
`and productions from Apple have not indicated that ST is providing the microchips at issue
`
`here.”3 At the hearing in this action, Fintiv initially represented that “STMicroelectronics
`
`manufactures secure elements for the phones that are accused products in this case.”4
`
`STMicroelectroinics responded that “Apple has consistently told Fintiv that Apple does not use
`
`2 Fintiv, Inc. v. Apple, Inc., Case No. 1:19-cv-01238-ADA, Dkt. No. 66, August 29, 2019 Venue Transfer Motion
`Hearing Transcript at 59.
`3 Dkt. No. 22 at 1.
`4 Dkt. No. 27 at 4.
`
`

`

`Case 1:21-cv-00044-ADA Document 30 Filed 04/20/21 Page 3 of 5
`
`the ST chips that would be at issue in this case.”5 The Court asked Fintiv “Do you have any
`
`evidence from someone at Apple that you deposed that – either that STMicroelectronics does
`
`supply anything to do with the NFC secure element or controller or anything that’s relevant to
`
`your infringement case that is used by Apple Pay or Apple Wallet?”6 Fintiv responded that “No.
`
`We do not.”7
`
`Fintiv’s briefing points to a September 2018 website article that mentions
`
`STMicroelectronics and Apple in the same article, but the article states that NXP—not
`
`STMicroelectronics—provides the NFC chips in question. Fintiv had ample opportunity through
`
`discovery of Apple to investigate the statements made in that article and determine whether
`
`STMicroelectronics had relevant information. Nevertheless, in its briefing and at the hearing,
`
`Fintiv has admitted that, despite the discovery it conducted of Apple, it still has no evidence that
`
`STMicrolectronics supplies anything relevant to Apple’s alleged infringement.8
`
`Fintiv has failed to show that it is entitled to compel production from STMicroelectronics
`
`in light of the factors set forth in Wiwa v. Royal Dutch Petroleum Co., 392 F.3d 812, 818 (5th
`
`Cir. 2004). The Court therefore DENIES Fintiv’s motion to compel STMicroelectronics.
`
`The Court is concerned about litigants issuing subpoenas to third parties without any
`
`evidence that the third parties have information relevant to the litigants’ claims or defenses.
`
`Courts are obligated to protect third parties from significant expense resulting from compliance.
`
`Id. at 818 & n.32. This is particularly true when there is no indication that the third party has
`
`relevant information.
`
`5 Id. at 7.
`6 Id. at 10.
`7 Id.
`8 See, e.g., Dkt. No. 22 at 1; Dkt. No. 27 at 10.
`
`

`

`Case 1:21-cv-00044-ADA Document 30 Filed 04/20/21 Page 4 of 5
`
`Federal Rules of Civil Procedure 37(a)(5)(B) and 45(d)(1) make the award of fees
`
`mandatory when denying a motion to compel under these circumstances. Rule 37(a)(5)(B)
`
`provides that when a motion to compel is denied, the party opposing the motion is entitled to
`
`recover its reasonable costs and attorney’s fees incurred in defending the motion, unless the
`
`motion was “substantially justified” or “other circumstances make an award of expenses unjust.”
`
`The United States Supreme Court has defined “substantially justified” to mean “justified in
`
`substance or in the main—that is, justified to a degree that could satisfy a reasonable person.”
`
`Pierce v. Underwood, 487 U.S. 552, 565 (1988) (internal quotation marks omitted). Here, given
`
`that Fintiv was on notice in 2019 through Apple’s representation that STMicroelectronics did not
`
`provide NFC chips to Apple, and Fintiv uncovered no evidence to the contrary after significant
`
`discovery directly from Apple, the Court concludes that Fintiv’s motion was not substantially
`
`justified.
`
`Rule 45(d)(1) required Fintiv to “take reasonable steps to avoid imposing undue burden
`
`or expense on” STMicroelectronics. That rule further requires the Court to enforce this duty:
`
`“The court for the district where compliance is required must enforce this duty and impose an
`
`appropriate sanction—which may include lost earnings and reasonable attorney’s fees—on a
`
`party or attorney who fails to comply.” Fed. R. Civ. P. 45(d)(1). Here, Fintiv moved to compel
`
`compliance with 100% of its subpoena, which asked for a broad range of technical and financial
`
`documents regarding all chips STMicroelectronics provides to Apple, regardless of whether such
`
`chips were relevant to the underlying case against Apple. The Court finds that Fintiv made no
`
`effort to avoid imposing an undue burden on STMicroelectronics.
`
`Therefore, the Court finds that STMicroelectronics should be awarded its reasonable
`
`attorney’s fees and costs incurred in opposing Fintiv’s motion to compel. The Court prefers that
`
`

`

`Case 1:21-cv-00044-ADA Document 30 Filed 04/20/21 Page 5 of 5
`
`the Parties work together to agree on the appropriate amount of such award. No later than May
`
`28, 2021, Counsel for STMicroelectronics is directed to either: (1) notify the Court of the amount
`
`of attorney’s fees and costs agreed to by the Parties, and provide the Court with a proposed order
`
`regarding such award; or (2) file under seal an affidavit, supported by relevant billing statements
`
`and/or invoices, setting forth the specific amount of attorneys’ fees and costs STMicroelectronics
`
`incurred in connection with its efforts to defend against Fintiv’s motion to compel.
`
`Signed on April 20, 2021.
`
`

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