throbber
Case 5:19-cv-00036-RWS Document 473 Filed 08/03/20 Page 1 of 8 PageID #: 25957
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`TEXARKANA DIVISION
`
`MAXELL, LTD.,
`
`
`
`Plaintiff
`
`Civil Action No. 5:19-cv-00036-RWS
`
`v.
`
`APPLE INC.,
`
`Defendant.
`
`JURY TRIAL DEMANDED
`
`
`
`
`
`
`
`
`
`
`APPLE INC.’S SUR-REPLY IN SUPPORT OF ITS OPPOSITION TO MAXELL, LTD.’S
`MOTION TO STRIKE PORTIONS OF APPLE’S REBUTTAL EXPERT REPORTS
`BASED ON UNTIMELY CLAIM CONSTRUCTION POSITIONS
`
`
`
`

`

`Case 5:19-cv-00036-RWS Document 473 Filed 08/03/20 Page 2 of 8 PageID #: 25958
`
`
`Maxell’s Reply (D.I. 431) confirms its motion is simply a vehicle for expanding claim
`
`scope. Maxell frames Apple’s experts’ technical analysis as claim construction by setting up
`
`strawman positions and misrepresenting their opinions. But Apple’s experts have not proffered
`
`any opinion that contradicts the Court’s Markman Order on construed terms or deviates from the
`
`plain meaning of un-construed terms. Maxell’s Motion (D.I. 369) should be denied.
`
`I.
`
`Dr. Bederson’s Rebuttal Expert Report—the ’306 and ’991 Patents
`
`’306 Patent: Maxell does not dispute that: (1) its own expert accused an iPhone’s
`
`memory as a “sound source,” and (2) Claim 12 requires “at least two sound sources.” D.I. 406 at
`
`2-3. Thus, Dr. Bederson’s opinion that a product with a single memory does not have “at least
`
`two sound sources” is a straight-forward non-infringement opinion—he did not construe any
`
`claim term. Similarly, Dr. Bederson cites the specification’s disclosure of “sound generation
`
`protocols” to confirm his understanding of the term’s plain meaning, and his opinion that the
`
`accused products do not use “a plurality of sound generation protocols” is based on the plain
`
`requirement that there must be multiple such protocols. Id. at 4. Maxell cites Dr. Bederson’s
`
`technical analysis of the accused products’ operation (Reply at 2), but these are not claim
`
`construction opinions. There is no basis to strike Dr. Bederson’s report.
`
`’991 Patent, TV Receiver: As explained in Apple’s motions (D.I. 358, D.I. 372), it is
`
`Maxell—not Apple—who is trying to undo the Court’s claim construction. Dr. Bederson
`
`faithfully applied the Court’s construction requiring a “videophone function-added TV receiver.”
`
`The opinions Maxell cites—Dr. Bederson’s analysis of whether the accused products include TV
`
`receiver components (e.g., television tuners), perform TV receiver functionality (e.g., receive
`
`television broadcast signals), and conform to TV standards (e.g., NTSC, PAL, etc.)—are part of
`
`his factual analysis of the accused products’ design and functionality. Dr. Bederson confirmed in
`
`his deposition that he considered these features as part of the “totality of the evidence” to
`
`1
`
`

`

`Case 5:19-cv-00036-RWS Document 473 Filed 08/03/20 Page 3 of 8 PageID #: 25959
`
`
`determine whether each accused product includes a “TV receiver.” D.I. 433, Ex. 6 at 240:17-
`
`241:1. He did not define “TV receiver” and he did not deviate from the Court’s construction.
`
`’991 Patent, “Display configured to …” and “Pauses”: Dr. Bederson’s non-
`
`infringement opinions for these limitations directly apply the terms’ plain meaning to the
`
`accused products’ designs. The “display” limitation plainly requires the display of two pieces of
`
`information, and the words “pause” and “stop” are different requirements recited by the claims.
`
`See ’991 Patent at Claims 1, 4. If Maxell wanted to construe “pause” and “stop” to have the
`
`same meaning, it was incumbent on Maxell—not Apple—to seek construction of the terms.
`
`II.
`
`Dr. Paradiso’s Rebuttal Expert Report—the ’317, ’498, ’999 Patents
`
`“Direction” limitations: Maxell cannot show that Dr. Paradiso deviated from the plain
`
`meaning of two limitations requiring the display of a “direction” to a “destination” when he
`
`opined that they are not infringed by the accused turn-by-turn route lines in Apple Maps.
`
`Instead, Maxell makes an improper claim construction argument: that those limitations should
`
`be construed broadly to encompass Figures 3(c)-(f), in addition to Figures 3(a)-(b). Reply at 3.
`
`But Dr. Paradiso testified that he is not limiting his understanding of the claim language to
`
`Figures 3(a)-(b). Ex. 21 at 196:14-197:21. And any dispute regarding whether the accused route
`
`lines satisfy the “direction” limitations presents a fact issue for trial, not a basis to strike.
`
` “PHS” Requirement: Maxell first attempts to mischaracterize Dr. Paradiso’s opinions
`
`by asserting that the Court’s construction does not require “the entire PHS; it requires a
`
`component of a PHS,” suggesting that Dr. Paradiso’s opinions treat PHS as a separate device.
`
`Reply at 3. But at his deposition, Dr. Paradiso testified that the Court’s claim construction does
`
`not require a “separate device or phone”; instead, it requires a component (e.g., a “chipset”) of a
`
`PHS device. Ex. 21 at 187:17-188:11. Thus, Maxell’s argument is simply a strawman.
`
`Maxell’s second criticism that Dr. Paradiso cites extrinsic evidence describing a “PHS”
`
`2
`
`

`

`Case 5:19-cv-00036-RWS Document 473 Filed 08/03/20 Page 4 of 8 PageID #: 25960
`
`
`as using PSTN/ISDN networks is flawed for two reasons. First, Dr. Paradiso uses industry
`
`evidence to provide context of what PHS technology is and Maxell cites no legal authority that
`
`Dr. Paradiso may not do so. At any rate, any disagreement over whether PHS technology is
`
`different from the accused products’ cellular technology is a factual dispute, not a claim
`
`construction issue. Second, Maxell cites specification passages that purport to show that “PHS”
`
`can use “cellular” networks. Reply at 3. But the specification’s mention of “cellular” describes
`
`the patent’s “portable telephone” technology, not a “PHS.” E.g., ’317 at 5:16-21, 5:64-67.
`
`Maxell’s other citations to the specification mentioning “wireless” and “Internet” are irrelevant;
`
`neither is the same as “cellular” or inconsistent with using PSTN/ISDN.1
`
`III. Dr. Bims’ Rebuttal Expert Report—the ’193 Patent
`
`Maxell wrongly seeks to preclude Apple’s expert from testifying that the plain meaning
`
`of “connected to” requires separately recited claim elements to be connected to each other.
`
`Maxell again resorts to improper claim construction arguments by citing the specification. Reply
`
`3-4. But the specification does not support Maxell’s position because it describes the recited
`
`elements as separate, interconnected components in all figures and embodiments. E.g., ’193
`
`Patent at 4:32-5:62, Fig. 1. Maxell argues that Dr. Bims’ invalidity report does not use the word
`
`“separate,” but that report maps separate components to the claim elements and shows the
`
`connections between them. E.g., D.I. 369, Ex. 18 at ¶ 174 (showing connection between
`
`separate “receiver” and “encoder/decoder”). There is no inconsistency between Dr. Bims’
`
`reports, and any inconsistency would be an issue for cross-examination, not a basis to strike.
`
`IV. Dr. Bovik’s Rebuttal Expert Report—the ’493 Patent
`
`“All”: Maxell argues that Dr. Bovik ignored the “N number” portion of the claim term.
`
`
`
`1 Maxell’s argument that Apple did not mention “PHS” in its IPR petitions is irrelevant and misleading
`because Apple’s IPR petitions applied Maxell’s proposed constructions in this case, which did not require
`a “PHS” at all. Ex. 22 (’999 Patent IPR Pet.) at 12-14; Ex. 23 (’317 Patent IPR Pet.) at 15-16.
`
`3
`
`

`

`Case 5:19-cv-00036-RWS Document 473 Filed 08/03/20 Page 5 of 8 PageID #: 25961
`
`
`This is simply untrue. See, e.g., D.I. 406, Ex. 10 ¶ 61 (addressing “N number” limitation).
`
`Claim 5 defines “N number” as the number of pixel lines on the image sensor. See ’493 Patent at
`
`Claim 5 (reciting “a light receiving sensor having an array of pixels … in an N number of
`
`vertically arranged pixel lines”). No claim construction is necessary to support Dr. Bovik’s
`
`understanding of the claim’s plain meaning. Thus, there is no basis to strike his opinions.
`
`Claim 6: Maxell attacks a strawman argument. The dispute is not whether the claim
`
`includes a negative limitation to exclude any device that performs post-processing, but whether
`
`image stability correction during post-processing infringes the claim. It does not because Claim
`
`6 plainly limits the claimed image stabilization operation to “when recording in the moving
`
`video mode.” ’493 Patent at Claim 6. Maxell again has identified no basis to strike.
`
`V.
`
`Dr. Menascé’s Rebuttal Expert Reports—the ’438, ’586, and ’794 Patents
`
`’438 Patent, “authentication process”: Maxell’s Reply confirms that the parties’
`
`dispute is over how the accused products work, not over the agreed construction for the claim
`
`term. Maxell does not mention the agreed construction, much less explain how Dr. Menascé
`
`deviated from it. Instead, Maxell obscures the parties’ dispute by suggesting that there is some
`
`dispute over whether the accused products use two-way communication. Reply at 4-5. But
`
`Maxell’s expert Dr. Williams plainly accuses two-way communication as “authentication” by,
`
`for example, pointing to both “advertise[]” and “return” signals as part of the accused
`
`authentication process. See, e.g., D.I. 406, Ex. 13 at ¶¶ 322, 411. Maxell argues that Dr.
`
`Williams does not mention the phrase “two-way” in his report, but admits that his theory is that
`
`the “Discovery Flow”—a two-way communication—meets the claimed “authentication process”
`
`limitation. Reply at 4-5. In fact, all infringement theories in Dr. Williams’ report involve two-
`
`way communication. Maxell also argues that Apple has conceded that the accused AirDrop
`
`feature’s “discovery flow” involves two-way communication. Id. at 5 n.3. This mischaracterizes
`
`4
`
`

`

`Case 5:19-cv-00036-RWS Document 473 Filed 08/03/20 Page 6 of 8 PageID #: 25962
`
`
`the parties’ dispute, which is about how and when authentication is carried out, e.g., whether
`
`Bluetooth carries out the claimed “authentication process.” D.I. 406 at 12. The dispute over
`
`how the accused devices work is a factual issue for the jury, not a basis to strike.
`
`’438 Patent, “display apparatus”: The parties selected a preamble term for
`
`construction and the Court construed that term by adopting Maxell’s proposal. Now, Maxell
`
`wants to avoid its own construction by arguing that the preamble is not limiting, despite having
`
`taken the opposite position during Markman. See D.I. 406 at 12-13. This cannot be permitted.
`
`’438 Patent, “if and only if”: Maxell is unable to explain how Dr. Menascé’s
`
`understanding of the claims deviated from their plain meaning, and argues only that his analysis
`
`uses words not found in the claims. Reply at 5. But an expert is not limited to using only words
`
`from the claims to describe their plain meaning. The asserted claims require data exchange “if”
`
`authentication is affirmed, and prohibits data exchange “if” authentication is not affirmed. ’438
`
`Patent at Claims 1, 4. As Dr. Menascé explained, the plain meaning of the claims limits data
`
`exchange to a scenario only if authentication is affirmed; otherwise, exchange is denied.
`
`’794 Patent, “when”: Dr. Menascé applied his understanding of the plain meaning of
`
`the “when” terms, and Maxell does not dispute that Dr. Menascé’s understanding is consistent
`
`with Maxell’s own application of the terms in its infringement contentions. See D.I. 406 at 14-
`
`15. Thus, there is no basis to strike Dr. Menascé’s opinions.
`
`’586 Patent, “previously stores”: Maxell continues to misrepresent Dr. Menascé’s
`
`opinions. Dr. Menascé did not opine that “previously stores” can only be accomplished through
`
`factory programming. For Maxell to prove direct infringement, it must show that Apple has
`
`programmed the accused memory to meet the “previously stores” limitation, either at the factory
`
`or through some other means, which, as Dr. Menascé explained, Maxell failed to do.
`
`5
`
`

`

`Case 5:19-cv-00036-RWS Document 473 Filed 08/03/20 Page 7 of 8 PageID #: 25963
`
`
`July 30, 2020
`
`
`
`
`
`
`
`/s/ Luann L. Simmons
`
`
`
`Luann L. Simmons (Pro Hac Vice)
`lsimmons@omm.com
`O’MELVENY & MYERS LLP
`Two Embarcadero Center
`28th Floor
`San Francisco, CA 94111
`Telephone: 415-984-8700
`Facsimile: 415-984-8701
`
`Xin-Yi Zhou (Pro Hac Vice)
`vzhou@omm.com
`O’MELVENY & MYERS LLP
`400 S. Hope Street
`Los Angeles, CA 90071
`Telephone: 213-430-6000
`Facsimile: 213-430-6407
`
`Marc J. Pensabene (Pro Hac Vice)
`mpensabene@omm.com
`Laura Bayne Gore (Pro Hac Vice)
`lbayne@omm.com
`O’MELVENY & MYERS LLP
`Times Square Tower, 7 Times Square
`New York, NY 10036
`Telephone: 212-326-2000
`Facsimile: 212-326-2061
`
`Melissa R. Smith (TX #24001351)
`melissa@gilliamsmithlaw.com
`GILLIAM & SMITH, LLP
`303 South Washington Avenue
`Marshall, Texas 75670
`Telephone: (903) 934-8450
`Facsimile: (903) 934-9257
`
`Attorneys for Defendant Apple Inc.
`
`6
`
`
`
`
`
`

`

`Case 5:19-cv-00036-RWS Document 473 Filed 08/03/20 Page 8 of 8 PageID #: 25964
`Case 5:19-cv-00036-RWS Document 473 Filed 08/03/20 Page 8 of 8 PageID #: 25964
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that all c01msel of record who are deemed to have
`
`consented to electronic service are being served with a copy of this docmnent via the Court's
`
`CM/ECF system per Local Rule CV—5(a)(3) on July 30. 2020.
`
`/s/ Melissa R. Smith
`
`Melissa R. Smith
`
`

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