• Yealink (USA) Network Technology Co., Ltd. / Yealink Network Technology Co., Ltd. v. Barco NVNo claims unpatentable
  PTAB · Oct 5, 2026 · IPR2025-00598 · APJ David C Mckone · IPR · Final written decision

  Claims 1–31 were not shown unpatentable under either § 103 ground because the asserted combinations did not teach required claim limitations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedOther

    “admissions by Patent Owner in litigation, contends that a person of ordinary skill in the art would have had “a Master of Science (M.S.) degree in electrical engineering or computer science, and five years of work experience in a related field” and that “[a]dditional educational experience could substitute for some of the work experience.” Pet. 5 (citing Ex. 1002 ¶¶ 36–37). “Patent Owner does not dispute Petitioner’s proposed level of skill in the art (Petition, 5) at this time.” PO Resp. 6. On the complete record, we adopt Petitioner’s description of the level of ordinary skill in the art, as it is uncontested and is consistent with the technology described in the ’347 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8

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

    “In the Preliminary Response, “Patent Owner accept[ed] the Petition’s claim construction.” Prelim. Resp. 6. However, in the Patent Owner Response, Patent Owner argues that “the claims of the ’347 Patent require no construction as they are valid under their plain and ordinary meaning.” PO Resp. 6. Based on the complete record, we do not find it necessary to provide express claim constructions of any claim terms. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 9

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “Beel actually discloses the following: [0321] On the peripheral device 32 the video packets are received at the corresponding plug and play port, e.g. the USB port 11, read by the Human Interface Driver (HID) interface handler 13, unpacked to remove HID protocol headers in an unpacker 20 and then transmitted to the communications network by a transmitter 21. The network can be wireless for example WiFi or LiFi network. [0322] Having been routed over a communications network to the base unit 33, the incoming stream is read from the communications interface such as a WiFi access point 22, unpacked in an unpacker 25, decoded in a decoder 26 and then inserted into a suitable composition such as an OpenGL based composition in the compositor 29 for display on a central display device. Ex. 1005 ¶¶ 321–322 (emphasis added to portions quoted by Petitioner). Patent Owner notes that “[t]he Petition mistakenly cites to ¶ 322 of Beel but quotes ¶ 321.” PO Resp. 20 n.3. However, it appears that Petitioner has grafted together a portion of paragraph 321 that introduces peripheral device 32 with a portion of paragraph 322, which discusses features of base unit 33. However, this grafting has been done in such a way as to convey (incorrectly) that peripheral device 32, not base unit 33, includes unpacker 25, decoder 26, and compositor 29 that process the first processed video data received by the first peripheral device to generate second video data. Dr. Almeroth’s testimony, which copies Petitioner’s incorrectly altered quotation to paragraph 322 of Beel, is unreliable as to this claim limitation and is entitled to no weight.4 Thus, Petitioner has no expert testimony on which to rely for this claim limitation.” slip op. at 19

  • Strike new argumentNew argument disregardedDecided for patent owner

    “5 At the oral argument, when challenged on its reliance on paragraph 322, Petitioner argued that paragraph 321 of Beel teaches this limitation. Tr. 22:26–23:24. Petitioner did not make this argument in the Petition and, instead, raised it for the first time during oral argument; thus, it will not be considered. See Dell Inc. v. Acceleron, LLC, 884 F.3d 1364, 1369 (Fed. Cir. 2018) (“Unless it chose to exercise its waiver authority under 37 C.F.R. § 42.5(b), the Board was obligated to dismiss Dell’s untimely argument given that the untimely argument in this case was raised for the first time during oral argument.”). Even if we were to consider this new argument, it would not be persuasive. As Patent Owner observes (PO Resp. 20), any processing performed by peripheral device 32 in paragraph 321 is on data received from the processing device and destined for the base station via the network, rather than data flowing in the direction of the first processed video data of claim 1.” slip op. at 22

  Patent outcomesUS 11,966,347 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 11,966,347
• Apple Inc. v. Proxense, LLCAll claims unpatentable
  PTAB · Sep 17, 2026 · IPR2025-00562 · APJ Thu A Dang · IPR · Final written decision

  Claims 1–20 are unpatentable as obvious over Giobbi ’157, Giobbi ’139, and Dua; the Board also finds the claims unpatentable under the Broadcom grounds.

  RulingsFinal written decision

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) does not applyDecided for petitioner

    “IPR2024-00783, Ex. 1001, 22:36–49. As the Federal Circuit stated, when a disputed claim limitation does not employ “means for” language, the presumption is that each of the terms conveys sufficiently definite structure or act and, thus, is not subject to § 112 ¶ 6. See Dyfan, 28 F.4th at 1367. Based on the record before us, this presumption that each of the terms is not subject to § 112 ¶ 6 is not overcome.” slip op. at 17

  • Skill levelOther

    “differences between the claimed subject matter and the prior art are such that the subject matter, as a whole, “would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). The question of obviousness is resolved on the basis of underlying factual determinations including: (1) the scope and content of the prior art; (2) any differences between the claimed subject matter and the prior art; (3) the level of ordinary skill in the art; and (4) objective evidence of non-obviousness. See Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 17–18 (1966).” slip op. at 25

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “We find persuasive Dr. Wolfe’s supporting testimony that a POSITA would have understood the terms “PDK” and “RDC” to have “definite structure.” Ex. 1013 ¶¶ 35–56. In particular, we find persuasive Dr. Wolfe’s testimony that the term “PDK,” for example, “encompasses at least ‘a collection of circuit components that includes an antenna, a transceiver, and a controller and memory for storing information particular to a user.’” Id. ¶ 35. Dr. Wolfe’s testimony is consistent with the Specification of the ’188 patent. See Ex. 1001, 5:42–6:7, 3:48–62. In particular, the Specification of the ’188 patent describes a microchip that stores information in memory and responds through an antenna when probed, which is consistent with Dr. Wolfe’s testimony. Id.; Ex. 1001, 1:30–62.” slip op. at 19

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

    “differences between the claimed subject matter and the prior art are such that the subject matter, as a whole, “would have been obvious at the time the invention was made to a person having ordinary skill in the art to which said subject matter pertains.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). The question of obviousness is resolved on the basis of underlying factual determinations including: (1) the scope and content of the prior art; (2) any differences between the claimed subject matter and the prior art; (3) the level of ordinary skill in the art; and (4) objective evidence of non-obviousness. See Graham v. John Deere Co. of Kansas City, 383 U.S. 1, 17–18 (1966).” slip op. at 25

  Patent outcomesUS 9,049,188 unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 9,049,188
• Amazon.Com, Inc. / Amazon.Com Services LLC et al. v. Soundclear Technologies LLCAll claims unpatentable
  PTAB · Sep 3, 2026 · IPR2025-00673 · APJ Michael R Zecher · IPR · Final written decision

  Claims 1–7 are unpatentable as obvious over the combined teachings of the asserted references, including Shin and Aoyama and Shimomura and Iwase.

  RulingsFinal written decision

  • PTAB / AIA Trials › Motions to amend / substitute claimsOther

    “1 SoundClear also filed a Contingent Motion to Amend that proposed to replace originally challenged claim 5 of the ’675 patent with proposed substitute claim 8. Paper 21. We, however, granted SoundClear’s request to withdraw its Contingent Motion to Amend and, as a result, the Contingent Motion to Amend will no longer be considered in this proceeding. Paper 30.” slip op. at 2

  • Skill levelOther

    “2. Level of Skill in the Art In determining whether an invention would have been obvious, we” slip op. at 21

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundMotivation not foundMixed

    “combination because (1) configuring Shin’s processor 120 accordingly “would have been trivial, involving straightforward changes to enhance the processor’s approach to simplifying and abbreviating its output”; and (2) this approach was well-known as evidenced by Ha’s disclosure of replacing “team meeting” and “date” with “schedules” based on the user’s environment.6 Id. at 27–28 (first quoting Ex. 1011 ¶ 97, then quoting Ex. 1011 ¶ 98) (citing Ex. 1002 ¶ 102; Ex. 1011, Fig. 7).” slip op. at 33

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “4. Dr. Stern’s Testimony is Reliable In its Patent Owner Response, SoundClear contends that “Dr. Stern’s” slip op. at 125

  Patent outcomesUS 11,244,675 unpatentable
  § 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,244,675
• Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentable
  PTAB · Sep 1, 2026 · IPR2025-00914 · APJ Brian P Murphy · IPR · Final written decision

  Claims 1–19 are unpatentable as obvious over Menon, Trefethen, RS6000, and POEref.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “In determining the level of ordinary skill in the art, various factors may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC, Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citing Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “These factors are not exhaustive but are merely a guide to determining the level of ordinary skill in the art.” Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). There is uncontested evidence in the record before us that reflects the knowledge and We adopt the Petition’s formulation of the level of ordinary skill in the art, which is consistent with the ’679 patent, the prior art of record, and the testimony of both experts.” slip op. at 10

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

    “The Petition relies on the ordinary and customary meaning of the claim terms consistent with the Phillips standard. Pet. 12–13 (citing 37 C.F.R. § 42.100(b)). The Petition also addresses the construction of “peer-to-peer architecture” recited in independent claim 1 of the ’679 patent, a limitation we need not construe to resolve the parties’ dispute in this proceeding. Id. at 13; see, e.g., Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011) (“[C]laim terms need only be construed ‘to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Owner relies on the ordinary and customary meaning of the claim terms consistent with the Phillips standard without further analysis. Resp. 7.” slip op. at 11

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

    “RS6000 with Menon, namely because RS6000 provides an overview of the IBM SP2 multiprocessor and Menon teaches the use of “IBM SP2, a modern high performance distributed memory multiprocessor” used in the MultiMATLAB system. Id. at 24–25 (citing Ex. 1003 ¶¶ 142–145; Ex. 1005, 5–6, 14; Ex. 1007, 1, 11). The Petition also explains why POEref pertains to the field of cluster computing in a parallel operating environment. Id. at 26 (citing Ex.1008, 11 (“PE Software is designed to run on an … RS/6000 network cluster”)); (further citing Ex. 1001, 1:14–15; Ex. 1003 ¶¶ 146–149). The Petition contends that a POSITA would have been motivated to combine the teachings of POEref with Menon “because Menon suggests the combination by teaching that MultiMATLAB uses ‘POE, IBM's Parallel Operating Environment.’” Id. at 26–27 (citing Ex. 1005, 6); (further citing Ex. 1003 ¶¶ 150–153; Ex. 1005, 14; Ex. 1008, 11, 46). We agree with Petitioner’s analysis. We find the Petition’s argument and evidence of a motivation to combine the asserted prior art references in the manner claimed to be compelling, persuasive, consistent with the disclosures in the references, which include internal cross-references to each other, and supported by the expert testimony of Dr. Bajaj.” slip op. at 19

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

    “skill, upon reading the reference, would be discouraged from following the path set out in the reference, or would be led in a direction divergent from the path that was taken by the applicant.” In re Gurley, 27 F.3d 551, 553 (Fed. Cir. 1994). Patent Owner argues that Menon teaches away from a combination with Trefethen because “Menon expressly states that Trefethen’s first-generation architecture is inadequate for the objectives that motivated the newer design.” Resp. 35–37. The evidence does not support Patent Owner’s position. First, Patent Owner’s teaching away argument is inconsistent with the strong evidence of a motivation to combine Menon and Trefethen discussed above. Second, Patent Owner’s teaching away argument is contrary to the evidence of record for the reasons given in Petitioner’s Reply. Reply 13–15 (e.g., “Menon explicitly cites Trefethen and explains that Menon builds on the teachings of Trefethen.”) (citing Pet. 22; Ex. 1003 ¶ 70; Ex. 1005, 1–3; Ex. 1163 ¶¶ 47–53). We are further persuaded by Dr. Bajaj’s reply testimony: the “MultiMATLAB teachings in Trefethen. In fact, Menon describes enhancing the system of Trefethen. For example, Menon describes a list of “goals” already achieved by MultiMATLAB and then states that the architecture has been “redesigned to achieve two further goals.” One of these two “further goals” is “extensibility,” which Menon achieves by its description of adding “MEX routines” to the system of Trefethen. Far from showing an “incompatibility” between Menon and Trefethen as the POR argues, Menon’s addition of the “MEX routines” to MultiMATLAB shows that such a modification was within the capabilities of a POSITA, because the authors of the Menon paper actually implemented the modification. Ex. 1163 ¶ 49 (citing Ex. 1005, 1–3). Dr. Bajaj’s testimony is unrebutted, credible, and supported by the record. We agree with Dr. Bajaj’s reasoning, which is based on direct quotes in Menon. We further agree with Dr. Bajaj’s conclusion that Menon does not teach away from the combination with Trefethen. Id. ¶¶ 50–52. Menon’s description of building on and enhancing the teachings of Trefethen—the earlier work of the same research group at Cornell—by adding MEX routines to achieve high-performance parallel computing and extensibility for MATLAB, demonstrates a classic motivation for a POSITA to combine the teachings of Menon and Trefethen. RS6000 and POEref are specifically referenced in Menon-Trefethen and add operational details of the parallel operating platform that teach a POSITA how to implement the MultiMATLAB system with a reasonable expectation of success. Such facts are inconsistent with Patent Owner’s teaching away and lack of motivation arguments.” slip op. at 24

  Patent outcomesUS 12,021,679 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 12,021,679
• Intel Corporation v. Advanced Cluster Systems, Inc.All claims unpatentable
  PTAB · Aug 26, 2026 · IPR2025-00913 · APJ Brian P Murphy · IPR · Final written decision

  Claims 1–30 are unpatentable: claims 1–25, 27–28, and 30 as obvious over Menon, Trefethen, RS6000, and POEref; claims 26 and 29 over those references plus MPIref.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “may be considered, including the “type of problems encountered in the art; prior art solutions to those problems; rapidity with which innovations are made; sophistication of the technology; and educational level of active workers in the field.” In re GPAC, Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995) (citing Custom Accessories, Inc. v. Jeffrey-Allan Indus., Inc., 807 F.2d 955, 962 (Fed. Cir. 1986)). “These factors are not exhaustive but are merely a guide to determining the level of ordinary skill in the art.” Daiichi Sankyo Co. v. Apotex, Inc., 501 F.3d 1254, 1256 (Fed. Cir. 2007). There is uncontested evidence in the record before us that reflects the knowledge and experience of a POSITA. We adopt the Petition’s formulation of the level of ordinary skill in the art, which is consistent with the ’034 patent, the prior art of record, and the testimony of both experts.” slip op. at 11

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed petitioner constructionOther

    “processor,” “multi-core” processor, or “singular ‘hardware processor’ that ‘comprises’ (or ‘with’) multiple ‘processing cores’” as Patent Owner contends. Resp. 11–12, 21; see also Ex. 1163 ¶ 22 (“The claim does not recite ‘single chip,’ ‘single package,’ ‘single die,’ or ‘single multi-core microprocessor.’”). Nor do the claims recite a plurality of processing cores “within” a single-chip package or read as “multi-core within a processor” as argued by Patent Owner. Resp. 12–14; Sur-Reply 2; see Reply 6 (citing Ex. 1163 ¶ 23 (“Thus, the phrase ‘with a plurality of processing cores’ identifies the required processing resources associated with the hardware processor; it does not import a packaging limitation.”)). The claims do recite a hardware processor “with” a plurality of processing cores; a critical distinction even Patent Owner reads as open-ended, i.e., as a hardware processor that “comprises” a plurality of processing cores. See Resp. 11 (“the claims require a singular ‘hardware processor’ that ‘comprises’ (or ‘with’) multiple ‘processing cores’”). Consequently, the claim language does not support Patent Owner’s proposed construction of “a . . . hardware processor with a plurality of processing cores” as a single multi-core processor. cores it contains” in reliance on a parsed description in the ’034 patent specification: The specification explains: “Each processor can contain one or more processor cores that are capable of single-threaded execution. Processor cores are generally independent microprocessors, but more than one can be included in a single-chip package.” Id. at 1212 (partially quoting Ex. 1001, 5:11–16); Sur-Reply 2. The quoted description does not support Patent Owner’s contention that the claimed “a . . . hardware processor with a plurality of processing cores” must be limited to a “single multi-core processor” that “locates multiple cores within a ‘single-chip package,’” i.e. limited to a single multi-core microprocessor such as “a Core 2 Duo is one processor package with two cores.” Resp. 12– 13, 21 (citing Ex. 1001, 7:15–25). The description quoted above from column 5, moreover, describes a “processor” that “can contain one or more processor cores” each of which can be an independent microprocessor. Reply 2–3 (citing Ex. 1001, 5:11–16; Ex. 1163 ¶¶ 10–14). As Petitioner emphasizes, the specification distinguishes a “processor” from a “microprocessor” and describes a “processor” that “can be one or more general purpose single-core or multi-core microprocessors,” rather than limiting a “processor” to a single multi-core microprocessor. Reply 3–5 (citing Ex. 1001, 7:14–36, Fig. 1; Ex. 1163 ¶¶ 15–18).” slip op. at 13

  • Obviousness (§103) › Analogous artAnalogous artDecided for petitioner

    “art because they pertain to the same “field of cluster computing” as the ’034 patent and “are reasonably pertinent to the problem of the ’034 patent, namely, executing a single program on multiple nodes.” Pet. 22 (citing Ex. 1001, 1:14–15; Ex. 1003, ¶¶ 65–69; Ex. 1005, 2; Ex. 1006, Abstract). The Petition emphasizes that Menon expressly cites and builds on the MultiMATLAB system taught by Trefethen. Id. (citing Ex. 1003 ¶ 71; Ex. 1005, 1–2). The Petition contends that: combination of prior art elements according to known methods (executing MATLAB code on a multiprocessor system) to yield the predictable result discussed in both papers: the MultiMATLAB system executing MATLAB in parallel to perform mathematical calculations. Id. at 22–23 (citing Ex. 1003 ¶ 70; Ex. 1005, Abstract; Ex. 1006, 2–7). The Petition further contends that a POSITA would have found it predictable to combine Trefethen with Menon with a reasonable expectation of success “because researchers had a strong desire to parallelize MATLAB.” Id. at 23–24 (citing Ex. 1003 ¶ 73; Ex. 1005, 2; Ex. 1006, 11–12.)” slip op. at 27

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

    “A POSITA would have had an especially strong reason to read these references together because they address the same project, the same MATLAB-based parallel-computing problem, and the same MultiMATLAB command environment. Menon expressly identifies Trefethen’s MultiMATLAB work and then describes a redesigned architecture that preserves the same user-level objective––parallel MATLAB computations—while improving implementation details and extensibility. A POSITA therefore would not view the references as mutually exclusive alternatives. Rather, a POSITA would understand Trefethen as teaching specific MultiMATLAB commands and examples, including Eval, Send, Recv, and the architecture was implemented and improved in a later version. Ex. 1163 ¶¶ 71–72 (emphases added). We find the above reasoning persuasive and adopt it as our own. Petitioner and Dr. Bajaj demonstrate a sound technical motivation for a POSITA—someone having a bachelor’s degree in computer science, computer engineering, or electrical engineering and two years of experience working in the field of cluster computing or parallel processing—to combine Menon and Trefethen: to improve MATLAB’s operational performance and extensibility in a parallel operating environment. Menon builds on Trefethen to improve and extend the parallel processing capabilities of MultiMATLAB: “This system will enable users to access high-performance parallel routines from within the MATLAB environment, to extend the environment with new parallel routines, and to use these routines to develop parallel applications with the MATLAB language.” Ex. 1005 Abstract. Menon is intended to be read in conjunction with Trefethen, as would be expected from two references generated by the same research group at the same university addressed to the same technical subject matter about a year apart. Ex. 1005, 1; Ex. 1006, Ex. 1086 ¶¶ 65, 101, 102. The very first citation in Menon is to Trefethen. Ex. 1005, 2, 16.” slip op. at 30

  Patent outcomesUS 11,570,034 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,570,034
• Apple Inc. v. Ferid AllaniAll claims unpatentable
  PTAB · Aug 25, 2026 · IPR2025-00857 · APJ Jeffrey S Smith · IPR · Final written decision

  Claims 1–27 are unpatentable: claims 24 and 26 over Rossmann and Himmel; claims 1–2, 4–6, 10–23, 25, and 27 over Rossmann, Himmel, King, and Adar; claims 3 and 7–9 over those references and Boyle.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “we consider the type of problems encountered in the art, the prior art solutions to those problems, the rapidity with which innovations are made, the sophistication of the technology, and the educational level of active workers in the field. See Custom Accessories, Inc. v. Jeffrey-Allan Industries, Inc., 807 F.2d 955, 962 (Fed. Cir. 1986); see Orthopedic Equip. Co. v. United States, 702 F.2d 1005, 1011 (Fed. Cir. 1983).” slip op. at 6

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

    “meaning of “icon” as claimed, including the dependent claims, the specification, the prosecution history, and the extrinsic evidence including expert testimony and dictionary definitions, we determine that the plain meaning of “icon” is readily apparent from the claims themselves. See Phillips, 415 F.3d at 1314 (“In some cases, the ordinary meaning of claim language as understood by a person of ordinary skill in the art may be readily apparent even to lay judges.”). We find that the plain meaning of “icon” as claimed encompasses at least “textual elements” because claim 20 recites “the icons comprise textual elements.” See id. (“Other claims of the patent in question, both asserted and unasserted, can also be valuable sources of enlightenment as to the meaning of a claim term.”). We highlight that the additional intrinsic evidence cited by the parties is consistent with the plain meaning. For example, Figures 1 and 2 of the specification show icons comprising textual elements. As another example, during prosecution of the ’058 patent, the Examiner found that the claimed icons were taught by textual hyperlinks. Ex. 1002, 586, 592. In order to overcome the Examiner’s rejection and obtain an allowance (id. at 641–50), applicant subsequently amended the claims to recite “specifically designed,” thus implicitly conceding to the Examiner’s interpretation of icon as encompassing textual hyperlinks. Id. at 625–640; see PO Resp. 43–44 (citing Ex. 1002, 626–27, 645–46) (acknowledging that the Examiner allowed the claims because applicant amended the claims to recite “specifically designed for containing a set of icons.”).” slip op. at 11

  • Claim Construction › Intrinsic evidence (Phillips canons) › Prosecution history disclaimer / disavowalTerm construed petitioner constructionDecided for petitioner

    “Requiring an element to be "specifically designed" for another element narrows the claim because it requires more than the first element being merely capable of being used with the second element. The term "configured to" is generally construed narrowly to mean "made to" and "designed to" rather than broadly to require merely "capable of". See In re Giannelli, 739 F. 3d 1375, 1379-80 (Fed. Cir. 2014) (the phrase "configured to" requires more than "mere capability." Rather, that term is synonymous with "made to" and "designed to."). However, rather than use "configured to", in order to avoid any confusion as to the narrower scope of the claims as amended, Applicant herein directly and explicitly requires "designed to." In re Giannelli at 1379-80 (Fed. Cir. 2014) (reversing an obviousness rejection because (1) the claims were properly construed narrowly to mean "designed to" and not broadly to encompass merely "capable of", and (2) the USPTO had not explained the motivation for modifying the prior art to meet the "design to" requirement) See also MPEP 2111.04, citing to In re Giannelli, for the proposition that a claim can be narrowed to require that it be "designed and constructed to be used" in a specific manner (as a rowing machine in the case of In re Giannelli). Logan has not been specifically designed and constructed in the required manner, so it does not cure all deficiencies of the primary reference Iki (which lacks any tree menu structure). Logan describes only "remote web" pages 90, 95 that are merely pages retrieved from Web browsing and stored in a web computer 25. Iki as modified by Logan would result on in a tree menu structure wherein not all levels of the tree included the required selection pages specifically designed for containing the claimed set of icons. Ex. 1002, 626–27 (emphasis omitted).” slip op. at 14

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

    “Petitioner contends that a person of ordinary skill in the art would have modified Rossmann to include several advantages expressly taught by Himmel: Himmel’s consumer hot list bookmark set for the benefits of providing a user with a consistent user interface when accessing a website; to simplify navigation for the user by providing an additional navigation aid; to provide more immediate access to commonly used web actions; to reduce the network traffic required to navigate through webpages to arrive at a particular web function; and to reduce usage charges and data usage. Pet. 22–23 (citing Ex. 1003 ¶¶ 94–99; Ex. 1004, 2:38–56, 12:24–34, 14:35–44; Ex. 1005, 18:63–65, 20:11–16). Petitioner contends that modifying Rossmann’s Figures 4A through 4G to include Himmel’s consumer hot list bookmark set yields each selection page including both selection icons for navigating to other local pages along with direct access icons such as on sale today to directly navigate to a predetermined web site to perform a common web action. Id. at 23–25 (citing Ex. 1003 ¶¶ 96–100; Ex. 1004, Figs. 4D–F). Petitioner contends that the selection page of Rossmann as modified by the bookmark set of Himmel teaches a first locally stored page specifically designed to include a direct access icon because the selection page is “used to include” a direct access icon, such as on sale today, and that during use, this selection page is programmed to display the set of direct access icons for selection by the user. Pet. 25 (citing Ex. 1003 ¶¶ 96–100); see id. at 21–24. Petitioner contends that a person of ordinary skill in the art would have had a reasonable expectation of success because technology for bookmarking websites and web actions was known at the time of invention, modifying Rossmann to utilize known bookmark manager software would have been straight forward, Rossmann already includes hardware and programming instructions to access a web server, and Himmel teaches that known prior art methods utilized both selection and direct access icons on a single page. Id. at 25–26 (citing Ex. 1003 ¶¶ 101–103; Ex. 1004, 2:38–41, 14:21–44; Ex. 1005, Fig. 6A, 21:27–34).” slip op. at 19

  Patent outcomesUS 10,943,058 unpatentable
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 10,943,058
• Yealink (USA) Network Technology Co. Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.All claims unpatentable
  PTAB · Jul 28, 2026 · IPR2025-00491 · APJ Frederick C Laney · IPR · Final written decision

  Claims 1–18 are unpatentable as obvious over Beel and Dinka, with or without Christison; the Kaplan, Van de Laar, and Christison ground fails for lack of motivation to combine.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Pet. 9–10 (citing Ex. 1002 ¶¶ 36–37). “Patent Owner does not dispute Petitioner’s proposed level of skill in the art.” PO Resp. 6. On the complete record, we adopt Petitioner’s proposed definition of a person of ordinary skill in the pertinent art, as it is consistent with the ’972 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 10

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

    “Rather than addressing Petitioner’s proposals, Patent Owner states “the claims of the ’972 Patent require no construction as they are valid under their plain and ordinary meaning.” PO Resp. 6. Our decision in this matter does not turn on resolving any particular differences between the parties’ constructions. Therefore, because only those terms in controversy need to be construed, and only to the extent necessary to resolve the controversy, we determine that no claim term requires express construction in this proceeding and that the ordinary and customary meaning of the claim terms apply. See Realtime Data LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019).” slip op. at 11

  • Expert testimonyPatent owner expert discountedDecided for petitioner

    “device. The ’972 patent expressly defines endpoints broadly “as data sources or sinks.” Ex. 1001, 7:64–67. And the ’972 patent admits that Beel’s Figure 11 discloses the same endpoints depicted in the ’972 patent’s own Figure 4. Id. at 4:28–33, 16:44–67. Beel’s Figure 11 and accompanying description disclose a “[m]ass storage device 12,” a “USB audio device 14,” and a “USB HID device 13” on the peripheral device. Ex. 1005, Fig. 11, ¶¶ 320–323. Patent Owner’s own declarant conceded that a mass storage device is “a type of endpoint” (Ex. 1034, 43:19–21), and that “audio devices are endpoints” (id. at 57:5–61:4). We give reduced weight to Patent Owner’s contrary position to the extent it rests on the premise that a reference cannot disclose an endpoint unless it uses the word “endpoint” (Ex. 2030 ¶ 94; Ex. 1034, 43:19–44:16, 72:18–73:12); a premise that is inconsistent with the ’972 patent’s own broad definition and with the ’972 patent’s admission regarding Beel’s Figure 11. As additional support not separately emphasized by the parties in this connection, we note Dr. Almeroth’s technical explanation that, for data to pass from a functional device to a peripheral device, “both the functional device and the peripheral device must have ‘endpoints’”—a data source and a data sink—reasoning consistent with the ’972 patent’s definition. Ex. 1002 ¶ 125.” slip op. at 27

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

    “First, we agree with Patent Owner that, under the ordinary meaning of the claim language, the endpoint is an endpoint of the peripheral device, and that it must be “a data source or a data sink which is able to store or emit data, of the functional device exposed or made available on the first peripheral device.” Ex. 1001, 23:11–17. The limitation thus identifies a structure—an endpoint, residing on the peripheral device, that is a source or sink and that corresponds to (is “of”) the functional device—through which the communication recited in subsequent element (g) is carried out. By its terms, it imposes no requirement as to the direction in which data flows; it requires only that the endpoint be a data “source” or a data “sink” that is able to “store or emit” data. The operative transmit-and-receive communication “from the functional device to the processing device via the . . . endpoint” is recited in subsequent element (g), which we take up separately below. The disputed question under this limitation is therefore the structural one: whether Beel discloses, on the peripheral device, an endpoint that is “of the functional device.” Because the inquiry is structural and non-directional, we are not persuaded that the audio-out orientation of Beel’s described embodiment, on which Patent Owner relies, is dispositive of this limitation. device. The ’972 patent expressly defines endpoints broadly “as data sources or sinks.” Ex. 1001, 7:64–67. And the ’972 patent admits that Beel’s Figure 11 discloses the same endpoints depicted in the ’972 patent’s own Figure 4. Id. at 4:28–33, 16:44–67. Beel’s Figure 11 and accompanying description disclose a “[m]ass storage device 12,” a “USB audio device 14,” and a “USB HID device 13” on the peripheral device. Ex. 1005, Fig. 11, ¶¶ 320–323. Patent Owner’s own declarant conceded that a mass storage device is “a type of endpoint” (Ex. 1034, 43:19–21), and that “audio devices are endpoints” (id. at 57:5–61:4). We give reduced weight to Patent Owner’s contrary position to the extent it rests on the premise that a reference cannot disclose an endpoint unless it uses the word “endpoint” (Ex. 2030 ¶ 94; Ex. 1034, 43:19–44:16, 72:18–73:12); a premise that is inconsistent with the ’972 patent’s own broad definition and with the ’972 patent’s admission regarding Beel’s Figure 11. As additional support not separately emphasized by the parties in this connection, we note Dr. Almeroth’s technical explanation that, for data to pass from a functional device to a peripheral device, “both the functional device and the peripheral device must have ‘endpoints’”—a data source and a data sink—reasoning consistent with the ’972 patent’s definition. Ex. 1002 ¶ 125. Third, we find that the endpoint Beel discloses is a data source or a data sink that is “able to store or emit data, of the functional device.” We begin with the words of the limitation. The endpoint need only be “able to store or emit data”—language of capability, not a requirement that particular data actually traverse the endpoint in operation, and still less in a particular direction. And the endpoint is defined by the character of the data it handles: it is “a data source or a data sink,” which the ’972 patent instructs An audio endpoint, so understood, is characterized as an audio source or sink; its structure is not tied to any single instance of an audio device. On that understanding, Beel’s disclosure establishes the required capability directly. Beel discloses that “audio data is captured through a virtual sound card interface added as a logical device over the physical interface provided in the peripheral device,” Ex. 1005 ¶ 43, that the peripheral device “acts as a composite device comprising for instance a (virtual) audio speaker device,” id. ¶ 317, and that “audio data is captured at this interface . . . internally in the peripheral device 32” and streamed over the communications network, id. ¶ 319. Beel thus shows the endpoint on the peripheral device actually storing and emitting audio—and, correspondingly, video—data, which is the very type of data produced and consumed by the audio/visual functional devices connected to the base unit, including the microphones, cameras, speakers, and displays. Id. ¶ 120. An endpoint shown to store or emit audio and video data is necessarily one that is “able to store or emit” such data; the capability the limitation requires is thus established by Beel’s disclosure.” slip op. at 26

  Patent outcomesUS 10,684,972 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,684,972
• Amazon.Com, Inc. / Amazon.Com Services LLC et al. v. Soundclear Technologies LLCAll claims unpatentable
  PTAB · Jul 27, 2026 · IPR2025-00565 · APJ Michael R Zecher · IPR · Final written decision

  Claims 1–5 are unpatentable because Amazon showed they are anticipated by Shin; the Board did not reach Amazon’s contingent obviousness ground over Shin.

  RulingsFinal written decision

  • BurdenOther

    “Written Decision under 35 U.S.C. § 318(a) as to the patentability of claims 1–5 of the ’337 patent. For the reasons we identify below, we hold that Amazon has demonstrated by a preponderance of the evidence that these claims are unpatentable.” slip op. at 2

  • Skill levelOther

    “2. Level of Skill in the Art In determining whether an invention would have been obvious, we” slip op. at 18

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

    “1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17

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

    “1. Principles of Law To establish anticipation, “all of the elements and limitations of the” slip op. at 17

  Patent outcomesUS 11,069,337 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,069,337
• Google LLC v. Brodti Inc.All claims unpatentable
  PTAB · Jun 30, 2026 · IPR2025-00472 · APJ Stephen E Belisle · IPR · Final written decision

  Claims 1–20 are unpatentable as obvious under § 103 over Nicholas, Laidlaw, Mayadas, and Error, with Yasnovsky added for claims 7, 8, 16, 17, and 20.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Petitioner’s and Patent Owner’s definitions for the level of ordinary skill in the art are substantially similar. In light of the record before us, we adopt Patent Owner’s proposal regarding the level of ordinary skill in the art. Based on our review of the ’898 patent and the prior art of record, we determine that the definition offered by Patent Owner comports with the qualifications a person would have needed to understand and implement the teachings of the ’898 patent and the prior art, particularly experience pertaining to Internet/web interfaces and web-based media. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (explaining that specific findings regarding ordinary skill level are not required “where the prior art itself reflects an appropriate level and a need for testimony is not shown”) (quoting Litton Indus. Prods., Inc. v. Solid State Sys. Corp., 755 F.2d 158, 163 (Fed. Cir. 1985)). Neither party argues, nor do we determine, that the outcome of our Decision depends on which party’s definition is selected.” slip op. at 11

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

    “includ[e] a server and one or more webpages that may be provided by the server for display in a web browser.” Pet. Reply 5 (citing Ex. 1026 ¶¶ 13–15). Petitioner argues, and we agree, that the Specification strongly supports this construction (requiring a server and webpage(s)) by describing a “website” as synonymous with a server computer system: “The WWW [(World Wide Web)] service allows a server computer system (i.e., Web server or Web site) to send graphical Web pages or screens of information such as the advertising materials to a remote client computer system 10.” Ex. 1001, 3:66–4:2 (emphases added); see id. at Fig. 1 (depicting a service engine and webpages as a web server, i.e., website), 3:15–18 (describing Figure 1 as showing “a server of the website” (emphasis added)); Pet. Reply 5; see Ex. 1026 ¶ 13. Petitioner also submits a supporting (and persuasive) contemporaneous technical dictionary definition of “website,” which highlights the distinction between a lay person’s understanding of the term versus that of the relevant artisan. Pet. Reply 5–6. This definition explains that the “common but technically inaccurate” usage of “website” is to mean “Web page,” but the technically correct usage of “website” is to mean “one or more computers that are associated with a fully qualified domain name and make content available on the Web.” Id. (citing Ex. 1028, 402). Petitioner’s expert, Dr. Crovella, likewise testifies that “[a] website cannot exist without the server or computer that provides its webpages.” Ex. 1026 ¶ 15; see Ex. 1027, 36:8–20 (Patent Owner’s expert, Dr. Myler, agreeing that “it has to be some machine somewhere that’s providing the webpages for the website.”). The limitations of claim 1 also support Petitioner’s position that “website” includes a server and webpage(s). Reply 5. For example, claim 1 recites advertising material for “populat[ing] on one or more websites,” and selected “advertising buy options comprise at least one website of the respective websites.” Ex. 1001, 10:29–51 (emphases added). We find these limitations make the most technical sense where “website” implicates an Internet domain or domain name, such as brodti.com, which itself is a computer system (server) and associated webpage(s) reached via that domain name. This interpretation aligns with testimony of Patent Owner’s expert, Dr. Myler, in which he states that a “website” describes “a group of webpages at a particular domain (e.g., www.espn.com, www.espn.com/nba, www.espn.com/nfl, www.espn.com/nhl).” Ex. 2009 ¶ 68 (emphasis in italics added). In other words, brodti.com and espn.com are two different websites, with each website having one or more webpages (e.g., www.espn.com/nba, www.espn.com/nfl), and such websites include a server giving life to such webpage(s). slip op. at 15

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

    “Patent Owner proffers that placing advertising material “within” web property content means “inserting” an advertisement into particular content. PO Resp. 12. Petitioner responds that “placing . . . within” means what it says, and notes that “[t]he words ‘insert’ or ‘inserting’ appear nowhere in the [Specification].” Pet. Reply 7–8; see id. at 8 (Petitioner arguing that Patent Owner’s expert “admitted that the claim does not specify details regarding how advertising material needs to be placed within web property content.” (citing Ex. 1027, 29:18–24)). Patent Owner replies that the relevant artisan allegedly “would have understood ‘placing . . . within’ to mean ‘inserting into,’” but then submits that whether “placing . . . within” versus “inserting into” is used does not matter because Petitioner allegedly has not demonstrated the obviousness of either. PO Sur-reply 17. As Petitioner observes, “[i]t is unclear if Patent Owner intended any difference in meaning between these two terms.” Pet. Reply 8. Accordingly, based on the complete record before us, we determine that no further construction of this limitation is needed, and “placing A within B” means what it says—“placing A within B.”” slip op. at 20

  • Expert testimonyPetitioner expert creditedOther

    “determining” of impression validity feature of limitation 1[h] by disclosing “a ‘single-pixel’ image technique for determining that an impression is valid,” e.g., by using “cookies.” Pet. 42–45. Petitioner’s expert, Dr. Crovella, testifies that this “single-pixel” impression tracking technique would have been a “well-known” technique to the relevant artisan, and as described by Error, operates as follows: [A] URL link for a single pixel (or transparent) image file is embedded onto a webpage that is delivered to a web browser. The image is not meant to be viewed and will likely not be visible to the user. After the user’s browser receives the webpage, it uses the embedded URL link to request the single-pixel image from a server. The receipt of that request by the server provides an indication that the user’s web browser actually received and presented the web page to the user. Ex. 1002 ¶ 133 (citing Ex. 1007, 1:36–54, 2:6–21); see id. at ¶¶ 132–139. slip op. at 43

  Patent outcomesUS 11,416,898 unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,416,898
• Palo Alto Networks, Inc. / Cisco Systems, Inc. et al. v. Centripetal Networks, Inc.All claims unpatentable
  PTAB · Jun 11, 2026 · IPR2022-01151 · APJ Kevin F Turner · IPR · Remand

  On remand, the Board held claims 1, 24, and 25 unpatentable as obvious over Buruganahalli; the copying evidence did not outweigh the strong obviousness showing.

  RulingsRemand decision

  • RemandOther

    “Scope on Remand On remand, the panel here will not address issues outside the scope of the Federal Circuit’s mandate. See Hayward Indus., Inc. v. Pentair Water Pool & Spa, Inc., 814 F. App’x 592, 597 (Fed. Cir. 2020) (“The Board is bound by the terms of a mandate issued by an appellate court. Aydin Corp. v. Widnall, 121 F.3d 726, 1997 WL 413329, at *3 (Fed. Cir. 1997). ‘Unless remanded by [an appellate] court, all issues within the scope of the appealed judgment are deemed incorporated within the mandate and thus are precluded from further adjudication.’ Engel Indus., Inc. v. Lockformer Co., 166 F.3d 1379, 1383 (Fed. Cir. 1999).”). The sole issue on remand is whether “the evidence of copying” is sufficient to overcome the obviousness ground of unpatentability over Buruganahalli. Centripetal Networks, 19–20. We restate portions of the former Final Written Decision, as an aid to the reader, but substantially incorporate the analysis of the prior Decision below. C.” slip op. at 4

  • Obviousness (§103) › Objective indicia / secondary considerations › CopyingObjective indicia outweighedDecided for petitioner

    “given to the Eastern District of Virginia court’s opinion because it was later vacated. The district court considered all of the Read factors (applying Read Corp. v. Portec, Inc., 970 F.2d 816, 826-827 (Fed. Cir. 1992)), of which only the first factor is directed to deliberate copying, although factors 2 and 9 bear indirectly on the issue of copying. The district court determined that “[t]he fact that Cisco released products with Centripetal’s functionality within a year of these meetings goes beyond mere coincidence. Therefore, the fact that Cisco’s system mirrors the functionality of the Centripetal patents is compelling evidence that damages should be enhanced for copying.” Ex. 1027, 157. Without more, it is difficult to evaluate the processes that the district court employed to reach its determination. As the Federal Circuit instructed, we need “not [] go searching throughout the entire litigation record to find the evidence of copying, but [we have] an obligation to consider the specific evidence that was put before” us. Centripetal Networks, 19. We continue to determine that the vacated finding of the district court should be provided little weight, especially in view of the strong case of obviousness discussed above.” slip op. at 40

  • Obviousness (§103) › Objective indicia / secondary considerations › Long-felt need / failure of othersObjective indicia outweighedDecided for petitioner

    “need and industry recognition for the technology claimed in the ‘856 Patent because it describes the problem of detecting threats in encrypted traffic as ‘unsolvable.’” PO Resp. 68 (citing Ex. 1027, 64). Given that this is a press release by a company announcing that company’s new commercial product, however, we 8 The concurrence reevaluates Patent Owner’s evidence of industry praise and nexus, but we deem such considerations outside the remit of the Federal Circuit’s remand. are reluctant to give the “unsolvable” characterization much weight, as it may amount to puffery. But beyond that, it appears that the problem identified as “unsolvable” in the press release––“detect[ing] known attack signatures even in encrypted traffic”––had, in fact, already been solved in Buruganahalli, using the very same hello message, flow correlation, and man-in-the-middle techniques described in the ‘856 Patent. We thus cannot say that the press release identifies a long-felt need that was actually unsolved. See ZUP, 896 F.3d at 1374 (explaining that “[w]here the differences between the prior art and the claimed invention are . . . minimal . . . it cannot be said that any long-felt need was unsolved”) (quoting Geo. M. Martin Co. v. All. Mach. Sys. Int’l LLC, 618 F.3d 1294, 1304–05 (Fed. Cir. 2010) (first alteration in original)).” slip op. at 35

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

    “The District Court did not provide an element-by-element analysis of how the claims of the ‘856 Patent cover this description. See Ex. 1027, 41. However, from the description, we understand the Court to have concluded that the system receives rules, identifies a set of packets as part of a flow using the NetFlow logs, “determines” that encrypted packets in the flow match known malicious signatures based on unencrypted data in other packets (e.g., data in the SNI), and then filters the flow based in a URI (e.g., that from the SNI), routing it to the null interface. The Court does not describe how the system “determines” that encrypted packets match known malicious signatures based on information in unencrypted packets, but we assume that is done as in the ‘856 Patent, by correlation, i.e., an encrypted packet is “determined” to match a threat indicator if it is in the same flow as a packet with unencrypted information that matches the threat indicator.10 With that understanding, we conclude that the allegedly infringing system operates, as least at the level described in the court’s decision, in the same way Buruganahalli’s system operates, filtering encrypted packets due to their presence in a flow that includes packets with unencrypted data, such as in a handshaking packet. It follows that Patent Owner is unable to establish a nexus, because “[w]here the offered secondary consideration actually results from something other than what is both claimed and novel in the claim, there is no nexus to the merits of the claimed invention.” Novartis AG v. Torrent Pharms. Ltd., 853 F.3d 1316, 1330 10 See Ex. 1001, 9:3–10 (explaining that, at step 17, rule gate 120 may “determine . . . that the packets comprise data corresponding to the network-threat indicators, for example, by correlating the packets with one or more packets previously determined . . . to comprise data corresponding to the network-threat indicators based on data stored in [the] logs”).” slip op. at 38

  Patent outcomesUS 9,917,856 unpatentable
  § 103 obviousness
  Patents in suitUS 9,917,856

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.