US20030123394A1 - Flow control between performance enhancing proxies over variable bandwidth split links - Google Patents

Flow control between performance enhancing proxies over variable bandwidth split links Download PDF

Info

Publication number
US20030123394A1
US20030123394A1 US10/292,901 US29290102A US2003123394A1 US 20030123394 A1 US20030123394 A1 US 20030123394A1 US 29290102 A US29290102 A US 29290102A US 2003123394 A1 US2003123394 A1 US 2003123394A1
Authority
US
United States
Prior art keywords
intermediate
tcp
data
pep
intermediate device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/292,901
Inventor
Jason Neale
Andrew Pether
Abdul-Kader Mohsen
Guy Begin
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ADVANTECH SATELLITE NETWORKS Inc
Original Assignee
EMS Technologies Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US33360801P priority Critical
Application filed by EMS Technologies Inc filed Critical EMS Technologies Inc
Priority to US10/292,901 priority patent/US20030123394A1/en
Assigned to EMS TECHNOLOGIES, INC. reassignment EMS TECHNOLOGIES, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NEALE, JASON, BEGIN, GUY, MOHSEN, ABDUL-KADER, PETHER, ANDREW M.
Publication of US20030123394A1 publication Critical patent/US20030123394A1/en
Assigned to SUNTRUST BANK reassignment SUNTRUST BANK SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: EMS TECHNOLOGIES, INC.
Assigned to EMS TECHNOLOGIES CANADA, LTD. reassignment EMS TECHNOLOGIES CANADA, LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: EMS TECHNOLOGIES, INC.
Assigned to ADVANTECH SATELLITE NETWORKS INC. reassignment ADVANTECH SATELLITE NETWORKS INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: EMS TECHNOLOGIES CANADA, LTD.
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/16Transmission control protocol/internet protocol [TCP/IP] or user datagram protocol [UDP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/14Relay systems
    • H04B7/15Active relay systems
    • H04B7/185Space-based or airborne stations; Stations for satellite systems
    • H04B7/18578Satellite systems for providing broadband data service to individual earth stations
    • H04B7/18582Arrangements for data linking, i.e. for data framing, for error recovery, for multiple access
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. van Duuren system ; ARQ protocols
    • H04L1/1829Arrangements specific to the receiver end
    • H04L1/1832Details of sliding window management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. van Duuren system ; ARQ protocols
    • H04L1/1829Arrangements specific to the receiver end
    • H04L1/1848Time-out mechanisms
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. local area networks [LAN], wide area networks [WAN]
    • H04L12/2854Wide area networks, e.g. public data networks
    • H04L12/2856Access arrangements, e.g. Internet access
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/02Communication control; Communication processing contains provisionally no documents
    • H04L29/06Communication control; Communication processing contains provisionally no documents characterised by a protocol
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/14Flow control or congestion control in wireless networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/19Flow control or congestion control at layers above network layer
    • H04L47/193Flow control or congestion control at layers above network layer at transport layer, e.g. TCP related
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/29Using a combination of thresholds
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/30Flow control or congestion control using information about buffer occupancy at either end or transit nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/32Packet discarding or delaying
    • H04L47/323Discarding or blocking control packets, e.g. ACK packets
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic regulation in packet switching networks
    • H04L47/10Flow control or congestion control
    • H04L47/36Evaluation of the packet size, e.g. maximum transfer unit [MTU]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/04Network-specific arrangements or communication protocols supporting networked applications adapted for terminals or networks with limited resources or for terminal portability, e.g. wireless application protocol [WAP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/16Transmission control protocol/internet protocol [TCP/IP] or user datagram protocol [UDP]
    • H04L69/161Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/16Transmission control protocol/internet protocol [TCP/IP] or user datagram protocol [UDP]
    • H04L69/163Adaptation of TCP data exchange control procedures
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/16Transmission control protocol/internet protocol [TCP/IP] or user datagram protocol [UDP]
    • H04L69/165Transmission control protocol/internet protocol [TCP/IP] or user datagram protocol [UDP] involving combined use or selection criteria between TCP and UDP protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/16Transmission control protocol/internet protocol [TCP/IP] or user datagram protocol [UDP]
    • H04L69/166IP fragmentation or TCP segmentation aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. van Duuren system ; ARQ protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32High level architectural aspects of 7-layer open systems interconnection [OSI] type protocol stacks
    • H04L69/322Aspects of intra-layer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/326Aspects of intra-layer communication protocols among peer entities or protocol data unit [PDU] definitions in the transport layer, i.e. layer four
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32High level architectural aspects of 7-layer open systems interconnection [OSI] type protocol stacks
    • H04L69/322Aspects of intra-layer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329Aspects of intra-layer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer, i.e. layer seven
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management, e.g. wireless traffic scheduling or selection or allocation of wireless resources
    • H04W72/04Wireless resource allocation
    • H04W72/044Wireless resource allocation where an allocation plan is defined based on the type of the allocated resource
    • H04W72/0453Wireless resource allocation where an allocation plan is defined based on the type of the allocated resource the resource being a frequency, carrier or frequency band
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/06Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04Large scale networks; Deep hierarchical networks
    • H04W84/06Airborne or Satellite Networks

Abstract

The invention provides a method and system for dealing with the flow of data between one Performance Enhancement Proxy and another in the context of split links for TCP over satellite performance improvement. The environment according to the invention may include one or more intermediate nodes experiencing variable latency and bandwidth allocations. The method and system manage the data flow to ensure bandwidth fairness between competing TCP/IP connections, prevention of PEP receiver buffer overflow and near 100% usage of the available satellite bandwidth without the need for conventional TCP/IP ACK driven probing algorithms. The near 100% usage of capacity being achieved, in part, through PEP to intermediate node message exchange.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application claims priority to U.S. Provisional Application No. 60/333,608 to Jason D. Neale et. al., entitled “Performance Enhancing Proxies for Satellite Transmission Control Protocols,” filed on Nov. 13, 2001.[0001]
  • BACKGROUND OF THE INVENTION
  • 1. Field of the Invention [0002]
  • This invention relates to data telecommunications satellites, and more specifically to the use of hardware and/or software, referred to as Performance Enhancing Proxies (PEPs), to optimize the performance of the Transmission Control Protocol (TCP) over satellite links with varying bandwidth. [0003]
  • 2. Description of Related Art [0004]
  • The Internet is a world-wide computer super-network, which is made up of a large number of component networks and their interconnections. Computer networks may consist of a wide variety of connected paths or network links serving to transport user information in the form of data between a diverse array of computer end systems. Different network links are more or less suitable for different network requirements. For example, a fiber optic cable typically provides a high bandwidth, low per bit cost, low error rate and low delay point-to-point network link. Alternatively, for example, a satellite link typically provides a lower bandwidth, higher per bit cost, higher error rate and longer delay point-to-multi-point network link. The wide variety of links and thus link characteristics encountered on the Internet or other private Internet Protocol (IP) based networks have a variety of effects on the behavior of protocols in the IP suite. [0005]
  • IP primarily provides the routing functionality for packets (bits or bytes of data) over a network. It acts at the network layer to direct packets from their sources to their destinations. Transmission Control Protocol (TCP) is the reliable transport layer protocol of the IP suite of protocols and, as such, layers on top of IP, providing reliability to applications and building on IP's unreliable datagram (packet) service. TCP underlies the vast majority, estimated to be around 90%, of all the traffic on the Internet. TCP supports the World Wide Web (WWW), electronic mail (email) and file transfers, along with other common applications. TCP was introduced in 1981 and since then has evolved in many ways, but today TCP still provides reliable and largely efficient service over a wide variety of links as evidenced by its omnipresent nature. However, there are a variety of conditions under which TCP may perform below expectations, its use with geosynchronous satellite links being an example. In response to the established use of TCP and also of certain link types, such as satellite, which are not ideal for TCP, Performance Enhancing Proxies (PEPs) were introduced. [0006]
  • In any point-to-point communications system, such as PEP to PEP, flow control between the two elements is important to prevent starvation or over-flow of data in any other Intermediate Device (such as the Terminal) as well as the receiving point. For the purposes of describing the invention, a PEP shall be described as an Intermediate Node between the endpoints of a connection, and any network element between the PEPs, such as a Satellite Gateway, Satellite or Satellite Terminal, shall be described as an Intermediate Device. Furthermore, a connection refers to an end-to-end connection between a client and a server which is broken up into three connection segments, client to PEP, PEP to PEP and PEP to Server, such that the client or server remain largely aware of the splitting. Starvation of data implies inefficient use of available communications capacity, and overflow of data implies packet loss and retransmissions of data. Moreover, where the point-to-point communications system includes an intermediate device that is required to request bandwidth based on the amount of data in its queue, then ensuring the queue is adequately provisioned guarantees that capacity requests will be made. [0007]
  • Ensuring any particular intermediate device (such as the Terminal) between the two points (PEPs) is accurately supplied with an appropriate amount of data is difficult if the amount of bandwidth capacity allocated to the device is constantly changing. However a bandwidth-on-demand satellite system scheme will naturally change the allocated capacity to a given terminal (based on, but not limited to, Traffic conditions and Quality of Service (QoS) agreements). [0008]
  • TCP performance is typically degraded to some extent in terms of lowered throughout and link utilization by, but not limited to, the following link characteristics; long delay, high bandwidth, high error rate, link asymmetry and link variability, all of which may be encountered on satellite and similar links. [0009]
  • PEPs may function as one or more Intermediate Nodes or pieces of software placed in the end-to-end path that suffers TCP performance degradation. PEP units may, for example, surround a satellite link. PEPs modify the traffic flow to attempt to alleviate the issues of TCP traffic on a specific link. PEPs may use many methods either alone or in concert to enhance performance. [0010]
  • A type of PEP, known as a distributed, connection splitting PEP, is commonly chosen due to that fact that it allows for the use of a proprietary protocol across the satellite link. This protocol can then be chosen or designed to mitigate problems specific to the link. A distributed connection splitting PEP uses more than one PEP in an end-to-end connection, most commonly, two PEPs are used, although the invention can be applied to systems using greater number of PEPs with the FP protocol of this invention. If two PEP devices are used, the end-to-end connection may be split into 3 connection segments. The end connections must remain TCP for compatibility, but the inter-PEP connection may be any protocol. Several protocols are available for use on the satellite link that provide improved performance over that of TCP. Examples of these protocols are Xpress Transport Protocol (XTP), Satellite Transport Protocol (STP), Space Systems Control Protocol Suite—Transport Protocol (SSCPS-TP) or even nonstandard modified TCP. [0011]
  • Current versions of TCP use a window mechanism and acknowledgement (ACK) driven algorithms, such as slow-start and congestion-avoidance algorithms, to manage the flow of data from the sender to the receiver to mitigate the effects of congestion and prevent over-flow of the receiver's buffers. These algorithms often mistake transmission errors as congestion and fail to fully-supply the satellite link with data. Although the TCP window-scaling option helps with the later and fast-retransmission/fast-recovery help with the former, the overall link usage often remains well below the available capacity. The aforementioned satellite protocols and PEPs address some of these problems by facilitating larger windows, discriminating between congestion losses and in some cases making use of link rate knowledge (where that rate is constant). However, all of the PEP solutions use some form of capacity probing procedure (akin to a slow-start technique) and thus are unable to immediately employ the full link capacity without fear of losses (due to packet discard at an Intermediate Device). More importantly, none of the other solutions are able to fully supply a variable bandwidth and/or latency link for the duration of a TCP transfer. Additionally, they are unable to communicate directly with Intermediate Devices, relying instead on PEP-to-PEP messages to determine capacity, with the inevitable reduction in throughput associated with a satellite round-trip delay message exchange. As a solution to this problem, the method and system described in this invention facilitate a near 100% usage of link capacity for the entire duration of the PEP-to-PEP transfer without the risk of packets being discarded or receiver buffer-overflow. [0012]
  • In terms of the sharing of resources to guarantee fairness while not limiting hungry connections when satellite resources permit, conventional TCP merely dedicates a buffer per end-to-end connection and manages those connections independently. Thus TCP is unable to quickly make use of free capacity for hungry connections when other connections start to slowly supply the link, relying instead on a slow-ramp through congestion avoidance. Indeed, the overall throughput is often reduced as a result of a lack of acknowledgments. Although many of the PEPs and other protocols are able to prevent the flow from diminishing because of a lack of ACKs, none of them include a flow fairness technique to ensure 100% supply to the link and fairness (assuming TCP/IP traffic supplies allow). Herein, fairness is defined as the ideal condition where each connection has an equal share of the link, as long as it has enough traffic to use this portion of the resources. If a connection is running more slowly, its unused share of capacity will be provided for the use of all other connections, in a fair way. [0013]
  • SUMMARY OF THE INVENTION
  • The invention provides methods and systems for the management of the flow of data between two PEPs where the link conditions, in terms of bandwidth resources and latency, are changing in relation to network traffic conditions and QoS profiles, among other things. This changing bandwidth condition is characteristic of a Bandwidth on Demand (BoD) satellite communications system. [0014]
  • The invention further provides systems and methods that enable the fair distribution of satellite resources between a number of competing TCP connections at a PEP, while facilitating the full usage of the available satellite bandwidth by accurately supplying a particular Intermediate Device with sufficient data and preventing the receiving PEP's buffers from overflowing. Additionally, the distribution process according to the invention prevents slow running TCP connections, at the receiver end, from unfairly being allocated excess link capacity whilst allowing for full usage of bandwidth at the transmitting PEP's end by distributing unused satellite capacity among hungry TCP connections. [0015]
  • The methods and systems in accordance with the invention allow satellite resources to be fairly shared between competing TCP connections while also facilitating the full use of the link capacity by hungry connections should resources allow. The overall flow strategy in accordance with the invention allows the fair sharing or satellite link resources between connections while achieving near 100% usage and not over-flowing the receiving end's buffers. [0016]
  • The invention provides satellite communication systems where the bandwidth between two PEPs is controlled by a Gateway and is subject to wide variations due to competing traffic, among other things. As an example, communication between two PEPs relies on an Intermediate Device (Terminal), forward and return satellite links and a Gateway. In such a network, numerous terminals could be operating with the Gateway, each terminal receiving data packets from a PEP, then requesting and receiving bandwidth allocations from the Gateway. Such a Bandwidth-on-Demand (BoD) scheme typically facilitates a fast variation in bandwidth allocation and substantial latency changes dependent on the number of terminals in operation, their traffic supplies and guaranteed quality of service agreements. [0017]
  • Thus, the invention provides for improved performance of TCP over a satellite link or other large bandwidth delay network. Moreover, the invention provides for the management of the flow of traffic from a PEP to an Intermediate Device in a satellite environment where the bandwidth and latency are fluctuating. This may be accomplished in part by replacing TCP with a new transport protocol, the EMS (proprietary) Flight Protocol (FP), over the wireless satellite link only and maintaining TCP connections over the terrestrial portions of the end-to-end connection. TCP performance over GEO links is traditionally very poor from a user perspective in terms of transfer time and throughput for web browsing and file transfer among other applications relying on a TCP transport layer. [0018]
  • The above aspects of the invention are achieved by addressing and in part accessing the characteristics of the satellite link, including available capacity, and treating a lack of acknowledgements from the receiver as errors and not congestion. The PEP invention described herein will improve the throughput and transfer times and achieve a higher utilization factor of the assigned link rates.[0019]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention. Together with the written description, these drawings serve to explain the principles of the invention. In the drawings: [0020]
  • FIG. 1 is an illustration showing the overall satellite network with the location of the PEPs, as exemplary of connections and equipment in a distributed, connection splitting PEP deployment; [0021]
  • FIG. 2 illustrates the end-to-end satellite protocol stacks for TCP/IP utilizing the PEPs; and [0022]
  • FIG. 3 shows an algorithm and procedures for making a PEP-to-intermediate device (Terminal) communication, and in particular, steps in making a query of the Terminal's buffer status and determining the amount of data to be sent to the Terminal.[0023]
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • The invention is described in the context of a bi-directional transfer of data between a client and a server over a communications link consisting of both terrestrial segments and up and down segments, or links, over satellite, as generally shown in FIG. 1. It is important to note that the use of a satellite is merely illustrative of one embodiment of the invention and that the invention is applicable to both terrestrial hard-wired and terrestrial wireless applications. [0024]
  • The PEP component consists of two main parts: a TCP Emulator (TCP*) and a Flight Protocol (FP) Processor. While the operation of inventive components and methods of the invention are different depending on whether they are functioning in a Receive or a Transfer mode, i.e., depending on whether the data is being sent by the client or server, it is to be understood that the components and methods are reciprocal. A description of the operation for sending data, for example, from a client to a server is essentially equivalent to data being sent in the reverse direction, from server to client, in this respect the PEP system is reciprocal. FIG. 2 presents an illustration generally showing where the TCP* and FP layers sit in a conventional stack. The PEP is designed to be used in pairs, one on each terrestrial side of the satellite link. [0025]
  • The TCP Emulator (TCP*) is present in the transmit and receive PEPs and behaves as if it is a TCP connection endpoint. The TCP Emulator transparently interrupts the TCP connection going from the client to the server (or server to client) and acts as a TCP endpoint. It translates TCP traffic into FP traffic, the inventive transport protocol used over the satellite link (or other large bandwidth * delay network) between the two PEPs. PEP1 is the first PEP in the transfer chain (the Transmitter) and PEP2 is the second PEP in the transfer chain (the Receiver), whichever direction of packet is being discussed. The names PEP1 and PEP2 do not necessarily apply to the terminal-side or gateway-side PEPs respectively. The role of the TCP emulator depends on the function of the PEP. In the Transmit PEP, the TCP Emulator converts TCP segments into FP packets. In the Receive PEP, the TCP Emulator (TCP*) receives the FP packets, converts them back to standard TCP packets and transmits them over a new TCP connection to their final destination: the communication's endpoint. The client and the server are the communication system's endpoints or end users. [0026]
  • With the introduction of the two PEPs, the standard connection going from the server to the client will be replaced with the following three connections: [0027]
  • 1. A TCP connection from the client to the first, terminal, PEP (PEP1) [0028]
  • 2. A FP connection going from PEP1 to PEP2 (gateway PEP) [0029]
  • 3. A TCP connection from PEP2 to the server [0030]
  • The TCP Emulator (TCP*) emulates a standard TCP connection between the external end user, the client and server, and converts TCP/IP packets into Flight Protocol (FP) packet ‘shells’. The TCP Emulator filters TCP/IP packets entering from the outside world (the real end points) and emulates the TCP behavior of the destination transport layer. This behavior includes the TCP three-way handshake, acknowledgements, flow control, re-transmissions and all other TCP functionality. It also manages the flow of traffic to the Flight Protocol Processor section of the PEP. [0031]
  • The Flight Protocol FP is the inventive transport protocol that is used over the satellite link between the transmit and receive PEPs that are connected, respectively, to a terrestrial/satellite gateway and a user terminal. The FP is optimized to operate over this link by not using the TCP Slow Start and Congestion Avoidance algorithms, and instead, utilizes the full available satellite capacity immediately and consistently throughout the lifetime of the connection, also improving link utilization efficiency. This throughput utilization is achieved despite bandwidth fluctuations, prevalent in a BoD satellite network, by linking the PEP with the Intermediate Device experiencing the said fluctuations. Other future protocols may also be used, the FP should be considered as merely one current example of such suitable protocols. While this invention is described with reference to the FP, it is to be understood that the invention is not limited to this protocol. It can equally be used with and applied to a variety of other protocols. [0032]
  • The FP also avoids the delays associated with the TCP three-way handshake by not using a pre-data handshaking (negotiation) mechanism of any form. Instead, the FP connection Initiator simply informs the remote entity that a new connection has been created and then immediately begins to send data. The assumption is that the FP connection will be created successfully unless evidence demonstrates to the contrary. The alternative rationale, as implemented by conventional TCP, assumes failure until success is explicitly signaled. This feature of the FP of this invention removes an additional one-off delay (per connection) that is significant for very small files or short duration transfers such as those typical of current web pages that at present comprise the greatest volume of Internet traffic. This setup mechanism may be used with either a half or full duplex connection allowing for bi-directional data communication on a single connection or alternatively with two associated simplex connections. [0033]
  • The invention involves the principle of an Intermediate Device breaking an end-to-end TCP and splitting the connection into a TCP/IP protocol and TCP/IP connections by the use of PEPs; and then managing the flow of data between the PEP and the Intermediate device (Terminal) by knowledge of the status of the Terminal queue. One of ordinary skill in the art will recognize other variations, modifications, and alternatives. [0034]
  • The principle involves the PEP sending sufficient data to at least partially or fully fill the Terminal queue (to a pre-defined level), and after adequate time for some of the data to be transmitted, checking the status of the Terminal, using some protocol, and then re-filling the Terminal queue to the previous level. This method could be as simple as the PEP sending regular SNAP get messages to the terminal MIB, the terminal sending SNAP traps when its queue reaches a certain level or in the case where the PEP and Terminal are co-located in the same device some form of direct linkage. The flow of data from the PEP to the Terminal could be made more accurate by the PEP having knowledge of the current and future bandwidth allocations of the intermediate device (Terminal). [0035]
  • Beyond the management of the flow of data from the PEP to the intermediate device two other functions are key to the successful flow of data from the PEP to PEP; firstly not overflowing the receiver's window and secondly the fair distribution of the satellite bandwidth between competing TCP connections. The former is dealt with by the use of conventional window mechanisms, as in TCP, and the latter is achieved by the sharing of resources by the number (n) of connections by the use of transmission storage. For example where the maximum bandwidth-delay product of a communications link is (x), the amount of capacity given to a connection, before allowance for the PEP to Intermediate device flow, is (x/n). When the sum of all actual capacity usage by each individual connection (n) is less than (x), then the available capacity is shared by any connections wishing to exceed their allocations. This allows the full capacity of the link to be employed if several incoming TCP/IP connections (from the terrestrial side) are running slowly. [0036]
  • Additionally, when new connections arrive, they are guaranteed (x/n) capacity even if the result is a temporarily over-supply of capacity; the existing connections flows are naturally reduced to the new lower rate. This is achieved by the use of a buffer to manage the flow, with packets only being allowed storage in the buffer when the afore mentioned rules are met. For example, if 1 Mb/s was previously shared between 10 connections a new connection would result in the over supply of 90.909 Kb/s (10*100 Kb/s+1*90.909 Kb/s). However the existing connections are forced down to around 90.909 Kb/s by preventing new incoming TCP/IP packets from the terrestrial side to progress from the TCP Emulator to the FP, until sufficient buffer space is created. Any temporary over-supply, until the system returns to the steady-state, is achieved by allowing the new connection packets to be stored in an output queue. The existing connections being denied further capacity until the new connection has reached its allocation and sufficient space exists in the output queue. The end result being a natural back-pressure to the TCP senders of the over-supplying connections and prevention of the new connection being starved of capacity when the link was previously fully occupied. [0037]
  • The transmission of data from the PEP to the intermediate device and onwards to the other PEP, depends on the passing of three conditions laid out above; namely: sufficient transmission buffer space (allowing for the rules above), sufficient space in the receiver window (allowing for the amount of data already transmitted since the last window update (as in TCP)) and sufficient capacity/buffer space at the intermediate device (Terminal). If any of these tests fail, data can be stored in an applicable Input or Output queue within the PEP (TCP Emulator or FP) thereby creating natural back pressure to the TCP sender in the regular window updates sent form the PEP to the TCP sender. [0038]
  • The invention provides for a return link in the Terminal-Satellite-Gateway direction that is shared between a number of Terminals and thus subject to varying bandwidth conditions. Likewise the output queue in the Terminal that is tested and then filled is a queue for all traffic. Variations are possible, for example, the Gateway could enjoy varying bandwidth conditions facilitating the need for such a scheme or the Intermediate Device could have several output queues, requiring a different parameter to be polled (e.g. the TCP/IP queue). [0039]
  • Referring now to the method of implementing the transfer of data in this environment according to an embodiment of the invention, FIG. 1 illustrates a simplified view of a performance enhancing proxy (PEP) communications system [0040] 100 including equipment and links involved in a PEP deployment in a satellite communication link environment. In FIG. 1, a client 101 initiates a connection attempt to a server 107 via a satellite 104. The client is connected by a local area network (LAN) segment 108 to a terminal-side PEP1 102, via another LAN segment 109 to a satellite terminal or satellite modem of some form 103. Traffic from a terminal 103 passes over the communications links 110 and 111 via the satellite 104 to the Gateway, central hub equipment or other satellite modem 105. Traffic leaving the Gateway passes via a LAN segment 112 to a gateway-side PEP2 106. The PEP2 106 then sends the traffic via a wide area network (WAN), such as part of the Internet, 113 to the server 107. The traffic may be a client request, which could generate server response traffic in the reverse direction.
  • Data transfer from the client [0041] 101 to the terminal PEP1 102, and from the gateway PEP2 106 to server 107 uses known TCP protocols. Data transfer over the satellite link from the PEP1 102 to the PEP2 106 uses the flight protocol (FP) described in greater detail above. The data transfer is thus sent over TCP-FP-TCP protocol links.
  • FIG. 2 shows the stacks involved in the various elements in a TCP-FP-TCP transfer. FIG. 2 shows the stacks of a transfer end point application which include an application/presentation/session layer [0042] 285, a TCP layer 206, an IP layer 212, an Ethernet or equivalent layer 222 and a UTP or equivalent layer 233. FIG. 2 also shows the stacks in a first PEP1 (first PEP in the transfer direction front end) which includes a UTP or equivalent layer 234, an Ethernet or equivalent layer 223, a modified IP layer 213, a modified TCP layer (TCP*) 207, an application/presentation/session layer 201, an FP layer 208, a modified IP layer 214, an Ethernet or equivalent layer 224 and a UTP or equivalent layer 235. A transfer originating from an end point 285 is acted upon using conventional data communication rules by the TCP layer 206, the IP layer 212, the Ethernet 222, the UTP layer 233, the UTP layer 234 and the Ethernet 223 before it is grabbed by the modified IP layer 213 and passed up the stack to the modified TCP layer 207, translated by the application/presentation/session layer 201 and then managed by the FP layer 208 before being sent through the modified IP layer 214, the Ethernet 224 and UTP layer 235.
  • Following the arrows in FIG. 2 illustrates the conventional stacks of the satellite gateway and terminal and also the stacks of a PEP2. In PEP2, incoming FP packets are grabbed by a modified IP layer [0043] 219, after passing through the physical UTP layer 240 and link Ethernet 229 layers, and then managed by the FP layer 209 before passing, via application/presentation/session/layer 204 to TCP* 210 which along with the modified IP layer 220 manages the terrestrial TCP/IP connection.
  • As described earlier, the invention allows for the exchange of information between the Intermediate Device (the “Terminal”) and PEP1. This is to aid overall flow control and the sharing of bandwidth within the overall flow, between incoming (terrestrial network-to-PEP) and outgoing (PEP-to-terrestrial network) TCP connections by managing buffer resources associated to the link Bandwidth Delay Product (BDP). Additionally, the novel overall flow control scheme ensures near 100% throughput, assuming sufficient TCP/IP traffic as an input, while allowing for the receiving PEPs buffer requirements, through conventional window mechanisms, and fairly sharing the capacity between a number of connections. The following section describes further aspects of the invention in greater detail. [0044]
  • From the PEP-Intermediate Device (Terminal) point of view, actual return link capacity available for PEP traffic at any given time is normally an unknown. This issue mainly relates to the terminal population and its access to return link capacity. When packets are queued in the terminal [0045] 103 shown in FIG. 1, capacity is requested related to the number of packets being queued, however a capacity request may be only partially fulfilled, or not fulfilled at all. In this case, it becomes possible for terminal PEP1 102 to oversupply or under supply the terminal which may result in dropping or low usage. This dropping may increase buffering at Intermediate Devices and lead to greater jitter and latency that results in low bandwidth usage and hence a loss of revenue potential. In brief, the PEP is unaware of the return link capacity because of:
  • 1. Limited knowledge about terminal queue status and size. [0046]
  • 2. Dynamic capacity assignment to the terminal. [0047]
  • 3. Non zero probability of loss on the local PEP-terminal link. [0048]
  • 4. No confirmation of data transfer between PEP and terminal. [0049]
  • 5. Unknown amount of traffic originating from the terminal itself, notably Operations Administration & Management (OA&M) traffic. [0050]
  • For accurate flow control purposes, what is really needed is information concerning the status of the Intermediate Device output queue, and for the PEP to supply data packets to fill the queue to a pre-determined level. We note that this queue could be an output queue for all packets or purely for TCP/IP traffic. [0051]
  • It is possible to obtain some valuable information by taking advantage of functionality often provided for network management. What follows is a description of how a PEP device could have knowledge of the Intermediate Devices (Terminal) queue status, and use this information to ensure that the queue is neither over-supplied nor under-supplied. Although the solution uses Simple Network Management Protocol (SNAP), it should be understood that other protocols could be used to exchange information and, moreover, the Intermediate Device and PEP could be co-located in the same unit with some form of direct linkage to erase the need for protocol driven communication. Furthermore, if the PEP were located in the terminal, it could make use of known future capacity allocations to manage the flow of incoming TCP/IP connections more accurately. For example, if the PEP knows of any Constant Rate Assignments (CRAs) to the Terminal PEP1 [0052] 102 (i.e. not dynamic and varying capacity) it can at least ensure that sufficient TCP/IP flow is maintained to fill its future assignments and possibly buffer space.
  • The Simple Network Management Protocol (SNAP) is a request-reply protocol running over User Datagram Protocol (UDP). SNAP is an asymmetric protocol, operating between a management station and an agent. Intermediate Devices (Terminals) are expected to support SNAP messaging for network management. The Management Information Base (MIB) specified for Terminals incorporates several (but not all) generic MIB-II (MIB version 2) objects. [0053]
  • The following assumptions are made: [0054]
  • 1. The PEP behind the terminal can assume the role of a local management station, thereby getting read access to MIB-II objects of the Intermediate Device (Terminal) using the appropriate community name. [0055]
  • 2. Buffering in the terminal is limited by number of packets rather than by volume of data (although we note that data bytes could be used if the Intermediate Device output queue length in bytes were known). [0056]
  • 3. The PEP either knows (or otherwise, can determine) the maximum size (in number of packets) of the Intermediate Device output queue. This parameter may be called MaxQlen. [0057]
  • Potentially useful MIB-II objects for deriving buffer occupancy information are in the interfaces group (the group of MIB-II objects related to the network interfaces of the device), specifically, for any of the interfaces given below. While these are specific, it should be understood that one of ordinary skill in the art would recognize possible use of other interface variations, modifications, and alternatives. [0058]
  • 1. IfOutQlen: is a gauge indicating the number of packets in the outbound queue. [0059]
  • 2. IfOutOctets: is a counter indicating the total number of octets transmitted out of the interface including framing octets. [0060]
  • 3. IfOutUcastpkts: is a counter indicating the number of unicast packets whose transmission to a single address was requested. [0061]
  • 4. IfOutNUcastpkts: is a counter indicating the total number of packets whose transmission to a multicast or broadcast address was requested. [0062]
  • The basic idea for PEP to Intermediate Device communication is for the PEP to regularly send SNAP GetRequest queries to the Intermediate Device (Terminal) for the IfOutQlen of the satellite link interface, although it is to be noted that the Intermediate Device could send the PEP an SNAP Set when its IfOutQlen reaches a pre-defined limit. The returned value allows the PEP to control the amount of data that is fed to the terminal. [0063]
  • From the point of view of a PEP, the algorithm is packet-driven: no actions are performed unless there are packets to send on the satellite link. A flow chart [0064] 300 for the algorithm is illustrated in FIG. 3. The algorithm proceeds as follows: In step 301, the variables FreeQ_i and FreeQ_(i−1) are first initialized. The process then moves to step 302. In step 302, the PEP then waits until there are packets to send to the terminal (Packets_to_send >0). The process then moves to step 303. In step 303, when there are packets to send, a test is performed to check whether the PEP is already aware of a certain amount of buffer space available on the terminal (FreeQ_(i−1)). If there is buffer space, the process moves to step 304, otherwise the process moves to step 305. In step 304, the PEP sends packets up to (FreeQ_(i−1)) packets. The process then moves to step S305. In step S305, the PEP sends a SNAP GetRequest for IfOutQlen. The terminal responds with a SNAP GetResponse containing a value for IfOutQlen. The process then moves to step S306. In step 306, the PEP computes FreeQ_i=(MaxQlen−OutQlen−Margin). The process then moves to step 307. In step 307, the PEPs send the minimum of {FreeQ_I, Packets_to_send} packets to the terminal. The process then moves to step 308.
  • In step [0065] 308, the system determines whether FreeQ_i>Packets_to_send. If yes, the process moves to step 309 where there is more buffer space available on the terminal, and FreeQ_(i−1) is updated to the remaining space, i.e., FreeQ_(i−1)=FreeQ_i−Packets_to_send and the process returns to step 302. If no, the process continues to step 310. In step 310, If (FreeQ_i >=Thresh) then the process returns to step 305. Otherwise, the process moves to step 311 to wait Query_timer and then returns to step 305. The following parameters employed by the process above are described:
  • 1. MaxQlen: maximum size (in number of packets) of the Intermediate Device (Terminal) satellite link outbound queue. [0066]
  • 2. Query timer: a delay to avoid querying the terminal too frequently. Its value may be set based on the time required to empty a full queue at a given return link maximum rate. [0067]
  • 3. Thresh: a threshold (in number of packets) for deciding whether the queue is full enough to wait before going back to query. A suitable low value should be used. [0068]
  • 4. Margin: a security margin to account for an unknown amount of traffic originating from the terminal itself, for inaccuracies in the OutQlen values reported. This should be set in such a way that the probability of dropping packets due to overflows at the terminal is suitably low to keep the costs of lost FP packets low. [0069]
  • The following variables are also defined: [0070]
  • 1. FreeQ_i: free satellite link buffer space maximum on the terminal. [0071]
  • 2. FreeQ_(i−1): remaining free satellite link buffer space available. In a situation where packets to send are few and far between, FreeQ_i will be much larger than Packets_to_send and the PEP will go through steps [0072] 302 to 308 each and every time a packet to send arrives. This entails one SNAP query per run, since step 303 avoids one SNAP query when the PEP is already aware of some buffer space available on the terminal. The PEP could be made to wait for a certain delay before returning to step 302 after step 308, thereby avoiding sending a certain number of SNAP queries. However, there is no simple way to avoid this delay when a large number of packets to send arrive in a burst. Since the delay would slow transmission down in that very important case, it is more efficient to go back to step 302 and run through step 308 without delay. At worst, there will therefore be one query per packet if packets arrive one by one, but in such a case, SNAP queries will not hamper traffic since there will be virtually no traffic to interfere with.
  • In step [0073] 311 the PEP will wait until the expiration of a query timer if FreeQ_i is not greater than a threshold. This is to prevent un-necessary SNAP queries being sent to an Intermediate Device when there is little chance of the PEP sent packets having been sent beyond the Intermediate Device (Terminal). Another, lower timer, could be employed between the tests of step 310 and step 305 should FreeQ_i be greater than the threshold to allow the Intermediate Device (Terminal) time to process the packets.
  • The PEP should also make use of some form of PEP rate control clocking-out mechanism to ensure that the transmission rate from the PEP to the Intermediate Device (Terminal) does not over run the Terminal input queue and processing rate when sending bursts to fill up the said queue. Finally, note that packets arriving at the PEP from the terrestrial side, while the packet-driven algorithm is in process, are queued and subsequently drawn from the queue when the algorithm returns to step [0074] 302, this process being consistent with the packet driven format of the PEP.
  • Management of individual competing TCP/IP connection flows within the general flow is achieved by sharing a buffer space equivalent to the Bandwidth-Delay Product of the satellite link. In principle, every time a packet arrives from the terrestrial side it is associated with a connection and, before transgressing from the TCP* layer [0075] 207 to the FP layer 208 shown in FIG. 2, three tests are undertaken. This section describes the “buffer utilization” test that is employed to share resources among the different connections.
  • The PEP includes both a Transmit and a Receive Buffer. On arrival at the PEP, a packet from the terrestrial world is queued in the TCP* [0076] 207 layer's buffer. This buffer is equivalent to a conventional TCP buffer at the receiving end point, with the space in the buffer being linked to the advertised window on the TCP connection. This ‘linkage’ allows the TCP connection on the terrestrial link to slow down the flow of packets to the PEP as the TCP* buffer becomes full, in much the same way as TCP would slow down the flow of packet as the receiving ends buffers become full.
  • Before a packet can pass from the TCP* buffer to the FP layer it must pass the following rules to ensure that sufficient space exists in the FP buffer: [0077]
  • 1. If the connection buffer utilization is less than its allowed buffer space (allowed buffer space=FP total buffer space/n connections, where the total buffer space is sufficient space to fill one bandwidth-delay product) then the packet can be pushed; or [0078]
  • 2. If the total buffer utilization (among all n connections) is less than the FP total buffer space allowed, then the packet can be pushed. [0079]
  • 3. Otherwise the packet remains in the TCP* buffers. [0080]
  • Once a packet is allowed to pass from the TCP* layer to the FP layer, it is also stored in the FP buffer and associated to a connection. The FP buffer facilitates re-transmissions if necessary and the sharing of the satellite link resources between competing TCP connections, as described. [0081]
  • It is important to note that the FP total buffer space can become artificially high. For example, if the global size is 3 Mbytes, then if three connections are opened, each connection will be allowed 1 Mbyte for its individual transmit buffer. [0082]
  • When opening a fourth connection, even if the three connections are using their whole transmit buffer, the new connection will immediately use its whole share of the transmit buffer. The FP global transmit buffer size will then become 3.75 Mbytes (1+1+1+0.75). The buffer utilization test allows to exceed the global transmit buffer size, but this situation will never last very long. The buffer utilization mechanism will redistribute equally the global transmit buffer size between the four opened connections. Each connection will be allowed to use a new individual transmit buffer size of 0.75 Mbyte (¾), thus pausing the flow of data on the three excessive connections. Eventually, the global transmit buffer size will decrease to 3 Mbytes (0.75+0.75+0.75+0.75) and therefore, the size of the global transmit buffer will fall back to 3 Mbytes in the steady state. [0083]
  • When space becomes available in the FP buffer (because of an acknowledgement signal, ACK, from the receiving ending indicating the successful arrival of a packet and thereby removing the packet from the FP Buffer), the PEP can pull a packet from the applicable TCP* buffer. This mechanism ensures that when the FP Buffer and even TCP* buffers are full, then the flow of a connection can be re-triggered by the arrival of ACKs. (note that, although the mechanism is not described as it is a known mechanism, the PEP includes a re-transmission procedure, based on timers, to ensure that data is re-transmitted if presumed lost, thereby guaranteeing the arrival of ACKs to re-trigger the flow or, if the satellite link is lost, a connection tear-down). [0084]
  • The following is an illustrative example for calculating default buffer sizes for the gateway and terminal-side PEP transmit and receive buffers. For purposes of this example, it is presumed that the total forward link rate is 60 mega-bits per second (Mbps) and the total return link rate is 48 Mbps. Each terminal can be assumed to operate at a maximum receive rate in the forward link of 8 Mbps and a maximum transmit rate in the return link of 2 Mbps. [0085]
  • In the forward direction the transmit bandwidth and thus transmit buffer should assume 60 Mbps. At the terminal (forward link receiver) the bandwidth is 8 Mbps. In the return link, the transmit and receive bandwidths are 2 Mbps and 48 Mbps respectively. To calculate the Bandwidth Delay Product (BDP) and hence the buffer requirements, 2 more factors are required: the Round Trip Time (RTT) and what can be called the utilization factor. [0086]
  • The RTT is actually the time for a packet to be sent and the associated FP ACK to be sent back and clear the packet from the transmit buffer or open up more receive buffer space through window advertisements. This is the RTT between the PEPs and includes any ACK delay timers used to provide a minimum ACK frequency. From satellite testing, a value of 600 ms is reasonable for Terminals that have been allocated a constant rate of bandwidth (Constant Rate Assignment—CRA) for this example and a delayed ACK timer of 500 ms could be assumed. For Terminals operating in a pure BoD environment using Variable Bandwidth Dynamic Capacity (VBDC), the mean RTT measured was around 1400 ms which would obviously require a larger buffer. [0087]
  • The utilization factor adjusts the calculated buffer sizes to maintain PEP/FP performance under heavier buffer utilization due to packet loss/corruption. From simulation and theory, we expect transmit buffer utilization to be around 102-105% of the calculated buffer size depending upon error conditions and packet sizes. Each FP packet that is lost must remain buffered for an additional RTT to allow for successful retransmission and acknowledgement. [0088]
  • At the receiver, a decision must be made regarding how many retransmissions of any individual packet must be supported before FP performance is impacted. A single BDP sized buffer allows the link to stay fully utilized as long as the receiver is processing the packets quickly enough and there are no errors. If a packet loss occurs, the missing packet (hole) will progress to the left edge of the receive window (as the receiver processes data) and the buffer will begin to fill. After one RTT the receive buffer will be full and transmission of new packets must be halted while the lost packet is retransmitted. Effectively, a single RTT pause is inserted for any packet lost once. If a double BDP buffer is used, then virtually any number of packets can be lost once with the FP and the connection will still send new data at full speed if available. [0089]
  • The following calculations are for example only, but an attempt has been made to make this example as efficient as possible. The two values given are for CRA and VBDC, respectively. It is important to note that one of ordinary skill in the art would recognize other variations, modifications, and alternatives [0090]
  • GW PEP TX BUFFER=60 Mbps/8 bits per byte*105%*1.1 s to 1.9 s=8.7M bytes to 14.9M bytes [0091]
  • GW PEP RX BUFFER=48 Mbps/8 bits per byte*200%*1.1 s to 1.9 s=13.2M bytes to 22.8M bytes [0092]
  • Terminal PEP TX BUFFER=2 Mbps/8 bits per byte*105%*1.1 s to 1.9 s=288K bytes to 499K bytes [0093]
  • Terminal PEP RX BUFFER=8 Mbps/8 bits per byte*200%*1.1 s to 1.9 s=2.2M bytes to 3.8M bytes [0094]
  • The description above has dealt with the use of the “buffer utilization” test to share resources between competing TCP/IP connections in the terrestrial to PEP direction. However, the same technique is used to manage the flow of resources between the PEP and the terrestrial world using a Receive Buffer. This allows for the fair sharing of resources between connections, the distribution of free resources if one or more connections are not employing their allocation and the prevention of slow connections dominating the link. (In simulations it was found that if connections are not limited in their allocation, then slow TCP/IP connections would tend to dominate the link). The scheme works using the same rules but in reverse, this time the intention being to decide whether or not to accept incoming FP packets from the satellite. FP packets that are allowed to be stored in the FP Receiver buffer are cleared by a TCP acknowledgement. In much the same way, as TCP operates, a window mechanism is used from the receiving PEP to the transmitting PEP to indicate the status of each connection's buffer space and thus prevent over-flow. [0095]
  • The task for an overall flow control mechanism applicable for a large bandwidth-delay product environment with changing bandwidth and latency, such as a satellite system, is to achieve the following goals: [0096]
  • 1. Maximize the flow of data from the sender to the satellite network without under-supplying or over-supplying the intermediate node (i.e. the terminal that requests and receives bandwidth capacity). [0097]
  • 2. Share satellite and terrestrial bandwidth within the overall flow so as to ensure fairness while allowing unused capacity to be employed by hungry connections and preventing slow connections from dominating the link capacity. [0098]
  • 3. Prevent the overflow of the receiving end PEPs buffer associated per connection. [0099]
  • As used in this section, transmission of data means the passing of a packet from the TCP* layer to the FP layer, the re-transmission of a FP data packet or an acknowledgment packet signaling the successful arrival of data. [0100]
  • In general (with the exception of re-transmissions and ACKs) packets are pushed, upon arrival from the terrestrial world, from the TCP* [0101] 207 to the FP layer 208 as shown on FIG. 2, and then sent via the satellite with a copy being stored in the FP Transmit buffer. Before packets can be pushed (or retransmitted/acknowledged) they have to pass three tests at PEP1, the transmitter PEP over satellite where the flow is client to server: a local (transmit) buffer space test (Distribution of Satellite Resources amongst TCP/IP connections at the PEP), a PEP-to-Intermediate Node Communication test, and a sufficient buffer space test. Sufficient buffer space at the receiving PEP is signalled using a conventional window strategy in packets (data or ACKs) flowing from the receiving PEP to the sending PEP.
  • When space becomes available (either because of a changed window parameter or an ACK removing a packet from the FP Tx Buffer), the PEP pulls a packet from the applicable TCP* buffer [0102] 207, providing that the three flow control rules allow this. This technique, in combination with the above rules and large initial windows, allows nearly 100% usage of available capacity, while managing the distribution of bandwidth in a variable bandwidth/latency system. Natural back pressure from the TCP* buffers slows down the terrestrial TCP/IP connection flow.
  • It will be apparent to those skilled in the art that various modifications and variations can be made to this invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention covers the modifications and variations of this invention provided that they come within the scope of any claims and their equivalents. [0103]

Claims (10)

1. In a distributed connection splitting system, which comprises at least two intermediate nodes, a method for managing data flow between the intermediate nodes and through an intermediate device, comprising the steps of:
obtaining status data of the intermediate device; and
managing the flow of data between the intermediate nodes and the intermediate device by determining the status of an intermediate device queue.
2. The method of claim 1, wherein the amount of at least one of data and packet space in the intermediate device is used to determine the quantity of at least one of data and packets which should be sent to the intermediate device.
3. The method of claim 1, wherein the intermediate nodes send sufficient data to at-least partially fill the intermediate device queue to a pre-defined level, and after a pre-determined delay to allow data to be transmitted, checks the status of the intermediate device and then re-fills the intermediate device queue to a previous level.
4. The method of claim 1, wherein the intermediate nodes send regular SNAP get messages to an intermediate device MIB or the intermediate device sends SNAP traps when a queue reaches a pre-detemined level to indicate the current queue status.
5. The method of claim 1, wherein the flow of data from the intermediate nodes to the intermediate device is more accurate by the intermediate nodes having knowledge of current and future bandwidth information from the intermediate device.
6. The method of claim 5, wherein the intermediate nodes and the intermediate device are co-located in the same device with some form of direct linkage between the allocated bandwidth/queue and the intermediate nodes.
7. A method of fairly distributing bandwidth among connections in a communications system, comprising the step of sharing of transmission storage amongst a number N connections.
8. The method according to claim 7, wherein the step of sharing further includes the steps of:
calculating an amount of capacity given to a connection before allowance for any applicable intermediate node to Intermediate device flow is X/N, where X is the maximum bandwidth-delay product of a communication and N is the number of connections;
determining if a sum of all the actual capacity usage by each individual connection N is less than X, wherein the available capacity is shared by any connections wishing to exceed an allocation; and
determining, if new connections arrive, whether they are guaranteed (X/N) capacity even if the result is a temporarily over-supply of capacity to a link resulting in buffering at an output queue of the intermediate node.
9. A method for managing the flow of data from an intermediate node to an intermediate device so that the transmission of data depends upon: sufficient transmission buffer space in the sending intermediate node; sufficient space in the receiver window of the receiving intermediate node; and sufficient capacity/buffer space at one of the intermediate devices.
10. The method of claim 9, wherein the failure of a test causes data to be stored in an applicable input or output queue within the intermediate node thereby creating natural back pressure to a TCP sender in the regular window updates sent from the intermediate node to the TCP sender.
US10/292,901 2001-11-13 2002-11-13 Flow control between performance enhancing proxies over variable bandwidth split links Abandoned US20030123394A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US33360801P true 2001-11-13 2001-11-13
US10/292,901 US20030123394A1 (en) 2001-11-13 2002-11-13 Flow control between performance enhancing proxies over variable bandwidth split links

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US10/292,901 US20030123394A1 (en) 2001-11-13 2002-11-13 Flow control between performance enhancing proxies over variable bandwidth split links

Publications (1)

Publication Number Publication Date
US20030123394A1 true US20030123394A1 (en) 2003-07-03

Family

ID=23303516

Family Applications (3)

Application Number Title Priority Date Filing Date
US10/292,899 Abandoned US20030131079A1 (en) 2001-11-13 2002-11-13 Performance enhancing proxy techniques for internet protocol traffic
US10/292,900 Expired - Fee Related US6975647B2 (en) 2001-11-13 2002-11-13 Enhancements for TCP performance enhancing proxies
US10/292,901 Abandoned US20030123394A1 (en) 2001-11-13 2002-11-13 Flow control between performance enhancing proxies over variable bandwidth split links

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US10/292,899 Abandoned US20030131079A1 (en) 2001-11-13 2002-11-13 Performance enhancing proxy techniques for internet protocol traffic
US10/292,900 Expired - Fee Related US6975647B2 (en) 2001-11-13 2002-11-13 Enhancements for TCP performance enhancing proxies

Country Status (5)

Country Link
US (3) US20030131079A1 (en)
EP (1) EP1446931A1 (en)
AU (2) AU2002352637A1 (en)
CA (1) CA2473863A1 (en)
WO (3) WO2003043288A1 (en)

Cited By (56)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040264368A1 (en) * 2003-06-30 2004-12-30 Nokia Corporation Data transfer optimization in packet data networks
US20050058131A1 (en) * 2003-07-29 2005-03-17 Samuels Allen R. Wavefront detection and disambiguation of acknowledgments
US20050063303A1 (en) * 2003-07-29 2005-03-24 Samuels Allen R. TCP selective acknowledgements for communicating delivered and missed data packets
US20050063307A1 (en) * 2003-07-29 2005-03-24 Samuels Allen R. Flow control system architecture
US20050083924A1 (en) * 2002-02-07 2005-04-21 Markus Dillinger Method for downloading data in a radio communications system
US20050210121A1 (en) * 2004-03-22 2005-09-22 Qualcomm Incorporated Satellite anticipatory bandwith acceleration
US20050210122A1 (en) * 2004-03-22 2005-09-22 Qualcomm Incorporated HTTP acceleration over a network link
US20060031571A1 (en) * 2004-04-29 2006-02-09 International Business Machines Corporation Data communications through a split connection proxy
US20060059273A1 (en) * 2004-09-16 2006-03-16 Carnevale Michael J Envelope packet architecture for broadband engine
US20060155840A1 (en) * 2003-05-27 2006-07-13 Macdonald Dettwiler And Associates Ltd. Satellite communications system for providing global, high quality movement of very large data files
US20060190719A1 (en) * 2004-07-23 2006-08-24 Citrix Systems, Inc. Systems and methods for communicating a lossy protocol via a lossless protocol using false acknowledgements
US20060262724A1 (en) * 2005-05-17 2006-11-23 Daniel Friedman Method and system for efficient flow control in a spot beam satellite system
US20070156879A1 (en) * 2006-01-03 2007-07-05 Klein Steven E Considering remote end point performance to select a remote end point to use to transmit a task
US20070153677A1 (en) * 2005-12-30 2007-07-05 Honeywell International Inc. Method and system for integration of wireless devices with a distributed control system
US20070248090A1 (en) * 2006-04-25 2007-10-25 Haseeb Budhani Virtual inline configuration for a network device
US20070280115A1 (en) * 2004-06-22 2007-12-06 Michael Meyer Network Feedback Method and Device
US20080049786A1 (en) * 2006-08-22 2008-02-28 Maruthi Ram Systems and Methods for Providing Dynamic Spillover of Virtual Servers Based on Bandwidth
JP2008136176A (en) * 2006-10-10 2008-06-12 Mitsubishi Electric Information Technology Centre Europa Bv Method and device for managing allocation of memory blocks, data transmission network system, computer-readable medium, and computer program product
US20080181108A1 (en) * 2006-10-06 2008-07-31 Viasat, Inc. Dynamic Feedback For Outbound Link Rate Adjustment In Multi-Rate Downstream
US20080225728A1 (en) * 2007-03-12 2008-09-18 Robert Plamondon Systems and methods for providing virtual fair queueing of network traffic
US20080225715A1 (en) * 2007-03-12 2008-09-18 Robert Plamondon Systems and methods of providing proxy-based quality of service
US7698453B2 (en) 2003-07-29 2010-04-13 Oribital Data Corporation Early generation of acknowledgements for flow control
US20100091699A1 (en) * 2008-10-15 2010-04-15 Viasat, Inc. Profile-based bandwidth scheduler
US20100246398A1 (en) * 2009-03-26 2010-09-30 Mung Chiang Tcp extension and variants for handling heterogeneous applications
US20100274901A1 (en) * 2004-11-19 2010-10-28 Viasat, Inc. Network accelerator for controlled long delay links
US7849270B2 (en) 2005-01-24 2010-12-07 Citrix Systems, Inc. System and method for performing entity tag and cache control of a dynamically generated object not identified as cacheable in a network
US20100322071A1 (en) * 2009-06-22 2010-12-23 Roman Avdanin Systems and methods for platform rate limiting
US20110153816A1 (en) * 2009-12-18 2011-06-23 Google Inc. Matching Encoder Output to Network Bandwidth
US7969876B2 (en) 2002-10-30 2011-06-28 Citrix Systems, Inc. Method of determining path maximum transmission unit
US8233392B2 (en) 2003-07-29 2012-07-31 Citrix Systems, Inc. Transaction boundary detection for reduction in timeout penalties
US8238241B2 (en) * 2003-07-29 2012-08-07 Citrix Systems, Inc. Automatic detection and window virtualization for flow control
US8255456B2 (en) 2005-12-30 2012-08-28 Citrix Systems, Inc. System and method for performing flash caching of dynamically generated objects in a data communication network
US8261057B2 (en) 2004-06-30 2012-09-04 Citrix Systems, Inc. System and method for establishing a virtual private network
US8270423B2 (en) 2003-07-29 2012-09-18 Citrix Systems, Inc. Systems and methods of using packet boundaries for reduction in timeout prevention
US8291119B2 (en) 2004-07-23 2012-10-16 Citrix Systems, Inc. Method and systems for securing remote access to private networks
US8301839B2 (en) 2005-12-30 2012-10-30 Citrix Systems, Inc. System and method for performing granular invalidation of cached dynamically generated objects in a data communication network
US8432800B2 (en) 2003-07-29 2013-04-30 Citrix Systems, Inc. Systems and methods for stochastic-based quality of service
US8437284B2 (en) 2003-07-29 2013-05-07 Citrix Systems, Inc. Systems and methods for additional retransmissions of dropped packets
US8462631B2 (en) 2007-03-12 2013-06-11 Citrix Systems, Inc. Systems and methods for providing quality of service precedence in TCP congestion control
US20130176847A1 (en) * 2012-01-09 2013-07-11 Ntt Docomo, Inc. Communication processing method, apparatus and gateway device
US8493858B2 (en) 2006-08-22 2013-07-23 Citrix Systems, Inc Systems and methods for providing dynamic connection spillover among virtual servers
US8495305B2 (en) 2004-06-30 2013-07-23 Citrix Systems, Inc. Method and device for performing caching of dynamically generated objects in a data communication network
US8499057B2 (en) 2005-12-30 2013-07-30 Citrix Systems, Inc System and method for performing flash crowd caching of dynamically generated objects in a data communication network
US8549149B2 (en) 2004-12-30 2013-10-01 Citrix Systems, Inc. Systems and methods for providing client-side accelerated access to remote applications via TCP multiplexing
US8559449B2 (en) 2003-11-11 2013-10-15 Citrix Systems, Inc. Systems and methods for providing a VPN solution
US8700695B2 (en) 2004-12-30 2014-04-15 Citrix Systems, Inc. Systems and methods for providing client-side accelerated access to remote applications via TCP pooling
US8706877B2 (en) 2004-12-30 2014-04-22 Citrix Systems, Inc. Systems and methods for providing client-side dynamic redirection to bypass an intermediary
US8739274B2 (en) 2004-06-30 2014-05-27 Citrix Systems, Inc. Method and device for performing integrated caching in a data communication network
US8780823B1 (en) 2009-10-08 2014-07-15 Viasat, Inc. Event driven grant allocation
US8856777B2 (en) 2004-12-30 2014-10-07 Citrix Systems, Inc. Systems and methods for automatic installation and execution of a client-side acceleration program
US8954595B2 (en) 2004-12-30 2015-02-10 Citrix Systems, Inc. Systems and methods for providing client-side accelerated access to remote applications via TCP buffering
EP1976202B1 (en) 2007-03-12 2016-03-09 Viprinet Europe GmbH Device and method for transmitting a data stream over bundled network access cables, as well as transmission and reception aid device and transmission and reception method for same
WO2016100890A1 (en) * 2014-12-19 2016-06-23 Nokia Solutions And Networks Oy Smooth bandwidth-delay product variation inside wireless networks
US20180152278A1 (en) * 2016-11-30 2018-05-31 International Business Machines Corporation Multi-domain connection establishment in computer networking communications
EP3399707A1 (en) * 2017-05-04 2018-11-07 Global Eagle Entertainment Inc. Data flow control for dual ended transmission control protocol performance enhancement proxies
US10248465B2 (en) * 2008-01-23 2019-04-02 Comptel Corporation Convergent mediation system with dynamic resource allocation

Families Citing this family (208)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110128972A1 (en) 2000-04-17 2011-06-02 Randy Thornton Peer to peer dynamic network link acceleration
US8996705B2 (en) * 2000-04-17 2015-03-31 Circadence Corporation Optimization of enhanced network links
AU5361301A (en) 2000-04-17 2001-10-30 Circadence Corp System and method for shifting functionality between multiple web servers
US6850732B2 (en) * 2001-03-30 2005-02-01 Wengen Wireless Llc Scalable satellite data communication system that provides incremental global broadband service using earth-fixed cells
US6778825B2 (en) * 2001-05-08 2004-08-17 The Boeing Company Path discovery method for return link communications between a mobile platform and a base station
US20050198379A1 (en) 2001-06-13 2005-09-08 Citrix Systems, Inc. Automatically reconnecting a client across reliable and persistent communication sessions
US7320833B2 (en) * 2001-11-07 2008-01-22 E.I. Du Pont De Nemours And Company Electroluminescent platinum compounds and devices made with such compounds
DE60322988D1 (en) * 2002-01-28 2008-10-02 Hughes Network Systems Llc Method and apparatus for integrating functions to improve performance in a virtual private network (VPN)
US8976798B2 (en) 2002-01-28 2015-03-10 Hughes Network Systems, Llc Method and system for communicating over a segmented virtual private network (VPN)
US7389533B2 (en) * 2002-01-28 2008-06-17 Hughes Network Systems, Llc Method and system for adaptively applying performance enhancing functions
US7042857B2 (en) 2002-10-29 2006-05-09 Qualcom, Incorporated Uplink pilot and signaling transmission in wireless communication systems
EP1652087B1 (en) * 2003-07-29 2015-07-08 Citrix Systems, Inc. Flow control architecture
JP4283589B2 (en) * 2003-03-25 2009-06-24 株式会社エヌ・ティ・ティ・ドコモ Communication device, a communication control method, and program
US7349400B2 (en) * 2003-04-29 2008-03-25 Narus, Inc. Method and system for transport protocol reconstruction and timer synchronization for non-intrusive capturing and analysis of packets on a high-speed distributed network
US7177297B2 (en) * 2003-05-12 2007-02-13 Qualcomm Incorporated Fast frequency hopping with a code division multiplexed pilot in an OFDMA system
US20040236855A1 (en) * 2003-05-23 2004-11-25 Amir Peles Multi-link tunneling
US7760729B2 (en) * 2003-05-28 2010-07-20 Citrix Systems, Inc. Policy based network address translation
FI20030929A (en) * 2003-06-19 2004-12-20 Nokia Corp The method and arrangements for carrying out wireless data transmission means of transport
US8275910B1 (en) 2003-07-02 2012-09-25 Apple Inc. Source packet bridge
US7665132B2 (en) * 2003-07-04 2010-02-16 Nippon Telegraph And Telephone Corporation Remote access VPN mediation method and mediation device
US7385937B2 (en) * 2003-07-23 2008-06-10 International Business Machines Corporation Method and system for determining a path between two points of an IP network over which datagrams are transmitted
US7460472B2 (en) * 2003-07-25 2008-12-02 Nokia Corporation System and method for transmitting information in a communication network
US7286476B2 (en) * 2003-08-01 2007-10-23 F5 Networks, Inc. Accelerating network performance by striping and parallelization of TCP connections
KR100506529B1 (en) 2003-08-06 2005-08-03 삼성전자주식회사 Apparatus, system and method for path mtu discovery in data communication network
US7376418B2 (en) * 2003-09-08 2008-05-20 Wells Loren L System and method for multiple access control in satellite communications system
US8553572B2 (en) * 2003-09-10 2013-10-08 Hyperdata Technologies, Inc. Internet protocol optimizer
US7058058B2 (en) 2003-11-05 2006-06-06 Juniper Networks, Inc. Transparent optimization for transmission control protocol initial session establishment
US7496097B2 (en) * 2003-11-11 2009-02-24 Citrix Gateways, Inc. System, apparatus and method for establishing a secured communications link to form a virtual private network at a network protocol layer other than at which packets are filtered
US20050122977A1 (en) * 2003-12-05 2005-06-09 Microsoft Corporation Efficient download mechanism for devices with limited local storage
US7760636B1 (en) * 2004-01-26 2010-07-20 Cisco Technology, Inc. Retransmission and flow control in a logical network tunnel
US8611283B2 (en) * 2004-01-28 2013-12-17 Qualcomm Incorporated Method and apparatus of using a single channel to provide acknowledgement and assignment messages
US7792147B1 (en) * 2004-02-09 2010-09-07 Symantec Corporation Efficient assembly of fragmented network traffic for data security
US7616644B2 (en) * 2004-02-25 2009-11-10 Nokia Corporation Method and apparatus providing a protocol to enable a wireless TCP session using a split TCP connection
US7360083B1 (en) 2004-02-26 2008-04-15 Krishna Ragireddy Method and system for providing end-to-end security solutions to aid protocol acceleration over networks using selective layer encryption
US7895648B1 (en) * 2004-03-01 2011-02-22 Cisco Technology, Inc. Reliably continuing a secure connection when the address of a machine at one end of the connection changes
US7539176B1 (en) * 2004-04-02 2009-05-26 Cisco Technology Inc. System and method for providing link, node and PG policy based routing in PNNI based ATM networks
WO2005114960A1 (en) * 2004-05-19 2005-12-01 Computer Associates Think, Inc. Method and apparatus for low-overhead service availability and performance moniroring
US8891349B2 (en) 2004-07-23 2014-11-18 Qualcomm Incorporated Method of optimizing portions of a frame
KR20070083482A (en) 2004-08-13 2007-08-24 사이트릭스 시스템스, 인크. A method for maintaining transaction integrity across multiple remote access servers
TW200608224A (en) * 2004-08-23 2006-03-01 Lite On It Corp Player and method for processing a file with vector-based format
US8224966B2 (en) * 2004-08-24 2012-07-17 Cisco Technology, Inc. Reproxying an unproxied connection
US7895431B2 (en) * 2004-09-10 2011-02-22 Cavium Networks, Inc. Packet queuing, scheduling and ordering
US20060056379A1 (en) * 2004-09-14 2006-03-16 Motorola, Inc. System and method for network-assisted connection in a wireless environment
US8613048B2 (en) 2004-09-30 2013-12-17 Citrix Systems, Inc. Method and apparatus for providing authorized remote access to application sessions
US7711835B2 (en) * 2004-09-30 2010-05-04 Citrix Systems, Inc. Method and apparatus for reducing disclosure of proprietary data in a networked environment
US7748032B2 (en) 2004-09-30 2010-06-29 Citrix Systems, Inc. Method and apparatus for associating tickets in a ticket hierarchy
KR20080042764A (en) * 2004-11-24 2008-05-15 아이에스티 인터내셔널 인코포레이티드 Methods and apparatus for estimating bandwidth of a data network
US7515566B2 (en) * 2004-12-09 2009-04-07 Viasat, Inc. Partial mesh communication in hub based system
US7551620B1 (en) * 2004-12-15 2009-06-23 Orbital Data Corporation Protecting data integrity in an enhanced network connection
US7480301B2 (en) * 2004-12-16 2009-01-20 International Business Machines Corporation Method, system and article for improved TCP performance during retransmission in response to selective acknowledgement
US7453849B2 (en) * 2004-12-22 2008-11-18 Qualcomm Incorporated Method of implicit deassignment of resources
US8238923B2 (en) 2004-12-22 2012-08-07 Qualcomm Incorporated Method of using shared resources in a communication system
US8831115B2 (en) 2004-12-22 2014-09-09 Qualcomm Incorporated MC-CDMA multiplexing in an orthogonal uplink
US8077632B2 (en) * 2005-01-20 2011-12-13 Citrix Systems, Inc. Automatic LAN/WAN port detection
US7581005B2 (en) * 2005-01-20 2009-08-25 Citrix Systems, Inc. Systems and methods for preserving transport layer protocol options
US7664857B2 (en) * 2007-01-26 2010-02-16 Citrix Systems, Inc. Systems and methods of using an IP ID field for automatic WAN/LAN detection
US8024568B2 (en) 2005-01-28 2011-09-20 Citrix Systems, Inc. Method and system for verification of an endpoint security scan
KR100597425B1 (en) * 2005-02-16 2006-06-29 삼성전자주식회사 Method for preventing unnecessary retransmission caused by transmission delay in wireless network and communication apparatus using the same
US9118717B2 (en) * 2005-02-18 2015-08-25 Cisco Technology, Inc. Delayed network protocol proxy for packet inspection in a network
JP4785551B2 (en) * 2005-03-07 2011-10-05 キヤノン株式会社 Executable by the communication apparatus and communication method, and computer program
US9055088B2 (en) * 2005-03-15 2015-06-09 International Business Machines Corporation Managing a communication session with improved session establishment
WO2006099883A1 (en) * 2005-03-23 2006-09-28 Telefonaktiebolaget Lm Ericsson (Publ) System and method for transporting data units through a communication network
US7697524B2 (en) * 2005-04-05 2010-04-13 Cisco Technology, Inc. Method and system for determining path maximum transfer unit for IP multicast
US7535907B2 (en) * 2005-04-08 2009-05-19 Oavium Networks, Inc. TCP engine
US8204080B2 (en) 2005-04-22 2012-06-19 Cisco Technology, Inc. Techniques for encapsulating point to point (PPP) over Ethernet frames
US7525972B2 (en) * 2005-04-22 2009-04-28 Cisco Technology, Inc. Techniques for encapsulating point to point protocol (PPP) over Ethernet frames
WO2007084177A2 (en) * 2005-05-06 2007-07-26 California Institute Of Technology Efficient loss recovery architecture for loss-decoupled tcp
US7706314B2 (en) * 2005-05-20 2010-04-27 Cisco Technology, Inc. Approach for implementing IPsec in performance enhancing proxy (PEP) environments
KR101114737B1 (en) * 2005-05-31 2012-02-29 삼성전자주식회사 Method for reporting packet received result in a mobile communication system
US8929402B1 (en) 2005-09-29 2015-01-06 Silver Peak Systems, Inc. Systems and methods for compressing packet data by predicting subsequent data
US8392684B2 (en) 2005-08-12 2013-03-05 Silver Peak Systems, Inc. Data encryption in a network memory architecture for providing data based on local accessibility
US8370583B2 (en) * 2005-08-12 2013-02-05 Silver Peak Systems, Inc. Network memory architecture for providing data based on local accessibility
DE602005017782D1 (en) * 2005-09-22 2009-12-31 Alcatel Lucent Network device to improve the transmission efficiency by treating the TCP segments
US7940713B2 (en) * 2005-12-08 2011-05-10 Electronics And Telecommunications Research Institute Apparatus and method for traffic performance improvement and traffic security in interactive satellite communication system
EP1798890B1 (en) * 2005-12-15 2009-03-18 Nokia Corporation Methods, device and computer program product for maintaining mapping relationship
US8151323B2 (en) 2006-04-12 2012-04-03 Citrix Systems, Inc. Systems and methods for providing levels of access and action control via an SSL VPN appliance
US8605730B2 (en) * 2006-04-13 2013-12-10 Directpacket Research, Inc. System and method for multimedia communication across disparate networks
US7894509B2 (en) * 2006-05-18 2011-02-22 Harris Corporation Method and system for functional redundancy based quality of service
GB0611249D0 (en) * 2006-06-07 2006-07-19 Nokia Corp Communication system
US8516153B2 (en) 2006-06-16 2013-08-20 Harris Corporation Method and system for network-independent QoS
US7990860B2 (en) 2006-06-16 2011-08-02 Harris Corporation Method and system for rule-based sequencing for QoS
US20070291767A1 (en) * 2006-06-16 2007-12-20 Harris Corporation Systems and methods for a protocol transformation gateway for quality of service
US8064464B2 (en) 2006-06-16 2011-11-22 Harris Corporation Method and system for inbound content-based QoS
US7856012B2 (en) 2006-06-16 2010-12-21 Harris Corporation System and methods for generic data transparent rules to support quality of service
US7916626B2 (en) 2006-06-19 2011-03-29 Harris Corporation Method and system for fault-tolerant quality of service
US8730981B2 (en) 2006-06-20 2014-05-20 Harris Corporation Method and system for compression based quality of service
KR101298265B1 (en) * 2006-07-07 2013-08-22 삼성전자주식회사 Method for receiving and sending packets
US8300653B2 (en) 2006-07-31 2012-10-30 Harris Corporation Systems and methods for assured communications with quality of service
US20100241759A1 (en) * 2006-07-31 2010-09-23 Smith Donald L Systems and methods for sar-capable quality of service
US8885632B2 (en) 2006-08-02 2014-11-11 Silver Peak Systems, Inc. Communications scheduler
US8755381B2 (en) * 2006-08-02 2014-06-17 Silver Peak Systems, Inc. Data matching using flow based packet data storage
US7953889B2 (en) * 2006-08-03 2011-05-31 Citrix Systems, Inc. Systems and methods for routing VPN traffic around network disruption
US8572721B2 (en) * 2006-08-03 2013-10-29 Citrix Systems, Inc. Methods and systems for routing packets in a VPN-client-to-VPN-client connection via an SSL/VPN network appliance
US8677007B2 (en) * 2006-08-03 2014-03-18 Citrix Systems, Inc. Systems and methods for bypassing an appliance
US7907621B2 (en) * 2006-08-03 2011-03-15 Citrix Systems, Inc. Systems and methods for using a client agent to manage ICMP traffic in a virtual private network environment
DE602007006322D1 (en) * 2006-08-18 2010-06-17 Koninkl Philips Electronics Nv decoupled connections
US7769869B2 (en) * 2006-08-21 2010-08-03 Citrix Systems, Inc. Systems and methods of providing server initiated connections on a virtual private network
US8655357B1 (en) * 2006-08-22 2014-02-18 At&T Mobility Ii Llc Systems and methods for identifying applications on a communications device
US7933257B2 (en) * 2006-09-20 2011-04-26 Cisco Technology, Inc. Using QoS tunnels for TCP latency optimization
US7646728B2 (en) * 2006-10-13 2010-01-12 SafeMedia Corp. Network monitoring and intellectual property protection device, system and method
US8102768B2 (en) * 2006-10-18 2012-01-24 D & S Consultants, Inc. Method and system for traffic flow control in a communication network
US8533846B2 (en) 2006-11-08 2013-09-10 Citrix Systems, Inc. Method and system for dynamically associating access rights with a resource
WO2008070660A2 (en) * 2006-12-04 2008-06-12 D & S Consultants, Inc. Integrated quality of service and resource management in a network edge device
US20080137863A1 (en) * 2006-12-06 2008-06-12 Motorola, Inc. Method and system for using a key management facility to negotiate a security association via an internet key exchange on behalf of another device
KR101329150B1 (en) * 2006-12-08 2013-11-14 삼성전자주식회사 PANA Authentication Method and System
US8477804B2 (en) * 2007-03-02 2013-07-02 Hitachi, Ltd. ICMP translator
US7743160B2 (en) * 2007-03-29 2010-06-22 Blue Coat Systems, Inc. System and method of delaying connection acceptance to support connection request processing at layer-7
WO2008143871A1 (en) 2007-05-15 2008-11-27 Radioframe Networks, Inc. Transporting gsm packets over a discontinuous ip based network
US8095774B1 (en) 2007-07-05 2012-01-10 Silver Peak Systems, Inc. Pre-fetching data into a memory
US8171238B1 (en) 2007-07-05 2012-05-01 Silver Peak Systems, Inc. Identification of data stored in memory
US8997115B2 (en) * 2007-08-31 2015-03-31 International Business Machines Corporation Method for data delivery in a network
US8908700B2 (en) * 2007-09-07 2014-12-09 Citrix Systems, Inc. Systems and methods for bridging a WAN accelerator with a security gateway
WO2009055061A1 (en) 2007-10-25 2009-04-30 Trilliant Networks, Inc. Gas meter having ultra-sensitive magnetic material retrofitted onto meter dial and method for performing meter retrofit
US8305896B2 (en) * 2007-10-31 2012-11-06 Cisco Technology, Inc. Selective performance enhancement of traffic flows
EP2257884A4 (en) 2007-11-25 2011-04-20 Trilliant Networks Inc System and method for transmitting and receiving information on a neighborhood area network
EP2215556A4 (en) 2007-11-25 2011-01-19 Trilliant Networks Inc System and method for power outage and restoration notification in an advanced metering infrastructure network
US8138934B2 (en) 2007-11-25 2012-03-20 Trilliant Networks, Inc. System and method for false alert filtering of event messages within a network
EP2215550A1 (en) 2007-11-25 2010-08-11 Trilliant Networks, Inc. Energy use control system and method
WO2009067254A1 (en) * 2007-11-25 2009-05-28 Trilliant Networks, Inc. System and method for operating mesh devices in multi-tree overlapping mesh networks
US8307115B1 (en) * 2007-11-30 2012-11-06 Silver Peak Systems, Inc. Network memory mirroring
US8489562B1 (en) 2007-11-30 2013-07-16 Silver Peak Systems, Inc. Deferred data storage
US7970928B2 (en) * 2007-12-17 2011-06-28 Microsoft Corporation Transparent auto-discovery of network devices logically located between a client and server
US8442052B1 (en) 2008-02-20 2013-05-14 Silver Peak Systems, Inc. Forward packet recovery
US7965721B1 (en) * 2008-03-21 2011-06-21 Nextel Communications Inc. System and method of transferring communications between networks
US7991008B2 (en) * 2008-06-26 2011-08-02 Dell Products L.P. Method for identifying the transmission control protocol stack of a connection
US9717021B2 (en) 2008-07-03 2017-07-25 Silver Peak Systems, Inc. Virtual network overlay
US8743683B1 (en) 2008-07-03 2014-06-03 Silver Peak Systems, Inc. Quality of service using multiple flows
JP5200755B2 (en) * 2008-08-20 2013-06-05 日本電気株式会社 The radio base station, a wireless communication system, path connection method, and program
WO2010027495A1 (en) 2008-09-04 2010-03-11 Trilliant Networks, Inc. A system and method for implementing mesh network communications using a mesh network protocol
US8387112B1 (en) 2008-10-29 2013-02-26 Juniper Networks, Inc. Automatic software update on network devices
US8560908B2 (en) * 2008-11-06 2013-10-15 Qualcomm Incorporated Methods and systems for ARQ feedback message improvement
US8140687B2 (en) * 2008-11-13 2012-03-20 Hughes Network Systems, Llc Performance enhancing proxy handover
US8811431B2 (en) 2008-11-20 2014-08-19 Silver Peak Systems, Inc. Systems and methods for compressing packet data
US8289182B2 (en) 2008-11-21 2012-10-16 Trilliant Networks, Inc. Methods and systems for virtual energy management display
US8891338B2 (en) 2009-01-29 2014-11-18 Itron, Inc. Measuring the accuracy of an endpoint clock from a remote device
EP2406778A4 (en) 2009-03-11 2014-06-25 Trilliant Networks Inc Process, device and system for mapping transformers to meters and locating non-technical line losses
US8325601B2 (en) * 2009-05-08 2012-12-04 Canon Kabushiki Kaisha Reliable network streaming of a single data stream over multiple physical interfaces
US8396960B2 (en) * 2009-05-08 2013-03-12 Canon Kabushiki Kaisha Efficient network utilization using multiple physical interfaces
US8880716B2 (en) * 2009-05-08 2014-11-04 Canon Kabushiki Kaisha Network streaming of a single data stream simultaneously over multiple physical interfaces
US8589570B2 (en) * 2009-08-13 2013-11-19 Verizon Patent And Licensing Inc. Dynamic handler for SIP max-size error
US8781462B2 (en) 2009-09-28 2014-07-15 Itron, Inc. Methodology and apparatus for validating network coverage
US20110134930A1 (en) * 2009-12-09 2011-06-09 Mclaren Moray Packet-based networking system
US20120290727A1 (en) * 2009-12-31 2012-11-15 Bce Inc. Method and system for increasing performance of transmission control protocol sessions in data networks
US9137166B2 (en) * 2010-01-28 2015-09-15 Brocade Communications Systems, Inc. In-order traffic aggregation with reduced buffer usage
US8356109B2 (en) 2010-05-13 2013-01-15 Canon Kabushiki Kaisha Network streaming of a video stream over multiple communication channels
US9294506B2 (en) * 2010-05-17 2016-03-22 Certes Networks, Inc. Method and apparatus for security encapsulating IP datagrams
WO2012027634A1 (en) 2010-08-27 2012-03-01 Trilliant Networkd, Inc. System and method for interference free operation of co-located tranceivers
CA2813534A1 (en) 2010-09-13 2012-03-22 Trilliant Networks, Inc. Process for detecting energy theft
US8832428B2 (en) 2010-11-15 2014-09-09 Trilliant Holdings Inc. System and method for securely communicating across multiple networks using a single radio
US20120131245A1 (en) * 2010-11-19 2012-05-24 Silicon Image, Inc. Transfer of control bus signaling on packet-switched network
US20120151087A1 (en) * 2010-12-14 2012-06-14 Nuvel, Inc. System and method for providing a network proxy data tunnel
US8364641B2 (en) * 2010-12-15 2013-01-29 International Business Machines Corporation Method and system for deduplicating data
US20120163167A1 (en) * 2010-12-27 2012-06-28 Symbol Technologies, Inc. Transmission control protocol optimization systems and methods for wireless networks
US9282383B2 (en) 2011-01-14 2016-03-08 Trilliant Incorporated Process, device and system for volt/VAR optimization
US8970394B2 (en) 2011-01-25 2015-03-03 Trilliant Holdings Inc. Aggregated real-time power outages/restoration reporting (RTPOR) in a secure mesh network
EP3288236A1 (en) 2011-02-10 2018-02-28 Trilliant Holdings, Inc. Device and method for facilitating secure communications over a cellular network
US9041349B2 (en) 2011-03-08 2015-05-26 Trilliant Networks, Inc. System and method for managing load distribution across a power grid
CN102739569B (en) * 2011-04-01 2015-04-15 中国科学院空间科学与应用研究中心 Gateway used in satellite communication and method for enhancing TCP performance
US20130128809A1 (en) * 2011-05-19 2013-05-23 Qualcomm Incorporated Apparatus and methods for media access control header compression
US9515925B2 (en) 2011-05-19 2016-12-06 Qualcomm Incorporated Apparatus and methods for media access control header compression
JP5264966B2 (en) * 2011-07-26 2013-08-14 株式会社日立製作所 Communication device
JP5258938B2 (en) * 2011-07-26 2013-08-07 株式会社日立製作所 Communication device
US9001787B1 (en) 2011-09-20 2015-04-07 Trilliant Networks Inc. System and method for implementing handover of a hybrid communications module
US9167614B2 (en) * 2011-09-28 2015-10-20 Marvell International Ltd. Tunneled direct link setup systems and methods with consistent link information maintenance
US9130991B2 (en) * 2011-10-14 2015-09-08 Silver Peak Systems, Inc. Processing data packets in performance enhancing proxy (PEP) environment
US9626224B2 (en) 2011-11-03 2017-04-18 Silver Peak Systems, Inc. Optimizing available computing resources within a virtual environment
TWI459768B (en) 2011-12-30 2014-11-01 Ind Tech Res Inst Communication system and method for assisting transmission of tcp packets
US9025475B1 (en) * 2012-01-16 2015-05-05 Amazon Technologies, Inc. Proactively retransmitting data packets in a low latency packet data network
US9742732B2 (en) * 2012-03-12 2017-08-22 Varmour Networks, Inc. Distributed TCP SYN flood protection
US8938804B2 (en) * 2012-07-12 2015-01-20 Telcordia Technologies, Inc. System and method for creating BGP route-based network traffic profiles to detect spoofed traffic
US9264365B2 (en) 2012-07-31 2016-02-16 International Business Machines Corporation Split transport control protocol (TCP) flow control management in a cellular broadband network
US9236936B2 (en) * 2012-08-31 2016-01-12 Hughes Network Systems, Llc System and method for low-complexity, high-speed preprocessing of encapsulated packets in a broadband communications network
US9258335B1 (en) 2012-09-17 2016-02-09 Amazon Technologies, Inc. Connection-aggregation proxy service
CN103795632B (en) 2012-10-31 2017-02-22 华为技术有限公司 A data packet transmission method and related apparatus, systems
JP6095362B2 (en) * 2012-12-27 2017-03-15 古野電気株式会社 Satellite communication apparatus and a satellite communication system
US9413652B2 (en) 2013-02-19 2016-08-09 Dell Products L.P. Systems and methods for path maximum transmission unit discovery
US9887925B2 (en) * 2013-03-04 2018-02-06 Gilat Satellite Networks Ltd. Network performance enhancement
US9549371B2 (en) 2013-03-14 2017-01-17 Qualcomm Incorporated Access point proxy and multi-hop wireless communication
US9282172B2 (en) * 2013-05-10 2016-03-08 Blackberry Limited System and method for relaying data based on a modified reliable transport protocol
US9491261B1 (en) * 2013-07-29 2016-11-08 Amazon Technologies, Inc. Remote messaging protocol
US10102755B1 (en) 2013-10-07 2018-10-16 Satcom Direct, Inc. Method and system for aircraft positioning—automated tracking using onboard global voice and high-speed data
US9565618B1 (en) 2013-10-09 2017-02-07 Satcom Direct, Inc. Air to ground management of multiple communication paths
US9553658B1 (en) 2013-10-09 2017-01-24 Satcom Direct, Inc. Router for aircraft communications with simultaneous satellite connections
US9577742B1 (en) * 2013-10-10 2017-02-21 Satcom Direct, Inc. Data compression and acceleration for air to ground communications
JP2015095680A (en) * 2013-11-08 2015-05-18 株式会社日立製作所 Communication device and communication system
US9191377B2 (en) * 2013-11-27 2015-11-17 Architecture Technology Corporation Method for network communication past encryption devices
US9887974B2 (en) 2013-11-27 2018-02-06 Architecture Technology Corporation Method for network communication past encryption devices
US9160553B2 (en) 2013-11-27 2015-10-13 Architecture Technology Corporation Adaptive multicast network communications
US9635114B2 (en) * 2014-01-24 2017-04-25 Netapp, Inc. Externally initiated application session endpoint migration
US10049508B2 (en) 2014-02-27 2018-08-14 Satcom Direct, Inc. Automated flight operations system
US9009332B1 (en) 2014-07-18 2015-04-14 Kaspersky Lab Zao Protection against network-based malicious activity utilizing transparent proxy services
US9948496B1 (en) 2014-07-30 2018-04-17 Silver Peak Systems, Inc. Determining a transit appliance for data traffic to a software service
US9875344B1 (en) 2014-09-05 2018-01-23 Silver Peak Systems, Inc. Dynamic monitoring and authorization of an optimization device
US9554275B1 (en) 2014-10-19 2017-01-24 Satcom Direct, Inc. Voice and SMS communication from a mobile device over IP network and satellite or other communication network
US9503362B2 (en) * 2015-01-07 2016-11-22 Vmware, Inc. Reverse path maximum transmission unit (PMTU) discovery
US9973472B2 (en) 2015-04-02 2018-05-15 Varmour Networks, Inc. Methods and systems for orchestrating physical and virtual switches to enforce security boundaries
US9525697B2 (en) 2015-04-02 2016-12-20 Varmour Networks, Inc. Delivering security functions to distributed networks
JP2016208315A (en) * 2015-04-23 2016-12-08 富士通株式会社 Communication device, communication processing method, and communication program
US9491282B1 (en) * 2015-05-13 2016-11-08 Cisco Technology, Inc. End-to-end call tracing
CN105491016A (en) * 2015-07-21 2016-04-13 成都理工大学 Method for hiding network TCP port
US9819602B2 (en) * 2015-07-27 2017-11-14 Qualcomm Incorporated Efficient datagram segmentation and reassembly for packet-switched networks
US9979466B2 (en) * 2015-08-06 2018-05-22 Space Systems/Loral, Llc Reverse wireless broadband system
US9483317B1 (en) 2015-08-17 2016-11-01 Varmour Networks, Inc. Using multiple central processing unit cores for packet forwarding in virtualized networks
WO2017053964A1 (en) 2015-09-25 2017-03-30 Fsa Technologies, Inc. Data flow prioritization system and method
US10164861B2 (en) 2015-12-28 2018-12-25 Silver Peak Systems, Inc. Dynamic monitoring and visualization for network health characteristics
US9967056B1 (en) 2016-08-19 2018-05-08 Silver Peak Systems, Inc. Forward packet recovery with constrained overhead
CN106385279A (en) * 2016-09-14 2017-02-08 西安远眺卫星通信有限公司 Wireless routing device and method for satellite communication
US9876612B1 (en) * 2017-02-06 2018-01-23 Naveen Maveli Data bandwidth overhead reduction in a protocol based communication over a wide area network (WAN)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6273622B1 (en) * 1997-04-15 2001-08-14 Flash Networks, Ltd. Data communication protocol for maximizing the performance of IP communication links
US20020071436A1 (en) * 2000-07-21 2002-06-13 John Border Method and system for providing connection handling
US6529516B1 (en) * 1996-06-20 2003-03-04 Fourelle Systems, Inc. Gateway architecture for data communication over bandwidth-constrained and charge-by-use networks
US20030069926A1 (en) * 2001-10-09 2003-04-10 Weaver Jeffrey Charles System and method for managing an exchange between a gateway server and a client-side module
US20030079022A1 (en) * 2001-10-23 2003-04-24 Mentat Inc. Multicast delivery systems and methods
US7082467B2 (en) * 2000-02-10 2006-07-25 Hughes Network Systems Method and device for selective transport level spoofing based on information in transport level packet

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE69739398D1 (en) * 1996-03-15 2009-06-25 Juniper Networks Inc Design of a closed control loop for operating ABR
US6339595B1 (en) * 1997-12-23 2002-01-15 Cisco Technology, Inc. Peer-model support for virtual private networks with potentially overlapping addresses
US6415329B1 (en) * 1998-03-06 2002-07-02 Massachusetts Institute Of Technology Method and apparatus for improving efficiency of TCP/IP protocol over high delay-bandwidth network
US6341129B1 (en) * 1998-04-03 2002-01-22 Alteon Networks, Inc. TCP resegmentation
US6594701B1 (en) * 1998-08-04 2003-07-15 Microsoft Corporation Credit-based methods and systems for controlling data flow between a sender and a receiver with reduced copying of data
US6327626B1 (en) * 1998-09-15 2001-12-04 Alteon Networks, Inc. Method and apparatus for MSS spoofing
US6215769B1 (en) * 1998-10-07 2001-04-10 Nokia Telecommunications, Inc. Enhanced acknowledgment pacing device and method for TCP connections
US6496505B2 (en) * 1998-12-11 2002-12-17 Lucent Technologies Inc. Packet tunneling optimization to wireless devices accessing packet-based wired networks
US6460085B1 (en) * 1999-02-02 2002-10-01 Mentat Inc. Method and system for managing memory in an internet over satellite connection
US6584083B1 (en) * 1999-02-02 2003-06-24 Mentat Inc. Internet over satellite method
US6529477B1 (en) * 1999-02-02 2003-03-04 Mentat Inc. Internet over satellite system
US6654344B1 (en) * 1999-02-02 2003-11-25 Mentat Inc. Method and system for controlling data flow in an internet over satellite connection
US6438108B1 (en) * 1999-03-11 2002-08-20 Telefonaktiebolaget L M Ericsson (Publ) System for improved transmission of acknowledgements within a packet data network
US6553032B1 (en) * 1999-09-01 2003-04-22 Tantivy Communications, Inc. Packeting timeout spoofing in a wireless data communications network
US6763005B1 (en) * 1999-10-01 2004-07-13 Nortel Networks Limited Satellite traffic routing
EP1240753A1 (en) * 1999-12-13 2002-09-18 Nokia Corporation Congestion control method for a packet-switched network
US7213063B2 (en) * 2000-01-18 2007-05-01 Lucent Technologies Inc. Method, apparatus and system for maintaining connections between computers using connection-oriented protocols
US6947440B2 (en) * 2000-02-15 2005-09-20 Gilat Satellite Networks, Ltd. System and method for internet page acceleration including multicast transmissions
US8359405B1 (en) * 2000-02-28 2013-01-22 John Border Performance enhancing proxy and method for enhancing performance
US6741555B1 (en) * 2000-06-14 2004-05-25 Nokia Internet Communictions Inc. Enhancement of explicit congestion notification (ECN) for wireless network applications

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6529516B1 (en) * 1996-06-20 2003-03-04 Fourelle Systems, Inc. Gateway architecture for data communication over bandwidth-constrained and charge-by-use networks
US6273622B1 (en) * 1997-04-15 2001-08-14 Flash Networks, Ltd. Data communication protocol for maximizing the performance of IP communication links
US7082467B2 (en) * 2000-02-10 2006-07-25 Hughes Network Systems Method and device for selective transport level spoofing based on information in transport level packet
US20020071436A1 (en) * 2000-07-21 2002-06-13 John Border Method and system for providing connection handling
US20030069926A1 (en) * 2001-10-09 2003-04-10 Weaver Jeffrey Charles System and method for managing an exchange between a gateway server and a client-side module
US20030079022A1 (en) * 2001-10-23 2003-04-24 Mentat Inc. Multicast delivery systems and methods

Cited By (120)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080175205A1 (en) * 2002-02-07 2008-07-24 Siemens Aktiengesellschaft Method of Downloading Data in a Radio Communications System
US8543080B2 (en) 2002-02-07 2013-09-24 Siemens Aktiengesellschaft Method of downloading data in a radio communications system
US20050083924A1 (en) * 2002-02-07 2005-04-21 Markus Dillinger Method for downloading data in a radio communications system
US7369517B2 (en) * 2002-02-07 2008-05-06 Siemens Aktiengesellschaft Method for downloading data in a radio communications system
US8553699B2 (en) 2002-10-30 2013-10-08 Citrix Systems, Inc. Wavefront detection and disambiguation of acknowledgements
US9008100B2 (en) 2002-10-30 2015-04-14 Citrix Systems, Inc. Wavefront detection and disambiguation of acknowledgments
US7969876B2 (en) 2002-10-30 2011-06-28 Citrix Systems, Inc. Method of determining path maximum transmission unit
US9496991B2 (en) 2002-10-30 2016-11-15 Citrix Systems, Inc. Systems and methods of using packet boundaries for reduction in timeout prevention
US8259729B2 (en) 2002-10-30 2012-09-04 Citrix Systems, Inc. Wavefront detection and disambiguation of acknowledgements
US8411560B2 (en) 2002-10-30 2013-04-02 Citrix Systems, Inc. TCP selection acknowledgements for communicating delivered and missing data packets
US20110044236A1 (en) * 2003-05-27 2011-02-24 Macdonald, Dettwiler And Associates Ltd. Satellite communications system for providing global, high quality movement of very large data files
US8412851B2 (en) 2003-05-27 2013-04-02 Macdonald, Dettwiler And Associates Ltd. Satellite communications system for providing global, high quality movement of very large data files
US20060155840A1 (en) * 2003-05-27 2006-07-13 Macdonald Dettwiler And Associates Ltd. Satellite communications system for providing global, high quality movement of very large data files
US9369883B2 (en) 2003-05-27 2016-06-14 Macdonald, Dettwiler And Associates Ltd. Satellite communications system for providing global, high quality movement of very large data files
US7783734B2 (en) 2003-05-27 2010-08-24 Macdonald, Dettwiler And Associates Ltd. Satellite communications system for providing global, high quality movement of very large data files
US20040264368A1 (en) * 2003-06-30 2004-12-30 Nokia Corporation Data transfer optimization in packet data networks
US8233392B2 (en) 2003-07-29 2012-07-31 Citrix Systems, Inc. Transaction boundary detection for reduction in timeout penalties
US8310928B2 (en) * 2003-07-29 2012-11-13 Samuels Allen R Flow control system architecture
US9071543B2 (en) 2003-07-29 2015-06-30 Citrix Systems, Inc. Systems and methods for additional retransmissions of dropped packets
US8270423B2 (en) 2003-07-29 2012-09-18 Citrix Systems, Inc. Systems and methods of using packet boundaries for reduction in timeout prevention
US20050058131A1 (en) * 2003-07-29 2005-03-17 Samuels Allen R. Wavefront detection and disambiguation of acknowledgments
US20050063307A1 (en) * 2003-07-29 2005-03-24 Samuels Allen R. Flow control system architecture
US20050063303A1 (en) * 2003-07-29 2005-03-24 Samuels Allen R. TCP selective acknowledgements for communicating delivered and missed data packets
US8432800B2 (en) 2003-07-29 2013-04-30 Citrix Systems, Inc. Systems and methods for stochastic-based quality of service
US8462630B2 (en) 2003-07-29 2013-06-11 Citrix Systems, Inc. Early generation of acknowledgements for flow control
US7616638B2 (en) 2003-07-29 2009-11-10 Orbital Data Corporation Wavefront detection and disambiguation of acknowledgments
US7630305B2 (en) 2003-07-29 2009-12-08 Orbital Data Corporation TCP selective acknowledgements for communicating delivered and missed data packets
US7656799B2 (en) * 2003-07-29 2010-02-02 Citrix Systems, Inc. Flow control system architecture
US8824490B2 (en) 2003-07-29 2014-09-02 Citrix Systems, Inc. Automatic detection and window virtualization for flow control
US7698453B2 (en) 2003-07-29 2010-04-13 Oribital Data Corporation Early generation of acknowledgements for flow control
US8437284B2 (en) 2003-07-29 2013-05-07 Citrix Systems, Inc. Systems and methods for additional retransmissions of dropped packets
US8238241B2 (en) * 2003-07-29 2012-08-07 Citrix Systems, Inc. Automatic detection and window virtualization for flow control
US8559449B2 (en) 2003-11-11 2013-10-15 Citrix Systems, Inc. Systems and methods for providing a VPN solution
US20050210122A1 (en) * 2004-03-22 2005-09-22 Qualcomm Incorporated HTTP acceleration over a network link
US20050210121A1 (en) * 2004-03-22 2005-09-22 Qualcomm Incorporated Satellite anticipatory bandwith acceleration
US20080177829A1 (en) * 2004-04-29 2008-07-24 International Business Machines Corporation Data Communications Through A Split Connection Proxy
US20060031571A1 (en) * 2004-04-29 2006-02-09 International Business Machines Corporation Data communications through a split connection proxy
US20070280115A1 (en) * 2004-06-22 2007-12-06 Michael Meyer Network Feedback Method and Device
US8416694B2 (en) * 2004-06-22 2013-04-09 Telefonaktiebolaget Lm Ericsson (Publ) Network feedback method and device
US8726006B2 (en) 2004-06-30 2014-05-13 Citrix Systems, Inc. System and method for establishing a virtual private network
US8261057B2 (en) 2004-06-30 2012-09-04 Citrix Systems, Inc. System and method for establishing a virtual private network
US8495305B2 (en) 2004-06-30 2013-07-23 Citrix Systems, Inc. Method and device for performing caching of dynamically generated objects in a data communication network
US8739274B2 (en) 2004-06-30 2014-05-27 Citrix Systems, Inc. Method and device for performing integrated caching in a data communication network
US8291119B2 (en) 2004-07-23 2012-10-16 Citrix Systems, Inc. Method and systems for securing remote access to private networks
US8897299B2 (en) 2004-07-23 2014-11-25 Citrix Systems, Inc. Method and systems for routing packets from a gateway to an endpoint
US8014421B2 (en) 2004-07-23 2011-09-06 Citrix Systems, Inc. Systems and methods for adjusting the maximum transmission unit by an intermediary device
US8363650B2 (en) 2004-07-23 2013-01-29 Citrix Systems, Inc. Method and systems for routing packets from a gateway to an endpoint
US7808906B2 (en) 2004-07-23 2010-10-05 Citrix Systems, Inc. Systems and methods for communicating a lossy protocol via a lossless protocol using false acknowledgements
US8634420B2 (en) 2004-07-23 2014-01-21 Citrix Systems, Inc. Systems and methods for communicating a lossy protocol via a lossless protocol
US20060190719A1 (en) * 2004-07-23 2006-08-24 Citrix Systems, Inc. Systems and methods for communicating a lossy protocol via a lossless protocol using false acknowledgements
US8892778B2 (en) 2004-07-23 2014-11-18 Citrix Systems, Inc. Method and systems for securing remote access to private networks
US8914522B2 (en) 2004-07-23 2014-12-16 Citrix Systems, Inc. Systems and methods for facilitating a peer to peer route via a gateway
US9219579B2 (en) 2004-07-23 2015-12-22 Citrix Systems, Inc. Systems and methods for client-side application-aware prioritization of network communications
US8351333B2 (en) 2004-07-23 2013-01-08 Citrix Systems, Inc. Systems and methods for communicating a lossy protocol via a lossless protocol using false acknowledgements
US20060059273A1 (en) * 2004-09-16 2006-03-16 Carnevale Michael J Envelope packet architecture for broadband engine
US7975064B2 (en) * 2004-09-16 2011-07-05 International Business Machines Corporation Envelope packet architecture for broadband engine
US9888470B2 (en) 2004-11-19 2018-02-06 Viasat, Inc. Network accelerator for controlled long delay links
US9301312B2 (en) 2004-11-19 2016-03-29 Viasat, Inc. Network accelerator for controlled long delay links
US8719409B2 (en) 2004-11-19 2014-05-06 Viasat, Inc. Network accelerator for controlled long delay links
US20100274901A1 (en) * 2004-11-19 2010-10-28 Viasat, Inc. Network accelerator for controlled long delay links
US8359387B2 (en) * 2004-11-19 2013-01-22 Viasat, Inc. Network accelerator for controlled long delay links
US8549149B2 (en) 2004-12-30 2013-10-01 Citrix Systems, Inc. Systems and methods for providing client-side accelerated access to remote applications via TCP multiplexing
US8856777B2 (en) 2004-12-30 2014-10-07 Citrix Systems, Inc. Systems and methods for automatic installation and execution of a client-side acceleration program
US8706877B2 (en) 2004-12-30 2014-04-22 Citrix Systems, Inc. Systems and methods for providing client-side dynamic redirection to bypass an intermediary
US8700695B2 (en) 2004-12-30 2014-04-15 Citrix Systems, Inc. Systems and methods for providing client-side accelerated access to remote applications via TCP pooling
US8954595B2 (en) 2004-12-30 2015-02-10 Citrix Systems, Inc. Systems and methods for providing client-side accelerated access to remote applications via TCP buffering
US8848710B2 (en) 2005-01-24 2014-09-30 Citrix Systems, Inc. System and method for performing flash caching of dynamically generated objects in a data communication network
US8788581B2 (en) 2005-01-24 2014-07-22 Citrix Systems, Inc. Method and device for performing caching of dynamically generated objects in a data communication network
US7849270B2 (en) 2005-01-24 2010-12-07 Citrix Systems, Inc. System and method for performing entity tag and cache control of a dynamically generated object not identified as cacheable in a network
US7849269B2 (en) 2005-01-24 2010-12-07 Citrix Systems, Inc. System and method for performing entity tag and cache control of a dynamically generated object not identified as cacheable in a network
US20060262724A1 (en) * 2005-05-17 2006-11-23 Daniel Friedman Method and system for efficient flow control in a spot beam satellite system
US8675486B2 (en) * 2005-05-17 2014-03-18 Hughes Network Systems, Llc Method and system for efficient flow control in a spot beam satellite system
US8255456B2 (en) 2005-12-30 2012-08-28 Citrix Systems, Inc. System and method for performing flash caching of dynamically generated objects in a data communication network
US20070153677A1 (en) * 2005-12-30 2007-07-05 Honeywell International Inc. Method and system for integration of wireless devices with a distributed control system
US8406220B2 (en) * 2005-12-30 2013-03-26 Honeywell International Inc. Method and system for integration of wireless devices with a distributed control system
US8499057B2 (en) 2005-12-30 2013-07-30 Citrix Systems, Inc System and method for performing flash crowd caching of dynamically generated objects in a data communication network
US8301839B2 (en) 2005-12-30 2012-10-30 Citrix Systems, Inc. System and method for performing granular invalidation of cached dynamically generated objects in a data communication network
US20070156879A1 (en) * 2006-01-03 2007-07-05 Klein Steven E Considering remote end point performance to select a remote end point to use to transmit a task
US8004973B2 (en) 2006-04-25 2011-08-23 Citrix Systems, Inc. Virtual inline configuration for a network device
US9100449B2 (en) 2006-04-25 2015-08-04 Citrix Systems, Inc. Virtual inline configuration for a network device
US20070248090A1 (en) * 2006-04-25 2007-10-25 Haseeb Budhani Virtual inline configuration for a network device
US8312120B2 (en) 2006-08-22 2012-11-13 Citrix Systems, Inc. Systems and methods for providing dynamic spillover of virtual servers based on bandwidth
US8493858B2 (en) 2006-08-22 2013-07-23 Citrix Systems, Inc Systems and methods for providing dynamic connection spillover among virtual servers
US20080049786A1 (en) * 2006-08-22 2008-02-28 Maruthi Ram Systems and Methods for Providing Dynamic Spillover of Virtual Servers Based on Bandwidth
US9185019B2 (en) 2006-08-22 2015-11-10 Citrix Systems, Inc. Systems and methods for providing dynamic connection spillover among virtual servers
US8275871B2 (en) 2006-08-22 2012-09-25 Citrix Systems, Inc. Systems and methods for providing dynamic spillover of virtual servers based on bandwidth
US20100046546A1 (en) * 2006-08-22 2010-02-25 Maruthi Ram Systems and methods for providing dynamic spillover of virtual servers based on bandwidth
US20080181108A1 (en) * 2006-10-06 2008-07-31 Viasat, Inc. Dynamic Feedback For Outbound Link Rate Adjustment In Multi-Rate Downstream
US8060593B2 (en) * 2006-10-10 2011-11-15 Mitsubishi Electric Corporation Protection of data transmission network systems against buffer oversizing
JP2008136176A (en) * 2006-10-10 2008-06-12 Mitsubishi Electric Information Technology Centre Europa Bv Method and device for managing allocation of memory blocks, data transmission network system, computer-readable medium, and computer program product
US20080256247A1 (en) * 2006-10-10 2008-10-16 Mitsubishi Electric Corporation Protection of data transmission network systems against buffer oversizing
US8462631B2 (en) 2007-03-12 2013-06-11 Citrix Systems, Inc. Systems and methods for providing quality of service precedence in TCP congestion control
US7706266B2 (en) 2007-03-12 2010-04-27 Citrix Systems, Inc. Systems and methods of providing proxy-based quality of service
US7796510B2 (en) 2007-03-12 2010-09-14 Citrix Systems, Inc. Systems and methods for providing virtual fair queueing of network traffic
US8184534B2 (en) 2007-03-12 2012-05-22 Citrix Systems, Inc. Systems and methods of providing proxy-based quality of service
EP1976202B1 (en) 2007-03-12 2016-03-09 Viprinet Europe GmbH Device and method for transmitting a data stream over bundled network access cables, as well as transmission and reception aid device and transmission and reception method for same
US8531944B2 (en) 2007-03-12 2013-09-10 Citrix Systems, Inc. Systems and methods for providing virtual fair queuing of network traffic
US20080225728A1 (en) * 2007-03-12 2008-09-18 Robert Plamondon Systems and methods for providing virtual fair queueing of network traffic
US20080225715A1 (en) * 2007-03-12 2008-09-18 Robert Plamondon Systems and methods of providing proxy-based quality of service
US10248465B2 (en) * 2008-01-23 2019-04-02 Comptel Corporation Convergent mediation system with dynamic resource allocation
US8958363B2 (en) 2008-10-15 2015-02-17 Viasat, Inc. Profile-based bandwidth scheduler
US9954603B2 (en) 2008-10-15 2018-04-24 Viasat, Inc. Profile-based bandwidth scheduler
US20100091699A1 (en) * 2008-10-15 2010-04-15 Viasat, Inc. Profile-based bandwidth scheduler
US8374091B2 (en) * 2009-03-26 2013-02-12 Empire Technology Development Llc TCP extension and variants for handling heterogeneous applications
US20130121148A1 (en) * 2009-03-26 2013-05-16 Empire Technology Development Llc Tcp extension and variants for handling heterogeneous applications
US8705367B2 (en) * 2009-03-26 2014-04-22 Empire Technology Development Llc TCP extension and variants for handling heterogeneous applications
US20100246398A1 (en) * 2009-03-26 2010-09-30 Mung Chiang Tcp extension and variants for handling heterogeneous applications
US9071526B2 (en) 2009-06-22 2015-06-30 Citrix Systems, Inc. Systems and methods for platform rate limiting
US20100322071A1 (en) * 2009-06-22 2010-12-23 Roman Avdanin Systems and methods for platform rate limiting
US8780823B1 (en) 2009-10-08 2014-07-15 Viasat, Inc. Event driven grant allocation
US10218818B2 (en) * 2009-12-18 2019-02-26 Google Llc Matching encoder output to network bandwidth
US8745209B2 (en) * 2009-12-18 2014-06-03 Google Inc. Matching encoder output to network bandwidth
US20140254613A1 (en) * 2009-12-18 2014-09-11 Google Inc. Matching encoder output to network bandwidth
US20110153816A1 (en) * 2009-12-18 2011-06-23 Google Inc. Matching Encoder Output to Network Bandwidth
US20130176847A1 (en) * 2012-01-09 2013-07-11 Ntt Docomo, Inc. Communication processing method, apparatus and gateway device
US9167473B2 (en) * 2012-01-09 2015-10-20 Ntt Docomo, Inc. Communication processing method, apparatus and gateway device
WO2016100890A1 (en) * 2014-12-19 2016-06-23 Nokia Solutions And Networks Oy Smooth bandwidth-delay product variation inside wireless networks
US20180152278A1 (en) * 2016-11-30 2018-05-31 International Business Machines Corporation Multi-domain connection establishment in computer networking communications
US10057045B2 (en) * 2016-11-30 2018-08-21 International Business Machines Corporation Multi-domain connection establishment in computer networking communications
EP3399707A1 (en) * 2017-05-04 2018-11-07 Global Eagle Entertainment Inc. Data flow control for dual ended transmission control protocol performance enhancement proxies

Also Published As

Publication number Publication date
EP1446931A1 (en) 2004-08-18
CA2473863A1 (en) 2003-05-22
AU2002352637A1 (en) 2003-05-26
US20030131079A1 (en) 2003-07-10
WO2003043289A3 (en) 2004-01-29
US6975647B2 (en) 2005-12-13
AU2002357711A1 (en) 2003-05-26
US20030123481A1 (en) 2003-07-03
WO2003043288A1 (en) 2003-05-22
WO2003043285A2 (en) 2003-05-22
WO2003043285A3 (en) 2004-06-10
WO2003043289A2 (en) 2003-05-22

Similar Documents

Publication Publication Date Title
Lakshman et al. The performance of TCP/IP for networks with high bandwidth-delay products and random loss
Ramakrishnan et al. A proposal to add explicit congestion notification (ECN) to IP
AU750222B2 (en) Method and apparatus for selectively allocating and enforcing bandwidth usage requirements on network users
Floyd Congestion control principles
US7969876B2 (en) Method of determining path maximum transmission unit
US6233224B1 (en) Communication method and data communications terminal, with data communication protocol for inter-layer flow control
JP4351159B2 (en) Management of quality of service in the network gateway
EP1295428B1 (en) Performance enhancement of transmission control protocol (tcp) for wireless network applications
EP1876779B1 (en) Congestion and delay handling in a packet data network
US6741555B1 (en) Enhancement of explicit congestion notification (ECN) for wireless network applications
Balakrishnan et al. An integrated congestion management architecture for Internet hosts
Balakrishnan et al. The effects of asymmetry on TCP performance
US6118765A (en) System method and computer program product for eliminating unnecessary retransmissions
EP1175045A2 (en) Method and system for using a backbone protocol to improve network performance
Ghani et al. TCP/IP enhancements for satellite networks
US6115357A (en) Method for pacing data flow in a packet-based network
US20050249114A1 (en) Method and device of dynamic resource allocation in a wireless network
AU772524B2 (en) Method and system for discarding and regenerating acknowledgment packets in ADSL communications
Camarillo et al. Evaluation of transport protocols for the session initiation protocol
US6584083B1 (en) Internet over satellite method
US6529477B1 (en) Internet over satellite system
US8824490B2 (en) Automatic detection and window virtualization for flow control
US20060165029A1 (en) Protecting real-time data in wireless networks
US6954797B1 (en) Data Communication method, terminal equipment, interconnecting installation, data communication system and recording medium
US6904058B2 (en) Transmitting data over a general packet radio service wireless network

Legal Events

Date Code Title Description
AS Assignment

Owner name: EMS TECHNOLOGIES, INC., GEORGIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NEALE, JASON;PETHER, ANDREW M.;MOHSEN, ABDUL-KADER;AND OTHERS;REEL/FRAME:013825/0928;SIGNING DATES FROM 20030224 TO 20030303

AS Assignment

Owner name: SUNTRUST BANK, GEORGIA

Free format text: SECURITY INTEREST;ASSIGNOR:EMS TECHNOLOGIES, INC.;REEL/FRAME:015484/0604

Effective date: 20041210

AS Assignment

Owner name: EMS TECHNOLOGIES CANADA, LTD., CANADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EMS TECHNOLOGIES, INC.;REEL/FRAME:016896/0621

Effective date: 20050726

AS Assignment

Owner name: ADVANTECH SATELLITE NETWORKS INC., CANADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EMS TECHNOLOGIES CANADA, LTD.;REEL/FRAME:017783/0275

Effective date: 20060309