Patent Grant
10355886
Not Applicable
Not Applicable
The present invention is directed to data communication systems and methods.
Over the last few decades, the use of communication networks exploded. In the early days Internet, popular applications were limited to emails, bulletin board, and mostly informational and text-based web page surfing, and the amount of data transferred was usually relatively small. Today, Internet and mobile applications demand a huge amount of bandwidth for transferring photo, video, music, and other multimedia files. For example, a social network like Facebook processes more than 500 TB of data daily. With such high demands on data and data transfer, existing data communication systems need to be improved to address these needs.
Over the past, there have been many types of communication systems and methods. Unfortunately, they have been inadequate for various applications. Therefore, improved communication systems and methods are desired.
The present invention is directed to data communication systems and methods. More specifically, embodiments of the present invention provide techniques for transceivers to quickly identify FEC mode used in data communication. A transmitting transceiver embeds FEC mode information in a designed field of an alignment marker. The receiving transceiver acknowledges the receipt of the FEC mode information and processes the incoming data accordingly. There are other embodiments as well.
According to an embodiment, the present invention provides a system for providing coding identification. The system includes a first transceiver that has a first alignment module, a first FEC module, and a pattern generator. The first transceiver is configured to generate at least a first data stream and a plurality of alignment markers. The plurality of alignment markers includes a first alignment marker and a second alignment marker. The first alignment marker includes a device message and an FEC mode message. The system also includes a second transceiver comprising a second alignment module and a second FEC module. The second transceiver is configured to process the plurality of alignment markers and the first data stream. The first FEC module encodes the first data stream using a first FEC mode. The FEC mode message indicates the first FEC mode. The second transceiver determines the first FEC mode from the second alignment marker. The second transceiver processes the first data stream using the first FEC mode.
According to another embodiment, the present invention provides a transceiver device. The device includes an input interface for processing incoming data from a plurality of channels. The device also includes an alignment module for generating a first data stream based on the incoming data received from the plurality of channels. The first data stream is separated by a plurality of alignment markers. The first plurality of alignment markers includes a first alignment marker and a second alignment marker. The device also includes an FEC module being configured to encode the first data stream in a first FEC mode. The device additionally includes a processing module configured to generate a second data stream and to embed a first device message in the first alignment marker and a first FEC mode message in the second alignment marker. The device further includes an output interface for transmitting the first data stream and the plurality of alignment markers to a receiving entity.
According to another embodiment, the present invention provides a transceiver device. The device includes an input data communication interface for receiving an analog data stream from a transmitting entity. The device also includes an ADC module for converting the analog data stream to a data stream and a plurality of alignment markers. The plurality of alignment markers includes a first alignment markers and a second alignment marker. The device also includes a processing module for determining an FEC mode by processing a device message embedded at the first alignment marker and a first FEC mode message storage. The method also includes an FEC module for processing the data stream in accordance with the first FEC mode.
It is to be appreciated that embodiments of the present invention provide many advantages over conventional techniques. With conventional techniques, determining FEC mode can be a time-consuming and inefficient process, as the receiving entity may need to try multiple FEC modes before determining which to use for decoding incoming data streams. According to various embodiments of the present invention, by using existing alignment markers to indicate FEC mode, transceivers can quickly establish a mode of communication, and thus operate efficiently. It is also to be appreciated that alignment markers is standardized and used in existing systems. By using a predefined field or region of alignment markers, systems and methods of the present invention are backward compatible with existing systems and processes. Depending on the specific implementation, embodiments of the present invention can be incorporated into existing or new systems. There are other embodiments as well.
The present invention is directed to data communication systems and methods. More specifically, embodiments of the present invention provide techniques for transceivers to quickly identify FEC mode used in data communication. A transmitting transceiver embeds FEC mode information in a designated field of an alignment marker. The receiving transceiver acknowledges the receipt of the FEC mode information and processes the incoming data accordingly. There are other embodiments as well.
In the last decades, with advent of cloud computing and data center, the needs for network servers have evolved. For example, the three-level configuration that have been used for a long time is no longer adequate or suitable, as distributed applications require flatter network architectures, where server virtualization that allows servers to operate in parallel. For example, multiple servers can be used together to perform a requested task. For multiple servers to work in parallel, it is often imperative for them to be share large amount of information among themselves quickly, as opposed to having data going back forth through multiple layers of network architecture (e.g., network switches, etc.).
As an example, leaf-spine architecture has been used for moving and sharing a large amount of data. More specifically, leaf-spine type of network architecture is provided to better allow servers to work in parallel and move data quickly among servers, offering high bandwidth and low latencies. Typically, a leaf-spine network architecture uses a top-of-rack switch that can directly access into server nodes and links back to a set of non-blocking spine switches that have enough bandwidth to allow for clusters of servers to be linked to one another and share large amount of data.
In a typical leaf-spine network today, gigabits of data are shared among servers. In certain network architectures, network servers on the same level have certain peer links for data sharing. Unfortunately, the bandwidth for this type of set up is often inadequate. It is to be appreciated that embodiments of the present invention utilizes PAM (e.g., PAM-8, PAM-12, PAM-16, etc.) in leaf-spine architecture that allows large amount (up terabytes of data at the spine level) of data to be transferred via optical network. It is to be appreciated that while embodiments of the present invention can be used in leaf-spine architectures, they are not limited to leaf-spine architectures and can be used in a wide variety of applications. For example, embodiments of the present invention can be used in different types of data communication networks that are capable of operating in different FEC modes.
The following description is presented to enable one of ordinary skill in the art to make and use the invention and to incorporate it in the context of particular applications. Various modifications, as well as a variety of uses in different applications will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to a wide range of embodiments. Thus, the present invention is not intended to be limited to the embodiments presented, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
In the following detailed description, numerous specific details are set forth in order to provide a more thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without necessarily being limited to these specific details. In other instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the present invention.
The reader's attention is directed to all papers and documents which are filed concurrently with this specification and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference. All the features disclosed in this specification, (including any accompanying claims, abstract, and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.
Furthermore, any element in a claim that does not explicitly state “means for” performing a specified function, or “step for” performing a specific function, is not to be interpreted as a “means” or “step” clause as specified in 35 U.S.C. Section 112, Paragraph 6. In particular, the use of “step of” or “act of” in the Claims herein is not intended to invoke the provisions of 35 U.S.C. Section 112, Paragraph 6.
Please note, if used, the labels left, right, front, back, top, bottom, forward, reverse, clockwise and counter clockwise have been used for convenience purposes only and are not intended to imply any particular fixed direction. Instead, they are used to reflect relative locations and/or directions between various portions of an object.
The leaf-spine architecture 100 comprises servers 120, leaf switches 110, and spine switches 103. It is to be appreciated that depending on the need and specific application, the number and arrangement of the servers and switches may be changed. As shown in
In a specific embodiment, a leaf switch comprises a receiver device configured to receive four communication channels, and each of the channels is capable of transferring incoming data at 25 gigabits/s and configured as a PAM-2 format. Similarly, a server (e.g. server 121) comprises a communication interface that is configured to transmit and receive at 100 gigabits/sec (e.g., four channels at 25 gigabits/s per channel), and is compatible with the communication interface of the leaf switches. The spine switches, similarly, comprise communication interfaces for transmitting and receiving data in PAM format. The spine switches may have a large number of communication channels to accommodate a large number of leaf switches, each of which provides switching for a large number of servers.
The leaf switches are connected to spine switches. As shown in
The servers, through the architecture 100 shown in
When servers shown in
It is to be appreciated that the PAM communication interfaces described above can be implemented in accordance with today communication standards form factors. In addition, afforded by high efficiency level, network transceivers according to embodiments of the present invention can have much lower power consumption and smaller form factor compared to conventional devices.
In an embodiment, the communication interface 300 is configured to receive incoming data at through four channels, where each channel is configured at 25 gigabits/s and configured as a PAM-2 format. Using the transmitter module 310, modulator 316, and the laser 314, the communication interface 300 processes data received at 25 gigabits/s from each of the four incoming channels, and transmits PAM modulated optical data stream at a bandwidth of 100 gigabits/s. It is to be appreciated that other bandwidths are possible as well, such as 40 Gbps, 400 Gbps, and/or others.
As shown the transmitter module 310 receives 4 channels of data. It is to be appreciated that other variants of pulse-amplitude modulation (e.g., PAM-4, PAM-8, PAM-12, PAM-16, etc.), in addition to PAM-2 format, may be used as well. The transmitter module 310 comprises functional block 311, which includes a clock data recovery (CDR) circuit configured to receive the incoming data from the four communication channels. In various embodiments, the functional block 311 further comprises multiplexer for combining 4 channels for data. For example, data from the 4 channels as shown are from the PCE-e interface 350. For example, the interface 350 is connected to one or more processors. In a specific embodiment, two 2:1 multiplexers are employed in the functional block 311. For example, the data received from the four channels are high-speed data streams that are not accompanied by clock signals. The receiver 311 comprises, among other things, a clock signal that is associated with a predetermined frequency reference value. In various embodiments, the receiver 311 is configured to utilize a phase-locked loop (PLL) to align the received data. For example, with four channels of data at 25 gigabits/s coming in, a total bandwidth of 100 gigabits/s is processed by the functional block 311, which acts a switch for processing data. More specifically, the data received by the receiver 311 are aligned into a single stream of data, and the alignment is indicated by alignment markers inserted during the serialization process.
The transmitter module 310 further comprises an encoder 312. As shown in
Depending on the specific implementation, the encoder 312 may utilize one or more FEC encoding modes, such as BCH, variations of RS encoding, and others. When a specific FEC mode (e.g., BCH, RS) is used for encoding outgoing data, the receiving end needs to uses the same FEC mode to process the incoming data. One way to determine the FEC mode is to try different FEC modes to see which works, which can be an inefficient process. It is to be appreciated that according to embodiments of the present invention, the outgoing data stream includes information for FEC mode, and the receiving entity can quickly determine the FEC mode by simply processing the incoming data containing FEC mode information. For example, the FEC mode information is embedded at a predetermined region (e.g., BIP field) of alignment markers and it transmitted as a part of outgoing data stream. The receiving entity processes the FEC mode information and sends an acknowledge message to the transmitting entity. For example, when the communication interface 300 functions as receiving entity, the FEC processors 324 determines the FEC mode by processing the corresponding field(s) of incoming data stream.
The PAM modulation driver 313 is configured to drive data stream encoded by the encoder 312. In various embodiments, the receiver 311, encoder 312, and the modulation driver 313 are integrated and part of the transmitter module 310.
The PAM modulator 316 is configured to modulate signals from the transmitter module 310, and convert the received electrical signal to optical signal using the laser 314. For example, the modulator 316 generates optical signals at a transmission rate of 100 gigabits per second. It is to be appreciated that other rate are possible as well, such as 40 Gbps, 400 Gbps, or others. The optical signals are transmitted in a PAM format (e.g., PAM-8 format, PAM-12, PAM-16, etc.). In various embodiments, the laser 314 comprises a distributed feedback (DFB) laser. Depending on the application, other types of laser technology may be used as well, as such vertical cavity surface emitting laser (VCSEL) and others.
Now referring back to
The amplified data signal from the amplifier 322 is processed by the analog to digital converter (ADC) 323. In a specific embodiment, the ADC 323 can be a baud rate ADC. For example, the ADC is configured to convert the amplified signal into a digital signal formatted into a 100 gigabit per second signal in a PAM format. The functional block 324 is configured to process the 100 Gb/s data stream and encode it into four at streams at 25 Gb/s each. For example, the incoming optical data stream received by the photo detector 321 is in PAM-8 format at a bandwidth of 100 Gb/s, and at block 324 four data streams in PAM-2 format is generated at a bandwidth of 25 Gb/s. The four data streams are transmitted by the transmitter 325 over 4 communication channels at 25 Gb/s. Among other features, the block 324 provides FEC function, and the FEC mode can determined by processing FEC mode information stored at incoming data stream.
It is to be appreciated that there can be many variations to the embodiments described in
The PAM modulation can be implemented in various ways.
The transceiver device 500 comprises a switch module 501, an alignment module 502, an FEC module 503, and a pattern generator 504. As shown, the switch module 501 receives four channels of data input. For example, each channel is configured at 25 gigabits/s bandwidth, and operating at 4×25 gigabits/s, the switch module 501 operates effectively at a bandwidth of 100 gigabits/s. It is to be appreciated that while the switch module 501 and the alignment module 502 are shown to process four channels of data, other configurations are possible as well. For example, the transceiver device 500 may additionally operate in 2× (two channels) mode, 8× (eight channels) mode, or others. The alignment module 502 aligns the incoming data received by the switch module 501 and generates a data stream. For example, alignment module 502 comprises a MUX module that processes incoming data one channel at a time. The data stream including data received from the four data channels. The FEC module 503 encodes the data stream to provide a serialized data stream. Depending on the implementation, an FEC mode (e.g., BCH, RS, etc.) is used to encode the data stream. To make sure the receiving entity uses correct FEC mode when processing the data stream, the serialized data stream includes FEC mode information. The encoded data stream is also serialized for data transmission. For example, a SerDes module is used to serialize incoming data. The pattern generator 504 maps or converts the data stream into a stream of symbols. For example, in accordance with communication standards (e.g., PAM), the serialized outgoing data stream comprises both data payloads and alignment markers. For example, alignment markers are standardized by one or more standard organizations, such as IEEE, and they help properly align serialized data. According to certain communication standards, the alignment markers are 64 (or 66) bits in length and positioned between payload data. Each of the alignment markers includes predefined data fields, such as sync header, lane designator, Bit Interleaved Parity (BIP) field, identifier.
The region 605 corresponds to a BIP field as defined according to various communication standards. For example, the Bit Interleaved Parity (BIP) contain a parity check calculated over the bits from the previously inserted alignment marker and all the subsequently transmitted blocks up to the current marker. According to embodiments of the present invention, data communication does need the BIP field, and BIP field (i.e., region 605) is used to store FEC mode information. More specifically, region 605 stores message indicating (1) that the transceiver device is a specific device that uses region 605 to store FEC mode information, and (2) the specific FEC mode used to encoding the data stream.
It is to be appreciated that the use of BIP field for FEC mode information is used by transceivers that are specifically configured to process the FEC mode information. Therefore, the transceiver of the receiving entity is specifically configured to process the BIP field of incoming alignment markers for the purpose of determining FEC mode and sends an acknowledge message to the transmitting entity to indicate that the FEC mode information is received and the two entity can now communicate using the same FEC mode.
The sharing of FEC mode information and establishing a common FEC mode are provide between the transceiver 701 and transceiver 702. For the purpose of illustration, the transceiver 701 functions as the transmitting entity, and the transceiver 702 functions as the receiving entity, but it is understood that both transceivers are capable of transmitting and receiving data stream.
At step 703, the transceiver 701 sends a device message to the transceiver 702. The device message is embedded in the BIP field(s) of the alignment markers, as described above. The device message is to indicate that the transceiver 701 is a manufacture-specific device that uses the BIP field in the alignment marker to indicate the FEC mode. For example, the transceiver 701 is manufactured by INPHI™ and is configured to use the BIP field of alignment markers to communicate FEC mode information. The device message is received and processed by the transceiver 702. Depending on the make and configuration of the transceiver 702, the transceiver 702 may or may not understand the device message embedded in the BIP field. For example, if the transceiver 702 does not understand the device message and processes the message embedded in the BIP field as parity information, the transceiver 702 may simply ignore the device message.
According to various embodiments, the transceiver 701 is configured to send device message to the transceiver 702 a number of times if an acknowledgement message is not received by the transceiver 702 within a predetermined period of time. For example, not receiving the acknowledgement message may be due to poor network connection or the inability of the transceiver 702 to process the device message in the BIP field. By repeatedly sending device messages to the transceiver 702, the device 701 ensures that the reason for not receiving acknowledgement message from the transceiver 702 is due to device incompatibility (e.g., transceiver 702 not configured to process the BIP field), not due to poor communication link. For example, if the transceiver 701 does not receive the acknowledgement message from the transceiver 702 within the predetermine period of time, the transceiver 701 stops embedding device message and/or FEC mode information in the BIP field. In a specific embodiment, once the transceiver 701 determines that the transceiver 702 is not configured to process device message or FEC mode information embedded in the BIP field, the transceiver 701 runs in a compatibility mode and set the BIP field according to parity of the data stream, or simply initializes the BIP field with zeroes.
At step 704, the transceiver 702 transmits an acknowledgement message to the transceiver 701. Among other features, the device acknowledgement message indicates that the transceiver 702 is configured to process device message and FEC mode information embedded in the BIP field. Depending on the implementation, the acknowledge message can be transmitted as a discrete acknowledgement message, or embedded a predetermined region of an alignment marker.
Upon receiving the acknowledgement message from the transceiver 702, the transceiver 701 sends an FEC mode message to the transceiver 702 at step 705. The FEC mode message indicates the type of FEC encoding used by the transceiver 701 to perform forward error correction. As illustrated in
Upon receiving the FEC mode message, the transceiver 702 sends an FEC acknowledgement message to the transceiver 701, at step 706. In addition, the transceiver 702 processes the data stream received from the transceiver 701 using the FEC mode indicated by the 701. For example, the transceiver 702 comprises an FEC processing module that is capable of processing different FEC data modes. Based on the FEC mode indicated by the transceiver 701, the transceiver 702 can switch from one FEC mode to another as needed. In certain embodiments, the transceiver 702 is in communication with multiple transceivers, and is capable to switch from on FEC mode to another as needed.
While the above is a full description of the specific embodiments, various modifications, alternative constructions and equivalents may be used. Therefore, the above description and illustrations should not be taken as limiting the scope of the present invention which is defined by the appended claims.
This patent application is a continuation of and claims priority to U.S. application Ser. No. 15/476,323, filed Mar. 31, 2017, which is a continuation of U.S. application Ser. No. 14/536,303 filed Nov. 7, 2014, now U.S. Pat. No. 9,678,799 issued May 9, 2017, which is related to U.S. patent application Ser. No. 13/791,201, filed on Mar. 8, 2013, now U.S. Pat. No. 9,020,346 issued Apr. 28, 2015, which claims priority from U.S. Provisional Patent Application No. 61/714,543, filed on Oct. 16, 2012, and U.S. Provisional Patent Application No. 61/699,724, filed on Sep. 11, 2012, all of which are incorporated by reference herein for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 9647799 | Tiruvur | May 2017 | B2 |
| 9992043 | Tiruvur | Jun 2018 | B2 |
| 20020078408 | Chambers et al. | Jun 2002 | A1 |
| 20060294443 | Fekih-Romdhane | Dec 2006 | A1 |
| 20080069570 | Dallesasse | Mar 2008 | A1 |
| 20120148242 | Chen et al. | Jun 2012 | A1 |
| 20120250679 | Judge et al. | Oct 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 10-2010-0134046 | Dec 2010 | KR |
| Entry |
|---|
| Office Action for U.S. Appl. No. 13/797,814, dated Apr. 3, 2014. |
| James F. Buckwalter et al., “A Monolithic 25-Gb/s Transceiver With Photonic Ring Modulators and Ge Detectors in a 130-nm CMOS SOI Process”, IEEE Journal of Solid-State Circuits, Jun. 2012, pp. 1309-1322, vol. 47, No. 6. |
| International Search Report and Written Opinion for PCT/US2014/021436, filed Mar. 6, 2014. |
| Number | Date | Country | |
|---|---|---|---|
| 20180248717 A1 | Aug 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15476323 | Mar 2017 | US |
| Child | 15968614 | US | |
| Parent | 14536303 | Nov 2014 | US |
| Child | 15476323 | US |
