throbber
Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 1 of 13 PageID #: 9456
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`AGIS SOFTWARE DEVELOPMENT LLC,
`
`
`Plaintiff,
`
`
`
`v.
`
`
`HTC CORPORATION,
`
`
`Defendant.
`










`
`
`Case No. 2:17-CV-0514-JRG
`(LEAD CASE)
`
`JURY TRIAL DEMANDED
`
`
`
`
`
`
`
`
`
`AGIS SOFTWARE DEVELOPMENT LLC’S OPPOSED MOTION
`TO STRIKE PORTIONS OF THE JANUARY 11, 2019
`EXPERT REPORT OF DR. ANDREW WOLFE
`
`
`
`
`

`

`Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 2 of 13 PageID #: 9457
`
`I.
`
`INTRODUCTION
`
`Plaintiff AGIS Software Development LLC (“AGIS”) submits this Motion to Strike
`
`Portions of the January 11, 2019 Expert Report of Dr. Andrew Wolfe (“Wolfe Report”) relating
`
`to
`
`
`
`
`
`
`
`
`
`
`
`
`
` relevant to HTC’s defenses
`
`(Dkt. 118 at 3-4) and P.R. 3-4 which requires HTC to produce source code with its invalidity
`
`contentions. HTC did not identify any Google source code printouts or the non-produced source
`
`code libraries in its discovery response to AGIS’s Interrogatory Request No. 8 seeking detailed
`
`non-infringement contentions. HTC could have and should have notified AGIS about any source
`
`code printouts produced by Google and any other discovery from Google, as well as the non-
`
`produced source code libraries. Because HTC failed to abide by the Court’s discovery order and
`
`P.R. 3-4, and failed to produce the source code printouts and libraries during the discovery
`
`period, AGIS respectfully moves the Court to strike the portions of the Wolfe Report including
`
`and related to the same.
`
`II.
`
`FACTUAL BACKGROUND
`
`On August 29, 2018, AGIS served deposition and document subpoenas on Google
`
`requesting, among other things,
`
`
`
`
`
`
`
`
`
`

`

`Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 3 of 13 PageID #: 9458
`
` Proper notice was provided to HTC of the subpoena to Google. Id. at 1.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`restrictive; it limits reviewers’ requests for printouts by number of total pages, number of
`
`consecutive pages, number of copies, and even the number of lines to be included for each page.
`
` The protective order in this case is
`
`Dkt. 119 at 14-16.
`
`
`
`
`
`
`
`
`
`On November 26, 2018 and December 13, 2018, AGIS notified HTC in writing that,
`
`responsive to AGIS’s subpoena, Google had made available source code for inspection, that
`
`AGIS had reviewed the code, and that Google produced to AGIS printouts of requested portions
`
`of the code. Ex. C, D. AGIS provided HTC with Google’s counsel’s contact information so that
`
`HTC could obtain copies of the source code printouts and requested that HTC copy AGIS on all
`
`correspondence with Google’s counsel. Id. AGIS received no response to its November 26,
`
`2018 and December 13, 2018 correspondence to HTC about the Google source code productions.
`
`HTC did not notify AGIS about any communication with Google’s counsel. HTC did not notify
`
`AGIS about any discovery or productions from Google to HTC. HTC provided no notice to
`
`2
`
`

`

`Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 4 of 13 PageID #: 9459
`
`AGIS that HTC had reviewed the Google source code or that HTC had requested any source
`
`code printouts from Google. HTC did not produce any Google source code printouts to AGIS.
`
`On December 14, 2018, AGIS served the Opening Expert Report of Mr. Joseph
`
`McAlexander regarding infringement of the patents-in-suit by HTC (“McAlexander Report”).
`
`On January 11, 2019, HTC served the rebuttal expert report of Andrew Wolfe regarding non-
`
`infringement (“Wolfe Report”). Ex. E. Nearly a month after the McAlexander Report and
`
`virtually concurrently with the Wolfe Report, on January 13, 2019, Google made available new
`
`source code for inspection. Ex. F. AGIS promptly notified HTC of the availability of the new
`
`Google source code. Ex. G. AGIS reviewed the code and requested additional source code
`
`printouts from Google. Ex. G, H. Google objected to AGIS’s printing request and produced
`
`only portions of the requested printouts of the new source code. Ex. H.
`
`
`
`
`
` HTC did not notify AGIS about
`
`any communication with Google’s counsel. HTC did not notify AGIS about any discovery or
`
`productions from Google to HTC. HTC provided no notice to AGIS that HTC had reviewed the
`
`Google source code or that HTC had requested any source code printouts from Google. HTC did
`
`not produce any Google source code printouts to AGIS.
`
`AGIS served Interrogatory Request No. 8 on March 8, 2018 which specifically requested
`
`HTC’s detailed non-infringement contentions, and AGIS pursued Google source code for the
`
`accused functionalities in order ensure HTC’s disclosure of any and all non-infringement
`
`theories based on Google source code. HTC’s non-infringement contentions made no reference
`
`to any Google source code or additional source code libraries. Ex. I. In fact, HTC’s response to
`
`AGIS’s requests for its non-infringement contentions includes an objection to any requirement
`
`3
`
`

`

`Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 5 of 13 PageID #: 9460
`
`for “information about applications designed and made by Google,” and a representation that
`
`HTC does not design or modify Google code and products. Ex. J at 4.
`
`-
`
`
`
`-
`
`
`
`
`
`
`
`
`
`
`
` The non-compliant source code printouts and libraries should be
`
`excluded from the Wolfe Report and HTC should be precluded from relying on the late code.
`
`III. LEGAL STANDARD
`
`P.R. 3-4 requires that “with the ‘Invalidity Contentions,’ the party opposing a claim of
`
`patent infringement must produce or make available for inspection and copying: (a) Source code,
`
`specifications, schematics, flow charts, artwork, formulas, or other documentation sufficient to
`
`show the operation of any aspects or elements of an Accused Instrumentality identified by the
`
`patent claimant in its P. R. 3-1(c) chart.”
`
`The Court’s discovery order requires that “[a] party receiving documents from a third
`
`party will provide copies of those documents to each other party within 5 business days of
`
`receiving those documents,” and that each party produce all documents, electronically stored
`
`information, and tangible things in the possession, custody, or control of the party that are
`
`relevant to the pleaded claims or defenses involved in this action “without awaiting a discovery
`
`request.” Dkt. 118 at 3-4 and 9.1
`
`
`1 HTC has represented to AGIS that it believes the Huawei discovery order is the operative
`order. Nevertheless, the discovery order in the HTC case contains substantially similar
`provisions. AGIS Software Development LLC v. HTC Corporation, Case No. 2:17-cv-00514,
`Dkt. 38 at 3-4 and 10.
`
`4
`
`

`

`Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 6 of 13 PageID #: 9461
`
`If a party fails to provide information or identify a witness as required by Rule 26(a) or
`
`(e), the party is not allowed to use that information or witness to supply evidence on a motion at
`
`a hearing, or at a trial, unless the failure was substantially justified or is harmless. Fed. R. Civ. P.
`
`37(c)(1). This Court has precluded the untimely discovery, and expert testimony based thereon,
`
`that “could have, and should have, been produced prior to the close of discovery.” ContentGuard
`
`Holdings, Inc. v. Amazon.com, Inc., No. 2:13-CV-1112-JRG, 2015 WL 6886957, at *2 (E.D.
`
`Tex. Nov. 7, 2015) (granting motion to exclude portions of expert reports and testimony because
`
`“the Court finds that Paragraphs 348–356, 367, 369–373, 380, 381, and 509 of Dr. Kelly’s report
`
`must be stricken in view of the Apple’s failure to produce the “correlation folders” for the iTunes
`
`source code for Windows and for Mac within the prescribed discovery period.”
`
`IV. ARGUMENT
`
`HTC should be precluded from relying on untimely discovery. In violation of the Court’s
`
`discovery order,
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` HTC
`
`
`
`5
`
`

`

`Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 7 of 13 PageID #: 9462
`
`did not produce the source code libraries during the discovery period and did not seek leave to
`
`produce discovery after the close of discovery. For example, Dr. Wolfe includes the following
`
`references to non-produced source code:
`
`Wolfe Rebuttal Report at 119.
`
`Wolfe Rebuttal Report at 127.
`
`
`
`
`
`
`
`
`
`Wolfe Rebuttal Report at 131-132.
`
`Dr. Wolfe uses these non-produced source code files to assert untimely infringement
`
`theories regarding Find My Device (and its predecessor Android Device Manager) for the
`
`following limitations of the ’970 patent.
`
`
`
`
`
`
`
`6
`
`

`

`Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 8 of 13 PageID #: 9463
`
`
`
`-
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` Each of these
`
`paragraphs and any related portions should be excluded from the Wolfe Report.
`
`HTC’s non-produced source code printouts and source code libraries were not identified
`
`in HTC’s non-infringement contentions. Ex. J. HTC could have and should have produced the
`
`untimely source code printouts and libraries as relevant discovery pursuant to the Court’s
`
`discovery order and P.R. 3-4. With respect to the non-produced Google source code, HTC had
`
`an obligation under the Court’s discovery order to produce any third party productions of
`
`documents, including source code documents, received from a third party such as Google. HTC
`
`cannot hide behind its business relationship with Google, a supplier of the source code, to deny
`
`its obligations.
`
`V.
`
`CONCLUSION
`
`For the foregoing reasons, AGIS respectfully requests that the Court grant AGIS’s
`
`motion to strike portions of the January 11, 2019 Wolfe Report relating to non-produced source
`
`code printouts and libraries.
`
`Dated: January 25, 2019
`
`
`
`
`
`
`
`
`BROWN RUDNICK LLP
`
` /s/ Alfred R. Fabricant
`
`
`
`Alfred R. Fabricant
`
`7
`
`

`

`Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 9 of 13 PageID #: 9464
`
`NY Bar No. 2219392
`Email: afabricant@brownrudnick.com
`Lawrence C. Drucker
`NY Bar No. 2303089
`Email: ldrucker@brownrudnick.com
`Peter Lambrianakos
`NY Bar No. 2894392
`Email: plambrianakos@brownrudnick.com
`Vincent J. Rubino, III
`NY Bar No. 4557435
`Email: vrubino@brownrudnick.com
`Alessandra C. Messing
`NY Bar No. 5040019
`Email: amessing@brownrudnick.com
`Shahar Harel
`NY Bar No. 4573192
`Email: sharel@brownrudnick.com
`John A. Rubino
`NY Bar No. 5020797
`Email: jrubino@brownrudnick.com
`Enrique W. Iturralde
`NY Bar No. 5526280
`Email: eiturralde@brownrudnick.com
`Timothy J. Rousseau
`NY Bar No. 4698742
`Email: trousseau@brownrudnick.com
`Daniel J. Shea, Jr.
`NY Bar No. 5430558
`Email: dshea@brownrudnick.com
`Justine Minseon Park
`NY Bar No. 5604483
`Email: apark@brownrudnick.com
`BROWN RUDNICK LLP
`7 Times Square
`New York, NY 10036
`Telephone: 212-209-4800
`Facsimile: 212-209-4801
`
`Samuel F. Baxter
`Texas State Bar No. 01938000
`Email: sbaxter@mckoolsmith.com
`Jennifer L. Truelove
`Texas State Bar No. 24012906
`Email: jtruelove@mckoolsmith.com
`McKOOL SMITH, P.C.
`104 East Houston Street, Suite 300
`
`8
`
`

`

`Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 10 of 13 PageID #: 9465
`
`Marshall, Texas 75670
`Telephone: 903-923-9000
`Facsimile: 903-923-9099
`
`ATTORNEYS FOR PLAINTIFF, AGIS
`SOFTWARE DEVELOPMENT LLC
`
`
`9
`
`

`

`Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 11 of 13 PageID #: 9466
`
`
`
`CERTIFICATE OF CONFERENCE
`
`I certify that on January 25, 2019, lead and local counsel for AGIS (Alfred R. Fabricant,
`
`Vincent J. Rubino, and Jennifer Truelove) and for HTC (Matthew Bernstein, Miguel J.
`
`Bombach, and Eric Findlay) conferred via telephone in compliance with L.R. CV-7(h-i)
`
`regarding the issues presented in the foregoing Motion. The Parties still were unable to resolve
`
`the issues and are at an impasse regarding the relief sought. The Court assistance is thus
`
`necessary. HTC opposes this Motion.
`
`
`/s/ Alfred R. Fabricant
` Alfred R. Fabricant
`
`
`
`
`
`
`
`
`
`
`
`10
`
`

`

`Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 12 of 13 PageID #: 9467
`
`
`
`CERTIFICATE OF AUTHORIZATION TO FILE UNDER SEAL
`
`The undersigned certifies that the foregoing document is authorized to be filed under seal
`
`pursuant to the Protective Order entered in this case.
`
`
`
`
`
`
`
`/s/ Alfred R. Fabricant
` Alfred R. Fabricant
`
`
`
`
`
`
`
`11
`
`

`

`Case 2:17-cv-00514-JRG Document 132 Filed 01/29/19 Page 13 of 13 PageID #: 9468
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that, on January 25, 2019, all counsel of record who are
`
`deemed to have consented to electronic service are being served with a copy of this document via
`
`the Court’s CM/ECF system per Local Rule CV-5(a)(3).
`
`
`/s/ Alfred R. Fabricant
` Alfred R. Fabricant
`
`
`
`
`
`
`
`
`
`

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