Aggregation source routing

• US 9,361,646 B2
• Filed: 09/25/2013
• Issued: 06/07/2016
• Est. Priority Date: 09/25/2012
• Status: Active Grant

• Current Assignee: MX Technologies Inc.
• Original Assignee: MX Technologies Inc.
• Inventors: Caldwell, John Ryan
• Primary Examiner(s): Meky, Moustafa M
• Application Number:
  US14/036,948
• Publication Number:
  US 20140095486A1
• Time in Patent Office: 986 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2468 Fuzzy queries
• CPC Class Codes: G06F 16/248 Presentation of query results
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 40/174 Form filling; Merging
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 20/407 Cancellation of a transaction
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: H04L 43/0894 Packet rate
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 45/245 Link aggregation, e.g. trunking

Abstract

The present disclosure extends to methods, systems, and computer program products for optimizing aggregation services. The methods and systems for optimizing aggregation routing over a network of computers may comprise computing hardware and software, wherein the software comprises computer readable instructions that cause the computing hardware to receive a request from a user for aggregated account data through a PFM, retrieve a predetermined form for the account data corresponding to the requesting PFM, determine the optimal aggregation source corresponding to the request, reformat the request to be compatible with the optimal aggregation source, send the reformatted request to the optimal aggregation source over the network of computers, receive requested data from the optimal aggregation source over the network of computers, populate the predetermined form corresponding to the PFM, output the populated form to the requesting PFM, and present the aggregated account data by way of the PFM to the user.

Claims

1. A method for optimizing aggregation routing over a network, the method comprising:

receiving a request for aggregated account data;

analyzing multiple data aggregator servers to determine which of the multiple data aggregator servers is an optimal data aggregator server corresponding to the request;

reformatting the request to be compatible with the optimal data aggregator server;

rerouting the reformatted request to the optimal data aggregator server over the network; and

receiving the requested aggregated account data from the optimal data aggregator server over the network.

2. The method of claim 1, wherein the analyzing of the multiple data aggregator servers to determine which of the multiple data aggregator servers is the optimal data aggregator server corresponding to the request comprises:

determining delivery attributes for each of the multiple data aggregator servers;

comparing the requested aggregated account data and a form of the requested aggregated account data to the delivery attributes of the multiple data aggregator servers; and

if a comparison threshold is met for a particular one of the multiple data aggregator servers, then selecting the particular one of the multiple data aggregator servers as the optimal data aggregator server.

3. The method of claim 2, wherein if the comparison threshold is not met for any of the multiple data aggregator servers, then adjusting the comparison threshold so that the adjusted comparison threshold is met for the particular one of the multiple data aggregator servers prior to selecting the particular one of the multiple data aggregator servers as the optimal data aggregator server.

4. The method of claim 2, wherein the comparison threshold corresponds to robustness of account data received from each of the multiple data aggregator servers.

5. The method of claim 2, wherein the comparison threshold corresponds to delivery speed of account data received from each of the multiple data aggregator servers.

6. The method of claim 2, wherein the comparison threshold corresponds to costs of account data received from each of the multiple data aggregator servers.

7. The method of claim 2, wherein the comparison threshold corresponds to completeness of account data received from each of the multiple data aggregator servers.

8. The method of claim 2, wherein the comparison threshold corresponds to an amount of history of account data received from each of the multiple data aggregator servers.

9. The method of claim 1, further comprising normalizing the received aggregated account data.

10. The method of claim 9, further comprising receiving a predetermined data scale for normalizing the received aggregated account data for use in normalizing the received aggregated account data.

11. The method of claim 1, further comprising analyzing the multiple data aggregator servers to determine which of the multiple data aggregator servers is a second optimal data aggregator server.

12. The method of claim 11, further comprising prioritizing aggregated account data received from the optimal data aggregator server over aggregated account data received from the second optimal data aggregator server.

13. One or more non-transitory computer-readable media storing one or more programs that are configured, when executed, to cause one or more processors to perform the method of claim 1.

14. A method for optimizing aggregation routing over a network of computers, the method comprising:

receiving, at a personal financial manager (PFM), a request from a user for aggregated account data;

analyzing, at the PFM, multiple data aggregator servers to determine which of the multiple data aggregator servers is an optimal data aggregator server corresponding to the request;

reformatting, at the PFM, the request to be compatible with the optimal data aggregator server;

rerouting, at the PFM, the reformatted request to the optimal data aggregator server over the network of computers;

receiving, at the PFM, the requested aggregated account data from the optimal data aggregator server over the network of computers; and

presenting, at the PFM, the received aggregated account data to the user.

15. The method of claim 14, wherein the analyzing, at the PFM, of the multiple data aggregator servers to determine which of the multiple data aggregator servers is the optimal data aggregator server corresponding to the request comprises:

determining, at the PFM, delivery attributes for each of the multiple data aggregator servers;

comparing, at the PFM, the requested aggregated account data and a form of the requested aggregated account data to the delivery attributes of the multiple data aggregator servers; and

if a comparison threshold is met for a particular one of the multiple data aggregator servers, then selecting, at the PFM, the particular one of the multiple data aggregator servers as the optimal data aggregator server.

16. The method of claim 15, wherein if the comparison threshold is not met for any of the multiple data aggregator servers, then adjusting, at the PFM, the comparison threshold so that the adjusted comparison threshold is met for the particular one of the multiple data aggregator servers prior to selecting the particular one of the multiple data aggregator servers as the optimal data aggregator server.

17. The method of claim 15, wherein the comparison threshold corresponds to robustness of account data received from each of the multiple data aggregator servers.

18. The method of claim 15, wherein the comparison threshold corresponds to delivery speed of account data received from each of the multiple data aggregator servers.

19. The method of claim 15, wherein the comparison threshold corresponds to costs of account data received from each of the multiple data aggregator servers.

20. The method of claim 15, wherein the comparison threshold corresponds to completeness of account data received from each of the multiple data aggregator servers.

21. The method of claim 15, wherein the comparison threshold corresponds to an amount of history of account data received from each of the multiple data aggregator servers.

22. The method of claim 14, further comprising normalizing, at the PFM, the received aggregated account data.

23. The method of claim 22, further comprising receiving, at the PFM, a predetermined data scale for normalizing the received aggregated account data for use in normalizing, at the PFM, the received aggregated account data.

24. The method of claim 14, further comprising analyzing, at the PFM, the multiple data aggregator servers to determine which of the multiple data aggregator servers is a second optimal data aggregator server.

25. The method of claim 24, further comprising prioritizing, at the PFM, aggregated account data received from the optimal data aggregator server over aggregated account data received from the second optimal data aggregator server.

26. One or more non-transitory computer-readable media storing one or more programs that are configured, when executed, to cause one or more processors to perform the method of claim 14.