DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Information Disclosure Statement
The information disclosure statements (IDS) submitted on 9/27/2024 was in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
Status of Claims
This action is in reply to the application filed on 9/27/2024, which is a CON of Application 17/682,304 issued as US Patent No. 12,131,389, wherein:
Claims 1-20 are currently pending and have been examined.
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP §§ 706.02(l)(1) - 706.02(l)(3) for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/process/file/efs/guidance/eTD-info-I.jsp.
Claims 1-20 of Application 18/900486 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-16 of US Patent No. 12,131,389. Although the claims at issue are not identical, they are not patentably distinct from each other because the claims of the US 12,131,389 Patent recite all the limitations of claims 1-20 of the instant Application 18/900486 as indicated in the comparison table below.
Application 18/900486
US 12,131,389
1. A server comprising: a processor device; and a non-transitory computer-readable memory that is executable by the processor device to perform operations comprising:
outputting a common user interface that provides integrated labeling for accessing data and performing functions relating to a first financial account data system and a second financial account data system, the integrated labeling being generic with respect to the first financial account data system and the second financial account data system,
the first financial account data system having first account data stored thereon and being configured to perform (i) at least one function according to a first process and using the first account data, and
the second financial account data system having second account data stored thereon that is unintegrated with the first account data, the second financial account data system being configured to perform (i) at least one function according to a second process and using the second account data;
comparing input data comprising input data from an entity with data included in a plurality of existing user profiles to identify, among the plurality of existing user profiles, a user profile associated with the input data by
determining, among a first set of user profiles and a second set of user profiles, the user profile associated with the input data by comparing the input data with a first set of user profiles and a second set of user profiles to identify historical data associated with the entity;
providing, via the common user interface and to an application programming interface (API) on a system configured to communicatively couple to the first financial account data system and the second financial account data system, a request for the function to be executed,
the API configured to determine a data system, among the first financial account data system and the second financial account data system, with which to execute the function based on the historical data;
receiving, from the API, a result from executing the function using the first process or the second process; and outputting the result via the common user interface.
1. A server comprising: a processor device; and
a non-transitory computer-readable memory that is executable by the processor device to perform operations comprising:
outputting a common user interface that provides integrated labeling for accessing data and performing functions relating to a first financial account data system and a second financial account data system, the integrated labeling being generic with respect to the first financial account data system and the second financial account data system,
the integrated labeling representing an integration of the first financial account data system and the second financial account data system at a future time,
the first financial account data system having first account data stored thereon and being configured to perform (i) at least one function according to a first process and using the first account data, and (ii) a first authentication process to authenticate, based on received data, a request to perform the first process,
the second financial account data system having second account data stored thereon that is unintegrated with the first account data, the second financial account data system being configured to perform (i) at least one function according to a second process and using the second account data, and
(ii) a second authentication process to authenticate, based on the received data, a request to perform the second process, the second process being different than the first process and the second authentication process being different than the first authentication process, the integrated labeling representing a process different than and generic to the first process and the second process and an authentication process different than and generic to the first authentication process and the second authentication process; receiving, via the integrated labeling, input data from an entity, the input data including a request to perform a function;
comparing the input data with data included in a plurality of existing user profiles to identify, among the plurality of existing user profiles, a user profile associated with the input data by: receiving, from the first financial account data system, a first set of user profiles, wherein each user profile of the first set of user profiles includes indications of known devices and known behaviors of a first corresponding entity having an account associated with the first financial account data system; receiving, from the second financial account data system, a second set of user profiles, wherein each user profile of the second set of user profiles includes indications of known devices and known behaviors of a second corresponding entity having an account associated with the second financial account data system; and
determining, among the first set of user profiles and the second set of user profiles, the user profile associated with the input data by comparing the input data with the first set of user profiles and the second set of user profiles to identify historical data associated with the entity;
providing, via the common user interface and to an application programming interface (API) on a system configured to communicatively couple to the first financial account data system and the second financial account data system, the request for the function to be executed,
the API configured to determine a data system, among the first financial account data system and the second financial account data system, with which to execute the function based on the historical data;
receiving, from the API, a result from executing the function using the first process or the second process; and outputting the result via the common user interface.
2. The server of claim 1, wherein the integrated labeling represents an integration of the first financial account data system and the second financial account data system at a future time.
1…the integrated labeling representing an integration of the first financial account data system and the second financial account data system at a future time;
3. The server of claim 1, wherein the first financial account data system is further configured to perform a first authentication process to authenticate, based on received data, a request to perform the first process,
wherein the second financial account data system is further configured to perform a second authentication process to authenticate, based on the received data, a request to perform the second process, and wherein the second authentication process is different than the first authentication process.
1…the first financial account data system having first account data stored thereon and being configured to perform…a first authentication process to authenticate, based on received data, a request to perform the first process,
1…the second financial account data system being configured to perform…a second authentication process to authenticate, based on the received data, a request to perform the second process,…the second authentication process being different than the first authentication process,
4. The server of claim 3, wherein the integrated labeling represents a process different than and generic to the first process and the second process and an authentication process different than and generic to the first authentication process and the second authentication process.
1…the integrated labeling representing a process different than and generic to the first process and the second process and an authentication process different than and generic to the first authentication process and the second authentication process
5. The server of claim 1, wherein the operations further comprise: receiving, from the first financial account data system, the first set of user profiles,
wherein each user profile of the first set of user profiles includes indications of known devices and known behaviors of a first corresponding entity having an account associated with the first financial account data system; and
receiving, from the second financial account data system, the second set of user profiles, wherein each user profile of the second set of user profiles includes indications of known devices and known behaviors of a second corresponding entity having an account associated with the second financial account data system.
1…receiving, from the first financial account data system, a first set of user profiles,
wherein each user profile of the first set of user profiles includes indications of known devices and known behaviors of a first corresponding entity having an account associated with the first financial account data system;
receiving, from the second financial account data system, a second set of user profiles, wherein each user profile of the second set of user profiles includes indications of known devices and known behaviors of a second corresponding entity having an account associated with the second financial account data system;
6. The server of claim 1, wherein the operation of outputting the result via the common user interface comprises outputting the result using the integrated labeling.
2. The server of claim 1, wherein the operation of outputting the result via the common user interface includes outputting the result using the integrated labeling.
7. The server of claim 1, wherein the server is a first server, wherein the system is a second server, and wherein the operations further comprise receiving the result from the second server subsequent to the second server executing an application programming interface call to the data system for transmitting input data and the function to the data system.
3. The server of claim 1, wherein the server is a first server, wherein the system is a second server, and wherein the operation of receiving the result from executing the function using the first process or the second process includes receiving the result from the second server subsequent to the second server executing an application programming interface call to the data system for transmitting input data and the function to the data system.
8. A system comprising: a first financial account data system having first account data stored thereon and being configured to perform at least one function according to a first process and using the first account data;
a second financial account data system having second account data stored thereon that is unintegrated with the first account data, the second financial account data system being configured to perform at least one function according to a second process and using the second account data,
the second process being different than the first process;
a server comprising a processor device and a non-transitory computer-readable memory that is executable by the processor device to perform operations comprising:
outputting a common user interface that provides integrated labeling for accessing data and performing functions relating to the first financial account data system and the second financial account data system, the integrated labeling being generic with respect to the first financial account data system and the second financial account data system;
comparing input data comprising input data from an entity with data included in a plurality of existing user profiles to identify, among the plurality of existing user profiles, a user profile associated with the input data by
determining, among a first set of user profiles and a second set of user profiles, the user profile associated with the input data by comparing the input data with a first set of user profiles and a second set of user profiles to identify historical data associated with the entity;
providing, via the common user interface and to an application programming interface (API) on a separate system configured to communicatively couple to the first financial account data system and the second financial account data system,
a request for the function to be executed, the API configured to determine a data system, among the first financial account data system and the second financial account data system,
with which to execute the function based on the historical data; receiving, from the API, a result from executing the function using the first process or the second process; and
outputting the result via the common user interface.
8. A system comprising: a first financial account data system having first account data stored thereon and being configured to perform (i) at least one function according to a first process and using the first account data,
and (ii) a first authentication process to authenticate, based on received data, a request to perform the first process;
a second financial account data system having second account data stored thereon that is unintegrated with the first account data, the second financial account data system being configured to perform (i) at least one function according to a second process and using the second account data, and
(ii) a second authentication process to authenticate, based on the received data, a request to perform the second process,
the second process being different than the first process and the second authentication process being different than the first authentication process;
a server comprising a processor device and a non-transitory computer-readable memory that is executable by the processor device to perform operations comprising:
outputting a common user interface that provides integrated labeling for accessing data and performing functions relating to the first financial account data system and the second financial account data system, the integrated labeling being generic with respect to the first financial account data system and the second financial account data system,
the integrated labeling representing an integration of the first financial account data system and the second financial account data system at a future time;
receiving, via the integrated labeling, input data from an entity, the input data including a request to perform a function;
comparing the input data with data included in a plurality of existing user profiles to identify, among the plurality of existing user profiles, a user profile associated with the input data by:
receiving, from the first financial account data system, a first set of user profiles, wherein each user profile of the first set of user profiles includes indications of known devices and known behaviors of a first corresponding entity having an account associated with the first financial account data system;
receiving, from the second financial account data system, a second set of user profiles, wherein each user profile of the second set of user profiles includes indications of known devices and known behaviors of a second corresponding entity having an account associated with the second financial account data system; and
determining, among the first set of user profiles and the second set of user profiles, the user profile associated with the input data by comparing the input data with the first set of user profiles and the second set of user profiles to identify historical data associated with the entity;
providing, via the common user interface and to an application programming interface (API) on a server configured to communicatively couple to the first financial account data system and the second financial account data system,
the request for the function to be executed, the API configured to determine a data system, among the first financial account data system and the second financial account data system,
with which to execute the function based on the historical data; receiving, from the API, a result from executing the function using the first process or the second process; and
outputting the result via the common user interface.
9. The system of claim 8, wherein the integrated labeling represents an integration of the first financial account data system and the second financial account data system at a future time.
8…the integrated labeling representing an integration of the first financial account data system and the second financial account data system at a future time;
10. The system of claim 8, wherein the first financial account data system is further configured to perform a first authentication process to authenticate, based on received data, a request to perform the first process,
wherein the second financial account data system is further configured to perform a second authentication process to authenticate, based on the received data, a request to perform the second process, and
wherein the second authentication process is different than the first authentication process.
8…A system comprising: a first financial account data system having first account data stored thereon and being configured to perform…a first authentication process to authenticate, based on received data, a request to perform the first process;
…the second financial account data system being configured to perform…a second authentication process to authenticate, based on the received data, a request to perform the second process,
…and the second authentication process being different than the first authentication process;
11. The system of claim 10, wherein the integrated labeling represents a process different than and generic to the first process and the second process and an authentication process different than and generic to the first authentication process and the second authentication process.
1…the integrated labeling representing a process different than and generic to the first process and the second process and an authentication process different than and generic to the first authentication process and the second authentication process;
12. The system of claim 8, wherein the operations further comprise: receiving, from the first financial account data system, the first set of user profiles, wherein each user profile of the first set of user profiles includes indications of known devices and known behaviors of a first corresponding entity having an account associated with the first financial account data system; and
receiving, from the second financial account data system, the second set of user profiles, wherein each user profile of the second set of user profiles includes indications of known devices and known behaviors of a second corresponding entity having an account associated with the second financial account data system.
8…receiving, from the first financial account data system, a first set of user profiles, wherein each user profile of the first set of user profiles includes indications of known devices and known behaviors of a first corresponding entity having an account associated with the first financial account data system;
receiving, from the second financial account data system, a second set of user profiles, wherein each user profile of the second set of user profiles includes indications of known devices and known behaviors of a second corresponding entity having an account associated with the second financial account data system;
13. The system of claim 8, wherein the operation of outputting the result via the common user interface comprises outputting the result using the integrated labeling.
9. The system of claim 8, wherein the operation of outputting the result via the common user interface includes outputting the result using the integrated labeling.
14. The system of claim 8, wherein the server is a first server, wherein the separate system is a second server, and wherein the operation of receiving the result from executing the function using the first process or the second process includes receiving the result from the first server subsequent to the first server executing an application programming interface call to the data system for transmitting input data and the function to the data system.
10. The system of claim 8, wherein the server is a first server, wherein the system is a second server, and wherein the operation of receiving the result from executing the function using the first process or the second process includes receiving the result from the first server subsequent to the first server executing an application programming interface call to the data system for transmitting input data and the function to the data system.
15. A method comprising: outputting, by a server, a common user interface that provides integrated labeling for accessing data and performing functions relating to a first financial account data system and a second financial account data system,
the first financial account data system having first account data stored thereon and being configured to perform at least one function according to a first process and using the first account data,
the second financial account data system having second account data stored thereon that is unintegrated with the first account data, the second financial account data system being configured to perform at least one function according to a second process and using the second account data,
the second process being different than the first process;
comparing input data comprising input data from an entity with data included in a plurality of existing user profiles to identify, among the plurality of existing user profiles, a user profile associated with the input data by
determining, among a first set of user profiles and a second set of user profiles, the user profile associated with the input data by comparing the input data with a first set of user profiles and a second set of user profiles to identify historical data associated with the entity;
providing, via the common user interface and to an application programming interface (API) on a system configured to communicatively couple to the first financial account data system and the second financial account data system,
a request for the function to be executed, the API configured to determine a data system, among the first financial account data system and the second financial account data system, with which to execute the function based on the historical data;
receiving, from the API, a result from executing the function using the first process or the second process; and
outputting the result via the common user interface
12. A method comprising: outputting, by a server, a common user interface that provides integrated labeling for accessing data and performing functions relating to a first financial account data system and a second financial account data system,
the integrated labeling being generic with respect to the first financial account data system and the second financial account data system, the integrated labeling representing an integration of the first financial account data system and the second financial account data system at a future time,
the first financial account data system having first account data stored thereon and being configured to perform (i) at least one function according to a first process and using the first account data,
and (ii) a first authentication process to authenticate, based on input data, a request to perform the first process,
the second financial account data system having second account data stored thereon that is unintegrated with the first account data, the second financial account data system being configured to perform (i) at least one function according to a second process and using the second account data, and
(ii) a second authentication process to authenticate, based on the input data, a request to perform the second process,
the second process being different than the first process and
the second authentication process being different than the first authentication process, the integrated labeling representing a process different than and generic to the first process and the second process and an authentication process different than and generic to the first authentication process and the second authentication process;
receiving, via the integrated labeling, input data from an entity, the input data including a request to perform a function;
identifying a user profile associated with the input data, the user profile including historical data associated with the entity, wherein identifying the user profile includes
comparing the input data with data included in a plurality of existing user profiles to identify, among the plurality of existing user profiles, a user profile associated with the input data by:
receiving, from the first financial account data system, a first set of user profiles, wherein each user profile of the first set of user profiles includes indications of known devices and known behaviors of a first corresponding entity having an account associated with the first financial account data system;
receiving, from the second financial account data system, a second set of user profiles, wherein each user profile of the second set of user profiles includes indications of known devices and known behaviors of a second corresponding entity having an account associated with the second financial account data system; and
determining, among the first set of user profiles and the second set of user profiles, the user profile associated with the input data by comparing the input data with the first set of user profiles and the second set of user profiles to identify historical data associated with the entity;
providing, by the server, via the common user interface, and to an application programming interface (API) on a system configured to communicatively couple to the first financial account data system and the second financial account data system,
a request for a function to be executed, the API configured to determine a data system, among a first financial account data system and a second financial account data system, with which to execute the function;
receiving, by the server and from the API, a result from executing the function using the first process or the second process; and
outputting, by the server, the result via the common user interface.
16. The method of claim 15, wherein the integrated labeling represents an integration of the first financial account data system and the second financial account data system at a future time.
12… the integrated labeling representing an integration of the first financial account data system and the second financial account data system at a future time,
17. The method of claim 15, wherein the first financial account data system performs a first authentication process to authenticate, based on received data, a request to perform the first process,
wherein the second financial account data system performs a second authentication process to authenticate, based on the received data, a request to perform the second process,
and wherein the second authentication process is different than the first authentication process.
12…the first financial account data system…being configured to perform…a first authentication process to authenticate, based on input data, a request to perform the first process,
12… the second financial account data system being configured to perform…a second authentication process to authenticate, based on the input data, a request to perform the second process,
…the second authentication process being different than the first authentication process,
18. The method of claim 17, wherein the integrated labeling represents a process different than and generic to the first process and the second process and an authentication process different than and generic to the first authentication process and the second authentication process.
12…the integrated labeling representing a process different than and generic to the first process and the second process and an authentication process different than and generic to the first authentication process and the second authentication process
19. The method of claim 15, further comprising: receiving, from the first financial account data system, the first set of user profiles, wherein each user profile of the first set of user profiles includes indications of known devices and known behaviors of a first corresponding entity having an account associated with the first financial account data system; and
receiving, from the second financial account data system, the second set of user profiles, wherein each user profile of the second set of user profiles includes indications of known devices and known behaviors of a second corresponding entity having an account associated with the second financial account data system
12… receiving, from the first financial account data system, a first set of user profiles, wherein each user profile of the first set of user profiles includes indications of known devices and known behaviors of a first corresponding entity having an account associated with the first financial account data system;
receiving, from the second financial account data system, a second set of user profiles, wherein each user profile of the second set of user profiles includes indications of known devices and known behaviors of a second corresponding entity having an account associated with the second financial account data system;
20. The method of claim 15, wherein outputting the result via the common user interface comprises outputting the result using the integrated labeling.
13. The method of claim 12, wherein outputting the result via the common user interface includes outputting, by the server, the result using the integrated labeling.
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-20 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. The claims recite a system and method for performing financial functions which is considered a judicial exception because it falls under Certain Methods of Organizing Human Activity such as commercial or legal interactions, including sales activities or behaviors, and business relations. This judicial exception is not integrated into a practical application as discussed below and the claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception as discussed below.
This rejection follows the 2019 Revised Patent Subject Matter Eligibility Guidance, 84 Fed Reg 4, January 7, 2019, pp. 50-57 (“2019 PEG”)(MPEP 2106).
Analysis
Step 1 (Statutory Categories) – 2019 PEG pg. 53 (See MPEP 2106.03)
Claims 1-20 are directed to the statutory category of a process, machine, or manufacture.
Step 2A, Prong 1 (Do the claims recite an abstract idea?) – 2019 PEG pg. 54 (See MPEP 2106.04(a)-(c))
For independent claims 1, 8, and 15, the claims recite an abstract idea of: performing financial functions. The steps of independent claim 1 recite the abstract idea (in bold below) of: “A server comprising: a processor device; and a non-transitory computer-readable memory that is executable by the processor device to perform operations comprising: outputting a common user interface that provides integrated labeling for accessing data and performing functions relating to a first financial account data system and a second financial account data system, the integrated labeling being generic with respect to the first financial account data system and the second financial account data system, the first financial account data system having first account data stored thereon and being configured to perform (i) at least one function according to a first process and using the first account data, and the second financial account data system having second account data stored thereon that is unintegrated with the first account data, the second financial account data system being configured to perform (i) at least one function according to a second process and using the second account data; comparing input data comprising input data from an entity with data included in a plurality of existing user profiles to identify, among the plurality of existing user profiles, a user profile associated with the input data by determining, among a first set of user profiles and a second set of user profiles, the user profile associated with the input data by comparing the input data with a first set of user profiles and a second set of user profiles to identify historical data associated with the entity; providing, via the common user interface and to an application programming interface (API) on a system configured to communicatively couple to the first financial account data system and the second financial account data system, a request for the function to be executed, the API configured to determine a data system, among the first financial account data system and the second financial account data system, with which to execute the function based on the historical data; receiving, from the API, a result from executing the function using the first process or the second process; and outputting the result via the common user interface”. Independent claims 8 and 15 recite similar steps that recite the abstract idea. Independent claims 1, 8, and 15, as drafted, are a process that, under the broadest reasonable interpretation, covers Certain Methods of Organizing Human Activity, since they recite commercial or legal interactions, including sales activities or behaviors, and business relations. If the claim limitations, under the broadest reasonable interpretation, covers methods of organizing human activity but for the recitation of additional elements including generic computer components, then it falls within the “Certain Methods of Organizing Human Activity” grouping of abstract ideas. Other than reciting the abstract idea, the independent claims recite additional elements including generic computer components such as “a server comprising a processor executing non-transitory computer readable memory, a user interface, a first financial account data system, a second financial account data system, an application programming interface (API), and a system”, and nothing in the claims precludes the steps from being performed as a method of organizing human activity. Accordingly, the independent claims recite an abstract idea.
Dependent claims 2-7, 9-14, and 16-20 recite similar limitations as independent claims 1, 8, and 15; and when analyzed as a whole are held to be patent ineligible under 35 U.S.C 101 because the additional recited limitations only refine the abstract idea further. Other than reciting the abstract idea, the dependent claims recite similar additional elements including generic computer components as the independent claims, such as “the server, the first financial account data system, the second account data system, the user interface, a first server, a second server, the system, and an API”. If a claim limitation, under its broadest reasonable interpretation, covers commercial or legal interactions, but for the recitation of generic computer components, then it falls within the “Certain Methods of Organizing Human Activity” grouping of abstract ideas.
Step 2A, Prong 2 (Does the claim recite additional elements that integrate the judicial exception into a practical application?) – 2019 PEG pg. 54 (See MPEP 2106.04(d)-(c))
This judicial exception is not integrated into a practical application. In particular, independent claims 1, 8, and 15 only recite the additional elements of “a server comprising a processor executing non-transitory computer readable memory, a user interface, a first financial account data system, a second financial account data system, an application programming interface (API), and a system”. A plain reading of the Figures and associated descriptions in the specification reveals that generic processors may be used to execute the claimed steps. The additional elements are recited at a high level of generality (i.e., as a generic processor performing generic computer functions) such that it amounts to no more than mere instructions to apply the exception using generic computer components (See MPEP 2106.05(f)) and limits the judicial exception to a particular environment (See MPEP 2106.05(h)). Mere instructions to apply an exception using a generic computer component and limiting the judicial exception to a particular environment doesn’t integrate the abstract idea into a practical application in Step 2A. Accordingly, these additional elements do not integrate the abstract idea into a practical application because it does not impose any meaningful limits on practicing the abstract idea. Hence, independent claims 1, 8, and 15 are directed to an abstract idea.
Dependent claims 2-7, 9-14, and 16-20, recite similar additional elements as the independent claims including generic computer components, such as “the server, the first financial account data system, the second account data system, the user interface, a first server, a second server, the system, and an API”. The judicial exception is not integrated into a practical application because the additional elements in the dependent claims are also recited at a high-level of generality such that it amounts to more no more than mere instructions to apply the exception using generic computer components. Therefore, the additional elements do not integrate the abstract idea into a practical application because they also do not impose any meaningful limits on practicing the abstract idea. Also, the claims do not affect an improvement to another technology or technical field; the claims do not amount to an improvement of the functioning of a computer system itself; the claims do not effect a transformation or reduction of a particular article to a different state or thing; and the claims do not move beyond a general link of the use of an abstract idea to a particular technological environment.
Step 2B (Does the claim recite additional elements that amount to significantly more than the judicial exception?) – 2019 PEG pg. 56 (See MPEP 2106.05)
Independent claims 1, 8, and 15 do not include additional elements that are sufficient to amount to significantly more than the judicial exception. As discussed above with respect to integration of the abstract idea into a practical application, the recited additional elements amount to no more than mere instructions to apply the exception using a generic computer component (See MPEP 2106.05(f)) and limits the judicial exception to the particular environment of computers (See MPEP 2106.05(h)). The additional elements of the instant underlying process, when taken in combination, together do not offer substantially more than the sum of the function of the elements when each is taken alone. Mere instructions to apply an exception using a generic computer component cannot provide an inventive concept in Step 2B.
In addition, the dependent claims 2-7, 9-14, and 16-20 do not include additional elements that are sufficient to amount to significantly more than the judicial exception. As discussed above with respect to integration of the abstract idea into a practical application, the additional elements of the dependent claims to perform the claimed limitations, amounts to no more than mere instructions to apply the exception using a generic computer component (See MPEP 2106.05(f)). Similar to the independent claims, mere instructions to apply an exception using a generic computer component cannot provide an inventive concept. Also, for the same reasoning as the independent claims, the additional elements of the limitations of the dependent claims, when considered individually and as an ordered combination, together do not offer significantly more than the sum of the functions of the elements when each is taken alone and the dependent claims as a whole, do not amount to significantly more than the abstract idea itself. For these reasons, the dependent claims also are not patent eligible.
Subject Matter Overcoming 35 USC §102/§103
Claims 1-20 would be allowable if rewritten to: overcome the rejections under 35 U.S.C. 101 set forth in this Office Action; and overcome the non-statutory double patenting rejections set forth in this Office Action.
The following is an examiner’s statement of reasons for subject matter of independent claims 1, 8, and 15 overcoming the prior art rejections under 35 USC §102/§103.
The closest prior art of record is US 20190362086 to Vanloo et al. (hereinafter referred to as Vanloo), JP 2004-078383 A to Van Os et al. (hereinafter referred to as Van Os), and US 2012/01310760 to Phillips (hereinafter referred to as Phillips). Allowable subject matter is indicated because none of the prior art of record, alone or in combination, appears to teach or fairly suggest or render obvious the combination set forth in independent claims 1, 8, and 15. For independent claim 1, the prior art of Vanloo, Van Os, and Phillips specifically do not disclose: “comparing input data comprising input data from an entity with data included in a plurality of existing user profiles to identify, among the plurality of existing user profiles, a user profile associated with the input data by determining, among a first set of user profiles and a second set of user profiles, the user profile associated with the input data by comparing the input data with a first set of user profiles and a second set of user profiles to identify historical data associated with the entity; providing, via the common user interface and to an application programming interface (API) on a system configured to communicatively couple to the first financial account data system and the second financial account data system, a request for the function to be executed, the API configured to determine a data system, among the first financial account data system and the second financial account data system, with which to execute the function based on the historical data; receiving, from the API, a result from executing the function using the first processor the second process; and outputting the result via the common user interface”. Similar reasoning and rationale apply to the other independent claims 9, and 15. Dependent claims 2-7, 9-14, and 16-20 are allowable over the prior art by virtue of their dependency on an allowed claim.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Paul Schwarzenberg whose telephone number is (313) 446-6611. The examiner can normally be reached on Monday-Thursday (7:30-6:30).
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, Christine Behncke, can be reached on (571) 272-8103. 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.
/PAUL S SCHWARZENBERG/Primary Examiner, Art Unit 3695 8/31/2026
Prosecution Insights