throbber
Case 2:15-cv-01274-JRG-RSP Document 130 Filed 08/08/16 Page 1 of 10 PageID #: 2979
`

`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`
`
`
`

`

`BLITZSAFE TEXAS, LLC,
`

`
`
`
`
`
`

`
`Plaintiff,
`
`
`

`
`
`
`
`
`

`
`v.
`
`
`
`

`
`
`
`
`
`HONDA MOTOR CO., LTD, et al.,

`
`
`
`
`
`

`
`Defendants.
`
`
`

`
`
`
`
`
`

`
`
`
`
`
`
`No. 2:15-CV-01274 (Lead Case)
`
`PLAINTIFF BLITZSAFE TEXAS LLC’S OPPOSITION TO DEFENDANTS’ MOTION
`FOR LEAVE TO SUPPLEMENT INVALIDITY CONTENTIONS
`
`Plaintiff, Blitzsafe Texas, LLC (“Plaintiff” or “Blitzsafe”), files this opposition to
`
`
`
`Defendants’ Motion for Leave to Supplement Invalidity Contentions (Dkt. 125) (“Motion”).
`
`Defendants seek to supplement their invalidity contentions with citations to, and analysis of,
`
`source code from a TOY/PAN interface. (Motion at 1.) Defendants’ Motion comes more than
`
`six months after the due date of their invalidity contentions. Defendants’ original invalidity
`
`contentions, served on January 19, 2016, relied on the TOY/PAN interfaces as prior art products
`
`and disclosed that Edward Fischer had written the code for the TOY/PAN interface (Ex. D, at
`
`14), and yet Defendants never subpoenaed Fisher’s documents, and did not subpoena any other
`
`possible source of the code until May 13, 2016. In fact, Defendants had reason to know about
`
`the source code many months prior to the due date of their invalidity contentions and failed to
`
`pursue it.
`
`
`
`Defendants were aware, at least as early as December 30, 2015, of a prior litigation
`
`between Ford Motor Corporation (“Ford”) and Blitzsafe’s predecessor, Marlowe Patent
`

`
`-1-
`
`

`
`Case 2:15-cv-01274-JRG-RSP Document 130 Filed 08/08/16 Page 2 of 10 PageID #: 2980
`

`
`Holdings, LLC (“MPH”), concerning one of the patents asserted in this case. (See Ex. A, at 21.)
`
`In that case, the TOY/PAN source code was produced to Ford in 2015 by Mr. Fischer. (Dkt.
`
`125-11.) Later in 2015, after the Ford case settled, the Toyota Defendants to this litigation
`
`retained the same expert witness that Ford had retained and who had analyzed the TOY/PAN
`
`product. (See Ex. B.) In December 2015, the Toyota Defendants filed multiple Petitions for
`
`Inter Partes Review (“IPR”) of the patents at issue in this case with the support of this expert.
`
`(Ex. A.) Attached to those IPR petitions were declarations prepared by their expert witness in
`
`which he discusses his involvement in the prior Ford litigation. (See Ex. A and B.) Defendants’
`
`review of the Ford case informed them that “Ford managed to locate a copy of the TOY/PAN
`
`source code from the third-party author of that code.” (Motion, at 4.) Thus, Defendants became
`
`aware of the prior litigation more than seven months ago, and it clearly informed them of the
`
`location of the information that they now wish to use to supplement their invalidity contentions.
`
`
`
`Despite knowing the location of the source code many months ago, Defendants now
`
`assert that “any delay in disclosing these contentions is a direct result of Blitzsafe’s failure to
`
`retain and produce its own source code.” (Motion, at 2.) In fact, it appears that although MPH’s
`
`outside counsel obtained a copy of the source code that had been produced to Ford by Mr.
`
`Fisher, that code was stamped “Attorneys Eyes Only” and was never provided to Ira Marlowe,
`
`MPH’s principal. (Ex. C.) Therefore, Blitzsafe was not in possession of the source code and,
`
`therefore, it was not collected or produce by Blitzsafe in this litigation.
`
`
`
`Defendants have failed to explain how the new source code citations and analysis are
`
`highly relevant or an improvement over the assertions made in Defendants’ initial invalidity
`
`contentions. Defendants already contend in their invalidity contentions that the TOY/PAN
`
`                                                            
`1 All exhibits to Blitzsafe’s opposition to Defendants’ motion for leave to supplement their
`invalidity contentions are attached to the declaration of Alessandra Messing, attached hereto.
`-2-
`

`
`

`
`Case 2:15-cv-01274-JRG-RSP Document 130 Filed 08/08/16 Page 3 of 10 PageID #: 2981
`

`
`device is prior art to the asserted patents and contain all of the features of several asserted claims,
`
`and Defendants’ expert submitted an affidavit in the Ford case that purports to support this
`
`contention (and which is attached to the Motion as Dkt. 125-5.) The source code is therefore of
`
`minimal value to Defendants because it is merely duplicative of their existing invalidity
`
`contentions.
`
`Moreover, Defendants have failed to show that an amendment at this late date would not
`
`be prejudicial to Blitzsafe. Defendants’ entire argument regarding lack of prejudice assumes that
`
`Blitzsafe had possession of the code but failed to produce it. Notably, Defendants’ Motion lacks
`
`any evidence that the code was actually provided to MPH or Mr. Marlowe, and so Defendants’
`
`allegations that Blitzsafe misrepresented whether it has possession of the code are unfounded.
`
`
`
`As explained in further detail below, Defendants’ motion to supplement their invalidity
`
`contentions should be denied.
`
`I.
`
`STATEMENT OF FACTS
`
`
`
`
`
`A. Expert Witness Dr. Matheson and Defendants’ Awareness of Prior Ford Case
`
`The TOY/PAN source code with which Defendants now wish to supplement their
`
`invalidity contentions was produced on February 11, 2015 to Ford Motor Corporation (“Ford”),
`
`in the earlier litigation between Blitzsafe’s predecessor, Marlowe Patent Holdings, LLC
`
`(“MPH”), and Ford. (Dkt. 125-11, at ¶ 6.) The expert retained in that case by Ford was Thomas
`
`G. Matheson, Ph.D. (See Ex. B, at 3.) Dr. Matheson was involved with the Ford case early on,
`
`providing a declaration regarding the functionality and operation of the TOY/PAN interfaces
`
`back in 2013. (See Dkt. 125-5.)
`
`
`
`Shortly after the Ford case settled, in May 2015, Dr. Matheson was retained as an expert
`
`by Defendant Toyota to produce declarations in support of a series of Petitions for Inter Partes
`

`
`-3-
`
`

`
`Case 2:15-cv-01274-JRG-RSP Document 130 Filed 08/08/16 Page 4 of 10 PageID #: 2982
`

`
`Review (“IPR”), cases IPR2016-00418, IPR2016-00419, IPR2016-00421, and IPR2016-00422.
`
`(See Ex. A, at 22; Ex. B.) These four IPR petitions were filed December 30, 2015, each with an
`
`attached declaration by Dr. Matheson. (See Ex. B.) Dr. Matheson, in the Relevant Professional
`
`Experience sections of his IPR declarations, describes his work in the Ford case. (See Ex. B, at
`
`3.) Additionally, each petition filed by Defendants identifies the Ford case as a Related Matter.
`
`(See Ex. A, at 2.)
`
`
`
`
`
`B. Possession and Production of TOY/PAN Source Code
`
`In the Ford case, Ford filed a Motion for Rule 11 Sanctions, but the Court denied the
`
`motion as “a transparent effort to secure summary judgment, in the guise of Rule 11 sanctions.”
`
`(Dkt. 125-8, at 8.) During discovery, Ford requested information from MPH that had been lost in
`
`2006 due to a leak during a severe storm. (See Dkt. 125-7.) Documents and source code that
`
`Ford sought were destroyed by mold and mildew, and MPH’s data server was subject to
`
`flooding. (Id.) MPH attempted to recover the lost information, and had the server inspected by a
`
`computer repair and upgrade center (the center where the server was purchased). (Id.) However,
`
`the drive had crashed and the computer repair company could not recover the data. (Id.)
`
`After Ford realized that MPH no longer had the source code, it served a document and
`
`deposition subpoena on Mr. Fischer, an engineer who had previously performed work for
`
`Blitzsafe. (Dkt. 125-11.) Mr. Fischer produced documents responsive to Ford’s subpoena,
`
`including a copy of the TOY/PAN source code. (Id.) Mr. Marlowe, having been under the
`
`impression that Mr. Fischer returned all copies of Blitzsafe’s intellectual property years earlier,
`
`was rightfully upset. (See Dkt. 125-10.) Mr. Marlowe was also troubled by the fact that he had
`
`informed Mr. Fischer of the flood and server crash that destroyed much of Blitzsafe's intellectual
`
`                                                            
`2 Only IPR2016-00418 is attached as exemplary.
`-4-
`

`
`

`
`Case 2:15-cv-01274-JRG-RSP Document 130 Filed 08/08/16 Page 5 of 10 PageID #: 2983
`

`
`property in 2006 and, in response, Mr. Fischer mentioned nothing of the copies of Blitzsafe’s
`
`code that he had made and kept. (Id.)
`
`
`
`On February 18, 2015, Ford’s attorney emailed the document production received from
`
`Mr. Fischer to Mr. Kun Cho, MPH’s attorney at the time. (Dkt. 125-9.) The following day, Mr.
`
`Cho responded to the Ford’s attorney’s email saying that he would provide the Fischer
`
`production to Mr. Marlowe despite the fact that the code was marked “Attorneys Eyes Only.”
`
`(Id.) Mr. Marlowe, however, never received Ed Fischer’s copy of the source code from Mr. Cho.
`
`(Id.; see also Ex. C, at ¶2.) In fact, Blitzsafe has never received the TOY/PAN source code that
`
`was sent to Ford’s counsel, and only now has a copy in its possession as a result of the
`
`production from Ford to Defendants in this case. (Ex. C, at ¶3.)
`
`
`
`
`
`C. Defendants’ Supplemental Invalidity Contentions
`
`Defendants first requested the TOY/PAN interface source code from Blitzsafe on March
`
`3, 2016. (Motion, at 5.) Defendants then waited nearly two months to contact Blitzsafe again to
`
`inquire about the source code. (Dkt. 125-13.) Responding to Defendants’ inquiry, Blitzsafe’s
`
`Brown Rudnick attorneys truthfully told Defendants that Blitzsafe does not have the source code
`
`for the TOY/PAN products. (Dkt. 125-17, Ex. C, at ¶2.) Defendants subpoenaed Ford and its
`
`counsel for the source code and eventually obtained it on June 14, 2016. (Motion, at 5.) Now,
`
`six months after filing their invalidity contentions, Defendants submit their motion for leave to
`
`supplement their contentions with citations to and analysis of this source code.
`
`II.
`
`ARGUMENT
`
`
`
`Defendants’ Motion should be denied because Defendants’ have failed to show good
`
`cause for supplementation. P.R. 3-6(b). Defendants have not shown that they were diligent in
`
`obtaining the source code and they have not shown that the source code, and their analysis of the
`

`
`-5-
`
`

`
`Case 2:15-cv-01274-JRG-RSP Document 130 Filed 08/08/16 Page 6 of 10 PageID #: 2984
`

`
`code, is highly relevant, or that Blitzsafe will not be prejudiced by the addition of this
`
`supplemental source code analysis.
`
`A.
`
`Defendants Have Failed to Show they Acted Diligently
`
`
`
`Defendants have failed to meet their burden to show that they acted diligently in locating
`
`the source code. See O2 Micro Intern. Ltd. v. Monolithic Power Systems, 467 F.3d 1355, 1366
`
`(Fed.Cir. 2006) (the moving party has the burden of establishing diligence to amend
`
`contentions). Defendants’ claim that “any delay in disclosing these contentions is a direct result
`
`of Blitzsafe’s failure to retain and produce its own source code” is disingenuous, as there is no
`
`explanation why Defendants did not earlier obtain the source code from either Mr. Fischer,
`
`Ford’s counsel, or Kun Cho, given that their expert was fully aware of its existence. (Motion, at
`
`2.)
`
`Prior to December 30, 2015, Defendants were well aware of the earlier case between
`
`Ford and MPH in which the TOY/PAN source code was produced by Mr. Fischer to Ford’s
`
`attorneys. (Ex. A.) Defendants’ awareness and knowledge of that prior litigation is likely what
`
`lead them to retain the same expert witness, Dr. Matheson. The Toyota Defendants even filed
`
`multiple IPR petitions in December 2015 against the patents at issue in this case, including in the
`
`petitions Declarations by Dr. Matheson which discussed his involvement with the prior Ford
`
`case. (Ex. B.) Additionally, in their original invalidity contentions served on January 19, 2016,
`
`Defendants stated that “Mr. Fischer wrote the source code and designed the circuit board for the
`
`TOY/PAN V.2 interface and other interfaces offered for sale by Blitzsafe of America.” (Ex. D, at
`
`14.) Yet, somehow, Defendants are now making the claim that they were diligent in locating
`
`that very code that they knew Mr. Fisher possessed but which they never sought from him.
`
`(Motion at 7.)
`

`
`-6-
`
`

`
`Case 2:15-cv-01274-JRG-RSP Document 130 Filed 08/08/16 Page 7 of 10 PageID #: 2985
`

`
` In their Motion, Defendants point to irrelevant facts from the earlier Ford case in a
`
`misguided effort to blame Blitzsafe for not possessing the source code. They point to the fact
`
`that Blitzsafe’s server crashed and documents grew mold after being flooded in a storm in 2005,
`
`causing a major loss of intellectual property for Blitzsafe. (Dkt. 125-7.) They point to the fact
`
`that in 2010 Ira Marlowe asked a webpage to take down an unauthorized copy of Blitzsafe's
`
`copyrighted intellectual property, which was being reproduced with inaccuracies. (Id.). They
`
`point to the fact that Blitzsafe’s previous contractor produced Blitzsafe’s own intellectual
`
`property in the course of the Ford litigation, which was long after that employee misrepresented
`
`to Blitzsafe that he did not possess such property. (Dkt. 125-9, Dkt. 125-10.) They point to the
`
`fact that, in April 2015, Blitzsafe's current counsel, Brown Rudnick, was retained for settlement
`
`negotiations with Ford. (Dkt. 125-18.) These allegations are all irrelevant to whether Defendants
`
`were diligent in obtaining the information for this amendment. 02 Micro Intern., 467 F.3d at
`
`1366.
`
`
`
`The only facts that matter in assessing the Defendants’ diligence in this instance are the
`
`facts that Defendants knew of the prior Ford case in which the source code was produced, that
`
`Defendants retained the same expert from that prior Ford case, and that Defendants had
`
`knowledge that Ed Fischer was a previous employee of Blitzsafe who wrote source code for
`
`these interfaces - all before January 19, 2016 when Invalidity Contentions were served.
`
`Defendants reasonably should have been aware at least as early as December 2015 of the
`
`location of the source code. 02 Micro Intern., 467 F.3d at 1367 (lack of diligence shown by party
`
`having a reason to know about relevant invalidity theories earlier); Google, Inc. v. Netlist, Inc.,
`
`No. C08–04144 SBA, 2010 WL 1838693, at *2 (N.D.Cal. May 5, 2010) (“The critical
`
`issue is not when [Defendants] discovered this information, but rather, whether they could
`

`
`-7-
`
`

`
`Case 2:15-cv-01274-JRG-RSP Document 130 Filed 08/08/16 Page 8 of 10 PageID #: 2986
`

`
`have discovered it earlier had it acted with the requisite diligence.”). Yet, Defendants did
`
`not obtain and start analyzing the source code until June 14, 2016. (Motion, at 5). Considering
`
`these facts along with Defendants’ six month delay in obtaining the source code, Defendants
`
`have not proven they were diligent. Realtime Data, LLC v. Packeteer, Inc., No. 6:08cv144, 2009
`
`WL 2590101, at *4 (E.D. Tex. Aug. 18, 2009) citing O2 Micro, 467 F.3d at 1366 (affirming
`
`district court's finding that a three month delay with lack of adequate explanation for the delay
`
`showed a lack of diligence).
`
`B. Defendants Have Failed to Show that the Source Code and Is Highly Relevant
`
`
`
`Defendants have failed to show that their citations to, and analysis of, the source code is
`
`highly relevant. Defendants’ Motion simply states that the “source code makes it clear that these
`
`interfaces did in fact generate the claimed ‘device presence signal.’” (Motion, at 8.) However,
`
`Defendants failed to argue that this piece of source code and its analysis is any more relevant
`
`than the 23 other references previously relied on in their invalidity contentions, including the
`
`very TOY/PAN product that Dr. Matheson has already stated in an affidavit has the same
`
`features that Defendants now contend are contained in the code. (Dkt. 125-5.)
`
`
`
`In Defendants’ Motion, instead of putting forth reasons the source code should be found
`
`relevant, Defendants state another irrelevant fact from the Ford case - that MPH and Ford settled
`
`the case, and that the settlement took place after Ed Fischer produced the source code in his
`
`response to the subpoena. (Motion, at 8.) Of course, this is true – settlements always take place
`
`at the end of a case. Defendants then argue there is a public interest in allowing validity of
`
`patents to be challenged in court, which is irrelevant to the Court’s analysis on a motion to
`
`amend invalidity contentions. (Id.) Finally, Defendants allege, without any support, that
`
`Blitzsafe engaged in litigation misconduct and “should not be rewarded.” (Motion, at 9.) The
`
`irrelevance of these allegations to the issue at hand underlines that Defendants cannot show that
`

`
`-8-
`
`

`
`Case 2:15-cv-01274-JRG-RSP Document 130 Filed 08/08/16 Page 9 of 10 PageID #: 2987
`

`
`the source code is “highly relevant.” Innovative Display Tech. LLC v. Acer Inc., 2014 WL
`
`2796555, at *2 (E.D. Tex. June 19, 2014) (finding that Defendants wholly failed to show the
`
`importance of the amendment when Defendants made a conclusory argument that prior art is
`
`critically important and attached amended invalidity contentions, without an explanation of how
`
`the "arts, if supplemented to the original Infringement Contentions, would render a particular
`
`patent invalid").
`
`C. Blitzsafe Will be Unfairly Prejudiced by the Supplementation
`
`Defendants’ argument that Blitzsafe will not be prejudiced is an admission that this
`
`motion should be denied. Defendants state that they are merely seeking to supplement their
`
`invalidity contentions with evidence of the same prior art product that they have already
`
`disclosed. This demonstrates that the amendment is unnecessary and, in Defendants’ own view,
`
`duplicative of evidence already in the record.
`
`The timing of this amendment will create unfair prejudice for Blitzsafe because it comes
`
`with only a few weeks remaining in the fact discovery period when Blitzsafe is busy taking
`
`depositions all over the country and preparing to address Defendants’ and their suppliers' refusal
`
`to produce their own source code and provide other discovery in this case. The production and
`
`reliance on new source code that needs to be analyzed at this late date—when Plaintiff’s experts
`
`are busy reviewing other technical information as part of their preparation of expert report—is
`
`unfair to Blitzsafe given Defendants’ lack of diligence.
`
`
`

`
`
`
`-9-
`
`

`
`Case 2:15-cv-01274-JRG-RSP Document 130 Filed 08/08/16 Page 10 of 10 PageID #: 2988
`

`
`III. CONCLUSION
`
`For the foregoing reasons, Blitzsafe respectfully requests that the Court deny Defendants’
`
`Opposed Motion to Leave to Supplement Invalidity Contentions.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`BROWN RUDNICK LLP
`
`By: __/s/ Alessandra Carcaterra Messing_
`Alfred R. Fabricant
`Texas Bar No. 2219392
`Email: afabricant@brownrudnick.com
`Lawrence C. Drucker
`Email: ldrucker@brownrudnick.com
`Texas Bar No. 2303089
`Peter Lambrianakos
`Texas Bar No. 2894392
`Email: plambrianakos@brownrudnick.com
`Alessandra Carcaterra Messing
`Texas Bar No. 5040019
`Email: amessing@brownrudnick.com
`BROWN RUDNICK LLP
`7 Times Square
`New York, NY 10036
`Telephone: (212) 209-4800
`
`Samuel F. Baxter
`Texas State Bar No. 01938000
`sbaxter@mckoolsmith.com
`Jennifer L. Truelove
`Texas State Bar No. 24012906
`jtruelove@mckoolsmith.com
`MCKOOL SMITH, P.C.
`104 E. Houston Street, Suite 300
`Marshall, Texas 75670
`Telephone: (903) 923-9000
`Facsimile: (903) 923-9099
`
`ATTORNEYS FOR PLAINTIFF,
`BLITZSAFE TEXAS, LLC 
`
`
`
`DATED: August 8, 2016
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`
`-10-

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