Self-describing transport protocol segments

• US 7,385,974 B2
• Filed: 03/18/2004
• Issued: 06/10/2008
• Est. Priority Date: 03/20/2003
• Status: Expired due to Fees

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Elzur, Uri
• Primary Examiner(s): PATEL, AJIT
• Application Number:
  US10/803,719
• Publication Number:
  US 20040184459A1
• Time in Patent Office: 1,545 Days
• Field of Search: 370/389, 370/392, 370470-475, 370/395.52, 370/351, 709221-226
• US Class Current: 370/389
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level

Abstract

Systems and methods that provide self-describing transport protocol segments are provided. In one embodiment, a system that handles transport protocol segments may include, for example, a sender that adapts a transport protocol segment. The transport protocol segment may include, for example, a self-describing header and an indicator. The indicator may indicate at least one of the presence and the location of the self-describing header.

Claims

1. A system for handling transport protocol segments, comprising:

a receiver adapted to process a transport protocol segment that has been resegmented by an intermediate network device in a communication pathway between the receiver and a sender,

wherein the transport protocol segment received by the receiver is a different size than the transport protocol segment sent by the sender,

wherein the receiver is unaware of the received transport protocol segment has been resegmented by the intermediate network device,

wherein the transport protocol segment comprises a self-describing header and an indicator, the self-describing header not being part of a transport protocol header of the transport protocol segment,

wherein a position of the self-describing header has changed in the transport protocol segment due to the intermediate network device resegmenting the transport protocol segment, and

wherein the receiver uses the indicator to locate the position of the self-describing header in the transport protocol segment.

2. The system according to claim 1, wherein the receiver is adapted to process the transport protocol segment in a non-flow-through manner.

3. The system according to claim 1, wherein the receiver is adapted to process the transport protocol segment in a flow-through manner.

4. The system according to claim 1,

wherein the transport protocol comprises at least one of a TCP and a stream control transmission protocol (SCTP), and

wherein the transport protocol segment comprises at least one of a TCP segment and an SCTP segment.

5. The system according to claim 4, wherein the indicator resides in an options field of a TCP header of the TCP segment.

6. The system according to claim 4, wherein the indicator resides in a reserved field of a TCP header of the TCP segment.

7. The system according to claim 4, wherein the indicator resides in a field residing in a TCP payload of the TCP segment.

8. The system according to claim 4, wherein the self-describing header comprises control information used to place data information in the TCP segment.

9. The system according to claim 1, wherein the self-describing header is disposed within at least one of a transport protocol header, a network protocol header and a payload.

10. The system according to claim 1, wherein the self-describing header is disposed between a transport protocol header and a network protocol header or after the transport protocol header.

11. The system according to claim 1, wherein the receiver uses information residing in the self-describing header to place data information in the transport protocol segment into a host memory of the receiver.

12. The system according to claim 1, wherein the receiver copies the data from an Ethernet to a location in an ULP buffer by using information stored in the self-describing header.