Autonegotiation by optics
By using PCS for automatic negotiation in the optical network, the problem that automatic negotiation technology in the optical network cannot be performed through the optical network interface is solved, and automatic negotiation without additional links is realized, network performance is improved and data exchange is simplified.
Patent Information
- Application Number
- CN202410511803.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-04-10
- Filing Date
- 2024-04-26
- Publication Date
- 2024-11-05
AI Technical Summary
The existing automatic negotiation technology cannot be performed through the optical network interface, and requires communication links separated from the optical communication link to facilitate automatic negotiation, resulting in additional network interface requirements.
Automatic negotiation between two physical layers is achieved by using physical coding sublayers (PCS) in an optical network, and automatic negotiation information is transmitted using optical signals, including in optical automatic negotiation (OAN) fields and pages, omitting link status checks and send disable steps, use the optical network interface for automatic negotiation.
It realizes automatic negotiation without additional communication links in the optical network, improves network performance, simplifies the data exchange process, and avoids dependence on dedicated negotiation links.
Smart Images

Figure CN118900291A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to networking, and more particularly, to optical networks and communications. Background Art
[0002] Switches and similar networking devices represent core components of many communications, security, and computing networks. Switches are often used to connect multiple devices to form a network.
[0003] Optical networking utilizes communication systems equipped with fiber optic technology. Fiber optic technology utilizes optical cables and light as the primary mechanism to convert and deliver data and voice communications over a network. Summary of the invention
[0004] Embodiments of the present disclosure relate to using a physical coding sublayer (PCS) to enable automatic negotiation between two physical layers (PHY) in an optical network. PCS is a networking protocol sublayer defined in the IEEE 802.3 standard for 1G Ethernet to 1.6T Ethernet and other Ethernet standards (e.g., Fast Ethernet, Gigabit Ethernet, and 10 Gigabit Ethernet standards). It sits on top of the physical layer (PHY) and provides an interface between the physical medium attachment (PMA) sublayer and the media independent interface (MII).
[0005] Implementing auto-negotiation between PCSs included in a communication link can help improve network performance, among other advantages. In some embodiments, a 64 / 66 command set can be defined to carry auto-negotiation information.
[0006] Example aspects of the present disclosure provide a system including a first PCS block that incorporates auto-negotiation information into a control block, wherein the control block is sent to a second PCS block, and wherein the auto-negotiation information is used to enable negotiation between the first PCS block and the second PCS block.
[0007] In some aspects, the control block is transparent to the digital signal processor data path.
[0008] In some aspects, the negotiation between the first PCS block and the second PCS block is transparent to a PMA sublayer and a physical medium dependent (PMD) sublayer.
[0009] In some aspects, the control block is sent to the second PCS block via an optical signal.
[0010] In some aspects, the first PCS block is part of a transmitter device in a communication network, and the transmitter device further includes a management data input / output (MDIO) register primitive that selectively bypasses or enables internal forward error correction (FEC) between the first PCS block and the second PCS block.
[0011] In some aspects, the control block includes an optical auto-negotiation (OAN) field and an OAN page.
[0012] In some aspects, the OAN page includes one or more protocol handshake variables.
[0013] In some aspects, the first PCS block and the second PCS block follow an auto-negotiation protocol in which at least one of a link status check and a transmit disable step is omitted.
[0014] In another illustrative example, a networking device is described as including: an optical network interface; and a PCS block for: sending and / or receiving optical data signals via the optical network interface; and performing auto-negotiation with another networking device via the optical network interface.
[0015] In some aspects, the automatic negotiation is performed by exchanging optical symbols with another networked device.
[0016] In some aspects, the auto-negotiation is performed at a nominal communication rate also used to exchange optical data signals via the optical network interface.
[0017] In some aspects, the auto-negotiation is performed at approximately the same speed at which the optical data signals are transmitted and / or received.
[0018] In some aspects, the auto-negotiation state machine is included in the PCS block.
[0019] In some aspects, the optical network interface comprises an Ethernet interface.
[0020] In some aspects, the networked device further includes a FEC unit that locks a communication link with another networked device.
[0021] In another example, an optical communication system is described including at least one communication node including an optical transceiver and a PCS block for performing auto-negotiation with another communication node in the optical communication system via the optical transceiver.
[0022] In some aspects, the PCS block incorporates the auto-negotiation information into a control block that is sent to another communication node.
[0023] In some aspects, the auto-negotiation information includes one or more FEC fields.
[0024] In some aspects, the one or more FEC fields indicate inner FEC bypass logic and / or convolutional interleaver logic to be used for a communication link established with another communication node.
[0025] In some aspects, the auto-negotiation is performed at a nominal communication rate also used to exchange optical data signals via the optical transceiver.
[0026] Additional features and advantages are described herein and will be apparent from the following description and accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0027] The present disclosure is described in conjunction with the accompanying drawings, which are not necessarily drawn to scale:
[0028] Figure 1 is a block diagram depicting an illustrative communication system in accordance with at least some embodiments of the present disclosure;
[0029] Figure 2 is a block diagram depicting additional details of an illustrative communication system in accordance with at least some embodiments of the present disclosure;
[0030] Figure 3 is a block diagram depicting data structures used in accordance with at least some embodiments of the present disclosure;
[0031] Figure 4 is a block diagram depicting additional details of data structures used in accordance with at least some embodiments of the present disclosure;
[0032] Figure 5A is a block diagram depicting a first step of a first negotiation process according to at least some embodiments of the present disclosure;
[0033] Figure 5B is a block diagram depicting additional steps of a first negotiation process according to at least some embodiments of the present disclosure;
[0034] Fig. 6A is a block diagram depicting a first step of a second negotiation process according to at least some embodiments of the present disclosure;
[0035] Figure 6B is a block diagram depicting a first set of additional steps of a second negotiation process in accordance with at least some embodiments of the present disclosure;
[0036] Figure 6C is a block diagram depicting a second set of additional steps of a second negotiation process in accordance with at least some embodiments of the present disclosure;
[0037] Fig. 7A is a block diagram depicting a first step of a third negotiation process in accordance with at least some embodiments of the present disclosure;
[0038] Figure 7B is a block diagram depicting additional steps of a third negotiation process in accordance with at least some embodiments of the present disclosure; and
[0039] Figure 8is a flow chart depicting a method in accordance with at least some embodiments of the present disclosure. DETAILED DESCRIPTION
[0040] The following description provides only embodiments and is not intended to limit the scope, applicability or configuration of the claims. Instead, the following description will provide a practical description for those skilled in the art to implement the described embodiments. It should be understood that various changes may be made to the functions and arrangements of the elements without departing from the spirit and scope of the appended claims.
[0041] It will be appreciated from the following description and for reasons of computational efficiency, that the components of the system may be arranged at any suitable locations within a distributed network of components without affecting the operation of the system.
[0042] In addition, it should be understood that the various links connecting these elements can be wired, trace, or wireless links, or any suitable combination thereof, or any other suitable known or later developed one or more elements capable of supplying and / or transmitting data to and from the connected elements. For example, the transmission medium used as a link can be any suitable carrier for electrical signals, including coaxial cables, copper wires and optical fibers, electrical traces on a printed circuit board (PCB), etc.
[0043] As used herein, the phrases "at least one," "one or more," "or," and "and / or" are open-ended expressions that are both conjunctive and transitional in operation. For example, each of the expressions "at least one of A, B, and C," "at least one of A, B, or C," "one or more of A, B, and C," "one or more of A, B, or C," "A, B and / or C," and "A, B, or C" means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B, and C together.
[0044] As used herein, the term "automatic" and variations thereof refer to any suitable process or operation that is completed without material human input when the process or operation is performed. However, if input is received before the process or operation is performed, the process or operation may be automatic even if the performance of the process or operation uses material or immaterial human input. Human input is considered material if such input affects how the process or operation will be performed. Human input that consents to the performance of the process or operation is not considered "material."
[0045] As used herein, the terms "determine," "calculate," "compute," and "calculate" and variations thereof are used interchangeably and include any suitable type of method, process, operation, or technique.
[0046] Various aspects of the disclosure are described herein with reference to the figures that are schematic illustrations of idealized configurations.
[0047] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will be further understood that terms (such as those defined in commonly used dictionaries) should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present disclosure.
[0048] As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that when used in this specification, the terms "comprise", "comprises" and / or "comprising" specify the presence of stated features, integers, steps, operations, elements and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. The term "and / or" includes any and all combinations of one or more of the associated listed items.
[0049] See now Figures 1 to 8 , various systems and methods for transmitting data between networked devices will be described. Communications between networked devices or within a communication system may include a phase in which the networked devices involved in a communication link negotiate aspects or parameters of the communications to be performed between the networked devices (e.g., via the communication link). Once the negotiation phase is complete, a communication link is established between the networked devices, and the negotiated aspects or parameters may be used to facilitate data exchange.
[0050] An Ethernet technique known as "auto-negotiation" enables two connected devices to select standard transmission characteristics, such as duplex mode, speed, precoding, FEC, and flow control. However, the problem is that existing auto-negotiation techniques are not performed over an optical network interface (e.g., an 802.3 optical network interface). Therefore, a communication link separate from the optical communication link is required to facilitate auto-negotiation. Embodiments of the present disclosure are intended to address these shortcomings by providing an improved auto-negotiation method that can be performed over an optical network interface for exchanging data, thereby avoiding the need for an additional communication link dedicated to auto-negotiation.
[0051] The concepts of automatic negotiation and communication described herein can be applied to information routing from one computing device to another computing device. The term packet as used herein should be interpreted as meaning any suitable discrete amount of digitized information. Without departing from the scope of the present disclosure, the data routed as part of automatic negotiation or after completing automatic negotiation can be in the form of a single packet or multiple packets.
[0052] like Figure 1 As shown, the communication system 100 may include two or more networked devices 104a, 104b, which are configured to electronically exchange information with each other. In some embodiments, the communication system 100 may include more than two networked devices 104a, 104b. Networked devices 104a, 104b can be connected to each other directly or through a larger communication network (e.g., Ethernet or a similar device group that implements a communication protocol similar to the Ethernet protocol). It should also be understood that networked devices 104a, 104b can be configured to communicate with each other using protocols other than the Ethernet protocol. Further, embodiments of the present disclosure can be used for any suitable or to-be-developed type of Ethernet protocol (e.g., 10Mbit / s Ethernet, Fast Ethernet, Gigabit Ethernet, 2.5 Gigabit Ethernet, 5 Gigabit Ethernet, 10 Gigabit Ethernet, 25 Gigabit Ethernet, 40 / 100 Gigabit Ethernet, etc.).
[0053] The networking devices 104a, 104b may be of the same type or of different types. Illustrative but non-limiting examples of the networking devices 104a, 104b include endpoint devices (e.g., user devices, mobile devices, personal computers (PCs), laptops, tablets, etc.), nodes, switches, servers, routers, gateways, network cards, network interface controllers (NICs), etc. The first networking device 104a may be a first type of networking device, and the second networking device 104b may be a second type of networking device. Alternatively, the first networking device 104a and the second networking device 104b may be a common type of networking device.
[0054] Although the first networking device 104a and the second networking device 104b are shown as having similar components, it should be understood that the components of the first networking device 104a do not necessarily match the components of the second networking device 104b. In some embodiments, for example, the first networking device 104a may have a first set of components that implement a first set of communication capabilities, while the second networking device 104b may have a second set of components that implement a second set of communication capabilities. Because the communication capabilities of the first networking device 104a and the second networking device 104b are not necessarily the same, the networking devices 104a, 104b have the ability to negotiate communication settings or parameters before exchanging data. In some embodiments, the first networking device 104a and / or the second networking device 104b may have auto-negotiation instructions 124 stored in the memory 116. When executed by the processor 120, the auto-negotiation instructions 124 may enable one networking device (e.g., the first networking device 104a) to perform an auto-negotiation protocol / process with another networking device (e.g., the second networking device 104b).
[0055] As will be described in further detail herein, the networking devices 104a, 104b may perform auto-negotiation via the optical network interface 108. The auto-negotiation process may result in the networking devices 104a, 104b agreeing on communication settings or parameters that will be used to exchange data (e.g., packets) via the same optical network interface 108. The communication settings or parameters may then be shared with the communication instructions 128, which are also stored in the memory 116. When executed by the processor 120, the communication instructions 128 may enable the networking devices 104a, 104b to communicate with each other via the optical network interface 108.
[0056] In some embodiments, the auto-negotiation instructions 124 may enable one networking device to exchange optical symbols with another networking device as part of an auto-negotiation process. In some embodiments, the auto-negotiation may be performed at a nominal communication rate that is also used to exchange optical data signals via the optical network interface 108. In other words, the auto-negotiation may be performed at approximately the same speed at which the networking devices 104a, 104b ultimately send and / or receive optical data signals. In some embodiments, the auto-negotiation instructions 124 may also include a state machine provided in a PCS block of the networking devices 104a, 104b. Advantageously, the auto-negotiation instructions 124 may implement the auto-negotiation via the same optical network interface 108 used for data exchange, thereby avoiding the need for an additional network interface to facilitate the auto-negotiation compared to the data exchange.
[0057] Figure 1Also shown is an optical network interface 108 coupled to a processor 120 via one or more transmit / receiver (TX / RX) circuits 112. Although illustrated as being separate from the processor 120, it should be understood that the TX / RX circuits 112 may be included with the processor 120, or the processor 120 may be provided as part of the TX / RX circuits 112.
[0058] As can be appreciated, the networking devices 104a, 104b may be capable of receiving, processing, and sending data (e.g., packets) to appropriate destinations within the communication system 100. For example, the networking devices 104a, 104b may be configured to exchange data with each other or with other switches or other network endpoints. The optical network interface 108, the TX / RX circuit 112, the processor 120, and the communication instructions 128 may be configured to facilitate data exchange according to the communication settings or parameters negotiated by the auto-negotiation instructions 124.
[0059] The optical network interface 108 may include, for example, an Ethernet interface or a similar type of communication interface. For example, the optical network interface 108 may include one or more devices that convert electrical signals into optical signals (e.g., to send data) or convert optical signals into electrical signals (e.g., to receive data). Although embodiments will be described in conjunction with an optical network interface 108 that includes an Ethernet interface (e.g., an Ethernet port), it should be understood that the optical network interface 108 may include any suitable type of optical device or collection of devices that facilitates machine-to-machine communication with optical signals.
[0060] One or more TX / RX circuits 112 may include any combination of analog and / or digital circuit components. As will be described in further detail herein, one or more TX / RX circuits 112 may include circuit components that facilitate the creation of a communication stack within a networked device. Illustratively but not limited to, one or more TX / RX circuits 112 may include circuit components that create one or more of a PMD sublayer, a PMA sublayer, a PCS block, a coordinated standard (RS) sublayer, a media access control (MAC) sublayer, and the like. These circuit components may include resistors, capacitors, inductors, diodes, transistors, and the like.
[0061] The processor 120 of the networked device 104a, 104b may include one or more processing circuits and / or processing units. Non-limiting examples of the processor 120 include a graphics processing unit (GPU), a central processing unit (CPU), a data processing unit (DPU), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a microprocessor or other circuit capable of performing calculations, as well as memory and storage resources for running software applications, handling data processing, and performing specific tasks as needed.
[0062] The memory 116 as described herein may include one or more memory elements capable of storing configuration settings, routing groups, application data, operating system data, and other data. Such memory elements may include, for example, random access memory (RAM), dynamic RAM (DRAM), flash memory, non-volatile RAM (NVRAM), ternary content addressable memory (TCAM), static RAM (SRAM), and / or other formats of memory elements.
[0063] Reference now Figure 2 , additional components of the networked devices 104a, 104b will be described in more detail. Specifically, Figure 2 Details of one or more TX / RX circuits 112 and functional blocks for facilitating automatic negotiation and / or data exchange between networking devices 104a, 104b are shown. By way of illustration and not limitation, one or both of the networking devices 104a, 104b may include a MAC sublayer 208, an RS sublayer 212, a PCS block 220, a first PMA sublayer 224, a second PMA sublayer 232, and a PMD sublayer 236. The RS sublayer 212 may be connected to the PCS block 220 via a medium independent interface (MII) 216. The first PMA sublayer 224 may be connected to the second PMA sublayer 232 via an attachment unit interface (AUI) 228.
[0064] The MAC sublayer 208 is configured to provide control capabilities for the optical network interface 108. In some embodiments, the MAC sublayer 208 may be part of the data link layer that provides flow control and multiplexing for the transmission medium.
[0065] The RS sublayer 212 may be configured to process PHY local and / or remote fault messages. The RS sublayer 212 may also be configured to process DDR conversions.
[0066] A PCS block 220 may be provided between the MII 216 and the first PMA sublayer 224. The PCS block 220 may be configured to provide an interface between the MII 216 and the first PMA sublayer 224, and may be responsible for data encoding, decoding, scrambling, and descrambling. The PCS block 220 may also be configured to provide alignment marker insertion and removal, block and symbol reallocation, FEC encoding and decoding, and channel block synchronization and deskew. In some embodiments, and as will be described in further detail herein, the PCS block 220 may be provided with auto-negotiation instructions 124. The auto-negotiation instructions 124 may enable the PCS block 220 to perform various auto-negotiation processes or functions over the optical network interface 108.
[0067] The PMA sublayers 224, 232 may be provided on both sides of the AUI 228. In some embodiments, the PMA sublayer 224 may be configured to provide multiple functions. Non-limiting examples of such functions include: adapting PCSL / FECL formatted signals to the appropriate number of abstract or physical channels; providing clock and data recovery per input channel; providing bit-level or RS symbol multiplexing; providing clock generation; providing signal drivers; providing local loopback; providing remote loopback; providing test modes; tolerating skew variations; performing PAM when required; <n>Encoding and decoding, including Gray mapping and optional pre-coding; PMA framing, octet synchronization, octet detection, scrambling, and descrambling capabilities.
[0068] The PMD sublayer 236 may be disposed between the second PMA sublayer 232 and the physical medium 204. The PMD sublayer 236 may include or provide a transceiver for the physical medium. For example, the PMD sublayer 236 may define the physical layer and handle the details of sending and receiving each bit on the physical medium 204. For example, the PMD sublayer 236 may be configured to provide bit timing, signal encoding, and other functions related to interacting with the physical medium 204.
[0069] The MII 216 may be configured to connect the RS sublayer 212 to the PCS block 220. In some embodiments, the MII 216 may also have a plurality of registers for supporting information exchange between the RS sublayer 212 and the PCS block 220. The MII 216 may also include an MDIO register primitive that selectively bypasses or enables internal forward error correction (FEC). In some embodiments, internal FEC may occur on an optical channel between two PHYs, where the PCS block 220 is a sublayer in the PHY.
[0070] The AUI 228 may be configured to connect the first PMA sublayer 224 and the second PMA sublayer 232. The AUI 228 may include physical and logical interfaces for connecting the sublayers 224,232.
[0071] As described above, the PCS block 220 of each networking device 104a, 104b may include auto-negotiation instructions 124. The auto-negotiation instructions 124 may enable the PCS block 220 of the first networking device 104a to negotiate with the PCS block 220 of the second networking device 104b. In some embodiments, the auto-negotiation may be transparent to the digital signal processor data path. The auto-negotiation between the PCS blocks 220 may also be transparent to the PMA sublayer 224, 232 and the PMD sublayer 236 of each networking device 104a, 104b. As shown, the PMA sublayer 232 and the PMD sublayer 236 may be included as part of the optical transceiver 244, while other components (e.g., MAC 208, RS212, PCS220, and PMA sublayer 224) may be included as part of the device hardware 240. Advantageously, the solution depicted and described herein does not require any significant changes to the functional operation of the existing optical transceiver 244. The auto-negotiation instructions 124 may enable the PCS block 220 of the first networking device 104a to incorporate auto-negotiation information into a control block that is sent to the PCS block 220 of the second networking device 104b. The control block may include an optical auto-negotiation (OAN) field and an OAN page, as will be described in further detail herein. The OAN page may include one or more protocol handshake variables.
[0072] The auto-negotiation information exchanged between the PCS blocks 220 facilitates the negotiation of communication settings or parameters to be used by the communication instructions 128 of the networking devices 104a, 104b. The auto-negotiation information may include one or more FEC fields indicating the internal FEC bypass logic and / or the convolution interleaver logic to be used for the communication link established between the networking devices 104a, 104b. The auto-negotiation information may also include one or more fields for supporting precoding or any other logical features supported by the optical transceiver 244. In some embodiments, the PCS blocks 220 may follow an auto-negotiation protocol, wherein at least one of the PMD control functions (e.g., link training, PMD startup protocol, etc.) and the transmit disable step is omitted. The link status check and transmit disable steps are typically used for traditional Ethernet negotiations involving separate electrical interfaces, but because the auto-negotiation protocol is executed through the optical network interface 108, the PMD control function and the transmit disable step may be omitted.
[0073] Reference now Figure 3 and Figure 4 , additional details regarding the control block 304 and its use in facilitating auto-negotiation over the optical network interface 108 will be described in accordance with at least some embodiments. Figure 3 Details of an example control block 304 are shown in which an OAN page is provided. There may be various types of OAN pages used at a portion of the control block 304. The size of the OAN page may be any suitable size, but the examples shown herein correspond to OAN pages having a size of 24 bits or 48 bits.
[0074] Figure 3 The examples of OAN pages shown in the figure include an OAN base page 308, an OAN message next page 312, and an OAN unformatted next page 316. It should be understood that the OAN page may include different formats, handshake variables or fields without departing from the scope of the present disclosure. The OAN base page 308 may include the clause 73 protocol handshake variables (e.g., RF, ACK, NP, etc.) for the AN base page example. Additional details of clause 73 are described in IEEE 802.3, the entire contents of which are hereby incorporated by reference herein. The OAN message next page 312 may follow the clause 73 protocol and use the same variables therein (e.g., T, ACK2, MP, ACK, NP, etc.). The OAN unformatted next page 316 may also utilize the variables defined in clause 73, but may be 48 bits.
[0075] As in Figure 4 As can be seen in FIG. 3 , a link 304 may be established between an OAN page (e.g., OAN base page 308) and a link codeword base page 404. The link codeword base page 404 is shown as having 16 data locations, but fewer or more data locations may be used without departing from the scope of the present disclosure.
[0076] In some embodiments, the OAN base page 308 may include handshake variables RF, ACK, and NP. It may not be necessary to define parameters such as E, C, T, and A because automatic negotiation occurs through the optical network interface 108. As described above, a new F parameter in the link codeword base page 404 may be provided for intra-FEC control. In some embodiments, the FEC field may include an F0 field, an F1 field, an F2 field, and an F3 field. These fields may support the definition of intra-FEC bypass logic and convolution interleaver logic.
[0077] The F0 field may define whether the networking device supports the inner FEC Hamming (128, 120) bypass and may be set to "1" for compatible devices. The F1 field may define whether the inner FEC Hamming (128, 120) bypass will be used. The F2 field may define whether the networking device supports an N-way convolutional interleaver (e.g., where N=12, N=6, N=4, etc.). The F3 field may define whether the 12-way convolutional interleaver is enabled. The inner FEC bypass logic may be defined as (LP.F0 AND RP.F0) AND (LP.F1 OR RP.F1). The convolutional interleaver logic may be defined as (LP.F2 AND RP.F2) AND (LP.F3 OR RP.F3). There may also be a number of bits reserved for future situations.
[0078] Reference now Figure 5A and Figure 5B , a first example 500 of an auto-negotiation and link-up process will be described in accordance with at least some embodiments of the present disclosure. The first auto-negotiation example 500 illustrates auto-negotiation between a first networking device 104a and a second networking device 104b, which begins with each networking device 104a, 104b determining a remote fault and a local fault. Thereafter, the AUI 228 and PMD sublayer 236 of each networking device 104a, 104b are indicated as ready (step 504). The indication of readiness may indicate that the AUI 228 and PMD sublayer 236 of each networking device 104a, 104b have completed any required form of calibration and / or equalization without being aware of the fact that auto-negotiation is occurring between the PCS blocks 220.
[0079] The PCS block 220 of the first networking device 104a then sends an AN command set (e.g., auto-negotiation information in the control block) to the PCS block 220 of the second networking device 104b. In response thereto or concurrently therewith, the PCS block 220 of the second networking device 104b sends an AN command set (e.g., auto-negotiation information in the control block) to the PCS block 220 of the first networking device 104a. The exchange of auto-negotiation information between the networking devices 104a, 104b enables the PCS blocks 220 of the networking devices 104a, 104b to negotiate communication settings or parameters. Once the auto-negotiation information has been exchanged and the auto-negotiation instructions 124 of each networking device 104a, 104b have applied the appropriate logic, the auto-negotiation is complete (step 508). Confirmation of the completion of the auto-negotiation results in the establishment of a communication link between the first networking device 104a and the second networking device 104b according to the communication settings or parameters defined during the auto-negotiation process (step 512).
[0080] Reference now FIG. 6A to FIG. 6C , a second example 600 of an auto-negotiation and linking process will be described in accordance with at least some embodiments of the present disclosure. The second auto-negotiation example 600 shows an auto-negotiation between a first networking device 104a and a second networking device 104b, which begins with each networking device 104a, 104b determining a remote fault and a local fault. Thereafter, the AUI 228 and the PMD sublayer 236 of each networking device 104a, 104b are indicated as ready (step 604).
[0081] The PCS block 220 of the first networking device 104a then sends the AN command set (e.g., auto-negotiation information in the control block) to the PCS block 220 of the second networking device 104b. In response thereto or concurrently therewith, the PCS block 220 of the second networking device 104b sends the AN command set (e.g., auto-negotiation information in the control block) to the PCS block 220 of the first networking device 104a. The exchange of auto-negotiation information between the networking devices 104a, 104b enables the PCS blocks 220 of the networking devices 104a, 104b to negotiate communication settings or parameters. Once the auto-negotiation information has been exchanged and the auto-negotiation instructions 124 of each networking device 104a, 104b have applied the appropriate logic, the auto-negotiation is complete (step 608).
[0082] The second auto-negotiation example 600 further illustrates the process of negotiating FEC. Figure 6B and Figure 6C As shown, the FEC sublayer and PMA sublayer of each networking device 104a, 104b may further perform unidirectional FEC locking (step 612) and then perform end-to-end (E2E) FEC locking (step 616). The unidirectional FEC locking may be performed by the RS sublayer 212 of one networking device sending FEC information to the PCS block 220 of another networking device. In some embodiments, the networking devices may include MDIO register primitives or common management interface specification (CMIS) registers that selectively bypass or enable internal FEC between the PCS block 220 of the first networking device 104a and the PCS block 220 of the second networking device 104b.
[0083] Confirmation of the completion of auto-negotiation and FEC lock results in a communication link being established between the first networking device 104a and the second networking device 104b according to the communication settings or parameters defined during the auto-negotiation process (step 620). It should be appreciated that FEC can be used to increase the resilience of a link to errors, with some penalties for power and latency. For this reason, some solutions may prefer to operate with FEC - to increase resilience, while other solutions may benefit from operating without FEC to optimize power and latency.
[0084] Reference now Fig. 7A and Figure 7B , a third example 700 of an auto-negotiation and linking process will be described in accordance with at least some embodiments of the present disclosure. The third auto-negotiation example 700 illustrates auto-negotiation between a first networking device 104a and a second networking device 104b, where the second networking device 104b includes a legacy host 704. The legacy host 704 may include hardware, firmware, etc. that is older than the hardware or firmware of the first networking device 104a, and therefore does not support certain features available to the first networking device 104a. For example, the PCS block 220 of the legacy host 704 does not include auto-negotiation instructions 124 or capabilities.
[0085] The third auto-negotiation example 700 begins with the PCS block 220 of the first networking device 104a sending an AN command set to the PCS block 220 of the second networking device 104b. The PCS block 220 of the second networking device 104b sends a local fault to the RS sublayer 212 of the second networking device 104b, and the RS sublayer 212 sends a remote fault result back to the PCS block 220 of the first networking device 104a. Receiving the remote fault result at the first networking device 104a causes the devices 104a, 104b to enter a link status check state (step 708).
[0086] Thereafter, the PCS block 220 of the first networking device 104a sends the remote fault result to the RS sublayer 212 of the first networking device 104a. In this step, the RS sublayer 212 of the first networking device 104a is receiving the remote fault result of the second networking device 104b and starts to send IDLE to the outdated host 704 (step 712).
[0087] Once the auto-negotiation information has been exchanged and the auto-negotiation instructions 124 of the first networking device 104a have determined the appropriate communication settings or parameters for supporting communication between the networking devices 104a, 104b, the auto-negotiation is complete (steps 716 and 720). In this particular example, there may not actually be auto-negotiation because the legacy host 704 may not be aware of the OAN process. However, this example shows that a link may still be established using some configuration based on the legacy host 704 configuration. In this way, the OAN process described herein may be backward compatible with legacy devices (e.g., legacy host 704).
[0088] Reference now Figure 8 , additional details and functions of systems, networks and devices will be described according to at least some embodiments of the present disclosure. Various methods will be described with reference to specific elements. It should be understood that the steps of some methods can be incorporated into other methods and / or the order of the steps of some methods can be changed without departing from the scope of the present disclosure. In addition, although some steps are described as being performed by an element, it should be understood that other elements can be configured to perform similar or identical steps without departing from the scope of the present disclosure.
[0089] Furthermore, the method 800 will be described in accordance with at least some embodiments of the present disclosure. Some or all of the steps of the method 800 may be performed at a networked device 104a, 104b using some or all of the components of the networked device 104a, 104b as depicted and described herein.
[0090] Method 800 begins by connecting a networking device (e.g., first networking device 104a) to a network via optical network interface 108 (step 804). When a networking device is connected to a network (e.g., an Ethernet cable connected to a larger network is physically connected to the networking device), the networking device may begin a process of discovering the communication capabilities of other networking devices that are also connected to the network.
[0091] Method 800 may continue by enabling the networking device to perform auto-negotiation with at least one other networking device via optical network interface 108 (step 808). As described herein, the auto-negotiation process may include the networking device utilizing auto-negotiation instructions 124 and PCS block 220 to exchange auto-negotiation information with another networking device.
[0092] When the auto-negotiation is complete, the method 800 continues (step 812). The method 800 may also include an optical FEC locking step (step 816). The completion of the auto-negotiation and optional FEC locking may result in communication settings or parameters being defined to support a communication link between a networked device and another networked device with which the auto-negotiation is performed (step 820). Specifically, the networked devices involved in the auto-negotiation may configure their communication instructions 128 according to the communication settings or parameters defined during the auto-negotiation and optional FEC locking process. Once each networked device has appropriately configured its communication instructions 128, the link between the networked devices may be completed, and data may then be exchanged between the networked devices (step 824). The data may be exchanged through the same optical network interface 108 used to facilitate the auto-negotiation. In some embodiments, the auto-negotiation is performed at a nominal communication rate that is also used to exchange optical data signals via the optical network interface. In other words, the auto-negotiation is performed at approximately the same speed at which the networked devices send and / or receive optical data signals.
[0093] It should be understood that any feature described herein may be claimed in combination with any other feature or features as described herein, regardless of whether or not such features are from the same described embodiment.
[0094] Specific details are given in the description to provide a thorough understanding of these embodiments. However, it will be understood by those of ordinary skill in the art that the embodiments can be practiced without these specific details. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the embodiments.
[0095] While illustrative embodiments of the present disclosure have been described in detail herein, it should be understood that the inventive concepts may be otherwise variously embodied and employed, and that the appended claims are intended to be interpreted to include such variations unless limited by prior art.< / n>
Claims
1. A system comprising: A first physical coding sublayer (PCS) block, the first PCS block merging auto-negotiation information into a control block, wherein the control block is sent to a second PCS block, and wherein the auto-negotiation information is used to enable negotiation between the first PCS block and the second PCS block.
2. The system of claim 1, wherein the control block is transparent to the digital signal processor data path.
3. The system of claim 1, wherein the negotiation between the first PCS block and the second PCS block is transparent to a physical medium attachment (PMA) sublayer and a physical medium dependent (PMD) sublayer.
4. The system of claim 1, wherein the control block is transmitted to the second PCS block via an optical signal.
5. The system of claim 1 , wherein the first PCS block is part of a transmitter device in a communication network, and wherein the transmitter device further comprises a management data input / output (MDIO) register primitive that selectively bypasses or enables inner forward error correction (FEC) between the first PCS block and the second PCS block.
6. The system of claim 1, wherein the control block comprises an optical auto-negotiation (OAN) field and an OAN page.
7. The system of claim 6, wherein the OAN page includes one or more protocol handshake variables.
8. The system of claim 1, wherein the first PCS block and the second PCS block follow an auto-negotiation protocol in which at least one of a link status check and a transmission disable step is omitted.
9. A networked device comprising: Optical network interface; as well as Physical coding sublayer PCS block, the PCS block is used for: sending and / or receiving optical data signals via the optical network interface; and Auto-negotiation is performed with another networking device via the optical network interface.
10. The networking device of claim 9, wherein the automatic negotiation is performed by exchanging optical symbols with the other networking device.
11. The networking device of claim 9, wherein the auto-negotiation is performed at a nominal communication rate also used to exchange the optical data signals via the optical network interface.
12. The networking device of claim 9, wherein the auto-negotiation is performed at substantially the same speed as transmitting and / or receiving the optical data signals.
13. The networking device of claim 9, wherein an auto-negotiation state machine is included in the PCS block.
14. The networking device of claim 9, wherein the optical network interface comprises an Ethernet interface.
15. The networking device of claim 9, further comprising a forward error correction (FEC) unit that locks the communication link with the other networking device.
16. An optical communication system, comprising: At least one communication node comprises an optical transceiver and a physical coding sublayer (PCS) block, wherein the PCS block is used to perform auto-negotiation with another communication node in the optical communication system via the optical transceiver.
17. The optical communication system of claim 16, wherein the PCS block incorporates auto-negotiation information into a control block sent to the another communication node.
18. The optical communication system of claim 17, wherein the auto-negotiation information comprises one or more forward error correction (FEC) fields.
19. The optical communication system of claim 18, wherein the one or more FEC fields indicate inner FEC bypass logic and / or convolutional interleaver logic to be used for the communication link established with the other communication node.
20. The optical communication system of claim 16, wherein the auto-negotiation is performed at a nominal communication rate also used to exchange optical data signals via the optical transceiver.
Citation Information
Cited By
Link state adjustment method, apparatus and system, communication apparatus, and chip
WO2026113382A1
