Incremental synchronization-based service switchover method, system and storage medium

Abstract

The present application relates to the field of communication technology, especially to a service cut method and system based on incremental synchronization and a storage medium. The method comprises the following steps: determining the cut task type according to the user request, disconnecting the fiber and marking the interrupted node and the broken state of the affected end-to-end service; rebuilding the target fiber, planning the label resource and the address resource; configuring the network element layer service data of the target fiber according to the resource allocation result; checking the network element layer service data, incrementally synchronizing the network element layer service data that passes the check to the subnet layer, and updating the activation state of the end-to-end service associated with the subnet layer; mapping the ID of the end-to-end service associated with the subnet layer to the network element layer, and incrementally issuing the network element node data with the specified activation state to the network element device, thereby realizing the service cut service. The present application improves the cut efficiency and accuracy, and shortens the service interruption time.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a service cutover method, system, and storage medium based on incremental synchronization. Background Technology

[0002] Multi-Protocol Label Switching-TransportProfile (MPLS-TP) is a connection-oriented tunneling technology that uses the MPLS protocol to establish bidirectional label-switched paths. It can carry L2VPN and L3VPN services and is characterized by having two Label Switching Paths (LSPs), where the incoming label of the next hop and the outgoing label of the previous hop are the same within the same path. With the increasing maturity of Packet Transport Network (PTN) technology, L2VPN and L3VPN services carried by MPLS-TP tunnels are widely used in telecommunications access networks, backhaul networks, and provincial trunk networks. The continuous development of equipment communication functions, capacity, and service types necessitates continuous optimization, transformation, and upgrading of communication network nodes. During network optimization and upgrading, due to objective reasons such as link replanning, aging communication equipment, equipment upgrades, and data center relocation, it is inevitable to cut over existing network services.

[0003] Common cutover scenarios include adding network elements (adding network elements to the existing link), removing network elements (removing network elements from the existing link), and replacing network elements (adding new network elements to replace old ones). Adding and removing network elements only involve changes to the MPLS-TP tunnel link, requiring only the MPLS-TP tunnel to be cut over. However, network element replacement scenarios involve different service nodes. Replacing intermediate network elements only affects the MPLS-TP tunnel link, while replacing source and destination network elements affects not only the MPLS-TP tunnel link but also the L2VPN and L3VPN services they carry.

[0004] To minimize the impact of network element nodes, shorten service interruption time, reduce network awareness, and improve the efficiency of service cutover, various equipment vendors and operators have introduced their own cutover strategies. The current service cutover operation process is as follows: 1. If a service on an existing network element needs to be cut over, network administrators select the end-to-end service passing through that network element to perform the cutover operation, modify the network element nodes through which the end-to-end service passes, delete the service on the original network element, create new node service data on the new network element, modify the service data on related network elements (such as adjacent network elements), and then verify the service; 2. If multiple services on an existing network element need to be cut over, network administrators select multiple end-to-end services passing through that network element and repeat the "delete → create → modify → verify" process one by one on the original network element; 3. For scenarios involving disruption and point reduction, modify the service data on related network elements one by one.

[0005] When performing business cutover using the above method, the following problems exist:

[0006] Long service interruption time: The operation mode of deleting the old service first and then creating the new service results in a long interruption time in the process of deletion and creation, which affects service quality;

[0007] Low operational efficiency: When there are many business layers and complex business types, resulting in a relatively large number of businesses to be cut over, the efficiency of cutting over one by one is low and the operation and maintenance costs are high.

[0008] High error rate: The probability of errors increases during cutover, raising risks and reducing user satisfaction with the service. Summary of the Invention

[0009] The purpose of this invention is to provide a service cutover method and system based on incremental synchronization, which can improve the efficiency and accuracy of service cutover and shorten the service interruption time during the cutover process.

[0010] To achieve the above objectives, the present invention provides the following technical solution:

[0011] A service cutover method based on incremental synchronization includes:

[0012] Determine the cutover task type based on user requests, including any one of the following: adding points to the network, removing points from the network, and replacing network elements; disconnect the fiber connection and mark the interrupted node and the damaged status of the affected end-to-end service.

[0013] Reconstruct the target fiber connection according to the cutover task type, allocate label resources to network elements within a specified range according to the adjacent node label matching rules, plan the address resources of the previous / next hop, and plan the label resources and port resources of the VPN service;

[0014] Configure the network element layer service data of the target fiber connection according to the resource allocation results, including: creating a single-site tunnel model CTunnel for a new network element, deleting the CTunnel data of the removed network element, modifying the CTunnel data of the boundary network element, and rebuilding the source / destination network element to replace the VPN service data involved, and modifying the activation status of the network element node data according to the data change type.

[0015] The network element layer service data is subjected to Label Switching Path (LSP) connectivity verification and VPN service parameter verification. The successfully verified network element layer service data is incrementally synchronized to the sub-network layer, and the activation status of the end-to-end services associated with the sub-network layer is updated.

[0016] The IDs of end-to-end services associated with the subnet layer are mapped to the network element layer, and incremental data of network element nodes with specified active states are sent to network element devices to realize service cutover services.

[0017] A cutover system, comprising a client and a network management server;

[0018] The client is used to initiate a service cutover request to the network management server, including any one of the following: adding points to the network, removing points from the network, and replacing network elements.

[0019] The network management server includes a service cutover management module, a subnet service management module, and a network element service management module;

[0020] The service cutover management module is used to disconnect the fiber optic cable according to the service cutover request, mark the interrupted node and the damaged state of the affected end-to-end service, and rebuild the target fiber optic cable.

[0021] The service cutover management module is also used to process network element layer services by calling the network element service management module and to process subnet layer services by calling the subnet service management module, thereby completing the corresponding cutover task.

[0022] The network element service management module is used for:

[0023] According to the adjacent node label matching rules, assign label resources to network elements within a specified range, plan the address resources of the previous / next hop, and plan the label and port resources for VPN services;

[0024] In addition, the network element layer service data of the target fiber connection is configured according to the resource allocation results, including: creating a single-site tunnel model CTunnel for a new network element, deleting the CTunnel data of the removed network element, modifying the CTunnel data of the boundary network element, and rebuilding the VPN service data involved in the source / destination network element replacement, and modifying the activation status of the network element node data according to the data change type.

[0025] In addition, incremental data of network element nodes in a specified active state is sent to network element devices to realize service cutover services;

[0026] The subnet service management module is used for:

[0027] Node labels for planning end-to-end business;

[0028] In addition, the label switching path LSP connectivity verification and VPN service parameter verification are performed on the network element layer service data. The verified network element layer service data is incrementally synchronized to the sub-network layer, and the activation status of the end-to-end services associated with the sub-network layer is updated.

[0029] In addition, the IDs of the end-to-end services associated with the subnet layer are mapped to the network element layer.

[0030] Based on the same inventive concept, the present invention also provides a computer storage medium storing computer-executable instructions, which, when executed, implement the aforementioned service cutover method.

[0031] The technical effects and advantages of this invention are as follows:

[0032] (1) Automated cutover mechanism: Reduce manual intervention, reuse known configuration resources to perform batch operations on MPLS-TP tunnel data and VPN service data, and improve cutover efficiency;

[0033] (2) Incremental synchronization and fault isolation: The subnet layer only synchronizes the data of the broken links to reduce the computing load, and intercepts the wrong parameters during the verification phase to prevent the misconfiguration from spreading to the live network;

[0034] (3) Incremental delivery mechanism: Only inactive and partially activated network element layer service data are incrementally delivered to network element devices to avoid full service refresh and shorten network interruption time.

[0035] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained by means of the structures pointed out in the description, claims and drawings. Attached Figure Description

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

[0037] Figure 1This is an overall flowchart of the service cutover method in an embodiment of the present invention;

[0038] Figure 2 This is a schematic diagram of the service hierarchy of L2VPN services in an embodiment of the present invention;

[0039] Figure 3 This is a schematic diagram of the service hierarchy of L3VPN services in an embodiment of the present invention;

[0040] Figure 4 This is a schematic diagram of the damage-addition point in Example 1;

[0041] Figure 5 This is a schematic diagram of the process for adding points to the damaged area in Example 1;

[0042] Figure 6 This is a schematic diagram of link connectivity verification in Example 1;

[0043] Figure 7 This is a schematic diagram of the destructive reduction point in Example 2;

[0044] Figure 8 This is a schematic diagram of the process for reducing the number of points in Example 2;

[0045] Figure 9 This is a schematic diagram of the intermediate network element replacement in Example 3;

[0046] Figure 10 This is a schematic diagram of the intermediate network element replacement process in Example 3;

[0047] Figure 11 This is a schematic diagram of the source network element replacement in Example 4;

[0048] Figure 12 This is a schematic diagram of the replacement of the host network element in Example 4;

[0049] Figure 13 This is a schematic diagram of the process for rebuilding L2VPN services in Example 4;

[0050] Figure 14 This is a schematic diagram of the process for rebuilding L3VPN services in Example 5;

[0051] Figure 15 This is a structural diagram of a service cutover system in another embodiment of the present invention. Detailed Implementation

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

[0053] This invention provides a service cutover method based on incremental synchronization, such as... Figure 1 As shown, the method includes:

[0054] S1. Determine the cutover task type based on the user request, including any one of the following: adding points to the network, removing points from the network, and replacing network elements. Disconnect the fiber and mark the interrupted node and the damaged status of the affected end-to-end service.

[0055] S2. Reconstruct the target fiber connection according to the cutover task type, allocate label resources to network elements within a specified range according to the adjacent node label matching rules, plan the address resources of the previous hop / next hop, and plan the label resources and port resources of the VPN service.

[0056] S3. Configure the network element layer service data of the target fiber connection according to the resource allocation results, including: creating a single-site tunnel model CTunnel for a new network element, deleting the CTunnel data of the removed network element, modifying the CTunnel data of the boundary network element, and rebuilding the source / destination network element to replace the VPN service data involved, and modifying the activation status of the network element node data according to the data change type.

[0057] S4. Perform Label Switching Path (LSP) connectivity verification and VPN service parameter verification on the network element layer service data, and incrementally synchronize the successfully verified network element layer service data to the sub-network layer, and update the activation status of the end-to-end services associated with the sub-network layer.

[0058] S5. Map the IDs of the end-to-end services associated with the subnet layer to the network element layer, and incrementally distribute the data of the network element nodes in the specified active state to the network element devices to realize the service cutover service.

[0059] This invention employs an automated cutover mechanism to reduce manual intervention, reuses known configuration resources to perform batch operations on MPLS-TP tunnel data, improves cutover efficiency, and only synchronizes damaged link data at the subnet layer, reducing computational load. During the verification phase, erroneous parameters are intercepted to prevent erroneous configurations from spreading to the existing network. In this solution, only inactive and partially activated network element layer service data are incrementally distributed to network element devices, avoiding a full service refresh and shortening network interruption time.

[0060] According to an embodiment of the present invention, after disconnecting the original fiber connection, the interrupted nodes are marked as left network element and right network element, respectively, and the left network element and right network element are boundary network elements.

[0061] In this embodiment of the invention, reconstructing the target fiber connection according to the splicing task type includes:

[0062] When handling the task of breaking and adding points, the left network element, several newly added network elements, and the right network element are connected in sequence to obtain the first target fiber connection.

[0063] When handling the task of reducing the number of broken wires, the left network element is connected to the right network element to obtain the second target fiber connection.

[0064] When handling network element replacement tasks, there are two scenarios:

[0065] If the network element to be replaced is an intermediate network element, connect the left network element, several intermediate network elements to be replaced, and the right network element in sequence to obtain the third target fiber connection;

[0066] If the network element to be replaced is a source / destination network element, connect the source / destination network element to be replaced with the adjacent network element to obtain the fourth target fiber connection.

[0067] In this embodiment of the invention, the adjacent node label matching rule is as follows:

[0068] The label for the current jump (positive outgoing label) equals the label for the next jump (positive incoming label);

[0069] The label that enters in the opposite direction of the current jump is the label that exits in the opposite direction of the previous jump.

[0070] The process of allocating label resources to network elements within a specified range according to adjacent node label matching rules, and planning the address resources for the previous / next hop, includes:

[0071] For the first target fiber connection, the forward outgoing label of the left network element is used as the forward incoming label of the first newly added network element, and the reverse incoming label of the left network element is used as the reverse outgoing label of the first newly added network element. Then, the label data of other newly added network elements are planned. In addition, the previous hop of the first newly added network element is planned as the network side port NNI address of the left network element, and its next hop is planned as the NNI port address of the adjacent newly added network element or the right network element.

[0072] For the second target fiber connection, the forward outgoing label of the left network element is used as the forward incoming label of the right network element, the reverse outgoing label of the right network element is used as the reverse incoming label of the left network element, and the next hop of the left network element is planned as the NNI port address of the right network element.

[0073] For the third target fiber connection, the forward outgoing label of the left network element is used as the forward incoming label of the first intermediate network element to be replaced, and the reverse incoming label of the left network element is used as the reverse outgoing label of the first intermediate network element to be replaced. Then, the label data of other intermediate network elements to be replaced are planned. In addition, the previous hop of the first intermediate network element to be replaced is planned as the NNI port address of the left network element, and its next hop is planned as the NNI port address of the adjacent intermediate network element to be replaced or the right network element.

[0074] For the fourth target fiber connection, there are two cases:

[0075] When the network element to be replaced is the source network element, the forward inbound label of the left network element is used as the forward outbound label of the source network element to be replaced, the reverse outbound label of the left network element is used as the reverse inbound label of the source network element to be replaced, and the next hop of the source network element to be replaced is planned as the NNI port address of the left network element.

[0076] When the network element to be replaced is the destination network element, the forward outgoing label of the right network element is used as the forward incoming label of the destination network element to be replaced, the reverse incoming label of the right network element is used as the reverse outgoing label of the destination network element to be replaced, and the previous hop of the destination network element to be replaced is planned as the NNI port address of the right network element.

[0077] According to a preferred embodiment, if the label assigned to the new network element / network element to be replaced (including the source network element to be replaced and the destination network element to be replaced) is a non-idle label, then the label resources of the relevant network element are re-planned according to the adjacent node label matching rule.

[0078] In practical applications, the end-to-end model is the subnet layer model, and the single-site model is the network element layer model. Based on the actual application requirements, the end-to-end service parameters are planned and configured, an end-to-end model object is generated, and the end-to-end object parameters are instantiated. Then, based on the actual device type, a single-site model object is generated, and the single-site object parameters are instantiated.

[0079] A single-site tunnel model is called a CTunnel, which mainly consists of two Label Switched Paths (LSPs) (forward and reverse). The CTunnel data for a single network element includes: tunnel-id (a unique one-way identifier assigned by the source), source IP, destination IP, ingress port address, egress port address, ingress label, egress label, next-hop address, and Quality of Service (OQS). The CTunnel is the execution unit of an MPLS-TP tunnel on a single network element, and its parameters (label, interface, node role) directly determine the device's forwarding behavior. In practical applications, network management maintains a CTunnel instance for each network element to achieve segmented control and service continuity of the end-to-end tunnel.

[0080] In this embodiment of the invention, network element layer service data is configured according to the resource allocation results of network element nodes in the target fiber connection. The target fiber connection may include old network elements and new network elements (newly added network elements and network elements to be replaced).

[0081] According to a specific embodiment, creating a new single-site tunnel model CTunnel for a new network element includes: creating a CTunnel replica on the new network element based on the CTunnel data of the left / right network element on the same target fiber, and modifying the relevant data in the CTunnel replica based on the assigned bidirectional tags and the previous and next hop addresses.

[0082] According to a specific embodiment, modifying the CTunnel data of the boundary network element includes: when processing a loop reduction task, modifying the labels of the left and right network elements and the next-hop address of the left network element according to the allocated node resources; or, when the label assigned to the newly added network element / to be replaced network element is a non-idle label, modifying the bidirectional label of the boundary network element and the newly added network element / to be replaced network element according to the adjacent node label matching rule.

[0083] In practical applications, Layer 2 Virtual Private Networks (L2VPNs) provide Layer 2 VPN services based on multiple data link layers to different users on a unified MPLS network, achieving isolated transmission of user Layer 2 data. L2VPN services include two types: Virtual Private Wire Service (VPWS) and Virtual Private LAN Service (VPLS). L2VPN services are implemented only on PE nodes, which can be understood as provider edge devices directly connected to user edge devices. Therefore, L2VPN services only exist on the source and destination network element nodes that establish the MPLS-TP tunnel. Before configuring L2VPN services, pseudowires (PWs) must be built on the MPLS-TP tunnel. PWs are essentially logical connections established between PE nodes, used to transparently carry user Layer 2 data frames. A PW consists of a pair of bidirectional virtual channels (VCs). Each VC channel is assigned a locally unique virtual channel identifier (VC-ID) on the PE node to distinguish different PWs.

[0084] From a business perspective, such as Figure 2As shown, the bottom service layer is an MPLS-TP tunnel, connected by network elements AE to provide packet forwarding paths. The intermediate service layer PW is built on top of the MPLS-TP tunnel, and the upper service layer is VPWS or VPLS. The MPLS-TP tunnel is the service layer of the PW, and the PW is the service layer of VPWS or VPLS.

[0085] The end-to-end L2VPN model is CL2VPN, while the single-site L2VPN models are CVpws and CVpls. On the same L2VPN service, the service IDs of CL2VPN instances, CVpws instances, and CVpls instances are identical. The end-to-end L2VPN model consists of a set of PE nodes participating in the L2VPN service. Each PE node contains network element node information (such as node identifier, address, etc.), the set of PWs it traverses (all PWs configured for the L2VPN instance on the PE node), and its node role (its function within a specific L2VPN instance).

[0086] The end-to-end PW model is CPwPath, and the single-site PW model is CPw. For the same PW, the CPwPath instance and the CPw instance have the same service ID. The attributes of the single-site PW model include Virtual Channel Identifier (VC-id), inbound label, outbound label, tunnel service layer (such as LSP path), and Quality of Service (QoS). The end-to-end PW model CPwPath consists of tunnels, starting from the source PE node and ending at the destination PE node. The attributes of the single-site VPLS model CVpws include the PW service layer (i.e., the PW bound to the VPLS instance), the User-to-Network Interface (UNI), the QoS of the UNI, etc. The CVpls model is similar to the CVpws model, the core difference being that VPLS services need to bind to multiple PWs to achieve multi-point connections.

[0087] Layer 3 Virtual Private Network (L3VPN) provides users with Layer 3 IP routing services within a PTN network. User data is routed and forwarded at the network layer, and different VPNs achieve logical isolation through IP address spaces, supporting cross-regional network interconnection. The end-to-end L3VPN model is CL3Vpn, and the single-site L3VPN model is CL3Vpn_ins. For the same L3VPN service, the CL3Vpn instance and the CL3Vpn_ins instance have the same service ID. The end-to-end L3VPN model consists of two sets of PE nodes. The attributes of the single-site L3VPN model include: Virtual RoutingForwarding (VRF), Route Distinguisher (RD), Route Target (RT), VPN Peer information (VPN-Peer), UNI interface, and QoS. The VPN-Peer includes attributes such as the tunnel connecting to the peer PE and the peer label.

[0088] like Figure 3 As shown, the MPLS-TP tunnel (the fiber optic connection of network element AE) is the service layer of L3VPN services.

[0089] In this embodiment of the invention, in the source / destination network element replacement scenario, since MPLS-TP may carry L2VPN and L3VPN services, it is necessary to rebuild the single-node L2VPN and L3VPN services on the source / destination network elements, and update the source and destination node information of the end-to-end MPLS-TP link routing. The end-to-end L2VPN service needs to update its service layer PW path information and its own PE node information, and the end-to-end L3VPN service needs to update the VPN-Peer information and its own PE node information.

[0090] In this embodiment of the invention, the reconstruction of source / destination network element replacement involves VPN service data, including:

[0091] Obtain the L2VPN service data configured on the original source / destination network element from the damaged service set, including CPw, CVpws and CVpls. Create CPw replicas, CVpws replicas and CVpls replicas on the source / destination network element to be replaced, and modify the user-side-network-side port UNI in the above replicas to generate network element layer L2VPN service data.

[0092] Obtain the L3VPN service data configured on the source / destination network element, including the single-site L3VPN model CL3Vpn_ins. Create a copy of CL3Vpn_ins on the source / destination network element to be replaced, and modify the UNI port in the copy of CL3Vpn_ins to generate network element layer L3VPN service data.

[0093] In this embodiment of the invention, the activation status is a marker indicating whether network management services have been distributed to devices. If network management services have not been distributed to devices, they are marked as inactive; if network management service data has been distributed to devices, it indicates that the service data of the network management system and the device are consistent, and it is marked as activated; if the activated network management service has only been modified on the network management system and has not been distributed to devices, it is marked as partially activated. Both subnet-level services and network element-level services have activation statuses. The network element-level service activation status is used to record whether the service data of a single network element has been distributed to the network element device, while the subnet-level service activation status is used to record whether the service data of all network element nodes has been distributed to the network element device. If some network element node service data has been distributed to the network element device, it is marked as partially activated; if all node service data has been distributed to the device, it is marked as activated. In this embodiment of the invention, newly added, modified, and deleted network element node data are calculated incrementally and their activation status is modified accordingly. Newly added service data is inactive, modified service data is partially activated, and removed service data is pending deletion.

[0094] Specifically, in this embodiment of the invention, the activation status of network element node data is modified according to the data change type of the network element node, including:

[0095] Mark the newly created CTunnel data on the target fiber-connected network element node as inactive;

[0096] The modified CTunnel data on the original network element is marked as partially active.

[0097] Mark the removed service data on the network element node as pending deletion.

[0098] The L2VPN service data and L3VPN service data at the network element layer are marked as partially active.

[0099] In this embodiment of the invention, when incrementally synchronizing the network element layer service data of the target fiber connection configuration to the sub-network layer, the network element layer service data undergoes Label Switched Path (LSP) connectivity verification and VPN service parameter verification. The incrementally synchronized network element layer service data that successfully passes the verification is then synchronized to the sub-network layer, and the activation status of the end-to-end services associated with the sub-network layer is updated. Specifically, this includes:

[0100] Cache CTunnel data, L2VPN service data and L3VPN service data of each network element node of the target fiber connection;

[0101] When using the CTunnel data of network element nodes to perform LSP path connectivity verification, an index is established based on the outgoing / incoming port address and outgoing / incoming label of the network element node. The next-hop address is searched with the boundary network element as the starting and ending node, and the CTunnel data of the node is checked to determine whether the traversed LSP route segment is connected. If so, the CTunnel data of each node in the target fiber is incrementally synchronized to the subnet layer.

[0102] When verifying L2VPN service data, an index is established based on the outgoing / incoming labels of the pseudowire Pw. Starting from the source / destination network element to be replaced, the peer PE node and peer Pw service data are searched based on the PE node of the local Pw service. The PE node parameters are verified. If the PE node parameters of the local and peer ends are correct, the Pw service path and PE node information verification is successful, the L2VPN service data verification is successful, and the successfully verified L2VPN service data is incrementally synchronized to the subnet layer.

[0103] When verifying L3VPN service data, an index is established based on the outgoing / incoming labels of the L3VPN service. Starting from the source / destination network element to be replaced, the peer PE node and peer L3VPN service are searched based on the PE node of the local L3VPN service. The PE node parameters are verified. If the PE node parameters of the local and peer ends are correct, the L3VPN service data verification is successful. The successfully verified L3VPN service data is incrementally synchronized to the subnet layer.

[0104] This function updates the end-to-end services associated with the subnet layer to an inactive or partially active state, prompting the network management terminal to issue a network element layer service data update instruction.

[0105] Furthermore, the IDs of the end-to-end services associated with the subnet layer are mapped to the network element layer, and incremental data of network element nodes in the specified active state is sent to the network element device, including: updating the CTunnel service ID, L2VPN service ID, and L3VPN service ID of the network element nodes in the target fiber connection to the IDs of the end-to-end services associated with the subnet layer; and sending incremental data of inactive and partially active network element nodes to the network element device based on the network element layer service data update instruction.

[0106] This invention, through batch configuration of service data at the network element layer and incremental synchronization of end-to-end services, automatically completes the transformation of network element layer services and subnet layer services, incrementally distributing the changed network element layer service data to network element devices, thereby improving the efficiency of packet service transformation and reducing service interruption time and error probability during cutover operations.

[0107] The following examples illustrate this in detail.

[0108] Example 1

[0109] like Figure 4 As shown, in the scenario of adding points to break the loop, the initial end-to-end MPLS-TP tunnel path is: network element A-network element B-network element C-network element D. Now, new network elements E, F, and G need to be added between network element B and network element C to form a new path: network element A-network element B-network element E-network element F-network element G-network element C-network element D, while ensuring that the tunnel service is unaffected.

[0110] like Figure 5 As shown, the process for handling broken points is as follows:

[0111] S100: Disconnect the original fiber connection and mark the left and right network elements as the start and end points of the damage;

[0112] Specifically, the starting point of the damage is the output port of network element B, and the ending point of the damage is the input port of network element C.

[0113] S101: Query all tunnels that pass through the fiber optic cable breakage and record them as broken.

[0114] Specifically, all end-to-end tunnel services passing through network element B (left network element) and network element C (right network element) are obtained, marked as broken, and the tunnel service IDs are cached.

[0115] S102: Plan the link resources between the left network element, the newly added network element, and the right network element;

[0116] Specifically, the labels of newly added network elements E, F, and G are assigned based on network elements B and C, and the label matching rules of adjacent nodes must be met. If the assigned labels conflict, for example, if the assigned label is already occupied in network element E, then the label associated with the new network element node needs to be reassigned.

[0117] Adjacent node label matching rules: the label of the current hop in the forward direction = the label of the next hop in the forward direction; the label of the current hop in the reverse direction = the label of the previous hop in the reverse direction.

[0118] Assume that in the single-station tunnel model CTunnel of network element B, the forward outgoing label is 301 and the reverse incoming label is 201; in the single-station tunnel model CTunnel of network element C, the forward incoming label is 401 and the reverse outgoing label is 101.

[0119] For network element E:

[0120] Forward infeed label = Forward outfeed label of network element B = 301

[0121] Reverse outgoing label = Reverse incoming label of network element B = 201

[0122] Forward outgoing label = forward incoming label of network element F (newly assigned label, e.g., 302)

[0123] Reverse input label = reverse output label of network element F (newly assigned label, e.g., 202)

[0124] For network element G:

[0125] Forward incoming label = forward outgoing label of network element F (newly assigned label, e.g., 303)

[0126] Reverse outgoing label = Reverse incoming label of network element F (newly assigned label, e.g., 203)

[0127] Forward outgoing label = Forward incoming label of network element C = 401

[0128] Reverse input label = Reverse output label of network element C = 101

[0129] Further, allocate ports to network element nodes:

[0130] The output port of network element B is the input port of network element E;

[0131] The output port of network element E is the input port of network element F;

[0132] The output port of network element F is the input port of network element G;

[0133] The output port of network element G is the input port of network element C;

[0134] Furthermore, allocate bandwidth resources:

[0135] Generally, the bandwidth parameters inherit the original tunnel's QoS configuration (e.g., 100Mbps).

[0136] S103. Configure the CTunnel data of the newly added network element, and modify the label and port data of the left and right network elements;

[0137] On an end-to-end MPLS-TP tunnel, the CTunnel data of each network element is mostly the same; the main differences are the port and label. By copying the CTunnel data of network elements B and C, a CTunnel copy is created on the new network element. Then, the egress / ingress labels and egress / ingress port parameters are modified based on the assigned label and port data. Taking network element E as an example, the CTunnel data of network element B is copied, including: tunnel-id, source IP, destination IP, ingress port address, egress port address, ingress label, egress label, next-hop address, Quality of Service (OQS), and other attribute data. A CTunnel copy is then generated on network element E. Finally, the port and label data in the CTunnel copy are modified based on the assigned egress port address, ingress port address, egress label, and ingress label. Since there may be more than one tunnel involved, a batch processing method can be used to improve efficiency.

[0138] S104: Re-establish fiber connections between the left network element, newly added network element, and right network element;

[0139] The newly established fiber optic path is: Element B - Element E - Element F - Element G - Element C;

[0140] S105. Update the activation status of service data for left network element, newly added network element, and right network element;

[0141] S106. Verify the link and parameters;

[0142] Specifically, such as Figure 6 As shown, the steps to verify link connectivity are as follows:

[0143] S1061. Load Ctunnel data for the specified network element range and create an index by port and tag;

[0144] S1062. Start searching for tunnel paths from the specified network element;

[0145] S1063. Obtain the node role of the current node;

[0146] S1064. If the current node is the source node, then find the next hop address based on the current node's output port and output label, until the termination node is reached.

[0147] S1065. If the current node is an intermediate node, then find the next hop address based on the current node's output port and output label, until the termination node is reached.

[0148] S1066. Based on the ingress port and ingress label of the current node, find the next hop address until the starting node;

[0149] S1067. If the current node is the destination node, then find the next hop address based on the ingress port and ingress label of the current node, until the starting node.

[0150] S1068. If the node role of the current network element cannot be determined, record the error information.

[0151] S107. Determine if the link is connected;

[0152] S108. If not, record the error message;

[0153] S109. If so, the tunnel data increment will be synchronized to the subnet layer, and the activation status of the end-to-end service in the subnet layer will be updated.

[0154] Specifically, the system reads key CTunnel data from the network element layer on the link between the left and right network elements, including tunnel-id, inbound and outbound ports, inbound and outbound labels, and node roles. An index is created using the inbound / outbound ports and labels, and loaded into the cache. Using the left and right network elements as start and end nodes, the system searches for the next hop and verifies other key parameters. The LSP routing fragment information is verified by checking the completeness of the link route and the correctness of the CTunnel data. If the link is complete and the CTunnel data is correct, the link route between the broken points of the CVpPath is updated, and the activation status of the CVpPath is changed to inactive.

[0155] S110. Modify the service ID of the newly added network element's CTunnel;

[0156] Specifically, the service ID of the CTunnel of the newly added network element is changed to the service ID of CVpPath, the activation status of the CTunnel of the newly added network element is updated to inactive, and the activation status of the CTunnel of network element B and network element C is changed to partially activated.

[0157] S111, Incrementally send CTunnel data of the left network element, newly added network element and right network element to the network element device.

[0158] Specifically, the subnet layer issues a data update instruction based on the service ID of the partially activated CVpPath. This instruction is used to instruct the network element layer to find the CTunnel service based on the service ID and only send inactive and partially activated CTunnel data to the network element device to complete the loop break and point cutover task.

[0159] Example 2

[0160] like Figure 7 As shown, in the scenario of breaking down the loop and reducing the number of points, the initial end-to-end MPLS-TP tunnel path is: network element A-network element B-network element E-network element F-network element G-network element C-network element D. Now, it is necessary to remove network elements E, F, and G between network element B and network element C to form a new path: network element A-network element B-network element C-network element D, while ensuring that the tunnel service is unaffected.

[0161] like Figure 8 As shown, the process for handling damage reduction points is as follows:

[0162] S200: Disconnect the original fiber connection and mark the left and right network elements as the start and end points of the damage;

[0163] Specifically, the starting point of the damage is the output port of network element B, and the ending point of the damage is the input port of network element C.

[0164] S201. Query all tunnels that pass through the fiber optic cable breakage and record them as broken.

[0165] Specifically, query all end-to-end tunnel services that pass through network element B (left network element) - network element C (right network element), mark them as broken, and cache the tunnel service ID.

[0166] S202. Plan the link resources between the left network element and the right network element;

[0167] If the outgoing label of the left network element is equal to the incoming label of the right network element, then there is no need to reallocate label resources; otherwise, reconfiguration is required. Configure the outgoing port of the left network element as the incoming port of the right network element.

[0168] S203. Delete the CTunnel data of the network element to be removed, and modify the CTunnel data of the left and right network elements.

[0169] If the labels are reassigned, the in / out labels of the left and right network elements need to be modified.

[0170] S204. Reconstruct the fiber connection between the left and right network elements;

[0171] S205. Update the service data activation status of the left and right network elements;

[0172] Specifically, the activation state of the CTunnel of network element B and network element C is modified to a partially activated state.

[0173] S206. Verify link data and parameters;

[0174] according to Figure 6 Perform the verification as shown in the steps.

[0175] S207. Determine if the link is connected;

[0176] S208. If not, record the error message;

[0177] S209. If so, the tunnel data increment will be synchronized to the subnet layer, and the activation status of the end-to-end service in the subnet layer will be updated.

[0178] Specifically, the system reads key CTunnel data from the network element layer on the link between the left and right network elements, including tunnel-id, inbound and outbound ports, inbound and outbound labels, and node roles. An index is created using the inbound / outbound ports and labels, and loaded into the cache. Using the left network element as the start and end node, the system searches for the next hop and verifies other key parameters. The LSP routing fragment information is verified by checking the completeness of the link route and the correctness of the CTunnel data. If the link is complete and the CTunnel data is correct, the link route between the broken points of the CVpPath is updated, and the activation status of the CVpPath is changed to inactive.

[0179] S210, incrementally distribute CTunnel data of the left and right network elements to the network element devices.

[0180] Specifically, the subnet layer issues a data update instruction based on the service ID of the partially activated CVpPath. This instruction is used to instruct the network element layer to find the CTunnel service based on the service ID and only send inactive and partially activated CTunnel data to the network element device to complete the loop-breaking and point-reduction cutover task.

[0181] Example 3

[0182] like Figure 9 As shown, in the scenario of intermediate network element replacement, the initial end-to-end MPLS-TP tunnel path is: network element A-network element B-network element E-network element C-network element D. Now, network element E needs to be replaced with network element F to form a new path: network element A-network element B-network element F-network element C-network element D, while ensuring that the tunnel service is unaffected.

[0183] like Figure 10 As shown, the processing flow for intermediate network element replacement includes the following specific steps:

[0184] S300: Disconnect the fiber optic cable between the replaced intermediate network element and the adjacent network element;

[0185] Specifically, disconnect the fiber optic cable between network element E and network elements B (left network element) and C (right network element).

[0186] S301. Query all tunnels that pass through the fiber optic cable breakage and record them as broken.

[0187] Specifically, query all end-to-end tunnel services that pass through network element E, mark them as broken, and cache the tunnel service ID.

[0188] S302: Plan the link resources between the left network element, the intermediate network element to be replaced, and the right network element;

[0189] The intermediate network element F to be replaced is a new network element. The link resources of network element F are planned according to the processing method of newly added network elements in Example 1.

[0190] S303. Configure the CTunnel data of the intermediate network element to be replaced, and modify the label and port data of the left and right network elements;

[0191] S304: Re-establish the fiber connection between the left network element, the middle network element to be replaced, and the right network element;

[0192] The newly established fiber connection path is: Element A - Element B - Element F - Element C - Element D.

[0193] S305. Update the activation status of service data for left network element, newly added network element, and right network element;

[0194] S306. Verify the link and parameters;

[0195] according to Figure 6 Perform the verification as shown in the steps.

[0196] S307. Determine if the link is connected;

[0197] S308. If not, record the error message;

[0198] S309. If so, the tunnel data increment will be synchronized to the subnet layer, and the activation status of the end-to-end service in the subnet layer will be updated.

[0199] Specifically, the system reads key CTunnel data from the network element layer on the link between the left and right network elements, including tunnel-id, inbound and outbound ports, inbound and outbound labels, and node roles. An index is created using the inbound / outbound ports and labels, and loaded into the cache. Using the left and right network elements as start and end nodes, the system searches for the next hop and verifies other key parameters. The LSP routing fragment information is verified by checking the completeness of the link route and the correctness of the CTunnel data. If the link is complete and the CTunnel data is correct, the link route between the broken points of the CVpPath is updated, and the activation status of the CVpPath is changed to inactive.

[0200] S310. Modify the service ID of the CTunnel of the intermediate network element to be replaced;

[0201] Specifically, the service ID of the CTunnel of the intermediate network element to be replaced is changed to the service ID of CVpPath, the activation status of the CTunnel of the intermediate network element to be replaced is updated to inactive, and the activation status of the CTunnel of network element B and network element C is changed to partially active.

[0202] S311, Incrementally send CTunnel data of the left network element, the middle network element to be replaced, and the right network element to the network element device.

[0203] Specifically, the subnet layer issues a data update instruction based on the service ID of the partially activated CVpPath. This instruction is used to instruct the network element layer to find the CTunnel service based on the service ID and only send inactive and partially activated CTunnel data to the network element device to complete the intermediate network element replacement and cutover task.

[0204] Example 4

[0205] The initial end-to-end MPLS-TP tunnel path is: Network element A - Network element B - Network element E - Network element C - Network element D.

[0206] like Figure 11As shown, the source network element replacement scenario is: replacing source network element A with network element F to form a new path, namely network element F-network element B-network element E-network element C-network element D.

[0207] like Figure 12 As shown, the scenario for replacing the destination network element is: replacing the destination network element D with network element F to form a new path, namely network element A-network element B-network element E-network element C-network element F.

[0208] Assuming that L2VPN service is configured on the source network element A / destination network element D, such as Figure 13 As shown, the steps to rebuild the L2VPN service are as follows:

[0209] S401. Obtain L2VPN service data from the cached set of broken services;

[0210] S402. Plan the L2VPN resources of the source / destination network elements to be replaced;

[0211] Specifically, the PW ingress / egress tags, VC-id, Vpws-id, and Vpls-id of the source / destination network element F to be replaced are planned to maintain resource consistency with the source / destination network element being replaced, and UNI ports are also planned.

[0212] S403. Configure the L2VPN service data of the source / destination network element to be replaced;

[0213] Specifically, batch creation of CPw, CVpws, and CVpls data involves copying CPw, CVpws, and CVpls service data from the old network element, generating replicas on the new network element, and then modifying individual differentiated attributes such as UNI. Since the configuration of the new network element replaces the configuration of the old network element (replacing the old version with the new version), a compatibility check is performed.

[0214] S404. Delete the L2VPN service data of the replaced source / destination network element;

[0215] Specifically, delete CPw, CVpws, and CVpls data in batches on the old network elements.

[0216] S405, Verify L2VPN service data;

[0217] Specifically, key data of network element layer CPw, CVpws, and CVpls on the link between the old network element and the adjacent network element are read, including PW inbound / outbound labels, node roles, Vpws-id, Vpls-id, etc., and loaded into the cache. An index is built based on the PW inbound / outbound labels. Starting from the new network element, the PW peer is searched and key parameters are verified. The peer network element is found according to the PW service layer CVpPath. The peer PW is found in the peer network element according to the inbound / outbound label matching rules, that is, the CPwPath is found. Then the PE node on the peer PW is found, and it is determined whether the parameters of the local PE node and the peer PE node are correct.

[0218] S406. If the L2VPN service data is incorrect, record the error message;

[0219] S407. If the L2VPN service data is correct, incrementally synchronize the L2VPN data at the network element layer and subnet layer.

[0220] Specifically, if the searched CPwPath path is complete and the CL2vpn data is correct, the CPwPath path, the L2VPN's NNI and PE nodes are incrementally updated to CPwPath and CL2Vpn, the CL2vpn activation status is modified to partially activated, and the CL2vpn broken status is revoked.

[0221] S408. Modify the L2VPN service ID of the source / destination network element to be replaced;

[0222] Specifically, the PW service ID, CVpws service ID, and CVpls service ID of the source / destination network element to be replaced are set to the CPwPath service ID, which is the same as the L2VPN service ID of the subnet layer. The L2VPN activation status of the adjacent network element is then updated to partially activated.

[0223] Example 5

[0224] Assuming that L3VPN service is configured on the source network element A / receiver network element D, such as Figure 14 As shown, the steps to rebuild the L3VPN service are as follows:

[0225] S501. Obtain L3VPN service data from the cached set of broken services;

[0226] S502, Plan the L3VPN resources of the source / destination network elements to be replaced;

[0227] Specifically, the L3VPN inbound / outbound labels of the source / destination network elements to be replaced are planned to maintain consistency with the resources of the old network elements (the source / destination network elements being replaced), as well as the fixed-line UNI ports.

[0228] S503, Configure L3VPN service data for the source / destination network element to be replaced;

[0229] Specifically, L3VPN service data from older network elements can be copied and version compatibility checks can be performed.

[0230] S504. Delete the L3VPN service data of the replaced source / destination network element;

[0231] S505, Verify L3VPN service data;

[0232] Specifically, key L3VPN data at the network element layer, such as L3VPN inbound / outbound labels, node roles, and VPN peers, are read from the links between the old network element and adjacent network elements and loaded into the cache. An index is built using L3VPN inbound / outbound labels. Starting with the new network element, the VPN peer is searched for and key parameters are verified. Once the VPN peer is found, the PE node of the L3VPN peer is located, and it is determined whether the parameters of the local PE node and the peer PE node are correct.

[0233] S506: If the L3VPN service data is incorrect, record the error information;

[0234] S507. If the L3VPN service data is correct, then incrementally synchronize the L3VPN data at the network element layer and subnet layer.

[0235] Specifically, if the VPN-peer and PE node data of the L3VPN service found are correct, the VPN-peer and PE node information of the subnet layer CL3vpn will be incrementally updated, the activation status of CL3vpn will be modified to partial activation, and the broken status of CL3vpn will be revoked.

[0236] S70509: Modify the L3VPN service ID of the source / destination network element to be replaced;

[0237] Specifically, modify the service ID of the CL3vpn_ins of the source / destination network element to be replaced to the service ID of the subnet layer CL3VPN, and update the L3VPN activation status of the adjacent network element (peer PE) to partially activated.

[0238] like Figure 15 As shown, another embodiment of the present invention also provides a cutover system, the system including a client and a network management server.

[0239] The client is used to initiate a service cutover request to the network management server, including any one of the following: adding points due to disruption, removing points due to disruption, and replacing network elements.

[0240] The network management server includes a service cutover management module, a subnet service management module, and a network element service management module.

[0241] The service cutover management module is used to disconnect the fiber optic cable according to the service cutover request, mark the interrupted node and the damaged state of the affected end-to-end service, and rebuild the target fiber optic cable.

[0242] The service cutover management module is also used to process network element layer services by calling the network element service management module and to process subnet layer services by calling the subnet service management module, thereby completing the corresponding cutover task.

[0243] The network element service management module is used for:

[0244] According to the adjacent node label matching rules, assign label resources to network elements within a specified range, plan the address resources of the previous / next hop, and plan the label and port resources for VPN services;

[0245] In addition, the network element layer service data of the target fiber connection is configured according to the resource allocation results, including: creating a single-site tunnel model CTunnel for a new network element, deleting the CTunnel data of the removed network element, modifying the CTunnel data of the boundary network element, and rebuilding the source / destination network element replacement involved VPN service data, and modifying the activation status of the network element node data according to the data change type.

[0246] Additionally, incremental data from network element nodes in a specified active state is sent to network element devices to enable service cutover.

[0247] The subnet service management module is used for:

[0248] Node labels for planning end-to-end business;

[0249] In addition, the label switching path LSP connectivity verification and VPN service parameter verification are performed on the network element layer service data. The verified network element layer service data is incrementally synchronized to the sub-network layer, and the activation status of the end-to-end services associated with the sub-network layer is updated.

[0250] In addition, the IDs of the end-to-end services associated with the subnet layer are mapped to the network element layer.

[0251] In this embodiment of the invention, the network element service management module includes:

[0252] The CTunnel creation module is used to create a CTunnel replica on a new network element based on the CTunnel data of the left / right network element on the same target fiber, and to modify the relevant data in the CTunnel replica according to the assigned bidirectional tags and the previous and next hop addresses.

[0253] The CTunnel modification module is used to modify the labels of the left and right network elements and the next-hop address of the left network element based on the allocated node resources when processing the task of breaking the loop and reducing the number of nodes.

[0254] Alternatively, when the label assigned to the new network element / to be replaced is a non-idle label, the bidirectional labels of the boundary network element and the new network element / to be replaced are modified according to the adjacent node label matching rules.

[0255] The VPN service data reconstruction module is used for:

[0256] Obtain the L2VPN service data configured on the original source / destination network elements from the damaged service set, including the pseudowire model CPw, the point-to-point virtual private line model CVpws, and the multi-point virtual private LAN model CVpls. Create CPw replicas, CVpws replicas, and CVpls replicas on the source / destination network elements to be replaced, and modify the user-side-network-side port UNI in the above replicas to generate network element layer L2VPN service data.

[0257] Obtain the L3VPN service data configured on the source / destination network element, including the single-site L3VPN model CL3vpn_ins. Create a copy of CL3vpn_ins on the source / destination network element to be replaced, and modify the UNI port in the copy of CL3vpn_ins to generate network element layer L3VPN service data.

[0258] In this embodiment of the invention, the subnet service management module includes:

[0259] The caching module is used to cache CTunnel data, L2VPN service data and L3VPN service data of each network element node of the target fiber connection.

[0260] The first verification module is used to establish an index based on the ingress / egress port address and ingress / egress label of the network element node, search for the next hop address with the boundary network element as the starting and ending node, and verify the CTunnel data of the node to determine whether the passed LSP route segment is connected. If so, the CTunnel data of each node in the target fiber is incrementally synchronized to the subnet layer.

[0261] The second verification module is used to establish an index based on the outgoing / incoming labels of the pseudowire Pw, starting from the source / destination network element to be replaced, and search for the peer PE node and peer Pw service data based on the PE node of the local Pw service, and verify the PE node parameters. If the PE node parameters of the local and peer ends are correct, the Pw service path and PE node information verification is successful, the L2VPN service data verification is successful, and the successfully verified L2VPN service data is incrementally synchronized to the subnet layer.

[0262] The third verification module is used to establish an index based on the outgoing / incoming labels of the L3VPN service. Starting from the source / destination network element to be replaced, it searches for the peer PE node and peer L3VPN service based on the PE node of the local L3VPN service, verifies the PE node parameters, and if the PE node parameters of the local and peer ends are correct, the L3VPN service data verification is successful, and the successfully verified L3VPN service data is incrementally synchronized to the subnet layer.

[0263] The update module is used to update the end-to-end services associated with the subnet layer to an inactive or partially active state, and prompt the network management terminal to issue a network element layer service data update instruction.

[0264] Regarding the system in the above embodiments, the specific manner in which each unit module performs operations has been described in detail in the embodiments related to the method, and will not be elaborated here.

[0265] Based on the same inventive concept, embodiments of the present invention also provide an electronic device, including: a memory and a processor, wherein the processor is used to read and execute a computer program stored in the memory to implement the aforementioned service cutover method.

[0266] Based on the same inventive concept, embodiments of the present invention also provide a computer storage medium storing computer-executable instructions, which, when executed, implement the aforementioned service cutover method.

[0267] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0268] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, the functional modules in the various embodiments of this invention can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0269] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0270] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the present invention is not limited to the described order of actions, because according to the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.

[0271] In the above embodiments, the descriptions of each embodiment have their own emphasis. Parts not described in detail in a particular embodiment can be found in the relevant descriptions of other embodiments. Finally, it should be noted that the above descriptions are merely preferred embodiments of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A service cutover method based on incremental synchronization, characterized in that, The method includes: Determine the cutover task type based on user requests, including any one of the following: adding points to the network, removing points from the network, and replacing network elements; disconnect the fiber connection and mark the interrupted node and the damaged status of the affected end-to-end service. Reconstruct the target fiber connection according to the cutover task type, allocate label resources to network elements within a specified range according to the adjacent node label matching rules, plan the address resources of the previous / next hop, and plan the label resources and port resources of the VPN service. The adjacent node label matching rule is as follows: The label for the current jump (positive outgoing label) equals the label for the next jump (positive incoming label); The label entered in the reverse direction of this jump = the label exited in the reverse direction of the previous jump; Configure the network element layer service data of the target fiber connection according to the resource allocation results, including: creating a single-site tunnel model CTunnel for a new network element, deleting the CTunnel data of the removed network element, modifying the CTunnel data of the boundary network element, and rebuilding the VPN service data involved in the source / destination network element replacement, and modifying the activation status of the network element node data according to the data change type. The network element layer service data is subjected to Label Switching Path (LSP) connectivity verification and VPN service parameter verification. The successfully verified network element layer service data is incrementally synchronized to the sub-network layer, and the activation status of the end-to-end services associated with the sub-network layer is updated. The IDs of end-to-end services associated with the subnet layer are mapped to the network element layer, and incremental data of network element nodes with specified active states are sent to network element devices to realize service cutover services.

2. The method according to claim 1, characterized in that, After disconnecting the fiber, the interrupted nodes are marked as left and right network elements, respectively, and the left and right network elements are boundary network elements; The step of reconstructing the target fiber connection according to the splicing task type includes: When handling the task of breaking and adding points, the left network element, several newly added network elements and the right network element are connected in sequence to obtain the first target fiber connection; When handling the task of reducing the number of broken wires, connect the left network element and the right network element to obtain the second target fiber connection; When handling network element replacement tasks If the network element to be replaced is an intermediate network element, connect the left network element, several intermediate network elements to be replaced, and the right network element in sequence to obtain the third target fiber connection; If the network element to be replaced is a source / destination network element, connect the source / destination network element to be replaced with the adjacent network element to obtain the fourth target fiber connection.

3. The method according to claim 2, characterized in that, The process of allocating label resources to network elements within a specified range according to adjacent node label matching rules, and planning the address resources for the previous / next hop, includes: For the first target fiber connection, the forward outgoing label of the left network element is used as the forward incoming label of the first newly added network element, and the reverse incoming label of the left network element is used as the reverse outgoing label of the first newly added network element. Then, the label data of other newly added network elements are planned. In addition, the previous hop of the first newly added network element is planned as the network side port NNI address of the left network element, and its next hop is planned as the NNI port address of the adjacent newly added network element or the right network element. For the second target fiber connection, the forward outgoing label of the left network element is used as the forward incoming label of the right network element, the reverse outgoing label of the right network element is used as the reverse incoming label of the left network element, and the next hop of the left network element is planned as the NNI port address of the right network element. For the third target fiber connection, the forward outgoing label of the left network element is used as the forward incoming label of the first intermediate network element to be replaced, and the reverse incoming label of the left network element is used as the reverse outgoing label of the first intermediate network element to be replaced. Then, the label data of other intermediate network elements to be replaced are planned. In addition, the previous hop of the first intermediate network element to be replaced is planned as the NNI port address of the left network element, and its next hop is planned as the NNI port address of the adjacent intermediate network element to be replaced or the right network element. For the fourth target fiber connection The forward inbound label of the left network element is used as the forward outbound label of the source network element to be replaced, the reverse outbound label of the left network element is used as the reverse inbound label of the source network element to be replaced, and the next hop of the source network element to be replaced is planned as the NNI port address of the left network element. And / or, use the forward outgoing label of the right network element as the forward incoming label of the destination network element to be replaced, use the reverse incoming label of the right network element as the reverse outgoing label of the destination network element to be replaced, and plan the previous hop of the destination network element to be replaced as the NNI port address of the right network element.

4. The method according to claim 3, characterized in that, If the tag assigned to the new network element / network element to be replaced is a non-idle tag, then the tag resources of the relevant network element shall be re-planned according to the adjacent node tag matching rules.

5. The method according to any one of claims 2 to 4, characterized in that, The single-site tunnel model CTunnel includes bidirectional LSP paths. The CTunnel data of a single network element includes: tunnel-id, source IP, destination IP, ingress port address, egress port address, ingress label, egress label, next-hop address, and quality of service (OQS). The single-site tunnel model CTunnel for creating new network elements includes: Based on the CTunnel data of the left / right network element on the same target fiber, create a CTunnel replica on the new network element, and modify the relevant data in the CTunnel replica according to the assigned bidirectional tags and the previous and next hop addresses. The modified CTunnel data of the boundary network element includes: When handling the task of reducing the number of nodes due to loop damage, modify the labels of the left and right network elements and the next-hop address of the left network element according to the allocated node resources. Alternatively, when the label assigned to the new network element / to be replaced is a non-idle label, the bidirectional labels of the boundary network element and the new network element / to be replaced are modified according to the adjacent node label matching rules. The VPN service data involved in the reconstruction of the source / destination network element replacement includes: Obtain the L2VPN service data configured on the original source / destination network elements from the damaged service set, including the single-site pseudowire model CPw, the single-site to-point virtual private line model CVpws, and the single-site to-multipoint virtual private LAN model CVpls. Create CPw replicas, CVpws replicas, and CVpls replicas on the source / destination network elements to be replaced, and modify the user-side-network-side port UNI in the above replicas to generate network element layer L2VPN service data. Obtain the L3VPN service data configured on the source / destination network element, including the single-site L3VPN model CL3Vpn_ins. Create a copy of CL3Vpn_ins on the source / destination network element to be replaced, and modify the UNI port in the copy of CL3Vpn_ins to generate network element layer L3VPN service data.

6. The method according to claim 5, characterized in that, The step of modifying the activation status of network element node data according to the data change type includes: Mark the newly created CTunnel data on the target fiber-connected network element node as inactive; The modified CTunnel data on the original network element is marked as partially active. Mark the removed service data on the network element node as pending deletion. The L2VPN service data and L3VPN service data at the network element layer are marked as partially active.

7. The method according to claim 6, characterized in that, The network element layer service data undergoes Label Switched Path (LSP) connectivity verification and VPN service parameter verification. Successfully verified network element layer service data is incrementally synchronized to the sub-network layer, and the activation status of the associated end-to-end services at the sub-network layer is updated, including: Cache CTunnel data, L2VPN service data and L3VPN service data of each network element node of the target fiber connection; When using the CTunnel data of network element nodes to perform LSP path connectivity verification, an index is established based on the outgoing / incoming port address and outgoing / incoming label of the network element node. The next-hop address is searched with the boundary network element as the starting and ending node, and the CTunnel data of the node is checked to determine whether the traversed LSP route segment is connected. If so, the CTunnel data of each node in the target fiber is incrementally synchronized to the subnet layer. When verifying L2VPN service data, an index is established based on the outgoing / incoming labels of the pseudowire Pw. Starting from the source / destination network element to be replaced, the peer PE node and peer Pw service data are searched based on the PE node of the local Pw service. The PE node parameters are verified. If the PE node parameters of the local and peer ends are correct, the Pw service path and PE node information verification is successful, the L2VPN service data verification is successful, and the successfully verified L2VPN service data is incrementally synchronized to the subnet layer. When verifying L3VPN service data, an index is established based on the outgoing / incoming labels of the L3VPN service. Starting from the source / destination network element to be replaced, the peer PE node and peer L3VPN service are searched based on the PE node of the local L3VPN service. The PE node parameters are verified. If the PE node parameters of the local and peer ends are correct, the L3VPN service data verification is successful. The successfully verified L3VPN service data is incrementally synchronized to the subnet layer. This function updates the end-to-end services associated with the subnet layer to an inactive or partially active state, prompting the network management terminal to issue a network element layer service data update instruction.

8. The method according to claim 7, characterized in that, Mapping the IDs of end-to-end services associated with the subnet layer to the network element layer, and incrementally distributing data from network element nodes in a specified active state to network element devices, including: Update the CTunnel service ID, L2VPN service ID, and L3VPN service ID of the target fiber-connected network element node to the ID of the end-to-end service associated with the subnet layer. Based on the network element layer service data update instruction, incremental data of inactive and partially activated network element nodes are sent to the network element device.

9. A cutover system, characterized in that, The system includes a client and a network management server; The client is used to initiate a service cutover request to the network management server, including any one of the following: adding points to the network, removing points from the network, and replacing network elements. The network management server includes a service cutover management module, a subnet service management module, and a network element service management module; The service cutover management module is used to disconnect the fiber optic cable according to the service cutover request, mark the interrupted node and the damaged state of the affected end-to-end service, and rebuild the target fiber optic cable. The service cutover management module is also used to process network element layer services by calling the network element service management module and to process subnet layer services by calling the subnet service management module, thereby completing the corresponding cutover task. The network element service management module is used for: According to the adjacent node label matching rules, assign label resources to network elements within a specified range, plan the address resources of the previous / next hop, and plan the label and port resources for VPN services; The adjacent node label matching rule is as follows: The label for the current jump (positive outgoing label) equals the label for the next jump (positive incoming label); The label entered in the reverse direction of this jump = the label exited in the reverse direction of the previous jump; In addition, the network element layer service data of the target fiber connection is configured according to the resource allocation results, including: creating a single-site tunnel model CTunnel for a new network element, deleting the CTunnel data of the removed network element, modifying the CTunnel data of the boundary network element, and rebuilding the source / destination network element replacement involved VPN service data, and modifying the activation status of the network element node data according to the data change type. In addition, incremental data of network element nodes in a specified active state is sent to network element devices to realize service cutover services; The subnet service management module is used for: Node labels for planning end-to-end business; In addition, the label switching path LSP connectivity verification and VPN service parameter verification are performed on the network element layer service data. The verified network element layer service data is incrementally synchronized to the sub-network layer, and the activation status of the end-to-end services associated with the sub-network layer is updated. In addition, the IDs of the end-to-end services associated with the subnet layer are mapped to the network element layer.

10. The system according to claim 9, characterized in that, The network element service management module includes: The CTunnel creation module is used to create a CTunnel replica on a new network element based on the CTunnel data of the left / right network element on the same target fiber, and to modify the relevant data in the CTunnel replica according to the assigned bidirectional tags and the previous and next hop addresses. The CTunnel modification module is used to modify the labels of the left and right network elements and the next-hop address of the left network element based on the allocated node resources when processing the task of breaking the loop and reducing the number of nodes. Alternatively, when the label assigned to the new network element / to be replaced is a non-idle label, the bidirectional labels of the boundary network element and the new network element / to be replaced are modified according to the adjacent node label matching rules. The VPN service data reconstruction module is used for: Obtain the L2VPN service data configured on the original source / destination network elements from the damaged service set, including the pseudowire model CPw, the point-to-point virtual private line model CVpws, and the multi-point virtual private LAN model CVpls. Create CPw replicas, CVpws replicas, and CVpls replicas on the source / destination network elements to be replaced, and modify the user-side-network-side port UNI in the above replicas to generate network element layer L2VPN service data. Obtain the L3VPN service data configured on the source / destination network element, including the single-site L3VPN model CL3vpn_ins. Create a copy of CL3vpn_ins on the source / destination network element to be replaced, and modify the UNI port in the copy of CL3vpn_ins to generate network element layer L3VPN service data.

11. The system according to claim 10, characterized in that, The subnet service management module includes: The caching module is used to cache CTunnel data, L2VPN service data and L3VPN service data of each network element node of the target fiber connection. The first verification module is used to establish an index based on the ingress / egress port address and ingress / egress label of the network element node, search for the next hop address with the boundary network element as the starting and ending node, and verify the CTunnel data of the node to determine whether the passed LSP route segment is connected. If so, the CTunnel data of each node in the target fiber is incrementally synchronized to the subnet layer. The second verification module is used to establish an index based on the outgoing / incoming labels of the pseudowire Pw, starting from the source / destination network element to be replaced, and search for the peer PE node and peer Pw service data based on the PE node of the local Pw service, and verify the PE node parameters. If the PE node parameters of the local and peer ends are correct, the Pw service path and PE node information verification is successful, the L2VPN service data verification is successful, and the successfully verified L2VPN service data is incrementally synchronized to the subnet layer. The third verification module is used to establish an index based on the outgoing / incoming labels of the L3VPN service. Starting from the source / destination network element to be replaced, it searches for the peer PE node and peer L3VPN service based on the PE node of the local L3VPN service, verifies the PE node parameters, and if the PE node parameters of the local and peer ends are correct, the L3VPN service data verification is successful, and the successfully verified L3VPN service data is incrementally synchronized to the subnet layer. The update module is used to update the end-to-end services associated with the subnet layer to an inactive or partially active state, and prompt the network management terminal to issue a network element layer service data update instruction.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed, implement the method described in any one of claims 1-8.

Images