• Adc Solutions Auto LLC v. The Noco CompanyAll claims unpatentable
  PTAB · Aug 26, 2025 · IPR2024-00671 · APJ Avelyn M Ross · IPR · Final written decision

  Claims 1, 2, 15, 17, 18, 51, 54, and 57 are unpatentable as obvious over the asserted combinations of Richardson, Zhao, Yu, Paparrizos, and Dao.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “claimed priority date of July 3, 2014, would have been a person with at least a bachelor’s degree in electrical engineering or its equivalent and at least two years of experience in the field of electrical engineering including some experience with DC power supply or battery charger design[;] . . . [l]ess work experience could be compensated for by a higher level of education, such as a master’s degree, and vice versa.” Pet. 17–18 (citing Ex. 1003 ¶¶ 41–44; Ex. 1014, 10–11). Patent Owner “does not propose a different level of skill in the art.” PO Resp. 19. In light of the record before us, and for purposes of this Decision, we adopt Petitioner’s proposal regarding the level of ordinary skill in the art. Based on our review of the ’243 patent and the prior art of record, we determine that the definition offered by Petitioner comports with the qualifications a person would have needed to understand the ’243 patent and the prior art.” slip op. at 11

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

    “As neither party proposes an express construction for our consideration and because we determine that claim construction is not necessary to decide whether to institute, we do not expressly construe any claim terms. See Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (holding that “only those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy”); see also Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (citing Vivid Techs. in the context of an inter partes review).” slip op. at 12

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

    “We agree with Petitioner that the skilled artisan would have had reason to combine the teachings of Richardson and Zhao to achieve the subject matter of claim 1. For example, Petitioner contends that a person of ordinary skill in the art would have modified Richardson’s system to include the USB input circuit of Zhao “to avoid the need to supply a proprietary charger or other type of AC ‘power brick’ that would be less ubiquitous or less standardized,” increase flexibility and convenience, and cater to consumer demand for USB technology. Pet. 36 (citing Ex. 1003 ¶¶ 88–89). Petitioner further alleges that the addition of a USB input circuit would provide for an alternative where traditional charging methods are lost, damaged, or otherwise unavailable. Id. at 35 (citing Ex. 1003 ¶ 88). Thus, Petitioner has provided sufficient reasoning with rational underpinnings to explain why a person of ordinary skill in the art would have modified the teachings of the applied references. See KSR, 550 U.S. at 418.” slip op. at 21

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “Ex. 1005 ¶ 28 (emphasis added). Dr. MacCarley testifies that a person of ordinary skill in the art would have known what external battery charger could have been used and where to place it in Richardson’s system. Ex. 1044 ¶ 13. In particular, Dr. MacCarley explains that there are numerous points in the circuitry disclosed by Richardson where a charging pathway from an external battery charger (e.g. the “battery charger” that Richardson explains is “not shown”, EX1005, ¶ [0028]) could be connected to charge Richardson’s batteries. EX2010, 52:3–54:5. Any of these connection points would be a trivial modification of Richardson’s embodiment. A PHOSITA would have understood how to implement this type of well-known configuration of an external battery charger and associated charging circuitry, which would have been as simple as wiring connections to the terminal anode and cathode of the batteries. The simplicity of this connection is why it is not surprising that Richardson describes such a pathway and leaves it “not shown” in the figures. Id. We credit the testimony of Dr. MacCarley in this regard. Moreover, Dr. Fayed confirms that it was known to recharge a jump starter with a barrel charger. Ex. 2014 ¶ 23.” slip op. at 28

  Patent outcomesUS 11,584,243 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,584,243
• Adc Solutions Auto LLC v. The Noco CompanyAll claims unpatentable
  PTAB · Aug 26, 2025 · IPR2024-00577 · APJ Avelyn M Ross · IPR · Final written decision

  Claims 1, 32, 38, 39, 47, 52, and 54 are unpatentable as obvious over Richardson and Zhao and over Yu and Paparrizos.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends that a person of ordinary skill in the art, as of the claimed priority date of July 3, 2014, would have been a person with at least a bachelor’s degree in electrical engineering or its equivalent and at least two years of experience in the field of electrical engineering including some experience with DC power supply or battery charger design[;] . . . [l]ess work experience could be compensated for by a higher level of education, such as a master’s degree, and vice versa. Pet. 22 (citing Ex. 1003 ¶¶ 39–42; Ex. 1014, 10–11). Patent Owner “does not propose a different level of skill in the art.” PO Resp. 19. In light of the record before us, and for purposes of this Decision, we adopt Petitioner’s proposal regarding the level of ordinary skill in the art. Based on our review of the ’023 patent and the prior art of record, we determine that the definition offered by Petitioner comports with the qualifications a person would have needed to understand the ’023 patent and the prior art.” slip op. at 11

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

    “Petitioner submits there are no formal claim constructions necessary in this proceeding.” Pet. 23. Patent Owner “does not propose any terms need to be construed.” PO Resp. 18. As neither party proposes an express construction for our consideration and because we determine that claim construction is not necessary to decide whether to institute, we do not expressly construe any claim terms. See Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (holding that “only those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy”); see also Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (citing Vivid Techs. in the context of an inter partes review). slip op. at 12

  • Expert testimonyPetitioner expert creditedDecided for petitioner
  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable

    “We agree with Petitioner that the skilled artisan would have had reason to combine the teachings of Richardson and Zhao to achieve the subject matter of claim 1. For example, Petitioner contends that a person of ordinary skill in the art would have modified Richardson’s system to include the USB input circuit of Zhao to avoid the need to supply a proprietary charger or other type of AC ‘power brick’ that would be less ubiquitous or less standardized,” increase flexibility and convenience, and cater to consumer demand for USB technology. Pet 45–46 (citing Ex. 1003 ¶¶ 88– 89). Petitioner further alleges that the addition of a USB input circuit would provide for an alternative where traditional charging methods are lost, damaged. or otherwise unavailable. Id. at 45 (citing Ex. 1003 ¶ 88). Thus, Petitioner has provided sufficient reasoning with rational underpinnings to explain why a person of ordinary skill in the art would have modified the teachings of the applied references. See KSR, 550 U.S. at 418. We acknowledge, but are not convinced by, Patent Owner’s arguments that the nature of Richardson requires the ability to charge a high capacity battery and rapid recharging and therefore would not have led a person of ordinary skill in the art to include Zhao’s USB charging circuit in Richardson. See PO Resp. 25–31. In particular, we are not persuaded that Richardson is limited to high capacity, rapid recharging of batteries as Patent Owner suggests. Instead, Richardson broadly describes “an apparatus and method for temporarily delivering supplemental power to the electrical system of a vehicle” (Ex. 1005 ¶ 6) where “[t]he jump starter 10 may be configured for 12, 18, 24, 30, 36, 42 or 48 volts” (id. ¶ 34). According to Richardson, this may be achieved by using “two or more batteries of the same or different voltage levels . . . to achieve the voltage requirements of the vehicle to be started.” Id. By way of example, Richardson states that “if the batteries 23 are both 12-volt batteries, the system may be configured for 12- or 24-volt operation” and “[i]f the batteries 23 are 12-volt batteries and a battery 25 is a 6-volt battery, 18- or 30-volt configurations may be provided.” Id. Neither Richardson’s claims nor its specification require any particular charging capacity or charging time. See generally Ex. 1005. While a single, near-final paragraph of Richardson introduces the concept of rapid charging of the jump starter batteries to charge a fleet of vehicles, Richardson characterization is permissive or optional. For example, Richardson states The charging system of the vehicle may be used to charge the capacitors 21 and jump starter batteries 22. . . . This allows the capacitors 21 and jump starter batteries 22 to be fully recharged in about 1 to 5 minutes and can therefore start many vehicles in a row without becoming discharged. Id. ¶ 55 (emphasis added). We do not view this singular occurrence as supplanting the breadth of Richardson’s complete disclosure. Furthermore, the crux of Patent Owner’s argument is that because of Richardson’s goal of charging high capacity batteries a USB charger would require significant charging time. PO Resp. 29; Sur-reply 2–14 But, nowhere does Patent Owner allege that a USB charger would not work given sufficient time.11 See generally PO Resp. and Sur-reply. And, when faced with no alternative, the person of ordinary skill in the art must balance the trade-offs and consider charging slowly, or not at all. Medichem, S.A. v. Rolabo, S.L., 437 F.3d 1157, 1165 (Fed. Cir. 2006) (explaining that “a given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine”); see also Winner 11 Petitioner in its Reply presents some evidence of charging times using a USB input charger. Pet. Reply 4–7; Ex. 1044 ¶¶ 6–12, Appendix A. Patent Owner disputes the accuracy of Petitioner’s calculations. Sur-reply 2–11. But, whether Petitioner’s calculations are accurate or not, Petitioner’s proposed alternative modification does not remove the faster charging path and instead adds the convenience and flexibility of a secondary charging method where the primary and faster charging path is unavailable. Ex. 1044 ¶ 12.” slip op. at 21

  Patent outcomesUS 11,447,023 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,447,023
• Google LLC v. Metarail, Inc.Rehearing denied
  PTAB · Aug 25, 2025 · IPR2024-01271 · APJ Frances L Ippolito · IPR · Rehearing

  The Board denied Google’s rehearing request, leaving institution denied for claims 1–21 because the petition did not show a reasonable likelihood that Belanger-Halevy taught limitation [1B].

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “II. ANALYSIS A request for rehearing “must specifically identify all matters the party believes the Board misapprehended or overlooked, and the place where each matter was previously addressed in a motion, an opposition, a reply or sur-reply.” 37 C.F.R. § 42.71(d). The party challenging a decision bears the burden of showing the decision should be modified. Id. We address Petitioner’s rehearing arguments below.” slip op. at 2

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

    “variable data database’ as required by claim 1.” Dec. 22. We discussed and quoted extensively from Petitioner’s expert declaration of Dr. Fox and Patent Owner’s expert declaration of Dr. Malek. Id. at 22–26 (citing Ex. 1003 ¶ 94; Ex. 2001 ¶¶ 68, 70). In reviewing the parties’ submissions, we found that: Halevy’s disclosures are consistent with Patent Owner’s arguments and Dr. Malek’s testimony that Halevy does not teach mapping fields to one another or mapping of fields to one another through SO-properties. For example, as described, in Figure 6 and Halevy as a whole, Halevy does not teach or suggest mapping or linking different keywords to one another, rather the keywords are mapped to SO-properties.” slip op. at 5

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

    “Dr. Fox states that “Halevy’s disclosure of a form database in which corresponding fields from different forms on different websites map to the same SO-properties based on the SO-class identified for the form would have been recognized by a POSA as what the ’342 patent refers to as a universal variable map.” Ex. 1003 ¶ 98 (citing Ex. 1001, 17:48– 52). Based on this conclusory opinion, Dr. Fox reasons that Halevy’s form database is a “universal variable map” that must also link computer-readable field identifiers from multiple different websites to each other in the form database, because field identifiers are mapped to the same SO-properties associated with an SO-class.” Id. (emphasis omitted). We observe first that Dr. Fox’s conclusion is not supported by the cited portions of the ’342 patent. In column 17, lines 48–52, the ’342 patent explains that fields or variables may be part of forms, and variations of the data fields or variables “may include a source form, a destination form, a single source to many destination form, many sources to one destination form, cascading forms (e.g., a first form links to a second form which links to a third form, etc.) and so on.” Ex. 1001, 17:48–52. While this portion of the ’342 patent indicates that forms may include variations on fields or variables, it does not describe linking or mapping variables to one another. Ex. 2001 ¶ 75 (“[T]hat portion of the specification does not have anything to do with the definition of a “universal variable map.” Rather, it merely discusses different types of variables and fields that might appear in different types of forms.”). Dec. 28–29. We again referred to the disclosure of the ’342 patent to address evidence in the Petition relied upon by Dr. Fox to support Petitioner’s position. Id. We credited Dr. Malek’s testimony over Dr. Fox’s testimony because Dr. Malek underlined the distinctions between the asserted Belanger-Halevy prior art combination and limitation [1B]. Dec. 28–31. In short, any confusion applying the prior art Belanger-Halevy references to the claim limitation is rooted in the Petition. The Board denied the Petition because the Petition did not demonstrate a reasonable likelihood of showing that Belanger-Halevy discloses or teaches limitation [1B] of the ’342 patent.” slip op. at 5

  None
  Patents in suitUS 10,262,342
• Google LLC v. Metarail, Inc.Rehearing denied
  PTAB · Aug 25, 2025 · IPR2024-01270 · APJ Frances L Ippolito · IPR · Rehearing

  The Board denied Google’s rehearing request, leaving in place the denial of institution because the Petition did not show a reasonable likelihood that Belanger-Halevy teaches limitation [1C] of claims 1–26.

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “II. ANALYSIS A request for rehearing “must specifically identify all matters the party believes the Board misapprehended or overlooked, and the place where each matter was previously addressed in a motion, an opposition, a reply or sur-reply.” 37 C.F.R. § 42.71(d). The party challenging a decision bears the burden of showing the decision should be modified. Id. We address Petitioner’s rehearing arguments below.” slip op. at 2

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

    “[m]issing, however, from Halevy’s disclosure is any teaching or suggestion that a ‘plurality of computer-readable field identifiers’ are mapped ‘to one another’ as required by claim 1.” Dec. 22. We discussed and quoted extensively from Petitioner’s expert declaration of Dr. Fox and Patent Owner’s expert declaration of Dr. Malek. Id. at 22–26 (citing Ex. 1003 ¶ 104; Ex. 2001 ¶¶ 69, 71). In reviewing the parties’ submissions, we found that: Halevy’s disclosures are consistent with Patent Owner’s arguments and Dr. Malek’s testimony that Halevy does not teach mapping fields to one another or mapping of fields to one another through SO-properties. For example, as described, in Figure 6 and Halevy as a whole, Halevy does not teach or suggest mapping or linking different keywords to one another, rather the keywords are mapped to SO-properties. slip op. at 5

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

    “Dr. Fox states that “Halevy’s disclosure of a form database in which corresponding fields from different forms on different websites map to the same SO-properties would have been recognized by a POSA as what the ’378 patent refers to as a universal variable map.” Ex. 1003 ¶ 108 (citing Ex. 1001, 17:42–46). Based on this conclusory opinion, Dr. Fox reasons that Halevy’s form database is a “universal variable map” that must also link computer-readable field identifiers (including parameter names) from multiple different websites to each other in the form database, because the field identifiers are mapped to the same SO-properties associated with an SO-class. Id. We observe first that Dr. Fox’s conclusion is not supported by the cited portions of the ’378 patent. In column 17, lines 42–46, the ’378 patent explains that fields or variables may be part of forms and variations of these data fields or variables “may include a source form, a destination form, a single source to many destination form, many sources to one destination form, cascading forms (e.g., a first form links to a second form which links to a third form, etc.) and so on.” Ex. 1001, 17:42–46. While this portion of the ’378 patent indicates that forms may include variations on fields or variables, it does not describe any linking or mapping of variables to one another. Ex. 2001 ¶ 76 (“[T]hat portion of the specification does not have anything to do with the definition of a “universal variable map.” Rather, it merely discusses different types of variables and fields that might appear in different types of forms.”). Dec. 28–29. We again referred to the disclosure of the ’378 patent to address evidence in the Petition relied upon by Dr. Fox to support Petitioner’s position. Id. We credited Dr. Malek’s testimony over Dr. Fox’s testimony because Dr. Malek underlined the distinctions between the asserted Belanger-Halevy prior art combination and limitation [1C]. Dec. 28–31. In short, any confusion applying the prior art Belanger-Halevy references to the claim limitation is rooted in the Petition. The Board denied the Petition because the Petition did not demonstrate a reasonable likelihood of showing that Belanger-Halevy discloses or teaches limitation [1C] of the ’378 patent.” slip op. at 5

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

    “Finally, with regard to the Reply and Sur-Reply submitted by the parties (Req. 9), we note that our Decision on Institution reviewed the parties’ discussion of claim construction, but ultimately determined that “[b]ased on our review of the preliminary record, we do not need to construe any terms expressly to reach our decision.” Dec. 11. Thus, we disagree with Petitioner that we misconstrued the mapping limitation where we did not find it necessary to construe any claim term for the purposes of our institution decision because we determined the Petition deficient for failing to meet our threshold requirements as discussed above and in detail in the Decision on Institution. See Req. 1–11.” slip op. at 7

  Claim construction
  Patents in suitUS 9,633,378
• Crowdstrike, Inc. v. Gosecure, Inc.Other
  PTAB · Aug 13, 2025 · IPR2025-00068 · APJ Neil T Powell · IPR · Remand

  On remand, the Board denied institution of IPR challenging claims 1–21, applying the construction of “association” used in the parallel petition.

  RulingsRemand decision

  • RemandOther

    “The Director Review Decision determined that we should not have instituted inter partes review in both proceedings. DR 1. Instead, we “should have construed [‘association’] and instituted review of, at most, one of the petitions.” Id. at 3. Given this, the Director Review Decision vacated this proceeding’s Institution Decision and the 70 Institution Decision, remanding “to the Board panel to determine which of the two proceedings, if Board should construe the term ‘association,’” the Director Review Decision instructed us to “consider the parties’ claim construction arguments in making [our] determination.” Id. at 4. As we explain in a concurrently issued decision in IPR2025-00070, the parties have persuaded us that the correct construction of the ’872 patent claims’ recitation of “association” is the construction advanced and applied in the 70 Petition, not the narrower, possible construction addressed in this proceeding’s Petition. IPR2025-00070, Paper 28. Accordingly, we deny institution of inter partes review in this proceeding.” slip op. at 2

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

    “As we explain in a concurrently issued decision in IPR2025-00070, the parties have persuaded us that the correct construction of the ’872 patent claims’ recitation of “association” is the construction advanced and applied in the 70 Petition, not the narrower, possible construction addressed in this proceeding’s Petition. IPR2025-00070, Paper 28. Accordingly, we deny institution of inter partes review in this proceeding.” slip op. at 3

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

    “As we explain in a concurrently issued decision in IPR2025-00070, the parties have persuaded us that the correct construction of the ’872 patent claims’ recitation of “association” is the construction advanced and applied in the 70 Petition, not the narrower, possible construction addressed in this proceeding’s Petition. IPR2025-00070, Paper 28. Accordingly, we deny institution of inter partes review in this proceeding. II. ORDER It is: ORDERED that, pursuant to 35 U.S.C. § 314(a), the petitioned institution of inter partes review of the ’872 patent is denied.” slip op. at 3

  Claim construction
  Patents in suitUS 9,954,872
• Crowdstrike, Inc. v. Gosecure, Inc.Other
  PTAB · Aug 13, 2025 · IPR2025-00070 · APJ Neil T Powell · IPR · Remand

  The Board instituted inter partes review of claims 1–21 on all asserted grounds, finding a reasonable likelihood that at least claim 1 is unpatentable over Capalik.

  RulingsRemand decision

  • Director reviewOther

    “Patent Owner then filed a Request for Director Review, arguing that Petitioner did not need two petitions to challenge the ’872 patent’s claims. Paper 19. Acting Director Coke Morgan Stewart granted Director Review. Paper 25 (“Director Review Decision” or “DR Dec.”); IPR2025-00068, Paper 25. The Director Review Decision vacated this proceeding’s Institution Decision and the 68 Institution Decision, remanding “to the Board panel to Authorizing the parties to brief “how the Board should construe the term ‘association,’” the Director Review Decision instructed us to “consider the parties’ claim construction arguments in making [our] determination.” Id.” slip op. at 2

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for petitioner

    “Thus, the parties agree on the correct construction of “association.” And the parties persuade us to adopt their construction: “association” does not require any classification as authorized or unauthorized. Pet. 4–8; PO Remand Br. 1–3; Pet. Resp. Br. 1–2. This construction of “association” is the one applied in this Petition’s claim challenges, which comports with (1) our earlier determination that the Petition demonstrates a reasonable likelihood of prevailing and (2) Petitioner’s preference for this Petition over the 68 Petition. Pet. 4–8, 13–74; Dec. 10–22; Paper 3, 2; Pet. Resp. Br. 2, 5.” slip op. at 13

  • BurdenDecided for petitioner

    “D. The Merits of Petitioner’s Claim Challenges In our Institution Decision, after weighing the parties’ arguments and evidence, we determined that the Petition demonstrates a reasonable likelihood of establishing unpatentability of at least claim 1 of the ’872 patent as obvious over Capalik. E.g., Dec. 16–22. Based on all of the arguments and evidence currently of record, we remain persuaded that the Petition demonstrates a reasonable likelihood of prevailing on at least claim 1 of the ’872 patent. Indeed, as discussed above in Section II.A, the parties’ agreement on the correct construction of “association” reinforces this determination. III. CONCLUSION In view of the foregoing, having determined that Petitioner has demonstrated a reasonable likelihood of establishing at least claim 1 of the ’872 patent is unpatentable, we institute trial as to all challenged claims on all grounds stated in the Petition IV. ORDER It is: ORDERED that inter partes review of claims 1–21 of the ’872 patent is instituted on all grounds presented in the Petition; and” slip op. at 18

  • PTAB / AIA Trials › Discretionary denial › §325(d) same art / argumentsDecided for petitioner

    “institution under § 325(d). Prior to our Institution Decision, Patent Owner did not argue we should deny under § 325(d). See generally Prelim. Resp.; Pet. Resp. Br. 4. Patent Owner first raised § 325(d) while its Request for Director Review was pending, emailing the Office with a request to brief § 325(d) in view of Ecto World. Ex. 3101, 4–5. The Office did not grant that request. Id. at 1. Nor did the Director Review Decision authorize Patent Owner to brief § 325(d). It only authorized Patent Owner “to file a ten-page brief explaining how the Board should construe the term ‘association.’” DR Dec. 4. In sum, Patent Owner’s unauthorized § 325(d) arguments are waived. Moreover, even if Patent Owner had not waived its § 325(d) arguments, we find Petitioner’s § 325(d) arguments more persuasive.” slip op. at 16

  Claim constructionDiscretionary denial
  Patents in suitUS 9,954,872
• 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
• Microsoft Corporation / Apple Inc. v. Proxense, LLCAll claims unpatentable
  PTAB · Aug 4, 2025 · IPR2024-01398 · APJ Thu A Dang · IPR · Final written decision

  Claims 1, 5, 6, 8–11, 13, and 14 are unpatentable under § 103 over Giobbi ’157, Giobbi ’139, and Dua.

  RulingsFinal written decision

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) does not applyDecided for petitioner

    “Here, as Petitioner points out, “the Challenged Claims . . . do not recite ‘means for’ or ‘step for.’” Pet. Reply 1. As the Federal Circuit stated, when a disputed claim limitation does not employ “means for” language, the presumption is that each of the terms conveys sufficiently definite structure or act and, thus, is not subject to § 112(f). See Dyfan, 28 F.4th at 1367. Based on the record before us, this presumption that each of the terms is not subject to § 112(f) is not overcome. Although Patent Owner argues that “to claim a means for performing a specific computer-implemented function and then to disclose only a general purpose computer as the structure designed to perform that function, amounts to pure functional claiming” (PO Sur-reply 5), the question here is whether “means for” analysis under § 112(f) applies at all. That is, as Patent Owner acknowledges, we must determine first whether the claim is even claiming a “means for” performing a function, “and then” determine whether the structure designed to perform that function is a general purpose computer. Id. As set forth in MPEP § 2181, the three-step analysis in determining whether § 112(f) applies begins with determining whether a claim limitation uses 1) the term “means” or “step” or 2) a nonce term used as a substitute for “means” that is a generic placeholder. See MPEP § 2181(I). We agree with Petitioner’s contentions during oral argument that Patent Owner’s arguments appear to be “based on adding a third general purpose computer structure category that triggers MPF treatment not supported by any case law.” Tr. 32:10–12. Accordingly, although Patent Owner argues that “claim 1 invokes § 112[(f)]” (PO Resp. 8, 18), and then provides extensive arguments with supporting testimony from Dr. Jakobsson as to the algorithm defining “local, secured information” (id. at 10–20 (citing Ex. 2016 ¶¶ 18, 38–51, 53–55)) and “algorithm of control logic 250” (id. at 21–25 (citing Ex. 2016 ¶¶ 37, 58)), the presumption that each of the terms is not subject to § 112(f) is not overcome; thus, we decline Patent Owner’s invitation to proceed to determining the corresponding algorithm.” slip op. at 18

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

    “would have found it obvious to combine the teachings of Giobbi ’157 and Giobbi ’139 (Pet. 13–22), and furthermore combine the teachings of Dua to the teachings of Giobbi ’157 and Giobbi ’139 (id. at 23–25), citing Dr. Traynor’s testimony for support. In particular, Petitioner contends that a POSITA would have been motivated to integrate a PDK and RDC into a hybrid device by recognizing that Giobbi-157 and Giobbi-139 are “directed to similar operations,” “describe similar structures for performing those operations,” and have techniques that “are compatible with each other,” wherein combining the techniques “would have worked in the same manner already described in the references.” Id. at 21–22. Petitioner then contends that “Dua further corroborates the teachings of the Giobbi references and provides implementation details for integrating an RDC and PDK into the same device,” wherein “a POSITA would have been motivated to combine the teachings of the Giobbi references and Dua” because, at least “these references are all in the same field of endeavor.” Id. at 23–24. Patent Owner does not address separately Petitioner’s explanations and supporting evidence regarding Petitioner’s proffered reasoning to combine the references. See generally PO Resp. We have reviewed Petitioner’s explanations and supporting evidence regarding these limitations, as well as Petitioner’s proffered reasoning to combine the references, and we agree with and adopt them as our own. Pet. 13–25. Because Patent Owner does not separately address these limitations or Petitioner’s proffered reasoning for combining the references, the Petitioner’s positions regarding these limitations of independent claim 1 and the combination of references stand unopposed as a part of this trial. Based on the complete record presented, we determine that Petitioner has persuasively shown that a person of ordinary skill in the art would have combined Giobbi ’157, Giobbi ’139, and Dua as proffered in the Petition.” slip op. at 46

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “Owner’s arguments that claim 1 invokes 35 U.S.C. § 112(f), with which, as discussed above, we do not agree. In particular, although Patent Owner argues that Giobbi ’157 does not teach or describe unlocking information from a service block in exchange for an access key “as required in the challenged claims” (PO Resp. 30), and thus fails to disclose the “enabling” function as required by the claim, claim 1 merely requires that one or more of the integrated RDC and integrated PDK enables one or more of an application, a function, and a service. In Giobbi ’157, when the PDK enters a proximity zone of the RDC, the RDC requests profile data stored within the PDK for authentication, and if the profile data received from the PDK is valid, the RDC “completes the transaction.” See Ex. 1005 ¶¶ 59–63. We find availing Petitioner’s reliance of Giobbi ’157’s completion of a transaction by the PDK and the RDC to gain access as teaching “enabling access to secure physical or digital assets,” i.e., “enabling one or more of an application, a function, and service” by at least one of a PDK and RDC. See Pet. 37. Based on the complete record presented, we determine that Petitioner has persuasively shown that the proposed combination of Giobbi ’157, Giobbi ’139, and Dua teaches “one or more of the integrated RDC and integrated PDK enabling one or more of an application, a function, and a service on one or more of the hybrid device and a device associated with the external RDC,” as recited in claim 1.” slip op. at 45

  Patent outcomesUS 8,646,042 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 8,646,042
• Microsoft Corporation / Apple Inc. v. Proxense, LLCAll claims unpatentable
  PTAB · Aug 4, 2025 · IPR2024-00573 · APJ Thu A Dang · IPR · Final written decision

  Claims 1, 5, 6, 8–11, 13, and 14 are unpatentable as obvious over Giobbi ’157, Giobbi ’139, and Dua; the Board did not reach the other grounds.

  RulingsFinal written decision

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) does not applyDecided for petitioner

    “Here, as Petitioner points out, “the Challenged Claims . . . do not recite ‘means for’ or ‘step for.’” Pet. Reply 1. As the Federal Circuit stated, when a disputed claim limitation does not employ “means for” language, the presumption is that each of the terms conveys sufficiently definite structure or act and, thus, is not subject to § 112(f). See Dyfan, 28 F.4th at 1367. Based on the record before us, this presumption that each of the terms is not subject to § 112(f) is not overcome. Although Patent Owner argues that “to claim a means for performing a specific computer-implemented function and then to disclose only a general purpose computer as the structure designed to perform that function, amounts to pure functional claiming” (PO Sur-reply 5), the question here is whether “means for” analysis under § 112(f) applies at all. That is, as Patent Owner acknowledges, we must determine first whether the claim is even claiming a “means for” performing a function, “and then” determine whether the structure designed to perform that function is a general purpose computer. Id. As set forth in MPEP § 2181, the three-step analysis in determining whether § 112(f) applies begins with determining whether a claim limitation uses 1) the term “means” or “step” or 2) a nonce term used as a substitute for “means” that is a generic placeholder. See MPEP § 2181(I). We agree with Petitioner’s contentions during oral argument that Patent Owner’s arguments appear to be “based on adding a third general purpose computer structure category that triggers MPF treatment not supported by any case law.” Tr. 32:10–12. Accordingly, although Patent Owner argues that “claim 1 invokes § 112[(f)]” (PO Resp. 8, 18), and then provides extensive arguments with supporting testimony from Dr. Jakobsson as to the algorithm defining “local, secured information” (id. at 10–20 (citing Ex. 2016 ¶¶ 18, 38–51, 53–55)) and “algorithm of control logic 250” (id. at 21–25 (citing Ex. 2016 ¶¶ 37, 58)), the presumption that each of the terms is not subject to § 112(f) is not overcome; thus, we decline Patent Owner’s invitation to proceed to determining the corresponding algorithm.” slip op. at 18

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

    “vi. Combining Giobbi ’157, Giobbi ’139, and Dua Petitioner further provides detailed explanations as to why a POSITA would have found it obvious to combine the teachings of Giobbi ’157 and Giobbi ’139 (Pet. 13–22), and furthermore combine the teachings of Dua to the teachings of Giobbi ’157 and Giobbi ’139 (id. at 23–25), citing Dr. Traynor’s testimony for support. In particular, Petitioner contends that a POSITA would have been motivated to integrate a PDK and RDC into a hybrid device by recognizing that Giobbi-157 and Giobbi-139 are “directed to similar operations,” “describe similar structures for performing those operations,” and have techniques that “are compatible with each other,” wherein combining the techniques “would have worked in the same manner already described in the references.” Id. at 21–22. Petitioner then contends that “Dua further corroborates the teachings of the Giobbi references and provides implementation details for integrating an RDC and PDK into the same device,” wherein “a POSITA would have been motivated to combine the teachings of the Giobbi references and Dua” because, at least “these references are all in the same field of endeavor.” Id. at 23–24.” slip op. at 46

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “Owner’s arguments that claim 1 invokes 35 U.S.C. § 112(f), with which, as discussed above, we do not agree. In particular, although Patent Owner argues that Giobbi ’157 does not teach or describe unlocking information from a service block in exchange for an access key “as required in the challenged claims” (PO Resp. 30), and thus fails to disclose the “enabling” function as required by the claim, claim 1 merely requires that one or more of the integrated RDC and integrated PDK enables one or more of an application, a function, and a service. In Giobbi ’157, when the PDK enters a proximity zone of the RDC, the RDC requests profile data stored within the PDK for authentication, and if the profile data received from the PDK is valid, the RDC “completes the transaction.” See Ex. 1005 ¶¶ 59–63. We find availing Petitioner’s reliance of Giobbi ’157’s completion of a transaction by the PDK and the RDC to gain access as teaching “enabling access to secure physical or digital assets,” i.e., “enabling one or more of an application, a function, and service” by at least one of a PDK and RDC. See Pet. 37. Based on the complete record presented, we determine that Petitioner has persuasively shown that the proposed combination of Giobbi ’157, Giobbi ’139, and Dua teaches “one or more of the integrated RDC and integrated PDK enabling one or more of an application, a function, and a service on one or more of the hybrid device and a device associated with the external RDC,” as recited in claim 1.” slip op. at 45

  Patent outcomesUS 8,646,042 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 8,646,042
• Yealink (USA) Network Technology Co. Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.Instituted
  PTAB · Jul 29, 2025 · IPR2025-00491 · APJ Frederick C Laney · IPR · Institution

  The Board instituted IPR of claims 1–18 on all asserted grounds after finding a reasonable likelihood that claims 1, 9, and 15 are unpatentable over Ground 1.

  RulingsInstitution decision

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

    “Having considered the arguments and evidence presented by both parties at this stage of the proceeding, we are persuaded that there is a reasonable likelihood Petitioners would prevail in showing that Beel discloses or suggests to a skilled artisan a base unit having a transmitter and a first peripheral device having a receiver and at least one fixed or a configurable endpoint, where the at least one fixed or a configurable endpoint is a data source or a data sink which is able to store or emit data, of the functional device exposed or made available on the first peripheral device.” slip op. at 26

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “B. Level of Ordinary Skill in the Art Petitioners contend that a person having ordinary skill in the art would have had “Master of Science (M.S.) degree in electrical engineering or computer science, and five years of work experience in a related field. Additional educational experience could substitute for some of the work experience.” Pet. 9–10 (citing Ex. 1002 ¶¶ 36–37). Patent Owner does not dispute this position at this time. See generally Prelim. Resp. For purposes of this Decision, we adopt Petitioners’ proposed definition of a person of ordinary skill in the pertinent art, as it is consistent with the ’972 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8

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

    “We do not agree with Patent Owner that “fixed” or “configurable” requires more than what is agreed to by the parties––i.e., the characteristics and operational parameters of the endpoint are either set prior to operation or can be set during operation. We disagree that the ’972 patent defines “fixed or a configurable endpoint” as “a number of descriptive fields of the endpoint.” Rather column 8, lines 5–6, of the ’972 patent states that “[a]n endpoint is defined by a number of descriptive fields,” which speaks more about the mechanism used to establish the characteristics and operational parameters of the endpoint than it does about how “fixed” or “configurable” would be understood by a skilled artisan. And the fact that an endpoint may be defined by descriptive fields does not inform a skilled artisan that “fixed” or “configurable” requires the endpoint to allow the processing device to correctly interpret and utilize the data from the endpoint. Correctly interpreting and utilizing data may be the goal, but that goal is not turned into a requirement of the claims because the recited endpoint is fixed or configurable. Similarly, there is no basis for making that goal a requirement simply because a fixed endpoint is described as providing basic functionality and a configurable endpoint is described as being configurable by the base unit either while pairing or via the processing device. As a result, we find little merit in Patent Owner’s contention that the language “fixed or a configurable” requires a process for setting up the characteristics and operational parameters of an endpoint within a device so that the processing device can correctly interpret and utilize the data of this endpoint. Patent Owner, however, will have an opportunity during trial to further develop this contention.” slip op. at 11

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

    “Having considered the arguments and evidence presented by both parties at this stage of the proceeding, we are persuaded that there is a reasonable likelihood Petitioners would prevail in showing that Beel discloses or suggests to a skilled artisan a base unit having a transmitter and a first peripheral device having a receiver and at least one fixed or a configurable endpoint, where the at least one fixed or a configurable endpoint is a data source or a data sink which is able to store or emit data, of the functional device exposed or made available on the first peripheral device. Petitioners’ offers evidence, supported by its expert declarant, that the endpoints disclosed in Beel are either fixed, such as a mass storage unit with predefined characteristics, or configurable, such as a virtual audio interface that may change configuration based on driver instructions or use context. Pet. 32–33. As Petitioners point out, the ’972 patent itself acknowledges that Beel’s Figure 11 illustrates a system comprising a combination of vendor-specific and standard endpoints, and further interprets these endpoints to correspond to drivers and host applications used for functionality like screen sharing and audio streaming, which demonstrates a direct conceptual and structural alignment between the ’972 patent and Beel. Id. Furthermore, Petitioner’s evidence demonstrates sufficiently that Beel describes a peripheral device acting as a virtual composite device capable of emulating different functions—such as a USB audio speaker—while rerouting the data stream (e.g., RTP audio stream) over the network. Id. For instance, Petitioners’ evidence demonstrates sufficiently Beel discloses or suggests that audio data can be captured by a virtual sound card interface implemented within the peripheral device, re-encoded, and transmitted to the base unit for playback or synchronization with video content. Id. In addition, Petitioners have demonstrated sufficiently that Beel’s architecture supports the requirement that the endpoint of the functional device—whether it is a camera, microphone, or speaker—is made available through or exposed on the peripheral device. Id. The functional device’s capabilities are effectively rendered accessible to the processing device by way of the peripheral device, which acts as an intermediary. Id. Petitioners’ evidence demonstrates sufficiently that this exposure can occur via logical interfaces, such as USB Audio Class (UAC) virtual drivers, that allow the processing device to recognize and interact with these endpoints using standard protocols. Id. Furthermore, Petitioners show sufficiently Beel discloses that the peripheral device may include software that facilitates communication with and presentation of media content on the processing device, further demonstrating that the endpoints are not only present but also actively used for data transmission. Id. Patent Owner’s arguments, at least at this stage of the proceeding, fail to undermine Petitioners’ showing because they are largely just that–– attorney arguments––without sufficient evidentiary backing and because they lack sufficient clarity regarding how the recited claim language distinguishes Beel’s disclosed system. First, Patent Owner makes several representations that Petitioners misplace its reliance on certain teachings or suggests found in Beel and that Beel does not support the contention Petitioners make, but Petitioners’ positions are backed the testimony of Dr. Almeroth and Patent Owner offers no contradictory evidence for why a skilled artisan would understand Beel differently. And, suffice it to say that, when the declaration of Dr. Almeroth is considered in juxtaposition with the cited evidence from Beel, we have found declarant Dr. Almeroth sufficiently persuasive to demonstrate Petitioner is reasonably likely to prevail on the point. For example, Patent Owner simply argues that “there is no indication in Beel of using any fixed or a configurable endpoint of the functional device exposed or made available on the first peripheral device” (Prelim. Resp. 31), but declarant Dr. Almeroth states that “Beel discloses that a peripheral device can act as a ‘virtual audio device’ using a USB Audio Class (UAC) interface,” which “indicates that endpoints of the functional device are ‘exposed or made available on the first peripheral device’” (Ex. 1002 ¶ 130 (emphasis added); see also id. ¶¶ 128–129). Patent Owner’s argument, without any evidentiary support, does little to undermine the opinion testimony from Dr. Almeroth about what Beel’s teachings would indicate to a skilled artisan. Second, although Patent Owner repeatedly states that Beel fails to” slip op. at 26

  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,684,972

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.