System and method for implementing application functionality within a network infrastructure

• US 9,185,185 B2
• Filed: 11/14/2013
• Issued: 11/10/2015
• 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
• Primary Examiner(s): LAZARO, DAVID R
• Application Number:
  US14/079,856
• Publication Number:
  US 20140074981A1
• Time in Patent Office: 726 Days
• Field of Search: 709/218, 709/224, 709/207, 709/240
• 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 system and method for implementing functionality within a network on behalf of first and second devices communicating with each other through the network. A front-end device is provided within the network that communicates data traffic with the first device. A back-end device is also implemented within the network and communicates data traffic with the second device. A communication channel couples the front-end device and the back-end device. Data traffic may be encoded into a different type or protocol for transport through the communication channel by the front-end device and back-end device. The front-end device and back-end device exchange quality of service information and may alter characteristics of the data traffic through the communication channel according to the quality of service information.

Claims

1. A method for transporting data between a first computing device and a second computing device through a limited bandwidth computer network comprising:

establishing at least one communication channel between a front-end and a back-end such that said first computing device is communicatively coupled with said second computing device via said at least one communication channel, wherein said front-end is associated with said first computing device and is configured to encode data packets of a first type into data packets of a second type and decode packets of said second type into packets of said first type, wherein said back-end is associated with said second computing device and is configured to encode data packets of said first type into data packets of said second type and decode packets of said second type into packets of said first type, and wherein at least one of the communication channels is configured to transport data between said front-end and said back-end in packets of said second type, said second type differing from said first type;

exchanging network quality of service information between said front-end and said back-end via one or more packets separate from said data packets of said second type;

encoding, at said front-end, data comprising packets of said first type generated by said first computing device by converting said data into one or more data packets of said second type;

transmitting said encoded data from said front-end to said back-end via said at least one communication channel configured to transport data in packets of said second type, wherein said exchanged quality of service information is utilized in said steps of encoding or transmitting;

decoding, at said back-end, said encoded data received from said front-end into data comprising packets of said first type for use by said second computing device.

2. The method in accordance with claim 1 further comprising controlling the rate at which said one or more data packets of a second type are transmitted through said at least one communication channel based on said quality of service information.

3. The method in accordance with claim 1 further comprising compressing said one or more data packets of a second type.

4. The method in accordance with claim 1 further comprising multiplexing said one or more packets of a first type to generate said one or more packets of a second type.

5. The method in accordance with claim 1, wherein said one or more data packets of a first type are TCP/IP packets and said one or more data packets of a second type are not TCP/IP packets.

6. The method in accordance with claim 1, wherein said front-end and back-end each comprise software.

7. The method in accordance with claim 1, wherein said one or more separate packets comprise data acknowledgement packets.

8. A method for transporting data from a first computing device to a second computing device through a limited bandwidth computer network comprising:

providing a front-end for association with said first computing device, said front-end comprising an interface to encode data packets of a first type into data packets of a second type and decode packets of said second type into packets of said first type, wherein said second type differs from said first type;

providing a back-end for association with said second computing device, said back-end comprising an interface to encode data packets of said first type into data packets of said second type and decode packets of said second type into packets of said first type;

establishing at least one communication channel coupling said front-end and said back-end wherein at least one of the communication channels is configured to transport data between said front-end and said back-end in one or more data packets of said second type;

exchanging network quality of service information between said front-end and said back-end via one or more packets separate from said data packets of said second type;

utilizing said front-end to encode data comprising packets of said first type generated by said first computing device by converting said data into one or more data packets of said second type;

transmitting said encoded data from said front-end to said back-end via said at least one communication channel configured to transport data in packets of said second type;

utilizing said back-end to decode said encoded data received from said front-end into data comprising packets of said first type for use by said second computing device.

9. The method in accordance with claim 8, wherein said first computing device comprises a client computer and said second computing device comprises a web server.

10. The method in accordance with claim 8, wherein said one or more data packets of a first type are TCP/IP packets and said one or more data packets of a second type are not TCP/IP packets.

11. The method in accordance with claim 8, wherein said front-end and back-end each comprise software.

12. The method in accordance with claim 8, wherein said encoding comprises compressing said packets of said first type.

13. The method in accordance with claim 8, wherein said quality of service information comprises time-based synchronization information.

14. The method in accordance with claim 8, wherein said one or more separate packets comprise data acknowledgement packets.

15. A method for transporting data from a client computing device to a response computing device through a limited bandwidth computer network comprising:

providing a front-end for association with said client computing device, said front-end comprising an interface to encode data packets of a first type into data packets of a second type and decode packets of said second type into packets of said first type, wherein said second type differs from said first type;

providing a response computing device having an associated back-end, said back-end comprising an interface to encode data packets of said first type into data packets of said second type and decode packets of said second type into packets of said first type;

in response to a request from said client computing device, establishing at least one communication channel coupling said front-end and said back-end wherein at least one of the communication channels is configured to transport data between said front-end and said back-end in one or more data packets of said second type;

transmitting, by said back-end, network quality of service information about at least one of said communication channels to said front-end via one or more packets separate from said data packets of said second type;

receiving at said back-end encoded data packets of said second type which were encoded by said front-end from packets of said first type into packets of said second type and transmitted from said front-end to said back-end; and

decoding said encoded data packets of said second type received from said front-end at said back-end into data comprising packets of said first type for use by said response computing device.

16. The method in accordance with claim 15, wherein said response computing device comprises a web server.

17. The method in accordance with claim 15 wherein said client computing device comprises an application.

18. The method in accordance with claim 15, wherein said one or more data packets of a first type are TCP/IP packets and said one or more data packets of a second type are not TCP/IP packets.

19. The method in accordance with claim 15, wherein said front-end and back-end each comprise software.

20. The method in accordance with claim 15, wherein said encoding comprises compressing said packets of said first type.

21. A method for transporting data between a first computing device and a second computing device through a computer network, said method comprising:

receiving, at said second computing device, a request to establish a communication channel with said first computing device;

in response to said request, establishing, at said second computing device, said communication channel between said second computing device and said first computing device, said communication channel configured to transport data that is encoded from a first type into a second type;

exchanging, via one or more packets separate from said data packets of said second type, quality of service information regarding said communication channel;

receiving, at said second computing device, data of said second type via said communication channel and decoding data of said second type into said first type for use by said second computing device; and

encoding, at said second computing device, data of said first type into data of said second type and transmitting said data of said second type to said first computing device via said communication channel, wherein at least one of said steps of encoding and transmitting is adjusted based at least in part on said quality of service information.

22. The method in accordance with claim 21, wherein said response computing device comprises a web server.

23. The method in accordance with claim 21, wherein said one or more data packets of a first type are TCP/IP packets and said one or more data packets of a second type are not TCP/IP packets.

24. The method in accordance with claim 21, wherein said front-end device and back-end each comprise software.

25. The method in accordance with claim 21, wherein said encoding from said first type to said second type comprises compressing said packets of said first type.

26. The method in accordance with claim 21, wherein said one or more separate packets comprise data acknowledgement packets.