US20080222304A1 - Apparatus and methods for providing translucent proxies in a communications network - Google Patents
Apparatus and methods for providing translucent proxies in a communications network Download PDFInfo
- Publication number
- US20080222304A1 US20080222304A1 US12/127,883 US12788308A US2008222304A1 US 20080222304 A1 US20080222304 A1 US 20080222304A1 US 12788308 A US12788308 A US 12788308A US 2008222304 A1 US2008222304 A1 US 2008222304A1
- Authority
- US
- United States
- Prior art keywords
- proxy
- request
- destination
- data
- source
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/2871—Implementation details of single intermediate entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/163—In-band adaptation of TCP data exchange; In-band control procedures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
Abstract
The Translucent Proxying of TCP (TPOT) device and methods use TCP-OPTIONS and IP tunneling to guarantee that all IP packets belonging to a specific TCP connection will traverse the proxy which intercepts the first packet of data. This guarantee allows the ad-hoc deployment of TPOT devices anywhere within the communication network, and does not restrict the placement of proxy devices at the edge of the network. Furthermore, no extra signaling support is required for the TPOT device to properly function while the addition of TPOT devices to communication networks significantly improves the throughput of intercepted TCP packets of data.
Description
- This application is a continuation of U.S. patent application Ser. No. 11/213,061 filed Aug. 26, 2005 entitled, “APPARATUS AND METHODS FOR PROVIDING TRANSLUCENT PROXIES IN A COMMUNICATIONS NETWORK” which is a continuation of U.S. patent application Ser. No. 09/713,214 filed Nov. 16, 2000, entitled “APPARATUS AND METHODS FOR PROVIDING TRANSLUCENT PROXIES IN A COMMUNICATIONS NETWORK”, now issued as U.S. Pat. No. 7,016,973 on Mar. 21, 2006, and claims priority to U.S. Provisional Application filed Nov. 19, 1999 and assigned Ser. No. 60/166,433. The aforementioned related patent applications are all herein incorporated by reference.
- 1. Field of Invention
- This invention relates to communication systems.
- 2. Description of Related Art
- Currently, transparent layer proxies are being widely deployed in the Internet to enable a vast variety of applications. The proxies are used for web proxy caching, as transcoders, firewalls and to distribute load among a group of servers. Transparent proxies are commonly used in solutions when an application is to be proxied in a manner that is completely invisible to a client, without requiring any prior configuration. Recently, there has been a great deal of activity in the area of transparent proxies for Web caching. A proxy server caches information for internal users who access and request information via the Internet. These Web caching devices cache often-accessed pages to improve access for Internet users.
- In the simplest scenario, a transparent proxy intercepts all Transmission Control Protocol (TCP) packets of data that are routed through the transparent proxy. This function may be refined by having the proxy intercept TCP packets destined only for specific ports or a specific set of destination addresses. The proxy's function is to respond to the client request, many times while masquerading as the remote web server. Scalability is achieved by partitioning client requests into separate hash buckets based on the destination address, effectively mapping web service to multiple caches attached to the proxy.
- Two types of proxies are commonly used at Layer 4 and Layer 7 of the OSI networking stack. A Layer-4 switch (or simply L-4 switch) functions to intercept TCP packets of data as described earlier. However, a Layer-7 switch (or L-7 switch) parses a Hyper Text Transfer Protocol (HTTP) request and extracts the Universal Resource Locator (URL), and possibly other fields of the HTTP request before deciding what to do with the request. Furthermore, the inspection of the HTTP request takes part in the applications layer or Layer 7.
- A problem associated with the use of transparent L-4 and L-7 Web proxies is that the proxies must be located at focal points in a network to ensure that all IP packets of an intercepted TCP connection are seen by the intercepting transparent proxy. Since routing functions in an Internet Protocol (IP) network can lead to situations where multiple paths from client to server may be cost effective, situations may occur where packets of a connection follow multiple paths. Subsequently, in this situation, a transparent proxy may see only a fraction of packets of a specific connection. In another situation, routes may change mid-way through a TCP connection due to routing updates within the IP network. For these reasons, transparent proxies are deployed exclusively at the edges or focal points within a network and used as gateways to/from single-homed client or servers. However, locating the proxy at the edge or focal point with a network is not always the best place to deploy a proxy acting as a Web cache. Studies for Web caching file objects suggest that a Web cache is more effective when it is located inside the network instead of at the edge of a network.
- Accordingly, there is a need for new technology that will allow more flexibility in the placement of proxy devices anywhere in a communications network.
- The present invention provides an apparatus for allowing proxies to be located anywhere within a communications network. In addition to allowing the placement of proxy devices anywhere in a network, the Translucent Proxying of TCP (TPOT) device of the claimed invention is an intermediary device that also enables newer architectures that employ non-TPOT enabled web proxy networks to be used in accordance with the present invention. In general, such architectures require the placement of multiple proxies within the network, not just at their edges and gateways. Existing proposals are either not transparent, or require the guarantee that all packets of the connection will pass through an intercepted proxy. A TPOT proxy according to the present invention located along the path from the client to the server simply picks up the request and satisfies the request from the TPOT proxy's own cache, or lets the request pass through. None of the TPOT functions require extra signaling support or knowledge of neighbors to function correctly. Because TPOT is a lightweight solution that does not require a complete overhaul of an existing IP networks, the TPOT can be deployed incrementally and can co-exist with other Internet traffic.
- The TPOT device and methods use TCP-OPTIONS and IP tunneling to guarantee that all IP packets belonging to a specific TCP connection will traverse the proxy which intercepts the first packet of data. This guarantee allows the deployment of TPOT devices anywhere within the communication network, and does not restrict a network system engineer to only placing the proxy device on the edge of a network. Furthermore, no extra signaling support is required for the TPOT device to properly function. Accordingly, the addition of TPOT devices to communication networks will significantly improve the throughput of intercepted TCP packets of data.
- The invention is described in detail with regard to the following figures, in which like elements are referred to with like numerals, and in which:
-
FIG. 1 is an exemplary block diagram of a communication system employing a conventional proxy device; -
FIG. 2 is an exemplary block diagram of a communication system employing a proxy device in accordance with the present invention; -
FIG. 3 is an exemplary signaling diagram of the protocol functions applicable to the present invention; -
FIG. 4 is another exemplary signaling diagram of the protocol functions in accordance with the present invention; -
FIG. 5 is an exemplary block diagram of an embodiment of the proxy device and system in accordance with the present invention; and -
FIG. 6 is an exemplary block diagram of another embodiment of the proxy device and system used in accordance with the present invention. - The present invention provides a proxying device that allows the placement of proxies anywhere within a network so that all IP packets belonging to a TCP connection will traverse the proxy which intercepts a first packet of data. Each IP packet typically contains an IP header and a TCP segment. The IP header contains the packet's source and destination IP address. The TCP segment contains a TCP header that includes the source port and the destination port so that the IP packet may be delivered via a communication link. This 4-tuple of the IP addresses and port numbers of the source and destination uniquely identify the TCP connection that is associated with a specific data packet. In addition, the TCP header contains both a flag that indicates whether the plate packet is a SYN packet and an ACK flag and sequence number that acknowledges the receipt of data from its peer. The SYN character within the data packet is a control character used to establish a TCP connection, and also used as time-fill in the absence of data. Furthermore, a TCP header may also contain TCP-OPTIONS “(i.e., the “TPOT” option) which can be used for custom signaling when the communication needs to be modified from the conventional TCP protocol.
- In addition to the above basic format of an IP packet, an IP packet can also be encapsulated in another IP packet. This concept is known as IP tunneling, which temporarily changes the destination of a packet in order to traverse one or more routers. At the source, this concept involves prefixing an IP header with an IP address of an intermediate tunnel point on an IP packet. On reaching the intermediate tunnel point, the IP header of the intermediary is stripped off, while the remaining IP packet is then processed as usual.
- The TPOT device guarantees that it will intercept a first packet of data (and all other data packets) by making an innovative use of TCP-OPTIONS and IP tunnels. A source initiating a TCP connection signals to potential proxies within a communications path that the source and data packet are TPOT-enabled by setting a TCP-OPTION within the SYN packet of data. When a TPOT proxy identifies such a SYN packet, it intercepts the packet and returns to the source an ACK packet which carries the TPOT proxy's IP address along with a TCP•OPTION. On receiving this ACK message, the source then sends the rest of the packets via the intercepting TPOT proxy over an IP tunnel.
-
FIG. 1 is an exemplary block diagram of a conventionaltransparent proxy device 105 used in acommunication system 100. As shown inFIG. 1 , thesystem 100 includessource 102 anddestination 104 coupled tonetworks communication links networks hosts communication links proxy 105 is connected to bothnetworks communication links networks communication lines router 106. - In this conventional system, if a user at
source 102 desires to send a request to network 112 anddestination 104, the user would do so usingsource 102 andnetwork 110 operating systems and protocols. However, in order to guarantee thatproxy 105 intercepts all data packets related to the request, theproxy 105 must be strategically located on the edge of thenetwork 110. But, bypositioning proxy 105 in the position shown inFIG. 1 , the proxy cannot provide a guarantee to intercept all the packets of the request fromsource 102 because some, or all, of the data packets may traverse to network 112 viacommunication links proxy 105 will intercept all packets of data of the request,proxy 105 has to be located on the edge ofnetwork 110, as shown by proxy 105 a. As discussed earlier, locating the proxy at such a focal point does not necessarily maximize the capabilities of the proxy and can be costly. - Because locating the proxy device at the edge or focal point within a network may not be the ideal place to locate the proxy device, and because placing proxy devices within several devices is not cost effective, the present invention allows a TPOT proxying device to be placed anywhere on the network and still supply a guarantee that all the packets of data will be seen.
-
FIG. 2 shows acommunication system 200 havingintermediary devices networks communication system 200 ofFIG. 2 includessource 202 anddestination 204 coupled tonetworks communication links system 200 further includes routers 205-207 that are located in betweennetworks - The
source 202 anddestination 204 can be devices of any type that allow for the transmission and/or reception of communication signals. For example, thesource 202 anddestination 204 can be land-line telephones, cellular telephones, computers, personal digital assistance, video telephones, video conference apparatuses, smart or computer assisted television, web TV and the like. For the purposes of the following description of the present invention, it will be assumed thatsource 202 anddestination 204 are personal computers. - The communication links 214-223 may be any type of connection that allows for the transmission of information. Some examples include conventional telephone lines, digital transmission facilities, fiber optic lines, direct serial/parallel connections, cellular telephone connections, satellite telecommunication links, radio frequency (RF) links, local area networks (LANs), Intranets and the like.
- The
networks network networks networks - When a user at
source 202 desires to send a request to network 212, the end user utilizes the operating systems and network protocols ofnetwork 210. The request will be delivered tonetwork 212 via communication links 215-221. The request could potentially be for any data, information, interfacing, etc., from other networks, telecommunications databases or warehouses. - Incorporated into the
communication networks communication system 200 are intermediary devices 208-209. As noted inFIG. 2 , the intermediary devices in accordance with TPOT can be located within a network, as withintermediary device 208 innetwork 210, and/or on the backside of a network, as withintermediary device 209 innetwork 212 or any other location. Any configuration that permits the coordinated transmission of data overnetworks intermediary devices intermediary devices - When an end user at
source 202 desires to send a data request to network 212 anddestination 204, the user utilizessource 202 the operating systems and protocols ofnetwork 210. Dependent upon traffic load, data type, etc., the request will be delivered todestination 204 using some or all of communication links 216-221. Because the request will be separated into multiple packets in accordance with the TCP and IP protocol, one or any combination of the communication paths 216-221 may be utilized to deliver the request in packetized form to network 212. As described with reference toFIG. 1 , because multiple paths can be used to deliver the packets of information, there is no guarantee that a specific proxy will intercept every packet of data. However, as shown inFIG. 2 ,intermediary devices intermediary devices - In operation, a
source 202 initiates a TCP connection signal to theintermediary device 208 by setting a TCP-OPTION within the SYN packet. Whenintermediary device 208 identifies the SYN packet, theintermediary device 208 intercepts the data packet. Theintermediary device 208 then responds to the SYN packet by transmitting an ACK packet to source 202 that acknowledges receipt of the request. On receiving the ACK packet, thesource 202 sends the rest of the data packets via theintermediary device 208 over an IP tunnel via links 216-221 directly tointermediary TPOT device 209, and by-passes routers 205-207. Because the request has been specifically identified as a TPOT request, all subsequent packets of data related to the request will be intercepted by theintermediary devices -
FIG. 3 is an exemplary signaling diagram of the TPOT protocol and associated functions in accordance with the present invention, and is typical of how an L-7 switch would operate. InFIG. 3 , asource 202, such as thehost 202 inFIG. 2 , is operated by end user in a manner to request data fromdestination 212, such as thenetwork 212, andpoint 303. In order to retrieve data from adestination 212, thesource 202 needs to establish a connection with thedestination 212 via TCP. Once the end user requests data viahost 202, the first 8YN packet is sent out by thesource 202 to thedestination 212 via theintermediary device 208, such as theintermediary device 208 inFIG. 2 . In the example inFIG. 2 , the notation (S, S_p, D, D_p) is used to describe a packet that is headed fromsource 202 todestination 212, and has Sp and Dp as the source and destination ports respectively. Furthermore, the notation (T, T −p, D, D −p) is used to describe a packet that is headed fromintermediary device 208 todestination 212. In each example, the notations 8 and T represent the IP addresses of thesource 202 andintermediary device 208, respectively. - In
FIG. 3 , thesource 202 transmits the request atpoint 303 tointermediary device 208 which receives the request atpoint 304. The request includes the SYN packet that has the TCP-OPTION listed as TPOT. Theintermediary device 208 then responds to the request from thesource 202 by sending a SYN-ACK packet back tosource 202 that has the TCP-OPTION with its own address listed as T. Thesource 202 receives the SYNACK packet atpoint 305, and in turn responds by transmitting the remaining packets of data, IP tunneled via intermediary device 208 (point 306) todestination 212 atpoint 307. Thedestination 212 then responds to theintermediary device 208 with a SYN-ACK packet.Intermediary device 208 receives the SYN-ACK packet the fromdestination 212 atpoint 308, and in turn responds by sending the remaining packets of that TCP connection todestination 212. While for the purposes of simplicity, only anintermediary device 208 is shown, it is to be understood that numerous intermediaries may exist without departing from the spirit and scope of the present invention. - In order to co-exist peacefully with other end-points that do not wish to talk using the TPOT protocol, the present invention can utilize a special TCP-OPTION “TPOT” that a
source 202 uses to explicitly indicate tointermediary device 208 within the network that they are interested in using the TPOT mechanism. If theintermediary device 208 does not understand this option, theintermediary device 208 will take no action and simply forward the packet onto its destination using its fast-path. However, ifintermediary device 208 sees a SYN packet that has the TCP-OPTION “TPOT” set, it can respond to thesource 202 with a SYN-ACK that encodes its own IP address Tin the TCP-OPTION field. Upon receiving this packet, thesource 202 must then send the remaining packets of the TCP connection, IP tunneled tointermediary device 208. - One technique for implementing the TCP-OPTION is to add additional bytes of information within the IP header by adding the IP address of
intermediary device 208 as a destination address to all packets that thesource 202 sends out for that TCP connection. However, because this additional header is removed on the next TPOT proxy, the total overhead is limited regardless of the number of TPOT proxies intercepting the connection from the source to the final destination. This overhead can be further reduced by IP header compression. - For applications such as Web caching, where the
intermediary device 208 may be able to satisfy a request from thesource 202, the response is simply served from one or more caches attached to theintermediary device 208. In the case of a “cache miss,” or for other applications whereintermediary device 208 might connect todestination 212 after inspecting some data, theintermediary device 208 communicates with the destination as shown inFIG. 3 . InFIG. 3 , note that theintermediary device 208 sets the TCP-OPTION “TPOT” in its SYN todestination 212 atpoint 306 to allow possibly another TPOT along the way to again proxy the connection (i.e.,intermediary device 209 inFIG. 2 ). - Based on optimization choices and the level of protocol within the data packet, the degree in which the transmission of multiple frames of data is allowed without waiting to see if the frames are acknowledged on an individual basis can be extended even more in order to reduce the number steps between sending data from a source to a destination. This technique is known as pipelining. As shown in
FIG. 4 , based on a received request, asource 202 can transmit the SYN packet incorporating the TPOT identifier in the TCP-OPTION. The origination of this data packet begins atpoint 403, however, unlikeFIG. 3 , a parallel connection is established at point 404 when the intermediary 208 receives the SYN packet. Based on the complexity of the protocol within the packet, and/or a developer's optimization choice, it is possible forintermediary device 208 to pipeline the handshake by sending out the original SYN packet to thedestination 212 immediately after receiving the SYN packet fromsource 202. This function would occur atpoint 404 a inFIG. 4 . At the same time, at point 404 b,intermediary device 208 delivers a SYN-ACK with its own address Tin the TCPOPTION field packet back tosource 202. - The degree of pipe lining depends on the objective of the proxying mechanism. In the case of an L-4 proxy for Web Caching, the original SYN packet contains the destination IP address and port number. Since L-4 proxies do not inspect the content, no further information is needed from the connection before deciding a course of action. In this situation, a SYN packet can be sent out by the
intermediary device 208 to thedestination 212 almost immediately after the intermediary 208 receives a SYN packet from thesource 202. - However, in the case of L-7 switching, the proxy located at the
intermediary device 208 would need to inspect the HTTP request (or at a minimum the URL in the request). In this situation, and as was seen inFIG. 3 , a parallel connection should not be established by theintermediary device 208. Because the request is typically not sent with the SYN, a SYN sent out to thedestination 213 can only happen after the first ACK is received by theintermediary device 208 from thesource 202. - With the parallel connection, if the pipelining can be extended at
point 404 a immediately after receiving the SYN packet fromsource 202, then thedestination 212 receives the data packet atpoint 406, while thesource 202 receives the SYN-ACK packet atpoint 405. Thedestination 212 then responds to theintermediary device 208 by transmitting a SYN-ACK data packet, which is received by theintermediary device 208 atpoint 407 a. Theintermediary device 208 receives this data packet and interprets the packet to acknowledge that thedestination 213 is ready to receive the flow of data. Accordingly, theintermediary device 208 responds by sending the remaining packets of data of that TCP connection that were received by thesource 405 through an IP tunnel. - As a further sophistication of the TPOT device, it is possible for multiple proxied TCP connections that share connections to be pooled at the
intermediary device 208 that may contain TPOT proxies. In general, this configuration improves the throughput and fairness of TCP connections. -
FIG. 5 shows an exemplary block diagram of another embodiment of the proxy device and system in accordance with the present invention. All of the communication system devices communication links and network features correspond to those described inFIG. 2 . However, in this embodiment thenetwork 510 and associated devices are non TPOT enabled. On the contrary, thenetwork 512 and associated devices incorporate theintermediary device 208 in accordance with the TPOT method within the network. Located in betweennetwork communication links transparent proxy 505.Transparent proxy 505 is configured at a focal point between networks in order to ensure that all packets of information will pass through thetransparent proxy device 505. Furthermore, in this embodiment,transparent proxy 505 is used to enable TPOT for non-TPOT aware clients innetwork 510. - As a result of enabling TPOT for data requests originating from
source 202, thetransparent proxy 505 terminates all TCP connection for certain TCP port numbers initiated bysource 202 and instead uses a TPOT enabled TCPIIP stack to connect to the original destination of the connection. Accordingly, all subsequent interceptions by any other TPOT devices, such as theintermediary device 208, will treat the packets of data in accordance with the TPOT protocol and perform IP tunneling as required. In other words, the IP tunnel modules will function to attach and remove IP tunnel headers because IP tunnel headers are added to all IP packets sent after a SYN or a SYN-ACK with a TPOT option set has been received. The inner IP modules spoofs (i.e., filters unnecessary traffic from going over the communications link) for the original destination of the TCP connection. The outer IP module uses the real IP addresses of thesource 202 of the TCP connection and the TPOT proxy which terminated the connection. - As a further sophistication of the TPOT device, it is possible for multiple proxied TCP connections that share connections to be pooled at the
intermediary device 208 that may contain TPOT proxies. In general, this configuration improves the throughput and fairness of TCP connections. -
FIG. 6 shows a third embodiment of the claimed invention. For high band width links which cannot be supported by a single TPOT device, a TPARTY configuration within aTPARTY router 640 can be used to scale TPOT. As seen inFIG. 6 ,TPARTY 640 uses a farm of TPOT devices 641-649 co-located within a router. In addition to routing, theTPARTY router 640 forwards TCP SYN packets for certain TCP port number, which have the TPOT option enabled, toward one of the TPOT devices 641-644. The router might forward the TPOT enabled SYNs in round-robin fashion or might use feedback from the TPOT devices 641-644 to make a more intelligent decision. - In this example,
communication system 600 incorporates all of the devices, networks, and communication links as previously seen in the other embodiments of the present invention. However, when a TPOT-enabled SYN arrives at theTPARTY router 640, thefirst TPOT device 641 decides if it can handle the additional request. IfTPOT device 641 cannot handle the request, the SYN is forwarded toTPOT device 642, which decides whether it can handle the request. The request continues to be handed off to additional TPOT devices until the request is satisfied. If none of the TPOT devices 641-644 can handle the request, the connection will not be proxied, and the SYN is sent back to therouter 640 where the packet is routed as usual to the final destination. However, if the TPARTY has enough resources to deal with the connection, the proxy terminates the connection as described in the TPOT protocol using the IP address of the individual TPOT device as proxying address. In either case, all subsequent packets on therouter 640 are routed as plain IP packets. - In all embodiments of the claimed invention, the TPOT devices either operate as TPOT proxies or as simple routers. If they operate as TPOT proxies, the first TPOT device enables the TPOT protocol and data is subsequently tunneled between the TPOT machine. Delays and losses are added in the device driver code of each TPOT device. Furthermore, the TPOT protocol can be implemented in any operating system. Examples of operating systems are, but not limited to, Scout, UNIX, MS-DOS and PICK, or any other software program which manages the basic operations of a computer system.
- While this invention has been described in conjunction with the specific embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, preferred embodiments of the invention are set forth herein are intended to be illustrative, not limiting. There are changes that may be made without departing from the spirit and scope of the present invention.
Claims (20)
1. A method for transmitting data over a network from a source to a destination through a plurality of intermediary devices, wherein said plurality of intermediary devices comprises at least one proxying device and at least one non-proxying device, the method comprising:
receiving a request for data, said request having an identifier, wherein the identifier designates the request as a proxy-enabled request;
recognizing the identifier in the request by said at least one proxying device;
intercepting the request by said at least one proxying device after recognizing the identifier and subsequently intercepting data packets associated with said request; and
forwarding said data packets associated with said request by said at least one proxying device to the destination.
2. The method of claim 1 , wherein the request is configured into an initial message by a host, the initial message containing an option field enclosing the identifier that allows the data to be forwarded by said at least one proxying device.
3. The method of claim 1 , wherein said at least one proxying device comprises a proxy, the proxy receiving from the source an initial message of the request that has the identifier in an option field, the proxy recognizing the identifier and responding to the source by sending an acknowledgment message to the source.
4. The method of claim 3 , wherein the proxy is located anywhere within the network.
5. The method of claim 4 , wherein the proxy encodes an address of the proxy in the option field within the acknowledgment message.
6. The method of claim 1 , wherein said at least one non-proxying device is a router, the router forwarding the data towards the destination over the network without recognizing the identifier in an option field of a message.
7. The method of claim 5 , wherein the proxy forwards the initial message to the destination while the proxy is sending an acknowledgment message to the source, thereby establishing two connections.
8. The method of claim 7 , wherein after the source receives the acknowledgment message, the source transmits at least one additional message to the destination that corresponds to the data.
9. The method of claim 8 , wherein each of the at least one additional message is configured by encapsulating a first packet of data within a second packet of data, prefixing a header of the first packet with an address of the proxy and the second packet with an address of the destination.
10. The method of claim 9 , wherein the header of the first packet is stripped off after the at least one additional message is received by the proxy, while the second packet is forwarded to the destination.
11. The method of claim 10 , wherein the destination responds to the proxy after receiving the second packet by sending an acknowledgment message to the proxy.
12. The method of claim 7 , wherein after the two connections are established, the source responds to the acknowledgment message by transmitting at least one additional message to the destination that corresponds to the data and the destination responds to the initial message by transmitting an acknowledgment message to the proxy.
13. The method of claim 12 , wherein the proxy responds to the acknowledgment message by transmitting at least one additional message to the destination that corresponds to the data.
14. The method of claim 13 , wherein said at least one proxying device comprises a plurality of proxies that is located anywhere within the network and is used to forward the data to the destination.
15. A system that transmits data over a network from a source to a destination through a plurality of intermediary devices, wherein said plurality of intermediary devices comprises at least one proxying device and at least one non-proxying device, comprising:
means for receiving a request for data, said request having an identifier, wherein the identifier designates the request as a proxy-enabled request;
means for recognizing the identifier in the request by said at least one proxying device;
means for intercepting the request by said at least one proxying device after recognizing the identifier and subsequently intercepting data packets associated with said request; and
means for forwarding said data packets associated with said request by said at least one proxying device to the destination.
16. The system of claim 15 , wherein the request is configured into an initial message by a host, the initial message containing an option field enclosing the identifier that allows the data to be forwarded by said at least one proxying device.
17. The system of claim 15 , wherein said at least one proxying device is a proxy, the proxy receiving from the source an initial message of the request that has the identifier in an option field, the proxy recognizing the identifier and responding to the source by sending an acknowledgment message to the source.
18. The system of claim 17 , wherein the proxy encodes an address of the proxy in the option field within the acknowledgment message.
19. The system of claim 15 , wherein said at least one non-proxying device comprises a router, the router forwarding the data towards the destination over the network without recognizing the identifier in an option field of a message.
20. The system of claim 17 , wherein the proxy forwards an initial message to the destination while the proxy is sending an acknowledgment message to the source, thereby establishing two connections.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/127,883 US20080222304A1 (en) | 1999-11-19 | 2008-05-28 | Apparatus and methods for providing translucent proxies in a communications network |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16643399P | 1999-11-19 | 1999-11-19 | |
US09/713,214 US7016973B1 (en) | 1999-11-19 | 2000-11-16 | Apparatus and methods for providing translucent proxies in a communications network |
US11/213,061 US7386631B1 (en) | 1999-11-19 | 2005-08-26 | Apparatus and methods for providing translucent proxies in a communications network |
US12/127,883 US20080222304A1 (en) | 1999-11-19 | 2008-05-28 | Apparatus and methods for providing translucent proxies in a communications network |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/213,061 Continuation US7386631B1 (en) | 1999-11-19 | 2005-08-26 | Apparatus and methods for providing translucent proxies in a communications network |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080222304A1 true US20080222304A1 (en) | 2008-09-11 |
Family
ID=36045718
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/713,214 Expired - Fee Related US7016973B1 (en) | 1999-11-19 | 2000-11-16 | Apparatus and methods for providing translucent proxies in a communications network |
US11/213,061 Expired - Fee Related US7386631B1 (en) | 1999-11-19 | 2005-08-26 | Apparatus and methods for providing translucent proxies in a communications network |
US12/127,883 Abandoned US20080222304A1 (en) | 1999-11-19 | 2008-05-28 | Apparatus and methods for providing translucent proxies in a communications network |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/713,214 Expired - Fee Related US7016973B1 (en) | 1999-11-19 | 2000-11-16 | Apparatus and methods for providing translucent proxies in a communications network |
US11/213,061 Expired - Fee Related US7386631B1 (en) | 1999-11-19 | 2005-08-26 | Apparatus and methods for providing translucent proxies in a communications network |
Country Status (1)
Country | Link |
---|---|
US (3) | US7016973B1 (en) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070283024A1 (en) * | 2006-03-08 | 2007-12-06 | Riverbed Technology, Inc. | Address manipulation for network transparency and troubleshooting |
US20090003334A1 (en) * | 2007-06-29 | 2009-01-01 | Sravan Vadlakonda | Analyzing a network with a cache advance proxy |
US20090210936A1 (en) * | 2001-07-12 | 2009-08-20 | Omar Salim H | System and method for providing remote data access for a mobile communication device |
US8239670B1 (en) * | 2008-05-13 | 2012-08-07 | Adobe Systems Incorporated | Multi-aspect identifier in network protocol handshake |
US20120287938A1 (en) * | 2011-05-11 | 2012-11-15 | Yokogawa Electric Corporation | Communication system |
US20120291124A1 (en) * | 2011-05-11 | 2012-11-15 | At&T Mobility Ii Llc | Carrier network security interface for fielded devices |
US9787564B2 (en) | 2014-08-04 | 2017-10-10 | Cisco Technology, Inc. | Algorithm for latency saving calculation in a piped message protocol on proxy caching engine |
Families Citing this family (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7016973B1 (en) * | 1999-11-19 | 2006-03-21 | At&T Corp. | Apparatus and methods for providing translucent proxies in a communications network |
JP2002278903A (en) * | 2001-03-15 | 2002-09-27 | Sony Corp | Information processor, information processing method, recording medium and program |
US20030174838A1 (en) * | 2002-03-14 | 2003-09-18 | Nokia Corporation | Method and apparatus for user-friendly peer-to-peer distribution of digital rights management protected content and mechanism for detecting illegal content distributors |
US20030174841A1 (en) * | 2002-03-15 | 2003-09-18 | Novell Inc. | Methods, systems, and data structures for secure data content presentation |
US7630305B2 (en) * | 2003-07-29 | 2009-12-08 | Orbital Data Corporation | TCP selective acknowledgements for communicating delivered and missed data packets |
US8233392B2 (en) * | 2003-07-29 | 2012-07-31 | Citrix Systems, Inc. | Transaction boundary detection for reduction in timeout penalties |
US7650416B2 (en) | 2003-08-12 | 2010-01-19 | Riverbed Technology | Content delivery for client-server protocols with user affinities using connection end-point proxies |
US7616638B2 (en) | 2003-07-29 | 2009-11-10 | Orbital Data Corporation | Wavefront detection and disambiguation of acknowledgments |
US8270423B2 (en) * | 2003-07-29 | 2012-09-18 | Citrix Systems, Inc. | Systems and methods of using packet boundaries for reduction in timeout prevention |
DE10319528A1 (en) * | 2003-04-30 | 2004-11-25 | Siemens Ag | Method and arrangement for the transparent dynamic provision of a web service |
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 |
US8238241B2 (en) | 2003-07-29 | 2012-08-07 | Citrix Systems, Inc. | Automatic detection and window virtualization for flow control |
US7978716B2 (en) | 2003-11-24 | 2011-07-12 | Citrix Systems, Inc. | Systems and methods for providing a VPN solution |
US20060029000A1 (en) * | 2004-05-14 | 2006-02-09 | International Business Machines Corporation | Connection establishment in a proxy server environment |
US8739274B2 (en) | 2004-06-30 | 2014-05-27 | Citrix Systems, Inc. | Method and device for performing integrated caching in a data communication 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 |
US7757074B2 (en) | 2004-06-30 | 2010-07-13 | Citrix Application Networking, Llc | System and method for establishing a virtual private network |
US7724657B2 (en) | 2004-07-23 | 2010-05-25 | Citrix Systems, Inc. | Systems and methods for communicating a lossy protocol via a lossless protocol |
ATE535078T1 (en) | 2004-07-23 | 2011-12-15 | Citrix Systems Inc | METHOD AND SYSTEM FOR SECURING REMOTE ACCESS TO PRIVATE NETWORKS |
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 |
US7810089B2 (en) | 2004-12-30 | 2010-10-05 | 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 |
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 |
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 |
US7581005B2 (en) * | 2005-01-20 | 2009-08-25 | Citrix Systems, Inc. | Systems and methods for preserving transport layer protocol options |
US8077632B2 (en) * | 2005-01-20 | 2011-12-13 | Citrix Systems, Inc. | Automatic LAN/WAN port detection |
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 |
US20060248194A1 (en) | 2005-03-18 | 2006-11-02 | Riverbed Technology, Inc. | Connection forwarding |
JP2007004352A (en) * | 2005-06-22 | 2007-01-11 | Fujifilm Holdings Corp | Character input system |
US8595814B2 (en) * | 2005-12-13 | 2013-11-26 | Google Inc. | TLS encryption in a managed e-mail service environment |
US7921184B2 (en) | 2005-12-30 | 2011-04-05 | 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 |
US9154512B2 (en) * | 2006-03-30 | 2015-10-06 | Cisco Technology, Inc. | Transparently proxying transport protocol connections using an external server |
WO2007149687A2 (en) | 2006-05-30 | 2007-12-27 | Riverbed Technology, Inc. | Selecting proxies from among autodiscovered proxies |
US8069209B1 (en) | 2006-06-16 | 2011-11-29 | Openwave Systems Inc. | Method for activating and deactivating client-side services from a distant server |
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 |
US8923275B2 (en) * | 2007-05-01 | 2014-12-30 | Cisco Technology, Inc. | Providing service information for charging a subscriber for a service |
US9112901B2 (en) * | 2007-11-20 | 2015-08-18 | Radware, Ltd. | Method and system for providing connection resiliency |
US7899031B2 (en) * | 2007-11-20 | 2011-03-01 | Microsoft Corporation | Locally terminating an established connection |
US9473598B2 (en) * | 2007-12-18 | 2016-10-18 | International Business Machines Corporation | Network connection failover during application service interruption |
US8943200B2 (en) | 2008-08-05 | 2015-01-27 | At&T Intellectual Property I, L.P. | Method and apparatus for reducing unwanted traffic between peer networks |
JP5494603B2 (en) * | 2011-09-29 | 2014-05-21 | 沖電気工業株式会社 | Security processing agent system |
JP6105163B2 (en) * | 2013-06-27 | 2017-03-29 | 徐 正 煥SEO, Jeong Hoan | Multiple connection system and method for service using Internet protocol |
WO2015167375A1 (en) * | 2014-04-30 | 2015-11-05 | Telefonaktiebolaget L M Ericsson (Publ) | Method and tcp proxy for supporting communication between a client device and a server node |
US10834065B1 (en) | 2015-03-31 | 2020-11-10 | F5 Networks, Inc. | Methods for SSL protected NTLM re-authentication and devices thereof |
US10404698B1 (en) | 2016-01-15 | 2019-09-03 | F5 Networks, Inc. | Methods for adaptive organization of web application access points in webtops and devices thereof |
Citations (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5392400A (en) * | 1992-07-02 | 1995-02-21 | International Business Machines Corporation | Collaborative computing system using pseudo server process to allow input from different server processes individually and sequence number map for maintaining received data sequence |
US6047332A (en) * | 1997-06-30 | 2000-04-04 | Sun Microsystems, Inc. | Global file system-based system and method for rendering devices on a cluster globally visible |
US6061734A (en) * | 1997-09-24 | 2000-05-09 | At&T Corp | System and method for determining if a message identifier could be equivalent to one of a set of predetermined indentifiers |
US6073178A (en) * | 1996-12-09 | 2000-06-06 | Sun Microsystems, Inc. | Method and apparatus for assignment of IP addresses |
US6105027A (en) * | 1997-03-10 | 2000-08-15 | Internet Dynamics, Inc. | Techniques for eliminating redundant access checking by access filters |
US6138162A (en) * | 1997-02-11 | 2000-10-24 | Pointcast, Inc. | Method and apparatus for configuring a client to redirect requests to a caching proxy server based on a category ID with the request |
US6173311B1 (en) * | 1997-02-13 | 2001-01-09 | Pointcast, Inc. | Apparatus, method and article of manufacture for servicing client requests on a network |
US6199109B1 (en) * | 1998-05-28 | 2001-03-06 | International Business Machines Corporation | Transparent proxying of event forwarding discriminators |
US6212563B1 (en) * | 1998-10-01 | 2001-04-03 | 3Com Corporation | Method and system for setting and managing externally provided internet protocol addresses using the dynamic host configuration protocol |
US6434596B1 (en) * | 1999-01-29 | 2002-08-13 | Sony Corporation | Method and system for distributed queues in a multimedia network with proxies |
US6438576B1 (en) * | 1999-03-29 | 2002-08-20 | International Business Machines Corporation | Method and apparatus of a collaborative proxy system for distributed deployment of object rendering |
US6473406B1 (en) * | 1997-07-31 | 2002-10-29 | Cisco Technology, Inc. | Method and apparatus for transparently proxying a connection |
US6493765B1 (en) * | 1999-03-23 | 2002-12-10 | Nortel Networks Limited | Domain name resolution in a network having multiple overlapping address domains |
US6507577B1 (en) * | 1998-11-12 | 2003-01-14 | Nortel Networks Limited | Voice over internet protocol network architecture |
US6532217B1 (en) * | 1998-06-29 | 2003-03-11 | Ip Dynamics, Inc. | System for automatically determining a network address |
US6560640B2 (en) * | 1999-01-22 | 2003-05-06 | Openwave Systems, Inc. | Remote bookmarking for wireless client devices |
US20030088699A1 (en) * | 1999-11-04 | 2003-05-08 | James V. Luciani | System, device, and method for supporting virtual private networks in a label switched communication network |
US6567857B1 (en) * | 1999-07-29 | 2003-05-20 | Sun Microsystems, Inc. | Method and apparatus for dynamic proxy insertion in network traffic flow |
US6594260B1 (en) * | 1999-09-03 | 2003-07-15 | Cisco Technology, Inc. | Content routing |
US6650641B1 (en) * | 1999-07-02 | 2003-11-18 | Cisco Technology, Inc. | Network address translation using a forwarding agent |
US6697360B1 (en) * | 1998-09-02 | 2004-02-24 | Cisco Technology, Inc. | Method and apparatus for auto-configuring layer three intermediate computer network devices |
US6848079B2 (en) * | 1997-05-08 | 2005-01-25 | Nec Corporation | Document conversion using an intermediate computer which retrieves and stores position information on document data |
US7016973B1 (en) * | 1999-11-19 | 2006-03-21 | At&T Corp. | Apparatus and methods for providing translucent proxies in a communications network |
-
2000
- 2000-11-16 US US09/713,214 patent/US7016973B1/en not_active Expired - Fee Related
-
2005
- 2005-08-26 US US11/213,061 patent/US7386631B1/en not_active Expired - Fee Related
-
2008
- 2008-05-28 US US12/127,883 patent/US20080222304A1/en not_active Abandoned
Patent Citations (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5392400A (en) * | 1992-07-02 | 1995-02-21 | International Business Machines Corporation | Collaborative computing system using pseudo server process to allow input from different server processes individually and sequence number map for maintaining received data sequence |
US6073178A (en) * | 1996-12-09 | 2000-06-06 | Sun Microsystems, Inc. | Method and apparatus for assignment of IP addresses |
US6138162A (en) * | 1997-02-11 | 2000-10-24 | Pointcast, Inc. | Method and apparatus for configuring a client to redirect requests to a caching proxy server based on a category ID with the request |
US6173311B1 (en) * | 1997-02-13 | 2001-01-09 | Pointcast, Inc. | Apparatus, method and article of manufacture for servicing client requests on a network |
US6105027A (en) * | 1997-03-10 | 2000-08-15 | Internet Dynamics, Inc. | Techniques for eliminating redundant access checking by access filters |
US6848079B2 (en) * | 1997-05-08 | 2005-01-25 | Nec Corporation | Document conversion using an intermediate computer which retrieves and stores position information on document data |
US6047332A (en) * | 1997-06-30 | 2000-04-04 | Sun Microsystems, Inc. | Global file system-based system and method for rendering devices on a cluster globally visible |
US6473406B1 (en) * | 1997-07-31 | 2002-10-29 | Cisco Technology, Inc. | Method and apparatus for transparently proxying a connection |
US6061734A (en) * | 1997-09-24 | 2000-05-09 | At&T Corp | System and method for determining if a message identifier could be equivalent to one of a set of predetermined indentifiers |
US6199109B1 (en) * | 1998-05-28 | 2001-03-06 | International Business Machines Corporation | Transparent proxying of event forwarding discriminators |
US6532217B1 (en) * | 1998-06-29 | 2003-03-11 | Ip Dynamics, Inc. | System for automatically determining a network address |
US6697360B1 (en) * | 1998-09-02 | 2004-02-24 | Cisco Technology, Inc. | Method and apparatus for auto-configuring layer three intermediate computer network devices |
US6212563B1 (en) * | 1998-10-01 | 2001-04-03 | 3Com Corporation | Method and system for setting and managing externally provided internet protocol addresses using the dynamic host configuration protocol |
US6507577B1 (en) * | 1998-11-12 | 2003-01-14 | Nortel Networks Limited | Voice over internet protocol network architecture |
US6560640B2 (en) * | 1999-01-22 | 2003-05-06 | Openwave Systems, Inc. | Remote bookmarking for wireless client devices |
US6434596B1 (en) * | 1999-01-29 | 2002-08-13 | Sony Corporation | Method and system for distributed queues in a multimedia network with proxies |
US6493765B1 (en) * | 1999-03-23 | 2002-12-10 | Nortel Networks Limited | Domain name resolution in a network having multiple overlapping address domains |
US6438576B1 (en) * | 1999-03-29 | 2002-08-20 | International Business Machines Corporation | Method and apparatus of a collaborative proxy system for distributed deployment of object rendering |
US6650641B1 (en) * | 1999-07-02 | 2003-11-18 | Cisco Technology, Inc. | Network address translation using a forwarding agent |
US6567857B1 (en) * | 1999-07-29 | 2003-05-20 | Sun Microsystems, Inc. | Method and apparatus for dynamic proxy insertion in network traffic flow |
US6594260B1 (en) * | 1999-09-03 | 2003-07-15 | Cisco Technology, Inc. | Content routing |
US20030088699A1 (en) * | 1999-11-04 | 2003-05-08 | James V. Luciani | System, device, and method for supporting virtual private networks in a label switched communication network |
US7016973B1 (en) * | 1999-11-19 | 2006-03-21 | At&T Corp. | Apparatus and methods for providing translucent proxies in a communications network |
US7386631B1 (en) * | 1999-11-19 | 2008-06-10 | At&T Corp. | Apparatus and methods for providing translucent proxies in a communications network |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090210936A1 (en) * | 2001-07-12 | 2009-08-20 | Omar Salim H | System and method for providing remote data access for a mobile communication device |
US8578057B2 (en) * | 2001-07-12 | 2013-11-05 | Blackberry Limited | System and method for providing remote data access for a mobile communication device |
US9332091B2 (en) | 2006-03-08 | 2016-05-03 | Riverbed Technology, Inc. | Address manipulation to provide for the use of network tools even when transaction acceleration is in use over a network |
US20070283024A1 (en) * | 2006-03-08 | 2007-12-06 | Riverbed Technology, Inc. | Address manipulation for network transparency and troubleshooting |
US8447802B2 (en) * | 2006-03-08 | 2013-05-21 | Riverbed Technology, Inc. | Address manipulation to provide for the use of network tools even when transaction acceleration is in use over a network |
US20090003334A1 (en) * | 2007-06-29 | 2009-01-01 | Sravan Vadlakonda | Analyzing a network with a cache advance proxy |
US8295277B2 (en) * | 2007-06-29 | 2012-10-23 | Cisco Technology, Inc. | Analyzing a network with a cache advance proxy |
US8239670B1 (en) * | 2008-05-13 | 2012-08-07 | Adobe Systems Incorporated | Multi-aspect identifier in network protocol handshake |
US20120291124A1 (en) * | 2011-05-11 | 2012-11-15 | At&T Mobility Ii Llc | Carrier network security interface for fielded devices |
US9055024B2 (en) * | 2011-05-11 | 2015-06-09 | Yokogawa Electric Corporation | Communication system |
US9270653B2 (en) * | 2011-05-11 | 2016-02-23 | At&T Mobility Ii Llc | Carrier network security interface for fielded devices |
US20160119311A1 (en) * | 2011-05-11 | 2016-04-28 | At&T Mobility Ii Llc | Carrier network security interface for fielded devices |
US20120287938A1 (en) * | 2011-05-11 | 2012-11-15 | Yokogawa Electric Corporation | Communication system |
US9596226B2 (en) * | 2011-05-11 | 2017-03-14 | At&T Mobility Ii Llc | Carrier network security interface for fielded devices |
US20170155633A1 (en) * | 2011-05-11 | 2017-06-01 | At&T Mobility Ii Llc | Carrier network security interface for fielded devices |
US9900303B2 (en) * | 2011-05-11 | 2018-02-20 | At&T Mobility Ii Llc | Carrier network security interface for fielded devices |
US9787564B2 (en) | 2014-08-04 | 2017-10-10 | Cisco Technology, Inc. | Algorithm for latency saving calculation in a piped message protocol on proxy caching engine |
Also Published As
Publication number | Publication date |
---|---|
US7016973B1 (en) | 2006-03-21 |
US7386631B1 (en) | 2008-06-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7386631B1 (en) | Apparatus and methods for providing translucent proxies in a communications network | |
US8406240B2 (en) | Packet fragmentation prevention | |
US9973387B1 (en) | System and method of traffic inspection and stateful connection forwarding among geographically dispersed network alliances organized as clusters | |
US7953820B2 (en) | Method and system for providing enhanced performance of web browsing | |
US6101549A (en) | Proxy-based reservation of network resources | |
US7139822B2 (en) | Interception method and system for compensating disadvantageous characteristics of a communication protocol | |
EP1760971B1 (en) | Processing communication flows in asymmetrically routed networks | |
US8938553B2 (en) | Cooperative proxy auto-discovery and connection interception through network address translation | |
US6947444B2 (en) | Method and apparatus for improving utilization efficiency of wireless links for web-based applications | |
US6940835B2 (en) | Application-level mobility support in communications network | |
US20080320154A1 (en) | Cooperative proxy auto-discovery and connection interception | |
US20040243703A1 (en) | Cooperative proxy auto-discovery and connection interception | |
EP2357570A1 (en) | System and method for network access without reconfiguration | |
US20040057430A1 (en) | Transmission of broadcast packets in secure communication connections between computers | |
WO2016049609A1 (en) | Application-aware multihoming for data traffic acceleration in data communications networks | |
US20050120140A1 (en) | Method of and system for multi-patch communication | |
KR20090010951A (en) | Virtual inline configuration for a network device | |
JP2010504688A (en) | Method and module for implementing network protocol stack handoff and optimization | |
WO2019209181A1 (en) | System and method for accelerating data delivery | |
US7564848B2 (en) | Method for the establishing of connections in a communication system | |
JPH11313109A (en) | Asymmetric route utilizing communication system and asymmetric route utilizing communication method | |
EP1170923B1 (en) | Interception method and system for compensating disadvantageous characteristics of a communication protocol | |
JP2002312261A (en) | Network service relay method and relay device | |
CN112118183A (en) | Message forwarding method | |
CN115967679A (en) | Data request method, communication device and communication system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |