• 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
• 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
• Microsoft Corporation v. Proxense, LLCAll claims unpatentable
  PTAB · Jul 17, 2025 · IPR2024-00407 · APJ Thu A Dang · IPR · Final written decision

  Claims 1–20 are unpatentable under § 103 over Giobbi ’157, Giobbi ’139, and Dua; the Board did not reach the other three 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

    “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 3), the question here is whether “means for” analysis under 112(f) applies at all. As Petitioner explained during oral arguments, the parties agree that “the law has been consistent and clear” that “the proper framework for an MPF [means-plus-function] construction analysis consists of two steps,” with the first being “determin[ing] whether the limitation is or is not an MPF limitation,” and “[o]nly if the limitation is determined or deemed to be an MPF limitation . . . do you then proceed to step 2 . . . where you analyze the specification of the patent to identify structure corresponding to the MPF limitation.” Tr. 17:22– 18:5. That is, as Petitioner pointed out, “all of the case law identified by [Patent Owner] limits this general purpose computer analysis to the second step of the MPF analysis.” Id. at 19:5–7. Thus, although Patent Owner argues that “[s]ince claim 1 invokes § 112[(f)]” (PO Resp. 9, 22), and then provides extensive arguments with supporting testimony from Dr. Jakobsson as to the “algorithm defining ‘local, secured information’” (id. at 9–19 (citing Ex. 2014 ¶¶ 18, 36–37, 40–54)) and “algorithm of control logic 250” (id. at 19–22 (citing Ex. 2014 ¶¶ 55–57)), 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 16

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

    “would have found it obvious to combine the teachings of Giobbi ’157 and Giobbi ’139 (Pet. 12–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 20–21. 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. Patent Owner does not address separately Petitioner’s explanations and supporting evidence regarding the remaining limitations in claim 1, or regarding the 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. 29–33. 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 the proposed combination of Giobbi ’157, Giobbi ’139, and Dua teaches the remaining limitations of claim 1, and that a person of ordinary skill in the art would have combined these references.” slip op. at 39

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

    “stored within the external PDK for authentication, wherein, if the profile data received from the external PDK is valid, the RDC completes the transaction, which includes enabling access to secure physical or digital assets. See Ex. 1005 ¶¶ 61, 63, Fig. 4. We are persuaded by Petitioner’s reliance on Giobbi ’157’s “transaction” wherein its completion “enabl[es] access to secure physical or digital assets,”’ i.e., “enables one or more of an application, a function, and service.” See Pet. 34. Based on the complete record presented, we determine that Petitioner has persuasively shown that the proposed combination of Giobbi ’157 in view of Giobbi ’139 and Dua teaches “one or more of (a) the integrated, RDC . . . and (b) the local, secured information stored by the integrated, secure memory enables one or more of an application, a function, and a service,” as recited in claim 1.” slip op. at 38

  Patent outcomesUS 9,679,289 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,679,289
• Microsoft Corporation v. Proxense, LLCAll claims unpatentable
  PTAB · Jul 17, 2025 · IPR2024-00405 · APJ Thu A Dang · IPR · Final written decision

  Claims 1–20 are unpatentable under § 103 over Giobbi ’157, Giobbi ’139, and Dua; the Board did not reach the other instituted 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

    “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 3 (emphasis omitted)), the question here is whether “means for” analysis under 112(f) applies at all. As Petitioner explained during oral argument, the parties agree that “the law has been consistent and clear” that “the proper framework for an MPF [means-plus-function] construction analysis consists of two steps,” with the first being “determin[ing] whether the limitation is or is not an MPF limitation,” and “[o]nly if the limitation is determined or deemed to be an MPF limitation . . . do you then proceed to step 2 . . . where you analyze the specification of the patent to identify structure corresponding to the MPF limitation.” Tr. 17:22–18:5. That is, as Petitioner pointed out, “all of the case law identified by [Patent Owner] limits this general purpose computer analysis to the second step of the MPF analysis.” Id. at 19:5–7. Thus, although Patent Owner argues that “[s]ince claim 1 invokes § 112[(f)]” (PO Resp. 8, 21), and provides extensive arguments with supporting testimony from Dr. Jakobsson as to the “algorithm defining ‘local, secured information’” (id. at 8–20 (citing Ex. 2014 ¶¶ 18, 36–37, 40–54)) and “algorithm of control logic 250” (id. at 20–22 (citing Ex. 2014 ¶¶ 55–57)), 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 16

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

    “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. 12–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 20–21. 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. Patent Owner does not address separately Petitioner’s explanations and supporting evidence regarding the remaining limitations in claim 1, or regarding the 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. 26–27, 29–33. 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 the proposed combination of Giobbi ’157, Giobbi ’139, and Dua teaches the remaining limitations of claim 1, and that a person of ordinary skill in the art would have combined these references. v. Claim 1 Conclusion Based on the complete record presented, Petitioner has shown that the proposed combination of Giobbi ’157, Giobbi ’139, and Dua teaches all limitations of claim 1. Thus, we determine that Petitioner has shown by a preponderance of the evidence that the subject matter of claim 1 would have been obvious over the proposed combination of Giobbi ’157, Giobbi ’139, and Dua.” slip op. at 39

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

    “Giobbi ’157 teaches, for example, an RDC requesting profile data stored within the external PDK for authentication, wherein if the profile data received from the external PDK is valid, the RDC completes the transaction, which includes enabling access to secure physical or digital assets. See Ex. 1005 ¶¶ 61, 63, Fig. 4. We are persuaded by Petitioner’s reliance on Giobbi ’157’s “transaction” wherein its completion “enabl[es] access to secure physical or digital assets,”’ i.e., “enables one or more of an application, a function, and service.” See Pet. 34. 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 (a) the integrated, wireless communication interface . . . and (b) the local, secured information stored by the integrated, secure memory enables one or more of an application, a function, and a service,” as recited in claim 1. iv. Remaining limitations of claim 1 Petitioner provides detailed explanations as to how the combination of Giobbi ’157, Giobbi ’139, and Dua teaches the remaining claim limitations as recited in independent claim 1, citing Dr. Traynor’s testimony for support. Pet. 26–27, 29–33 (citing Ex. 1005 ¶¶ 12, 26–44, 50, Fig. 3; Ex. 1006 ¶¶ 22– 44, 88–89; Ex. 1007, 6:46–65, 12:36–45, 12:51–64, 13:9–18, 13:49–60, 14:53–64, 15:42–46, 16:31–34, Figs. 1, 4A, 5–6; Ex. 1003 ¶¶ 56–64). For example, Petitioner contends that Giobbi ’139 “discloses that RDCs operate on battery power (such that the device including an RDC contains ‘a battery’.)” Id. at 26 (citing Ex. 1006 ¶ 89). In addition, Petitioner contends that “Dua discloses that its devices include an ‘internal battery 103.’” Id. at 27 (citing Ex. 1007 12:36–45, 13:49–60, Figs. 1, 5–6; Ex. 1003 ¶ 58). Petitioner also contends that Giobbi ’157’s RDC receives data from the PDK, and discloses “[t]he Reader 108 wirelessly communicates with the PDK 102 when the PDK 102 is within a proximity zone of the Reader 108.” Id. at 29–30 (citing Ex. 1005 ¶¶ 26–44, 50). Petitioner further contends that “Dua’s Reader Unit 304 is another example of an ‘integrated, wireless communication interface’ as “Reader Unit 304 also ‘communicat[es] wirelessly with at least one external device within a proximity zone’ and is ‘communicatively coupled to [an] integrated, secure memory’ (the RFID Tag Unit 306).” Id. at 31–32 (citing Ex. 1007, 6:46–65, 12:51–64, 13:9–18, 14:53–64, 15:42–56, 16:31–34, Figs. 4A, 6; Ex. 1003 ¶ 63) (alteration in original). Petitioner further provides detailed explanations as to why a POSITA” slip op. at 38

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

    “Because the determination of whether the claims invoke § 112(f) comes down to “whether the words of the claim are understood by persons of ordinary skill in the art to have a sufficiently definite meaning as the name for structure” (Williamson, 792 F.3d at 1348), we find Dr. Traynor’s testimony that claim 1 recites sufficiently definite structure persuasive. Ex. 1032. As the Federal Circuit advised in Williamson, declarations and/or testimony of expert witnesses can play a large role in this determination. Williamson, 792 F.3d at 1348. Similarly, in Dyfan, the Federal Circuit found the district court ignored key evidence – unrebutted deposition testimony regarding how a POSITA would have understood claim terms at issue. Dyfan, 28 F.4th at 1367. In particular, the Federal Circuit in Dyfan found to be “key evidence” the expert’s explanation that the terms, themselves, connote structure, wherein, in combination with the recitation of the code or application’s operation would have connoted structure to a POSITA. Id. In this proceeding, we find persuasive Dr. Traynor’s testimony that a POSITA would have understood the terms “local, secured information stored by the integrated, secure memory,” and “wireless communication interface communicating wirelessly with the at least one external device within the proximity zone,” to have “sufficient definite structure, such that a § 112, ¶ 6 interpretation is improper.” Ex. 1032 ¶ 4. In particular, we find persuasive Dr. Traynor’s testimony that the term “memory” alone has definite structure, and, for example, “is defined as the ‘capacity of a computer or integrated computer system for short and medium-term retention of digital data’ and speaks to a broad class of structures used to retain data for various purposes.” Id. at 5 (citing Ex. 1020, 5). According to Dr. Traynor, “not only does memory connote structure, but a POSITA would have recognized that memory can participate in ‘enabl[ing] one or more of an application, a function, and a service’ by simply storing information . . . necessary to access or otherwise invoke that application.” Id. at 6 (first alteration in original). Dr. Traynor’s testimony is consistent with the Specification of the ’960 patent, which describes a microchip that stores information in memory and responds through an antenna when probed. See Ex. 1001, 2:3–29. Similarly, we also find persuasive Dr. Traynor’s testimony that a “wireless communication interface communicating wirelessly with the at least one external device within the proximity zone” also has sufficiently definite structure for performing the function of “enabling one or more of an application, a function and a service.” Ex. 1032, 8. In particular, we find persuasive Dr. Traynor’s testimony that “a POSITA would have understood that an ‘integrated wireless communication interface’ speaks to a class of structures used to connect to wireless networks.” Id. According to Dr. Traynor, “[a] POSITA also would have readily recognized that a ‘wireless communication interface’ is often used to ‘enable one or more of an application, a function, and a service’ by enabling wireless communication of information . . . necessary to access or otherwise invoke that application, function, or service.” Id. at 10. Dr. Traynor cites to various technical dictionaries to persuasively support his testimony. See Ex. 1021 (WILEY ELECTRICAL AND ELECTRONICS ENGINEERING DICTIONARY), 11–12; Ex. 1023 (NEWTON’S TELECOM DICTIONARY), 5; Ex. 1024 (THE AUTHORITATIVE DICTIONARY OF IEEE STANDARDS TERMS), 5–7; Ex. 1025 (MICROSOFT COMPUTER DICTIONARY), 3–4. Thus, although Patent Owner argues that claim 1 invokes § 112(f) (PO” slip op. at 19

  Patent outcomesUS 10,073,960 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,073,960
• Apple Inc. v. Proxense, LLCAll claims unpatentable
  PTAB · Jun 17, 2025 · IPR2024-01334 · APJ David C Mckone · IPR · Final written decision

  Claims 1–7, 10, 12–19, and 22–27 are unpatentable as obvious over Ludtke alone or Ludtke and Kon.

  RulingsFinal written decision

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

    “Id. at 6:18–26. Petitioner argues that “an ATM is not a party to a transaction—the parties are the user and the bank, and the ATM is the mechanism through which the bank’s accounts are accessed.” Reply 5–6 (citing Ex. 1026 ¶ 13). Similarly, Petitioner argues, a file “is not a principal party to a transaction—rather the user and the provider of the file (e.g., a vendor) are the parties.” Id. at 6 (citing Ex. 1026 ¶ 13). Petitioner makes similar arguments for financial accounts, savings accounts, medical records, and insurance information. Id. (citing Ex. 1001, 6:18–26; Ex. 1026 ¶ 14). We agree with Petitioner. The specification, here, gives several examples where the application being accessed is not, itself, a party to the transaction, but rather an asset of one of the parties or the mechanism by which the parties transact.” slip op. at 13

  • Prior constructionPrior construction adoptedDecided for petitioner

    “Petitioner notes that a District Court has construed “access message” to mean “[a] signal or notification enabling or announcing access.” Pet. 4 (citing Ex. 1009, 3; Ex. 1010, 15, 20). However, Petitioner “maintains that the Board need not construe the term ‘access message.’” Reply 6. Patent Owner states that it “agree[s] on the construction of the term ‘access message’ to mean ‘a signal or notification enabling or announcing access.’” PO Resp. 7. However, Patent Owner argues that applying “access message” to Ludtke’s transaction confirmation “fails to account for the claim term ‘access to an application.’” Id. at 7–8. Rather, Patent Owner argues, a transaction confirmation “is a message announcing that a transaction has been completed.” Id. at 8. Patent Owner contends that “[t]he plain and ordinary meaning of ‘access message’ is a message enabling entry to, communication with, or use of an object wherein the object is the claimed application.” Id. (citing access, MERRIAM-WEBSTER DICTIONARY (available at https://www.merriam-webster.com/dictionary/access)). Here, Patent Owner appears to retreat on its agreement that “access message” can include a signal “announcing” access, and suggests that we limit “access message” to a signal “enabling” access. However, Patent Owner then returns to its agreement, stating that “[i]t would be improper to construe ‘access message’ as something other than a signal or notification enabling or announcing a user’s access to (ability to enter, communicate with, or make use of) an application.” Id.” slip op. at 16

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “1. Level of skill in the art Petitioner contends that a person of ordinary skill in the art “would have had at least a bachelor’s degree in Computer or Electrical Engineering or an equivalent engineering discipline, and at least three years of experience in the field of encryption and security, or the equivalent,” and that “[a]dditional education could substitute for professional experience, and significant work experience could substitute for formal education.” Pet. 4 (citing Ex. 1003 ¶¶ 31–32, 53–55). Patent Owner does not challenge Petitioner’s proposed level of skill or propose an alternative in its papers.” slip op. at 18

  • Expert testimonyPatent owner expert discountedDecided for petitioner

    “As explained above, a person of ordinary skill in the art would have had at least a bachelor’s degree in Computer or Electrical Engineering or an equivalent engineering discipline, and at least three years of experience in the field of encryption and security, or the equivalent, while additional education could substitute for professional experience, and significant work experience could substitute for formal education. Mr. Carrothers claims to be “a financial services and retail leader with approximately thirty years of experience working in a variety of leadership roles in retail payments.” Ex. 2018 ¶ 1. He lists professional and consulting experience with retail payments, operational and risk management of a credit card portfolio, and payment insurance and acceptances in stores and online. Id. ¶¶ 1–5. His Curriculum Vitae (Ex. 2018, Appendix A) lists education including a Bachelor of Business Administration and a Master of Business has either the technical education or the technical experience to be a person of ordinary skill in the art. In response to Petitioner’s challenge to Mr. Carrothers’ qualifications, Patent Owner does not contend that Mr. Carrothers is at least a person of ordinary skill in the art.7 Rather, Patent Owner argues that “[t]o put the asserted portions of Ludtke in context, Mr. Carrothers provided testimony regarding the processing of credit and debit card payments with respect to online transactions based on his expertise and experience with retail payments.” Sur-reply 1. Patent Owner uses Mr. Carrothers’ testimony to support arguments regarding the timing and parties to the communications generated by Ludtke’s system, and to support arguments that the TPCH is a party to Ludtke’s transactions. PO Resp. 13–17 (citing Ex. 2018 ¶¶ 20–31). We find that Mr. Carrothers testifies on technical details regarding unpatentability, and that a declarant testifying as to such subject matter should have at least ordinary skill in the art. Thus, Mr. Carrothers’ testimony is entitled to no weight. See Kyocera, 22 F.4th at 1376–77.” slip op. at 39

  Patent outcomesUS 8,886,954 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 8,886,954
• Apple Inc. v. Proxense, LLCAll claims unpatentable
  PTAB · Jun 17, 2025 · IPR2024-00233 · APJ David C Mckone · IPR · Final written decision

  Claims 1–7, 10, 12–19, and 22–27 are unpatentable as obvious over Ludtke alone or Ludtke and Kon.

  RulingsFinal written decision

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

    “In short, Patent Owner points to no language in the specification limiting the claims to transactions in which the application being accessed is, itself, a party to the transaction and Petitioner points to several examples in which the application being accessed is not a party to the transaction. Thus, Patent Owner has provided no persuasive basis to depart from the plain and ordinary meaning of the claims.” slip op. at 14

  • Prior constructionPrior construction adoptedDecided for petitioner

    “Petitioner notes that a District Court has construed “access message” to mean “[a] signal or notification enabling or announcing access.” Pet. 4 (citing Ex. 1009, 3; Ex. 1010, 15, 20). However, Petitioner “maintains that the Board need not construe the term ‘access message.’” Reply 6. Patent Owner states that it “agree[s] on the construction of the term” slip op. at 16

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “1. Level of skill in the art Petitioner contends that a person of ordinary skill in the art “would have had at least a bachelor’s degree in Computer or Electrical Engineering or an equivalent engineering discipline, and at least three years of experience in the field of encryption and security, or the equivalent,” and that “[a]dditional education could substitute for professional experience, and significant work experience could substitute for formal education.” Pet. 4 (citing Ex. 1003 ¶¶ 31–32, 53–55). Patent Owner does not challenge Petitioner’s proposed level of skill or propose an alternative in its papers.” slip op. at 18

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

    “3. Differences, if any, between claims 1, 2, 4–7, 10, 12, 13, 15, 16, 18, 19, and 22–27 and Ludtke; reasons to modify Regarding claim limitations 1ai, 1aii, and 1aiii, Petitioner argues that Ludtke teaches persistently storing, in a user identity/account information block of the transaction device, biometric information (e.g., fingerprint, retinal scan, voice, DNA, hand profile, face recognition), a plurality of codes and other values comprising a device ID code uniquely identifying the transaction device (e.g., globally unique silicon ID (GUID), magnetic strip, bar codes), and a secret decryption value (e.g., public key infrastructure (PKI) public keys and private keys). Pet. 9–21 (citing Ex. 1005, 5:11–20, 8:63–67, 9:18–25, 10:64–67, 11:1–5, 13:27–29, 13:39–41, 14:13–21, 19:9– 14, 19:29–40, 23:11–19, 30:18–27, 37:39–45, 38:1–3, 38:9–21, 38:25–29, 38:40–61, 39:7–18, 40:5–26, Figs. 7B–7C, 27, 33; Ex. 1003 ¶¶ 73–94). Patent Owner does not contest Ludtke’s applicability to these aspects of claim 1. Based on Petitioner’s evidence, we find that Ludtke teaches claim limitations 1ai, 1aii, and 1aiii. More particularly, we find that Ludtke’s fingerprint, retinal scan, etc., are “biometric data”; that Ludtke’s GUID, magnetic strip, etc., are examples of “a device ID code uniquely identifying an integrated device”; and that PKI keys are examples of “a secret decryption value.” transaction device requests and receives a fingerprint sample or other biometric data. Id. at 21–22 (citing Ex. 1005, 14:33–42, 14:40–46, 16:47– 50; Ex. 1003 ¶¶ 95–96). As to claim limitation 1c, Petitioner argues that Ludtke’s transaction device compares the fingerprint sample to stored authorized samples to determine a match. Id. at 22 (citing Ex. 1005, 14:40– 46; Ex. 1003 ¶ 97). Patent Owner does not contest Ludtke’s applicability to these aspects of claim 1. We agree with Petitioner and find that Ludtke teaches claim limitations 1b and 1c.” slip op. at 23

  Patent outcomesUS 8,886,954 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 8,886,954

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.