throbber
From:
`To:
`Cc:
`
`Subject:
`Date:
`
`Jeremy Monaldo
`Director_PTABDecision_Review
`IPR39843-0128IP1; rhwang@skiermontderby.com; tmartin@skiermontderby.com; pgraves@gravesshaw.com;
`gshaw@gravesshaw.com; Andy Ehmke IPR; Clint Wilkins IPR
`IPR2022-01004 (Patent 9,614,943 B1) - Request for Director Review
`Wednesday, January 3, 2024 8:29:57 PM
`
`CAUTION: This email has originated from a source outside of USPTO. PLEASE CONSIDER THE SOURCE before
`responding, clicking on links, or opening attachments.
`
`Honorable Director,
`
`Petitioner in IPR2022-01004 respectfully requests Director Review of the Final Written Decision
`(Paper 40) issued by the Board on December 4, 2023. Concurrently herewith, Petitioner has filed a
`Request for Rehearing by the Director in the Patent Trial and Appeal Case Tracking System (P-
`TACTS). This request for Director Review involves issues related to the issues identified in the
`Director Review requested in IPR2022-01005 on January 2, 2024.
`
`Petitioner’s request seeks review of the Board’s decision that a POSITA would not have combined
`the Raleigh and Byrne references because Petitioner failed to show a reasonable expectation of
`success in implementing Raleigh’s “remote unit” as a telephone. In particular,
`a. The Board erred because the record includes clear evidence that radio telephones were
`well-known by the 1999 filing date of the challenged patent, the secondary reference
`(Byrne) in the combination describes a telephone, and the primary reference (Raleigh)
`describes its technology as being applicable to “remote units.”
`b. The Board’s decision also applied the incorrect standard for reasonable expectation of
`success by finding that the prior art did not explicitly describe the proposed modification
`(“[t]he cited portions of Raleigh and Byrne do not describe adding Raleigh’s signal
`processing system to a radio telephone” (FWD, 84)), rather than assessing whether a
`skilled artisan would have reasonably expected success in implementing the “remote
`unit” as a telephone.
`c. The Board’s decision further failed to consider the challenged patent’s sparse disclosure
`of how to implement the claimed features in a telephone.
`d. Finally, the Board misapprehended the combination by only assessing whether it would
`have been obvious to implement Raleigh’s signal processing in a telephone, where the
`Petition clearly proposed modification of Raleigh’s “remote unit,” not a telephone, and
`the Board acknowledged the same without addressing the argument (“combination can
`be read to add only Byrne’s cordless circuitry to Raleigh’s remote unit,” FWD, 86).
`e. These failings reflect an (a) abuse of discretion, (b) important issue of law or policy, (c)
`erroneous findings of material fact, and/or (d) erroneous conclusions of law for which the
`Board would benefit from Director Review. Indeed, the Board would benefit from
`Director guidance on the correct standard for assessing reasonable expectation of
`success, the proper role a patent’s disclosure plays in evaluating obviousness, and the
`
`IPR2022-01004
`Ex. 3100
`
`

`

`need to address all arguments presented in a Petition.
`
`
`For these reasons, Petitioner respectfully requests Director Review of the Board’s Final Written
`Decision.
`
`Respectfully Submitted,
`Jeremy J. Monaldo
`
`
`Jeremy Monaldo :: Principal :: Fish & Richardson P.C.
`+1 (202) 626-7717 direct :: Monaldo@fr.com
`fr.com :: Bio :: LinkedIn :: Twitter
`
`
`************************************************************************************
`****************************************
`This email message is for the sole use of the intended recipient(s) and may contain
`confidential and privileged information. Any unauthorized use or disclosure is
`prohibited. If you are not the intended recipient, please contact the sender by
`reply email and destroy all copies of the original message.
`************************************************************************************
`****************************************
`
`

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