- 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 - 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 - 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 - Ironsource Ltd. v. Digital Turbine Inc.All claims unpatentablePTAB · Jan 4, 2023 · PGR2021-00096 · APJ Iftikhar Ahmed · PGR · Final written decision
Claims 1–18 are unpatentable; the contingent motion to amend proposing claims 19–36 is denied, and the parties’ motions to exclude are denied in part and granted in part.
RulingsFinal written decision- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'IneligibleUnpatentable
“3. Analysis On the full record developed during trial, we are persuaded by Patent Owner’s argument. Petitioner’s analysis of the independent claims described above only loosely corresponds to the actual limitations recited in the claim. The Federal Circuit has “cautioned that courts ‘must be careful to avoid oversimplifying the claims’ by looking at them generally and failing to account for the 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)). Petitioner’s analysis of the claim limitations appears to do. Petitioner’s argument that “the essence of all 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:6–35. 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 representing a basic task in organizing human activity. Pet. 30. 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); October 2019 Update at 5 (“this grouping is limited to activity that falls within the enumerated sub-groupings . . . , and is not to be expanded beyond these enumerated sub-groupings except in rare circumstances”). The claimed invention may result in multitasking on the device, but the claims are directed to downloading and installing an application in the background instead of directing the user to an 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. We also agree with Patent Owner that the challenged claims are somewhat similar to those that the Federal Circuit held patentable in DDR Holdings. The claims there were directed to a method of generating a composite webpage that combined visual elements of a host website with content from a third-party, e.g., by combining the logo, background color, and fonts of the host website with product information from a merchant. DDR Holdings, 773 F.3d at 1248. When a user clicked on a link on the host website, the system would construct the composite web page comprising a look and feel description from the host website along with content based on product information from the merchant’s product catalog. Id. at 1250. The court held those claims were not directed at an abstract idea because they addressed the problem of retaining website visitors that, absent the claimed invention, would be instantly transported away from a host’s website after clicking on an advertisement and activating a hyperlink. Id. at 1257.” slip op. at 29
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed
“1. Independent Claim 1 a) “A mobile device configured for running software applications, comprising:” Petitioner contends that Pasha discloses computer system 600, which” slip op. at 38
- 112 supportMotion to amend, deniedDenied
“4. Support in the Original Disclosure A motion to amend may not present substitute claims that introduce new subject matter. 35 U.S.C. § 326(d)(3); 37 C.F.R. § 42.221(a)(2)(ii) (“A motion to amend may be denied where . . . [t]he amendment seeks . . . introduce new subject matter.”). “Normally, a claim element without support in the original disclosure (i.e., the application as originally filed) merits a rejection under 35 U.S.C. § 112 for lack of written description support.” Lectrosonics, Paper 15, 7. Accordingly, a motion to amend must set forth written description support in the originally filed disclosure of the subject patent for each proposed substitute claim.” Id.” slip op. at 74
- ExcludeMotion to exclude, grantedGranted in part
“CTPG at 73–74. Accordingly, Rule 42.23(b) prohibits filing of new evidence other than deposition transcripts of the cross-examination of any reply witness with a sur-reply. Patent Owner does not argue that the opinions presented in paragraphs 4–13 of Dr. Mao’s declaration are within the scope of §42.23(b). See generally PO MTE Opp. Nor do we find it in the interests of justice to allow this evidence in the case file. Accordingly, we grant in part Petitioner’s Motion to Exclude paragraphs 4–13 of Exhibit 2013 pursuant to 37 C.F.R. § 42.23(b).22” slip op. at 90
Patent outcomesUS 10,782,951 unpatentable§ 101 eligibility§ 102 anticipationcites Alice · Enfish · Phillips · KSR · GrahamPatents in suitUS 10,782,951 - Ironsource Ltd. v. Digital Turbine Inc.InstitutedPTAB · Jan 6, 2022 · PGR2021-00096 · APJ Iftikhar Ahmed · PGR · Institution
Instituted PGR on claims 1–18 under § 101, claims 1, 3–12, and 14–18 under § 102(a) over Pasha, and the listed § 103 grounds.
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 presents information demonstrating 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) › Lexicography (patentee as own lexicographer)Term construed board ownDecided for petitioner
“For the purposes of this Decision, we agree with Petitioner. Figure 7 of the ’951 patent shows the Downloader & Installer Module as a module within the “installation client,” not as the installation client itself. Ex. 1001, 14:4–45 (discussing “installation client 700” and its various modules); Fig. 7 (showing Download & Installer 720 as part of Installation Client 700). The ’951 patent states: Installation client 700 is represented as several modules performing separate functions. The division of functionality demonstrated in FIG. 7 is illustrative, and not intended to be limiting. Other embodiments of an installation client may organize the various functions performed by the installation client 700 in a different manner. Id. at 14:6–12. Accordingly, the proper construction of the term “installation client” does not limit the number or arrangement of components” slip op. at 11
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 not directed to exceptionNot shown unpatentable
“Petitioner’s analysis of the independent claims described above only loosely corresponds to the actual limitations recited in the claim. The Federal Circuit has “cautioned that courts ‘must be careful to avoid oversimplifying the claims’ by looking at them generally and failing to account for the 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 essence of all the claims” is captured by a single claim element not only ignores that that limitation recites installing software, 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:6–35. Nor are we persuaded by Petitioner’s characterization of the claims as directed to multitasking, which Petitioner characterizes as representing a basic task in organizing human activity. Pet. 30. 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 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); October 2019 Update at 5 (“this grouping is limited to activity that falls within the enumerated sub-groupings except in rare circumstances”). Although the claimed invention may result in multitasking on the device, the claims are directed to downloading and installing an application in 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); DDR Holdings, LLC v. Hotels.com, L.P., 773 F.3d 1245, 1257 (Fed. Cir. 2014) (finding claims that address the problem of retaining website visitors after clicking on an advertisement hyperlink not directed to an abstract idea). Accordingly, based on the current record, we question whether Petitioner establishes sufficiently that the claims are directed to a judicial exception under Step 2A of the Guidance. Nevertheless, because Petitioner has shown that it is more likely than not that challenged claims are unpatentable under 35 U.S.C. §§ 102, 103 (see infra §§ III.F–I), we include this ground in the instituted post-grant review. See SAS Inst., Inc. v. Iancu, 138 S. Ct. 1348, 1354, 1359–60 (2018); see also PGS Geophysical AS v. Iancu, 891 F.3d 1354, 1360 (Fed. Cir. 2018) (interpreting the statute to embracing all challenges included in the petition”).” slip op. at 17
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Instituted
“As discussed above (supra Section II.C.1), at this preliminary stage, we do not construe “installation client” so narrowly as to limit the number or arrangement of components required to meet that claim element. Also, as discussed above (id.), the specification of the ’951 patent supports that multiple modules performing separate functions may comprise the installation client. Therefore, based on our review and consideration of the current record, we are not persuaded by Patent Owner’s argument that Pasha fails to disclose the claimed installation client. Petitioner’s arguments are inconsistent across the Petition. The Petition clearly alleges that “the App Manager 180 and Installer 182 disclose the claimed ‘installation client for downloading and installing applications on said device.’” Pet. 58. Petitioner’s description of Pasha’s App Manager is consistent with Pasha’s disclosure itself. For example, although Pasha discloses that “the host application 132 may use an App Manager component 180 and an Installer component 182,” it also states that “[t]he App Manager 180 may control portions of the application download and install process.” Ex. 1003, 17:22–26; Pet. 38. Pasha further discloses that “[t]he App Manager 180 [itself] may perform at least a portion of one or more of the steps 310–350 of FIG. 3,” i.e., including the step of “[i]nstalling the downloadable application on the computer system from the application package by executing program code having permission to install applications.” Ex. 1003, 17:35–36, Fig. 3. Patent Owner’s argument that Pasha’s “App Manager does not have the role of installing software applications,” is therefore contrary to Pasha’s disclosure. Also, Petitioner’s reasoning and evidentiary underpinnings here are based not so much on modifying Pasha, as Patent Owner suggests, as explaining how one of ordinary skill in the art would have understood Pasha’s disclosure. Between its App Manager and Installer, Pasha discloses the claimed functionality of the “installation client,” but, similar to the ’951 patent, Pasha teaches flexibility between the use of those components to implement the claimed functionality. For the purposes of institution, we are unpersuaded that Petitioner fails to meet its threshold burden of showing anticipation under Net MoneyIN. See, e.g., Blue Calypso, LLC v. Groupon, Inc., 815 F.3d 1331, 1344 (Fed. Cir. 2016) (explaining that a reference need not always as it teaches that the disclosed components or functionalities may be combined and one of skill in the art would be able to implement the combination). Based on our review of the current record, we therefore determine that the information presented supports sufficiently, for the purpose of institution, Petitioner’s assertion that Pasha discloses this limitation.” slip op. at 26
Claim construction§ 101 eligibility§ 102 anticipation§ 103 obviousnessDiscretionary denialcites Alice · Enfish · PhillipsPatents in suitUS 10,782,951
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.