throbber
Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 1 of 11 PageID #: 19329
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`AGIS SOFTWARE DEVELOPMENT LLC,
`
`
`Plaintiff,
`
`
`
`v.
`
`
`HUAWEI DEVICE USA INC. ET AL.,
`
`
`Defendants.
`
`
`Case No. 2:17-CV-0513-JRG
`(LEAD CASE)
`
`JURY TRIAL DEMANDED
`
`
`
`
`










`
`
`Case No. 2:17-CV-0516-JRG
`(CONSOLIDATED CASE)
`
`JURY TRIAL DEMANDED
`
` §
`
`
`APPLE, INC.,
`
`
`Defendant.
`
`



`
`
`
`
`
`PLAINTIFF AGIS SOFTWARE DEVELOPMENT LLC’S SUR-REPLY IN
`OPPOSITION TO APPLE INC.’S DAUBERT MOTION TO EXCLUDE THE
`OPINIONS OF MR. ALAN RATLIFF RELATING TO DAMAGES (DKT. 231)
`
`

`

`Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 2 of 11 PageID #: 19330
`Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 2 of 11 PageID #: 19330
`
`
`
`ii
`ii
`
`

`

`Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 3 of 11 PageID #: 19331
`
`AGIS submits this sur-reply memorandum in further opposition to Apple’s Daubert
`
`motion to exclude certain opinions of AGIS’s damages expert Alan Ratliff (Dkt. 231). Apple’s
`
`Reply in support of its motion is essentially a rehash of the arguments in its opening motion
`
`papers. For the reasons set forth below and in AGIS’s opposition (Dkt. 250), Apple’s motion
`
`should be denied.
`
`I.
`
`ARGUMENT
`
`A. Mr. Ratliff’s “Technical Apportionment” is Not Arbitrary and is
`Properly Supported by the Opinions of AGIS’s Technical Expert
`
`
`
`Apple does not dispute that Mr. Ratliff apportions between the patented and non-patented
`
`features, and agrees that Mr. Ratliff’s opinion is based on Mr. McAlexander’s technical analysis
`
`of the value of the accused functions and patented features. Apple simply disagrees with
`
`Mr. McAlexander’s conclusions about the relative significance of the patented technology and
`
`the resulting quantification of that in the damages context by Mr. Ratliff.
`
`
`
`Apple again focuses on a single paragraph of Mr. McAlexander’s report, ignoring the
`
`remainder of his analysis on which Mr. Ratliff relied. See Dkt. 250 at 5. Apple now labels as
`
`“arbitrary” (Dkt. 268 at 2) what is actually an estimate based on substantial qualitative analysis,
`
`an approach condoned by this Court in other similar cases, offering no additional authority,
`
`citing only cases that are clearly distinguishable and do not support the vague, alternative test
`
`which Apple seems to advocate. Apple attempts to distinguish the Federal Circuit’s decision in
`
`Chrimar Holding Co., LLC v. ALE USA Inc., 732 F. App’x 876, 2018 WL 2120618 (Fed Cir.
`
`2018), Dkt. 250 at 7, arguing that the damages analysis in Chrimar was based on royalty rates
`
`from licenses the parties had previously entered and that the apportionment of unpatented versus
`
`patented features was with respect to a standards essential patent and based on descriptions in the
`
`standard itself. Dkt. 268 at 3. But nowhere in Chrimar did the Court limit its opinion to
`
`
`
`

`

`Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 4 of 11 PageID #: 19332
`
`comparisons involving previously-negotiated royalty rates, nor did the Court limit its holding to
`
`SEPs. Chrimar permits a damages expert to rely on a technical expert’s analysis to estimate the
`
`relative values of patented versus non-patented features. Chrimar, 2018 WL 2120618, at *9.
`
`
`
`Mr. Ratliff’s 40% apportionment to the patented features - based on Mr. McAlexander’s
`
`conclusion that the patented features are almost if not as important as the non-patented features -
`
`is not, as Apple contends, a “black box.” Dkt. 268 at 2. Apple’s own damages expert, Paul
`
`Meyer, apportioned the value of the price paid by Apple for a patent portfolio for what he deems
`
`a comparable license by quantifying similar language.
`
`.
`
` AGIS should not be held to a higher standard of precision than
`
`Apple’s own expert.
`
`
`
`Apple also reargues that “AGIS . . . failed to account for several critical technologies in
`
`the Accused Apps, including battery life-saving features, the apps’ ‘look-and-feel,’ and
`
`technology covered by Apple’s own patents.” Dkt. 268 at 3. Apple again misses the point.
`
`Apple does not dispute that fee-based device and friend-finding apps offered by the wireless
`
`carriers, xFi and Family Tracker, which have tens-of-millions of downloads combined, offer the
`
`same core functions and features as Apple’s Find My iPhone and Find My Friends apps. It is
`
`these core functions and features that are accused by AGIS of infringing, not the other features
`
`and functions of its devices that are the baseline technology which all of the accused and
`
`comparable third-party apps are built upon, and therefore need not be apportioned out since the
`
`upfront fees are paid for the apps, not their common, shared device platforms.
`
`2
`
`

`

`Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 5 of 11 PageID #: 19333
`
`B.
`
`The Market Price of the Family Tracker App Was a Reliable
`Starting Point for the Hypothetical Negotiation
`
`
`
`Attacking Mr. Ratliff’s choice of the Family Tracker app as a starting point for his
`
`analysis, Apple argues that “AGIS does not identify any evidence showing that Apple made a
`
`single additional sale, received a single additional dollar in ‘advertising’ revenue, or received a
`
`single additional dollar in any ‘other way’ that is attributable to the Accused Apps.” Dkt. 268 at
`
`1. Apple then claims that “AGIS provides no objective evidence correlating the price of the
`
`third-party Family Tracker app to the alleged ‘ecosystem’ value of the Accused Apps.” Dkt. 268
`
`at 4. But Apple does not dispute that it did not produce any data or metrics reflecting, under its
`
`ecosystem monetization model, claiming that it “does not track financial information for apps
`
`that it distributes for free.” Despite Apple’s internal decision to not track this data, Apple does
`
`not and cannot deny that popular, highly-used apps, such as these, do have value and that this
`
`value can be estimated based on market information relating to comparable apps that use a
`
`different monetization model. For Apple to claim otherwise would mean that Apple includes
`
`such apps in every single one of the millions of accused iPhones, iPads, iPods and Apple watches
`
`it sells out of sheer benevolence. Such a claim is simply not credible.1
`
`
`
`Apple also injects a new “Economics 101” argument into this issue, arguing without
`
`citing to any authority that no consumer would pay for an app if a similar app is given away free.
`
`Apple then declares the only possible explanation is that those who purchased the fee-based
`
`third-party apps must have been paying for some feature the third-party apps have that the
`
`
`1
`
`
`
`
`
`
`
`3
`
`
`
`
`
`-
`
`

`

`Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 6 of 11 PageID #: 19334
`
`accused apps do not. Dkt. 268 at 5. Apple’s argument is flawed in several ways. Notably,
`
`Apple does not list, much less prove, that there are additional valuable features of the third-party
`
`apps that would merit the fees. Further, Mr. Ratliff demonstrated in his report and workpapers,
`
`and explained in his deposition, that there are no significant differences, just different providers
`
`in different businesses with different monetization models. See Dkt. 250 at 9. Ultimately, Apple
`
`focuses on the wrong question. The relevant inquiry is not why a significant number of users
`
`might choose the comparable third-party apps over the accused apps but, rather, what is the
`
`market value of the accused core features and functions of the accused apps? Mr. Ratliff
`
`answers this using pricing for comparable third-party apps that may be downloaded for a fee as a
`
`proxy for Apple’s different monetization model.2
`
`
`
`While not denying the usage statistics AGIS relies on for its estimate downloads of the
`
`Family Tracker app, Apple suggests that it did not produce app metrics for Family Tracker or
`
`other similar apps because it did not know that information might be relevant until it saw
`
`Mr. Ratliff’s report. Now months later, Apple finally does so, but only for the latest version and
`
`only covering a partial year period in 2018. During that period, “the data shows that Family
`
`Tracker was downloaded only 424 times for iPhone and only 19 times for iPad.” Dkt. 268 at 5;
`
`Dkt. 268-2. As with its prior citation to statistics regarding Family Tracker user reviews, Apple
`
`again misleads. See Dkt. 250 at 10, fn. 4. The data cited in Apple’s Reply is limited to its
`
`production of new subscriptions to a single upgrade version of Family Tracker released in early
`
`2018, ignoring subscriptions to at least 23 prior versions dating back to 2010. This does
`
`nothing to rebut, and in fact corroborates, Mr. Ratliff’s estimates based on market information
`
`that combined Apple and Android distribution of Family Tracker is in the 20,000 to 100,000
`
`
`2 Apple attempts to frame Mr. Ratliff’s market price starting as one exclusively based on Family Tracker, but his
`report makes it clear that he considers multiple third-party apps with a range of fees and simply used the app at
`lowest end of the range which was Family Tracker.
`
`4
`
`

`

`Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 7 of 11 PageID #: 19335
`
`range,3 and fails to address the cumulative wireless carrier and xFi app distributions in the tens-
`
`of-millions on Google Play alone. Dkt. 250-4 at ¶¶8, 9.
`
`C.
`
`The Insurance Adjustment is Not Arbitrary and is Supported
`
`
`
`Apple does not dispute that the accused devices are pre-configured to and capable of
`
`being used to find a lost device.
`
`-
`
`
`
`.
`
`
`
`
`
`
`
`
`
`
`
`For shock value, Apple mischaracterizes AGIS’s argument concerning the insurance
`
`benefit, citing a “$200 insurance benefit” (Dkt. 268, at 5) as if it was a royalty base or price, as
`
`opposed to focusing on the actual impact on the royalty amount. The insurance amount estimate
`
`was chosen at the low end price and deductible for device loss insurance reflecting a benefit (or
`
`avoided cost) of having the ability to locate a lost device, but was only used to compare the
`
`relative cost of the insurance to device replacement cost. Dkt. 250-2, at ¶94.
`
`
`3 Half that distribution is reflected on GooglePlay, and the Apple distribution was estimated to be similar. Dkt. 250-
`4 [Ratliff Declaration], at ¶8.
`
`). Id.
`
`-
`
`5
`
`

`

`Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 8 of 11 PageID #: 19336
`
`
`
`
`
`
`
`
`
`D.
`
`Apple Mischaracterizes the Reference to Apple’s Profits
`
`
`
`Finally, Apple does not dispute that Georgia-Pacific factor 15 expressly contemplates a
`
`comparison of the reasonable royalty to the accused product’s profitability. Apple again
`
`misstates what Mr. Ratliff does in connection with this factor. To be clear, AGIS will not
`
`present, and Mr. Ratliff will not opine, as to “evidence suggesting a royalty rate as a percentage
`
`of Apple’s overall revenues or profits,” as argued by Apple. Dkt. 268 at 6. Any references to
`
`Apple’s revenues or profits in Mr. Ratliff’s expert report were limited to the context of Georgia-
`
`Pacific Factor 15 and focus solely on the profits of the SSPPU, and then only after further usage
`
`apportionment and technical apportionment. Apple conflates “profits” (a term used to represent
`
`a dollar amount) with “profit margin” (a percentage of relevant sales price) in trying to confuse
`
`the issue. Mr. Ratliff’s focus is on the estimated profit margin relevant to the ecosystem value of
`
`the accused apps (the SSPPU), and his opinion on this point is limited to amount of the
`
`reasonable royalty compared to that profit margin.
`
`For all of the foregoing reasons, Apple’s motion to exclude certain damages opinions of
`
`Alan Ratliff should be denied in its entirety.
`
`Dated: January 14, 2018
`
`
`
`
`
`
`
`BROWN RUDNICK LLP
`
`
`
`
`
` /s/ Alfred R. Fabricant
`Alfred R. Fabricant
`NY Bar No. 2219392
`Email: afabricant@brownrudnick.com
`Lawrence C. Drucker
`NY Bar No. 2303089
`
`
`4
`
`
`
`
`
`
`
`6
`
`

`

`Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 9 of 11 PageID #: 19337
`
`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
`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 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
`Marshall, Texas 75670
`Telephone: 903-923-9000
`Facsimile: 903-923-9099
`
`ATTORNEYS FOR PLAINTIFF, AGIS
`SOFTWARE DEVELOPMENT LLC
`
`
`7
`
`

`

`Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 10 of 11 PageID #: 19338
`Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 10 of 11 PageID #: 19338
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`8
`
`

`

`Case 2:17-cv-00513-JRG Document 302 Filed 01/16/19 Page 11 of 11 PageID #: 19339
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that, on January 14, 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