throbber
Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 1 of 20 PageID #: 49800
`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 1 of 20 PagelD #: 49800
`
`IN THE UNITED STATES DISTRICT COURT
`
`FOR THE DISTRICT OF DELAWARE
`
`ACCELERATION BAYLLC,
`
`Plaintiff,
`
`V.
`
`ACTIVISION BLIZZARD INC.,
`
`Defendant.
`
`eeOSaSsaS’
`
`C.A. No. 16-453 (RGA)
`
`REDACTED
`
`PUBLIC VERSION
`
`DEFENDANT’S MOTION TO PRECLUDE THE NEW DAMAGESTHEORIES
`
`PLAINTIFF RAISED AT THE PRETRIAL CONFERENCE
`
`Morris, NICHOLS, ARSHT & TUNNELL LLP
`Jack B. Blumenfeld (41014)
`Stephen J. Kraftschik (#5623)
`1201 North MarketStreet
`P.O. Box 1347
`Wilmington, DE 19899
`(302) 658-9200
`jblumenfeld@mnat.com
`skraftschik@munat.com
`
`Attorneysfor Defendants
`
`OF COUNSEL:
`
`Michael A. Tomasulo
`Gino Cheng
`David K. Lin
`Joe S. Netikosol
`WINSTON & STRAWN LLP
`333 South Grand Avenue, 38th Floor
`Los Angeles, CA 90071
`(213) 615-1700
`
`David P. Enzminger
`Louis L. Campbell
`WINSTON & STRAWN LLP
`275 Middlefield Road, Suite 205
`Menlo Park, CA 94025
`(650) 858-6500
`
`Dan K. Webb
`Kathleen B. Barry
`Sean H. Suber
`WINSTON & STRAWN LLP
`35 West Wacker Drive
`Chicago, IL 60601
`(312) 558-5600
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 2 of 20 PageID #: 49801
`
`Krista M. Enns
`WINSTON & STRAWN LLP
`101 California Street, 35th Floor
`San Francisco, CA 94111
`(415) 591-1000
`Michael M. Murray
`Anup K. Misra
`WINSTON & STRAWN LLP
`200 Park Avenue,
`New York, NY 10166
`(212) 294-6700
`Andrew R. Sommer
`Thomas M. Dunham
`Joseph C. Masullo
`Paul N. Harold
`WINSTON & STRAWN LLP
`1700 K Street, N.W.
`Washington, DC 20006
`(202) 282-5000
`
`B. Trent Webb
`Aaron E. Hankel
`Jordan T. Bergsten
`Maxwell C. McGraw
`SHOOK HARDY & BACON LLP
`2555 Grand Boulevard
`Kansas City, MO 64108
`(816) 474-6550
`Original Filing Date: October 22, 2018
`Redacted Filing Date: October 29, 2018
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 3 of 20 PageID #: 49802
`
`
`
`That a prevailing patentee is entitled to no less than a reasonable royalty “does not mean that
`
`the rules of evidence do not apply.” AVM Techs., LLC v. Intel Corp., 927 F. Supp. 2d 139, 146 (D.
`
`Del. 2013). Acceleration “cannot introduce a damages theory to the jury without establishing its
`
`reliability.” Id. at 147. After the Court excluded Acceleration’s two attempts to state an admissible
`
`claim for a reasonable royalty, Acceleration now intends to present to the jury two “fact-based”
`
`approaches it described at the pretrial conference – (1) the cost to write the entire code base for the
`
`accused products, including code having nothing to do with accused networking functions and (2)
`
`the revenue for the accused products based on product sales.1 These are nothing more than the bases
`
`for the royalty rates that the Court previously excluded because plaintiff could not identify
`
`admissible evidence to support its proposed rate. D.I. 600. Now that both of its proposed rates have
`
`been excluded, these untethered proposed royalty bases cannot become admissible when recast as
`
`“fact-based” theories.
`
`To be clear, what Acceleration is proposing is to put
`
` numbers before the jury
`
`with no reasonable royalty calculation, and to ask the jury to award a large verdict. That is legally
`
`impermissible. Uniloc USA, Inc. v. Microsoft Corp., 632 F.3d 1292, 1315 (Fed. Cir. 2011).
`
`Damages must be based on admissible facts. Contrary to Acceleration’s arguments, Apple Inc. v.
`
`Motorola, Inc., does not support a different rule. In that case, the plaintiff’s damages expert actually
`
`put forward an admissible calculation of reasonable royalty damages. 757 F.3d 1286, 1329 (Fed.
`
`Cir. 2014). Acceleration’s failure to propose any admissible evidence requires exclusion of its new
`
`damages theories and related facts.
`
`
`1 At the pretrial conference, Acceleration also described a revenue approach based on the number
`of users. Yesterday afternoon, Acceleration advised that it would not rely on the number of users
`as a separate royalty base, but maintains it will present that information to the jury. Ex. 2.
`
`
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 4 of 20 PageID #: 49803
`
`
`
`I. Background
`
`On August 29, 2018, the Court excluded Acceleration’s only expert opinion on a reasonable
`
`royalty calculation. D.I. 578. Acceleration proposed a new reasonable royalty of 15.5% applied to
`
`three royalty bases. On October 17, 2018, the Court precluded this royalty rate and its associated
`
`royalty bases as unsupported by admissible evidence. D.I. 600.
`
`At the pretrial conference, Acceleration for the first time stated that it would present a “fact-
`
`based damages theory” to the jury. In truth, this “fact-based damages theory” is nothing more than
`
`the same royalty bases excluded by the Court’s October 17 Order but now with no royalty rate or
`
`damages calculation whatsoever attached to them. Stated simply, Acceleration plans to present
`
`billion-dollar figures that supposedly constitute a “fact-based damages theory” together with a
`
`purported apportionment and a Georgia-Pacific analysis that is not tied to any royalty analysis or
`
`damages calculation, and then leave it to the jury to speculate on a damages award.
`
`Acceleration’s first theory is a purported “cost savings” model based on Dr. Valerdi’s
`
`estimate that re-architecting the accused games would have cost
`
`. Ex. 1 (Pretrial Conf. Tr.)
`
`at 4:9–11. Dr. Valerdi did not provide a “cost savings” analysis for purposes of determining
`
`damages. Rather, Dr. Valerdi provided a cost estimate for writing and maintaining the entire code
`
`base for the accused products.2 To do this, Dr. Valerdi used a computer model to estimate the
`
`amount the accused games should have cost in total to develop, and declared that estimate to be the
`
`same as a redesign cost. Ex. 3, Valerdi Dep. Tr. 100:6–11. He input into this model an estimate of
`
`the total lines of compiled code in the accused products. Valerdi Report (D.I. 444, Ex. C-2) at 4, 12–
`
`13; Ex. 5 (Valerdi errata). He did not confine his cost analysis to the code related to the accused
`
`2 “I further relied on their opinions that there are no viable non-infringing alternatives to the Asserted
`Claims, but that, if there were such an alternative, it would require rearchitecting the game to
`develop a new network architecture and associated functionality. I set forth to estimate the cost to do
`so.” Valerdi Report (D.I. 444, Ex. C-2) at 3.
`
`2
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 5 of 20 PageID #: 49804
`
`
`
`functionality in this case. Id.; see also Ex. 3, Valerdi Dep. Tr. 97:19–98:15. His analysis has
`
`nothing to do with the patented technology, and he testified (a) he did not know what is accused of
`
`infringement in the games, (b) he did not consider the patents at all in his analysis. Ex. 3, Valerdi
`
`Dep. Tr. 97:19–98:15. He also did not consider the actual cost to design the games. Ex. 3, Valerdi
`
`Dep. Tr. 100:12–20.
`
`Dr. Meyer stated that Dr. Valerdi’s estimates were not an “indicator of value” for the patents
`
`that would have been used by the parties in a hypothetical negotiation:
`
`“The conservative estimates by Dr. Valerdi, taking into account only a portion of the
`necessary costs and not accounting for the risk of delay or failure, further reinforce that an
`NIA [non-infringing alternative], even if one were to be technologically feasible, would have
`been unlikely to be economically viable at the time of the hypothetical negotiation. Hence,
`while the maximum willingness of the Defendants to pay a royalty is likely to have been
`quite high, it is necessary to rely on other indicators of value available in the
`marketplace to determine a reasonable royalty in this matter.”
`
`Meyer Report (D.I. 444, Ex. C-3) at ¶57 (emphasis added).
`
`Acceleration’s second proposed royalty theory is a “revenue model” based on “revenue and
`
`the profits of the infringing technology over the relevant time period.”3 Ex. 1 (Pretrial Conf. Tr.) at
`
`4:14–17. Acceleration also stated that it plans to introduce evidence of the number of users and units
`
`of the games as an additional data point.
`
`Acceleration stated that Dr. Meyer would apportion one or more of these royalty bases in the
`
`manner set forth in her expert report. With respect to World of Warcraft, Dr. Meyer did not provide
`
`any apportionment—she opined that one hundred percent of World of Warcraft revenues (from both
`
`product sales and user subscriptions) are attributable to the alleged infringement. At the pretrial
`
`conference, Acceleration confirmed that the alleged infringement claim for World of Warcraft was
`
`
`3 Acceleration has not indicated what a “revenue-based model” based on “revenue and profits of the
`infringing technology” actually is. It is unclear whether Acceleration plans to use both revenue or
`profits or both. In any event, Acceleration has no witness who can explain such a model.
`
`3
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 6 of 20 PageID #: 49805
`
`
`
`limited to “cross realm functionality” that was added to the game by an upgrade in 2013 or 2014.
`
`Ex. 1 (Pretrial Conf. Tr.) at 45:13–18, 49:17–21, 60:3–23. Yet Dr. Meyer provided no
`
`apportionment opinion for this cross-realm functionality.
`
`With respect to Call of Duty and Destiny, Dr. Meyer similarly assumed that one hundred
`
`percent of the “multiplayer” functionality is attributable to accused functionality without any
`
`analysis of other multiplayer and networking functionality not accused of infringement.4
`
`Absent from Acceleration’s theories is any expert opinion that the parties to the hypothetical
`
`negotiation would have used any of these facts in reaching a reasonable royalty. Dr. Meyer’s sole
`
`opinion relied exclusively on a per unit/user royalty based on the Uniloc jury verdict, which has now
`
`been excluded. See Meyer Report (D.I. 444, Ex. C-3) at ¶149. The new proposed theories are
`
`different and further removed from the required analysis, and Acceleration has no witness who can
`
`connect them to a hypothetical negotiation between Boeing and Activision at the relevant time.
`
`Because Acceleration has no evidence of a royalty rate, it proposes to simply present the
`
`bases as “raw data” and ask the jury, without any calculation or guidance, to use these enormous
`
`numbers to determine a “lump sum royalty on the life of the sales of those patents” in a vacuum. Ex.
`
`1 (Pretrial Conf. Tr.) at 5:5–8, 14:22–15:10, 18:3–5.
`
`II. A reasonable royalty must be tethered to the patented technology and based on
`sound economic principles.
`
`Neither the theories nor the evidence Acceleration seeks to advance are admissible.
`
`Acceleration sought previously to introduce these theories as royalty bases for a 15.5% royalty. The
`
`Court held that “the 15.5% royalty and the bases associated with it are effectively precluded as
`
`well.” D.I. 600 at 7. Acceleration’s new plan to present these same royalty bases without any
`
`4 Multiplayer games just mean they involve more than one player. The ‘069 and ‘147 patents
`asserted against Call of Duty and Destiny require a minimum of six players to form an allegedly
`infringing network.
`
`4
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 7 of 20 PageID #: 49806
`
`
`
`royalty rate is equally inadmissible. Exmark Mfg. Co. Inc. v. Briggs & Stratton Power Prod. Grp.,
`
`LLC, 879 F.3d 1332, 1350 (Fed. Cir. 2018).
`
`The patentee bears the burden of proving damages. Lucent Techs., Inc. v. Gateway, Inc., 580
`
`F.3d 1301, 1324 (Fed.Cir.2009). To properly carry this burden, the patentee must “sufficiently tie
`
`the expert testimony on damages to the facts of the case.” Uniloc USA, Inc. v. Microsoft Corp., 632
`
`F.3d at 1315. If the patentee fails to tie the theory to the facts of the case, the evidence must be
`
`excluded. Id. A damages award may not be based on “speculation or guesswork.” Lucent Techs,
`
`580 F.3d at 1309.
`
`In Exmark, the Federal Circuit held that expert testimony regarding the Georgia Pacific
`
`factors is admissible only if it is tied to a specific proposed royalty rate. Id. at 1349–51. The expert
`
`there discussed “each of the Georgia-Pacific factors, including the benefits of the patented
`
`technology, sales and profitability, and the competitive relationship of the parties” and “concluded
`
`with little explanation that Exmark and Briggs would have agreed to a 5% reasonable royalty rate on
`
`the sales of the accused [products].” Id. at 1349. Her opinions were inadmissible because she did
`
`not “tie the relevant Georgia-Pacific factors to the 5% royalty rate or explain how she calculated a
`
`5% royalty rate using these factors.” Id. The Court noted that a “superficial recitation of the
`
`Georgia-Pacific factors, followed by conclusory remarks, [cannot] support the jury’s verdict” and
`
`held that when “performing a Georgia-Pacific analysis, damages experts must not only analyze the
`
`applicable factors, but also carefully tie those factors to the proposed royalty rate.” Id. at 1350.
`
`Here, Acceleration plans to offer a Georgia Pacific analysis without any rate or royalty at
`
`all. Because Acceleration proposes no rate or royalty, there is no “reasonable royalty analysis” that
`
`“carefully” ties the “proof of damages to the claimed invention’s footprint in the market place.”
`
`ResQNet.com, Inc. v. Lansa, Inc., 594 F.3d 860, 869 (Fed. Cir. 2010). The analysis must be
`
`5
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 8 of 20 PageID #: 49807
`
`
`
`carefully tied to the evidence of alleged infringement because “the ultimate combination of royalty
`
`base and royalty rate must reflect the value attributable to the infringing features of the product, and
`
`no more.” Ericsson, Inc. v. D– Link Sys., Inc., 773 F.3d 1201, 1226 (Fed. Cir. 2014). Without such
`
`evidence, Acceleration’s latest theories must be excluded. Uniloc, 632 F.3d at 1315 (royalty must be
`
`tied to facts of the case).
`
`Just as Acceleration’s experts cannot speculate, Acceleration cannot “urg[e] jurors to rely on
`
`[their own] speculation.” Lucent Techs., Inc. v. Gateway, Inc., 580 F.3d 1301, 1327 (Fed. Cir.
`
`2009). If Acceleration cannot identify an admissible royalty rate, it cannot ask the jury to “pluck[]
`
`[one] from thin air.” Finjan, Inc. v. Blue Coat Sys., Inc., 879 F.3d 1299, 1312 (Fed. Cir. 2018).
`
`Apple, the principal case upon which Acceleration relies, states that if there is no “evidence on which
`
`to base a damages award, the record may well support a zero royalty award.” 757 F.3d at 1328. “A
`
`factfinder cannot be asked to speculate,” so Acceleration must “present competent evidence
`
`regarding how the factfinder should perform the reasonable royalty calculation.” Unicom
`
`Monitoring, LLC v. Cencom, Inc., 2013 WL 1704300, at *8 (D.N.J. Apr. 19, 2013). Its “failure to
`
`present competent evidence … is fatal to [its] claim for reasonable royalty damages.” Id.
`
`III. Dr. Valerdi’s opinion is not admissible because it is not apportioned to the patented
`technology and is not about cost saving.
`
`Dr. Valerdi’s expert report does not provide an admissible cost savings damages analysis.
`
`Dr. Valerdi provides an opinion that the cost to write and maintain the entire code base for the
`
`accused products totals approximately
`
`. He did not estimate the cost for changing only the
`
`code directed to the accused functionality. Nor did he estimate any savings Activision may have
`
`achieved by using the allegedly infringing functionality over a non-infringing alternative.
`
`Accordingly, Dr. Valerdi’s opinion is not admissible to support a damages finding.
`
`6
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 9 of 20 PageID #: 49808
`
`
`
`A. Dr. Valerdi’s opinion is not apportioned or tied to the patented technology.
`
`Dr. Valerdi purported to present the cost of rewriting the source code base for the accused
`
`products to become non-infringing. In reality, Dr. Valerdi estimated the cost of rewriting the entire
`
`code base for the accused products, including all files that fall outside the accused networking
`
`functions. See Valerdi Report (D.I. 444, Ex. C-2) at 1. Nothing in his report suggests which features
`
`would have to be rewritten to avoid infringement, let alone the costs of rewriting just those portions
`
`of the code. In fact, he testified he did not know what features are associated with the patented
`
`technology, see, e.g., Ex. 3, Valerdi Dep. Tr. 119:3–9, 133:3–16, and he did not know and “was not
`
`interested in how [the developers] would re-architect or what part of the game would need to be re-
`
`architected,” id. at 97:19–98:15.
`
`For example, for World of Warcraft, counsel for Acceleration stated at the pretrial conference
`
`that the functionality accused of infringement is limited to the “cross-realm” features introduced in
`
`2013. Ex. 1 (Pretrial Conf. Tr.) at 45:13–18. Dr. Valerdi did not provide any opinion on the cost of
`
`removing or altering these “cross-realm” functions. Rather, he provided an estimated cost for
`
`writing the entire World of Warcraft game code, of which “cross-realm” functionality is only a
`
`miniscule portion.
`
`Similarly, for Call of Duty and Destiny, Dr. Valerdi estimated the cost of writing the entire
`
`code base, including third party tools, graphics and other code having nothing to do with networking.
`
`Because Dr. Valerdi addressed the cost of writing the entire code base for the accused products,
`
`without any limitation or apportionment to the specific features accused of infringement, his opinion
`
`is not admissible to support a damages theory. In addition, although most claims against Call or
`
`Duty and Destiny “dropped out … on summary judgment,” Dr. Valerdi’s estimate did not change—
`
`“suggesting that [it] was never tied to the specific patents at issue.” Apple, 757 F.3d at 1325 n.5.
`
`7
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 10 of 20 PageID #: 49809
`
`
`
`B. Dr. Meyer acknowledged that Dr. Valerdi’s report does not support a damages
`theory.
`
`Acceleration’s own damages expert expressly confirms that Dr. Valerdi’s estimates were not
`
`a reliable indicator of the value of the patented technology. Meyer Report (D.I. 444, Ex. C-3) at ¶57.
`
`She used his estimates simply to argue that non-infringing alternatives would not have been
`
`“economically viable” and that, accordingly, Activision would have been willing to pay a high
`
`royalty. She did not calculate a royalty based on his estimates and expressly stated that it was
`
`“necessary to rely on other indicators of value ... to determine a reasonable royalty in this
`
`matter.” Id. Thus, this case is very different than Prism, where the expert “testified that the parties
`
`would have valued the [] patents based on Sprint’s expected cost savings.” Prism Techs. LLC v.
`
`Sprint Spectrum L.P., 849 F.3d 1360, 1378 (Fed. Cir. 2017) (emphasis added). Here, Dr. Meyer’s
`
`opinion is the exact opposite.
`
`C. Dr. Valerdi’s estimate is not a cost savings analysis.
`
`But even more fundamentally, Dr. Valerdi’s opinion is not a “cost savings” analysis at all.
`
`Even Dr. Meyer testified “there is no basis upon which to do a cost analysis or cost savings
`
`analysis.” Ex. 4, Meyer (Take-Two) Dep. Tr. 118:24–120:2. Dr. Valerdi’s analysis is an estimate of
`
`the cost to build the accused games, not a modification or alternative to them. See Ex. 3, Valerdi
`
`Dep. Tr. 100:6–11 (“[Q.] So what were you trying to estimate, then? A. [I]n the case of the
`
`Activision report, the cost of developing the software as is[.]”) (emphasis added); see also id. at
`
`83:10–19, 97:16–98:11, 99:7–19, 100:5–11, 103:17–20. When Dr. Valerdi used the estimated
`
`number of lines of code from the existing accused games as the input to his model, he was actually
`
`generating an estimate of the cost to develop the existing accused games, not an alternative game.
`
`Dr. Valerdi only says that his estimate also applies to a re-architected alternative game
`
`because he assumed that the existing game and a re-architected hypothetical non-infringing
`
`8
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 11 of 20 PageID #: 49810
`
`
`
`alternative would both require writing the same number of lines of code. But with that assumption,
`
`Dr. Valerdi’s computer model will always generate the same cost estimate for the existing games as
`
`it does for the alternative. “[T]he same inputs (project characteristics) would generate the same
`
`outputs (cost and schedule).” Valerdi Report (D.I. 444, Ex. C-2) at 4; Ex. 3, Valerdi Dep. Tr. 68:25–
`
`69:13 (“The SEER model, like other cost models, are what’s considered to be a deterministic model
`
`– same inputs always create the same outputs…”). If the existing games and the alternative
`
`technology each required the same number of lines of code (input), there can be no “cost savings.”
`
`D. Dr. Valerdi’s opinion is inadmissible under FRE 403.
`
`Even if Dr. Valerdi’s opinions were otherwise admissible, they should be excluded under
`
`Fed. R. Evid. 403. By using the number of code lines of the existing accused games as his starting
`
`point, Dr. Valerdi’s computer model estimated that it should have cost Activision and Bungie Inc.
`
`more than
`
` to write and maintain the source code of the existing accused products. See Ex.
`
`3, Valerdi Dep. Tr. 100:6–11. Because Dr. Valerdi’s estimate is not tailored to the cost of changing
`
`the specific accused functionality, it has no relevance or probative value to a reasonable royalty.
`
`Further, Dr. Valerdi’s cost estimate for rewriting the entirety of the accused games dwarfs the actual
`
`development costs of the accused games, which further demonstrates its lack of probative value.
`
`Given that the actual costs were produced; what relevance is Dr. Valerdi’s litigation-inspired
`
`estimate of those costs?
`
`Further, the prejudice to Activision from allowing Dr. Valerdi’s opinion to be presented to
`
`the jury greatly outweighs its probative value. Its sole purpose is to put a huge, irrelevant number
`
`before the jury. Hynix Semiconductor Inc. v. Rambus Inc., 2008 WL 504101, at *1 (N.D. Cal. Feb.
`
`20, 2008) (excluding a “dollar figure” estimate). “[E]ven with a limiting instruction, the probative
`
`value of the dollar amounts [would be] substantially outweighed by the risk of unfair prejudice.”
`
`9
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 12 of 20 PageID #: 49811
`
`
`
`EMC Corp. v. Pure Storage, Inc., 2016 WL 775742, at *3 (D. Del. Feb. 25, 2016). If Acceleration is
`
`allowed to do this, the damage cannot be undone. It should be excluded.
`
`IV. Total revenues and profits, without proper apportionment, are inadmissible.
`
`A reasonable royalty award “must be based on the incremental value that the patented
`
`invention adds to the end product.” Ericsson, 773 F.3d at 1226. Nowhere does Acceleration
`
`disclose any quantifiable value of the patented inventions. Royalty bases reflecting a product’s
`
`entire value are inadmissible because they “cannot help but skew the damages horizon for the jury.”
`
`Uniloc, 632 F.3d at 1320. Acceleration cannot rely on revenues because basing damages on a
`
`product’s total value violates the rules of evidence and the patent damages statute. “Admission of
`
`such overall revenues, which have no demonstrated correlation to the value of the patented feature
`
`alone, only serve to make a patentee’s proffered damages amount appear modest by comparison, and
`
`to artificially inflate the jury’s damages calculation beyond that which is ‘adequate to compensate
`
`for the infringement.’” LaserDynamics, 694 F.3d at 68. As an “evidentiary” matter, it risks
`
`“misleading the jury by placing undue emphasis on the value of the entire product.” Commonwealth
`
`Sci. & Indus. Research Organisation v. Cisco Sys., Inc., 809 F.3d 1295, 1302 (Fed. Cir. 2015).
`
`Indeed, “disclosure of the end product’s total revenue ‘cannot help but skew the damages horizon for
`
`the jury, regardless of the contribution of the patented component to this revenue.’” Id. (quoting
`
`Uniloc, 632 at 1320). Juries are “less equipped to understand the extent to which the royalty rate
`
`would need to do the work in such instances,” and need “a more realistic starting point for the
`
`royalty calculations.” Ericsson, 773 F.3d at 1227. Legally, it “carries a considerable risk that the
`
`patentee will be improperly compensated for non-infringing components”—violating Section 284.
`
`Commonwealth Sci., 809 F.3d at 1302.
`
`World of Warcraft. Dr. Meyer’s discussion regarding apportionment appears at paragraphs
`
`169-176 of her report. Dr. Meyer attributed “100 percent” of World of Warcraft’s value to “the
`
`10
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 13 of 20 PageID #: 49812
`
`
`
`Patents-in-Suit” based on her assumption that the game is “always infringing the Patents-in-Suit.”
`
`Meyer Report (D.I. 444, Ex. C-3) at 90. But that is not the correct test. A royalty base of total
`
`revenues is permissible only where the patentee can “establish that its patented technology drove
`
`demand for the entire product.” Virnetx, Inc. v. Cisco Sys., Inc., 767 F.3d 1308, 1329 (Fed. Cir.
`
`2014). It “is not enough to merely show that the [patented feature] is viewed as valuable, important,
`
`or even essential to the use of the [infringing product],” it must be “the sole driver of customer
`
`demand.” Power Integrations, Inc. v. Fairchild Semiconductor Int’l, Inc., 904 F.3d 965, 979 (Fed.
`
`Cir. 2018) (quoting LaserDynamics, Inc. v. Quanta Computer, Inc., 694 F.3d 51, 68 (Fed. Cir.
`
`2012)). Acceleration has no such evidence.
`
` “Merely concluding that other components do not affect the value of the accused [product]
`
`amounts to nothing more than speculation.” Exmark, 879 F.3d at 1350. At the Pretrial Conference,
`
`counsel admitted that its infringement theory relates to a “particular patch” added to the game in
`
`2013 – nearly ten years after World of Warcraft had already become one of the most successful
`
`online multiplayer video games of all time. Ex. 1 at 45:13–18. There is no evidence that the
`
`topology of a purported broadcast channel in the server-to-server network and alleged to be part of
`
`that “particular patch” was “the sole driver of customer demand.” Power Integrations, 904 F.3d at
`
`979. In fact, there is no evidence that customers care at all how World of Warcraft servers are
`
`connected, let alone whether they ever use an m-regular broadcast channel with six or more
`
`participants.
`
`Dr. Meyer even attributed 100% of sales of the World of Warcraft game applications that are
`
`not accused of infringement of the patents-in-suit. See Medvidovic Report (D.I. 443 Ex. A-1) ¶2
`
`(accusing only the back-end “World of Warcraft Server-to-Server” network that does not include the
`
`game applications). There is no evidence that the volume of unit sales of non-infringing game
`
`11
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 14 of 20 PageID #: 49813
`
`
`
`applications has any technical or economic relationship with the accused patch of the World of
`
`Warcraft Server-to-Server Communications Network added in 2013.
`
`Call of Duty/Destiny. Dr. Meyer failed to do any apportionment of the patented
`
`technology’s contribution to Call of Duty or Destiny. Meyer Report (D.I. 444, Ex. C-3) at 88–90.
`
`Instead, as the sole basis for her purported apportionment, Dr. Meyer referenced a single internal
`
`
`
`
`
`
`
` Moreover, although
`
` did not address
`
`Destiny, Dr. Meyer used the same figures for her alleged apportionment of that game as well. Id. at
`
`89. The basis of her conclusion was her belief that “multiplayer” was the “main purchase driver” for
`
` of Call of Duty purchasers. Again, this is not the right test. Even though Dr. Meyer
`
`admitted that “all multiplayer functionality is not accused or at issue,” she made no effort to
`
`apportion them out. Meyer Reply Report (D.I. 444, Ex. C-5) at 15. When relying on
`
`
`
` “the patented feature must be separated” (Virnetx, 767 F.3d at 1333), and multiplayer is a
`
`“broad term [that] undoubtedly incorporates consumers’ value for other non-patented … features.”
`
`Blue Spike, LLC v. Huawei Techs. Co., 2016 WL 9286102, at *4 (E.D. Tex. Oct. 14, 2016)
`
`(excluding an apportionment theory based on a survey). Because multiplayer functionality “contains
`
`non-infringing features, additional apportionment [was] still required.” Finjan, 879 F.3d at 1311.
`
`After summary judgment, the only remaining asserted claims against Call of Duty and
`
`Destiny concern methods for joining and departing an m-regular broadcast channel. See D.I. 578 at
`
`3 (dismissing, for Call of Duty, all claims of the ’344, ’966, ’634, and ’497 patents and claims 11,
`
`15, and 16 of the ’147 patent). Joining or leaving an m-regular broadcast channel is not the same as
`
`broad multiplayer functionality. Dr. Meyer’s apportionment includes claims that “dropped out … on
`
`summary judgment,” “suggesting that [it] was never tied to the specific patents at issue.” Apple, 757
`
`12
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 15 of 20 PageID #: 49814
`
`
`
`F.3d at 1325 n.5. There is no evidence that some consumers’ preference for “multiplayer” has
`
`anything to do with the asserted functionality related to joining and departing an m-regular broadcast
`
`channel with six or more participants. There is no admissible evidence that the remaining method
`
`claims asserted against Call of Duty and Destiny account for two-thirds of their value, after four
`
`asserted patents were rejected on summary judgment.
`
`V. There should be a judgment of no damages.
`A. Because Acceleration has strategically and repeatedly chosen to rely on
`inadmissible evidence for its royalty, an award of no royalty is appropriate.
`
`Acceleration has chosen to advance a series of inadmissible damages theories based on its
`
`position that Section 284 requires an award of damages. Not so. Even though infringement
`
`establishes the “fact of damages,” the patentee still must “prov[e] an amount to be awarded.”
`
`Unicom, 2013 WL 1704300 at *5. Acceleration must point to evidence sufficient “to formulate a
`
`royalty,” and because it does not, “[it is] not entitled to collect any royalty.” Devex Corp. v. Gen.
`
`Motors Corp., 667 F.2d 347, 363 (3d Cir. 1981) (affirming an “award of no damages”); see also
`
`Gustafson, Inc. v. Intersystems Indus. Prod., Inc., 897 F.2d 508, 509 (Fed. Cir. 1990) (affirming
`
`award of “no damages” because “none were proven”). “A factfinder cannot be asked to speculate
`
`from numbers unsupported by law and divorced from expert guidance, but rather the factfinder needs
`
`either clear guidance from an expert about how to apply complex calculations or simple factual
`
`proofs about what this patentee has previously accepted in factually analogous licensing situations.”
`
`Unicom, 2013 WL 1704300 at *8. Acceleration does not rely on “expert guidance” or “simple
`
`factual proofs.” Id. Without the ‘tools to arrive at a reasonable royalty, the Court cannot invent one
`
`out of thin air, particularly given that the Federal Circuit requires ‘sound economic proof of the
`
`nature of the market and likely outcomes’ in order ‘to prevent the hypothetical from lapsing into
`
`pure speculation.’” Hollister Inc. v. Zassi Holdings, Inc., 2016 WL 1238025, at *16 (M.D. Fla. Mar.
`
`13
`
`

`

`Case 1:16-cv-00453-RGA Document 618 Filed 10/29/18 Page 16 of 20 PageID #: 49815
`
`
`
`30, 2016) (awarding “zero dollars in damages”). Acceleration has not proffered admissible evidence
`
`from which any factfinder could determine a royalty. The Federal Circuit’s opinion in Apple v.
`
`Motorola is not to the contrary. The court observed there: “For example, in a case completely
`
`lacking any evidence on which to base a damages award, the record may well support a zero royalty
`
`award.” Apple, 757 F.3d at 1328.
`
`B. Acceleration should be precluded from offering a damages case.
`
`This Court is not required to give Acceleration yet another bite at the apple. In circumstances
`
`such as these, the Federal Circuit has expressly approved district courts’ “prevent[ing] [patentees]
`
`from presenting evidence of damages.” ePlus, Inc. v. Law

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