throbber
Case 2:16-cv-00695-RWS-RSP Document 91 Filed 10/18/23 Page 1 of 7 PageID #: 1753
`
`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 LAY WITNESSES PROVIDING EXPERT TESTIMONY
`
`Plaintiff Alacritech, Inc. (“Alacritech”) respectfully raises issues and concerns based on
`
`recent demonstratives and trial exhibits disclosed by Defendant Intel Corporation (“Intel”) for use
`
`with its forthcoming fact witnesses, Timothy Labatte and Jesse Brandeburg. Specifically, the
`
`demonstratives and exhibits for Messrs. Labatte and Brandeburg indicate Intel intends to present
`
`improper expert analysis and testimony through lay witnesses who were never disclosed or
`
`qualified as experts in this case. Pursuant to Federal Rules of Evidence 701 and 702, however, “it
`
`is an abuse of discretion to permit a witness to testify as an expert on the issues of noninfringement
`
`or invalidity unless that witness is qualified as an expert in the pertinent art.” Sundance, Inc. v.
`
`DeMonte Fabricating Ltd., 550 F.3d 1356, 1363 (Fed. Cir. 2008). “The prohibition of unqualified
`
`witness testimony extends to the ultimate conclusions of infringement and validity as well as to
`
`1
`
`

`

`Case 2:16-cv-00695-RWS-RSP Document 91 Filed 10/18/23 Page 2 of 7 PageID #: 1754
`
`the underlying technical questions.” HVLPO2, LLC v. Oxygen Frog, LLC, 949 F.3d 685, 689
`
`(Fed. Cir. 2020).
`
`Mr. Labatte. Here, Mr. Labatte’s demonstratives include magnetic posterboards that
`
`appear aimed at presenting the purported operation of not just “Intel NIC[s]” but prior art “1990s
`
`NIC[s]” and “Alacritech NIC[s].” See Dkt. 87 (10/18/23 Notice of Morning Disputes) at Ex. A.
`
`Mr. Labatte, thus, will likely attempt to walk through a technical tutorial regarding the alleged
`
`operation of such NICs and TCP/IP processing performed by such NICs while attempting to draw
`
`distinctions between them, which would clearly amount to expert testimony directed to non-
`
`infringement. See id. at 6 (magnetic placards corresponding to elements of the TCP/IP protocol
`
`stack). Indeed, Intel’s comparisons between the accused Intel NICs and Alacritech’s TOE
`
`technology is the subject of Alacritech’s concurrently filed trial brief, and is yet another attempt
`
`by Intel to impress upon the jurors that Intel NICs do not infringe based on an improper comparison
`
`with Alacritech NICs—as opposed to the asserted claim language. Such comparisons are hardly
`
`proper for an expert witness let alone a fact witness. See Dkt. 875 (striking expert testimony that
`
`compared accused products with Alacritech commercial products).
`
`Mr. Brandeburg. With Mr. Brandeburg, Intel intends on using a 1400+ page technical
`
`manual regarding the accused Intel Niantic NICs. Indeed, the exhibit is a version of the very same
`
`technical specification used by both Alacritech’s infringement expert, Dr. Almeroth, and Intel’s
`
`non-infringement expert, Dr. Heegard. Based on his prior testimony and designated deposition
`
`topics in this case, Mr. Brandeburg is a Linux driver developer and likely does not have sufficient
`
`personal knowledge to testify regarding a 1400+ page technical specification covering the entire
`
`Niantic product. Accordingly, it is unclear what Mr. Brandeburg’s estimated 30 minutes of
`
`testimony could possibly relate to other than providing improper observations and technical
`
`2
`
`

`

`Case 2:16-cv-00695-RWS-RSP Document 91 Filed 10/18/23 Page 3 of 7 PageID #: 1755
`
`testimony directed to Intel’s non-infringement arguments and aimed at bolstering Intel’s experts.
`
`At a minimum, to the extent Mr. Brandeburg is allowed to testify regarding how Niantic operates
`
`(assuming Intel can establish a proper foundation for his personal knowledge), he should not be
`
`allowed to testify in the negative as to how Niantic does not operate or provide any testimony
`
`aimed at comparing or distinguishing Niantic’s operation from any other method of operation or
`
`that relates in any way to asserted claim language or expert disputes.
`
`Improper Expert Testimony From a Lay Witness Invites Reversible Error
`
`Allowing Messrs. Labatte and/or Brandeburg to testify on matters reserved for experts
`
`would invite reversible error. HVLPO2, 949 F.3d 685 (finding district court abused its discretion
`
`by allowing expert analysis and ultimate conclusion of obviousness by lay witness). In HVLPO2,
`
`for example, the Federal Circuit found the district court erred by allowing expert testimony on the
`
`topic of obviousness through a lay witness not only because that witness offered the ultimate
`
`conclusion of obviousness, but also because he offered “observations” on the underlying technical
`
`questions. Id. at 690 (finding even a curative instruction was not enough to cure the prejudice).
`
`Similarly, here, Mr. Labatte may offer improper observations regarding the TCP/IP
`
`processing performed by accused products, prior art products, and Alacritech TOE products, all
`
`aimed at bolstering the conclusion of Intel and its experts that Intel NICs do not infringe—again,
`
`not because they purportedly do not meet one or more claim limitations but because they are
`
`different from Alacritech’s TOE products. As a concrete example, claim 41 of the ’880 patent
`
`requires “a flow re-assembler, disposed in the network interface.” Intel argues this was something
`
`“that Alacritech was proposing go in the network interface card, and it doesn’t in the Intel
`
`products.” Trial Tr., 10/17/2023, 229:6-9. Through his demonstratives, Mr. Labatte will likely
`
`attempt to testify that “control” and reassembly of packets occurs on the host computer for accused
`
`3
`
`

`

`Case 2:16-cv-00695-RWS-RSP Document 91 Filed 10/18/23 Page 4 of 7 PageID #: 1756
`
`Intel NICs and that this is different than Alacritech NICs. Yet the actual location of packet
`
`reassembly under the asserted claim language is precisely one of the disputes between the parties’
`
`experts. A fact witness should not be allowed to place his thumb on the scale in favor of one expert
`
`when there is a dispute regarding how a product operates as it relates to the asserted claim
`
`language. For example, it would be improper for any of the lay witnesses to explain how the Intel
`
`NICs purportedly process TCP/IP responses via a protocol stack, such as by handing off control
`
`for session and/or network layer processing between a host computer and NIC.
`
`Nor should lay witnesses be allowed to provide testimony referencing or using claim
`
`language, such as communication flows, re-assembling data portions of data packets, maintaining
`
`a TCP connection for communication flows, storing a TCP connection as a control block,
`
`performing fast path processing, parsing received packet headers and checking for exception
`
`conditions, directing packets to a protocol stack for processing, and anything relating to whether a
`
`protocol stack of a host computer performs any network layer processing or any transport layer
`
`processing. Reference to claim terms and concepts would risk confusing the jury into giving
`
`improper weight to fact testimony as if it were that of a qualified expert.
`
`Accordingly, to the extent any of Intel’s witnesses offer factual testimony regarding the
`
`accused products, they should be limited to nothing more than high-level descriptions. See
`
`Intellectual Ventures v. T-Mobile et al., No. 2:17-CV-577-JRG, Dkt. 335, at 122:10-11 (E.D. Tex.
`
`Feb. 6, 2019) (prohibiting lay witness testimony “beyond a high level [description] of the operation
`
`and functionality”). For example, in Intellectual Ventures I, LLC v. T-Mobile USA, Inc., et al, No.
`
`6:13-cv-00072-RWS, Dkt. 259-1 at 109:6-21 (June 17, 2021), this Court sustained objections to
`
`numerous technical questions of the type Alacritech expects to be directed to Intel’s lay witnesses,
`
`including:
`
`4
`
`

`

`Case 2:16-cv-00695-RWS-RSP Document 91 Filed 10/18/23 Page 5 of 7 PageID #: 1757
`
`- “So how does the uplink scheduler decide which phone gets to transmit at a
`particular time?” Id. at 113:25-114:4.
`- “how often did you design your uplink scheduler to make the scheduling
`competition decisions?” Id. at 115:9-14.
`- “In the uplink scheduler that you designed for Ericsson, which of the frames does
`it schedule?” Id. at 117:16-20.
`- “And can you tell me how these priority values work in the delay base scheduler
`that you designed? . . . [W]hat is the general concept of the delay base scheduler
`that you designed?” Id. at 118:12-21.
`
`Neither Mr. Labatte nor Mr. Brandeburg should be allowed to provide testimony in
`
`response to similar questions aimed at eliciting expert opinions and observations regarding the
`
`accused RSC functionality. How RSC operates in relation to the limitations of the asserted claims
`
`is purely within the province of expert opinion.
`
`*
`
`*
`
`*
`
`Despite Intel’s claim that Messrs. Labatte and Brandeburg will provide only fact testimony
`
`(Dkt. 86), the demonstratives and exhibit indicate otherwise and, at a minimum, raise an
`
`unacceptably high risk of testimony that will delve into improper expert analysis and observations
`
`in violation of Federal Rules of Evidence 701 and 702. Accordingly, Alacritech seeks to preclude
`
`such testimony outside of the presence of the jury and in advance of Intel’s trial presentation,
`
`which would require Alacritech potentially “having to come to the bench repetitively” and putting
`
`it “in a bad light.” See Intellectual Ventures I, LLC v. T-Mobile USA, Inc., et al, No. 6:13-cv-
`
`00072-RWS, Dkt. 259-1 at 109:6-21 (June 17, 2021).
`
`
`
`
`
`
`
`5
`
`

`

`Case 2:16-cv-00695-RWS-RSP Document 91 Filed 10/18/23 Page 6 of 7 PageID #: 1758
`
`
`
`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 91 Filed 10/18/23 Page 7 of 7 PageID #: 1759
`
`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