- Cisco Systems, Inc. v. Portsmouth Network Corp.No claims unpatentablePTAB · Mar 31, 2026 · IPR2024-01450 · APJ Peter D Shapiro · IPR · Final written decision
Claims 1–4, 6–11, and 13–20 were not shown unpatentable because Dziong and Sathyanath do not teach the claimed sharing definition for existing connections with allocated bandwidth.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“First, the claims use present-tense language, “one or more other connections, which have respective bandwidths and which are permitted to share a bandwidth allocation with the new connection.”3 Ex. 1001, claim 1 (emphasis added). The exclusive use of the present tense have indicates “other connections” must have current possession of the bandwidth. For these other connections to share bandwidth with a newly established connection, they must already exist and have bandwidth ready for immediate use, rather than merely holding a dormant “reservation” pending a network failure. See PO Supp. Br. 1. The Federal Circuit addressed a similar situation where the Court found the present-tense limitation “is connected to the computer network” means a device was required to be connected at the” slip op. at 15
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“combination, do not teach or suggest limitations 1.2 and 1.3 requiring: providing a sharing definition specifying one or more other connections, which have respective bandwidths and which are permitted to share a bandwidth allocation with the new connection, such that a total bandwidth allocated jointly to the new connection and to the other connections in any given segment is equal to a maximum of the requested bandwidth and of the bandwidths of the other connections in the given segment Ex. 1001, limitations 1.2, 1.3 (emphasis added); see PO Resp. 17–22; Sur-reply 4–5, 12–14. As discussed above in Section II.C.2, we interpret “other connections” to mean “existing connections in the network that already have bandwidth allocated to them.” Because the information shared in Dziong and Sathyanath, described below, relates to reserved protection paths, rather than existing connections that have bandwidth that can currently transmit network traffic, the references do not teach or suggest the “other connections” part of the sharing definition in limitations 1.2 and 1.3. Dziong describes advertising, across the network, the amount of bandwidth reserved for recovery on each link that would be activated when a protected link fails. See, e.g., Ex. 1005 ¶ 60; Pet. 36. Once activated, network traffic from a “primary path” failure is rerouted to these recovery paths. See Ex. 1005 ¶¶ 7–9, 70, 83. Petitioner points to this advertising of the reserved bandwidth information as teaching the claimed “sharing definition.” Pet. 33–36 (arguing that the “protection paths [in Dziong] have bandwidth reservations” and “share an overall protection bandwidth reservation”); Reply 21–23. However, since the advertised information only contains information about the recovery paths “that would be activated” upon a primary path failure, such paths are not existing connections that already have bandwidth allocated to them, and therefore do not teach the claimed “other connections” that are part of the sharing definition. See, e.g., Ex. 1005 ¶ 60.” slip op. at 43
Patent outcomesUS 7,596,088 not shown unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 7,596,088 - 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 - 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 - Netflix, Inc. v. Avago Technologies International Sales Pte. LimitedAll claims unpatentablePTAB · Jan 21, 2026 · IPR2021-01343 · APJ Kristen L Droesch · IPR · Remand
Claims 6, 8, 11, and 17 are unpatentable as obvious over the combined teachings of Cooper and Baldwin.
RulingsRemand decision- RemandOther
“The Federal Circuit vacated the Board’s determination as to claims 6, 8, 11, and 17 and remanded to the Board to address Petitioner’s motivationto-combine arguments for Cooper and Baldwin in view of the Board’s finding that Cooper does not teach limitation 1[d], and to address whether Cooper teaches the additional limitations of claims 6, 8, 11, and 17. See Fed. Cir. Dec. 10. The Federal Circuit faulted the Board’s conclusion as failing to provide substantive analysis of Petitioner’s motivation to combine arguments. See id. at 8. In particular, the court explained that Petitioner provided a detailed explanation of why a person of ordinary skill in the art would have been motivated to combine Cooper’s receiver teachings with Baldwin’s teachings of providing alternative streams with staggered access points and selecting the stream with the next available access point. See id. at 8–9. The court highlighted Petitioner’s following arguments: (1) a person of ordinary skill in the art would have combined the prior art according to known methods to yield predictable results; (2) combining the prior art would have been a simple substitution of one known element for another to obtain predictable results; and (3) the combination represents a choice from a finite number of identified predictable solutions with a reasonable expectation of success. See id. at 9. Accordingly, the issues before us are whether a person of ordinary skill in the art would have been motivated to combine the teachings of Cooper and Baldwin and whether Cooper teaches the additional limitations of dependent claims 6, 8, 11, and 17. See Fed. Cir. Dec. 8–10. To provide the full context for the issues before us, we first address each of the limitations of independent claims 1 and 12, and Petitioner’s reasons for combining the teachings of Cooper and Baldwin, followed by an analysis of the limitations of dependent claims 6, 8, 11, and 17.” slip op. at 8
- Skill levelSkill level board ownDecided for petitioner
“II. ANALYSIS A. Level of Ordinary Skill in the Art As previously set forth in the Final Written Decision, we determine a person of ordinary skill would have had a bachelor’s degree in electrical 3 U.S. Patent No. 7,810,124 B2, issued Oct. 5, 2010 (Ex. 1004). 4 U.S. Patent No. 7,603,689 B2, issued Oct. 13, 2009 (Ex. 1005). engineering, computer engineering, computer science, or a similar field and two years of experience in digital video signal processing or digital video streaming, which is consistent with the parties’ arguments, the ’014 patent, and the prior art of record. See Final Dec. 5.” slip op. at 5
- BurdenUnpatentable
“Based on the entire record, including the Final Written Decision, and Federal Circuit Decision, and after having considered Petitioner’s citations to Cooper, Baldwin, and Mr. Wechselberger’s testimony (Ex. 1003), we are persuaded Petitioner sets forth sufficient articulated reasoning with rational underpinning to support the conclusion that it would have been obvious to one of ordinary skill in the art to combine the teachings of Cooper and Baldwin by substituting Baldwin’s teachings of providing alternative streams with staggered access points and selecting the stream with the next available access point in place of Cooper’s teaching of identifying which alternative stream is readily available or not time-delayed to yield predictable results with the benefit of allowing a more objective-effective identification of the next available stream. See Pet. 18–23; Ex. 1003 ¶¶ 54–58; Ex. 1004, 2:58–62, 4:15–38, 5:5–23, 5:39–62, 6:5–49, 7:8–22, 17:23–45, 18:17–31, 18:57–19:3, 19:19–23, 19:41–45, 23:56–64, 24:10–19; Ex.1005, 1:25–41, 2:5–15, 6:31–35, 6:55–61, 7:40–47, 9:24–28, 10:18–24, 12:42–44; KSR, 550 U.S. at 418. e) [1e] “processing, by the receiver, the identified video information stream” slip op. at 14
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
“Based on the entire record, including the Final Written Decision, and Federal Circuit Decision, and after having considered Petitioner’s citations to Cooper, Baldwin, and Mr. Wechselberger’s testimony (Ex. 1003), we are persuaded Petitioner sets forth sufficient articulated reasoning with rational underpinning to support the conclusion that it would have been obvious to one of ordinary skill in the art to combine the teachings of Cooper and Baldwin by substituting Baldwin’s teachings of providing alternative streams with staggered access points and selecting the stream with the next available access point in place of Cooper’s teaching of identifying which alternative stream is readily available or not time-delayed to yield predictable results with the benefit of allowing a more objective-effective identification of the next available stream. See Pet. 18–23; Ex. 1003 ¶¶ 54–58; Ex. 1004, 2:58–62, 4:15–38, 5:5–23, 5:39–62, 6:5–49, 7:8–22, 17:23–45, 18:17–31, 18:57–19:3, 19:19–23, 19:41–45, 23:56–64, 24:10–19; Ex.1005, 1:25–41, 2:5–15, 6:31–35, 6:55–61, 7:40–47, 9:24–28, 10:18–24, 12:42–44; KSR, 550 U.S. at 418. e) [1e] “processing, by the receiver, the identified video information stream” slip op. at 14
Patent outcomesUS 8,646,014 unpatentable§ 103 obviousnesscites PhillipsPatents in suitUS 8,646,014 - Juniper Networks, Inc. v. Portsmouth Network Corp.Some claims unpatentablePTAB · Jan 13, 2026 · IPR2024-00913 · APJ Justin T Arbes · IPR · Final written decision
Claims 1, 2, 4, 6, 7, 11, 12, 14, 16, and 17 are unpatentable over Blease, Weyman, and Hu, with some claims also over Deng; claims 8–10 and 18 were not shown unpatentable.
RulingsFinal written decision- Expert testimonyPetitioner expert discountedOther
“disclosure in Weyman (or Blease) for deactivating and activating ports, or performing certain actions in the time between such actions. Again, the only portion of Weyman cited pertains to a request to join the fabric from a processing unit having a “default” configuration, which does not relate to the timing or sequence of events in initialization. See Ex. 1006 ¶¶ 69, 156, 161–162; Ex. 1103 ¶¶ 93–94. Nor does Dr. Lavian point to any other evidence in the record supporting his conclusion that a person of ordinary skill in the art would have “ensure[d] that the processing unit is deactivated prior to being updated for use . . . and then activate[d] the processing unit after updating.” See Ex. 1103 ¶ 94. Accordingly, we give little weight to Dr. Lavian’s conclusory opinion” slip op. at 75
- Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableUnpatentable
“See Axonics, 73 F.4th at 957; Allied Erecting, 825 F.3d at 1381; Mouttet, 686 F.3d at 1332–33. Petitioner’s position is that, based on the teachings of Weyman, a person of ordinary skill in the art would have modified Blease’s system to distribute the functionality of control unit 44 (including its existing multicast forwarding information 48 used by OIF mapper 50). See Pet. 23–26, 38; Fleming v. Cirrus Design Corp., 28 F.4th 1214, 1222 (Fed. Cir. 2022) (“That the proposed combination of [two references]—rather than one of the individual references—discloses the disputed claim limitations does not defeat the Board’s conclusion of obviousness. In this case, it is sufficient that a person of ordinary skill in the art would have been motivated to combine the prior art in a way such that the combination discloses the claim limitations.”).” slip op. at 55
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“10 In the Cisco IPR, we determined that Cisco had proven claims 8 and 18 to be unpatentable based on a different combination of references (identified as Weyman, Jain, and LeMaire), finding that limitation 8[f.ii] was taught by Jain and LeMaire. IPR2024-00506, Paper 38 at 58–77. As explained herein, we are not persuaded by Petitioner’s arguments in this proceeding that limitation 8[f.ii] is taught or suggested by Weyman. Also, in the Decision on Institution in this proceeding, the Board found that there were questions as to Petitioner’s showing for limitation 8[f.ii] and declined to reach a conclusion on whether Petitioner had shown a reasonable likelihood of prevailing on its asserted ground based on Blease and Weyman. Dec. on Inst. 43.” slip op. at 71
Patent outcomesUS 8,014,394 mixed§ 103 obviousnesscites KSR · GrahamPatents in suitUS 8,014,394 - Juniper Networks, Inc. v. Portsmouth Network Corp.All claims unpatentablePTAB · Dec 9, 2025 · IPR2024-00893 · APJ Justin T Arbes · IPR · Final written decision
Claims 3, 8, 11, 12, 15, 20, 23, and 24 are unpatentable as obvious over Gai and IEEE 1999.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner argues that at the time of the application for the ’986 patent (January 2002), a person of ordinary skill in the art would have had “a bachelor’s degree in electrical engineering or a related field, plus at least two years of industry experience or graduate-level academic experience with computer networking.” Pet. 20. In the Decision on Institution, the Board agreed with and applied Petitioner’s proposed definition, removing the phrase “at least” to avoid unnecessary ambiguity. Dec. on Inst. 18–19. Patent Owner uses Petitioner’s proposed definition for its Response. PO Resp. 5. Neither party made any further argument regarding the level of ordinary skill in the art in its papers during trial. In the Cisco IPR, we adopted a similar definition, determining that a person of ordinary skill in the art would have had “a bachelor’s degree in computer science, computer engineering, electrical engineering, or in an equivalent field, or approximately two years of experience working in the field of information technology and networking,” where “[l]ack of professional experience can be substituted by additional education, and vice versa.” IPR2024-00505, Paper 29 at 10–11 (alteration in original); see Dec. on Inst. 19 n.7 (noting the proposed definition in the Cisco IPR). Based on the full record developed during trial, including our review of the ’986 patent and the types of problems and solutions described in the ’986 patent and cited prior art, we adopt the same definition of the level of ordinary skill in the art as the Cisco IPR and apply it for purposes of this Petitioner’s similar proposed definition in this proceeding.” slip op. at 12
- Expert testimonyPetitioner expert creditedDecided for petitioner
“Gai discloses entering an Enable_Uplinkfast command at an access switch (e.g., access switch 114) to block a failed port (e.g., the root port) and configure the access switch to send dummy traffic upstream through a new active port. . . . When modified in view of IEEE 1999’s disclosure that self-healing network traffic can advantageously be sent both upstream and downstream, the command would be entered at a backbone switch (e.g., backbone switch 122) to block a failed port (e.g., a designated port connected to access switch 114) and configure the backbone switch to send dummy traffic downstream to an access switch (e.g. access switch 114) through a new active port. While Gai uses its protocol signaling command, Enable_Uplinkfast, to send dummy traffic through a new root port, [a person of ordinary skill in the art] would deem it an obvious implementation detail to modify the parameters of the port on a backbone switch. See Ex. 1003 ¶ 139 (citing Ex. 1005, col. 6, ll. 39–46).” slip op. at 34
- Prior constructionPrior construction adoptedDecided for petitioner
“In the Cisco IPR, we addressed four claim terms in the final written decision: “access switch” and “edge switch,” which appear in independent claims 1 and 13 and various dependent claims, and “downstream” and “upstream,” which appear in claims 11, 12, 23, and 24. IPR2024-00505, Paper 29 at 11–14. We interpreted “access switch” to mean “a switch with ports that connect to LANs and/or to other network endpoints, such as user computer systems,” interpreted “edge switch” to mean “a core switch that is directly connected to an access switch,” interpreted “downstream” to mean “away from the root switch,” and interpreted “upstream” to mean “toward the root switch.” Id. As noted above, Patent Owner did not appeal that decision. We incorporate herein our previous analysis in the Cisco IPR, but note that none of the analysis of the disputed issues below depends on such determine whether Petitioner has met its burden to prove unpatentability of the challenged claims. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“Because we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy,’ we need not construe [a particular claim limitation] where the construction is not ‘material to the . . . dispute.’” (emphasis added) (citation omitted)).” slip op. at 13
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“1999, supported by the testimony of Mr. McNair, which we credit, is persuasive. See Pet. 25–30, 40–46; Ex. 1003 ¶¶ 132–145, 165–174. Based on the full trial record, we find that Gai and IEEE 1999 teach limitation [1E] and that a person of ordinary skill in the art would have been motivated to combine their teachings in the manner described by Petitioner. Based on all of the evidence of record, we determine that Petitioner has proven, by a preponderance of the evidence, that claim 3 would have been obvious over Gai and IEEE 1999 under 35 U.S.C. § 103(a). 4. Claims 8, 15, and 20 Claim 8 depends indirectly from independent claim 1. Claims 15 and 20 depend indirectly from independent claim 13, which is similar to claim 1 but recites a network switching device rather than a method. As to independent claim 13, Patent Owner refers to its earlier arguments regarding claim 1, asserting that limitation [13C] is “substantially similar” to limitation [1E]. PO Resp. 14–15. We disagree with Patent Owner’s arguments for the reasons explained above. See supra Section II.D.3.b. Patent Owner does not argue dependent claims 8, 15, and 20 separately from their respective parent claims 1 and 13. See PO Resp. 19. We have reviewed Petitioner’s contentions and supporting evidence, including the testimony of Mr. McNair, and are persuaded that Petitioner has proven, by a preponderance of the evidence, that claims 8, 15, and 20 would have been obvious based on Gai and IEEE 1999 under 35 U.S.C. § 103(a), for the reasons stated by Petitioner. See Pet. 21–46, 48–52, 55–59; Ex. 1003 ¶¶ 113–175, 179–185, 194–203.” slip op. at 41
Patent outcomesUS 6,917,986 unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 6,917,986
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.