Packet fragment handling

• US 7,773,599 B1
• Filed: 09/11/2007
• Issued: 08/10/2010
• Est. Priority Date: 03/22/2002
• Status: Expired due to Fees

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Lim, Raymond Marcelino Manese, Libby, Jeffrey G.
• Primary Examiner(s): Sam; Phirin
• Application Number:
  US11/853,356
• Time in Patent Office: 1,064 Days
• Field of Search: None
• US Class Current: 370/392
• CPC Class Codes: H04L 1/0061 Error detection codes
• CPC Class Codes: H04L 1/0072 Error control for data other than payload data, e.g. control data

Abstract

A network device may include a packet header processing engine configured to receive a packet containing packet header information that includes a maximum transfer unit size and a packet length, and determine whether the packet length is greater than the maximum transfer unit size. The packet header processing engine may also be configured to generate and transmit new packet header information when the packet length is less than the maximum transfer unit size, and generate a first fragment header when the packet length is greater than the maximum transfer unit size. The packet header processing engine may further be configured to transmit the first fragment header for generation of a first packet fragment when the packet length is greater than the maximum transfer unit size.

Claims

1. A packet header processing engine comprising:

a packet processing unit configured to;

receive a packet containing packet header information that includes a maximum transfer unit size and a packet length,

determine whether the packet length is greater than the maximum transfer unit size,

generate and transmit new packet header information when the packet length is less than the maximum transfer unit size,

generate a first fragment header when the packet length is greater than the maximum transfer unit size,

transmit the first fragment header for generation of a first packet fragment when the packet length is greater than the maximum transfer unit size,

determine whether an updated packet length contained in the first fragment header is greater than the maximum transfer unit size,

generate and transmit a new packet header when the updated packet length is less than the maximum transfer unit size, and

generate a second fragment header when the updated packet length is greater than the maximum transfer unit size.

2. The packet header processing engine of claim 1, where the second fragment header includes a size of packet data, and the packet processing unit is further configured to:

calculate the updated packet length based on the size of packet data; and

include the updated packet length in the first fragment header.

3. The packet header processing engine of claim 2, where the second fragment header further includes recycle information.

4. The packet header processing engine of claim 1, where the recycle information includes at least one of a bit indicating previous fragmentation or a length of a layer 2 (L2) header.

5. The packet header processing engine of claim 1, where the maximum transfer unit size comprises a maximum transfer unit size associated with an interface that is a destination of the packet.

6. The packet header processing engine of claim 5, where the interface comprises at least one of:

a Synchronous Optical Network (SONET) interface;

an Ethernet interface;

or

an Asynchronous Transfer Mode (ATM) interface.

7. The packet header processing engine of claim 1, where the packet processing unit is further configured to:

detect the packet length from the packet.

8. The packet header processing engine of claim 1, where the packet processing unit is further configured to:

construct a key based on the packet header information; and

use the key to determine the maximum transfer unit size.

9. The packet header processing engine of claim 1, where the packet processing unit is further configured to:

assemble the new packet header information into a new packet.

10. The packet header processing engine of claim 1, where the first fragment header includes a size of payload data in two cells of the packet and a size of packet data, and the packet processing unit is further configured to:

calculate an updated packet length based on the size of payload data and the size of packet data; and

include the updated packet length in the first fragment header.

11. The packet header processing engine of claim 10, where the first fragment header further includes recycle information.

12. The packet header processing engine of claim 11, where the recycle information includes at least one of a bit indicating previous fragmentation or a length of a layer 2 (L2) header.

13. A device-implemented method comprising:

receiving, by the device, a packet containing packet header information that includes a maximum transfer unit size and a packet length;

determining, by the device, whether the packet length is greater than the maximum transfer unit size;

generating, by the device, new packet header information when the packet length is less than the maximum transfer unit size;

transmitting, by the device, the new packet header information;

generating, by the device, a first fragment header when the packet length is greater than the maximum transfer unit size, where the first fragment header includes a size of payload data in two cells of the packet, a size of packet data, and recycle information;

transmitting, by the device, the first fragment header for generation of a first packet fragment when the packet length is greater than the maximum transfer unit size;

calculating, by the device, an updated packet length based on the size of payload data and the size of packet data and including, by the device, the updated packet length in the first fragment header.

14. The method of claim 13, further comprising:

determining whether an updated packet length contained in the first fragment header is greater than the maximum transfer unit size;

generating a new packet header when the updated packet length is less than the maximum transfer unit size;

transmitting the new packet header; and

generating a second fragment header when the updated packet length is greater than the maximum transfer unit size.

15. The method of claim 14, where the second fragment header includes a size of packet data, and the method further comprises:

calculating the updated packet length based on the size of packet data; and

including the updated packet length in the first fragment header.

16. The method of claim 15, where the second fragment header further includes recycle information.

17. The method of claim 16, where the recycle information includes at least one of a bit indicating previous fragmentation or a length of a layer 2 (L2) header.

18. The method of claim 13, where the maximum transfer unit size comprises a maximum transfer unit size associated with an interface that is a destination of the packet.

19. The method of claim 18, where the interface comprises at least one of:

a Synchronous Optical Network (SONET) interface;

an Ethernet interface;

or

an Asynchronous Transfer Mode (ATM) interface.

20. The method of claim 13, further comprising:

detecting the packet length from the packet.

21. The method of claim 13, further comprising:

constructing a key based on the packet header information; and

determining the maximum transfer unit size based on the key.

22. The method of claim 13, further comprising:

assembling the new packet header information into a new packet.

23. The method of claim 13, where the recycle information includes at least one of a bit indicating previous fragmentation or a length of a layer 2 (L2) header.

24. A system comprising:

means for receiving a packet containing packet header information that includes a maximum transfer unit size and a packet length;

means for determining whether the packet length is greater than the maximum transfer unit size;

means for generating new packet header information when the packet length is less than the maximum transfer unit size;

means for transmitting the new packet header information;

means for generating a first fragment header when the packet length is greater than the maximum transfer unit size;

means for transmitting the first fragment header for generation of a first packet fragment when the packet length is greater than the maximum transfer unit size;

means for determining whether an updated packet length contained in the first fragment header is greater than the maximum transfer unit size;

means for generating and transmitting a new packet header when the updated packet length is less than the maximum transfer unit size; and

means for generating a second fragment header when the updated packet length is greater than the maximum transfer unit size.

25. A network device comprising:

a packet header processing engine configured to;

receive a packet containing packet header information that includes a maximum transfer unit size and a packet length,

determine whether the packet length is greater than the maximum transfer unit size,

generate and transmit new packet header information when the packet length is less than the maximum transfer unit size,

generate a first fragment header when the packet length is greater than the maximum transfer unit size, where the first fragment header includes a size of payload data in two cells of the packet, a size of packet data, and recycle information,

transmit the first fragment header for generation of a first packet fragment when the packet length is greater than the maximum transfer unit size,

calculate an updated packet length based on the size of payload data and the size of packet data, and

include the updated packet length in the first fragment header.