PTAB
Advanced fields
14 decisions · 358msnewest first
  • PTAB · Mar 20, 2015 · CBM2014-00013 · APJ Meredith C Petravick · CBM · Final written decision

    Claims 1, 2, 4, 5, 10, and 12 are unpatentable under § 101; claims 3, 6–9, 11, and 13–16 were not shown unpatentable because the petition did not establish their claimed features were conventional.

    RulingsFinal written decision
    • BurdenMixed

      “We are persuaded by Patent Owner’s argument. Petitioner states that the claimed linking is a “classic example[] of manual tasks that cannot be rendered patent-eligible merely by performing them with a computer.” Reply 15. However, Petitioner fails to provide sufficient evidence to support its statement. See Pet. 49–66; Reply 9–15. Petitioner provides insufficient evidence to establish that a menu having the functionality to perform the claimed linking from a GUI on a hand-held device, was well-known or conventional and merely require a general purpose computer. See id. Upon review, we determine that Petitioner fails to establish by a preponderance of the evidence that claims 3 and 11 recite patent-ineligible subject matter.” slip op. at 37

    • Skill levelOther

      “B. Claim Construction The Board interprets claims of unexpired patents using the broadest reasonable construction in light of the specification of the patent in which they appear. 37 C.F.R. § 42.300(b). Under the broadest reasonable construction standard, claim terms are given their ordinary and customary meaning, as would be understood by one of ordinary skill in the art in the context of the entire disclosure. In re Translogic Tech., Inc., 504 F.3d 1249, 1257 (Fed. Cir. 2007). Any special definition for a claim term must be set forth with reasonable clarity, deliberateness, and precision. In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir. 1994). In the absence of such a definition, limitations are not to be read from the specification into the claims. In re Van Geuns, 988 F.2d 1181, 1184 (Fed. Cir. 1993). Prior to construing the relevant claim limitations, we turn to some initial matters raised by Patent Owner. First, Patent Owner argues that we must construe “the entirety of the challenged claims” (PO Resp. 31), and proposes constructions for some, but not all, limitations of the challenged claims (see id. at 34–36). Claim construction, however, “is not an inviolable prerequisite to a validity determination under § 101.” Bancorp Servs. L.L.C. v. Sun Life Assur. Co. of Canada (U.S.), L.L.C., 687 F.3d 1266, 1273 (Fed. Cir. 2012). See, e.g., Vivid Techs., Inc. v. Am. Sci. & Eng'g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (only those terms that are in controversy need to be construed, and only to the extent necessary to resolve the controversy). Below, we construe the limitations that are relevant to the issues of patent-eligibility discussed below. We determine that all other claim limitations need no explicit construction.” slip op. at 8

    • Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notPreamble not limitingDecided for petitioner

      “In general, a preamble limits the invention if it recites essential structure or steps, or if it is ‘necessary to give life, meaning, and vitality’ to the claim.” Catalina Mktg. Int'l, Inc. v. Coolsavings.com, Inc., 289 F.3d 801, 808 (Fed. Cir. 2002) (citing Pitney Bowes Inc. v. Hewlett-Packard Co., 182 F.3d 1298, 1305 (Fed. Cir. 1999)). A preamble, however, is not limiting where the claim body defines a structurally complete invention and the preamble only states a purpose or intended use for the invention. Id. slip op. at 11

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

      “We are persuaded by Petitioner that the broadest reasonable construction in light of the Specification of the term CPU is the computational and control unit of a computer. Petitioner’s construction is consistent with the Specification, which describes that the system of the ’733 patent uses typical hardware elements in the form of a computer workstation and that “a typical workstation platform includes hardware such as a central processing unit (‘CPU’), e.g., a Pentium® microprocessor.” Ex. 1033, col. 6, ll. 52–54; see also id. at col. 6, l. 65 (“a CPU, e.g., Pentium® microprocessor”). Further, Petitioner’s construction is consistent with the Specification, which as discussed above, discloses using a desktop PC to generate and download menus to a connected handheld device (see id. at col. 7, l. 38–col. 10, l. 15), as well as, discloses the use of a central back-office server (e.g., see id. at col. 2, ll. 37–40). Patent Owner’s proposed construction improperly reads into the claims the central back-office server. See Renishaw, 158 F.3d at 1249 (explaining that extraneous features should not be read into the claims). For these reasons, we determine that the broadest reasonable construction, in light of the Specification, of CPU is the computational and control unit of a computer.” slip op. at 15

    Patent outcomesUS 6,982,733 mixed
    Claim construction§ 101 eligibilitycites Alice · Mayo
    Patents in suitUS 6,982,733
  • PTAB · Mar 20, 2015 · CBM2014-00016 · APJ Meredith C Petravick · CBM · Final written decision

    Claims 1–10 are unpatentable under § 101 because they claim the abstract idea of generating a criteria-based menu and transmitting it using conventional computer elements.

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

      “Petition (Paper 8, “Pet.”) requesting review under the transitional program for covered business method patent of claims 1–15 of U.S. Patent No. 6,871,325 B1 (Ex. 1032, “the ’325 patent”). On March 26, 2014, pursuant to 35 U.S.C. § 324, we instituted this trial as to claims 1–10 of the ’325 patent on only one proposed ground of unpatentability, 35 U.S.C. § 101. Paper 19 (“Dec. to Inst.”). We did not institute as to claims 11–16 on any of the grounds proposed in the Petition. Ameranth, Inc. (“Patent Owner”) filed a Patent Owner Response (Paper 26, “PO Resp.”) and Petitioner filed a Reply (Paper 27, “Reply”).” slip op. at 2

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

      “Prior to construing the relevant claim limitations, we turn to some initial matters raised by Patent Owner. First, Patent Owner argues that we must construe “the entirety of the challenged claims” (PO Resp. 30), and proposes constructions for some, but not all, limitations of the challenged claims (see id. at 33–35). Claim construction, however, “is not an inviolable prerequisite to a validity determination under § 101.” Bancorp Servs. L.L.C. v. Sun Life Assur. Co. of Canada (U.S.), L.L.C., 687 F.3d 1266, 1273 (Fed. Cir. 2012). See, e.g., Vivid Techs., Inc. v. Am. Sci. & Eng'g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (only those terms that are in controversy need to be construed, and only to the extent necessary to resolve the controversy). We construe, below, the limitations that are relevant to the issues of patenteligibility discussed below. We determine that all other claim limitations need no explicit construction.” slip op. at 9

    • Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notPreamble not limitingDecided for petitioner
    • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner

      “We are persuaded by Petitioner that the broadest reasonable construction in light of the Specification of the term CPU is the computational and control unit of a computer. Petitioner’s construction is consistent with the Specification, which describes that the system of the ’325 patent uses typical hardware elements in the form of a computer workstation and that “[a] typical workstation platform includes hardware such as a central processing unit (‘CPU’), e.g., a Pentium® microprocessor.” Ex. 1032, col. 5, ll. 43–45; see also id. at col. 5, ll. 54–56 (“a CPU, e.g., Pentium® microprocessor”). Further the Specification discloses using a desktop PC to generate and download menus to a connected handheld device (see id. at col. 6, l. 33–col. 9, l. 3), as well as, discloses the use of a central back-office server (e.g., see id. at col. 2, ll. 31–37). Patent Owner’s proposed construction improperly reads into the claims the central back-office server. See Renishaw, 158 F.3d at 1249 (explaining that extraneous features should not be read into the claims). For these reasons, we determine that the broadest reasonable construction, in light of the Specification, of CPU is the computational and control unit of a computer.” slip op. at 15

    Patent outcomesUS 6,871,325 unpatentable
    Claim construction§ 101 eligibilitycites Alice · Mayo · Bilski
    Patents in suitUS 6,871,325
  • Agilysys, Inc. v. Ameranth, Inc.All claims unpatentable
    PTAB · Mar 20, 2015 · CBM2014-00015 · APJ Meredith C Petravick · CBM · Final written decision

    Claims 1–11 are unpatentable under § 101 because they claim the abstract idea of generating and transmitting menus using only generic computer elements and conventional activity.

    RulingsFinal written decision
    • Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notPreamble not limitingDecided for petitioner

      “In general, a preamble limits the invention if it recites essential structure or steps, or if it is ‘necessary to give life, meaning, and vitality’ to the claim.” Catalina Mktg. Int’l, Inc. v. Coolsavings.com, Inc., 289 F.3d 801, 808 (Fed. Cir. 2002) (citing Pitney Bowes Inc. v. Hewlett-Packard Co., 182 F.3d 1298, 1305 (Fed. Cir. 1999)). A preamble, however, is not limiting where the claim body defines a structurally complete invention and the preamble only states a purpose or intended use for the invention. Id. The body of claim 1 recites a system that includes a central processing unit (“CPU”), a data storage device, an operating system with a GUI, a first menu, a modifier menu, a sub-modifier menu, and application software. Ex. 1031, col. 14, l. 48–col. 15, l. 11. The application software is recited as “for generating a second menu from said first menu” and the wherein clause further defines how the second menu is generated from the first menu. Id. at col. 15, ll. 1–11. The application software is recited, further, as “for . . . transmitting said second menu to a wireless handheld computing device or Web page.” Id. at col. 15, l. 1–2. As can be seen from the above, the body of claim 1 recites a structurally complete invention; one that corresponds to the embodiment that has a desktop PC and a menu configuration application described in the Specification at column 6, line 9 thru column 8, line 62 and depicted in Figure 1. See also Ex. 1031, col. 3, ll. 35–41 (describing the present invention as a software tool for building a menu, modifying a menu, and downloading it to a handheld device or Web Page). As described in the Specification, a menu is updated using the GUI of the menu configuration application and, then, the updated menu is downloaded to a connected handheld device by clicking on a “Download Database” item or icon in GUI 1. Ex. 1031, col. 8, ll. 45–62; see also id. at col. 3, ll. 35–37; col. 6, ll. 22– 25; col. 7, ll. 12. Thus, the updated menu is the same on the desktop PC and the handheld device. At the oral hearing, Patent Owner indicated that downloading is synchronizing, as “[i]t’s making something the same with something else.” See Tr. 28. For these reasons, we agree with Petitioner that the preamble is non- slip op. at 9

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

      “We are persuaded by Petitioner that the broadest reasonable construction in light of the Specification of the term CPU is the computational and control unit of a computer. Petitioner’s construction is consistent with the Specification, which describes that the system of the ’850 patent uses typical hardware elements in the form of a computer workstation and that “a typical workstation platform includes hardware such as a central processing unit (‘CPU’), e.g., a Pentium® microprocessor.” Ex. 1031, col. 5, ll. 34–40; see also id. at col. 5, ll. 48–49 (“a CPU, e.g., Pentium ® microprocessor”). Further, as discussed above, the Specification discloses using a desktop PC to generate and downloads menus to a connected handheld device (see id. at col. 6, l. 22–col. 8, l. 62), as well as, discloses the use of a central back-office server (e.g., see id. at col. 2, ll. 29–33). Patent Owner’s proposed construction improperly reads into the claims the central back-office server. See Renishaw, 158 F.3d at 1249 (explaining that extraneous features should not be read into the claims). For these reasons, we determine that the broadest reasonable construction, in light of the Specification, of CPU is the computational and control unit of a computer.” slip op. at 12

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

      “We are not persuaded by Patent Owner that its proposed construction is the broadest reasonable construction in light of the Specification. We see nothing in the Specification, and Patent Owner does not point to anything in the Specification, that provides support for Patent Owner’s proposed construction, in particular that the menus have a “linked levels” feature. Although the Specification discloses some menus that are linked to additional menus, this “linked levels” feature is extraneous and should not be read from the Specification into the claim. See Ex. 1031, col. 5, ll. 23–33 (“File options can have additional subordinate or child options associated with them. If a file option having a subordinate option is selected . . .” (emphases added)). We give “menu” its ordinary and customary meaning. RANDOM HOUSE WEBSTER’S COLLEGE DICTIONARY defines menu as “a list of options available to a user, as displayed on a computer or TV screen.” RANDOM HOUSE WEBSTER’S COLLEGE DICTIONARY, 520 (2nd ed. 1997). This definition is consistent with the Specification, which describes menus as providing choices or options in a GUI. See Ex. 1031, col. 5, ll. 17–20; see Fig. 1 (depicting a menu, a modifier menu, and a sub modifier menu). For these reasons, we determine that the broadest reasonable construction, in light of the Specification, of “menu” is a list of options available to a user displayable on a computer. v. “the second menu is capable of being displayed on the display screen of a” slip op. at 13

    • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable

      “The claims recite a system that generates a second menu from a first menu by selecting menu categories and items from the first menu, adding menu categories and items to the second menu, and selecting parameters from modifier and sub-modifier menus to assign to items in the second menu. The claims also recite that the system transmits the second menu to a wireless handheld computing device or Web page. As discussed in section I(A) above, the Specification discloses a user generating a menu by adding or deleting menu categories, such as salads or desserts; menu items, such as caesar salad or green salad; menu modifiers, such as dressing; and menu sub-modifiers, such as ranch or blue cheese to create the second menu. Ex. 1031, col. 6, l. 35–col. 8, l. 20. The Specification states: [w]hile the preferred embodiment of the invention includes the selection of items from a master menu wherein the master menu is displayed using a graphical user interface, it is to be appreciated that any means for displaying the master menu to the user and generating another menu in response to and comprised of the selections made is encompassed by the contemplated invention. (id. at col. 13, ll. 52–58) and [t]he inventive concept encompasses the generation of a menu in any context known to those skilled in the art where an object is to facilitate display of the menu so as to enable selection of items from that menu. . . . Likewise, displaying menus generated in accordance with the invention on PDAs and Web pages to facilitate remote ordering are but a few examples of ways in which such menu might be used in practice. Any display and transmission means known to those skilled in the art is equally usable with respect to menus generated in accordance with the claimed invention.” slip op. at 18

    Patent outcomesUS 6,384,850 unpatentable
    Claim construction§ 101 eligibilitycites Alice · Mayo
    Patents in suitUS 6,384,850
  • PTAB · Sep 16, 2014 · CBM2013-00024 · APJ Georgianna W Braden · CBM · Final written decision

    Claims 1–21 are unpatentable under §§ 101 and 102 over Ito; the contingent motion to amend with substitute claims 22–30 is denied.

    RulingsFinal written decision
    • Skill levelOther
    • Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notTerm construed board ownPreamble limitingDecided for patent owner

      “1. “system being implemented using a processor and a storage device accessible to the processor” The preamble of claim 1 recites a “system being implemented using a processor and a storage device.” Petitioner contends that the recited processor and storage device need not be components of the claimed system because they are not positively recited elements. Pet. 11 (citing Ex. 1002 ¶ 39). We are not persuaded by Petitioner’s reasoning, because the processor and storage device recited in the preamble of each independent claim of the ’413 patent serve as the antecedent basis for “said processor” and “the storage device” recited in the body of each claim. Dec. to Inst. 18– 19 (citing C.W. Zumbiel Co., Inc., v. Kappos & Graphic Packaging Int’l, 702 F.3d 1371, 1385 (Fed. Cir. 2012) (noting that a preamble constitutes a limitation when the elements in the body of a claim depend on it for antecedent basis)). Furthermore, if the plain language of a claim indicates that a system is implemented by certain components, then those components constitute required parts of the system. “Implemented,” in that setting, can mean “constituted” or “formed.” Therefore, we construe the clause as setting forth that the processor and the storage device are both components of the claimed system.” slip op. at 13

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

      “We agree with Patent Owner that the specification of the ’413 patent teaches that “model entity” is a set of assembled computer data or data item that represents fundamental components of a model. See Ex. 1001, col. 2, ll. 37–42. Patent Owner, however, does not (1) point to any disclosure in the specification that requires a data object to provide the capability for a user to perform specified operations on the model in order for the data object to qualify as a “model entity,” or (2) offer any persuasive evidence regarding the meaning of “model entity.” Therefore, we construe the phrase “model entity” as “a set of assembled computer data or data item that represents fundamental components of a model.”” slip op. at 14

    • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable

      “issue are directed to a patent-ineligible concept, such as an abstract idea. See Alice, 134 S. Ct. at 2355. “[I]t is important at the outset to identify and define whatever fundamental concept appears wrapped up in the claim so that the subsequent analytical steps can proceed on a consistent footing.” CLS Bank Int’l v. Alice Corp. Pty. Ltd., 717 F.3d 1269, 1282 (Fed. Cir. 2013) (plurality opinion). Here, the challenged claims are directed to a representation of a model for use in processing management information of a collaborative activity. Ex. 1001, col. 2, ll. 37–47. To aid in the management of a collaborative activity (e.g., developing customer relationships), a computer database is created that represents a model of the collaborative activity. Ex. 1004, 116. The model includes model entities (e.g., goals and projects) organized into a plurality of hierarchies (e.g., goals to be done and project hierarchy for doing them, or domain hierarchy of functional areas) having a plurality of types. Id.; see also Ex. 1001, Fig. 3 (hierarchy of goals and projects), Fig. 8 (hierarchy of domains). The model may contain data such as the customer segment, products, needs, etc. Ex. 1001, col. 2, l. 60– col. 3, l. 16. A processor provides a graphical user interface (“GUI”) for interaction with a user. Ex. 1004, p. 0116; see Ex. 1001, Fig. 9 (GUI displaying goals belonging to a domain). Therefore, given this disclosure, we find that the challenged claims are directed to an abstract idea, the creation and use of models to aid in processing management information by organizing and making the information readily accessible by the collaborators of the project. See, e.g., Ex. 1001, col. 2, l. 9–col. 5, l. 8. The model, as described by the specification, is a disembodied concept that is not tied to a specific algorithm or specialized computer. Thus, at the first step of the analysis, we determine the claims at issue here are directed to a patent-ineligible concept: an abstract idea.” slip op. at 21

    Patent outcomesUS 8,095,413 unpatentable
    Claim construction§ 101 eligibility§ 102 anticipationcites Alice · Mayo
    Patents in suitUS 8,095,413
Page 2 of 2

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.