• Crowdstrike, Inc. v. Gosecure, Inc.Some claims unpatentable
  PTAB · Aug 12, 2026 · IPR2025-00070 · APJ Neil T Powell · IPR · Final written decision

  Claims 1, 3–7, and 9–21 are unpatentable as obvious; claims 2 and 8 were not shown unpatentable because the asserted art did not meet their construed limitations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “III. ANALYSIS LEVEL OF ORDINARY SKILL A. Petitioner explains the applicable level of skill in the art as follows: As of June 24, 2010, a person of ordinary skill in the art (POSITA) would be a person having a bachelor’s degree in computer science, computer engineering, or an equivalent, as well as two years of industry experience and who would have had a working knowledge of software security analysis, and dynamic malware analysis. Additional graduate education could substitute for professional experience, or significant experience in the field could substitute for formal education. Pet. 8 (Ex. 1003 ¶¶ 30–31). Patent Owner does not dispute Petitioner’s explanation of the level of skill in the art. See Ex. 2031 ¶¶ 15–16. We adopt Petitioner’s uncontested proposed level of ordinary skill in the art, which we find consistent with the level of ordinary skill in the art reflected by the ’872 patent and the prior art of record. See Okajima v.” slip op. at 12

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

    “We begin with the claim language in view of the Specification, which weighs heavily against Patent Owner’s position that we should rewrite “computer system” as narrowly referring to a “computing device.” PO Resp. 24. As Petitioner notes, the ’872 patent’s Specification uses “computer system” to refer to a wide range of equipment, from a component of a computing device, to a whole computing device, to a collection of computing devices. Reply 9–10 (citing Ex. 1001, 4:5–8, 11:15–18, 16:50–55). In one example, the Specification refers to “one or more other computer systems (e.g., protected network devices 136).” Ex. 1001, 18:52–53. Thus, the Specification lists “protected network devices 136” as only an example of “other computer systems,” demonstrating that “computer systems” refers to things other than protected network devices. Although Patent Owner may be correct that this passage more than a single computing device,” we find that other disclosures in the ’872 patent do. Specifically, the Specification uses the language “distributed computer system” when referring to numerous components, including “protected network devices” and an “IDS/IPS system.” Ex. 1001, 3:26–28; Reply 10. In addition to showing that a “computer system” is not limited to a single computing device, this conveys that a “computer system” according to the ’872 patent can include an IDS/IPS.” slip op. at 14

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

    “Based on our review of the complete record, we find Petitioner’s arguments and evidence to be more persuasive. Patent Owner does not dispute Petitioner’s argument and evidence that capturing detailed information like Goel’s activity sources, activity targets, and association was recognized as enhancing threat analysis. Pet. 44 (citing Ex. 1003 ¶ 79); see PO Resp. 55–59; Sur-Reply 15–17. Additionally, contrary to Patent Owner’s suggestion, we find that the Petition does not propose incorporating Goel’s kernel hooks into Capalik’s system. See Pet. 41–46. Patent Owner contends that the Petition’s reference to modifying Capalik by “adding lines of code” suggests implementing the code disclosed in Goel include kernel hooks. Id. Notwithstanding Patent Owner’s assertion otherwise, this is an unpersuasive bodily incorporation argument, as the Petition never says an ordinarily skilled artisan would have used the exact lines of code from Goel in Capalik. Rather, the Petition says that an ordinarily skilled artisan would have had sufficient skill to implement straightforward code modifications to identify activity sources, targets, and associations: a [person of ordinary skill in the art] would have understood that modifying Capalik’s system (e.g., Linux-based) to additionally monitor, identify, and store each individual activity of an attack including “activity sources, activity targets, and associations” would have required straightforward modifications to programs/code instructions, which would have been well-within the skillset of a [person of ordinary skill in the art]. Pet. 46. Patent Owner argues that Petitioner does not explain how an ordinarily skilled artisan would have modified Capalik without using kernel hooks. Sur-Reply 17. But Patent Owner does not cite any evidence to counter Dr. Jakobsson’s testimony that an ordinarily skilled artisan would have had the skill to apply Goel’s general teaching of identifying sources, targets, and associations to Capalik’s system. Ex. 1003 ¶ 182. On the whole, the evidence does not support Patent Owner’s position that the combination would have required substantially increased detection risk. Moreover, even if the combination would have somewhat increased detection risk, Petitioner persuades us that an ordinarily skilled artisan still would have had reason to combine the references teachings. Patent Owner’s allegations of increased detection risk do not negate the undisputed evidence that the combination would have provided the advantage of improved threat analysis. Pet. 44 (citing Ex. 1003 ¶¶ 175–182). Ultimately, Patent Owner’s that activity logging be undetectable.” PO Resp. 56 (emphasis added) (citing Ex. 1004 ¶ 6). This exaggerates Capalik’s disclosure. Although the cited paragraph suggests that certain systems unfortunately may be detectable by some users, it does not convey that it is a requirement for the system to be categorically undetectable. See Ex. 1004 ¶ 6.8 In sum, Petitioner persuades us by a preponderance of the evidence that it would have been obvious to modify Capalik “to identify and store unauthorized activities including the activity source, activity target, and association of each activity.” Pet. 41–46; PO Resp. 55–59; Reply 20–22; Sur-Reply 15–17.” slip op. at 47

  • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for patent owner

    “arguments and evidence, we determine that Patent Owner fails to sufficiently show a nexus between any of its objective indicia evidence and the claimed invention. See Fox Factory, Inc. v. SRAM, LLC, 944 F.3d 1366, 1373 (Fed. Cir. 2019) (“The patentee bears the burden of showing that a nexus exists”). A showing of sufficient nexus is required to establish that the evidence relied upon traces its basis to a novel element in the claim, not to something in the prior art. Institut Pasteur & Universite Pierre Et Marie Curie v. Focarino, 738 F.3d 1337, 1347 (Fed. Cir. 2013). Objective evidence that results from something that is not “both claimed and novel in the claim” lacks a nexus to the merits of the invention. In re Kao, 639 F.3d 1057, 1068 (Fed. Cir. 2011) (emphasis omitted). Thus, establishing nexus involves a showing that novel elements in the claim, not prior-art elements, account for the objective evidence of nonobviousness. Id. As discussed above, Petitioner shows that Capalik teaches all limitations of claim 1. Petitioner persuades us that none of claim 1’s elements individually nor any combination thereof is novel over Capalik’s disclosure. Accordingly, claim 1 is not novel over Capalik, which disproves Patent Owner’s assertion of nexus. PO Resp. 73–76. Moreover, even if claim 1 were novel, Patent Owner otherwise fails to show nexus for its commercial success, praise, or copying assertions. Patent Owner’s evidence does not show that Petitioner’s commercial product embodies claim 1. For example, we agree with Petitioner that Patent Owner “failed to analyze any meaningful detail regarding” how the Falcon Platform allegedly meets limitation 1(d). Reply 28–29. In particular, Patent Owner has not sufficiently addressed limitation 1(d) with the following argument: “1[D] The Falcon Platform transmitted to other computer systems” slip op. at 37

  Patent outcomesUS 9,954,872 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 9,954,872
• Samsung Display Co., Ltd. v. Pictiva Displays International Ltd.Some claims unpatentable
  PTAB · Feb 17, 2026 · IPR2024-01187 · APJ Garth D Baer · IPR · Final written decision

  Claims 1, 2, 8–11, and 16 are unpatentable as obvious over Ingle and Hasei; claims 3, 5, and 6 were not shown unpatentable because the Hanamura-based grounds lack the claimed trench.

  RulingsFinal written decision

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

    “isolation, rather than in the claims’ context, and in light of the ’492 patent’s specification. In the trench/layers context of the ’492 patent, the word in requires more than it does in the circle/square context.” slip op. at 6

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “a bachelor’s degree in Electrical Engineering, Physics, or a comparable field of study, and at least three years of research or industrial experience with semiconductor (organic or inorganic) optoelectronic devices and/or lighting or displays. An individual with additional education could have less research or industrial experience and vice-versa. Pet. 9. Patent Owner does not dispute Petitioner’s proposed definition. We adopt Petitioner’s uncontested proposed definition because it is consistent with the disclosures of the asserted prior art.” slip op. at 9

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “rather than the combination of Ingle’s capacitor and Hasei’s droplet discharge application that Petitioner asserts. See In re Keller, 642 F.2d 413, 426 (CCPA 1981). Even if Ingle falls short of teaching structured application for its capacitor’s cathode, as Patent Owner argues, that does not undermine Petitioner’s challenge because Petitioner proposes using Hasei’s structured application (i.e., a droplet discharge device) to form the cathode of Ingle’s capacitor. See Pet. 24–25. Patent Owner’s additional argument that “Hasei contains no discussion of forming capacitors” (PO Resp. 36; see PO Sur-reply 17–18) is similarly flawed—it attacks Hasei individually, while ignoring Ingle’s capacitor teaching. We agree with Petitioner—the combination of Ingle and Hasei teaches structured application of the capacitor’s cathode. In addition, we disagree with Patent Owner that “Petitioner provides no reason why a POSITA would have extended Hasei’s method for producing its OLED to a capacitor.” PO Resp. 36; see PO Sur-reply 17 (asserting “pure conjecture”). To the contrary, as noted above, Petitioner explains, with relevant support from Hasei, that its structured application method reduced electrode-material waste and shortened manufacturing times as compared to photolithography. Pet. 25 (citing Ex. 1007 ¶¶ 5, 7). Given those benefits, Petitioner has articulated sufficient reasoning with rational underpinning to support that its proffered combination would have been obvious. See KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 418 (2007).” slip op. at 13

  Patent outcomesUS 9,257,492 mixed
  Claim construction§ 103 obviousnesscites KSR
  Patents in suitUS 9,257,492
• Samsung Display Co., Ltd. v. Pictiva Displays International Ltd.Some claims unpatentable
  PTAB · Jan 22, 2026 · IPR2024-01094 · APJ Grace Karaffa Obermann · IPR · Final written decision

  Claims 1, 2, 6, and 8–14 are unpatentable as obvious over Ma; claims 3 and 4 were not shown unpatentable over Werner.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends: A person of ordinary skill in the art (“POSA”) at the time of the alleged invention of the ’223 patent would have had a university degree in chemistry and additional expertise or a second university degree in the field of electrical engineering, particularly optoelectronics, or alternatively a university degree in electrical engineering and additional expertise or a second university degree in the field of chemistry. The person of ordinary skill in the art has spent several years studying the structure and function of organic optoelectronic components, in particular OLEDs, and has detailed knowledge of the chemical structure of light-emitting organic layers and the transport of charge carriers to these layers. In this respect, the person of ordinary skill in the art works at the interface between electrical engineering/physics (charge carrier transport and light emission processes in optoelectronic components) and chemistry, in particular organic chemistry (materials and layer stack combinations suitable). Pet. 14 (citing Ex. 1003 ¶¶ 46–47). Patent Owner does not dispute Petitioner’s contention. See generally Resp. Neither party indicates that the result would change depending on the definition selected. We adopt Petitioner’s uncontested proposed definition, because it is consistent with the disclosures of the asserted prior art references. See Ex. 1005, (code 57); Ex. 1007, 8107 (abstracts of the references asserted in the patentability challenges).” slip op. at 8

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

    “history pertaining to the patent.” 37 C.F.R. § 42.100(b). Under that standard, claim terms generally are given their plain and ordinary meaning as would have been understood by the ordinarily skilled artisan at the time of the invention and within the context of the entire patent disclosure. See Phillips v. AWH Corp., 415 F.3d 1303, 1313 (Fed. Cir. 2005) (en banc). We construe claim terms only as relevant to the parties’ contentions and only to the extent necessary to resolve the issues in dispute. See Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999); Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017). Neither party indicates that an express construction for any claim term is necessary to resolve the disputes at hand. Pet. 15; see generally Resp. On this record, we determine that no claim term requires express construction for purposes of this Decision. In our analysis of the challenges, however, we discuss the meaning of the terms “metal complex” and “central metal atom,” which appear in claim 1 (Ex. 1001, 19:19–20) to the extent necessary to resolve Patent Owner’s contention that Petitioner fails to establish that Ma invalidates claim 1. See Resp. 53, 56–58.” slip op. at 9

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner

    “Whether Ma qualifies as a “printed publication” involves an inquiry into the facts and circumstances surrounding the reference’s disclosure to members of the public. In re Klopfenstein, 380 F.3d 1345, 1350 (Fed. Cir. 2004). A reference is considered “publicly accessible” upon a satisfactory showing that the document has been “disseminated or otherwise made available to the extent that persons interested and ordinarily skilled in the subject matter or art exercising reasonable diligence[] can locate it.” Kyocera Wireless Corp. v. ITC, 545 F.3d 1340, 1350 (Fed. Cir. 2008); see Hulu, LLC v. Sound View Innovations, LLC, IPR2018-01039, Paper 29, 10– 11 (PTAB Dec. 20, 2019) (precedential).” slip op. at 10

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

    “Based on the information presented, we find Petitioner has the better position. Patent Owner admits that joint vaporization means “two materials vaporize together.” Reply 21 (quoting Resp. 54). As Petitioner argues, “This is what Ma discloses.” Id. We agree with Petitioner that Ma describes a “two-component” electron transport layer having a “thickness with one value.” Id.; see Ex. 1007, 811 (reporting a “co-deposited” application of “BPhen:LiQ” that is “50 nm thick”). Ma’s disclosure, thereby, strongly “indicates that the two components were vaporized together––as opposed to creating a ‘macroscopically homogenous form’” prepared by sequentially vaporizing the individual components as Patent Owner “hypothesizes.” Reply 21 (citing Ex. 1020 ¶¶ 42–44; Ex. 2041 ¶¶ 155–157); see Resp. 54– 55; see also Ex. 1007, 811 (Ma’s description of its device fabrication, appearing in the third paragraph of the experiments section). Petitioner further advances evidence that “[p]reparing a layer that is ‘macroscopically homogeneous’ but potentially microscopically heterogeneous,” as Patent Owner postulates, “would introduce excessive variability and render the data noncomparable and unreliable, thus undermining the experiment’s purpose.” Reply 21 (citing Ex. 1020 ¶ 44); see Resp. 54–55. Patent Owner presents no counterargument or evidence that is persuasive to undercut Petitioner’s reasoning or evidence on that point. See Sur-reply 19–22. Petitioner also argues that an ordinarily skilled artisan would have recognized “that vaporizing materials together would best achieve Ma’s objective of assessing the current density using different Liq doping percentages.” Reply 22 (citing Ex. 1007, 811; Ex. 1020 ¶ 51). Here again, Petitioner’s evidence on point stands uncontested. See Sur-reply 19–22 (declining to contest that point). On this record, therefore, we agree with Petitioner that, as to the relevant disclosure in Ma, “the most natural interpretation of ‘co-deposition’ for forming a layer, particularly when there is nothing to indicate that the materials” are “vaporized sequentially,” is that the materials are co-deposited by joint vaporization. Reply 22 (citing Ex. 1020 ¶ 46–51). We further agree that, “[u]nder a preponderance standard, Ma’s disclosures are sufficient to render joint vaporization at least obvious.” Id. For the above reasons, we determine that Petitioner demonstrates by a preponderance of the evidence that Ma discloses joint vaporization as required by the challenged claims.” slip op. at 15

  Patent outcomesUS 8,558,223 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 8,558,223
• Cisco Systems, Inc. / Juniper Networks, Inc. v. Orckit CorporationSome claims unpatentable
  PTAB · Oct 22, 2024 · IPR2024-00034 · APJ Kristen L Droesch · IPR · Final written decision

  Claims 1–13 and 17–20 are unpatentable over the stated obviousness grounds; claims 14–16 are not shown unpatentable because the cited art does not teach logic configured to determine concurrent failure probability.

  RulingsFinal written decision

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner

    “We decline to adopt Patent Owner’s implicit construction that would require “selecting an entity pair from” all of the entity pairs of “said plurality of transport entities.” Contrary to Patent Owner’s arguments addressing the claim language, the plain language of claim 1 does not require the selection to be from all of the entity pairs of the plurality of transport entities for which an overall cost has been determined. The plain language of claim 1 also does not preclude the selection to be from a subset of the entity pairs of the plurality of transport entities for which an overall cost has been determined. Rather, dependent claim 9, through its dependence on claims 1 and 4, explicitly allows for the selection to be from a subset of the entity pairs of the plurality of transport entities. Patent Owner’s arguments advocate for the importation of limitations from the ’821 Patent Specification into the claim––namely the disclosure that all entity pairs of transport entities examined in step 220 of Figure 2 are input to the entity pair selection step 230. See PO Sur-reply 4. It is well settled that it is improper to read an extraneous limitation into a claim from the specification. See e.g., Commark Comm’s Inc. v. Harris Corp., 156 F.2d 1182, 1186 (Fed. Cir. 1998); E.I. du Pont de Nemours & Co. v. Phillips Petroleum Co., 849 F.2d 1430, 1433 (Fed. Cir. 1988). An extraneous limitation is “a limitation read into a claim from the specification wholly apart from any need to interpret what the patentee meant by particular words or phrases in the claim.” E.I. du Pont de Nemours, 849 F.2d at 1433. Accordingly, we construe “selecting an entity pair from said plurality of transport entities based at least upon said overall cost” according to its plain meaning, the scope of which includes selecting an entity pair from all or a subset of the entity pairs of the plurality of transport entities for which an overall cost has been determined.” slip op. at 11

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

    “As demonstrated in the analysis below, we need not construe “working entity” and “protection entity” in order 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))). Other Claim Terms and Phrases As demonstrated in our analysis below, we need not construe any other claim terms or phrases to resolve the controversy before us. See, e.g., Realtime, 912 F.3d 1368, 1375.” slip op. at 13

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner does not dispute Petitioner’s level of ordinary skill for purposes of this Patent Owner Response.” PO Resp. 25. We adopt Petitioner’s definition of a person of ordinary skill in the art because it is supported by declaration testimony and is consistent with the level of skill reflected by the ’821 Patent Specification and the asserted prior art. slip op. at 14

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

    “Based on the entire record and after having considered Petitioner’s citations to Doshi, Guichard, and Dr. Houh’s testimony (Ex. 1003) as well as Patent Owner’s citations to Doshi, Guichard and Mr. Gomez’s testimony, 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 Doshi with Guichard’s teachings of reoptimization of a LSP path triggered by an network change. See Pet. 20–22, 40–45; KSR, 550 U.S. at 418. Petitioner asserts that “[t]he results of the combination would have been predictable and there would have been a reasonable expectation of success since Doshi and Guichard both address the same technology.” Pet. 22 (citing Ex. 1003 ¶¶ 63–65). According to Petitioner, “a POSITA would have had a reasonable expectation of success in reoptimizing Doshi’s LSP pair selection because Guichard provides significant implementation details, including when to trigger reoptimization evaluations and how to ‘avoid network instabilities.’” Pet. 22–23 (citing Ex. 1003 ¶¶ 63–65; Ex. 1006, 5). Petitioner asserts that a reasonable expectation of success is evidenced by other skilled artisans that reoptimized similar systems. See Pet. 23 (citing Ex. 1003 ¶¶ 63–65; Ex. 1009, 136; Ex. 1010, 1; Ex. 1023, 34; Ex. 1034 ¶¶ 27–33, claim 19; Ex. 1035 ¶ 24). In support, Petitioner contends that “the combination would be within a POSITA’s skillset since Doshi already sets forth the calculation and selection techniques that would be utilized during the reoptimization evaluation.” Id. (citing Ex. 1003 ¶¶ 63–65). According to Petitioner, “since Doshi is already ‘monitoring and updating . . . network topology’ . . . event-based reoptimization evaluation per Guichard, would be directly applicable.” Id. (citing Ex. 1003 ¶¶ 63–65; Ex. 1005 ¶¶ 270–281).” slip op. at 38

  Patent outcomesUS 8,830,821 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,830,821
• Cisco Systems, Inc. / Juniper Networks, Inc. v. Orckit CorporationSome claims unpatentable
  PTAB · Oct 22, 2024 · IPR2023-00402 · APJ Kristen L Droesch · IPR · Final written decision

  Claims 1–13 and 17–20 are unpatentable over the Doshi and Guichard grounds; claims 14–16 were not shown unpatentable over Doshi, Guichard, and Xu.

  RulingsFinal written decision

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner

    “require “selecting an entity pair from” all of the entity pairs of “said plurality of transport entities.” Contrary to Patent Owner’s arguments addressing the claim language, the plain language of claim 1 does not require the selection to be from all of the entity pairs of the plurality of transport entities for which an overall cost has been determined. The plain language of claim 1 also does not preclude the selection to be from a subset of the entity pairs of the plurality of transport entities for which an overall cost has been determined. Rather, dependent claim 9, through its dependence on claims 1 and 4, explicitly allows for the selection to be from a subset of the entity pairs of the plurality of transport entities. Patent Owner’s arguments advocate for the importation of limitations from the ’821 Patent Specification into the claim––namely the disclosure that all entity pairs of transport entities examined in step 220 of Figure 2 are input to the entity pair selection step 230. See PO Sur-reply 4. It is well settled that it is improper to read an extraneous limitation into a claim from the specification. See e.g., Commark Comm’s Inc. v. Harris Corp., 156 F.2d 1182, 1186 (Fed. Cir. 1998); E.I. du Pont de Nemours & Co. v. Phillips Petroleum Co., 849 F.2d 1430, 1433 (Fed. Cir. 1988). An extraneous limitation is “a limitation read into a claim from the specification wholly apart from any need to interpret what the patentee meant by particular words or phrases in the claim.” E.I. du Pont de Nemours, 849 F.2d at 1433. Accordingly, we construe “selecting an entity pair from said plurality of transport entities based at least upon said overall cost” according to its plain meaning, the scope of which includes selecting an entity pair from all or a subset of the entity pairs of the plurality of transport entities for which an overall cost has been determined.” slip op. at 11

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

    “As demonstrated in the analysis below, we need not construe “working entity” and “protection entity” in order 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))). Other Claim Terms and Phrases As demonstrated in our analysis below, we need not construe any other claim terms or phrases to resolve the controversy before us. See, e.g., Realtime, 912 F.3d 1368, 1375.” slip op. at 13

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner does not dispute Petitioner’s level of ordinary skill for purposes of this Patent Owner Response.” PO Resp. 25. We adopt Petitioner’s definition of a person of ordinary skill in the art because it is supported by declaration testimony and is consistent with the level of skill reflected by the ’821 Patent Specification and the asserted prior art. slip op. at 14

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

    “Based on the entire record and after having considered Petitioner’s citations to Doshi, Guichard, and Dr. Houh’s testimony (Ex. 1003) as well as Patent Owner’s citations to Doshi, Guichard and Mr. Gomez’s testimony, 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 Doshi with Guichard’s teachings of reoptimization of a LSP path triggered by an network change. See Pet. 20–22, 40–45; KSR, 550 U.S. at 418. Petitioner asserts that “[t]he results of the combination would have been predictable and there would have been a reasonable expectation of success since Doshi and Guichard both address the same technology.” Pet. 22 (citing Ex. 1003 ¶¶ 63–65). According to Petitioner, “a POSITA would have had a reasonable expectation of success in reoptimizing Doshi’s LSP pair selection because Guichard provides significant implementation details, including when to trigger reoptimization evaluations and how to ‘avoid network instabilities.’” Pet. 22–23 (citing Ex. 1003 ¶¶ 63–65; Ex. 1006, 5). Petitioner asserts that a reasonable expectation of success is evidenced by other skilled artisans that reoptimized similar systems. See Pet. 23 (citing Ex. 1003 ¶¶ 63–65; Ex. 1009, 136; Ex. 1010, 1; Ex. 1023, 34; Ex. 1034 ¶¶ 27–33, claim 19; Ex. 1035 ¶ 24). In support, Petitioner contends that “the combination would be within a POSITA’s skillset since Doshi already sets forth the calculation and selection techniques that would be utilized during the reoptimization evaluation.” Id. (citing Ex. 1003 ¶¶ 63–65). According to Petitioner, “since Doshi is already ‘monitoring and updating . . . network topology’ . . . event-based reoptimization evaluation per Guichard, would be directly applicable.” Id. (citing Ex. 1003 ¶¶ 63–65; Ex. 1005 ¶¶ 270–281).” slip op. at 38

  Patent outcomesUS 8,830,821 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,830,821
• Cisco Systems, Inc. v. Orckit CorporationSome claims unpatentable
  PTAB · Oct 8, 2024 · IPR2023-00714 · APJ Brent M Dougal · IPR · Final written decision

  Claims 1–5, 7–16, 18–22, and 24–26 are unpatentable as obvious over Vink and Patrick, with or without AAPA; claims 6, 17, and 23 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “understanding of a person of ordinary skill in the art at the time of the invention. Id. at 13, 17. Petitioner asserts that a person of ordinary skill in the art (“POSA” or “POSITA”) would have had a bachelor’s degree in computer science, computer engineering, electrical engineering, or equivalent training, or approximately two years of experience working in the field of information technology and networking . . . . Lack of professional experience can be substituted by additional education, and vice versa. Pet. 12 (citing Ex. 1003 ¶¶ 59–60). “Patent Owner does not dispute Petitioner’s proposed level of ordinary skill.” PO Resp. 19. We are persuaded that Petitioner’s proposal is consistent with the problems and solutions addressed in the ’904 patent and prior art of record. We adopt Petitioner’s definition of the level of skill for the purposes of this Decision.” slip op. at 6

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

    “Patent Owner argues “that ‘subscriber lines’ should be construed as ‘communication lines to users of subscription-based network services.’” Id. Petitioner does not dispute this construction directly, but rather argues that no construction is necessary. Reply 6. We determine that no terms need to be construed. 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 7

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

    “Here however, we have found that it was known to connect LANs to external networks. See Ex. 1014, 6:23–28, Fig. 1; Ex. 1015, 1:6–9; Ex. 1016, 1:22–25; Ex. 1017, 1:7–11. We further agree with Petitioner’s uncontested point that “[t]echniques to further allow the communication system to access external networks by connecting the master to an external network were well-known in the art, as evidenced by Patrick and/or AAPA.” Pet. 24 (citing Ex. 1003 ¶¶ 74–88). The Petition focusses on combining the “communication systems” of Vink, Patrick and/or AAPA, as opposed to relying on a particular type of LAN. Thus, in contrast to Forest Lab’ys, we determine that the general or “generic” benefit of providing “access to a wider array of information,” where it was already known to provide external network access (e.g., the internet) to LANs,5 does provide a motivation to combine Vink and Patrick, with or without AAPA. See Intel Corp. v. Pact XPP Schweiz AG, 61 F.4th 1373, 1380–81 (Fed. Cir. 2023) (“There is a motivation to combine when a known technique ‘has been used to improve one device, and a person of ordinary skill in the art would recognize that it would improve similar devices in the same way.’” (quoting KSR, 550 U.S. at 417)).” slip op. at 20

  • Obviousness (§103) › Motivation to combine / reasonable expectation of success › Teaching awayTeaching away not foundDecided for petitioner

    “Patent Owner also argues that Vink “teaches against” hierarchical addressing because “doing so would eliminate the purported advantages associated with using a non-hierarchical system.” PO Resp. 36 (citing Ex. 2005 ¶ 69 (Patent Owner’s declarant making the same statement)). Patent Owner does not further discuss the reasoning behind this statement, identify the “purported advantages,” or even identify the relevant disclosure relied on in Vink. We decline to speculate as to Patent Owner’s position in this regard. We further note that “a given course of action often has simultaneous advantages and disadvantages, and this does not necessarily obviate motivation to combine.” Medichem, S.A. v. Rolabo S.L., 437 F.3d 1157, 1165 (Fed. Cir. 2006).” slip op. at 19

  Patent outcomesUS 6,680,904 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,680,904
• Cisco Systems, Inc. / Dell Technologies Inc. et al. v. Corrigent CorporationSome claims unpatentable
  PTAB · Jul 3, 2024 · IPR2023-00169 · APJ Christopher L Ogden · IPR · Final written decision

  Claims 1–10, 12–22, and 24–30 are unpatentable as obvious under § 103(a); claims 11 and 23 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for patent owner

    “Relying on Dr. Houh’s testimony, Petitioner argues that a person of ordinary skill in the art “would have had a working knowledge of the networking art that is pertinent to the ’431 patent, including network communications techniques and bandwidth management methodologies,” and “would have had a bachelor’s degree in computer science, computer engineering, electrical engineering, or an equivalent, and two years of professional experience relating to network communications including the use of logical topologies and bandwidth management. Lack of professional experience can be remedied by additional education, and vice versa.” Pet. 11 (citing Ex. 1003 ¶¶ 18–20). Patent Owner adopts Petitioner’s proposed definition of the level of ordinary skill. PO Resp. 3. Because Petitioner’s articulation of that level of skill is uncontested, supported by testimonial evidence, and appears consistent with the types of problems and solutions in the ’431 patent, we adopt it for this decision. See, e.g., Ex. 1001, 1:5–6:14.” slip op. at 8

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

    “We see no significant difference between Petitioner’s proposed construction of in response to as “using” and Patent Owner’s proposed construction as “using information from.” Thus, it does not appear that the construction of in response to is genuinely in controversy. Thus, we need not construe the term for this decision. 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.’” (alteration in original) (quoting Vivid Techs., Inc. v. Am. Sci & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))). To the extent that we need to interpret any other claim language, we address that language below in the context of the prior art.” slip op. at 11

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

    “Considering the evidence of record on both sides, we find Petitioner’s argument persuasive that Baker teaches a “mapping” as recited in limitation 1.4. Baker’s disclosure of a “mapping” is explicit. See, e.g., Ex. 1005 ¶ 69, 83. And the evidence shows that this mapping occurs “in advance of a communication,” and may, for example, take place in the head node as part of the Administer Ring routine. See, e.g., Ex. 1005 ¶¶ 51–56, 76. That intermediate rings are ultimately configured to simply forward traffic “according to preconfigured rules” (Ex. 1005 ¶ 87) rather than to perform more complicated routing has no pertinent bearing on the process corresponding to the recited “mapping” step, which occurs “in advance” of the communication and any such forwarding (id. ¶ 76).” slip op. at 26

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

    “allocating bandwidth as part of its resources and that, in light of Wright, a person of ordinary skill in the art would have had reason to make this allocation for each of the links in of the physical topology (see Ex. 1006 ¶ 18 (“bandwidth allocation at each link”)) using information from both (1) the bandwidth requirements of Baker’s logical connections and (2) the mapping between Baker’s logical and physical topologies. As Petitioner persuasively argues, we find that Wright’s teaching of further details on ensuring the availability of bandwidth, in a similar context, would have been sufficient motivation for a person of ordinary skill in the art to incorporate Wright’s teachings into Baker’s method. We also determine that whether Wright, itself, teaches a mapping step is not the determining factor because Petitioner relies on Baker, not Wright, for teaching mapping limitation 1.4. Nevertheless, Wright does teach allocating bandwidth using the same information that would be available as a result of Baker’s mapping, including the logical (“restricted”) topology and the physical links associated with that topology. In particular, we agree with Petitioner that a person of ordinary skill in the art would have understood that allocating bandwidth to the physical links (step 510 of Figure 5) requires knowing which physical links correspond to Wright’s restricted topology. See Pet. 36; Pet. Reply 22–23; Ex. 1007 ¶ 17; Ex. 1003 ¶¶ 94–96; Ex. 1036 ¶¶ 49–51. We also disagree with Patent Owner that Petitioner has failed to adequately explain how a person of ordinary skill in the art would have modified Baker’s method to apply Wright’s teachings on bandwidth allocation, such as how Baker’s head node N0 would have been modified. See PO Resp. 31–32. Based on the level of ordinary skill and the level of detail in Baker, Wright, and the ’431 patent, and crediting Dr. Houh’s testimony, we find Petitioner’s argument persuasive that such modification would have been within the capability of someone of ordinary skill in the art. See Pet. 17–20 (citing Ex. 1003 ¶¶ 42–46, 48). And we agree with Petitioner that modifying Baker with Wright’s teachings would have been “nothing more than the combination of known elements . . . according to known methods . . . to yield predictable results.” Pet. 20 (citing Ex. 1003 ¶ 47).” slip op. at 32

  Patent outcomesUS 7,330,431 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,330,431
• Arista Networks, Inc. v. Corrigent CorporationSome claims unpatentable
  PTAB · Jul 3, 2024 · IPR2023-00515 · APJ Christopher L Ogden · IPR · Final written decision

  Claims 1–10, 12–22, and 24–30 are unpatentable as obvious under § 103; claims 11 and 23 were not shown unpatentable.

  RulingsFinal written decision

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “For reasons explained in the Petition and Petitioner’s Reply, we agree with Petitioner that the Baker–Wright–Holender ’699 combination teaches summing the two bandwidths determined in “allocating” steps 12.5 and 12.7 to determine a total allocation for each of the physical links—motivated by the known need to ensure that bandwidths do not exceed the available physical link capacity. We disagree with Patent Owner that Holender ’699’s discussion of summing is merely describing a physical constraint. Holender ’699 teaches normalizing the logical link capacities, which requires summing the logical link capacities. See Ex. 1007, 8:38–51. We credit Dr. Houh’s testimony that this “confirms that [Holender ’699’s] teachings about summing are not simply ‘explaining a physical constraint,’ but actually performed.” Ex. 1036 ¶ 61. Holender ’699 refers to capacities 𝐶𝐶𝑗𝑗 as “logical link capacities for each logical link j over all logical networks. Ex. 1007, 6:52–55. But when mapped to physical links, Holender ’699 denotes capacities 𝐶𝐶𝑘𝑘𝑘𝑘 as “capacities of the logical links [𝑙𝑙] that need capacity on the k:th physical link.” Ex. 1007, 8:38–43. In other words, they are the capacities, or bandwidths, allocated to each physical link 𝑘𝑘 for implementing associated logical link 𝑙𝑙. See also id. at 6:60–67 (describing a matrix designed to indicate “if logical link j needs capacity on the k:th physical link.”).” slip op. at 50

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Relying on Dr. Houh’s testimony, Petitioner argues that a person of ordinary skill in the art “would have had a working knowledge of the networking art that is pertinent to the ’431 patent, including network communications techniques and bandwidth management methodologies,” and “would have had a bachelor’s degree in computer science, computer engineering, electrical engineering, or an equivalent, and two years of professional experience relating to network communications including the use of logical topologies and bandwidth management. Lack of professional experience can be remedied by additional education, and vice versa.” Pet. 3 (citing Ex. 1003 ¶¶ 18–20). Patent Owner adopts Petitioner’s proposed definition of the level of ordinary skill. PO Resp. 3. Because Petitioner’s articulation of that level of skill is uncontested, supported by testimonial evidence, and appears consistent with the types of problems and solutions in the ’431 patent, we adopt it for this decision. See, e.g., Ex. 1001, 1:5–6:14.” slip op. at 8

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

    “necessary because the construction does not resolve any contested issues. Pet. Reply 8–10 (citing Ex. 1005 ¶¶ 16, 62; Ex. 1006 ¶¶ 5, 24; Ex. 1003 ¶ 96; Ex. 1036 ¶¶ 49–50). But if a construction is necessary, Petitioner argues that the we should construe in response to as “using,” consistent with how the claimed invention is described in the ’431 patent. Id. at 10–11 (citing Ex. 1001, 2:52–6:10, 8:52–9:2; Ex. 1036 ¶¶ 7–11). Petitioner disagrees that the term means “based on” because limitation 1.3 uses the phrase based on, suggesting that the applicant made a conscious decision to use different language in limitation 1.5. Id. at 11 (citing Ex. 1036 ¶ 11). Patent Owner responds that its two proposed constructions are synonymous, and argues that Petitioner agrees that in response to encompasses “using” or “using information from.” PO Sur-reply 8 (citing Ex. 1001, 2:22–26). Patent Owner contends that its proposed construction resolves a controversy because in Patent Owner’s view, the Baker–Wright combination does not use information from the recited mapping to allocate bandwidth. Id. at 9–12 (citing Ex. 1006 ¶¶ 5, 17, 24; Ex. 2009, 52–56; Ex. 2008 ¶¶ 62–76). Similarly, Patent Owner contends that Holender ’699 does not teach mapping. Id. at 12–13 (citing Ex. 1007, 3:15–17; Ex. 2008 ¶¶ 89–92). We see no significant difference between Petitioner’s proposed construction of in response to as “using” and Patent Owner’s proposed construction as “using information from.” Thus, it does not appear that the construction of in response to is in controversy. Thus, we need not construe the term for this decision. 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.’” (alteration in original) (quoting Vivid Techs., Inc. v. Am. Sci & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999))). To the extent that we need to interpret any other claim language, we address that language below in the context of the prior art.” slip op. at 10

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

    “We find Petitioner’s arguments persuasive that Baker teaches allocating bandwidth as part of its resources and that, in light of Wright and Holender ’699, a person of ordinary skill in the art would have had reason to make this allocation for each of the links in of the physical topology (see Ex. 1006 ¶ 18 (“bandwidth allocation at each link”)) using information from both (1) the bandwidth requirements of Baker’s logical connections and (2) the mapping between Baker’s logical and physical topologies. As Petitioner persuasively argues, we find that Wright’s teaching of further details on ensuring the availability of bandwidth, in a similar context, would have been sufficient motivation for a person of ordinary skill in the art to incorporate Wright’s teachings into Baker’s method. Holender ’669 provides further supporting disclosure. We also determine that whether Wright, itself, teaches a mapping step is not the determining factor because Petitioner relies on Baker, not Wright, for teaching mapping limitation 1.4. Nevertheless, Wright does teach allocating bandwidth using the same information that would be available as a result of Baker’s mapping, including the logical (“restricted”) topology and the physical links associated with that topology. In particular, we agree with Petitioner that a person of ordinary skill in the art would have understood that allocating bandwidth to the physical links (step 510 of Figure 5) requires knowing which physical links correspond to Wright’s restricted topology. See Pet. 33; Pet. Reply 22–23; Ex. 1007 ¶ 17; Ex. 1003 ¶¶ 94–96; Ex. 1036 ¶¶ 49–51. We also disagree with Patent Owner that Petitioner has failed to adequately explain how a person of ordinary skill in the art would have modified Baker’s method to apply Wright’s teachings on bandwidth allocation, such as how Baker’s head node N0 would have been modified. See PO Resp. 31–32. Based on the level of ordinary skill and the level of detail in Baker, Wright, and the ’431 patent, and crediting Dr. Houh’s testimony, we find Petitioner’s argument persuasive that such modification would have been within the capability of someone of ordinary skill in the art. See Pet. 9–12 (citing Ex. 1003 ¶¶ 42–46, 48; Ex. 1021 ¶¶ 100–101). And we agree with Petitioner that modifying Baker with Wright’s teachings would have been “nothing more than the combination of known elements . . . according to known methods . . . to yield predictable results.” Pet. 11–12 (citing Ex. 1003 ¶ 47; Ex. 1021 ¶¶ 102–104).” slip op. at 34

  Patent outcomesUS 7,330,431 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,330,431
• Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. et al. v. Smart Mobile Technologies LLCSome claims unpatentable
  PTAB · Jan 23, 2024 · IPR2022-01248 · APJ Aaron W Moore · IPR · Final written decision

  Claims 14–21 and 23–26 are unpatentable under §103; claims 1–13 and 27–30 were not shown unpatentable because the asserted combinations failed to establish multiplexing.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “education.” Id. (citing Ex. 1003 ¶¶ 27–28). Patent Owner does not propose a level of ordinary skill and does not dispute Petitioner’s proposal. As Patent Owner does not dispute Petitioner’s characterization of the level of skill in the art, and because we find it generally consistent with the disclosures of the ’653 patent and the cited prior art, we adopt it. C.” slip op. at 10

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

    “Claim Construction Petitioner states that “no formal claim constructions are necessary in this proceeding.” Pet. 2. Patent Owner does seek an express construction of any claim term, and we thus conclude that we need not expressly construe any terms to resolve the issues 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)). D.” slip op. at 10

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

    “d. Multiplexing Being “Well-Known” Petitioner additionally argues that multiplexing techniques were well- known. See Pet. 34; Pet. Reply 18. Even if that is correct, however, it is insufficient because Petitioner must show that it would have been obvious to modify Yegoshin to add multiplexing, and merely establishing that multiplexing was known in other contexts is insufficient to show how or why Yegoshin should be modified.” slip op. at 22

  • PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted

    “Patent Owner filed an opposition to the motion. See Paper 24. Patent Owner contends that the declaration is untimely and unfairly prejudicial because it circumvents our word count limitations and amounts to an additional brief because it analyzes claim construction and includes new cites to the record. See id. at 2–10. Having reviewed the parties’ positions, we grant the Motion. We note, however, that in view of the full record, and for the reasons below, our determination would not change even if we denied the motion. B.” slip op. at 9

  Patent outcomesUS 8,842,653 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 8,842,653
• Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. et al. v. Smart Mobile Technologies LLCSome claims unpatentable
  PTAB · Jan 23, 2024 · IPR2022-01249 · APJ Hyun J Jung · IPR · Final written decision

  Claims 14–15, 17–21, and 27–30 are unpatentable as obvious; claims 1–13, 16, and 26 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelOther

    “C. Level of Ordinary Skill in the Art” slip op. at 9

  • PTAB / AIA Trials › Other PTAB motions (exclude, strike, seal, additional discovery, rehearing)Granted

    “A. Petitioner’s Motion to Submit Supplemental Information” slip op. at 7

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successUnpatentableNot shown unpatentableMixed

    “agree that “Yegoshin’s phone is configured to switch between cellular and IP communication modes, and also ‘capable of taking some calls via cellular path while receiving other calls via IP path’” but that does not lead to the conclusion, or support, that “in order to receive calls on both cellular network and WLAN simultaneously or to switch between two networks, the phone includes multiplexing of the signals communicated on two network paths.” Ex. 1003 ¶¶ 126 (citing Ex. 1004, 3:18–22, 5:33–65), 127 (citing Ex. 1004, 5:33–65; Ex. 1006, 1:6:12, 1:54–60, 3:53–61). The declarant’s citations to the record also do not support that Yegoshin’s “phone includes multiplexing of the signals communicated on two network paths.” Ex. 1004, 3:18–22, 5:33–65; Ex. 1006, 1:6:12, 1:54–60, 3:53–61.” slip op. at 45

  Patent outcomesUS 9,019,946 mixed
  § 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,019,946

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.