# US 2011/0238860 A1 · System and method for implementing application functionality within a network infrastructure

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2011/0238860 A1
- Document ID: US20110238860A1
- Status: Published application
- Kind: A1
- Application number: 13/156,120
- Filed: 2011-06-08
- Published: 2011-09-29
- Earliest claimed: 2000-04-17
- Assignees: Circadence Corporation
- Inventors: Mark Vange; Marc Plumb; Michael Kouts; Glenn Sydney Wilson
- Web page: https://patentgrep.com/patent/US20110238860A1

## CPC

- G06F 9/5027: {the resource being a machine, e.g. CPUs, Servers, Terminals}
- G06F 9/505: {considering the load}
- G06F 9/5055: {considering software capabilities, i.e. software resources associated or available to the machine}
- G06F 9/5088: {involving task migration}
- H04L 45/14: {Routing performance; Theoretical aspects}
- H04L 47/10: Flow control; Congestion control
- H04L 47/193: at the transport layer, e.g. TCP related
- H04L 47/24: Traffic characterised by specific attributes, e.g. priority or QoS
- H04L 61/4511: using domain name system [DNS]
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)}
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- H04L 63/1458: {Denial of Service}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/1001: for accessing one among a plurality of replicated servers
- H04L 67/1008: based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30)
- H04L 67/101: based on network conditions
- H04L 67/1021: based on client or server locations
- H04L 67/1029: using data related to the state of servers by a load balancer
- H04L 67/1031: Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
- H04L 67/1034: Reaction to server failures by a load balancer
- H04L 67/142: Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
- H04L 67/303: Terminal profiles
- H04L 67/561: Adding application-functional data or data for application control, e.g. adding metadata
- H04L 67/563: Data redirection of data network streams
- H04L 67/564: Enhancement of application control based on intercepted application data
- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L 67/5681: Pre-fetching or pre-delivering data based on network characteristics
- H04L 67/5682: Policies or rules for updating, deleting or replacing the stored data
- H04L 67/61: taking into account QoS or priority requirements
- H04L 69/16: Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L 69/329: in the application layer [OSI layer 7]
- H04W 8/04: Registration at HLR or HSS [Home Subscriber Server]
- G06F 2209/5021: Priority
- H04L 63/0272: {Virtual private networks}
- H04L 67/10015: {Access to distributed or replicated servers, e.g. using brokers}
- Y10S 707/99944: Object-oriented database structure
- Y10S 707/99945: Object-oriented database structure processing
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## 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

### Claim 1

A method for transporting data from a first device to a second device through a limited bandwidth computer network comprising:
providing a front-end device comprising an interface to communicate data with at least one first device, said data comprising one of more data packets of a first type;
providing a back-end device comprising an interface to communicate data with at least one second device, said data comprising one or more data packets of said first type;
establishing at least one communication channel coupling the front-end device and the back-end device wherein at least one of the communication channels is configured to transport data between said at least one front-end device and said at least one back-end device in one or more data packets of a second type, which second type differs from said first type;
exchanging network quality of service information between said front-end and said back-end over at least one of said communication channels;
receiving said data comprising one or more data packets of said first type from said first device at said front-end device;
encoding said data received by said front-end device from said first computer by converting said data into one or more data packets of said second type, wherein said step of encoding comprises changing characteristics of said data based at least in part on said exchanged quality of service information;
transmitting said encoded data from said front-end device to said back-end device over said at least one communication channel configured to transport data in packets of said second type;
decoding said encoded data received from said front-end device at said back-end device into data comprising packets of said first type; and
transmitting said decoded data from said back-end device to said second device.

### Claim 2 (depends on 1)

The method of 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.

### Claim 3 (depends on 1)

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

### Claim 4 (depends on 1)

The method of 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.

### Claim 5 (depends on 1)

The method of 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.

### Claim 6 (depends on 1)

The method of claim 1, wherein said front-end device and back-end device each comprise software.

### Claim 7

A system for transporting data from a first device to a second device through a limited bandwidth computer network comprising:
a front-end device comprising an interface to communicate data with at least one first device, said data comprising one of more data packets of a first type;
a back-end device comprising an interface to communicate data with at least one second device, said data comprising one or more data packets of said first type;
at least one communication channel coupling the front-end device and the back-end device wherein at least one of the communication channels is configured to transport data between said at least one front-end device and said at least one back-end device in one or more data packets of a second type, which second type differs from said first type, wherein said front-end device and said back-end device exchange network quality of service information between said front-end and said back-end over at least one of said communication channels;
wherein said front-end device encodes said data received from said first computer by converting said data into one or more data packets of said second type, said step of encoding comprising changing characteristics of said data based at least in part on said exchanged quality of service information;
wherein said back-end device receives and decodes said encoded data from said front-end device into data comprising packets of said first type for use by said at least one second device.

### Claim 8 (depends on 7)

The system of claim 7, wherein said front-end device is configured to transmit said encoded data from said front-end device to said back-end device over said at least one communication channel.

### Claim 9 (depends on 7)

The system of claim 7, wherein said back-end device is configured to decode said encoded data received from said front-end device into data comprising packets of said first type.

### Claim 10 (depends on 7)

The system of claim 7, wherein said back-end device is configured to transmit said decoded data to said second device.

### Claim 11 (depends on 7)

The system of claim 7, wherein the front-end device is configured to control a rate at which said encoded data is transmitted through said at least one communication channel based on said quality of service information.

### Claim 12 (depends on 7)

The system of claim 7, wherein the front-end device is configured to compress said one or more data packets of a second type to generate said encoded data and said changing characteristic comprises a compression level of said data packets.

### Claim 13 (depends on 7)

The system of claim 7, wherein the front-end device is configured to multiplex said one or more packets of a first type to generate said encoded data and said changing characteristic comprises multiplexing said data.

### Claim 14 (depends on 7)

The system of claim 7, 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.

### Claim 15 (depends on 7)

The system of claim 7, wherein said front-end device and said back-end device comprise software.

### Claim 16

A system for transporting data from a first device to a second device through a limited bandwidth computer network comprising:
a front-end device comprising an interface to communicate data with at least one first device, said data comprising one of more data packets of a first type, said front-end device configured to encode data of said first type into one or more data packets of a second type;
a back-end device comprising an interface to communicate data comprising one or more data packets of said first type with at least one second device, said back-end device configured to decode said encoded data into one or more data packets of a first type;
at least one communication channel coupling the front-end device and the back-end device wherein at least one of the communication channels is configured to transport data between said front-end device and said back-end device in one or more data packets of said second type, said second type distinct from said first type;
wherein said front-end device and said back-end device are configured to exchange network quality of service information over at least one of said communication channels, and said front-end device is configured to change characteristics of said data from said at least one first device during encoding based at least in part on said exchanged quality of service information

### Claim 17 (depends on 16)

The system of claim 16, wherein said front-end device is configured to transmit said encoded data from said front-end device to said back-end device over said at least one communication channel.

### Claim 18 (depends on 16)

The system of claim 16, wherein said back-end device is configured to decode said encoded data received from said front-end device into data comprising packets of said first type, and to transmit said decoded data to said second device.

### Claim 19 (depends on 16)

The system of claim 16, wherein the front-end device is configured to control a rate at which said encoded data is transmitted through said at least one communication channel based on said quality of service information.

### Claim 20 (depends on 16)

The system of claim 16, wherein the front-end device is configured to compress said one or more data packets of a second type to generate said encoded data.

### Claim 21 (depends on 16)

The system of claim 16, wherein the front-end device is configured to multiplex said one or more packets of a first type to generate said encoded data.

### Claim 22 (depends on 16)

The system of claim 16, 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.
