Ocs link recovery control architecture for optical-electrical hybrid network based on out-of-band channel

Abstract

The application discloses an optical-electric hybrid network OCS link recovery control architecture based on an out-of-band channel and relates to the technical field of optical circuit switching control.The application is based on a hardware foundation of separation of a control channel and a data channel, recovery control state records are maintained by an OCS operating system, and optical path states in the OCS and recovery states of ports on the electric domain side are collected.Equalizer parameters are preset, transmission recovery triggers and state information are transmitted through the out-of-band control channel, and the collaborative control of equalizer recovery, CDR locking confirmation, data boundary confirmation and service data release is realized.The application significantly shortens the additional waiting time from the formation of a target optical path to the release of service data, and improves the optical path reconstruction efficiency of the AIDC optical-electric hybrid network.

Description

Technical Field

[0001] This invention belongs to the field of optical circuit switching control technology, and in particular relates to an OCS optical link recovery collaborative control architecture based on out-of-band control channels, which is suitable for high-speed interconnection scenarios of large-scale computing nodes in artificial intelligence data centers (AIDCs). Background Technology

[0002] In Artificial Intelligence Data Centers (AIDCs), large-scale interconnection of computing nodes places high demands on bandwidth, power consumption, and latency. Optical CS (Optical Components Controlled Path) can establish direct optical paths between electrical domain devices on demand, making it suitable for carrying high-bandwidth service connections. However, in hybrid optoelectronic networks, the formation of a target optical path within the OCS does not equate to the transceivers of the electrical domain devices on both sides of that optical path being ready for service use.

[0003] Typically, after the target optical path is formed, for any transmission direction, the receiving direction's electrical domain side data plane interface still needs to sequentially complete equalizer recovery, Clock and Data Recovery (CDR) lock confirmation, and data boundary confirmation. Only after equalizer convergence, CDR lock confirmation, and data boundary confirmation all meet preset conditions can service data be allowed to pass.

[0004] In existing OCS optical path reconfiguration processes, the internal optical path status of the OCS is typically maintained by the OCS side, while the equalizer convergence status, CDR lock confirmation status, data boundary confirmation status, and service data gating status are generated at the port side of the electrical domain equipment. These statuses are distributed across the OCS side and the electrical domain endpoints on both sides of the optical path. When the software control plane uniformly collects the internal optical path status of the OCS and the port-side recovery status involved in a single optical path reconfiguration, the status sources are scattered, resulting in long status feedback paths. Furthermore, without utilizing a port-level out-of-band control channel separate from the data channel to carry recovery control information, the equalizer preset information, recovery trigger information, recovery status and confirmation information, and recovery adjustment information corresponding to the target optical path are often difficult to transmit in a timely manner between the OCS-side coordinating body and the electrical domain-side port. Consequently, the OCS-side coordinating body struggles to obtain the port-side recovery status based on the target optical path context and issue necessary recovery adjustments in a timely manner, resulting in a significant additional waiting time between the formation of the target optical path and the release of service data.

[0005] Therefore, based on the existing control hardware architecture, it is necessary to further refine its control mechanism in the optical link recovery scenario, so that the control channel can be used for recovery configuration preset, recovery status feedback and recovery adjustment coordination, and coordinate service data gating and release around the recovery control status record, thereby reducing the additional waiting time between the formation of the target optical path and the release of service data. Summary of the Invention

[0006] The technical problem this invention aims to solve is that in existing optoelectronic hybrid networks, the state of the electrical domain side port recovery process after OCS optical path reconstruction is scattered, control information transmission is not timely, and there is a lack of effective coordination mechanism, resulting in an excessively long additional waiting time between the formation of the target optical path and the release of service data.

[0007] To address the aforementioned technical issues, this invention provides an OCS link recovery control architecture based on out-of-band channels. Its core idea is to utilize an out-of-band control channel separate from the data channel to achieve timely interaction of recovery control information between the OCS side and the electrical domain side; the OCS operating system uniformly maintains recovery control status records, aggregating the optical path status within the OCS and the port recovery status on the electrical domain side; recovery configurations are pre-set before the target optical path is formed, and status feedback and dynamic adjustments are performed during the recovery process to achieve coordinated control of the port-side recovery process.

[0008] The specific technical solution is as follows:

[0009] Infrastructure and Recovery Control State Record

[0010] This invention is based on an OCS control hardware architecture that separates the control channel and the data channel. By utilizing the separation structure of the control channel and the data channel, the recovery configuration preset before or during the formation of the target optical path, as well as the recovery trigger, recovery status feedback and recovery adjustment after the formation of the target optical path, can be performed through the control channel without relying on the data channel having entered a service-available state.

[0011] The OCS operating system, acting as the coordinating entity for optical path reconstruction and recovery, maintains a recovery control state record corresponding to each optical path reconstruction. This recovery control state record includes at least the internal optical path state of the OCS, equalizer convergence state, CDR lock confirmation state, phase deviation information related to CDR lock confirmation, data boundary confirmation state, and service data gating state. The OCS operating system uses the target optical path corresponding to this optical path reconstruction and its two adjacent electrical domain endpoints as associated objects, collecting and updating the state information from the OCS-side control plane interface and processing unit and the electrical domain-side control plane interface and processing unit. This allows the internal optical path state of the OCS and the port-side recovery states of the electrical domain devices on both sides to be coordinated and used within the same recovery control state record.

[0012] In some implementations, the recovery control state record can be established when an optical path reconfiguration request arrives, and associated with the recovery processes of different target optical paths in conjunction with the recovery object identification information. This allows for the separate aggregation of recovery configurations, recovery states, and service data gating states corresponding to multiple concurrent optical path reconfigurations, avoiding state confusion between different recovery processes. The recovery control state record may also include at least one of the following: stage timing information, stage exception reasons, retry count information, recovery cancellation flag, or recovery failure flag. This information is used by the OCS operating system to maintain the correspondence between the recovery control state record and the port-side recovery state when recovery is incomplete, state feedback is missing, state order is inconsistent, or the recovery process is canceled.

[0013] Based on this, the OCS operating system coordinates port-level control with the electrical domain side control plane interface and processing unit through the OCS-side control plane interface and control channel. The electrical domain side control plane interface and processing unit interacts with the electrical domain side data plane interface through the internal control interaction path of the electrical domain side port. This is used to write or associate recovery configurations related to data plane execution to the receiving-side electrical domain side data plane interface, and to receive and aggregate the recovery status returned by it.

[0014] This invention uses the recovery control state record corresponding to a single optical path reconstruction and the port-side recovery process of the associated receiving direction electrical domain side data plane interface as the main recovery control content. The receiving direction electrical domain side data plane interface may include or be associated with an equalizer recovery function unit, a CDR lock confirmation function unit, a data boundary confirmation function unit, and a service data gating function unit. Specifically, the equalizer recovery function unit performs equalizer preset, equalizer local training, or equalizer recovery confirmation; the CDR lock confirmation function unit performs CDR lock confirmation after the equalizer recovery meets the conditions; the data boundary confirmation function unit performs word boundary, block boundary, or frame boundary confirmation after the CDR lock confirmation meets the conditions; and the service data gating function unit maintains service data gating until the above recovery states meet the service data release conditions, and performs service data release after the release conditions are met. The transmitting direction electrical domain side data plane interface corresponding to this receiving direction participates in CDR lock cooperative control as the object of the recovery adjustment information.

[0015] In some implementations, the equalizer recovery function unit can be implemented by an equalizer, equalizer parameter register, training state machine, or a combination thereof in the receiving direction electrical domain side data plane interface. The CDR lock confirmation function unit can be implemented by a CDR loop, phase detection logic, loop control logic, and lock status register. As an exemplary physical implementation, during service data gating, the transmitting direction port can send a preset transition sequence on the data channel, enabling the receiving direction CDR to obtain continuous transition edges; the preset transition sequence is a non-service data pattern agreed upon on the port side, and the specific code type is not limited. The phase detection logic forms an early / late decision based on the early / late relationship between the transition edge and the local sampled phase, and the loop control logic counts the bias of the early / late decision within a preset observation window and forms a digital phase deviation field with direction and amplitude. This digital phase deviation field is used to characterize the residual phase deviation of the current received signal relative to the CDR lock target, which belongs to the sorting result of the receiving direction local recovery state.

[0016] The data boundary confirmation function unit can be implemented by block synchronization logic, block locking logic, synchronization header detection logic, or word boundary detection logic in the physical coding sublayer. It is used to form a data boundary confirmation state after the CDR locking confirmation condition is met. The service data gating function unit can be located on the service data output path of the receiving direction electrical domain side data plane interface, and before the service data output position after the data boundary confirmation is completed. It is used to perform output blocking control on the service data output path before the service data release condition is met, so that the service data reaching this position is directly discarded; after the service data release condition is met, the output blocking control is released and the service data output is restored.

[0017] Restore the composition and carrying relationship of control information

[0018] In this invention, the recovery control information carried by the control channel includes a pre-set optical link recovery configuration set before or during the formation of the target optical path, and recovery process interaction information transmitted after the formation of the target optical path and before the release of service data. The former is used to establish a port-side recovery context corresponding to the target optical path, and the latter is used to complete recovery triggering, status confirmation, and subsequent adjustments.

[0019] The OCS operating system generates an optical link recovery configuration set based on the target optical path and its link attributes, and pre-configures it to the electrical domain side control plane interface and processing unit via the OCS-side control plane interface and processing unit and control channel. The link attributes may include at least one of the following: link length, fiber type, port type, or other parameters characterizing the transmission conditions of the target optical path. The optical link recovery configuration set can be generated based on the link attributes, combined with historical recovery results, deployment calibration results, default parameters, or combinations thereof corresponding to the target optical path. The electrical domain side control plane interface and processing unit then writes or associates the configuration related to data plane execution to the receiving-side electrical domain side data plane interface via the internal control interaction path of the electrical domain side port.

[0020] The optical link recovery configuration set includes at least equalizer preset information. This equalizer preset information is used to provide the equalizer recovery function unit in the receiving direction electrical domain side data plane interface with initial equalizer parameters corresponding to the target optical path, or to provide the parameter range and constraints for local training, enabling the receiving direction electrical domain side data plane interface to enter equalizer recovery from the preset parameters or limited training range after the target optical path is formed. The equalizer preset information can be generated from historical recovery results corresponding to the target optical path, deployment calibration results, reference parameters of similar links, link attribute information, default parameters, or combinations thereof.

[0021] To facilitate the use of the aforementioned recovery control information, the electrical domain-side control plane interface and processing unit saves or calls local recovery completion determination rules corresponding to port type, protocol rules, or target optical path attributes. These rules are local judgment criteria of the electrical domain-side control plane interface and processing unit, and are not information items carried by the control channel, nor are they independent configuration contents in the optical link recovery configuration set. They are used to determine whether the service data release conditions are met based on the equalizer convergence status, CDR lock confirmation status, and data boundary confirmation status returned by the receiving direction electrical domain-side data plane interface.

[0022] In some implementations, the local recovery completion determination rule may take the following form: when the equalizer training error metric is lower than a first threshold within a first duration period, the equalizer is determined to have converged; when the CDR phase deviation is lower than a second threshold within a second duration period, the CDR lock confirmation is determined to be satisfied; when the physical coding sublayer continuously detects a preset number of correct synchronization header, block lock results, or boundary markers, the data boundary confirmation is determined to be satisfied. The aforementioned thresholds, duration periods, and preset number of times can be configured according to the port rate, encoding method, protocol type, and device implementation.

[0023] The recovery process interaction information differs from the preset optical link recovery configuration set and includes at least one or more of the following:

[0024] Optical link recovery trigger information is used to instruct the receiving direction electrical domain side data plane interface to start executing the recovery process corresponding to the target optical path;

[0025] Recovery status and confirmation information are used to represent the equalizer convergence status, CDR lock confirmation status, phase deviation information related to CDR lock confirmation, data boundary confirmation status, and service data gating status, and form a stage confirmation when the conditions are met in the corresponding recovery stage; the phase deviation information is formed by the receiving direction electrical domain side data plane interface according to the local recovery status in the CDR lock confirmation process, and is used to characterize the degree of phase deviation or adjustment direction of the current received signal relative to the CDR lock target;

[0026] The recovery adjustment information is used to instruct the equalizer to be retrained, the equalizer parameter search range to be expanded, the transmit clock phase auxiliary adjustment to be triggered based on the phase deviation information, and the data boundary confirmation to be re-executed when the recovery state conditions are not met.

[0027] The aforementioned optical link recovery configuration set and recovery process interaction information correspond to the specific content carried by information categories D1 to D5 in the optical link recovery and service data release scenario. Specifically, D1 is optical path reconstruction control information, used to characterize the object to be reconstructed, target optical path requirements, and related port or internal connectivity constraints; the optical link recovery configuration set corresponds to port-side preset information D2; the optical link recovery trigger information corresponds to connection recovery trigger information D3; recovery status and confirmation information correspond to status feedback information D4; and D5 is optical path reconstruction and recovery result information, used to characterize the internal optical path status of the OCS, port-side recovery status, service data release result, cause of anomalies, or final availability confirmation result. The basic functions of D1 and D5 follow the existing optical path reconstruction control information and optical path reconstruction result information; this invention mainly refines the recovery configuration preset, recovery trigger, recovery status feedback, recovery adjustment, and service data release control content carried by D2, D3, and D4 in the optical link recovery scenario. Recovery adjustment information can be formed based on the D4 result and distributed as the content of subsequent connection recovery trigger information D3.

[0028] In some implementations, the recovery status and confirmation information D4 may further include at least one of the following: a phase incomplete flag, a phase anomaly cause, a phase timing status, retry count information, or a recovery cancellation flag. This information is used by the OCS operating system to determine, based on the recovery control status record, whether to continue waiting, re-issue the light link recovery trigger information, issue recovery adjustment information, end the current recovery control status record, or report the recovery incompleteness or failure result to the network controller via the control connection.

[0029] The collaborative process for recovery triggering and business data release based on the control channel:

[0030] After the target optical path is formed, the data channel may still be in a training, synchronization, or gating state. This invention continues to use the control channel as the port-side recovery control path. The OCS operating system sends optical link recovery trigger information to the electrical domain-side control plane interface and processing unit via the OCS-side control plane interface and processing unit corresponding to the target port and the control channel. The electrical domain-side control plane interface and processing unit associates the trigger information with the pre-set recovery configuration and triggers the receiving-direction electrical domain-side data plane interface to enter the recovery process corresponding to the target optical path via the internal control interaction path of the electrical domain-side port.

[0031] The receiving direction's electrical domain side data plane interface executes port-side recovery actions sequentially: first, the equalizer recovery function unit performs equalizer recovery; after the equalizer recovery meets the conditions, the CDR lock confirmation function unit performs CDR lock confirmation; after the CDR lock confirmation meets the conditions, the data boundary confirmation function unit performs data boundary confirmation. Each of these stages forms a corresponding recovery state, which is then returned to the electrical domain side control plane interface and processing unit via the internal control interaction path of the electrical domain side port.

[0032] The electrical domain-side control plane interface and processing unit determine the aforementioned recovery status based on the local recovery completion judgment rules. When equalizer convergence, CDR lock confirmation, and data boundary confirmation are not all met, the electrical domain-side control plane interface and processing unit, through the internal control interaction path of the electrical domain-side port, maintain service data gating by the service data gating function unit and directly discard service data arriving at the service data output path. Once the above conditions are met, the service data gating function unit immediately releases the service data gating and generates a service data gating status and service data release condition judgment result. After gating is released, the service data can continue to be processed by the electrical domain communication entity according to relevant communication protocols, such as Ethernet communication protocol, InfiniBand communication protocol, or other packet communication protocols for regular frame or message processing. If any recovery stage fails to meet the conditions, the stage anomaly is not resolved, or the recovery process is canceled, the service data gating function unit continues to maintain service data gating until new service data release conditions are met or the corresponding recovery control status record is terminated.

[0033] The recovery status and confirmation information that need to be transmitted back to the OCS side are sent by the corresponding electrical domain side control plane interface and processing unit to the corresponding OCS side control plane interface and processing unit via the control channel, and then sent to the OCS operating system by the OCS side control plane interface and processing unit. The recovery status and confirmation information are used to indicate at least the port-side recovery stage, the result of the service data release condition determination, the phase deviation information related to CDR lock confirmation, or the cause of the corresponding stage abnormality.

[0034] The OCS operating system generates recovery adjustment information based on the target optical path context and the feedback results, and sends it to the corresponding electrical domain side control plane interface and processing unit through the OCS-side control plane interface and processing unit and control channel of the corresponding target port. If the feedback results indicate that recovery actions need to be performed on the receiving electrical domain side data plane interface, such as when the equalizer convergence state or data boundary confirmation state is not met, the recovery adjustment information is used to instruct the equalizer to be retrained, the equalizer parameter search range to be expanded, or the data boundary confirmation to be re-executed. If the equalizer has converged but the CDR lock confirmation is not met and the feedback results include phase deviation information, the recovery adjustment information is used to instruct the transmitting electrical domain side control plane interface and processing unit to trigger the transmitting electrical domain side data plane interface to perform auxiliary adjustment of the transmitting clock phase via the internal control interaction path of the electrical domain side port, so that the receiving electrical domain side data plane interface obtains an input signal more favorable for CDR lock confirmation. As an exemplary physical implementation, the transmit direction electrical domain side control plane interface and processing unit can write recovery adjustment information into the phase adjustment control register of the transmit direction port. Based on this, the transmit direction electrical domain side data plane interface changes the phase control word of the local transmit clock, causing the edges of the transmitted serial data to be slightly advanced or delayed relative to the original transmit clock. This phase control can be implemented using a phase-locked loop (PLL) phase selection, a phase interpolator, a controllable delay line, or an equivalent transmit clock phase selection circuit.

[0035] The present invention has the following advantages over the prior art:

[0036] (1) The port-side recovery status is returned through the control channel, and the OCS operating system associates the internal optical path status of the OCS and the port-side recovery status with the recovery control status record, so that recovery configuration, status return, recovery adjustment and service data gating can be coordinated in the same recovery control context, reducing the coordination overhead caused by decentralized judgment and decentralized waiting;

[0037] (2) By transmitting recovery configuration, recovery trigger information, recovery status and confirmation information and recovery adjustment information through the control channel, the OCS operating system can still obtain the port-side recovery status and issue recovery adjustments when the business data has not yet been released through the data channel, reducing the waiting time introduced by relying on the business data channel to be available before performing status aggregation and configuration adjustment;

[0038] (3) By presetting the initial parameters, local training range or constraints of the equalizer before or during the formation of the target optical path, the data plane interface on the receiving direction electrical domain side can enter the equalizer recovery based on the target optical path recovery context, thereby reducing the additional waiting caused by re-searching or fully training the equalizer parameters after the target optical path is formed.

[0039] (4) By triggering the transmit clock phase adjustment based on the phase deviation information when the equalizer has converged but the CDR lock confirmation condition is not met, the data plane interface on the receiving direction electrical domain side obtains input signal conditions that are more favorable to CDR lock confirmation, thereby reducing the probability of repeated waiting, repeated attempts or timeout backoff caused by unfavorable phase relationship.

[0040] Of course, any product implementing this invention does not necessarily need to achieve all of the advantages described above at the same time. Attached Figure Description

[0041] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a schematic diagram of the fast OCS control hardware architecture and centralized optical path control system for AIDC optoelectronic hybrid networks on which this invention is based.

[0043] Figure 2 This is a schematic diagram of the specific hardware implementation structure of the OCS control hardware architecture on which this invention is based;

[0044] Figure 3 This is a schematic diagram of the optical link recovery and service data gating function structure of the receiving direction electrical domain side port in this invention;

[0045] The attached diagram lists the components represented by each number as follows:

[0046] 101 Network Controller; 201 Control connection between Network Controller and Electrical Domain Device; 201A Control connection between Network Controller and First Electrical Domain Device; 201B Control connection between Network Controller and Second Electrical Domain Device; 202 Control connection between Network Controller and OCS Device; 301 Electrical Domain Device; 301A First Electrical Domain Device; 301B Second Electrical Domain Device; 302 Electrical Domain Device Operating System; 302A First Electrical Domain Device Operating System; 302B Second Electrical Domain Device Operating System; 303 Electrical Domain Communication Entity; 303A First Electrical Domain Communication Entity; 303B Second Electrical Domain Communication Entity; 304 Electrical Domain-Side Transceiver; 304A First Electrical Domain-Side Transceiver; 304B Second Electrical Domain-Side Transceiver; 305 Electrical Domain Side Control Plane Interface and Processing Unit; 305A First Electrical Domain Side Control Plane Interface and Processing Unit; 305B Second Electrical Domain Side Control Plane Interface and Processing Unit; 306 Electrical Domain Side Data Plane Interface; 306A First Electrical Domain Side Data Plane Interface; 306B Second Electrical Domain Side Data Plane Interface; 307 Electrical Domain Side Demultiplexing / Splitting Unit; 307A First Electrical Domain Side Demultiplexing / Splitting Unit; 307B Second Electrical Domain Side Demultiplexing / Splitting Unit; 308 Electrical Domain Side Port Internal Control Interaction Path; 308A First Electrical Domain Side Port Internal Control Interaction Path; 308B Second Electrical Domain Side Port Internal Control Interaction Path; 401 OCS Equipment; 402 OCS Operating System; 403 Optical Switching Matrix; 404 OCS Side Transceiver Devices; 404A OCS-side transceiver corresponding to the first electrical domain side; 404B OCS-side transceiver corresponding to the second electrical domain side; 405 OCS-side control plane interface and processing unit; 405A OCS-side control plane interface and processing unit corresponding to the first electrical domain side; 405B OCS-side control plane interface and processing unit corresponding to the second electrical domain side; 406 OCS-side data plane interface; 406A OCS-side data plane interface corresponding to the first electrical domain side; 406B OCS-side data plane interface corresponding to the second electrical domain side; 407 OCS-side demultiplexing / multiplexing unit; 407A OCS-side demultiplexing / multiplexing unit corresponding to the first electrical domain side; 407B OCS-side demultiplexing / multiplexing unit corresponding to the second electrical domain side. ; 408 OCS-side port internal control interaction path; 408A and the OCS-side port corresponding to the first electrical domain side internal control interaction path; 408B and the OCS-side port corresponding to the second electrical domain side internal control interaction path; 501 External optical fiber; 501A External optical fiber connecting the transceiver on the first electrical domain side and the corresponding OCS-side transceiver; 501B External optical fiber connecting the transceiver on the second electrical domain side and the corresponding OCS-side transceiver; 502 OCS internal data plane path; 503 Control channel; 504 Data channel; 601 Status centralized coordination range schematic box; 701 Equalizer recovery function unit; 702 CDR lock confirmation function unit; 703 Data boundary confirmation function unit; 704 Service data gating function unit. Detailed Implementation

[0047] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0048] This invention is based on Figure 1 and Figure 2 The OCS control hardware architecture implementation is shown below. Figure 1 As shown, the network controller 101 is connected to the two electrical domain devices 301 via control connection 201 and to the OCS device 401 via control connection 202, for transmitting optical path reconstruction control information and receiving optical path reconstruction results. The electrical domain-side transceiver 304 in the electrical domain device 301 is connected to the corresponding OCS-side transceiver 404 via an external optical fiber 501. The external optical fiber 501 may include a control channel 503 and a data channel 504, used to carry control signals and data plane signals respectively. The OCS device 401 internally includes an OCS operating system 402, an optical switching matrix 403, an OCS-side transceiver 404, and an OCS internal data plane path 502; the electrical domain device 301 internally includes an electrical domain device operating system 302, an electrical domain communication entity 303, and an electrical domain-side transceiver 304. Figure 1 The schematic box 601 in the state central coordination scope is used to indicate that the coordinated components and their states directly related to a single end-to-end optical path reconstruction are included in the unified coordination scope. The schematic box is used to indicate the coordination processing boundary, and does not indicate the addition of new independent physical devices, nor does it indicate that the complete electrical domain device 301 is included in the control scope of the OCS operating system 402. The unified coordination scope includes at least: the electrical domain transceiver 304, the port-side functional units in the OCS-side transceiver 404 related to port-side preset, connection restoration triggering and state backhaul, the optical switching matrix 403, the OCS internal data plane path 502, and the external optical fiber 501 and its related channels.

[0049] like Figure 2As shown, the electrical domain transceiver 304 internally includes at least an electrical domain control plane interface and processing unit 305, an electrical domain data plane interface 306, an electrical domain demultiplexing / multiplexing unit 307, and an electrical domain port internal control interaction path 308; the OCS-side transceiver 404 internally includes at least an OCS-side control plane interface and processing unit 405, an OCS-side data plane interface 406, an OCS-side demultiplexing / multiplexing unit 407, and an OCS-side port internal control interaction path 408. Specifically, the electrical domain-side control plane interface and processing unit 305 and the OCS-side control plane interface and processing unit 405 are used for control signal transmission and reception, local information processing, and status organization; the electrical domain-side data plane interface 306 and the OCS-side data plane interface 406 are used for connection establishment or connection restoration, with the OCS-side data plane interface 406 also interfacing with the OCS internal data plane path 502; the electrical domain-side demultiplexing / multiplexing unit 307 and the OCS-side demultiplexing / multiplexing unit 407 are used for demultiplexing or multiplexing control signals and data plane signals; the electrical domain-side port internal control interaction path 308 and the OCS-side port internal control interaction path 408 are used to transmit port-side control information within their respective transceivers. Figure 2 It is known that the control channel 503 and the data channel 504 enter the corresponding functional units on the port side, thereby realizing the separation of the control path and the data plane path, and providing a hardware foundation for the OCS operating system 402 to centrally coordinate port-side presets, connection recovery triggers and status feedback through the OCS-side control plane interface and processing unit 405, and through the control channel 503 and the electrical domain-side control plane interface and processing unit 305.

[0050] like Figure 3 As shown, the control channel 503 in the external optical fiber 501 enters the electrical domain-side control plane interface and processing unit 305 via the electrical domain-side splitter / multiplexer unit 307, and the data channel 504 enters the receiving-side electrical domain-side data plane interface 306 via the electrical domain-side splitter / multiplexer unit 307. The electrical domain-side control plane interface and processing unit 305 interact with the receiving-side electrical domain-side data plane interface 306 via the electrical domain-side port internal control interaction path 308 to restore configuration, restore status, and service data gating control information. The receiving-side electrical domain-side data plane interface 306 is schematically configured with an equalizer recovery function unit 701, a CDR lock confirmation function unit 702, a data boundary confirmation function unit 703, and a service data gating function unit 704, which are used to demonstrate that after the target optical path is formed, the port-side recovery control is completed in the order of equalizer recovery, CDR lock confirmation, data boundary confirmation, and service data release.

[0051] The implementation of the present invention will be described below with reference to specific embodiments:

[0052] Example 1: Restoring the data format of control state, message type, and interaction information

[0053] This embodiment illustrates a field organization method for recovery control status, message types D1 to D5, optical link recovery configuration set, and recovery process interaction information, wherein the recovery control status record is maintained locally by the OCS operating system 402.

[0054] Data format for recovery control status: Recovery control status is a data record maintained internally by the OCS operating system 402, used to associate the internal optical path status of the target optical path with the port-side recovery status of the electrical domain endpoints on both sides of the target optical path. This data record can be abstracted as an object containing recovery object identification information, target optical path identification information, status update time, and recovery status group. Its exemplary JSON structure can be represented as follows:

[0055] {

[0056] "Restore object identification information":"restore-object-001",

[0057] "Target optical path identification information":"path-oc-001",

[0058] "Status Update Time":"2026-05-20T10:00:00+08:00",

[0059] "Recovery Status Group":{

[0060] "OCS Internal Optical Path Status": "Established"

[0061] Equalizer convergence status: "Converged"

[0062] "CDR lock confirmation status": "Not satisfied"

[0063] "Phase deviation information":{

[0064] "Direction": "Lag"

[0065] "Amplitude": 12.5,

[0066] Dimensions: "ps"

[0067] },

[0068] "Data boundary confirmation status": "Unconfirmed"

[0069] "Business Data Gating Status": "Gating Maintained"

[0070] "Stage timer status": "Preset waiting time has not exceeded",

[0071] "Retry count information": 1

[0072] }

[0073] }

[0074] The recovery object identification information is used within the OCS operating system 402 to associate the state of the same optical path recovery process with the same recovery control state record. The phase deviation information indicates the direction and magnitude of the phase offset of the current received signal relative to the CDR-locked target; the unit can be expressed in picoseconds, the ratio of the time interval between two adjacent data decision moments, or local phase steps. The stage timing state and retry count information illustrate that the recovery control state record can be associated with and maintained for stage waiting and retry processes; its specific timing window, counting threshold, and retry strategy can be configured according to port rate, encoding method, protocol type, device implementation, or deployment strategy. This recovery control state is maintained locally by the OCS operating system 402 and is not considered an independent message on the control channel 503.

[0075] The correspondence between message types D1 to D5: In this embodiment, message type information can be used to distinguish different interaction stages in the same optical path reconstruction and optical link recovery process. D1 is optical path reconstruction control information, used by the network controller 101 to indicate the object to be reconstructed, target optical path requirements, related ports, and internal connectivity constraints to the OCS operating system 402 via control connection 202; D2 is port-side preset information, used to carry the optical link recovery configuration set; D3 is connection recovery trigger information, used to carry the optical link recovery trigger information and recovery adjustment information based on D4; D4 is status feedback information, used to carry the port-side recovery status and confirmation information; D5 is optical path reconstruction and recovery result information, used by the OCS operating system 402 to form the final result by combining the internal optical path status of the OCS and the port-side recovery status, and then write it back to the network controller 101 via control connection 202. The above classification of D1 to D5 is used to illustrate the functional relationship of information at different stages. For the optical link recovery collaborative control of the present invention, the control channel 503 mainly carries the information related to port-side recovery in D2, D3 and D4; D1 and D5 can interact with each other through the control connection 202 between the network controller 101 and the OCS operating system 402, and can also be used as associated inputs or result outputs of the recovery control status record inside the OCS operating system 402.

[0076] Data format of D1 to D5 interactive information:

[0077] D1: Optical Path Reconstruction Control Information: Used to associate the object to be reconstructed, the target optical path requirements, related ports, and internal connectivity constraints to the same optical path reconstruction and recovery process. Its exemplary JSON structure can be represented as:

[0078] {

[0079] "Message type information":"D1",

[0080] "Identifier information of the object to be reconfigured":"reconfig-object-001",

[0081] "Target optical path requirement information":"path-request-001",

[0082] "Related port identification information":[

[0083] "<First Electric Domain Side Port>",

[0084] "<Second electrical domain side port>"

[0085] ],

[0086] "Internal connectivity constraints": "Connected by the internal optical path of the OCS to both ports"

[0087] }

[0088] D2: Optical Link Recovery Configuration Set: This can be distributed as configuration content in the port-side preset information, used to describe target optical path association information, equalizer preset information, and service data access control information. Its exemplary JSON structure can be represented as:

[0089] {

[0090] "Message type information":"D2",

[0091] "Identifier information of the object to be reconfigured":"reconfig-object-001",

[0092] "Related port identification information":[

[0093] "<Electrical Domain Side Receive Direction Port>",

[0094] "<Corresponding OCS side port>"

[0095] ],

[0096] "Optical link recovery configuration set":{

[0097] "Target optical path association information":"path-oc-001",

[0098] "Equalizer preset information":{

[0099] "Preset Mode": "Historical Parameters Prioritized"

[0100] "Initial parameters":"eq_profile_a",

[0101] "Local training range":"range_1",

[0102] "Constraints":"link_profile_match"

[0103] },

[0104] "Business Data Release Control Information":{

[0105] "Release Criteria": "Equalizer convergence, CDR lock confirmation, and data boundary confirmation are all met."

[0106] "Data processing method during gating": "Maintain gating and discard business data directly".

[0107] "When to release gating": "Release gating immediately after the conditions for allowing business data to pass are met."

[0108] }

[0109] }

[0110] }

[0111] Among them, the business data release control information is used to characterize the conditions and control methods for maintaining or releasing business data gating. It may include the data processing method during gating and the timing of releasing gating, such as directly discarding business data during gating and releasing gating immediately after the release conditions are met. The relevant determination is still made by the electrical domain side control plane interface and processing unit 305 according to the local recovery completion determination rules.

[0112] The recovery process interaction information is used to carry the recovery trigger, status feedback, and recovery adjustment content after the target optical path is formed. Among them, the optical link recovery trigger information can be used as the content of the connection recovery trigger information (D3); the recovery status and confirmation information can be used as the content of the status feedback information (D4); the recovery adjustment information can be generated based on the feedback result of D4 and sent as the content of the connection recovery trigger information (D3).

[0113] D3: Recovery Trigger Information: Taking recovery trigger as an example, its exemplary JSON structure can be represented as:

[0114] {

[0115] "Message Type Information":"D3",

[0116] "Identifier information of the object to be reconfigured":"reconfig-object-001",

[0117] "Related port identification information":[

[0118] "<Electrical Domain Side Receive Direction Port>",

[0119] "<Corresponding OCS side port>"

[0120] ],

[0121] "Restore trigger information":{

[0122] "Target optical path association information":"path-oc-001",

[0123] Triggering condition: "Target optical path has been formed".

[0124] "Send clock phase auxiliary adjustment information":{

[0125] "Adjust direction": "Ahead of schedule",

[0126] "Phase Adjustment Threshold": "10% of the time interval between two adjacent data decision points",

[0127] "Phase step unit": "2% of the time interval between two adjacent data decision points",

[0128] "Adjust step size": 1,

[0129] Maximum number of adjustments: 3

[0130] },

[0131] "Initial state of business data gating": "Maintain gating",

[0132] "State feedback requirements": "Feedback should be sent after the phase state is formed."

[0133] }

[0134] }

[0135] D4: Recovery Status Postback Information: Taking the recovery status postback as an example, its exemplary JSON structure can be represented as follows:

[0136] {

[0137] "Message type information":"D4",

[0138] "Identifier information of the object to be reconfigured":"reconfig-object-001",

[0139] "Related port identification information":[

[0140] "<Electrical Domain Side Receive Direction Port>",

[0141] "<Corresponding OCS side port>"

[0142] ],

[0143] "Recovery Status and Confirmation Information":{

[0144] Equalizer convergence status: "Converged"

[0145] "CDR lock confirmation status": "Not satisfied"

[0146] "Phase deviation information":{

[0147] "Direction": "Lag"

[0148] "Amplitude": 12.5,

[0149] Dimensions: "ps"

[0150] },

[0151] "Data boundary confirmation status": "Unconfirmed"

[0152] "Business Data Gating Status": "Gating Maintained"

[0153] "Business data release condition determination result": "Not met"

[0154] "Stage timer status": "Preset waiting time has not exceeded",

[0155] "Retry count information": 1

[0156] },

[0157] "Reason for Stage Anomaly": "CDR lock confirmation not satisfied"

[0158] }

[0159] When the message type information is D3, the recovery process interaction information includes optical link recovery trigger information, which is used to trigger the receiving direction electrical domain side data plane interface 306 to enter the recovery process. In cases where subsequent recovery adjustments are made based on the D4 feedback result, the relevant adjustment content can also be incorporated into the corresponding field of D3 and sent. In some implementations, D3 may include transmit clock phase auxiliary adjustment information, used to indicate the adjustment direction, phase adjustment threshold, phase step unit, adjustment step size, and maximum number of adjustments.

[0160] When the message type information is D4, the recovery process interaction information includes recovery status and confirmation information, used to transmit equalizer convergence status, CDR lock confirmation status, phase deviation information, data boundary confirmation status, and business data gating status. In some implementations, the phase deviation information can use a directional numeric field or equivalent encoding to represent the direction and magnitude of the phase offset; D4 can also carry stage timing status, retry count information, recovery cancellation flag, or stage exception reason to support the OCS operating system 402 in determining whether to continue waiting, retry, adjust, cancel, or report recovery failure.

[0161] D5: Optical Path Reconstruction and Recovery Result Information: Used to combine the optical path status within the OCS, the port-side recovery status, and the service data release results into a final result, and write it back to the network controller 101. Its exemplary JSON structure can be represented as:

[0162] {

[0163] "Message Type Information":"D5",

[0164] "Identifier information of the object to be reconfigured":"reconfig-object-001",

[0165] "Target optical path association information":"path-oc-001",

[0166] "OCS Internal Optical Path Status": "Established"

[0167] "Port-side recovery status": "Completed"

[0168] "Business data release result": "Released"

[0169] "Optical path reconstruction and restoration result": "Successful"

[0170] }

[0171] The above JSON structure is only used to illustrate the field organization relationship and does not limit the specific field names, field order, field length, encoding method, serialization method, control message format or protocol implementation; the control information confirmation, retransmission and abnormal result formation methods can follow the existing control channel interaction mechanism.

[0172] Example 2: Establishment and Update of Control State Records

[0173] This embodiment illustrates how the OCS operating system 402 establishes, updates, and restores control state records around a single optical path reconstruction.

[0174] When an optical path reconfiguration request arrives, the OCS operating system 402 establishes a recovery control status record, using the target optical path corresponding to the reconfiguration and its two electrical domain endpoints as associated objects. This recovery control status record records the internal optical path status of the OCS, as well as the equalizer convergence status, CDR lock confirmation status, phase deviation information related to CDR lock confirmation, data boundary confirmation status, and service data gating status formed during the port-side recovery process. In implementations requiring maintenance of abnormal states, it can also record stage timing information, stage abnormality reasons, retry count information, recovery cancellation flag, or recovery failure flag. For cases where multiple optical path reconfiguration requests arrive concurrently, the OCS operating system 402 can establish corresponding recovery control status records based on the recovery object identification information, ensuring that each record is only associated with the recovery configuration preset, recovery status feedback, and service data release control of its respective target optical path.

[0175] The OCS operating system 402 obtains the internal optical path status or reconstruction results of the OCS through the OCS-side control plane interface and processing unit 405. The electrical domain-side control plane interface and processing unit 305 sends the port-side recovery status to the corresponding OCS-side control plane interface and processing unit 405 via the control channel 503, and the OCS-side control plane interface and processing unit 405 then sends it up to the OCS operating system 402 to collect and update the aforementioned recovery control status record. Thus, the internal optical path status of the OCS and the port-side recovery status of the electrical domain endpoints on both sides are included in the same recovery control status record, serving as the basis for subsequent recovery configuration presets, recovery triggers, service data release judgments, and recovery adjustments.

[0176] In some implementations, when service data has been released, the target optical path has been removed, optical path reconstruction has been canceled, or the recovery process has not been completed within a preset waiting time, the OCS operating system 402 can end and clear the corresponding recovery control status record. If, after the target optical path is formed and the optical link recovery trigger information has been sent, the OCS operating system 402 does not receive the recovery status feedback for the corresponding stage within a preset waiting time, or the received recovery statuses do not satisfy the serial recovery relationship defined by this invention, including the CDR lock confirmation status not being satisfied while the data boundary confirmation status has been returned as satisfied, or the service data release condition determination result still not being satisfied while the service data gating status has been returned as released, then it can be determined that the current recovery control status record does not correspond to the actual recovery progress on the port side.

[0177] In the above situations, the OCS operating system 402 can handle the situation according to the uncorresponding state type: when there is a lack of equalizer convergence state, CDR lock confirmation state, or data boundary confirmation state feedback, the trigger information of the light-emitting link is restored to the corresponding electrical domain side control plane interface and processing unit 305 to prompt the corresponding receiving direction electrical domain side data plane interface 306 to re-execute the current stage state confirmation and feedback result; when a stage abnormality reason is received or the conditions are not met in multiple feedbacks of the same stage, the OCS operating system 402 can issue recovery adjustment information, or continue to maintain service data gating and wait for the next state feedback.

[0178] If the same recovery target fails to achieve a satisfactory equalizer convergence state, CDR lock confirmation state, or data boundary confirmation state within a preset number of retries, the OCS operating system 402 can mark the corresponding recovery control state record as recovery incomplete or recovery failed, and maintain the service data gating state of the corresponding receiving direction electrical domain side data plane interface 306. The OCS operating system 402 can also clear the recovery configuration context, stage timing information, retry count information, and phase adjustment context associated with this recovery target. When it is necessary for the upper-layer control plane to perceive the recovery result and redetermine the optical path reconstruction strategy, the OCS operating system 402 can report the result of recovery incomplete, recovery failed, or target optical path unavailable to the network controller 101 via the control connection 202.

[0179] Example 3: Restoring configuration presets and equalizer restoration

[0180] This embodiment illustrates how, before or during the formation of the target optical path, a preset recovery configuration set is configured through the control channel 503, enabling the receiving direction electrical domain side data plane interface 306 to enter the equalizer recovery based on the preset configuration after subsequent recovery triggering.

[0181] When the target optical path has been determined or is about to be formed, the OCS operating system 402 generates an optical link recovery configuration set based on the target optical path and its link attributes. The link attributes may include at least one of the following: link length, fiber type, port type, or other parameters that characterize the transmission conditions of the target optical path. The configuration set includes at least target optical path association information and equalizer preset information, and may also include service data release control information. The equalizer preset information can be used to provide initial equalizer parameters corresponding to the target optical path, or to provide parameter ranges and constraints for local training; the parameter ranges and constraints for local training can be determined based on historical recovery results, deployment calibration results, reference parameters for similar links, or combinations thereof.

[0182] The OCS operating system 402 sends the configuration set to the electrical domain side control plane interface and processing unit 305 through the OCS-side control plane interface and processing unit 405 and the control channel 503. The electrical domain side control plane interface and processing unit 305 then writes or associates the configuration related to data plane execution to the receiving direction electrical domain side data plane interface 306 through the electrical domain side port internal control interaction path 308 to form a port-side recovery context corresponding to the target optical path.

[0183] After the target optical path is formed and the optical link recovery trigger information is received, the equalizer recovery function unit 701 in the receiving directional electrical domain side data plane interface 306 performs equalizer recovery based on the equalizer preset information. When there are historical parameters that match the target optical path, the historical parameters are loaded first and the status is confirmed. When there are no completely matching historical parameters but there are similar link reference parameters, local training is performed within a preset range. When the above parameters are insufficient to meet the convergence conditions, full equalizer training is then performed. After the equalizer converges, the interface enters the CDR lock confirmation stage.

[0184] Example 4: Recovery Trigger, Status Backhaul, and Service Data Release

[0185] This embodiment illustrates how, after the target optical path is formed, service data gating and release can be achieved through optical link recovery trigger information, recovery status feedback, and local determination.

[0186] After the target optical path is formed, the OCS operating system 402 sends optical link recovery trigger information through the OCS-side control plane interface and processing unit 405 and control channel 503 corresponding to the target port. The electrical domain-side control plane interface and processing unit 305 associates the trigger information with the preset recovery configuration, and triggers the receiving direction electrical domain-side data plane interface 306 to enter the recovery process through the internal control interaction path 308 of the electrical domain-side port.

[0187] The receiving direction electrical domain side data plane interface 306 executes port-side recovery confirmation sequentially: first, the equalizer recovery function unit 701 performs equalizer recovery and forms an equalizer convergence state; after the equalizer convergence state meets the conditions, the CDR lock confirmation function unit 702 performs CDR lock confirmation and forms a CDR lock confirmation state; after the CDR lock confirmation state meets the conditions, the data boundary confirmation function unit 703 performs data boundary confirmation and forms a data boundary confirmation state. The recovery states formed in the above stages are returned to the electrical domain side control plane interface and processing unit 305 via the electrical domain side port internal control interaction path 308.

[0188] The electrical domain-side control plane interface and processing unit 305 determines the equalizer convergence status, CDR lock confirmation status, and data boundary confirmation status based on the local recovery completion judgment rules. If all of the above statuses do not yet meet the service data release conditions, the electrical domain-side control plane interface and processing unit 305 uses the internal control interaction path 308 of the electrical domain-side port to maintain service data gating in the service data gating function unit 704, and directly discards service data arriving at the service data output path. Once all of the above statuses meet the service data release conditions, the service data gating function unit 704 immediately releases the service data gating, and a service data gating status and service data release condition judgment result are generated. After the gating is released, the service data can be further processed by the electrical domain communication entity 303 according to relevant communication protocols, such as Ethernet communication protocol, InfiniBand communication protocol, or other packet communication protocols for regular frame or message processing.

[0189] In this embodiment, the local recovery completion determination rule can be pre-configured in the electrical domain side control plane interface and processing unit 305. This rule includes equalizer convergence determination parameters, CDR lock determination parameters, and data boundary confirmation parameters. The equalizer convergence determination parameters include a first threshold and a first duration period. The first threshold limits the range that the equalizer training error metric, eye diagram quality index, equalizer tap coefficient change, or combinations thereof must satisfy. The first duration period limits the duration for which the above range is continuously maintained. The CDR lock determination parameters include a second threshold and a second duration period. The second threshold limits the range that the CDR phase deviation, frequency deviation, or combinations thereof must satisfy. The second duration period limits the duration for which the above range is continuously maintained. The data boundary confirmation parameters include the number of consecutive correct sync headers. After the CDR lock confirmation condition is met, the data boundary confirmation function unit 703 performs sync header detection on the physical coding sublayer. When the number of consecutively detected correct sync headers reaches the number of consecutive correct sync headers, the data boundary confirmation is determined to be satisfied. In coding methods using other boundary identifiers, the number of consecutive correct sync headers can be equivalently replaced by the number of consecutive correct boundary identifiers.

[0190] In a set of optional configurations, the first threshold can be set to the change in the equalizer tap coefficient between two consecutive updates not exceeding 1% to 2% of the full scale, or the equalizer training error metric being lower than the local calibration error threshold; the first duration can be set to 5 microseconds to 20 microseconds. The second threshold can be set to the CDR phase deviation not exceeding 5% to 10% of the time interval between two consecutive data decision times, or the frequency deviation being lower than 10^-6 to 10^-5 of the target line rate; the second duration can be set to 5 microseconds to 20 microseconds; the number of consecutive correct synchronization headers can be set to 32. The above values ​​are used to illustrate one implementable configuration of the local recovery completion judgment rule, and the actual values ​​can be determined according to the link rate, encoding method, transceiver capability, target error requirement, and service data release policy.

[0191] The recovery status and confirmation information that needs to be transmitted back to the OCS side are sent by the electrical domain side control plane interface and processing unit 305 to the corresponding OCS side control plane interface and processing unit 405 via control channel 503, and then sent by the OCS side control plane interface and processing unit 405 to the OCS operating system 402 for updating the recovery control status record. The recovery status and confirmation information may include equalizer convergence status, CDR lock confirmation status, data boundary confirmation status, service data gating status, service data release condition judgment result, and the corresponding stage abnormality reason.

[0192] Example 5: Phase Deviation Information-Driven Transmit Clock Phase-Assisted Adjustment

[0193] This embodiment is a further implementation of the recovery process described in Embodiment 4 when the CDR lock confirmation does not meet the conditions, and is used to illustrate how to use phase deviation information to trigger auxiliary adjustment of the transmission clock phase.

[0194] When the equalizer recovery function unit 701 confirms that the equalizer has converged, but the CDR lock confirmation function unit 702 fails to meet the CDR lock confirmation condition, the receiving direction electrical domain side data plane interface 306 generates phase deviation information based on the local recovery status during the CDR lock confirmation process. As an exemplary physical implementation, the transmitting direction port transmits a preset transition sequence during service data gating. The preset transition sequence is a non-service data pattern agreed upon by the port side, used to provide sufficient continuous transition edges for CDR phase detection; the specific code type is not limited. The receiving direction CDR samples this sequence, and the phase detection logic forms an early / late decision near each valid transition edge. If the early or late decision continues to dominate within a preset observation window, it indicates that there is a residual deviation in the same direction of the locally sampled phase relative to the input data edge. The loop control logic can organize the net bias vector of the early / late decision or the corresponding phase control quantity into a directional digital phase deviation field. For analog phase error signals, they can first be compared or converted from analog to digital to form a digital quantity, and then written into the phase deviation field. The dimensions of the field can be picoseconds, the ratio of the time interval between two adjacent data decision times, or the local phase step; its measurement accuracy can be determined by the CDR phase detection resolution, the observation window length, and the local calibration results. This phase deviation information is returned to the electrical domain side control plane interface and processing unit 305 via the internal control interaction path 308 of the electrical domain side port, and then transmitted back to the OCS operating system 402 via the control channel 503.

[0195] The OCS operating system 402 determines the transmission direction port corresponding to the receiving direction based on the target optical path context and the returned phase deviation information, and generates recovery adjustment information. In some implementations, when the equalizer convergence state is satisfied, the CDR lock confirmation state is not satisfied, and the effective phase deviation of the phase deviation information exceeds a preset phase adjustment threshold, auxiliary phase adjustment of the transmission clock is triggered. This threshold is used to avoid unnecessary adjustments triggered by instantaneous jitter or quantization errors; the adjustment step size can be mapped to one or more local phase steps according to the phase deviation amplitude, or a preset fixed step size can be used. The adjustment direction moves the edges of subsequent transmitted data towards the sampling stability interval of the receiving direction CDR. If the CDR lock confirmation condition is still not met after reaching the maximum number of adjustments, the OCS operating system 402 can mark the recovery control state as recovery incomplete or recovery failed.

[0196] In one set of optional configurations, the preset phase adjustment threshold can be configured such that the effective phase deviation corresponding to the phase deviation information exceeds 10% to 15% of the time interval between two adjacent data decision moments. The phase step unit can be determined by the minimum controllable phase change of the phase interpolator, controllable delay line, phase-locked loop phase selection circuit, or equivalent phase selection circuit in the data plane interface on the transmitting direction electrical domain side, and can be configured to be 2% to 5% of the time interval between two adjacent data decision moments. The adjustment step size can be configured to 1 to 3 phase step units; when the phase deviation is close to the preset phase adjustment threshold, 1 phase step unit is used for adjustment, and when the phase deviation is large, 2 to 3 phase step units are used for adjustment. The maximum number of adjustments can be configured to 3 to 6 times. The above parameters are used to describe one implementable configuration for auxiliary adjustment of the transmitting clock phase. The actual values ​​can be determined according to the link rate, the phase adjustment accuracy of the transmitting direction port, the CDR phase detection resolution, the target bit error rate requirement, and the service data release strategy.

[0197] The recovery adjustment information can be used as the corresponding content of the subsequent connection recovery trigger information (D3), and is sent to the transmission direction electrical domain side control plane interface and processing unit 305 via the corresponding OCS side control plane interface and processing unit 405 and control channel 503. As an exemplary physical implementation, the transmission direction electrical domain side control plane interface and processing unit 305 writes the adjustment direction, phase step unit, adjustment step size, and maximum number of adjustments into the phase adjustment control register of the transmission direction port. The transmission direction electrical domain side data plane interface adjusts the transmission clock phase selection or phase interpolation control word accordingly, so that the data edge of the subsequent preset transition sequence is advanced or delayed by one or more discrete phase steps relative to the original transmission clock. This adjustment can be implemented by a local phase interpolator, controllable delay line, phase-locked loop phase selection, or equivalent circuit.

[0198] To avoid impacting other services, the transmit clock phase auxiliary adjustment is associated with the target optical path, transmit direction port, and corresponding service object. For implementations that support independent adjustment by port, channel, or transmit lane, the adjustment only applies to the corresponding recovery object. For implementations where transmit clock resources are shared by multiple services and the impact of the adjustment cannot be isolated, this adjustment may not be performed, or it may only be performed when the relevant service is paused, gated, drained, or in a preset transition sequence transmission window.

[0199] After the adjustment is completed, the CDR lock confirmation function unit 702 in the receiving direction electrical domain side data plane interface 306 continues to perform CDR lock confirmation; after the CDR lock confirmation meets the conditions, the data boundary confirmation function unit 703 performs data boundary confirmation. If the CDR lock confirmation still does not meet the conditions, the receiving direction electrical domain side data plane interface 306 can continue to generate updated recovery status and confirmation information, and transmit them back to the OCS operating system 402 via the control channel 503 to support subsequent recovery adjustments.

[0200] Example 6: Supplementary Explanation of State Collection in Abnormal and Bidirectional Scenarios

[0201] This embodiment is used to further illustrate how the recovery control status record can maintain the status aggregation relationship when the recovery is incomplete, the recovery is cancelled, or the bidirectional optical path needs to form an overall availability confirmation.

[0202] In some implementations, if equalizer recovery, CDR lock confirmation, or data boundary confirmation still fails to reach a stage state that meets the conditions under local preset conditions, the electrical domain side control plane interface and processing unit 305 can transmit the stage incomplete identifier, stage anomaly cause, stage timing status, or retry count information as part of the recovery status and confirmation information to the OCS operating system 402 via the control channel 503. The local preset conditions can be a timing window, a counting window, a status return count limit, a retry count threshold, or a combination thereof, and can be configured according to port rate, encoding method, protocol type, device implementation, or deployment strategy.

[0203] After receiving the above information, the OCS operating system 402 can decide whether to continue waiting, re-issue optical link recovery trigger information, issue recovery adjustment information, maintain service data gating, end the current recovery control state record, or report the recovery incomplete or failed result to the network controller 101 via the control connection 202. If a new optical path reconstruction request is received during the recovery process, the OCS operating system 402 can choose to continue the current recovery process, cancel the current recovery process, or queue the new optical path reconstruction request according to the target optical path priority, the current recovery stage, or the service strategy. When canceling the current recovery process, the corresponding electrical domain side control plane interface and processing unit 305 can be notified through the control channel 503 to maintain service data gating and clear the port-side recovery context associated with the current recovery object.

[0204] For bidirectional optical paths, the recovery processes in the first and second directions are independent of each other. Both can perform equalizer recovery, CDR lock confirmation, data boundary confirmation, and service data release at their respective receiving direction's electrical domain side data plane interface. There is no necessary sequential order where one direction's recovery must be completed before the other begins recovery. The OCS operating system 402 can record the recovery status of the first and second directions separately in the same recovery control status record and receive the recovery status and confirmation information transmitted back from both directions via the control channel 503. Bidirectional services can form an overall availability confirmation after both directions meet the service data release conditions, based on service requirements. In scenarios where unidirectional independent recovery is allowed, service data release results can also be formed separately for each direction. This bidirectional state coordination is reflected in the OCS operating system 402's state aggregation and availability confirmation of the two independent recovery processes, without requiring the recovery status of one direction to control the recovery initiation timing of the other direction.

[0205] Comparative example: Optical link recovery method without preset recovery configuration and recovery status backhaul.

[0206] To illustrate the impact of this invention on the additional waiting time between the formation of the target optical path and the release of service data, a comparative example is provided below. This comparative example is only used to illustrate a typical recovery process when the optical link recovery cooperative control method described in this invention is not employed, and does not limit all implementation methods of the prior art.

[0207] In this comparative example, the OCS device 401 can still form a target optical path through the optical switching matrix 403. However, before or during the formation of the target optical path, the OCS operating system 402 does not pre-set the optical link recovery configuration set corresponding to the target optical path to the electrical domain side control plane interface and processing unit 305 through the control channel 503, nor does it establish a recovery control status record around the target optical path for collecting the internal optical path status and port-side recovery status of the OCS. After the target optical path is formed, the receiving direction electrical domain side data plane interface 306 usually performs equalizer recovery based on default parameters, a complete training process, or a local re-search process. The equalizer convergence status, CDR lock confirmation status, data boundary confirmation status, and service data release condition judgment results are mainly formed on the electrical domain device side and reported and confirmed step by step through the conventional control path. When the CDR lock confirmation condition is not met, the phase deviation information formed in the receiving direction is difficult to be coordinated to the corresponding transmitting direction port through the control channel 503 in a timely manner as recovery adjustment information. Therefore, business data release usually requires waiting for the equalizer to complete training, CDR lock confirmation, data boundary confirmation, and cross-control entity state aggregation to be completed before proceeding.

[0208] For ease of analysis, the additional waiting time between the formation of the target optical path and the release of business data can be divided into the following equivalent time components. These time components are used for functional decomposition and do not require the corresponding processes in the comparative examples to have the same name or message type; the suffix 'a' indicates the time component in the comparative example, and the suffix 'b' indicates the time component in the embodiment of this invention.

[0209] Time component meaning Comparison Tp Preset time for optical link recovery configuration in the embodiments of the present invention Tp can be executed before or during the formation of the target optical path; only the portion of Tp that occurs after the formation of the target optical path is counted as additional waiting time. Teq_a / Teq_b Equalizer recovery time This invention reduces the waiting time caused by equalizer re-searching or full training by using equalizer preset information, historical parameters, or local training range. Tcdr_a / Tcdr_b CDR lock confirmation time This invention can trigger auxiliary adjustment of the transmit clock phase based on phase deviation information when the equalizer has converged but the CDR lock confirmation condition has not been met. Tba_a / Tba_b Data boundary confirmation time This invention does not require shortening the data boundary confirmation itself as a necessary condition, but it ensures that the recovery process continues after the CDR lock confirmation meets the conditions. Tg_a / Tg_b Release determination and status feedback time This invention does not require shortening this time component as a necessary condition; the recovery status and confirmation information are transmitted back via the control channel to update the recovery control status record.

[0210] Table 1: Equivalent Time Components and Comparisons from Target Optical Path Formation to Service Data Release

[0211] In this invention, the optical link recovery configuration set can be sent in advance as port-side preset information (D2), and the optical link recovery trigger information can be used as connection recovery trigger information (D3) to trigger the receiving direction electrical domain side data plane interface 306, which already has a recovery context, to perform equalizer recovery, CDR lock confirmation, and data boundary confirmation. The recovery status and confirmation information can be used as status feedback information (D4) to be sent back to the corresponding OCS side control plane interface and processing unit 405 via the control channel 503, and then sent up to the OCS operating system 402 by the OCS side control plane interface and processing unit 405.

[0212] Based on the above equivalent decomposition, if TA represents the additional waiting time in the comparative example from the formation of the target optical path to the release of service data, then:

[0213] TA = Teq_a + Tcdr_a + Tbd_a + Tg_a

[0214] In this invention, Tp can be advanced before or during the formation of the target optical path. If Tpath represents the time required for the formation of the target optical path, then the effect of the preset process on the additional waiting time after the formation of the target optical path can be expressed as:

[0215] ΔTp=max(0,Tp-Tpath)

[0216] Where ΔTp represents the portion of the optical link recovery configuration preset that is later than the formation of the target optical path; when the optical link recovery configuration preset is no later than the completion of the formation of the target optical path, ΔTp is zero. If TB represents the additional waiting time from the formation of the target optical path to the release of service data in the embodiment of the present invention, then:

[0217] TB=ΔTp+Teq_b+Tcdr_b+Tbd_b+Tg_b

[0218] The difference between the two can be expressed as:

[0219] TA-TB=(Teq_a-Teq_b)+(Tcdr_a-Tcdr_b)+(Tbd_a-Tbd_b)+(Tg_a-Tg_b)-ΔTp

[0220] The above comparison shows that the present invention mainly reduces the additional waiting time between the formation of the target optical path and the release of service data by restoring the configuration and shifting the equalizer context preset forward, and by performing recovery adjustments based on phase deviation information when the CDR lock confirmation condition is not met. The above comparison is only used to illustrate the compression mechanism of additional waiting time; the specific time depends on the port rate, transceiver recovery mechanism, equalizer training method, CDR lock condition, control channel protocol, and confirmation retransmission strategy.

[0221] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

[0222] The preferred embodiments of the present invention disclosed above are merely illustrative of the invention. These preferred embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the content of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the invention, thereby enabling those skilled in the art to better understand and utilize the invention. The invention is limited only by the claims and their full scope and equivalents.

Claims

1. A hybrid optoelectronic network (OCS) link recovery control architecture based on out-of-band channels, characterized in that, include: OCS equipment includes the OCS operating system, optical switching matrix, OCS-side transceiver, and OCS-side control plane interface and processing unit; Electrical domain equipment includes an electrical domain-side transceiver, an electrical domain-side control plane interface and processing unit, and an electrical domain-side data plane interface; The external optical fiber includes a separate control channel and a data channel, wherein the control channel connects the OCS-side control plane interface and processing unit and the electrical domain-side control plane interface and processing unit. The OCS operating system is a recovery control status record corresponding to an optical path reconstruction maintenance. The recovery control status record includes at least the internal optical path status of the OCS, the equalizer convergence status, the CDR lock confirmation status, the phase deviation information, the data boundary confirmation status, and the service data gating status. The electrical domain side data plane interface includes an equalizer recovery function unit, a CDR lock confirmation function unit, a data boundary confirmation function unit, and a service data gating function unit. The OCS operating system sends a preset optical link recovery configuration set to the electrical domain side through the control channel, sends recovery trigger information after the target optical path is formed, receives and processes the recovery status information returned by the electrical domain side, and generates and sends recovery adjustment information.

2. The OCS link recovery control architecture based on out-of-band channels in a hybrid optoelectronic network according to claim 1, characterized in that, The optical link recovery configuration set includes at least equalizer preset information, which is used to provide the equalizer recovery function unit with the initial parameters or local training parameter range corresponding to the target optical path. The optical link recovery configuration set is generated based on the link attributes of the target optical path, and the link attributes include at least one of link length, fiber type and port type.

3. The OCS link recovery control architecture based on out-of-band channels in a hybrid optoelectronic network according to claim 1, characterized in that, The recovery control state record is established when the optical path reconstruction request arrives. The OCS operating system maintains multiple recovery control state records for optical path reconstruction based on the recovery object identification information to avoid state confusion between different recovery processes.

4. The OCS link recovery control architecture based on out-of-band channels in a hybrid optoelectronic network according to claim 1, characterized in that, The OCS operating system receives recovery status and confirmation information from the electrical domain side via the control channel. The recovery status and confirmation information includes equalizer convergence status, CDR lock confirmation status, phase deviation information, data boundary confirmation status, and service data gating status.

5. The OCS link recovery control architecture based on out-of-band channels in a hybrid optoelectronic network according to claim 1, characterized in that, The equalizer recovery function unit is used to perform equalizer preset, equalizer local training, or equalizer recovery confirmation; the CDR lock confirmation function unit is used to perform CDR lock confirmation and generate phase deviation information after the equalizer recovery meets the conditions; the data boundary confirmation function unit is used to perform word boundary, block boundary, or frame boundary confirmation after the CDR lock confirmation meets the conditions; the service data gating function unit is used to maintain service data gating before the recovery state meets the service data release conditions, and to perform service data release after the release conditions are met.

6. The OCS link recovery control architecture based on out-of-band channels in a hybrid optoelectronic network according to claim 1, characterized in that, When the equalizer has converged but the CDR lock confirmation condition is not met and the returned phase deviation information exceeds the preset threshold, the OCS operating system generates recovery adjustment information and instructs the data plane interface on the electrical domain side of the transmission direction to perform auxiliary adjustment of the transmission clock phase.

7. The OCS link recovery control architecture based on out-of-band channels in a hybrid optoelectronic network according to claim 6, characterized in that, The auxiliary adjustment of the transmit clock phase is achieved by writing the adjustment direction, phase step unit, adjustment step size and maximum number of adjustments into the phase adjustment control register of the transmit direction port. The adjustment step size is mapped to one or more local phase steps according to the phase deviation amplitude.

8. The OCS link recovery control architecture based on out-of-band channels in a hybrid optoelectronic network according to claim 1, characterized in that, The electrical domain side control plane interface and processing unit save local recovery completion judgment rules, which include: equalizer convergence is determined when the equalizer training error metric is lower than a first threshold within a first duration period; CDR lock confirmation is determined when the CDR phase deviation is lower than a second threshold within a second duration period; and data boundary confirmation is determined when the physical coding sublayer continuously detects a preset number of correct synchronization headers.

9. The OCS link recovery control architecture based on out-of-band channels in a hybrid optoelectronic network according to claim 1, characterized in that, The service data gating function unit is located on the service data output path of the receiving direction electrical domain side data plane interface, and is located before the service data output position after the data boundary confirmation is completed. It is used to perform output blocking control on the service data output path before the service data release conditions are met.

10. The OCS link recovery control architecture based on out-of-band channels in a hybrid optoelectronic network according to claim 1, characterized in that, For bidirectional optical paths, the OCS operating system records the recovery status in both directions in the same recovery control status record. Bidirectional services can form an overall availability confirmation after the service data release conditions are met in both directions according to service requirements.

Images