PTAB
Advanced fields
2 decisions · 372msnewest first
  • PTAB · Oct 12, 2018 · IPR2016-01828 · APJ Kevin C Trock · IPR · Rehearing

    Rehearing was granted in part: review was instituted on all challenged claims and grounds, but claims 16 and 28 were not shown unpatentable because their scope could not be determined without speculation.

    RulingsRehearing decision
    • RehearingRehearing, grantedGranted in part

      “For the reasons explained below, we grant Patent Owner’s request for rehearing to the extent we (1) modify our Institution Decision to institute on all of the challenged claims, including claims 16 and 28, and all of the grounds presented in the Petition, including Ground 2; and (2) modify our Final Written Decision to include a determination with respect to claims 16 and 28. We deny, however, Patent Owner’s request for rehearing to the extent we decline to read claims 16 and 28 on the prior art.” slip op. at 2

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

      “In SAS, the Supreme Court held that a decision to institute under 35 U.S.C. § 314 may not institute on less than all claims challenged in the petition. SAS Inst., Inc., 1348 at 1359–60. In our Institution Decision, we determined that Petitioner demonstrated a reasonable likelihood that it would establish that at least one of the challenged claims of the U.S. Patent No. 8,650,591 B2 is unpatentable. Inst. Dec. 23. Because of the Supreme Court’s ruling in SAS, we now modify our Institution Decision to institute on all of the challenged claims, including claims 16 and 28, and on all of the grounds presented in the Petition, including Ground 2, and we determine, in this Decision on Patent Owner’s Motion for Rehearing, whether claims 16 and 28 have been shown, by a preponderance of the evidence, to be unpatentable.” slip op. at 4

    • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

      “If our unpatentability analysis requires “considerable speculation as to the meaning and assumptions as to the scope” of the claims, In re Steele, 305 F.2d 859, 862 (CCPA 1962), the differences between the claimed invention and the prior art cannot be ascertained. See id.; see also BlackBerry Corp. v. MobileMedia Ideas, LLC, Case IPR2013-00036, slip op. at 19–20 (PTAB Mar. 7, 2014) (Paper 65) (citing Steele, 305 F.2d at 862–63 for the proposition that “the prior art grounds of unpatentability must fall, pro forma, because they are based on speculative assumption[s] as to the meaning of the claims” and reasoning that “an obviousness determination based on less than all of the claimed elements is speculative as to the meaning or scope of the claims”). In other words, “[w]ithout ascertaining the proper claim scope, we cannot conduct a necessary factual inquiry for determining obviousness—ascertaining differences between the claimed subject matter and the prior art.” Id. at 20 (citing Graham v. John Deere Co., 383 U.S. 1, 17–18 (1966)).” slip op. at 6

    • Prior constructionPrior construction adoptedDecided for patent owner

      “least one partition of said at least one secondary storage device through said secondary storage partitions window,” “means for manipulating said at least one cabinet record through said cabinet visible partition window,” and “means for modifying said at least one cabinet record through said cabinet visible partition window.” Ex. 101, 9:66–10:25. In related litigation, the district court found in its claim construction opinion that the ’400 patent does not provide structure corresponding clearly to the functions of these limitations. Ex. 1010, 49–61. We have reviewed and considered the district court’s analysis and findings and we concur with the district court’s conclusion. We are unable to discern structure in the ’400 patent that corresponds clearly to the functions recited in the “means for” limitations of claim 16. Claim 28 recites similarly “program code for configuring said at least one partition of said at least one secondary storage device through a secondary storage partitions window,” “program code for manipulating said virtual cabinet record through said cabinet visible partition window,” and “program code for means for modifying said at least one cabinet record through said cabinet visible partition window.” Ex. 1001, 10:65–11:29. The district court also found that the ’400 patent did not provide structure corresponding clearly to the function of these limitations. Ex. 1010, 49–61. We have reviewed and considered the district court’s analysis and findings and we concur with the district court’s conclusion. We are unable to discern structure in the ’400 patent that corresponds clearly to the functions recited in the “program code for” limitations of claim 28.” slip op. at 5

    Claim construction§ 103 obviousnesscites Graham
    Patents in suitUS 6,690,400
  • PTAB · Jul 1, 2016 · IPR2016-00326 · APJ Kevin W Cherry · IPR · Rehearing

    On rehearing, the Board instituted IPR on claims 1, 2, and 13 based on anticipation by Anderl and obviousness over Anderl or Anderl and Hendry.

    RulingsRehearing decision
    • RehearingRehearing, grantedGranted

      “On June 17, 2016, Patent Owner filed a Request for Rehearing (Paper 13, “Request” or “Reh’g Req.”) of our Decision to Institute (Paper 10, “Decision”) an inter partes review in this case. We have reviewed Patent Owner’s Request, and we agree that we overlooked the matters identified in the Request. See Reh’g Req. 2–4. Thus, for the reasons stated in the Request, we grant Patent Owner’s Request for Rehearing. On rehearing, we withdraw our previous Decision and reconsider our Decision in light of the full record, as Patent Owner requests. Id. at 4. Pursuant to this reconsideration, we issue the instant Amended Decision to Institute.” slip op. at 2

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

      “determine that the information presented shows there is a reasonable likelihood that Petitioner would prevail in establishing the unpatentability of at least one of claims 1, 2, and 13 (“the challenged claims”) of the ’537 patent.” slip op. at 2

    • BurdenOther

      “limitation, we are persuaded that Petitioner has shown adequately that Anderl discloses “said appended information featuring said at least one associated type of permission for accessing the stored data,” as recited in claim 1. Patent Owner focuses narrowly on the value of the data included in protection bytes 43 to 45 of Anderl. See Prelim. Resp. 13–15. Yet the claim does not focus only on the data alone, but instead recites “appended information.” As the Petition explains, Anderl discloses that the information is appended based on location in file as the value at the particular location. See Pet. 23–24. In particular, Anderl discloses that each file includes prefix section 41 that is located in the first record of each file and contains file identification number 42 and protection bytes 43, 44, and 45. Ex. 1005, 6:57–60. Anderl states that “[t]he protection bytes 43 through 45 specify the file permissions.” Id. at 6:65–66 (emphasis added). As Anderl discloses,” slip op. at 20

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

      “not persuaded that “type of permission” is limited to only the type of action that can be performed, e.g., reading or writing, with respect to the data. Instead, the Specification repeatedly refers to the “types of permissions” as “for determining access to the stored data, such that if an attempt is made to access particular data which does not have a suitable permission type, access is denied.” See, e.g., Ex. 1001, Abstract (“The device, method and system enable various types of permissions to be set for determining access to the stored data, such that if an attempt is made to access particular data which does not have a suitable permission type, access is denied.”); 2:32–36 (“The present invention enables various types of permissions to be set for determining access to the stored data, such that if an attempt is made to access particular data which does not have a suitable permission type, access is denied.”); 3:4:26–30 (same). Given this broader usage in the Specification, for purposes of this decision, the “type of permission” is for determining access to the stored data, such that if an attempt is made to access particular data that does not have a suitable permission type, access is denied. The access, if not denied, may include reading from or writing to the stored data. As for “featuring,” we are not persuaded that “featuring,” as used in claim 1 of the ’537 patent is synonymous with “represent,” as Patent Owner contends. A relevant meaning of “featuring” is “to be an important part or aspect of something.” See Ex. 3001. This meaning only requires that the thing that is featured be an important part or aspect, not that it correspond to or represent the thing. Patent Owner does not point us to any disclaimer or definition that would limit this meaning. See Prelim. Resp. 13–15. Instead, the Specification appears to use the related term “feature” in this ordinary sense. See, e.g., Ex. 1001, 4:54–56 (“As another option, the device may feature a single chip with a microprocessor and firmware for operating the data access features ….”); 5:25– 27 (“A system 10 features a CPU 12 for executing instructions….”); 8:15–19 (“For example, an access control code could be implemented with a combination of different types of data, each of which could again feature a separately selected and assigned data access permission, which optionally and preferably is different for each portion of the data.”). Moreover, the portion of Specification cited by Patent Owner (Prelim. Resp. 12–13 (citing Ex. 1001, 6:34–61)) makes clear that it only refers to a preferred embodiment and the permissions do not need to be stored as a “code,” i.e., specific information or data representing the permission. See id. at 6:35–36 (“According to preferred embodiments…”), 6:43–47 (“If such a permission is to be stored in an abbreviated code, the code for this particular type of permission could be given as ‘R/W/WP’, for example. Such a code could optionally be stored in the non-volatile 16, for example.” (emphases added)). Such optional language is not sufficient to limit the claimed “appended information” to only something that “represents” the permission, such as a code. See Prolitec Inc. v. Scentair Techs., Inc., 807 F.3d 1353, 1358 (Fed. Cir. 2015) (“[T]he use of ‘may’ signifies that the inventors did not intend to limit [the claim]. . . .”); Ancora Techs., Inc. v. Apple, Inc., 744 F.3d 732, 735 (Fed. Cir. 2014) (noting that non-limiting examples are not sufficient to redefine a term).” slip op. at 8

    Claim construction§ 102 anticipation§ 103 obviousness
    Patents in suitUS 6,324,537

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.