The Compact Disc Appendix (CD Appendix), which is a part of the present disclosure, contains a hardware description language (Verilog code) description of receive and transmit modules of a network physical layer in accordance with an embodiment of the invention. A portion of the disclosure of this patent document contains material subject to copyright protection. The copyright owner of that material has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights.
The Ethernet local area network (LAN) is one of the most popular and widely used computer networks in the world. Since the early 1970's, computer networking companies and engineering professionals have continually worked to improve Ethernet product versatility, reliability, and transmission speeds. To ensure that new Ethernet products were compatible, interoperable, and reliable, the Institute of Electrical and Electronic Engineers (IEEE) formed a standards group to define and promote industry LAN standards. Today, the IEEE 802.3 standards group is responsible for standardizing the development of new Ethernet protocols and products under an internationally well-known LAN standard called the “IEEE 802.3 standard.”
Currently, there are a wide variety of standard Ethernet products used for receiving, processing, and transmitting data over Ethernet networks. By way of example, these networking products are typically integrated into networked computers, network interface cards (NICs), SNMP/RMON probes, routers, switching hubs, bridges and repeaters. To meet the demand for ever faster data transmission speeds, the IEEE 802.3 standards committee periodically introduces improved variations of the original IEEE 802.3 standard. For example, the “IEEE 802.3u standard” defines a system capable of transmitting data at speeds of up to about 100 Mbps and the “IEEE 802.3z standard” defines a system capable of transmitting data at speeds of up to 1 Gbps.
OSI model 100 has as its lower-most layer a physical layer 105 that is responsible for encoding and decoding data into signals that are transmitted across a particular medium. As is well known in the art, physical layer 105 is also known as the “PHY layer.” Above physical layer 105, a data link layer 110 provides reliable transmission of data over a network while performing appropriate interfacing with physical layer 105 and a network layer 115. Data link layer 110 generally includes a logical link control (LLC) layer 110A and a media access control (MAC) layer 110B. LLC layer 110A is generally a software function responsible for attaching control information to the data being transmitted from network layer 115 to MAC layer 110B. MAC layer 110B detects errors and schedules and controls the access of data to physical layer 105. In some cases, MAC layer 110B employs the well-known carrier sense multiple access with collision detection (CSMA/CD) algorithm. At the gigabit level and above, the CSMA/CD function has essentially been eliminated. MAC layer 110B is optionally connected to physical layer 105 via a Gigabit Medium Independent Interface (GMII).
Like data link layer 110, physical layer 105 includes multiple sublayers. A physical coding sublayer (PCS) 105A synchronizes and reformats data frames from link layer 110 into 10-bit code groups. A physical medium attachment (PMA) sublayer 105B serializes and transmits the code groups. PMA sublayer 105B deserializes data coming in from a communication medium 140 via a medium-dependent interface (MDI) and a physical medium dependent (PMD) layer 105C, and is additionally responsible for recovering the clock from incoming data streams.
Network layer 115 routes data between nodes in a network, and initiates, maintains, and terminates a communication link between users connected to those nodes. Transport layer 120 performs data transfers within a particular level of service quality. By way of example, a typical software protocol used for performing transport layer 120 functions may be TCP/IP, Novell IPX and NetBeui. Session layer 125 controls when users are able to transmit and receive data depending on whether the user is capable of full-duplex or half-duplex transmission, and also coordinates between user applications needing access to the network. Presentation layer 130 is responsible for translating, converting, compressing and decompressing data being transmitted across a medium. As an example, presentation layer 130 functions are typically performed by computer operating systems like Unix, DOS, Microsoft Windows, and Macintosh OS. Finally, Application layer 135 provides users with suitable interfaces for accessing and connecting to a network.
For more information on Ethernet network communication technology, reference may be made to issued U.S. patents entitled “Apparatus and Method for Full-Duplex Ethernet Communications” having U.S. Pat. Nos. 5,311,114 and 5,504,738, and “Media Access Control Micro-RISC Stream Processor and Method for Implementing the Same” having U.S. Pat. No. 6,172,990. These patents are incorporated herein by reference.
Moving to step 215, link layer 110 performs a thirty-two-bit cyclic redundancy check (CRC) to calculate a CRC value. The CRC value is a function of the contents of frame 210 except for the preamble, SFD, FCS, and extension fields. The CRC value is then appended to frame 210 in a frame check sequence (FCS) field. Next, before passing the frame on to physical layer 105, the link layer optionally adds an extension field, which enforces the minimum carrier event duration in some operational modes.
PCS sublayer 105A accepts frame 210 from link layer 110 and encapsulates frame 210 (step 225) into a packet 227. In the art, packets like packet 227 are often referred to as “physical layer streams.” In the present disclosure, the term “physical layer stream” refers to sequences of packets 227.
Properly formed, packet 227 includes a Start-of-Stream Delimiter (SSD), data code groups (DATA) corresponding to the data from the link layer, and an End-of-Stream Delimiter (ESD) (In some standards, the ESD can be replaced by a special SSD that can perform multiple functions. In the present disclosure, the placement of the delimiter defines whether it is a start-of-frame or end-of-frame delimiter). In addition, some standards specify that idle data IDLE be included in a physical layer stream between some packets 227. Each packet and associated idle data are collectively termed a “packet assembly” 234 for purposes of this disclosure.
The PCS sublayer calculates the running disparity for each packet assembly (step 235). Running disparity maintains an equivalence between the number of transmitted ones and zeros to keep the DC level balanced halfway between the “one” voltage level and the “zero” voltage level. Running disparity can be either positive or negative. In the absence of errors, the running disparity value is positive if, since power-on or reset, more ones have been transmitted than zeros, and is negative if more zeros have been transmitted than ones. The PCS sublayer adjusts the disparity and provides the disparity-adjusted physical layer stream to the PMA sublayer.
The entire link layer 110, and sometimes portions of physical layer 105, can be implemented using configurable logic in a programmable logic device (PLD), commonly a field-programmable gate array (FPGA). (For a more detailed treatment of one such embodiment, see the Xilinx Product specification entitled “1-Gigabit Ethernet MAC Core,” Nov. 28, 2001, which is incorporated herein by reference.) Unfortunately, though a relatively simple function, the CRC circuitry in the link layer can occupy a significant portion of the available programmable resources, leaving fewer resources for other tasks. There is therefore a need for a more efficient means of facilitating network functionality in programmable logic.
The present invention is directed to methods and structures for transmitting and receiving data over a network. In an embodiment consistent with the OSI network model, the transmit and receive CRC generators are moved from the link layer to the physical layer. This modification frees up valuable programmable logic resources when a programmable logic device is employed to perform the functions of the link layer.
In one embodiment, the CRC generators of the physical layer are adapted to comply with a plurality of network communication standards. In yet another embodiment, the physical layer, including the CRC generators, is instantiated in hard logic on a programmable logic device. This embodiment offers a flexible and efficient solution for providing the physical and link layers on a single integrated circuit.
This summary does not define the scope of the invention, which is instead defined by the appended claims.
Data link layer 305 is, like the prior art, adapted to receive data from network layer 115 via an LLC sublayer 110A (
PCS 310 includes a data encapsulator 317 that encapsulates frames from MAC sublayer 315 in the manner described above in connection with
In an embodiment that complies with the IEEE 802.3z standard, the idle data is a two-byte sequence in which the first byte is a K28.5 “comma” defined by the standard and the second byte renders the sequence either correcting or non-correcting. However, because the idle data depends upon the non-existent CRC value, in one embodiment data encapsulator 350 merely inserts, by default, the correcting form (or non-correcting form) of the idle data.
PCS 310, with the exception of data encapsulator 317, is instantiated in hard logic 319. PCS 310 includes a CRC generator 318, which in turn includes a programmable demultiplexer 320 adapted to provide the output of data encapsulator 317 to any of a number of data ports within PCS 310. Demultiplexer 320 can be programmed using memory cells (not shown) such as those commonly available on programmable logic devices.
CRC generator 318 additionally includes a CRC module 325 that receives data frames modified to comply with a number of communication standards. In the depicted embodiment, packets and packet assemblies from data encapsulator 317 can be routed via demultiplexer 320 to four different modules, each of which modifies the function of CRC module 325 to comply with a particular standard. The four modules include an InfiniBand™ module 330, a Gigabit Ethernet module 335, a Fibre Channel module 340, and a User-Mode module 345. Depending on the selected communication standard, as determined by programming demultiplexer 320, CRC module 325 calculates a CRC for each incoming frame embedded in a packet from data encapsulator 317 and inserts the resulting CRC value into the appropriate FCS field of the packet derived from the frame. InfiniBand™ module 330 works with CRC module 325 to perform a CRC in compliance with the specification entitled “InfiniBand™ Architecture Release 1.0.a,” Jun. 19, 2001; Gigabit Ethernet module 335 works with CRC module 325 to perform a CRC in compliance with the IEEE 802.3z Gigabit Ethernet specification; and Fibre Channel module 340 works with CRC module 325 to perform a CRC in compliance with the Fibre Channel standard, as outlined in “Fibre Channel Overview,” by Zoltán Meggyesi of the Research Institute for Particle and Nuclear Physics. Each of the foregoing documents is incorporated herein by reference. User module 345 can be adapted to perform a CRC in compliance with e.g. another standard.
CRC module 325 includes an optional force-error input line FE connected to an external, user-accessible pin (not shown). If line FE is held to a logic zero, module 325 provides the CRC value to data pipe 355 as described above. If, on the other hand, line FE is held to a logic one, module 325 corrupts the last byte of the CRC value to force a CRC error. Force-error line FE and related circuitry allow users to verify the operation of CRC module 325.
In one embodiment, module 325 corrupts the CRC value by XORing each bit of the last byte of the CRC value with a logic one to produce a corrupt CRC value in which each bit of the last byte is inverted. In another embodiment, users can configure inputs to the XOR function to be either ones or zeros, and can therefore determine which bits of the last byte are inverted. In still other embodiments, the last byte is replaced with a fixed value or one of two or more alternative values.
Positioning CRC generator 318 within the physical layer in hard logic minimizes the amount of circuitry required to cover multiple standards. CRC module 325 is reasonably similar for each of the standards, only requiring minor modifications via modules 330, 335, 340, and 345. For example, the Gigabit Ethernet standard runs all frame bits through CRC module 325 to create a CRC value, while the InfiniBand™ standard, depending upon the packet, masks out some bits before performing the CRC. The different modules account for such differences, but each relies on the same function performed by CRC module 325.
PCS 310 cannot determine whether to send the correcting or the non-correcting form of the idle data until the disparity for the entire packet assembly is known, but the disparity cannot be calculated until the CRC value is in place within the packet. Data pipe 355 receives the packet assembly, sans the CRC value, from data encapsulator 317 and then inserts into the FCS field of the associated packet the CRC value calculated by CRC module 325. Data pipe 355 then conveys the packet assembly with the potentially erroneous idle data to packet-assembly modifier 360. 8B/10B encoder 365 calculates the running disparity on the resulting packet assembly and conveys the disparity to assembly modifier 360, which modifies the packet assembly, if necessary, to provide the appropriate one of the correcting or non-correcting forms. In the case of a system employing the Gigabyte Ethernet standard, the disparity should be negative before transmitting data from the physical layer, so packet-assembly modifier 360 modifies the idle data to the correcting form in the event that the disparity is positive.
Next, data encapsulator 317 encapsulates the resulting frame 405 in the manner discussed above in connection with
For more detailed discussion of link and physical layers of the prior art, see IEEE standard 802.3, 2000 edition, entitled, “Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications,” which is incorporated herein by reference.
The Fibre Channel standard also discourages transmission of “negative commas.” Instead of modifying the idle data, however, modifier 360 is adapted to modify the ESD field of packet 410 to correct for a positive disparity. The InfiniBand™ standard does not require either an idle modifier or an end-of-packet modifier.
PCS sublayer 510 includes a 8B/10B decoder 515, an elastic buffer 520, a CRC generator 525, and a data decapsulator 530. In the depicted embodiment, all these elements except for data decapsulator 530 are instantiated in hard logic 533, though this need not be the case.
8B/10B decoder 515 (sometimes referred to as an “10B/8B decoder”) conventionally receives and decodes data from a PMA sublayer and conveys the resulting decoded packet assemblies to elastic buffer 520. Also conventional, decoder 515 identifies some types of packet errors and alerts MAC sublayer 570 of erroneous packets via e.g. an error line 534.
Elastic buffer 520 is a conventional buffer with adjustable data capacity; in one embodiment, buffer 520 can hold up to 64 bytes of data, an amount sufficient to comply with each of the above-mentioned standards. Buffer 520 forwards packet assemblies to CRC generator 525 and data decapsulator 530.
CRC generator 525 includes a programmable demultiplexer 535 that provides packet assemblies from buffer 520 to any of a number of data ports within PCS 510. PCS 510 additionally includes a CRC module 540 that receives data from one of four sources. In the depicted embodiment, packet assemblies from buffer 520 can be routed via demultiplexer 535 to four different modules, each of which modifies the function of CRC module 540 to comply with a particular standard. The four modules include an InfiniBand™ module 545, a Gigabit Ethernet module 550, a Fibre Channel module 555, and a User-Mode module 560. Depending on the selected communication standard, as determined by programming demultiplexer 535, CRC module 540 calculates a CRC value for each incoming packet assembly. This CRC value depends on the same fields for which the previously mentioned CRC value was calculated in the foregoing discussion of
CRC generator 525 includes a CRC compare module 565 that strips the CRC value from each packet assembly and compares the stripped CRC value with the calculated CRC value from CRC module 540. During the comparison process, CRC compare module 565 alerts link layer 505 by asserting a signal “checking CRC.” In the event of a mismatch between the stripped and calculated CRC values, CRC compare module 565 generates an error signal to link layer 505 by pulling a line CRC INVALID high (i.e., to a logic one).
Data decapsulator 530 conventionally strips headers and removes idle data from incoming packet assemblies to reproduce data frames. The frames are then conveyed to a MAC sublayer 570 within link layer 505. As with MAC sublayer 315 of transmitter 300 (
As is conventional, MAC sublayer 570 “flushes” erroneous packets, whether those packets are identified by decoder 515 or by a CRC mismatch. Unlike conventional MAC sublayers, however, MAC sublayer 570 relies upon CRC generator 525 to find CRC errors. In the depicted embodiment, MAC sublayer 570 has no control over whether CRC module 525 performs a CRC on incoming packets, so receiver 500 performs a CRC on each packet regardless of whether decoder 515 identifies an error. The absence of MAC-sublayer control places CRC generator 525 outside of the conventional boundary of the link layer.
In addition to conventional features, FPGA 600 includes hardwired (i.e., application specific) logic 319 (
While the present invention has been described in connection with specific embodiments, variations of these embodiments will be obvious to those of ordinary skill in the art. For example, many of the elements instantiated in programmable logic can be instantiated instead in hard logic, and vice versa. Therefore, the spirit and scope of the appended claims should not be limited to the foregoing description.
Number | Name | Date | Kind |
---|---|---|---|
4486739 | Franaszek et al. | Dec 1984 | A |
4758985 | Carter | Jul 1988 | A |
4855669 | Mahoney | Aug 1989 | A |
5072418 | Boutaud et al. | Dec 1991 | A |
5142625 | Nakai | Aug 1992 | A |
RE34363 | Freeman | Aug 1993 | E |
5274570 | Izumi et al. | Dec 1993 | A |
5311114 | Sambamurthy et al. | May 1994 | A |
5339262 | Rostoker et al. | Aug 1994 | A |
5347181 | Ashby et al. | Sep 1994 | A |
5361373 | Gilson | Nov 1994 | A |
5457410 | Ting | Oct 1995 | A |
5473267 | Stansfield | Dec 1995 | A |
5500943 | Ho et al. | Mar 1996 | A |
5504738 | Sambamurthy et al. | Apr 1996 | A |
5537601 | Kimura et al. | Jul 1996 | A |
5543640 | Sutherland et al. | Aug 1996 | A |
5550782 | Cliff et al. | Aug 1996 | A |
5552722 | Kean | Sep 1996 | A |
5574930 | Halverson, Jr. et al. | Nov 1996 | A |
5574942 | Colwell et al. | Nov 1996 | A |
5581745 | Muraoka | Dec 1996 | A |
5600845 | Gilson | Feb 1997 | A |
5652904 | Trimberger | Jul 1997 | A |
5671355 | Collins | Sep 1997 | A |
5705938 | Kean | Jan 1998 | A |
5732250 | Bates et al. | Mar 1998 | A |
5737631 | Trimberger | Apr 1998 | A |
5740404 | Baji | Apr 1998 | A |
5742179 | Sasaki | Apr 1998 | A |
5742180 | DeHon et al. | Apr 1998 | A |
5748979 | Trimberger | May 1998 | A |
5752035 | Trimberger | May 1998 | A |
5760607 | Leeds et al. | Jun 1998 | A |
5809517 | Shimura | Sep 1998 | A |
5835405 | Tsui et al. | Nov 1998 | A |
5874834 | New | Feb 1999 | A |
5889788 | Pressly et al. | Mar 1999 | A |
5892961 | Trimberger | Apr 1999 | A |
5914616 | Young et al. | Jun 1999 | A |
5914902 | Lawrence et al. | Jun 1999 | A |
5933023 | Young | Aug 1999 | A |
5970254 | Cooke et al. | Oct 1999 | A |
6011407 | New | Jan 2000 | A |
6020755 | Andrews et al. | Feb 2000 | A |
6026481 | New et al. | Feb 2000 | A |
6094439 | Krishna et al. | Jul 2000 | A |
6096091 | Hartmann | Aug 2000 | A |
6154051 | Nguyen et al. | Nov 2000 | A |
6163166 | Bielby et al. | Dec 2000 | A |
6172990 | Deb et al. | Jan 2001 | B1 |
6178541 | Joly et al. | Jan 2001 | B1 |
6181163 | Agrawal et al. | Jan 2001 | B1 |
6211697 | Lien et al. | Apr 2001 | B1 |
6242945 | New | Jun 2001 | B1 |
6272451 | Mason et al. | Aug 2001 | B1 |
6279045 | Muthujumaraswathy et al. | Aug 2001 | B1 |
6282627 | Wong et al. | Aug 2001 | B1 |
6295626 | Nair et al. | Sep 2001 | B1 |
6301696 | Lien et al. | Oct 2001 | B1 |
6343207 | Hessel et al. | Jan 2002 | B1 |
6353331 | Shimanek | Mar 2002 | B1 |
6356987 | Aulas | Mar 2002 | B1 |
6389558 | Herrmann et al. | May 2002 | B1 |
6418494 | Shatas et al. | Jul 2002 | B1 |
6434735 | Watkins | Aug 2002 | B1 |
6460172 | Insenser Farre et al. | Oct 2002 | B1 |
6467009 | Winegarden et al. | Oct 2002 | B1 |
6483342 | Britton et al. | Nov 2002 | B1 |
6507942 | Calderone et al. | Jan 2003 | B1 |
6510548 | Squires | Jan 2003 | B1 |
6518787 | Allegrucci et al. | Feb 2003 | B1 |
6519753 | Ang | Feb 2003 | B1 |
6522167 | Ansari et al. | Feb 2003 | B1 |
6532572 | Tetelbaum | Mar 2003 | B1 |
6539508 | Patrie et al. | Mar 2003 | B1 |
6541991 | Hornchek et al. | Apr 2003 | B1 |
6578174 | Zizzo | Jun 2003 | B1 |
6587995 | Duboc et al. | Jul 2003 | B1 |
6588006 | Watkins | Jul 2003 | B1 |
6601227 | Trimberger | Jul 2003 | B1 |
6604228 | Patel et al. | Aug 2003 | B1 |
6611951 | Tetelbaum et al. | Aug 2003 | B1 |
20010049813 | Chan et al. | Dec 2001 | A1 |
20030062922 | Douglass et al. | Apr 2003 | A1 |
20040114638 | Matsuura et al. | Jun 2004 | A1 |
20040177162 | Wetzel et al. | Sep 2004 | A1 |
Number | Date | Country |
---|---|---|
EP-0676697 | Mar 1995 | DE |
0315275 | Oct 1989 | EP |
0 905 906 | Mar 1999 | EP |
1 235 351 | Aug 2002 | EP |
WO 93 25968 | Dec 1993 | WO |