WO2003098454A2 - Bus conversion device, system and method - Google Patents
Bus conversion device, system and method Download PDFInfo
- Publication number
- WO2003098454A2 WO2003098454A2 PCT/US2003/012793 US0312793W WO03098454A2 WO 2003098454 A2 WO2003098454 A2 WO 2003098454A2 US 0312793 W US0312793 W US 0312793W WO 03098454 A2 WO03098454 A2 WO 03098454A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data frame
- bytes
- mil
- xgmii
- data
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
- H04L12/462—LAN interconnection over a bridge based backbone
Definitions
- Data transmission protocols typically define how data is to be transmitted in a data link.
- a data transmission protocol may define a format for data frame to be transmitted as well as data rates for transmitting data frames in data links.
- data link communication protocols evolve, data communication from a source to a destination may include transmitting data frames on data links which transmit data according to different data transmission protocols.
- a communication path transmitting data between the source and destination typically comprises multiple data links where different data links in the communication transmit ting data frames according to different data transmission protocols.
- FIG. 1 shows an interface between two media independent interfaces (Mils) according to an embodiment of the present invention.
- Figure 2 shows an interface to forward data frames received at a Gigabit Mil (GMII) to a 10 Gigabit Mil (XGMII) according to an embodiment of the interface shown in Figure 1.
- Figure 3 shows an interface to forward data frames received at an XGMII to a GMII according to an embodiment of the interface shown in Figure 1.
- Figures 4 shows an embodiment of the present invention comprising an XGMII coupled to communicate with a plurality of GMIIs incorporating a GMII to XGMII interface as shown in Figure 1.
- Figures 5 shows an alternative embodiment of the present invention comprising an XGMII coupled to communicate with a plurality of GMIIs incorporating a GMII to XGMII interface as shown in Figure 1.
- Figure 6 shows an interface to forward data frames from a plurality of GMIIs to a single XGMII according to either of the alternative embodiments shown in Figures 4 and 4.
- Figure 7 shows an interface to forward data frames from a single XGMII to a plurality of GMIIs according to either of the alternative embodiments shown in Figures 4 and 5.
- Such circuitry may comprise a finite state machine which receives a digital input and provides a digital output, or circuitry which provides one or more analog output signals in response to one or more analog input signals.
- Such circuitry may be provided in an application specific integrated circuit (ASIC) or field programmable gate array (FPGA).
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- logic may comprise machine-executable instructions stored in a memory in combination with processing circuitry to execute such machine-readable instructions.
- a "media independent interface" as referred to herein relates to an interface to receive data from source or transmit data to a destination in a format which is independent of a particular transmission medium for transmitting the data.
- a data transceiver may transmit data to a transmission medium in a data transmission format in response to data received at an MIL
- a data transceiver may provide data to an Mil in response to receiving data from a transmission medium in a data transmission format.
- a "Gigabit Mil” (GMII) as referred to herein relates to an Mil capable of receiving data from a source or transmitting data to a destination at a data rate of about one gigabit per second.
- a "10 Gigabit Mil” (XGMII) as referred to herein relates to an Mil capable of receiving data from a source or transmitting data to a destination at a data rate of about ten gigabits per second.
- An "Extended Attachment Unit hiterface" as referred to herein relates to a data link capable of transmitting data between an Mil and data transceiver.
- a 10 Gigabit Extended Attachment Unit Interface" (XAUI) as referred to herein relates to a data link capable of transmitting data between an XGMII and a data transceiver.
- Other Extended Attachment Unit Interfaces may be defined for higher data rates such as 40 or 100 gigabits per second.
- a "data byte” as referred to herein relates to a fixed quantity of data such as eight bits.
- a “data word” as referred to herein relates to a quantity of data comprising an integer number of related data bytes.
- these are merely examples of a data byte and data word, and embodiments of the present invention are not limited in these respects.
- a "data frame" as referred to herein relates to a quantity of data that may be transmitted from a source to a destination according to a data transmission protocol.
- a data frame may comprise data to be transmitted from a source to a destination in a data link according to a data link layer protocol.
- a data frame may be associated with a size that is based upon a quantity of data such as, for example, a number of data bytes in the data frame.
- a data frame may be transmitted as a sequence of data bytes that are to be processed in the sequence at a destination.
- a data frame may comprise a "start code” as a symbol indicating the beginning of a data frame.
- one or more of the trailing data bytes in such a sequence of data bytes may comprise "terminate code” as a symbol indicating the end of a data packet.
- start code As a symbol indicating the beginning of a data frame.
- trailing data bytes in such a sequence of data bytes may comprise "terminate code” as a symbol indicating the end of a data packet.
- start code and terminate code are merely examples of a start code and terminate code, and embodiments of the present invention are not limited in these respects.
- a data frame may also be formatted for transmission from a source to a destination according an Ethernet protocol as provided in versions of the IEEE standard 802.3.
- Such an Ethernet data frame comprises fields including address fields to provide an Ethernet protocol.
- Ethernet address for each of a destination and a source. This Ethernet address may also be known as a physical address, hardware address, or MAC address.
- a device may compare the destination address of the frame with a physical address associated with the device. If the destination address matches that of the receiving device, the device may read and deliver the entire data frame.
- a "media access control” (MAC) device as referred to herein relates to a device enabling access a transmission medium to transmit or receive data.
- a MAC device may be coupled to an Mil to enable a client process to transmit or receive data frames through a transmission medium.
- a MAC device may be associated with an Ethernet address to receive and forward data frames having the associated Ethernet address.
- An "optical transmission medium” as referred to herein relates to a transmission medium that is capable of transmitting light energy in an optical signal which is modulated by a data signal that is recoverable by demodulating the optical signal.
- an optical transmission medium may comprise fiber optic cabling coupled between a transmitting point and a receiving point.
- a "backplane" as referred to herein relates to a system level circuit board that is capable of being coupled to one or more subsystem level circuit boards.
- a backplane may comprise one or more sockets as "backplane interfaces" for integrating subsystem circuit boards or expansion cards.
- a backplane interface may also couple a backplane to an external transmission medium.
- these are merely examples of a backplane and backplane interface, and embodiments of the present invention are not limited in these respects.
- an embodiment of the present invention is directed to a method and apparatus to transmit data frames between a first Mil and a second MIL
- the first Mil may determine the size of the received data frame to enable the second Mil to provide the received data frame to a destination.
- FIG 1 shows an interface 12 between two Mils.
- a Gigabit Mil (GMII) comprises a transmit interface 18 and a receive interface 20 while a 10 Gigabit Mil (XGMII) comprises a transmit interface 14 and a receive interface 16.
- the transmit and receive interfaces 18 and 20 may be formed according to IEEE standard 802.3z or 802.3-2000, clause 35 while the transmit and receive interface 14 and 16 maybe formed according to IEEE P802.3ae, clause 46.
- the interface 12 may comprise an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA) circuit.
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- these are merely examples of how a bus conversion device may be implemented in logic and embodiments of the present invention are not limited in these respects.
- the interfaces 18 and 20 may be coupled to a MAC device (not shown) adapted to transmit data to or receive data from the interface 12 according to IEEE standard 802.3 - 2000.
- the interfaces may be coupled to a device comprising a physical coding sublayer (PCS) (not shown) for transmitting data to or receiving data from a category 5 cable according to IEEE standard 802.3-2000, clause 40.
- PCS physical coding sublayer
- these are merely examples of devices that may coupled to communicate with a GMII and embodiments of the present invention are not limited in this respect.
- the transmit and receive interfaces 14 and 16 may be coupled to any one of several devices to transmit data to a destination or receive data from a source.
- the interfaces 14 and 16 may be coupled to a physical layer device comprising physical medium attachment (PMA) and physical medium dependent
- the interfaces 14 and 16 may be coupled to a MAC (not shown) to transmit data between the XGMII and an I/O system such as a switch fabric or multiplexed data bus.
- the interfaces may be coupled to an XGMII extended sublayer (XGXS) circuit (not shown) to provide a 10 Gigabit Attachment Unit Interface (XAUI) according to IEEE P802.3ae, clause 47.
- XGMII extended sublayer
- XAUI 10 Gigabit Attachment Unit Interface
- FIG. 2 shows an interface 50 to forward data frames received at a GMII to an XGMII according to an embodiment of the interface 12 shown in Figure 1.
- a GMII transmit state machine 52 receives sequentially clocked byte wide data 78 of a received data frame in response to an enable signal GMII_TXEN.
- Registers 56 and 58 each comprise sixty-four bits to receive eight of the received data bytes.
- a multiplexer 54 alternates loading registers 56 and 58 with the received data bytes to enable the data from one register to be written to a first-in-first-out (FIFO) buffer 72 while received data bytes are being loaded to the other register.
- FIFO first-in-first-out
- the GMII transmit state machine 52 may also determine the size of the received data frame by counting the number of bytes received as byte wide data 78.
- the GMII transmit state machine 52 may determine the start of a data frame by, for example, detecting a transition in the signal GMII_TX_EN from “0" to "1.” All data bytes received as byte wide data 78 may then be counted until detecting a transition in the signal GMII_TX_EN from "1" to "0" indicating the end of the frame.
- the resulting byte count may then be stored in a buffer 62 associated with the data frame stored in the buffer 72.
- the GMII transmit state machine 52 may store the byte count in the buffer 72 in association with the stored data frame.
- the buffer 72 provides the stored data frames as multi-byte words having eight bytes each in response to requests from an XGMII transmit state machine 66.
- the XGMII transmit state machine 66 also controls multiplexers 64 and 70 in response to the detection of a start of a data frame (read out from the buffer 72) and an end of the data frame.
- the XGMII transmit state machine 66 may detect the start of a data frame by, for example, detecting size information (e.g., byte count) being written to the buffer 62 or detecting changes in size information (e.g., byte count) the buffer 72.
- the XGMII transmit state machine 66 may de-assert signal idle_en to cause the multiplexer 64 to begin transmitting the multi-byte words 74 read out from the buffer 72 and the multiplexer 70 to transmit a control code 8'b00000001 on bytes XGMII_TXC_[7:0].
- An XGMII decoder 68 provides a control code on signal txc_delayed[7:0] through the multiplexer 70 in response to a leading or trailing multi-byte word XGMII_TXD_d[63:0] being' transmitted from the multiplexer 64.
- a start code of "FB" may be inserted as the leading byte of the data frame which is stored in the buffer 72 such that the start code is the leading byte of the frame ourputted on XGMII_TXD_d[63:0].
- the GMII transmit state machine 52 may insert a start or terminate code into registers 56 or 58 to indicate the beginning or ending of a data frame.
- a terminate code "FD" is inserted into the last multi-byte word read out to
- the XGMII transmit state machine 66 may determine the end of a data frame (read out as 64 bit words) by decrementing a byte count when each multi-byte word is read out from the buffer 72 (e.g., by eight in the presently illustrated embodiment of sixty- four bit words).
- the XGMI transmit state machine 66 may also determine control codes to be inserted into XGMII_TXC_[7:0] in response to detection a start and end of a data frame. When there are no data frames in the buffer 72 to transmit through the
- the multiplexer 70 may output an idle control code of 8 'b 11111111 and the multiplexer 64 may output value 64'h07070707070707 in response to an asserted idle_en signal. As discussed above, upon detection of the start of a data frame at the XGMII transmit state machine 66 and de-assertion of the idle_en signal, the multiplexer 70 may output the control code 8'b00000001. Between the start and terminate conditions, the multiplexer 70 may output 8 '00000000 to indicate that data is present.
- the multiplexer 70 When the XGMII transmit state machine 66 determines that the remaining bytes in the data frame in the buffer 72 are fewer than a complete multi-byte word (e.g., fewer than eight bytes in the presently illustrated embodiment), the multiplexer 70 outputs control code XGMII_TXC_[7:0] based upon the remaining bytes as shown in Table 1.
- the multiplexer 64 provides the output 74 as sequentially clocked sixty-four bit words and the multiplexer 70 provides the output
- latching circuitry may be used to partition the sixty-four bit output 74 into thirty-two bit words, and partition the eight bit output 76 into four bit quantities to provide a XGMII compliant output.
- GMII transmit state machine 52 and buffer 72 may store portions of received data frames as thirty-two bit words.
- the multiplexer 64 may then readout the output 74 as thirty bit words at about twice speed of reading out the sixty-four bit words in the aforementioned embodiment.
- the multiplexer 70 and XGMII transmit state machine 66 may provide four bit control codes in the output 76 synchronized with the thirty-two bit output.
- Figure 3 shows an interface to forward data frames received at an XGMII to a GMII according to an embodiment of the interface 12 shown in Figure 1.
- a data frame is received at an XGMII as sequentially clocked sixty-four bit input words 106 which are stored in a FIFO buffer 124.
- a multiplexer 104 may then read out the stored data frame as sequentially clocked eight bit output 116 as GMII_RXD[7:0] to a GMII.
- An XGMII decode section 108 also receives the input words 106 to detect a start code (e.g., "FB") in a first byte of the received data frame and a terminate code (e.g., "FD") in a last byte of the received data frame.
- the XGMII decode section 108 may provide start and terminate signals to an XGMII receive state machine 110 in response to detecting the start and termination codes.
- the start and terminate signals may enable the XGMII receive state machine 110 to determine the size (e.g., number of eight bit bytes) of the received data frame by counting the number of eight bit bytes in the received data frame.
- the XGMII receive state machine 110 may do this by, for example, determining a difference in time between receipt of the start signal and the terminate signal. However, this merely an example of how the size of a data frame received at an XGMII may be determined and embodiments of the present invention are not limited in this respect. [0036] Upon determining the size of the received data frame, the XGMII receive state machine 110 may write size information as the number of received bytes in a buffer 112 in association with the received data frame stored in the buffer 124. Alternatively,
- XGMII receive state machine 110 may store the size of the received data frame with the received data bytes in the buffer 124.
- a multiplexer 104 outputs byte portions of the data frame stored in the buffer 124 in response to a byte_en[2:0] signal from a GMII receive state machine 102.
- the multiplexer 104 may receive the stored data frame in multi-byte wide quantities (e.g., sixty four bit words) and output the data frame as sequentially clocked eight bit bytes GMII_RXD[7:0].
- the input data to the multiplexer 104 may be refilled every eight clock cycles of the
- GMII as data is presented to the multiplexer 104 directly from the buffer 124.
- the GMII receive state machine 102 may assert the signal GMII_RXDN to indicate detection of an error in data received at the XGMII (e.g., in response to an error control code received at XGMII__RXC[7:0]).
- Such an error condition may be detected by the XGMII receive state machine 110 and indicate such an error condition by setting a bit in the buffer 112 or buffer 124 in association with the received data frame stored in the buffer 124.
- the GMII receive state machine 102 may inhibit forwarding of the stored data frame through the multiplexer 104 by skip over the bytes of the stored data frame in the buffer 124.
- the XGMII receive state machine 110 may detect error conditions on a received data frame by sensing an XGMII_RXC[7:0] bit set during a frame transmission (framed by START and TERMINATE) while the corresponding byte in XGMII_RXD[63:0] is not the START, TERMINATE or IDLE code.
- the XGMII receive state machine 110 may be signaled by the XGMII decode section 108 set the aforementioned error bit in either buffer 112 or buffer 124.
- An interpacket error may also be detected by the XGMII decode section
- XGMII_RXC[7:0] bit set during idle time (framed by TERMINATE and START codes), while the corresponding XGMII_RXD[63:0] byte is not the START, TERMINATE, or IDLE code. This condition may be ignored.
- XGMII_RXC[7:0] indicates data (by being 0 in any bit), then that data may be ignored since this would precede detection of the START code.
- the three bit signal byte_en[2:0] selects a particular byte (out of a possible eight bytes in the presently illustrated embodiment) to be output by the multiplexer 104.
- the GMII receive state machine 102 may determine the last byte of the stored data frame to be transmitted based upon the size information stored by the XGMII receive state machine 110 as discussed above. For example, the
- GMII receive state machine 102 may decrement a byte count which is stored in either the buffer 112 or 124 associated with the stored data frame. Upon determining the last byte in the data frame, the GMII receive state machine 102 may provide a value for the signal byte_en[2:0] to skip over the terminate code in the stored data frame (e.g., "FD") and de-assert the signal GMII_RXER following transmission of the last byte prior to the terminate code.
- Figures 4 and 5 show systems incorporating a GMII to XGMII interface according to the interface 12 shown in Figure 1.
- an XGMII to GMII interface 126 is coupled to transmit data between a 10 Gigabit Attachment Unit Interface (XAUI) data link 130 (coupled to the interface 126 at an XGMII) and a plurality of GMIIs 128.
- XAUI Gigabit Attachment Unit Interface
- the XAUI data link 130 may extend across a printed circuit board or backplane to provide a serial link between an external attachment and GMII compatible devices coupled to the GMIIs 128.
- the XAUI data link 130 comprises a first ' XGMII Extended Sublayer (XGXS) device 134 coupled to an XGMII on the interface 126 and a second XGXS device 135 coupled to a data transceiver 132 as provided in the IEEE standard 802.3ae, clause 47. It should be understood, however, that other extended sublayer devices may be used to support physical transmissions protocols for increased data rates including, for example, 40 or 100 gigabit Ethernet formats.
- the first and second XGXS devices 134 and 135 may be coupled on a printed circuit board by traces extending up to approximately 50 cm.
- the data transceiver 132 may comprise a physical coding sublayer (PCS) portion, physical media attachment (PMA) portion and a physical media dependent (PMD) portion to transmit or receive data from an optical transmission medium through a media dependent interface (MDI) as provided in the IEEE standard 803.3ae, clauses 49 through 52 .
- a GMII 128 maybe coupled to any on of several devices capable of communicating through a GMII including, for example, a MAC device or data transceiver comprising PCS and PMA portions to communicate over an transmission medium.
- a MAC device or data transceiver comprising PCS and PMA portions to communicate over an transmission medium.
- these are merely examples of devices that may be coupled to a GMII and embodiments of the present invention are not limited in these respects.
- an XGMII to GMII interface 136 is coupled to transmit data between a data transceiver 142 and a plurality of MAC devices 140 (coupled to GMIIs 138) enabling a plurality of independent devices to transmit and receive data through a common XGMII.
- the MAC devices 140 enable multiple network clients in a local area network (LAN) to use the common XGMII.
- LAN local area network
- these are merely examples of how multiple MACs may be employed for communicating in a common XGMII and embodiments of the present invention are not limited in these respects.
- Figures 6 and 7 show an interface to forward data frames between an XGMII and a plurality of GMIIs according to either alternative embodiments of the present invention shown in Figures 4 and 5.
- Figure 6 shows an interface to forward data frames from a plurality of GMIIs 178 to a single XGMII according to an embodiment of the interface 126 or 136 shown in Figures 4 and 5.
- Each of the GMIIs 178 comprise a buffer 172 to store data frames received as sequentially clocked eight bit bytes at a
- the GMII transmit state machine 152 may also determine the size of the received data frame by counting the received data bytes while the signal GMII_TX_EN is asserted also as discussed with reference to Figure 2.
- the XGMII may read out data frames from the buffers 172 through a multiplexer 180 as sequentially clocked sixty four bit words. While each of the GMIIs 178 may independently receive data frames to be stored in an associated buffer 172, an XGMII transmit state machine 166 may control the selection of GMII interfaces 178 to provide the stored data frames.
- the XGMII transmit state machine 166 selects to receive an entire data frame from a GMII 178 before selecting to receive any portion of a data frame from a subsequent GMII 178.
- the XGMII transmit state machine 166 may select a GMII 178 to commence forwarding a data frame (from an associated buffer 172) from among only those GMIIs 178 having a complete date frame stored in the associated buffer 172.
- the XGMII transmit state machine 166 may select a subsequent GMII 178 (having a complete data frame stored in its associated buffer 172) to commence providing a data frame to the multiplexer 180 by asserting the signal fifo_read on a bus 182.
- the GMIIs 178 may maintain a byte count in a buffer 162 which is accessible by the XGMII transmit state machine 166 when reading out data frames.
- the XGMII transmit state machine 166 may determine the end of a data frame (read out as 64 bit words) by decrementing the byte count as each multi-byte word is read out from a buffer 172.
- a terminate code "FD" is inserted into the last multi-byte word read out to XGMII_TXD_d[63 :0] followed by an idle code "07” in each remaining byte of the multi-byte word.
- Table 1 above shows a format for the trailing bytes to be inserted in the sixty four bit word based upon the number of remaining data frame bytes in the last multi-byte word.
- the XGMI transmit state machine 166 may also determine error codes to be inserted into XGMII_TXC_[7:0] (as discussed above with reference to Figure 2) in response to detection a start and end of a data frame.
- the XGMII transmit state machine 166 determines that the remaining bytes in the data frame in the buffer 72 are fewer than a complete multi-byte word (e.g., fewer than eight bytes in the presently illustrated embodiment)
- the multiplexer 70 outputs an error code XGMII_TXC_[7:0] based upon the remaining bytes as shown in Table 1.
- FIG. 7 shows an interface to forward data frames from a single XGMII to a plurality of GMIIs 278 according to an embodiment of the interface 126 or 136 shown in Figures 4 and 5.
- an XGMII 280 comprises an XGMII receive state machine 210 to forward received data frames to selected GMIIs 278.
- the XGMII receive state machine 210 may forward received data frames to the GMIIs 278 using any one of several routing schemes such as, for example, a round robin scheme, TCP/IP routing scheme to route specific IP data gram to a given interface or an Ethernet address where the XGMII 280 is associated with multiple address (each address corresponding to one of the GMIIs 278).
- each of the GMIIs 278 is associated with a unique Ethernet address such that the XGMII receive state machine 210 may route received data frames to a corresponding destination GMII 278 based upon a destination Ethernet address in the data frame.
- the XGMII receive state machine 210 may maintain a record or table associating each of the GMIIs 278 with its Ethernet address.
- the XGMII 280 may build this table or record by for each GMII 278, for example, receiving an initial egress data frame from the GMII 278 and associating a source
- the XGMII receive state machine 210 may then route subsequent ingress data frames to the GMII 278 based upon an association of the destination Ethernet address of the ingress data frames with the Ethernet address associated with the GMII 278.
- a data frame is received at the XGMII 280 as sequentially clocked sixty four bit input words which are stored in a FIFO buffer 224 of a selected destination GMII 278.
- a multiplexer 204 of the selected GMII 278 may then read out the stored data frame as sequentially clocked eight bit output GMII_RXD[7:0].
- An XGMII decode section 208 also receives the input words to detect a start code (e.g., "FB") in a first byte of the received data frame and a terminate code (e.g., "FD") in a last byte of the received data frame.
- the XGMII decode section 208 may provide start and terminate signals to the XGMII receive state machine 210 in response to detecting the start and termination codes.
- the start and terminate signals enable the XGMII receive state machine 210 to determine the size (e.g., number of eight bit bytes) of the received data frame by counting the number of eight bit bytes in the received data frame.
- the XGMII receive state machine 210 may write the size information as the number of received bytes in a buffer 212 of the selected GMII 278 in association with the received data frame. Alternatively, XGMII receive state machine 210 may store the size of the received data frame with the received data bytes in the buffer 224 of the selected destination GMII 278. [0052] A multiplexer 204 of the selected destination GMII 278 outputs byte portions of the data frame stored in the buffer 124 in response to a byte_en[2:0] signal from a GMII receive state machine 202 while the signal GMII_RXDN is asserted.
- the GMII receive state machine 202 may determine the last byte of the stored data frame to be transmitted based upon the size information stored by the XGMII receive state machine 210. Upon determining the last byte in the data frame, the GMII receive state machine 202 may provide a value for the signal byte_en[2:0] to skip over the terminate code in the stored data frame (e.g., "FD") and de-assert the signal GMIIJ XDN following transmission of the last byte prior to the terminate code.
- a value for the signal byte_en[2:0] to skip over the terminate code in the stored data frame (e.g., "FD"
- de-assert the signal GMIIJ XDN following transmission of the last byte prior to the terminate code.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2003269390A AU2003269390A1 (en) | 2002-05-16 | 2003-04-24 | Bus conversion device, system and method |
EP03752991A EP1506489B1 (en) | 2002-05-16 | 2003-04-24 | Bus conversion device, system and method |
DE60316680T DE60316680T2 (en) | 2002-05-16 | 2003-04-24 | BUS IMPLEMENTATION DEVICE, SYSTEM AND METHOD |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/150,366 US7376146B2 (en) | 2002-05-16 | 2002-05-16 | Bus conversion device, system and method |
US10/150,366 | 2002-05-16 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2003098454A2 true WO2003098454A2 (en) | 2003-11-27 |
WO2003098454A3 WO2003098454A3 (en) | 2004-04-08 |
Family
ID=29419236
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2003/012793 WO2003098454A2 (en) | 2002-05-16 | 2003-04-24 | Bus conversion device, system and method |
Country Status (8)
Country | Link |
---|---|
US (1) | US7376146B2 (en) |
EP (1) | EP1506489B1 (en) |
CN (1) | CN100476779C (en) |
AT (1) | ATE374972T1 (en) |
AU (1) | AU2003269390A1 (en) |
DE (1) | DE60316680T2 (en) |
TW (1) | TWI242136B (en) |
WO (1) | WO2003098454A2 (en) |
Families Citing this family (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7619975B1 (en) | 2001-11-21 | 2009-11-17 | Marvell International Ltd. | Generalized auto media selector |
KR100429911B1 (en) * | 2002-05-18 | 2004-05-03 | 한국전자통신연구원 | Apparatus of variable length packets multiplexing and demultiplexing and method thereby |
US7373561B2 (en) * | 2002-10-29 | 2008-05-13 | Broadcom Corporation | Integrated packet bit error rate tester for 10G SERDES |
US8005055B2 (en) * | 2003-07-23 | 2011-08-23 | Interdigital Technology Corporation | Method and apparatus for determining and managing congestion in a wireless communications system |
US20050128977A1 (en) * | 2003-07-23 | 2005-06-16 | Interdigital Technology Corporation | Method and apparatus for determining and managing congestion in a wireless communications system |
US7664134B2 (en) * | 2003-09-23 | 2010-02-16 | Broadcom Corporation | Programmable Q-ordered sets for in-band link signaling |
US7668086B2 (en) * | 2003-09-23 | 2010-02-23 | Broadcom Corporation | Verification and correction of 10GBASE-X lane routing between nodes |
US7296129B2 (en) | 2004-07-30 | 2007-11-13 | International Business Machines Corporation | System, method and storage medium for providing a serialized memory interface with a bus repeater |
US7305574B2 (en) * | 2004-10-29 | 2007-12-04 | International Business Machines Corporation | System, method and storage medium for bus calibration in a memory subsystem |
US7512762B2 (en) | 2004-10-29 | 2009-03-31 | International Business Machines Corporation | System, method and storage medium for a memory subsystem with positional read data latency |
US7331010B2 (en) | 2004-10-29 | 2008-02-12 | International Business Machines Corporation | System, method and storage medium for providing fault detection and correction in a memory subsystem |
US7593416B1 (en) | 2004-12-30 | 2009-09-22 | Marvell International Ltd. | Media and speed independent interface |
US7599391B1 (en) | 2004-12-30 | 2009-10-06 | Marvell International Ltd. | Media and speed independent interface |
US7478259B2 (en) | 2005-10-31 | 2009-01-13 | International Business Machines Corporation | System, method and storage medium for deriving clocks in a memory system |
US7685392B2 (en) | 2005-11-28 | 2010-03-23 | International Business Machines Corporation | Providing indeterminate read data latency in a memory system |
US7669086B2 (en) | 2006-08-02 | 2010-02-23 | International Business Machines Corporation | Systems and methods for providing collision detection in a memory system |
US7539842B2 (en) * | 2006-08-15 | 2009-05-26 | International Business Machines Corporation | Computer memory system for selecting memory buses according to physical memory organization information stored in virtual address translation tables |
US7720068B2 (en) | 2006-08-23 | 2010-05-18 | Solarflare Communications, Inc. | Method and system for a multi-rate gigabit media independent interface |
US7870459B2 (en) | 2006-10-23 | 2011-01-11 | International Business Machines Corporation | High density high reliability memory module with power gating and a fault tolerant address and command bus |
US7721140B2 (en) | 2007-01-02 | 2010-05-18 | International Business Machines Corporation | Systems and methods for improving serviceability of a memory system |
US8699514B2 (en) | 2007-01-12 | 2014-04-15 | Broadcom Corporation | Multi-rate MAC to PHY interface |
KR101933447B1 (en) * | 2014-03-17 | 2018-12-28 | 엘에스산전 주식회사 | Monitoring device of two channels bus data in network system |
CN107562661A (en) * | 2017-08-07 | 2018-01-09 | 郑州云海信息技术有限公司 | A kind of conversion equipment of MII interfaces to RMII interfaces |
CN110875911B (en) * | 2018-09-03 | 2022-03-04 | 厦门奇力微电子有限公司 | Communication protocol and communication method for supporting automatic identification of single data packet data bit number |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0300350A2 (en) * | 1987-07-20 | 1989-01-25 | Matsushita Electric Industrial Co., Ltd. | Communication system |
US5651002A (en) * | 1995-07-12 | 1997-07-22 | 3Com Corporation | Internetworking device with enhanced packet header translation and memory |
US6064674A (en) * | 1997-10-22 | 2000-05-16 | International Business Machines Corporation | Method and apparatus for hardware forwarding of LAN frames over ATM networks |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6081523A (en) * | 1997-12-05 | 2000-06-27 | Advanced Micro Devices, Inc. | Arrangement for transmitting packet data segments from a media access controller across multiple physical links |
US6556589B2 (en) * | 1998-04-17 | 2003-04-29 | Advanced Micro Devices, Inc. | Network transceiver for steering network data to selected paths based on determined link speeds |
US7031324B1 (en) * | 1999-03-22 | 2006-04-18 | Cisco Technology, Inc. | Local area network/wide area network switch |
US6873630B1 (en) * | 1999-05-19 | 2005-03-29 | Sun Microsystems, Inc. | Method and apparatus for a multi-gigabit ethernet architecture |
US6944163B2 (en) * | 2000-02-09 | 2005-09-13 | Nortel Networks Limited | 10 Gigabit ethernet mappings for a common LAN/WAN PMD interface with a simple universal physical medium dependent interface |
CN100527697C (en) * | 2001-11-09 | 2009-08-12 | 维特赛半导体公司 | Means and a method for switching data packets or frames |
-
2002
- 2002-05-16 US US10/150,366 patent/US7376146B2/en not_active Expired - Fee Related
-
2003
- 2003-04-24 AT AT03752991T patent/ATE374972T1/en not_active IP Right Cessation
- 2003-04-24 EP EP03752991A patent/EP1506489B1/en not_active Expired - Lifetime
- 2003-04-24 AU AU2003269390A patent/AU2003269390A1/en not_active Abandoned
- 2003-04-24 WO PCT/US2003/012793 patent/WO2003098454A2/en active IP Right Grant
- 2003-04-24 CN CNB03810900XA patent/CN100476779C/en not_active Expired - Fee Related
- 2003-04-24 DE DE60316680T patent/DE60316680T2/en not_active Expired - Lifetime
- 2003-05-15 TW TW092113225A patent/TWI242136B/en not_active IP Right Cessation
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0300350A2 (en) * | 1987-07-20 | 1989-01-25 | Matsushita Electric Industrial Co., Ltd. | Communication system |
US5651002A (en) * | 1995-07-12 | 1997-07-22 | 3Com Corporation | Internetworking device with enhanced packet header translation and memory |
US6064674A (en) * | 1997-10-22 | 2000-05-16 | International Business Machines Corporation | Method and apparatus for hardware forwarding of LAN frames over ATM networks |
Also Published As
Publication number | Publication date |
---|---|
US20030214974A1 (en) | 2003-11-20 |
US7376146B2 (en) | 2008-05-20 |
CN100476779C (en) | 2009-04-08 |
TW200404216A (en) | 2004-03-16 |
ATE374972T1 (en) | 2007-10-15 |
TWI242136B (en) | 2005-10-21 |
AU2003269390A1 (en) | 2003-12-02 |
WO2003098454A3 (en) | 2004-04-08 |
CN1653437A (en) | 2005-08-10 |
EP1506489B1 (en) | 2007-10-03 |
DE60316680T2 (en) | 2008-07-24 |
EP1506489A2 (en) | 2005-02-16 |
AU2003269390A8 (en) | 2003-12-02 |
DE60316680D1 (en) | 2007-11-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7376146B2 (en) | Bus conversion device, system and method | |
EP0980612B1 (en) | Physical layer device having a media independent interface for connecting to either media access control entities or other physical layer devices | |
US6539488B1 (en) | System with a plurality of media access control circuits with a shared memory for storing data and synchronizing data from a clock domain to a host clock domain | |
JP4554863B2 (en) | Network adapter and communication method with reduced hardware | |
KR100429911B1 (en) | Apparatus of variable length packets multiplexing and demultiplexing and method thereby | |
US8787406B2 (en) | Method and apparatus for distributing and receiving high-speed ethernet media independent interface blocks | |
US6385208B1 (en) | Serial media independent interface | |
US7072349B2 (en) | Ethernet device and method for extending ethernet FIFO buffer | |
JP2011050099A (en) | Method and apparatus for multi-gigabit ethernet (r) architecture | |
JPH11187051A (en) | Method and device for transmitting packet data from medium access controller | |
US7480282B2 (en) | Methods and apparatus for controlling ethernet packet transfers between clock domains | |
EP1506651B1 (en) | Alignment and deskew device, system and method | |
EP1491995B1 (en) | Dual-port functionality for a single-port cell memory device | |
US7321596B2 (en) | Packet control system and communication method | |
US8953637B1 (en) | Media and speed independent interface | |
US7031333B1 (en) | Reduced pin count media independent interface | |
US7599391B1 (en) | Media and speed independent interface | |
US7512075B1 (en) | Method and apparatus for collecting statistical information from a plurality of packet processing blocks | |
US6697385B1 (en) | Circuit(s), method(s) and architecture for configurable packet re-timing in network repeater hubs | |
KR20050069568A (en) | Device and method for multiplexing of fast ethernet in router system | |
Barrass et al. | System Architecture for 100Gb/s Ethernet; System elements, partition and issues related to 100 gigabit/second Ethernet |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2003810900X Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2003752991 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2003752991 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: JP |
|
WWG | Wipo information: grant in national office |
Ref document number: 2003752991 Country of ref document: EP |