• 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
• Oneplus Technology (Shenzen) Co., Ltd. v. Pantech CorporationInstituted
  PTAB · Oct 15, 2025 · IPR2025-00762 · APJ Scott B Howard · IPR · Institution

  The Board instituted IPR on claims 1–5 and 8–12 on all asserted grounds, finding a reasonable likelihood that claim 1 would have been obvious over Koskinen.

  RulingsInstitution decision

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

    “determine whether to institute an inter partes review. 35 U.S.C. § 314 (2024); 37 C.F.R. § 42.4(a) (2024). Inter partes review may not be instituted unless “the information presented in the petition filed under [35 U.S.C.] section 311 and any response filed under [35 U.S.C.] section 313 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). “When instituting inter partes review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.” 37 C.F.R. § 42.108(a). For the reasons set forth below, upon considering the briefing and the evidence of record, we determine that the information presented in the Petition establishes a reasonable likelihood that Petitioner will prevail with respect to at least one of the challenged claims. Accordingly, we institute inter partes review on all of the challenged claims based on all of the grounds identified in the Petition.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner argues that a person having ordinary skill in the art “would have had a bachelor’s degree in electrical engineering, computer engineering, computer science, or a related field and at least two years of practical experience with design or development of telecommunication and/or wireless communications systems, or the equivalent.” Pet. 7 (citing Ex. 1003 ¶¶ 19–21). Petitioner further argues that “[a]dditional education” slip op. at 8

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

    “For the purposes of this Decision, we need not expressly construe any claim terms.6 See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 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 10

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

    “Additionally, a person having ordinary skill in the art would have known and been familiar with information elements (IEs) that specified an RLC reordering timer value based on (1) general knowledge that IEs carried information in RRC messages and (2) that 3GPP TSs describe an IE carrying recording timer duration information for the RLC layer. See Ex. 1003 ¶ 151; Ex. 1014, 219–20. Accordingly, it would have been obvious to a person having ordinary skill in the art “that the PDCP timer information, which used similar variables as its RLC counterpart (Koskinen, ¶¶37-38), would also be carried in a PDCP configuration IE.” Ex. 1003 ¶ 151.” slip op. at 13

  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,863,573
• Google LLC / Cellco Partnership D/B/A Verizon Wireless et al. v. Headwater Research LLCAll claims unpatentable
  PTAB · Oct 1, 2025 · IPR2024-00943 · APJ Scott B Howard · IPR · Final written decision

  Claims 2–23, 26, 41–60, 63, 64, 91–152, and 155–171 are unpatentable; Rao anticipates some claims, and the stated Rao combinations render the remaining claims obvious.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner argues that a person having ordinary skill in the art “would have at least a bachelor’s degree in computer science, computer engineering, or a similar field, and approximately two years of industry or academic experience in a field related to computer software development and/or computer networking.” Pet. 2 (citing Ex. 1015 ¶¶ 50–52). Petitioner further argues that “[w]ork experience can substitute for education, and additional education can substitute for work experience.” Id. at 2–3 (citing Ex. 1015 ¶¶ 50–52). Because Petitioner’s proposed level of ordinary skill in the art is consistent with the field of the invention of the ’541 patent and not disputed by Patent Owner (see PO Resp.), we adopt Petitioner’s formulation of the person having ordinary skill in the art.” slip op. at 12

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

    “Petitioner states “[n]o terms require construction to resolve this Petition.” Pet. 3. Patent Owner does not propose any claim constructions. See PO Resp. For the purposes of this Decision, we need not expressly construe any claim terms. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 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 13

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

    “preponderance of the evidence that claim 3 was anticipated by Rao.” slip op. at 25

  Patent outcomesUS 8,589,541 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,589,541
• Google LLC / Cellco Partnership D/B/A Verizon Wireless et al. v. Headwater Research LLCAll claims unpatentable
  PTAB · Oct 1, 2025 · IPR2024-00942 · APJ Scott B Howard · IPR · Final written decision

  Claims 2–23, 26, 41–60, 63, 64, 91–152, and 155–171 are unpatentable; Rao anticipates some claims, and Rao-based combinations render the others obvious.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner argues that a person having ordinary skill in the art “would have at least a bachelor’s degree in computer science, computer engineering, or a similar field, and approximately two years of industry or academic experience in a field related to computer software development and/or computer networking.” Pet. 2 (citing Ex. 1015 ¶¶ 50–52). Petitioner further argues that “[w]ork experience can substitute for education, and additional education can substitute for work experience.” Id. at 2–3 (citing Ex. 1015 ¶¶ 50–52). Because Petitioner’s proposed level of ordinary skill in the art is consistent with the field of the invention of the ’541 patent and not disputed by Patent Owner (see PO Resp.), we adopt Petitioner’s formulation of the person having ordinary skill in the art.” slip op. at 12

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

    “Petitioner states “[n]o terms require construction to resolve this Petition.” Pet. 3. Patent Owner does not propose any claim constructions. See PO Resp. For the purposes of this Decision, we need not expressly construe any claim terms. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 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 13

  • Expert testimonyOther

    “157, and 171 are anticipated by Rao. Pet. 1, 19–39, 42. Petitioner’s arguments are supported by citations to the prior art and the testimony of Dr. Wolfe. See id. We have reviewed Petitioner’s arguments and evidence, agree with them, and, therefore, adopt Petitioner’s arguments and evidence as our own.” slip op. at 26

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed

    “anticipated by Rao. Pet. 1, 30–31, 33–42. We have reviewed Petitioner’s arguments for each of those dependent claims. See Pet. 30–31, 33–42. For each of those dependent claims, the Petition appears to only argue a theory of obvious. That is, the Petition never states that the additional limitation is disclosed by Rao. See id. For example, claim 26 depends from claim 1 and further recites “wherein the policy is based on a background service class.” Ex. 1001, 112:49–52. We reproduce Petitioner’s arguments directed to claim 26 below: Rao’s policies 520 may “define prioritization” for network packets “based on whether an application is running in the foreground or the background.” [Ex. 1002] ¶ 182; id. ¶¶ 38–43, 180, 182, 188–89, 193, Figs. 5A, 5B. Each packet “may be placed and arranged in a priority order respective to all other . . . packets to provide a packet by packet prioritization across all applications 338a-338n and . . . network packets.” Id. ¶ 191. It would have been obvious to determine and apply a policy assigning a specific priority to packets associated with background applications, supra [1e]-[1f], and Rao thus discloses or renders obvious assigning a priority to network communications based on whether they are characterized as background services (class of services associated with application(s) running in the background of client 105), EX-1015 ¶¶195-96; supra [1e], [1f]. Pet. 33–34. Although the Petition sets forth why the claim limitation would have been obvious, there is no discussion as to how the additional limitation of claim 26—policy based on background class—is disclosed in Rao. See id. Similar arguments are presented for the other claims. See Pet. 30–31, 35–42. Because the Petition does not sufficiently show how the additional limitations recited in claims 20, 26, 58, 64, 165, and 169 were disclosed by Rao, Petitioner has not shown by a preponderance of the evidence that claims 20, 26, 58, 64, 165, and 169 were anticipated by Rao.” slip op. at 28

  Patent outcomesUS 8,589,541 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,589,541
• Comcast Cable Communications, LLC v. Entropic Communications, LLCAll claims unpatentable
  PTAB · Sep 3, 2025 · IPR2024-00441 · APJ Aaron W Moore · IPR · Final written decision

  Claims 1–18 are unpatentable over Kamieniecki and Konstantinos; Petitioner did not show claims 1–18 unpatentable over Renken or Renken and Cholas because Renken is not prior art.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Level of Ordinary Skill in The Art Petitioner contends that a person having ordinary skill in the art “would have had a degree in electrical engineering or a similar discipline, and three-to-four years of experience working with television signal processing and communication 1 Because the challenged claims have an effective filing date before the effective date of the AIA, we apply the pre-AIA version of 35 U.S.C. § 103. 2 US 2005/0114879 A1, published May 26, 2005 (Ex. 1009). 3 US 2010/0120386 A1, published May 13, 2010 (Ex. 1010). 4 US 2010/0303181 A1, published Dec. 2, 2010 (Ex. 1016). 5 US 2008/0313691 A1, published Dec. 18, 2008 (Ex. 1017). 6 US 8,649,421 B2, issued Feb. 11, 2014 (Ex. 1011). systems,” and that “[a]dditional education may substitute for professional experience and significant work experience may substitute for formal education.” Pet. 30 (citing Ex. 1002 ¶¶ 40–42). “Patent Owner accepts the Petition’s [description of a person of ordinary skill] solely for purposes of responding to the Petition in this proceeding.” PO Resp. 11. Based on our review of the record before us, we determine that Petitioner’s stated level of ordinary skill in the art is reasonable because it appears consistent with the evidence of record, including the asserted prior art. Accordingly, we apply Petitioner’s definition in this Decision. B.” slip op. at 8

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

    “On the present record, we do not discern a need to construe explicitly any claim language because doing so would have no effect on our analyses and will not assist in resolving the present controversy between the parties. 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)). C.” slip op. at 9

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

    “We agree that the record provides sufficient evidence that one of ordinary skill in the art would have found it advantageous to add a multi-channel receiver to improve monitoring, as Petitioner argues. Having the ability to monitor without waiting for idle or disturbing users would be a clear advantage.” slip op. at 18

  • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner

    “We conclude that Patent Owner has not shown a sufficient nexus between the claimed invention and any product embodying the claimed invention that was successful, praised, or solved a long-felt need. Patent Owner identifies five elements allegedly required “[t]o implement MaxLinear’s Remote Spectrum Monitoring in CPE.” See PO Resp. 65. To support this, Patent Owner cites pages 5–7 of Exhibit 2009. See id.7 That exhibit, however, describes requirements for “Full Band Capture,” not MaxLinear’s “Remote Spectrum Monitoring.” To” slip op. at 31

  Patent outcomesUS 8,792,008 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 8,792,008
• 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
• DISH Network LLC v. Entropic Communications, LLCAll claims unpatentable
  PTAB · Jul 22, 2025 · IPR2024-01059 · APJ Jon M Jurgovan · IPR · Final written decision

  Claims 1 and 3 are unpatentable as obvious over Kliger and Isaksson, and over Amit, Jacobsen, and Isaksson.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for petitioner

    “Although Patent Owner points to various parts of the ’518 patent as supporting its proposal, other parts of the patent are not so limited. For example, the ’518 patent repeatedly mentions prior art patents disclosing communication techniques applied to twisted pair wiring, including discrete multi-tone (DMT) modulation and bit loading. Ex. 1001, 3:49–50, 3:67–4:2, 8:19–26. The patent further mentions that its data network overlays cable or satellite services. See, e.g., id. at 5:1–6. Thus, a POSITA would not be limited to experience only with “coaxial cables” as opposed to work involving signal processing and/or communication systems/networks more generally. The ’518 patent describes the “Technical Field” as “broadband communication networks and specifically . . . communications using coaxial cable building wiring.” Id. at 1:25–30. We find it appropriate here to use the broader statement of “broadband communication networks” as the field of a POSITA’s experience. The challenged claims of the ’518 patent relate to a “data communication network” comprising “cable wiring” with “segments of coaxial cable.” Id. at 12:16–19. This does not mean that the “cable wiring” is strictly coaxial—only that it includes segments that are.” slip op. at 11

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

    “Petitioner contends that the challenged claims are “obvious under any reasonable interpretation,” so “no express constructions are required.” Pet. 3. Patent Owner does not offer construction of any claim term, so there is no dispute over claim construction that we need to resolve. We apply the ordinary and customary meanings consistent with 37 C.F.R. § 42.100(b).” slip op. at 12

  • Obviousness (§103) › Analogous artAnalogous artDecided for petitioner

    “The ’518 patent seeks to overcome channel impairments by using probe messages to characterize the communication channel and determine optimum bit loading. Ex. 1001, code (57). These impairments include signal reflections, ISI, and signal attenuation. Pet. Reply 9–10 (citing Ex. 1001, 3:5–19). Similarly, Isaksson estimates channel characteristics by periodic transmission of a base sync frame from one transceiver to another where it is compared with a reference frame. Ex. 1013, 10. Isaksson’s channel characteristics may include attenuation, phase shifting, and variance, which are similar to the problems identified in the ’518 patent. Id. Both the ’518 patent and Isaksson address the problem of ISI by using bit loading to transmit data using sub-carriers less affected. Ex. 1001, 3:5–20; Ex. 1013, 16, 35, 79. Hence, we find the problems identified in the ’518 patent and Isaksson of how to overcome channel impairments reasonably pertinent such that Isaksson is analogous art to the ’518 patent. We find unavailing Patent Owner’s arguments that the ’518 patent is specific to in-home networks with coaxial cables and splitters whereas Isaksson is restricted to twisted pair, point-to-point networks having no intervening devices and which are located outside of homes. PO Resp. 15– 20; PO Sur-Reply 21–24. Any such differences do not change the fundamental nature of the problems of noise and interference affecting these environments. Such differences go more toward the field of endeavor than the reasonable pertinence of the problems each address. See Pet. Reply 10 (citing Donner Tech., LLC v. Pro Stage Gear, LLC, 979 F.3d 1353, 1360 (Fed. Cir. 2020)). Specifically, both the ’518 patent and Isaksson address the problem of channel impairments such as interference (e.g., ISI) and noise, and use the solution of bit loading to overcome them. See, e.g., Ex. 1001, 4:42–47; Ex. 1013, 1:3–7, 6:17–20, 16:10–16, 79:5–14. Hence, we find that the ’518 patent and Isaksson are analogous art because Isaksson is reasonably pertinent to the problems addressed in the ’518 patent notwithstanding Patent Owner’s arguments. We do not reach the question of whether the two are in the same field of endeavor.” slip op. at 17

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

    “Kliger identifies the problems of splitter reflections causing inter- symbol interference, external noise, and dynamic network conditions adversely affecting home network communications. Pet. 23–24 (citing Ex. 1007 ¶ 73; Ex. 1010, 5; Ex. 1004 ¶¶ 65–68). Isaksson teaches using multi-carrier modulation, such as DMT and OFDM, to address frequency dependent loss and noise using synchronized bit-loading based on carrier SNR. Id. at 24 (citing Ex. 1004 ¶ 69; Ex. 1013, code (57), 26:4–20). We agree with Petitioner that the combination of Kliger and Isaksson amounts to the use of known techniques (Isaksson’s synchronized bit-loading) to improve similar devices in the same way (overcoming interference and maintaining connections with other modems). Id. at 26–27 (citing KSR, 550 U.S. at 415–421). We do not agree with Patent Owner’s argument that Kliger already solves the issues that Petitioner identifies such that a POSITA would not have looked to Isaksson’s synchronized bit-loading. PO Resp. 50. Petitioner has established that Isaksson’s solutions would improve Kliger’s modulation by determining the number of bits-per-carrier based on SNR, disabling noisy carriers, and synchronizing bit loading. Pet. 23–28; Pet. Reply 23–24. Hence, a POSITA would have been motivated to improve Kliger with Isaksson. See KSR, 550 U.S. at 417 (“if a technique has been used to improve one device, and a [POSITA] would recognize that it would improve similar devices in the same way, using the technique is obvious unless its actual application is beyond his or her skill”). Patent Owner alleges that Kliger’s network is coaxial whereas Isaksson’s is point-to-point, twisted pair with no intermediary devices such as splitters which would cause the interference, noise, and attenuation that the ’518 patent addresses. PO Resp. 50–55. However, we do not agree that these alleged differences would have precluded a POSITA from making the combination of references. “Signal impairments such as reflections, noise, attenuation, and inter-symbol interference (ISI) are common challenges in nearly all communication mediums.” Ex. 1036 ¶¶ 23–27. Communication networks experience these challenges, whether point-to-point or shared, twisted pair or coaxial, in-home or out-of-home, with or without splitters. Id. As Petitioner’s expert, Dr. Williams, puts it, “a POSITA can draw from the same toolbox of known solutions to address these impairments regardless of the medium.” Id. ¶ 27. Among those solutions is Isaksson’s approach of synchronized bit-loading. Moreover, Isaksson expressly states that “[i]t should be emphasized that the present invention can be used not only with the MUSIC system as herein described, but with other multi-carrier systems employing dynamic bit loading.” Ex. 1013, 72:5–8 (emphasis added); Ex. 1004 ¶¶ 81–82. Hence, a POSITA would have been led to consider using Isaksson’s synchronized bit-loading with Kliger’s coaxial network which uses a multi-tone transmitter to determine whether to transmit power on each particular tone. See, e.g., Ex. 1007 ¶ 166; Ex. 1013 1:1–7. Further facilitating the combination is Kliger’s disclosure of using “a regular multi-tone transmitter (either OFDM or DMT) to determine whether to transmit power on each particular tone wherein tones can be silenced (which is, in effect, a form of bit-loading). See, e.g., Ex. 1007 ¶¶ 6, 166, Fig. 1; Ex. 1013, 1:1–7, 3:24–34, 4:21–25, 16:8–12. In addition, Kliger expressly recognizes and seeks to address signal impairments caused by splitters, including poor signal isolation, return loss performance, degradation at higher frequencies, and inter-symbol interference due to reflections (the same problems the ’518 patent addresses). Ex. 1007 ¶¶ 61, 73. Accordingly, a POSITA would have been motivated to combine teachings of Kliger and Isaksson. Patent Owner argues that Petitioner did not explain how a control channel would exist across a coaxial splitter’s multipath signal. PO Resp. 56–58 (citing Pet. 26; Ex. 1013, 73:4–15, 74:22–31, Fig. 33; Ex. 2002 ¶¶ 147–148). Patent Owner does not explain why it would be necessary to use Isaksson’s control channel in Kliger, particularly when Kliger has its own control channel. Ex. 1007 ¶¶ 63–64, 166. Patent Owner’s argument amounts to bodily incorporation of Isaksson in Kliger, which is not a proper approach to obviousness. See In re Keller, 642 F.2d 413, 426 (CCPA 1981). We further disagree with Patent Owner’s argument that Isaksson’s base sync frames (equivalent to the claimed probe messages) would not function in Kliger’s network. PO Resp. 58–60 (citing Pet. 26; Ex. 1007 ¶¶ 55–57; Ex. 1013, 24:8–28, Fig. 1; Ex. 2002 ¶¶ 149–154). Patent Owner’s arguments are directed toward an embodiment of Isaksson that Petitioner did not cite in its Petition. Pet. Reply 26. In any case, Patent Owner does not establish that using Isaksson’s base sync messages in Kliger’s system would have been beyond a POSITA’s skill. Id. at 25–26 (citing Ex. 1036 ¶¶ 90– 93). Patent Owner argues that Isaksson’s base sync frames would alter the principle of operation of Kliger because Kliger requires all devices to transmit fixed constellation size based on overall network characteristics rather than specific channel characteristics between each HNM. PO Resp. 60–63 (citing Ex. 1007, code (57), ¶¶ 40–44, 91, 99, Fig. 1; Ex. 1013, 3:24– 27, 20:24–25, 26:14–17, 78:5–79:5, Fig. 36; Ex. 2002 ¶¶ 155–157). Patent Owner has not established, however, that fixed constellation size is a “principle of operation” of Kliger, or that Kliger would require substantial reconstruction or redesign to incorporate variable constellation sizes. See In re Ratti, 270 F.2d 810, 813 (CCPA 1959). We agree with Dr. Williams that a POSITA would have sought to improve Kliger with Isaksson’s techniques. Ex. 1036 ¶ 95.” slip op. at 19

  Patent outcomesUS 7,295,518 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 7,295,518

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.