• Ironsource Ltd. v. Digital Turbine Inc.All claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 101 eligibility§ 103 obviousnesscites Alice · Berkheimer · Enfish · Phillips
  Patents in suitUS 11,157,256
• Nabors Drilling Technologies USA, Inc. v. Motive Drilling Technologies, Inc.All claims unpatentable
  PTAB · Feb 22, 2024 · PGR2022-00055 · APJ Sean P O’Hanlon · PGR · Final written decision

  Claims 1–4 and 10–13 are unpatentable under § 101; claims 1–4 and 11–13 are also unpatentable as obvious over Pirovolou, Panchal, and Budiman, and claim 10 over those references plus Downton.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “The level of ordinary skill in the art is “a prism or lens” through which we view the prior art and the claimed invention. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). The person of ordinary skill in the art is a hypothetical person presumed to have known the relevant art at the time of the invention. In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995). In determining the level of ordinary skill in the art, we may consider certain factors, including: “(1) the educational level of the inventor; (2) type of problems encountered in the art; (3) prior art solutions to those problems; (4) rapidity with which innovations are made; (5) sophistication of the technology; and (6) educational level of active workers in the field.” Best Med. Int’l, Inc. v. Elekta Inc., 46 F.4th 1346, 1353 (Fed. Cir. 2022) (citations omitted). “The patent’s purpose can also be informative.” Id. (citation omitted).” slip op. at 9

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther

    “The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (alteration in original) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). Neither party presents arguments for the express construction of any term, instead interpreting the claim terms according to their ordinary and customary meaning. Pet. 18; PO Resp. 29. For purposes of this Decision, and based on the record before us, we determine that no construction of any term is necessary. slip op. at 10

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable

    “information (recitations 1.3, 1.8), using received information to generate a set of possible drilling paths (recitation 1.4), removing certain ones of the generated possible paths (recitations 1.5–1.6), selecting a desired one of the generated paths (recitation 1.7), and updating a plan to include the selected path (recitation 1.9). This collection and manipulation of data is similar to the data collection and management concepts that were held to be patent ineligible in previous cases. See Content Extraction & Transmission LLC v. Wells Fargo Bank, 776 F.3d 1343, 1345, 1347 (Fed. Cir. 2014); In re TLI Commc’ns LLC Patent Litig., 823 F.3d 607, 610, 613 (Fed. Cir. 2016); Elec. Power Grp., LLC v. Alstom S.A., 830 F.3d 1350, 1351–54 (Fed. Cir. 2016). Although the claim enumerates the type of information (i.e., BHA location, target path, and possible convergence paths) that is acquired and analyzed, the Federal Circuit has explained that the mere selection and manipulation of particular information by itself does not make an abstract concept any less abstract. Elec. Power Grp., 830 F.3d at 1353; Dig. Image Techs., LLC v. Elecs. for Imaging, Inc., 758 F.3d 1344, 1351 (Fed. Cir. 2014).” slip op. at 20

  • Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable

    “removing illogical options as the “pruning” step, rather than both of the “removing” steps as asserted by Patent Owner. See Ex. 1001, 6:21–34, 6:42–43, 6:50. The two “removing” steps noted by Patent Owner reduce the number of cost considerations that the computer must perform (by increasing the number of other comparisons (regarding illogical options and rule violations)), but do not change the way in which the computer performs the cost analyses. And, as explained above, neither the “removing” steps nor any other recitation alters the way in which drilling is performed. Moreover, as also noted above, the “removing” steps relied upon by Patent Owner are part of the abstract idea itself and, therefore, cannot evidence an inventive concept. See Berkheimer v. HP Inc., 890 F.3d 1369, 1374 (Fed. Cir. 2018) (Moore, J., concurring); BSG Tech LLC v. BuySeasons, Inc., 899 F.3d 1281, 1290–91 (Fed. Cir. 2018). As noted above, the additional elements of the processor and memory are recited at a high level of generality, i.e., as a generic processor performing a generic computer function of processing data. The ’454 patent also describes the processor and memory as generic computer components. See Ex. 1001, 4:50–5:29. The claim includes the additional recitations of a memory and processor to send a control signal. A memory for storing data and a processor for processing data and sending signals are well‐understood, routine, and conventional computer components, which in this claim are recited at a high level of generality and perform generic computer functions (e.g., storing, processing, and transmitting information). See Ex. 1003 ¶¶ 104–105 (citing Ex. 1006 ¶ 22, Fig. 2, code (57)). Generic computer components performing generic computer functions, alone, do not amount to significantly more than the abstract idea, as the Supreme Court has explained that “the mere recitation of a generic computer cannot transform a patent-ineligible abstract idea into a patent-eligible invention.” Alice, 573 U.S. at 223. Viewing the limitations in combination also fails to amount to significantly more than the abstract idea. The claimed system seeks to use a processor and memory to generate possible convergence paths, remove certain ones of the generated possible paths, select a desired one of the generated paths, update a plan to include the selected path, and send a signal, but these functions reflect ordinary usage typically performed by a generic computer, as would be recognized by those of ordinary skill in the field of mining. See, e.g., Ex. 1006 ¶ 22, code (57). The claim here does not invoke any of the considerations that courts have identified as providing significantly more than an exception; the combination of elements is no more than the sum of their parts. Additionally, as the Federal Circuit has explained, claims that do not include a requirement for performing “claimed functions of [data] gathering, analyzing, and [transmitting] by use of anything [other than] conventional, generic technology” fail to provide an inventive concept. Elec. Power Grp., 830 F.3d at 1356. Accordingly, on this record, Petitioner sufficiently shows that the claim as a whole does not amount to significantly more than the recited exception.” slip op. at 29

  Patent outcomesUS 11,170,454 unpatentable
  Claim construction§ 101 eligibility§ 102 anticipation§ 103 obviousnesscites Alice · Mayo · Bilski · Electric Power · KSR · Graham
  Patents in suitUS 11,170,454
• Ironsource Ltd. v. Digital Turbine Inc.Instituted
  PTAB · 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 · Phillips
  Patents in suitUS 11,157,256
• Nabors Drilling Technologies USA, Inc. v. Motive Drilling Technologies, Inc.Instituted
  PTAB · Mar 13, 2023 · PGR2022-00055 · APJ Sean P O’Hanlon · PGR · Institution

  The Board instituted PGR on claims 1–4 and 10–13, finding the petition showed a reasonable likelihood of prevailing on § 101 and § 103 grounds.

  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. 35 U.S.C. § 324(c) (2018); 37 C.F.R. § 42.4(a). Institution of postgrant review is authorized by statute only when “the information presented in the petition . . . , 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). “When instituting post-grant review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.” 37 C.F.R. § 42.208(a)). Having considered the arguments and evidence presented by Petitioner and Patent Owner, we determine that Petitioner has demonstrated that it is more likely than not that it will prevail with respect to at least one challenged claim. Accordingly, we institute post-grant review of the challenged claims of the ’454 patent.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner does not contest Petitioner’s definition or offer a definition of its own. See generally Prelim. Resp. Based on the arguments presented and the cited references, we find Petitioner’s definition of the level of ordinary skill reasonable and, for purposes of this Decision, adopt it as our own.” slip op. at 10

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther

    “The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (alteration in original) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). Neither party presents arguments for the express construction of any term, instead interpreting the claim terms according to their ordinary and customary meaning. Pet. 18; Prelim. Resp. 15. For purposes of this Decision, and based on the record before us, we determine that no construction of any term is necessary. We note that this determination does not preclude the parties from arguing their proposed constructions of the claims during trial. Indeed, the parties are hereby given notice that claim construction, in general, is an issue to be addressed at trial. A final determination as to claim construction will be made at the close of the proceeding, after any hearing, based on all the evidence of record. slip op. at 11

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionInstituted

    “Claim 1 recites a system that performs the steps of receiving information (recitations 1.3, 1.8), using received information to generate a set of possible drilling paths (recitation 1.4), removing certain ones of the generated possible paths (recitations 1.5–1.6), selecting a desired one of the generated paths (recitation 1.7), and updating a plan to include the selected path (recitation 1.9). This collection and manipulation of data is similar to the data collection and management concepts that were held to be patent ineligible in previous cases. See Content Extraction & Transmission LLC v. Wells Fargo Bank, 776 F.3d 1343, 1345, 1347 (Fed. Cir. 2014); In re TLI Commc’ns LLC Patent Litig., 823 F.3d 607, 610, 613 (Fed. Cir. 2016); Elec. Power Grp., LLC v. Alstom S.A., 830 F.3d 1350, 1351–54 (Fed. Cir. 2016). Although the claim enumerates the type of information (i.e., BHA location, target path, and possible convergence paths) that is acquired and analyzed, the Federal Circuit has explained that the mere selection and manipulation of particular information by itself does not make an abstract concept any less abstract. Elec. Power Grp., 830 F.3d at 1353; Dig. Image Techs., LLC v. Elecs. for Imaging, Inc., 758 F.3d 1344, 1351 (Fed. Cir. 2014). Accordingly, on this record, Petitioner sufficiently shows that the claim recites an abstract idea that falls within the grouping of mental processes. See Elec. Power Grp., 830 F.3d at 1355.” slip op. at 19

  Claim construction§ 101 eligibility§ 102 anticipation§ 103 obviousnesscites Alice · Mayo · Bilski · Electric Power · KSR · Graham
  Patents in suitUS 11,170,454
• Ironsource Ltd. v. Digital Turbine Inc.All claims unpatentable
  PTAB · 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 · Graham
  Patents in suitUS 10,782,951
• Kiosoft Technologies, LLC / Techtrex, Inc. v. Payrange Inc.Some claims unpatentable
  PTAB · Dec 14, 2022 · PGR2021-00093 · APJ Ken B Barrett · PGR · Final written decision

  Claims 1–6, 8–10, 14, 15, and 18–25 are unpatentable under § 101; claims 7, 11–13, 16, and 17 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “B. The Level of Ordinary Skill in the Art In determining the level of ordinary skill in the art, various factors may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (internal quotation marks and citation omitted). Petitioner contends: A [person of ordinary skill in the art (“POSITA” or “POSA”)] at the time of the earliest claimed filing date of the ’614 Patent would have had an education background of, or practical experience providing an equivalent to, a Bachelor of Science in Electrical Engineering, Computer Science, Information Technology, 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 affirmatively states that it does not dispute Petitioner’s asserted educational background of a person of ordinary skill in the art. PO Resp. 7. Patent Owner does not dispute Petitioner’s proposed number of years of experience, instead contending that “the claims are patentable regardless of the number of years of work experience a POSA would have had.” Id. (citing Ex. 2019 ¶¶ 49–58). Petitioner’s definition is consistent with the level of ordinary skill reflected in the prior art references of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (recognizing that the prior art itself may reflect an appropriate level of skill in the art). We adopt Petitioner’s definition of the person of ordinary skill in the art.” slip op. at 8

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther

    “construction disputes to find that Petitioners have failed to satisfy their burden of proof.” PO Resp. 8. Patent Owner goes on to state its agreement with Petitioner’s proposed construction for the “identifying” limitation (id. at 9) and indicate its disagreement with certain of Petitioner’s proposals (id. at 9–14). Patent Owner confirmed at the oral argument that no claim term needs to be construed to reach a dispositive issue. Tr. 33:23–34:5. We determine that we need not expressly construe any claim terms to resolve the parties’ disputes.” slip op. at 11

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionDecided for petitioner

    “All of the claimed method steps of claim 1 occur “at the mobile device” (element 1.1), and the method includes a step of enabling user interaction with the user interface to complete the vending transaction (element 1.9). Id. at 46:61–65, 47:24–28. Claim 1 does not recite completing the purchase. The ’614 patent describes a commercial transaction completed at the payment accepting unit (i.e. the vending machine), not at the mobile device. Ex. 1001, 7:15–19; see also id. at 16:46–50; 17:57–59; 19:17–20; 19:35–38. We, thus, agree with Patent Owner that the claimed method does not require completing or conducting the transaction, but only enabling the completion of the transaction. On this complete record, we are persuaded that the elements block quoted above recite the concept of identifying a merchant and enabling completion of a purchase from the merchant. See Pet. 20 (arguing that the claimed method “is no less abstract than a customer noticing a store, making a purchase, and receiving a receipt.”); Pet. Reply 5 (arguing that the claim describes “nothing more than a customer noticing and identifying a store amongst multiple stores based on the unique visual image of that store, entering the store and communicating with the merchant, making a purchase, and receiving a receipt—all while using conventional tools.”). In particular, claim 1 recites a step for identifying a merchant based on its advertised presence—identifying a nearby vending machine that is available to accept payment from a mobile payment application, with that identifying involving the broadcasting of predefined radio messages.8 Claim 1 also recites steps for enabling completion of a purchase from the merchant— establishing a communication connection between the user’s device and the vending machine; displaying an interface that allows a user to select a vending machine, to trigger payment for the vending transaction, and to enable the completion of the transaction; and updating the user interface after receiving information from the vending machine regarding the transaction (which, as indicated by dependent claim 3, may be information indicating that the vending transaction was completed). Our slight revision of the abstract idea from what we previously stated in our Institution Decision does not impact the patentability analysis. Apple, Inc. v. Ameranth, Inc., 842 F.3d 1229, 1241 (Fed. Cir. 2016).” slip op. at 17

  • Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptMixed

    “As discussed above, the Specification indicates that the short-range communication between the vending machine and mobile device can be not only conventional technologies such as Bluetooth, near-field communication (NFC), and radio frequency identification (RFID), but also could be “any wired or wireless technology that could be used to communicate a small distance (approximately a hundred feet or closer) that is known.” Ex. 1001, 9:57–67. The Specification ties that technology to the “broadcast” in claim 1 (id. at 47:2–5). For example, the Specification explains that “[e]ach adapter module 100 [of the vending machine] advertises its presence by broadcasting signals (advertising broadcast signals) to mobile devices in the zones 102, 104, 106.” Id. at 10:43–45. “The outermost range is the Bluetooth range 106 . . . [and] is the area in which the adapter module 100 is able to broadcast its presence.” Id. at 18:29–33. Further, Dr. Shamos testified that the Bluetooth protocol requires that two devices wishing to interact with each other identify themselves to each other. Ex. 1030, 102:3– 24. Dr. Shamos also testified that the Low prior art reference discloses that a vending machine identifies itself to the user. Id. at 100:9–20; see Ex. 1007, 2:25–28 (Low stating that, “in some embodiments, multiple machines may send their unique identifiers, such that the user is able to select one or more machines to purchase from.”). Thus, the abstract idea of identifying a merchant is implemented by nothing more than well-known, routine, and conventional wireless communications.” slip op. at 39

  Patent outcomesUS 10,891,614 mixed
  Claim construction§ 101 eligibility§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Mayo · Bilski · Phillips · KSR · Graham · Nautilus
  Patents in suitUS 10,891,614
• Kiosoft Technologies, LLC / Techtrex, Inc. v. Payrange Inc.Institution denied
  PTAB · Dec 6, 2022 · PGR2022-00035 · APJ Ken B Barrett · PGR · Institution

  The Board denied institution because Petitioner did not show it was more likely than not that any of claims 1–17 was unpatentable on the asserted grounds.

  RulingsInstitution decision

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

    “A post-grant review may not be instituted “unless . . . the information presented in the petition . . . , 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) (2018). Having considered the arguments and evidence presented by Petitioner and Patent Owner, we determine that Petitioner has not demonstrated that, if unrebutted, it is more likely than not that at least one of the claims challenged in the patent is unpatentable. Accordingly, we do not institute a post-grant review of the challenged claims of the ’580 patent.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “have a Bachelor of Science in Electrical Engineering, Computer Science, or another degree related to electromechanical systems, as well as at least 3 years of academic or industry experience in electronic payment systems.” Pet. 25–26 (citing Ex. 1003 ¶ 22). Patent Owner, at this stage, does not disagree or propose a different definition of the person of ordinary skill in the art. Petitioner’s definition is consistent with the level of ordinary skill reflected in the prior art references of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (recognizing that the prior art itself may reflect an appropriate level of skill in the art). For purposes of this decision, we apply Petitioner’s definition of the person of ordinary skill in the art.” slip op. at 7

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther

    “Petitioner states that, “[u]nless otherwise noted, Petitioners submit that the claim terms should be given their plain and ordinary meaning since the claim terminology appears to be the same as that used in the [Multi-Drop Bus] protocol.” Pet. 28. Patent Owner does not propose any constructions, asserting that “the Board need not reach any claim constructions in order to deny this petition.” Prelim. Resp. 12. On this record and for purposes of this decision, we determine that no claim terms require express construction.” slip op. at 8

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable

    “in Anderson of a mobile device making, or the receipt from a mobile device of, a request to access peripheral device-generated signals. See Prelim. Resp. 17–24; see, e.g., id. at 17 (“Petitioners point to no evidence that any external device in Anderson ever requests access to the signals generated by the peripheral.”). We find this argument persuasive. Petitioner, in the section for “receiving” limitation 1.5(f), cites paragraph 44 of Anderson several times. See Pet. 36–39. That paragraph concludes with the statement: The IC 125 may also include a modem (not shown) to display content on external devices such as cellular phones via cellular network or any other network know[n] in the art. Thus, in one implementation, a user may receive nutritional information or balance information on his cell phone. Ex. 1005 ¶ 44. That is a disclosure of data flowing to the cell phone in the form of content to display, and it is ambiguous as to what component could be said to have requested that data flow. Limitation 1.5(f) recites data flow in the opposite direction, from the mobile device, and pertains to a specific message—“a request to access signals generated by the first peripheral device.” Ex. 1001, 53:22–24. Petitioner does not explain adequately how the disclosure in Anderson’s paragraph 44 could support a finding that there was received, from the cell phone, a request to access signals generated by a peripheral device. See, e.g., Pet. 36–37 (quoting Anderson’s paragraph 44).” slip op. at 13

  Claim construction§ 101 eligibility§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Mayo · Bilski · Phillips · KSR · Graham · Nautilus
  Patents in suitUS 11,074,580
• Ironsource Ltd. v. Digital Turbine Inc.Instituted
  PTAB · 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 · Phillips
  Patents 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.