• Amazon.Com, Inc. / Amazon.Com Services LLC et al. v. Soundclear Technologies LLCAll claims unpatentable
  PTAB · Jul 27, 2026 · IPR2025-00565 · APJ Michael R Zecher · IPR · Final written decision

  Claims 1–5 are unpatentable because Amazon showed they are anticipated by Shin; the Board did not reach Amazon’s contingent obviousness ground over Shin.

  RulingsFinal written decision

  • BurdenOther

    “Written Decision under 35 U.S.C. § 318(a) as to the patentability of claims 1–5 of the ’337 patent. For the reasons we identify below, we hold that Amazon has demonstrated by a preponderance of the evidence that these claims are unpatentable.” slip op. at 2

  • Skill levelOther

    “2. Level of Skill in the Art In determining whether an invention would have been obvious, we” slip op. at 18

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

    “1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableNot shown unpatentableMixed

    “1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17

  Patent outcomesUS 11,069,337 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,069,337
• Tableau Software, LLC v. Icharts LLCAll claims unpatentable
  PTAB · May 7, 2026 · IPR2024-01387 · APJ Iftikhar Ahmed · IPR · Final written decision

  Claims 1–16 are unpatentable under the instituted obviousness grounds, including Becerra, the QlikView Manuals, and combinations with other references.

  RulingsFinal written decision

  • ExcludeMotion to exclude, grantedMotion to exclude, deniedGranted in part

    “why it is trustworthy and how it archives dates by which the webpages were accessible, as this is an information resource on which librarians reasonably rely. See FED. R. EVID. 703. We agree with Petitioner that Dr. Hall-Ellis does have personal knowledge of the facts stated in the remaining testimony (e.g., what she actually downloaded from websites), and that FEDERAL RULE OF EVIDENCE 602 is inapplicable to her testimony offered as an expert. See Pet. Opp. 5–6 (citing Ex. 1030 ¶¶ 26, 29–32, 35, 37–39). We find her testimony to be relevant to the issues presented and specifically to whether the QlikView documents were publicly accessible. We also find no danger that the testimony would confuse the issues or mislead the Board or present unfair prejudice to Patent Owner. Accordingly, we deny Patent Owner’s Motion as to the remaining portion of Dr. Hall-Ellis’s declaration.” slip op. at 92

  • Strike new argumentNew argument disregardedGranted

    “FURTHER ORDERED that Petitioner’s Motion to Strike portions of Patent Owner’s Reply on its Motion to Exclude (Paper 32) is granted; and” slip op. at 102

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable

    “1. Motivation to Combine Becerra and Couckuyt Petitioner argues that a person of ordinary skill in the art would have been motivated to combine the teachings of Becerra and Couckuyt because such a person would have recognized that Couckuyt discloses useful techniques of assigning data to Becerra’s charts, including assigning data to each axis. Pet. 34 (citing Ex. 1005 ¶¶ 19, 52, Fig. 5; Ex. 1003 ¶ 224). Petitioner contends that Couckuyt discloses associating data from a “spreadsheet document” with a chart, such as a “bar graph.” Id. at 35 (citing Ex. 1006, 6:1–37; Figs. 3a, 3c). below. Petitioner’s annotations to Figure 4 identify “Drop Zones” in red and “Data Fields” in Blue. Id. at 36. Petitioner contends Couckuyt discloses a “drag-and-drop user interface (DDUI) . . . associated with a data source, such as the two-dimensional data source 300,” and Figure 4 illustrates the DDUI permitting “value data fields and the characteristic data fields . . . to be dragged and dropped into drop zones.” Id. at 35–36 (citing Ex. 1006, 7:10–13). Petitioner contends that a “primary benefit of the charting DDUI is that the user can quickly change the data that is being presented in the chart,” and using Couckuyt’s techniques, a user can “quickly change the data” and see the desired effects. Id. at 36 (citing Ex. 1006, 1:18–19; Ex. 1003 ¶ 228). Petitioner contends that when Becerra’s control panel includes multiple charts, Couckuyt’s techniques would allow dragging-anddropping data from a data source to multiple charts, and would simplify the process of assigning data to multiple control panel components. Id. at 36–37 skill in the art would have also had a reasonable expectation of success combining Becerra with Couckuyt because the combination would amount to nothing more than incorporating Couckuyt’s well-known drag-and-drop techniques into Becerra’s system. Id. at 37 (citing Ex. 1003 ¶¶ 229–231). Patent Owner responds that Couckuyt focuses on selecting a data icon that corresponds to dragging and dropping data fields, not dragging and dropping data, while Becerra teaches that selecting various data ranges from the spreadsheet is desirable. PO Resp. 36–37 (citing Ex. 1004 7:48–52; Ex. 2001 ¶ 146). According to Patent Owner, a person of ordinary skill in the art would not have been motivated to merely select data fields that do not limit the selected data in any way. Id. Patent Owner further argues Becerra’s method of binding components to a spreadsheet range and extracting formulas from a spreadsheet teaches away from the multiple chart generation scheme of Couckuyt that uses drag and dropping of data fields. Id. at 37. According to Patent Owner, Couckuyt is directed to the need for a charting DDUI that can generate multiple charts at the same time and such a need does not exist in Becerra which in turn is focused on creating a control panel that is an interactive graphics simulation. Id. (citing Ex. 1004, 1:66–67, 2:5–8; Ex. 1005 ¶ 11; Ex. 2001 ¶ 148). Based on our review of the complete record, we determine that” slip op. at 31

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

    “2. Whether QlikView Manuals Qualify as Prior Art Petitioner argues that “the QlikView Manuals describe a well-known system and are printed publications available to the public at least by July 8, 2008.” Pet. 7–9. Petitioner offers ample evidence to demonstrate the QlikView Manuals were publicly accessible by July 8, 2008. See id. (citing Ex. 1008; Ex. 1009; Ex. 1014–1023; Ex. 1003 ¶ 129–140; Ex. 1030;11 Ex. 1068 ¶¶ 4–7; Ex. 1032; Ex. 1033). Petitioner contends in 2008, QlikView was a well-known software product sold by QlikTech International AB (“QlikTech”). Id. at 8 (citing Ex. 1003 ¶ 129; Ex. 1030 ¶ 23; Ex. 1068 ¶¶ 4–7). Petitioner asserts that QlikTech announced that QlikView version 8.50 was scheduled for release on June 30, 2008, and QlikTech’s website added the “QlikView 8.50” hyperlink by July 8, 2008. Id. (citing Ex. 1003 ¶¶ 129–131; Ex. 1022, 1; Ex. 1068 ¶ 7). Petitioner contends that, as of July 8, 2008, a person of ordinary skill in the art would have understood that they could view the QlikView Manuals in the installation package. Id. (citing Exs. 1014–1017; Ex. 1003 ¶¶ 131–132; Ex. 1068 ¶ 7). Petitioner further contends that the QlikView Manuals were also available on QlikTech’s website as of this 11 As discussed below (see infra § IV.A), we grant Patent Owner’s Motion to Exclude as to certain portions of Exhibit 1030 and do not give them any weight. However, we deny Patent Owner’s Motion as to the remaining portions of Dr. Hall-Ellis’s testimony as well as Ms. Lofton’s testimony and various other exhibits proffered by Petitioner to show public accessibility of the QlikView manuals as of July 8, 2008. QlikView 8.50 was published on July 8, 2008. Id. at 8–9 (citing Exs. 1008, 1009, 1017, 1059, 1060; Ex. 1030 ¶¶ 29, 37). In its Patent Owner Response, Patent Owner does not contest that the QlikView Manuals were published and publicly available by July 8, 2008. PO Resp. 50 n.2 (noting only that Patent Owner intends to move to exclude evidence Petitioner relies on to establish the publication date for QlikView Manuals); Tr. 45:3–19. We are persuaded that Petitioner has shown by a preponderance of the evidence that the QlikView Manuals were publicly available as of July 8, 2008.12” slip op. at 50

  Patent outcomesUS 8,271,892 unpatentable
  § 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,271,892
• Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Co., Ltd.All claims unpatentable
  PTAB · Jan 23, 2026 · IPR2024-01192 · APJ Michael J Strauss · IPR · Final written decision

  Claims 1–10 and 16 are unpatentable as obvious over the asserted combinations of the Lorex Manual or Lorex Video with the identified references.

  RulingsFinal written decision

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date awardedDecided for petitioner

    “Patent Owner does not dispute any of Petitioner’s contentions as to the effective filing date, stating in agreement with Petitioner’s asserted Effective Filing Date of the Challenged Claims that “[t]he ’916 Patent claims a priority of a provisional application 61/924,240 filed on January 7, 2014.” PO Resp. 8. Given that the parties are in agreement on the January 7, 2014, effective filing date, we similarly use January 7, 2014, as the effective filing date of the challenged claims for purposes of this Decision.” slip op. at 4

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “II. ANALYSIS A. Level of Ordinary Skill in the Art Relying on the testimony of Vlad Kardashov, Petitioner proposes that a person of ordinary skill in the art at the time of the invention of the ’916 patent “would have had a bachelor’s degree in electrical engineering and two 7 US 2012/0198040 A1, published August 2, 2012 (Ex. 1011, “Kuo”). 8 The subject ’916 patent claims priority to Kuo as a continuation-in-part of that earlier filed application. Ex. 1001, code (63). 9 Lorex Technology Inc., “How to set up remote access for DVR using - Lorex Stratus Connectivity” (June 18, 2013), available at https://www. youtube.com/watch?v=fMPRi9WFuTM (Ex. 1012, the “Lorex Video”). 10 US 2012/0113265 A1, published May 10, 2012 (Ex. 1013, “Galvin”). years of work experience with network and communication technologies.” Pet. 8 (citing Ex. 1003 ¶¶ 12–14). Patent Owner does not contest Petitioner’s proposal or provide a proposal of its own. On the complete record, we adopt Petitioner’s description of the level of ordinary skill in the art, as it is consistent with the technology described in the ’916 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8

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

    “Petitioner asserts that “no claim elements need a formal construction for purposes of resolving controversies in this proceeding.” Pet. 9 (citing Ex. 1003 ¶¶ 43–44; Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011), Google Inc. v. Intellectual Ventures II LLC, 701 Fed. Appx. 946, 956 (Fed. Cir. 2017)). Petitioner states “[a]ll claim terms should be construed according to the Phillips standard.” Id. (citing Phillips, 415 F.3d at 1303; 37 C.F.R. § 42.100). Patent Owner presents no proposed claim constructions. 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 9

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityReference is prior artPriority date awardedDecided for petitioner

    “that Patent Owner fails to demonstrate that the Lorex Manual was based on a disclosure made by the inventor or joint inventor or by another who obtained the subject matter disclosed directly or indirectly from the inventor or a joint inventor. The Lorex Manual is relied on under Ground 1A, exclusively or in the alternative to or in combination with Kim, for all claim elements. Pet. 9– 31. Patent Owner fails to demonstrate that this subject matter was disclosed to Lorex by ThroughTek, much less by one of the inventors of the ’916 Patent.” slip op. at 22

  Patent outcomesUS 9,774,916 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,774,916
• Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Technology (Shenzhen) Co., Ltd. And Throughtek Co., Ltd.All claims unpatentable
  PTAB · Dec 15, 2025 · IPR2024-01193 · APJ David C Mckone · IPR · Final written decision

  Claims 1–3, 5, 7–13, 15–19, and 23–25 are unpatentable: claims 1, 7, 8, 10, 11, 15, 16, 18, 19, and 23–25 as anticipated by Zhang; all challenged claims also as obvious over at least one …

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “person of ordinary skill in the art “would have had a bachelor’s degree in electrical engineering and two years of work experience with network and communication technologies.” Pet. 5 (citing Ex. 1003 ¶¶ 13–15). Patent Owner does not contest Petitioner’s proposal or provide a proposal of its own. On the complete record, we adopt Petitioner’s description of the level of ordinary skill in the art, as it is consistent with the technology described in the ’448 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 11

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededTerm construed board ownMixed

    “construction of “feature flag” is inconsistent with the language of claim 8, which states that “the feature flag indicates that the running state of the second apparatus is the sleep state.” Petitioner also argues that Patent Owner’s proposal is not supported by claim 24, which depends from claim 23 and states that “the feature flag is located at a header of the sleep login packet.” Id. at 3. We agree with Petitioner. The plain language of claim 8 states what a feature flag indicates. Claim 24 recites where the feature flag is located. Neither claim suggests any of Patent Owner’s additional limitations.” slip op. at 13

  • Expert testimonyPetitioner expert creditedDecided for petitioner
  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

    “[A] prior art reference will anticipate if it ‘disclose[s] each and every element of the claimed invention . . . arranged or combined in the same way as in the claim.’” Blue Calypso, LLC v. Groupon, Inc., 815 F.3d 1331, 1341 (Fed. Cir. 2016) (quoting In re Gleave, 560 F.3d 1331, 1334 (Fed. Cir. 2009) (alteration by Federal Circuit)). “However, a reference can anticipate a claim even if it ‘d[oes] not expressly spell out’ all the limitations arranged or combined as in the claim, if a person of skill in the art, reading the reference, would ‘at once envisage’ the claimed arrangement or combination.” Id. (quoting Kennametal, Inc. v. Ingersoll Cutting Tool Co., 780 F.3d 1376, 1381 (Fed. Cir. 2015) (alteration by Federal Circuit); In re Petering, 301 F.2d 676, 681 (CCPA 1962)). For the reasons explained below, we are persuaded that Petitioner has shown, by a preponderance of the evidence, that claims 1, 7, 8, 10, 11, 15, 16, 18, 19, and 23–25 are anticipated by Zhang. slip op. at 16

  Patent outcomesUS 10,602,448 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 10,602,448
• 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
• Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Co., Ltd.All claims unpatentable
  PTAB · Aug 4, 2025 · IPR2024-00509 · APJ Michael J Strauss · IPR · Final written decision

  Claims 1–4 and 6–19 are unpatentable as obvious over Throughtek-2012 and the Lorex Video; claims 1–3, 6, 10, 12–14, 17, and 18 are also unpatentable under two other grounds.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “II. ANALYSIS A. Level of Ordinary Skill in the Art Relying on the testimony of Dr. Bims, Petitioner proposes that a person of ordinary skill in the art at the time of the ’842 patent would have been a person having a bachelor’s degree in electrical engineering and two years of work experience with network and communication technologies. Pet. 11 (citing Ex. 1001 ¶¶ 15–16). Patent Owner does not provide any proposed qualifications for a person 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) (citation omitted). The level of ordinary skill in the art is also reflected by the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). We adopt the assessment offered by Petitioner as it is consistent with the ’842 patent and the asserted prior art.” slip op. at 7

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

    “Petitioner asserts “no claim elements need a formal construction for purposes of resolving the controversy in this proceeding.” Pet. 11 (citing Ex. 1001 ¶ 55; Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011); Google Inc. v. Intellectual Ventures II LLC, 701 Fed. Appx. 946, 956 (Fed. Cir. 2017)). Petitioner states “[a]ll claim terms should be construed according to the Phillips standard.” Id. (citing Phillips, 415 F.3d at 1303; 37 C.F.R. §42.100). Patent Owner presents no proposed claim constructions. 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 8

  • Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner

    “In addition, “[n]egative claim limitations are adequately supported when the specification describes a reason to exclude the relevant limitation. Such written description support need not rise to the level of disclaimer.” Santarus, Inc. v. Par Pharm., Inc., 694 F.3d 1344, 1351 (Fed. Cir. 2012). A reason to exclude an element may be found in “statements in the specification expressly listing the disadvantages of using” that element. Santarus, 694 F.3d at 1351. Another reason to exclude may be when the specification “distinguishes among” the element and alternatives to it. Inphi Corp. v. Netlist, Inc., 805 F.3d 1350, 1357 (Fed. Cir. 2015). As the Federal Circuit explained, “[t]he common denominator of these examples [(i.e., the reasons to exclude an element)] is disclosure of the element.” Novartis Pharm. Corp. v. Accord Healthcare, Inc., 38 F.4th 1013, 1017 (Fed. Cir. 2022). More particularly, “[s]ilence is generally not disclosure.” Novartis, 38 F.4th at 1017; see also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1288 (Fed. Cir. 2021). Accordingly, “the written description requirement cannot be met through simple disregard of the presence or absence of a limitation.” Novartis, 38 F.4th at 1017. Our reviewing court further notes that “it is possible that the written description requirement may be satisfied when a skilled artisan would understand the specification as inherently disclosing the negative limitation.” Novartis, 38 F.4th at 1017 (emphasis added, footnote omitted). Thus, “it is a question whether the application necessarily discloses that particular device . . . A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997) (quoting Jepson v. Coleman, 314 F.2d 533, 536 (CCPA 1963)) (emphasis added).” slip op. at 20

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportDecided for petitioner

    “In addition, “[n]egative claim limitations are adequately supported when the specification describes a reason to exclude the relevant limitation. Such written description support need not rise to the level of disclaimer.” Santarus, Inc. v. Par Pharm., Inc., 694 F.3d 1344, 1351 (Fed. Cir. 2012). A reason to exclude an element may be found in “statements in the specification expressly listing the disadvantages of using” that element. Santarus, 694 F.3d at 1351. Another reason to exclude may be when the specification “distinguishes among” the element and alternatives to it. Inphi Corp. v. Netlist, Inc., 805 F.3d 1350, 1357 (Fed. Cir. 2015). As the Federal Circuit explained, “[t]he common denominator of these examples [(i.e., the reasons to exclude an element)] is disclosure of the element.” Novartis Pharm. Corp. v. Accord Healthcare, Inc., 38 F.4th 1013, 1017 (Fed. Cir. 2022). More particularly, “[s]ilence is generally not disclosure.” Novartis, 38 F.4th at 1017; see also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1288 (Fed. Cir. 2021). Accordingly, “the written description requirement cannot be met through simple disregard of the presence or absence of a limitation.” Novartis, 38 F.4th at 1017. Our reviewing court further notes that “it is possible that the written description requirement may be satisfied when a skilled artisan would understand the specification as inherently disclosing the negative limitation.” Novartis, 38 F.4th at 1017 (emphasis added, footnote omitted). Thus, “it is a question whether the application necessarily discloses that particular device . . . A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997) (quoting Jepson v. Coleman, 314 F.2d 533, 536 (CCPA 1963)) (emphasis added).” slip op. at 20

  Patent outcomesUS RE47,842 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
• PLR Worldwide Sales Ltd. v. Flip Phone Games, Inc.Some claims unpatentable
  PTAB · Apr 24, 2025 · IPR2024-00209 · APJ Scott B Howard · IPR · Final written decision

  Claims 1–11 and 13–19 are unpatentable as obvious over Ho and Aoki; claims 12 and 20 were not shown unpatentable over Jiau and Aoki or Jiau and Kim.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner argues for a slightly different level of ordinary skill in the art: “a bachelor’s degree in electrical engineering, computer engineering, computer science, or a similar field, along with one to two years of experience developing or programming video games or video game systems, or similar types of computer systems.” PO Resp. 2 (citing Ex. 2006 ¶ 29). Patent Owner further argues that the person having ordinary skill in the art “may have additional education that might substitute for some of the experience, and additional experience might substitute for some of the educational background.” Id. (citing Ex. 2006 ¶ 29). According to Patent Owner, Petitioner’s proposal does not require experience in programming video games. Id. at 3. However, Patent Owner states, “[t]his difference does not materially affect the analysis presented below.” Id. We see very little difference between the parties’ respective proposals. We adopt Patent Owner’s marginally more specific proposal. Additionally, because we would reach the same conclusions under Petitioner’s proposal, we agree with Patent Owner that this does not affect our analysis.” slip op. at 9

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

    “Patent Owner argues that the plain and ordinary meaning of “downloading” excludes “real-time fetching of data by a client from a server system.” PO Resp. 34; see also PO Sur-reply 16–17; Tr. 32:22–34:7. Because we need not expressly construe any claim terms, we do not construe any terms of the ’662 patent. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co. Matal, 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we 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 11

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

    “date of the ’662 patent, Ho is not a “printed publication” within the meaning of 35 U.S.C. § 311(b). PO Resp. 30–33; PO Sur-reply 15–16. The Federal Circuit has rejected this argument, holding that: a published patent application is, by its literal terms, a “printed publication.” So, when § 311(b) permits IPR challenges based upon “prior art . . . printed publications,” it includes within its literal scope challenges based upon a published patent application. And, by virtue of § 102(e)(1), a published patent application—this specific type of “printed publication”—is deemed prior art as of its filing date. Therefore, the plain language of §§ 311(b) and 102(e)(1) permits IPR challenges based upon published patent applications, and such published patent applications can be deemed prior art in IPRs as of their filing date. Lynk Labs, Inc. v. Samsung Elecs. Co., 125 F.4th 1120, 1127 (Fed. Cir. 2025). Thus, Petitioner asserts permissible grounds of unpatentability under 35 U.S.C. § 311(b) by arguing that claims 1–20 are unpatentable under 35 U.S.C. § 103(a) on the basis of Ho, which is a prior art printed publication, and either Aoki or Kim.” slip op. at 11

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

    “A person having ordinary skill in the art would have combined Aoki’s teaching of using user-identification information as part of the request for an advertisement with Ho’s system, which also teaches a client device sending information to a server to request hot spot information, such as advertisements. See Ex. 1003 ¶¶ 103–107, 111, 114, 117. Because both Ho and Aoki are directed to improvements in game design and monetization from using advertisements (id. ¶ 106; Ex. 1004, 1:26–28; Ex. 1005 ¶¶ 6–8), a person having ordinary skill in the art would have looked at both Ho and Aoki and combined the relevant features with a reasonable expectation of success (Ex. 1003 ¶¶ 103, 106, 117). A person having ordinary skill in the art would have appreciated that using Aoki’s teaching of sending user-identification information with Ho, which includes sending information with a request for information relating to interactive information elements (hot spots), allows for targeted advertisements, which was a known advantage in advertising. Id. ¶ 117; Ex. 10089 ¶¶ 54–55 (describing advantages of targeted advertising).” slip op. at 26

  Patent outcomesUS 9,427,662 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,427,662

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.