• Qualcomm Incorporated v. Unm Rainforest InnovationsAll claims unpatentable
  PTAB · Sep 30, 2025 · IPR2021-00375 · APJ Kristen L Droesch · IPR · Remand

  Proposed substitute claims 44–47, 49, and 50 are unpatentable as obvious under collateral estoppel; the Board denied Patent Owner’s motion to amend.

  RulingsRemand decision

  • RemandOther

    “the Acting Director of the USPTO (Paper 81, “Acting Director’s Order”) and after a decision by the U.S. Court of Appeals for the Federal Circuit (“the Federal Circuit”) in ZyXEL Communications Corp. v. UNM Rainforest Innovations, 107 F.4th 1368 (Fed. Cir. 2024) (“Federal Circuit Decision”) regarding the Board’s original Final Written Decision (Paper 68, “Final Written Decision” or “Final Dec.”) in this proceeding. In particular, the court remanded to the Board to determine if proposed substitute claims 44–47, 49, and 50 are unpatentable as obvious under collateral estoppel based on the court’s holding that claims 1–4 and 6–8 are unpatentable as obvious. ZyXEL, 107 F.4th at 1371, 1384.” slip op. at 2

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

    “proposed substitute claim 44 presents the same issues as those litigated before the Federal Circuit: whether it would have been obvious to a person of ordinary skill in the art to include the first key element and whether it would have been obvious to a person of ordinary skill in the art to include the second key element.” slip op. at 9

  • PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, deniedDenied

    “Final Written Decision, and the Federal Circuit Decision, as well as the postremand briefing, we determine that the application of collateral estoppel to proposed substitute claim 44 is appropriate. It is also appropriate to apply collateral estoppel to substitute claims 45–47, 49, and 50. This is because proposed substitute claims 45–47, 49, and 50 depend from proposed substitute claim 44 and recite identical limitations to dependent claims 2–4, 6, and 7. Therefore, the resolution of the question of obviousness of the subject matter of proposed substitute claims 45–47, 49, and 50 necessarily presents the same issues of whether it would have been obvious to a person of ordinary skill in the art to include the first key element and whether it would have been obvious to a person of ordinary skill in the art to include the second key element.” slip op. at 11

  Patent outcomesUS 8,265,096 unpatentable
  § 103 obviousness
  Patents in suitUS 8,265,096
• Aylo Freesites Ltd v. Wellcomemat, LLCAll claims unpatentable
  PTAB · Aug 26, 2025 · IPR2024-00710 · APJ Brian P Murphy · IPR · Final written decision

  Claims 13–15 and 17–20 are unpatentable: claims 13–15 and 20 as anticipated by Fegan, claim 17 as obvious over Fegan and Sull, and claims 13–14 and 17–20 as obvious over Vasilevsky and Logan.

  RulingsFinal written decision

  • ExcludeMotion to exclude, deniedDenied

    “afforded experts in forming opinions in reliance on hypotheticals and “presentation of data to the expert outside of court and other than by his own perception,” i.e., hearsay. Id. (Adv. Comm. Notes). And where a court acts as fact finder, rather than a jury, the danger of unfair prejudice to the objecting party is substantially diminished. See Science Applications Int’l Corp. v. United States, 175 Fed. Cl. 389, 395 (2025) (“bench trials limit the ‘concern for juror confusion or potential prejudice’”) (citations omitted). The Board, sitting as a non-jury tribunal with administrative expertise, is well-positioned to determine and assign appropriate weight to evidence presented, as we have done in the present case. See Gnosis S.p.A. v. S. Alabama Med. Sci. Found., Case IPR2013-00118, slip op. at 43 (PTAB June 20, 2014) (Paper 64); see also Donnelly, 123 F.2d at 224 (“One who is capable of ruling accurately upon the admissibility of evidence is equally capable of sifting it accurately after it has been received.”). In rendering our Decision, we have assigned appropriate weight to Exhibit 2022 in view of the entire record before us. For the reasons given above, we deny Petitioner’s motion to exclude Exhibit 2022.” slip op. at 78

  Patent outcomesUS 8,307,286 unpatentable
  Nonecites KSR
  Patents in suitUS 8,307,286
• Google LLC v. Metarail, Inc.Rehearing denied
  PTAB · Aug 25, 2025 · IPR2024-01271 · APJ Frances L Ippolito · IPR · Rehearing

  The Board denied Google’s rehearing request, leaving institution denied for claims 1–21 because the petition did not show a reasonable likelihood that Belanger-Halevy taught limitation [1B].

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “II. ANALYSIS A request for rehearing “must specifically identify all matters the party believes the Board misapprehended or overlooked, and the place where each matter was previously addressed in a motion, an opposition, a reply or sur-reply.” 37 C.F.R. § 42.71(d). The party challenging a decision bears the burden of showing the decision should be modified. Id. We address Petitioner’s rehearing arguments below.” slip op. at 2

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied

    “variable data database’ as required by claim 1.” Dec. 22. We discussed and quoted extensively from Petitioner’s expert declaration of Dr. Fox and Patent Owner’s expert declaration of Dr. Malek. Id. at 22–26 (citing Ex. 1003 ¶ 94; Ex. 2001 ¶¶ 68, 70). In reviewing the parties’ submissions, we found that: Halevy’s disclosures are consistent with Patent Owner’s arguments and Dr. Malek’s testimony that Halevy does not teach mapping fields to one another or mapping of fields to one another through SO-properties. For example, as described, in Figure 6 and Halevy as a whole, Halevy does not teach or suggest mapping or linking different keywords to one another, rather the keywords are mapped to SO-properties.” slip op. at 5

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

    “Dr. Fox states that “Halevy’s disclosure of a form database in which corresponding fields from different forms on different websites map to the same SO-properties based on the SO-class identified for the form would have been recognized by a POSA as what the ’342 patent refers to as a universal variable map.” Ex. 1003 ¶ 98 (citing Ex. 1001, 17:48– 52). Based on this conclusory opinion, Dr. Fox reasons that Halevy’s form database is a “universal variable map” that must also link computer-readable field identifiers from multiple different websites to each other in the form database, because field identifiers are mapped to the same SO-properties associated with an SO-class.” Id. (emphasis omitted). We observe first that Dr. Fox’s conclusion is not supported by the cited portions of the ’342 patent. In column 17, lines 48–52, the ’342 patent explains that fields or variables may be part of forms, and variations of the data fields or variables “may include a source form, a destination form, a single source to many destination form, many sources to one destination form, cascading forms (e.g., a first form links to a second form which links to a third form, etc.) and so on.” Ex. 1001, 17:48–52. While this portion of the ’342 patent indicates that forms may include variations on fields or variables, it does not describe linking or mapping variables to one another. Ex. 2001 ¶ 75 (“[T]hat portion of the specification does not have anything to do with the definition of a “universal variable map.” Rather, it merely discusses different types of variables and fields that might appear in different types of forms.”). Dec. 28–29. We again referred to the disclosure of the ’342 patent to address evidence in the Petition relied upon by Dr. Fox to support Petitioner’s position. Id. We credited Dr. Malek’s testimony over Dr. Fox’s testimony because Dr. Malek underlined the distinctions between the asserted Belanger-Halevy prior art combination and limitation [1B]. Dec. 28–31. In short, any confusion applying the prior art Belanger-Halevy references to the claim limitation is rooted in the Petition. The Board denied the Petition because the Petition did not demonstrate a reasonable likelihood of showing that Belanger-Halevy discloses or teaches limitation [1B] of the ’342 patent.” slip op. at 5

  None
  Patents in suitUS 10,262,342
• Google LLC v. Metarail, Inc.Rehearing denied
  PTAB · Aug 25, 2025 · IPR2024-01270 · APJ Frances L Ippolito · IPR · Rehearing

  The Board denied Google’s rehearing request, leaving in place the denial of institution because the Petition did not show a reasonable likelihood that Belanger-Halevy teaches limitation [1C] of claims 1–26.

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “II. ANALYSIS A request for rehearing “must specifically identify all matters the party believes the Board misapprehended or overlooked, and the place where each matter was previously addressed in a motion, an opposition, a reply or sur-reply.” 37 C.F.R. § 42.71(d). The party challenging a decision bears the burden of showing the decision should be modified. Id. We address Petitioner’s rehearing arguments below.” slip op. at 2

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied

    “[m]issing, however, from Halevy’s disclosure is any teaching or suggestion that a ‘plurality of computer-readable field identifiers’ are mapped ‘to one another’ as required by claim 1.” Dec. 22. We discussed and quoted extensively from Petitioner’s expert declaration of Dr. Fox and Patent Owner’s expert declaration of Dr. Malek. Id. at 22–26 (citing Ex. 1003 ¶ 104; Ex. 2001 ¶¶ 69, 71). In reviewing the parties’ submissions, we found that: Halevy’s disclosures are consistent with Patent Owner’s arguments and Dr. Malek’s testimony that Halevy does not teach mapping fields to one another or mapping of fields to one another through SO-properties. For example, as described, in Figure 6 and Halevy as a whole, Halevy does not teach or suggest mapping or linking different keywords to one another, rather the keywords are mapped to SO-properties. slip op. at 5

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

    “Dr. Fox states that “Halevy’s disclosure of a form database in which corresponding fields from different forms on different websites map to the same SO-properties would have been recognized by a POSA as what the ’378 patent refers to as a universal variable map.” Ex. 1003 ¶ 108 (citing Ex. 1001, 17:42–46). Based on this conclusory opinion, Dr. Fox reasons that Halevy’s form database is a “universal variable map” that must also link computer-readable field identifiers (including parameter names) from multiple different websites to each other in the form database, because the field identifiers are mapped to the same SO-properties associated with an SO-class. Id. We observe first that Dr. Fox’s conclusion is not supported by the cited portions of the ’378 patent. In column 17, lines 42–46, the ’378 patent explains that fields or variables may be part of forms and variations of these data fields or variables “may include a source form, a destination form, a single source to many destination form, many sources to one destination form, cascading forms (e.g., a first form links to a second form which links to a third form, etc.) and so on.” Ex. 1001, 17:42–46. While this portion of the ’378 patent indicates that forms may include variations on fields or variables, it does not describe any linking or mapping of variables to one another. Ex. 2001 ¶ 76 (“[T]hat portion of the specification does not have anything to do with the definition of a “universal variable map.” Rather, it merely discusses different types of variables and fields that might appear in different types of forms.”). Dec. 28–29. We again referred to the disclosure of the ’378 patent to address evidence in the Petition relied upon by Dr. Fox to support Petitioner’s position. Id. We credited Dr. Malek’s testimony over Dr. Fox’s testimony because Dr. Malek underlined the distinctions between the asserted Belanger-Halevy prior art combination and limitation [1C]. Dec. 28–31. In short, any confusion applying the prior art Belanger-Halevy references to the claim limitation is rooted in the Petition. The Board denied the Petition because the Petition did not demonstrate a reasonable likelihood of showing that Belanger-Halevy discloses or teaches limitation [1C] of the ’378 patent.” slip op. at 5

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

    “Finally, with regard to the Reply and Sur-Reply submitted by the parties (Req. 9), we note that our Decision on Institution reviewed the parties’ discussion of claim construction, but ultimately determined that “[b]ased on our review of the preliminary record, we do not need to construe any terms expressly to reach our decision.” Dec. 11. Thus, we disagree with Petitioner that we misconstrued the mapping limitation where we did not find it necessary to construe any claim term for the purposes of our institution decision because we determined the Petition deficient for failing to meet our threshold requirements as discussed above and in detail in the Decision on Institution. See Req. 1–11.” slip op. at 7

  Claim construction
  Patents in suitUS 9,633,378
• Reolink Innovation Inc. / Shenzhen Reolink Technology Co., Ltd. v. Throughtek Co., Ltd.All claims unpatentable
  PTAB · Aug 4, 2025 · IPR2024-00509 · APJ Michael J Strauss · IPR · Final written decision

  Claims 1–4 and 6–19 are unpatentable as obvious over Throughtek-2012 and the Lorex Video; claims 1–3, 6, 10, 12–14, 17, and 18 are also unpatentable under two other grounds.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “II. ANALYSIS A. Level of Ordinary Skill in the Art Relying on the testimony of Dr. Bims, Petitioner proposes that a person of ordinary skill in the art at the time of the ’842 patent would have been a person having a bachelor’s degree in electrical engineering and two years of work experience with network and communication technologies. Pet. 11 (citing Ex. 1001 ¶¶ 15–16). Patent Owner does not provide any proposed qualifications for a person of ordinary skill in the art. 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) (citation omitted). The level of ordinary skill in the art is also reflected by the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). We adopt the assessment offered by Petitioner as it is consistent with the ’842 patent and the asserted prior art.” slip op. at 7

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

    “Petitioner asserts “no claim elements need a formal construction for purposes of resolving the controversy in this proceeding.” Pet. 11 (citing Ex. 1001 ¶ 55; Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011); Google Inc. v. Intellectual Ventures II LLC, 701 Fed. Appx. 946, 956 (Fed. Cir. 2017)). Petitioner states “[a]ll claim terms should be construed according to the Phillips standard.” Id. (citing Phillips, 415 F.3d at 1303; 37 C.F.R. §42.100). Patent Owner presents no proposed claim constructions. We determine that we need not expressly construe any claim terms to resolve the parties’ disputes on the current record. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“[W]e 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 8

  • Disclosure Requirements (§112) › Written description (Ariad)Not entitled to earlier dateDecided for petitioner

    “In addition, “[n]egative claim limitations are adequately supported when the specification describes a reason to exclude the relevant limitation. Such written description support need not rise to the level of disclaimer.” Santarus, Inc. v. Par Pharm., Inc., 694 F.3d 1344, 1351 (Fed. Cir. 2012). A reason to exclude an element may be found in “statements in the specification expressly listing the disadvantages of using” that element. Santarus, 694 F.3d at 1351. Another reason to exclude may be when the specification “distinguishes among” the element and alternatives to it. Inphi Corp. v. Netlist, Inc., 805 F.3d 1350, 1357 (Fed. Cir. 2015). As the Federal Circuit explained, “[t]he common denominator of these examples [(i.e., the reasons to exclude an element)] is disclosure of the element.” Novartis Pharm. Corp. v. Accord Healthcare, Inc., 38 F.4th 1013, 1017 (Fed. Cir. 2022). More particularly, “[s]ilence is generally not disclosure.” Novartis, 38 F.4th at 1017; see also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1288 (Fed. Cir. 2021). Accordingly, “the written description requirement cannot be met through simple disregard of the presence or absence of a limitation.” Novartis, 38 F.4th at 1017. Our reviewing court further notes that “it is possible that the written description requirement may be satisfied when a skilled artisan would understand the specification as inherently disclosing the negative limitation.” Novartis, 38 F.4th at 1017 (emphasis added, footnote omitted). Thus, “it is a question whether the application necessarily discloses that particular device . . . A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997) (quoting Jepson v. Coleman, 314 F.2d 533, 536 (CCPA 1963)) (emphasis added).” slip op. at 20

  • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportDecided for petitioner

    “In addition, “[n]egative claim limitations are adequately supported when the specification describes a reason to exclude the relevant limitation. Such written description support need not rise to the level of disclaimer.” Santarus, Inc. v. Par Pharm., Inc., 694 F.3d 1344, 1351 (Fed. Cir. 2012). A reason to exclude an element may be found in “statements in the specification expressly listing the disadvantages of using” that element. Santarus, 694 F.3d at 1351. Another reason to exclude may be when the specification “distinguishes among” the element and alternatives to it. Inphi Corp. v. Netlist, Inc., 805 F.3d 1350, 1357 (Fed. Cir. 2015). As the Federal Circuit explained, “[t]he common denominator of these examples [(i.e., the reasons to exclude an element)] is disclosure of the element.” Novartis Pharm. Corp. v. Accord Healthcare, Inc., 38 F.4th 1013, 1017 (Fed. Cir. 2022). More particularly, “[s]ilence is generally not disclosure.” Novartis, 38 F.4th at 1017; see also Seabed Geosolutions (US) Inc. v. Magseis FF LLC, 8 F.4th 1285, 1288 (Fed. Cir. 2021). Accordingly, “the written description requirement cannot be met through simple disregard of the presence or absence of a limitation.” Novartis, 38 F.4th at 1017. Our reviewing court further notes that “it is possible that the written description requirement may be satisfied when a skilled artisan would understand the specification as inherently disclosing the negative limitation.” Novartis, 38 F.4th at 1017 (emphasis added, footnote omitted). Thus, “it is a question whether the application necessarily discloses that particular device . . . A description which renders obvious the invention for which an earlier filing date is sought is not sufficient.” Lockwood v. Am. Airlines, Inc., 107 F.3d 1565, 1572 (Fed. Cir. 1997) (quoting Jepson v. Coleman, 314 F.2d 533, 536 (CCPA 1963)) (emphasis added).” slip op. at 20

  Patent outcomesUS RE47,842 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
• Cisco Systems, Inc. v. Portsmouth Network Corp.No claims unpatentable
  PTAB · Aug 4, 2025 · IPR2024-00503 · APJ Charles J Boudreau · IPR · Final written decision

  Claims 1–18 were not shown unpatentable because the asserted obviousness combinations did not cure the failure to show the claimed request and routing steps.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner contends that a person of ordinary skill in the art in the field of the ’279 patent in January 2001 “would have had a working knowledge of the network communication technologies that are pertinent to the ’279 patent, including network flow allocation in a ring topology.” Pet. 12. More specifically, Petitioner argues, a person of ordinary skill in the art “would have had a master’s degree in computer science, computer engineering, or an equivalent, and two years of professional experience relating to network communications and resource allocations,” where “[a]dditional work experience can substitute for specific educational background, and vice versa.” Id. (citing Ex. 1003 ¶ 20). Patent Owner represents that it “does not dispute Petitioner’s definition” for the purposes of its Response. PO Resp. 5. We find Petitioner’s proposal is consistent with the evidence of record, including the asserted prior art and the ’279 patent, and, therefore, we likewise adopt Petitioner’s proposed definition of the level of ordinary skill in the art for purposes of this Decision.” slip op. at 11

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

    “Neither party contends that any formal claim construction is necessary. See Pet. 12 (“Petitioner submits that, for the purposes of this proceeding and the grounds presented herein, no claim term requires express construction.”); PO Resp. 4 (“Here, at this stage in the proceeding, Patent Owner will apply the ordinary and customary meaning to the ’279 Patent’s claim terms.”). Patent Owner notes, however, that Petitioner had asserted specific constructions in the Cisco litigation for the term “predetermined,” as recited in claims 1, 10, 14–16, and 18, and for the term “quantum.” PO Resp. 4. Specifically, according to Patent Owner, Petitioner proposed that “predetermined” be construed as “determined before the data flow request” and that “quantum” be construed as “an amount of a requested resource by which to increase or decrease.” Id. (citing Ex. 2007). Patent Owner contends asserted prior art combinations disclose or render obvious the challenged claims under these constructions. Id. Because our conclusion that Petitioner has not demonstrated that any of the challenged claims are unpatentable does not turn on the construction of either “predetermined” or “quantum,” there is no need for us to construe those terms. See Realtime Data, 912 F.3d at 1375.” slip op. at 12

  • Strike new argumentNew argument disregardedDecided for patent owner

    “We again are not persuaded by Petitioner’s argument. As an initial matter, we find no argument with respect to “best effort data traffic” or dropped packets in the Petition. See Tr. 12:10–21 (conceding that “the phrase ‘best effort’ was not in the Petition” but arguing that it was raised in response to the Patent Owner Response). Moreover, we are unable to identify any argument in the Patent Owner Response to which this line of argument is properly responsive, and Petitioner does not identify any such line of argument. Instead, Petitioner’s argument appears to advance belatedly a new theory. See 37 C.F.R. § 42.23(b); Patent Trial and Appeal Board Consolidated Trial Practice Guide (Nov. 2019), 73–74, available at” slip op. at 43

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedMixed

    “We credit the supporting testimony of Dr. Olivier on the points discussed above, as it is explained sufficiently and consistent with the testimony simply mirrors the Petition and does not explain sufficiently why a person of ordinary skill in the art would have understood Kovvali in the manner Petitioner asserts. See Pet. 35; Reply 17–18; Ex. 1003 ¶ 83.” slip op. at 44

  Patent outcomesUS 7,035,279 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,035,279
• Cisco Systems, Inc. v. Portsmouth Network Corp.Some claims unpatentable
  PTAB · Aug 4, 2025 · IPR2024-00505 · APJ Justin T Arbes · IPR · Final written decision

  Claims 1, 2, 4–7, 9, 10, 13, 14, 16–19, 21, and 22 are unpatentable as obvious over Gai under theory 1B; claims 11, 12, 23, and 24 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “patent, we look to “1) the types of problems encountered in the art; 2) the prior art solutions to those problems; 3) the rapidity with which innovations are made; 4) the sophistication of the technology; and 5) the educational level of active workers in the field.” Ruiz v. A.B. Chance Co., 234 F.3d 654, 666–67 (Fed. Cir. 2000). “Not all such factors may be present in every case, and one or more of them may predominate.” Id. at 667.” slip op. at 10

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

    “The most common type of MAC bridge is a switch, which has multiple ports connecting it to LANs, other switches, host computing systems, or other network elements. Switches can be roughly classified as access switches or core switches. An access switch has ports that connect to LANs and/or to other network endpoints, such as user computer systems. Core switches interconnect the access switches into a Wide Area Network (WAN), by direct connection between the core switch and access switches and/or by connection to other core switches. Core switches that are directly connected to access switches are referred to herein as edge switches. Ex. 1001, col. 1, ll. 27–38. Both parties refer to this disclosure when arguing whether particular switches in the asserted prior art (Gai) qualify as an “access switch” or “edge switch.” See Pet. 5, 22, 27–28 (“edge switches are ‘[c]ore switches that are directly connected to access switches’”), 71; PO Resp. 31–32 (“The ’986 patent discloses that ‘[a]n access switch has ports that connect to LANs and/or to other network endpoints.’ . . . The ’986 patent also discloses that edge switches are ‘[c]ore switches that are directly connected to access switches.’”); Reply 20, 22. Dr. Houh and Dr. Olivier do so as well. See Ex. 1003 ¶¶ 39, 66–67, 82–83, 166, 171, 193; Ex. 2001 ¶ 80. Based on the full trial record, we agree and conclude that the descriptions of “access switch” and “edge switch” in the ’986 patent reflect what was understood to be the plain and ordinary meanings of these terms at the time of the invention. Accordingly, we interpret “access switch” to mean a switch with ports that connect to LANs and/or to other network endpoints, such as user computer systems, and interpret “edge switch” to mean a core switch that is directly connected to an access switch.” slip op. at 12

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

    “and conclude that Petitioner has not shown sufficiently that a person of ordinary skill in the art would have been motivated to designate switch 117 as the root switch when implementing the network reconfiguration method of Gai. The only mention of an access switch connected to port 7 of switch 114 is at column 13, lines 59–63 of Gai. While that sentence establishes that such an access switch may exist in the network, it does not state or imply that it would be the root switch. Instead, when discussing the operation of the Figure 1 network, Gai only identifies switches 120 and 121 as the root switch. See Ex. 1005, col. 10, ll. 37–41, col. 11, ll. 60–64, col. 14, ll. 16–20, col. 15, ll. 27–29, 38–51, col. 16, ll. 42–45. To be sure, Gai does disclose that “execution of the spanning tree algorithm causes the switches to elect a single switch, among all the switches within each network, to be the ‘root’ switch,” where “[e]ach switch has a unique numerical identifier (switch ID) and the root is the switch having the lowest switch ID numeric value,” such that an access switch can be the root switch if it has the lowest switch ID. See Ex. 1005, col. 2, ll. 42–47, col. 10, ll. 29–36. As Patent Owner and Dr. Olivier explain in detail, though, Gai expressly cautions against doing so. Gai discloses that [d]epending on the configuration of a given network, the location of the root can significantly affect the distance that messages must travel. For example, many networks include a plurality of switches designated as access switches that provide connectivity to LANs, end stations, etc., and a plurality of backbone switches that, in turn, interconnect the various access switches. If the root is located at an access switch and the principal server utilized by the end stations (i.e., clients) is coupled to a backbone switch, the average distance between end stations and the primary server may be quite high, resulting in inefficient network operation. In addition, the backbone switches may become partitioned as ports between them are blocked. Id. at col. 3, ll. 17–29; see also id. at col. 10, ll. 26–29 (the “location of the root may affect the average distance (i.e., the average number of hops) a message travels and/or cause undesirable partitioning of backbone switches”). Thus, the location of the root is not an unimportant consideration—it affects the distance messages must travel and can cause backbone switches to be partitioned. See id. Gai, therefore, discloses that “[t]o reduce the average distance and avoid partitioning of the backbone switches, it is desirable to locate the root at a backbone switch.”10 Id. at col. 3, ll. 29–31 (emphasis added). Switch 117 in Petitioner’s modified Figure 1 is an access switch, not a backbone switch. See id. at col. 6, ll. 10–12 (“Access switches are preferably coupled to entities (e.g., LANs, end stations, etc.) whereas backbone switches provide the interconnections between access switches.”).” slip op. at 44

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

    “We agree with Petitioner. For purposes of claim 1, which does not recite “downstream” communication of dummy traffic (unlike claims 11, 12, 23, and 24), the only modification to Figure 1 is the addition of switch 117 and server 112e—otherwise, in Petitioner’s analysis, Gai’s method operates exactly as described when a failure occurs at root port 3 of switch 114. See Pet. 69–73, 81–85; Tr. 47:20–48:2. That modification is expressly supported by Gai, which discloses the following: Rapid reconfiguration entity 234 similarly generates one or more separate multicast messages 400 for each remaining entity directly coupled to access switch 114 (i.e., entities or end stations on LANs 102–104). In each message 400, entity 234 loads SA field 414 with the address of the corresponding entity. Each of these messages are similarly forwarded by access switch 114 through the new forwarding port (i.e., port number four). In addition, entity 234 generates and transmits one or more multicast messages 400 for entities reachable through switch 114 on ports other than its root port. For example, if port number seven at switch 114 were coupled to another access switch, entity 234 would transmit multicast messages 400 carrying the source address of entities directly coupled to this additional access switch as well. Thus, at least one multicast message 400 is generated and transmitted for each entity directly coupled to or downstream of access switch 114 (relative to the root). As set forth above, upon receipt of these multicast messages 400, the other devices within network 100 update their corresponding filtering databases with the new destination ports, as necessary. Ex. 1005, col. 13, l. 50–col. 14, l. 3 (emphasis added). Gai thus expressly contemplates the addition of “another access switch” coupled to port 7 of switch 114. Switch 117 in the modified Figure 1 is such a switch. See PO Resp. 30 (Patent Owner arguing that “a [person of ordinary skill in the art] would understand that switch 117 is an access switch”); Ex. 1018, 84:14–85:9 (Dr. Olivier agreeing that switch 117 is an “access switch”). And because an “access switch” has “ports that connect to LANs and/or to other network endpoints, such as user computer systems,” and the above disclosure mentions “entities directly coupled to th[e] additional access switch,” switch 117 would be directly connected to a device like server 112e as well. See Ex. 1001, col. 1, ll. 31–33; Ex. 1005, col. 13, ll. 59–63; supra Section II.B. We credit Dr. Houh’s testimony that Gai in its written description expressly discloses the particular “variation of the topology” of Figure 1 that Petitioner asserts. See Ex. 1003 ¶ 165. Third, Patent Owner argues that Petitioner has not established that a person of ordinary skill in the art “would have had a reasonable expectation of success in modifying Gai to meet the claims.” PO Resp. 14–16 (citing Ex. 2001 ¶¶ 47–49). Patent Owner’s arguments are primarily directed to Petitioner’s asserted modification for its “1A” theory. See id. To the extent Patent Owner’s arguments apply to claim 1 and “1B,” we disagree, as Gai expressly describes the asserted modification to Figure 1 (i.e., adding an access switch connected to port 7 of switch 114). Thus, we are persuaded that a person of ordinary skill in the art would have had a reasonable expectation of success in achieving the method of claim 1 based on Gai’s full disclosure.” slip op. at 33

  Patent outcomesUS 6,917,986 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,917,986
• Ceva Santé Animale S.A. / Egg-Chick Automated Technologies S.A.S et al. v. Targan, Inc.Some claims unpatentable
  PTAB · Jul 24, 2025 · IPR2024-00595 · APJ Brian P Murphy · IPR · Final written decision

  Claims 1–15 are unpatentable as obvious over the asserted §103 grounds; Petitioner did not show claims 16–18 unpatentable because the angled-conveyor combination lacked a supported rationale.

  RulingsFinal written decision

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “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, including the ’124 patent, the Gershman, Pierre, Yavnai, Tao, and Goodwin references, and the background and qualifications of both sides expert witnesses that reflect the knowledge and experience of a POSITA, including knowledge of systems for assessing and transporting poultry in an industrial setting. Patent Owner’s proposed skill level overlaps with Petitioner’s proposed skill level, and any differences would not alter the outcome of this proceeding. Therefore, we adopt Patent Owner’s proposed skill level with two modifications. A POSITA also could have a Bachelor of Science degree in Animal Science or similar discipline, and a POSITA would be familiar with techniques for assessing and transporting poultry in an industrial setting, such as visual and/or anatomical characteristics of a chick.” slip op. at 7

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

    “Therefore, we find that Applicant distinguished Tao from “an unrestrained chick” because in Tao’s automated system a chick is restrained—the chick is held in place—by a retainer unit on a moving platform, whereas in Applicant’s claimed system a chick is not held in place on a moving platform. We further conclude that Applicant’s reason for distinguishing the claimed invention over Tao informs the claim construction even if the “prosecution history statements do not rise to the level of unmistakable disavowal . . . .” Personalized Media, 952 F.3d at 1345 (Fed. Cir. 2020). In view of the ’124 patent claims, specification, and prosecution history, we determine “an unrestrained chick” is a chick not held in place on the moving platform and free to open its wings.” slip op. at 19

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

    “For the reasons given below, we find the Petition has established that Gershman discloses and teaches “a moving platform to support an unrestrained chick of a particular breed” by a preponderance of the evidence.” slip op. at 29

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

    “to determine a characteristic [of the chick] . . . [that] manifests in one of two or more possible states, e.g., sex (male vs. female), health (healthy vs. unhealthy), genetic mutation (present vs. not present).” Reply 13 (citing Ex. 1004, 3). The recitation of a generic “database of images” does not distinguish limitation [1.4] from the asserted combination of Gershman-Pierre, particularly in view of Pierre’s disclosure of “a computerized processing process is implemented in order to compare the captured images to reference images,” as asserted in the Petition. Ex. 1004, 3 (emphasis added); see Pet. 23–24 (citing Ex. 1003, 2–5; Ex. 1004, 3, 5). Thus, we find that storage of Pierre’s reference images of male and female wing feathers in a database used for comparison in Gershman’s computerized digital chick image processing system would have been obvious to a POSITA and satisfies limitation [1.4].19 We agree with Petitioner that it would have been obvious and well within the skill level of a POSITA—someone with a Bachelor of Science degree in agricultural, industrial, or electrical engineering and two years of experience in industrial poultry sexing and/or image processing (Resp. 20)—to store reference images as taught by Pierre in a “computerized processing” database. The rationale argued by Petitioner, to organize the collection of reference images for comparison to determine whether the characteristic of interest was present, finds direct support in Gershman and Pierre. Both references disclose comparing digital images of a chick’s wing feathers to reference data (Gershman) or reference images (Pierre) of male and female chick wing patterns. Pet. 23–24; Reply 12–13. Storing digital reference images in a database for comparison to captured digital images is, moreover, a basic and straightforward task in any computerized image processing” slip op. at 44

  Patent outcomesUS 10,806,124 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR
  Patents in suitUS 10,806,124
• Google LLC v. Brodti Inc.Instituted
  PTAB · Jul 24, 2025 · IPR2025-00472 · APJ Stephen E Belisle · IPR · Institution

  The Board instituted IPR of claims 1–20 on all petitioned grounds, finding a reasonable likelihood that claims 1, 10, and 19 are obvious over Nicholas, Laidlaw, Mayadas, and Error.

  RulingsInstitution decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

    “review. 35 U.S.C. § 314(b) (2024); 37 C.F.R. § 42.4(a) (2024). We may not institute an inter partes review “unless . . . there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a). The “reasonable likelihood” standard is “a higher standard than mere notice pleading” but “lower than the ‘preponderance’ standard to prevail in a final written decision.” Hulu, LLC v. Sound View Innovations, LLC, IPR2018-01039, Paper 29 at 13 (PTAB Dec. 20, 2019) (precedential). When instituting inter partes review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim. 37 C.F.R. § 42.108(a).” slip op. at 2

  • 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) (citation omitted). Considering the subject matter of the ’898 patent, the background technical field, the prior art, and Petitioner’s proposed and unopposed definition of the skilled artisan (Ex. 1002 ¶¶ 9–12), we apply the level of skill set forth above.” slip op. at 11

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

    “Petitioner submits that all terms in the Challenged Claims should be given their plain and ordinary meaning in this proceeding, and that no specific construction of any claim term is required to resolve this case. Pet. 6 (“Petitioner does not believe express claim construction is necessary to resolve this Petition.”). Patent Owner has not submitted a preliminary response, and thus does not propose any terms for construction at this stage. In determining that Petitioner has demonstrated a reasonable likelihood of establishing unpatentability of at least one Challenged Claim, we need not and do not construe expressly any claim terms. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (stating 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 12

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

    “Petitioner argues the skilled artisan would have had various rational reasons for combining the teachings of these four references, and would have had a reasonable expectation of success in doing so. See, e.g., Pet. 18–21 (discussing reasons to combine Nicholas and Laidlaw and expectation of success in doing so), 33–37 (discussing reasons to combine Nicholas and Mayadas and expectation of success in doing so), 44–45 (discussing reasons to combine Nicholas, Laidlaw, Mayadas, and Error and expectation of success in doing so). Based on the record before us, we find Petitioner sufficiently shows that the combination of Nicholas, Laidlaw, Mayadas, and Error would have taught or at least fairly suggested to the skilled artisan the limitations of claim 1.4 Thus, for the reasons stated in the Petition (Pet. 8–51), we determine that Petitioner has established a reasonable likelihood that it would prevail in showing that independent claim 1 would have been unpatentable as obvious over the combination of Nicholas, Laidlaw, Mayadas, and Error.” slip op. at 21

  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 11,416,898
• Microsoft Corporation v. X1 Discovery, Inc.Instituted
  PTAB · Jul 22, 2025 · IPR2025-00255 · APJ Charles J Boudreau · IPR · Institution

  The Board instituted IPR on claims 1–27 and all petition grounds, finding a reasonable likelihood that claims 1, 23, and 27 are obvious over Wilcox, Londergan, Raskin, and Wu.

  RulingsInstitution decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted

    “c) Summary For the reasons discussed above, Petitioner has made sufficient showings at this stage of the proceeding that the Wilcox-Londergan-Raskin- Wu combination teaches or suggests every limitation in claims 1, 23, and 27 of the ’139 patent, that one of ordinary skill in the art would have had reason to combine those teachings and suggestions to arrive at the inventions recited in claims 1, 23, and 27, and that one of ordinary skill in the art would have had a reasonable expectation of success. Accordingly, Petitioner has demonstrated a reasonable likelihood of prevailing on its challenges to claims 1, 23, and 27 based on the combination of Wilcox, Londergan, Raskin, and Wu. Accordingly, institution of an inter partes review is appropriate under 35 U.S.C. § 314(a).” slip op. at 33

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Patent Owner does not comment on Petitioner’s formulation or offer any competing formulation in its Preliminary Response. See generally Prelim. Resp. Mr. Haeberli, however, testifies as follows in his Declaration: 29. In my opinion, the POSITA at the time of the alleged invention of the Asserted Patents would have had a (1) a Bachelor’s degree in a pertinent discipline, such as computer science, electric engineering, computer engineering, or a related field and (2) have 2–4 years of experience in working with computing devices and have an understanding of indexed search systems utilized by such computing devices. 30. I am aware that Dr. Terveen has provided its own definition . . . . 31. I believe Dr. Terveen’s definition is not meaningfully different from my definition of a POSITA. My opinions would not change regardless of which definition of POSITA is applied. Ex. 2001 ¶¶ 29–31. We find Mr. Haeberli’s formulation to be consistent with the evidence of record at this stage of the proceeding, including the asserted prior art and the ’139 patent, and, accordingly, we adopt and apply that definition for purposes of this Decision. B.” slip op. at 8

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

    “missing in the prior art. Prelim. Resp. 29–34. Limitations [1.4], [23.5], and [27.4] each recite: “wherein the first and second partial search strings are separated by a string separator character in the first search field.” Ex. 1001, 29:47–49, 31:33–35, 32:29–31. Petitioner asserts that both of the Lotus Notes references teach receiving a first search string and a second search string in a single search field, separated by “a string separator character (e.g., a Boolean AND operator and/or a comma).” Pet. 25–26 (footnote omitted). We are not fully persuaded by Petitioner’s argument. In particular, the evidence does not support Petitioner’s argument that a Boolean operator such as “AND” is a string separator character. Patent Owner has pointed to intrinsic and extrinsic evidence demonstrating that a string separator character consists of just one character.17 Consequently, based on the 17 As Patent Owner argues, the intrinsic evidence does not support this interpretation of the claim language. Prelim. Resp. 31–32. “First, the ’139 patent distinguishes between string separator characters (such as space, comma, etc.) and ‘modifiers’ (such as AND, OR, NOT, etc.).” Id. at 31; compare Ex. 1001, 30:19–22 (claim 6, “string separator character”), with id. at 31:22–26 (claim 22, Boolean “modifiers”). Moreover, Patent Owner persuasively argues that “a POSITA would not understand Boolean operators such as ‘AND’ to function as string separator characters” and “would have known that the operator AND is a search syntax instruction rather than a string separator.” Prelim. Resp. 31 (citing Ex. 1059, 162; Ex. 2001 ¶ 110). Even Petitioner acknowledges in a footnote that it may not be appropriate to include the Boolean AND operator in the definition of “string separator character.” Petitioner argues:” slip op. at 28

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

    “one of ordinary skill in the art would have considered “reverting some of the changes that had been made to Lotus Notes R5’s ‘Search Builder’ to make it more similar to Lotus Notes earlier 3.0’s ‘Query Builder.’” Prelim. Resp. 16. The issue, however, is not whether “over the years Lotus Notes moved away from a unified search field[,]” as Patent Owner suggests. Id. at 14. The issue is what “inferences and creative steps” a person of ordinary skill in the art would have employed, based on Wilcox and Londergan, when designing a new method and system for search indexing. KSR, 550 U.S. at 418. Petitioner’s argument is that one of ordinary skill in the art would have been motivated to consider Wilcox and Londergan together in order to “obtain a more complete and comprehensive understanding of the Lotus Notes system,” which in turn would have inspired certain inferences and creative steps that would have resulted in the portions of the claimed invention allegedly disclosed in Wilcox and/or Londergan. Pet. 22. We do not agree with Patent Owner that this argument can only be the result of improper hindsight bias. See Prelim. Resp. 16–17. At this stage of the proceedings and based on the current record, we determine that Petitioner has sufficiently shown that a POSITA would have been motivated to combine Wilcox and Londergan.” slip op. at 20

  Claim construction§ 103 obviousnesscites Phillips · KSR
  Patents in suitUS 9,633,139

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.