throbber
Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 1 of 26
`
`UNITED STATES DISTRICT COURT
`FOR THE DISTRICT OF MASSACHUSETTS
`
`PHILIPS NORTH AMERICA LLC,
`
`v.
`
`FITBIT, INC.,
`
`Plaintiff,
`
`Defendant.
`
`Civil Action No. 1:19-cv-11586-IT
`
`FITBIT’S RESPONSIVE CLAIM CONSTRUCTION BRIEF
`
`
`
`

`

`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 2 of 26
`
`TABLE OF CONTENTS
`
`
`Page
`
`3.
`4.
`
`U.S. PATENT NO. 6,013,007.........................................................................................1
`A.
`“means for computing athletic performance feedback data from the series
`of time-stamped waypoints obtained by said GPS receiver” (Claims 1, 21) .........1
`1.
`Philips’ admissions compel a finding of indefiniteness ............................1
`2.
`Philips’ case law citations actually support a finding of
`indefiniteness ..........................................................................................5
` Philips’ other arguments against indefiniteness fail .................................7
`Philips misrepresents Fitbit’s proposed construction and the
`parties’ disputes .......................................................................................8
`Construction of “athletic performance feedback data”..............................9
`5.
`“means for suspending and resuming operation of said means for
`computing when a speed of the athlete falls below a predetermined
`threshold” (Claim 7).......................................................................................... 11
`U.S. PATENT NO. 6,976,958....................................................................................... 13
`A.
`“in the event of an interruption of the wireless connection . . . configured
`to store the health parameter or visual data in a memory or on the
`removable memory device” (Claims 15, 16) ...................................................... 13
` “memory” (Claims 15, 16) ............................................................................... 14
`“internet-enabled wireless web device” (Claims 15, 16) .................................... 15
`“health parameter indicative of a disease state or condition of a patient”
`(Claim 15) and “health parameter or visual data corresponding to a
`patient’s disease state or condition” (Claim 16) ................................................. 16
`U.S. PATENT NO. 7,088,233....................................................................................... 16
`A.
`“governing information transmitted between the first personal device and
`the second device” (Claim 1)............................................................................. 16
` “first personal device” (Claim 1) ...................................................................... 18
`B.
`“wireless communication” (Claim 1) ................................................................. 19
`C.
`U.S. PATENT NO. 8,277,377....................................................................................... 20
`A.
`“indicating a physiologic status of a subject” (Claim 1) ..................................... 20
`
`B.
`
`B.
`C.
`D.
`
`
`I.
`
`II.
`
`III.
`
`IV.
`
`
`
`-i-
`
`

`

`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 3 of 26
`
`TABLE OF AUTHORITIES
`
`
`Page(s)
`
`
`Cases
`
`Abbott Labs. v. Sandoz, Inc.,
`566 F.3d 1282 (Fed. Cir. 2009) ............................................................................................ 15
`
`Alfred E. Mann Found. for Sci. Research v. Cochlear Corp.
`841 F.3d 1334 (Fed. Cir. 2016) .......................................................................................... 6, 7
`
`Aristocrat Techs. Australia Pty. Ltd. v. Int’l Game Tech.,
`521 F.3d 1328 (Fed. Cir. 2008) .......................................................................................... 1, 8
`
`Augme Techs., Inc. v. Yahoo! Inc.,
`755 F. 3d 1326 (Fed. Cir. 2014) ............................................................................................. 8
`
`B. Braun Med., Inc. v. Abbott Labs.,
`124 F.3d 1419 (Fed. Cir. 1997) ........................................................................................ 4, 12
`
`Biomedino, LLC v. Waters Techs. Corp.,
`490 F.3d 946 (Fed. Cir. 2007)............................................................................................ 5, 6
`
`BlackBoard, Inc. v. Desire2Learn, Inc.,
`574 F.3d 1371 (Fed. Cir. 2009) .............................................................................................. 3
`
`Default Proof Credit Card System, Inc. v. Home Depot USA, Inc.,
`412 F.3d 1291 (Fed. Cir. 2005) .............................................................................................. 3
`
`EON Corp. IP Holdings LLC v. AT&T Mobility LLC,
`785 F.3d 616 (Fed. Cir. 2015)...................................................................................... 3, 4, 12
`
`Finisar Corp. v. DirecTV Grp., Inc.,
`523 F.3d 1323 (Fed. Cir. 2008) .......................................................................................... 5, 6
`
`Function Media, LLC v. Google, Inc.,
`708 F.3d 1310 (Fed. Cir. 2013) .......................................................................................... 3, 8
`
`GPNE Corp. v. Apple, Inc.,
`830 F.3d 1365 (Fed. Cir. 2016) ...................................................................................... 14, 19
`
`Harris Corp. v. Ericsson Inc.,
`417 F.3d 1241 (Fed. Cir. 2005) .............................................................................................. 2
`
`Merck & Co. v. Teva Pharms. USA, Inc.,
`395 F.3d 1364 ..................................................................................................................... 13
`
`Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co.,
`
`-ii-
`
`

`

`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 4 of 26
`
`TABLE OF AUTHORITIES
`(continued)
`
`Page(s)
`
`
`
`868 F.3d 1013 (Fed. Cir. 2017) ............................................................................................ 13
`
`Oatey Co. v. IPS Corp.,
`514 F.3d 1271 (Fed. Cir. 2008) ................................................................................ 16, 18, 20
`
`Phillips v. AWH Corp.,
`415 F.3d 1303 (Fed. Cir. 2005) ...................................................................................... 18, 20
`
`S3 Inc. v. NVIDIA Corp.,
`259 F.3d 1364 (Fed. Cir. 2001) .............................................................................................. 5
`
`SkinMedica, Inc. v. Histogen Inc.,
`727 F.3d 1187 (Fed. Cir. 2013) ............................................................................................ 16
`
`Ventana Med. Sys. v. BioGenex Labs., Inc.,
`473 F.3d 1173 (Fed. Cir. 2006) ............................................................................................ 15
`
`Williamson v. Citrix Online, LLC,
`792 F.3d 1339 (Fed. Cir. 2015) ................................................................................ 1, 2, 9, 12
`
`WMS Gaming, Inc. v. Int’l Game Tech.,
`184 F.3d 1339 (Fed. Cir. 1999) .......................................................................................... 7, 8
`
`Statutes
`
`35 U.S.C. § 112 ........................................................................................................................... 7
`
`-iii-
`
`

`

`
`
`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 5 of 26
`
`Fitbit’s claim constructions are supported by Federal Circuit law and intrinsic record.
`
`Philips’ constructions rely on expert testimony to rewrite claim language, skirt statutory
`
`disclosure requirements, and contradict file history admissions. The case law is decidedly on
`
`Fitbit’s side; even Philips’ legal authorities support Fitbit’s positions.
`
`I.
`
`U.S. PATENT NO. 6,013,007
`
`A.
`
`“means for computing athletic performance feedback data from the series of
`time-stamped waypoints obtained by said GPS receiver” (Claims 1, 21)
`
`1.
`
`Philips’ admissions compel a finding of indefiniteness
`
`The law of indefiniteness pertaining to a computer-implemented function of a means-
`
`plus-function (“MPF”) is straightforward. Such claim terms are indefinite if the patent
`
`specification fails to disclose a linked algorithm, as is the case here. See Williamson v. Citrix
`
`Online, LLC, 792 F.3d 1339, 1351-52 (Fed. Cir. 2015); D.I. 72 at 2-5; D.I. 44 at 9-15.1 As
`
`detailed in subsection I.A.2 below, Philips’ opening brief grossly misstates the relevant law.
`
`Indeed, the cases Philips relies on recognize the MPF disclosure requirements and support
`
`indefiniteness here.2
`
`In an attempt to supply the missing algorithm, Philips supplements the ’007 patent
`
`disclosure with testimony from its expert, Dr. Martin. This strategy is inappropriate because the
`
`content of the specification controls. See Harris Corp. v. Ericsson Inc., 417 F.3d 1241, 1253
`
`1 The ’007 patent’s failure to disclose the necessary algorithm is not surprising given that it was
`filed in 1998 and issued in 2000. It was not until years later that the Federal Circuit provided
`guidance that “t]he corresponding structure for a § 112, ¶ 6 claim for a computer-implemented
`function is the algorithm disclosed in the specification.” Aristocrat Techs. Australia Pty. Ltd. v.
`Int’l Game Tech., 521 F.3d 1328, 1333 (Fed. Cir. 2008).
`2 Philips argued in the parties’ joint status report that indefiniteness should be addressed during
`claim construction (D.I. 60 at 2-3, 7-9). Now Philips takes the inconsistent position that the
`Court should delay addressing indefiniteness until after claim construction (D.I. 73 at 8).
`Indefiniteness for failure to disclose an algorithm is commonly determined in the context of
`claim construction. E.g., Williamson v. Citrix Online LLC, 792 F.3d 1339, 1345-46, 1351-55 (en
`banc) (affirming finding of indefiniteness in claim construction order).
`
`
`- 1 -
`
`

`

`
`
`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 6 of 26
`
`(Fed. Cir. 2005) (“A computer-implemented means-plus-function term is limited to the
`
`corresponding structure disclosed in the specification . . .”) (emphasis added). And “[t]he
`
`testimony of one of ordinary skill in the art cannot supplant the total absence of structure from
`
`the specification.” Williamson, 792 F.3d at 1354. Moreover, Dr. Martin confirmed that there was
`
`no algorithm for performing the claimed function in the specification – only that a skilled artisan
`
`would know what to do because the algorithms were so simple and obvious. Dr. Martin’s
`
`declaration offers pages of formulas and assumptions for computing athletic performance
`
`feedback data. (D.I. 73-5 at ¶¶ 18-26). However, none of these formulas or any other formula for
`
`computing athletic performance feedback data are disclosed in the ’007 patent specification or
`
`included in Philips’ proposed construction. 3 See Martin Tr. 41:9-45:23 4 (no disclosure of
`
`algorithm
`
`for calculating distance), 45:25-46:21
`
`(no disclosure of algorithm
`
`for
`
`calculating/finding average or current speed), 69:14-72:25 (no disclosure of algorithm for
`
`claimed “computing athletic performance feedback data . . .”), 75:3-76:11 (no “smart algorithm”
`
`disclosed and “implementation details are not provided”).
`
`In fact, Dr. Martin admitted during deposition that he “wasn’t trying to show that there
`
`was an algorithm” in the specification for the claimed “computing athletic performance feedback
`
`data . . .” Id., 41:14-17. Rather, the opinions in his declaration were meant to show that the
`
`claimed algorithm would have been “relatively simple and would have been obvious to
`
`somebody who was skilled in the art” or would have been known to a POSITA. Id., 40:16-43:8.
`
`Even if the simplicity and obviousness of the algorithm were true, it is irrelevant under
`
`
`3 The ‘007 patent criticizes the prior art because “[t]hey do not include real-time athletic
`performance algorithms…” ’007 patent, 1:47-48. Yet Philips and Dr. Martin admit the
`specification of the ‘007 patent also does not include such algorithms, and that a person of skill
`in the art would need to look outside the specification for the algorithms.
`4 The Martin Depo excerpts are attached to the Peterman Declaration as Ex. A
`
`- 2 -
`
`

`

`
`
`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 7 of 26
`
`MPF law as even simple algorithms for performing a claimed function must be expressly
`
`disclosed in the specification. EON Corp. IP Holdings LLC v. AT&T Mobility LLC, 785 F.3d
`
`616, 623-624 (Fed. Cir. 2015) (“[w]here the specification discloses no algorithm, the skilled
`
`artisan’s knowledge is irrelevant”). Importantly, “[a] patentee cannot avoid providing specificity
`
`as to structure simply because someone of ordinary skill in the art would be able to devise a
`
`means to perform the claimed function.” BlackBoard, Inc. v. Desire2Learn, Inc., 574 F.3d 1371,
`
`1385 (Fed. Cir. 2009); see also Function Media, LLC v. Google, Inc., 708 F.3d 1310, 1319 (Fed.
`
`Cir. 2013) (“proving that a person of ordinary skill could devise some method to perform the
`
`function is not the proper inquiry as to definiteness”). Dr. Martin’s admissions regarding the
`
`specification’s lack of algorithms and decision to not find algorithms because they were obvious
`
`shows that “means for computing . . .” is indefinite. See EON, 785 F.3d at 623-624.
`
`Moreover, Dr. Martin’s endeavors to boil the omitted algorithms down to known
`
`arithmetic (D.I. 73-5 at ¶¶ 18-26) conflict with the ’007 specification, which explains that the
`
`invention requires a “smart algorithm” for computing athletic performance feedback to correct
`
`for errors in GPS waypoints. ’007 patent, 7:52-56 (“smart algorithm can be used to filter out the
`
`erroneous position points”). Dr. Martin admitted the problems associated with inaccurate GPS
`
`waypoints at the time of invention. Martin Tr. 73:1-7 (“Q. Back in the 1998 time frame, did GPS
`
`waypoints possibly contain errors? A. Yeah. Selective availability was still being used in the
`
`‘90s”); see also id., 75:22-79:14. He also admitted that errors in GPS waypoints would lead to
`
`errors in the claimed “computing performance feedback data . . .” based on these waypoints,
`
`however the “smart algorithm” required to correct these errors is an “implementation detail” not
`
`supplied by the specification. Id., 73:17-76:11. Default Proof Credit Card System, Inc. v. Home
`
`Depot USA, Inc., 412 F.3d 1291, 1302 (Fed. Cir. 2005) (“the testimony of one of ordinary skill in
`
`- 3 -
`
`

`

`
`
`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 8 of 26
`
`the art cannot supplant the total absence of structure from the specification”). Again, Dr.
`
`Martin’s testimony demonstrates that the disclosure of the ’007 patent is insufficient under law.
`
`Dr. Martin’s testimony also confirmed that the Katz exception does not apply 5. Dr.
`
`Martin admitted that a generic processor would have needed to be specially programmed in order
`
`to perform the claimed “computing athletic performance feedback data . . .” Martin Tr. 48:6-
`
`50:20. Thus, the Katz exception would not apply regardless of whether the algorithms are
`
`“relatively simple to implement.” EON Corp., 785 F.3d at 621-22, D.I. 72 at 5.
`
`Finally, Philips’ arguments are inconsistent with its own proposed construction. Philips
`
`and Dr. Martin contend a skilled artisan would have understood the multiple algorithms required
`
`to program a processor to compute athletic performance feedback data from a series of time-
`
`stamped waypoints simply by reading the ’007 claims and specification (D.I. 73 at 8-10; D.I. 73-
`
`5 at ¶¶ 18-26), yet Philips failed to include these algorithms in its proposed construction. Philips
`
`argues that the POSITA’s knowledge would render these missing algorithms and programming
`
`“obvious,” yet Philips does not want to limit its claims to these algorithms and instead identifies
`
`only a processor as the “means for computing . . .” structure.6 This is an obvious attempt to avoid
`
`its duty to link the claimed function with any specific algorithm, which is the required quid pro
`
`quo for using functional claiming. B. Braun Med., Inc. v. Abbott Labs., 124 F.3d 1419, 1424
`
`(Fed. Cir. 1997). Philips cannot have it both ways: if the “obvious” algorithms provided by Dr.
`
`Martin are required to perform the claimed function and render the claim definite, these
`
`algorithms must be included in the structure linked to the claimed “computing . . .” function.
`
`5 As noted in Fitbit’s opening brief, this is a very narrow exception applicable only where
`standard microprocessors can be structure for ‘functions [that] can be achieved by any general
`purpose computer without special programming.” D.I. 72 at 5.
`6 The algorithms now identified by Dr. Martin were never mentioned by Philips during the meet
`and confer process or in the joint chart submitted to the court, nor does Philips include them in
`its proposed construction.
`
`- 4 -
`
`

`

`
`
`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 9 of 26
`
`2.
`
`Philips’ case law citations actually support a finding of indefiniteness
`
`Philips’ argument that the specification need not disclose what was known to a skilled
`
`artisan is not correct in the context of disclosing structure for a means-plus-function limitation.
`
`Here, Philips cites to a number of cases that do not stand for the propositions Philips claims.
`
`Philips cites S3 Inc. v. NVIDIA Corp., 259 F.3d 1364, 1371 (Fed. Cir. 2001) to argue that the
`
`specification need not disclose an algorithm known to a POSITA. See D.I. 73 at 8. The S3
`
`decision said no such thing. In S3, the MPF term at issue was not a computer-implemented
`
`function, but rather a means for receiving a data stream. S3, 259 F.3d at 1370. The specification
`
`did disclose the structure (a known electrical component called a “selector”) corresponding to the
`
`claimed function. Id. at 1370-71. NVIDIA argued that the disclosure of the electronic selector
`
`component alone did not provide sufficient details about the “electronic structure” or the “details
`
`of its electronic operation.” Id. at 1371. The Federal Circuit stated that these mundane details
`
`related to a “standard electronic component” were not required to be disclosed in the
`
`specification. Id. at 1371-72. This is far from holding that an algorithm required to perform the
`
`claimed computer-implemented function need not be disclosed. Philips also provides entirely
`
`context-lacking citations to Finisar Corp. v. DirecTV Grp., Inc., 523 F.3d 1323, 1340 (Fed. Cir.
`
`2008) and Biomedino, LLC v. Waters Techs. Corp., 490 F.3d 946, 950 (Fed. Cir. 2007). See D.I.
`
`73 at 8. In both cases, the Federal Circuit found means-plus-function limitations indefinite due to
`
`lack of a linked structure disclosed in the specification. Finisar, 523 F.3d at 1340-41; Biomedino,
`
`490 F.3d at 951-53.
`
`Indeed, the analysis and outcome in Biomedino directly contradicts Philips’ position. In
`
`Biomedino, the Federal Circuit asked “the following question: for purposes of § 112, P 6, is
`
`sufficient corresponding structure disclosed when the specification simply recites that a claimed
`
`function can be performed by known methods or using known equipment where . . . the
`
`- 5 -
`
`

`

`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 10 of 26
`
`
`
`testimony of experts suggest that known methods and equipment exist?” Biomedino, 490 F.3d at
`
`951. The Federal Circuit answered this question in the negative, and explicitly distinguished
`
`cases where the specification described how methods for performing the claimed function were
`
`known from cases where this information was provided by expert opinion alone. Id. at 951-52
`
`(“There is a significant difference between the facts of Atmel and those in the present case.
`
`In Atmel it was not the fact that one skilled in the art was aware of known circuit techniques that
`
`resulted in a conclusion that sufficient structure was recited. Rather, it was the inclusion in the
`
`written description . . . The expert’s testimony did not create or infer the structure”). Similarly, in
`
`Finisar, the Federal Circuit explained that structural disclosure “at least [] satisfact[ory] to one of
`
`ordinary skill in the art” must be included in the specification. Finisar, 523 F.3d at 1340. In
`
`Finisar, the Federal Circuit referenced a mathematical formula as something that would be
`
`“satisfactory” to a POSITA (id.)—something conspicuously missing from the ’007 patent.
`
`Philips also relies heavily on Alfred E. Mann Found. for Sci. Research v. Cochlear Corp.
`
`841 F.3d 1334 (Fed. Cir. 2016). See D.I. 73 at 8, 10. In Alfred Mann, the Federal Circuit found
`
`sufficient structural disclosure for certain challenged claims because the specification adequately
`
`disclosed an algorithm for “processing [] status-indicating signals to derive information
`
`therefrom.” Alfred E. Mann, 841 F.3d at 1345. The specification disclosed that “both voltage and
`
`current are measured and that these values are associated with the [claimed] ‘status-indicating
`
`signal’” and also that “impedance is calculated based on voltage and current.” Id. The Federal
`
`Circuit found that this disclosure, which expressly linked impedance, voltage, and current in a
`
`single phrase, was enough to “render the bounds of the claim understandable to one of ordinary
`
`skill in the art” given that both parties’ experts testified that a POSITA’s knowledge of Ohm’s
`
`law reflecting the relationship between impedance, voltage and current meant that the disclosure
`
`- 6 -
`
`

`

`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 11 of 26
`
`
`
`of measurements of voltage and current necessarily also disclosed impedance. Id.
`
`Unlike the claims found definite in Alfred E. Mann, the ’007 patent does not provide any
`
`disclosure of “computing athletic performance feedback data from the series of time-stamped
`
`waypoints.” The ’007 patent specification notes that “real-time athletic performance algorithms”
`
`were not disclosed in GPS prior art systems and that a so-called, unspecified “smart algorithm”
`
`could be used as part of the process. ’007 patent, 1:47-48, 7:52. Indeed, the ’007 claims are more
`
`similar to those found indefinite in Alfred E. Mann because, similar to those claims, the ’007
`
`claims’ “means for computing . . .” function “may be implemented through various unspecified
`
`algorithms.” Id. at 1343-44. The Federal Circuit affirmed indefiniteness where the “patent d[id]
`
`not disclose an algorithm, or even a small set of algorithms for performing the claimed
`
`logarithmic conversion function” and noted that “[d]isclosing [a] broad class of [logarithmic
`
`conversion] d[id] not limit the scope of the claim . . . as required by Section 112”). Id.
`
`3.
`
` Philips’ other arguments against indefiniteness fail
`
`Philips’ proposed construction is also wrong because identification of the generic
`
`processor alone as the linked structure, without an algorithm to program the processor, would
`
`result in functional claiming of “any means for performing the recited function,” which is “at
`
`odds with the requirements of 35 U.S.C. § 112.” WMS Gaming, Inc. v. Int’l Game Tech., 184
`
`F.3d 1339, 1348 (Fed. Cir. 1999).
`
`Further, Philips’ attempt to rely on structural details of system components unrelated to
`
`performance of the means for computing function are irrelevant, as the structural details it
`
`identifies do not provide the requisite algorithm for “computing athletic performance feedback
`
`data . . .”. See D.I. 73 at 9. Here, Philips merely identifies that the generic processor (CPU 602)
`
`with memory (memory 608) obtains inputs (time-stamped waypoints) from a GPS receiver
`
`module and then outputs athletic performance feedback data. See id. Fatally, this does not
`
`- 7 -
`
`

`

`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 12 of 26
`
`
`
`disclose how the generic processor “comput[es] athletic performance feedback data.” Dr. Martin
`
`conceded that the processor could not perform this function, absent additional programming that
`
`is not disclosed in the specification. Martin Tr. 49:25-50:2 (“Q. But the key is that someone
`
`would need to program those off-the-shelf processors; correct? A. That is correct”) (emphasis
`
`added).
`
`Federal Circuit precedent confirms that simply disclosing inputs and expected outputs is
`
`not sufficient for disclosure of a computer-implemented algorithm—rather, the specification (not
`
`expert testimony) must disclose how the processor performs the claimed function. Augme Techs.,
`
`Inc. v. Yahoo! Inc., 755 F. 3d 1326, 1338 (Fed. Cir. 2014) (“disclosing a black box that performs
`
`the recited function is not a sufficient explanation of the algorithm required to render [a] means-
`
`plus-function term definite”); Function Media, 708 F.3d at 1318 (““[i]t is well-settled that simply
`
`disclosing software, . . . without providing some detail about the means to accomplish the
`
`function, is not enough”); Aristocrat, 521 F.3d at 1334 (rejecting argument that sufficient
`
`structure was disclosed in patent because it simply “describes the result of practicing the third
`
`function . . . the equation is not an algorithm that describes how the function is performed, but is
`
`merely a mathematical expression that describes the outcome of performing the function”).
`
`Philips’ statement that the claimed function of “computing various forms of elapsed distance,
`
`current and average speed, and current and average pace from a series of GPS waypoints . . . is
`
`the algorithm” (D.I. 73 at 10 (emphasis added)) is exactly the argument the Federal Circuit
`
`rejected as a matter of law in Augme and Aristocrat. See Augme, 755 F.3d at 1326; Aristocrat,
`
`521 F.3d at 1334.
`
`4.
`
`Philips misrepresents Fitbit’s proposed construction and the parties’
`disputes
`
`Philips’ opening brief is inconsistent with the joint claim construction chart (see D.I. 68-
`
`- 8 -
`
`

`

`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 13 of 26
`
`
`
`1), misrepresents Fitbit’s proposed construction, and inaccurately portrays the parties’ disputes
`
`regarding the “means for computing . . .” and the “means for suspending…” terms. For example,
`
`Fitbit’s proposal for “means for computing . . .” includes the function and specific reference to
`
`the lack of structure, which Philips ignores. (Compare D.I 65-1 at 1-2 with D.I 73 at 5.)
`
`Philips also claims in its brief that the parties do not have “any real dispute as to
`
`structure” for this term. As discussed above and shown in the joint claim construction chart, this
`
`is clearly false. Further, there is an even more fundamental dispute between the parties which
`
`Philips now ignores: whether structure and function must be identified separately for
`
`construction of a means-plus-function term. D.I. 72 at 2 (Philips combines structure and function
`
`into a “Proposed Construction”). Ignoring the wealth of controlling Federal Circuit authority
`
`spelling out the two-step process for MPF construction and application of that construction to
`
`determine infringement (identification of function first, then structure clearly linked to
`
`performance of the claimed function), Philips insists on proposing a “combination” construction
`
`that does not delineate a clear function and its linked structure.7 Philips’ proposed combination
`
`seeks to capture all possible algorithms that could allow a processor to perform the claimed
`
`function, and should therefore be rejected.
`
`5.
`
`Construction of “athletic performance feedback data”
`
`Philips’ effort to exclude distance remaining, time remaining, and calories burned
`
`
`7 As Fitbit explained in its opening claim construction brief (D.I. 72 at 1-4) and the Motion for
`Partial Summary Judgment (D.I. 44 at 4-9), construction of means-plus-function claim
`limitations is a two-step process that requires identification of both a function and its
`corresponding linked structure. Williamson, 792 F.3d at 1351-52 (“Construing a means-plus-
`function claim term is a two-step process. The court must first identify the claimed function.
`Then, the court must determine what structure, if any, disclosed in the specification corresponds
`to the claimed function”) (citations omitted). The Federal Circuit’s Model Jury Instructions also
`illustrate this two-step process. See Peterman Decl. Ex. B (Instruction 3.1b requiring, for
`purposes of finding infringement, separate identification of structure and function for means-
`plus-function terms).
`
`- 9 -
`
`

`

`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 14 of 26
`
`
`
`contradicts the specification and relies exclusively on attorney argument and unsupported expert
`
`opinions.8 The specification clearly states that distance remaining, time remaining, and calories
`
`burned are “performance data” calculated “[f]rom [the athlete’s GPS positions and times data
`
`(i.e., a series of time-stamped waypoints)], performance data such as elapsed distance, current
`
`and average speeds and paces, calories burned, miles remaining, and time remaining are
`
`calculated.” ’007 patent, 7:40-48 (emphasis added).
`
`Philips, citing no evidence, argues that “miles remaining” and “time remaining” should
`
`be excluded from “athletic performance feedback data” because both “require that a user input
`
`some sort of destination end point for the [] session—a step contrary to the calculation
`
`contemplated by either claim 1 or claim 21.” D.I. 73 at 7. Philips provides no explanation why
`
`entering a destination would be a “step contrary” to either of these claims’ calculations.
`
`Moreover, Philips’ underlying premise is wrong as the specification expressly states that the user
`
`can use input buttons to set performance targets (e.g., total miles or time): “The GPS-based
`
`personal performance monitor and feedback device 101 includes input buttons 115 . . . for
`
`inputting the feedback options and targets.” ’007 patent 4:4-8; see also id. at 2:14-16. And,
`
`Philips’ expert admitted that one could just enter a “total distance”—such as in a situation where
`
`an athlete is running laps on a track. Martin Tr. 87:24-89:19.
`
`Philips and its expert argue “miles remaining” should be excluded because it is “based
`
`solely on the most recent GPS location (rather than a series of time-stamped waypoints[).]” D.I.
`
`73 at 7; D.I. 73-5, ¶ 26. Yet, during his deposition, Dr. Martin admitted that calculating “distance
`
`remaining” does in fact involve “using a series of waypoints,” since the “total distance that
`
`8 Philips seeks to exclude these instances of performance feedback data because they make the
`required algorithms (that are missing from the specification) even more complicated. Philips’
`expert offers no example of an algorithm that would perform the calculations for these claimed
`functions of calories burned or miles and time remaining.
`
`- 10 -
`
`

`

`Case 1:19-cv-11586-IT Document 78 Filed 07/08/20 Page 15 of 26
`
`
`
`you’ve already traveled” is calculated by “the distance between the waypoints as you’ve gone
`
`along.” Martin Tr. 90:5-92:16. Dr. Martin’s deposition admission is unsurprising, as his initial
`
`opinion was clearly not thought through: a calculation for miles remaining must necessarily
`
`include both the starting location and the current location. For example, if an athlete inputs a goal
`
`to run 5 miles, and at the 3 mile mark she is told she has 2 miles remaining, that “miles
`
`remaining” feedback is based on her initial location (time-stamped waypoint 1) and current
`
`location (time-stamped waypoint 2) and thus a calculation using a series of time-stamped
`
`waypoints.
`
`Philips’ attorneys argue (citing no evidence) that excluding “calories burned” from the
`
`claimed feedback data “of course makes sense,” as “tracking calories has little to do with
`
`feedback on performance[.]” D.I. 73 at 7. Philips’ argument is contradicted by the intrinsic
`
`record which specifically identifies calories burned as relying on a series of time-stamped GPS
`
`waypoints. ’007 patent, 7:40-48. Further, in describing the background art the specification
`
`expressly describes “calories burned” as a feedback provided in real-time: “Treadmills provide
`
`the runner with continuous read-outs of time, distance, speed, pace, inclination, calories
`
`burned and so forth.” Id. at 1:22-24 (emphasis added.)
`
`Beyond attorney argument, Philips employs a red herrin

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