Payment Networks and Methods for Facilitating Data Transfers Within Payment Networks

• US 20170053258A1
• Filed: 08/21/2015
• Published: 02/23/2017
• Est. Priority Date: 08/21/2015
• Status: Active Grant

• Current Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Original Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Inventors: Collins, Pierce A., Carney, Kevin S.
• Granted Patent: US 10,198,724 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/0829 Packet loss
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 43/087 Jitter
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application

Abstract

Exemplary payment networks and methods are provided for facilitating data transfers. One exemplary method includes determining a performance of a first path through a first WAN between a hub and a customer, determining a performance of a second path through a second different WAN between the hub and the customer, causing a data traffic associated with a first class of application to be routed along the first path when the performance of the first path is within a first performance threshold, and causing the data traffic, when routed along the first path, to be switched to the second path when the performance of the first path fails to satisfy and/or violates the performance threshold.

Claims

1. A network for facilitating data transfer between a customer and at least one of a different customer and a payment network data center, the network comprising:

a hub coupled to a data center and including a first hub router coupled to a first wide area network (WAN) and a second hub router coupled to at least one of a second WAN and/or an Internet;

a first edge router coupled to a customer and the first WAN, the first edge router including an engine, the first edge router configured to generate a first tunnel between the first edge router and the first hub router, via the first WAN; and

a second edge router coupled to said customer and the at least one of the second WAN and/or the Internet, the second edge router configured to generate a second tunnel between the second edge router and the second hub router, via the at least one of the second WAN and/or the Internet, wherein the engine is configured to route data traffic between the hub and said customer, along the first tunnel, based on a first performance threshold of the first tunnel and to switch the data traffic to the second tunnel, when the first tunnel fails to satisfy the first performance threshold.

2. The network of claim 1, wherein the engine is further configured to route the data traffic between the hub and the first edge router based on a preferred path;

and

wherein the first tunnel is the preferred path; and

wherein the engine is still further configured to switch the data traffic back to the first tunnel, after switching to the second tunnel, when the first tunnel no longer fails to satisfy the first performance threshold.

3. The network of claim 1, wherein the first performance threshold includes one of:

byte loss, packet loss, jitter, or latency.

4. The network of claim 1, wherein the first edge router is configured to encrypt the data traffic to be transferred, prior to transmitting the data traffic into the first tunnel;

and

wherein the first edge router is configured to encrypt the data traffic based on a certificate stored at the first edge router.

5. The network of claim 4, wherein each of the first edge router, the second edge router, the first hub router, and the second hub router are IPSec peers within said network.

6. The network of claim 1, wherein the engine is further configured to route different data traffic between the hub and said customer along the second tunnel, when the data traffic is routed along the first tunnel, thereby providing data traffic along two separate paths.

7. The network of claim 6, wherein a second performance threshold is associated with the second tunnel;

and

wherein the engine is further configured to switch the different data traffic from the second tunnel to the first tunnel, when the second tunnel fails to satisfy the second performance threshold.

8. The network of claim 7, wherein the engine is further configured to route the data traffic based on the first performance threshold and a class of an application associated with the data traffic;

and

wherein the engine is further configured to route the different data traffic between the hub and said customer along the second tunnel based on a class of an application associated with the different data traffic.

9. The network of claim 7, wherein the first and second edge routers are configured to transmit multiple probes along the first tunnel and along the second tunnel;

and

wherein the engine is further configured to determine a performance of the first tunnel relative to the first performance threshold based on the multiple probes transmitted along the first tunnel and to determine a performance of the second tunnel relative to the second performance threshold based the multiple probes transmitted along the second tunnel.

10. The network of claim 1, wherein the data center includes a certificate server coupled to the hub, the certificate server configured to:

issue a certificate to each of the first edge router and the first hub router, whereby the first edge router and the first hub router are able to verify one another, prior to the first tunnel being generated between the first edge router and the first hub router.

11. The network of claim 10, wherein the certificate server is configured to remove the certificate of first edge router from a directory of certificates, when the first edge router is decommissioned, such that the first and the second hub routers are unable to verify said certificate of the first edge router.

12. The network of claim 1, wherein the data traffic includes transaction data associated with at least one payment account transaction.

13. The network of claim 1, further comprising a third edge router coupled to at least one of said customer and/or a different customer, the third edge router also coupled to at least one of a third WAN and/or the Internet;

wherein the hub includes a third hub router coupled to the third WAN and/or the Internet;

wherein the third edge router is configured to generate a third tunnel between the third edge router and the third hub router, via the at least one of the third WAN and/or the Internet; and

wherein the engine is configured to switch the data traffic to one of the second tunnel and the third tunnel, when the first tunnel fails to satisfy the first performance threshold.

15. The network of claim 1, wherein the hub further includes at least one intrusion detection sensor (IDS) coupled to the first and second hub routers and configured to inspect one or more packets received by the hub to identify a signature of an attack.

16. A non-transitory computer readable storage media including computer executable instructions for routing data traffic in a payment network that, when executed by at least one processor, cause the at least one processor to:

determine a performance of a first path between a hub and a customer, the first path defined by an encrypted tunnel through a first wide area network (WAN) between the hub and a first edge router associated with the customer;

determine a performance of a second path between the hub and the customer, the second path defined by a tunnel, through one of a second different WAN and/or an Internet, between the hub and a second edge router associated with the customer;

initially route data traffic along the first path when the performance of the first path is within a first performance threshold;

initially route the data traffic along the second path, when the performance of the first path is not within the performance threshold, but the performance of the second path is within a second performance threshold; and

switch the data traffic from the first path to the second path when the data traffic is routed along the first path, but the performance of the first path is not within the performance threshold while the performance of the second path is within a second performance threshold.

17. The non-transitory media of claim 16, wherein the first performance threshold and the second performance threshold each includes a threshold for one of:

byte loss, packet loss, jitter, or latency.

18. The non-transitory media of claim 17, wherein the first performance threshold includes a first value when the data traffic is associated with a first application and a second different value when the data traffic is associated with a different application.

19. The non-transitory media of claim 16, wherein the computer executable instructions, when executed by the at least one processor, further cause the at least one processor to switch the data traffic from the second path to the first path when the data traffic is routed along the second path, but the performance of the first path is within the performance threshold.

20. The non-transitory media of claim 16, wherein the computer executable instructions, when executed by the at least one processor, further cause the at least one processor to:

initially route the data traffic along the first path when the performance of the first path is within a first performance threshold and the data traffic is associated with a first class of application; and

initially route the data traffic along the second path, when the performance of the second path is within the second performance threshold and the data traffic is associated with a second class of application.

21. A computer-implemented method for facilitating data transfers within a payment network, the method comprising:

determining, by a routing engine, a performance of a first path between a hub associated with a payment network data center and a customer, the first path defined by a first tunnel through a first wide area network (WAN) between the hub and a first edge router associated with the customer, the hub including the router;

determining, by the routing engine, a performance of a second path between the hub and the customer, the second path defined by a second tunnel through a second WAN between the hub and a second edge router associated with the customer;

causing, by the routing engine, a data traffic to be initially routed along the first path;

selecting a first performance threshold for the data traffic based on a class of application associated with the data traffic; and

switching, by the routing engine, the traffic to the second path, when the first path fails to satisfy the first performance threshold and the second path does not fail to satisfy the second performance threshold.