`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE DISTRICT OF MASSACHUSETTS
`
`
`PHILIPS NORTH AMERICA LLC,
`
`
`Plaintiff,
`
`
`
`
`Civil Action No. 1:19-cv-11586-FDS
`
`
`
`
`
`
`v.
`
`FITBIT, INC.,
`
`
`
`
`Defendant.
`
`DEFENDANT’S OPPOSITION TO PLAINTIFF’S
`MOTION FOR LEAVE TO AMEND L.R. 16.6(d)(1) INFRINGEMENT CONTENTIONS
`
`
`
`
`
`
`
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 2 of 18
`
`
`
`TABLE OF CONTENTS
`
`Page
`
`INTRODUCTION ...........................................................................................................................1
`
`LEGAL STANDARD ......................................................................................................................2
`
`ARGUMENT ...................................................................................................................................3
`
`I.
`
`THERE IS NO GOOD CAUSE FOR PHILIPS’S AMENDMENTS. ................................3
`
`1.
`
`2.
`
`Philips Cannot Justify Its Extended Delay...............................................................3
`
`Philips’s New And Undisclosed Proposed Amendments Prejudice Fitbit. .............8
`
`II.
`
`PHILIPS’S PROPOSED AMENDMENTS WOULD BE FUTILE. ...................................9
`
`CONCLUSION ..............................................................................................................................13
`
`
`
`
`
`
`
`
`
`
`
`
`i
`
`
`
`
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 3 of 18
`
`
`
`TABLE OF AUTHORITIES
`
`CASES
`
`Page(s)
`
`Abiomed, Inc. v. Maquet Cardiovascular LLC,
`Civil Action No. 16-10914-FDS, 2020 WL 3868803 (D. Mass. July 9, 2020) .................. 5
`
`Acer, Inc. v. Tech. Properties Ltd.,
`No. 5:08-CV-00877 JF/HRL, 2010 WL 3618687 (N.D. Cal. Sept. 10, 2010) ................... 3
`
`Allvoice Developments US, LLC v. Microsoft Corp.,
`612 F. App’x 1009 (Fed. Cir. 2015) ................................................................................... 8
`
`Inline Plastics Corp. v. Lacerta Group, Inc.,
`No. 4:18-11631-TSH (D. Mass. Feb. 23, 2021) ................................................................. 2
`
`Intellectual Ventures, LLC v. NetApp, Inc.,
`No. 16-10868-PBS (D. Mass. Aug. 15, 2019) .................................................................... 3
`
`Medtronic CoreValve, LLC v. Edwards Lifesciences Corp.,
`741 F.3d 1359 (Fed. Cir. 2014)............................................................................. 11, 12, 13
`
`Nat. Alts. Int'l, Inc. v. Iancu,
`904 F.3d 1375 (Fed. Cir. 2018)......................................................................................... 12
`
`O2 Micro Int’l Ltd. v. Monolithic Power Sys., Inc.,
`467 F.3d 1355 (Fed. Cir. 2006)............................................................................... 2, 3, 7, 8
`
`Potter Voice Techs., LLC v. Apple Inc.,
`No. C 13-1710 CW, 2015 WL 13404106 (N.D. Cal. Mar. 20, 2015) ................................ 8
`
`Synopsys, Inc. v. Atoptech, Inc.,
`No. 13CV02965MMCDMR, 2016 WL 4945489 (N.D. Cal. Sept. 16, 2016) .................... 5
`
`35 U.S.C. § 119(e) ........................................................................................................................ 11
`
`STATUTES
`
`RULES
`
`Local Rule 16.6 ....................................................................................................................... 5, 6, 8
`
`Local Rule 16.6(d)(1)(A) ................................................................................................................ 2
`
`Local Rule 16.6(d)(5).................................................................................................................. 4, 6
`
`
`
`
`
`ii
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 4 of 18
`
`
`
`REGULATIONS
`
`37 C.F.R. § 1.53 ...................................................................................................................... 10, 11
`
`37 C.F.R. § 1.78(a)(4) ................................................................................................................... 12
`
`
`
`
`
`
`
`iii
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 5 of 18
`
`
`
`INTRODUCTION
`
`Plaintiff Philips North America LLC (“Philips”) asks the Court to ignore its lack of
`
`diligence and expand the case to include additional accused products after the close of fact
`
`discovery. Specifically, Philips seeks to amend its infringement contentions after the close of fact
`
`discovery to accuse four additional products released by Defendant Fitbit, Inc. (“Fitbit”) in April
`
`and September 2020 of infringing U.S. Patent No. 8,277,377 (the “’377 Patent”). See D.I. 168
`
`(“Motion”) at 1. Philips does not provide any credible justification for its significant delay and
`
`does not establish good cause for expanding the scope of the accused Fitbit products at this late
`
`stage. Philips’s Motion should be denied for three reasons.
`
`First, Philips’s failure to diligently pursue its infringement claims alone warrants denial of
`
`its Motion. Philips waited to request leave to add its infringement contentions for the Charge 4
`
`product until almost one year after its release and waited to request leave to add its infringement
`
`contentions for the Versa 3, Inspire 2, and Sense products until approximately six months after
`
`their release. Philips cannot justify that extended delay and fails to carry its burden to show that
`
`it acted diligently. The Court should deny the Motion on that basis alone.
`
`Second, Philips fails to apprise the Court and Fitbit of its proposed amendments to its
`
`contentions and thus cannot demonstrate that the amendments will not prejudice Fitbit. In
`
`particular, Philips’s Motion does not attach any claim charts for the Versa 3, Inspire 2, and Sense
`
`products that Philips now seeks to accuse of infringement. And the sole claim chart that Philips
`
`did submit with its Motion for the Charge 4 product differs in material respects from the chart
`
`Philips previously provided to Fitbit. Adding four new products and infringement claims that were
`
`not explored during discovery, and have still not been fully disclosed, would significantly
`
`prejudice Fitbit. Philips’s incomplete and unspecified amendments should not be allowed.
`
`
`
`1
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 6 of 18
`
`
`
`Third, Philips’s proposed amendment would be futile because the ’377 Patent expired
`
`before the release dates of the new products. The ’377 Patent claims priority to an earlier
`
`application that is a conversion of a provisional application filed in 1999. Because the earlier
`
`application was identified as a conversion, the term of the ’377 Patent is calculated from the
`
`provisional date in 1999 and expired on January 18, 2020. Philips’s Motion argues that the
`
`identification of the earlier application as a conversion was an error. But the burden of providing
`
`an accurate priority claim is on the patent owner. As a consequence, the ’377 Patent expired
`
`months before any of the four newly-accused Fitbit products were released. Thus, the new
`
`products could not have infringed the expired ’377 Patent.
`
`LEGAL STANDARD
`
`Local Rule 16.6 required Philips to disclose its infringement claims and theories, with
`
`charts identifying “each accused product” and providing “an element-by-element description of
`
`where and how each element of each asserted claim is found in each accused product.” Local Rule
`
`16.6(d)(1)(A). The Rules further provide that, in recognition of the duty to supplement discovery
`
`responses, Philips’s infringement contentions “may be amended and supplemented only by leave
`
`of court upon a timely showing of good cause.”1 Local Rule 16.6(d)(5); see also Inline Plastics
`
`Corp. v. Lacerta Group, Inc., No. 4:18-11631-TSH, slip op. at 3 (D. Mass. Feb. 23, 2021).
`
`Whether good cause exists at this late stage depends upon Philips’s diligence and the prejudice to
`
`Fitbit. See O2 Micro Int’l Ltd. v. Monolithic Power Sys., Inc., 467 F.3d 1355, 1366 (Fed. Cir.
`
`2006). “The burden is on the movant to establish diligence rather than on the opposing party to
`
`establish a lack of diligence.” Id. Where the moving party fails to establish its own diligence,
`
`there is no good cause regardless of whether the proposed amendment causes prejudice. Id. at
`
`
`1 All emphases are added unless otherwise noted.
`2
`
`
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 7 of 18
`
`
`
`1368 (“Having concluded that the district court could properly conclude that [the plaintiff] did not
`
`act diligently in moving to amend its infringement contentions, we see no need to consider the
`
`question of prejudice to [the defendant].”).
`
`ARGUMENT
`
`I.
`
`THERE IS NO GOOD CAUSE FOR PHILIPS’S AMENDMENTS.
`
`1.
`
`Philips Cannot Justify Its Extended Delay.
`
`Philips provides no credible reason for waiting a year before filing its request to add the
`
`Charge 4 to its infringement claims and waiting six months before filing its request to add the
`
`Versa 3, Inspire 2, and Sense. (See Ex. N at 5; Ex. O at 7.2) In that time, Philips twice came within
`
`days of previously-scheduled deadlines for the close of fact discovery without amending its
`
`contentions. See D.I. 127, 152 (extending fact discovery). Only now—after the thrice-extended
`
`close of fact discovery—does Philips finally seek leave to amend its contentions. Contrary to
`
`Philips’s insistence that it expeditiously sought leave to amend, Philips’s conduct is the antithesis
`
`of diligence and should not be entertained. Indeed, courts have found a lack of diligence even
`
`where there is far less delay. See, e.g., Intellectual Ventures, LLC v. NetApp, Inc., No. 16-10868-
`
`PBS, slip op. at 2 (D. Mass. Aug. 15, 2019) (denying leave to amend contentions where, as here,
`
`relevant information was discovered months earlier, fact discovery was closed under amended
`
`deadlines, and opening expert disclosures were looming); Acer, Inc. v. Tech. Properties Ltd., No.
`
`5:08-CV-00877 JF/HRL, 2010 WL 3618687, at *5 (N.D. Cal. Sept. 10, 2010) (finding lack of
`
`diligence where patentee delayed for three months after it began source code review and three
`
`weeks after that review was completed).
`
`
`2 Citations to Exhibits A-Q refer to the lettered exhibits filed with Philips’s Motion. Citations to
`Exhibits 1-9 refer to the numbered exhibits filed with this Opposition.
`3
`
`
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 8 of 18
`
`
`
`For the Charge 4 product, Philips’s failure to timely amend its contentions within the
`
`discovery period is particularly inexcusable given that its proposed contentions cite exclusively to
`
`public information that was available nearly a year ago.3 Philips’s contentions in the Charge 4
`
`claim chart filed with the Motion consist entirely of screenshots of mobile phone user interfaces
`
`and references to publicly available documents. (See Ex. I.) Those contentions could have been
`
`compiled within days of the Charge 4’s release in April 2020 and could easily have been included
`
`in Philips’s First Supplemental Contentions, served one month later on May 15, 2020. (See Ex.
`
`1.) Philips at least tacitly acknowledges that it could have—and should have—sought leave to add
`
`the Charge 4 to its contentions at that time. Motion at 1 (“No new contentions with respect to any
`
`new products were added at this time, nor would it have been appropriate to add them without
`
`leave of court.”). Philips’s choice to instead wait almost a full year before seeking leave to add
`
`the Charge 4 to this case after fact discovery is inexcusable.
`
`For the Versa 3, Inspire 2, and Sense products, neither the Court nor Fitbit can fully assess
`
`the information Philips will rely on to support its contentions because Philips inexplicably did not
`
`submit any charts for those products with the Motion. Philips delayed for six months after the
`
`Versa 3, Inspire 2, and Sense were released before seeking to add them to its case and still has not
`
`disclosed exactly how Philips intends to amend its contentions for these three products. The
`
`cursory charts Philips provided in December 2020, (see Exs. 2-4), demonstrate that the significant
`
`delay cannot be explained by Philips’s general assertion that it needed to “inspect and confirm
`
`whether or not Fitbit’s new product infringed,” as those charts rely on screenshots and information
`
`that was publicly available months ago. Motion at 4; see also Synopsys, Inc. v. Atoptech, Inc., No.
`
`
`3 Philips’s conduct stands in stark contrast to the exemplary circumstances provided in Local Rule
`16.6(d)(5), which acknowledges that the “discovery of nonpublic information about the asserted
`infringement” may support a finding of good cause in the absence of prejudice.
`4
`
`
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 9 of 18
`
`
`
`13CV02965MMCDMR, 2016 WL 4945489, at *4 (N.D. Cal. Sept. 16, 2016) (finding a lack of
`
`diligence where the patentee’s conclusory and vague statements regarding a need for inspection
`
`failed to explain its delay).
`
`Philips’s heavy reliance on this Court’s decision in Abiomed is misplaced. See Abiomed,
`
`Inc. v. Maquet Cardiovascular LLC, Civil Action No. 16-10914-FDS, 2020 WL 3868803 (D.
`
`Mass. July 9, 2020). The facts of that case were starkly different. First, the Court found in
`
`Abiomed that, “while perhaps Maquet could have supplemented its contentions earlier,” it was
`
`reasonable in seeking to amend its contentions to add a single new product “three months after
`
`learning of a new product and less than one month after the Court’s ruling on its previous
`
`supplemental contentions.” Id. at *4. In contrast, here Philips seeks to add the Charge 4 one year
`
`after its release and the other products more than six months after their release and cannot point
`
`to any Court ruling in the interim that could justify the delay. Second, the Court found in Abiomed
`
`that Maquet acted reasonably in light of scheduling considerations that are not at issue here. The
`
`applicable scheduling order in Abiomed set a deadline for final amendments to contentions for a
`
`date “to be decided.” Id. at *3. When that date was eventually decided, Maquet had just one week
`
`to serve amended infringement contentions. Maquet immediately sought leave to amend, within
`
`the formal deadline to do so. Id. Here, by contrast, no deadline allowing late amendments was
`
`ever set, and Philips had no reason to believe that it was entitled to amend its contentions until
`
`after the close of fact discovery. Amendments to the contentions were always subject to the
`
`requirements of Local Rule 16.6, namely that contentions could only be amended “by leave of
`
`court upon a timely showing of good cause”—a requirement that Philips has not met.4 Local Rule
`
`
`4 The version of Local Rule 16.6, which was amended in June of 2018, that applied in Abiomed
`differed in important respects from the present version that governs this case. In particular, the
`5
`
`
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 10 of 18
`
`
`
`16.6(d)(5). Third, unlike in Abiomed, fact discovery in this case was extended three times, once
`
`on an emergency motion. See D.I. 116, 127, 152. Philips came within days of those deadlines
`
`without seeking leave to amend its contentions. As such, Philips had no reasonable reliance
`
`interest in seeking to amend its contentions after the thrice-extended, and now past, close of fact
`
`discovery.
`
`Philips’s additional reasons for its failure to timely amend its contentions are meritless post
`
`hoc excuses. For example, Philips asserts that it failed to include the Charge 4 in its First
`
`Supplemental Contentions—served weeks after the Charge 4 was released—because it “believed
`
`that the most efficient approach to amending the contentions would be to seek a single amendment
`
`that would cover all the new products released during the course of discovery.” Motion at 4. But
`
`even if efficiency could justify Philips’s delay, Philips had no way of knowing in April 2020 (when
`
`discovery was set to close in October 2020) whether additional Fitbit products would be released,
`
`much less knowing that the products would allegedly infringe. Indeed, the Versa 3, Inspire 2, and
`
`Sense were not announced until late August 2020, more than three months after Philips’s First
`
`Supplemental Contentions and four months after the Charge 4 was released. (Ex. O at 1.) Philips’s
`
`suggestion that it delayed adding the Charge 4 to its case because it thought Fitbit might release
`
`new products that might infringe strains credulity and is hardly the conduct of a diligent plaintiff.
`
`Moreover, Philips failed to seek leave to amend its contentions for another six months after the
`
`release of the later products. Thus, even if Philips were justified in waiting for those products to
`
`be released, Philips still waited an additional half a year to amend its contentions and failed to
`
`diligently prosecute its case.
`
`
`prior Rule provided a more permissive standard that only required good cause to amend for
`amendments made within thirty days or later of the Markman hearing.
`6
`
`
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 11 of 18
`
`
`
`Philips also mischaracterizes the parties’ communications regarding Philips’s proposed
`
`amendments. Philips asserts that Fitbit’s opposition is “inconsistent and unreasonable” because
`
`Fitbit supposedly “agreed not to oppose” Philips’s proposed amendments. See Motion at 5. No
`
`such agreement was ever reached. The correspondence instead demonstrates that Fitbit proposed
`
`potential compromises, and Philips rejected them. (See Ex. G at 4-5.) Philips first contacted Fitbit
`
`about a potential agreement for mutual amendments to infringement and invalidity contentions on
`
`January 11, 2021—nine months after the release of the Charge 4 and almost four months after
`
`the release of the other newly-accused products.5 (Id. at 5-6.) Four days later, Fitbit responded
`
`that it would not agree to Philips’s proposed amendment to add the Charge 4 and provided a
`
`counterproposal as to the other three products. (Id. at 5.) More than two weeks later, Philips
`
`rejected that proposal. (Id. at 4.) Thus, contrary to Philips’s assertion, Fitbit never agreed to forego
`
`its opposition to the late addition of new products. Indeed, Philips understood Fitbit’s opposition
`
`and sought to again discuss the issue more than a month later, on March 10, after another extension
`
`of fact discovery. (Id. at 3.) And if any doubt could have remained at the time of the parties’
`
`March 26 discovery conference, Fitbit reiterated that it opposed Philips’s amendments. (Ex. 5 at
`
`1.) Philips cannot justify its delay on the basis of an agreement that did not exist. See O2 Micro,
`
`467 F.3d at 1367 (affirming finding of unexcused delay where there was no tentative agreement
`
`or misleading conduct regarding proposed amended contentions).
`
`It is Philips’s burden to show that it acted with diligence. Id. at 1366. Philips fails to carry
`
`that burden, and its proposed amendments should be denied. See id. at 1368; Allvoice
`
`
`5 Philips first informed Fitbit of its intent to add the four products to its contentions on December
`14, 2020, and stated that it would file for leave to amend within the week. (See Ex. A at 2.) Philips,
`of course, did not amend its contentions at that time. Nor did Philips promptly seek to amend its
`contentions after Fitbit’s December 28 email explicitly stating that it would oppose introduction
`of the products. (See Ex. 6 at 1.)
`
`
`
`7
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 12 of 18
`
`
`
`Developments US, LLC v. Microsoft Corp., 612 F. App’x 1009, 1015 (Fed. Cir. 2015) (“If the
`
`moving party is not able to meet that burden [to demonstrate diligence], it is unnecessary to
`
`examine the potential prejudice of the amendment to the non-moving party.”).6
`
`2.
`
`Philips’s New And Undisclosed Amendments Prejudice Fitbit.
`
`In addition to Philips’s request to amend its contentions being untimely, it is substantially
`
`incomplete. Inexplicably, and contrary to Local Rule 16.6—which requires Philips to disclose
`
`infringement claim charts for each accused product—Philips’s Motion does not include any claim
`
`charts for three of the four newly-accused products. Thus, Philips fails to inform the Court and
`
`Fitbit of the substance of its proposed amendments for any of the Versa 3, Inspire 2, or Sense
`
`devices. Philips cannot claim that its amendments will not prejudice Fitbit when Philips has not
`
`even provided those amendments for scrutiny.
`
`The only claim chart that Philips did include with its Motion, purporting to chart
`
`infringement for the Charge 4 product, differs in material respects from the chart Philips previously
`
`provided to Fitbit in December 2020. Specifically, the chart Philips attached to its Motion
`
`conspicuously omits references to “Active Zone Minutes,” a new feature that was introduced with
`
`the Charge 4 and that was included in Philips’s December 2020 chart. (Compare Ex. 7 at 21-25
`
`with Ex. I at 21-23.; see also Ex. N at 1 (announcing the launch of Active Zone Minutes as a new
`
`feature).) Of course, neither the Court nor Fitbit can tell whether Philips intends to assert a new
`
`infringement theory against that feature for the three remaining products for which Philips has not
`
`submitted any charts. The charts that Philips provided to Fitbit in December 2020 for those
`
`products, however, all asserted new infringement theories accusing the Active Zone Minutes
`
`
`6 The case Philips cites for the proposition that the Court should exercise its discretion to allow
`Philips’s amendment even if the Court finds a lack of diligence (see Motion at 3) is inapposite.
`That case dealt with an unopposed request to amend contentions. Potter Voice Techs., LLC v.
`Apple Inc., No. C 13-1710 CW, 2015 WL 13404106, at *1 (N.D. Cal. Mar. 20, 2015).
`8
`
`
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 13 of 18
`
`
`
`feature. (See Ex. 2 at 20-27; Ex. 3 at 20-27; Ex. 4 at 20-27.) And Philips’s counsel has at least
`
`hinted that, while there may be overlap in its infringement theories for the new and old products,
`
`Philips does intend to assert new infringement theories against the new features of the new
`
`products. (See Ex. A (“These products infringe for many of the same reasons already set forth
`
`in the contentions for related products, but appear to have also introduced new features as
`
`well.”).) Philips’s accusation of those new features prejudices Fitbit because it introduces new
`
`infringement theories that were not disclosed or investigated in discovery.
`
`Even if Philips truly does intend to amend its contentions without accusing any new
`
`features, the addition of four new products at this late stage unduly prejudices Fitbit. Fact
`
`discovery was extended three times already in this case and is now closed. Because these products
`
`were not timely added to Philips’s infringement contentions, Fitbit and Philips neither took nor
`
`produced discovery relating to these products during fact discovery. To require Fitbit to go
`
`forward without the relevant discovery or to yet again reopen discovery would prejudice Fitbit and
`
`disrupt the orderly progress of this litigation. Especially in light of Philips’s lack of diligence, the
`
`Court should not require Fitbit to go without or to engage in additional discovery at this late stage.
`
`II.
`
`PHILIPS’S PROPOSED AMENDMENTS WOULD BE FUTILE.
`
`Even if the Court were to find good cause for Philips’s amendments, Philips’s Motion
`
`should still be denied because the ’377 Patent expired on January 18, 2020, months before any of
`
`the newly-accused products were released. The patent expired in January 2020 because of
`
`decisions the patentee made when filing U.S. Patent No. 6,602,191 (the “’191 Patent”), to which
`
`the ’377 Patent claims priority. Philips disagrees with the ’377 Patent’s expiration date by accusing
`
`Fitbit of relying on an “incorrect premise” that the ’191 Patent “was a ‘conversion’” when
`
`calculating the expiration date of the ’377 Patent. Motion at 6. Far from incorrect, that premise is
`
`exactly what the patents have said to the public for years. See Ex. 8 at 1:18-22 (’377 Patent stating
`9
`
`
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 14 of 18
`
`
`
`that the ’191 Patent “is a conversion of U.S. Provisional Application Ser. No. 60/172,486, filed
`
`Dec. 17, 1999”); Ex. 9 at 1:9-10 (’191 Patent stating that it “is a conversion of U.S. Provisional
`
`Patent Application Ser. No. 60/172,486 filed Dec. 17, 1999”). Philips’s explanation for those
`
`statements in the patents is essentially that they were mistakes, and Philips does not want to be
`
`stuck with the consequences of the mistakes. Mistake or not, the burden was on the patentee to
`
`clearly and accurately give the public notice of the priority claims. Based on the priority claims
`
`written into the patents, the ’377 Patent expired in January 2020, and Philips thus cannot assert
`
`infringement claims for any of the four products it seeks to add to its contentions.
`
`The key question in determining the expiration date of the ’377 Patent is which of the
`
`patent’s priority applications should be used as the starting date for the ’377 Patent’s twenty-year
`
`term. The earliest application in the ’377 Patent’s priority chain is Provisional Application No.
`
`60/172,486 (the “’486 Application”), filed December 17, 1999. The next application in the chain
`
`is the ’191 Patent, filed December 15, 2000. Because the ’191 Patent was identified as a
`
`conversion of the ’486 Application (see Ex. 9 at 1:9-10), the filing date of the ’486 Application—
`
`and not the filing date of the ’191 Patent—is the start of the ’377 Patent’s term. See 37 C.F.R. §
`
`1.53 (“Conversion of a provisional application to a nonprovisional application under this paragraph
`
`will result in the term of any patent to issue from the application being measured from at least the
`
`filing date of the provisional application for which conversion is requested.”). Thus, the ’377
`
`Patent’s term expired on January 18, 2020—twenty years after the ’486 Application’s filing date
`
`(December 17, 1999) plus the thirty-two days of term extension granted on the face of the ’377
`
`Patent. (See Ex. 8 at Cover (noting patent term extension of 32 days).)
`
`The public is entitled to rely on the unequivocal statements in the ’377 Patent and the ’191
`
`Patent priority claims—including the statement that the ’191 Patent was a conversion—in
`
`
`
`10
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 15 of 18
`
`
`
`determining the expiration date of the ’377 Patent. The burden is on the patentee to accurately
`
`state its priority claims. Medtronic CoreValve, LLC v. Edwards Lifesciences Corp., 741 F.3d 1359,
`
`1367 (Fed. Cir. 2014) (“The patentee is the person best suited to understand the genealogy and
`
`relationship of her applications; a requirement for her to clearly disclose this information should
`
`present no hardship.”) The patentee clearly stated in the ’191 Patent that it was a conversion and
`
`thus should bear the consequences of that conversion, including the expiration date of the ’377
`
`Patent. While Philips may wish its term were longer, there can be no claim of surprise because
`
`the regulations explicitly warn patentees of that consequence. See 37 C.F.R. § 1.53
`
`(“[A]pplicants should consider avoiding this adverse patent term impact by filing a nonprovisional
`
`application claiming the benefit of the provisional application under 35 U.S.C. § 119(e), rather
`
`than converting the provisional application into a nonprovisional application pursuant to this
`
`paragraph.”).
`
`Tellingly, neither Philips nor the prior owners of the ’191 Patent and ’377 Patent attempted
`
`to change the priority claim statements written into the patents years ago. The applicant never
`
`amended the specification of the ’191 Patent application to update its characterization as a
`
`conversion. The applicant continued to characterize the ’191 Patent as a conversion when filing
`
`the ’377 Patent application nearly eight years later. And there was never any attempt to change
`
`the priority statement in either patent. Thus, the patents have given the public notice that the ’191
`
`Patent was a conversion—and that the ’377 Patent would expire in January 2020—for over twenty
`
`years.
`
`Philips attempts to sidestep the conversion issue by stating that the patentee never filed a
`
`separate request, aside from the priority statements in the patent specifications, for conversion.
`
`Motion at 6-7. But Philips cites no support for the proposition that the absence of any such separate
`
`
`
`11
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 16 of 18
`
`
`
`request changes the priority claim made in the ’191 Patent specification. Nor does Philips cite any
`
`authority showing that the priority claim in the specification did not suffice for the required
`
`conversion request. In fact, Philips included its statement that the ’191 Patent was a conversion in
`
`the very first sentence of the patent, where the rules at the time required accurate priority
`
`information to be provided. See 37 C.F.R. § 1.78(a)(4) (July 2000). Philips’s only real response
`
`to the public notice provided in its patents is that the public should forensically sift through the file
`
`histories of its patents in an attempt to discern the priority chain on their own. Motion at 6. But
`
`the law makes clear that the public does not bear such a burden in view of the requirement that
`
`patentees clearly state their priority claims. Medtronic, 741 F.3d at 1367 (“Allocating the
`
`responsibility of disclosure through specific references to the patentee eliminates the inefficiencies
`
`associated with having the public expend efforts to unearth information when such information is
`
`readily available to the patentee.”); see also Nat. Alts. Int'l, Inc. v. Iancu, 904 F.3d 1375, 1380
`
`(Fed. Cir. 2018) (“Furthermore, examiners and adjudicators cannot be expected to scrutinize the
`
`prosecution history of an application and each parent application to determine whether the
`
`application would have met § 120’s requirements at any point during its pendency.”).
`
`The additional excuses Philips offers—including that the priority claims were sloppy
`
`draftsmanship and an imprecise “colloquial reference” (Motion at 7)—all but admit that the ’191
`
`Patent was identified as a conversion, even if mistakenly so. Philips cannot undo that mistake
`
`now, over twenty years later, to capture another year of patent term and four more Fitbit products
`
`with its infringement case. The ’377 Patent and the ’191 Patent both include express and
`
`unmistakable priority claims stating that the ’191 Patent was a conversion and thus that the public
`
`may safely practice the claims of the ’377 Patent after its expiration on January 18, 2020. Philips
`
`must bear the consequences of those statements. See Medtronic, 741 F.3d at 1367. Accordingly,
`
`
`
`12
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 17 of 18
`
`
`
`the ’377 Patent expired before any of the four newly-accused products were released, and Phillips
`
`cannot accuse them of infringement.
`
`CONCLUSION
`
`For the foregoing reasons, Fitbit respectfully requests that the Court deny Philips’s Motion.
`
`
`
`
`
`Dated: April 14, 2021
`
`By:
`
`
`
`
`
` /s/ Karim Oussayef
`Karim Z. Oussayef (pro hac vice)
`koussayef@desmaraisllp.com
`Leslie M. Spencer (pro hac vice)
`lspencer@desmaraisllp.com
`Brian D. Matty (pro hac vice)
`bmatty@desmaraisllp.com
`
`DESMARAIS LLP
`230 Park Avenue
`New York, NY 10169
`Telephone: (212) 351-3400
`Facsimile: (212) 351-3401
`
`Ameet A. Modi (pro hac vice)
`amodi@desmaraisllp.com
`Emily H. Chen (pro hac vice)
`echen@desmaraisllp.com
`
`DESMARAIS LLP
`101 California Street
`San Francisco, CA 94111
`Telephone: (415) 573-1900
`Facsimile: (415) 573-1901
`
`Gregory F. Corbett (BBO # 646394)
`WOLF, GREENFIELD & SACKS, P.C.
`600 Atlantic Avenue
`Boston, MA 02110
`Telephone: (617) 646-8000
`Facsimile: (617) 646-8646
`E-mail: gcorbett@wolfgreenfield.com
`
`Attorneys for Fitbit, Inc.
`
`13
`
`
`
`Case 1:19-cv-11586-FDS Document 173 Filed 04/14/21 Page 18 of 18
`
`CERTIFICATE OF SERVICE
`
`I hereby c