Twilio, Inc. v. Telesign Corporation, No. 5:2016cv06925 - Document 152 (N.D. Cal. 2017)
Court Description: ORDER GRANTING IN PART 121 TELESIGN'S MOTION TO COMPEL AMENDED DAMAGES CONTENTIONS. Signed by Magistrate Judge Susan van Keulen on 11/17/2017. (ofr, COURT STAFF) (Filed on 11/17/2017)
Download PDF
<![CDATA[
Twilio, Inc. v. Telesign Corporation Doc. 152 1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 TWILIO, INC., Plaintiff, 8 v. 9 10 TELESIGN CORPORATION, Defendant. United States District Court Northern District of California 11 12 13 Case No.16-cv-06925-LHK (SVK) I. ORDER GRANTING IN PART TELESIGN'S MOTION TO COMPEL AMENDED DAMAGES CONTENTIONS Re: Dkt. No. 121 Introduction Plaintiff Twilio, Inc. (“Twilio”) initiated this action in December 2016. The parties filed 14 their joint case management statement on February 22, 2017. ECF 45. In accordance with the 15 schedule set forth in the Patent Local Rules, Twilio served its damages contentions on June 20, 16 2017; Defendant Telesign Corporation (“Telesign”) served its responsive damages contentions on 17 July 20, 2017. The parties have engaged in meet and confer efforts, to varying degrees of success. 18 On September 21, 2017, Telesign filed this motion to compel Twilio’s compliance with Patent 19 Local Rule 3-8. The parties have been ordered to an early mediation (ECF 74, 130), which is 20 scheduled for December 4, 2017. 21 Following this Court’s assessment of the requirements of the Patent Local Rules, the 22 arguments presented in the parties’ briefs and at the hearing held on November 14, 2017, 23 Telesign’s motion to compel is granted in part. Twilio will supplement its damages contentions 24 with a computation of damages, as detailed below, no later than November 29, 2017. In addition, 25 the parties will continue rigorous meet and confer efforts and produce additional documents as 26 directed at the hearing and reflected in the record. 27 28 Dockets.Justia.com 1 II. The Patent Local Rules Require a Computation of Damages 2 The Patent Local Rules1 were amended as of January 2017, to address disclosure of 3 damages information, and challenges in this District to L.R. 3-8 are still relatively few. This case, 4 where Twilio has not provided either the reasonable estimate addressed in L.R. 2(b)(5) or a 5 computation as contemplated in L.R. 3-8, presents an opportunity to address the Local Rule 6 requirements to provide clarity to the parties, particularly in light of the impending mediation on 7 December 4, 2107. 8 A. 9 To orient itself and the parties to the disclosure obligations set forth in the Local Rules, the 10 The Rules Court finds it helpful to begin with a relevant definition: United States District Court Northern District of California 11 noun: disclosure 12 1. 13 "A judge ordered the disclosure of the government documents." 14 the action of making new or secret information known. Disclosure, Oxford English Dictionary (3rd Ed. 2010) (Emphasis added). The first instance under the Local Rules where parties are to make known damages 15 16 calculations is the initial case management conference. Local Rule 2(b)(5), in requiring a good 17 faith estimate at the initial case management conference, provides: 18 2. GENERAL PROVISIONS ... (b) Initial Case Management Conference. When the parties confer pursuant to Fed. R. Civ. P. 26(f), in addition to the matters covered by Fed. R. Civ. P. 26, the parties shall discuss and address in the Case Management Statement filed pursuant to Fed. R. Civ. P. 26(f) and Civil L.R. 16-9, the following topics: ... (5) The parties shall provide the court with a non-binding, good-faith estimate of the damages range expected for the case along with an explanation for the estimates. If either party is unable to provide such information, that party shall explain why it cannot and what specific information is needed before it can do so. Such party shall also state the time by which it should be in a position to provide that estimate and explanation. (Emphasis added.) 19 20 21 22 23 24 25 26 27 28 1 All references to the Local Rules are references to the Norther District of California Patent Local Rules and are hereinafter indicated by “L.R.” 2 1 Ninety days later, L.R. 3-8 requires a computation of damages, specifically: 2 3. PATENT DISCLOSURES ... 3-8. Damages Contentions Not later than 50 days after service of the Invalidity Contentions, each party asserting infringement shall: (a) Identify each of the category(-ies) of damages it is seeking for the asserted infringement, as well as its theories of recovery, factual support for those theories, and computations of damages within each category, including: 1. lost profits; 2. price erosion; 3. convoyed or collateral sales; 4. reasonable royalty; and 5. any other form of damages. (b) To the extent a party contends it is unable to provide a fulsome response to the disclosures required by this rule, it shall identify the information it requires. (Emphasis added.) 3 4 5 6 7 8 9 10 United States District Court Northern District of California 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Similarly, the defendant has an obligation to make known, with specificity, its defenses to the damages claimed: 3-9. Responsive Damages Contentions Not later than 30 days after service of the Damages Contentions served pursuant to Patent L.R. 3-8, each party denying infringement shall identify specifically how and why it disagrees with those contentions. This should include the party’s affirmative position on each issue. To the extent a party contends it is unable to provide a fulsome response to the disclosures required by this rule, it shall identify the information it requires. B. Applying the Local Rules in Litigation The requirements of L.R. 3-8 could not be more clear: identify the theories of recovery; identify the known facts that support the theories; do the math. A plaintiff’s persistent deference to a future expert report, as well as a defendant’s insistence on a final expert opinion, is misplaced. Local Rule 3-8 does not require certainty, and it is not fairly interpreted as replacing the robust analysis of a patent damages expert report. It is worth noting that unlike the more rigorous disclosure requirements for infringement and invalidity contentions (see L.R. 3-1, L.R. 3-3), there is no “good cause” threshold for amendment of damages contentions, nor is there even a requirement to amend the contentions. See L.R. 3-6. There is ample room between the initial “non-binding, good faith estimate of the damages range” contemplated by L.R. 2(b)(5) and a damages expert’s report pursuant to Federal Rule of Civil Procedure 26 for meaningful disclosure, 3 1 including a computation, under L.R. 3-8. The timing as to when a plaintiff must provide a computation of damages is not arbitrary. 2 3 The computation follows the disclosure of infringement and invalidity contentions to allow for 4 focus on the actual accused instrumentalities. The Sedona Conference Commentary on Case 5 Management of Patent Damages and Remedies Issues: Proposed Model Local Rule for Damages 6 Contentions, at p. 4 (April 2016, public comment version).2 Yet the damages computation is 7 provided early enough in the course of fact discovery to inform the parties and the court on issues 8 of relevance and proportionality. Id. Finally, the reveal of the computation of damages in the time 9 frame set forth in L.R. 3-8 creates a potential opportunity for meaningful settlement discussions. 10 Id. The expectation built into L.R. 3-8, as well as L.R. 3-9, that there is discovery—perhaps United States District Court Northern District of California 11 12 significant discovery—still to be conducted at the time of computation is not properly construed as 13 an opportunity to ignore the disclosure obligations all together. Contending one is unable to 14 provide a damages calculation should be considered the exception, not the default, as each party 15 exercises its best, good faith efforts to comply with this Court’s Local Rules. Where the exception 16 lies, and a party feels compelled to state that it has no alternative but to identify additional 17 information it must acquire before it can comply with a particular component of its disclosure 18 obligations, such identification must be specific: 1. Which outstanding discovery request is 19 directed to the particular missing fact? 2. What is the status of meet and confer efforts between 20 the parties to facilitate a timely response? 3. When is a response due and, once received, on what 21 date will the party comply with its disclosure obligation? A party’s failure to provide this 22 information with a high degree of specificity undermines an argument that the information is 23 necessary for a computation of damages. The Court notes that L.R. 3-8 and L.R. 3-9 do not directly address apportionment. The 24 25 Federal Circuit requires that a damages opinion provide an evidentiary basis for the apportionment 26 27 28 2 Available at https://thesedonaconference.org/publication/The%20Sedona%20Conference% 20Commentary%20on%20Case%20Management%20of%20Patent%20Damages%20and%20Rem edies%20Issues%3A%20Proposed%20Model%20Local%20Rule%20for%20Damages%20Conten tions 4 1 of damages between the patented feature and the unpatented features. See Uniloc USA, Inc. v. 2 Microsoft Corp., 632 F.3d 1292, 1318 (Fed. Cir. 2011). Apportionment is an extremely fact- 3 intensive exercise requiring more discovery and analysis than is likely to be completed at the 4 juncture of the damages computation required by L.R. 3-8. Nevertheless, the apportionment 5 requirement does not obviate the need to compute damages under L.R. 3-8. A plaintiff should, at 6 a minimum, identify the likely factors that will be considered in its apportionment calculation, 7 quantify those factors to the extent possible, and identify the outstanding discovery directed to 8 quantifying these factors with the particularity outlined above. 9 Notwithstanding the challenges of determining a viable computation of damages prior to the close of fact discovery, in cases such as the present one it simply is not credible that a full year 11 United States District Court Northern District of California 10 after the filing of the complaint, which certainly followed a diligent investigation, a plaintiff is 12 unable to quantify, with reasonableness if not certainty, the damages it will seek at trial. Nor is it 13 credible that a plaintiff cannot break that quantification into elements of a computation: a royalty 14 base, a royalty rate, and other potential factors that will compose its alleged damages. Indeed, 15 when a party fails to provide even a non-binding estimated range of damages as required by 16 L.R. 2(b)(5), its failure to comply with L.R. 3-8 further reflects an unwillingness, rather than an 17 inability, to provide a computation of damages. With the foregoing guidelines in mind, the Court 18 turns to the contentions at issue. 19 C. Damages Contentions in the Present Case i. Twilio’s Damages Contentions 20 21 In its opening, Twilio’s damages contentions present a number of arguments generously 22 construed to relate to its obligations under L.R. 3-8. Twilio then addresses each of the Georgia- 23 Pacific factors, primarily, but not exclusively, identifying broad categories of documents it 24 contends are necessary for its calculations. The Court does not find it productive at this juncture to 25 review Twilio’s approach in detail but provides direction as to the form and substance of damages 26 contentions under L.R. 3-8 and L.R. 3-9 by addressing a few general points. 27 28 Briefing in the disclosure statement on the legal parameters for treble damages is unnecessary. Local Rule 3-1 already requires that a party set forth the basis for an 5 1 allegation of willful infringement. If, for completeness, a plaintiff wishes to 2 restate the contention, a short recitation of relevant facts is all that is necessary. 3 Similarly, a brief in support of injunctive relief is unnecessary. L.R. 3-8 and L.R. 4 3-9 are directed to damages. While not inappropriate to state that a party intends to 5 seek an injunction, the extensive legal and factual argument for such relief 6 obfuscates the objective of L.R. 3-8 which is to provide a computation of damages. 7 Reservation of the right to amend after every instance where a plaintiff either discloses or comes close to disclosing a fact in support of its damages theories is 9 unnecessary. Local Rule 3-8 does not foreclose future adjustments to the damages 10 computation. If a party feels compelled, however, to reserve its rights to continue 11 United States District Court Northern District of California 8 to develop its damages calculations, a single reservation at the outset of the 12 contentions will suffice. 13 ii. Telesign’s Responsive Damages Contentions 14 Similarly, under L.R. 3-9, a defendant must resist making non-infringement and invalidity 15 arguments throughout its response to plaintiff’s damages contentions. Responsive contentions are 16 the place to set forth for the plaintiff and the court where defendant finds factual discrepancies in 17 plaintiff’s damages theories and computations, assuming a finding of liability. For the reasons 18 stated above, briefs in opposition to claims of willful infringement and/or injunctive relief are not 19 only unhelpful but detract from the ability of the responsive contentions to educate the court as to 20 pertinent issues, such as proportionality. 21 22 iii. Status of Production of Relevant Documents Twilio’s Contentions and Opposition identify numerous categories of documents that it 23 claims are necessary for a calculation of damages. Yet, Twilio identifies only one specific request 24 for production: All documents related to the determination of a reasonable royalty. ECF 101-5 at 25 3. Such a request may be helpful as a catchall discovery demand, but is not, without more, an 26 adequate foundation upon which to complain that a party lacks sufficient information to compute 27 damages. 28 Telesign, in turn, argues repeatedly that it has produced the documents required by the 6 1 Local Rules and that such productions should be sufficient for a computation of damages. While 2 the production requirements of L.R. 3-4 are a good place to start, they are merely the start, not the 3 end, of Telesign’s obligations. Telesign has an obligation to engage in good faith meet and confer 4 efforts with Twilio to reach compromise on the additional data to be produced. At the hearing, Twilio helpfully narrowed the categories of necessary documents to four, at 5 6 least for purposes of its immediate computation obligations and the December mediation, and 7 updated the Court as to the meet and confer status of each. Telesign’s production obligations as to 8 these categories, including deadlines, are set forth in the record of the hearing. The Court strongly 9 urges the parties to continue their meet and confer efforts with regards to their discovery obligations and to that end provides the following frame of reference. It is not uncommon in 11 United States District Court Northern District of California 10 patent damages discovery for the plaintiff to seek a complete financial history of all of defendant’s 12 products. Similarly, the defendant often seeks to limit production to an incredibly narrow base 13 and time frame. Where plaintiff demands the beach, defendant responds with a few grains of 14 sand. It is counsel’s duty to educate their clients on the relevant law as well as the requirements of 15 the Local Rules and to meet and confer in good faith to allow both sides to fulfill those 16 obligations. Only when there is an actual impasse, an inability to find a reasonable compromise, 17 should the dispute come to court. Some of Twilio’s demands, as framed in its contentions, are 18 aggressively overbroad and beyond the bounds of relevance and proportionality. Similarly, 19 several of Telesign’s objections to production are facially not well taken, particularly in light of 20 well-established factors of apportionment. With these cautions in mind, the parties must turn their 21 attention to earnest meet and confer efforts. 22 // 23 // 24 // 25 // 26 // 27 28 7 1 2 3 CONCLUSION 1. Twilio is to supplement its damages contentions with a reasonable good faith computation of damages no later than November 29, 2017. The computation must identify the following: 4 o royalty base(s) 5 o royalty rate(s) 6 o date(s) of the hypothetical negotiation currently used, 7 o factors identified to date that are or will be used in apportionment, and where possible a quantification of those factors. 8 9 10 United States District Court Northern District of California 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 As set forth above, this computation is not expected to be Twilio’s final computation of damages, and the computation may change without amendment to the contentions. The Court notes, however, that a new theory of recovery (such as lost profits instead of or in addition to a reasonable royalty), would require amendment to the damages contentions. 2. The parties met and conferred on usage metric documents to be produced by Telesign. At the hearing, the parties identified a subset of usage metric documents for accelerated production. Telesign is to produce and/or confirm completion of production of those certain damages-related documents by November 22, 2017, in accordance with the hearing record. Any production is to begin promptly and continue on a rolling basis. 3. In addition to the four specific categories of documents addressed at the hearing, the parties are ordered to continue good faith meet and confer efforts to resolve issues regarding the scope of outstanding requests of damages-related documents and the timing of production, including identification of a date for completion of production of damages-related documents. The Court reminds the parties that the case management schedule allows only 30 days from the close of fact discovery for opening expert reports. SO ORDERED. Dated: November 17, 2017 26 27 SUSAN VAN KEULEN United States Magistrate Judge 28 8
]]>
Some case metadata and case summaries were written with the help of AI, which can produce inaccuracies. You
should read the full case before relying on it for legal research purposes.
This site is protected by reCAPTCHA and the Google
Privacy Policy and
Terms of Service apply.
