- 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.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 - PTAB · Dec 17, 2021 · PGR2021-00093 · APJ Meredith C Petravick · PGR · Institution
The Board instituted PGR on claims 1–25 on all petition grounds after finding the § 101 challenge to claim 1 met the institution threshold.
RulingsInstitution decision- PTAB / AIA Trials › Discretionary denial › Fintiv (parallel litigation)Decided for petitioner
“Fintiv sets forth the factors that we weigh in determining whether to exercise our discretion to deny institution of the post-grant patent review proceeding here under 35 U.S.C. § 324(a). See Fintiv, Paper 11, 5–6. These factors are: 1. whether the court granted a stay or evidence exists that one may be granted if a proceeding is instituted; 2. proximity of the court’s trial date to the Board’s projected statutory deadline for a final written decision; 3. investment in the parallel proceeding by the court and the parties; 4. overlap between issues raised in the petition and in the parallel proceeding; 5. whether the petitioner and the defendant in the parallel proceeding are the same party; and 6. other circumstances that impact the Board’s exercise of discretion, including the merits. support the exercise of authority to deny institution in view of an earlier trial date in the parallel proceeding.” Id. at 6. “[T]he Board takes a holistic view of whether efficiency and integrity of the system are best served by denying or instituting review.” Id.” slip op. at 7
- PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsDecided for petitioner
“Because the claims at issue here, in particular claim 1, differ from the March 2015 amended claims of the ’859 patent and the August 2014 amended claims of the ’296 patent (see, e.g., Ex. 1001, 46:59–47:34), we are not persuaded that the cited prosecution history equally applies to the claims here. In particular, we note that claim 1, which we discuss in the analysis below, does not recite a first transceiver corresponding to a short-range communication mode and a second transceiver corresponding to a long-range communication mode, and does not specify whether a first or second transceiver perform certain actions recited in the claim. Id. As Patent Owner points out (Prelim. Resp. 19), claim 1 of the ’614 patent more but claim 1 does not specify whether it is long or short range and merely recites it being used to establish a connection for the exchange of information between a mobile device and a payment accepting unit in some of the claimed steps. Id. Thus, considering Becton, Dickinson factors (a) and (d), we are not persuaded that the same or substantially the same arguments concerning § 101 were previously presented to the Office. Because we determine that the same or substantially the same arguments with respect to § 101 were not previously presented to the Office, we need not address part two of the Advanced Bionics framework with respect to those arguments.” slip op. at 19
- Skill levelSkill level petitioner adoptedDecided for petitioner
“A [person having ordinary skill in the art (“POSITA”)] would have had an education background of, or practical experience providing an equivalent to, a Bachelor of Science in Electrical Engineering, Computer Science, or a related/equivalent field and at least 3 years of academic or industry experience in electronic payment systems. Pet. 16 (citing Ex. 1003 ¶¶ 5–6). Patent Owner does not dispute Petitioner’s contention in its Preliminary Response. See generally Prelim. Resp. Based on the record before us, we adopt Petitioner’s asserted level of ordinary skill to determine whether it is more likely than not that at least one of the claims challenged in the Petition is unpatentable. This level of skill in the art is consistent with the disclosure of the ’614 patent and the prior art of record. See In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995).” slip op. at 22
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionInstituted
“Ex. 1001, 46:61–47:34. Based on the current record, we are persuaded that the limitations above recite the concept of identifying a merchant and making a purchase from the merchant. In particular, claim 1 recites steps for identifying payment accepting units (i.e., a merchant) — limitations 1.2– 1.7.1. Claim 1 also recites steps for conducting the purchase —limitations 1.7.2–1.11. Based on the current record, we find that identifying a merchant and making a purchase from the merchant is a commercial interaction, a sales activity. It falls within the enumerated “[c]ertain methods of organizing human activity” grouping of abstract ideas set forth in MPEP § 2106.04(a)(2).” slip op. at 28
Claim construction§ 101 eligibility§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Mayo · Bilski · Berkheimer · Phillips · NautilusPatents in suitUS 10,891,614 - Epicor Software Corporation v. Protegrity CorporationRehearing deniedPTAB · Apr 19, 2016 · CBM2015-00002 · APJ Kevin F Turner · CBM · Rehearing
The Board denied both rehearing requests, leaving the institution of § 101 review of claims 1, 5, 8, 19, 20, and 27–31 and denial of prior art grounds unchanged.
RulingsRehearing decision- RehearingRehearing, deniedDenied
“D. Conclusion We are not persuaded of an abuse of discretion either by Patent Owner or Petitioner. III. ORDER In consideration of the foregoing, it is hereby: ORDERED that each Request for Rehearing is denied.” slip op. at 18
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“The Board instituted covered business method patent review of the ’201 Patent based upon the following ground, combined from both proceedings: Ground Prior Art Challenged Claims § 101 n/a 1, 5, 8, 19, 20, and 27–31 Papers 17 and 13 (’02 Decision and ’30 Decision, respectively). The Board did not institute covered business method patent review upon any prior art grounds. See ’02 Decision 6 and ’30 Decision 4–5 (listing grounds proffered by Petitioner).” slip op. at 2
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionDecided for petitioner
“Response, Patent Owner argues that the claims are directed toward protection of data in a database on a more granular level, namely at the data element level. Prelim. Resp. 27 (“the ’201 Patent is not directed to some abstract idea, but rather a specific improvement in computing technologies to protect data in a database at the date element level”). However, the abstract idea we identified is that of “determining whether access to a given data element value in a database should be granted based on whether one or more rules are satisfied.” ’02 Decision 20. See also Pet. 20. As such, the abstract idea goes directly to the concept of protecting data at the data element level.” slip op. at 13
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“Although Atalla discloses authorization to a file based on information about the file, Ex. 1007, 3:27–58, Petitioner has not shown that the information about the file is individual data element types. Overall, Atalla addresses accessing files, in part, based on whether the files were previously accessed, but a file in not the same as an individual data element value. The section of Atalla cited in Petitioner’s Rehearing Request discloses the need for a correct key code, but that key code is for the entire file and not specific to the data element type. Pet. Req. 6 (citing Ex. 1007, 3:27–58). Although “information about the file” could include information about individual data element types, Petitioner has not demonstrated any such teaching or suggestion in Atalla. As stated in the ’02 Decision, Atalla “does not describe that access authorization file 15 comprises ‘a data element protection catalogue (DPC), which contains each individual data element type (DT) and one or more protection attributes stating processing rules for data element values’ as requires by claim 1.” ’02 Decision 28. Thus, we are not persuaded by Petitioner that we abused our discretion in denying institution of covered business method patent review of claims 1, 5, 19, 20, and 27–31 over the anticipation ground of Atalla provided in the Petition.” slip op. at 16
§ 101 eligibility§ 102 anticipation§ 103 obviousnessPatents in suitUS 6,321,201
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.