- American Express Company / American Express Travel Related Services Company, Inc. v. Signature Systems, LLCAll claims unpatentablePTAB · Oct 30, 2019 · CBM2018-00035 · APJ Frances L Ippolito · CBM · Final written decision
Claims 1, 2, 5, 6, 9, 10, 13, and 14 are unpatentable under § 101; proposed substitute claims 17–20 are unpatentable under § 101, and the contingent motion to amend is denied.
RulingsFinal written decision- Skill levelOther
“F. Level of Skill in the Art Petitioner asserts that a person of ordinary skill in the art (“POSITA”)” slip op. at 32
- Expert testimonyOther
“For the above reasons, we are persuaded that Petitioner has met its” slip op. at 62
- Claim Construction › Functional claiming / §112(f) means-plus-function › Corresponding structure / algorithm (indefinite if none)Decided for petitioner
“1. Principles of Law Use of the word “means” in a claim gives rise to a rebuttable” slip op. at 12
- PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, deniedDenied
“Further, based on the entirety of the record, we determine that proposed substitute claims 17–20 are unpatentable by a preponderance of the evidence based on 35 U.S.C. § 101. Motion to Amend Outcome Claims Substitute Claims: Proposed in the Amendment 17–20 Substitute Claims: Motion to Amend Denied 17–20” slip op. at 101
Patent outcomesUS 8,423,402 unpatentableClaim construction§ 101 eligibilitycites Alice · Mayo · Bilski · Berkheimer · EnfishPatents in suitUS 8,423,402 - Autodesk, Inc. v. Uniloc USA, Inc. And Uniloc Luxembourg, S.A.All claims unpatentablePTAB · Sep 11, 2017 · CBM2016-00043 · APJ Christopher M Kaiser · CBM · Final written decision
Claims 1, 2, 4–7, and 12–19 are unpatentable under § 101; claims 3, 8–11, and 20 are subject to adverse judgment after disclaimer.
RulingsFinal written decision- Adverse judgmentAdverse judgmentGranted
“B. Statutory Disclaimer During the pendency of this proceeding, Patent Owner filed a disclaimer pursuant to 35 U.S.C. § 253(a) and 37 C.F.R. § 1.321(a). Ex. 2014. According to this disclaimer, Patent Owner disclaims claims 3, 8–11, and 20 of the ’820 patent. Id.; see also Resp. 1 (“Contemporaneously with the filing of this Response, Patent Owner is disclaiming claims 3, 8, 9, 10, 11, and 20 of the ’820 Patent.”). Our rules provide for entry of adverse judgment against a Patent Owner who disclaims “a claim such that the party has no remaining claim in the trial.” 37 C.F.R. § 42.73(b)(2). Although Patent Owner does not disclaim all the challenged claims, and although Patent Owner therefore has some claims remaining in this trial, we construe the disclaimer of claims 3, 8–11, and 20 as a request for the entry of adverse judgment solely with respect to those claims. We grant the request and enter adverse judgment with respect to claims 3, 8–11, and 20.” slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed patent owner constructionDecided for patent owner
“1. Add-On Computer Software Code Both parties propose construing “add-on computer software code,” a term that appears in every challenged claim. Ex. 1001, 78:43–82:36. Petitioner argues that this term should be interpreted as a “set of computer code that cannot be run independently from a parent program.” Pet. 22. Patent Owner argues that the term should be interpreted as “set of computer code that is designed to run within a parent computer software application or code, particularly architectural CAD software (or another architectural, civil, industrial, or other software design tool), as an internal component.” Resp. 42–43. We agree with Patent Owner. Patent Owner’s construction is taken directly from the written description of the ’820 patent, which provides a reasonably clear, deliberate, and precise definition of the term. See Paulsen, 30 F.3d at 1480; Ex. 1001, 61:42–51 (“The plug-in (add-on) computer software code is . . . .”). To the extent that Petitioner’s proposed construction seeks to limit add-on software code further by requiring that the software code be incapable of running independently from a parent program, as opposed merely to being designed to run within the parent program as an internal component, this further limitation is inconsistent with the lexicography undertaken by the patentee of the ’820 patent. Accordingly, we construe “add-on computer software code” as a “set of computer code that is designed to run within a parent computer software application or code, particularly architectural CAD software (or another architectural, civil, industrial, or other software design tool), as an internal component.”” slip op. at 6
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable
“As discussed above, the ’820 patent describes solving problems with the generation of cost estimates of construction projects, including that the process takes significant time and effort, that the estimates produced are difficult to revise, and that the estimates can be inaccurate, leading to cost overruns and difficulties obtaining construction loans. Ex. 1001, 1:15–62. The claims recite a computer readable medium or system for automating the process of generating a price schedule, which is used to develop the overall project cost estimate. Id. at 78:43–82:36. In so doing, the claims do not recite any “specific asserted improvement in computer capabilities,” such as the “self-referential table for a computer database” in Enfish, 822 F.3d at 1336. Instead, the claims of the ’820 patent “invoke[]” known aspects of computer technology, including “[a] non-transitory computer readable medium,” “a computer that includes a processor and a memory,” “an add-on computer software code,” “a software design tool,” and “a database,” “merely as a tool” for solving the problem of improving the known process of generating construction project cost estimates. Id.; Ex. 1001, 78:43–60. Accordingly, the claims of the ’820 patent are not like those considered in Enfish, where the claims were determined at the first step of the Alice framework not to be directed to abstract ideas because they were directed to “[a] specific asserted improvement in computer capabilities.” 822 F.3d at 1336. Instead, Petitioner has shown by a preponderance of the evidence that the challenged claims of the ’820 patent are focused “on a process that qualifies as an ‘abstract idea.’” Id. The ’820 patent makes clear that the heart of the claimed subject matter is generating prices for construction projects, a process that can be accomplished without automation technology. Ex. 1001, 1:15–62. The claims themselves recite “[a] non-transitory computer readable medium [that] causes [a] computer to generate a price schedule” and “[a] system for creating a pricing schedule.” Id. at 78:43–51, 82:4. As discussed above, the computer technology recited in the claims is used merely as a tool to automate the process of determining the price of a construction project. Determining a price is an abstract idea. See Versata Dev. Grp., 793 F.3d at 1333–34 (Fed. Cir. 2015). Thus, on the current record, Petitioner has made a sufficient showing that the claims of the ’820 patent are directed to an abstract idea under the first step of the Alice analysis.” slip op. at 20
- Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable
“application of an abstract idea. Mayo, 566 U.S. at 78. Petitioner argues that the challenged claims have no such elements, because “the challenged claims add nothing more than well-understood, routine, conventional activity to the abstract idea of calculating a price.” Pet. 32–48. Patent Owner argues that the presence of the add-on computer software code limitations in the challenged claims transforms those claims into patent-eligible applications. Resp. 49–50. We are persuaded that Petitioner has shown by a preponderance of the evidence that the challenged claims of the ’820 patent do not add an inventive concept sufficient to ensure that the patent in practice amounts to significantly more than a patent on the abstract idea itself. Alice, 134 S. Ct. at 2355.” slip op. at 23
Patent outcomesUS 8,515,820 unpatentableClaim construction§ 101 eligibilitycites Alice · Mayo · EnfishPatents in suitUS 8,515,820 - Washington Inventory Services D/B/A Wis International v. Rgis, LLCAll claims unpatentablePTAB · Dec 30, 2015 · CBM2014-00158 · APJ James T Moore · CBM · Final written decision
Claims 1–19 are unpatentable under § 101 as directed to abstract inventory verification implemented with conventional technology, and under § 103 over Whitehouse and ordinary skill in the art.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“We must not import unrecited elements into the claim from the specification. Phillips v. AWH Corp., 415 F.3d 1303, 1319–20 (Fed. Cir. 2005) (en banc). The specification observes its own exemplary nature—“[i]t should be understood that the description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.” Ex. 1001, 2:16–19.” slip op. at 11
- Claim Construction › Intrinsic evidence (Phillips canons) › Prosecution history disclaimer / disavowalTerm construed board ownDecided for petitioner
“During prosecution, in a responsive amendment, Patent Owner proffered that “mode” implied a device: Amended claim 1 recites “selecting a verification mode, which includes a set of rules that define a methodology for verifying the inventory dataset, from a plurality of verification modes” and “acquiring verification data in the completed area with the remote verification device based on the selected verification mode.” The McGraw-Hill Dictionary of Scientific and Technical Terms, 6th Edition, defines the word “mode” as “one of several alternative conditions or methods of operation of a device.” The portion regarding the “set of rules that define a methodology for verifying the inventory dataset” further clarifies what is meant by verification mode. Ex. 1002, 180–81. Claim 1, however, broadly interpreted, can reasonably refer to either “mode”—the verification mode, or the device mode. Moreover, the specification itself, in describing manual processing of prior art printed inventory sheets, also refers to that method of inventory verification as a “mode.” Ex. 1001, 1:31–38 (see in particular line 35). We, therefore, decline to limit the term “mode” to only “on a device” when inventory checking alone can have different “modes” of being” slip op. at 17
- Skill levelSkill level board ownDecided for petitioner
“Mr. Melucci opines that a person of ordinary skill in the art relevant to the ’658 patent “would have at least two years [of] experience related to collecting and verifying inventory data.” Ex. 1006 ¶ 27. Dr. Jagannathan testifies that “a person of ordinary skill in the art of the [’]658 Patent would have had: (1) a Bachelor’s degree in computer science, computer engineering, or related field; (2) one year of related professional experience; and (3) a basic understanding of inventory processes and the use of UPCs and other product identifiers. The professional experience may include, for example, work related to use of bar codes, stock keeping units, and the like. It is further my opinion that relevant professional or practical experience with computer systems and software may substitute for academic credentials.” Ex. 2001 ¶ 40. Based on our review of the ’658 patent, the types of problems and solutions described in the ’658 patent and cited prior art, and the testimony of the parties’ Declarants, we conclude that a person of ordinary skill in the art at the time of the claimed invention would have had at least two years of experience in computerized inventory management. We further note that the applied prior art reflects the appropriate level of skill at the time of the claimed invention. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 18
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable
“imports limitations into the claims from the specification. See, e.g., PO Resp. 35 (discussing the claims jointly). For example, Patent Owner asserts that Petitioner “ignores the actual claim language that requires the verification mode selection to be made on and with the device.” PO Resp. 37. The defect in this argument is that the language of “selecting a particular verification mode on the verification device” is absent from claim 1. See Ex. 1001, 6:2–14. Furthermore, the broadest reasonable interpretation of the term “mode” does not limit the step to a device. Claim 1 positively recites the device in the downloading, deploying, acquiring, computing, and displaying steps, but the term “device” is specifically omitted from the selecting step. Accordingly, we do not interpret claim 1 as requiring the step of selecting a verification mode on the device. Contrary to Patent Owner’s position, we are persuaded by Petitioner that each of challenged claims 1–14, and 18, as a whole, is directed to the fundamental concept of providing inventory verification. Pet. 23. In the Abstract, the ’658 patent states: “[a] system and method of verifying the completeness and accuracy of inventory records is disclosed.” Ex. 1001, Abst. Additionally, in the Background section, the ’658 patent states: Prior methods of verification require that the inventory records be printed out in a predetermined format which is then taken to a specific area in the facility for comparison to the inventory physically located there. These methods are inflexible, tedious and time consuming because the mode of verification is strictly depend[e]nt on the predetermined format of the printed reports and requires a repeated reference to the report and comparison with the actual inventory. Ex. 1001, 1:31–38. The only technological features recited in claims 1–14 and 18 are a computer performing conventional computer functions. Ex. 1001, 6:2–22. Specifically, those include downloading data from a computer to a device, deploying the device, acquiring data with the device, computing, and displaying.” slip op. at 23
Patent outcomesUS 8,606,658 unpatentableClaim construction§ 101 eligibility§ 103 obviousnesscites Alice · Mayo · Bilski · Phillips · GrahamPatents in suitUS 8,606,658 - Cambridge Associates, LLC v. Capital DynamicsAll claims unpatentablePTAB · Aug 31, 2015 · CBM2014-00079 · APJ Donna M Praiss · CBM · Final written decision
Claims 1–17 are unpatentable under § 101 because they claim an abstract mathematical correlation implemented with generic computer functions.
RulingsFinal written decision- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable
“We agree with Petitioner that Digitech is instructive guidance concerning claims to “a process that employs mathematical algorithms to manipulate existing information to generate additional information.” Digitech, 758 F.3d at 1351 (citing Parker v. Flook, 437 U.S. at 595) (concluding such claims are ineligible subject matter). Like the ’196 patent claims, the process claim in Digitech did not recite expressly mathematical formulae or equations. It claimed, in prose, generating two data sets by taking existing information, such as measured chromatic stimuli, spatial stimuli, and device response characteristic functions, and organizing the information into a new form called a device profile. Digitech, 758 F.3d at 1350–51. The method claim was determined to be an abstract idea “because it describes a process of organizing information through mathematical correlations and is not tied to a specific structure or machine.” Id. at 1350. The absence of expressly recited mathematical formulae or equations in the claim carried no significance in determining whether the claims as a whole were directed to the abstract idea. See also Alice, 134 S. Ct. at 2356–57 (noting that no special significance was given to the fact that one of the claims in Bilski reduced hedging to a mathematical formula). In sum, because we agree with Petitioner that the challenged claims involve determining a mathematical correlation, like the claims in Digitech, we conclude that the first step in the Alice/Mayo test is met for claims 1–17.” slip op. at 12
- Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable
“The fact that a claim relies on a method that is implemented on a computer does not, by itself, demonstrate that the claim is patent eligible. Rather, a challenged claim, properly construed, must incorporate enough meaningful limitations to ensure that what is claimed is more than just an abstract idea, and is not a mere “drafting effort designed to monopolize [an abstract idea] itself.” Mayo, 132 S. Ct. at 1297. In order for a machine to impose a meaningful limitation on the scope of a method claim, it must play “a significant part in permitting the claimed method to be performed, rather than function solely as an obvious mechanism for permitting a solution to be achieved more quickly.” SiRF Tech., Inc. v. Int’l Trade Comm’n, 601 F.3d 1319, 1333 (Fed. Cir. 2010). Claims that recite a method of doing business on a computer, and do no more than merely recite the use of the computer for its ordinary function of performing repetitive calculations, are not patent eligible. Bancorp Servs., L.L.C. v. Sun Life Assurance Co., 687 F.3d 1266, 1278–79 (Fed. Cir. 2012) (finding computer used for its most basic function, the performance of repetitive calculation, does not impose a meaningful claim limitation). We are persuaded that Petitioner has shown by a preponderance of the evidence that the extent to which a computer aids the performance of the claimed invention is no more than the ordinary function of common computer software programs, such as the Microsoft Excel spreadsheet used by Patent Owner’s expert. Reply 7 (citing Ex. 1012, 153:15–154:21). Patent Owner’s argument that the computer technology required by the ’196 patent claims “is integral to meeting the requirements of accuracy, precision and timeliness” (PO Resp. 27 (citing Ex. 2004 ¶ 96)) focuses on a specific commercial application of the patent claims “[i]n the private equity world” (id. (citing Ex. 2004 ¶¶ 86–95)). We are not persuaded by Patent Owner’s arguments because they presume particular mathematical computation methods not required by the claims, and reinforce that the nature of the invention is a patent ineligible mathematical algorithm. For example, Patent Owner contends that when presented with a problem to solve at his deposition, Petitioner’s expert, Dr. Robinson, inaccurately computed a real rate of return on an investment because he used quarterly compounding rather than daily compounding. Ex. 2004 ¶ 87. According to Mr. Reyes, Patent Owner’s expert, “daily cashflow (as opposed to monthly or quarterly) has been recognized as a requisite compounding frequency as far back as the 1960s.” Id. at ¶ 91. Such mathematical computations, even if required by the claims, are not sufficient to transform the claims into patent eligible subject matter.” slip op. at 15
- ExcludeMotion to exclude, deniedDenied
“For the reasons that follow, we determine that Petitioner has shown by a preponderance of the evidence that claims 1–17 of the ’196 patent are unpatentable under 35 U.S.C. § 101. Because our determination does not rely on the deposition testimony subject to Patent Owner’s Motion to Exclude, we dismiss the motion as moot.” slip op. at 2
- Expert testimonyOther
“We are persuaded that Petitioner has shown by a preponderance of the evidence that the extent to which a computer aids the performance of the claimed invention is no more than the ordinary function of common computer software programs, such as the Microsoft Excel spreadsheet used by Patent Owner’s expert. Reply 7 (citing Ex. 1012, 153:15–154:21). Patent Owner’s argument that the computer technology required by the ’196 patent claims “is integral to meeting the requirements of accuracy, precision and timeliness” (PO Resp. 27 (citing Ex. 2004 ¶ 96)) focuses on a specific commercial application of the patent claims “[i]n the private equity world” (id. (citing Ex. 2004 ¶¶ 86–95)). We are not persuaded by Patent Owner’s arguments because they presume particular mathematical computation methods not required by the claims, and reinforce that the nature of the invention is a patent ineligible mathematical algorithm. For example, Patent Owner contends that when presented with a problem to solve at his deposition, Petitioner’s expert, Dr. Robinson, inaccurately computed a real rate of return on an investment because he used quarterly compounding rather than daily compounding. Ex. 2004 ¶ 87. According to Mr. Reyes, Patent Owner’s expert, “daily cashflow (as opposed to monthly or quarterly) has been recognized as a requisite compounding frequency as far back as the 1960s.” Id. at ¶ 91. Such mathematical computations, even if required by the claims, are not sufficient to transform the claims into patent eligible subject matter.” slip op. at 16
Patent outcomesUS 7,698,196 unpatentable§ 101 eligibilitycites Alice · Mayo · BilskiPatents in suitUS 7,698,196 - Allscripts Healthcare Solutions, Inc. v. Mymedicalrecords, Inc.All claims unpatentablePTAB · Aug 26, 2015 · CBM2015-00022 · APJ Barbara A Parvis · CBM · Final written decision
Claims 8–12 are unpatentable under § 101 as directed to nonstatutory subject matter; the Board did not reach the anticipation or obviousness grounds.
RulingsFinal written decision- BurdenUnpatentable
“Second, we consider the challenged claims as an ordered combination. Id. at 2359. On this record, when viewed as a whole, the challenged claims 8–12 simply recite the concept of user management performed by a generic computer. The challenged claims, for example, do not purport to improve the functioning of the computer itself. Nor do they improve another technology or technical field. Petitioner additionally relies on the Declaration of Dr. Bysinger (Pet. 20–28), who testifies that the recited elements including “server,” “storing files . . . in a computer readable storage medium,” and “user interface on a computing device” were well-known conventional concepts in 2005. Ex. 1008 ¶¶ 30–32. Dr. Bysinger additionally states “the abstract idea of privately accessing and managing patient medical records . . . [has] existed since at least the promulgation of HIPAA.” Id. ¶ 33. We credit Dr. Bysinger’s statements because they are consistent with the challenged claims. Challenged dependent claims 9–12 add nothing that alters the above analysis under § 101. Claims 9, 10, 11, and 12 recite additional limitations, such as wherein the access information comprises a password, receiving files from a second provider, wherein the files comprise image format files including wills and powers of attorney, respectively. Based on the present record, these comprise either generic limitations, such as using a password for access or sending a file in a known image format, or they relate to organizing human activities, such as user management of legal and financial documents, in addition to health records. Accordingly, we determine that Petitioner has shown by a preponderance of the evidence that claims 8–12 of the ’466 Patent are unpatentable under 35 U.S.C. § 101, because they are directed to non-statutory subject matter.” slip op. at 11
- Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable
“Petitioner asserts that claims 8–12 of the ’466 Patent are unpatentable under 35 U.S.C. § 101, because they are directed to the abstract concept of allowing individuals to manage and access their health records and other medical or legal files privately. Pet. 19. We agree with Petitioner that the claimed invention is directed to an abstract idea: privately managing files by the user. The preamble and all claim limitations of the challenged claims support this view of the claims, and the ’466 Patent consistently describes the invention as allowing an individual to control access to their medical records. See, e.g., Ex. 1001, 5:21–23. Management or control by the user or patient rather than by the health care provider is a method of organizing a human activity. On this record, the concept is an abstract idea, just like the basic hedging concept at issue in Bilski and the abstract idea of intermediated settlement in Alice.3” slip op. at 8
- Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable
“We conclude that receiving and sending data is a routine and conventional computer function. As explained in Alice, “use of a computer to obtain data . . . and issue automated instructions . . . are ‘well-understood, routine, conventional actitiv[ies]’ previously known to the industry.” Alice, 134 S. Ct. 2359; see also buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355 (Fed. Cir. 2014) (“That a computer receives and sends the information over a network—with no further specification—is not even arguably inventive.”). Restricting access by password also is routine and conventional. See Ultramercial, Inc. v. Hulu, LLC, 772 F.3d 709, 712–13, 717 (Fed. Cir. 2014) (determining that representative claim 1 is patent ineligible although it recites “a fourth step of restricting general public access.”). Similarly, providing a user interface is an insignificant activity. See Accenture Global Servs., GmbH v. Guidewire Software, Inc., 728 F.3d 1336, 1342–43 (Fed. Cir. 2013) (determining that claim 1 is patent ineligible although it recites a “claim folder,” which “manages claim information . . . by providing a structured and easy to use interface.”). Claim 8 includes additional recitations relating to how data is stored and managed on the server. We determine that these limitations recite generic functions performed by a generic server and computing device. Storing files is a basic computer function. See Alice, 134 S. Ct. at 2359 (“Using a computer to create and maintain ‘shadow’ accounts amounts to electronic recordkeeping—one of the most basic functions of a computer.”). Additionally, regarding the recitation in challenged claim 8 of “wherein the files are maintained on the server independently from any files maintained by the health care provider” (Ex. 1001, 17:18–19 (emphasis added)), we note the representative claim in Alice had a similar recitation. See Alice, 134 S. Ct. at 2352. In particular, in Alice, the representative claim included the following:” slip op. at 10
- Expert testimonyPetitioner expert creditedDecided for petitioner
“Petitioner additionally relies on the Declaration of Dr. Bysinger (Pet. 20–28), who testifies that the recited elements including “server,” “storing files . . . in a computer readable storage medium,” and “user interface on a computing device” were well-known conventional concepts in 2005. Ex. 1008 ¶¶ 30–32. Dr. Bysinger additionally states “the abstract idea of privately accessing and managing patient medical records . . . [has] existed since at least the promulgation of HIPAA.” Id. ¶ 33. We credit Dr. Bysinger’s statements because they are consistent with the challenged claims.” slip op. at 11
Patent outcomesUS 8,301,466 unpatentableClaim construction§ 101 eligibilitycites Alice · BilskiPatents in suitUS 8,301,466 - Salesforce.Com, Inc. v. Virtualagility, Inc.All claims unpatentablePTAB · 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 unpatentableClaim construction§ 101 eligibility§ 102 anticipationcites Alice · MayoPatents in suitUS 8,095,413
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.