- Amazon.Com, Inc. / Amazon.Com Services LLC et al. v. Soundclear Technologies LLCAll claims unpatentablePTAB · 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 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,069,337 - Tableau Software, LLC v. Icharts LLCAll claims unpatentablePTAB · 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 · GrahamPatents in suitUS 8,271,892 - Early Warning Services, LLC v. Intellectual Ventures II LLCNo claims unpatentablePTAB · 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 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 7,314,167 - Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Co., Ltd.All claims unpatentablePTAB · 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 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,774,916 - Luxottica Of America Inc. v. E-Vision Optics, LLCSome claims unpatentablePTAB · Dec 23, 2025 · IPR2024-01030 · APJ Richard H Marschall · IPR · Final written decision
Claims 1–20, 22–31, and 33–37 are unpatentable; claims 21 and 32 were not shown unpatentable, principally because the proposed combinations failed to establish motivation to combine or the required airtight seal.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“We find that the proposals from the parties substantially overlap, such that it remains unclear whether any substantive difference exists. Notably, neither party argues that the minor differences in the proposals lead to a different outcome on any issues in this proceeding. Based on our review of the proposals, we apply Patent Owner’s proposal because it is consistent with the problems and solutions disclosed in the ’483 patent and prior art of record. See, e.g., GPAC, 57 F.3d at 1579 (approving the determination of the level of ordinary skill in the art by appeal to the references of record). The outcome of the issues addressed in this Decision would not change if we applied Petitioner’s proposal.” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“hermetically sealed” module does not encompass waterproof modules that are not airtight. First, as Petitioner admits, as a general matter, “[s]omething that is hermetically sealed is sealed so as to be airtight.” Pet. 28 (citing Ex. 1002 ¶ 103; Ex. 1010, 269); PO Sur-reply 16. Petitioner later tries to argue that the specification puts a different spin on this meaning, but still acknowledges that “[o]utside the context of the ’483 patent, a hermetic seal is sometimes equated with an airtight seal.” See Pet. Post-hearing 2–3 (citing Ex. 1002 ¶ 103; Ex. 1010, 269). Based on our review of the record, the “ordinary meaning” of “hermetically sealed” means “airtight,” and, as noted above, “airtight” is not the same thing as “waterproof.” Second, the claims support Patent Owner’s position by including dependent claims that separately claim a “hermetically sealed” module (claims 13 and 32) and a “waterproof” module (claims 15 and 34), strongly suggesting that the terms have a different scope to avoid rendering some claims redundant. See Ex. 1001, 11: 65–66, 12:3–4, 12:52–53, 12:55–56. Petitioner argues in its Post-hearing brief that claims requiring waterproof modules are “a narrower species” of hermetic seal, but fails to explain how hermetic, airtight, and waterproof seals would not fall within the scope of both claims using its approach. Pet. Post-hearing Reply 2. Petitioner’s earlier argument in its Reply also seems to cut against this position by asserting that the specification “treats hermitically sealing as conventional and equivalent to waterproofing,” with different dependent claims directed to two allegedly “equivalent” terms making little sense. Pet. Reply 14 (emphasis added). The most natural reading of the claim language suggests that “hermetically sealed” means airtight, and does not encompass modules that are waterproof but not airtight. Third, while the specification does not define “hermetically sealed” and uses “waterproof” and “hermetically sealed” in similar contexts, it does not suggest that “hermetically sealed” does not require an airtight seal consistent with its ordinary meaning. See Pet. Reply 14–15 (citing Ex. 1001, 6:47–53, 9:15–18, 10:47–50). Instead, the specification states that hermetic seals prevent water from contacting electronics, which remains consistent with Patent Owner’s position because airtight hermetic seals are also waterproof. See Ex. 1001, 6:47–53, 9:15–18. The specification also states that “[t]he module preferably houses any of the aforementioned electrical components in a substantially water-proof and wear resistant/moisture resistant environment and is preferably hermetically sealed.” Id. at 10:47–50 (emphasis added). This passage supports Patent Owner’s position by suggesting that the preferable “hermetically sealed” module goes beyond mere water resistance. See PO Sur-reply 16–17. slip op. at 16
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“2. Petitioner’s Anticipation Arguments and Evidence Petitioner argues that Howell-596 discloses every limitation of claims 1, 9, 10, 14, 15, and 18, and points to specific portions of Howell-596 and expert testimony to support its arguments. See Pet. 10–20 (citing Ex. 1002; Ex. 1003). We have reviewed the evidence and arguments of record and find that Petitioner has shown, by a preponderance of the evidence, that the limitations in claims 1, 9, 10, 14, 15, and 18 are disclosed by Howell-596 for the reasons set forth in the Petition, which we adopt as our own. See id.11 Accordingly, we find that Petitioner has established, by a preponderance of the evidence, that Howell-596 anticipates claims 1, 9, 10, 14, 15, and 18.” slip op. at 12
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentableNot shown unpatentable
“Based on these undisputed points and the parties’ arguments, we agree with Patent Owner that Petitioner fails to establish that a POSITA would have been motivated to locate Howell-596’s module housing 1700, which contains its UV detection system 1500, behind a user’s ear. Petitioner never squarely addresses the fact that placing Howell-596’s UV detection system behind a user’s ear would negatively impact its performance. Pet. 31–33; Pet. Reply 17–22. As a result, even if we accept Petitioner’s arguments and evidence as to the various advantages when placing electronics behind a user’s ear, it fails to establish a motivation to combine that requires placing Howell-596’s module housing 1700, and therefore its UV detection system, behind a user’s ear. Petitioner never acknowledges the readily apparent disadvantages of placing a UV detection system behind the ear, where it may not work at all. See Pet. 31–33. Nor does Petitioner argue that, in its combination, adjustments would be made to ensure accurate operation of Howell-596’s UV detection system. See id. Similarly, Petitioner notes that both Howell-596 and Howell-833 disclose UV sensors behind the ear of a user, but those teachings do not establish that placing Howell-596’s module behind the ear would ensure proper operation of its UV detection system housed within that module. See Pet. Reply 17–22. Instead, even though Howell-596 discloses a sensor behind the ear of a user, it maintains the UV detection system in a module toward the front of the temple, away from the ear. See id. at 18–19; PO Surreply 21–22; Ex. 1003 ¶ 205 (describing UV detection system 2102), Fig. 21 (showing UV detection system 2102 toward the front of the temple). Moreover, Petitioner’s reliance on the sensor placed behind the ear of the user in Howell-596 lacks weight because that sensor merely indicates that the device “is being worn by a user,” which serves a very different purpose than Howell-596’s UV detection system, which seeks to monitor a user’s exposure to UV radiation, a central purpose of Howell-596’s eyewear. See Ex. 1003 ¶ 205, code (57). Howell-833 also employs a UV sensor behind the ear, but Petitioner does not establish that it operates any differently than the “being worn” sensor in Howell-596, and therefore does not establish that Howell-596’s UV detection system would still work for its intended purposes in Petitioner’s proposed combination. See Pet. Reply 19–20.” slip op. at 29
Patent outcomesUS 8,708,483 mixedClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSRPatents in suitUS 8,708,483 - Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Technology (Shenzhen) Co., Ltd. And Throughtek Co., Ltd.All claims unpatentablePTAB · 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 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · GrahamPatents in suitUS 10,602,448 - Apple Inc. v. Apex Beam Technologies LLCInstitutedPTAB · Nov 14, 2025 · IPR2025-00907 · APJ Justin T Arbes · IPR · Institution
The Board instituted IPR on claims 1–20 and all asserted grounds after finding a reasonable likelihood that claim 1 is unpatentable over the three 3GPP references.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“inter partes review unless the information in the petition and 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.” See 37 C.F.R. § 42.4(a) (“The Board institutes the trial on behalf of the Director.”). For the reasons that follow, we institute an inter partes review as to claims 1–20 of the ’944 patent on all grounds of unpatentability asserted in the Petition.” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“B. Level of Ordinary Skill in the Art Petitioner argues that at the time of the ’944 patent (November 2019),2 a person of ordinary skill in the art would have had “a bachelor’s degree in electrical engineering, computer engineering, computer science, or a similar field, along with two years of experience designing or developing wireless networks, including long-term evolution LTE/4G or 5G new radio (NR) cellular technology,” where “[a]dditional years of experience could substitute for an advanced-level degree (and vice versa).” Pet. 10 (citing Ex. 1003 ¶¶ 39–44). Patent Owner “utilizes Petitioner’s proposed level of skill in the art” for its Preliminary Response. Prelim. Resp. 8. Based on the record presented, including our review of the ’944 patent and the types of problems and solutions described in the ’944 patent and cited prior art, we agree with Petitioner’s proposed definition of the level of ordinary skill in the art and apply it for purposes of this Decision.” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“C. Claim Interpretation We interpret each challenged claim using the same claim construction standard that would be used to construe the claim in a civil action under 35 U.S.C. 282(b), including construing the claim in accordance with the ordinary and customary meaning of such claim as understood by one of ordinary skill in the art and the prosecution history pertaining to the patent. 37 C.F.R. § 42.100(b). Petitioner argues that “no claim terms need be construed.” Pet. 8. Patent Owner does not propose interpretations of any claim terms in its Preliminary Response. We conclude that no express interpretation of any claim term is necessary to determine whether to institute an inter partes review in this proceeding, but encourage the parties to address various claim interpretation issues identified below during trial. See infra Section II.D.5; Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“Because we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy,’ we need not construe [a particular claim limitation] where the construction is not ‘material to the . . . dispute.’” (emphasis added) (citation omitted)).” slip op. at 11
- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedInstituted
“Patent Owner responds that Petitioner fails to show that the 3GPP-38.213-CR “document sent to [the] 3GPP email list on November 3 was available to non-3GPP members by November 5, 2019” (the alleged critical date for the ’944 patent). Prelim. Resp. 3 (emphasis omitted); see Pet. 10. According to Patent Owner, the listserv archive of emails cited by Mr. Rodermund “only shows that the November 3, 2019 email is available now—not that it was uploaded within a day of when the original email was sent”—and Mr. Rodermund provides only his uncorroborated opinion that uploads were “automatic” and “immediate.” Prelim. Resp. 5–6 (citing Ex. 1008 ¶¶ 43–63, 72–80). Patent Owner also contends that the November 2, 2019, metadata only relates to creation of 3GPP-38.213-CR and does not support Petitioner’s contention that the email was immediately uploaded. Id. at 6. Finally, Patent Owner argues that whether the subject matter of 3GPP-38.213-CR was discussed at the 3GPP meeting in October 2019 is “irrelevant,” given the date of the metadata, and has no bearing on whether the document itself was later publicly accessible. Id. at 6–7. Assessing the evidence of record collectively, however, we are persuaded that Petitioner has shown a reasonable likelihood that 3GPP-38.213-CR was publicly accessible from the ETSI email archive before November 5, 2019. Given his many years of experience with ETSI, in particular his responsibilities pertaining to management of documents like change requests, and as the “list owner” “responsible for managing and administrating” several email exploder lists, Mr. Rodermund appears to be well-qualified to testify to the matters in his declaration. See Ex. 1008 ¶¶ 7, 10–15, 47. He explains in detail how, based on his experience, emails sent” slip op. at 20
Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · GrahamPatents in suitUS 11,139,944 - Tanklogix, LLC v. Sitepro, Inc.Institution deniedPTAB · 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 · GrahamPatents in suitUS 11,726,504 - Tanklogix, LLC v. Sitepro, Inc.Institution deniedPTAB · 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 · GrahamPatents in suitUS 11,294,403 - Tanklogix, LLC v. Sitepro, Inc.Institution deniedPTAB · 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 · GrahamPatents in suitUS 11,175,680
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.