throbber
Case 5:19-cv-00036-RWS Document 39 Filed 06/18/19 Page 1 of 9 PageID #: 464
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`TEXARKANA DIVISION
`
`
`MAXELL, LTD.,
`
`v.
`
`APPLE INC.,
`
`Plaintiff,
`
`Defendant.
`
`Civil Action No. 5:19-cv-00036-RWS
`
`JURY TRIAL DEMANDED
`
`
`
`PLAINTIFF MAXELL, LTD.’S SUR-REPLY IN OPPOSITION TO DEFENDANT
`APPLE INC.’S MOTION FOR PARTIAL DISMISSAL OF PLAINTIFF’S COMPLAINT
`FOR FAILURE TO STATE A CLAIM
`
`

`

`Case 5:19-cv-00036-RWS Document 39 Filed 06/18/19 Page 2 of 9 PageID #: 465
`
`Apple’s Reply confirms that its motion is based on gamesmanship rather than principle.
`
`Its strategy is to cherry-pick excerpts from the Complaint, omit the relevant context, and feign
`
`ignorance of the surrounding circumstances.
`
`Apple’s tactic fails because it is built on grossly incorrect legal standards. The correct
`
`legal standard to state a claim is mere plausibility. See Bell Atlantic Corp. v. Twombly, 550 U.S.
`
`544, 570 (2007). Notice pleading “do[es] not require heightened fact pleading of specifics.” Id.
`
`Rather, all that is required is that the Complaint sets out “enough facts to state a claim to relief
`
`that is plausible on its face.” Id.
`
`Moreover, Apple has no legal basis to complain that the Opposition includes some
`
`additional details adding color to the Complaint. To the extent any of those details are absent
`
`from the Complaint, they are readily permissible, not for the purpose of supplementing the
`
`Complaint, but for illustrating that the allegations therein are plausible. See Early v. Bankers Life
`
`& Cas. Co., 959 F.2d 75, 79 (7th Cir. 1992) (“a plaintiff is free, in defending against a motion to
`
`dismiss, to allege without evidentiary support any facts he pleases that are consistent with the
`
`complaint, in order to show that there is a state of facts within the scope of the complaint that if
`
`proved (a matter for trial) would entitle him to judgment.”). Thus, to the extent Maxell’s
`
`Opposition contains any color beyond the Complaint, that is unobjectionable.
`
`Under the proper legal standards, the Complaint states a claim for willful and induced
`
`infringement that is plainly “plausible on its face.” Twombly, 550 U.S. at 570. The details in
`
`Maxell’s opposition confirm this. The Court should reject Apple’s gamesmanship and deny the
`
`motion to dismiss.
`
`
`
`1
`
`

`

`Case 5:19-cv-00036-RWS Document 39 Filed 06/18/19 Page 3 of 9 PageID #: 466
`
`I.
`
`ARGUMENT
`A.
`
`The Complaint Plausibly Alleges Apple’s Specific Intent.
`
`Apple continues to characterize Maxell’s references to Apple’s websites as generic, but
`
`that does not make them so. The allegations in the Complaint provide ample detail to inform
`
`Apple of what products, functionality, and user communications form the basis of the claims. For
`
`example, consider the allegations regarding the ’317 Patent.
`
` The Complaint includes allegations that the iPhone XS includes Apple’s “Maps”
`
`software that “allows users to access location information, including the present
`
`location of the device and orientation of the device and use such information to
`
`provide walking navigation information and/or share location.” Compl. at ¶24.
`
` The Complaint includes annotated “excerpts from Apple’s websites [to] provide non-
`
`limiting
`
`examples
`
`of
`
`the
`
`iPhone XS
`
`infringing.”
`
`Id.
`
`(citing
`
`https://www.apple.com/ios/maps/). This instructional material is plainly intended to
`
`promote customer use of the described features. Indeed, it includes statements
`
`directed to potential users, like “You’ll also be able to get where you’re going with
`
`improved routes,” and “you can get detailed directions.” Id. (emphasis added).
`
` The Complaint further includes allegations that “Apple’s customers who purchase
`
`devices and components thereof and operate such devices and components in
`
`accordance with Apple’s instructions directly infringe” and “Apple instructs its
`
`customers through at least user guides or websites, such as those located at…
`
`https://www.apple.com/ios/maps/.” Id. at 24, 27; see also Opp. 4-6 (providing
`
`additional examples for other patents). And that link is to the very same web page
`
`excerpted just three paragraphs prior.
`
`
`
`2
`
`

`

`Case 5:19-cv-00036-RWS Document 39 Filed 06/18/19 Page 4 of 9 PageID #: 467
`
`Despite all this, Apple still argues that it is “left to guess what Maxell’s theory of specific intent
`
`is.” Reply at 2. Apple provides four arguments for why, but none holds water. Id. at 1-3.
`
`First, Apple argues that Maxell’s citations to the manual landing page is insufficient
`
`because that page links to many manuals. Reply 1-2. But, for each patent, Maxell specifically
`
`identifies accused products at issue. See, e.g., Complaint at ¶ 24-25. No doubt, Apple can use its
`
`own landing page to identify the manuals corresponding to those accused products, just as it
`
`expects its customers to do. Because the Complaint includes sufficient information to identify the
`
`relevant manuals, it is irrelevant that the landing page links to additional manuals.
`
`
`
`Second, Apple argues that Maxell fails to cite the exact portion of each manual or
`
`webpage related to the accused functionality. This argument fails because the Complaint
`
`identifies exactly which features are relevant to each patent and which webpages provide
`
`instructions regarding those features. As discussed above, the Complaint even includes website
`
`excerpts demonstrating the relevant features. The Complaint thus provides ample notice of which
`
`manuals and webpages are relevant, and which portions therein are concerned.
`
`
`
`Third, Apple argues that Maxell failed to distinguish Core Wireless Licensing S.A.R.L. v.
`
`Apple Inc., No. 6:14-cv-JRG-JDL, 2015 U.S. Dist. LEXIS 107354 (E.D. Tex. Jul. 15, 2015).
`
`Reply 2-3. But that is not so. Maxell argued in its Opposition that Core Wireless is
`
`distinguishable because it involved a failure to identify accused functionalities. See Opp. 7. In
`
`contrast, Maxell has identified at length the products and functionality accused. See id.
`
`Fourth, Apple argues that allegations describing its products’ infringing functionality are
`
`relevant only to its own direct infringement, not to its specific intent to induce infringement.
`
`Reply 3. But the fact that Apple sells products configured to infringe when used as intended is
`
`highly relevant to the case for inducement: such sales, coupled with Apple’s promotion of the
`
`
`
`3
`
`

`

`Case 5:19-cv-00036-RWS Document 39 Filed 06/18/19 Page 5 of 9 PageID #: 468
`
`infringing features through user manuals and advertising, suffice to state a plausible claim for
`
`induced infringement. See Compl. at ¶¶ 24, 25, 27.
`
`B.
`
`The Allegations Regarding Pre-Suit Notice of the ’586 Patent Are Sufficient.
`
`Regarding pre-suit notice of the ’586 Patent, Apple continues to demand that Maxell have
`
`alleged this fact with heightened specificity where the law demands only plausibility. At bottom,
`
`Apple’s argument is only that notice of the ’586 Patent is implausible because the patent issued
`
`after the alleged date of the notice. Yet Apple’s own arguments demonstrate that notice in these
`
`circumstances is plausible: Apple appears to acknowledge that it received notice of the
`
`underlying application on October 9, 2018,1 and it admits that such notice can constitute notice
`
`of the patent. See Reply 4. Those arguments demonstrate that, even where a defendant is alleged
`
`to have received notice of a patent four months before that patent issued, knowledge of the patent
`
`remains plausible. Whether Maxell can ultimately prove that knowledge is a fact issue for trial,
`
`not a reason to dismiss. See Pecorino v. Vutec Corp., 934 F. Supp. 2d 422, 450 (E.D.N.Y. 2012).
`
`Apple’s attempt to distinguish the Complaint from that in Copa fails out of the gate. See
`
`Reply 4 (citing 1:18-cv-00218, 2018 U.S. Dist. LEXIS 191927 (D. Me. Nov. 9, 2018)). Apple
`
`argues that the Copa complaint included “other facts”—that the defendant reviewed the patent
`
`application and competed with the plaintiff. Reply 4. But the Complaint here also includes “other
`
`facts”—details regarding the years of licensing negotiations and technical discussions concerning
`
`the asserted patents. See Opp. at 10-12 (citing Compl. at ¶ 5). Those “other facts” render it
`
`plausible that Apple received notice of the ’586 Patent.
`
`C.
`
`The Allegations Regarding Knowledge of Infringement Are Sufficient.
`
`The allegations in the Complaint are also sufficient to support a plausible inference of
`
`knowledge for pre-suit indirect and willful infringement. The Complaint details six years of
`
`1 The Opposition’s reference to October 19, rather than October 9 was a typographical error.
`4
`
`
`
`

`

`Case 5:19-cv-00036-RWS Document 39 Filed 06/18/19 Page 6 of 9 PageID #: 469
`
`licensing negotiations and technical discussions between the parties concerning the asserted
`
`patents, and it identifies the specific dates of the relevant meetings and communications through
`
`which Apple learned of each asserted patent. Opp. at 10-12. Apple is aware of these facts
`
`because it participated in every meeting and communication. These allegations make it plausible
`
`that Apple knew it was infringing the asserted claims. Opp. at 10-13.
`
`The additional details provided in Maxell’s Opposition were not included to shore up
`
`legal deficiencies in the Complaint, but to demonstrate that the allegations are indeed plausible.
`
`In any event, Apple exaggerates the extent to which Maxell’s Opposition includes “new
`
`allegations.” For example, Apple objects
`
`that
`
`the Complaint contains no allegation
`
`corresponding to Maxell’s argument that, during the negotiations, it presented Apple with
`
`“detailed explanations” of infringement, “including claim charts.” Reply at 5. But to the
`
`contrary, the Complaint includes allegations that:
`
`[M]eetings included Apple’s representatives being provided with detailed
`information regarding Maxell’s patents, the developed technology, and Apple’s
`ongoing use of this patented technology. Through this process, Apple’s
`representatives requested and received detailed explanations regarding Maxell’s
`patents and allegations.
`
`Compl. at ¶ 5. Thus, the additional details of these meetings are not “new allegation[s].”
`
`Abandoning its reliance on E.D. Texas authority, Apple argues that Deere & Co. v.
`
`AGCO Corp., No. 18-827-CFC, 2019 U.S. Dist. LEXIS 25885, at *15-16) (D. Del. Feb. 19,
`
`2019) is “the most analogous case.” Reply 5. But Deere is readily distinguishable because the
`
`parties there did not negotiate directly. Rather, knowledge was alleged based on a letter sent to a
`
`third party, and the letter failed to identify any accused products. See id. at *19. Here, the parties
`
`negotiated directly for years and exchanged “detailed information regarding … Apple’s ongoing
`
`use of [Maxell’s] patented technology.” Compl. at ¶ 5.
`
`
`
`5
`
`

`

`Case 5:19-cv-00036-RWS Document 39 Filed 06/18/19 Page 7 of 9 PageID #: 470
`
`Dated: June 18, 2019
`
`By:
`
`
`
`6
`
`/s/ Jamie B. Beaber
`Geoff Culbertson
`Kelly Tidwell
`Patton, Tidwell & Culbertson, LLP
`2800 Texas Boulevard (75503)
`Post Office Box 5398
`Texarkana, TX 75505-5398
`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
`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
`
`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
`
`

`

`Case 5:19-cv-00036-RWS Document 39 Filed 06/18/19 Page 8 of 9 PageID #: 471
`
`
`Counsel for Plaintiff Maxell, Ltd.
`
`
`
`7
`
`

`

`Case 5:19-cv-00036-RWS Document 39 Filed 06/18/19 Page 9 of 9 PageID #: 472
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned certifies that all counsel of record who are deemed to have consented to
`
`electronic service are being served this 18th day of June, 2019, with a copy of this document via
`
`the Court’s electronic CM/ECF system.
`
`Dated: June 18, 2019
`
`
`
`/s/ Jamie B. Beaber
`Jamie B. Beaber
`
`
`
`
`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