• Google LLC v. Mindbasehq, LLCAll claims unpatentable
  PTAB · Mar 16, 2026 · IPR2021-01252 · APJ Kara L Szpondowski · IPR · Remand

  On remand, claims 14–19, 33–40, and 43–46 were held unpatentable as obvious; the Federal Circuit’s affirmed findings leave claims 1–13, 20–32, 41, and 42 unpatentable as well.

  RulingsRemand decision

  • RemandOther

    “to both cases vacating and remanding in part and affirming in part our Final Written Decisions. Appeal Dec. With respect to Petitioner’s appeals, the Federal Circuit addressed the “dictionary routine” claims (claims 14–19 and 33–40) and the “normalization” claims (claims 43–46). Appeal Dec. 7–14. For the “dictionary routine” claims, the Federal Circuit vacated and remanded, stating that In sum, as Google contends and we now hold, the “dictionary routine” claims can be practiced by use of an already-created dictionary, and do not also require the automatic creation of a dictionary. The Board needs to consider Google’s evidence and argument by applying this construction of the automatically classifying and storing limitation, and using this understanding to determine whether Conlon may, in fact, render the “dictionary routine” claims obvious (and, relatedly, whether its prior distinctions of Conlon may be immaterial). Appeal Dec. 10–11. For the “normalization” claims, the Federal Circuit also vacated and remanded, stating that our “decision to exclude Google’s rebuttal argument and supplemental declaration is based on a clear factual error,” so on remand we “must include evaluation of the evidence and argument Google provided in reply.” Id. at 13–14. With respect to Patent Owner’s cross-appeals, the Federal Circuit affirmed. Id. at 14–16.” slip op. at 3

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

    “The Federal Circuit concluded that Petitioner’s construction of “automatically classifying and storing” (as recited in limitation [14.3]), is correct. Appeal Dec. 8. That is, “the ‘dictionary routine’ claims can be practiced by [the] use of an already-created dictionary, and do not also require the automatic creation of a dictionary.” Id. at 10; see also Reply 7 (the limitation is “directed to the use of a dictionary function to automatically look up words and their syntax”); Appeal Dec. 8 (“nothing about the term . . . would inform a person of ordinary skill in the art that automatic ‘creation’ of a database, in addition to the ‘use’ of an already-created database, is a requirement of the dictionary routine claims”); id. (“the plain and ordinary meaning of the claim language is broad enough to include ‘use’”); id. (agreeing with Petitioner that “the specification describes the ‘dictionary routine’ as the act of looking up words already in the database”); id. at 9 (stating that “[i]t is notable, as well, that the specification nowhere describes automatically creating a dictionary; all instances of creating dictionary entries rely, at least in part, on manual data entry by users”). As directed by the Federal Circuit, we will apply this construction in our analysis.8 Id. 8 Patent Owner argues that the Federal Circuit “cherry-picks” and misinterprets the patents’ specifications, and “ignores the clearly contrary specification language.” PO Remand Br. 4–5, 10; id. at 8 (arguing that that the specification clearly set forth the definition of the claim term, and “the Board must accept term definitions . . . above all external definitions”). We do not consider these arguments on the construction of this limitation, because the Federal Circuit has directed us to proceed under its construction of the limitation. We also agree with Petitioner that the Federal Circuit’s claim construction is “foreclosed from further consideration” under its” slip op. at 17

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

    “We agree with Petitioner that claim 43 is obvious over the combination of Conlon, Miller, and Fong. The Federal Circuit stated, “[i]n this context, ‘normalization’ generally refers to de-duplicating and simplifying database entries (for instance, combining entries for ‘car’ and ‘automobile’).” Appeal Dec. 4 (cited at Pet. Response Br. 5). This is consistent with the disclosure in the ’433 patent. E.g., Ex. 1001, 16:55– 17:24 (discussing, for example, “recogniz[ing] that the differently named data elements in different structures are actually the same data element . . . is referred to as normalizing the names of the same data elements,” “recogniz[ing] that the same named data elements in different structures are actually different data elements . . . is referred to as normalizing the names of the different data elements,” and “normalizing multiple single data elements”). This is also consistent with how Fong describes “normalization.” Ex. 1029, 76 (The “Function” of “Normaliz[ing] the collection of entities” is to “[r]emove redundancies and detect errors”); see also Ex. 1057 ¶ 226. Patent Owner’s arguments that Fong’s normalization is “different” from the normalization described in the ’433 patent does not persuasively rebut Petitioner’s arguments. As Petitioner points out, Patent Owner does not provide a construction for “normalization,” despite claiming that the term is “defined” in the ’433 patent. Pet. Remand Resp. Br. 6; PO Remand Br. 13. Moreover, although Patent Owner purports to identify differences between the ’433 patent and Fong, the “normalization” applied is expressly recited in limitations [43.1.1], [43.1.2], and [43.2], and the subsequent actions taken on those normalized databases (i.e., comparing and recording) are recited in limitations [43.3]–[43.5]. That is, the “normalization” required by the claim is reflected in the claim language itself, and is broader than argued by Patent Owner. See In re Baxter Travenol Labs., 952 F.2d 388, 391 (Fed. Cir. 1991) (“It is not the function of this court to examine the claims in greater detail than argued by an appellant, looking for nonobvious distinctions over the prior art”). Patent Owner does not explain how these purported “differences” (e.g., that Fong may require the use of “database keys,” “identifiers,” “entities,” or determining ‘non-key attributes’ from key attributes) impacts the claim language, or Petitioner’s showing. See EWP Corp. v. Reliance Universal Inc., 755 F.2d 898, 907 (Fed. Cir. 1985) (A prior art reference “must be considered for everything it teaches by way of technology and is not limited to the particular invention it is describing and attempting to protect”). For the same reasons, as well as those set forth by Petitioner, we are also not persuaded by Patent Owner’s arguments that each DBMS requires a normalization process that is customized for it. Pet. Remand Resp. Br. 6–7. These arguments by Patent Owner also are not commensurate with the scope of the claim language, which does not recite a DBMS, and generally recites “normalizing” or “normalized” without regard to the DBMS. Id. Dr. Jansen provides an example of a database in unnormalized form that is converted into a normalized form, based on Fong’s four conditions, as applied to the claim language. See Reply 31–35; Ex. 1057 ¶¶ 226–261. Therefore, we are not persuaded by Patent Owner’s arguments that Petitioner has not explained how the example maps onto the limitations. PO Remand Resp. Br. 6–12. Patent Owner’s complaint that Dr. Jansen created the graphic in the example does not undermine Petitioner’s showing. E.g., Trial Practice Guide,14 I.G., (“Experts may testify about the teachings of the prior art and how they relate to the patentability of the challenged claims.”). We find Dr. Jansen’s testimony credible and persuasive in explaining why the combination of Conlon and Fong teaches the claim limitations. After considering the properly presented evidence and arguments of the complete record, we determine that Petitioner has shown, by a preponderance of the evidence, that the combination of Conlon, Miller, and Fong teaches the limitations in claim 43, that one of ordinary skill in the art would have been motivated to combine the teachings of Conlon, Miller, and Fong, and that claim 44 would have been obvious over Conlon, Miller, and Fong. 2. Analysis of Dependent Claims 44–46 Claims 44–46 depend, directly or indirectly, from claim 41. We, likewise, determine whether the combination renders obvious claims 44–46, taking into account the arguments made in Petitioner’s Reply Briefs and Dr. Jansen’s Supplemental Rebuttal Declarations. Petitioner contends that dependent claims 44–46, would have been obvious over Conlon, Miller, and Fong, and provides explanation as to how the prior art teaches each claim limitation. Pet. 84–86; Reply 35–39; Pet. Remand Br. 13–14. Patent Owner does not provide further briefing on dependent claims 44–46. 14 Available at https://www.uspto.gov/patents/ptab/trial-practice-guide#step2. Patent Owner did not specifically challenge Petitioner’s contentions as” slip op. at 31

  • Strike new argumentNew argument disregardedDecided for petitioner

    “Patent Owner’s arguments do not undermine Petitioner’s showing. Patent Owner did not specifically challenge Petitioner’s contentions as to the sufficiency of Conlon’s disclosure for claim 1410 in the Patent Owner Response. In the Sur-replies, Patent Owner argues that the claim requires that at least some relationships are created “automatically,” and “these automatic embodiments . . . are represented in this group of claims.” Sur-reply 9. Along these lines, in the additional briefing Patent Owner argues that Conlon does not teach “automatic,” but merely teaches “semi-automatic.” PO Remand Br. 9–10. The crux of Patent Owner’s argument, however, is that the Federal Circuit did not properly construe the limitation, and ignored certain disclosures in the ’433 (and ’680) patent. Id. at 10–11; see Pet. Remand Resp. Br. 1–4; PO Remand Resp. Br. 4–5. The Federal Circuit held that “the dictionary routine claims can be satisfied by mere use of a lexical database, and do not also require the automatic creation of additional definitions.” Appeal Dec. 10. Moreover, the statements from Conlon that Patent Owner relies upon relate to creating a database, not using the database. See id. As discussed above, on remand we are directed to apply the Federal Circuit’s construction. Patent Owner does not explain 10 As discussed in the original Final Written Decisions, Patent Owner raised several arguments that generally applied to all the claims, challenging, for example, the level of ordinary skill in the art, whether Conlon, Miller, and Beckwith were analogous art, and several general arguments relating to Conlon and the motivation to combine Conlon with a DBMS. See Final Dec. 14–23, 25–27. We were not persuaded by Patent Owner’s arguments; the Federal Circuit affirmed, determining that our findings were supported by substantial evidence. Appeal Dec. 14–16. why Petitioner’s contentions are not persuasive in light of the Federal Circuit’s construction of this limitation. In addition, Patent Owner argues in the Sur-replies that “[c]laims 14– 19 are not disclosed by the proffered prior art” and cites to paragraphs 78–83 of the Ranka Rebuttal Declarations. Sur-reply 10. As discussed in the original Final Written Decisions, Patent Owner’s reliance on six paragraphs of Dr. Ranka’s Rebuttal Declarations is an improper incorporation by reference, as Patent Owner did not discuss that testimony or further elaborate on these arguments in the Sur-replies. 37 C.F.R. § 42.6(a)(3); Cisco Systems, Inc. v. C-Cation Techs., LLC, IPR2014-00454, Paper 12 at 9–10 (PTAB Aug. 29, 2014) (informative); see, e.g., Final Dec. 37–39, 45, 48–50, 52. Therefore, we will not consider arguments that are not made in the Sur-replies, but are instead improperly incorporated by reference to the cited paragraphs in Dr. Ranka’s Rebuttal Declarations. Accordingly, after considering the evidence and arguments of the complete record, we determine that Petitioner has shown, by a preponderance of the evidence, that Conlon teaches limitation [14.3], and that claim 14 would have been obvious over Conlon.” slip op. at 21

  Patent outcomesUS 6,665,680 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,665,680
• Google LLC v. Mindbasehq, LLCAll claims unpatentable
  PTAB · Mar 16, 2026 · IPR2021-01251 · APJ Kara L Szpondowski · IPR · Remand

  On remand, claims 14–19, 33–40, and 43–46 were held unpatentable as obvious over Conlon alone or Conlon, Miller, and Fong; the affirmed unpatentability of claims 1–13, 20–32, 41, and 42 remains.

  RulingsRemand decision

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

    “automatically classifying and storing” (as recited in limitation [14.3]), is correct. Appeal Dec. 8. That is, “the ‘dictionary routine’ claims can be practiced by [the] use of an already-created dictionary, and do not also require the automatic creation of a dictionary.” Id. at 10; see also Reply 7 (the limitation is “directed to the use of a dictionary function to automatically look up words and their syntax”); Appeal Dec. 8 (“nothing about the term . . . would inform a person of ordinary skill in the art that automatic ‘creation’ of a database, in addition to the ‘use’ of an already-created database, is a requirement of the dictionary routine claims”); id. (“the plain and ordinary meaning of the claim language is broad enough to include ‘use’”); id. (agreeing with Petitioner that “the specification describes the ‘dictionary routine’ as the act of looking up words already in the database”); id. at 9 (stating that “[i]t is notable, as well, that the specification nowhere describes automatically creating a dictionary; all instances of creating dictionary entries rely, at least in part, on manual data entry by users”). As directed by the Federal Circuit, we will apply this construction in our analysis.8 Id. 8 Patent Owner argues that the Federal Circuit “cherry-picks” and misinterprets the patents’ specifications, and “ignores the clearly contrary specification language.” PO Remand Br. 4–5, 10; id. at 8 (arguing that that the specification clearly set forth the definition of the claim term, and “the Board must accept term definitions . . . above all external definitions”). We do not consider these arguments on the construction of this limitation, because the Federal Circuit has directed us to proceed under its construction of the limitation. We also agree with Petitioner that the Federal Circuit’s claim construction is “foreclosed from further consideration” under its slip op. at 17

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

    “combination of Conlon, Miller, and Fong. The Federal Circuit stated, “[i]n this context, ‘normalization’ generally refers to de-duplicating and simplifying database entries (for instance, combining entries for ‘car’ and ‘automobile’).” Appeal Dec. 4 (cited at Pet. Response Br. 5). This is consistent with the disclosure in the ’433 patent. E.g., Ex. 1001, 16:55– 17:24 (discussing, for example, “recogniz[ing] that the differently named data elements in different structures are actually the same data element . . . is referred to as normalizing the names of the same data elements,” “recogniz[ing] that the same named data elements in different structures are actually different data elements . . . is referred to as normalizing the names of the different data elements,” and “normalizing multiple single data elements”). This is also consistent with how Fong describes “normalization.” Ex. 1029, 76 (The “Function” of “Normaliz[ing] the collection of entities” is to “[r]emove redundancies and detect errors”); see also Ex. 1057 ¶ 226. Patent Owner’s arguments that Fong’s normalization is “different” from the normalization described in the ’433 patent does not persuasively rebut Petitioner’s arguments. As Petitioner points out, Patent Owner does not provide a construction for “normalization,” despite claiming that the term is “defined” in the ’433 patent. Pet. Remand Resp. Br. 6; PO Remand Br. 13. Moreover, although Patent Owner purports to identify differences between the ’433 patent and Fong, the “normalization” applied is expressly recited in limitations [43.1.1], [43.1.2], and [43.2], and the subsequent actions taken on those normalized databases (i.e., comparing and recording) are recited in limitations [43.3]–[43.5]. That is, the “normalization” required by the claim is reflected in the claim language itself, and is broader than argued by Patent Owner. See In re Baxter Travenol Labs., 952 F.2d 388, 391 (Fed. Cir. 1991) (“It is not the function of this court to examine the claims in greater detail than argued by an appellant, looking for nonobvious distinctions over the prior art”). Patent Owner does not explain how these purported “differences” (e.g., that Fong may require the use of “database keys,” “identifiers,” “entities,” or determining ‘non-key attributes’ from key attributes) impacts the claim language, or Petitioner’s showing. See EWP Corp. v. Reliance Universal Inc., 755 F.2d 898, 907 (Fed. Cir. 1985) (A prior art reference “must be considered for everything it teaches by way of technology and is not limited to the particular invention it is describing and attempting to protect”). For the same reasons, as well as those set forth by Petitioner, we are also not persuaded by Patent Owner’s arguments that each DBMS requires a normalization process that is customized for it. Pet. Remand Resp. Br. 6–7. These arguments by Patent Owner also are not commensurate with the scope of the claim language, which does not recite a DBMS, and generally recites “normalizing” or “normalized” without regard to the DBMS. Id. Dr. Jansen provides an example of a database in unnormalized form that is converted into a normalized form, based on Fong’s four conditions, as applied to the claim language. See Reply 31–35; Ex. 1057 ¶¶ 226–261. Therefore, we are not persuaded by Patent Owner’s arguments that Petitioner has not explained how the example maps onto the limitations. PO Remand Resp. Br. 6–12. Patent Owner’s complaint that Dr. Jansen created the graphic in the example does not undermine Petitioner’s showing. E.g., Trial Practice Guide,14 I.G., (“Experts may testify about the teachings of the prior art and how they relate to the patentability of the challenged claims.”). We find Dr. Jansen’s testimony credible and persuasive in explaining why the combination of Conlon and Fong teaches the claim limitations.” slip op. at 31

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “Dr. Jansen provides an example of a database in unnormalized form that is converted into a normalized form, based on Fong’s four conditions, as applied to the claim language. See Reply 31–35; Ex. 1057 ¶¶ 226–261. Therefore, we are not persuaded by Patent Owner’s arguments that Petitioner has not explained how the example maps onto the limitations. PO Remand Resp. Br. 6–12. Patent Owner’s complaint that Dr. Jansen created the graphic in the example does not undermine Petitioner’s showing. E.g., Trial Practice Guide,14 I.G., (“Experts may testify about the teachings of the prior art and how they relate to the patentability of the challenged claims.”). We find Dr. Jansen’s testimony credible and persuasive in explaining why the combination of Conlon and Fong teaches the claim limitations.” slip op. at 32

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

    “4. Summary of Ground 1 Having considered the Graham factors,11 including the level of ordinary skill in the art, the scope and content of the prior art, and the differences between the prior art and the challenged claims, we are persuaded, based on the current record, that Petitioner has shown, by a preponderance of the evidence, that claims 14–19 and 33–40 would have been obvious over Conlon.” slip op. at 24

  Patent outcomesUS 6,510,433 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,510,433
• BMW Of North America, LLC v. Foras Technologies Ltd.No claims unpatentable
  PTAB · Mar 5, 2026 · IPR2024-01347 · APJ Russell E Cass · IPR · Final written decision

  Claims 1–27 were not shown unpatentable because the asserted combinations did not teach switching the boot-processor role to a spare processor.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “B. Level of Ordinary Skill in the Art The level of skill in the art is “a prism or lens” through which we view the prior art and the claimed invention. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). “This reference point prevents . . . factfinders from using their own insight or, worse yet, hindsight, to gauge obviousness.” Id.” slip op. at 17

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

    “processor” to the spare processor, we determine that the claim is describing this transfer of identification of “boot processor,” which is required when transferring a boot processor’s functions to a spare because of the “problems [that] arise in attempting to idle (or eject) the boot processor.” Id. at 6:25– 27. This is confirmed by the language of limitation [1d], stating that the switching of the role of boot processor involves “changing a system identifier of the spare processor to that of the boot processor.” Thus, the firmware and operating system exchange this information identifying the boot processor, which is described in the specification as a device tree. See, e.g., id. at 13:21–35. The ’302 patent makes clear that accurate identification of which processor is the boot processor remains critical during runtime. See, e.g., id. at 6:25–27. Thus, Patent Owner is correct in requiring the system to have a way to identify the boot processor and to transfer this identification during runtime. However, as made clear in the embodiments described in the ’302 patent discussed above, this identification is for runtime purposes to accommodate runtime problems, not for booting purposes. Although Patent Owner may be correct that a function of the boot processor is to boot the system (PO Sur-reply 5), the problem identified in the ’302 patent is a problem relating to the runtime reassignment of the boot processor identity, to address a runtime need to identify the boot processor. See, e.g., Ex. 1001, 11:6–9. Accordingly, based on our analysis of the claims and specification, we determine that “switching the role of boot processor to a spare processor without shutting down the system’s operating system” means causing the system to identify the spare processor as the boot processor (e.g., in a device tree), which then causes the spare processor to appear as the boot processor to the system during runtime. Ex. 1001, 6:25–41, 11:4–18 (describing why boot processors are treated differently even after the boot process has completed); compare id. at 9:65–11:3 (process for recovering from loss of lockstep of a non-boot processor without using a spare), with id. at 11:4–43 (process for recovering from loss of lockstep of a boot processor using a spare because boot processors, during runtime, need special treatment); see also 14:66–15:21 (emphasizing that spares are only needed for recovering boot processors). We construe switching a “role of boot processor” to mean transferring an identification in the system of which processor is the boot processor. This construction comports with the embodiments described in the specification. We do not adopt an additional requirement that this procedure also requires designating which processor will boot the system in the next reboot, which is not disclosed in the specification.” slip op. at 24

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

    “may swap processors that are failing, and perform the necessary bookkeeping to keep the operating system informed as to how to address the processors available, nothing in the Petition persuasively explains whether this generic processor swapping switches the boot processor role. As we explained in our claim construction section, the term “boot processor” is not merely a label of convenience to describe the processor that happened to have earlier booted the system. The role of boot processor is specifically switched to the spare; it is a piece of information tracked by the system. As we explain below, Petitioner does not adequately address the transfer of this information to make the system aware of which processor has the boot processor role. Petitioner asserts that “the BSP flag” of the IA-32 system is used to “determine whether a processor is the boot processor.” Pet. 17–18. Petitioner here is relying on a register used in IA-32 processors to identify whether or not they are the boot processor. This register is used during booting so that only the boot processor boots the system. See, e.g., Ex. 1008, 238–40, 710. This register does not appear to serve any further role, and Petitioner offers no persuasive evidence or argument that the processor register flag is exposed or copied to the operating system or APIC table. Petitioner’s proposed combination does not involve updating this register, nor does Petitioner explain how, even if the register were updated, it would meet the “switching” a “role of boot processor” in limitation [1d].” slip op. at 32

  • ExcludeOther

    “The USPTO has established Rules for objecting to and challenging evidence. 37 C.F.R. § 42.64. This process sets various timeframes and permits briefing and curative actions, all of which are designed to crystallize 5 We follow the parties’ convention of citing to the later-added “Page X of Y” pagination rather than the native pagination. the issues and ensure a full and fair opportunity for the parties to be heard. See id. In this instance, Patent Owner’s evidentiary arguments regarding Exhibits 1008 and 1028 are untimely. Accordingly, we will not exclude Exhibits 1008 or 1028 on the basis of their authenticity, admissibility, or for any reason that should have been raised under the proper procedures. See, e.g., PO Resp. 7–8; PO Sur-reply 7–8; see also Pet. Reply 11 (asserting that “Patent Owner has not filed any objection to or a motion to exclude these references”). We consider Petitioner’s citations to these documents in our prior art analysis below. Notwithstanding, as is clear from our patentability analysis below, Exhibits 1008 and 1028 do not serve to demonstrate the unpatentability of any claim.” slip op. at 26

  Patent outcomesUS 7,624,302 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 7,624,302
• BMW Of North America, LLC v. Foras Technologies Ltd.No claims unpatentable
  PTAB · Mar 5, 2026 · IPR2024-01346 · APJ Russell E Cass · IPR · Final written decision

  Claims 1–30 were not shown unpatentable because the prior-art combinations did not establish transfer of the role of boot processor during system runtime.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for patent owner

    “Patent Owner asserts that: A person of ordinary skill in the art in the field of the ’781 patent would have been a person with at least a bachelor’s degree in Electrical Engineering, Computer Engineering, or equivalent, and at least two years of prior work experience with computer architecture, including experience relating to fault tolerant computer architecture, as of the earliest priority date of the ’781 patent—October 25, 2004. If a person did not have a bachelor’s degree, additional relevant and practical experience with fault tolerant computer systems could provide an acceptable substitute. Likewise, further education beyond a bachelor’s degree could compensate for a deficiency in practical experience. See EX2004, Declaration of Nigel A. Jones (“Jones”), ¶ 26. PO Resp. 3. Patent Owner further notes that its position is “similar, but not identical to, Petitioner’s [position]” but that “the analysis [of the claims] is identical for both proposed determinations.” Id. We agree that our analysis would not differ based on choosing one proposed level of skill over the other, but as the losing party, we select Petitioner’s proposed level of skill.” slip op. at 20

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

    “Accordingly, based on our analysis of the claims and specification, we determine that “logic . . . for transferring, during system runtime, the role of boot processor” means logic that causes the system to identify the spare processor as the boot processor (e.g., in a device tree) which then causes the spare processor to appear as the boot processor to the system during runtime. Ex. 1001, 5:39–55, 10:43–67 (describing why boot processors are treated differently even after the boot process has completed); compare id. at 9:37– 10:42 (process for recovering from loss of lockstep of a non-boot processor without using a spare), with id. at 10:43–11:42 (process for recovering from loss of lockstep of a boot processor using a spare because boot processors, during runtime, need special treatment); see also 15:21–42 (emphasizing that spares are only needed for recovering boot processors). We construe transferring a “role of boot processor” to mean transferring an identification in the system of which processor is the boot processor. This construction comports with the embodiments described in the specification. We do not adopt an additional requirement that this procedure also requires designating which processor will boot the system in the next reboot, which is not disclosed in the specification.” slip op. at 26

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “Based on the clear support in the specification for the above interpretation, we see no need to resort to extrinsic evidence. Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1287 (Fed. Cir. 2021) (“If the meaning of a claim term is clear from the intrinsic evidence, there is no reason to resort to extrinsic evidence.”) (citing Profectus Tech. LLC v. Huawei Techs. Co., 823 F.3d 1375, 1380 (Fed. Cir. 2016) (“Extrinsic evidence may not be used ‘to contradict claim meaning that is unambiguous in light of the intrinsic evidence.’” (quoting Phillips, 415 F.3d at 1324)). In general, the cited portions of testimony from the declarants from both parties in the briefs do little more than point to the portions of the ’781 patent described above or argue about what a boot processor does during booting. See, e.g., Pet. Reply 2–8. The specification makes clear that it is focused on the role of boot processor during runtime because of problems encountered during runtime; it is not focused on the boot processor during booting. Ex. 1001, 5:39–55, 10:43–67. Thus, the testimony about what a boot processor does during booting, or that the primary function of the boot processor is to boot, is not particularly pertinent, and does not undo the unambiguous discussion in the ’781 patent.” slip op. at 27

  • BurdenDecided for patent owner

    “whether they are the boot processor or not (Ex. 1008, 238, 710), Petitioner does not explain how such information is exposed to the BIOS or operating system, nor how it is changed during runtime, after its purpose has been fulfilled. In sum, even if Petitioner’s proposed combination swaps the spare processor for the processor that booted the system, Petitioner’s proposed combination does not appear to transfer the role of boot processor to the spare processor. At best, Petitioner’s proposed combination transfers the tasks of one processor to another. See Ex. 1005 ¶¶ 15 (Fox describing its disclosure as “updat[ing] the ‘active’ processor list” and “[re-]allocat[ing] the threads that were running on the failing processor”), 46 (transferring “processes (instructions, threads, etc.) initially allocated to the failing processor” to the spare processor)). Of the art of record, we are only aware of the ’781 patent transferring a designation of which processor is the boot processor during the swap to a spare processor. See, e.g., Ex. 1001, 10:43– 55, 11:10–12, 16:19–21, 17:51–55; claims 1, 9, 16, 25. In conclusion, we find that Petitioner has not shown, by a preponderance of the evidence, how the prior art teaches “transferring” a “role of boot processor” as required by limitation 1[c].” slip op. at 40

  Patent outcomesUS 7,627,781 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 7,627,781
• Qualcomm Incorporated v. Cobblestone Wireless, LLCSome claims unpatentable
  PTAB · Mar 5, 2026 · IPR2024-01336 · APJ Russell E Cass · IPR · Final written decision

  Claims 1–4, 6–9, 24, and 25 are unpatentable; claims 10, 13, 14, 17, and 21–23 were not shown unpatentable, principally due to missing limitations or insufficient motivation to combine.

  RulingsFinal written decision

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

    “information” should be given its plain and ordinary meaning as “data,” and that Patent Owner’s narrower construction of “first information” and “second information” lacks sufficient support in the intrinsic record. We agree with Petitioner that the ’802 patent Specification defines “information” as data when it uses the phrase “information (i.e., data).” See Ex. 1001, 5:60–62 (“Information (i.e., data) to be transmitted may be received in a baseband digital system 250, such as a wireless digital baseband processor.” (emphasis added)), 11:30–32 (“In this example, the signals 911 and 912 carry the same information (data).” (emphasis added)). As the Federal Circuit has explained, a “specification’s use of ‘i.e.’ signals an intent to define the word to which it refers.” Edwards Lifesciences LLC v. Cook Inc., 582 F.3d 1322, 1334 (Fed. Cir. 2009). slip op. at 13

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

    “argument based on Fernandez alone, we find that Petitioner has not provided a sufficient evidentiary basis to support a motivation to remove the amplification from each of Fernandez’s signal generators 10A-10E and add a single power amplifier instead. See Pet. 76–77 Ex. 1003 ¶ 235. Petitioner’s only rationale for this modification to Fernandez is that “[a] single amplifier has several advantages compared to multiple amplifiers, including lower complexity, a single (vs. multiple) potential point of failure, and lower cost,” and that one of ordinary skill “would have found a single amplifier to be a simple matter of design preference.” Pet. 76–77. Dr. Almeroth simply repeats these cursory allegations without providing any further explanation or evidentiary support. Ex. 1003 ¶ 235. Moreover, Dr. Cooklev provides credible testimony that replacing Fernandez’s amplification in signal generators 10A–10E with a single amplifier would not necessarily have the advantages that Petitioner suggests. See Ex. 2013 ¶¶ 99, 104–105. For example, Dr. Cooklev testifies that a single amplifier would need to have a wider bandwidth than the multiple amplifiers used in Fernandez, which could cause potential stability issues. Id. ¶ 105. According to Dr. Cooklev, this wider bandwidth would require more circuit elements, and thus would not provide the reduction in space usage and power consumption that Petitioner asserts. Id. According to Dr. Cooklev, Montojo also points to several “substantial, and potentially impractical, drawbacks” of using a single amplifier for multiple signal generators, including power constraints imposed by spectral emission requirements and on-board battery capacity. Id. ¶ 104 (citing Ex. 1006 ¶¶ 7– 8). In light of this testimony, which we find credible, Petitioner has failed to provide sufficient explanation or evidence to support its assertion that one of ordinary skill would have found it obvious to replace the multiple amplifiers in Fernandez’s signal generators with a single amplifier.” slip op. at 65

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable

    “argument based on Fernandez alone, we find that Petitioner has not provided a sufficient evidentiary basis to support a motivation to remove the amplification from each of Fernandez’s signal generators 10A-10E and add a single power amplifier instead. See Pet. 76–77 Ex. 1003 ¶ 235. Petitioner’s only rationale for this modification to Fernandez is that “[a] single amplifier has several advantages compared to multiple amplifiers, including lower complexity, a single (vs. multiple) potential point of failure, and lower cost,” and that one of ordinary skill “would have found a single amplifier to be a simple matter of design preference.” Pet. 76–77. Dr. Almeroth simply repeats these cursory allegations without providing any further explanation or evidentiary support. Ex. 1003 ¶ 235. Moreover, Dr. Cooklev provides credible testimony that replacing Fernandez’s amplification in signal generators 10A–10E with a single amplifier would not necessarily have the advantages that Petitioner suggests. See Ex. 2013 ¶¶ 99, 104–105. For example, Dr. Cooklev testifies that a single amplifier would need to have a wider bandwidth than the multiple amplifiers used in Fernandez, which could cause potential stability issues. Id. ¶ 105. According to Dr. Cooklev, this wider bandwidth would require more circuit elements, and thus would not provide the reduction in space usage and power consumption that Petitioner asserts. Id. According to Dr. Cooklev, Montojo also points to several “substantial, and potentially impractical, drawbacks” of using a single amplifier for multiple signal generators, including power constraints imposed by spectral emission requirements and on-board battery capacity. Id. ¶ 104 (citing Ex. 1006 ¶¶ 7– 8). In light of this testimony, which we find credible, Petitioner has failed to provide sufficient explanation or evidence to support its assertion that one of ordinary skill would have found it obvious to replace the multiple amplifiers in Fernandez’s signal generators with a single amplifier.” slip op. at 65

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedOther

    “We find credible and agree with Dr. Cooklev’s testimony that the predistortion signals from tables 17-1 and 17-2 “are cancelled out by Suzuki’s amplifier” 28. Ex. 2013 ¶ 50. Dr. Cooklev supports his opinion by referring to paragraph 1 of Suzuki, which states that Suzuki’s invention is directed to “a multi-band lookup table type predistorter” (such as the one implemented using lookup tables 17-1 and 17-2 in Figure 6) that “compensates for a distortion of a power amplifier.” Ex. 2013 ¶ 54; Ex. 1004 ¶ 1. Dr. Cooklev’s opinion is also supported by paragraph 3 of Suzuki, which explains that a conventional digital predistorter uses a lookup table “for linearizing non-linear characteristics of an amplifier.” Ex. 1004 ¶ 3; Ex. 2013 ¶ 54. Dr. Cooklev further supports his opinion by relying on Suzuki’s disclosure in paragraph 46 that power amplifier 28 is “subject to distortion compensation” by the predistorter, and that distortion components in the signal output by the amplifier are canceled by “distortion compensation data [that] are read out from the lookup tables 17-1 and 17-2 and provided to the adders 13-1 and 13-2, respectively.” Ex. 1004 ¶ 46; Ex. 2013 ¶ 54. And, Dr. Cooklev’s opinion is supported by Suzuki’s disclosure in paragraph 47 that the distortion compensation added by adders 13-1 and 13-2 add the distortion compensation data from lookup tables 17-1 and 17-2 “to perform distortion compensation (addition of predistortion)” to “signals to be transmitted.” Ex. 1004 ¶ 47; Ex. 2013 ¶ 54. Petitioner agrees that the distortion compensation data from lookup tables 17-1 and 17-2 “are added to the respective frequency band from” input signal ST “in order to predistort the output signal, which is then transmitted,” and does not dispute that the distortion compensation data from lookup tables 17-1 and 17-2 is ultimately cancelled out by the distortion created by amplifier 28. Pet. Reply 8. In light of the above evidence, we agree with Patent Owner that Suzuki’s distortion components from lookup tables 17-1 and 17-2 in Figure 6 (which Petitioner relies on for the first and second digital signals in limitations 10a and 10b) are cancelled out by the distortion created by power amplifier 28 before the signal is ultimately transmitted. We agree with Petitioner that these first and second digital signals include data in the form of distortion compensation data. However, because these signals are cancelled by the distortion from amplifier 28 before transmission, the data from these signals is never transmitted. Thus, the first and second digital signals identified by Petitioner (the distortion compensation data from lookup tables 17-1 and 17-2) do not comprise data “to be transmitted,” as limitations 10a and 10b require.” slip op. at 35

  Patent outcomesUS 7,924,802 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,924,802
• Apple Inc. v. Varia Holdings LLCAll claims unpatentable
  PTAB · Feb 27, 2026 · IPR2024-01364 · APJ Norman H Beamer · IPR · Final written decision

  Claims 1–39 are unpatentable under § 103 over Willgert and Mooney; claims 3–9, 15–19, 22–28, and 34–38 are also unpatentable over Willgert, Mooney, Holloway, and Pitroda.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Based on a review of the record, we adopt Patent Owner’s proposed level of ordinary skill in the art, with its inclusion of a Computer Science background, because it is consistent with the evidence of record, including the asserted prior art and ‘984 patent specification. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). However, our Decision would not be altered if Petitioner’s definition applied.” slip op. at 10

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

    “d) Analysis Re Construing “Voice Call Signals” We conclude that it is unnecessary to define “voice call signal.” Patent Owner’s construction would read into the term additional limitations that are for the most part already set forth in the claims: “a switchable mobile communications device capable of . . . voice call communication” (claims 1, 13, 21, 32); “output . . . a voice call signal for transmission . . . over a wireless network” (claims 13, 21, 32); “wherein the mobile communication device is a selected one of a wireless mobile phone and a personal digital assistant equipped with communication capability” (claims 12, 20, 31, 39). Thus the claims require a mobile communications device that is capable of communicating a voice call signal, but do not restrict the voice call signal to only be communicated by a mobile communications device. Likewise, claims 13, 21, and 32 (but not claim 1) require the voice call signal to be transmitted over a wireless network, but do not restrict transmission to only a wireless network, and do not restrict the wireless network to “a network of a wireless network service provider,” as Patent Owner would require.” slip op. at 15

  • Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageTerm construed board ownDisclaimer not foundDecided for petitioner

    “construction for the RFID transponder signal or data terms — it is sufficient for purposes here to conclude that the claims encompass Petitioner’s “functional emulation” articulation. See Reply 11–12. That is, the purpose of the frequent references to “emulated,” “emulation,” or the like in the ‘984 patent is to emphasize the fact that the mobile communications device of the claims has a dual role: to provide voice call communications, and to transmit RFID transponder data. In the latter role, transmitted RFID transponder data appears to an RFID reader to have been transmitted from an ordinary RFID transponder. But there is no need to rewrite the claims to restore the emulation terms, given that, as we discuss further below, Patent Owner deliberately removed those terms during prosecution. The functional emulation implicit in the ‘984 specification and claims” slip op. at 22

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

    “the fact that Willgert teaches that integrating its communications unit into a mobile telephone designed for Bluetooth communication was a “highly user-friendly application,” and that it was well known practice to use a Bluetooth headset wirelessly communicating with the phone to enable hands-free phone calls, as specifically taught by Mooney. Pet. 12–14 (citing Ex. 1004 ¶¶ 8, 30–32; Ex. 1005, Fig. 3, ¶¶ 7, 39, 46–48; Ex. 1021; Ex. 1003 ¶¶ 72–76). Petitioner further argues that Bluetooth headsets were widely available, that incorporating the headset involved known methods yielding predictable results, and that one of ordinary skill would have reasonably expected to succeed in combining the teachings of Willgert and Mooney. Id. at 15–16 (citing Ex. 1004 ¶¶ 8, 10; Ex. 1005, ¶ 8; Ex. 1017, 1, 3; Ex. 1021, 2; Ex. 1003 ¶¶ 77–79). Patent Owner does not specifically address the issue of motivation to combine Willgert and Mooney. See generally PO Resp. We find, based on the record, that Petitioner has proved by a preponderance of the evidence that a person of ordinary skill in the art would have been motivated to combine Willgert and Mooney as proffered by Petitioner with a reasonable expectation of success.” slip op. at 31

  Patent outcomesUS 8,127,984 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,127,984
• Apple Inc. v. Varia Holdings LLCAll claims unpatentable
  PTAB · Feb 27, 2026 · IPR2024-01363 · APJ Norman H Beamer · IPR · Final written decision

  Claims 1–32 are unpatentable under § 103 over Willgert and Mooney, or Willgert, Mooney, Holloway, and Pitroda, as applicable.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner “disputes the narrow range of educational experiences in the Petition’s POSITA definition, but does not otherwise dispute the remaining portion of the definition.” PO Resp. 13. Patent Owner contends that person of ordinary skill in the art: [W]ould have been someone “with at least a Bachelor’s degree in Electrical Engineering, Computer Science, or a related field, with a background in radio frequency communications and software development, as well as approximately two years of experience working with or researching radio frequency communication systems. Lack of work experience can be remedied by additional education, and vice versa.” PO Resp. 13–14 (citing Ex. 2004 ¶ 34).7 Based on a review of the record, we adopt Patent Owner’s proposed level of ordinary skill in the art, with its inclusion of a Computer Science background, because it is consistent with the evidence of record, including the asserted prior art and ’947 patent specification. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). However, our Decision would not be altered if Petitioner’s definition applied.” slip op. at 9

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

    “d) Analysis Re Construing “Voice Call Signals” We conclude that it is unnecessary to define “voice call signal.” Patent Owner’s construction would read into the term additional limitations that are for the most part already set forth in the claims: “the voice call signal is output over a wireless network” (claims 1 ); “outputting the voice call signal over a wireless network” (claim 9); “output a voice call signal for transmission over a wireless network” (claim 16); transmit voice call signals . . . over a wireless network” (claim 26); “wherein the mobile communication device is one of a wireless mobile phone and a personal digital assistant equipped with communication capability” (claims 8, 15, 25, 32). Thus the claims require the voice call signal to be transmitted over a wireless network, but do not restrict transmission to only a wireless network, and do not restrict the wireless network to “a network of a wireless network service provider,” as Patent Owner would require. We also agree that there is nothing in the ’984 prosecution history that supports Patent Owner’s assertion that the Examiner found that the Bluetooth signal of Cooper was not a voice call signal. Cooper was distinguished because: The term “transceiver,” however, is well understood by those of ordinary skill in the art. One of ordinary skill in the art would not reasonably interpret a “transceiver” so broadly as to incorporate an entire mobile device’s circuitry, and in particular to be read on by two separate transmitters, as Cooper teaches. Ex. 1008, 40. On the other hand, we agree with Patent Owner that Petitioner’s” slip op. at 14

  • Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageTerm construed petitioner constructionDecided for petitioner

    “This functional emulation solution is served regardless of how the specific RFID transceiver is implemented — the ’947 specification specifically provides for both software and hardware implementations. Id. at 2:24–28 (“Embodiments of the present invention includes . . . certain hardware and/or software embodied therein for the practice of the emulated RFID method”), 3:35–36 (“mobile communication device 102 is equipped with hardware and/or software elements”), 3:52–54 (“substantial portions of the hardware and/or software elements employed to provide a RFID”), 5:16 (“A Hardware/Software Implementation”). There is no reason why one version of the hardware used to emulate the RFID function could not be RFID transponder circuitry. The issue is not whether an RFID transponder can emulate itself, but rather whether RFID transponder circuitry incorporated into a mobile communications device can be used to allow the mobile communications device to emulate a separate RFID transponder. For example, rather than requiring the person described in the Background of the ’947 patent to carry both a mobile phone and a “key with remote control for gaining access to his/her vehicle,” they need only carry the mobile communications device of the claims. The statement in the ’947 patent that “the present invention is related to an emulated radio frequency data input method” (Ex. 1001, 1:22–24), and the other references to emulation, are consistent with a conclusion that the claims encompass the “functional emulation” option as described above. However, there is no basis for adding the negative limitation proposed by Patent Owner (“without the use of a physical RFID transponder”). Omega Engineering, 334 F.3d at 1333 (rejecting a construction because “neither the plain text of the claims, the specification, nor the file wrapper justifies the imposition of this negative limitation”). See also BillJCo, LLC v. Apple Inc., No. 2023-2189, 2023-2190, 2025 WL 1417957, at *1 (Fed. Cir. May 16, 2025): Our court has “identified claim constructions that exclude a particular element as including a ‘negative limitation’ and held that such exclusions must find support either in ‘the words of the claim’ or through an ‘express disclaimer or independent lexicography in the written description that would justify adding that negative limitation.’” Ethicon LLC v. Intuitive Surgical, Inc., 847 F. App’x 901, 907 (Fed. Cir. 2021). Moreover, the prosecution history of the ’984 grandfather patent is not” slip op. at 22

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

    “Petitioner argues that this combination would have been motivated by the fact that Willgert teaches that integrating its communications unit into a mobile telephone designed for Bluetooth communication was a “highly user- friendly application,” and that it was well known practice to use a Bluetooth headset wirelessly communicating with the phone to enable hands-free phone calls, as specifically taught by Mooney. Pet. 16–18 (citing Ex. 1004 ¶¶ 8, 30, 32; Ex. 1005, Fig. 3, ¶¶ 7, 39, 48; Ex. 1021; Ex. 1003 ¶¶ 62–65). Petitioner further argues that Bluetooth headsets were a well-known concept and widely available, that incorporating the headset involved known methods yielding predictable results, and that one of ordinary skill would have reasonably expected to succeed in combining the teachings of Willgert and Mooney. Id. at 19–21 (citing Ex. 1004 ¶¶ 8, 10, 30; Ex. 1005, ¶ 8; Ex. 1016; Ex. 1017, 1, 3; Ex. 1021, 2; Ex. 1003 ¶¶ 66–68). Patent Owner does not specifically address the issue of motivation to combine Willgert and Mooney. See generally PO Resp. We find, based on the record, that Petitioner has proved by a preponderance of the evidence that a person of ordinary skill in the art would have been motivated to combine Willgert and Mooney as proffered by Petitioner with a reasonable expectation of success.” slip op. at 29

  Patent outcomesUS 9,405,947 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,405,947
• Apple Inc. v. Varia Holdings LLCAll claims unpatentable
  PTAB · Feb 27, 2026 · IPR2024-01362 · APJ Norman H Beamer · IPR · Final written decision

  Claims 1–19 are unpatentable under § 103 over Willgert and Mooney, or over Willgert, Mooney, Holloway, and Pitroda for claims 3–6, 10, 11, and 13–17.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner “disputes the narrow range of educational experiences in the Petition’s POSITA definition, but does not otherwise dispute the remaining portion of the definition.” PO Resp. 12. Patent Owner contends that person of ordinary skill in the art: [W]ould have been someone “with at least a Bachelor’s degree in Electrical Engineering, Computer Science, or a related field, with a background in radio frequency communications and software development, as well as approximately two years of experience working with or researching radio frequency communication systems. Lack of work experience can be remedied by additional education, and vice versa.” PO Resp. 12 (citing Ex. 2004 ¶ 34).7 Based on a review of the record, we adopt Patent Owner’s proposed level of ordinary skill in the art, with its inclusion of a Computer Science background, because it is consistent with the evidence of record, including the asserted prior art and ’974 patent specification. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). However, our Decision would not be altered if Petitioner’s definition applied.” slip op. at 9

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

    “We agree with Patent Owner’s description of the characteristics and operation of a wireless mobile phone, which are not in dispute. Also, the Specification’s description of wireless mobile phones is relied on by Patent Owner in its arguments regarding the construction of “voice call signal,” as discussed below. Nonetheless, Petitioner argues that it is unnecessary to construe the term, “wireless mobile phone.” Reply 4. We agree. The term “wireless mobile phone” is only used in dependent claim 19 (not in independent claim 12, as Patent Owner alleges), and the principal reference relied on by Petitioner (Willgert) explicitly discloses the use of a mobile telephone. Ex. 1001, 12:2; Ex. 1004 ¶¶ 30–32. For these reasons, and because our analysis of the issues set forth below is not dependent on Patent Owner’s proposed construction, it is unnecessary to adopt Patent Owner’s construction or otherwise construe the term “wireless mobile phone.”” slip op. at 12

  • Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageTerm construed petitioner constructionDecided for petitioner

    “to an emulated radio frequency data input method” (Ex. 1001, 1:20–21), and the other references to emulation, are consistent with a conclusion that the claims encompass the “functional emulation” option as described above. However, there is no basis for adding the negative limitation proposed by Patent Owner (“without the use of a physical RFID transponder”). Omega Engineering, 334 F.3d at 1333 (rejecting a construction because “neither the plain text of the claims, the specification, nor the file wrapper justifies the imposition of this negative limitation”). See also BillJCo, LLC v. Apple Inc., No. 2023-2189, 2023-2190, 2025 WL 1417957, at *1 (Fed. Cir. May 16, 2025): Our court has “identified claim constructions that exclude a particular element as including a ‘negative limitation’ and held that such exclusions must find support either in ‘the words of the claim’ or through an ‘express disclaimer or independent lexicography in the written description that would justify adding that negative limitation.’” Ethicon LLC v. Intuitive Surgical, Inc., 847 F. App’x 901, 907 (Fed. Cir. 2021). Patent Owner’s argument that the claim language, “[a] transceiver . . . configured to output . . . RFID transponder [signals or data],” only makes sense “if the transceiver is not itself an RFID transponder” (Sur-Reply 10) is not persuasive. Examination of the complete version of the passage that Patent Owner only paraphrases — “[a] transceiver configured to output voice call signals in the first state and to output RFID transponder signals in the second state” — shows that the transceiver is capable of both voice call and RFID functions, and thus there is no inconsistency in allowing the RFID function to be performed by RFID transponder circuitry incorporated into the transceiver.” slip op. at 24

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

    “Petitioner argues that this combination would have been motivated by the fact that Willgert teaches that integrating its communications unit into a mobile telephone designed for Bluetooth communication was a “highly user-friendly application,” and that it was well known practice to use a Bluetooth headset wirelessly communicating with the phone to enable hands-free phone calls, as specifically taught by Mooney. Pet. 14–17 (citing Ex. 1004 ¶¶ 8, 30–32; Ex. 1005, Fig. 3, ¶¶ 7, 39, 46–48; Ex. 1021; Ex. 1003 ¶¶ 72–76). Petitioner further argues that Bluetooth headsets were widely available, that incorporating the headset involved known methods yielding predictable results, and that one of ordinary skill would have reasonably expected to succeed in combining the teachings of Willgert and Mooney. Id. at 17–19 (citing Ex. 1004 ¶ 10; Ex. 1005, ¶ 8; Ex. 1017, 1, 3; Ex. 1021, 2; Ex. 1003 ¶¶ 77–79). Patent Owner does not specifically address the issue of motivation to combine Willgert and Mooney. See generally PO Resp. We find, based on the record, that Petitioner has proved by a preponderance of the evidence that a person of ordinary skill in the art would have been motivated to combine Willgert and Mooney as proffered by Petitioner with a reasonable expectation of success.” slip op. at 31

  Patent outcomesUS 8,381,974 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 8,381,974
• Charter Communications, Inc. v. Iarnach Technologies Ltd.Some claims unpatentable
  PTAB · Feb 19, 2026 · IPR2024-01287 · APJ Russell E Cass · IPR · Final written decision

  Claim 5 is unpatentable over Bernstein alone or with Tsuge; claims 1–3 and 6–11 were not shown unpatentable because the asserted grounds fail to teach required limitations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner asserts that an ordinarily skilled artisan at the time of the alleged invention “would have at least a bachelor’s degree in electrical engineering, computer science or comparable degree or 2–3 years industry experience designing and/or maintaining back-end networking equipment.” Pet. 11. In the Preliminary Response, Patent Owner stated that it “does not contest Petitioner’s recitation of the level of skill in the art, because even under Petitioner’s proposed level of skill,” Petitioner “has failed to demonstrate a reasonable likelihood of success.” Prelim. Resp. 17. In the Institution Decision, we adopted Petitioner’s proposed definition of a person of ordinary skill in the art, finding that it was consistent with the ’982 patent and the asserted prior art. Inst. Dec. 14 (citing Okajima, 261 F.3d at 1355).” slip op. at 14

  • Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notPreamble limitingDecided for patent owner

    “Following the Institution Decision, both parties submitted proposed claim constructions in the district court stating that the preamble is limiting. Ex. 2009, 3–4 (Petitioner’s Preliminary Claim Construction Chart); Ex. 2010, 7 (Patent Owner’s Preliminary Claim Construction Chart). Patent Owner states in the Patent Owner Response that “[t]he parties now agree that the entire preambles of both claims 1 and 6 are limiting.” PO Resp. 17. In its Reply, Petitioner states that “whether the Board finds the phrase ‘service auto-configuration’” in the preamble to be limiting is “immaterial” because it “does not affect the analysis of whether the prior art cited in the petition invalidates [the challenged] claims.” Pet. Reply 5. At the oral hearing, Petitioner acknowledged that it does not dispute that the entire preamble of claims 1 and 6 is limiting. Tr. 20:25–21:17, 23:15–17. Because the parties agreed in district court that the entire preamble of claims 1 and 6 is limiting, and also agree in this proceeding, we find that the preambles of claims 1 and 6 are limiting for purposes of this Decision. We will discuss the meaning of the preamble further in the sections below applying the prior art to the claims. See §§ III.A..4(a), III.A.7, III.C.1(a), III.C.7, infra.” slip op. at 15

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

    “Based on the record before us, and for purposes of this Decision, we do not need to, and do not, construe any other claim terms to resolve the controversy before us. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))).” slip op. at 16

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

    “Based on the full trial record, we find that Petitioner has failed to meet its burden to show that Bernstein recites a “service auto-configuration” method as recited in the preamble of claim 1. As discussed above, the parties agree that the preamble of claim 1, including the “service auto-configuration method” language, is limiting. See § II.B, supra. As we explained in the Institution Decision, the Petition does not set forth a construction of “service auto-configuration method” or explain how the prior art discloses a “service auto-configuration method.” Pet. 11, 24; Inst. Dec. 32. Instead, the Petition merely explains how Bernstein teaches “a DOCSIS Provisioning of EPON (DPoE) system,” without explaining how it teaches a “service auto-configuration method.” Pet. 24 (citing Ex. 1005 ¶ 59). By failing to offer a construction of “service auto-configuration method” or explain how this limitation is met by the prior art, the Petition fails to show by a preponderance of the evidence that the prior art discloses or suggests this limitation.” slip op. at 34

  Patent outcomesUS 9,287,982 mixed
  Claim construction§ 103 obviousness
  Patents in suitUS 9,287,982
• Universal Electronics, Inc. / Gemstar Technology (Qinzhou) Co. Ltd. et al. v. ROKU, Inc.All claims unpatentable
  PTAB · Jan 21, 2026 · IPR2022-00818 · APJ Russell E Cass · IPR · Remand

  On remand, the Board held claim 11 unpatentable under §103 over Wouters and Verzulli because Wouters’s fixer saves the combined codeset for reinstallation.

  RulingsRemand decision

  • RemandOther

    “We agree with Petitioner that the above-quoted paragraph of Wouters teaches “combining . . . correct working codes from the scanned remote control code-sets into a new custom configuration code set” using Wouters’s “fixer,” which combines the codes into a custom codeset, gives it a name, such as “user1,” and stores it in a memory (the “RC code set data base”). See Pet. Reply 2; Ex. 1009, 10:18–20. This custom codeset includes a combination of the working codes previously tested and installed by the user. Ex. 1009, 10:18–20. We also find that the above-quoted paragraph of Wouters teaches “installing . . . the combined correct working codes of the new custom configuration code set for use by the remote control.” Specifically, Wouters teaches that, when the remote control’s batteries die, “the user may easily reinstall the chosen code set by choosing ‘user1’ from the proposed list or immediately selecting ‘user1.’” Ex. 1009, 10:20–22 (emphasis added). This reinstallation is of the combined correct working codes of a new custom configuration codeset previously stored and named by the fixer, such as the “user1” codeset. Id. at 10:20–24. We find that Wouters’s “reinstallation” of the chosen code set (e.g., the “user1” codeset) is an “installation” of that codeset. The claim merely recites “installing” the codeset, and does not distinguish between an initial installation and a re-installation, such as after the batteries of the remote control die. Ex. 1001, 10:45. Patent Owner also does not point to anything in the ’875 patent Specification or the other intrinsic evidence that would limit the “installing” in limitation 11[e] to an initial installation, or that would exclude a re-installation after the remote control’s batteries die. Consequently, we find that Wouters’s reinstallation of the codeset after the batteries die is an “install[ation]” as required by limitation 11[e]. We further agree with Petitioner that the Wouters-Verzulli combination discloses that these operations would be performed using a processor and memory, which Patent Owner does not appear to dispute. FWD 52; Pet. 24–27, 37; PO” slip op. at 20

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successNot reached

    “Additionally, the obviousness inquiry typically requires an analysis of “whether there was an apparent reason to combine the known elements in the fashion claimed by the patent at issue.” KSR, 550 U.S. at 418 (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006) (requiring “articulated reasoning with some rational underpinning to support the legal conclusion of obviousness”)); see In re Warsaw Orthopedic, Inc., 832 F.3d 1327, 1333 (Fed. Cir. 2016) (citing DyStar Textilfarben GmbH & Co. Deutschland KG v. C.H. Patrick Co., 464 F.3d 1356, 1360 (Fed. Cir. 2006)).” slip op. at 10

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

    “We agree with Petitioner that the above-quoted paragraph of Wouters teaches “combining . . . correct working codes from the scanned remote control code-sets into a new custom configuration code set” using Wouters’s “fixer,” which combines the codes into a custom codeset, gives it a name, such as “user1,” and stores it in a memory (the “RC code set data base”). See Pet. Reply 2; Ex. 1009, 10:18–20. This custom codeset includes a combination of the working codes previously tested and installed by the user. Ex. 1009, 10:18–20. We also find that the above-quoted paragraph of Wouters teaches “installing . . . the combined correct working codes of the new custom configuration code set for use by the remote control.” Specifically, Wouters teaches that, when the remote control’s batteries die, “the user may easily reinstall the chosen code set by choosing ‘user1’ from the proposed list or immediately selecting ‘user1.’” Ex. 1009, 10:20–22 (emphasis added). This reinstallation is of the combined correct working codes of a new custom configuration codeset previously stored and named by the fixer, such as the “user1” codeset. Id. at 10:20–24. We find that Wouters’s “reinstallation” of the chosen code set (e.g., the “user1” codeset) is an “installation” of that codeset. The claim merely recites “installing” the codeset, and does not distinguish between an initial installation and a re-installation, such as after the batteries of the remote control die. Ex. 1001, 10:45. Patent Owner also does not point to anything in the ’875 patent Specification or the other intrinsic evidence that would limit the “installing” in limitation 11[e] to an initial installation, or that would exclude a re-installation after the remote control’s batteries die. Consequently, we find that Wouters’s reinstallation of the codeset after the batteries die is an “install[ation]” as required by limitation 11[e]. We further agree with Petitioner that the Wouters-Verzulli combination discloses that these operations would be performed using a processor and memory, which Patent Owner does not appear to dispute. FWD 52; Pet. 24–27, 37; PO” slip op. at 20

  • Strike new argumentNew argument consideredDecided for petitioner

    “We also find that Petitioner has not forfeited its argument that Wouters’s fixer and reinstallation functionality satisfies limitation 11[e]. The Petition pointed to Wouters’s “fixer” for limitation 11[e], and cited Dr. Houh’s Declaration specifically identifying and quoting Wouters’s disclosure of reinstallation at page 10, lines 14 through 24. Pet. 35 (quoting Ex. 1009, 10:14–20) (citing Ex. 1002 ¶ 167); Ex. 1003 ¶ 167 (quoting Ex. 1009, 10:14–24). We find that a person of ordinary skill in the art reading the Petition and its cited evidence (including paragraph 167 of Dr. Houh’s first Declaration) would be apprised that Petitioner was relying on the portion of Wouters describing the “fixer” and reinstallation functionality.” slip op. at 23

  Patent outcomesUS 8,378,875 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,378,875

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.