throbber
Case 2:16-cv-00695-RWS-RSP Document 92 Filed 10/18/23 Page 1 of 8 PageID #: 1760
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`
`
`ALACRITECH, INC.,
`
`
`
`
`
`Plaintiff,
`
`Defendants,
`
`
`2:16-cv-00695-RWS-RSP
`
`
`JURY TRIAL DEMANDED
`
`v.
`
`DELL INC.,
`
`and
`
`INTEL CORPORATION, et al.,
`
`Intervenors.
`
`
`
`TRIAL BRIEF REGARDING IMPROPER COMPARISONS OF THE ACCUSED
`PRODUCTS TO ANYTHING OTHER THAN THE ASSERTED CLAIMS
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 2:16-cv-00695-RWS-RSP Document 92 Filed 10/18/23 Page 2 of 8 PageID #: 1761
`
`
`
`Plaintiff Alacritech, Inc. (“Alacritech”) hereby seeks and renews its motion in limine
`
`seeking to preclude evidence and argument characterizing Alacritech’s asserted patents as limited
`
`to its commercial TOE technology and comparisons between Intel’s accused products and TOE as
`
`opposed to the asserted claim language. “It is a bedrock principle of patent law that the claims of
`
`a patent”—not any commercial embodiments—“define the invention to which the patentee is
`
`entitled the right to exclude.” Phillips v. AWH Corp., 415 F.3d 1303, 1312 (Fed. Cir. 2005)
`
`(citations omitted). Accordingly, “it is error for a court to compare in its infringement analysis the
`
`accused product or process with the patentee’s commercial embodiment or other version of the
`
`product or process; the only proper comparison is with the claims of the patent.” Zenith Lab'ys,
`
`Inc. v. Bristol-Myers Squibb Co., 19 F.3d 1418, 1423 (Fed. Cir. 1994) (citation omitted). Yet it is
`
`clear through two days of trial that Defendant Intel Corporation (“Intel”) is improperly focusing
`
`the jury on a comparison of Intel’s accused RSC functionality with Alacritech’s commercial TOE
`
`technology and other improper placeholders for claim language.
`
`1. Day 1 Improper Comparisons Between Accused Functionality and TOE
`
`For example, in his opening remarks, Dell’s counsel expressly invited the jurors to compare
`
`TOE with RSC as part of their evaluation of the evidence. See 10/16/23 Trial Tr. at 215:10-14
`
`(“Please, as we go through the evidence in this case, every document that you see, every witness
`
`that you hear, make sure that you understand whether we're talking about TOE or RSC because
`
`those things are different, as the Plaintiff just told you.”) (all emphases added unless noted
`
`otherwise). In his opening remarks, Intel’s counsel likewise stressed to the jurors that RSC is not
`
`TOE and, importantly, that “the reason why that matters so much” is because the asserted patents
`
`and claims nowhere recite the phrase RSC. Id. at 219:3-220:20 (“RSC is not the same thing as
`
`TOE. They're different. And here's what -- the reason why that matters so much. And, again,
`
`1
`
`

`

`Case 2:16-cv-00695-RWS-RSP Document 92 Filed 10/18/23 Page 3 of 8 PageID #: 1762
`
`
`
`why the details matter, why careful consideration matters. In a patent case like this, the patent
`
`owner is limited to the boundaries of their patent. They can’t stretch those boundaries. You’re not
`
`permitted to move the fence line so to speak. You’re limited to what you actually came up with,
`
`your actual invention and the boundary lines in that patent.”).
`
`2. Day 2 Improper Comparisons Between Accused Functionality and TOE
`
`On day 2 of trial, Intel continued to intimate that Alacritech’s patents are directed to TOE
`
`throughout his questioning of Alacritech’s corporate designee, Larry Boucher. For example,
`
`asking Mr. Boucher a line of questions designed to suggest to the jury that the Alacritech patents
`
`asserted in this case are TOE patents—“Q. The first and only time Alacritech told Intel that its
`
`RSC products somehow infringe TOE patents is right here in this case, isn’t that true?” (10/17/23
`
`Trial Tr. 366:16-367:4)—and whether Alacritech ever put Intel on notice of RSC (id. at 373:13-
`
`374:5). The questioning and repeated emphasis on the undisputed point that “TOE is different
`
`than RSC” is all aimed at inviting the jury to determine whether there is infringement by the
`
`accused products based on whether the asserted patents contain the term “RSC” as opposed to
`
`evaluating and comparing the accused products against the claim language.
`
`3. Forthcoming Improper Comparisons of Accused Functionality
`
`Now, heading into Intel’s case-in-chief, it is apparent they intend on presenting the same
`
`misdirection through not just their experts, but their fact witnesses as well. For example,
`
`demonstratives disclosed to be used with Intel’s corporate designee appear to be designed to have
`
`a lay witness provide a technology tutorial and demonstrate the purported processing of
`
`“Alacritech NIC[s]” that practiced TOE with “Intel NIC[s]” that practice RSC. See Dkt. 86-1
`
`(10/18/23 Notice of Morning Disputes). Thus, Intel attempts to do through fact testimony what
`
`this Court has already precluded its experts from doing—i.e., comparing the accused products to
`
`2
`
`

`

`Case 2:16-cv-00695-RWS-RSP Document 92 Filed 10/18/23 Page 4 of 8 PageID #: 1763
`
`
`
`Alacritech’s commercial TOE technology as opposed to the asserted claims. See Dkt. 875 at 7-8
`
`(“Dr. Heegard’s opinions comparing Alacritech’s TOE products to Intel’s accused products do not
`
`involve comparing the asserted claims to the accused products. Therefore, those opinions will not
`
`help the jury understand whether the accused products include each and every limitation recited in
`
`the asserted claims. FED. R. EVID. 702. And any marginal probative value that testimony has is
`
`substantially outweighed by a danger of confusing the issues and misleading the jury. FED. R.
`
`EVID. 403.”).
`
`Not stopping with its fact witnesses, Intel’s experts also appear intent on presenting
`
`improper comparisons of the accused products to things other than the asserted claims. For
`
`example, Intel’s non-infringement expert, Dr. Heegard, shortcuts the proper infringement analysis
`
`through several demonstratives, including slides aimed at comparing “Intel RSC” with an
`
`illustration of “Alacritech Patents” untethered to the claim language—all as a shortcut for arguing
`
`non-infringement. See Dkt. 86-3 (10/18/23 Notice of Morning Disputes). Not only is this
`
`misleading, but it is an attempt to draw a distinction with Intel’s characterization of Alacritech’s
`
`TOE technology.
`
`Similarly, Intel’s invalidity expert, Dr. Wicker, improperly compares Intel RSC with
`
`Alacritech’s provisional patent application as opposed to the asserted claims—as a shortcut for a
`
`proper written description analysis, which requires comparing the asserted claims to the underlying
`
`priority document. See Ariad Pharm., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010)
`
`(en banc) (focusing written description inquiry on “whether the disclosure of the application
`
`relied upon reasonably conveys to those skilled in the art that the inventor had possession of the
`
`claimed subject matter as of the filing date”). Dr. Wicker’s flawed analysis comparing the accused
`
`3
`
`

`

`Case 2:16-cv-00695-RWS-RSP Document 92 Filed 10/18/23 Page 5 of 8 PageID #: 1764
`
`
`
`products to a priority document is yet another backdoor attempt to imply to the jurors that there is
`
`no infringement by comparing Intel RSC with something other than the asserted claims:
`
`
`
`Dkt. 86-4 at 8-18 (10/18/23 Notice of Morning Disputes).
`
`*
`
`*
`
`*
`
`Any one of Intel’s tactics alone is improper, and Alacritech believes that a curative
`
`instruction is appropriate in light of the repeated improper arguments during trial. Moreover,
`
`Alacritech requests that the Court preclude any further argument or examination before the jury is
`
`left with the irreversible impression that there is no infringement in this case—not because the
`
`claim limitations are not practiced by the accused products, but because they could not find the
`
`term “RSC” or “receive side coalescing” in the claims or because Intel “RSC” is not Alacritech
`
`“TOE.” Indeed, this is not an unfamiliar issue for courts in this District, yet it is one that has
`
`uniformly been addressed through curative instructions throughout trial making clear to the jury
`
`that “the only correct comparison is between the accused products and the language of the claim
`
`itself.” See, e.g., Personalized Media Commc’ns v. Google, Case No. 2:19-cv-00090-JRG, Trial
`
`Tr. at 945:12-20 (E.D. Tex.) (“To determine whether there is infringement, you must compare the
`
`4
`
`

`

`Case 2:16-cv-00695-RWS-RSP Document 92 Filed 10/18/23 Page 6 of 8 PageID #: 1765
`
`
`
`asserted claims, as I have defined each of them to you, to the accused product. You should not
`
`compare the accused product with any other specific example set out in the patents in reaching
`
`your decision on infringement. As I've reminded you during the trial, the only correct comparison
`
`is between the accused products and the language of the claim itself.”); id. at 951:3-12 (same).
`
`Accordingly, Alacritech respectfully apprises the Court of the issue and asks for relief in
`
`the form of either a curative instruction akin to that given by other Courts in this District (id.) and
`
`by allowing Alacritech’s attorneys to make standing objections to lines of questioning and
`
`testimony that compares the accused products to anything other than the asserted claims.
`
`
`
`
`
`5
`
`

`

`Case 2:16-cv-00695-RWS-RSP Document 92 Filed 10/18/23 Page 7 of 8 PageID #: 1766
`
`
`
`
`
`Dated: October 18, 2023
`
`
`
`QUINN EMANUEL URQUHART &
`SULLIVAN, LLP
`
`/s/ Brian E. Mack
`Joe Paunovich
`joepaunovich@quinnemanuel.com
`California State Bar No. 228222
`QUINN EMANUEL URQUHART &
`SULLIVAN, LLP
`865 South Figueroa Street, 10th Floor
`Los Angeles, CA 90017
`Telephone: (213) 443-3000
`Facsimile: (213) 443-3100
`
`Brian E. Mack
`brianmack@quinnemanuel.com
`California State Bar No. 275086
`QUINN EMANUEL URQUHART &
`SULLIVAN, LLP
`50 California Street, 22nd Floor
`San Francisco, CA 94111
`Telephone: (415) 875-6600
`Facsimile: (415) 875-6700
`
`T. John Ward, Jr.
`Texas State Bar No. 00794818
`jw@wsfirm.com
`Claire Abernathy Henry
`Texas State Bar No. 24053063
`claire@wsfirm.com
`WARD & SMITH LAW FIRM
`1507 Bill Owens Parkway
`Longview, Texas 75604
`Telephone: (903) 757-6400
`Facsimile: (903) 757-2323
`
`Attorneys for Plaintiff Alacritech, Inc.
`
`
`
`
`
`
`
`
`6
`
`

`

`Case 2:16-cv-00695-RWS-RSP Document 92 Filed 10/18/23 Page 8 of 8 PageID #: 1767
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that all counsel of record who are deemed to have
`
`consented to electronic service are being served with notice of the filing of this sealed document
`
`via the Court’s CM/ECF system pursuant to Local Rule CV-5(a) on October 18, 2023, and a copy
`
`of this sealed document, in its entirety, via electronic mail. All counsel who are not deemed to
`
`have consented to electronic service are being served by U.S. first-class mail.
`
`/s/ Brian E. Mack
`Brian E. Mack
`
`
`
`
`
`
`
`
`
`
`CERTIFICATE OF AUTHORIZATION TO FILE UNDER SEAL
`
`Pursuant to Local Rule CV-5, the undersigned counsel hereby certifies that
`
`authorization for filing under seal has been previously granted by the Court in the Protective
`
`Order entered in this case.
`
`
`
`/s/ Brian E. Mack
`Brian E. Mack
`
`
`
`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