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 .
This office action is in response to the claimed invention filed on June 11, 2025, in which claims 1-20 are presented for examination.
Information Disclosure Statement
The information disclosure statement filed on June 11, 2025; July 15, 2025, August 01, 2025 and February 11, 2026 complies with the provisions of 37 CFR 1.97, 1.98 and MPEP § 609. It has been placed in the application file. The information referred to therein has been considered as to the merits.
Double Patenting
The non-statutory 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 non-statutory 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 § 2146 et seq. 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 filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual 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/apply/applying-online/eterminal-disclaimer.
Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over clams 1-18 of U.S. Patent No. 12,061,631. Although the claims at issue are not identical, they are not patentably distinct from each other because claims 1-20 under examination are obvious, respectively, by claims 1-18 of the reference Patent. Every limitations in the instant application under examination claims are recited in the conflicting reference patent claims, and the differences or additional limitations between the claims are highlighted below by underlining and bolding all limitations. Therefore, it would have been obvious to one having ordinary skill in the art before the effective filing date of the claimed invention to modify the independent claim 1 of the instant application to storing, by one or more processors, a mapping between class values and account types; establishing, by the one or more processors, a connection via one or more application programming interfaces (APIs) with each of a plurality of remote computing devices, each of the plurality of remote computing devices corresponding to a different institution, in order to utilize a middleware computing system to establish connections with the different computing devices to manage connections between accounts and/or profiles of the institutions, thereby allowing the computing devices of institutions to attempt to classify external accounts with data that is available to the institutions, either data stored locally or data stored in external data sources to which computing devices have access when linking accounts, identifying the identification of the institution from the request and select the connection that the analytics server has pre-established with the remote computing device of the institution from the plurality of pre-established connections based on the identification of the institution. Note, such deviation would not interfere with the functionality of the claims that are already patented, and would achieve the same end result.
Please, see the comparison table below:
Application
Patent
1. A method comprising:
in response to receiving, by one or more processors, a request for a data structure type classification for a data structure, retrieving, by the one or more processors, a plurality of records each comprising an identification of the data structure and a class value in a field-value pair corresponding to a class attribute of the record;
automatically determining, by the one or more processors, a data structure type of the data structure by applying one or more rules to the class values in the plurality of records; and
generating, by the one or more processors, instructions containing the determined data structure type to a computing device configured to link the data structure to a profile stored in memory of the computing device and store an identification of the data structure type in a data structure type field-value pair for the linked data structure in the profile.
1. A method comprising:
storing, by one or more processors, a mapping between class values and account types;
establishing, by the one or more processors, a connection via one or more application programming interfaces (APIs) with each of a plurality of remote computing devices, each of the plurality of remote computing devices corresponding to a different institution;
in response to receiving, by the one or more processors, a request for an account type classification of an account, the request including an identification of an institution corresponding to a remote computing device of the plurality of remote computing devices, retrieving, by the one or more processors via the one or more APIs and over the connection with the remote computing device corresponding to the institution identified in the request, a plurality of transaction records each comprising a class value in a field-value pair corresponding to a class transaction attribute of the transaction record;
automatically determining, by the one or more processors applying a rule-based engine and based on the mapping between class values and account types, an account type of the account based only on a comparison between the class values in the plurality of transaction records and the mapping between class values and account types; and
generating, by the one or more processors, instructions containing the determined account type of the account to a computing device configured to link the account to a profile stored in memory of the computing device and store an identification of the account type in an account type field-value pair for the linked account in the profile.
Claims 2-11 are rejected for incorporating the deficiency of their respective base claims by dependency.
Application
Patent
2. The method of claim 1, further comprising: establishing, by the one or more processors, a connection via one or more application programming interfaces (APIs) with each of a plurality of remote computing devices, each of the plurality of remote computing devices corresponding to a different institution.
3. The method of claim 2, wherein the request comprises an identification of an institution corresponding to a remote computing device of the plurality of remote computing devices, and wherein retrieving the plurality of records comprises transmitting, by the one or more processors via the one or more APIs over the connection with the remote computing device, a query comprising an identification of the data structure to the remote computing device.
4. The method of claim 1, wherein determining the data structure type of the data structure comprises: determining, by the one or more processors applying a rule-based engine, a most common class value of the class values of the plurality of records; and determining, by the one or more processors applying the rule-based engine, the data structure type based on the most common class value of the class values of the plurality of records.
5. The method of claim 1, wherein determining the data structure type of the data structure comprises: determining, by the one or more processors applying a rule-based engine, a set of two or more class values of the class values of the plurality of records satisfy a criterion; and determining, by the one or more processors applying the rule-based engine, the data structure type based on the set of two or more class values of the class values of the plurality of records satisfying the criterion.
6. The method of claim 1, wherein determining the data structure type of the data structure comprises: identifying, by the one or more processors applying a rule-based engine, a record of the plurality of records based on the record including a most recent timestamp; identifying, by the one or more processors applying the rule-based engine, a class value in the identified record; and determining, by the one or more processors applying the rule-based engine, the data structure type based on the class value in the identified record.
7. The method of claim 1, wherein determining the data structure type of the data structure comprises: determining, by the one or more processors applying a rule-based engine, a count of a class value within the class values of the plurality of records satisfies a threshold; and determining, by the one or more processors applying the rule-based engine, the data structure type based on the count of the class value within the class values of the plurality of records satisfying the threshold.
8. The method of claim 1, wherein determining the data structure type of the data structure comprises: executing, by the one or more processors, a machine learning model using the class values of the plurality of records as input to cause the machine learning model to output the data structure type, wherein the machine learning model is trained based on historical class values of a plurality of historical records.
9. The method of claim 1, further comprising: identifying, by the one or more processor, a set of records from the plurality of records that include one of a defined set of class values, wherein determining the data structure type of the data structure comprises determining, by the one or more processors applying a rule-based engine, the data structure type of the data structure based only on class values in the identified set of records.
10. The method of claim 1, wherein retrieving the plurality of records comprises retrieving, by the one or more processors, the plurality of records responsive to each of the plurality of records having a timestamp within a defined time period.
11. The method of claim 1, wherein determining the data structure type of the data structure comprises determining, by the one or more processors applying a rule-based engine, whether the data structure is a consumer data structure or a business data structure.
2. The method of claim 1, wherein retrieving the plurality of transaction records comprises transmitting, by the one or more processors via the one or more APIs over the connection with the remote computing device, a query comprising an identification of the account to the remote computing device.
3. The method of claim 1, wherein determining the account type of the account comprises: determining, by the one or more processors applying the rule-based engine, a most common class value of the class values of the plurality of transaction records; and determining, by the one or more processors applying the rule-based engine, the account type based on the account type having a stored association with the determined most common class value in the mapping.
4. The method of claim 1, wherein determining the account type of the account comprises: determining, by the one or more processors applying the rule-based engine, a set of two or more class values of the class values of the plurality of transaction records satisfy a criterion; and determining, by the one or more processors applying the rule-based engine, the account type based on the account type having a stored association with the determined set of two or more class values in the mapping.
5. The method of claim 1, wherein determining the account type of the account comprises: identifying, by the one or more processors applying the rule-based engine, a transaction record of the plurality of transaction records based on the transaction record including a most recent timestamp; identifying, by the one or more processors applying the rule-based engine, a class value in the identified transaction record; and determining, by the one or more processors applying the rule-based engine, the account type based on the account type having a stored association with the identified class value in the mapping.
6. The method of claim 1, wherein determining the account type of the account comprises: determining, by the one or more processors applying the rule-based engine, a count of a class value within the class values of the plurality of transaction records satisfies a threshold; and determining, by the one or more processors applying the rule-based engine, the account type based on the account type having a stored association with the class value with the count that satisfies the threshold in the mapping.
7. The method of claim 1, wherein determining the account type of the account comprises: executing, by the one or more processors, a machine learning model using the class values of the plurality of transaction records as input to cause the machine learning model to output the account type, wherein the machine learning model is trained based on historical class values of a plurality of historical transaction records.
8. The method of claim 1, further comprising: identifying, by the one or more processor, a set of transaction records from the plurality of transaction records that include one of a defined set of class values, wherein determining the account type of the account comprises determining, by the one or more processors applying the rule-based engine, the account type of the account based only on class values in the identified set of transaction records.
9. The method of claim 1, wherein retrieving the plurality of transaction records from the remote computing device comprises retrieving, by the one or more processors, the plurality of transaction records responsive to each of the plurality of transaction records having a timestamp within a defined time period.
10. The method of claim 1, wherein determining the account type of the account comprises determining, by the one or more processors applying the rule-based engine, whether the account is a consumer account or a business account.
As to claim 11, one having skill in the art before the effective filing date of the claimed invention would have found it obvious to modify the independent claim 11 of the instant application to storing, by one or more processors, a mapping between class values and account types; establishing, by the one or more processors, a connection via one or more application programming interfaces (APIs) with each of a plurality of remote computing devices, each of the plurality of remote computing devices corresponding to a different institution, in order to utilize a middleware computing system to establish connections with the different computing devices to manage connections between accounts and/or profiles of the institutions, thereby allowing the computing devices of institutions to attempt to classify external accounts with data that is available to the institutions, either data stored locally or data stored in external data sources to which computing devices have access when linking accounts, identifying the identification of the institution from the request and select the connection that the analytics server has pre-established with the remote computing device of the institution from the plurality of pre-established connections based on the identification of the institution. Note, such deviation would not interfere with the functionality of the claims that are already patented, and would achieve the same end result.
Please, see the comparison table below:
Application
Patent
12. A system comprising:
a network interface;
a processor; and
a non-transitory, computer-readable medium comprising instructions which, when executed by the processor, cause the processor to:
in response to receiving a request for a data structure type classification, retrieve a plurality of records each comprising an identification of a data structure and a class value in a field-value pair corresponding to a class attribute of the record;
automatically determine a data structure type of the data structure by applying one or more rules to the class values in the plurality of records; and
generate instructions containing the determined data structure type to a computing device configured to link the data structure to a profile stored in memory of the computing device and store an identification of the data structure type in a data structure type field- value pair for the linked data structure in the profile.
11. A system comprising:
a network interface;
a processor; and
a non-transitory, computer-readable medium comprising instructions which, when executed by the processor, cause the processor to:
store a mapping between class values and account types;
establish, via the network interface, a connection via one or more application programming interfaces (APIs) with each of a plurality of remote computing devices, each of the plurality of remote computing devices corresponding to a different institution;
in response to receiving a request for an account type classification of an account, the request including an identification of an institution corresponding to a remote computing device of the plurality of remote computing devices, retrieve, via the one or more APIs and over the connection with the remote computing device corresponding to the institution identified in the request, a plurality of transaction records each comprising a class value in a field-value pair corresponding to a class transaction attribute of the transaction record;
automatically determine, using a rule-based engine and based on the mapping between class values and account types, an account type of the account based only on a comparison between the class values in the plurality of transaction records and the mapping between class values and account types; and
generate instructions containing the determined account type of the account to a computing device configured to link the account to a profile stored in memory of the computing device and store an identification of the account type in an account type field-value pair for the linked account in the profile.
Claims 12-20 are rejected for incorporating the deficiency of their respective base claims by dependency.
Application
Patent
13. The system of claim 12, wherein the instructions cause the processor to: establish a connection via one or more application programming interfaces (APIs) with each of a plurality of remote computing devices, each of the plurality of remote computing devices corresponding to a different institution.
14. The system of claim 13, wherein the request comprises an identification of an institution corresponding to a remote computing device of the plurality of remote computing devices, and wherein the instructions cause the processor to retrieve the plurality of records by transmitting, via the one or more APIs over the connection with the remote computing device, a query comprising an identification of the data structure to the remote computing device.
15. The system of claim 12, wherein the instructions cause the processor to determine the data structure type of the data structure by: determining a most common class value of the class values of the plurality of records; and determining, by applying a rule-based engine, the data structure type based on the most common class value of the class values of the plurality of records.
16. The system of claim 12, wherein the instructions cause the processor to determine the data structure type of the data structure by: determining, by applying a rule-based engine, a set of two or more class values of the class values of the plurality of records satisfy a criterion; and determining, by applying the rule-based engine, the data structure type based on the set of two or more class values of the class values of the plurality of records satisfying the criterion.
17. The system of claim 12, wherein the instructions cause the processor to determine the data structure type of the data structure by: identifying, by applying a rule-based engine, a record of the plurality of records based on the record including a most recent timestamp; identifying, by applying the rule-based engine, a class value in the identified record; and determining, by applying the rule-based engine, the data structure type based on the class value in the identified record.
18. The system of claim 12, wherein the instructions cause the processor to determine the data structure type of the data structure by: determining, by applying a rule-based engine, a count of a class value within the class values of the plurality of records satisfies a threshold; and determining, by applying the rule-based engine, the data structure type based on the count of the class value within the class values of the plurality of records satisfying the threshold.
19. The system of claim 12, wherein the instructions cause the processor to determine the data structure type of the data structure by: executing a machine learning model using the class values of the plurality of records as input to cause the machine learning model to output the data structure type, wherein the machine learning model is trained based on historical class values of a plurality of historical records.
20. The system of claim 12, wherein the instructions further cause the processor to: identify a set of records from the plurality of records that include one of a defined set of class values, wherein the instructions cause the processor to determine the data structure type of the data structure by determining, by applying a rule-based engine, the data structure type of the data structure based only on class values in the identified set of records.
12. The system of claim 11, wherein the instructions cause the processor to retrieve the plurality of transaction records by transmitting, via the one or more APIs over the connection with the remote computing device, a query comprising an identification of the account to the remote computing device.
13. The system of claim 11, wherein the instructions cause the processor to determine the account type of the account by: determining, using the rule-based engine, a most common class value of the class values of the plurality of transaction records; and determining, using the rule-based engine, the account type based on the account type having a stored association with the determined most common class value in the mapping.
14. The system of claim 11, wherein the instructions cause the processor to determine the account type of the account by: determining, using the rule-based engine, a set of two or more class values of the class values of the plurality of transaction records satisfy a criterion; and determining, using the rule-based engine, the account type based on the account type having a stored association with the determined set of two or more class values in the mapping.
15. The system of claim 11, wherein the instructions cause the processor to determine the account type of the account by: identifying, using the rule-based engine, a transaction record of the plurality of transaction records based on the transaction record including a most recent timestamp; identifying, using the rule-based engine, a class value in the identified transaction record; and determining, using the rule-based engine, the account type based on the account type having a stored association with the identified class value in the mapping.
16. The system of claim 11, wherein the instructions cause the processor to determine the account type of the account by: determining, using the rule-based engine, a count of a class value within the class values of the plurality of transaction records satisfies a threshold; and determining, using the rule-based engine, the account type based on the account type having a stored association with the class value with the count that satisfies the threshold in the mapping.
17. The system of claim 11, wherein the instructions cause the processor to determine the account type of the account by: executing a machine learning model using the class values of the plurality of transaction records as input to cause the machine learning model to output the account type, wherein the machine learning model is trained based on historical class values of a plurality of historical transaction records.
18. The system of claim 11, wherein the instructions further cause the processor to: identify a set of transaction records from the plurality of transaction records that include one of a defined set of class values, wherein the instructions cause the processor to determine the account type of the account by determining, using the rule-based engine, the account type of the account based only on class values in the identified set of transaction records.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
US 20200167840 A1 (involved in receiving number applying transaction issued to a blockchain, where the number applying transaction includes an account identification of a number applying party account. An electronic bill number is assigned to a number claimant from an electronic note number segment maintained by a superior account corresponding to the number applying party account in response to the number applying transaction. The electronic bill number assigned to the number claimant is added to the number applying party account for maintenance. An intelligent contract deployed on the blockchain is invoked).
US 10846765 B2 (involved in receiving number applying transaction issued to a blockchain, where the number applying transaction includes an account identification of a number applying party account. An electronic bill number is assigned to a number claimant from an electronic note number segment maintained by a superior account corresponding to the number applying party account in response to the number applying transaction. The electronic bill number assigned to the number claimant is added to the number applying party account for maintenance. An intelligent contract deployed on the blockchain is invoked).
US 20200175526 (involved in receiving target transaction for verification processing of a target electronic bill. A verification logic issued in an intelligent contract published on a blockchain is invoked to obtain a bill number of a target electronic bill. Judgment is made to check whether the bill number matches an electronic bill number segment maintained in a blockchain account corresponding to an issuer of the target electronic bill. Legality check is performed on a bill content of the target electronic bill when the bill number matches the electronic bill number segment. A verification processing completion event is issued to a blockchain for deposit.).
US 20210326906 (involved in receiving target transaction for verification processing of a target electronic bill. A verification logic issued in an intelligent contract published on a blockchain is invoked to obtain a bill number of a target electronic bill. Judgment is made to check whether the bill number matches an electronic bill number segment maintained in a blockchain account corresponding to an issuer of the target electronic bill. Legality check is performed on a bill content of the target electronic bill when the bill number matches the electronic bill number segment. A verification processing completion event is issued to a blockchain for deposit.).
US 11429983 (involved in receiving target transaction for verification processing of a target electronic bill. A verification logic issued in an intelligent contract published on a blockchain is invoked to obtain a bill number of a target electronic bill. Judgment is made to check whether the bill number matches an electronic bill number segment maintained in a blockchain account corresponding to an issuer of the target electronic bill. Legality check is performed on a bill content of the target electronic bill when the bill number matches the electronic bill number segment. A verification processing completion event is issued to a blockchain for deposit.).
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JEAN M CORRIELUS whose telephone number is (571)272-4032. The examiner can normally be reached Monday-Friday 6:30a-10p(Midflex).
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, Ann J Lo can be reached at (571)272-9767. 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.
/JEAN M CORRIELUS/Primary Examiner, Art Unit 2159 July 9, 2026
Prosecution Insights