System and method for implementing application functionality within a network infrastructure

• US 7,975,066 B2
• Filed: 02/03/2006
• Issued: 07/05/2011
• Est. Priority Date: 04/17/2000
• Status: Expired due to Fees

• Current Assignee: Sons of Innovation LLC
• Original Assignee: Circadence Corporation
• Inventors: Plumb, Marc, Wilson, Glenn Sydney, Kouts, Michael, Vange, Mark
• Primary Examiner(s): LAZARO, DAVID R
• Application Number:
  US11/346,767
• Publication Number:
  US 20060129697A1
• Time in Patent Office: 1,978 Days
• Field of Search: 709/233, 709/236, 370/229
• US Class Current: 709/233
• 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 system and method for implementing functionality within a network on behalf of first and second computers communicating with each other through the network. A front-end computer is provided within the network having an interface for communicating data traffic with the first computer. A back-end computer is also implemented within the network having an interface for communicating data traffic with the second computer. A communication channel couples the front-end computer and the back-end computer. Data traffic is encoded over the communication channel in a first process in the front-end computer. Data traffic is also encoded over the communication channel in a second process in the back-end computer, wherein the first process and the second process implement compatible semantics.

Claims

1. A data transport device for implementing a data transport mechanism comprising:

a hardware interface for communicating one or more TCP packets with a plurality of data transport links; and

one or more processors providing;

a first unit configured to reduce the one or more TCP packets from the plurality of data transport links into data of one or more sizes suitable to multiplex the data for transport through a shared-bandwidth channel;

one or more enhanced UDP packets configured to store and transport the multiplexed data through the shared-bandwidth channel using a connectionless protocol; and

a second unit configured to encode multiplexed data from the first unit into a payload portion of the one or more enhanced UDP packets and apply rate control to the shared-bandwidth channel, wherein the second unit encodes the multiplexed data at a rate based on one or more quality of service metrics for the shared-bandwidth channel.

2. The data transport device of claim 1, wherein the first unit comprises a first set of machine readable code stored on the data transport device.

3. The data transport device of claim 1, wherein the second unit comprises a second set of machine readable code stored on the data transport device.

4. The data transport device of claim 1, wherein the first unit is a blender.

5. The data transport device of claim 1 further comprising a second hardware interface for communicating multiplexed data from the first unit, the second hardware interface connected to the shared-bandwidth channel.

6. The data transport device of claim 1, wherein the first unit is also configured to process multiplexed data from the shared-bandwidth channel to separate the multiplexed data into one or more data streams.

7. The data transport device of claim 1, wherein the second unit is also configured to decode one or more enhanced packets whereby decoded data from the second unit is communicated through one or more of the plurality of data transport links by the one or more processors.

8. The data transport device of claim 1, wherein the second unit is configured to claim additional bandwidth of the shared-bandwidth channel until one or more of the one or more enhanced UDP packets are unacknowledged.