Unified data packet for encapsulating data packets having diverse formats
First Claim
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.
6 Assignments
0 Petitions
Accused Products
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.
-
Citations
21 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. - View Dependent Claims (2, 3, 4)
-
-
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. - View Dependent Claims (6, 7, 8, 9, 10, 11)
-
-
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. - View Dependent Claims (13, 14, 15)
-
-
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. - View Dependent Claims (17, 18, 19, 20, 21)
-
Specification