A method and system for implementing a service label adaptation of a binding ring

Abstract

The application relates to a method and system for realizing a service label adaptation of a ring service, and relates to the field of automatic protection switching of a PTN network, and comprises the following steps: after a service is bound to a ring network, the out label of a service channel is set as the in label of an upper ring node, and a ring label of the ring in which the upper ring node is located is added to the upper ring node; the ring label is forwarded through a ring channel in a middle node of the ring, and the ring label is popped out at a lower ring node. The application solves the problem that services with inconsistent service labels of upper ring nodes and lower ring nodes cannot be bound to a ring, expands the application scene of ring network protection, and greatly improves the engineering usability of the ring network protection function.

Description

Technical Field

[0001] This application relates to the field of automatic protection switching in PTN (Packet Transport Network) networks, specifically to a method and system for adaptive implementation of ring-bound service labels. Background Technology

[0002] The continuous expansion of network bandwidth has placed increasingly higher demands on network stability and reliability. Ring network protection plays an important role in increasingly complex network topologies due to its advantages of batch switching and support for multi-point fiber breakage.

[0003] The G.8132 standard provides a detailed description of the label allocation and switching mechanism for ring network protection. Services are bound to the ring network; a ring label is applied at the upstream node, forwarded through the ring channel, and the ring label is removed at the outgoing node, continuing the service label exchange. For example... Figure 1 As shown, nodes A, B, C, H, I, and J form ring 1, and nodes C, D, E, F, G, and H form ring 2. The service path is nodes A, B, C, D, E, and F. Before and after the service is bound to the ring network, label switching occurs at each service station. The switching actions at each node are as follows: at node A, label LSP label 1 is replaced with LSP label 2; at node B, label LSP label 2 is replaced with LSP label 3; at node C, label LSP label 3 is replaced with LSP label 4; at node D, label LSP label 3 is replaced with LSP label 4; at node E, label LSP label 4 is replaced with LSP label 6; and at node F, label LSP label 6 is replaced with LSP label 7. Here, PAYLOAD represents other labels that do not participate in label switching and remain in place.

[0004] The service ring tag processing logic described in the G.8132 standard and related existing patents only involves the exchange logic of ring tags, without processing the service tags before and after ring binding. Once a service enters the ring network from the upper ring node, only the ring tags are exchanged during the forwarding process within the ring. After the ring tags are popped out at the lower ring node, the exposed service tags are the same as the service tags at the upper ring node. This makes it impossible for services with inconsistent service tags at the upper and lower ring nodes to be bound to the ring network, limiting the application scenarios of service binding to the ring network in practical applications. Summary of the Invention

[0005] This application provides a method and system for adaptive implementation of ring-binding service labels to solve the problem in related technologies where services with inconsistent service labels at the upper and lower nodes cannot be bound to the ring network.

[0006] Firstly, a method for adaptive implementation of ring-binding business labels is provided, including the following steps:

[0007] After the service is bound to the ring network, the outgoing label of the service channel at the upstream node is set to the incoming label of the downstream node, and the ring label of the ring is added at the upstream node.

[0008] The intermediate nodes of the ring forward the label through the ring channel and pop up the ring label at the next node.

[0009] In some embodiments, the ring binding information of the service-bound ring network includes the source ring ID, the destination ring ID, the destination node ID, and the destination service label, wherein the destination service label is the ingress label of the LSP channel of the next node in the service channel.

[0010] In some embodiments, for each of the ring intermediate nodes, the service channel resources include occupied resources and idle resources, and the resource entries of the ring-binding services of the ring intermediate node are divided from occupied resources to reserved resources.

[0011] In some embodiments, when creating a new service, the idle resources are used first. When the idle resources are insufficient, the reserved resources of the bound services that do not require unbinding in the short term are selected to create the new service.

[0012] In some embodiments, when deleting a service, if there are occupied resource entries in the reserved resources, the resource entries of the occupied resources corresponding to the deleted service will be restored to the occupied resource entries in the reserved resources.

[0013] In some embodiments, if there are unoccupied resource entries in the reserved resources, the resource entries corresponding to the deleted services that are already occupied will be released as idle resources.

[0014] In some embodiments, when a ring-bound service is unbound from the ring network, if the unbound service has a corresponding reserved resource entry, the unbinding is successful directly, and the corresponding reserved resource entry is classified as occupied resource.

[0015] In some embodiments, if there is no corresponding reserved resource entry for the unbound service, the reserved resource entry for the bound service that does not have an unbinding requirement in the short term is selected and classified as occupied resource.

[0016] In some embodiments, if the unbound service does not have a corresponding reserved resource entry, nor any other reserved resource entries, a prompt will appear to manually modify the configuration and release the service channel resources; otherwise, the unbinding will fail.

[0017] Secondly, an implementation system for an adaptive implementation method of ring-binding business labels is provided, including:

[0018] The tag setting module is used to set the outgoing tag of the service channel to the incoming tag of the next link point at the previous link point after the service is bound to the ring network, and to add the ring tag of the ring at the previous link point.

[0019] The tag processing module is used to forward tags through the ring channel at intermediate nodes of the ring, and also to pop up tags at the next node.

[0020] The beneficial effects of the technical solution provided in this application include:

[0021] At the upstream node, the outgoing label of the service channel is set to the incoming label of the downstream node, and the ring label of the current ring is applied at the upstream node. When the ring label pops up at the downstream node, the exposed service label is the incoming service label of the downstream node, which can further complete the subsequent service label exchange process. Therefore, the problem of services that cannot be bound to the ring due to inconsistent service labels at the upstream and downstream nodes is solved, expanding the application scenarios of ring network protection and greatly improving the engineering usability of ring network protection functions.

[0022] For each ring intermediate node, the resource entries of the ring-bound services of the intermediate node are divided from occupied resources to reserved resources. The idle resources are used to participate in the creation of new services, deletion of services, and unbinding of ring-bound services. This is very beneficial for alleviating the shortage of service resources of old network equipment, and can also maximize the reserve resources for unbinding ring-bound services, preventing too many services from being unable to unbind the ring. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of this application, 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 this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This refers to the tag forwarding process before or after business binding / unbinding in existing technologies.

[0025] Figure 2 This invention provides a label forwarding process for a ring network bound to services, as described in this embodiment.

[0026] Figure 3 This is a schematic diagram illustrating the changes in tag actions before and after service binding to the ring network in an embodiment of the present invention;

[0027] Figure 4This is a classification of service channel resources in an embodiment of the present invention. Detailed Implementation

[0028] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0029] This application provides a method for adaptive implementation of ring-binding service labels, which can solve the problem that services with inconsistent service labels at the upper and lower links cannot be bound to the ring network. Even if the service labels at the upper and lower links are inconsistent, ring network binding can still be achieved.

[0030] This application provides an embodiment of a ring-bound service label adaptive implementation method, including the following steps: After the service is bound to the ring network, the outgoing label of the service channel at the upper node is set to the incoming label of the lower node, and the ring label of the ring is applied at the upper node; the intermediate node of the ring forwards the label through the ring channel, and the ring label is popped out at the lower node. The exposed service label is the service incoming label at the lower node, which can further complete the subsequent service label exchange process. By configuring and exchanging the service label of the lower ring at the upper node, the ring network binding of the service can be achieved even when the service label at the upper node and the service label at the lower node are inconsistent.

[0031] Specifically, existing service binding information is implemented using a triple (source ring ID + destination ring ID + destination node ID). In this application, the binding information for the service binding ring network is a quadruple (source ring ID + destination ring ID + destination node ID + destination service label), where the destination service label is the incoming label of the LSP (Label Switching Path) channel of the service channel.

[0032] like Figure 2 As shown, at the upstream node, the service receives the ring-binding four-tuple configuration. After the service is bound to the ring network, the same applies to... Figure 1For each node in the process, the tag exchange action after binding using the above method embodiment is as follows: At node A, tag LSPlabel 1 is replaced with LSP label 3 and PUSH RING1 C&D is performed; at node B, tag RING1 C&D remains unchanged; at node C, POPRING1 C&D is performed, tag LSP label 3 is replaced with LSP label 6 and PUSH RING2 F is performed; at node D, tag RING2F remains unchanged; at node E, RING2 F remains unchanged; at node F, POP RING2 F is performed, and tag LSP label 6 is replaced with LSPlabel 7. Here, PAYLOAD represents other tags that do not participate in the tag exchange and remain unchanged; PUSH means pushing in a tag, and POP means popping out a tag.

[0033] like Figure 3 As shown, the label actions change before and after the service is bound to the ring network. Taking node A as an example, which is the ingress node, the service label action on the unbound service channel is: PUSH, changing from PAYLOAD to PAYLOAD+LSP label 1. The ring channel has no label. The label action for the service channel bound to the ring network is: PUSH, changing from PAYLOAD to PAYLOAD+LSP label 3. LSP label 3 is the ingress label for ring 1 at the next node C. The ring channel label action is: PUSH, which is PAYLOAD+LSP label 3+RING1 C&D.

[0034] For node C, the labeling action for a service channel not bound to a ring network is: SWAP, changing from PAYLOAD+LSP label 3 to PAYLOAD+LSP label 4. There is no ring channel label. The labeling action for a service channel bound to a ring network is: PAYLOAD+LSP label 3 to PAYLOAD+LSP label 6, where LSP label 6 is the incoming label for ring 2 at the next node F. The labeling action for the ring channel is: PUSH, which is PAYLOAD+LSP label 6+RING 2F.

[0035] The above embodiments are all illustrated using the scenario of a transit service being bound to two ring networks, as this scenario is representative of the changes in tag actions before and after the service is bound to a ring network. The same logic applies to scenarios where services are bound to a single or multiple rings, and also to scenarios where source and destination node services are bound to ring networks.

[0036] In live network applications, before services are bound to the ring network, each node through which a service passes is configured with a corresponding service channel. After services are bound to the ring network, except for the upstream and downstream nodes, all intermediate nodes through which services pass are forwarded via the ring channel. The service channels allocated before binding are no longer needed. However, when a service is unbound from the ring network, these service channel resources are required again. The current approach is to directly reserve these service channel resources to prevent services from being unable to unbind from the ring network. However, the configuration of services bound to the ring network in the live network tends to be stable and does not frequently bind or unbind. Nodes that have been in use for a long time may have insufficient resources to enable new services, and the unusable reserved resources after unbinding result in a certain degree of waste.

[0037] To address the aforementioned issues, and in conjunction with the above embodiments, this application provides a flexible management method for ring-binding services, enabling the temporary allocation of reserved resources under resource constraints. For example... Figure 4 As shown, for each intermediate node of the ring, the service channel resources were originally divided into occupied resources and idle resources. In this embodiment, a new type of reserved resource for ring-bound services is added. Once a service is bound to the ring network, the resource entries of the original service channel resources of the ring-bound service at the intermediate node of the ring are reclassified from occupied resources to reserved resources. Then, the reserved resources can be used to participate in the management of ring-bound services.

[0038] When a new business needs to be created, idle resources are used first. When there are insufficient idle resources, reserved resources of bound businesses that do not need to be unbound in the short term are selected to create the new business. If there are neither idle resources nor reserved resources, the creation of the new business will fail.

[0039] When a service needs to be deleted, the reserved resources of the linked service are checked to see if any resource entries are occupied. If so, the resource entries of the occupied resources corresponding to the deleted service are restored to the reserved resource entries that are occupied. If not, the resource entries of the occupied resources corresponding to the deleted service are released as free resources.

[0040] For example, the resource entries that are already occupied are a, b, c, and d, and the resource entries that are reserved are e and f. Each resource entry corresponds to one service. The number of reserved resource entries that are currently occupied is 1, which is occupied by d. Now, we want to delete the resource entry c that is already occupied for the service. Considering that the reserved resource entry d is already occupied, we prioritize restoring the reserved resource entries. Therefore, after deleting the service corresponding to resource entry c, the reserved resource entries will be c, e, and f, and the resource entries that are already occupied will be a, b, and d.

[0041] For example, if the resource entries that are already occupied are a, b, c, and d, and the resource entries that are reserved are e and f, and the number of reserved resource entries that are occupied is 0, and now we want to delete the resource entry c that is already occupied corresponding to the business, then after deleting the business corresponding to resource entry c, the resource entries that are already occupied will be a, b, and d, the resource entries that are reserved will be e and f, and resource entry c will be released as an idle resource.

[0042] When a ring-bound service is unbound from the ring network, it is determined whether there is a corresponding reserved resource entry for the unbound service. If so, the unbinding is successful directly, and the reserved resource entry corresponding to the unbound service is classified as occupied resource. If not, the reserved resource entry of the ring-bound service that does not have an unbinding requirement in the short term is selected and classified as occupied resource.

[0043] If the service to be unbound has no corresponding reserved resource entry, and there are no other reserved resource entries, the user will be prompted to specify which resource entries are insufficient for unbinding. The user can then choose whether to manually modify the configuration to release service channel resources, such as deleting some useless resource entries or binding other services to the ring network. If the user manually releases enough service channel resources, the unbinding will be successful.

[0044] For example, the resource entries that have been occupied are a, b, c, and d, and the resource entries that have been reserved are e and f. Now, the ring-bound service corresponding to resource entry e needs to be unbound. After unbinding, the resource entries that have been occupied are a, b, c, d, and e, and the resource entry that has been reserved is f.

[0045] The resource entries that are already occupied are a, b, c, and d, and the resource entries that are reserved are e and f. Now, the ring-binding service g needs to unbind the ring network. If no corresponding reserved resource is found, it will prompt whether to release resource entry e or f. If not, the unbinding will fail. If you choose to release, for example, release resource entry e, the unbinding will be successful. After that, the resource entries that are already occupied will be a, b, c, and g, and the reserved resource entry will be F.

[0046] By setting reserved resources, the resource shortage of intermediate nodes in the ring-binding service can be alleviated, while also taking into account the reserved resource requirements when unbinding the ring network, so as to maximize the utilization of service channel resources.

[0047] This application also provides a ring-bound service label adaptive implementation system, which can be used to implement the above method, including a label setting module and a label processing module. The label setting module is used to set the outgoing label of the service channel at the upstream node to the incoming label of the downstream node after the service is bound to the ring network, and to affix the ring label of the ring at the upstream node. The label processing module is used to forward labels through the ring channel at intermediate nodes of the ring, and also to pop up labels at the downstream node; the exposed service label is the service incoming label at the downstream node, which can further complete the subsequent service label exchange process.

[0048] It should be noted that in this application, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0049] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for adaptive implementation of ring-binding service tags, characterized in that, Including the following steps: After the service is bound to the ring network, the outgoing label of the service channel at the upstream node is set to the incoming label of the downstream node, and the ring label of the ring is added at the upstream node. The intermediate nodes of the ring forward the label through the ring channel and pop up the ring label at the next node.

2. The adaptive implementation method for the ring-binding service tag as described in claim 1, characterized in that: The ring binding information of the service-bound ring network includes the source ring ID, the destination ring ID, the destination node ID, and the destination service label. The destination service label is the ingress label of the LSP channel of the next node in the service channel.

3. The adaptive implementation method for the ring-binding service tag as described in claim 1, characterized in that: For each of the ring intermediate nodes, the service channel resources include occupied resources and idle resources. The resource entries of the ring-binding services of the ring intermediate nodes are divided from occupied resources to reserved resources.

4. The adaptive implementation method for the ring-binding service tag as described in claim 3, characterized in that: When creating a new service, the available resources are used first. When there are insufficient available resources, the reserved resources of the binding service that does not need to be unbound in the short term are selected to create the new service.

5. The adaptive implementation method for the ring-binding service tag as described in claim 3, characterized in that: When deleting a service, if there are any occupied resource entries in the reserved resources, the occupied resource entries corresponding to the deleted service will be restored to the occupied resource entries in the reserved resources.

6. The adaptive implementation method for the ring-binding service tag as described in claim 5, characterized in that: If there are no occupied resource entries in the reserved resources list, the resource entries corresponding to the deleted services that were already occupied will be released as idle resources.

7. The adaptive implementation method for the ring-binding service tag as described in claim 3, characterized in that: When unbinding a ring network service, if the unbound service has a corresponding reserved resource entry, the unbinding will be successful directly, and the corresponding reserved resource entry will be classified as occupied resource.

8. The adaptive implementation method for the binding service tag as described in claim 7, characterized in that: If there is no corresponding reserved resource entry for the business to be unbound, select the reserved resource entry for the bound business that does not have a need to be unbound in the short term and classify it as occupied resource.

9. The adaptive implementation method for the ring-binding service tag as described in claim 7, characterized in that: If the service to be unbound does not have a corresponding reserved resource entry, nor any other reserved resource entries, a prompt will appear to manually modify the configuration and release the service channel resources; otherwise, the unbinding will fail.

10. A system for implementing the adaptive implementation method of the binding service tag according to any one of claims 1-9, characterized in that, include: The tag setting module is used to set the outgoing tag of the service channel to the incoming tag of the next link point at the previous link point after the service is bound to the ring network, and to add the ring tag of the ring at the previous link point. The tag processing module is used to forward tags through the ring channel at intermediate nodes of the ring, and also to pop up tags at the next node.

Images