throbber
Trials@uspto.gov
`571-272-7822
`
`
`
`
`
`
`Paper 24
`Date: October 3, 2014
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`_____________
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`____________
`
`MICROSOFT CORP. and APPLE INC.,
`Petitioner,
`
`v.
`
`VIRNETX INC.,
`Patent Owner.
`____________
`
`Case IPR2014-004041
`
`Patent 7,987,274 B2
`____________
`
`
`Before MICHAEL P. TIERNEY, KARL D. EASTHOM, and STEPHEN C. SIU,
`Administrative Patent Judges.
`
`SIU, Administrative Patent Judge.
`
`
`
`DECISION
`Request for Rehearing
`37 C.F.R. § 42.71(d)
`
`
`
`
`
`1 Case IPR2014-00484 has been joined to Case IPR2014-00404.
`
`

`

`IPR2014-00404
`Patent 7,987,274 B2
`
`I.
`
`BACKGROUND
`
`
`
`
`
`VirnetX, Inc. (“Patent Owner”), in its Request for Rehearing (“Req.” or
`
`“Request”), seeks reversal of the Board’s Decision (“Decision”) to institute an
`
`inter partes review of claims 1–5, 7, 8, 10, 12, 15, and 17 of U.S. Patent 7,987,274
`
`B2 (“the ’274 Patent,” Ex. 1001) and to join IPR2014-00484 with the instant
`
`proceeding. See Paper 22, 1 (“Req. Reh’g.”). For the reasons that follow, the
`
`Board denies the requested relief.
`
`The applicable standard for a request for rehearing is set forth in 37 C.F.R.
`
`§ 42.71(d), which provides in relevant part:
`
`A party dissatisfied with a decision may file a request for rehearing,
`without prior authorization from the Board. The burden of showing a
`decision should be modified lies with the party challenging the
`decision. The request must specifically identify all matters the party
`believes the Board misapprehended or overlooked, and the place
`where each matter was previously addressed in a motion, opposition,
`or a reply.
`
`
`
`II. DISCUSSION
`
`Patent Owner has not shown an abuse of discretion or an overlooked
`
`material point. Patent Owner argues that Apple Inc. (“Petitioner”) “relies on an
`
`expert declaration that makes no mention of Kiuchi or the ’274 patent.” Req.
`
`Reh’g 4–5. However, Petitioner proposes grounds of unpatentability for claims 1–
`
`4, 7, 8, 10, 12, 15, and 17 as anticipated by Kiuchi and includes claim charts
`
`mapping specific citations of Kiuchi to claim limitations recited in the ’274 patent.
`
`See, e.g., ’484 IPR Pet. 17–31. Petitioner provides similar arguments with respect
`
`to Kiuchi in combination with other references. See, e.g., ’484 IPR Pet. 31–39.
`
`Patent Owner does not explain persuasively how we overlooked a point in ’484
`
`IPR Petition that would render institution and joinder deficient.
`
`2
`
`
`

`

`IPR2014-00404
`Patent 7,987,274 B2
`
`
`
`Patent Owner also argues that “the flaws in Apple’s petition render it
`
`
`
`incapable of providing the explanation and particularity required by 35 U.S.C.
`
`§§ 312(a)(3)-(4) and 37 C.F.R. §§ 42.104(b)(4)-(5).” Req. Reh’g 5. Specifically,
`
`Patent Owner argues that “Apple at least fails to explain why Kiuchi’s
`
`‘REQUEST’ message allegedly discloses the ‘access request message’ of claim 1”
`
`and that “none of these issues was addressed in the Board’s Decision instituting
`
`Apple’s petition.” Req. Reh’g. 7–8. Contrary to Patent Owner’s contention, both
`
`Microsoft (’404 IPR) and Apple (’484 IPR) argue that the Kiuchi discloses an
`
`“access request message.” See, e.g., ’404 IPR Pet. 36; ’484 IPR Pet. 27–28.
`
`Patent Owner does not point out any specific differences in these contentions.
`
`As we stated in the Decision, with respect to Kiuchi, “[w]e incorporate our
`
`previous analysis regarding the . . . asserted grounds of unpatentability.” ’484 IPR
`
`Decision 6. In the Decision in the ’404 IPR (incorporated into the Decision of the
`
`’484 IPR), we explained the basis of our conclusion to institute inter partes review
`
`with respect to the “access request message” claim limitation. ’404 IPR Pet. 5–6,
`
`13–15. Thus, we disagree with Patent Owner’s contention that the issue of the
`
`“access request message of claim 1” was supposedly not “addressed in the Board’s
`
`Decision.”
`
`Patent Owner argues that our incorporation of the ’404 IPR Decision in the
`
`’484 IPR Decision is improper because “Apple’s contentions regarding Kiuchi in
`
`IPR2014-00484 are in fact different than the contentions made by Microsoft in
`
`IPR2014-00404.” Req. Reh’g 8–9. Patent Owner does not point out specific
`
`material differences between the contentions made in the ’404 IPR with respect to
`
`contentions made in the ’484 IPR that would preclude the incorporation of the ’404
`
`IPR Decision with that of the ’484 IPR.
`
`3
`
`
`

`

`IPR2014-00404
`Patent 7,987,274 B2
`
`
`
`Patent Owner argues that joinder of the ’484 IPR with the ’404 IPR is
`
`
`
`improper because Patent Owner would need to “address two different expert
`
`declarations [which would] requir[e] significant additional analysis and expense by
`
`[Patent Owner].” Req. Reh’g 11-12. Patent Owner does not point out how
`
`“significant” the additional analysis or expense would be to analyze an expert
`
`declaration or how such “significance” would, in fact, be prohibitive.
`
`
`
`
`
`III. CONCLUSION
`
`Based on the foregoing discussion, Patent Owner’s requested relief for a
`
`reversal of the Decision is denied because Patent Owner has not shown that the
`
`Decision overlooks or misapprehends a material point.
`
`
`
`IV. ORDER
`
`For the reasons given, it is
`
`ORDERED that the Request for Rehearing is denied.
`
`
`
`
`
`
`
`
`
`
`
`4
`
`
`

`

`IPR2014-00404
`Patent 7,987,274 B2
`
`
`PETITIONER:
`
`
`
`
`
`
`W. Karl Renner
`Kevin E. Greene
`FISH & RICHARDSON P.C.
`axf@fr.com
`greene@fr.com
`
`Jeffrey Kushan
`Joseph Micallef
`SIDLEY AUSTIN LLP
`jkushan@sidley.com
`jmicallef@sidley.com
`
`
`PATENT OWNER:
`
`Joseph E. Palys
`Naveen Modi
`PAUL HASTINGS LLP
`josephpalys@paulhastings.com
`naveenmodi@paulhastings.com
`
`Jason E. Stach
`FINNEGAN, HENDERSON, FARABOW, GARRETT & DUNNER, L.L.P.
`jason.stach@finnegan.com
`
`
`5
`
`
`

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