Method, system and device for clearing residual SPC service of ASON network and medium

Abstract

The present disclosure relates to the technical field of ASON network, and provides a method, which comprises: in an ASON network SPC service, a routing node containing residual state information of LSP activation, cross configuration, deletion state and node ID; when creating or deleting an LSP operation, the node updates its own information and transmits the information to a network management for storage; after creating an LSP, if LSP of node A is not activated or cross configuration fails, there is service residual; after deleting an LSP, if node A deletion is not activated or cross configuration fails, there is also residual; the network management initiates a clearing request according to the ID of node A with residual to clear the service residual. The present application can realize efficient tracking and clearing of residual, ensure stable operation of the network, and improve operation and maintenance efficiency and reliability of the ASON network.

Description

Technical Field

[0001] The present disclosure 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 uses Resource Reservation Protocol (RSVP) signaling to interactively control the establishment and deletion of end-to-end Label Switching Paths (LSPs) for SPC services. The network management initiates an establishment or deletion request to the source node of the end-to-end LSP connection. From the source to the destination node, the network management controls the establishment or deletion of local LSP connections and cross-connect configurations at each routing node through bidirectional RSVP signaling, completing the automatic establishment or deletion of end-to-end LSPs. The process of establishing and deleting an end-to-end LSP connection for SPC services in the ASON network is as follows: Figure 2 、 Figure 3 shown.

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

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

[0005] NE1 (T1 interface inbound, E1 interface outbound), NE2 (W1 interface inbound, E1 interface outbound), and NE3 (W1 interface inbound, T1 interface outbound). Each interface has both inbound and outbound directions. NE1 creates an LSP on its own node, assigns a reverse inbound E1i label (NE1.E1i), and sends a PATH (C) signaling message carrying the NE1.E1i label to the downstream NE2 node to create the LSP. This message then reports end-to-end LSP information to the network management system, including NE1, NE2, and NE3 routing information and the inactive state of the LSP.

[0006] Process 2: NE2 receives the PATH(C) signaling from upstream NE1, establishes an LSP on N2, updates NE2's reverse egress W1o label (NE2.W1o) based on the NE1.E1i label, assigns NE2's reverse ingress E1i label (NE2.E1i), and sends a PATH(C) signaling to NE3 to establish the LSP, carrying the NE2.E1i label.

[0007] Process 3: NE3 receives PATH(C) signaling from upstream NE2 and establishes an LSP on N3. It updates NE3's reverse egress W1o label (NE3.W1o) based on the NE2.E1i label. After determining that NE3 is the LSP sink, it assigns NE3's forward ingress W1i label (NE3.W1i). NE3 configures forward and reverse crossover between W1i and T1o, and between T1i and W1o. It then sends a RESV signaling message to the upstream NE2, carrying the NE3.W1i label, to establish the LSP.

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

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

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

[0011] Process 1: NE1 source node controller receives a request from the network management system to delete an end-to-end LSP connection. It reports to the network management system that the end-to-end LSP is in the inactive state. NE1 then sends a PATH(D) LSP deletion signaling message to the downstream NE2 node.

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

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

[0014] In process 4, the source node NE1 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 complete.

[0015] On the Data Communication Network (DCN), the ASON network transmits RSVP control signaling. It uses PATH / RESV bidirectional RSVP signaling to distribute control services across 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 across all routing nodes to delete LSPs and configure forwarding plane device crossovers, enabling the establishment and deletion of 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 end-to-end LSP establishment and deletion process, DCN network communication or control plane program processing anomalies caused bidirectional RSVP signaling between nodes to fail. This prevented LSP establishment or deletion at all routing nodes along the LSP connection, leading to end-to-end LSP establishment or deletion failure. This resulted in residual LSPs on some routing nodes, which occupied network time slots or wavelength transmission resources, impacting ASON network resource utilization 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 cross-connection to the device disk serving as the transport plane. When the single-disk communication or program processing is abnormal, the device cross-connection configuration fails, resulting in residual cross-connection. The residual cross-connection occupies transport plane resources. Since the control plane cannot perceive the residual cross-connection, the subsequent use of the residual cross-connection by a newly created LSP will cause the new SPC service LSP connection to fail, resulting in service interruption.

[0018] In addition, the ASON network management 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 and restoration type, end-to-end establishment and deletion activation status, routing nodes, etc., but does not include all routing node LSP and device cross-configuration status data. The network management cannot perceive and manage the LSP residues and device cross-configuration residues discretely distributed on the ASON network nodes when the above-mentioned faults occur.

[0019] When these two types of residues occur, network SPC service connection deployment or switchover fails. Service connection and network recovery can only be achieved by comparing service connections and device cross-data, and finding and clearing discrete residues node by node. However, finding and clearing these discrete residues is difficult to maintain, resulting in long SPC service interruptions and a heavy maintenance workload, which impacts the application of ASON network engineering. Summary of the Invention

[0020] To address the above-mentioned issues, the present disclosure provides a method, system, device, and medium for clearing residual SPC services in an ASON network. By setting residual status information in the node and updating the information and reporting it to the network manager when creating and deleting LSPs, the present disclosure avoids the drawbacks of the traditional method where the network manager cannot perceive the residual services and needs to conduct node-by-node comparison and removal.

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

[0022] Setting node residual state information in the routing node of the ASON network SPC service, 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;

[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 established, if the LSP activation status of node A saved in the network management system is LSP inactive, or the cross-connection configuration status of node A is cross-connection configuration failed, SPC services are still present on node A.

[0025] After deleting the LSP connection, if the node deletion status of node A saved in the network management system is "deletion inactive" or the node cross-connection configuration status of node A is "cross-connection configuration failed", then SPC services remain on node A.

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

[0027] Furthermore,

[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] Device cross-connection status, including device cross-connection success status and device cross-connection failure status. If the node device is consistent with the node control level cross-connection configuration, the device cross-connection success status is set; otherwise, the device cross-connection failure status is set.

[0031] Furthermore,

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

[0033] When the service connection source node receives a Create LSP message, or a non-source node receives an RSVP forward PATH(C) signaling message, it creates a node LSP and initializes the node's residual state information to: LSP creation state, LSP inactive state, and device crossover 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 cross-connection between the configuration and the reading device is configured. If the cross-connection between the reading device fails, the cross-connection configuration state is set to the cross-connection configuration failure state; if the cross-connection between the reading device succeeds, the cross-connection configuration state is set to the cross-connection configuration success state;

[0035] If a node receives a cross-residual 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] Furthermore,

[0037] When deleting an LSP connection, a node updates its residual node state information. This includes:

[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's residual status information is set to: LSP delete operation status, LSP inactive status, and cross-configuration successful status;

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

[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 issued by the device. If successful, it sets the cross-connection configuration status to the cross-connection configuration success status and deletes the node LSP.

[0041] Furthermore,

[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] Furthermore,

[0050] If there is node LSP residue when creating the 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, from the head node to the end node of the residual segment, and clears all node LSP residues of the residual segment through the RSVP forward PATH(D) and reverse PATHERR bidirectional RSVP signaling.

[0052] Furthermore,

[0053] If there is node cross residue when creating the 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 system that its node LSP is activated and no cross-connection remains.

[0057] The network management system updates the end-to-end LSP to an activated, no-crossing residual state, thus clearing the node cross-linking residuals during LSP connection creation.

[0058] A system for clearing residual SPC services in an ASON network, 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 is used to update the residual state information of each node when creating or deleting an LSP connection, and transmit the updated residual state information to the network management for storage;

[0061] The judgment module is configured to determine that after the LSP connection is established, if the LSP activation state of node A stored in the network management system is an LSP inactive state, or the node cross-connection configuration state of node A is a cross-connection configuration failure state, then there is an SPC service residual on node A;

[0062] After deleting the LSP connection, if the node deletion status of node A saved in the network management system is "deletion inactive" or the node cross-connection configuration status of node A is "cross-connection configuration failed", then SPC services remain on node A.

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

[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 perform the method.

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

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

[0067] By setting node residual status information including LSP activation status, cross-connection configuration status, deletion status and node ID at the routing nodes of the ASON network SPC service, 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 then accurately determine the residual service and initiate a removal request based on this information.

[0068] This approach achieves comprehensive recording, real-time control and effective management of node status, avoiding the drawbacks of traditional methods where network managers are unable to perceive management residues and need to compare and search for and clear them node by node. In principle, it can significantly improve residue processing efficiency, reduce service interruption time, and reduce maintenance workload, thereby effectively solving problems such as service deployment or switching failures, long-term interruptions and maintenance difficulties caused by residues in ASON networks.

[0069] Other features and advantages of the present disclosure will be described in the following description, and in part will become apparent from the description, or will be understood by practicing the present disclosure. The purposes and other advantages of the present disclosure can be realized and obtained by the structures indicated 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 following briefly introduces the drawings required for use in the embodiments or the description of the prior art. 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 Shown is a schematic diagram of the method of the present invention;

[0072] Figure 2 This figure shows an example of the process flow of establishing an end-to-end LSP connection for SPC services in an ASON network;

[0073] Figure 3 This diagram shows an example of the process flow of deleting an LSP connection end-to-end for an SPC service in an ASON network;

[0074] Figure 4 The figure shows an example of a method for controlling the residual state of a sensing node when establishing 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 6A flowchart illustrating an example of a method for automatically tracking and clearing residual LSP connections according to 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 FIG2 shows an example flow chart of an end-to-end LSP connection residual automatic tracking algorithm implementation process according to the first embodiment of the present invention;

[0079] Figure 9 This figure shows an example flow chart of the implementation of the second embodiment of the present invention, which is to create a new end-to-end LSP for the SPC service and automatically track and clear node cross residues.

[0080] Figure 10 This section shows an example of the implementation process of creating a new end-to-end LSP for an SPC service and automatically tracking and clearing residual node LSPs in the third embodiment of the present invention.

[0081] Figure 11 This figure shows an example flow chart of an implementation of the fourth embodiment of the present invention, in which an SPC service deletes an end-to-end LSP and automatically tracks and clears node cross residues.

[0082] Figure 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] To make the objectives, technical solutions, and advantages of the embodiments of the present disclosure more clear, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present disclosure without making any creative efforts shall fall 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 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 state, LSP creation state, and LSP deletion operation state;

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

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

[0091] Cross-connect configuration status, including cross-connect configuration initial status, cross-connect configuration success status, and cross-connect configuration failure status. If the cross-connect configuration of the device and the node leveling is consistent, the status is set to success; otherwise, the status is set to failure.

[0092] Specifically,

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

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

[0095] When the sink node receives RSVP forward PATH(C) signaling or other nodes receive RESV reverse signaling, it sets the node's residual state to activated; configures and reads the device cross-connection; if the device cross-connection reading fails, sets the node's LSP cross-connection configuration to failed; if the device cross-connection reading succeeds, sets the cross-connection configuration state to successful.

[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 read according to the cross-connect backup configuration of the device. If successful, the cross-connect configuration is set to a successful state.

[0097] Specifically,

[0098] When deleting an LSP connection or clearing a residual segment, the node leveling method for sensing the node residual state is as follows: Figure 5 As shown:

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

[0100] When the sink node receives RSVP forward PATH(D) signaling or another node receives PATHERR reverse signaling, it sets the node LSP to activated state, configures and reads the device cross-connect (deletes); if reading the device cross-connect fails, it sets the node LSP cross-connect configuration to failed state.

[0101] Upon receiving the cross-residue clear request message, the device reads the cross-configuration according to the cross-configuration (deletion) backup configuration. If successful, the cross-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-connection 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 residual properties, a one-click residual 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 system initiates the creation of an SPC service LSP connection. Initializes end-to-end LSP information, including the source and sink nodes.

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

[0110] 2) LSP deletion scenario:

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

[0112] Set the deletion status or inactive status.

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

[0114] The network management system requests the removal of residual LSP connections based on the residual status. Residual LSP removal methods include: LSP segment removal, node-by-node LSP removal, and cross-residual removal.

[0115] The three methods are:

[0116] Method 1: End-to-end LSP remnant removal. During the establishment or deletion of an end-to-end LSP for an SPC service, DCN communication anomalies cause RSVP signaling interruption, resulting in LSP remnants. After DCN communication is restored, the network management initiates a remnant removal at the source node of the remnant segment. From the beginning node to the end node of the remnant segment, RSVP forward PATH(D) and reverse PATHERR bidirectional RSVP signaling are used to remove LSP remnants from all nodes in the remnant segment. The nodes then report the remnant removal results to the network management.

[0117] Method 2: Node-by-node LSP residual cleanup. The network management records the LSP residual status of each routing node in the end-to-end LSP information. LSP residual cleanup can be initiated for each node, and the node reports the LSP residual cleanup results to the network management.

[0118] Method 3: Clear cross-link residuals on each node. The network management records the cross-link residual status of each routing node in the end-to-end LSP information. 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 NMS receives the end-to-end LSP connection information reported by the source node. If this is an LSP creation scenario, the end-to-end LSP information reported by the source node includes all connected routing nodes. The NMS sets the end-to-end LSP, LSPs of all routing nodes, and device cross-connection to the residual state.

[0120] Step 3: The network management receives the LSP update status data report of the routing node and updates the node LSP and device cross-connection residual information, including: LSP establishment or deletion operation status, activated or inactivated status, and 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 consists of a network management subsystem and an ASON node control subsystem. Figure 6 shown.

[0123] 1) The ASON node leveling subsystem is used to control the establishment and deletion of end-to-end LSP connections through RSVP signaling. It senses the end-to-end LSP connection and node LSP status, reports the status changes to the network management in real time, and supports the network management's LSP residual tracking and removal functions. The ASON node leveling subsystem includes:

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

[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 status of establishment or deletion operations, connection activation status, device cross-configuration success or failure status, and reports status updates to the network management system;

[0127] The device cross-connect configuration module receives local node LSP cross-connect data, issues cross-connect configuration to local transmission devices, reads device cross-connect status, and returns cross-connect configuration success or failure status to the node LSP management module.

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

[0129] 2) The network management subsystem is 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. It includes:

[0130] End-to-end LSP connection residual display layer, which updates and displays end-to-end LSP connection residual information and provides a human-machine interface for LSP residual clearing;

[0131] The 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-residual node list, number of elements t;

[0140] When an end-to-end LSP is initially established, deleted, or a 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: Upon receiving the NE node LSP activation update status report, the NE node ID is searched and added to the LSP active node list;

[0142] 3) Step S03: Calculate the end-to-end LSP remnant, update the remnant state, calculate the number m of elements in the LSP active node list, and if m is less than n, set the LSP connection to the remnant state; calculate the LSP remnant segment, and if the end-to-end LSP is in the create operation state, the LSP active node list includes all remnant nodes; if the end-to-end LSP is in the LSP delete operation state, the LSP active node list includes all non-remnant 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, proceed to step S07; if not, proceed to step S06;

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

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

[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-connection residual node list records the IDs of all cross-connection residual nodes of LSP connections. You can clear the cross-connection residual nodes according to the list.

[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. In these four examples, the LSP connections pass through three routing nodes: NE1 (source), NE2 (middle), and NE3 (destination).

[0150] 2. Example 2: Example of the implementation process of the SPC service of the present invention to create a new end-to-end LSP, automatically track and clear the node cross residue, such as Figure 9 As shown, the process includes:

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

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

[0153] Step S12: The network manager initializes the end-to-end LSP residual tracking information, creates an LSP routing node list containing the three elements NE1, NE2, and NE3 (the number of elements n = 3), creates an empty LSP active node list (the number of elements m = 0), and creates a cross residual node list containing 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 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, and NE3 node controllers sequentially create node LSPs, reserve interface transmission resources (time slots or wavelengths), set the node LSP to inactive state, and 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). RSVP signaling PATH messages are transmitted to downstream nodes. NE1, NE2, and NE3 report the node LSP status to the network management system, and the network management system 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 and sends an RSVP signaling RESV message to the upstream NE2. It sets the NE3 LSP to active and the backup cross-connect configuration to LSP-XC-BAK. After successfully configuring and reading the device cross-connect configuration, it sets the LSP device cross-connect configuration to successful, deletes the backup cross-connect configuration LSP-XC-BAK, and reports to the network management system that the NE3 LSP is active and no cross-connection remains.

[0157] NE2 receives the RESV message, allocates interface transmission resources, and sends an RSVP signaling RESV message to the upstream NE1. It sets the NE2 LSP to active and the backup cross-connect configuration to LSP-XC-BAK. Configuration and reading of the device cross-connect configuration fails, and the LSP device cross-connect configuration is set to failed. It then reports to the network management system that the NE3 LSP is active and has residual cross-connection status.

[0158] NE1 receives the RESV message, allocates interface transmission resources, sets the LSP on NE2 to active, sets the backup cross-connect configuration to LSP-XC-BAK, successfully configures and reads the device cross-connect configuration, sets the LSP device cross-connect configuration to successful, deletes the backup cross-connect configuration LSP-XC-BAK, and reports to the network management system that the LSP on NE1 is active and no cross-connection remains.

[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 then updates the end-to-end LSP status.

[0161] Step S15: The network management receives the node LSP and cross-residual status information reported by NE3, NE2, and NE1, calculates the cross-residual of 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. It reads the device cross configuration successfully, sets the LSP device cross configuration to a successful state, deletes the cross configuration backup LSP-XC-BAK, and reports to the network management that the NE2 node LSP is activated and has no cross residue status. The network management updates the end-to-end LSP to an activated state with no cross residue, completing 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 Figure 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 and sends an RSVP signaling RESV message to the upstream NE2. It sets the NE3 LSP to active and the backup cross-connect configuration to LSP-XC-BAK. After successfully configuring and reading the device cross-connect configuration, it sets the LSP device cross-connect configuration to successful, deletes the backup cross-connect configuration LSP-XC-BAK, and reports to the network management system that the NE3 LSP is active and no cross-connection remains.

[0167] NE2 receives the RESV message, allocates interface transmission resources, and sends an RSVP signaling RESV message to the upstream NE1. It sets the NE2 LSP to active, sets the backup cross-connect configuration to LSP-XC-BAK, and successfully configures and reads the device cross-connect configuration. It sets the LSP device cross-connect configuration to successful, deletes the backup cross-connect configuration LSP-XC-BAK, and reports to the network management system that the NE2 LSP is active and no cross-connection remains.

[0168] Due to a DCN network communication anomaly, the LSP on NE1 cannot be created and activated. Only NE3 and NE2 report to the network management system that the LSP is activated and there is no cross-link residual status. The network management system then updates the end-to-end LSP residual tracking information.

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

[0170] Step S26: Delete the residual end-to-end LSP to be established. The network management requests to delete the end-to-end LSP and 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. An empty LSP active node list (the number of elements m=0) is created. The cross residual node list containing the three elements NE1, NE2, and NE3 (the number of elements t=3) is cleared and added. Since n>m, it is calculated that the end-to-end LSP is in the residual state to be deleted. The LSP of the nodes NE1, NE2, and NE3 is residual. NE1 and NE3 are the first and last nodes of the residual LSP segment respectively. The network management requests NE1 to delete the residual end-to-end LSP to be established.

[0171] Step S27: LSP connection distributed control RSVP forward PATH (D) signaling process. Along the LSP route, NE1, NE2, and NE3 node controllers sequentially set the node LSP to pending deletion status and the device crossover to successful status. RSVP signaling PATHERR messages are transmitted to downstream nodes. NE1, NE2, and NE3 report the pending deletion status of the node LSP to the network management system, and the network management system 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 and sends an RSVP signaling PATHERR message to the upstream NE2. The LSP on NE3 is set to the deletion-activated state, the backup cross-connection configuration is set to LSP-XC-BAK, the cross-connection configuration is successfully configured and read, the LSP device cross-connection configuration is set to the successful state, the backup cross-connection configuration LSP-XC-BAK is deleted, and the information that the LSP on NE3 has been deleted and no cross-connection remains is reported to the network management system.

[0174] NE2 receives the PATHERR message, releases the interface transmission resources, and sends an RSVP signaling PATHERR message to the upstream NE1. It sets the NE2 LSP to the deletion-activated state and the backup cross-connection configuration to LSP-XC-BAK. The configuration and reading of the device cross-connection configuration fails, and the LSP device cross-connection configuration is set to the failed state. The network management system is notified that the NE2 LSP has been deleted and that some cross-connection remains.

[0175] NE1 receives the PATHERR message and releases the interface transmission resources. It then checks and finds that the LSP creation on NE1 is inactive. It then sets the LSP on NE1 to active deletion and the LSP cross-connection configuration to successful. It then reports to the network management system that the LSP on NE1 has been deleted and no cross-connection remains.

[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 deleted state of the end-to-end LSP to the network manager, and the network manager deletes the end-to-end LSP.

[0178] In the above process, when a new end-to-end LSP connection generates LSP residues, the network management system tracks and calculates the residue status to automatically clear the LSP residues.

[0179] 4. Example 4: This is an example of the implementation process of the SPC service of the present invention to delete the end-to-end LSP, automatically track and clear the node cross residue, such as Figure 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 manager initializes end-to-end LSP residual tracking information. The end-to-end LSP information includes an LSP routing node list of three elements: NE1, NE2, and NE3 (number of elements: n = 3). An empty LSP node list to be deleted (number of elements: m = 0) is created. A cross residual node list (number of elements: t = 3) is created, which includes three elements: NE1, NE2, and NE3. Since n > m, the end-to-end LSP is calculated to be in a residual state to be deleted. The LSPs at NE1, NE2, and NE3 are residual. NE1 and NE3 are the first and last nodes of the residual LSP segment, respectively.

[0183] Step S33: LSP connection distributed control RSVP forward PATH (D) signaling process. Along the LSP route, NE1, NE2, and NE3 node controllers sequentially set the node LSP to pending deletion status and the device crossover to successful status. RSVP signaling PATHERR messages are transmitted to downstream nodes. NE1, NE2, and NE3 report the pending deletion status of the node LSP to the network management system, and the network management system 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 and sends an RSVP signaling PATHERR message to the upstream NE2. The LSP on NE3 is set to the deletion-activated state, the backup cross-connection configuration is set to LSP-XC-BAK, the cross-connection configuration is successfully configured and read, the LSP device cross-connection configuration is set to the successful state, the backup cross-connection configuration LSP-XC-BAK is deleted, and the information that the LSP on NE3 has been deleted and no cross-connection remains is reported to the network management system.

[0186] NE2 receives the PATHERR message, releases the interface transmission resources, and sends an RSVP signaling PATHERR message to the upstream NE1. It sets the NE2 LSP to the deletion-activated state and the backup cross-connection configuration to LSP-XC-BAK. The configuration and reading of the device cross-connection configuration fails, and the LSP device cross-connection configuration is set to the failed state. The network management system is notified that the NE2 LSP has been deleted and that some cross-connection remains.

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

[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 NE3, NE2, and NE1, calculates the cross-residual of NE2 according to the residual tracking algorithm, and updates the end-to-end LSP to the pending deletion and NE2 cross-residual status;

[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 it to the device cross-configuration. It reads the device cross-configuration successfully, sets the LSP device cross-configuration to a successful state, deletes the cross-configuration backup LSP-XC-BAK, deletes the node LSP, and reports to the network manager that the NE2 node LSP has been deleted and there is no cross-residue status. The network manager then 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 to delete the end-to-end LSP, automatically track and clear the node LSP residue, such as Figure 12 As shown, the process includes:

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

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

[0194] NE3 releases the interface transmission resources and sends an RSVP signaling PATHERR message to the upstream node NE2. The LSP on NE3 is set to the deletion-activated state, the backup cross-connection configuration is set to LSP-XC-BAK, the cross-connection configuration is successfully configured and read, the LSP device cross-connection configuration is set to the successful state, the backup cross-connection configuration LSP-XC-BAK is deleted, the LSP on NE3 is deleted, and the information that the LSP on NE3 is deleted and no cross-connection remains is reported to the network management system.

[0195] NE2 releases the interface transmission resources and sends an RSVP signaling PATHERR message to the upstream NE1 node. The LSP on NE2 is set to the deletion-activated state, the backup cross-connection configuration is set to LSP-XC-BAK, the cross-connection configuration is successfully configured and read, the LSP device cross-connection configuration is set to the successful state, the backup cross-connection configuration LSP-XC-BAK is deleted, the LSP on NE3 is deleted, and the information that the LSP on NE2 has been deleted and no cross-connection remains is reported to the network management system.

[0196] Due to a DCN network anomaly, communication between NE1 and NE2 is interrupted. NE1 cannot receive the PATHERR signaling message sent by NE2, and the LSP on NE1 cannot be deleted or activated. The network management only receives reports from NE3 and NE2 indicating that the LSP has been deleted and activated and that there is no cross-residual state. 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 residual (LSP residual of NE1 node);

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

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

[0200] NE1 finds the next-hop LSP route is NE2, but NE2 finds no node LSP.

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

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

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

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

[0205] Step S49: Delete the end-to-end LSP. The network manager 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 it to the network manager, and the network manager deletes the end-to-end LSP.

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

[0207] 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, node cross configuration state, node deletion state, and node ID;

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

[0209] The judgment module is configured to determine that after the LSP connection is established, if the LSP activation state of node A stored in the network management system is an LSP inactive state, or the node cross-connection configuration state of node A is a cross-connection configuration failure state, then there is an SPC service residual on node A;

[0210] After deleting the LSP connection, if the node deletion status of node A saved in the network management system is "deletion inactive" or the node cross-connection configuration status of node A is "cross-connection configuration failed", then SPC services remain on node A.

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

[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-mentioned 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-mentioned 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 further provides a computer storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to perform 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 cause the essence of the corresponding technical solutions to 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: Setting node residual state information in the routing node of the ASON network SPC service, 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; 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 established, if the LSP activation status of node A saved in the network management system is LSP inactive, or the cross-connection configuration status of node A is cross-connection configuration failed, SPC services are still present on node A. After deleting the LSP connection, if the node deletion status of node A saved in the network management system is "deletion inactive" or the node cross-connection configuration status of node A is "cross-connection configuration failed", then SPC services remain on node A. The network management system initiates a residual clearing request based on the node ID of node A where the SPC service remains, and clears the SPC service residue.

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

3. The method for clearing residual SPC services in an ASON network according to claim 2, wherein: When establishing an LSP connection, each node updates its own residual node state information, including: When the service connection source node receives a Create LSP message, or a non-source node receives an RSVP forward PATH(C) signaling message, it creates a node LSP and initializes the node's residual state information to: LSP creation state, LSP inactive state, and device crossover 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 cross-connection between the configuration and the reading device is configured. If the cross-connection between the reading device fails, the cross-connection configuration state is set to the cross-connection configuration failure state; if the cross-connection between the reading device succeeds, the cross-connection configuration state is set to the cross-connection configuration success state; If a node receives a cross-residual 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, wherein: When deleting an LSP connection, a node updates its residual node state information. This includes: 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's residual status information is set to: LSP delete operation status, LSP inactive status, and cross-configuration successful status; When the sink node receives the RSVP positive PATH(D) signaling or other nodes receive the PATHERR reverse signaling message, set the activation state of the sink node to the deletion activation state; configure and read the device cross-connect. If the device cross-connect reading fails, set the cross-connect configuration state to the cross-connect configuration failure state; if the device cross-connect reading is successful, set the cross-connect configuration state to the cross-connect configuration success state and delete the cross-connect configuration backup. If a node receives a cross-residual repair request message, configure according to the device cross-connect backup, read the cross-connect configuration. If successful, set the cross-connect configuration state to the cross-connect configuration success state 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 has: 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 state 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 state being the cross-connect configuration failure state. The number of elements in the cross-residual node list is t; An LSP to-be-deleted node list for storing the node deletion state 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 ends, 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 ends, 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 source node of the residual segment. From the first node to the last node of the residual segment, all node LSP residues of the residual 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 state, 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.

8. A system for clearing residual SPC services in an ASON network, characterized in that: The network management system updates the end-to-end LSP to the activated and non-cross-residual state, completing the clearing of node cross-residual when creating an LSP connection. Include: 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 is used to update the residual state information of each node when creating or deleting an LSP connection, and transmit the updated residual state information to the network management for storage; The judgment module is configured to determine that after the LSP connection is established, if the LSP activation state of node A stored in the network management system is an LSP inactive state, or the node cross-connection configuration state of node A is a cross-connection configuration failure state, then there is an SPC service residual on node A; After deleting the LSP connection, if the node deletion status of node A saved in the network management system is "deletion inactive" or the node cross-connection configuration status of node A is "cross-connection configuration failed", then SPC services remain on node A. The residual clearing module is used for the network management to initiate a residual clearing request based on the node ID of the node A where the SPC service residual exists to clear the SPC service residual.

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 to enable the at least one processor to execute the method for clearing residual SPC services in an 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