Unified data packet for encapsulating data packets having diverse formats

• US 8,135,036 B2
• Filed: 03/17/2009
• Issued: 03/13/2012
• Est. Priority Date: 08/24/2000
• Status: Expired due to Term

• Current Assignee: Tellabs Reston, Inc. (Infinera Corp.)
• Original Assignee: Tellabs Reston, Inc. (Infinera Corp.)
• Inventors: Fang, Rong C., Labana, Paramjit S., Tozer, David John, Cordani, Joseph M., Wisniewski, James J., Roller, Christopher D.
• Primary Examiner(s): Pham, Chi H.
• Assistant Examiner(s): MEW, KEVIN D
• Application Number:
  US12/381,868
• Publication Number:
  US 20090185582A1
• Time in Patent Office: 1,092 Days
• Field of Search: 370/392, 370/395.1, 370/395.6, 37039563-39565, 370470-472, 370/474, 370/476, 370465-466, 370/469, 370/389
• US Class Current: 370/474
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

Embodiments of the present invention described and shown in the specification and drawings facilitate the transportation of data packets having diverse formats through a general packet switching system. Due to the diverse formats of the data packets used by various common communications protocols, it is has been difficult to produce general packet switching systems that are able to switch multiple protocols. Embodiments of the present invention provide a Unified Data Packet for encapsulating data packets having diverse formats. Through encapsulation, embodiments of the present invention improve switching system efficiency by providing a single data packet format for handling by the switching system while enabling data packets in diverse formats to pass through the switch.

Claims

1. A data structure embodied on a non-transitory computer readable medium, comprising:

a payload section including data; and

a header section including a segment type field and a final payload count valid field, the segment type and final payload count valid fields being set responsive to the data of the payload section, the final payload count valid field indicating whether the payload section includes a final payload count field, and any final payload count field indicating an amount of data in the payload section.

2. A data structure as in claim 1 wherein the segment type field indicates whether the data is carried over multiple frames.

3. A data structure as in claim 1 wherein in an event the final payload count valid field indicates that the data does not require the entire payload section for transmission, the payload section includes a final payload count field.

4. A data structure as in claim 1 wherein in an event the final payload count valid field indicates that the data requires the entire payload section for transmission, the payload section does not include a final payload count field.

5. A method for transmitting data, comprising:

encapsulating data in a payload section of a frame;

setting, responsive to the data, a segment type field and a final payload count valid field of a header section of the frame, the final payload count valid field indicating whether the payload section includes a final payload count field, and in an event the payload section includes a final payload count field, setting the final payload count field to indicate an amount of data in the payload section; and

transmitting the frame to a communications system.

6. A method as in claim 5 further comprising:

extracting from the frame, responsive to the segment type field and the final payload count valid field, the data from the payload section of the frame.

7. A method as in claim 6 wherein in an event the payload section includes a final payload count field, extracting the data from the payload section of the frame responsive to the final payload count field.

8. A method as in claim 5 wherein setting the segment type field includes setting the segment type field to indicate whether the data is to be carried over multiple frames.

9. A method as in claim 5 wherein setting the final payload count valid field includes setting the final payload count valid field to indicate that the data does not require the entire payload section for transmission.

10. A method as in claim 9 further including adding a final payload count field into the payload section.

11. A method as in claim 5 wherein setting the final payload count valid field includes setting the final payload count valid field to indicate that the data requires the entire payload section for transmission.

12. An apparatus for transmitting data, comprising:

a packet switch configured to encapsulate data in a payload section of a frame and to set, responsive to the data, a segment type field and a final payload count valid field of a header section of the frame, the final payload count valid field indicating whether the payload section includes a final payload count field, and any final payload count field indicating an amount of data in the payload section; and

a transmitter configured to transmit the frame to a communications system.

13. An apparatus as in claim 12 wherein the packet switch is further configured to indicate in the segment type field whether the data is carried over multiple frames.

14. An apparatus as in claim 12 wherein in an event the data does not require the entire payload section for transmission, the packet switch is further configured to (i) indicate in the final payload count valid field that the data does not require the entire payload section for transmission, and (ii) include a final payload count field in the payload section.

15. An apparatus as in claim 12 wherein in an event the data requires the entire payload section for transmission, the packet switch is further configured to (i) indicate in the final payload count valid field that the data requires the entire payload section for transmission, and (ii) not include a final payload count field in the payload section.

16. A data structure embodied on a non-transitory computer readable medium, comprising:

a first payload section including a first portion of data;

a second payload section including a second portion of the data;

a first header section associated with the first payload section and including a first segment type field and a first final payload count valid field, the first segment type and final payload count valid fields being set responsive to the data of the first payload section, the first final payload count valid field indicating whether the first payload section includes a first final payload count field, and any first final payload count field indicating an amount of data in the first payload section; and

a second header section associated with the second payload section and including a second segment type field and a second final payload count valid field, the second segment type and final payload count valid fields being set responsive to the data of the second payload section, the second final payload count valid field indicating whether the second payload section includes a second final payload count field, and any second final payload count field indicating an amount of data in the second payload section.

17. A data structure as in claim 16 wherein the first and second segment type fields indicate whether the data is carried over multiple frames.

18. A data structure as in claim 16 wherein in an event the first final payload count valid field indicates that the first portion of data does not require the entire first payload section for transmission, the first payload section includes a first final payload count field.

19. A data structure as in claim 16 wherein in an event the first final payload count valid field indicates that the first portion of data requires the entire first payload section for transmission, the first payload section does not include a first final payload count field.

20. A data structure as in claim 16 wherein in an event the second final payload count valid field indicates that the second portion of data does not require the entire second payload section for transmission, the second payload section includes a second final payload count field.

21. A data structure as in claim 16 wherein in an event the second final payload count valid field indicates that the second portion of data requires the entire second payload section for transmission, the second payload section does not include a second final payload count field.