throbber

`
`
`
`Paper No. 59__
`IPR2018-00767
`
`
`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`
`
`
`
`SONOS, INC.
`Petitioner
`
`v.
`
`IMPLICIT, LLC
`Patent Owner
`
`
`
`
`IPR2018-00767
`U.S. Patent No. 8,942,252
`
`
`
`
`
`
`
`PETITIONER’S RESPONSE TO
`PATENT OWNER’S OPENING BRIEF AFTER REMAND
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`
`
`TABLE OF CONTENTS
`
`TABLE OF CONTENTS ........................................................................................... i
`
`TABLE OF AUTHORITIES .................................................................................... ii
`
`INTRODUCTION ..................................................................................................... 1
`
`I.
`
`IMPLICIT’S CASELAW DOES NOT SUPPORT REVISITING THE
`FINAL WRITTEN DECISIONS..................................................................... 2
`
`A.
`
`B.
`
`Roche Does Not Apply to Corrections Beyond § 102(f) ...................... 3
`
`Southwest and SIPCO Do Not Support Implicit’s Reading .................. 4
`
`II.
`
`THE PUBLIC POLICY INTERESTS IDENTIFIED BY IMPLICIT
`DO NOT SUPPORT RETROACTIVE EFFECT ON THESE FINAL
`WRITTEN DECISIONS ................................................................................. 5
`
`A.
`
`B.
`
`C.
`
`The Public Interest in Naming Inventors Correctly Does Not
`Outweigh the Public’s Interest in Case Finality and Fairness .............. 5
`
`Public Policy Dictates That Implicit’s Request Be Denied .................. 6
`
`Implicit’s Inventorship Correction Was Not Informed by the
`Board’s Findings ................................................................................... 6
`
`III. CONCLUSION ................................................................................................ 7
`
`
`
`
`
`i
`
`

`

`
`
`CASES
`
`TABLE OF AUTHORITIES
`
`Egenera, Inc. v. Cisco Systems, Inc.,
`972 F.3d 1367 (Fed. Cir. 2020) ............................................................................ 7
`
`Emerson Elec. Co. v. SIPCO, LLC,
`IPR2016-00984 (P.T.A.B. Jan. 24, 2020) ............................................................ 5
`
`Heat Techs., Inc. v. Papierfabrik Aug. Koehler SE,
`2019 WL 1915620 (N.D. Ga. Jan. 3, 2019) .......................................................... 4
`
`Interactive Gift Exp., Inc. v. Compuserve Inc.,
`256 F.3d 1323 (Fed. Cir. 2001) ............................................................................ 6
`
`Lizut v. Department of Army,
`717 F.2d 1391 (Fed. Cir. 1983) ............................................................................ 6
`
`New Hampshire v. Maine,
`532 U.S. 742 (2001) .............................................................................................. 6
`
`Roche Palo Alto LLC v. Ranbaxy Lab'ys Ltd.,
`551 F. Supp. 2d 349 (D.N.J. 2008) ....................................................................... 3
`
`Southwest Software, Inc. v. Harlequin Inc.,
`226 F.3d 1280 (Fed. Cir. 2000) ........................................................................3, 4
`
`
`
`ii
`
`

`

`
`
`
`
`
`
`
`INTRODUCTION
`
`Implicit’s post-Final Written Decision change in inventorship does not undo
`
`the invalidity decided in these Final Written Decisions because § 256 limits
`
`retroactive validity applications to scenarios of misjoinder or nonjoinder under §
`
`102(f). The Board did not hold the challenged claims invalid under § 102(f) and
`
`thus § 256 does not apply to undo The Board’s invalidity finding here. Principles
`
`of waiver and judicial estoppel, as outlined in Sonos’s opening brief, support this
`
`notion as it has long been a hallmark of the American Judicial system that parties
`
`cannot return to tribunals and reopen decisions by advancing new arguments or
`
`changing certain facts. Setting these dispositive aspects aside, even were the
`
`Board to consider the changed inventorship, the result will ultimately be the same
`
`because there are other reasons independent of inventorship why the swear-behind
`
`attempt fails. Undoing the invalidity decisions at this stage, based on activity
`
`occurring years after the issuance of the Final Written Decisions, would also
`
`violate Due Process and the APA, capping off why changed inventorship does not
`
`resurrect the invalid claims here.
`
`Implicit advances two unpersuasive arguments in its opening brief. First,
`
`Implicit argues that § 256 can apply retroactively, compared to §§ 254 and 255,
`
`which apply prospectively. But this does not get Implicit the relief it asks for. The
`
`question is not whether § 256 applies retroactively in some scenarios, the question
`
`1
`
`

`

`
`
`is “does it apply retroactively in this scenario?” Where misjoinder or nonjoinder
`
`
`
`
`
`were not at issue in the IPRs, the statute and caselaw are clear that Implicit cannot
`
`use § 256 as a get-out-of-jail free card for other types of invalidity. It makes sense
`
`why § 256 applies retroactively only for cases of misjoinder or nonjoinder because
`
`with misjoinder or nonjoinder the correction completely removes the basis for
`
`invalidity. In cases with other types of invalidity, like ours, correction does not
`
`remove the basis for invalidity – it has no direct effect on the §§ 102, 103
`
`invalidity grounds here, and there remains independent reasons why Implicit’s
`
`swear-behind fails. Second, Implicit argues that public policy supports correction
`
`because it rewards the actual inventors. But public policy supports the principles
`
`of finality, waiver, and judicial estoppel as well. Allowing Implicit to resurrect its
`
`challenged claims by changing inventorship after issuance of the Final Written
`
`Decisions would encourage parties to play a wait-and-see game with swear-
`
`behinds, molding inventorship after the fact to whatever inventive entity fits their
`
`evidence. Such gamesmanship should not be rewarded.
`
`I.
`
`IMPLICIT’S CASELAW DOES NOT SUPPORT REVISITING THE
`FINAL WRITTEN DECISIONS
`
`Sonos’s opening brief demonstrated why § 256 retroactively applies to cure
`
`§102(f) invalidity but does not apply to cure other types of invalidity. Implicit’s
`
`brief fails to cite any authority permitting the type of retroactive application of §
`
`256 Implicit asks for. Instead, Implicit attempts to show that § 256 applies
`
`2
`
`

`

`
`
`retroactively for some situation by comparing it to §§ 254 and 255, which govern
`
`
`
`
`
`other corrections. But the dispute was never whether § 256 applies retroactively in
`
`some situations, but rather whether § 256 applies in Implicit’s situation. Implicit
`
`relies on Southwest Software, Inc. v. Harlequin Inc., 226 F.3d 1280 (Fed. Cir.
`
`2000), and Roche Palo Alto LLC v. Ranbaxy Lab'ys Ltd., 551 F. Supp. 2d 349
`
`(D.N.J. 2008). Neither supports Implicit’s reading of § 256.
`
`A. Roche Does Not Apply to Corrections Beyond § 102(f)
`In Roche, the District of New Jersey considered the application of § 256 to a
`
`nonjoinder situation. The patent in question issued naming only three of the five
`
`actual inventors, notwithstanding the patentee’s efforts to correct the nonjoinder
`
`prior to issuance of the patent. Roche, 551 F.Supp.2d at 351. Despite multiple
`
`attempts by the patentee to correct inventorship, it was not until after institution of
`
`an infringement suit that the USPTO issued a certificate of correction remedying
`
`the nonjoinder. Id. at 352. While it was unclear from the record whether the
`
`USPTO issued the certificate of correction pursuant to § 254 or § 256, the court
`
`held that correction of inventorship to cure invalidity resulting from nonjoinder
`
`(i.e., invalidity predicated on § 102(f)) is entitled to retroactive effect, regardless of
`
`the specific section under which the correction issued. Id. at 358.
`
`This case does not involve non-joinder or misjoinder. Implicit has changed
`
`the inventorship under § 256 as a self-help attempt to make a new swear-behind
`
`3
`
`

`

`
`
`argument to antedate established §§ 102 and 103 prior art. This is not within the
`
`
`
`
`
`scope of § 256 and is not provided for under Roche. Indeed, it makes sense why §
`
`256 applies retroactively to cure invalidity under § 102(f) but not invalidity under
`
`the other provisions. This is because with § 102(f), the correction will completely
`
`remove the basis for invalidity. With other provisions, like §§ 102 or 103,
`
`correction does not remove the basis for invalidity. Even in cases of a swear
`
`behind, the Board will still need to consider the swear behind evidence under the
`
`new inventorship as well as Sonos’s other reasons why the swear-behind fails. In
`
`this way, Roche does not support Implicit’s reading of § 256. See also Heat
`
`Techs., Inc. v. Papierfabrik Aug. Koehler SE, 2019 WL 1915620 (N.D. Ga. Jan. 3,
`
`2019), amended, 2019 WL 1923663 (N.D. Ga. Apr. 18, 2019) (Section 256
`
`“merely states that correcting inventorship will save a patent’s validity for that
`
`reason—i.e., for failing to list all inventors.”).
`
`B. Southwest and SIPCO Do Not Support Implicit’s Reading
`Southwest did not consider § 256 and does not provide authority for
`
`Implicit’s reading of that statute. Instead, Implicit relies on Southwest to illustrate
`
`the prospective operation of § 254, which is not at issue here. Paper 55, 7. In
`
`Southwest, the patent in question issued without material needed for the Best Mode
`
`and Enablement requirements of § 112. Southwest, 226 F.3d at 1297. The Federal
`
`Circuit held that a certificate of correction issued under § 254 is only effective “for
`
`4
`
`

`

`
`
`causes of action arising after [the certificate of correction] was issued.” Id. at
`
`
`
`
`
`1294-96. As noted above, Southwest includes no discussion of § 256 and does not
`
`provide direct support for Implicit’s reading of § 256.
`
`SIPCO is inapposite as well for the reasons discussed in Sonos’s Opening
`
`Brief. Like Southwest, SIPCO’s holding does not support the proposition that
`
`corrections under § 256 have retroactive effect for every possible scenario.
`
`Emerson Elec. Co. v. SIPCO, LLC, IPR2016-00984, Paper 52 at 17-21 (P.T.A.B.
`
`Jan. 24, 2020) (on remand). Rather, SIPCO’s discussion of § 256 was dicta,
`
`merely highlighting the nonretroactivity of § 255 by comparing it to a statue with
`
`some retroactive effect.
`
`II. THE PUBLIC POLICY INTERESTS IDENTIFIED BY IMPLICIT DO
`NOT SUPPORT RETROACTIVE EFFECT ON THESE FINAL
`WRITTEN DECISIONS
`
`A. The Public Interest in Naming Inventors Correctly Does Not
`Outweigh the Public’s Interest in Case Finality and Fairness
`In Patent Owner’s Opening Brief, Implicit argues that retroactive application
`
`of § 256 will “reward actual inventors” and is thus consistent with public policy
`
`rationales. But the Certificates of Correction can be entered without disturbing the
`
`Final Written Decisions, still fulfilling the public policy rationale of § 256.
`
`Further, it is in the public interest to uphold the Board’s carefully considered Final
`
`Written Decisions because this promotes public trust in the judicial system. This is
`
`the reason courts apply the doctrines of judicial estoppel and waiver discussed in
`
`5
`
`

`

`
`
`Sonos’s Opening Brief. See, e.g., New Hampshire v. Maine, 532 U.S. 742, 750-51
`
`
`
`
`
`(2001) (judicial estoppel serves to maintain integrity of and public trust in the
`
`judicial system). For the reasons discussed in Sonos’s Opening Brief, these
`
`doctrines preclude Implicit from using the Certificates of Correction to circumvent
`
`the Final Written Decisions of the Board.
`
`Public Policy Dictates That Implicit’s Request Be Denied
`B.
`Even if the Board had discretion to consider the changed inventorship for the
`
`Final Written Decisions in contravention of § 256, judicial estoppel, waiver, and
`
`Due Process and APA concerns, public policy suggests that the Board refuse this
`
`invitation. Doing so would discourage parties from seeking any type of correction
`
`at all during an IPR, knowing that they can seek correction after the IPR is over
`
`and get another bite at the apple if and only if they lose the first IPR. This would
`
`amount to a severe drain on the Board’s and the parties’ resources and contravenes
`
`settled judicial principals of finality. Lizut v. Department of Army, 717 F.2d 1391,
`
`1396 (Fed.Cir.1983) (“Allowing a party to withhold important issues from the
`
`[agency] and later present them to this court would undermine the [agency’s]
`
`authority.”); Interactive Gift Exp., Inc. v. Compuserve Inc., 256 F.3d 1323, 1346
`
`(Fed. Cir. 2001) (“[A] party’s argument should not be a moving target.”).
`
`C.
`
`Implicit’s Inventorship Correction Was Not Informed by the
`Board’s Findings
`
`6
`
`

`

`
`
`
`
`
`
`
`Implicit relies on Egenera, Inc. v. Cisco Systems, Inc., 972 F.3d 1367 (Fed.
`
`Cir. 2020) to justify its post-decision attempt to negate the Final Written Decisions
`
`by changing inventorship. Paper 55, 11. In particular, Implicit raises Egenera’s
`
`discussion of how the inventorship analysis can be “informed by a tribunal’s view
`
`of the evidence” as justification for its changing positions. Id. at p. 12. But
`
`Implicit cannot demonstrate that its decision to pursue an inventorship change was
`
`“informed” by the Board’s “view of the evidence” regarding inventorship because
`
`inventorship was not at issue before the Board. At issue was whether Implicit’s
`
`evidence corroborated Implicit’s story that Balassanian and Bradley conceived the
`
`invention and communicated it to Carpenter for reduction to practice. The Board
`
`had no occasion to decide whether Carpenter was or was not a proper inventor.
`
`Simply put, there was no indication during the IPR that the original inventorship
`
`advanced by Implicit was incorrect. To the contrary, Implicit advanced the
`
`original inventorship, which was accepted and relied on by the Board and by
`
`Sonos. Only after the Board issued the Final Written Decisions did Implicit seek
`
`to effect a change in inventorship, and did so in direct contradiction to its own
`
`evidence proffered to the Board. For these reasons, Egenera is inapposite.
`
`III. CONCLUSION
`
`For any one or more of the forgoing reasons, the Board should decline to
`
`revisit the Final Written Decisions in view of the Certificates of Correction.
`
`7
`
`

`

`
`
`
`
`
`
`
`Respectfully submitted,
`
`Date: March 1, 2023
`
`
`
`By: /Cole B. Richter/
`
`
`
`Rory P. Shea
`George I. Lee
`Sean M. Sullivan
`Cole B. Richter
`LEE SULLIVAN SHEA & SMITH LLP
`656 West Randolph, Suite 5W
`Chicago, Illinois 60661
`Tel.: (312) 754-9602
`Attorneys for Petitioner, Sonos, Inc.
`
`
`
`
`
`8
`
`

`

`
`
`
`
`
`
`
`CERTIFICATE OF SERVICE
`
`In accordance with 37 CFR §42.6(e)(4), I hereby certify that on March 1,
`
`2023 a true copy of the foregoing BRIEF, was served via electronic mail to the
`
`following counsel at the addresses designated for service by Patent Owner:
`
`Timothy McAnulty
`FINNEGAN, HENDERSON, FARABOW, GARRETT & DUNNER, LLP
`1875 Explorer Street, Suite 800
`Reston, Va 20190-6023
`Timothy.McAnulty@finnegan.com
`Back-up Counsel
`
`Christian Hurt
`THE DAVIS FIRM, PC
`213 N. Fredonia Street, Suite 230
`Longview, Texas 75601
`churt@bdavisfirm.com
`sue@davisfirm.com
`Lead Counsel
`
`
`
`
`
`
`/Cole B. Richter/
`Cole B. Richter (USPTO Reg. No. 65,398)
`LEE SULLIVAN SHEA & SMITH LLP
`656 West Randolph Street, Floor 5W
`Chicago, Illinois 60661
`Tel: (312) 754-9602
`Fax: (312) 754-9603
`richter@ls3ip.com
`
`Date: March 1, 2023
`
`
`
`
`
`
`
`
`
`
`
`9
`
`

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