- Altria Client Services LLC v. Yiwu Jingangke Trading Co., Ltd.Adverse judgmentPTAB · Oct 1, 2026 · PGR2026-00035 · APJ Robert L Kinder · PGR · Adverse judgment
The Board entered adverse judgment against Patent Owner for abandoning the contest and canceled the sole challenged claim.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“Pursuant to our rules, “[a]ctions construed to be a request for adverse judgment include . . . [a]bandonment of the contest.” 37 C.F.R. § 42.73(b)(4). Our prior order warned that a failure to respond would be construed as an abandonment of the contest under 37 C.F.R. § 42.73(b)(4), and that entry of judgment adverse to Patent Owner and cancellation of the challenged claim may follow. Show Cause Order, 2. Because Patent Owner did not respond by the September 15, 2026, deadline and has not entered an appearance in this proceeding, we determine that Patent Owner has abandoned the contest. Under these circumstances, we enter judgment adverse to the Patent Owner and cancel the challenged design claim.” slip op. at 2
None - BMW Of North America, LLC v. Foras Technologies Ltd.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 7,624,302 - BMW Of North America, LLC v. Foras Technologies Ltd.No claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 7,627,781 - Qualcomm Incorporated v. Cobblestone Wireless, LLCSome claims unpatentablePTAB · 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 mixedClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 7,924,802 - Cisco Systems, Inc. v. Lionra Technologies LimitedAll claims unpatentablePTAB · Mar 4, 2026 · IPR2024-01281 · APJ Steven M Amundson · IPR · Final written decision
Claims 1–3, 5–10, 12–15, and 17–21 are unpatentable as obvious over Cornett, Paatela, and Nelson; claim 8 is also unpatentable with Russell.
RulingsFinal written decision- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“been motivated to combine the teachings of Cornett, Paatela, Nelson, and Russell in the way Petitioner proposes and would have had a reasonable expectation of success. See supra §§ III.E.2(a)–(b). Hence, Petitioner has shown by a preponderance of the evidence that claim 8 is unpatentable under § 103(a) because the claim would have been obvious over Cornett, Paatela, Nelson, and Russell.” slip op. at 122
- Skill levelOther
“B. Level of Ordinary Skill in the Art Factors pertinent to determining the level of ordinary skill in the art” slip op. at 13
Patent outcomesUS 7,738,471 unpatentable§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 7,738,471 - Charter Communications, Inc. v. Iarnach Technologies Ltd.Some claims unpatentablePTAB · 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 mixedClaim construction§ 103 obviousnessPatents in suitUS 9,287,982 - Tiktok Inc. v. Ntech Properties, Inc.Some claims unpatentablePTAB · Feb 6, 2026 · IPR2024-01340 · APJ Terrence W Mcmillin · IPR · Final written decision
Claims 1–12 and 14–18 are unpatentable as obvious over Whitehead, alone or with Marcus ’904; claims 13 and 19–24 were not shown unpatentable.
RulingsFinal written decision- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableNot shown unpatentableMixed
“establishes that the subject matter of independent claim 19 would have been obvious in view of Whitehead. Claim 19 recites “an aggregator having a memory and a processor, the processor adapted for . . . providing an output signal including data indicative of the selection and of user data.” Ex. 1001, 15:51–16:3. As discussed above (Section II.C.2), we construe claim 19 as requiring a signal including both “data indicative of the selection and of user data.” Accordingly, we consider whether Petitioner has shown that Whitehead teaches or suggests that the “aggregator” “provid[e] an output signal including” both “data indicative of the selection and of user data.”” slip op. at 46
- Expert testimonyOther
“Cristofalo’s “user identifiers” represent data about users that Cristofalo’s system uses to “select a specific media object” (advertisements) from received “multi-object programming data.” Cristofalo at ¶ [0048]. For example, a user identifier may indicate that a given user is a Coca-Cola drinker, and when the receiving system receives the multi-object programming data it can select a particular media object out of several possible media objects (e.g., a Pepsi advertisement) to push to the user. Id. This user data exists independently of, and does not relate to, any particular media stream or streams. See Goodrich PO Resp. Decl. at ¶ 135. Petitioner seems to recognize this when tersely referring to “user identifiers” as “data,” not “data relating to a plurality of streams.” Pet. at 71. Accordingly, Cristofalo’s “user identifiers” are not the claimed “data related to the plurality of media streams.” Goodrich PO Resp. Decl. at ¶ 136.” slip op. at 73
Patent outcomesUS 8,145,704 mixed§ 103 obviousnesscites GrahamPatents in suitUS 8,145,704 - Tiktok Inc. v. Ntech Properties, Inc.Some claims unpatentablePTAB · Jan 23, 2026 · IPR2024-01342 · APJ Terrence W Mcmillin · IPR · Final written decision
Claims 1–4 and 6–10 are unpatentable as obvious over each asserted ground; claim 5 was not shown unpatentable because the petitions failed to establish its additional feed and time-period limitations.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner
“1b, 1c, and 1e of claim 1 and in claims 4 and 5 of the ’753 patent. Patent Owner contends that the plain and ordinary meaning of “feed” is “one or more associated media elements.” See, e.g., PO Resp. 4. However, as discussed below, this alleged plain and ordinary meaning of feed is not supported by the claim language, the specification of the ’753 patent, or dictionary definitions of feed as contended by Patent Owner. We reject this contention and the related contentions that the cited art may be distinguished from the claims of the ’753 patent based on the recited term “feed.” Patent Owner relies on the language of claim 1 to support its” slip op. at 13
- Skill levelSkill level petitioner adoptedDecided for petitioner
“The parties’ definitions are similar, although we observe that Patent Owner proposes that the person of ordinary skill would have a bachelor’s degree or an equivalent or professional experience, whereas Petitioner proposes that such a person would have both a degree and experience. Neither party presents any arguments relating or referring to the level of ordinary skill in the art. Determining the level of ordinary skill in the art involves various factors, 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 prior art of record also reflects the level of ordinary skill in the art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). We adopt Petitioner’s assessment of the level of skill in the art. Petitioner’s assessment is supported by the testimony of Dr. Almeroth and is consistent with the ’753 patent and the asserted prior art. However, our obviousness analysis would be the same under either party’s assessment. See Ex. 2014 ¶ 17 (Patent Owner’s declarant, Dr. Goodrich, stating that “I note that my definition of a POSITA is similar to that of Dr. Almeroth” and “My opinions in this declaration would not change were I to adopt the definition of a POSITA offered by Dr. Almeroth.”).” slip op. at 11
- Expert testimonyPetitioner expert discountedDecided for patent owner
“16 With regard to claim 5, the Petition cites paragraphs 97 and 98 of the Almeroth Declaration (Ex. 1002). See Pet. 28–29. We have considered the cited paragraphs in the Almeroth Declatation and found that they consist of nothing more than the inadequate and conclusory contentions in the Petition preceded by, in paragraph 97, “[i]n my opinion” and “it is my opinion” and, in paragraph 98, “[i]t is also my opinion.” Ex. 1003 ¶¶ 97, 98. As related to claim 5, we accord the Almeroth Declaration little or no weight. See 37 C.F.R. § 42.65 (a) (“Expert testimony that does not disclose the underlying facts or data on which the opinion is based is entitled to little or no weight.”). that might become out-of-date before a user accesses access [sic] them. Ex. 1003, 11:49–58 (emphasis added). The cited passage in Whitehead mentioning “near real-time” does not support finding that Whitehead teaches or suggests the elements recited in claim 5.” slip op. at 39
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“Petitioner contends, “[a] POSITA would have modified Whitehead’s mixing server 130 to incorporate Marcus ’904’s algorithm (running on Marcus ’904’s receiver) for receiving, selecting, ordering, and assembling different media streams (both for content and advertising).” Pet. 33. Petitioner supports this contention by articulating the following reasons for the asserted modification of Whitehead’s mixing server 130 to incorporate Marcus ’904’s algorithm: “makes it more likely the system will identify content best suited for a particular user,” “allows for more targeted advertising and/or an opportunity to maximize revenue,” “improves Whitehead’s ability to target content and advertising to a particular user,” “would unlock new revenue sources for Whitehead,” “Marcus ’904’s content selection and concatenation algorithm improves Whitehead’s efficiency,” “[b]oth Whitehead and Marcus ’904 generate custom media programming based on a user profile,” “incorporating Marcus ’904’s teachings would not require redesigning Whitehead’s architecture and instead merely supplements Whitehead’s disclosure,” and “Petitioner’s proposed modification can be implemented entirely in software and does not require any hardware modifications. Indeed, Whitehead acknowledges that such modifications are possible. EX1003 at 19:64-20:6, 22:26-40.” Id. at 33–35 (citing Ex. 1002 (Almeroth Decl.) ¶¶ 110–115) (emphasis omitted). Based on this undisputed showing, we find that one of ordinary skill would have had a motivation to combine the teachings of Whitehead and Marcus ’904 as asserted in the Petition with a reasonable expectation of success.” slip op. at 48
Patent outcomesUS 8,886,753 mixedClaim construction§ 103 obviousnesscites GrahamPatents in suitUS 8,886,753 - Reed Semiconductor Corp. v. Monolithic Power Systems, Inc.All claims unpatentablePTAB · Jan 22, 2026 · IPR2024-01158 · APJ Ken B Barrett · IPR · Final written decision
Claims 1–5, 7–15, 17, and 18 are unpatentable: claims 1–4, 9–14, 17, and 18 as anticipated by Tateishi, and claims 5, 7, 8, and 15 as obvious over Tateishi.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“We discern no material difference between the parties’ definitions. Petitioner’s definition is consistent with the level of ordinary skill reflected in the prior art references of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (recognizing that the prior art itself may reflect an appropriate level of skill in the art). For purposes of this decision, we apply Petitioner’s definition of the person of ordinary skill in the art. We note, however, that were we to adopt Patent Owner’s assessment, the outcome of this Decision would be the same.” slip op. at 13
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“After considering the parties’ arguments and evidence, we determine that Patent Owner has not offered persuasive evidence that a person of ordinary skill in the art reading the claims in light of the Specification would understand the plain and ordinary meaning of “control signal” to be as narrow as Patent Owner proposes. We do not construe the claims such that the “control signal” must be the exclusively controlling factor of a component, as Patent Owner urges. Petitioner’s position, on the other hand, is consistent with the evidence of record. We construe “control signal” as having its plain and ordinary meaning, namely a signal configured to control a circuit component. D. The Asserted Anticipation of Claims 1–4, 9–14, 17, and 18 by Tateishi” slip op. at 24
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“We determine that Petitioner has demonstrated by a preponderance of the evidence that Tateishi discloses the “control signal” recited in limitations 1B2 and 1D of independent claim 1.” slip op. at 37
- BurdenNot shown unpatentable
“based on the Tateishi application publication (Ex. 1007), that the Tateishi Patent (Ex. 1005) also anticipates claims 1–4, 9–14, 17, and 18. See Pet. 23–24 (“The Tateishi Patent is also prior art under (pre-AIA) §102(e)”; identifying Ground 1 as anticipation “under §102 by Tateishi and/or the Tateishi Patent”). However, we are unable to locate in the Petition or Petitioner’s Reply a discussion of or citation to the Tateishi Patent other than under the Petitioner’s heading “Identification of Challenge and Relief Requested” on pages 23 and 24 of the Petition. Cf. id. at i–x (Table of Contents identifying a section of the Petition discussing the Tateishi (Application) anticipation ground but not a section discussing a Tateishi Patent anticipation ground). Although the issued patent may be substantively identical to the published application, Petitioner does not assert that, and we decline to compare the documents to determine whether that is the case. In light of Petitioner’s silence on the alternative ground, Petitioner has not demonstrated by a preponderance of the evidence that the Tateishi Patent anticipates 1–4, 9–14, 17, and 18.” slip op. at 47
Patent outcomesUS 9,041,377 unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 9,041,377 - Universal Electronics, Inc. / Gemstar Technology (Qinzhou) Co. Ltd. et al. v. ROKU, Inc.All claims unpatentablePTAB · 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 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents 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.