• Wombat Security Technologies v. Phishme, Inc.Rehearing denied
  PTAB · Jul 20, 2017 · PGR2017-00009 · APJ Jennifer S Bisk · PGR · Rehearing

  The Board denied Wombat’s rehearing request, leaving institution of PGR denied because the petition did not show the patent was eligible for PGR.

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “DISCUSSION The applicable standard for granting a request for rehearing is abuse of discretion. 37 C.F.R. § 42.71(c). The requirements of a request for rehearing are set forth in 37 C.F.R. § 42.71(d), which provides in relevant part: A party dissatisfied with a decision may file a single 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, an opposition, or a reply.” slip op. at 3

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied

    “sufficiently shown that the ’038 patent was eligible for post-grant review. Inst. Dec. 8–13. Specifically, we found deficient Petitioner’s contention that the challenged claims were not entitled to the benefit of the filing date of Application No. 13/785,252 (“the ’252 application”) to which the ’038 patent claims priority as a continuation-in-part. Inst. Dec. 8–13. This finding was based on the following deficiencies of the Petition: (1) the Petition did not discuss the relevant disclosure of the application to which the ’038 patent claims priority—Application No. 13/785,282 (“the ’252 application”)—as originally filed, citing instead to the ’940 patent, which issued from the ’252 application; (2) the Petition did not address the Examiner’s statements in the Notice of Allowability that “[t]he present application is being examined under the pre-AIA first to invent provisions”; and (3) Petitioner did not satisfy its burden to show that a person of ordinary skill in the art would not have understood the inventor to have possession of “providing feedback to the individual confirming that the identified email was a simulated phishing attack” (“the feedback limitation”). Id. For the third deficiency, we found the feedback limitation supported by at least paragraphs 5 and 18 of the ’252 application, which discuss training individuals who receive simulated phishing attacks such that users are better able to recognize and thwart a real phishing attack. Id. at 11–12.” slip op. at 2

  • BurdenDecided for patent owner

    “being recited expressly in the ’252 application it “satisf[ied] its burden to establish that it was more likely than not that the ’038 patent was not entitled to the filing date of the [’252 application].” Reh’g Req. 3. In Blue Calypso, LLC v. Groupon, Inc., however, the Federal Circuit explicitly found that identifying a limitation as not being recited expressly in the specification at issue was not enough to support a finding of lack of written description. 815 F.3d 1331, 1345 (Fed. Cir. 2016). The Federal Circuit explained that it was “troubled by the fact that the Board did not cite any evidence other than the fact that the terms were not present in the specification to support its finding,” concluding this placed “undue weight on the absence of the [exact] terms appearing in the specification.” Id. at 1345–46. Petitioner’s burden, therefore, is not established simply by pointing out that the ’252 application does not explicitly state the feedback limitation.” slip op. at 4

  • Disclosure Requirements (§112) › Written description (Ariad)Not reached

    “being recited expressly in the ’252 application it “satisf[ied] its burden to establish that it was more likely than not that the ’038 patent was not entitled to the filing date of the [’252 application].” Reh’g Req. 3. In Blue Calypso, LLC v. Groupon, Inc., however, the Federal Circuit explicitly found that identifying a limitation as not being recited expressly in the specification at issue was not enough to support a finding of lack of written description. 815 F.3d 1331, 1345 (Fed. Cir. 2016). The Federal Circuit explained that it was “troubled by the fact that the Board did not cite any evidence other than the fact that the terms were not present in the specification to support its finding,” concluding this placed “undue weight on the absence of the [exact] terms appearing in the specification.” Id. at 1345–46. Petitioner’s burden, therefore, is not established simply by pointing out that the ’252 application does not explicitly state the feedback limitation.” slip op. at 4

  § 112 disclosure
  Patents in suitUS 9,398,038

Holdings, summaries, rulings, issues, outcomes, winners and claim constructions shown for a decision were generated by a large language model reading the opinion. They are a guide to the decision, not the decision. Confirm every one against the court's own text before relying on it. Outcomes read from the patent owner’s side. Party names are extracted from the decision and are missing on about 900 short Director denials and scans, which carry the trial number instead.