US6006268A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Method and apparatus for reducing overhead on a proxied connection
Assignee: Cisco Technology Inc
•
Filing: 1997-07-31
•
Granted: 1999-12-21
•
Expires: 2017-07-31
Abstract
Abstract A system and method are disclosed for bypassing a participating application that receives data from a client connection between a proxy and a client and receives data from a server connection between a proxy and a server is disclosed. The method includes deriving a client originated packet sequence synchronization factor. The client originated packet sequence synchronization factor is derived from the difference between a last data sequence number sent by the participating application to the server and a last data acknowledgment number sent by the participating application to the client. A server originated packet sequence synchronization factor is derived from the difference between a last data sequence number sent by the participating application to the client and a last data acknowledgment number sent by the participating application to the server. A server originated data sequence number of a packet sent from the server to the client is adjusted using the server originated packet sequence synchronization factor. A client originated the data acknowledgment number of a packet sent from the client to the server is adjusted using the server originated packet sequence synchronization factor. A client originated data sequence number of a packet sent from the client to the server is adjusted using the client originated packet sequence synchronization factor. A server originated data acknowledgment number of a packet sent from the server to the client is adjusted using the client originated packet sequence synchronization factor. As a result, the data sequence and acknowledgment numbers are synchronized between the client and the server.
Inventors
- 👤 Brantley W. Coile
- 👤 Richard A. Howes
- 👤 William M. LeBlanc
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-01 17:54
CPC Classifications
H; H04; H04L; H04L1/00; H04L1/12; H04L1/16; H04L69/00; H04L69/16; H04L69/163; H04L9/00; H04L9/40; H04L2001/0092; H04L67/00; H04L67/01; H04L69/30; H04L69/32; H04L69/322; H04L69/326
Claims Analysis
Total Claims: 12
Claim 1
Independent Claim
160 words
A method of reducing overhead on a proxied connection between a client and a server comprising: receiving incoming data packets from a client on a client side and from a server on a server side, wherein the incoming data packets are associated with a proxied connection between the client and the server; processing the incoming data packets with a participating application and relaying data derived from the incoming data packets from the client side to the server side and from the server side to the client side by generating outgoing data packets; determining that the proxied connection is a suitable connection to be unproxied; determining that all outgoing data packets have been acknowledged; and routing subsequent incoming data packets for the proxied connection to a nonparticipating application wherein the nonparticipating application relays client originated incoming data packets from the client side to the server side and relays server originated incoming data packets from the server side to the client side.
Claim 2
Independent Claim
160 words
A method of reducing overhead on a proxied connection between a client and a server comprising: receiving incoming data packets from a client on a client side and from a server on a server side, wherein the incoming data packets are associated with a proxied connection between the client and the server; processing the incoming data packets with a participating application and relaying data derived from the incoming data packets from the client side to the server side and from the server side to the client side by generating outgoing data packets; determining that the proxied connection is a suitable connection to be unproxied; determining that all outgoing data packets have been acknowledged; and routing subsequent incoming data packets for the proxied connection to a nonparticipating application wherein the nonparticipating application relays client originated incoming data packets from the client side to the server side and relays server originated incoming data packets from the server side to the client side.
Claim 3
Dependent Claim
27 words
A method as recited in claim 1 wherein the participating application participates in the TCP protocol and the nonparticipating application does not participate in the TCP protocol.
Claim 4
Dependent Claim
16 words
A method as recited in claim 1 wherein the nonparticipating application does not acknowledge incoming packets.
Claim 5
Dependent Claim
19 words
A method as recited in claim 1 wherein the nonparticipating application does not check the checksum of incoming packets.
Claim 6
Dependent Claim
81 words
A method as recited in claim 1 wherein the incoming packets from the client side have a client sequence number and a client acknowledgment number and wherein the incoming packets from the server side have a server sequence number and a server acknowledgment number and wherein the nonparticipating application applies a client originated packet sequence synchronization factor to the client sequence number so that the client sequence number corresponds to the sequence number of the next packet expected by the server.
Claim 7
Dependent Claim
48 words
A method as recited in claim 5 wherein the client originated packet sequence synchronization factor is derived from the difference between the last data sequence number sent by the participating application to the server and the last data acknowledgment number sent by the participating application to the client.
Claim 8
Dependent Claim
81 words
A method as recited in claim 1 wherein the incoming packets from the server side have a server sequence number and a server acknowledgment number and wherein the incoming packets from the client side have a client sequence number and a client acknowledgment number and wherein the nonparticipating application applies a server originated packet sequence synchronization factor to the server sequence number so that the server sequence number corresponds to the sequence number of the next packet expected by the client.
Claim 9
Dependent Claim
48 words
A method as recited in claim 7 wherein the server originated packet sequence synchronization factor is derived from the difference between the last data sequence number sent by the participating application to the client and the last data acknowledgment number sent by the participating application to the server.
Claim 10
Dependent Claim
38 words
A method as recited in claim 1 wherein the incoming data packets include packet headers having data checksums and IP checksums and wherein the data checksums and IP checksums are incremented and not checked by the nonparticipating application.
Claim 11
Dependent Claim
50 words
A method as recited in claim 1 further including defining a connection object including a quad, the quad including a client IP address, a server IP address, a client port number, and a server port number wherein the connection object is used to modify packet headers in the nonparticipating application.
Claim 12
Dependent Claim
110 words
A method as recited in claim 10 wherein the connection object further includes a client originated packet sequence synchronization factor and a server originated packet sequence synchronization factor wherein the client originated packet sequence synchronization factor is derived from the difference between the last data sequence number sent by the participating application to the server and the last data acknowledgment number sent by the participating application to the client and the server originated packet sequence synchronization factor is derived from the difference between the last data sequence number sent by the participating application to the client and the last data acknowledgment number sent by the participating application to the server.
References Cited (Backward Citations)
US5319712A
Cited
US5592611A
Cited
US5802320A
Cited
US5828846A
Cited
US5781550A
Cited
US5778174A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2002-12-20 | 2003-06-21 | 2003-12-21 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2006-12-20 | 2007-06-21 | 2007-12-21 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2010-12-20 | 2011-06-21 | 2011-12-21 | $7700.00 | Window Closed / Lapsed |