PTAB
Advanced fields
2 decisions · 417msnewest first
  • 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
  • PTAB · Jul 15, 2015 · CBM2014-00060 · APJ Bart A Gerstenblith · CBM · Final written decision

    Claims 1–28 are unpatentable for lack of adequate written description under § 112, first paragraph.

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

      “that “hyperlink” is a well-understood term that the ’022 patent uses in accordance with its ordinary meaning. As explained above, the Microsoft Computer User’s Dictionary makes clear that a hyperlink includes a connection to another element or document. Patent Owner points to no persuasive evidence that the ’022 patent describes a hyperlink as separate from this connection such that the connection can be changed with the hyperlink remaining the same. Indeed, the ’022 patent describes “replac[ing] all links in the translated web page 7 with links that point to the translation manager 4” as part of the translation process. Ex. 1001, 3:37–38. Thus, as described in the patent, changing the connection to point to the translation manager requires a new link. This is consistent with the ordinary meaning of a hyperlink as including a specific connection from one document to another element or document. Our preliminary construction of “hyperlink” included “a link or connection” but did not include a recitation of the element or document linked. To resolve the parties’ dispute, consistent with the ordinary meaning and the specification, we conclude, on the full record before us, that one of ordinary skill in the art at the time of the invention would have understood “hyperlink” to mean “a connection between an element in a hypertext document, such as a word, phrase, symbol, or image, and a different element in the document, another hypertext document, a file, or a script.”” slip op. at 10

    • ExcludeMotion to exclude, deniedDenied

      “First, the inter partes reexamination of the ’022 patent is relevant to our consideration of the claim construction issues presented here because claim construction was at issue in the reexamination. Second, we see no risk of undue prejudice that would outweigh the probative value of the documents and evidence submitted in the reexamination. Of note, is that this proceeding is not a jury trial and, thus, the risk of prejudice in this forum is less than what may otherwise exist before a jury. Third, we agree with Petitioner that Exhibit 1013 is not hearsay at least under Federal Rule of Evidence 801(d)(2)(B) because the testimony in Dr. Nakhimovsky’s Declaration was submitted by, and on behalf of, Patent Owner to the Patent Office, thus evidencing that Patent Owner manifested a belief that the statements contained therein were true. Accordingly, Patent Owner’s Motion to Exclude as applied to Exhibit 1013 is denied.” slip op. at 22

    • Disclosure Requirements (§112) › Written description (Ariad)Written description inadequateUnpatentable

      “Patent Owner’s first argument is contrary to our constructions of the term “hyperlink” and the phrase “said hyperlink.” As reflected in our construction, “said hyperlink” in each of independent claims 1, 17, and 26, refers back to the original recitation of “one or more hyperlinks” in the original (untranslated) electronic communication. The portion of the specification relied upon by Patent Owner does not disclose providing translation of said further electronic communications when the original one or more hyperlink is activated. Rather, this disclosure indicates that the translation manager may replace all of the links (i.e., hyperlinks) in the translated web page with links that point to the translation manager. These replaced links are in the translated electronic communication (e.g., web page 7), and not in the original untranslated electronic communication (e.g., web page 2). Thus, this disclosure does not reasonably convey to one of ordinary skill in the art that the inventors had possession of a translation manager that provides translation of further electronic communications when the one or more hyperlinks in the original untranslated electronic communication is activated (i.e., one or more hyperlinks with unmodified destination addresses). See Ariad Pharm., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc).” slip op. at 25

    • Disclosure Requirements (§112) › Definiteness (Nautilus)Not reached

      “E. Indefiniteness of Claims 23 and 25–28 Under 35 U.S.C. § 112, Second Paragraph Our determination that each challenged claim is unpatentable for lack of an adequate written description renders it unnecessary to reach Petitioner’s contentions that claims 23 and 25–28 of the ’022 patent are indefinite.” slip op. at 31

    Patent outcomesUS 6,857,022 unpatentable
    Claim construction§ 112 disclosurecites Phillips
    Patents in suitUS 6,857,022

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.