Optimizing aggregation routing over a network

• US 9,741,073 B2
• Filed: 06/06/2016
• Issued: 08/22/2017
• 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:
  US15/174,620
• Publication Number:
  US 20160285747A1
• Time in Patent Office: 442 Days
• 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

In one example embodiment, a method for optimizing aggregation routing over a network may include detecting that aggregated account data is unavailable over a network from a first data aggregator server, detecting that the aggregated account data is available over the network from a second data aggregator server, formatting a request for the aggregated account data to be compatible with the second data aggregator server, routing the formatted request over the network to the second data aggregator server, and receiving the requested aggregated account data over the network from the second data aggregator server.

Claims

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

detecting that aggregated account data is unavailable over a network from a first data aggregator server;

detecting that the aggregated account data is available over the network from a second data aggregator server;

formatting a request for the aggregated account data to be compatible with the second data aggregator server;

routing the formatted request over the network to the second data aggregator server; and

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

2. The method of claim 1, wherein the detecting that the aggregated account data is available over the network from the second data aggregator server includes:

analyzing multiple data aggregator servers to determine which of the multiple data aggregator servers is optimal for the aggregated account data; and

selecting the second data aggregator server from among the multiple data aggregator servers as the optimal data aggregator server.

3. The method of claim 2, wherein the analyzing of the multiple data aggregator servers to determine which of the multiple data aggregator servers is optimal includes:

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

comparing the aggregated account data to the delivery attributes of each of the multiple data aggregator servers to determine if a comparison threshold is met for a particular one of the multiple data aggregator servers.

4. The method of claim 3, further comprising:

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.

5. The method of claim 3, 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 3, wherein the comparison threshold corresponds to costs of account data received from each of the multiple data aggregator servers.

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

8. The method of claim 1, wherein the request for the aggregated account data originates from a user.

9. The method of claim 1, wherein the request for the aggregated account data originates from personal financial manager (PFM) software.

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

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

12. 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.

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

detecting that aggregated account data is unavailable over a network from a data aggregator server;

analyzing multiple other data aggregator servers that are available over the network to determine that a particular one of the multiple other data aggregator servers is an optimal data aggregator server for the aggregated account data;

formatting a request for the aggregated account data to be compatible with the optimal data aggregator server;

routing the formatted request over the network to the optimal data aggregator server; and

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

14. The method of claim 13, wherein the analyzing of the multiple other data aggregator servers that are available over the network includes:

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

comparing the aggregated account data to the delivery attributes of each of the multiple other data aggregator servers to determine if a comparison threshold is met for the particular one of the multiple other data aggregator servers.

15. The method of claim 14, further comprising:

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

16. The method of claim 14, wherein the comparison threshold corresponds to:

delivery speed of account data received from each of the multiple other data aggregator servers, costs of account data received from each of the multiple other data aggregator servers, or an amount of history of account data received from each of the multiple other data aggregator servers, or some combination thereof.

17. The method of claim 13, further comprising:

receiving a predetermined data scale for normalizing the received aggregated account data for use in normalizing the received aggregated account data; and

normalizing the received aggregated account data.

18. The method of claim 13, wherein the request for the aggregated account data originates from personal financial manager (PFM) software.

19. The method of claim 13, further comprising:

analyzing the multiple other data aggregator servers to determine which of the multiple other data aggregator servers is a second optimal data aggregator server for the aggregated account data; and

prioritizing the aggregated account data received from the optimal data aggregator server over the aggregated account data received from the second optimal data aggregator server.

20. 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 13.