PTAB
Advanced fields
2 decisions · 310msnewest first
  • PTAB · Aug 13, 2025 · IPR2024-01469 · APJ Steven M Amundson · IPR · Final written decision

    Claims 1–7, 9–15, and 18–20 are unpatentable; claims 8, 16, and 17 are not determined unpatentable under the asserted prior-art grounds.

    RulingsFinal written decision
    • PTAB / AIA Trials › §315(b) time barNot time barredDecided for petitioner

      “G. Analysis 1. REAL PARTY IN INTEREST Based on the record before us and for the reasons explained below, we disagree with Patent Owner that Menard is a “real party in interest” under § 315(b). See Resp. 77–82; Sur-reply 27–28. First, the circumstances here differ materially from the circumstances in Ventex. There, two agreements defined the relationship between Ventex (the petitioner and manufacturer of Heatwave fabric) and Seirus (the alleged real party in interest and purchaser of Heatwave fabric). Ventex, IPR2017- 00651, Paper 152 at 7 & n.8. First, a 2013 Supplier Agreement “prevented Ventex from selling to Seirus competitors” and included an indemnity provision requiring Ventex to indemnify Seirus for losses arising from Ventex’s failure to perform certain obligations. Id. at 7, 14. Second, a 2016 Exclusive Manufacturing Agreement provided that Ventex would manufacture the Heatwave fabric only for Seirus in exchange for Seirus’s payment of an exclusivity fee. Id. at 7. Columbia (the patent owner) accused Seirus products incorporating the Heatwave fabric of infringing the patent at issue, and Columbia served Seirus with a complaint alleging patent infringement in 2014 more than two years before Ventex filed a petition in 2017. Id. at 5, 7. When determining that Seirus was a “real party in interest” under § 315(b), the Board reasoned that “Ventex and Seirus had a specially structured, preexisting, and well established business relationship with one another, including indemnification and exclusivity arrangements.” Ventex, IPR2017-00651, Paper 152 at 10; see id. at 12. Additionally, the Board noted that certain evidence “suggest[ed] that” slip op. at 32

    • PTAB / AIA Trials › Real party in interest / privityRpi dispute resolved for petitionerDecided for petitioner

      “G. Analysis 1. REAL PARTY IN INTEREST Based on the record before us and for the reasons explained below, we disagree with Patent Owner that Menard is a “real party in interest” under § 315(b). See Resp. 77–82; Sur-reply 27–28. First, the circumstances here differ materially from the circumstances in Ventex. There, two agreements defined the relationship between Ventex (the petitioner and manufacturer of Heatwave fabric) and Seirus (the alleged real party in interest and purchaser of Heatwave fabric). Ventex, IPR2017- 00651, Paper 152 at 7 & n.8. First, a 2013 Supplier Agreement “prevented Ventex from selling to Seirus competitors” and included an indemnity provision requiring Ventex to indemnify Seirus for losses arising from Ventex’s failure to perform certain obligations. Id. at 7, 14. Second, a 2016 Exclusive Manufacturing Agreement provided that Ventex would manufacture the Heatwave fabric only for Seirus in exchange for Seirus’s payment of an exclusivity fee. Id. at 7. Columbia (the patent owner) accused Seirus products incorporating the Heatwave fabric of infringing the patent at issue, and Columbia served Seirus with a complaint alleging patent infringement in 2014 more than two years before Ventex filed a petition in 2017. Id. at 5, 7. When determining that Seirus was a “real party in interest” under § 315(b), the Board reasoned that “Ventex and Seirus had a specially structured, preexisting, and well established business relationship with one another, including indemnification and exclusivity arrangements.” Ventex, IPR2017-00651, Paper 152 at 10; see id. at 12. Additionally, the Board noted that certain evidence “suggest[ed] that” slip op. at 32

    • Skill levelOther

      “C. Level of Ordinary Skill in the Art Factors pertinent to determining the level of ordinary skill in the art include (1) the educational level of the inventor; (2) the type of problems encountered in the art; (3) prior-art solutions to those problems; (4) the rapidity with which innovations are made; (5) the sophistication of the technology; and (6) the educational level of workers active in the field. Envtl. Designs, Ltd. v. Union Oil Co., 713 F.2d 693, 696–97 (Fed. Cir. 1983). Not all factors may exist in every case, and one or more of these or other factors may predominate in a particular case. Id. These factors are not exhaustive, but 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). Moreover, the prior art itself may reflect an appropriate skill level. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). Petitioner asserts that a person of ordinary skill in the art at the ’336 patent’s effective filing date would have had “a bachelor’s degree in mechanical engineering, electrical engineering, optics, or physics with at least three years of experience working in the design of LED lights or lighting fixtures; a master’s degree in one of the above disciplines with at least two years of experience; or equivalent experience.” Pet. 14 (citing Ex. 1004 ¶¶ 26–29). Dr. Eden’s testimony supports Petitioner’s assertion. See Ex. 1004 ¶¶ 27–28. Patent Owner “adopts for purposes of this proceeding only” Petitioner’s description of an ordinarily skilled artisan. Resp. 10 (citing Pet. 14). We adopt Petitioner’s description of an ordinarily skilled artisan because it comports with the technology and claims of the ’336 patent as” slip op. at 40

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

      “Alleged Objective Indicia of Nonobviousness (i) General Principles Before reaching a conclusion about obviousness, we consider evidence concerning objective indicia of nonobviousness. See Apple, 839 F.3d at 1048. For such evidence to have substantial weight, “its proponent must establish a nexus between the evidence and the merits of the claimed invention.” ClassCo, Inc. v. Apple, Inc., 838 F.3d 1214, 1220 (Fed. Cir. 2016); see Ancora Techs., Inc. v. Roku, Inc., 140 F.4th 1351, 1361 (Fed. Cir. 2025) (noting that the Board did not err by requiring “a nexus to the challenged claims as opposed to the patent as a whole”). “[T]here is no nexus unless the evidence presented is ‘reasonably commensurate with the scope of the claims.’” ClassCo, 838 F.3d at 1220 (quoting Rambus Inc. v. Rea, 731 F.3d 1248, 1257 (Fed. Cir. 2013)). The patentee “bears the burden of showing that a nexus exists.” WMS Gaming, Inc. v. Int’l Game Tech., 184 F.3d 1339, 1359 (Fed. Cir. 1999). A rebuttable presumption of nexus arises “when the patentee shows that the asserted objective evidence is tied to a specific product and that product ‘embodies the claimed features, and is coextensive with them.’” Fox Factory, Inc. v. SRAM, LLC, 944 F.3d 1366, 1373 (Fed. Cir. 2019) (quoting Polaris Indus., Inc. v. Arctic Cat, Inc., 882 F.3d 1056, 1072 (Fed. Cir. 2018)). Whether a rebuttable presumption of nexus arises “turns on the nature of the claims and the specific facts.” Teva Pharms. Int’l GmbH v. Eli Lilly & Co., 8 F.4th 1349, 1362 (Fed. Cir. 2021). The presumption analysis should consider the unclaimed features in the product tied to the objective evidence to assess their significance and impact on the correspondence between the patented invention and the product. Quanergy Sys., Inc. v. Velodyne Lidar USA, Inc., 24 F.4th 1406, 1418 (Fed. Cir. 2022). When, “for example, the patented invention is only a small component of the product tied to the objective evidence, there is no presumption of nexus.” Henny Penny Corp. v. Frymaster LLC, 938 F.3d 1324, 1333 (Fed. Cir. 2019). Absent a presumption of nexus, the patentee may prove nexus by” slip op. at 76

    Patent outcomesUS 10,299,336 mixed
    § 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
    Patents in suitUS 10,299,336
  • Microsoft Corporation v. Enfish, LLCSome claims unpatentable
    PTAB · Mar 2, 2015 · IPR2013-00560 · APJ Barbara A Parvis · IPR · Final written decision

    Claims 47–48 are unpatentable as anticipated by Visual Basic, and claims 49–50 as obvious over Visual Basic and Jensen; claims 51–53 were not shown unpatentable, and claims 17–23 were terminated.

    RulingsFinal written decision
    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownNo construction neededDecided for patent owner

      “Enfish contends that our construction for “object identification number” is incomplete. PO Resp. 15. We evaluate Enfish’s contention below. Enfish also provides a proposed construction for “anchor,” recited in claims 21 and 51. PO Resp. 22. Because we determine that Microsoft has not met its burden with respect to these claims for other reasons, no construction of this term for the purposes of this Decision is necessary. We discern no reason, based on the complete record now before us, to change our constructions in the Decision to Institute of “logical table,” “object identification number,” and “attribute set.”” slip op. at 8

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

      “evidence, and the detailed claim analysis, which reads persuasively all elements of claim 47 onto the disclosure of Visual Basic. Pet. 33–46 (citing Ex. 1104, LR 162, 185, 280, 425, 484, 532, 558, PF 1, 3, 18, 37–39, 40, 47, 76, 80, PG 453, 471, 481, 482 ; Ex. 1119 ¶¶ 67–98). For example, we are persuaded that Microsoft has shown by a preponderance of the evidence that Visual Basic discloses configuring memory according to a logical table, as recited in claim 47. In the cited portions above, Visual Basic discloses storing data in a computer formatted as a table object, which is “a logical representation of a physical table.” Ex. 1104, LR 558. The table object comprises “records (rows) and fields (columns).” Id.” slip op. at 16

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

      “2007 ¶ 231. In contrast to Dr. Jagadish’s statement, however, Jensen teaches an object-oriented application for managing information retrieved from a structured database, such as a relational database. Ex. 1106, Abstract. Enfish further contends that Microsoft does not explain why one of ordinary skill in the art would have been motivated to apply the pointers of Jensen to the indexing structure in Visual Basic. PO Resp. 35. We, however, are persuaded that Microsoft has shown a sufficiently articulated reason with rational underpinning to support obviousness (Pet. 48–49 (citing Ex. 1119 ¶¶ 387–404)). Microsoft, for example, states “[i]t was well known in the art at the time that indexes such as the index disclosed in [Visual Basic], maintain object identification numbers of the cell for locating data.” Pet. 49 (emphasis added). Microsoft continues, “Jensen discloses containing the address in a pointer, e.g., a physical memory address (i.e., OIDs).” Id. (citing Ex. 1106, 7:29–35). Dr. Hosking testifies “[i]t was well known in the art at the time that Index Objects locate data by maintaining object identification numbers in the internal pointers as disclosed in Jensen.” Ex. 1119 ¶ 403 (emphasis added). Dr. Hosking further testifies “[a] person of ordinary skill in the art would be motivated to combine Jensen’s teaching of maintaining the OIDs in a pointer with [Visual Basic’s] disclosure of identifying the logical columns / rows with the OIDs.” Ex. 1119 ¶ 404. The predictable use of familiar prior art elements according to their established functions renders the recited invention obvious. See KSR Int’l Co. v. Teleflex, Inc., 550 U.S. 398, 417 (2007).” slip op. at 19

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

      “invention, the totality of the evidence submitted, including objective evidence of nonobviousness, may lead to a conclusion that the claimed invention would not have been obvious to one with ordinary skill in the art. In re Piasecki, 745 F.2d 1468, 1471–72 (Fed. Cir. 1984). However, to accord substantial weight to objective evidence requires the finding of a nexus between the evidence and the merits of the claimed invention. In re GPAC Inc., 57 F.3d 1573, 1580 (Fed. Cir. 1995); see also In re Huang, 100 F.3d 135, 140 (Fed. Cir. 1996) (“success is relevant in the obviousness context only if there is proof that the sales were a direct result of the unique characteristics of the claimed invention.”). Enfish contends that the claimed invention received industry accolades, including praise from Microsoft, satisfied a long-felt need, resulted in success where others had failed, as well as commercial success. PO Resp. 42–47. Enfish points to features of claim 17, which Enfish contends are the features of the claimed invention that resulted in the objective indicia of success to which Enfish refers. Id. at 43–44. Claim 17 of the ’775 patent, however, is challenged on the basis that it is anticipated by Visual Basic. Secondary considerations do not weigh into determinations regarding anticipation. Cohesive Techs., Inc. v. Waters Corp., 543 F.3d 1351, 1364 (Fed. Cir. 2008). Because we conclude that Microsoft has not shown that claims 51–53 of the ’775 patent are unpatentable for other reasons, the only claims that we need to evaluate are dependent claims 49 and 50 of the ’775 patent. Microsoft asserts that claims 49 and 50 are obvious over the combination of Visual Basic with a reference that teaches referencing objects through two-way pointers. Pet. 49 (citing Ex. 1106, 7:29–35). Enfish has not shown a nexus between any of the accolades or successes it says occurred and the use of two-way pointers.” slip op. at 24

    Patent outcomesUS 6,163,775 mixed
    Claim construction§ 102 anticipation§ 103 obviousnesscites KSR
    Patents in suitUS 6,163,775

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.