throbber
Case 6:17-cv-01217-EFM Document 270 Filed 10/17/22 Page 1 of 8
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE DISTRICT OF KANSAS
`
`
`
`
`
`
`Case No. 6:17-cv-01217
`
`
`
`
`
`
`
`
`LOGANTREE LP,
`
` Plaintiff,
`vs.
`
`GARMIN INTERNATIONAL, INC.,
`
`
`
`
`
`
`Defendant.
`
`GARMIN’S TRIAL BRIEF
`
`Pursuant to this Court’s Trial Scheduling Order (ECF No. 229), Garmin submits its Trial
`
`Brief in support of the case it will present at trial, and to aid the Court with the relevant history of
`
`the case and to make it aware of serious concerns Garmin has that LoganTree will introduce new
`
`theories and evidence, which includes theories already stricken by this Court.
`
`I.
`
`LOGANTREE’S STRICKEN INFRINGEMENT THEORIES AND EVIDENCE
`AND SUBSEQUENT ATTEMPTS TO REINTRODUCE THEM
`
`This Court already concluded that LoganTree repeatedly attempted to skirt this Court’s
`
`rules and orders. Specifically, the Court’s order provided a comprehensive history of LoganTree’s
`
`antics and the resulting harm it caused to Garmin and this case. See generally ECF Nos. 138; 186.
`
`Below, Garmin highlights the relevant aspects of that history here.
`
`As the Court knows, the local rules require a plaintiff to disclose their infringement theory
`
`early in the case and, in this case, provided for “final” infringement contentions. L.P.R. 3-1. The
`
`purpose of these requirements is to force the plaintiff to explain their infringement theory, so the
`
`parties can focus discovery and expert reports on the correct theory of infringement. Significantly,
`
`this means the parties do not play hide the ball regarding the infringement theory. Unfortunately,
`
`
`
`1
`
`

`

`Case 6:17-cv-01217-EFM Document 270 Filed 10/17/22 Page 2 of 8
`
`LoganTree ignored these requirements and is now attempting to change its position after 5 years
`
`of litigation.
`
`LoganTree’s infringement theory in this case had always been the same, at least until it
`
`served LoganTree’s expert report of Mr. Monty Myers. Prior to Myers’ report, LoganTree’s
`
`infringement theory was solely based on when users set a manual step goal. Myers’ report
`
`attempted to inject new theories centered around Garmin’s goal streak feature (how many days in
`
`a row the user meets their step goal) and the related step goal multiples (when a user meets their
`
`step goal multiple times in a single day). Myers also attempted to interject new theories of
`
`infringement based on functions performed by a separate software, the Garmin Connect app. ECF
`
`No. 186, at 12.
`
`The reasons LoganTree made these last-minute changes are clear. First, LoganTree
`
`repeatedly characterized the scope of the invention in a narrow manner in order to survive
`
`challenges to the ’576 Patent’s validity by Garmin at the PTAB, and in the District of Delaware.
`
`Specifically, LoganTree argued the claims required a single microprocessor that performed all the
`
`relevant claim limitations. Second, rather than conducting discovery to support its infringement
`
`theory, LoganTree sat on its hands. LoganTree did not even attempt to review Garmin’s source
`
`code or talk to Garmin’s engineers about the microprocessor(s) in Garmin’s products. Notably, the
`
`source code (i.e., the “instructions” explain how the Accused Products are programmed) is
`
`required to prove the microprocessor limitation. Those failures are especially critical here. The
`
`asserted claims set forth specific requirements as to what the Accused Products’ microprocessors
`
`must perform. But what functions those microprocessors perform and how they perform those
`
`functions are dictated by the source code. Here, the Accused Products’ source code completely
`
`
`
`2
`
`

`

`Case 6:17-cv-01217-EFM Document 270 Filed 10/17/22 Page 3 of 8
`
`failed to evidence LoganTree’s infringement theory. Thus, LoganTree had no choice but to try to
`
`change its infringement theory at the 11th hour.
`
`And the Court agreed that LoganTree wrongly attempted to change its theories and it was
`
`unfair to Garmin. For example, Garmin asked the Court to strike LoganTree’s new mapping of the
`
`Goal Streak and Multiple Daily Step Goals:
`
`First, to the extent LoganTree is arguing Goal Streak merely “demonstrates” the
`operation of Step Goal, this is false. Goal Streak, unlike Daily Step Goals, is not a
`“user-defined” event based on “user-defined parameters” as the claim requires. It
`is simply a “counter” that a user can never adjust or set. A non-user defined
`functionality cannot be “demonstrative” of a user-defined functionality. And, Mr.
`Myers does far more than use Goal Streak as an example of Step Goal. Instead, he
`includes an extensive discussion of the Goal Streak source code and its (alleged)
`timestamps and maps Goal Streak to the claims. Mr. Myers relies on Goal Streak
`to meet the limitations of the claims, not merely as an example of Step Goal.
`
`ECF No. 169, at 1–2 (bold italics added); see also ECF No. 158, at 3–6.
`
`Agreeing with Garmin, the Court went even further, concluding “there is no explanation for
`
`LoganTree’s new infringement theories other than that they appear to have been motivated by
`
`gamesmanship.” ECF No. 186, at 29. And the Court’s resulting order on what it was striking was
`
`unambiguous:
`
`LoganTree’s infringement contentions did not provide Garmin with reasonable
`notice that LoganTree was relying on any user-defined functionality other than the
`user’s daily step-count goal. Those contentions identified the user’s daily step-
`count goal set via the user’s Garmin Connect account—and only this daily step-
`count goal—as the ‘first user-defined event.’ If LoganTree was going to rely on
`any other user-defined functionality, LoganTree was required to identify all
`Accused Instrumentalities (e.g., Garmin Connect) with specificity . . . LoganTree’s
`contentions did not identify the number of consecutive days a user meets their
`daily step-count goal (Goal Streak) or the number of times the user meets the
`daily step count goal in a given day as ‘user-defined events.’ These features are
`not even user defined. They are built-in automatic counting features. . . . These
`features are therefore not ‘demonstrative’ of the user meeting the daily step-count
`goal, nor are they user-defined functionality[.]
`
` .
`
`
`
` . .
`
`
`
`3
`
`

`

`Case 6:17-cv-01217-EFM Document 270 Filed 10/17/22 Page 4 of 8
`
`The court strikes all theories relying on Goal Streak and all theories relying on
`Garmin Connect as they relate to the “detecting” and “storing” limitations.
`
`
` ECF No. 186, at 17–18, 35 (emphasis added).
`
`Garmin also informed LoganTree’s new counsel about these issues. In fact, Garmin
`
`explained the proceedings in the case, how LoganTree continually stalled, delayed, blew through
`
`deadlines, and ignored the Court’s rules and order. LoganTree ignored this and the gamesmanship
`
`continued. At the summary judgment hearing, LoganTree presented stricken source code to the
`
`Court as alleged evidence in support of its infringement theory. 09/01/2022 MSJ Hr’g Trans, at
`
`57:13–58:8, 76:25–77:11. And in preparation for trial, LoganTree filed its exhibit list and doubled-
`
`down on its intent to ignore the Court’s order striking its improper infringement theories by
`
`including on its trial exhibit list dozens of exhibits that were the exact evidence this Court had
`
`already stricken from Myers’ report. ECF Nos. 253-3, 253-4.
`
`Finally, with just 11 days until trial, LoganTree continues to press forward with its stricken
`
`theories. LoganTree ignores the Court’s prior order and contends it did not apply to ANY
`
`functionality on the device. This is false. The Court’s own language makes it abundantly clear; the
`
`Court struck all Goal Streak and Garmin Connect theories outright. Hard stop! As the Court
`
`observed, LoganTree never disclosed Goal Streak or Garmin Connect as part of its infringement
`
`theory and was barred from raising these theories.
`
`The introduction of these new theories and evidence at trial violates this Court’s local rules,
`
`this Court’s prior order, and is enormously prejudicial to Garmin. The introduction of this evidence
`
`will warrant setting aside the jury verdict, a new trial, or reversal at the Federal Circuit. LoganTree
`
`should be ordered to do what it should have done of its own accord already—abide by the Court’s
`
`prior rulings.
`
`
`
`4
`
`

`

`Case 6:17-cv-01217-EFM Document 270 Filed 10/17/22 Page 5 of 8
`
`II.
`
`LOGANTREE WILL NOT BE ABLE TO MEET ITS BURDEN OF PROVING
`DAMAGES
`
` “The burden of proving damages falls on the patentee.” Lucent Techs., Inc. v. Gateway,
`
`Inc., 580 F.3d 1301, 1324 (Fed. Cir. 2009). LoganTree contends it is “entitled to an award of
`
`damages in the amount of not less than a reasonable royalty.” ECF No. 187, at 34. In such cases,
`
`the Federal Circuit’s “law recognizes that a reasonable royalty award ‘must be based on the
`
`incremental value of that the invention adds to the end product.’” Exmark Mfg. Co. Inc. v. Briggs
`
`& Stratton Power Prods. Grp., LLC, 879 F.3d 1332, 1348 (Fed. Cir. 2018) (quoting Ericsson, Inc.
`
`v. D-Link Sys., Inc., 773 F.3d 1201, 1226 (Fed. Cir. 2014)). Garmin will establish at trial that, as
`
`a matter of fact and law, LoganTree wholly failed all the basic LEGAL requirements of patent
`
`damages:
`
`• Apportionment – Required as a matter of law.
`
`• Technical and economic comparability – Required as a matter of law.
`
`• Royalty is to the incremental value of the manual step goal functionality – Required
`
`as a matter of law.
`
`• Plucking royalty rates out of thin air – Barred as a matter of law.
`
`• Showing entire revenue amounts – Barred as a matter of law.
`
`First, Volkov admits he did not apportion. This means his opinions are clear error and
`
`contrary to the Federal Circuit authority. This is one of the most frequent reasons the Federal
`
`Circuit reverses jury verdicts. Despite this, Volkov refused to perform this basic requirement. As
`
`background, “apportionment” refers to the Supreme Court’s mandate that the patentee must, in
`
`every case, “separate” out its damages from the value of all the unpatented components and
`
`features of the Accused Products to ensure the patentee is only compensated for the value of the
`
`claimed invention, and nothing more. Power Integrations, Inc. v. Fairchild Semiconductor Int’l,
`
`
`
`5
`
`

`

`Case 6:17-cv-01217-EFM Document 270 Filed 10/17/22 Page 6 of 8
`
`Inc., 904 F.3d 965, 977 (Fed. Cir. 2018). Here, Volkov admits “I did not apportion,” which means
`
`there is no evidence of damages. Finjan, 879 F.3d at 1309.
`
`Second, Volkov admits he did not perform any technical comparability analysis because
`
`he is not an engineer. And Volkov also failed to do any economic comparability analysis. These
`
`are both required by the Federal Circuit as a matter of law. VirnetX, Inc. v. Cisco Sys., Inc., 767
`
`F.3d 1308, 1330 (Fed. Cir. 2014); Apple Inc. v. Wi-Lan Inc., 25 F.4th 960, 972 n.5 (Fed. Cir. 2022)
`
`(citing Elbit Sys. Land & C4I Ltd. v. Hughes Network Sys., LLC, 927 F.3d 1292, 1299 (Fed. Cir.
`
`2019)). Instead of following the law, Volkov just wholesale used certain other Garmin’s licenses
`
`without any comparability analysis. As background, to use any prior license, it must sufficiently
`
`similar both in the technology and/or patents it covers, and in terms of economics (e.g., the
`
`respective size of the licensee and licensor; the scope and duration of the license, the number of
`
`patents being licensed, the licensing policies of the parties, etc.). It is LoganTree’s burden to prove
`
`that an existing license satisfies the threshold level of comparability to be admissible. If it does not
`
`make that showing, which LoganTree did not here, the prior existing licenses must be excluded.
`
`See id.
`
`Third, the manual step feature is all that is accused, but very few Garmin users use this
`
`feature. Therefore, Volkov’s damages were not limited to the claimed invention, which too violates
`
`the law. Even more, Garmin will show that the value Garmin receives from the Accused Products
`
`is derived, primarily, from features that have not been accused of infringement. For example, the
`
`Quatix model watches, are designed specifically for sailors and marine enthusiasts. Among its
`
`sailing and marine specific features are (1) sailing assistance; (2) anchor assist; (3) tide data; and
`
`(4) fishing. Garmin will also highlight the D2 Charlie model watch, specifically designed for pilots.
`
`Among its flying specific features are (1) altitude alerts; (2) barometric pressure; (3) flight
`
`
`
`6
`
`

`

`Case 6:17-cv-01217-EFM Document 270 Filed 10/17/22 Page 7 of 8
`
`navigation; and (4) flight plan creation and management. As Volkov admits, the value of Garmin’s
`
`watches is driven primarily by these other features.
`
`Fourth, Volkov proffered “illustrative” 1%, 2%, and 3% royalty rates. Plucking these
`
`illustrative rates out of thin air is not permissible under Federal Circuit law and is reversible error
`
`as LoganTree well knows. Exmark, 879 F.3d at 1351; Uniloc USA, Inc. v. Microsoft Corp., 632
`
`F.3d 1292, 1315 (Fed. Cir. 2011).
`
`Fifth, Volkov reliance on the total revenues Garmin received from the Accused Products
`
`as his royalty base is a clear violation of established Federal Circuit law. A patentee cannot rely
`
`on the total revenues of a multi-component product, which the Accused Products indisputably are,
`
`that has non-infringing components and features, which the Accused Products indisputably do.
`
`LaserDynamics, Inc. v. Quanta Computer, Inc., 694 F.3d 51, 67 (Fed. Cir. 2012). Volkvo ignores
`
`this well-established law, which dictates that the harm to Garmin is irreparable because any royalty
`
`will seem small as compared to the revenue number. Id.
`
`This case is unique in that LoganTree has not presented a single viable damages theory that
`
`has ever been accepted by the Federal Circuit. Not a single one. Instead, every analysis performed
`
`by Dr. Volkov has been soundly rejected by the Federal Circuit. LoganTree’s only response is
`
`diversion—to suggest that Garmin has somehow “waived” this issue by not raising it at Daubert.
`
`But under existing 10th Circuit precedent the Court must perform its gatekeeping role at some
`
`point, whether that is before trial, during a voir dire before Dr. Volkov testifies, or after the
`
`conclusion of the case in the context of a motion for remittitur. Garmin strongly believes that the
`
`presentation of such evidence would be prejudicial to Garmin and would taint the jury and,
`
`therefore, it should be addressed before Dr. Volkov testifies. Nonetheless, if the Court does not
`
`address LoganTree’s legally flawed damages theory prior to Dr. Volkov’s testimony, and if
`
`
`
`7
`
`

`

`Case 6:17-cv-01217-EFM Document 270 Filed 10/17/22 Page 8 of 8
`
`LoganTree is successful at trial, then Garmin will present these same issues to the Court to address
`
`in a motion for remittitur.
`
`Dated: October 17, 2022
`
`
`
`
`
`
`
`Respectfully submitted,
`
`ERISE IP, P.A.
`
`/s/ Adam P. Seitz
`
`Adam P. Seitz, KS Bar #21059
`Megan J. Redmond, KS Bar #21999
`Carrie A. Bader, KS Bar #24436
`Clifford T. Brazen, KS Bar #27408
`ERISE IP, P.A.
`7015 College Blvd., Suite 700
`Overland Park, Kansas 66211
`Telephone: (913) 777-5600
`Facsimile: (913) 777-5601
`adam.seitz@eriseip.com
`megan.redmond@eriseip.com
`carrie.bader@eriseip.com
`cliff.brazen@eriseip.com
`
`Attorneys for Defendant Garmin
`International, Inc.
`
`
`
`
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that, on October 17, 2022, the foregoing document filed with the Clerk of
`
`the Court using CM/ECF and that 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
`
`accordingly.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`8
`
`

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