Data redirection system and method therefor

• US 9,380,129 B2
• Filed: 04/05/2013
• Issued: 06/28/2016
• Est. Priority Date: 04/17/2000
• Status: Expired due to Term

• Current Assignee: Sons of Innovation LLC
• Original Assignee: Circadence Corporation
• Inventors: Vange, Mark, Plumb, Mark, Kouts, Michael, Wilson, Glenn Sydney, Chekhovtsov, Alexandr
• Primary Examiner(s): LAZARO, DAVID R
• Application Number:
  US13/857,817
• Publication Number:
  US 20150019753A1
• Time in Patent Office: 1,180 Days
• Field of Search: 709/203, 709/218, 709/238
• US Class Current: 1/1
• CPC Class Codes: G06F 2209/5021 Priority
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: G06F 9/5088 involving task migration
• CPC Class Codes: H04L 45/14 Routing performance; Theoretical aspects
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/193 at the transport layer, e.g. TCP related
• CPC Class Codes: H04L 47/24 Traffic characterised by specific attributes, e.g. priority or QoS
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/1408 by monitoring network traffic monitoring network traffic per se H04L43/00
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 63/1458 Denial of Service
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 Access to distributed or replicated servers, e.g. using brokers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 : based on network conditions
• CPC Class Codes: H04L 67/1021 : based on client or server locations
• CPC Class Codes: H04L 67/1029 : using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1031 : Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
• CPC Class Codes: H04L 67/1034 : Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/142 : Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/303 : Terminal profiles
• CPC Class Codes: H04L 67/561 : Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/563 : Data redirection of data network streams
• CPC Class Codes: H04L 67/564 : Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/565 : Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5681 : Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04L 67/5682 : Policies or rules for updating, deleting or replacing the stored data
• CPC Class Codes: H04L 67/61 : taking into account QoS or priority requirements
• CPC Class Codes: H04L 69/16 : Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04W 8/04 : Registration at HLR or HSS [Home Subscriber Server]
• CPC Class Codes: Y10S 707/99944 : Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 : Object-oriented database structure processing

Abstract

A data redirection system and method comprises a first and second redirector in one or more embodiments. The first redirector may receive and respond to requests for a network service by redirecting a client'"'"'s request to the second redirector. The second redirector may receive and respond to the redirected request by sending a network address of a gateway. The gateway may provide an enhanced communication link with a network resource providing the network service. In this manner, communications used to provide the network service may be redirected to the enhanced communication link. The requests for a network service and responses to the requests will typically be communicated over a standard communication link.

Claims

1. A data redirection system comprising:

at least one front-end gateway communicatively linked to a server, the at least one front-end gateway supporting communications with said server via at least one enhanced communication link with said front-end gateway; and

at least one redirector, said redirector configured to receive a redirection request from said server relative to a request from a client directed to a network address corresponding to said server via a second communication link to said server, said second communication link not including said at least one front-end gateway, said redirector configured, in response to said redirection request, to respond to said redirection request by redirecting said client to a network address of said at least one front-end gateway, whereby communications between said client and said server occur via said at least one enhanced communication link with said at least one front-end gateway rather than said second communication link.

2. The system of claim 1 wherein said at least one front-end gateway is configured to establish a communication link between said server and said client in response to said client being redirected to said front-end gateway, said communication link comprising said enhanced communication link between said front-end gateway and said client.

3. The system of claim 1, wherein said at least one enhanced communication link utilizes a non-standard Internet protocol for communication.

4. The system of claim 1 wherein the at least one redirector is configured to respond with said network address of said at least one front-end gateway through other than said at least one enhanced communication link.

5. The system of claim 1 wherein the at least one redirector is configured to select a front-end gateway from the at least one front-end gateway based on a quality of service metric for at least one of the enhanced communication links provided by said front-end gateways, wherein the at least one redirector responds with the network address of the selected front-end gateway.

6. The system of claim 1 wherein the at least one redirector is configured to select a front-end gateway from the at least one front-end gateway based on a relative distance between each of the front-end gateways and a location of said client, wherein the at least one redirector responds with the network address of the selected front-end gateway.

7. The system of claim 1 wherein the at least one redirector is configured to select a front-end gateway from the at least one front-end gateway based on an identification of the type of client application making said client request, wherein the at least one redirector respond with the network address of the selected front-end gateway.

8. A method of data redirection comprising the steps of:

providing at least one front-end gateway communicatively linked to a server;

providing at least one redirector;

receiving at said at least one redirector a redirection request from said server relative to a request from a client directed to a network address corresponding to said server via a first communication link to said server, said first communication link not including said at least one front-end gateway;

transmitting from said at least one redirector a redirection response for redirecting said client, said redirection response comprising a network address of said at least one front-end gateway; and

establishing a second communication link between said server and said client via said at least one front-end gateway in response to a redirected request by said client to said network address of said at least one front-end gateway, said second communication link comprising at one enhanced communication link with said at least one front-end gateway.

9. The method in accordance with claim 8 wherein said at least one enhanced communication link utilizes a non-standard Internet protocol.

10. The method in accordance with claim 8 wherein said at least one redirector acts as a domain name resolver.

11. The method in accordance with claim 8 further comprising the step of said redirector selecting said a front-end gateway from said at least one front-end gateway based upon one or more metrics and wherein said redirection response comprises a network address of said selected front-end gateway.