DETAILED ACTION
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Receipt of Applicant’s Amendment filed September 9, 2026, is acknowledged.
Response to Amendment
Claim 1 has been amended. Claims 4-6, 8, 10-13, 16, 18-23, 25-38, 40-65, 67-69, 72, 75-79, and 83-95 have been canceled. Claims 1-3, 7, 9, 14, 15, 17, 24, 39, 66, 70, 71, 73, 74, and 80-82 are pending and are provided to be examined upon their merits.
Response to Arguments
Applicant's arguments filed September 9, 2026, have been fully considered but they are not persuasive. A response is provided below in bold where appropriate.
.Applicant notes claim interpretation of “container,” pg. 15 of Remarks:
A. The Office Action's Claim Interpretation of "Container" (Office Action, Page 9).
The Office Action sets forth a claim interpretation of "container," specifically that "[a] container is therefore interpreted as computer software for financial planning that can store data (e.g., client data, narratives) and execute instructions (e.g., defines prompts, generates container)." Office Action, Page 9. Applicant appreciates the Examiner's effort to clarify the record and responds so that the record is not taken as acquiescence.
Applicant agrees in part with the Office Action's interpretation. A container does "execute instructions," and it does so specifically by defining prompts and generating a further container. In the interest of advancing prosecution, Applicant has amended Claim 1 to expressly recite these terms.
Applicant respectfully traverses the qualifier "for financial planning." That phrase does not describe what a container is or what it does; it describes the environment in which the disclosed embodiment operates. Building the field of use into the construction of the term, and then citing the field of use as a reason the term cannot supply eligibility, resolves the Step 2A question inside the claim interpretation rather than in the analysis. Applicant respectfully requests that "container" be construed by reference to what at least the amended claim requires it to do, e.g., store client data and a narrative, define a specification that governs which prompts the interface renders and which inputs it accepts, select subsequent prompts from received data, and generate a second container with its own specification - without the field-of-use qualifier.
Noted, however, “Financial Plan Container” is recited in both the specification and drawings and Applicant has referred to a financial plan container. The problem is there is no single definition of container taught in the original filed disclosure and container is used in various ways. The point of the claim interpretation section is to clarify how the claim is being interpreted by the examiner. Respectfully, if Applicant can provide a single definition from the specification for what a container is, that will be used.
Applicant argues 35 USC 101 Rejection, starting pg. 15 of Remarks:
B. Step 2A, Prong One - Amended Claim 1 Resolves in Favor of Patentability
Applicant respectfully traverses the finding that Claim 1 recites a certain method of organizing human activity. Specifically, the Office Action identifies two sub- groupings. As to "fundamental economic practice," the limitation cited is "applying projection factors to the financial plan container that contains the client data." Office Action, Page 11. Applicant respectfully submits that applying a projection factor to a data container, where the factor is derived from changes in the client data of other containers having a different container timing, is not a practice of long standing in commerce of the kind contemplated by MPEP 2106.04(a)(2)(I). As to "managing personal behavior," whether tied to "incorporating the financial plan container into a client financial plan," (Office Action, Page 3) or "applying projection factors to a financial plan container, incorporating client data into a client financial plan" (Office Action, Page 11), neither formulation identifies a rule of conduct, an instruction, or a relationship between people, which is what MPEP 2106.04(a)(2)(II) describes.
Using computer technology to perform a judicial exception is not enough to make abstract claims statutory as claimed.
Applicant respectfully submits that Core Wireless is resolved at Prong One: "Because we hold that the asserted claims are not directed to an abstract idea, we do not proceed to the second step of the inquiry." Core Wireless, 880 F.3d at 1363; see also Office Action, Page 4 (quoting the same passage). For the reasons set forth in Sections III through VI below, Applicant respectfully submits that amended Claim 1 is likewise not directed to an abstract idea, and that the analysis should end at Prong One. The arguments that follow are presented in the alternative and without conceding Prong One
Core Wireless improved computer technology itself with an improved display screen. Respectfully, Applicant is not inventing or improving display technology.
C. Claim 1, As Amended, Recites the Specific Mechanism Allegedly Missing.
The Office Action advances three related criticisms of the graphical user interface limitations of Claim 1. Specifically, the Office Action asserts: (1) that "[t]he 'container defines a specification for the graphical user interface' is claimed at a high level of generality, is not used for anything," Office Action, Page 13; (2) that "configured to reduce a complexity of queries to the user" is "intended use language as there is no guarantee complexity will be reduced," Office Action, Page 5; and (3) that the graphical user interface "is display software," Office Action, Page 13.
Applicant has amended Claim 1 to clarify what the container's specification does to the graphical user interface and what the graphical user interface does in response. As amended, Claim 1 recites that "the graphical user interface is rendered in accordance with the specification defined by the at least one financial plan container such that (i) each prompt of the one or more prompts rendered in the graphical user interface is a prompt defined by the specification, and (ii) the graphical user interface accepts, for each rendered prompt, only input that is within a set of permitted inputs defined at least in part by the specification."
Thus, the specification, in addition to being defined, is now executed, and governs which prompts the interface renders, and it constrains what the interface will accept. Thus, Applicant respectfully submits that the Office Action's assertion that the specification "is not used for anything," (Office Action, Page 13), is no longer applicable to Independent Claim 1, as amended.
Applicant has further amended Claim 1 to recite the affirmative, machine- performed steps of "selecting, by the at least one financial plan container and based on the client data received through the custom client interface, one or more subsequent prompts that are defined by the specification and that are different from the one or more prompts, and rendering the one or more subsequent prompts in the graphical user interface in accordance with the specification," Applicant respectfully submits that these are structural, verifiable operations, not merely aspirational statements of purpose or statements of intended use. The interface is not statically drawn and then handed to the user. The container evaluates the data the user has entered, selects the next prompts to render. Whether a given implementation performs these steps is a question of fact that can be determined by inspection, which means they cannot be disregarded as mere statements of intended use.
Noted. However, displaying information and interacting with the information is not enough to make abstract claims statutory.
D. Any Uncertainty Around Reduction In Complexity Is Eliminated By Amended Claim 1.
The Office Action reasons that the reduction in complexity recited by the claims is intended use "as there is no guarantee complexity will be reduced." Office Action, Page 5; see also Office Action, Page 13. Applicant disagrees, however, in the interest of advancing prosecution, Applicant is amending Independent Claim 1 to affirmatively recite the reduction of complexity as a claimed structural consequence of the recited steps.
Specifically, amended Claim 1 requires that "each prompt rendered in the graphical user interface is a prompt defined by the specification," that the subsequent prompts likewise be "defined by the specification," and that the interface accept "only input that is within a set of permitted inputs defined at least in part by the specification." Thus, the claimed graphical user interface, that renders only the prompts a container specifies, and that accepts only the inputs a container permits, presents the user with fewer and simpler queries than an unconstrained interface soliciting the same underlying financial data.
This reduction in complexity is exactly as outlined in the application specification. Specifically, the Life Cards "may be tightly controlled to create a user interface in which the client is asked one or a series of simple questions, and for which limited input is accepted," so that a "specifically tailored financial plan [may] be presented to the client, with minimal strain on the client's resources." Specification, Para. [0078]. And each container "has a specification for the user interface which is designed to reduce the complexity of the queries to the user, so that the user can obtain a customized, accurate financial plan simply by answering the queries that are tied to each container." Specification, Para. [0082]. The specification further explains the purpose served: "[i]t is one purpose of the system to generate prompts for inputs that allow even unsophisticated clients to provide all the necessary data to the system to generate an initial profile." Specification, Para. [0088].
With all due respect, the above is using a display for a judicial exception. This is different than improving computer technology itself, as in Core Wireless.
E. Trading Technologies Is Not Applicable to This Claim; It Is Core Wireless That Is Most Applicable
The Office Action relies on MPEP 2106.05(a)(I)(viii) and Trading Technologies v. IBG LLC, 921 F.3d 1084 (Fed. Cir. 2019), for the proposition that "a graphical user interface that assists traders in processing information more quickly was not enough to make abstract claims statutory." Office Action, Page 6. Applicant respectfully submits that Trading Technologies is distinguishable. The claims there were directed to "[a]rranging transactional information on a graphical user interface," MPEP 2106.05(a)(I)(viii) - that is, to the arrangement and display of information that the trader already had. The Federal Circuit found no change to how the machine operated; the same information was simply laid out differently on the screen. The asserted speed benefit was a benefit to the human reader, not a change in the operation of the interface.
In Independent Claim 1, as amended, there is not a mere rearrangement of displayed information. The recited invention changes what the interface solicits and what the interface will accept, and it changes those things dynamically, at run time, as a function of data already received. The container determines the subsequent prompts. Nothing analogous occurred in Trading Technologies, where the display was populated with pre-existing market data in a fixed arrangement. Applicant respectfully submits that this distinction is the same one the Federal Circuit drew in Core Wireless. There, the improvement lay in "a specific manner of displaying a limited set of information to the user, rather than using conventional user interface methods to display a generic index on a computer." Core Wireless Licensing S.A.R.L. v. LG Elecs., Inc., 880 F.3d 1356, 1362- 63 (Fed. Cir. 2018). Here, likewise, the claim recites a specific manner of soliciting a limited set of information from the user, rather than using conventional user interface methods to present a generic data-entry form.
From Applicant’s specification…
“… Each container has a specification for the user interface which is designed to reduce the complexity of the queries to the user, so that the user can obtain a customized, accurate financial plan simply by answering the queries that are tied to each container. For example, when a client 205 logs on for the first time, they may be led to fill out various containers, e.g., a “job,” container 210, which prompts the client 205 to answer basic questions about the client’s job. Depending on the answers to the questions specified by the “job” container 210, the “job” container 210 may generate different questions. Moreover, depending on the answers to the questions specified by the “job” container, other containers may be generated, and presented to the client 205 for filling in the client data. For example, if, in the interface of “job” container 210, the client 205 specifies that she is “self-employed,” that may generate a “small business” container that the client 205 will then fill out. Other examples of containers include a “home” container 220, where the client 205 can enter in information about her home, a “vacation” container 230 where the client 205 can enter data about a vacation the client would like to take, and a “baby” container 240 where the user can enter her family information and/or family plans.” [0082]
The above is about streamlining (reducing) questions (queries) to a user in order to fill out a financial plan. I guess a decision tree could do this (conditional logic)? This is not improving display technology itself.
The Office Action distinguishes Core Wireless on two grounds: first, that "Core Wireless did not recite abstract claim elements," Office Action, Page 4; and second, that the Core Wireless "language indicated the claims were direct[ed] to an improvement in the function of computers, particularly those with small screens," Office Action, Page 4.
As to the first ground, Applicant respectfully submits that the relevant teaching of Core Wireless is its holding on what constitutes a technological improvement, e.g., that a specific manner of controlling what a user interface presents is such an improvement. That teaching is codified in MPEP 2106.05(a)(I)(x). Applicant respectfully submits that the elements of Independent Claim 1 are not abstract, as set forth above and herein. These elements are recited in Independent Claim 1, as amended.
The rejection is not based on Core Wireless, rather follow MPEP guidelines.
As to the second ground, the reference in Core Wireless to devices "with small screens" was an illustration of where the improvement was most acutely felt, not a limitation on the holding. The operative reasoning was that "[r]ather than paging through multiple screens of options, 'only three steps may be needed from start up to reaching the required data/functionality,"' and that "[t]his language clearly indicates that the claims are directed to an improvement in the functioning of computers." Core Wireless, 880 F.3d at 1363; see also Office Action, Page 4 (quoting the same passage). The structure of that reasoning was that because the interface requires fewer interactions to reach the needed data, the interface is improved.
Applicant submits that Independent Claim 1, as amended, satisfies that same structure. By rendering only container-specified prompts, accepting only container- permitted inputs, and determining subsequent prompts from data already received, the claimed interface obtains from the user the data necessary for a financial plan in fewer and simpler interactions than a conventional data-entry interface would require. See Specification, Paras. [0078], [0082], [0088]. That is the Core Wireless improvement, applied to a different interface problem.
If Applicant is improving display technology, that should be taught and claimed. Using computer software for a judicial exception is not improving computer technology itself.
F. Step 2A, Prong Two: The Additional Elements Integrate Any Exception into a Practical Application.
Applicant respectfully submits that, when the claim is considered as a whole and as an ordered combination, as MPEP 2106.04(d) requires, amended Claim 1 integrates any recited exception into a practical application.
The Office Action's Prong Two analysis rests on the premise that "[t]he financial plan container, template, and user interface, appear to be software to implement the abstract elements," and that the container "appears to be a template with user interface (software) for entering categories of data (e.g., job data) for financial planning purposes, which is abstract." Office Action, Pages 12-13. Applicant respectfully submits that this characterization does not apply at least to Independent Claim 1, as amended.
That software implements an improvement does not make the improvement abstract. "Software can make non-abstract improvements to computer technology just as hardware improvements can." Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 1335 (Fed. Cir. 2016). Additionally, MPEP 2106.05(a) expressly contemplates that improvements to a graphical user interface may be improvements in computer functionality, and MPEP 2106.05(a)(I)(x) identifies the Core Wireless interface as an example.
Nor is the Office Action's Step 2A analysis answered by the observation that the computer hardware is recited generically. Office Action, Page 12. Applicant does not rely on the hardware to impart patentability. Rather, Applicant relies on the specific, claimed manner in which the interface is constructed, constrained, and dynamically re-rendered under the control of the container specification - operations that the recited generic hardware carries out but does not itself supply. Under MPEP 2106.05(a), the question is whether the claimed invention improves the functioning of a computer or another technology, not whether the computer is a special-purpose one.
Software directed to improving computer technology itself is not the same as using software for a judicial exception.
From MPEP 2106.05(f)…
“(3) The particularity or generality of the application of the judicial exception.
A claim having broad applicability across many fields of endeavor may not provide meaningful limitations that integrate a judicial exception into a practical application or a mount to significantly more. For instance, a claim that generically recites an effect of the judicial exception or claims every mode of accomplishing that effect, amounts to a claim that is merely adding the words “apply it” to the judicial exception. See
Internet Patents Corporation v. Active Network, Inc., 790 F.3d 1343, 1348, 115 USPQ2d 1414, 1418 (Fed. Cir. 2015) (The recitation of maintaining the state of data in an online form without restriction on how the state is maintained and with no description of the mechanism for maintaining the state describes “the effect or result dissociated from any method by which maintaining the state is accomplished” and does not provide a meaningful limitation because it merely states that the abstract idea should be applied to achieve a desired result). See also O’Reilly v. Morse, 56 U.S. 62 (1854) (finding ineligible a claim for “the use of electromagnetism for transmitting signals at a distance”); The Telephone Cases, 126 U.S. 1, 209 (1888) (finding a method of “transmitting vocal or other sound telegraphically ... by causing electrical undulations, similar in form to the vibrations of the air accompanying the said vocal or other sounds,” to be ineligible, because it “monopolize[d] a natural force” and “the right to avail of that law by any means whatever.”).”
Therefore, an effect or result by itself is likely not enough.
G. Dependent Claims 2, 3, 7, 9, 14, 15, 17, 24, 39, 66, 70, 71, 73, 74, and 80-82
The Office Action addresses the dependent claims collectively, stating that they "further define the abstract idea." Office Action, Page 14. Applicant respectfully submits that claims 2, 3, 7, 9, 14, 15, 17, 24, 39, 66, 70, 71, 73, 74, and 80-82 are allowable at least by virtue of their dependence from amended Claim 1, and additionally for the further features each recites.
Applicant respectfully directs the Examiner's attention in particular to Claim 3, which recites facilitating presentation "through use of one or more iconographical visual elements that are personalized to a particular client, wherein the one or more iconographical visual elements have at least one visual property that changes relative to an underlying numeric value represented by the one or more iconographical visual elements." This is a further specific manner of displaying information, e.g., a visual property bound to and varying with an underlying numeric value. Thus, at least Dependent Claim 3 is an additional improvement to the interface under MPEP 2106.05(a). Applicant likewise notes Claim 39, which recites that the template of variables "is modified based on other clients' input to other containers that are the same as the financial plan container," reciting a further mechanism by which the container specification, and therefore the interface it defines, is adapted. See Specification, Para. [0084] ("the containers may self-tailor to the client as the client is filling out the containers, based on one or more of crowd-sourcing various container data, receiving data from third parties . . .and from previously inputted data by the client herself.").
Facilitating presentation of the client financial plan is an abstract concept. Doing so with an iconographical visual element is just further limiting an abstract idea and is therefore itself abstract.
From the specification on iconographical visual elements…
“Referring now to Fig. 14, Fig. 14 shows various implementations of financial plan presentation facilitating module 859, according to embodiments. An example of the visual representations generated in financial forecast presentation facilitating module 859, according to one or more embodiments, may be found in Figs. 23 and 24. In an embodiment, referring again to Fig. 14, financial plan presentation facilitating module 859 may include a client financial plan presentation through use of one or more iconographic visual elements of underlying numeric values module 1402. For example, in an embodiment, cash flow distribution between financial life events is visually represented in the financial plan or forecast. In another embodiment, the timing of life events and between life events also is visually represented in the client financial plan or forecast.” [00219]
The above is just displaying abstract concepts of financial data.
H. Conclusion that the Claims Recite Eligible Subject Matter Under 35 U.S.C. 101
For at least the foregoing reasons, Applicant respectfully submits that amended Independent Claim 1 recites eligible subject matter, because the claimed constraint of the graphical user interface by the container specification, and the dynamic determination of subsequent prompts and generation of additional containers from received client data, constitute "improvements to the functioning of a computer or to any other technology or technical field" within the meaning of MPEP 2106.05(a) and Core Wireless.
For at least these reasons, Applicant respectfully requests reconsideration and withdrawal of the rejections of claims 1-3, 7, 9, 14, 15, 17, 24, 39, 66, 70-71, 73, 74, and 80-82 as allegedly directed to non-statutory subject matter.
The rejection is respectfully maintained based on the above response.
II. Art Rejections
No rejection under 35 U.S.C. § 102 or § 103 is presently of record. The Office Action states that "[a] prior art search was updated but does not result in a prior art rejection at this time." Office Action, Page 15. Applicant acknowledges the Examiner's updated search with appreciation. To the extent the Examiner's search is understood to indicate that the pending claims are distinguishable over the prior art of record, Applicant respectfully submits that this consideration weighs in favor of allowance, and respectfully requests that the application be passed to issue upon withdrawal of the § 101 rejection.
Novelty is not determinative of statutory eligibility under 35 USC 101. Novel abstract claims are still abstract.
Claim Interpretation
Applicant has argued regarding “container” that (from Remarks filed January 12, 2026):
“The financial plan container is specifically defined in the Specification and the Claims, including, just from the claim language that it is "at least partially based on a user interaction of a user with the computer," that it is "configured to receive and contain client data," that it includes a template of one or more variables "based on one or more of a type of the financial plan container and financial plan data, and wherein at least one variable of the template of variables is based on data inputted by another entity."” (Remarks filed January 12, 2026).
Therefore, a container contains client data that includes a template of variables.
From Applicant’s argument above…
“The financial plan container specifies "a custom client interface including one or more prompts defined by the financial plan container that is presented through the graphical user interface, and wherein each financial plan container comprises a narrative that includes one of an event, an occurrence, and a condition, and wherein each financial plan container defines a specification for the graphical user interface that is configured to reduce a complexity of queries to the user." (Amended Independent Claim 1).”
Therefore, a financial plan container specifies a client interface including prompts defined by the financial plan container and comprises a narrative and defines a specification for a graphical user interface.
Also, Fig. 10A teaches a financial plan container can generate at least one container that includes a template of one or more variables.
A container is therefore interpreted as computer software for financial planning that can store data (e.g., client data, narratives) and execute instructions (e.g., defines prompts, generates container).
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 1-3, 7, 9, 14, 15, 17, 24, 39, 66, 70, 71, 73, 74, and 80-82 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
Claims 1-3, 7, 9, 14, 15, 17, 24, 39, 66, 70, 71, 73, 74, and 80-82 are directed to a method, which is a statutory category of invention. (Step 1: YES).
The Examiner has identified method Claim 1 as the claim that represents the claimed invention for analysis.
Claim 1 recites the limitations of:
A computationally-implemented method, comprising:
generating, on a computer, at least one financial plan container, said generating at least partially based on a user interaction of a user with the computer, that includes a template of one or more variables, said financial plan container configured to receive and contain client data, and said template of one or more variables is based on one or more of a type of the financial plan container and financial plan data, and wherein at least one variable of the template of variables is based on data inputted by another entity;
facilitating presentation, through a graphical user interface, of the at least one financial plan container that is configured to receive the client data, wherein the at least one financial plan container specifies a custom client interface including one or more prompts defined by the financial plan container that is presented through the graphical user interface, and wherein each financial plan container comprises a narrative that includes one of an event, an occurrence, and a condition, and wherein each financial plan container defines a specification for the graphical user interface that is configured to reduce a complexity of queries to the user, and wherein the graphical user interface is rendered in accordance with the specification defined by the at least one financial plan container such that
(i) each prompt of the one or more prompts rendered in the graphical user interface is a prompt defined by the specification, and
(ii) the graphical user interface accepts, for each rendered prompt, only input that is within a set of permitted inputs defined at least in part by the specification;
receiving the client data through the custom client interface specified by the at least one financial plan container and presented through the specified graphical user interface, into the at least one financial plan container by presenting one or more questions to the user that are based on the type of the financial plan container;
selecting, by the at least one financial plan container and based on the client data received through the custom client interface, one or more subsequent prompts that are defined by the specification and that are different from the one or more prompts, and rendering the one or more subsequent prompts in the graphical user interface in accordance with the specification;
applying one or more projection factors to the at least one financial plan container that contains the client data, wherein said one or more projection factors are based on:
changes in client data of one or more further financial plan containers that are associated with one or more users and that have a different container timing than the at least one container,
and wherein a particular projection factor of the one or more projection factors is based on the selection of a particular economic segment that is based on the life data contained in the at least one financial plan container; and
incorporating the at least one financial plan container that contains the client data and to which the one or more projection factors have been applied, into a client financial plan that is presented to a user in the graphical user interface.
These above limitations, under their broadest reasonable interpretation, cover performance of the limitation as certain methods of organizing human activity. The claim recites elements, highlighted in bold above, which covers performance of the limitation as a fundamental economic practice (e.g., applying projection factors to the financial plan container that contains the client data) and managing personal behavior (e.g., applying projection factors to a financial plan container, incorporating client data into a client financial plan). If a claim limitation, under its broadest reasonable interpretation, covers performance of the limitation as a fundamental economic practice and/or managing personal behavior, then it falls within the “Certain Methods of Organizing Human Activity” grouping of abstract ideas. Accordingly, the claim recites an abstract idea. Claim 1 therefore is abstract. (Step 2A-Prong 1: YES. The claims are abstract)
This judicial exception is not integrated into a practical application. In particular, the claims only recite: a computer (Claim 1). The computer hardware is recited at a high-level of generality (i.e., as a generic processor performing a generic computer function) such that it amounts no more than mere instructions to apply the exception using a generic computer component. See Applicant’s specification, para. [00228] of using a general-purpose computer. Also, para. [00224] where those skilled in the art will recognize implementations may be easily changed. The financial plan container, template, and user interface, appear to be software to implement the abstract elements. The “container” in the disclosure can include a template of variables (para. [0014]), where the container is represents of various occurrences, events, conditions or other things that may have financial data associated with them (para. [0087]). For example, a live container may be an event such as purchase of a house and contain assets, goals, taxes, etc. (therefore a template of variables related to purchase of a house, assets, goals, taxes, etc.). A “container” also appears to be categories or grouping of similar things (such as job, home, vacation, baby) with client data (e.g. Fig. 2, ref. 210, 220, 230, and 240). A user interface (Fig. 2) may be filled out by customers for the different containers (e.g., a template for a job container may be filled out by a client). Summarizing “container” therefore, this appears to be a template with user interface (software) for entering categories of data (e.g., job data) for financial planning purposes, which is abstract. The “container defines a specification for the graphical user interface” is claimed at a high level of generality, is not used for anything. The graphical user interface is display software. The claims also recite “each financial plan container defines a specification for the graphical user interface that is configured to reduce a complexity of queries to the user” where similar claiming of an interface that facilitates a trader in processing information more quickly was shown to be insufficient (MPEP 2106.05(a) I viii, Trading Technologies v. IBG LLC). Also, this is recited at a high level of generality and there is no guarantee that complexity will be reduced. The prompts defined by the specification and accepts only input that is within a set of permitted inputs defined by the specification is for receiving information related to financial plan information, therefore is using graphical user interface (generic computer) for collecting financial plan information (see para. [0088] regarding prompts) and amount to apply the exception using a generic computer. Accordingly, these additional elements, when considered separately and as an ordered combination, do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea. Therefore Claim 1 is directed to an abstract idea without a practical application. (Step 2A-Prong 2: NO. The additional claimed elements are not integrated into a practical application)
The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception because, when considered separately and as an ordered combination, they do not add significantly more (also known as an “inventive concept”) to the exception. As discussed above with respect to integration of the abstract idea into a practical application, the additional element of using a computer hardware amounts to no more than mere instructions to apply the exception using a generic computer component. Mere instructions to apply an exception using a generic computer component cannot provide an inventive concept. Also, mere data gathering has been shown to be insignificant extra solution activity (MPEP 2106.05(g) (3), such as performing clinical tests on individuals to obtain input for an equation, obtaining information about transactions to verify credit card transactions, consulting and updating an activity log). Accordingly, these additional elements, when considered separately and as an ordered combination, do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea. Steps such as receiving are steps that are considered insignificant extra solution activity and mere instructions to apply the exception using general computer components (see MPEP 2106.05(d), II). Thus Claim 1 is not patent eligible. (Step 2B: NO. The claims do not provide significantly more)
Dependent claims 2, 3, 7, 9, 14, 15, 17, 24, 39, 66, 70, 71, 73, 74, and 80-82 further define the abstract idea that is present in independent Claims 1 and thus correspond to Certain Methods of Organizing Human Activity and Mental Processes and hence are abstract for the reasons presented above. The dependent claims do not include any additional elements that integrate the abstract idea into a practical application or are sufficient to amount to significantly more than the judicial exception when considered both individually and as an ordered combination. Claims 2, 3, and 7 are abstract as facilitating presentation of a financial plan. Claim 3 and “iconographical visual elements” is just further limiting presentation of client financial plan (see para. [00219] of the instant specification). Claim 7, 14, 15, and 17 are abstract as generating a template to receive client data. Claim 24 generates a financial plan container, where the container is a life card. This is abstract as financial plan data. Claim 39 generates a generates a financial plan container that includes a template with variables, which is abstract as financial plan data. Claim 66 is providing a financial plan container to receive client data, itself abstract as receiving data for use in a financial plan. Claim 70 is applying models at a high level of generality to project a value of content of a financial plan container, itself abstract as relating to financial plan. Claims 72, 73 and 74 are similar to claim 70 and applying projection factors. Claims 80-82 are utilizing, acquiring, and modifying financial plan data and are abstract themselves as relating to a financial plan. Therefore, the claims 2, 3, 7, 9, 14, 15, 17, 24, 39, 66, 70, 71, 73, 74, and 80-82 are directed to an abstract idea. Thus, the claims 1-3, 7, 9, 14, 15, 17, 24, 39, 66, 70, 71, 73, 74, and 80-82 are not patent-eligible.
Claim Rejections - 35 USC § 112
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention.
Claims 1-3, 7, 9, 14, 15, 17, 24, 39, 66, 70, 71, 73, 74, and 80-82 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention.
Claim 1 recites “graphical user interface that is configured to reduce a complexity of queries to the user, and wherein the graphical user interface is rendered in accordance with the specification defined by the at least one financial plan container such that
(i) each prompt of the one or more prompts rendered in the graphical user interface is a prompt defined by the specification, and
(ii) the graphical user interface accepts, for each rendered prompt, only input that is within a set of permitted inputs defined at least in part by the specification;”
and…
“selecting, by the at least one financial plan container and based on the client data received through the custom client interface, one or more subsequent prompts that are defined by the specification and that are different from the one or more prompts, and rendering the one or more subsequent prompts in the graphical user interface in accordance with the specification;”
The above recites a graphic user interface is rendered in accordance with the specification defined by a financial plan container, and that prompts rendered in the GUI are defined by the specification and the GUI accepts only input within a set of permitted inputs defined at least in part by the specification.
From para. [0082] of Applicant’s specification…
“… Each container has a specification for the user interface which is designed to reduce the complexity of the queries to the user, so that the user can obtain a customized, accurate financial plan simply by answering the queries that are tied to each container. For example, when a client 205 logs on for the first time, they may be led to fill out various containers, e.g., a “job,” container 210, which prompts the client 205 to answer basic questions about the client’s job. Depending on the answers to the questions specified by the “job” container 210, the “job” container 210 may generate different questions. Moreover, depending on the answers to the questions specified by the “job” container, other containers may be generated, and presented to the client 205 for filling in the client data. For example, if, in the interface of “job” container 210, the client 205 specifies that she is “self-employed,” that may generate a “small business” container that the client 205 will then fill out. Other examples of containers include a “home” container 220, where the client 205 can enter in information about her home, a “vacation” container 230 where the client 205 can enter data about a vacation the client would like to take, and a “baby” container 240 where the user can enter her family information and/or family plans.” [0082]
The above teaches a container has a specification for the user interface designed to reduce complexity of queries. This is not the same as a GUI rendered in accordance with a specification defined by a container and the GUI accepts only input within a set of permitted inputs defined by the specification. This is interpreted as a container has a specification for a user interface to provide queries to a client to obtain a customized financial plan
Claims 2, 3, 7, 9, 14, 15, 17, 24, 39, 66, 70, 71, 73, 74, and 80-82 are further rejected as they depend from Claim 1.
Examiner Request
The Applicant is requested to indicate where in the specification there is support for amendments to claims should Applicant amend. The purpose of this is to reduce potential 35 U.S.C. §112, 1st paragraph issues that can arise when claims are amended without support in the specification. The Examiner thanks the Applicant in advance
Prior Art
A prior art search was updated but does not result in a prior art rejection at this time.
Conclusion
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to KENNETH BARTLEY whose telephone number is (571)272-5230. The examiner can normally be reached Mon-Fri: 7:30 - 4:00 EST.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, SHAHID MERCHANT can be reached at (571) 270-1360. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/KENNETH BARTLEY/Primary Examiner, Art Unit 3684