- PTAB · Nov 22, 2024 · PGR2024-00034 · APJ Patrick R Scanlon · PGR · Institution
Instituted PGR on claims 1–19 and all asserted grounds after finding at least one claim more likely than not unpatentable.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“We have authority to determine whether to institute a post-grant review. See 35 U.S.C. § 324 (2018); 37 C.F.R. § 42.4(a) (2022). To institute a post-grant review, we must determine that “the information presented in the petition . . . would demonstrate that it is more likely than not that at least 1 of the claims challenged in the petition is unpatentable.” 35 U.S.C. § 324(a). For the reasons set forth below, we determine that the information presented shows that it is more likely than not that Petitioner would prevail in establishing unpatentability of at least one challenged claim. Accordingly, we institute a post-grant review of the challenged claims on the grounds set forth in the Petition.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“We note that the identification of a Ph.D. as an example of “more formal education” creates a vast range of education relative to a bachelor’s degree. Thus, we treat the identification of a Ph.D. just as it is—an example—and not a requirement. In this case, “more formal education” can be satisfied by a level of education less than a Ph.D (but greater than a bachelor’s degree). Based on our review of the record before us, we determine that Petitioner’s stated level of ordinary skill in the art is reasonable because it appears consistent with the evidence of record, definition, limited as discussed above, for the purposes of this Decision.” slip op. at 9
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“On the present record, we do not discern a need to construe explicitly any claim language because doing so would have no effect on our analyses below of Petitioner’s asserted grounds and will not assist in resolving the present controversy between the parties. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those 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 10
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundInstituted
“would have understood Unger’s disclosure to “suggest the use of a torsion spring to facilitate attachment and detachment, because torsion springs are designed to impart this functionality.” Id. (citing Ex. 1002 ¶ 118). Petitioner also asserts that one of ordinary skill in the art would have “understood that there were a limited number of ways to impart the referenced resilient or flexible ‘manipulation,’” and “would have been motivated to look to various known solutions to impart the suggested functionality, including the torsional spring mechanism of Smith that is used in a similar hearing protection device application for a similar purpose as Unger’s mounting arms (to apply a clamping force).” Id. at 32 (citing Ex. 1002 ¶¶ 120–121).” slip op. at 17
Claim construction§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 11,736,855 - PTAB · Nov 14, 2024 · PGR2024-00026 · APJ Hyun J Jung · PGR · Institution
Instituted PGR on claims 1–7 and all grounds because Petitioner showed it was more likely than not that at least one challenged claim lacks written-description support.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“At this stage, Petitioner’s arguments, cited portions of the Specification, and supporting testimonial evidence demonstrate that it is more likely than not that claims 1–7 are unpatentable.” slip op. at 20
- Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateDecided for petitioner
“patent describes that “angular position transducer 78 is placed on top of swing leg pivot shaft 24” and that “pivot shaft 24 is rotationally fixed to the connector plate and duplicates the angular movements of swing leg 20 about the pivot shaft.” Ex. 1001, 12:15–16, 12:20–22, Figs. 5, 7. The ’723 patent also describes that “[a]ngular position transducer 78 is mounted inside . . . protective can 90 . . . which is bolted to hinge bracket 28 via an upright holding arm 92” and that “trigger pin 94 projects upwardly from the top surface of pivot shaft 24 and cooperates with angular position transducer 78 to generate an angular position signal.” Id. at 12:28–33, Fig. 5. These descriptions expressly convey that angular position transducer 78 is on pivot shaft 24 and mounted inside protective can 90 that is bolted to hinge bracket 28. Id. at 12:15–16, 12:20–22, 12:28–30, Figs. 5, 7; see also Prelim. Resp. 17 (describing the same embodiment shown in Figs. 5 and 7). According to Petitioner, the ’723 patent describes the pivot shaft as part of the hinge bracket, not the modular frame or swing leg. Pet. 109–110 (citing Ex. 1001, 7:42–46, 12:17–22). On the preliminary record, we agree because the cited portions of the Specification describe that a “hinge bracket is interposed between each swing leg and an associated surface of the bolsters and includes a fixed, upright pivot shaft that pivotally engages the swing leg for pivotal movements” and “pivot shaft 24 is rotationally fixed to the connector plate.” Ex. 1001, 7:42–45, 12:20–21. We also agree that “even if one were to find that the hinge bracket is part of either the modular frame or swing leg (contrary to the claims and specification treating these all as separate components), the specification would only provide written description for one of the claimed alternatives.” Pet. 110 (citing Ex. 1002 ¶ 199).” slip op. at 19
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“At this preliminary stage, we determine that express claim interpretation is not necessary to determine whether it is more likely than not that at least one of the claims challenged in the petition is unpatentable. Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those 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 16
- PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsDecided for petitioner
“We will also not use our discretion under § 325(d) to deny the Petition based on arguments previously presented in IPR2021-00135, because Petitioner relies on a Board determination regarding claim 8 from IPR2021- 00136, not arguments previously made for claim 1 in IPR2021-00135. Pet. 111–115, 119; Prelim. Resp. 8–9; Prelim. Sur-reply 5. Furthermore, we determined the effective filing date of claim 8 of the ’571 patent without deciding, that other challenged claims, such as claim 1, were entitled to their earliest possible effective filing date. See Godberson-Smith, Paper 61 at 11, 12.” slip op. at 12
Claim construction§ 112 disclosureDiscretionary denialcites Phillips · KSR · GrahamPatents in suitUS 11,772,723 - Bj’S Wholesale Club Holdings, Inc. v. Walmart Apollo, LLCAll claims unpatentablePTAB · Apr 10, 2024 · IPR2022-01564 · APJ Patrick R Scanlon · IPR · Final written decision
Claims 1–14 are unpatentable as anticipated by Keith; the Board did not reach the alternative obviousness ground over Hanson and Keith.
RulingsFinal written decision- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“claims of the later-filed application must be supported by the written description in the parent ‘in sufficient detail that one skilled in the art can clearly conclude that the inventor invented the claimed invention as of the filing date sought.’” Anascape, Ltd. v. Nintendo of Am. Inc., 601 F.3d 1333, 1335 (Fed. Cir. 2010) (quoting Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997)). “[T]he hallmark of written description is disclosure,” and the test “is whether the disclosure of the application relied upon reasonably conveys to those skilled in the art that the inventor had possession of the claimed subject matter as of the filing date” of that application. Ariad Pharms., Inc. v. Eli Lilly and Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc) (citing Vas-Cath Inc. v. Mahurkar, 935 F.2d 1555, 1562–63 (Fed. Cir. 1991)). “[T]he test requires an objective inquiry into the four corners of the specification from the perspective of a person of ordinary skill in the art.” Id. But, “[i]t is not sufficient for purposes of the written description requirement of [35 U.S.C.] § 112 that the disclosure, when combined with the knowledge in the art, would lead one to speculate as to modifications that the inventor might have envisioned, but failed to disclose.” Lockwood, 107 F.3d at 1572.” slip op. at 33
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“A claim is anticipated only if each and every element as set forth in the claim is found, either expressly or inherently described, in a single prior art reference.” Verdegaal Bros. Inc., v. Union Oil Co. of Cal., 814 F.2d 628, 631 (Fed. Cir. 1987). Moreover, “[b]ecause the hallmark of anticipation is prior invention, the prior art reference—in order to anticipate under 35 U.S.C. § 102—must not only disclose all elements of the claim within the four corners of the document, but must also disclose those elements ‘arranged as in the claim.’” Net MoneyIN, Inc. v. VeriSign, Inc., 545 F.3d 1359, 1369 (Fed. Cir. 2008). Whether a reference anticipates is assessed from the perspective of an ordinarily skilled artisan. See Dayco Prods., Inc. v. Total Containment, Inc., 329 F.3d 1358, 1368 (Fed. Cir. 2003) (“‘[T]he dispositive question regarding anticipation [i]s whether one skilled in the art would reasonably understand or infer from the [prior art reference’s] teaching’ that every claim element was disclosed in that single reference.”). slip op. at 13
- BurdenFwd all claims unpatentableDecided for petitioner
“preponderance of the evidence that the claims are unpatentable. 35 U.S.C. § 316(e) (2018); 37 C.F.R. § 42.1(d) (2022). “In an IPR, the petitioner has the burden from the onset to show with particularity why the patent it challenges is unpatentable.” Harmonic Inc. v. Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed. Cir. 2016) (citing 35 U.S.C. § 312(a)(3) (2012) (requiring inter partes review petitions to identify “with particularity . . . the evidence that supports the grounds for the challenge to each claim”)). This burden of persuasion never shifts to the patent owner. See Dynamic Drinkware, LLC v. Nat’l Graphics, Inc., 800 F.3d 1375, 1378 (Fed. Cir. 2015) (discussing the burden of proof in inter partes review).” slip op. at 12
Patent outcomesUS 10,803,435 unpatentable§ 102 anticipation§ 112 disclosurecites KSR · GrahamPatents in suitUS 10,803,435 - Ironsource Ltd. v. Digital Turbine Inc.All claims unpatentablePTAB · Mar 12, 2024 · PGR2022-00053 · APJ Iftikhar Ahmed · PGR · Final written decision
Claims 1–22 are unpatentable under collateral estoppel; revised substitute claims 23–37 are allowed because Petitioner did not prove them unpatentable.
RulingsFinal written decision- BurdenFwd all claims unpatentableDecided for petitioner
“The party seeking to invoke collateral estoppel must show: (1) the issue is identical to one decided in the first action; (2) the issue was actually litigated in the first action; (3) resolution of the issue was essential to a final judgment in the first action; and (4) [the party against who collateral estoppel is being asserted] had a full and fair opportunity to litigate the issue in the first action. Google, 54 F.4th at 1381 (quoting In re Freeman, 30 F.3d 1459, 1465 (Fed. Cir. 1994)). Collateral estoppel may also operate to bar re-litigation of common issues in actions involving different but related patents. Mycogen Plant Science, Inc. v. Monsanto Co., 252 F.3d 1306, 1310 (Fed. Cir. 2001) (citing Amgen, Inc. v. Genetics Inst., Inc., 98 F.3d 1328, 1329–32 (Fed. Cir. 1996); Interconnect Planning Corp. v. Feil, 774 F.2d 1132, 1136 (Fed. Cir. 1985)). We are persuaded that each of the four Google requirements is satisfied and, accordingly, agree with Petitioner that the challenged claims of the ’256 patent are unpatentable in light of our Final Written Decision in PGR2021-00096.” slip op. at 13
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 not directed to exceptionNot shown unpatentable
“specific requirements of the claims.” McRO, Inc. v. Bandai Namco Games America Inc., 837 F.3d 1299, 1313 (Fed. Cir. 2016) (quoting In re TLI Commc’ns LLC Patent Litig., 823 F.3d 607, 611 (Fed. Cir. 2016)). But “failing to account for the specific requirements of the claims” is what Petitioner’s analysis of the claim limitations appears to do. Petitioner’s argument that “the focus of the claims” is captured by a single claim element (f3) not only ignores that that limitation recites performing two specific software tasks simultaneously—which we are not persuaded is an abstract idea—but also asks us to disregard multiple technical aspects recited in the claims, such as identifying a link, determining whether an installation client is available on the device, invoking the installation client, and redirecting to the device an app store. See, e.g., Ex. 1001, 21:12–41; Revised MTA 24–25. That is, under Step 2A of the Guidance, we are neither persuaded that limitation f3, which Petitioner points us to, recites an abstract idea (Prong 1), nor that the other limitations recited in the independent claims fail to integrate the alleged abstract idea into a practical application (Prong 2). Petitioner characterizes the claims as directed to multitasking, which Petitioner describes as an example applied to improve a user experience, i.e., as related to organizing human activity. Pet. 29. Although the Guidance recognizes certain methods of organizing human activity, including certain activity between a person and a computer, as constituting a patent-ineligible abstract idea, we are not persuaded that the claims here fall within the scope of such activity. See Guidance, 84 Fed. Reg. at 52 (listing fundamental economic principles or practices, commercial or legal interactions, and managing personal behavior or relationships as organizing human activity). The claimed invention may result in multitasking on the device, but the background instead of directing the user to an app store, thereby maintaining user experience with the foreground application, and do not recite an abstract idea. And although that process does result in improving user experience, the claims recite more than that mere result; they recite specific steps—invoking, without exiting the foreground software application, the installation client for downloading and installing applications on the device to run in the background—that accomplish the desired result. See Finjan, Inc. v. Blue Coat Sys., Inc., 879 F.3d 1299, 1305–06 (Fed. Cir. 2018) (finding a method that employs a new kind of file in a computer security system directed to a non-abstract improvement in computer functionality, rather than the abstract idea of computer security writ large). Petitioner thus fails to establish sufficiently that the claims are directed patent ineligible subject matter under Step 2A of the Guidance.” slip op. at 52
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable
“When the application package 172 has been received by the client system 130, the App Manager 180 may extract or retrieve a set of requested permissions 174 from the application package 172, and present a request to the user for asking for approval to perform operations corresponding to the requested permissions, e.g., opening files, accessing contact information, accessing a camera on the client device 130, and so on. . . . In particular embodiments, when the requested permissions 174 have been requested, and a response specifying a set of accepted permissions 176 has been received from the user, the set of accepted permissions 176 may be compared to the set of requested permissions 174. If the sets are the same, then the installation process may continue, and the App Manager 180 may invoke an installer 182 to install the application package 172. Ex. 1003, 8:67–9:22 (emphasis added). That is, the set of permissions to be checked are obtained by the App Manager once the download of the application package to be installed is initiated. See id. at 8:59–61 (“when the download is initiated by a request sent from the client system 130 to the server 162, the server 162 may send the requested object, e.g., the download page 168 or the application package 172, back to the client system 130”). And these permissions relate to operations that the installed applications may perform, e.g., opening files, accessing contact information, accessing a camera on the client device. Id. at 9:6–7. These permissions may also indirectly determine whether the installation client can install that app. See id. at 9:33–38. There is no suggestion in Pasha, however, that these permissions have anything to do with the host application, i.e., the second software application. said second software application is eligible to use capabilities of the installation client.” RMTA 25; see also Ex. 1001, 15:11–14 (“The installation client, upon receiving an instant install link, checks the eligibility of the caller and if identified as eligible continues the process of downloading the app.”). Pasha does not teach or suggest checking eligibility of its host application in any way or at any point. Moreover, as Patent Owner points out, Pasha’s App Manager performs the eligibility check after it downloads the app package, further supporting that Pasha’s eligibility check has nothing to do with the host application.9 Dr. Almeroth testifies that “Pasha discloses the App Manager 180 confirming that it has obtained the required permissions, which, in [his] opinion, a [person of ordinary skill in the art] would understand may include inter alia that the ‘second software application’ (e.g., the host application invoking the app manager) is eligible to use its capabilities.” Ex. 1035 ¶ 68. Dr. Almeroth fails to cite any supporting evidence or provide any technical reasoning to support his statement. Id. Because we find no basis in the record for Dr. Almeroth’s conclusion, we give little weight to this testimony.” slip op. at 40
- Expert testimonyPetitioner expert discountedDecided for patent owner
“Dr. Almeroth testifies that “Pasha discloses the App Manager 180 confirming that it has obtained the required permissions, which, in [his] opinion, a [person of ordinary skill in the art] would understand may include inter alia that the ‘second software application’ (e.g., the host application invoking the app manager) is eligible to use its capabilities.” Ex. 1035 ¶ 68. Dr. Almeroth fails to cite any supporting evidence or provide any technical reasoning to support his statement. Id. Because we find no basis in the record for Dr. Almeroth’s conclusion, we give little weight to this testimony. 9 During oral argument, Petitioner pointed us to disclosure in Pasha that teaches that the permission dialog may be displayed to the user at different points in the download process. Tr. 47:24–48:8 (citing Ex. 1003, 22:21–42). As Patent Owner pointed out, this disclosure was not relied up on by Petitioner in its papers and is new evidence. Id. at 51:19–22; Paper 46, 4. Petitioner’s argument based on this new evidence is therefore forfeited. But even if we were to consider the cited disclosure from Pasha, it still only suggests that permissions need to come from the server after the download process has been initiated, and are therefore, unrelated to the host application. See Ex. 1003, 22:46–49 (“the requested permissions may be downloaded prior to downloading the application or may be extracted from the application package”). 24, 2022) (precedential) (“Expert testimony that does not disclose the underlying facts or data on which the opinion is based is entitled to little or no weight.”) (quoting 37 C.F.R. § 42.65(a)). As the Board explained in Xerox, such expert testimony “is particularly problematic in cases where, like here, expert testimony is offered not simply to provide a motivation to combine prior-art teachings, but rather to supply a limitation missing from the prior art.” Id. (citing Arendi S.A.R.L. v. Apple, Inc., 832 F.3d 1355, 1361–62 (Fed. Cir. 2016)).” slip op. at 41
Patent outcomesUS 11,157,256 unpatentableClaim construction§ 101 eligibility§ 103 obviousnesscites Alice · Berkheimer · Enfish · PhillipsPatents in suitUS 11,157,256 - Apple Inc. v. Rfcyber Corp.All claims unpatentablePTAB · Jan 19, 2024 · IPR2022-01256 · APJ Kevin W Cherry · IPR · Final written decision
Claims 1–11 are unpatentable as obvious over Buhot, GPC, and Zhu.
RulingsFinal written decision- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“earlier applications, in particular Application No. 11/534,653 (“the ’653 application”), which issued as U.S. Patent No. 8,118,218 B2 (“the ’218 patent”). “‘It is elementary patent law that a patent application is entitled to the benefit of the filing date of an earlier filed application only if the disclosure of the earlier application provides support for the claims of the later application, as required by 35 U.S.C. § 112.’” PowerOasis, Inc. v. T- Mobile USA, Inc., 522 F.3d 1299, 1306 (Fed. Cir. 2008). The test for determining compliance with the written description requirement under § 112(a) is whether the original disclosure of the earlier-filed application reasonably would have conveyed to one with ordinary skill in the art that the inventor had possession of the claimed subject matter at the time of the earlier-filed application. Ariad Pharm., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc). It is well settled that “[e]ntitlement to a filing date does not extend to subject matter which is not disclosed but would be obvious over what is expressly disclosed.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1571−72 (Fed. Cir. 1997). “It is not sufficient for purposes of the written description requirement of § 112 that the disclosure, when combined with the knowledge in the art, would lead one to speculate as to modifications that the inventor might have envisioned, but failed to disclose.” Id. We agree with Petitioner there does not appear to be support for limitation [1(j)] in the ’653 application. We find that the disclosure of the ’653 application—limited to general teachings of a smart card, an operating system, and a smart card manager—is insufficient to show possession of limitation [1(j)]. See Ex. 2001 (’218 patent), 4:47–56. As we explained above, “[e]ntitlement to a filing date does not extend to subject matter which is not disclosed but would be obvious over what is expressly disclosed.” Lockwood, 107 F.3d at 1571−72. The ’653 Application contains no disclosure of replacing applications, even if the disclosure might render such replacing obvious, it is not sufficient to show the possession required to establish entitlement to a priority date. Accordingly, we agree with Petitioner that the challenged claims of the ’724 patent are entitled to a priority date no earlier than March 4, 2012.” slip op. at 7
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Relying on the declaration testimony of Mr. Smith, Petitioner contends that an ordinarily skilled artisan for the ’724 patent “would have had at least a bachelor’s degree in computer engineering, computer science, electrical engineering, or a related field, with at least one year of experience in the field of mobile payment technology. Additional pertinent education might substitute for the requisite experience and vice versa.” Pet. 6–7 (citing Ex. 1007 (Smith Decl.) ¶¶ 34–35). Patent Owner states that “[t]he parties agree on the level of skill in the art.” PO Resp. 11. Accordingly, we adopt Petitioner’s articulation of the level of ordinary skill in the art, which is consistent with the ’724 patent and the asserted prior art, and we apply it in our obviousness evaluations below. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art, itself, can reflect appropriate level of ordinary skill in art).” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for petitioner
“Petitioner contends that it applies “the plain and ordinary meaning as understood by a [person of ordinary skill in the art] for all terms not expressly construed below,” and indicates that in parallel District Court litigation, the parties agreed to claim construction for the term “emulator device” to mean “hardware device, alone or containing software, that pretends to be another particular device or program that other components expect to interact with.” Pet. 8. Petitioner proposes that the term “application” should be construed to mean “‘software program suitable for being executed on a portable device,’” but that the “distinction between the parties’ respective proposals need not be resolved for this proceeding.” Id. at 8–9. Petitioner finally contends that the phrase “a portion of or in entirety” in each independent claim means “in its entirety or partially,” but not both. Id. at 9. Patent Owner submits that “[t]he parties agree that the Board should construe ‘emulator device’ as ‘hardware device, alone or containing software, that pretends to be another particular device or program that other components expect to interact with.’” PO Resp. 11. Patent Owner “does not believe that any other terms require construction to resolve the issues presented in this proceeding.” Id. We apply the agreed upon constructions above, but otherwise find that no express constructions are necessary for this decision.” slip op. at 12
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“We agree with Petitioner that, even if the applications were stored in “generic memory” as Patent Owner contends, Zhu provides adequate security and would not undermine Petitioner’s motivation to combine. See Intel, 61 F.4th at 1380 (“It’s not necessary to show that a combination is the best option, only that it be a suitable option.”). Indeed, Zhu addresses the problem Patent Owner contends it would cause in the combination.3 As Zhu 3 Patent Owner argues that Petitioner should be precluded from discussing Zhu’s encryption embodiment because it was not raised in the Petition. See Sur-Reply 6–7. We disagree. The claims do not recite anything about how the data should be stored. Thus, it is not surprising that the Petition did not address it. Patent Owner raised the teaching away argument regarding the security of the data. See PO Resp. 12–16. Petitioner relies on the exact same mapping, same motivation, and same arguments why Zhu accounted for certain limitations. See Reply 4–11. Petitioner’s Reply merely explained that Zhu did address the problem Patent Owner contended would “teach away” from the combination. Indeed, Patent Owner was aware of Zhu’s teachings and addressed them in their Patent Owner Response. The Federal recognizes, “[l]oading one of the smart card applications already resident on the smart card to another memory location on the mobile device can provide sufficient memory for the selected smart card application, but can also create a security problem.” Ex. 1006 (Zhu), 3:25–34. To address this problem, Zhu proposes encrypting these applications in generic memory which “reduces the possibility of unauthorized access to the information.” Id. at 3:59–61, 8:30–55, 9:28–33; Ex. 1033 (Smith Supp. Decl.) ¶¶ 5–6. Although acknowledging this disclosure, Patent Owner’s expert, Dr. Weaver, testifies that Zhu’s encryption is inadequate and that encryption would have certain drawbacks. See Ex. 2002 (Weaver Decl.) ¶ 69. We find this testimony, which directly contradicts the teachings of Zhu that encryption is an adequate solution, lacks sufficient support to be entitled to much weight. Dr. Weaver provides no citations to support his contention that a person of ordinary skill at the time of the invention would find encryption so inadequate or problematic as he now contends. Moreover, we find that Dr. Weaver’s testimony on cross examination provides an additional, independent basis to give this testimony little weight. On cross examination, Dr. Weaver contended that there was nothing uniquely inadequate about the particular encryption scheme disclosed in Zhu, but rather that his “opinion was more general, that encryption schemes known in the 2012 time frame were all breakable with computing power and time,” and thus, inadequate Circuit has explained that “the petitioner in an inter partes review proceeding may introduce new evidence after the petition stage if the evidence is a legitimate reply to evidence introduced by the patent owner.” Anacor Pharm., Inc. v. Iancu, 889 F.3d 1372, 1380–81 (Fed. Cir. 2018). That is the case here, so we find that Petitioner’s arguments and evidence regarding Zhu’s encryption are proper. for storing payment applications in a mobile device’s general memory. Ex. 1027 (Weaver Tr.), 26:11–23; see also id. at 23:3–8 (“[D]oes encryption ever provide a sufficiently high security to permit storing payment application on a mobile device’s general memory? A. No”); 24:15–25:23 (testifying all publicly known encryption schemes in 2012 were breakable). However, when confronted with the fact that the ’724 patent discloses storing payment application on general baseband memory using an encryption method that was breakable, id. at 26:24–29:7, Dr. Weaver testified that this encryption method was sufficient to allow storing payment applications in general baseband memory even though it was “not perfectly secure,” id. at 29:8–14. Dr. Weaver provides no explanation or rationale why the encryption method in the ’724 patent, which he admits suffers from the same drawbacks he identified with respect to Zhu, is sufficient, but other encryption methods would not be sufficient. In its Sur-reply, Patent Owner attempts to rehabilitate Dr. Weaver’s testimony with justifications and qualifications not found in his original testimony. Sur-Reply 7–8. Yet, Dr. Weaver’s testimony discussed above was clear and unequivocal. See Ex. 1027 (Weaver Tr.), 24:15–29:14. Patent Owner made no effort to redirect his testimony at his deposition, so it cannot now do so through mere attorney argument. We find the inconsistency between Dr. Weaver’s treatment of Zhu and his treatment of similar disclosure in the ’724 patent exposes the insufficient reasoning supporting his opinions regarding the adequacy of Zhu’s use of encryption in the combination. Accordingly, we give no weight to his testimony that a skilled artisan would not have combined Zhu with a Buhot/GPC system due to security concerns. In contrast, we find the testimony of Mr. Smith regarding the use of encryption and the tradeoffs with the benefits of adopting Zhu’s memory management technique, which he offers in his Supplemental Declaration, to be well-reasoned, consistent with the disclosure of Zhu and the ’724 patent4, and entitled to substantial weight. See Ex. 1033 (Smith Supp. Decl.) ¶¶ 4–15. As Petitioner recognizes, “‘[a] given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine.’” Allied Erecting & Dismantling Co. v. Genesis Attachments, LLC, 825 F.3d 1373, 1381 (Fed. Cir. 2016). As Mr. Smith and Dr. Weaver testified, decryption without access to the security keys is an extremely computationally intensive and time-consuming process. Ex. 1033 (Smith Supp. Decl.) ¶¶ 6–8; Ex. 1027 (Weaver Tr.), 23:17–25:2; see also Ex. 10175, 132. Mr. Smith testifies that the benefits of using encryption would be sufficient to resolve the security concerns Patent Owner raises, and that any burden of generating a certificate would be outweighed by the benefits of using encryption and the memory advantages Zhu’s technique would offer. See Ex. 1033 (Smith Supp. Decl.) ¶¶ 4–15. Accordingly, we find that Patent Owner’s security concerns would be” slip op. at 25
Patent outcomesUS 11,018,724 unpatentableClaim construction§ 103 obviousness§ 112 disclosurecites KSR · GrahamPatents in suitUS 11,018,724 - PTAB · Aug 11, 2023 · PGR2023-00013 · APJ Sharon Fenick · PGR · Institution
Instituted PGR on claims 1–27 on all asserted grounds; the Board found it more likely than not that at least one claim is unpatentable.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“A post-grant review may be instituted only if “the information presented in the petition filed under section 321, if such information is not rebutted, would demonstrate that it is more likely than not that at least 1 of the claims challenged in the petition is unpatentable.” 35 U.S.C. § 324(a). For the reasons below, Petitioner has demonstrated that it is more likely than not that at least one of the challenged claims is unpatentable. Accordingly, we institute a post-grant review of the challenged claims of the ’286 patent on all grounds raised in the Petition.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“A. Level of Ordinary Skill in the Art Petitioner contends that: A person of ordinary skill in the art . . . would have had (1) a bachelor’s degree in computer science, computer engineering, electrical engineering, or a related field, and (2) one to two years of experience working with payment processing and/or digital authentication systems, including familiarity with short-range wireless technologies.” slip op. at 9
- Parallel petitionsDecided for petitioner
“The Trial Practice Guide states that “one petition should be sufficient to challenge the claims of a patent in most situations.” CTPG 59. “Two or more petitions filed against the same patent at or about the same time . . . may place a substantial and unnecessary burden on the Board and the patent owner and could raise fairness, timing, and efficiency concerns.” Id. (citing 35 U.S.C. § 316(b), which is identical to 35 U.S.C. § 326(b)). Although rare circumstances may necessitate two petitions, “the Board finds it unlikely that circumstances will arise where three or more petitions by a petitioner with respect to a particular patent will be appropriate.” Id. To help the Board determine whether multiple petitions are necessary, the Trial Practice Guide further instructs a petitioner filing multiple petitions challenging the same patent to explain “the differences between the petitions, why the issues addressed by the differences are material, and why identifies one petition that satisfies petitioner's burden under 35 U.S.C. § 314(a).” CTPG 59–60. Additionally, the Trial Practice Guide instructs the patent owner to “clearly proffer any necessary stipulations,” where the patent owner asserts that “the differences identified by the petitioner are directed to an issue that is not material or not in dispute.” Id. at 61. The patent owner may, for example, “seek to avoid additional petitions by proffering a stipulation that certain claim limitations are not disputed or that certain references qualify as prior art.” Id. In light of the particular facts before us, we decline to exercise our discretion to deny the Petition pursuant to 35 U.S.C. § 324(a) on the basis of the filing of two parallel petitions. In particular, we recognize that the two petitions do not include duplicate attacks on the basis of unpatentability over prior art, but rather break the issues into two distinct parts—prior-art based unpatentability challenges, in PGR2023-00012, and 35 U.S.C. §§ 101 and 112 challenges here. The usual considerations of fairness, timing, and efficiency do not weigh in favor of exercising our discretion to deny institution. In particular, the petitions were filed concurrently, which means that Petitioner did not gain a timing advantage that might otherwise occur if the petitions were filed serially. Additionally, the proceedings can be coordinated, and a similar or common schedule can be adopted. To the extent that Patent Owner argues (see Prelim. Resp. 55–56) that Petitioner was attempting to avoid providing a single stipulation that (upon institution) Petitioner will pursue neither section 103 grounds on certain art, as per the stipulation offered in PGR2023-00012, nor section 101 and 112 grounds as per the stipulation here (see Pet. 49), discretionary denial of this Petition would not provide such a stipulation. Because we institute both here and in is equivalent to our best understanding of Patent Owner’s desired stipulation “tak[ing] into account” the two Petitions. Accordingly, based on the particular facts and circumstances before us, we decline to exercise our discretion to deny the instant Petition under § 324(a) on the basis of the Petitioner’s filing of multiple petitions.” slip op. at 14
- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Decided for petitioner
“2. Conclusion We have considered the circumstances and facts before us in view of the first five Fintiv factors. Because our analysis is fact-driven, no single factor is determinative of our conclusion. Considering these five Fintiv factors together, we determine that they do not favor a discretionary denial. As we do not find that the first five Fintiv factors favor discretionary denial, we therefore do not make a determination regarding compelling merits under Fintiv factor 6, and our consideration ends with this conclusion. CommScope, 4–5.” slip op. at 23
Claim construction§ 101 eligibility§ 112 disclosureDiscretionary denialcites Alice · Mayo · Bilski · Enfish · Phillips · NautilusPatents in suitUS 11,328,286 - PTAB · Aug 11, 2023 · PGR2023-00012 · APJ Sharon Fenick · PGR · Institution
Instituted PGR on claims 1–27 and all asserted grounds after finding it more likely than not that at least one challenged claim is unpatentable.
RulingsInstitution decision- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner
“On this record, and for the purposes of institution, we agree that Petitioner has sufficiently shown that the information presented on the interface of the card device is not described in the ’891 provisional as being limited to use in an in-store merchant card reader facility. The ’891 provisional describes the card “connect[ing] to a personal computer” for use in generating payment information for online purchases. Ex. 1012 ¶ 17. While Patent Owner argues that the description in the ’891 provisional of “uniquely generat[ing] a credit card number” means a use “unique from that used for in-store transactions,” this description echoes the general description of the use of the card to provide “a unique credit card number . . . for each transaction.” Compare Ex. 1012 ¶ 14, with id. ¶ 17.” slip op. at 12
- Skill levelSkill level petitioner adoptedDecided for petitioner
“A person of ordinary skill in the art . . . would have had (1) a bachelor’s degree in computer science, computer engineering, electrical engineering, or a related field, and (2) one to two years of experience working with payment processing and/or digital authentication systems, including familiarity with short-range wireless technologies.” slip op. at 10
- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Denied
“Because the trial in the district court litigation, under any of the parties’ proposed approaches, appears likely to begin several months before our deadline to reach a decision, this factor weighs in favor of discretionary denial.” slip op. at 18
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for petitioner
“We address the meaning of several claim terms below and determine that no additional claim construction is needed for purposes of this Decision.” slip op. at 23
Claim construction§ 103 obviousness§ 112 disclosureDiscretionary denialcites PhillipsPatents in suitUS 11,328,286 - PTAB · Apr 11, 2023 · IPR2022-01564 · APJ Patrick R Scanlon · IPR · Institution
The Board instituted IPR on claims 1–14 and all asserted grounds, finding a reasonable likelihood that Keith anticipates at least claims 1 and 10.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“review. See 35 U.S.C. § 314 (2018); 37 C.F.R. § 42.4(a) (2021). To institute an inter partes review, we must determine that the information presented in the Petition shows “a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). For the reasons set forth below, we determine that the information presented in the Petition establishes a reasonable likelihood that Petitioner will prevail with respect to at least one challenged claim. We institute an inter partes review of claims 1‒14 based on the grounds set forth in the Petition.” slip op. at 2
- Parallel petitionsDecided for petitioner
“Under the circumstances presented, where the priority date of the challenged claims is disputed, we conclude it is not unreasonable for Petitioner to present separate challenges, one of which relies on references that are prior art only if the challenged claims are not entitled to Patent Owner’s claimed priority date, which has yet to be finally determined. See TPG 59 (stating that “a dispute about priority date requiring arguments under multiple prior art references” can be a potential reason for the Board to institute trial on multiple petitions challenging the same patent). Thus, on the present record, we decline to exercise our discretion to deny institution of this Petition on the basis of Petitioner filing multiple petitions.” slip op. at 46
- Skill levelSkill level petitioner adoptedDecided for petitioner
“have had a Bachelor’s degree in computer science, computer engineering, electrical engineering, or a related field or equivalent coursework or experience, and one to two years of experience with mobile device applications and retail POS systems,” also noting that “[m]ore education can supplement practical experience and vice versa.” Pet. 20–21 (citing Ex. 1002 ¶ 34). Patent Owner, at this stage of the proceeding, does not dispute Petitioner’s definition of the person of ordinary skill in the art. Prelim. Resp. 18. For the purposes of this Decision, we apply Petitioner’s proffered level of skill in the art because it appears consistent with the problems addressed in the ’435 patent and the prior art.” slip op. at 11
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“We determine that an express construction of this or any other claim term is not necessary for purposes of this Decision. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those 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
Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosureDiscretionary denialPatents in suitUS 10,803,435 - Ironsource Ltd. v. Digital Turbine Inc.InstitutedPTAB · Mar 17, 2023 · PGR2022-00053 · APJ Iftikhar Ahmed · PGR · Institution
The Board instituted PGR on claims 1–22 under § 101, § 102(a) over Pasha, and § 103 over Pasha, Pasha and Yamada, and Pasha and Molinet.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“Under 35 U.S.C. § 324(a), a post-grant review may not be instituted unless it is determined that it is more likely than not that at least one of the challenged claims is unpatentable. Based on the information presented in the Petition and the supporting evidence, we are persuaded that the Petition demonstrates it is more likely than not that at least one of the challenged claims is unpatentable. Accordingly, we institute a post-grant review of the challenged claims on the grounds set forth in the Petition.” slip op. at 2
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“[t]he words of a claim are generally given their ordinary and customary meaning as understood by a person of ordinary skill in the art when read in the context of the specification and prosecution history.” Thorner v. Sony Comput. Entm’t Am. LLC, 669 F.3d 1362, 1365 (Fed. Cir. 2012) (citing Phillips, 415 F.3d at 1313). “There are only two exceptions to this general rule: 1) when a patentee sets out a definition and acts as his own lexicographer, or 2) when the patentee disavows the full scope of a claim term either in the specification or during prosecution.” Id. (citing Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1580 (Fed. Cir. 1996)). Neither of those exceptions apply here, and for the reasons below, we find the plain and ordinary meaning of “invoke” or “invoking” to be to call or activate, as proposed by Petitioner. slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed petitioner constructionDecided for petitioner
“to mean “to shift user interaction on the device,” and we disagree with Patent Owner that the claim term requires the shifting to take place without requiring a user interaction. We begin with the language of the independent claims. Claim 1 recites “redirect said device to an app store for downloading said first software application on said device.” Ex. 1001, 21:38–40. The claim language, therefore, does not recite any requirement relating to user interaction during the redirect.” slip op. at 15
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction needed
“3. Other Claim Terms We determine that we do not need to expressly construe any other terms in order to determine whether to institute. The parties are reminded claim terms will be based on the complete record developed during trial.” slip op. at 17
Claim construction§ 101 eligibility§ 102 anticipation§ 103 obviousnessDiscretionary denialcites Alice · Enfish · PhillipsPatents in suitUS 11,157,256 - PTAB · Feb 8, 2023 · IPR2022-01335 · APJ Arthur M Peslak · IPR · Institution
The Board instituted IPR on claims 19, 20, and 37–52 based on the §103 combination of Hardin and Salmre, finding a reasonable likelihood of prevailing.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“on behalf of the Director.”). Under 35 U.S.C. § 314(a), an inter partes review may not be instituted unless the information presented in the Petition shows “there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” Considering the Petition, the arguments presented in the Preliminary Response, as well as all supporting evidence, we conclude that the information presented in the Petition establishes that there is a reasonable likelihood that Petitioner would prevail in its challenge of at least one claim of the ’447 patent as unpatentable. Pursuant to 35 U.S.C. § 314, we hereby institute an inter partes review of all Challenged Claims of the ’447 patent on the ground stated in the Petition.” slip op. at 3
- Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateOther
“(1) Petitioner asserts that substantially the same two claim limitations lack written description support in the ’094 application and U.S. Patent Application No. 13/856,392 (“the ’392 application”) (compare Pet. 23–29, with IPR2022-01333, Paper 4 (petition) at 23–28); (2) Petitioner asserts that because these limitations lack written description support in the ’094 and ’392 applications, the Challenged Claims are not entitled to the priority date of either of these applications and, therefore, Hardin ’665 (the pre-issuance publication of the ’094 application) is available as prior art to the Challenged Claims (compare Pet. 1, 2, 28–29, with IPR2022-01333, Paper 4 at 1, 2, 28–29);” slip op. at 15
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundInstituted
“(3) Petitioner asserts that the same combination of references— Hardin ’665 and Salmre—would have rendered the subject matter of the claims challenged in each petition obvious to one of ordinary skill in the art at the time of the invention (compare Pet. 29–64, with IPR2022-01333, Paper 4 at 29–66); (4) Petitioner asserts the same reasons with rational underpinning as to why one of ordinary skill in the art would have been motivated to combine the teachings of Hardin ’665 and Salmre as proposed with a reasonable expectation of success (compare Pet. 65–71, with IPR2022-01333, Paper 4 at 66–71);” slip op. at 15
- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Denied
“that we should exercise our discretion to deny institution pursuant to 35 U.S.C. § 314(a) and Apple Inc. v. Fintiv, Inc., IPR2020-00019, Paper 11 (PTAB Mar. 20, 2020) (precedential) (compare Prelim. Resp. 61–66, with IPR2022-01333, Paper 9 at 61–66);” slip op. at 16
Claim construction§ 103 obviousness§ 112 disclosureDiscretionary denialcites PhillipsPatents in suitUS 10,984,447
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.