• Early Warning Services, LLC v. Intellectual Ventures II LLCNo claims unpatentable
  PTAB · Feb 11, 2026 · IPR2024-01221 · APJ Iftikhar Ahmed · IPR · Final written decision

  Petitioner failed to prove claims 1, 2, 4, 5, 7, 8, 12, 13, 17, 19–21, 23, 24, 26, 27, 29, 30, 34, 39–41, and 43 unpatentable because the cited grounds did not establish the required …

  RulingsFinal written decision

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner

    “image capture device” refers to an imaging-based barcode reader and not a laser-based barcode scanner because we are persuaded that claim language and Specification support that interpretation and also because Patent Owner persuasively shows that a person of ordinary skill in the art would have understood the term as such. Claim 1 recites an “image capture device configured to capture an image.” Ex. 1001, 16:24–25. The plain meaning of the claim term requires that the image be captured, not just scanned. The claim further requires “generating an output based on the information embedded in the image,” requiring that information is retrieved from the captured image. Id. at 16:32–33. A device that does not capture an image is not an “image capture device” under the plain language of the claim. A laser-based barcode scanner employs light reflected from a laser beam to “generate an electrical signal that corresponds to the bars and spaces in the barcode being scanned.” See Ex. 2029 ¶¶ 42–43 (explaining in detail how laser-based barcode self-emitting a laser light across a code to be scanned, with a sensor tuned to capture the reflected light from the laser.”). It simply does not capture an image. slip op. at 14

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Based on our review of the complete record, we determine that Petitioner’s stated level of ordinary skill in the art is reasonable because it is consistent with the evidence of record, including the asserted prior art. The field of the ’167 patent “relates generally to secure transactions, and more specifically, to methods and devices for providing secure identification, verification, and authorization using a portable secure device.” Ex. 1001, 1:8–11. The ’167 patent seeks “to provide methods and devices that are capable of providing secure transactions in a more efficient manner.” Id. at 3:11–13. Accordingly, we adopt Petitioner’s definition. We note, however, that our patentability analysis would be the same under Patent Owner’s definition.” slip op. at 11

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

    “We agree with Patent Owner that Wang fails to disclose limitation 1[a]. Wang discloses a portable electronic authorization device (PEAD) that can be used as a self-checkout terminal. Ex. 1004 ¶ 115. In this context, Wang discloses By entering the UPC code or barcode using keypad on the PEAD or scanning in the UPC code or barcode using the input device built into the PEAD such as a barcode scanner or OCR reader, the PEAD can generate the receipt with the list of item prices through the wireless network and Internet by querying the item price using the barcode as the index for price lookup table which is Stored in a Server System. Id. (emphasis added). As discussed above (Section III.C.1), we are persuaded by Patent Owner’s arguments that the claimed “image capture device” refers to an imaging-based device and not a laser-based barcode scanner. Petitioner does not contend that Wang’s disclosure of the barcode scanner necessarily refers to an imaging-based device, but argues that Wang’s disclosure is sufficient because “both imaging-based barcode scanners and laser-based barcode scanners constitute image capture devices.” Reply 11. In light of our claim construction above, we disagree.” slip op. at 27

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “Petitioner contends that claims 1, 4, 5, 7, 12, 17, 23, 26, 27, 29, 34, and 43 are unpatentable as obvious over the combination of Wang and Drummond. Pet. 30–43. 1. Drummond Drummond is a patent titled “Automated Banking Machine System and Method,” and “relates to an automated banking machine apparatus and system that are capable of use in a wide area network, and which provides a user with a remote electronic receipt or other record related to a transaction performed at the machine.” Ex. 1008, code (54), ¶ 2. Drummond discloses that its automated banking machine, may “initiate the sending of a non-paper transaction receipt to the customer,” “[t]he receipt may be sent using a wide area network, such as the Internet,” and “[t]he receipt may be an electronic receipt, for example a receipt in the form of an e-mail message.” Id. ¶ 247. 2. Claims 1, 4, 5, 7, 12, 17, 23, 26, 27, 29, 34, and 43 For this obviousness ground, Petitioner relies on the same arguments and evidence as its Ground 1a (anticipation by Wang), discussed above, for the majority of claim limitations. See Pet. 33–43. Importantly, Petitioner relies solely on Wang as teaching independent claim limitations [1a], [23a], and [43b] relating to an image capture device and embedded information. Pet. 36, 41, 43. Accordingly, for the reasons discussed above with respect to Ground 1a, Petitioner has not established by a preponderance of the evidence, that the subject matter of claims 1, 4, 5, 7, 12, 17, 23, 26, 27, 29, 34, and 43 would have been obvious to one of ordinary skill in the art over the combination of Wang and Drummond.” slip op. at 31

  Patent outcomesUS 7,314,167 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,314,167
• Tanklogix, LLC v. Sitepro, Inc.Institution denied
  PTAB · Oct 10, 2025 · IPR2025-00653 · APJ Bart A Gerstenblith · IPR · Institution

  The Board denied institution on all claims because the Petition did not show a reasonable likelihood that any challenged claim was unpatentable over the asserted grounds.

  RulingsInstitution decision

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

    “An inter partes review may be instituted only if “the information presented in the petition . . . and any [preliminary] response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2024). For the reasons given below, on this record Petitioner has not established a reasonable likelihood that it would prevail in showing the unpatentability of any of the Challenged Claims. Accordingly, we do not institute an inter partes review.” slip op. at 2

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “The parties’ proposed levels of ordinary skill in the art are similar, although Patent Owner proposes two years of experience along with a bachelor’s degree whereas Petitioner proposes “significant” experience. Patent Owner also proposes an alternative with more extensive experience in lieu of a bachelor’s degree. Although we find Petitioner’s proposed qualifications acceptable, we adopt Patent Owner’s proposed qualifications for the purposes of this Decision because they offer a wider range of qualifications that nonetheless comport with the level of ordinary skill necessary to understand and implement the teachings of the ’504 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978). Our analysis and findings herein, however, do not turn on any differences in the parties’ proposed qualifications.” slip op. at 12

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

    “Additionally, only terms that are in controversy need to be construed, and these need be construed only to the extent necessary to resolve the controversy. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)). The parties assert that each claim term should be construed in accordance with its plain and ordinary meaning. Pet. 9; Prelim. Resp. 4 (citing Ex. 2009 ¶ 72); see Ex. 1002 ¶ 22 (opining the same). And, in the respective claim construction sections of their briefs, the parties do not propose any claim terms for express construction. We agree with the parties that no claim terms require express construction to resolve the controversy before us. See Realtime Data, 912 F.3d at 1375.” slip op. at 13

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “Ex. 1002 ¶ 47. As reflected above, Dr. Wooley’s testimony as to element [1.2] does not even assert that Cardamone discloses a tank, let alone one or more sensors disposed at a tank as recited in element [1.2]. Thus, Dr. Wooley’s testimony does not support Petitioner’s argument on this issue.” slip op. at 18

  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,726,504
• Tanklogix, LLC v. Sitepro, Inc.Institution denied
  PTAB · Oct 10, 2025 · IPR2025-00652 · APJ Bart A Gerstenblith · IPR · Institution

  The Board denied institution because Petitioner did not show a reasonable likelihood that claims 1–23 and 25–30 were unpatentable over the asserted grounds.

  RulingsInstitution decision

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

    “presented in the petition . . . and any [preliminary] response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2024). For the reasons given below, on this record Petitioner has not established a reasonable likelihood that it would prevail in showing the unpatentability of any of the Challenged Claims. Accordingly, we do not institute an inter partes review.” slip op. at 2

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “The parties’ proposed levels of ordinary skill in the art are similar, although Patent Owner proposes two years of experience along with a bachelor’s degree whereas Petitioner proposes “significant” experience. Patent Owner also proposes an alternative with more extensive experience in lieu of a bachelor’s degree. Although we find Petitioner’s proposed qualifications acceptable, we adopt Patent Owner’s proposed qualifications for the purposes of this Decision because they offer a wider range of qualifications that nonetheless comport with the level of ordinary skill necessary to understand and implement the teachings of the ’403 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978). Our analysis and findings herein, however, do not turn on any differences in the parties’ proposed qualifications.” slip op. at 12

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

    “The parties assert that each claim term should be construed in accordance with its plain and ordinary meaning. Pet. 10; Prelim. Resp. 4 (citing Ex. 2009 ¶ 73); see Ex. 1002 ¶ 22 (opining the same). And, in the respective claim construction sections of their briefs, the parties do not propose any claim terms for express construction. We agree with the parties that no claim terms require express construction to resolve the controversy before us. See Realtime Data, 912 F.3d at 1375.” slip op. at 13

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

    “We agree with Patent Owner that the Petition fails to demonstrate that Kahn discloses element [1.2] because the evidence cited does not disclose a “first computer system being configured to provide remote control of the first pump or first valve” (i.e., a fluid-handling device). Kahn is directed to providing access to fluid sensing data and analyzing and providing visual information on that data, but Petitioner has not identified any disclosure of the capability to remotely control fluid-handling devices. See, e.g., Ex. 1005, code (54), 1:27–36, 2:50–3:2. More specifically, Kahn’s disclosures that Petitioner relies on for allegedly teaching remote control are deficient. We discuss each. First, Petitioner points to the following, “[f]or instance, as illustrated in FIG. 1C, a fluid control device such as a valve 15A is located on the input side of a sen[s]or unit 110.” Ex. 1005, 8:19–21, cited in Pet. 13. This portion of Kahn, however, does not disclose remote control. Second, Petitioner cites to the following: Finally, or in addition to, the communication unit 112B can include on-site alerts such as optical (indicator lights), audible alerts (e.g., alarm sounds), tactile (e.g., vibration of the unit) or can be interfaced to an appropriate control valve for simply shutting off the supply of fluid upon the detection of emergency events, for instance. Pet. 13 (citing Ex. 1005, 10:62–67). We agree with Patent Owner that this portion of Kahn teaches on-site alerts and local control of the fluid-handling device. See Prelim. Resp. 7. This portion of Kahn does not disclose remote control.” slip op. at 18

  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,294,403
• Tanklogix, LLC v. Sitepro, Inc.Institution denied
  PTAB · Oct 10, 2025 · IPR2025-00651 · APJ Bart A Gerstenblith · IPR · Institution

  The Board denied institution because Petitioner did not show a reasonable likelihood that claims 1–3, 6, 7, and 9–20 were unpatentable over any asserted ground.

  RulingsInstitution decision

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

    “presented in the petition . . . and any [preliminary] response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2024). For the reasons given below, on this record Petitioner has not established a reasonable likelihood that it would prevail in showing the unpatentability of any of the Challenged Claims. Accordingly, we do not institute an inter partes review.” slip op. at 2

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “The parties’ proposed levels of ordinary skill in the art are similar, although Patent Owner proposes two years of experience along with a bachelor’s degree whereas Petitioner proposes “significant” experience. Patent Owner also proposes an alternative with more extensive experience in lieu of a bachelor’s degree. Although we find Petitioner’s proposed qualifications acceptable, we adopt Patent Owner’s proposed qualifications for the purposes of this Decision because they offer a wider range of qualifications that nonetheless comport with the level of ordinary skill necessary to understand and implement the teachings of the ’680 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978). Our analysis and findings herein, however, do not turn on any differences in the parties’ proposed qualifications.” slip op. at 11

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner

    “target value” is part of a command that is sent from a computing device to a server and then to a controller. The controller then receives a measurement of the fluid by a sensor and determines whether the measurement satisfies the “target value.” If the measurement does not satisfy the “target value,” further operations are undertaken. The recited operation sequence makes clear that the plain and ordinary meaning of “target value” is not as Dr. Wooley opines because the particular operating condition that a device is in at a particular time is represented by the measurement taken by the sensor, 11 Some claim language less relevant to construing “target value” was omitted for ease of reference. which the controller then uses to determine whether the measurement satisfies the “target value.” Additionally, claim 1 recites that the “target value” is sent as part of a command to the controller. The “target value” is not sent to the controller from the sensor, as might be expected if the plain and ordinary meaning of “target value” were as Dr. Wooley opines. Petitioner and Dr. Wooley’s construction would also result in “target value” meaning effectively the same thing as the measurement of the fluid by the sensor, a concept that is separately recited in claim 1 and to which the “target value” is compared. The Specification of the ’680 patent does not support Petitioner’s understanding of the plain and ordinary meaning of “target value.” Although the Specification does not recite “target value,” it recites “target state,” and describes “target state” sufficiently to understand the plain and ordinary meaning of “target” as used in “target value” and “target state.” In particular, the ’680 patent explains that “[i]n some embodiments, the process 104 includes receiving, via a network interface, from a remote user device, (e.g., via a command-center server) a command to change a state of a fluid-handling device to a target state.” Ex. 1001, 11:48–51. This portion reflects that the command is seeking to change a state of a fluid-handling device to a target state. In other words, the “target value” or “target state” is not generally “the particular operating condition that a device is in at a particular time”; rather, it is a value or state that the fluid-handling device is desired to be in, as Patent Owner and Dr. Durham explain. Additionally, just as claim 1 recites a directional component for the “target value” to be sent to the controller in a command, so too does the Specification describe a “target state” as being sent in a command from a remote user device. Thus, the Specification clearly supports the plain and ordinary meaning proposed by Patent Owner and Dr. Durham and not the plain and ordinary meaning proposed by Petitioner and Dr. Wooley. slip op. at 14

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

    “time-stamped process data, report exception therein to the remote host, and extract and transmit time-stamped process data to the remote host.” Ex. 1005, Abst. (emphases added). Almadi explains that its remote field systems must include a plurality of controller units “to issue commands to, and gather and process data from a plurality of field devices, including remote systems and instruments, . . . [and] a database server for the storage of process data retrieved from the remote subsystems and instruments.” Id. at 2:22–30 (emphases added). Based on these disclosures, we agree with Patent Owner that Petitioner has not established that Almadi discloses element [1.4]. Specifically, the teachings from Almadi identified by Petitioner refer to process data, which is data retrieved from the remote subsystems/field devices. Thus, we understand that Almadi’s teaching—of using an Ethernet switch to transmit “process data”—describes transmitting data from the remote subsystems/field devices. See Ex. 1005, 3:13–17, cited in Pet. 15. But claim 1 and particularly element [1.4], recites “sending, with the server, the target value to the network address [which identifies a controller of the fluid-handling device13] via the network,” which is different than sending process data from the field devices to the remote host or database server for storage.” slip op. at 19

  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,175,680
• Tanklogix, LLC v. SiteproInstitution denied
  PTAB · Oct 10, 2025 · IPR2025-00650 · APJ Sheila F Mcshane · IPR · Institution

  The Board denied institution because Petitioner did not show a reasonable likelihood that claims 18–32 and 34 were unpatentable over Kahn or Kahn and Gutierrez.

  RulingsInstitution decision

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

    “information presented in the petition . . . and any response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a) (2024). Upon consideration of the Petition, the Preliminary Response, and the evidence of record, we determine that Petitioner has not established a reasonable likelihood of prevailing with respect to the unpatentability of at least one claim of the ’871 patent. Accordingly, for the reasons that follow, we decline to institute an inter partes review of claims 18–32 and 34 of the ’871 patent.” slip op. at 2

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “The respective proposed levels of qualifications for a person of ordinary skill in the art are similar, with Patent Owner proposing two years of experience compared to Petitioner proposing significant experience with remotely controlling fluid-handling devices, like SCADA systems. Patent Owner also proposes more extensive experience in lieu of educational experience. While we find Petitioner’s proposed qualifications to be acceptable, we adopt Patent Owner’s proposed qualifications for the purposes of this Decision because they offer a wider range of qualifications that nonetheless comport with the level of skill necessary to understand and implement the teachings of the ’871 patent and the asserted prior art. Our analysis and findings herein, however, do not turn on any differences in the qualifications adopted.” slip op. at 8

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

    “We determine that we need not expressly construe any claim terms to resolve the parties’ disputes on the current record. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 10

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

    “actuators and the remote control of fluid handling devices, including the receipt with the user-interface module of “a user command to actuate an actuator via a presented control interface” (limitation [18.7]) and “account authorized to send commands to remotely control fluid handling devices” (limitation [18.11]). We agree with Patent Owner that the Petition fails to demonstrate that Kahn discloses or teaches these limitations because the evidence does not provide support that there is remote control of fluid handling devices or the use of a user command on a control interface to send a command to a fluid handling device, for instance. Kahn is directed to providing access to fluid sensing data and analyzing and providing visual information on that data, but we do not discern that it teaches or discloses the capability to remotely control fluid handling devices. See, e.g., Ex. 1005, code (54), 1:27–36, 2:50–3:2. More specifically, the Kahn disclosures that Petitioner repeatedly relies upon for allegedly teaching this control are deficient. See Ex. 1005, 10:62–67, 14:35– 15:2, 15:62–16:32; see also Pet. 12–14, 16–18. Kahn discloses that “the communication unit 112B can include on-site alerts such as optical (indicator lights), audible alerts (e.g., alarm sounds), tactile (e.g., vibration of the unit) or can be interfaced to an appropriate control valve for simply shutting off the supply of fluid upon the detection of emergency events, for instance.” Ex. 1005, 10:62–67. Communication unit 112B is part of the local “sensor unit,” wherein the detection conditions determined by the sensor are communicated to remote devices by communication unit 112B. See id. at 3:31–33, 5:62–6:2, 6:27–35, 7:33–37, 13:7–12, Figs. 1A–1C. Kahn discloses that the sensor units, which include communication units 112B, can be located near shut-off valves and can communicate with distant locations. See id. at 11:1–13. There are no disclosures, however, in the above passages that there is remote control of fluid handling devices, that there is a user command on a control interface that actuates an actuator, or that there is a command sent to the facility actuators via a network connection, as required in limitations [18.5]–[18.7] and [18.9]–[18.12], respectively. Rather, the disclosure indicates that the communication unit 112B includes on-site alerts and that the local (non-remote) communication unit 112B can be interfaced with the control valve.” slip op. at 18

  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,488,871
• Early Warning Services, LLC v. Intellectual Ventures II LLCInstituted
  PTAB · Feb 14, 2025 · IPR2024-01221 · APJ Iftikhar Ahmed · IPR · Institution

  Instituted review of claims 1, 2, 4, 5, 7, 8, 12, 13, 17, 19–21, 23, 24, 26, 27, 29, 30, 34, 39–41, and 43 on all asserted grounds.

  RulingsInstitution decision

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

    “We have authority to determine whether to institute an inter partes review. See 35 U.S.C. § 314 (2018); 37 C.F.R. § 42.4(a) (2022). To institute an inter partes review, we must determine that the information presented in the Petition shows “a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). Based on the information presented in the Petition and the supporting evidence, we are persuaded that there is a reasonable likelihood that Petitioner would prevail with respect to at least one of the challenged claims. Accordingly, we institute an inter partes review of the challenged claims on the grounds set forth in the Petition.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “have had “a relatively high level of skill, such as having at least a bachelor’s degree in the field of computer science and/or electrical engineering, together with 2–3 years in the financial technology sector.” Pet. 16. Petitioner adds that a person having ordinary skill in the art “would have knowledge of the commercial and scientific literature pertaining to securing transactions” and “would also have knowledge of processing devices.” Id. at 16–17 (citing Ex. 1002 ¶ 19). Patent Owner does not address the level of ordinary skill in the art in its Preliminary Response. See Prelim. Resp. Based on our review of the record before us, we determine that Petitioner’s stated level of ordinary skill in the art is reasonable because it appears consistent with the evidence of record, including the asserted prior art. Accordingly, for the purposes of this Decision, we adopt Petitioner’s definition.” slip op. at 11

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner

    “At this stage of the proceeding, we are not persuaded that the term “embedded” should be narrowly construed in the manner proposed by Patent Owner. We find nothing in the claims that requires us to import a “hidden” or a “provide security” limitation into the claims. Claim 1, for example, merely recites “the image having information embedded therein, including information related to a transaction,” and “generat[ing] an output based on the information embedded in the image.” Ex. 1001, 16:24–33 (emphasis added). The claim language therefore does not require limiting embedded information in the proposed way.” slip op. at 13

  • Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageDisclaimer not foundDecided for petitioner

    “As discussed above, disclaiming or disavowing claim scope requires a “clear and unmistakable disclaimer.” Thorner, 669 F.3d at 1367. We are not persuaded that the cited portion can be read to clearly and unmistakably disavow claim scope. The cited portion of the Specification discusses various input parameters for decoding a captured image. Ex. 1001, 6:8–10. When viewed in context, “other information” refers to other predetermined information, including “the corresponding private key,” “stored in the memory 150,” which “may be used to decrypt or decode the captured image.” Id. at 6:13–22; see also id. at 5:18–20 (private keys are stored in memory). We therefore read the Specification as merely listing possible input parameters for decoding an image and not disclaiming “the corresponding private key” from the scope of “predetermined information.” After all, the very next sentence states that “predetermined information may include, for example, address information, personal profile information, and payment account information.” Id. at 6:17–22 (emphasis added). Given the various broad categories included in “predetermined information,” we are not persuaded, for purposes of institution, that “predetermined information” excludes a private key. We further determine that this preliminary construction is sufficient to resolve the Petitioner’s anticipation and obviousness contentions presented under Petitioner’s Ground 1, and no further construction of the term is necessary.” slip op. at 18

  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 7,314,167
• Iriusrisk, Inc. v. Threatmodeler Software Inc.All claims unpatentable
  PTAB · Nov 14, 2024 · IPR2023-00821 · APJ Stephen E Belisle · IPR · Final written decision

  Claims 1 and 3 are unpatentable as anticipated by Jones; claims 2 and 4–20 are unpatentable as obvious over Jones, Zheng, and Keenan.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedOther

    “B. Level of Ordinary Skill in the Art Petitioner contends that a person of ordinary skill in the art, at the time” slip op. at 14

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “9 In arguing that Jones does not disclose a “predefined interrelated group” of threat model components, Patent Owner, in a footnote, alleges that the testimony of Petitioner’s expert, Mr. Hurlbut, is “tainted by bias” arising from his “personal and professional connections” to Petitioner. PO Resp. 27 n.4; see PO Sur-reply 21–22. Patent Owner cites no authority to show that such connections necessarily render expert testimony biased, and identifies no actual testimony of Mr. Hurlbut that it alleges to be driven only by bias. On the other hand, Petitioner submits that Mr. Hurlbut also has personal and professional connections to Patent Owner—it’s a small world. See Pet. Reply 24 (“Mr. Hurlbut personally knows Mr. Agarwal, [Patent Owner’s] CEO and inventor of the ’008 patent.”). In this case, we assess the credibility of both parties’ experts based on the plausibility of and support for their testimony, and weigh such testimony accordingly. See Consolidated Trial Practice Guide (“CTPG”) at 32 (“[T]he credibility of experts often turns less on demeanor and more on the plausibility of their theories.”), 35 (“The Board has broad discretion to assign weight to be accorded expert testimony.”); see also 84 Fed. Reg. 64,280 (Nov. 21, 2019).” slip op. at 37

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable

  Patent outcomesUS 10,699,008 unpatentable
  § 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,699,008
• Iriusrisk, Inc. v. Threatmodeler Software Inc.No claims unpatentable
  PTAB · Oct 2, 2024 · IPR2023-00656 · APJ Stephen E Belisle · IPR · Final written decision

  Claims 1–20 were not shown unpatentable because Keenan did not disclose the claimed stored threats, and the obviousness combinations did not establish the mapping limitations or a reason to combine.

  RulingsFinal written decision

  • Expert testimonyPatent owner expert creditedDecided for patent owner

    “construction of “threat,” which we find in the context of the ’366 patent does not encompass “risk.” See supra § III.D.3.a.1 (discussing “‘Threats’ versus ‘Risks’”). We agree with Patent Owner that Petitioner’s premise that “risk” includes “threats” or knowing risk allows for determination of threats is false, and belied by the parties’ experts who do not disagree on this distinction, namely that “risk” is not a “threat,” but rather represents the likelihood of a threat occurring compounded by the impact of such a threat on a given system (discussed above). See Ex. 2002, 24:3–25:5, 31:5–33:2 (Petitioner’s expert, Mr. Hurlbut, agreeing that “Risk = Likelihood x Impact”); Ex. 2009 ¶ 80; PO Sur-reply 9–10. Thus, we find unavailing Petitioner’s attempt to walk backwards from Keenan’s explicit disclosure of “risk” modeling into an anticipatory (explicit) disclosure of stored “threats” that may give rise to such risk. Viewing Keenan in the light agreed upon by the parties’ experts, where “risk” is a product of the “likelihood” of a threat occurring and the “impact” of such a threat on a given system, persuades us that although Keenan discloses “risk,” “types of risk,” and “risk ranking” (see, e.g., Ex. 1004, 16:21–63), Keenan uses such “risk” as a given value without explicitly disclosing any underlying stored threats or use thereof. See Ex. 2009 ¶ 112 (“Keenan does not disclose a system for measuring risk. The risk for objects is determined before the objects are imported into the [Integrated Object Environment]. Keenan does not make that measurement.”). Indeed, in order to “store” “threats” in “one or more databases” as recited in claim 1, such “threats” must be identified (i.e., known) at some level of specificity to the system. Petitioner does not direct us to any persuasive evidence that Keenan explicitly discloses using “threats” or “storing” an identified “threat,” let alone storing such “threat” in a database along with its association with a particular threat model component, and even more so with a threat model component that itself is correlated with a third-party diagram component as recited in claim 1.” slip op. at 32

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “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) (citation omitted). The level of ordinary skill in the art also may be reflected by the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). Neither party argues that the outcome of this case would differ based on our adoption of any particular definition of the level of ordinary skill in the art. Considering the subject matter of the ’366 patent, the background technical field, the prior art, and Petitioner’s unopposed definition of the skilled artisan, we apply the level of skill set forth above, which is consistent with the testimony of Mr. Hurlbut (Ex. 1003 ¶ 33).” slip op. at 10

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner

    “43:21–61. Contrary to Petitioner’s arguments (Pet. Reply 3–5), this “subset” feature shows that the “threats” stored in databases in claim 1 represent “potential events” that may or may not occur depending on the composition of a given system undergoing threat modeling—a system may implicate all stored threats, some of them, or even just one of them, leaving the remaining stored threats for use in preparing threat models for other systems. See PO Sur-reply 2–3 (discussing Figure 2 and arguing that “not every threat is necessarily included in the threat model”). We find the claim language itself supports interpreting “threats” as “potential events that, if they occur, can cause adverse effects to a target system.”” slip op. at 19

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner

    “Claim 1 recites, in part, “the one or more mapping files correlating the threat model components with [“third party diagram components”].” Ex. 1001, 43:30–35. Generally, from the standpoint of what claim 1 requires, the parties’ views of “mapping file” are in alignment. Claim 1 plainly recites that a “mapping file” (where a “file” in the context of computer systems is data itself) correlates data A with data B, and when construed in the context of the subject claim language, correlates threat model components (i.e., data A) with third party diagram components (i.e., data B). We find that this interpretation of “mapping files” is sufficient to resolve the controversy between the parties. See Nidec Motor, 868 F.3d at 1017.” slip op. at 39

  Patent outcomesUS 10,713,366 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,713,366
• Keysight Technologies, Inc. / Palo Alto Networks, Inc. v. Centripetal Networks, LLCSome claims unpatentable
  PTAB · Aug 5, 2024 · IPR2023-01353 · APJ Kevin F Turner · IPR · Final written decision

  Claims 1–4, 6–11, and 13–20 are unpatentable as obvious over Sourcefire and Emerging Threats; claims 5 and 12 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner, supported by Dr. Staniford’s testimony, proposes that a person of ordinary skill in the art at the time of the invention “would have had a bachelor’s degree in computer science, computer engineering, or an equivalent, and four years of industry experience,” and “would have had a working knowledge of packet-switched networking, firewalls, security policies, communication protocols and layers, and the use of customized rules to address cyber-attacks.” Pet. 16 (citing Ex. 1003 ¶¶ 23, 25). Patent Owner does not challenge the qualifications proposed by Petitioner for a person of ordinary skill in the art. See generally PO Resp. We find Petitioner’s proposal consistent with the level of ordinary skill in the art reflected by the prior art of record, see Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978), and, therefore, we adopt Petitioner’s unopposed position as to the level of ordinary skill in the art for purposes of this Decision” slip op. at 7

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Plain and ordinary meaningNo construction neededOther

    “We largely agree with Patent Owner that there is no explicit claim- construction dispute. We address Patent Owner’s issues of what ordinarily skilled artisans would have considered in creating and implementing packetfiltering rules in the discussion below. The preservation of the flow of normal legitimate network traffic without disruption is one aspect that those with a working knowledge of packet-switched networking, firewalls, security policies, communication protocols and layers, and the use of customized rules to address cyber-attacks would have considered. Nonetheless, overall, we determine that the plain and ordinary meaning of “configured to prevent an exfiltration operation,” does not require preventing all exfiltrations from occurring, nor allowing all non-exfiltration traffic, and that we need not consider the preservation of the flow of normal legitimate network traffic without disruption in the context of that claim construction. We determine that no claim terms need to be construed expressly for purposes of this Decision.” slip op. at 10

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner

    “We agree with Petitioner. The identified aspects of Emerging Threats website would have allowed interested parties to locate the rule sets, download the rule sets and make determinations regarding what rule to use in a packet-handling system, such as Sourcefire. Emerging Threats need not be indexed or broadly searchable under Petitioner’s theory of the ground of unpatentability, namely that Emerging Threats was known, one of ordinary skill in the art would have gone to Emerging Threats, and downloaded the emerging-all.rules file, guided by the documentation wiki. As such, we do not agree with Patent Owner’s argument that “the record evidence of this” slip op. at 16

  • PTAB / AIA Trials › §315(e) estoppelEstoppel appliesDecided for petitioner

    “With respect to Petitioner’s assertions of collateral estoppel, notably in the Petition at pages 47, 49, 51, 52, and 54, with respect to limitations [1a] through [1d], we agree with Petitioner that Patent Owner is estopped from asserting that Sourcefire is not prior art to the challenged claims, and also estopped from asserting that those limitations are not taught or suggested by Sourcefire, to the extent that the limitations “do not materially alter the question” of patentability relative to the elements of the claims of the ’552 patent. See Soverain Software LLC v. Victoria’s Secret Direct Brand Mgmt., LLC, 778 F.3d 1311, 1319 (Fed. Cir. 2015). Independent Claim 1 a. Petitioner’s Assertions As discussed above, we concur with Petitioner that collateral estoppel exists with respect to limitations [1a] through [1d]. Thus, we begin with a discussion of Petitioner’s assertions regarding claim limitation [1e].” slip op. at 21

  Patent outcomesUS 10,567,343 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,567,343
• Keysight Technologies, Inc. / Palo Alto Networks, Inc. v. Centripetal Networks, LLCSome claims unpatentable
  PTAB · Aug 5, 2024 · IPR2023-00446 · APJ Kevin F Turner · IPR · Final written decision

  Claims 1–4, 6–11, and 13–20 are unpatentable as obvious over Sourcefire and Emerging Threats; claims 5 and 12 were not shown unpatentable.

  RulingsFinal written decision

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner

    “We agree with Petitioner. The identified aspects of Emerging Threats website would have allowed interested parties to locate the rule sets, download the rule sets and make determinations regarding what rule to use in a packet-handling system, such as Sourcefire. Emerging Threats need not be indexed or broadly searchable under Petitioner’s theory of the ground of unpatentability, namely that Emerging Threats was known, one of ordinary skill in the art would have gone to Emerging Threats, and downloaded the emerging-all.rules file, guided by the documentation wiki. As such, we do not agree with Patent Owner’s argument that “the record evidence of this” slip op. at 16

  • PTAB / AIA Trials › §315(e) estoppelEstoppel appliesDecided for petitioner

    “With respect to Petitioner’s assertions of collateral estoppel, notably in the Petition at pages 47, 49, 51, 52, and 54, with respect to limitations [1a] through [1d], we agree with Petitioner that Patent Owner is estopped from asserting that Sourcefire is not prior art to the challenged claims, and also estopped from asserting that those limitations are not taught or suggested by Sourcefire, to the extent that the limitations “do not materially alter the question” of patentability relative to the elements of the claims of the ’552 patent. See Soverain Software LLC v. Victoria’s Secret Direct Brand Mgmt., LLC, 778 F.3d 1311, 1319 (Fed. Cir. 2015). Independent Claim 1 a. Petitioner’s Assertions As discussed above, we concur with Petitioner that collateral estoppel exists with respect to limitations [1a] through [1d]. Thus, we begin with a discussion of Petitioner’s assertions regarding claim limitation [1e].” slip op. at 21

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner

    “how and why persons of ordinary skill in the art would have modified the existing rules to prevent exfiltrations. PO Sur-reply 3. Patent Owner also argues that Petitioner’s assertions to make them “drop” rules, per Sourcefire, relies on what an administrator could have done, not what they would have been motivated to do. Id. at 4–5 (citing Pet. 57–58). We disagree with Patent Owner’s arguments. We continue to be persuaded that one of ordinary skill in the art, combining Sourcefire and Emerging Threats, would have understood that downloaded rules should be reviewed, and it would have been obvious to enable rules that such persons deemed appropriate. We find Dr. Staniford’s testimony to be persuasive on this point. See Ex. 2011, 67:10–68:24, 69:8–72; Ex. 1020, 109. We acknowledge that downloading all of a particualr ruleset from Emerging Threats and enabling all the rules, might have resulted in a drop in performance of the network appliance, but, at the same time, we are significant drop in performance, especially if a potential threat might be sufficient to warrant a minor performance hit. Patent Owner’s counsel acknowledged at oral hearing that instituting all rules of a set in “alert” mode would not result in a decrease in performance, even though some computational outlay must be engaged to engage those alert rules. See Hr’g Tr. 24:24–25:4. We are persuaded that judiciously implementing certain rules would not necessary result in a network device that is unusable. Additionally, there is testimony from Dr. Staniford that “you start out with your rules in alert because there might be false positives. I mean, for the best rule in the world, Snort wasn’t known for false positives in the rules, when you apply them to a large network.” Ex. 2011, 68:2–7. As such, we continue to determine that it would have been obvious, in combining Sourcefire with Emerging Threats, for one of ordinary skill in the art to have downloaded rules and implemented specific rules.” slip op. at 24

  • Obviousness (§103) › Motivation to combine / reasonable expectation of success › HindsightDecided for petitioner

    “Reviewing all of the evidence of record, we are persuaded that the Petition’s obviousness rationale based on Sourcefire and Emerging Threats is not guided by impermissible hindsight bias. We find persuasive Dr. Staniford’s testimony that one of ordinary skill in the art would have understood that “this rule [SID:2003021] was not directed to looking for instances of exploits or attacks (which would be invisible within the encryption) but rather was looking for exfiltration of some kind of encrypted data.” Ex. 1003 ¶ 228. As discussed by Petitioner, such recognition was also made by Mr. Marinho and Dr. Goodrich, such that the rule would have been understood to possibly prevent exfiltrations. We continue to be persuaded that Petitioner provides that a correspondence exists between the REQUIRE-TLS-1.1-1.2 operator in the ’343 Patent and SID:2003021 in Emerging Threats, in that both detect an SSL/TLS version in application packet header field values to detect exfiltration attempts using out-of-date encryption protocols. Pet. 43 (citing Ex. 1003 ¶¶ 229–230). We are ’343 Patent discloses the interruption of a similar type of exfiltration, without resorting to impermissible hindsight bias, that Patent Owner asserts. Patent Owner has provided no evidence that Petitioner used the specification of the ’343 Patent to find an applicable rule in Emerging Threats, as opposed to the testified-version provided by Dr. Staniford that he recalls “working on a similar feature where we looked for large encrypted transmissions outbound from the network on non-HTTP ports as a possible symptom of exfiltration of large amounts of data.” Ex. 1003 ¶ 228. Thus, we are not persuaded by Patent Owner’s arguments.” slip op. at 30

  Patent outcomesUS 10,567,343 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,567,343

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.