- PNC Bank N.A. v. United Services Automobile AssociationInstitution deniedPTAB · Mar 2, 2022 · IPR2021-01381 · APJ Michael R Zecher · IPR · Institution
The Board denied institution because PNC did not show that Oakes, Medina, or Roach qualified as prior art, so it failed to establish a reasonable likelihood of prevailing on any challenged claim.
RulingsInstitution decision- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“Although USAA takes issue with PNC’s approach to claim construction for purposes of this proceeding, it does not appear that USAA disputes PNC’s position that we should apply the constructions for the claim terms “mobile device,” “portable device,” and “digital camera” that USAA proposed in the district court and, eventually, the district court adopted. Compare Ex. 1028, 15, with Ex. 1054, 20. Because there is no dispute between the parties as to the construction of these three claim terms, we need not construe them for purposes of this Decision. See, e.g., Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 13
- Skill levelSkill level petitioner adoptedDecided for petitioner
“2. Level of Skill in the Art There is sufficient evidence in the current record that enables us to determine the knowledge level of a person of ordinary skill in the art. Relying on the testimony of Dr. Noble, PNC argues the following: [a] person of ordinary skill in the relevant field of art . . . at the relevant time (2006–2017) of the ’681 patent would have had a Bachelor’s degree in computer science, computer engineering, electrical engineering, or equivalent field, and two years of experience in software development and programming in the area of image capturing/scanning technology involving transferring and processing of image data to and at a server. Less work experience may be compensated by a higher level of education, and vice versa. Pet. 10 (citing Ex. 1002 ¶¶ 37, 38). In response, USAA states that, “[f]or the purposes of [its] Preliminary Response only, USAA applies the level of skill in the art proposed by [PNC].” Prelim. Resp. 21. To the extent necessary, and for purposes of this Decision, we adopt PNC’s assessment of the level of skill in the art because it is supported by the testimony of Dr. Noble and it is consistent with the ’681 patent.” slip op. at 17
- Disclosure Requirements (§112) › Written description (Ariad)Written description adequateEntitled to earlier dateDecided for patent owner
“conclusion PNC asks us to draw from them. In particular, PNC appears to contend that we should find that the ’247 application does not provide sufficient written description support for the device limitations merely because the scope of the independent claims encompass a configuration that is not described expressly in that document. See Pet. 16, 18–19. But this reflects a misunderstanding of the law—a claim can be broader than the embodiments disclosed. See, e.g., Rexnord, 274 F.3d at 1344 (“[A]n applicant is not required to describe in the specification every conceivable and possible future embodiment of his invention.”); see also Ethicon, 93 F.3d 1582 n.7 (noting that a claim may be “literally infringed by undisclosed embodiments” and yet sufficiently supported); In re Smythe, 480 F.2d 1376, 1382 (C.C.P.A. 1973) (“We cannot agree with the broad proposition . . . that in every case where the description of the invention in the specification is narrower than that in the claim there has been a failure to fulfill the [written] description requirement in section 112.”). We acknowledge that there are situations where a claim’s breadth results in a lack of written description support, but PNC fails to show that such a situation is present here. In its argument, PNC primarily relies on Reckitt, but this case is unavailing. See Pet. 13–15, 19, 32 (citing Reckitt Benckiser LLC v. Ansell Healthcare Prods. LLC, IPR2017-00063, Paper 38 (PTAB Jan. 30, 2018)). First, Reckitt is a non-precedential Board decision that is not binding on this panel.5 Second, and perhaps more importantly, the case is readily distinguishable on its facts. See Prelim. Resp. 30–31 (distinguishing Reckitt from the circumstances presented here). In particular, in Reckitt, the Board panel found that claims lacking a pre-vulcanization requirement lacked written description support in the priority document, noting that “[p]re-vulcanization [was] not some ancillary feature but rather the very heart of the invention.” Reckitt, IPR2017-00063, Paper 38 at 12, 14–15 (emphasis added). However, “[PNC] identifies nothing whatsoever in the ’247 application suggesting that it is important— much less the ‘very heart of the invention’—that the described image capture device be in a housing entirely separate from the described general purpose computer.” Prelim. Resp. 31. In fact, the Petition identifies (and we perceive) no reason why the relative location of the general purpose computer (i.e., the portable/mobile device) and the image capture device” slip op. at 21
- Expert testimonyPetitioner expert discountedDecided for patent owner
“We have considered Dr. Noble’s supporting testimony, but it suffers from the same deficiencies as PNC’s arguments. See Ex. 1002 ¶¶ 42–58. Moreover, in our view, Dr. Noble does not explain sufficiently his conclusions regarding what a person of ordinary skill would have understood the inventor of the ’247 application to possess (or not possess) and, accordingly, we assign little weight to his testimony on this particular issue. E.g., id. ¶¶ 46, 54–57; see TQ Delta, LLC v. CISCO Sys., Inc., 942 F.3d 1352, 1358 (Fed. Cir. 2019) (“Conclusory expert testimony does not qualify as substantial evidence.”).” slip op. at 25
Claim construction§ 102 anticipation§ 112 disclosurecites PhillipsPatents in suitUS 10,013,681 - Wombat Security Technologies v. Phishme, Inc.Rehearing deniedPTAB · 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 disclosurePatents 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.