throbber
Trials@uspto.gov
`571-272-7822
`
`
`Paper 9
`Entered: August 8, 2019
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`APPLE INC.,
`Petitioner,
`
`v.
`
`MPH TECHNOLOGIES OY,
`Patent Owner.
`____________
`
`Case IPR2019-00819 (Patent 7,620,810 B2)
`Case IPR2019-00820 (Patent 7,937,581 B2)1
`____________
`
`
`Before KAMRAN JIVANI, JOHN D. HAMANN, and
`STACY B. MARGOLIES, Administrative Patent Judges.
`
`HAMANN, Administrative Patent Judge.
`
`
`
`ORDER
`Conduct of the Proceeding
`37 C.F.R. §§ 42.5(a); 42.108(c)
`
`
`
`
`
`
`
`1 This Order addresses an issue pertaining to the listed cases. We exercise
`our discretion to issue one Order to be filed in each case. The parties are not
`authorized to use this style heading for any subsequent papers.
`
`

`

`IPR2019-00819 (Patent 7,620,810 B2)
`IPR2019-00820 (Patent 7,937,581 B2)
`
`On July 22, 2019, Petitioner sent an email requesting a call to seek
`
`authorization to file a Reply to Patent Owner’s Preliminary Response. On
`July 31, 2019, we held the call with Judges Jivani, Hamann, and Margolies
`and respective counsel for the parties. During the call, the parties presented
`arguments as to Petitioner’s request. We were unpersuaded by Petitioner’s
`arguments, and we denied Petitioner’s request on the call. This Order
`memorializes our decision, and provides our reasoning.
`
`Petitioner sought a Reply to address Patent Owner’s alleged
`mischaracterizations of the asserted art and prosecution history made in the
`Preliminary Response in the context of § 325(d). Petitioner argued that it
`could not have anticipated these alleged mischaracterizations. Petitioner
`argued, for example, that it could not have anticipated that Patent Owner
`would characterize Murakawa (which was not before the Office) as being
`duplicative of Ahonen (which was before the Office). Patent Owner argued
`that Petitioner could have anticipated Patent Owner’s arguments, and that
`Petitioner failed to show good cause to warrant a Reply.
`
`In requesting a Reply to a Preliminary Response, a Petitioner must
`show good cause. 37 C.F.R. § 42.108(c). We found that Petitioner failed to
`show good cause. In particular, Petitioner failed to show that it could not
`have anticipated Patent Owner’s arguments. For example, we find it
`foreseeable that Patent Owner would argue that new art (Murakawa) is
`duplicative of art (Ahonen) that was before the Office during prosecution,
`especially here where Petitioner asserts that Ishiyama (which also was
`before the Office), combined with Murakawa, renders challenged claims
`unpatentable. Furthermore, at this stage of the proceeding, we are able to
`
`
`
`2
`
`

`

`IPR2019-00819 (Patent 7,620,810 B2)
`IPR2019-00820 (Patent 7,937,581 B2)
`
`determine whether the parties have properly characterized the asserted art
`and prosecution history without additional briefing.
`
`Accordingly, we deny Petitioner’s request.
`
`It is hereby ORDERED that Petitioner’s request for authorization to
`file a Reply to Patent Owner’s Preliminary Response is denied.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`3
`
`

`

`IPR2019-00819 (Patent 7,620,810 B2)
`IPR2019-00820 (Patent 7,937,581 B2)
`
`PETITIONER:
`
`Michael D. Specht
`Daniel S. Block
`Timothy L. Tang
`STERNE, KESSLER, GOLDSTEIN & FOX
`mspecht-ptab@sternekessler.com
`dblock-ptab@sternekessler.com
`ttang-ptab@sternekessler.com
`
`
`PATENT OWNER:
`
`James T. Carmichael
`CARMICHAEL IP LAW, PLLC
`jim@carmichaelip.com
`
`Christopher J. Lee
`Richard B. Megley
`Brian E. Haan
`Ashley E. LaValley
`LEE SHEIKH MEGLEY & HAAN LLC
`clee@leesheikh.com
`rmegley@leesheikh.com
`bhaan@leesheikh.com
`alavalley@leesheikh.com
`
`Kenneth J. Weatherwax
`Patrick Maloney
`Jason C. Linger
`LOWENSTEIN & WEATHERWAX LLP
`weatherwax@lowensteinweatherwax.com
`maloney@lowensteinweatherwax.com
`linger@lowensteinweatherwax.com
`
`
`
`4
`
`

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