Method, system and device for removing SPC service residues in ASON network and medium

Abstract

The invention relates to the technical field of ASON networks, and provides a method which comprises the following steps: in an SPC service of an ASON network, a routing node is provided with residual state information including LSP activation, cross configuration, a deletion state and a node ID; when the LSP operation is created or deleted, the node updates own information and transmits the information to the webmaster for storage; after the LSP is created, if the LSP of the node A is not activated or cross configuration fails, service residues exist; after the LSP is deleted, if the deletion of the node A is not activated or the cross configuration fails, residues also exist; and the network manager initiates a clearing request according to the ID of the residual node A to clear the service residue. According to the invention, efficient tracking and residue removal can be realized, stable operation of the network is ensured, and the operation and maintenance efficiency and reliability of the ASON network are improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of ASON networks, and in particular, relates to a method, system, device and medium for clearing residual SPC services in an ASON network. Background Art

[0002] The ASON network is based on the Resource Reservation Protocol (RSVP) signaling interaction to control the establishment and deletion of the end-to-end Label Switching Path (LSP) of the SPC service in a distributed manner. The network management initiates an establishment or deletion request to the source node of the end-to-end LSP connection. Along the route from the source to the destination node, the network management controls the establishment or deletion of the local LSP connection and cross-connection configuration of each routing node through bidirectional RSVP signaling to complete the automatic establishment or deletion of the end-to-end LSP. The process of establishing and deleting the end-to-end LSP connection of the SPC service in the ASON network is as follows: Figure 2 , Figure 3 shown.

[0003] The process of establishing an end-to-end LSP connection for SPC services in an ASON network includes the following steps:

[0004] Process 1: The control plane of the NE1 node receives a request from the network management to establish an end-to-end LSP from the NE1 branch interface T1 to the NE3 node branch interface T1. Based on the ASON network TE topology, the LSP connection route from the source to the sink node is calculated as follows:

[0005] NE1 node (T1 interface in, E1 interface out), NE2 (W1 interface in, E1 interface out), NE3 (W1 interface in, T1 interface out), where each interface has two directions: in and out. NE1 creates an LSP for the local node, allocates a reverse ingress E1i label (NE1.E1i), and sends a PATH (C) signaling to the downstream NE2 node to create an LSP with the NE1.E1i label, and reports end-to-end LSP information to the network management, including: NE1, NE2, NE3 routing information and the inactive state of creation.

[0006] Process 2: NE2 receives the PATH(C) signaling from upstream NE1, creates LSP for N2 node, updates the reverse egress W1o label (NE2.W1o) of NE2 node according to the NE1.E1i label, allocates the reverse ingress E1i label (NE2.E1i) of NE2 node, and sends PATH(C) signaling to NE3 node to create LSP, carrying the NE2.E1i label.

[0007] Process 3: NE3 node receives PATH(C) signaling from upstream NE2, creates LSP for N3 node, updates NE3 node reverse egress W1o label (NE3.W1o) according to NE2.E1i label, determines that NE3 is LSP sink node, allocates NE3 node forward ingress W1i label (NE3.W1i), configures forward and reverse crossover of NE3 device W1i to T1o and T1i to W1o, and sends RESV signaling to upstream NE2 node to create LSP with NE3.W1i label;

[0008] Process 4: NE2 receives the RESV signaling from the downstream NE3, updates the NE2 node forward egress E1o label (NE2.E1o) according to the NE3.W1i label, allocates the NE2 node forward ingress W1i label (NE1.W1i), configures the NE2 device W1i (NE3 node forward ingress) to E1o (NE2 node forward egress) and E1i (NE2 node reverse ingress) to W1o (NE3 node reverse egress) forward and reverse crossover, and sends the RESV signaling to the NE1 node to create the LSP, carrying the NE2.W1i label;

[0009] Process 5: NE1 receives the RESV signaling from the downstream NE2, updates the forward egress E1o label (NE1.E1o) of NE1 according to the NE2.W1i label, configures the forward and reverse crossover of T1i to E1o and E1i to T1o on NE1, determines that NE1 is the LSP source node, and reports the successful creation and activation of the end-to-end LSP to the network management. The network management updates the LSP status and the establishment is completed.

[0010] The end-to-end deletion process of the ASON network SPC service LSP connection includes the following steps:

[0011] Process 1: NE1 source node control receives the request from the network management to delete the end-to-end LSP connection, reports to the network management that the end-to-end LSP is in the deletion inactive state, and NE1 sends the LSP deletion signaling PATH(D) to the downstream NE2 node;

[0012] Process 2: NE2 sends a delete LSP signaling PATH(D) to the downstream node NE3;

[0013] Process 3: The NE3 sink node receives the PATH(D) signaling, and NE3 and NE2 send PATHERR signaling to the upstream node in turn. NE3, NE2, and NE1 delete the local LSP and the device cross-connection configuration in turn.

[0014] Process 4: NE1 source node reports to the network management system that the end-to-end LSP deletion and activation is successful. The network management system deletes the LSP, and the deletion is completed.

[0015] On the Data Communication Network (DCN), the ASON network transmits RSVP control signaling, and uses PATH / RESV bidirectional RSVP signaling to distribute control services to connect all routing nodes to establish LSPs and configure forwarding plane device crossovers. It also uses PATH(D) / PATHERR bidirectional RSVP signaling to distribute control services to connect all routing nodes to delete LSPs and forwarding plane device crossovers, thereby establishing and deleting SPC end-to-end LSP connections. The following faults may occur when the ASON network distributes control to establish or delete end-to-end SPC service LSP connections:

[0016] Fault 1: During the process of establishing and deleting end-to-end LSPs, the DCN network communication or control plane program processing is abnormal, and the bidirectional RSVP signaling message interaction between nodes fails, resulting in the failure of all LSP establishment or deletion success at the routing nodes through which the LSP connection passes, and the failure of end-to-end LSP establishment or deletion. Some routing nodes generate node LSP residues, which will occupy network time slots or wavelength transmission resources, affecting the utilization of ASON network resources and subsequent service deployment.

[0017] Fault 2: When a node LSP is established or deleted, the control plane sends the configuration for establishing or deleting a cross-connection to the device single disk that serves as the transmission plane. When the single disk communication or program processing is abnormal, the device cross-connection configuration fails, resulting in residual device cross-connection. The residual cross-connection occupies the transmission plane resources. Since the control plane cannot perceive the residual device cross-connection, the subsequent creation of a new LSP that uses the residual cross-connection will cause the new SPC service LSP connection to fail, resulting in service interruption.

[0018] In addition, the ASON network manager receives connection data from the service source node to manage the end-to-end LSP connection. The connection data includes the type of service signal carried, protection recovery type, end-to-end establishment and deletion activation status, routing nodes, etc., but does not include all routing node LSP and equipment cross-configuration status data. The network manager cannot perceive and manage the LSP remnants and equipment cross-configuration remnants discretely distributed on the ASON network nodes when the above-mentioned faults occur.

[0019] When these two types of residues appear, network SPC service connection deployment or switching fails. The only way to restore service connection and network is to find and clear discrete residues node by node through service connection and equipment cross-data comparison. It is difficult to find and clear such discrete residues, which causes long-term interruption of SPC service and heavy maintenance workload, affecting the application of ASON network engineering. Summary of the invention

[0020] To solve the above problems, the present invention provides a method, system, device and medium for clearing SPC service residues in an ASON network, which adopts a method of setting residual status information in the node and updating the information and reporting it to the network management when creating and deleting LSPs. This can avoid the disadvantages of the traditional method that the network management cannot perceive the management residues and needs to compare and search for removal node by node.

[0021] The following is the technology of the present invention:

[0022] The node residual state information is set in the routing node of the ASON network SPC service, and the node residual state information includes: the LSP activation state of the node, including the LSP activated state and the LSP inactivated state; the node cross configuration state, including the cross configuration success state and the cross configuration failure state; the node deletion state, including the deletion activation state and the deletion inactivated state; the node ID;

[0023] When creating or deleting an LSP connection, each node updates its own node residual state information and transmits the updated node residual state information to the network management for storage;

[0024] After the LSP connection is created, if the LSP activation state of node A saved in the network management system is LSP inactive, or the node cross-connection configuration state of node A is cross-connection configuration failure, then there is residual SPC service on node A;

[0025] After deleting the LSP connection, if the node deletion status of node A saved in the network management system is the deletion inactive state, or the node cross-connection configuration status of node A is the cross-connection configuration failure state, then there is residual SPC service on node A;

[0026] The network management system initiates a residue clearing request based on the node ID of the node A where the SPC service residue exists, and clears the SPC service residue.

[0027] Further,

[0028] The node residual state information also includes:

[0029] The operation status of the node, including idle state, LSP creation state, and LSP deletion operation state;

[0030] The device crossover status includes the device crossover success status and the device crossover failure status. If the node device is consistent with the node control level crossover configuration, the device crossover success status is set; otherwise, the device crossover failure status is set.

[0031] Further,

[0032] When creating an LSP connection, each node updates its own node residual state information, including:

[0033] When the service connection source node receives the Create LSP message, or the non-source node receives the RSVP forward PATH (C) signaling message, the node LSP is created and the node residual state information is initialized to: LSP creation state, LSP inactive state, device cross success state;

[0034] When the sink node receives RSVP forward PATH (C) signaling or other nodes receive RESV reverse signaling messages, the node residual state information is set to the LSP activated state; the configuration and reading device crossover, if the reading device crossover fails, the crossover configuration state is set to the crossover configuration failure state; if the reading device crossover succeeds, the crossover configuration state is set to the crossover configuration success state;

[0035] If a node receives a cross-residue repair request message, it reads the cross-configuration according to the cross-backup configuration of the device, and if successful, sets the cross-configuration status to the cross-configuration success status.

[0036] Further,

[0037] When deleting an LSP connection, the node updates its own node residual state information, including:

[0038] When the service connection routing source node receives a delete LSP message, or a non-source node receives an RSVP forward PATH (D) signaling message, the node residual state information is set to: LSP deletion operation state, LSP inactive state, and cross-configuration successful state;

[0039] When the sink node receives RSVP forward PATH (D) signaling or other nodes receive PATHERR reverse signaling message, the activation state of the sink node is set to delete activation state; configure and read the device cross-connection, if the reading of the device cross-connection fails, set the cross-connection configuration state to the cross-connection configuration failure state; if the reading of the device cross-connection succeeds, set the cross-connection configuration state to the cross-connection configuration success state, and delete the cross-connection configuration backup;

[0040] If a node receives a cross-connection residual repair request message, it reads the cross-connection configuration according to the cross-connection backup configuration of the device. If successful, it sets the cross-connection configuration state to the cross-connection configuration success state and deletes the node LSP.

[0041] Further,

[0042] The network management system is provided with:

[0043] LSP connection routing node list, used to store all LSP routing nodes, the number of elements in the LSP connection routing node list is n;

[0044] The LSP activation node list is used to save the nodes whose LSP activation status is the LSP activated status. The number of elements in the LSP activation node list is m;

[0045] The cross-residual node list is used to record the nodes whose reported node cross-configuration status is the cross-configuration failure status. The number of elements in the cross-residual node list is t;

[0046] The LSP to-be-deleted node list is used to save the node deletion status of the nodes, record the deleted LSP nodes. The number of elements in the LSP to-be-deleted node list is p;

[0047] After the LSP connection operation ends, the network management receives the updated node residual status information and updates the number of elements in the LSP activation node list to m1 and the number of elements in the cross-residual node list to t1; if m1 < n or t1 > 0, there is SPC service residue;

[0048] After the LSP deletion operation ends, the network management receives the updated node residual status information and updates the number of elements in the LSP connection routing node list, the LSP to-be-deleted node list to p2, and the number of elements in the cross-residual node list to t1; if p2 < n or t1 > 0, there is SPC service residue.

[0049] Further,

[0050] If there is node LSP residue when creating an LSP connection; the clearing of the SPC service residue includes:

[0051] After the DCN communication is restored, the network management initiates residue clearing for the residual segment source node, and from the first node to the last node of the residual segment, clears all node LSP residues of the residual segment through the RSVP forward PATH(D) and reverse PATHERR bidirectional RSVP signaling.

[0052] Further,

[0053] If there is node cross-residue when creating an LSP connection; the clearing of the SPC service residue includes:

[0054] The network management issues a request to restore the node LSP cross-configuration to node B with node cross-residue;

[0055] Node B searches for the cross-configuration backup LSP-XC-BAK and issues device cross;

[0056] The cross-connection configuration of the device is read successfully, the cross-connection configuration of the LSP device is set to the cross-connection configuration success state, the cross-connection configuration backup LSP-XC-BAK is deleted, and node B reports to the network management that its node LSP has been activated and there is no cross-connection residual state information;

[0057] The network management system updates the end-to-end LSP to an activated state with no cross-link residue, thus clearing the node cross-link residue when creating the LSP connection.

[0058] A system for clearing residual SPC services in an ASON network, characterized by comprising:

[0059] A setting module is used to set node residual state information in the routing node of the ASON network SPC service, wherein the node residual state information includes: LSP activation state of the node, including LSP activated state and LSP inactivated state; node cross configuration state, including cross configuration success state and cross configuration failure state; node deletion state, including deletion activation state and deletion inactivated state; node ID;

[0060] An information transmission module, used for each node to update its own node residual state information when creating or deleting an LSP connection, and transmit the updated node residual state information to the network management for storage;

[0061] A judgment module, used for, after the LSP connection is created, if the LSP activation state of the node A saved in the network management is the LSP inactive state, or the node cross-connection configuration state of the node A is the cross-connection configuration failure state, then the node A has SPC service residual;

[0062] After deleting the LSP connection, if the node deletion status of node A saved in the network management system is the deletion inactive state, or the node cross-connection configuration status of node A is the cross-connection configuration failure state, then there is residual SPC service on node A;

[0063] The residual clearing module is used for the network management to initiate a residual clearing request to clear the SPC service residual based on the node ID of the node A where the SPC service residual exists.

[0064] An electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method.

[0065] A computer storage medium stores executable instructions, which, when executed by a processor, enable the processor to implement the method described.

[0066] Compared with the prior art, the present invention has the following advantages:

[0067] By setting node residual status information including LSP activation status, cross-configuration status, deletion status and node ID at the routing node of the SPC service in the ASON network, the node updates and uploads the status information to the network management in real time when creating or deleting LSP operations. The network management can accurately determine the service residual and initiate a clearing request based on this information.

[0068] This method realizes comprehensive recording, real-time control and effective management of node status, avoiding the disadvantages of the traditional method that the network management cannot perceive the management residue and needs to compare and search for and clear each node. In principle, it can significantly improve the efficiency of residue processing, reduce service interruption time, and reduce maintenance workload, thereby effectively solving the problems of service deployment or switching failure, long-term interruption and maintenance difficulty caused by residue in the ASON network.

[0069] Other features and advantages of the present disclosure will be described in the following description, and partly become apparent from the description, or be understood by implementing the present disclosure. The purpose and other advantages of the present disclosure can be realized and obtained by the structures pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0071] Figure 1 A schematic diagram of the method of the present invention is shown;

[0072] Figure 2 An example diagram of the process flow of establishing an end-to-end LSP connection for an SPC service in an ASON network is shown;

[0073] Figure 3 An example diagram of the process flow of end-to-end deletion of LSP connection for SPC service in ASON network is shown;

[0074] Figure 4 The figure shows an example of a method for controlling the residual state of a node when creating an LSP connection;

[0075] Figure 5 An example diagram of a method for controlling the residual state of a sensing node when deleting an LSP connection or clearing a residual segment according to the present invention is shown;

[0076] Figure 6An example flow chart of the method for automatically tracking and clearing residual LSP connections of the present invention is shown;

[0077] Figure 7 An example diagram of an automatic tracking and clearing system for SPC service LSP connection residues according to the present invention is shown;

[0078] Figure 8 The first embodiment of the present invention shows an example diagram of an implementation process of an end-to-end LSP connection residual automatic tracking algorithm;

[0079] Fig. 9 The following is a flowchart of an implementation example of a second embodiment of the present invention, in which a new end-to-end LSP is created for an SPC service, and cross-node residues are automatically tracked and cleared;

[0080] Fig.10 The third embodiment of the present invention shows an example of the implementation process of creating a new end-to-end LSP for the SPC service, and automatically tracking and clearing the node LSP residue;

[0081] Fig.11 The fourth embodiment of the present invention shows an example diagram of the implementation process of SPC service deleting end-to-end LSP, automatically tracking and clearing node cross residues;

[0082] Fig.12 The fifth embodiment of the present invention shows an example of the implementation process of the SPC service deleting the end-to-end LSP and automatically tracking and clearing the node LSP residue. DETAILED DESCRIPTION

[0083] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0084] Figure 1 A schematic diagram of the method according to the present invention is shown, and the specific implementation details of the present invention include:

[0085] 1. Step 1: Set the node residual state information in the node. When creating an LSP connection, deleting an LSP, or clearing a residual segment, the node updates its own node residual state information. The node control level perceives the node residual state information and reports the changes in the LSP connection routing node residual state to the network management.

[0086] The node residual state information includes:

[0087] Node ID;

[0088] The operation status of the node, including idle status, LSP creation status, and LSP deletion operation status;

[0089] The LSP activation status of the node, including LSP activated status and LSP inactivated status;

[0090] Node deletion status, including deletion activation status and deletion inactivation status;

[0091] The cross-connection configuration status includes the cross-connection configuration initial status, the cross-connection configuration success status, and the cross-connection configuration failure status. If the cross-connection configuration of the device and the node control level is consistent, the status is set to the success status; otherwise, the status is set to the failure status.

[0092] Specifically,

[0093] When creating an LSP connection, the node leveling method for sensing the node residual state is as follows: Figure 4 As shown:

[0094] The service connection source node receives a create LSP message, or a non-source node receives an RSVP forward PATH (C) signaling message, creates a node LSP, and initializes the node residual state to: LSP creation state, inactive state, device cross-connection success state;

[0095] When the sink node receives RSVP forward PATH (C) signaling or other nodes receive RESV reverse signaling messages, the node residual state is set to: activated state; configure and read the device cross; if the device cross reading fails, the node LSP cross configuration is set to the failed state; if the device cross reading succeeds, the cross configuration state is set to the cross configuration success state;

[0096] For a node whose cross-connect configuration is in a failed state, if a cross-connect residual repair request message is received, the cross-connect configuration is sent according to the cross-connect backup of the device, and the cross-connect configuration is read. If successful, the cross-connect configuration success state is set.

[0097] Specifically,

[0098] When an LSP connection is deleted or a residual segment is cleared, the node control leveling method to perceive the node residual state is as follows: Figure 5 As shown:

[0099] The service connection routing node receives a delete LSP message, or a non-source node receives an RSVP forward PATH (D) signaling message, and sets the node LSP to an activated state: a delete operation state, a node LSP to an inactive state, and a cross-configuration to a successful state;

[0100] The sink node receives RSVP forward PATH (D) signaling or other nodes receive PATHERR reverse signaling messages, sets the node LSP to activated state, configures and reads the device cross (delete); if reading the device cross fails, sets the node LSP cross configuration to failed state;

[0101] After receiving the cross-residue clear request message, the cross-connection (deletion) backup configuration of the device is issued, the cross-connection configuration is read, and if successful, the cross-connection configuration success status is set, and the node LSP is deleted.

[0102] 2. Step 2: The network management updates and saves the SPC service end-to-end LSP connection data, including the residual status information of all routing nodes: operation status, node LSP activation status and device cross status.

[0103] 3. Step 3: Use the residue tracking algorithm to record and track the residue status of all routing nodes, and calculate the service connection residue attributes in real time. The service connection residue attributes include: end-to-end LSP residue type, residue segment and residue node.

[0104] According to the residue properties, a one-click residue removal function is provided.

[0105] Specifically, the automatic tracking and removal of residual LSP connections includes:

[0106] Step 1:

[0107] 1) LSP creation scenario:

[0108] The network management initiates the creation of an SPC service LSP connection. Initializes the end-to-end LSP information, including the source node and the sink node;

[0109] Set the creation status and inactive status, and initiate a creation request to the service source node.

[0110] 2) LSP deletion scenario:

[0111] The network management initiates the SPC service to delete the LSP connection. The end-to-end LSP information includes all routing nodes.

[0112] Set the deleted state and inactive state.

[0113] 3) End-to-end LSP residue removal scenario:

[0114] The network management requests the LSP connection residue to be cleared according to the residue status. The LSP connection residue clearing methods include: LSP residue segment clearing, node-by-node LSP residue clearing, and cross residue clearing.

[0115] The three methods are:

[0116] Method 1: End-to-end LSP residue removal: During the process of establishing or deleting the end-to-end LSP of the SPC service, DCN communication is abnormal, causing RSVP signaling interruption and resulting in LSP residue. After the DCN communication is restored, the network management initiates residue removal at the source node of the residue segment, and removes the LSP residue of all nodes in the residue segment from the first node to the last node through RSVP forward PATH (D) and reverse PATHERR bidirectional RSVP signaling. The node reports the residue removal result to the network management;

[0117] Method 2: Clear LSP residues node by node. The network management end-to-end LSP information records the LSP residue status of each routing node. LSP residue clearing can be initiated for each node, and the node reports the LSP residue clearing result to the network management.

[0118] Method 3: Clear cross-link residuals of equipment node by node. The network management end-to-end LSP information records the cross-link residual status of each routing node equipment. Cross-link residual clearing can be initiated for each node, and the node reports the device cross-link residual clearing results to the network management.

[0119] Step 2: The network management receives the end-to-end LSP connection information reported by the source node. If it is an LSP creation scenario, the end-to-end LSP information reported by the source node includes all connected routing nodes. The end-to-end LSP, LSPs of all routing nodes, and device cross-connection are set to residual state.

[0120] Step 3: The network management receives the LSP update status data report of the routing node, updates the node LSP and the device cross-connection residual information, including: LSP establishment or deletion operation status, activated or inactivated status, cross-connection configuration success or failure status;

[0121] Step 4: Calculate the end-to-end LSP residual end according to the residual tracking algorithm and update the end-to-end LSP residual state.

[0122] Based on the above method, the present invention also provides an SPC service LSP connection residual automatic tracking and clearing system, which is composed of a network management subsystem and an ASON node control subsystem. Figure 6 shown.

[0123] 1) ASON node control subsystem, which is used to control the establishment and deletion of end-to-end LSP connections through RSVP signaling, perceive the end-to-end LSP connection and node LSP status, and report the change status to the network management in real time, and support the network management LSP residual tracking and removal function. The ASON node control subsystem includes:

[0124] The end-to-end LSP management module receives the end-to-end LSP creation, deletion and residual removal requests from the network management at the SPC service source node, manages the end-to-end LSP connection data, including LSP connection routing, establishment or deletion operation status, connection activation status, and reports status updates to the network management;

[0125] The end-to-end LSP route calculation module receives the route calculation request from the end-to-end LSP management module, calculates and returns the end-to-end LSP connection route based on the ASON network TE topology;

[0126] The node LSP management module creates and manages the local node LSP status according to the distributed control process, including the establishment or deletion operation status, whether the connection is activated, the success or failure status of the device cross-configuration, and reports the status update to the network management;

[0127] The device cross-connection configuration module receives the local node LSP cross-connection data, sends the cross-connection configuration to the local transmission device, reads the device cross-connection status, and returns the cross-connection configuration success or failure status to the node LSP management module;

[0128] The RSVP signaling module performs the bidirectional RSVP signaling function in the LSP connection establishment and deletion process.

[0129] 2) Network management subsystem, used to support the end-to-end establishment and deletion of SPC service LSP connections, receive ASON node LSP status, automatically track and calculate LSP connection residues, and support end-to-end LSP residue removal, which includes:

[0130] The end-to-end LSP connection residue display layer updates and displays the end-to-end LSP connection residue information and provides a human-machine interface for LSP residue clearing;

[0131] End-to-end LSP connection data management module manages the end-to-end LSP connection data of SPC services, receives and updates the LSP status of routing nodes, and calls the residual automatic tracking algorithm to calculate and update the end-to-end LSP connection residual in real time;

[0132] Node LSP residual management module manages routing node LSP data, receives ASON node LSP update status reports, and supports issuing node LSP residual removal configuration;

[0133] The end-to-end LSP residual automatic tracking algorithm calculates the end-to-end service connection residual in real time after the routing node LSP status is updated.

[0134] The following are specific embodiments:

[0135] 1. The following embodiment 1 is an end-to-end LSP connection residual automatic tracking algorithm implementation of the present invention, such as Figure 8 As shown, the implementation process includes:

[0136] 1) Step S01: The network management initializes end-to-end LSP residual tracking information, including:

[0137] LSP connection routing node list, including all LSP routing nodes, the number of elements is n;

[0138] LSP active node list, the number of elements is m,

[0139] Cross-residue node list, number of elements t;

[0140] When the end-to-end LSP is established or deleted for the first time, or when the residual LSP segment is cleared, the LSP active node list and the cross residual node list are cleared, m is equal to 0, and t is equal to 0;

[0141] 2) Step S02: receiving the NE node LSP activation update status report, searching the LSP activation node list and adding the NE node ID;

[0142] 3) Step S03: Calculate the end-to-end LSP residue, update the residue state, calculate the number of elements m in the LSP active node list, if m is less than n, the LSP connection is set to the residual state; calculate the LSP residual segment, if the end-to-end LSP is in the create operation state, the LSP active node list includes all residual nodes; if the end-to-end LSP is in the LSP delete operation state, the LSP active node list includes all non-residual nodes;

[0143] 4) Step S04: The network management receives the NE node cross-connection configuration status report;

[0144] 5) Step S05: Determine whether the NE node cross-connection configuration is successful, if yes, go to step S07, if no, go to step S06;

[0145] 6) Step S06: search and add NE node ID in the cross-residual node list;

[0146] 7) Step S07: searching and deleting the NE node ID in the cross-residual node list;

[0147] 8) Step S08: Update the LSP cross residual state, calculate the number of elements t in the cross residual node list, and if t is greater than 0, the LSP connection is set to the residual state.

[0148] The network management cross-residual node list records all cross-residual node IDs of LSP connections. You can clear cross-residual nodes according to the list records.

[0149] The end-to-end LSP connection residual automatic tracking algorithm of Example 1 is adopted. The following four examples are used to illustrate the automatic tracking and clearing of LSP and device cross-residues for newly created and deleted SPC service connections. The LSP connections of these four examples pass through three routing nodes: NE1 (source), NE2 (middle), and NE3 (destination).

[0150] 2. Embodiment 2: An example of the implementation process of the SPC service of the present invention to create an end-to-end LSP, automatically track and clear node cross residues, such as Fig. 9 As shown, the process includes:

[0151] Step S10: The network management creates service LSP connection information. NE1 and NE3 are end-to-end LSP source and sink nodes, and the LSP is in a newly created and unactivated state.

[0152] Step S11, the NE1 source node receives the LSP creation request, creates an end-to-end LSP, calculates the LSP route, passes through the NE1, NE2, and NE3 nodes in sequence, and reports the end-to-end LSP information to the network management, including the route information and the inactivated status;

[0153] Step S12, the network management initializes the end-to-end LSP residual tracking information, creates an LSP routing node list containing three elements NE1, NE2, and NE3 (the number of elements n=3), creates an empty LSP activation node list (the number of elements m=0), and creates a cross residual node list containing three elements NE1, NE2, and NE3 (the number of elements t=3). Since n>m, it is calculated that the end-to-end LSP is in a residual inactive state, and the NE1, NE2, and NE3 nodes are residual. NE1 and NE3 are the first and last nodes of the residual segment respectively;

[0154] Step S13, LSP connection distributed control RSVP forward PATH signaling process, along the LSP route, NE1, NE2, NE3 node control level sequentially create node LSP, reserve interface transmission resources (time slot or wavelength), set the node LSP to inactive state, set the device crossover to successful state (when the device crossover configuration is consistent with the crossover data of the current node LSP, the device crossover is determined to be successful), transmit RSVP signaling PATH message to the downstream node, NE1, NE2, NE3 report the node LSP state to the network management, and the network management updates the end-to-end LSP residual tracking information;

[0155] Step S14, LSP connection distributed control RSVP reverse RESV signaling process:

[0156] NE3 allocates interface transmission resources, sends RSVP signaling RESV message to upstream NE2 node, sets NE3 node LSP to activated state, sets backup cross-connection configuration to LSP-XC-BAK, configures and reads device cross-connection successfully, sets LSP device cross-connection configuration to successful state, deletes cross-connection configuration backup LSP-XC-BAK, and reports to the network management that NE3 node LSP has been activated and no cross-connection remains.

[0157] NE2 receives the RESV message, allocates interface transmission resources, sends RSVP signaling RESV message to the upstream NE1 node, sets the NE2 node LSP to activated state, sets the backup cross-connection configuration to LSP-XC-BAK, fails to configure and read the device cross-connection configuration, sets the LSP device cross-connection configuration to failed state, and reports to the network management that the NE3 node LSP has been activated and there is a cross-connection residual state information;

[0158] NE1 receives the RESV message, allocates interface transmission resources, sets the NE2 node LSP to the activated state, sets the backup cross-connection configuration to LSP-XC-BAK, configures and reads the device cross-connection configuration successfully, sets the LSP device cross-connection configuration to the successful state, deletes the cross-connection configuration backup LSP-XC-BAK, and reports to the network management that the NE1 node LSP has been activated and there is no cross-connection residual state information;

[0159] NE3, NE2, and NE1 report the node LSP status to the network management system, and the network management system updates the end-to-end LSP residual tracking information;

[0160] NE1 sets the end-to-end LSP status to activated and reports it to the network management system. The network management system updates the end-to-end LSP status.

[0161] Step S15: The network management receives the node LSP and cross-residual status information reported by the NE3, NE2, and NE1 nodes, calculates the cross-residual of the NE2 node according to the residual tracking algorithm, and updates the end-to-end LSP residual status;

[0162] Step S16, create LSP cross residue clearing, NE2 node receives the network management restoration node LSP cross configuration request, NE2 finds the LSP-XC-BAK backup configuration and sends the device cross, reads the device cross configuration successfully, sets the LSP device cross configuration to a successful state, deletes the cross configuration backup LSP-XC-BAK, reports to the network management that the NE2 node LSP has been activated and there is no cross residue status information, the network management updates the end-to-end LSP to an activated state with no cross residue status, and completes the new LSP quick repair.

[0163] 3. Example 3: This is an example of the implementation process of the SPC service of the present invention to create an end-to-end LSP, automatically track and clear the node LSP residue, such as Fig.10 As shown, the process includes:

[0164] Steps S20 to S23 are the same as steps S10 to S13 in Example 2;

[0165] Step S24, LSP connection distributed control RSVP reverse RESV signaling process:

[0166] NE3 allocates interface transmission resources, sends RSVP signaling RESV message to upstream NE2 node, sets NE3 node LSP to activated state, sets backup cross-connection configuration to LSP-XC-BAK, configures and reads device cross-connection successfully, sets LSP device cross-connection configuration to successful state, deletes cross-connection configuration backup LSP-XC-BAK, and reports to the network management that NE3 node LSP has been activated and no cross-connection remains.

[0167] NE2 receives the RESV message, allocates interface transmission resources, sends RSVP signaling RESV message to the upstream NE1 node, sets the NE2 node LSP to activated state, sets the backup cross-connection configuration to LSP-XC-BAK, configures and reads the device cross-connection successfully, sets the LSP device cross-connection configuration to successful state, deletes the cross-connection configuration backup LSP-XC-BAK, and reports to the network management that the NE2 node LSP has been activated and there is no cross-connection residual state information;

[0168] Due to abnormal DCN network communication, the NE1 node LSP cannot be created and activated. Only NE3 and NE2 report to the network management that the node LSP has been activated and there is no cross-residual status. The network management updates the end-to-end LSP residual tracking information.

[0169] Step S25: The network management receives the node LSP and cross-residual status information reported by the NE3 and NE2 nodes, calculates the LSP remnant of NE1 according to the remnant tracking algorithm, and updates the end-to-end LSP remnant status;

[0170] Step S26, delete the residual end-to-end LSP to be built, the network management requests to delete the end-to-end LSP, update the residual tracking information of the end-to-end LSP, the LSP routing node list containing the three elements NE1, NE2, and NE3 (the number of elements n=3) remains unchanged, create an empty LSP activation node list (the number of elements m=0), clear and add the cross residual node list of the three elements NE1, NE2, and NE3 (the number of elements t=3), because n>m, calculate that the end-to-end LSP is in the residual state to be deleted, NE1, NE2, and NE3 nodes LSP is residual, NE1 and NE3 are the first and last nodes of the LSP residual segment respectively, and the network management requests NE1 to delete the end-to-end residual LSP to be built;

[0171] Step S27, LSP connection distributed control RSVP forward PATH (D) signaling process, along the LSP route, NE1, NE2, NE3 node control level sequentially set the node LSP to be deleted state, the device cross-connection to the success state, transmit RSVP signaling PATHERR message to the downstream node, NE1, NE2, NE3 report the node LSP to be deleted state to the network management, and the network management updates the end-to-end LSP residual tracking information;

[0172] Step S28, LSP connection distributed control RSVP reverse PATHERR signaling process:

[0173] NE3 releases the interface transmission resources, sends an RSVP signaling PATHERR message to the upstream NE2 node, sets the NE3 node LSP to the deletion activation state, sets the backup cross-connection configuration to LSP-XC-BAK, configures and reads the device cross-connection successfully, sets the LSP device cross-connection configuration to the success state, deletes the cross-connection configuration backup LSP-XC-BAK, and reports to the network management that the NE3 node LSP has been deleted and there is no cross-connection remaining state information;

[0174] NE2 receives the PATHERR message, releases the interface transmission resources, sends an RSVP signaling PATHERR message to the upstream NE1 node, sets the NE2 node LSP to the deletion activation state, sets the backup cross-connection configuration to LSP-XC-BAK, fails to configure and read the device cross-connection configuration, sets the LSP device cross-connection configuration to the failure state, and reports to the network management that the NE2 node LSP has been deleted and there is a cross-connection residual state information;

[0175] NE1 receives the PATHERR message and releases the interface transmission resources. It checks and finds that the LSP creation of NE1 is inactive. It sets the LSP of NE1 to the deletion activation state and the LSP device cross-connection configuration to the success state. It reports to the network management that the LSP of NE1 has been deleted and there is no cross-connection remaining.

[0176] NE3, NE2, and NE1 report the node LSP status to the network management system, and the network management system updates the end-to-end LSP residual tracking information;

[0177] Step S29: Delete the end-to-end LSP information. The network manager requests NE1 to delete the end-to-end LSP. NE1 reports the end-to-end LSP deletion status to the network manager. The network manager deletes the end-to-end LSP.

[0178] When a new end-to-end LSP connection is created in the above process and LSP residues are generated, the network management system tracks and calculates the residue status to realize automatic LSP residue removal.

[0179] 4. Example 4: This is an example of the implementation process of the SPC service of the present invention deleting the end-to-end LSP, automatically tracking and clearing the node cross residues, such as Fig.11As shown, the process includes:

[0180] Step S30: The network management initiates end-to-end deletion of the LSP connection, NE1 and NE3 are the source and sink nodes of the LSP to be deleted, and NE2 is the intermediate node;

[0181] Step S31, the source node NE1 receives the end-to-end LSP deletion request, sets and reports the end-to-end LSP pending deletion status to the network management;

[0182] Step S32, the network management initializes the end-to-end LSP residual tracking information, the end-to-end LSP information includes the LSP routing node list of the three elements NE1, NE2, and NE3 (the number of elements n=3), creates an empty LSP node list to be deleted (the number of elements m=0), and creates a cross residual node list including the three elements NE1, NE2, and NE3 (the number of elements t=3). Since n>m, it is calculated that the end-to-end LSP is in the residual state to be deleted, and the LSP of the nodes NE1, NE2, and NE3 is residual. NE1 and NE3 are the head and tail nodes of the LSP residual segment respectively;

[0183] Step S33, LSP connection distributed control RSVP forward PATH (D) signaling process, along the LSP route, NE1, NE2, NE3 node control level sequentially set the node LSP to be deleted state, the device cross-connection to the success state, transmit RSVP signaling PATHERR message to the downstream node, NE1, NE2, NE3 report the node LSP to be deleted state to the network management, and the network management updates the end-to-end LSP residual tracking information;

[0184] Step S34, LSP connection distributed control RSVP reverse PATHERR signaling process:

[0185] NE3 releases the interface transmission resources, sends an RSVP signaling PATHERR message to the upstream NE2 node, sets the NE3 node LSP to the deletion activation state, sets the backup cross-connection configuration to LSP-XC-BAK, configures and reads the device cross-connection successfully, sets the LSP device cross-connection configuration to the success state, deletes the cross-connection configuration backup LSP-XC-BAK, and reports to the network management that the NE3 node LSP has been deleted and there is no cross-connection remaining state information;

[0186] NE2 receives the PATHERR message, releases the interface transmission resources, sends an RSVP signaling PATHERR message to the upstream NE1 node, sets the NE2 node LSP to the deletion activation state, sets the backup cross-connection configuration to LSP-XC-BAK, fails to configure and read the device cross-connection configuration, sets the LSP device cross-connection configuration to the failure state, and reports to the network management that the NE2 node LSP has been deleted and there is a cross-connection residual state information;

[0187] NE1 receives the PATHERR message, releases the interface transmission resources, sets the NE1 node LSP to the deleted state, sets the backup cross-connection configuration to LSP-XC-BAK, configures and reads the device cross-connection configuration successfully, sets the LSP device cross-connection configuration to the successful state, deletes the cross-connection configuration backup LSP-XC-BAK, and reports to the network management that the NE1 node LSP has been deleted, activated, and has no cross-connection remaining status information;

[0188] NE3, NE2, and NE1 report the node LSP status to the network management system, and the network management system updates the end-to-end LSP residual tracking information;

[0189] Step S35: The network management receives the node LSP and cross-residual status information reported by the NE3, NE2, and NE1 nodes, calculates the cross-residual of the NE2 node according to the residual tracking algorithm, and updates the end-to-end LSP to be deleted and the NE2 cross-residual state;

[0190] Step S36, delete the LSP cross residue and clear it. The network manager requests the NE2 node to restore the node LSP cross configuration. NE2 finds the LSP-XC-BAK backup configuration and sends the device cross configuration. The device cross configuration is read successfully. The LSP device cross configuration is set to a successful state. The cross configuration backup LSP-XC-BAK is deleted, the node LSP is deleted, and the NE2 node LSP is reported to the network manager. The network manager deletes the end-to-end LSP.

[0191] 5. Example 5: This is an example of the implementation process of the SPC service of the present invention deleting the end-to-end LSP, automatically tracking and clearing the node LSP residue, such as Fig.12 As shown, the process includes:

[0192] Steps S40 to S43 are the same as steps S30 to S33 of the third embodiment;

[0193] Step S44, LSP connection distributed control RSVP reverse PATHERR signaling process:

[0194] NE3 releases the interface transmission resources, sends an RSVP signaling PATHERR message to the upstream NE2 node, sets the NE3 node LSP to the deletion activation state, sets the backup cross-connection configuration to LSP-XC-BAK, configures and reads the device cross-connection successfully, sets the LSP device cross-connection configuration to the success state, deletes the cross-connection configuration backup LSP-XC-BAK, deletes the NE3 node LSP, and reports to the network management that the NE3 node LSP has been deleted and there is no cross-connection remaining state information;

[0195] NE2 releases the interface transmission resources, sends an RSVP signaling PATHERR message to the upstream NE1 node, sets the NE2 node LSP to the deletion activation state, sets the backup cross-connection configuration to LSP-XC-BAK, configures and reads the device cross-connection successfully, sets the LSP device cross-connection configuration to the success state, deletes the cross-connection configuration backup LSP-XC-BAK, deletes the NE3 node LSP, and reports to the network management that the NE2 node LSP has been deleted and there is no cross-connection remaining state information;

[0196] Due to DCN network anomalies, the communication between NE1 and NE2 nodes is interrupted. NE1 node cannot receive the PATHERR signaling message sent by NE2 node, and NE1 node LSP cannot be deleted and activated. The network management only receives reports from NE3 and NE2 that the node LSP has been deleted and activated and there is no cross-residual status. The network management updates the end-to-end LSP residual tracking information;

[0197] Step S45, the network management calculates the end-to-end LSP status (deleted, inactivated) and the residual (NE1 node LSP residual);

[0198] Step S46: Clear the end-to-end LSP residue to be deleted, and send a residue clearing command message to the head node of the residue segment;

[0199] Step S47, LSP connection distributed control RSVP forward PATH (D) signaling process:

[0200] NE1 finds that the next-hop LSP route is NE2, and NE2 searches for a node LSP that is empty.

[0201] Step S48, LSP connection distributed control RSVP reverse PATHERR signaling process:

[0202] NE2 returns a PATHERR message to the upstream NE1;

[0203] NE1 releases LSP interface resources, backs up and deletes cross-connection configuration LSP-XC-BAK, sends cross-connection to devices, reads cross-connection configuration successfully, deletes cross-connection backup LSP-XC-BAK, deletes node LSP, and reports to the network management system that NE1 node LSP deletion has been activated.

[0204] The network management updates the end-to-end LSP residual tracking information, and the NE1 node LSP has been deleted;

[0205] Step S49, deleting the end-to-end LSP. The network management sends a request message to delete the end-to-end LSP to be established to the NE1 node. After deleting the end-to-end LSP, NE1 reports to the network management, and the network management deletes the end-to-end LSP.

[0206] Based on the method of the present invention, the embodiment of the present disclosure also provides a system for clearing residual SPC services in an ASON network corresponding to the above method, which includes:

[0207] A setting module, used to set node residual state information in the routing node of the ASON network SPC service, wherein the node residual state information includes: LSP activation state of the node, node cross configuration state, node deletion state, and node ID;

[0208] An information transmission module, used for each node to update its own node residual state information when creating or deleting an LSP connection, and transmit the updated node residual state information to the network management for storage;

[0209] A judgment module, used for, after the LSP connection is created, if the LSP activation state of the node A saved in the network management is the LSP inactive state, or the node cross-connection configuration state of the node A is the cross-connection configuration failure state, then the node A has SPC service residual;

[0210] After deleting the LSP connection, if the node deletion status of node A saved in the network management system is the deletion inactive state, or the node cross-connection configuration status of node A is the cross-connection configuration failure state, then there is residual SPC service on node A;

[0211] The residual clearing module is used for the network management to initiate a residual clearing request to clear the SPC service residual based on the node ID of the node A where the SPC service residual exists.

[0212] Based on the same inventive concept as the above disclosed content, an embodiment of the present disclosure also provides a device corresponding to the above method, which includes at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the above method.

[0213] It should be noted that the electrical connection between the above-mentioned units does not necessarily mean the connection between lines. An indirect connection method can be applied to the embodiments of the present disclosure as long as the purpose of the present disclosure is achieved.

[0214] Based on the same inventive concept, the present disclosure also provides a computer storage medium on which executable instructions are stored. When the instructions are executed by a processor, the processor performs the above method.

[0215] Although the present disclosure has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure.

Claims

1. A method for clearing residual SPC services in an ASON network, characterized in that: include: The node residual state information is set in the routing node of the ASON network SPC service, and the node residual state information includes: the LSP activation state of the node, including the LSP activated state and the LSP inactivated state; the node cross configuration state, including the cross configuration success state and the cross configuration failure state; the node deletion state, including the deletion activation state and the deletion inactivated state; the node ID; When creating or deleting an LSP connection, each node updates its own node residual state information and transmits the updated node residual state information to the network management for storage; After the LSP connection is created, if the LSP activation state of node A saved in the network management system is LSP inactive, or the node cross-connection configuration state of node A is cross-connection configuration failure, then there is residual SPC service on node A; After deleting the LSP connection, if the node deletion status of node A saved in the network management system is the deletion inactive state, or the node cross-connection configuration status of node A is the cross-connection configuration failure state, then there is residual SPC service on node A; The network management system initiates a residue clearing request based on the node ID of the node A where the SPC service residue exists, and clears the SPC service residue.

2. A method for clearing residual SPC services in an ASON network according to claim 1, characterized in that: The node residual state information also includes: The operation status of the node, including idle status, LSP creation status, and LSP deletion operation status; The device crossover status includes the device crossover success status and the device crossover failure status. If the node device is consistent with the node control level crossover configuration, the device crossover success status is set; otherwise, the device crossover failure status is set.

3. A method for clearing residual SPC services in an ASON network according to claim 2, characterized in that: When creating an LSP connection, each node updates its own node residual state information, including: When the service connection source node receives the Create LSP message, or the non-source node receives the RSVP forward PATH (C) signaling message, the node LSP is created and the node residual state information is initialized to: LSP creation state, LSP inactive state, device cross success state; When the sink node receives RSVP forward PATH (C) signaling or other nodes receive RESV reverse signaling messages, the node residual state information is set to the LSP activated state; the configuration and reading device crossover, if the reading device crossover fails, the crossover configuration state is set to the crossover configuration failure state; if the reading device crossover succeeds, the crossover configuration state is set to the crossover configuration success state; If a node receives a cross-residue repair request message, it reads the cross-configuration according to the cross-backup configuration of the device, and if successful, sets the cross-configuration status to the cross-configuration success status.

4. The method for clearing residual SPC services in an ASON network according to claim 2, characterized in that: When deleting an LSP connection, the node updates its own node residual state information, including: When the service connection routing source node receives a delete LSP message, or a non-source node receives an RSVP forward PATH (D) signaling message, the node residual state information is set to: LSP deletion operation state, LSP inactive state, and cross-configuration successful state; When the sink node receives the RSVP positive PATH(D) signaling or other nodes receive the PATHERR reverse signaling message, set the activation status of the sink node to the deleted activation status; configure and read the device cross-connect. If the device cross-connect reading fails, set the cross-connect configuration status to the cross-connect configuration failure status; if the device cross-connect reading is successful, set the cross-connect configuration status to the cross-connect configuration success status and delete the cross-connect configuration backup. If a node receives a cross-residual repair request message, configure and issue the configuration according to the device cross-connect backup, read the cross-connect configuration. If successful, set the cross-connect configuration status to the cross-connect configuration success status and delete the node LSP.

5. The method for clearing residual SPC services in an ASON network according to claim 1, characterized in that: The network management system is provided with: An LSP connection routing node list for storing all routing nodes of the LSP. The number of elements in the LSP connection routing node list is n; An LSP activation node list for storing nodes with the LSP activation status of the LSP being activated. The number of elements in the LSP activation node list is m; A cross-residual node list for recording nodes with the reported node cross-connect configuration status of the cross-connect configuration failure status. The number of elements in the cross-residual node list is t; An LSP to-be-deleted node list for storing the node deletion status of the node and recording the deleted LSP nodes. The number of elements in the LSP to-be-deleted node list is p; After the LSP connection operation is completed, the network management system receives the updated node residual status information and updates the number of elements in the LSP activation node list to m1 and the number of elements in the cross-residual node list to t1; if m1 < n or t1 > 0, there is SPC service residue. After the LSP deletion operation is completed, the network management system receives the updated node residual status information and updates the number of elements in the LSP connection routing node list, the LSP to-be-deleted node list to p2, and the number of elements in the cross-residual node list to t1; if p2 < n or t1 > 0, there is SPC service residue.

6. The method for clearing residual SPC services in an ASON network according to claim 1, characterized in that: If there is node LSP residue when creating an LSP connection; the clearing of the SPC service residue includes: After the DCN communication is restored, the network management system initiates residue clearing for the residue segment source node. From the first node to the last node of the residue segment, all node LSP residues of the residue segment are cleared through the RSVP positive PATH(D) and reverse PATHERR bidirectional RSVP signaling.

7. The method for clearing residual SPC services in an ASON network according to claim 1, characterized in that: If there is node cross-residual when creating an LSP connection; the clearing of the SPC service residue includes: The network management system issues a request to restore the node LSP cross-connect configuration to node B with node cross-residual; Node B searches for the cross-connect configuration backup LSP-XC-BAK and issues the device cross-connect; If the device cross-connect configuration reading is successful, set the LSP device cross-connect configuration to the cross-connect configuration success status, delete the cross-connect configuration backup LSP-XC-BAK, and node B reports to the network management system its node LSP has been activated and there is no cross-residual status information; The network management system updates the end-to-end LSP to the activated and cross-residual-free status, and completes the clearing of the node cross-residual when creating the LSP connection.

8. A system for clearing residual SPC services in an ASON network, characterized in that: Including: A setting module is used to set node residual state information in the routing node of the ASON network SPC service, wherein the node residual state information includes: LSP activation state of the node, including LSP activated state and LSP inactivated state; node cross configuration state, including cross configuration success state and cross configuration failure state; node deletion state, including deletion activation state and deletion inactivated state; node ID; An information transmission module, used for each node to update its own node residual state information when creating or deleting an LSP connection, and transmit the updated node residual state information to the network management for storage; A judgment module, used for, after the LSP connection is created, if the LSP activation state of the node A saved in the network management is the LSP inactive state, or the node cross-connection configuration state of the node A is the cross-connection configuration failure state, then the node A has SPC service residual; After deleting the LSP connection, if the node deletion status of node A saved in the network management system is the deletion inactive state, or the node cross-connection configuration status of node A is the cross-connection configuration failure state, then there is residual SPC service on node A; The residual clearing module is used for the network management to initiate a residual clearing request to clear the SPC service residual based on the node ID of the node A where the SPC service residual exists.

9. An electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method for clearing residual SPC services in the ASON network as described in any one of claims 1 to 7.

10. A computer storage medium having executable instructions stored thereon, wherein when the instructions are executed by a processor, the processor is enabled to implement the method according to any one of claims 1 to 7.

Images