System and method for router data aggregation and delivery
First Claim
1. A method of passing received Internet Protocol (IP) data packets through a network device, said method comprising:
- constructing within said network device a chunk with a payload that is sized to fit more than one of said IP data packets;
formatting said chunk to include at least one of;
a forward error correction (FEC) code; and
a cyclical redundancy check (CRC) code;
filling said payload of said chunk with a portion of at least one said IP data packet;
including a framing symbol in each said chunk; and
passing said chunk through a switch fabric of said network device.
9 Assignments
0 Petitions
Accused Products
Abstract
A chunk format for a large-scale, high data throughput router includes a preamble that allows each individual chunk to have clock and data recovery performed before the chunk data is retrieved. The format includes a chunk header that contains information specific to the entire chunk. A chunk according to the present format can contain multiple packet segments, with each segment having its own packet header for packet-specific information. The format provides for a scrambler seed which allows scrambling the data to achieve a favorable zero and one balance as well as minimal run lengths. There are forward error correction (FEC) bytes as well as a chunk cyclical redundancy check (CRC) to detect and/or correct any errors and also to insure a high degree of data and control integrity. Advantageously, a framing symbol inserted into the chunk format itself allows the receiving circuitry to identify or locate a particular chunk format. “Break Bytes” and “Make Bytes” fields located at the beginning of a chunk preamble precondition an optical receiver to a proper state before the actual chunk arrives at the receiver.
-
Citations
47 Claims
-
1. A method of passing received Internet Protocol (IP) data packets through a network device, said method comprising:
-
constructing within said network device a chunk with a payload that is sized to fit more than one of said IP data packets; formatting said chunk to include at least one of; a forward error correction (FEC) code; and a cyclical redundancy check (CRC) code; filling said payload of said chunk with a portion of at least one said IP data packet; including a framing symbol in each said chunk; and passing said chunk through a switch fabric of said network device. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 46)
-
-
20. An Internet Protocol (IP) packet router, said router comprising:
-
at least one chunk having a payload comprising a plurality of IP data packets and a framing symbol; and a switch fabric through which said chunk passes; wherein a respective chunk includes at least one of; a forward error correction (FEC) code, and a cyclical redundancy check (CRC) code. - View Dependent Claims (21, 22, 23, 24, 25, 26, 27, 28, 29, 31, 47)
-
-
30. An Internet Protocol (IP) packet router system, said system comprising:
-
at least one chunk having a payload comprising a plurality of data packets and a framing symbol; and an IP packet router, including; a switch fabric through which said chunk passes; and
,a first electrical switch stage at an input side of said switch fabric and a second electrical switch stage at an output side of said switch fabric, wherein each said chunk is formatted to include a chunk header and at least one of; a forward error correction (FEC) code, and a cyclical redundancy check (CRC) code, and wherein said chunk header includes a sequence number.
-
-
32. A method of information flow through an IP packet network system device, said method comprising:
-
encapsulating within said network device input IP data packets from a plurality of source ports into chunks, wherein a respective chunk includes at least one of; a forward error correction (FEC) code, and a cyclical redundancy check (CRC) code; formatting overhead information onto each of said chunks, said overhead including a framing symbol; sending said chunks to a switch plane of said IP network device. - View Dependent Claims (33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45)
-
Specification