Fault recovery method and related equipment

Abstract

The embodiment of the invention provides a fault recovery method and related equipment, and relates to the field of communication. In the method, a first node sends first information to a controller. The first information is used for indicating that a first sub-path in the ASON breaks down, and a first working path in the ASON passes through the first sub-path. And in addition, the first node sends first information to each node on a first fault recovery path corresponding to the first working path, so that each node recovers cross configuration based on the first information and a first corresponding relationship corresponding to the node. The first corresponding relation is used for indicating the corresponding relation between the fault sub-path, the service corresponding to the working path and the recovery cross indication information. According to the scheme, fault recovery is directly started in the fault notification process, the time required for message notification during fault recovery can be shortened, and the fault recovery performance is effectively improved.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of communications, and in particular, to a fault recovery method and related devices. Background Art

[0002] With the large-scale construction of data centers, reliable interconnection between data centers is required to ensure uninterrupted data transmission between data centers.

[0003] In a traditional optical transport network (OTN), a control plane is introduced to form an automatically switched optical network (ASON) to achieve automatic route setting, end-to-end service scheduling, network automatic recovery, etc. As Figure 1A shown, ASON 101 is introduced into the data center interconnection network to achieve interconnection between data centers. Figure 1A In, data centers are taken as an example of data center 1, data center 2, and data center 3. When a fault occurs at a certain position in ASON 101, ASON 101 can perform fault recovery. This fault recovery solution can reduce the number of optical cables required for data center interconnection. However, when ASON performs fault recovery, there is a problem of high message notification time consumption, resulting in low fault recovery performance. Summary of the Invention

[0004] The present application provides a fault recovery method and related devices, which can improve fault recovery performance.

[0005] In a first aspect, a fault recovery method is provided. This method can be executed by a first node in an automatically switched optical network (ASON), or by a chip in the first node. The above ASON further includes a controller.

[0006] The above fault recovery method includes the following steps: sending first information to the controller. The above first information is used to indicate that a first sub-path in the ASON has failed, and a first working path in the ASON passes through the first sub-path. The first working path can be one or more. Sending the first information to each node on the first fault recovery path corresponding to the first working path, so that each node performs recovery cross-configuration based on the first information and the first corresponding relationship corresponding to the node. The above first corresponding relationship is used to indicate the corresponding relationship between the faulty sub-path, the service corresponding to the working path, and the recovery cross-indication information. The above recovery cross is used to restore the connectivity of the service from a faulty or blocked state.

[0007] In this solution, the first node sends the first information to the controller to inform the controller that a failure has occurred in the first sub-path, and the first node sends the first information to each node on the first fault recovery path corresponding to the first working path, so that each node performs recovery cross-configuration based on the first information and the first corresponding relationship corresponding to the node (referring to the node on the first fault recovery path). That is, in this solution, the fault recovery is directly started during the fault notification process, which can reduce the time required for message notification during fault recovery and effectively improve the fault recovery performance.

[0008] In a possible implementation manner of the first aspect, the above-mentioned sending the first information to each node on the first fault recovery path corresponding to the first working path specifically includes the following steps: sending the first information to each node in the ASON, and each node in the ASON includes each node on the first fault recovery path.

[0009] In this solution, when the first node sends the first information to each node on the first fault recovery path, it can send the first information to each node in the ASON. This can not only enable each node on the first fault recovery path to obtain the first information, but also enable the nodes in the ASON other than the nodes on the first fault recovery path to obtain the first information, and can timely know the change of the topological state information of the ASON.

[0010] In a possible implementation manner of the first aspect, the above-mentioned sending the first information to each node in the ASON specifically includes the following steps: sending the first information to the first neighbor nodes of the first node, so that each first neighbor node sends the first information to the neighbor nodes of the first neighbor node.

[0011] In this solution, the first node can send the first information to each node in the ASON based on the neighbor extension mode, which can not only improve the transmission performance of the first information, but also ensure that each node on the first fault recovery path obtains the first information.

[0012] In a possible implementation manner of the first aspect, the above-mentioned sending the first information to each node on the first fault recovery path corresponding to the first working path specifically includes the following steps: sending the first information to the second node on the first fault recovery path based on the fault notification path, and the fault notification path is related to the first node and the second node.

[0013] In this solution, when the first node sends the first information to the second node on the first fault recovery path, the first node can send the first information to the second node through the fault notification path (i.e., the specified notification path) between the first node and the second node. By notifying the first information through the specified path, detours or transmission failures can be avoided, and the most suitable path can be selected to send the first information to the second node, improving the transmission performance of the first information.

[0014] In a possible implementation manner of the first aspect, the above-mentioned fault recovery method further includes the following steps: receiving a fault notification path corresponding to a second node sent by a controller.

[0015] In this solution, the controller designates a fault notification path for the first node and the second node, and the controller sends the fault notification path to the first node. In this way, an optimal or most suitable path can be determined between the first node and the second node, improving the information transmission performance between the first node and the second node. In addition, by designating a path by the controller, network traffic and load can be better managed. The controller can disperse the traffic to different paths to avoid overloading of certain paths, thereby achieving load balancing of the network.

[0016] In a second aspect, the present application further provides a fault recovery method, which can be executed by a controller in an automatically switched optical network (ASON), or by a chip in the controller. The above-mentioned ASON further includes a first node.

[0017] The above-mentioned fault recovery method includes the following steps: receiving first information sent by the first node. The above-mentioned first information is used to indicate that a first sub-path in the ASON fails, and a first working path in the ASON passes through the first sub-path. Receiving second information sent by a node on a first fault recovery path, the first fault recovery path corresponding to the first working path. The above-mentioned second information is used to indicate that the node on the first fault recovery path has completed a recovery cross-configuration based on the first information and a first corresponding relationship corresponding to the node. The above-mentioned first corresponding relationship is used to indicate the corresponding relationship between the fault sub-path, the service corresponding to the working path, and the recovery cross-indication information.

[0018] In this solution, the controller receives the first information sent by the first node to know that the first sub-path fails, and the nodes on the first fault recovery path corresponding to the first working path perform a recovery cross-configuration based on the first information and the first corresponding relationship corresponding to the node. The nodes on the first fault recovery path send the second information to the controller to inform the controller of the result of their own recovery cross-configuration. The controller can determine the fault recovery result based on the first information and the second information, that is, the recovery result of the service corresponding to the first working path. It can be seen that this solution directly starts fault recovery during the fault notification process, which can reduce the time required for message notification during fault recovery and effectively improve the fault recovery performance.

[0019] In a possible implementation manner of the second aspect, the above-mentioned fault recovery method further includes the following steps: Based on the topology state information of ASON and the working paths in ASON, determine the fault recovery paths corresponding to each sub-path in the working path during a fault. Based on the fault recovery paths corresponding to each sub-path in the working path, determine the first corresponding relationship for each node on the fault recovery path. Send the first corresponding relationship corresponding to each node to each node on the fault recovery path.

[0020] In this solution, the controller determines the fault recovery paths and the first corresponding relationship for each node, which can simplify the requirements for the device capabilities of the nodes. The first node only needs to be responsible for transmitting the first information, and the nodes on the fault recovery path only need to start the local recovery cross-configuration based on the first information and transmit the results of the recovery cross-configuration, then the fault recovery can be achieved.

[0021] In a possible implementation manner of the second aspect, the above-mentioned fault recovery method further includes the following steps: When receiving the second information sent by all the nodes on the first fault recovery path, use the first fault recovery path as the new working path in ASON.

[0022] In this solution, the controller can determine the fault recovery result based on the first information and the second information. When receiving the second information sent by all the nodes on the first fault recovery path, it can be determined that the end-to-end recovery configuration of the first fault recovery path has been completed, that is, the service recovery corresponding to the first working path is completed, and the first fault recovery path can be used as the new working path corresponding to the service.

[0023] In a possible implementation manner of the second aspect, the above-mentioned fault recovery method further includes the following steps: ASON further includes a second node, and the above-mentioned fault recovery method further includes the following steps: Based on the first node and the second node, determine the fault notification path corresponding to the second node, and the nodes on the first fault recovery path include the second node. Send the fault notification path corresponding to the second node to the first node.

[0024] In this solution, the controller designates the fault notification path for the first node and the second node, and the controller sends the fault notification path to the first node. In this way, an optimal or most suitable path can be determined between the first node and the second node, improving the information transmission performance between the first node and the second node. In addition, by designating the path by the controller, the network traffic and load can be better managed. The controller can distribute the traffic to different paths to avoid overloading of certain paths, thus achieving load balancing of the network.

[0025] In a possible implementation of the second aspect, the above-mentioned fault recovery method further includes the following steps: when the ASON adds a new working path, update the working paths in the ASON. Based on the topological state information of the ASON and the updated working paths, re-determine the new fault recovery paths corresponding to each sub-path in the updated working paths in case of a fault. Based on the new fault recovery paths, determine the new first correspondences corresponding to each node on the new fault recovery paths.

[0026] In this solution, when a new working path is added to the ASON, the controller needs to update the working paths in the ASON, and update the fault recovery paths and the first correspondences according to the updated working paths and the topological state information of the ASON; so that the fault recovery paths and the first correspondences can be updated in a timely manner following the latest state of the ASON, ensuring the reliability and stability of the service, and enabling the ASON to operate stably.

[0027] In a possible implementation of the second aspect, the above-mentioned fault recovery method further includes the following steps: when the first working path returns to normal, update the working paths in the ASON, and update the topological state information of the ASON. Based on the updated topological state information of the ASON and the updated working paths, re-determine the new fault recovery paths corresponding to each sub-path in the updated working paths in case of a fault. Based on the new fault recovery paths, determine the new first correspondences corresponding to each node on the new fault recovery paths.

[0028] In this solution, when the first working path returns to normal, the controller needs to update the working paths in the ASON and update the topological state information of the ASON, and update the fault recovery paths and the first correspondences according to the updated working paths and the updated topological state information; so that the fault recovery paths and the first correspondences can be updated in a timely manner following the latest state of the ASON, ensuring the reliability and stability of the service, and enabling the ASON to operate stably.

[0029] In a possible implementation of the second aspect, the above-mentioned fault recovery method further includes the following steps: when the second sub-path in the fault recovery path in the ASON fails, update the topological state information of the ASON. Based on the updated topological state information of the ASON and the working paths in the ASON, re-determine the new fault recovery paths corresponding to each sub-path in each working path in case of a fault. Based on the new fault recovery paths, determine the new first correspondences corresponding to each node on the new fault recovery paths.

[0030] In this solution, when a failure occurs in the second sub-path of the fault recovery path, that is, the failure does not affect the working path. At this time, it is necessary to update the topological state information of the ASON, and update the fault recovery path and the first corresponding relationship based on the updated topological state information; it can cope with network changes, ensure the service continuity of the ASON, and improve the reliability of the ASON.

[0031] In a possible implementation manner of the second aspect, the above fault recovery method further includes the following steps: when the working path in the ASON is updated and a failure occurs in the second sub-path of the fault recovery path in the ASON, update the topological state information of the ASON. Based on the updated topological state information of the ASON and the updated working path, re-determine the new fault recovery path corresponding to each sub-path in the updated working path when a failure occurs. Determine the new first corresponding relationship corresponding to each node on the new fault recovery path based on the new fault recovery path.

[0032] In this solution, when the working path in the ASON is updated and a failure occurs in the second sub-path of the fault recovery path, it is necessary to update the topological state information of the ASON, and update the fault recovery path and the first corresponding relationship based on the updated topological state information and the updated working path; to cope with network changes, ensure the service continuity of the ASON, and improve the reliability of the ASON.

[0033] In the third aspect, the present application further provides a fault recovery method, which can be executed by a second node in an automatically switched optical network (ASON), or by a chip in the second node. The above ASON further includes a first node.

[0034] The above fault recovery method includes the following steps: receiving the first information sent by the first node. The above first information is used to indicate that a failure occurs in the first sub-path in the ASON. The first working path in the ASON passes through the first sub-path. The second node is a node on the first fault recovery path corresponding to the first working path. Perform a recovery cross configuration based on the first information and the first corresponding relationship corresponding to the second node. The above first corresponding relationship is used to indicate the corresponding relationship between the fault sub-path, the service corresponding to the working path, and the recovery cross indication information.

[0035] In this solution, the second node receives the first information sent by the first node and performs a recovery cross configuration based on the first information and the first corresponding relationship corresponding to the node. That is, in this solution, the fault recovery is directly started during the fault notification process, which can reduce the time required for message notification during fault recovery and effectively improve the fault recovery performance.

[0036] In a possible implementation manner of the third aspect, receiving the first information sent by the first node specifically includes the following steps: receiving the first information sent by a neighbor node of the second node, where the neighbor node obtains the first information from the first node.

[0037] In this solution, the first node may send the first information to its neighbor nodes based on the neighbor diffusion mode, and the neighbor nodes send the first information to the second node; this can improve the transmission performance of the first information.

[0038] In a possible implementation manner of the third aspect, receiving the first information sent by the first node specifically includes the following steps: receiving the first information sent by the first node through a fault notification path, where the fault notification path is related to the first node and the second node.

[0039] In this solution, when the first node sends the first information to the second node on the first fault recovery path, the first node may send the first information to the second node through the fault notification path (i.e., the specified notification path) between the first node and the second node. By notifying the first information through the specified path, this can avoid detours or unnecessary transmissions, and the most appropriate path can be selected to send the first information to the second node, improving the transmission performance of the first information.

[0040] In a possible implementation manner of the third aspect, the above ASON further includes a controller, and the above fault recovery method further includes the following steps: receiving the first corresponding relationship corresponding to the second node sent by the controller.

[0041] In this solution, the controller determines the fault recovery path and the first corresponding relationship corresponding to each node, which can simplify the equipment capability requirements for the nodes. The first node only needs to be responsible for transmitting the first information, and the second node only needs to start the local recovery cross-configuration based on the first information and transmit the result of the recovery cross-configuration to achieve fault recovery.

[0042] In a possible implementation manner of the third aspect, the above ASON further includes a controller, and the above fault recovery method further includes the following steps: sending a second information to the controller. The second information is used to indicate that the second node has completed the recovery cross-configuration based on the first information and the first corresponding relationship corresponding to the second node.

[0043] In this solution, after the second node completes the recovery cross-configuration based on the first information and the first corresponding relationship corresponding to the second node, the second node sends the second information to the controller so that the controller can know the result of the recovery cross-configuration of the second node.

[0044] Fourth aspect, the present application further provides a fault recovery method, which is applied to an automatically switched optical network (ASON). The above ASON includes a controller, a first node, and a second node.

[0045] The above-mentioned fault recovery method includes the following steps: The first node sends a first message to the controller. The above-mentioned first message is used to indicate that a fault has occurred in the first sub-path in the ASON, and the first working path in the ASON passes through the first sub-path. The controller receives the first message sent by the first node. The first node sends the first message to the second node. The second node is a node on the first fault recovery path corresponding to the first working path. The second node performs a restoration cross-configuration based on the first message and the first corresponding relationship corresponding to the second node. The above-mentioned first corresponding relationship is used to indicate the corresponding relationship between the faulty sub-path, the service corresponding to the working path, and the restoration cross-indication information. The second node sends a second message to the controller. The above-mentioned second message is used to indicate that the second node has completed the restoration cross-configuration based on the first message and the first corresponding relationship corresponding to the second node. The controller receives the second message sent by the second node.

[0046] In this solution, the first node sends a first message to the controller to inform the controller that a fault has occurred in the first sub-path, and the first node sends the first message to the second node so that the second node performs a restoration cross-configuration based on the first message and the first corresponding relationship corresponding to the node.

[0047] After the second node completes the restoration cross-configuration, it sends a second message to the controller to inform the controller of the result of its own restoration cross-configuration. This solution directly starts fault recovery during the fault notification process, which can reduce the time required for message notification during fault recovery and effectively improve the fault recovery performance.

[0048] Furthermore, the controller can determine the fault recovery result based on the first message and the second message, that is, the recovery result of the service corresponding to the first working path.

[0049] In a fifth aspect, the present application also provides a first node, which includes units or modules for executing the fault recovery method described in the first aspect.

[0050] In a sixth aspect, the present application also provides a controller, which includes units or modules for executing the fault recovery method described in the second aspect.

[0051] In a seventh aspect, the present application also provides a second node, which includes units or modules for executing the fault recovery method described in the third aspect.

[0052] In an eighth aspect, the present application also provides a fault recovery system, which includes a first node, a controller, and a second node. The first node is used to execute the fault recovery method described in the first aspect, the controller is used to execute the fault recovery method described in the second aspect, and the second node is used to execute the fault recovery method described in the third aspect.

[0053] In a ninth aspect, the present application further provides a communication device, including a processor and a memory. The processor is connected to the memory. The memory is used to store program code, and the processor is used to call the program code to execute the fault recovery method described in any one of the first aspect to the fourth aspect.

[0054] In a tenth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the fault recovery method described in any one of the first aspect to the fourth aspect.

[0055] In an eleventh aspect, the present application further provides a computer program product including instructions. When the computer program product runs on a computer, the computer is caused to execute the fault recovery method described in any one of the first aspect to the fourth aspect.

[0056] In a twelfth aspect, the present application further provides a chip. The chip includes a processor and a data interface. The processor reads instructions stored on a memory through the data interface and executes the fault recovery method described in any one of the first aspect to the fourth aspect.

[0057] Optionally, as an implementation, the chip may further include a memory. Instructions are stored in the memory, and the processor is used to execute the instructions stored on the memory. When the instructions are executed, the processor is used to execute the fault recovery method described in any one of the first aspect to the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] The following introduces the drawings used in the embodiments of the present application.

[0059] Figure 1A A schematic diagram of data center interconnection based on ASON provided for an embodiment of the present application;

[0060] Figure 1B A schematic diagram of data center interconnection based on OLP provided for an embodiment of the present application;

[0061] Figure 1C A schematic flowchart of a fault notification provided for an embodiment of the present application;

[0062] Figure 1D A schematic diagram of the architecture of ASON provided for an embodiment of the present application;

[0063] Figure 2 A schematic flowchart of a fault recovery method provided for an embodiment of the present application;

[0064] Figure 3AFlow diagram of another fault recovery method provided by an embodiment of the present application;

[0065] Figure 3B Interaction flow diagram of a fault recovery method provided by an embodiment of the present application;

[0066] Figure 3C Schematic diagram of a fault recovery method provided by an embodiment of the present application;

[0067] Figure 3D Schematic diagram of a method for sending a first message provided by an embodiment of the present application;

[0068] Figure 3E Schematic diagram of another method for sending a first message provided by an embodiment of the present application;

[0069] Figure 3F Schematic diagram of another method for sending a first message provided by an embodiment of the present application;

[0070] Figure 4 Schematic diagram of the structure of a first node provided by an embodiment of the present application;

[0071] Figure 5 Schematic diagram of the structure of a controller provided by an embodiment of the present application;

[0072] Figure 6 Schematic diagram of the structure of a second node provided by an embodiment of the present application;

[0073] Figure 7 Schematic diagram of the structure of a communication device provided by an embodiment of the present application. Detailed implementation manners

[0074] Next, the technical solutions in the present application will be described in conjunction with the accompanying drawings.

[0075] In the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly speaking, using words such as "exemplary" or "for example" aims to present relevant concepts in a specific manner.

[0076] In the embodiments of this application, "at least one" mentioned refers to one or more, and "a plurality" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single item or plural items. For example, at least one of a, b, or c can represent: a, b, c, (a and b), (a and c), (b and c), or (a and b and c), where a, b, c can be single or multiple. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. Here, A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after. And the sequence numbers of the steps in the embodiments of this application (such as step S1, step S21, etc.) are only used to distinguish different steps and do not limit the order of execution between steps.

[0077] Moreover, unless otherwise stated, the ordinal numbers such as "first" and "second" used in the embodiments of this application are used to distinguish multiple objects and do not limit the order, time sequence, priority, or importance of multiple objects. For example, the first device and the second device are only for easy description, and do not mean that the structures, importance levels, etc. of the first device and the second device are different. In some embodiments, the first device and the second device can also be the same device.

[0078] As used in the above embodiments, depending on the context, the term "when..." can be interpreted to mean "if...", or "after...", or "in response to determining...", or "in response to detecting...". The above are only optional embodiments of this application and are not intended to limit this application. Any modifications, equivalent replacements, improvements, etc. made within the concept and principle of this application shall be included in the protection scope of this application.

[0079] For the convenience of understanding, the following first introduces relevant terms and related concepts involved in the embodiments of this application.

[0080] (1), ASON

[0081] ASON is an Automatically Switched Transport Network (ASTN) based on an optical transport network. Its basic idea is to introduce a control plane into the optical transport network to achieve real-time on-demand allocation of network resources, thereby realizing the intelligence of the optical network. ASON can provide fast, reliable, and flexible optical network connections, support multiple service types and protection and restoration mechanisms, and improve the reliability and availability of the network.

[0082] The main features of ASON include:

[0083] Dynamic Routing and Wavelength Assignment: ASON uses automated routing protocols and wavelength assignment mechanisms to dynamically establish optical network connections according to service requirements, improving the utilization rate of network resources.

[0084] Distributed Control Plane: ASON adopts a distributed control plane, where each network node independently exchanges routing and link state information to achieve fast fault recovery and path optimization.

[0085] Multi-service Support: ASON can support multiple service types, such as Time Division Multiplexing (TDM), Asynchronous Transfer Mode (ATM), Ethernet, etc., and can provide different levels of protection and recovery mechanisms according to service requirements.

[0086] Intelligent Management: ASON is configured, monitored, and maintained through a centralized network management system, improving the manageability and maintainability of the network.

[0087] In the embodiments of this application, ASON includes a controller and at least three nodes. Among them, in the embodiments of this application, there are no restrictions on the hardware devices of the nodes. Exemplarily, the nodes can be optical network devices such as optical transmission devices, optical cross-connect devices, and optical amplification devices, or devices such as edge devices with the capabilities of fault detection and recovery cross-configuration. An edge device refers to a device located at the edge of the network, close to the end user, and is responsible for processing and managing data and requests from the end user. For example, edge devices can include routers, switches, gateways, access servers, etc.

[0088] (2), Available Zone (AZ)

[0089] An AZ refers to an available zone in a data center. It is a logical concept representing a fault isolation area. An AZ may contain one or more Data Centers (DCs), and one data center can also be set with one or more AZs. In actual deployment, AZs and DCs can be flexibly mapped according to requirements. For example, in large-scale public clouds, one AZ can contain multiple DCs; in medium and small-scale private clouds, multiple independent AZs can be set within one DC; or one DC can be planned as one AZ, in which case the DC and the AZ are equivalent.

[0090] (3), Recovery Cross-configuration

[0091] Recovery Crossover is an operation in a switching network used to restore service connectivity from a faulty or blocked state. For example, the recovery crossover of node 6 is set to the cross-connection between port 1 channel 1 and port 4 channel 1, meaning that when a network fault or blockage occurs, communication can be restored by switching traffic from port 1 channel 1 to port 4 channel 1.

[0092] Recovery Crossover is a network configuration used to restore network connectivity and communication stability by reconfiguring network devices when a network fault or blockage occurs. This configuration is typically used to improve network reliability and availability. By configuring Recovery Crossover, when the original path fails, it can quickly switch to the fault recovery path (i.e., the backup path), thus ensuring network connectivity and communication stability. This configuration is particularly important for critical services and network environments that require high availability.

[0093] Reference Figure 1B , Figure 1B FIG. 10 is a schematic diagram of data center interconnection based on OLP provided for an embodiment of the present application; the data centers are exemplified by data center 1, data center 2, and data center 3. Four pairs of optical cables 102 need to be deployed between every two data centers, and optical line protection (OLP) is deployed between every two pairs of optical cables, which can support three fiber breakage fault recoveries. A total of 12 pairs of optical cables need to be deployed among the three data centers, consuming a large amount of network optical cables.

[0094] In view of Figure 1B the existing defects, a solution for data center interconnection based on ASON in Figure 1A is proposed. Figure 1A In Figure 1A , only nine groups of optical cables need to be deployed among the three data centers, and the optical cables deployed inside the data centers do not consume network resources and can be not counted; therefore,

[0095] However, Figure 1A the interconnection solution in Figure 1C has the problem of high time consumption for fault message notification during fault recovery, resulting in low fault recovery performance. Exemplarily, referring to Figure 1C FIG. 30 is a schematic diagram of a fault notification process provided for an embodiment of the present application; assume the working path is source node 1 - node 2 - node 3, and the recovery path is source node 1 - node 4 - node 5 - node 6. When Figure 1A a sub-path in the ASON of Figure 1CTaking the failure of the first link between node 2 and node 3 as an example, after node 2 detects the failure of the first link, it notifies the source node 1. The source node 1 initiates the recovery. The source node 1 notifies node 4, node 5, and node 6 through a signaling protocol to complete the configuration of the recovery path. The above signaling protocol can be the Resource Reservation Protocol (RSVP). Figure 1C The main problem existing in the solution of Figure 1C is that the failure needs to be notified to the source node (or the first node) of the working path first, and then notified to each node for recovery by the source node. The time for failure notification is determined by the distance and hop count between the failure detection point and the source node, and this part of the time cannot be used for failure recovery. For example, for a 20-hop path, if the failure occurs on the 19th-hop optical fiber, then according to the forwarding time of 1 millisecond (ms) for each node, it takes 19 ms to notify the failure to the source node.

[0096] Therefore, the embodiment of the present application provides a failure recovery method, which can effectively reduce the time required for message notification during failure recovery and improve the failure recovery performance.

[0097] The failure recovery method of the embodiment of the present application can be applied to scenarios that require network transmission. For example, between institutions, between branch offices, or between data centers. Exemplarily, ASON can be responsible for network transmission.

[0098] In the embodiment of the present application, with reference to Figure 1D , Figure 1D FIG. Figure 1D shows a schematic architecture diagram of an ASON provided for the embodiment of the present application; ASON includes a controller and at least three nodes. Replacements for the controller include control device, control apparatus, master controller, master device, master apparatus, etc. The network composed of the above at least three nodes can be a non-chain and non-loop structure.

[0099] Among them, the controller is responsible for implementing the topology management, path calculation, and service management of the ASON network. The controller mainly includes the following units:

[0100] The resource management unit is responsible for managing the local resources of the nodes in the ASON, including link ports and link channels.

[0101] The topology management unit is responsible for managing the network topology of the ASON, including nodes and links. The link is the optical fiber connection between nodes.

[0102] The path calculation unit is responsible for calculating the paths of services, including the working path and the failure recovery path. It is responsible for calculating the failure notification path when the failure notification mode is the specified routing mode.

[0103] The service management unit is responsible for managing all services in ASON, including the working path, the fault recovery path, and the first correspondence relationship of each node on the fault recovery path. The first correspondence relationship of the above nodes is used to indicate the correspondence relationship between the fault sub-path, the service corresponding to the working path, and the recovery cross indication information of the node.

[0104] The nodes in ASON are responsible for fault detection, fault notification, and recovery cross configuration. The nodes mainly include the following units:

[0105] The link management unit is used to respond the local link information to the controller.

[0106] The fault detection unit: responsible for network fault detection, including node faults or link faults between nodes, etc.

[0107] The notification protocol unit: responsible for notifying the fault information (i.e., the first information in the embodiments of the present application) to the corresponding nodes in the network, and the notification methods include the neighbor diffusion mode or the specified routing mode.

[0108] The service cross unit: responsible for managing the first correspondence relationship and performing recovery cross configuration according to the received fault information.

[0109] In the embodiments of the present application, by taking the controller as the formulator of the overall recovery strategy, and each network element as the executor of fault recovery, and the fault detection point only needs to spread the fault to each node on the fault recovery path, and then each node on the fault recovery path starts the local recovery cross configuration based on the received fault notification.

[0110] The following specifically describes the fault recovery method of the embodiments of the present application.

[0111] In the embodiments of the present application, the execution subjects of the fault recovery method are taken as the controller, the first node, and the second node as examples.

[0112] Refer to Figure 2 , Figure 2 which is a schematic flowchart of a fault recovery method provided by the embodiments of the present application; the fault recovery method includes the following steps:

[0113] 201. The first node sends the first information to the controller.

[0114] Specifically, the above first information is used to indicate that a first sub-path in the ASON fails, and the first working path in the ASON passes through the first sub-path. Exemplarily, the first sub-path can be a node in the ASON or a transmission link composed of at least two nodes. The first information can directly or indirectly indicate the failure of the first sub-path, and the first information includes the failure description information or the failure unique identity document (ID) of the first sub-path. The failure description information of the first sub-path can include the name of the first sub-path or the path ID of the first sub-path. Each type of failure ID corresponds to a specific failure that occurs in the first sub-path.

[0115] Among them, there can be one or more first working paths passing through the first sub-path. When there are multiple first working paths, each first working path corresponds to a different service. For example, when there are three first working paths, namely the first working path 1, the first working path 2, and the first working path 3, passing through the first sub-path, the first working path 1 corresponds to the first service, and the first working path 1 is the working path of the first service; the first working path 2 corresponds to the second service, and the first working path 2 is the working path of the second service; the first working path 3 corresponds to the third service, and the first working path 3 is the working path of the third service.

[0116] Correspondingly, the controller receives the first information sent by the first node.

[0117] 202. The first node sends the first information to the second node.

[0118] Among them, the second node is a node on the first failure recovery path corresponding to the first working path. The first failure recovery path is the service recovery path of the first working path when the first sub-path fails. The first failure recovery path does not pass through the above first sub-path.

[0119] Among them, when there are multiple first working paths, there are also multiple first failure recovery paths, and one first working path corresponds to one first failure recovery path when the first sub-path fails.

[0120] Correspondingly, the second node receives the first information sent by the first node.

[0121] 203. The second node performs restoration cross-configuration based on the first information and the first corresponding relationship corresponding to the second node.

[0122] Among them, the above first corresponding relationship is used to indicate the corresponding relationship between the failed sub-path, the service corresponding to the working path, and the restoration cross-indication information of the second node. The above restoration cross-indication information is used to indicate the restoration cross-configuration that the second node needs to perform.

[0123] The specific form of the faulty sub-path in the first correspondence relationship may be the name of the faulty sub-path, or the ID of the faulty sub-path, or the fault ID, etc. The specific form of the service corresponding to the working path in the first correspondence relationship may be the name of the service corresponding to the working path, or the service identifier of the service corresponding to the working path, etc. The specific form of the recovery cross indication information in the first correspondence relationship is not limited, as long as it can indicate the recovery cross configuration that the second node needs to execute.

[0124] The specific form of the first correspondence relationship may be in the form of a table.

[0125] 204. The second node sends the second information to the controller.

[0126] Specifically, after the second node completes the recovery cross configuration based on the first information and the first correspondence relationship corresponding to the second node, it sends the second information to the controller to enable the controller to know the result of the recovery cross configuration of the second node. Among them, the above second information is used to indicate that the second node has completed the recovery cross configuration based on the first information and the first correspondence relationship corresponding to the second node.

[0127] Correspondingly, the controller receives the second information sent by the second node.

[0128] In the embodiment of the present application, the first node sends the first information to the controller to inform the controller that a fault has occurred in the first sub-path, and the first node sends the first information to the second node so that the second node performs a recovery cross configuration based on the first information and the first correspondence relationship corresponding to the node. After the second node completes the recovery cross configuration, it sends the second information to the controller to inform the controller of the result of its own recovery cross configuration. This solution is a method for triggering service recovery based on a fault. The fault recovery is directly started during the fault notification process, completely eliminating the time for the fault notification to reach the source node, reducing the time required for message notification during fault recovery, and effectively improving the fault recovery performance.

[0129] In a possible implementation manner, refer to Figure 3A , Figure 3A which is a schematic flow diagram of another fault recovery method provided by the embodiment of the present application; the above fault recovery method further includes the following steps:

[0130] 301. The controller determines the fault recovery path corresponding to each sub-path in the working path during a fault based on the topological state information of the ASON and the working paths in the ASON.

[0131] Specifically, the working paths in the ASON are the working paths corresponding to the services in the ASON. There may be one or more services in the ASON, and there may be one or more corresponding working paths. Refer to Figure 3B , Figure 3BSchematic diagram of the interaction process of a fault recovery method provided by an embodiment of the present application; step 301 includes step 311 and step 312.

[0132] Step 311: The controller synchronizes the link information of the entire ASON network.

[0133] Among them, the topology management unit in the controller sends a link synchronization request message to each node in the ASON. The link management unit in each node in the ASON responds to the received link synchronization request message and responds with the local link information to the controller. The above link information includes link port identifiers and statuses (normal and faulty), link advertisement identifiers and statuses (in use and idle). The link information of all nodes in the ASON constitutes the above topology status information.

[0134] Step 312: The controller calculates the fault recovery path.

[0135] Among them, the service management unit in the controller sends a path calculation request to the path calculation unit to request the path calculation unit to calculate the fault recovery path of each working path, and the path calculation unit calculates the fault recovery path of each working path.

[0136] Exemplarily, the above path calculation request includes a working path and an advertisement mode (neighbor expansion mode or specified routing mode).

[0137] Exemplarily, there may be one or more fault recovery paths for each of the above working paths. The fault recovery path needs to calculate the fault recovery path required when a sub-path fails based on each sub-path passed by the working path. For example, if the working path is node 1 - node 2 - node 3, the recovery path needs to calculate the corresponding fault recovery paths for node 1, node 2, node 3, the first link between node 1 and node 2, and the second link between node 2 and node 3 when they fail respectively. The fault recovery paths of different sub-paths of the same working path may be the same or different. Further exemplarily, in order to reduce the computational complexity of calculating the fault recovery path, the fault recovery paths of different sub-paths of the same working path are preferably the same.

[0138] For example, referring to Figure 3C , Figure 3C Schematic diagram of a fault recovery method provided by an embodiment of the present application; among them, the working path of the service is indicated by a straight line with an arrow. Among them, the working path of service 1 is working path 1, the working path of service 2 is working path 2, and the working path of service 3 is working path 3.

[0139] That is, the working path 1 is node 1 - node 2 - node 3 - node 4. When the second link between node 2 and node 3 fails, the corresponding fault recovery path 1 of the working path 1 is node 1 - node 6 - node 7 - node 4.

[0140] The working path 2 is Node 1 - Node 2 - Node 3. When a fault occurs in the second link between Node 2 and Node 3, the corresponding fault recovery path 2 of the working path 2 is Node 1 - Node 5 - Node 6 - Node 3.

[0141] The working path 3 is Node 2 - Node 3 - Node 4. When a fault occurs in the second link between Node 2 and Node 3, the corresponding fault recovery path 3 of the working path 3 is Node 2 - Node 6 - Node 7 - Node 8 - Node 4.

[0142] If the notification mode is the specified path mode, the path calculation unit needs to calculate the fault notification path between the fault detection point and the nodes on the fault recovery path to be notified. The above - mentioned fault detection point is the node on the working path. Taking the first node and the second node as an example, in the case of a fault in the first sub - path, the controller determines the fault notification path corresponding to the second node based on the first node and the second node.

[0143] Reference Figure 3C , taking the fault detection node as Node 3 and the fault recovery path as the fault recovery path 2 as an example. In the case of a fault in the first sub - path (for example, the second link between Node 2 and Node 3), the controller needs to determine the fault notification paths of Node 3 and Node 5 on the fault recovery path 2. Since there is a fault between Node 2 and Node 3, the controller designates the fault notification path for Node 3 and Node 5 as Node 3 - Node 6 - Node 5, which can avoid the situation that the fault notification cannot be sent to Node 5 normally and affect the recovery performance.

[0144] 302. The controller determines the first corresponding relationship corresponding to each node on the fault recovery path based on the fault recovery path corresponding to each sub - path in the working path.

[0145] Specifically, the service management unit in the controller obtains the fault recovery paths corresponding to the sub - paths of all working paths, and processes them to obtain the first corresponding relationship corresponding to each node on the fault recovery path.

[0146] Exemplarily, reference Figure 3C, taking node 6 as an example, when the second link fails, the second link corresponds to three fault recovery paths, namely fault recovery path 1, fault recovery path 2, and fault recovery path 3, all of which pass through node 6. Therefore, based on the three working paths and the three fault recovery paths corresponding to the second link, the first correspondence 304 of node 6 can be obtained. Among them, for working path 1, the recovery cross configuration at node 6 is that port 2 channel 1 of node 6 is switched to port 5 channel 1. The recovery cross indication information for indicating the recovery cross configuration can be 2.1 <-> 5.1 or 2-1 <-> 5-1 or 2.1—5.1 or 2.1—> 5.1. For working path 2, the recovery cross configuration at node 6 is that port 1 channel 1 of node 6 is switched to port 4 channel 1. Then the recovery cross indication information for indicating the recovery cross configuration can be 1.1 <-> 4.1 or 1-1 <-> 4-1 or 1.1—4.1 or 1.1—> 4.1. For working path 3, the recovery cross configuration at node 6 is that port 3 channel 1 of node 6 is switched to port 5 channel 2. Then the recovery cross indication information for indicating the recovery cross configuration can be 3.1 <-> 5.2 or 3-1 <-> 5-2 or 3.1—5.2 or 3.1—> 5.2.

[0147] According to the above method, corresponding first correspondences are configured for other faults and other nodes. That is, the controller configures the corresponding first correspondence for each node of each fault recovery path.

[0148] 303. The controller sends the first correspondence corresponding to each node on the fault recovery path to each node.

[0149] Correspondingly, taking the second node as an example, the second node receives the first correspondence corresponding to the second node sent by the controller. After receiving the first correspondence, the service cross unit of the second node stores the first correspondence locally.

[0150] In the embodiment of the present application, the controller is used to determine the fault recovery path and the first correspondence corresponding to each node, which can simplify the device capability requirements for the nodes. The nodes can be edge devices, that is, devices with relatively weak hardware capabilities. The first node only needs to be responsible for transmitting the first information, and the nodes on the fault recovery path only need to start the local recovery cross configuration based on the first information and transmit the recovery cross configuration result to achieve fault recovery.

[0151] If the specified routing mode is adopted, the service management unit of the controller also needs to configure the fault notification path for the fault detection nodes in each fault scenario, that is, the nodes on the working path. For example, for working path 3, the controller needs to send the fault notification path corresponding to each node in the fault recovery path 3 to node 2, node 3, and node 4. After receiving the fault notification path, the notification protocol unit of the fault detection node stores the fault notification path locally.

[0152] In this solution, the controller specifies the fault notification path for the first node and the second node, and the controller sends the fault notification path to the first node. In this way, an optimal or most suitable path can be determined between the first node and the second node, improving the information transmission performance between the first node and the second node. In addition, by specifying the path by the controller, network traffic and load can be better managed. The controller can distribute the traffic to different paths to avoid overloading of certain paths, thereby achieving network load balancing.

[0153] Taking the first node and the second node as an example, at this time, the controller sends the fault notification path corresponding to the second node to the first node. Correspondingly, the first node receives the fault notification path corresponding to the second node sent by the controller.

[0154] In a possible implementation manner, the above-mentioned first node can obtain the first information in multiple ways. Exemplarily, the first node has the fault detection ability, and the first node can detect that the first sub-path fails and generate the first information. The first sub-path at this time can be the first node or the third link, and the first node is a node in the third link (such as the starting node, the ending node, or the intermediate node of the third link). Also exemplarily, the third node detects that the first sub-path fails and generates the first information, and the third node sends the first information to the first node. The above-mentioned third node can be any node in the ASON.

[0155] In the embodiment of this application, after the first node obtains the first information, it notifies the fault to the controller and the nodes on the first fault recovery path corresponding to the first working path, that is, sends the first information.

[0156] In an instance, the first node can send the first information concurrently to all the nodes on the first fault recovery path. Refer to Figure 3D , Figure 3D which is a schematic diagram of a method for sending the first information provided by the embodiment of this application; taking the node 3 as an example of the first node, and the first fault recovery path being node 1 - node 5 - node 6 - node 3. Node 3 simultaneously sends the first information to node 1, node 5, node 6, and node 3.

[0157] However, the solution for concurrent information is affected by the routing convergence performance and cannot guarantee that the first information is notified to each node on time. For example, in a network with 150 nodes, when a network failure occurs, the routing convergence performance is between 1s and 10s, so notifying the first information may be delayed by several seconds. Therefore, the embodiments of the present application also propose two other method examples for sending the first information, namely the first example and the second example.

[0158] In the first example, the first node sends the first information to each node on the first fault recovery path corresponding to the first working path, which specifically includes the following steps:

[0159] The first node sends the first information to each node in the ASON. Each node in the ASON includes each node on the first fault recovery path.

[0160] In this example, when the first node sends the first information to each node on the first fault recovery path, it can be to send the first information to each node in the ASON. There are various specific sending methods and no special limitations are made. In this way, not only can each node on the first fault recovery path obtain the first information, but also the nodes in the ASON other than the nodes on the first fault recovery path can obtain the first information and can timely know the change of the topological state information of the ASON.

[0161] Further exemplarily, when the first node sends the first information to each node in the ASON, it can be sent based on the neighbor diffusion mode, which specifically includes the following steps:

[0162] The first node sends the first information to the first neighbor nodes of the first node, so that each first neighbor node sends the first information to the neighbor nodes of the first neighbor node. Among them, when the first neighbor node receives the first information and determines that there is no duplicate reception, it continues to distribute it to the neighbor nodes of the first neighbor node.

[0163] Correspondingly, when the second node is a neighbor node of the first node, the second node receives the first information sent by the first node.

[0164] When the second node is not a neighbor node of the first node, the second node receives the first information sent by the neighbor nodes of the second node. The above neighbor nodes obtain the first information from the first node. The neighbor nodes of the second node can obtain the first information directly or indirectly from the first node. When the neighbor node of the second node is a neighbor node of the first node, the neighbor node of the second node directly obtains the first information from the first node. When the neighbor node of the second node is not a neighbor node of the first node, the neighbor node of the second node indirectly obtains the first information from the first node. For example, the neighbor node of the second node obtains the first information from the fourth node. The fourth node is a neighbor node of the first node and the fourth node obtains the first information from the first node.

[0165] Exemplarily, referring to Figure 3C , taking Node 3 as an example of the first node, after Node 3 detects a failure in the second link, it notifies the first information to the neighbor nodes of Node 3. Each first information may include a random number to distinguish different failures. The neighbor nodes of Node 3 include Node 2, Node 4, Node 6, Node 7, and Node 8.

[0166] After receiving the first information, the neighbor nodes of the first node notify it to their own neighbor nodes. For example, after receiving the first information, Node 7 notifies it to its neighbor nodes. The neighbor nodes of Node 7 include Node 2, Node 3, Node 4, Node 6, and Node 8.

[0167] If a node has received the first information before receiving it again, it will no longer forward it to its neighbor nodes. It can be judged whether it is a repeated reception by the reception timestamp and random number of the first information. For example, when Node 8 receives the first information notified by Node 7 and determines that the first information is the same as the first information notified by Node 3, Node 8 will no longer forward it to its neighbor nodes. For each node, the first information will be forwarded to its neighbor nodes once, but not the second time. That is, when the first information is received for the second time, it will no longer be forwarded to its neighbor nodes.

[0168] In this solution, the first node can send the first information to each node in the ASON based on the neighbor expansion mode, which can not only improve the transmission performance of the first information, but also ensure that each node on the first fault recovery path obtains the first information.

[0169] Referring to Figure 3E , Figure 3E is a schematic diagram of another method for sending the first information provided by the embodiment of the present application; the neighbor diffusion mode will be specifically described below. Taking Node 1 as an example of the first node, it specifically includes the following steps:

[0170] 305. Node 1 detects a failure and generates the first information.

[0171] Specifically, the failure detection unit of Node 1 detects a failure in the first sub-path in the ASON and notifies the failure ID of the first sub-path to the notification protocol unit. The notification protocol unit encapsulates the failure ID and the corresponding random number into the notification message. At this time, the notification message is the above-mentioned first information. The first working path passes through the first sub-path.

[0172] 306. Node 1 sends the first information to the controller.

[0173] 307. Node 1 sends the first information to the neighbor nodes of Node 1.

[0174] Among them, step 306 and step 307 can be executed simultaneously or successively, and no limitation is imposed on the sequence of their execution.

[0175] 308. Node 2 receives and forwards the first piece of information.

[0176] Specifically, the advertisement protocol unit of node 2 receives the first piece of information, that is, the advertisement message. After parsing the advertisement message, it notifies the service cross-connect unit of node 2 of the fault ID. In addition, when node 2 determines based on the first piece of information that the first piece of information has not been received repeatedly, it forwards the first piece of information to the neighbor node of node 2. Taking node 3 as an example of the neighbor node of node 2.

[0177] 309. Node 2 performs restoration cross-connection configuration based on the first piece of information and the first corresponding relationship corresponding to node 2.

[0178] Specifically, the service cross-connect unit of node 2 searches according to the fault ID in the local first corresponding relationship. If the restoration cross-connection indication information corresponding to the fault ID is found, indicating that node 2 is a node on the first fault restoration path corresponding to the first working path, then the service cross-connect unit of node 2 starts and completes the restoration cross-connection configuration corresponding to the restoration cross-connection indication information.

[0179] Furthermore, after node 2 completes the restoration cross-connection configuration, node 2 sends a second piece of information to the controller to notify the controller that the restoration cross-connection configuration has been completed.

[0180] Exemplarily, referring to Figure 3C , taking node 6 as an example, after node 6 receives the first piece of information corresponding to the second link, by looking up the first corresponding relationship 304, it can be determined that the restoration cross-connection indication information corresponding to the second link during a fault is: 2.1 <-> 5.1, 1.1 <-> 4.1, and 3.1 <-> 5.2. Then node 3 configures these three cross-connections. After node 6 completes the configuration of the above three cross-connections, it sends a second piece of information to the controller to notify the controller that it has completed the restoration cross-connection configuration for service 1, service 2, and service 3.

[0181] Among them, step 308 and step 309 can be executed simultaneously or successively, and no limitation is imposed on the sequence of their execution.

[0182] 310. Node 3 receives the first piece of information sent by node 2.

[0183] For the specific description of step 310, reference can be made to the description of step 308, and details will not be repeated here.

[0184] 311. Node 3 performs restoration cross-connection configuration based on the first piece of information and the first corresponding relationship corresponding to node 3.

[0185] For the specific description of step 311, reference can be made to the description of step 309, and details will not be repeated here.

[0186] Until the controller determines that it has received the second information sent by all nodes on the first fault recovery path, the controller can determine that the service recovery corresponding to the first working path is completed.

[0187] In the second instance, the above-mentioned first node sends the first information to each node on the first fault recovery path corresponding to the first working path, specifically including the following steps:

[0188] The first node sends the first information to the second node on the first fault recovery path based on the fault notification path, and the fault notification path is related to the first node and the second node.

[0189] Correspondingly, the second node receives the first information sent by the first node through the fault notification path.

[0190] In this instance, the first node can send the first information to the second node based on the specified routing mode. When the first node sends the first information to the second node on the first fault recovery path, the first node can send the first information to the second node through the fault notification path (i.e., the specified notification path) between the first node and the second node. By notifying the first information through the specified path, detours or unnecessary transmissions can be avoided, and the most appropriate path can be selected to send the first information to the second node, improving the transmission performance of the first information.

[0191] Reference Figure 3F , Figure 3F is a schematic diagram of another method for sending the first information provided by the embodiment of the present application; the specified routing mode will be specifically described below. Taking the first node as node 1, it specifically includes the following steps:

[0192] 312. Node 1 detects a fault and generates the first information.

[0193] For the specific description of step 312, reference can be made to step 305, which will not be elaborated here.

[0194] 313. Node 1 sends the first information to the controller.

[0195] 314. Node 1 performs recovery cross-configuration based on the first information and the first corresponding relationship corresponding to node 1.

[0196] Specifically, the notification protocol unit of node 1 sends the first information to the service cross unit of node 1. When the service cross unit of node 1 searches for the recovery cross indication information corresponding to the fault ID in the local first corresponding relationship and indicates that node 1 is a node on the first fault recovery path, node 1 starts and completes the recovery cross-configuration corresponding to the recovery cross indication information. When the recovery cross indication information corresponding to the fault ID is not searched, the recovery cross-configuration is not started.

[0197] 315. Node 1 sends the first information to the nodes that need to be notified based on the fault notification path.

[0198] Specifically, when Node 1 sends the first information to the nodes that need to be notified based on the fault notification path, the notification message at this time also includes the fault notification path corresponding to the node that needs to be notified. In this embodiment, the nodes that Node 1 needs to notify are exemplified by Node 2 and Node 3. For example, for the notification message that needs to be notified to Node 3, the notification message includes a fault ID and a fault notification path. At this time, the fault notification path of Node 3 is Node 1 - Node 2 - Node 3.

[0199] For another example, refer to Figure 3C , when Node 3 detects a second link fault between Node 2 and Node 3, Node 3 needs to send the first information to the nodes on the fault recovery path 1 corresponding to the working path 1, the nodes on the fault recovery path 2 corresponding to the working path 2, and the nodes on the fault recovery path 3 corresponding to the working path 3. Then, it sends the first information to each node that needs to be notified according to the fault notification path corresponding to the node that needs to be notified. When there are duplicate nodes among the nodes on the fault recovery path 1 corresponding to the working path 1, the nodes on the fault recovery path 2 corresponding to the working path 2, and the nodes on the fault recovery path 3 corresponding to the working path 3, only one first information needs to be sent, and there is no need to send the first information repeatedly.

[0200] There are various implementation schemes for sending the first information to the nodes based on the fault notification path, that is, the specified routing mode, which is not limited. For example, based on the Segment Routing (SR) scheme, segment routing is a tunnel implementation mechanism based on source routing. It realizes routing by dividing the network path into segments and assigning segment numbers (SegmentIDs, SIDs) to these segments. These SIDs can identify forwarding nodes or adjacent links and are arranged in an orderly manner to form a segment sequence (Segment List), representing a forwarding path. The essence of SR is an instruction that guides where the packet goes and how to go.

[0201] 316. Node 2 receives the first information.

[0202] Specifically, when the notification protocol unit of Node 2 receives the notification message and parses the message content, it notifies the local service cross-connect unit of the fault ID.

[0203] 317. Node 2 performs restoration cross-configuration based on the first information and the first corresponding relationship corresponding to Node 2.

[0204] Specifically, the service cross unit of node 2 searches according to the first corresponding relationship of the fault ID locally. If the recovery cross indication information corresponding to the fault ID is found, it starts and completes the configuration of the recovery cross. After the completion of the recovery cross configuration, node 2 sends a second message to the controller to notify the controller that it has completed the recovery cross configuration.

[0205] 318. Node 3 receives the first message.

[0206] 319. Node 3 performs recovery cross configuration based on the first message and the first corresponding relationship corresponding to node 3.

[0207] For the specific descriptions of steps 318 and 319, reference can be made to the descriptions of steps 315 and 316, and details will not be repeated here.

[0208] Until the controller determines that it has received the second messages sent by all nodes on the first fault recovery path, the controller can determine that the service recovery corresponding to the first working path is completed.

[0209] In the embodiments of the present application, the first node forwards the first message through the neighbor diffusion mode or the specified routing mode, effectively avoiding the problem of uncertain message forwarding time caused by routing convergence, and effectively improving the performance of fault recovery.

[0210] In a possible implementation manner, the above fault recovery method further includes the following steps:

[0211] When the controller receives the second messages sent by all nodes on the first fault recovery path, it takes the first fault recovery path as the new working path in the ASON.

[0212] Specifically, the controller can determine the fault recovery result based on the received first message and the second message, that is, the recovery result of the service corresponding to the first working path. The controller obtains the second message in real time. When it determines that it has received the second messages sent by all nodes on the first fault recovery path, it can determine that the end-to-end recovery configuration of the first fault recovery path has been completed, that is, the service recovery corresponding to the first working path is completed, and the first fault recovery path can be taken as the new working path of the service.

[0213] When there are network changes and / or service changes in the ASON, the controller needs to refresh the first corresponding relationship of the nodes again. For specific reference, see the following four examples. In addition, the four examples can be combined according to the actual situation, without limitation.

[0214] In the first example, the above fault recovery method further includes the following steps:

[0215] When a new working path is added to the ASON, the working paths in the ASON are updated. Specifically, the situation where a new working path is added to the ASON can be that the first fault recovery path completes the end-to-end recovery setup and the first fault recovery path is used as the new working path. Or, if a new service is added to the ASON, then there is a working path corresponding to the new service in the ASON.

[0216] Based on the topological state information of the ASON and the updated working paths, re-determine the new fault recovery paths corresponding to each sub-path in the updated working paths in case of a fault.

[0217] Based on the new fault recovery paths, determine the new first correspondences corresponding to each node on the new fault recovery paths.

[0218] In this example, when a new working path is added to the ASON, the controller needs to update the working paths in the ASON and update the fault recovery paths and the first correspondences according to the updated working paths and the topological state information of the ASON; so that the fault recovery paths and the first correspondences can be updated in a timely manner following the latest state of the ASON, ensuring the reliability and stability of the service, and enabling the ASON to operate stably.

[0219] In the second example, the above fault recovery method further includes the following steps:

[0220] When the first working path returns to normal, update the working paths in the ASON and update the topological state information of the ASON. Specifically, when the first working path returns to normal, at this time the working paths in the ASON are updated, and at the same time, the topological state information in the ASON also changes.

[0221] Based on the updated topological state information of the ASON and the updated working paths, re-determine the new fault recovery paths corresponding to each sub-path in the updated working paths in case of a fault.

[0222] Based on the new fault recovery paths, determine the new first correspondences corresponding to each node on the new fault recovery paths.

[0223] In this example, when the first working path returns to normal, that is, when the fault of the first sub-path is eliminated, the controller needs to update the working paths in the ASON and update the topological state information of the ASON, and update the fault recovery paths and the first correspondences according to the updated working paths and the updated topological state information; so that the fault recovery paths and the first correspondences can be updated in a timely manner following the latest state of the ASON, ensuring the reliability and stability of the service, and enabling the ASON to operate stably.

[0224] Exemplarily, when the end-to-end recovery configuration of the first fault recovery path corresponding to the first working path has been completed and the first fault recovery path is used as the new working path, when the first working path returns to normal, the first fault recovery path is restored as the fault recovery path of the first working path.

[0225] In the third example, the above-mentioned fault recovery method further includes the following steps:

[0226] When a second sub-path in the fault recovery path in ASON fails, the topological state information of ASON is updated. Specifically, in the case where the second sub-path fails, the fault does not affect the working path but affects the fault recovery path. At this time, the topological state information of ASON changes, so the controller needs to re-refresh the fault recovery path of ASON and the first corresponding relationship of the nodes.

[0227] Based on the updated topological state information of ASON and the working paths in ASON, new fault recovery paths corresponding to each sub-path in each working path during a fault are re-determined.

[0228] Based on the new fault recovery paths, new first corresponding relationships corresponding to each node on the new fault recovery paths are determined.

[0229] In this example, in the case where the second sub-path in the fault recovery path fails, that is, the fault does not affect the working path. At this time, the topological state information of ASON needs to be updated, and the fault recovery path and the first corresponding relationship are updated based on the updated topological state information; it can cope with network changes, ensure the service continuity of ASON and improve the reliability of ASON.

[0230] In the fourth example, the above-mentioned fault recovery method further includes the following steps:

[0231] When the working path in ASON is updated and a second sub-path in the fault recovery path in ASON fails, the topological state information of ASON is updated. Specifically, the update of the working path in the above-mentioned ASON can be the situations shown in the above-mentioned first example and the second example.

[0232] Based on the updated topological state information of ASON and the updated working path, new fault recovery paths corresponding to each sub-path in the updated working path during a fault are re-determined.

[0233] Based on the new fault recovery paths, new first corresponding relationships corresponding to each node on the new fault recovery paths are determined.

[0234] In this embodiment, when the working path in the ASON is updated and the second sub-path in the fault recovery path fails, it is necessary to update the topological state information of the ASON, and update the fault recovery path and the first corresponding relationship based on the updated topological state information and the updated working path; to cope with network changes, ensure the service continuity of the ASON, and improve the reliability of the ASON.

[0235] Exemplarily, after the controller obtains the new first corresponding relationship, it sends the new first corresponding relationship to each node on the new fault recovery path.

[0236] The method of the embodiment of the present application is elaborated in detail above. Next, the device provided by the embodiment of the present application is introduced.

[0237] Figure 4 、 Figure 5 、 Figure 6 and Figure 7 are schematic structural diagrams of possible devices provided by the embodiment of the present application. Among them, Figure 4 The first node shown can be used to implement the functions of the first node in the above-mentioned Figure 2 shown fault recovery method embodiment, and thus can also achieve the beneficial effects of the above-mentioned fault recovery method embodiment. In the embodiment of the present application, the first node can be an electronic device or a module (such as a chip) applied to an electronic device. Figure 5 The controller shown can be used to implement the functions of the controller in the above-mentioned Figure 2 shown fault recovery method embodiment, and thus can also achieve the beneficial effects of the above-mentioned fault recovery method embodiment. In the embodiment of the present application, the controller can be an electronic device or a module (such as a chip) applied to an electronic device. And Figure 6 The second node shown can be used to implement the functions of the second node in the above-mentioned Figure 2 shown fault recovery method embodiment, and thus can also achieve the beneficial effects of the above-mentioned fault recovery method embodiment. In the embodiment of the present application, the second node can be an electronic device or a module (such as a chip) applied to an electronic device.

[0238] As Figure 4 shown, Figure 4 is a schematic structural diagram of a first node provided by the embodiment of the present application; the first node 400 includes a sending module 410. The first node 400 is used to implement the functions of the first node in the above-mentioned Figure 2 shown fault recovery method embodiment. Or, the first node 400 may include a module for implementing the above-mentioned Figure 2A module for any function or operation of the first node in the embodiment of the fault recovery method shown, and this module can be implemented in whole or in part by software, hardware, firmware, or any combination thereof.

[0239] When the first node 400 is used to implement Figure 2 the functions of the first node in the method embodiment shown, the sending module 410 is used to send a first piece of information to the controller. The above-mentioned first piece of information is used to indicate that a fault has occurred in the first sub-path in the ASON, and the first working path in the ASON passes through this first sub-path. The above-mentioned sending module 410 is also used to send the first piece of information to each node on the first fault recovery path corresponding to the first working path, so that each node performs restoration cross-configuration based on the first piece of information and the first corresponding relationship corresponding to this node. The above-mentioned first corresponding relationship is used to indicate the corresponding relationship between the faulty sub-path, the service corresponding to the working path, and the restoration cross-indication information.

[0240] In a possible implementation manner, in terms of sending the first piece of information to each node on the first fault recovery path corresponding to the first working path, the above-mentioned sending module 410 is specifically used for: sending the first piece of information to each node in the ASON, and each node in the ASON includes each node on the first fault recovery path.

[0241] In a possible implementation manner, in terms of sending the first piece of information to each node in the ASON, the above-mentioned sending module 410 is specifically used for: sending the first piece of information to the first neighbor nodes of the first node, so that each first neighbor node sends the first piece of information to the neighbor nodes of the first neighbor node.

[0242] In a possible implementation manner, in terms of sending the first piece of information to each node on the first fault recovery path corresponding to the first working path, the above-mentioned sending module 410 is specifically used for: sending the first piece of information to the second node on the first fault recovery path based on the fault notification path, and the fault notification path is related to the first node and the second node.

[0243] In a possible implementation manner, referring to Figure 4 , the above-mentioned first node 400 further includes a receiving module 420. The receiving module 420 is used to receive the fault notification path corresponding to the second node sent by the controller.

[0244] For the introduction of the above-mentioned various modules, reference can be made to the records of the foregoing embodiments, and details will not be repeated here.

[0245] As Figure 5 shown, Figure 5 is a schematic structural diagram of a controller provided by an embodiment of the present application; the controller 500 includes a receiving module 510. The controller 500 is used to implement the above-mentioned Figure 2The functions of the controller in the embodiment of the fault recovery method shown. Alternatively, the controller 500 may include a module for implementing any function or operation of the controller in the embodiment of the fault recovery method shown above, and the module may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. Figure 2 in the embodiment of the fault recovery method shown above.

[0246] When the controller 500 is used to implement the functions of the controller in the method embodiment shown Figure 2 above, the receiving module 510 is configured to receive the first information sent by the first node. The first information is used to indicate that a fault has occurred in the first sub-path in the ASON, and the first working path in the ASON passes through the first sub-path. The receiving module 510 is further configured to receive the second information sent by the nodes on the first fault recovery path, and the first fault recovery path corresponds to the first working path. The second information is used to indicate that the nodes on the first fault recovery path have completed the restoration cross-configuration based on the first information and the first corresponding relationship corresponding to the node. The first corresponding relationship is used to indicate the corresponding relationship between the fault sub-path, the service corresponding to the working path, and the restoration cross-indication information.

[0247] In a possible implementation manner, referring to Figure 5 , the controller 500 further includes a processing module 520 and a sending module 530. The processing module 520 is configured to determine the fault recovery path corresponding to each sub-path in the working path when a fault occurs based on the topological state information of the ASON and the working path in the ASON. The processing module 520 is further configured to determine the first corresponding relationship corresponding to each node on the fault recovery path based on the fault recovery path corresponding to each sub-path in the working path. The sending module 530 is configured to send the first corresponding relationship corresponding to each node to each node on the fault recovery path.

[0248] In a possible implementation manner, when the processing module 520 receives the second information sent by all the nodes on the first fault recovery path, the processing module 520 uses the first fault recovery path as the new working path in the ASON.

[0249] In a possible implementation manner, the above ASON further includes a second node, and the processing module 520 is further configured to determine the fault notification path corresponding to the second node based on the first node and the second node. The nodes on the first fault recovery path include the second node. The sending module 530 is further configured to send the fault notification path corresponding to the second node to the first node.

[0250] In a possible implementation manner, the above processing module 520 is further configured to update the working paths in the ASON when a new working path is added to the ASON. The above processing module 520 is further configured to re-determine, based on the topological state information of the ASON and the updated working paths, new failure recovery paths corresponding to each sub-path in the updated working paths in case of a failure. The above processing module 520 is further configured to determine new first correspondences corresponding to each node on the new failure recovery paths based on the new failure recovery paths.

[0251] In a possible implementation manner, the above processing module 520 is further configured to update the working paths in the ASON and update the topological state information of the ASON when the first working path returns to normal. The above processing module 520 is further configured to re-determine, based on the updated topological state information of the ASON and the updated working paths, new failure recovery paths corresponding to each sub-path in the updated working paths in case of a failure. The above processing module 520 is further configured to determine new first correspondences corresponding to each node on the new failure recovery paths based on the new failure recovery paths.

[0252] In a possible implementation manner, the above processing module 520 is further configured to update the topological state information of the ASON when the second sub-path in the failure recovery path in the ASON fails. The above processing module 520 is further configured to re-determine, based on the updated topological state information of the ASON and the working paths in the ASON, new failure recovery paths corresponding to each sub-path in each working path in case of a failure. The above processing module 520 is further configured to determine new first correspondences corresponding to each node on the new failure recovery paths based on the new failure recovery paths.

[0253] In a possible implementation manner, the above processing module 520 is further configured to update the topological state information of the ASON when the working paths in the ASON are updated and the second sub-path in the failure recovery path in the ASON fails. The above processing module 520 is further configured to re-determine, based on the updated topological state information of the ASON and the updated working paths, new failure recovery paths corresponding to each sub-path in the updated working paths in case of a failure. The above processing module 520 is further configured to determine new first correspondences corresponding to each node on the new failure recovery paths based on the new failure recovery paths.

[0254] In a possible implementation manner, the above sending module 530 is further configured to send the new first correspondences to each node on the new failure recovery paths.

[0255] For the introduction of the above modules, reference can be made to the descriptions in the foregoing embodiments, which will not be elaborated herein.

[0256] AsFigure 6 As shown Figure 6 FIG. is a schematic structural diagram of a second node provided by an embodiment of the present application; the second node 600 includes a receiving module 610 and a processing module 620. The second node 600 is used to implement the functions of the second node in the above-mentioned Figure 2 fault recovery method embodiment shown. Alternatively, the second node 600 may include a module for implementing any function or operation of the second node in the fault recovery method embodiment shown above, and this module may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. Figure 2

[0257] When the second node 600 is used to implement the functions of the second node in the Figure 2 method embodiment shown, the receiving module 610 is used to receive the first information sent by the first node. The above-mentioned first information is used to indicate that a fault has occurred in the first sub-path in the ASON. The first working path in the ASON passes through the first sub-path. The second node is a node on the first fault recovery path corresponding to the first working path. The processing module 620 is used to perform restoration cross-configuration based on the first information and the first corresponding relationship corresponding to the second node. The above-mentioned first corresponding relationship is used to indicate the corresponding relationship between the fault sub-path, the service corresponding to the working path, and the restoration cross-indication information.

[0258] In a possible implementation manner, in terms of receiving the first information sent by the first node, the receiving module 610 is specifically used for: receiving the first information sent by the neighbor node of the second node, and the neighbor node obtains the first information from the first node.

[0259] In a possible implementation manner, in terms of receiving the first information sent by the first node, the receiving module 610 is specifically used for: receiving the first information sent by the first node through the fault notification path, and the fault notification path is related to the first node and the second node.

[0260] In a possible implementation manner, the above-mentioned ASON further includes a controller, and the receiving module 610 is further used to receive the first corresponding relationship corresponding to the second node sent by the controller.

[0261] In a possible implementation manner, referring to Figure 6 , the second node further includes a sending module 630. The sending module 630 is used to send the second information to the controller. The above-mentioned second information is used to indicate that the second node has completed the restoration cross-configuration based on the first information and the first corresponding relationship corresponding to the second node.

[0262] For the introduction of the above-mentioned modules, reference may be made to the descriptions in the foregoing embodiments, and details are not repeated here.

[0263] Referring to Figure 7 ​, Figure 7 A schematic structural diagram of a communication device provided for an embodiment of the present application; the communication device 700 includes a memory 701, a processor 702, a communication interface 704, and a bus 703. Among them, the memory 701, the processor 702, and the communication interface 704 are communicatively connected to each other through the bus 703.

[0264] Optionally, the above communication device 700 further includes a display screen (not shown), and the display screen is communicatively connected to the memory 701, the processor 702, and the communication interface 704 through the bus 703. The display screen is used to output information for interaction with the user, such as voice output or display output.

[0265] The memory 701 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 701 may store a program. When the program stored in the memory 701 is executed by the processor 702, the processor 702 and the communication interface 704 are used to execute the respective steps of the fault recovery method according to any embodiment of the present application.

[0266] The processor 702 may be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), a graphics processing unit (GPU), or one or more integrated circuits, and is used to execute relevant programs to implement the functions required to be executed by the units in the first node or the controller or the second node according to any embodiment of the present application, or to execute the fault recovery method according to any embodiment of the present application.

[0267] The processor 702 can also be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the fault recovery method according to any embodiment of the present application can be completed by the integrated logic circuit in the hardware of the processor 702 or instructions in the form of software. The above-mentioned processor 702 can also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the fault recovery method, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the fault recovery method according to any embodiment of the present application can be directly embodied as being executed by the hardware processor, or executed by a combination of the hardware and software modules in the processor. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory 701, and the processor 702 reads the information in the memory 701 and combines its hardware to complete the functions required to be executed by the units included in the first node or controller or the second node according to any embodiment of the present application, or executes the fault recovery method according to any embodiment of the present application.

[0268] The communication interface 704 uses a transceiver device such as, but not limited to, a transceiver to implement the communication between the communication device 700 and other devices or communication networks. For example, the first information, the second information, etc. can be obtained through the communication interface 704.

[0269] The bus 703 can include a path for transmitting information between various components of the communication device 700 (for example, the memory 701, the processor 702, the communication interface 704). In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

[0270] The unit described as a separation component may or may not be physically separated. The component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0271] In addition, in each embodiment of the present application, each functional unit may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit.

[0272] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that the computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape, a magnetic disk, or an optical medium, such as a digital versatile disc (DVD), or a semiconductor medium, such as a solid state disk (SSD), etc.

[0273] As described above, only the specific implementation manners of the present application are provided, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed in the present application can easily think of changes or substitutions, which should all be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A fault recovery method, characterized in that, Applied to the first node in an Automatically Switched Optical Network (ASON), the ASON further includes a controller; The method includes: Sending first information to the controller, where the first information is used to indicate that a first sub-path in the ASON has failed, and a first working path in the ASON passes through the first sub-path; Sending the first information to each node on a first fault recovery path corresponding to the first working path, so that each node performs restoration cross-configuration based on the first information and a first corresponding relationship corresponding to the node; the first corresponding relationship is used to indicate the corresponding relationship between the faulty sub-path, the service identifier corresponding to the working path, and the restoration cross-indication information.

2. The method according to claim 1, characterized in that, The sending the first information to each node on the first fault recovery path corresponding to the first working path includes: Sending the first information to each node in the ASON, and each node in the ASON includes each node on the first fault recovery path.

3. The method according to claim 2, characterized in that The sending the first information to each node in the ASON includes: Sending the first information to a first neighbor node of the first node, so that each first neighbor node sends the first information to a neighbor node of the first neighbor node.

4. The method according to claim 1, wherein The sending the first information to each node on the first fault recovery path corresponding to the first working path includes: Sending the first information to a second node on the first fault recovery path based on a fault notification path, and the fault notification path is related to the first node and the second node.

5. The method according to claim 4, characterized in that, The method further includes: Receiving the fault notification path corresponding to the second node sent by the controller.

6. A fault recovery method, characterized in that, Applied to a controller in an Automatically Switched Optical Network (ASON), the ASON further includes a first node; The method includes: Receiving first information sent by the first node, where the first information is used to indicate that a first sub-path in the ASON has failed, and a first working path in the ASON passes through the first sub-path; Receiving second information sent by a node on a first fault recovery path, where the first fault recovery path corresponds to the first working path; the second information is used to indicate that the node on the first fault recovery path has completed restoration cross-configuration based on the first information and a first corresponding relationship corresponding to the node, and the first corresponding relationship is used to indicate the corresponding relationship between the faulty sub-path, the service corresponding to the working path, and the restoration cross-indication information.

7. The method according to claim 6, wherein The method further includes: Determining, based on the topological state information of the ASON and the working paths in the ASON, a fault recovery path corresponding to each sub-path in the working path in case of a fault; Determining, based on the fault recovery paths corresponding to each sub-path in the working path, the first corresponding relationship corresponding to each node on the fault recovery path; Sending the first corresponding relationship corresponding to each node to each node on the fault recovery path.

8. The method according to claim 6 or 7, characterized in that, The method further includes: When receiving the second information sent by all nodes on the first fault recovery path, use the first fault recovery path as a new working path in the ASON.

9. The method according to any one of claims 6 to 8, characterized in that The ASON further includes a second node, and the method further includes: Determine a fault notification path corresponding to the second node based on the first node and the second node, where the nodes on the first fault recovery path include the second node; Send the fault notification path corresponding to the second node to the first node.

10. The method according to any one of claims 6 to 9, characterized in that The method further includes: When the ASON adds a new working path, update the working paths in the ASON; Based on the topological state information of the ASON and the updated working paths, determine new fault recovery paths corresponding to each sub-path in each updated working path in case of a fault; Based on the new fault recovery paths corresponding to each sub-path in each updated working path, determine new first correspondences corresponding to each node on the new fault recovery paths.

11. The method according to any one of claims 6 to 9, characterized in that The method further includes: When the first working path returns to normal, update the working paths in the ASON and update the topological state information of the ASON; Based on the updated topological state information of the ASON and the updated working paths, re-determine new fault recovery paths corresponding to each sub-path in each updated working path in case of a fault; Based on the new fault recovery paths, determine new first correspondences corresponding to each node on the new fault recovery paths.

12. The method according to any one of claims 7 to 9, characterized in that, The method further includes: When a second sub-path in the fault recovery path in the ASON fails, update the topological state information of the ASON; Based on the updated topological state information of the ASON and the working paths in the ASON, re-determine new fault recovery paths corresponding to each sub-path in each working path in case of a fault; Based on the new fault recovery paths, determine new first correspondences corresponding to each node on the new fault recovery paths.

13. The method according to any one of claims 7 to 9, characterized in that The method further includes: When the working paths in the ASON are updated and a second sub-path in the fault recovery path in the ASON fails, update the topological state information of the ASON; Based on the updated topological state information of the ASON and the updated working paths, re-determine new fault recovery paths corresponding to each sub-path in each updated working path in case of a fault; Based on the new fault recovery paths, determine new first correspondences corresponding to each node on the new fault recovery paths.

14. A fault recovery method, characterized in that, Applied to a second node in an automatically switched optical network (ASON), the ASON further includes a first node; The method includes: Receive first information sent by the first node, where the first information is used to indicate that a first sub-path in the ASON fails, and the first working path in the ASON passes through the first sub-path; the second node is a node on the first fault recovery path corresponding to the first working path; Perform restoration cross-configuration based on the first information and the first corresponding relationship corresponding to the second node; the first corresponding relationship is used to indicate the corresponding relationship between the faulty sub-path, the service corresponding to the working path, and the restoration cross-indication information.

15. The method according to claim 14, wherein The receiving the first information sent by the first node includes: Receiving the first information sent by a neighbor node of the second node, where the neighbor node obtains the first information from the first node.

16. The method according to claim 14, characterized in that, The receiving the first information sent by the first node includes: Receiving the first information sent by the first node through a fault notification path, where the fault notification path is related to the first node and the second node.

17. The method according to any one of claims 14 to 16, characterized in that, The ASON further includes a controller, and the method further includes: Receiving the first corresponding relationship corresponding to the second node sent by the controller.

18. The method according to any one of claims 14 to 17, characterized in that The ASON further includes a controller, and the method further includes: Sending second information to the controller, where the second information is used to indicate that the second node has completed restoration cross-configuration based on the first information and the first corresponding relationship corresponding to the second node.

19. A fault recovery method, characterized in that, Applied to an automatically switched optical network (ASON), the ASON includes a controller, a first node, and a second node; The method includes: The first node sends first information to the controller, where the first information is used to indicate that a first sub-path in the ASON has failed, and a first working path in the ASON passes through the first sub-path; The controller receives the first information sent by the first node; The first node sends the first information to the second node, where the second node is a node on a first fault recovery path corresponding to the first working path; The second node performs restoration cross-configuration based on the first information and the first corresponding relationship corresponding to the second node; the first corresponding relationship is used to indicate the corresponding relationship between the faulty sub-path, the service corresponding to the working path, and the restoration cross-indication information; The second node sends second information to the controller, where the second information is used to indicate that the second node has completed restoration cross-configuration based on the first information and the first corresponding relationship corresponding to the second node; The controller receives the second information sent by the second node.

20. A first node, characterized in that, The first node includes a unit or module for performing the fault recovery method according to any one of claims 1 to 5.

21. A controller, characterized in that, The controller includes a unit or module for performing the fault recovery method according to any one of claims 6 to 13.

22. A second node, characterized in that, The second node includes a unit or module for performing the fault recovery method according to any one of claims 14 to 18.

23. A fault recovery system, characterized in that, Including a first node, a controller, and a second node, where the first node is used to perform the fault recovery method according to any one of claims 1 to 5, the controller is used to perform the fault recovery method according to any one of claims 6 to 13, and the second node is used to perform the fault recovery method according to any one of claims 14 to 18.

24. A communication device, characterized in that, It includes a processor and a memory. Among them, the processor is connected to the memory. The memory is used to store program codes, and the processor is used to call the program codes to execute the fault recovery method according to any one of claims 1 to 19.

25. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the fault recovery method according to any one of claims 1 to 19.

Images