WO2018053747A1

WO2018053747A1 - Resource sharing method, network node, and associated apparatus

Info

Publication number: WO2018053747A1
Application number: PCT/CN2016/099705
Authority: WO
Inventors: 张弦; 冯皓宇
Original assignee: 华为技术有限公司
Priority date: 2016-09-22
Filing date: 2016-09-22
Publication date: 2018-03-29
Also published as: CN109644122A; CN109644122B; CN112803995A; CN112803995B

Abstract

The application discloses a resource sharing method, a network node, and an associated apparatus. The method comprises: upon a fault of a service occurring in a working route, and a fallback route being adopted for data transmission, determining, by a node on a working route, whether a fault has been found in an associated link, and temporarily releasing a link resource of the node having no fault to be used by another service in a network. As a result, the embodiment is utilized to increase a utilization rate of network resources while ensuring an increased success rate of a service.

Description

Resource sharing method, network node and related equipment

Technical field

The present invention relates to the field of optical network communication technologies, and in particular, to a resource sharing method, a network node, and a device.

Background technique

In the current ASON (Automatically Switched Optical Network), the management plane, the data plane (transport plane) and the control plane are mainly included; wherein the control plane and the functions provided by the control plane are all related to the relevant international standards organization. The defined architecture and associated communication protocol support and implementation.

At present, the network usage rate of the ASON is measured by the service success rate. The service success rate refers to the number of services that are successfully received and carried by the network among the total number of service requests. However, in the process of measuring the network usage of ASON, it is also necessary to consider the SLA (Service Level Agreement) of the network, and the SLA is usually embodied by establishing different protection mechanisms for the service. At present, in order to ensure that the service can recover from network failures quickly, 1+1 protection or 1:1 protection is adopted.

The 1+1 protection refers to establishing two service paths for one service, and the service data is transmitted from the two service paths at the same time. When the service data is transmitted to the destination node through the two service paths, the destination node is Select one of the two service paths to receive service data; 1:1 protection refers to establishing a work path for transmitting service data for the service, and a protection path for carrying service data only when the work path is faulty.

It can be seen from the above that in order to ensure that the service can be quickly recovered from the network failure, the protection mechanism adopted is that additional network resources are needed. Obviously, this conflicts with the improvement of network usage. Especially in the case of heavy network load, the prior art approach cannot balance the service success rate and network resource utilization.

Summary of the invention

The embodiment of the present application provides a resource sharing method, a network node, and related equipment, so as to solve the problem that the prior art cannot balance the service success rate and the network resource utilization rate in the process of performing service data transmission.

To achieve the above objective, the present application provides the following technical solutions:

In a first aspect of the present application, a resource sharing method is disclosed, including:

After receiving the working path fault message, the service source node performs a resource status update determination, where the resource update determines whether the link resource between the service source node and the downstream neighbor node is faultless.

If the link resource between the service source node and the downstream neighbor node is not faulty, update the link resource status between the service source node and the downstream neighbor node to be shareable;

Sending a resource status update request message to the downstream neighboring node, where the resource status update request message includes link resource status information between the service source node and the downstream neighboring node.

In the first implementation manner provided by the first aspect of the present application, the method further includes:

If the link resource between the service source node and the downstream neighbor node is faulty, the link resource status is not updated, or the link resource status between the service source node and the downstream neighbor node is updated to Not shareable.

In the second implementation manner provided by the first aspect of the present application, the resource status update request message further carries request information that requires the downstream neighboring node to perform the resource status update determination.

In a third implementation manner provided by the first aspect of the present application, after updating the link resource status between the service source node and the downstream neighboring node to be sharable, the method further includes:

The service source node floods the link that can be shared between the service source node and the downstream neighbor node.

In the third implementation manner of the resource sharing method, the service source node is flooded in the foregoing manner, and the link resources that are not faulty are temporarily released to be used by other services in the network, thereby ensuring service success. Based on the rate, the utilization of network resources is also improved.

In a fourth implementation manner provided by the first aspect of the present application, before updating the link resource status between the service source node and the downstream neighboring node to be sharable, the method further includes:

Pre-determined link resource configuration information exists in the service source node, determining that the link resource configuration information is sharable, and/or the service source node receives a link resource from the downstream neighboring node. The source configuration indication information indicates that the link resource configuration indication information is shareable.

Based on the fourth implementation manner of the resource sharing method disclosed above, the service source node is pre-set with the condition that the link related to the link can be shared or the link resource configuration, and the condition for flooding is increased, and the resource sharing can be further implemented. Whether or not flooding is more diversified.

In a fifth aspect provided by the first aspect of the present application, the method further includes: setting a flooding condition;

The flooding condition includes flooding the links between the arbitrarily shareable nodes to other nodes located in the same routing domain, or flooding the nodes to other working paths having a lower priority than the working path. One or a combination of two links between sharable nodes;

Correspondingly, the flooding of the shareable link includes:

Flooding the shareable link according to the flooding conditions.

Based on the fifth implementation manner of the resource sharing method disclosed above, flooding is performed based on the set flooding conditions to improve the accuracy of flooding.

In the sixth mode provided by the first aspect of the present application, the method further includes:

And receiving, by the service destination node, a second feedback message that is sent by using a signaling manner, where the second feedback message includes complete link resource state information of the working path;

The complete link resource status information refers to link resource status information between the nodes constituting the working path.

In the seventh aspect provided by the first aspect of the present application, the method further includes:

Receiving, by the node corresponding to the other service, an advertisement message, and marking, according to the advertisement message, that the link resource between the corresponding nodes is occupied;

The information that the sharable link resources between any nodes in the working path that are carried in the advertisement message are occupied by nodes corresponding to other services.

In the eighth aspect provided by the first aspect of the present application, the method further includes:

After receiving the service service failure recovery message, query whether there are link resources in the shared link resource that are not used by other services;

If all are not used by other services, the protection path directly falls back to the original working path;

If part of the service is not used, if the service policy is satisfied, the protection path is rolled back to a part of the sharable link resources that are not used by other services. The partial protection path and part of the original working path constitute a new job. Path

If all are used by other services, if the user policy allows, the original service is downgraded, and all resources are released, and a new work path is re-established;

Or, when it is queried that the sharable link resource is partially or completely occupied by the service with low priority, disconnecting the tradable link resource of the original service that is used in the working path of the low priority service, and Roll back directly from the protection path to the original working path.

Based on the resource sharing method disclosed above, in the process of the original service rollback, the eighth method disclosed above can be used to guide all the original services to fall back, or partially fall back, or re-establish the working path, and improve the efficiency of the rollback.

In a second aspect of the present application, a network node is disclosed, including:

a first determining module, configured to: after receiving the working path fault message, the network node performs a resource status update determining, where the resource update is determined to determine a link between the network node and a downstream neighboring node of the service source node Whether the resource is fault free;

The first update module, configured to: link resource status between the network node and the downstream neighboring node when link resources between the network node and the downstream neighboring node are not faulty Updated to shareable;

And a first sending module, configured to send a resource status update request message to the downstream neighboring node, where the resource status update request message includes link resource status information between the network node and the downstream neighboring node.

In the first implementation manner provided by the second aspect of the present application, the first determining module is further configured to:

If the link resource between the network node and the downstream neighboring node is faulty, the link resource state is not updated;

The first update module is further configured to update a link resource status between the network node and a downstream neighboring node when a link resource between the network node and the downstream neighboring node is faulty Not shareable.

In the second implementation manner provided by the second aspect of the present application, the method further includes:

a first flooding module, configured to share the link resource status between the network node and the downstream neighbor node after being sharable, and share the network node with the downstream neighbor node The link is flooded.

In a third implementation manner provided by the second aspect of the present application, the method further includes:

a first determining module, configured to perform preset link resource configuration information existing in the network node before updating a link resource status between the network node and the downstream neighboring node to be sharable Confirming that the link resource configuration information is sharable;

and / or,

a first receiving module, configured to receive link resource configuration indication information from the downstream neighboring node, before updating a link resource status between the network node and the downstream neighboring node to be sharable The link resource configuration indication information indicates that sharing is possible.

In a fourth implementation manner provided by the second aspect of the present application, the first flooding module is further configured to flood a link between any sharable nodes according to the set flooding condition;

The flooding condition includes flooding the links between the arbitrarily shareable nodes to other nodes located in the same routing domain, or flooding the nodes with other working paths having a lower priority than the working path. A combination of one or both of the links between any shareable nodes.

In a fifth implementation manner of the second aspect, the first receiving module is further configured to receive a second feedback message that is sent by the service destination node by using a signaling manner, where the second feedback message includes the working path. Link resource status information; the link resource status information refers to link resource status information between nodes constituting the working path.

In a sixth implementation manner of the second aspect, the first receiving module is further configured to: receive a notification message sent by a node corresponding to another service, and mark a chain between the corresponding nodes based on the notification message. Road resources are occupied;

In a seventh implementation manner provided by the second aspect of the present application, the method further includes: a back-off module, configured to: after the network node receives the working service failure recovery message, query whether there is any unshared link resource The link resources used by other services; if all are not used by other services, the protection path directly falls back to the original working path; if some of the services are not used by other services, the protection path is rolled back to the case where the service policy is satisfied. In some sharable link resources that are not used by other services, the partial protection path and part of the original working path form a new working path; if all are used by other services, the original service is downgraded if the user policy allows Process and release all resources to re-establish a new working path;

or,

The fallback module is further configured to: when the network node queries that part or all of the sharable link resources are occupied by a service with a low priority, disconnecting the working path of the low priority service The shareable link resource of the original service and directly fall back from the protection path to the original working path.

A third method of the present application discloses a network node, including: a first memory, and a first processor connected to the memory;

The first memory is configured to store an operation process of the network node performing resource sharing;

The first processor is configured to perform an operation flow of the resource sharing of the network node, where the operation flow of the resource sharing includes: after receiving the working path fault message, the network node performs a resource status update judgment The resource update is determined to determine whether the link resource between the network node and a downstream neighboring node of the network node is faultless;

If the link resource between the network node and the downstream neighboring node is not faulty, update the link resource status between the network node and the downstream neighboring node to be shareable;

Sending a resource status update request message to the downstream neighboring node, where the resource status update request message includes link resource status information between the network node and the downstream neighboring node.

In a fourth aspect of the present application, a resource sharing method is disclosed, including:

After receiving the resource status update request message sent by the upstream neighboring node, the intermediate node performs a resource status update determination, where the resource status update determines that the link resource between the intermediate node and the downstream neighboring node of the intermediate node is determined. Whether there is no fault;

If the link resource between the intermediate node and the downstream neighboring node is not faulty, update the link resource status between the intermediate node and the downstream neighboring node to be shareable;

Sending, by the downstream neighboring node, the resource status update request message, where the resource status update request message includes link resource status information between the intermediate node and the downstream neighboring node;

Sending a first feedback message to the upstream neighboring node, where the first feedback message includes: sharable link resource configuration indication information indicating that the upstream neighboring node is flooded and related to itself.

In the first implementation manner provided by the fourth aspect of the present application, the method further includes:

If the link resource between the intermediate node and the downstream neighboring node is faulty, the link resource state is not updated, or the link resource status between the intermediate node and the downstream neighboring node is updated to Not shareable.

In the second implementation manner provided by the fourth aspect of the present application, the resource status update request message further carries request information that requires the downstream neighboring node to perform the resource status update determination.

In a third implementation manner provided by the fourth aspect of the present application, the method further includes:

Flooding the link that can be shared between the upstream neighboring node and the intermediate node, and flooding the link that can be shared between the intermediate node and the downstream neighboring node.

Specifically, after the receiving, by the intermediate node, the first feedback message sent by the downstream neighboring node, the upstream neighboring node and the obtained resource status update request message sent by the upstream neighboring node are obtained. The link that can be shared between the intermediate nodes is flooded, and the link that can be shared between the intermediate node and the downstream neighboring node is flooded;

Or acquiring link resource state information between the upstream neighboring node and the intermediate node included in the resource state update request message sent by the upstream neighboring node, and after confirming that the resource state is sharable, the upstream phase is A link that can be shared between the neighboring node and the intermediate node is flooded;

After updating the link resource status between the intermediate node and the downstream neighbor node to be shareable, the link that can be shared between the intermediate node and the downstream neighbor node is flooded.

In the third implementation manner of the resource sharing method, the intermediate node is flooded in the foregoing manner, and the link resources that are not faulty are temporarily released to be used by other services in the network, thereby ensuring the improvement of the service success rate. On the basis of, while improving the utilization of network resources.

In a fourth implementation manner of the fourth aspect, the method further includes: the preset link resource configuration information exists in the intermediate node, determining that the link resource configuration information is shareable, and/or The intermediate node receives link resource configuration indication information from the downstream neighboring node, and the link resource configuration indication information indicates that it is shareable.

Based on the fourth implementation manner of the resource sharing method disclosed above, the intermediate node is pre-set whether the link related to the link can be shared or the link resource configuration, and whether the condition for flooding is increased, and the resource sharing can be further implemented. Whether or not flooding is more diversified.

In a fifth implementation manner provided by the fourth aspect of the present application, the method further includes:

Receiving the acknowledgment information sent by the upstream neighboring node, determining whether the resource configuration between the intermediate node and the upstream neighboring node is equal, or whether the carried service attributes are consistent;

If the resource configuration is the same or the service attributes are consistent, the correct information is fed back;

If the resource configuration is not equal or the service attributes are inconsistent, the error message is fed back.

In a sixth implementation manner provided by the fourth aspect, the method further includes: setting a flooding condition;

The flooding condition includes flooding the link resource state information between the arbitrarily shareable nodes to other nodes located in the same routing domain, or flooding the nodes with other working paths having a lower priority than the working path. One or a combination of two link resource state information between any shareable nodes.

In a fifth aspect of the present application, a network node is disclosed, including:

a second determining module, configured to: after receiving, by the network node, the resource status update request message sent by the upstream neighboring node, perform a resource status update determination, where the resource update is determined to determine a link between the network node and a downstream neighboring node Whether the resource is fault free;

The second update module is configured to update a link resource status between the network node and the downstream neighboring node when the link resource between the network node and the downstream neighboring node is faultless Is shareable;

a second sending module, configured to send the resource status update request message to the downstream neighboring node, where the resource status update request message includes a link resource status between the network node and the downstream neighboring node And the first feedback message is sent to the upstream neighboring node, where the first feedback message includes: leasable link resource configuration indication information indicating that the upstream neighboring node is flooded with itself.

In a first implementation manner disclosed in the fifth aspect of the present application, the second determining module is further configured to not update if the link resource between the network node and the downstream neighboring node is faulty. Link resource status;

The second update module is further configured to: when the link resource between the network node and the downstream neighboring node is faulty, connect the link between the network node and the downstream neighboring node The resource status is updated to be unshareable.

In a second implementation manner disclosed in the fifth aspect of the present application, the method further includes:

a second flooding module, configured to flood a link that is sharable between the upstream neighboring node and the network node, and a chain that is shareable between the network node and the downstream neighboring node The road is flooded.

In a third implementation manner disclosed in the fourth aspect of the present application, the method further includes:

a second determining module, configured to link resource resources of the network node and the downstream neighboring node Before the state is updated to be sharable, the preset link resource configuration information existing in the network node is confirmed, and the link resource configuration information is determined to be shareable;

and / or,

The second receiving module is configured to receive link resource configuration indication information from the downstream neighboring node before updating a link resource status between the network node and the downstream neighboring node to be sharable The link resource indication information indicates that sharing is possible.

In a fourth implementation manner disclosed in the fifth aspect of the present application, the second determining module is further configured to receive the acknowledgement information sent by the upstream neighboring node, and determine the resource configuration between the network node and the upstream neighboring node. If the resource attributes are the same or the service attributes are the same, the correct information is fed back; if the resource configuration is not equal or the service attributes are inconsistent, the error information is fed back.

In a fifth implementation manner disclosed in the fifth aspect of the present application, the second flooding module is further configured to perform flooding according to the flooding condition;

The flooding condition includes flooding the links between the arbitrarily shareable nodes to other nodes located in the same routing domain, or flooding the nodes to other working paths having a lower priority than the working path. One or a combination of two of the links between the nodes that can be shared.

In a sixth aspect of the present application, a network node is disclosed, including: a second memory, and a second processor connected to the second memory;

The second storage is configured to store an operation process of the network node performing resource sharing;

The second processor is configured to perform an operation flow of the resource sharing of the network node, where the operation flow of the resource sharing includes: after receiving, by the network node, a resource status update request message sent by an upstream neighboring node, Performing a resource status update determination, where the resource status update is determined to determine whether the link resource between the network node and the downstream neighbor node is faultless;

Sending, by the downstream neighboring node, the resource status update request message, where the resource status update request message includes link resource status information between the network node and the downstream neighboring node;

A seventh aspect of the present application discloses a resource sharing method, including:

The service destination node receives the resource status update request message sent by the upstream neighboring node, and obtains link resource status information between the upstream neighboring node and the service destination node included in the resource status update message, and confirms the upstream Whether the link resource status information between the neighboring node and the service destination node is shareable;

After confirming that the link resource state information between the upstream neighboring node and the service destination node is sharable, performing a pan on the link that can be shared between the upstream neighboring node and the service destination node flood;

In the first implementation manner disclosed in the seventh aspect of the present application, before the flooding of the link between the upstream neighboring node and the service destination node, the method further includes:

A preset link resource configuration information exists in the service destination node, and the link resource configuration information is determined to be shareable.

Based on the first implementation manner of the resource sharing method disclosed above, the service destination node is pre-set with the condition that the link related to the link can be shared or the link resource configuration, and the condition for flooding is increased, and the resource sharing can be further implemented. Whether or not flooding is more diversified.

In a second implementation manner disclosed in the seventh aspect of the present application, the method further includes:

Receiving the acknowledgment information sent by the upstream neighboring node, determining whether the resource configuration between the service destination node and the upstream neighboring node is equal, or whether the carried service attributes are consistent;

In an eighth aspect of the present application, a network node is disclosed, including:

a third determining module, configured to receive, by the network node, a resource status update request message sent by the upstream neighboring node, and obtain a link resource between the upstream neighboring node and the network node included in the resource status update message status information;

The third flooding module is configured to: after confirming that link resource state information between the upstream neighboring node and the network is sharable, between the upstream neighboring node and the network node The shared link is flooded;

a third sending module, configured to send a first feedback message to the upstream neighboring node, where the first feedback message includes: a sharable link resource configuration indication indicating that the upstream neighboring node is flooded and related to itself information.

In a first implementation manner disclosed in the eighth aspect of the present application, the method further includes: a third determining module, configured to: before flooding the link between the upstream neighboring node and the network node, A preset link resource configuration information is confirmed in the network node, and the link resource configuration information is determined to be shareable.

In a second implementation manner disclosed in the eighth aspect of the present application, the third determining module is further configured to receive the acknowledgement information sent by the upstream neighboring node, and determine the resource configuration between the network node and the upstream neighboring node. If the resource attributes are the same or the service attributes are the same, the correct information is fed back; if the resource configuration is not equal or the service attributes are inconsistent, the error information is fed back.

A ninth aspect of the present application discloses a network node, including: a third memory, and a third processor connected to the third memory;

The third storage is configured to store an operation process of the network node performing resource sharing;

The third processor is configured to perform an operation process of resource sharing of the network node, where the operation process of the resource sharing includes: receiving, by the network node, a resource status update request message sent by an upstream neighboring node, acquiring the In the resource status update message, the link resource status information between the upstream neighbor node and the network node is included, and it is confirmed whether the link resource status information between the upstream neighbor node and the network node is shareable. ;

After confirming that the link resource status information between the upstream neighboring node and the network node is sharable, flooding the link that can be shared between the upstream neighboring node and the network node;

A network resource sharing system is disclosed in the tenth aspect of the present application, comprising: the network node disclosed in the second aspect and the third aspect of the present application, the network node disclosed in the fifth aspect and the sixth aspect of the present application, and a network node disclosed in the eighth aspect and the ninth aspect of the present application;

The working nodes of the above network nodes form a service.

In an eleventh aspect of the present application, a resource sharing method is disclosed, including:

After receiving the working path fault message, the service source node reports the working path fault message to the centralized controller;

Receiving, by the centralized controller, a resource shareable message, where the resource shareable message includes link resource state information between adjacent nodes in the working path;

Determining, according to the link resource status information, whether link resource status information between the service source node and a downstream neighbor node is sharable;

If the link resource status information between the service source node and the downstream neighbor node is sharable, the service source node floods the shareable link;

The service source node sends the resource shareable message to the downstream neighboring node.

In a first implementation manner disclosed in the eleventh aspect of the present application, the service source node sends the resource shareable message to the downstream neighboring node, including:

The service source node deletes information related to the service source node in the resource sharable message, and sends the truncated resource sharable message to the downstream neighboring node.

By transmitting the truncated resource sharable message to the downstream neighboring node, the efficiency of the downstream neighboring node to find information related to itself can be improved.

In a second implementation manner disclosed in the eleventh aspect of the present application, the method further includes:

If the link resource status information between the service source node and the downstream neighbor node is not shareable, the service source node does not perform flooding, and sends the resource shareable message to the Downstream neighbors.

In a third implementation manner disclosed in the eleventh aspect of the present application, when the downstream neighboring node is an intermediate node, the intermediate node receives and determines, in the resource sharable message sent by the upstream neighboring node, Whether the included intermediate node and the upstream neighboring node, and the link resource state information between the intermediate node and the downstream neighboring node have sharable link resource state information;

If the intermediate node and the upstream neighboring node, and the link resource state information between the intermediate node and the downstream neighboring node have sharable link resource state information, the intermediate node is panned a link that can be shared;

The intermediate node sends the resource sharable message to the downstream neighboring node.

In a fourth implementation manner disclosed in the eleventh aspect of the present application, the intermediate node sends the resource shareable message to the downstream neighboring node, including:

And deleting, by the intermediate node, the information related to the intermediate node in the resource sharable message sent by the upstream neighboring node, and sending the truncated resource sharable message to the downstream neighboring node.

In a fifth implementation manner disclosed in the eleventh aspect of the present application, the method further includes:

If the intermediate node and the upstream neighboring node, or the link resource state information between the intermediate node and the downstream neighboring node are not shareable, the intermediate node does not perform flooding, and The resource shareable message sent by the upstream neighboring node is sent to the downstream neighboring node.

In a sixth implementation manner disclosed in the eleventh aspect of the present application, when the downstream neighboring node is a service destination node, the service destination node receives and determines the resource sharing message sent by the upstream neighboring node. Whether the link resource status information between the service destination node and the upstream neighbor node is sharable;

If the link resource status information between the service destination node and the upstream neighbor node is sharable, the service destination node floods the shareable link.

In the seventh implementation manner disclosed in the eleventh aspect of the present application, the method further includes:

If the link resource status information between the service destination node and the upstream neighbor node is not sharable, the service destination node does not perform flooding.

In an eighth implementation manner disclosed in the eleventh aspect of the present application, the resource shareable message further carries a flooding condition;

In the ninth implementation manner disclosed in the eleventh aspect of the present application, after the service source node receives the working path failure recovery message, the method further includes:

Transmitting, by the service source node, the working path failure recovery message to a centralized controller;

Receiving, by the centralized controller, control information generated based on the working path failure recovery message to evaluate the complexity restored to the original working path;

Performing a rollback operation according to the control information;

The control information includes:

If the complexity is lower than the preset complexity, the service is controlled to fall back from the protection path to a part of the shareable link that is not used by other services according to the state in which the shareable link resource in the original working path is partially occupied. The resource is forcibly rolled back to the original working path according to the state in which the sharable link resource in the original working path is occupied by part or all of the service with low priority;

If the complexity is higher than the preset complexity, recalculate a working path and feed back the service source node.

A twelfth aspect of the present application discloses a network resource sharing system, including: a centralized controller, a service source node, an intermediate node, and a service destination node;

The service source node, the intermediate node, and the service destination node constitute a working path of the service;

The centralized controller centrally determines whether the link between the service source node, the intermediate node, and the service destination node is sharable.

The above-mentioned technical solution for resource sharing disclosed in the present application is performed by using a protection path to transmit data after a service has failed due to a failure of a working path, and whether each link on the working path has a fault with the related link. It is judged that the link resources that have not failed are temporarily released from each node and used by other services in the network, thereby improving the utilization rate of the network resources while ensuring the improvement of the service success rate.

DRAWINGS

In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings to be used in the description of the prior art will be briefly described below. It is obvious that the drawings in the following description are only the invention. For some examples, other figures may be obtained from those of ordinary skill in the art in light of the inventive work.

1 is a schematic diagram of a network topology structure and related information of service 1 according to Embodiment 1 of the present application;

2 is a schematic flowchart of a resource sharing method according to Embodiment 1 of the present application;

3 is a schematic flowchart of a resource sharing method according to Embodiment 2 of the present application;

4 is a schematic diagram of a network topology structure and related information of service 2 according to Embodiment 3 of the present application;

FIG. 5 is a schematic flowchart of a resource sharing method according to Embodiment 3 of the present application;

FIG. 6 is a schematic diagram of a network topology structure and related information of service 3 according to Embodiment 4 of the present application;

FIG. 7 is a schematic structural diagram of a network node according to Embodiment 5 of the present application;

FIG. 8 is a schematic structural diagram of another network node according to Embodiment 5 of the present application;

FIG. 9 is a schematic structural diagram of another network node according to Embodiment 5 of the present application;

10 is a schematic structural diagram of hardware of each node disclosed in Embodiment 5 of the present application;

FIG. 11 is a schematic structural diagram of a network resource sharing system according to Embodiment 5 of the present application;

FIG. 12 is a schematic structural diagram of another network resource sharing system according to Embodiment 5 of the present application.

detailed description

The following is the full name and Chinese interpretation of the English abbreviation used in the specific embodiment of the present application:

ITU-T: International Telecommunication Union-Telecommunication Standardization Sector, International Telecommunication Union - Telecommunication Standardization Sector;

ASON: Automatically Switched Optical Network, automatic switched optical network;

IETF: Internet Engineering TaskForce, Internet Engineering Task Force;

GMPLS: Generalized Multi-Protocol Label Switching, extended multi-protocol label switching;

OSPF-TE: Open Shortest Path First-Traffic Engineering, open shortest path priority for traffic engineering extensions;

RSVP-TE: Resource ReserVation Protocol-Traffic Engineering, resource reservation protocol for traffic engineering extension;

PCE: Path Computation Element, path calculation unit;

PCC: Path Computation Client path calculation client;

PCECP: Path Computation Element Communication Protocol, used for communication between PCE and PCC;

LSP: Label SwitchedPath, label switching path;

SDN: Software DefinedNetwork, software defined network.

The technical solutions in the present application will be clarified below in conjunction with the drawings in the specific embodiments of the present application. BRIEF DESCRIPTION OF THE DRAWINGS It is apparent that the described embodiments are only a part of the examples of the present application, and not all examples. All other examples obtained by a person of ordinary skill in the art based on the embodiments of the present application without creative efforts are within the scope of the present application.

It can be seen from the prior art that in the prior art, when a link in a service working path fails, in order to ensure that the service can quickly recover from the network failure, the adopted protection mechanism needs to use additional network resources, so that although It can improve the service success rate, but it occupies additional network resources, and other normal paths in the working path where the faulty link is located cannot be used by other services because of exclusive reasons, especially in network load comparison. In the case of heavy, the prior art approach is even more incapable of balancing service success rate and network resource utilization.

Thus, the present application discloses a technical solution for resource sharing, which refers to a collective name of an entity in a network that can be used to deliver service data. Including: link resources and node resources, etc., wherein the link resource is a kind of resource, which refers to using an actual physical carrier (such as: a fiber) to move customer data from one location to another; node resources, It refers to the ability to perform necessary processing on the business, for example, to convert the signal type of the customer from an electrical signal to an optical signal; or to exchange business data from one entry to another. The specific node function depends on the specific functional requirements. In the resource sharing technical solution disclosed in the present application, it mainly relates to a link resource that does not fail on a working path that actually belongs to the service after the data is transmitted by the protection path due to the failure of the working path in a certain service. It is temporarily released for use by other services in the network, thereby improving the utilization rate of network resources while ensuring the improvement of business success rate.

The specific implementation process is described in detail by the specific embodiments disclosed in the present application.

Embodiment 1

As shown in FIG. 1 , it is a schematic diagram of a network topology structure and service related information (LSP1) disclosed in Embodiment 1 of the present invention;

The service source node of the service one (LSP1) is A, the service destination node is B, and the link bandwidth between the node and the node is 1, so the service 1 can be simply referred to as LSP1 (A, B, 1).

The protection type of the service path is 1:1 protection. The working path is: A-E-F-B (LSP1_W), and the protection path is: A-G-H-I-J-B (LSP1_P). In this embodiment, when one or more links in the working path LSP1_W of the service one fails, protection switching needs to be performed, that is, the service is from LSP1_W is switched to LSP1_P. Also, it is assumed that other links in the working path LSP1_W that have not failed can be used as shared resources for other services in the network. In the present embodiment, it is assumed that the link F-B between the node F and the node B fails. For the other fault-free link AEs in the working path LSP1_W of the LSP1 (A, B, 1), the link EF is shared, that is, the link AE and the link EF are specifically shared by using the resource sharing method disclosed in the present application. The sharing process is shown in the following example;

Example one

In the first example, a specific flowchart for performing sharing on the link A-E and the link E-F is as shown in FIG. 2:

S100: After receiving the working path fault message, the service source node A performs a resource status update determination, where the resource update determines whether the link resource between the current node and the downstream neighbor node is faultless.

S101: The link AE between the service source node A and the intermediate node E (the downstream neighboring node of the service source node A) is faultless, and the service source node A updates the link resource status of the corresponding link AE in the working path to Shareable

S102: The service source node A sends a first resource status update request message to the intermediate node E.

In the step S102 of the embodiment, the first resource status update request message includes the link resource status information of the link AE, and the link resource of the link AE is the link resource of the link AE. Status information indicates that the link AE can be shared;

In the example disclosed in the present application, the first resource status update request, preferably, the request information that requires the downstream neighboring node to perform the resource status update determination may be represented by the link resource status information, or may be independently carried;

S103: The intermediate node E receives the first resource status update request message, and performs a link EF between the intermediate node E and the intermediate node F (the downstream neighboring node of the intermediate node E), and the resource status update judgment of whether the link resource is faultless ;

In the example disclosed in the present application, after the intermediate node E receives the first resource status update request message sent by the service source node A, the resource update determination is performed;

S104: The link resource status of the link E-F between the intermediate node E and the intermediate node F is no fault, and the intermediate node E updates the link resource status of the corresponding link E-F in the working path to be sharable;

S105: The intermediate node E sends a second resource status update request message to the intermediate node F.

In step S105 of this embodiment, the second resource status update request message includes the link E-F. Link resource status information, because the link resource status of the link E-F is sharable, the link resource status information of the link E-F indicates that the link E-F can be shared;

S106: The intermediate node F receives the second resource status update request message, and performs a link FB between the intermediate node F and the service destination node B (the downstream neighboring node of the intermediate node F), and whether the link resource has a faultless resource status. Update judgment

S107: The link state of the link F-B between the intermediate node F and the service destination node B is a fault, and the intermediate node F sends a third resource status update request message to the service destination node B.

In step S108 of this embodiment, the third resource status update request message includes link resource status information of the link FB. If the link FB fails, the link resource status information of the link FB indicates the link. FB has a fault;

S108: The service destination node B receives the third resource status update request message, and determines whether the link resource status information of the link F-B included in the third resource status update request message indicates that the link F-B is shareable.

In the step S108 of the embodiment, the third resource status update request message received by the service destination node B may include request information that requires the downstream neighboring node to perform the resource status update determination, but because the service destination node B is the working path. The last node on the node, therefore, the service destination node B does not need to judge whether the link resources between itself and the downstream neighbor nodes are sharable, and only needs to make a judgment on whether to flood;

S109: The link resource status information of the link FB indicates that the link FB is faulty, and the service destination node B does not perform flooding, and the service destination node B sends the first to the intermediate node F (the upstream adjacent node of the service destination node B) Feedback message

In step S111 of the present embodiment, the link resource state information of the link F-B indicates that the link F-B is faulty due to the assumption based on the present embodiment. Therefore, after the judgment of step S108 is passed, it is confirmed that the link F-B is faulty and cannot be shared, and flooding is not required. The first feedback message includes: sharable link resource configuration indication information indicating that the upstream neighboring node is flooded and related to itself;

S110: After receiving the first feedback message, the intermediate node F floods the sharable link E-F obtained in the received second resource status update request message.

Because the F-B link is faulty in this embodiment, in the process of performing flooding in step S110 of this embodiment, after receiving the first feedback message, the intermediate node F is aware of the known shared chain. The road E-F floods to share the link E-F in the routing domain.

S111: The intermediate node F sends a first feedback message to the intermediate node E (the upstream neighboring node of the intermediate node F), where the first feedback message includes: an indication indicating that the upstream neighboring node floods the susceptible link related to itself information;

S112: After receiving the first feedback message, the intermediate node E performs the sharable link AE obtained in the received first resource status update request message, and the sharable link EF obtained through the self-determination. Flooding

In step S116 of the embodiment, the shareable link EF is determined by the intermediate node E after performing step S103 and step S104; the intermediate node E is known to be related to the first feedback message after receiving the first feedback message. The sharable link EF and the link AE are flooded to share the link EF and the link AE in the routing domain;

It should be noted that flooding may be performed based on the OSPF protocol, or flooding may be performed based on other protocols;

S113: The intermediate node E sends a first feedback message to the service source node A (the upstream neighboring node of the intermediate node E), where the first feedback message includes: indicating that the upstream neighboring node floods the susceptible link related to itself. Indication information;

S114: After receiving the first feedback message, the service source node A floods the sharable link A-E that has been determined by itself.

In step S114 of this embodiment, the shareable link A-E is determined by the service source node A after performing step S101. As described above, after receiving the first feedback message, the service source node A floods the known LINK-shared links A-E, and implements sharing of the links A-E in the routing domain.

After the link FB in the working path LSP1_W of the LSP1 is faulty, the resource sharing mode disclosed in the present application is used to update the link EF and the link EF of the working path to the shared link. The nodes that are related to themselves and have no faults are flooded across the network, so that other nodes in the network can be notified that these updates are sharable links.

That is to say, in a certain service, because the link in the working path fails, and the data is transmitted by using the protection path, the link resources that are actually in the working path of the service are not temporarily released, and Use of other services in the network, so as to ensure the success rate of the business, At the same time, the utilization of network resources is improved.

Example two

In the second example, the flow of performing sharing on the link A-E and the link E-F is different from that in the first example in that:

After confirming that the respective related links are sharable, each node directly floods the link that can be shared between the respective neighboring nodes, and does not need to perform resource update judgment on each node in the entire working path. After the upstream neighboring node receives the feedback message sent by the downstream neighboring node, performing flooding based on the feedback message;

That is, based on the above-mentioned example 1, in the second example, after the service source node A performs step S101, the service source node A floods the link resource status update to the shareable link A-E;

In the second example, after the step S104 is performed, the intermediate node E obtains the shareable link AE obtained in the received first resource state update request message, and the shareable information obtained through the self judgment. Link EF for flooding;

In the second example, the intermediate node F performs step S107 to confirm that the link resource of the link FB between the intermediate node F and the service destination node B is faulty, and the intermediate node F pairs the received second resource. In the status update request message, the obtained shareable link EF is flooded;

In the second example, further, when each node confirms that there is no problem with a certain link related to itself, the flooding can be performed.

For example, after the intermediate node E receives the first resource status update request message sent by the service source node A and parses the AE link resource status information indicating that the link AE can be shared, the LINK link AE is performed. Flooding.

At the same time as or after the intermediate node E performs the current flooding, it is determined whether the link resource of the link EF between the intermediate node E and the intermediate node F is faultless, and the link resource of the link EF is obtained as a faultless After that, the link EF updated to be shareable is flooded.

That is to say, in the second example, the intermediate node located on the working path can obtain the contiguous link resources of the upstream neighboring node and itself, and determine that the link resources of the neighboring node and the downstream neighboring node are shareable. After that, a flooding is performed; after receiving the link resource state information indicating that the link can be shared by the upstream neighboring node, the flooding is performed first, and the link between the neighboring node and the downstream neighboring node is determined. Once the resource is shareable, perform another flood.

Through the timing of performing flooding by each node disclosed in the foregoing example 2, it is also possible for each node to obtain or confirm the fault-free link related to itself, flooding the entire network, thereby realizing notification to other nodes in the network. These updates can be used as links in a shareable state.

The above embodiments are merely examples given in the present application, and do not limit the faulty link to the last segment, which is applicable to the case where any link on the working path fails. In the resource sharing method disclosed in the present application, for a service source node in a working path, the specific operation is:

After receiving the working path fault message, the service source node performs a resource status update judgment, and the resource update determines whether the link resource between the service source node and the downstream neighbor node is faultless.

Sending a resource status update request message to the downstream neighboring node, where the resource status update request message includes link resource status information between the service source node and the downstream neighboring node;

In the foregoing embodiment of the present disclosure, whether the service source node updates the link resource status further includes: if it is determined that the link resource between the service source node and the downstream neighbor node is faulty, the link resource is not updated. Status, or, update the link resource status between the service source node and the downstream neighbor node to be non-shareable;

In the foregoing embodiment disclosed in the present application, the method further includes: sharing, after the link resource status between the service source node and the downstream neighbor node is sharable, shareable between the service source node and the downstream neighbor node. Link flooding;

In the foregoing embodiment disclosed in the present application, for different flooding occasions, the service source node adopts the following manner:

The first type of service, the service source node receives the first feedback message sent by the downstream neighboring node, where the first feedback message includes leasable link resource configuration indication information indicating that the upstream neighboring node is flooded with itself;

The service source node floods the shareable link and does not flood the unshareable link.

Second, after the link resource status between the service source node and the downstream neighbor node is updated to be sharable, the service source node pairs the service before sending the resource status update request message to the downstream neighbor node. The link that can be shared between the source node and the downstream neighboring node is flooded.

For the intermediate nodes in the working path, the specific operations are:

After receiving the resource status update request message sent by the upstream neighboring node, the intermediate node performs a resource status update determination, and the resource update determines whether the link resource between the intermediate node and the downstream neighboring node is faultless.

If the link resource between the intermediate node and the downstream neighbor node is not faulty, update the link resource status between the intermediate node and the downstream neighbor node to be shareable;

Sending a resource status update request message to the downstream neighboring node, where the resource status update request message includes link resource status information between the intermediate node and the downstream neighboring node;

In the foregoing embodiment disclosed in the present application, whether the intermediate node updates the link resource status further includes: if it is determined that the link resource between the intermediate node and the downstream neighbor node is faulty, the link resource status is not updated, or Updating the link resource status between the intermediate node and the downstream neighbor node to be non-shareable;

In the above embodiments disclosed in the present application, the method further includes: the intermediate node floods the link that can be shared between the upstream neighboring node and the intermediate node, and the link that can be shared between the intermediate node and the downstream neighboring node. Flooding.

In the above embodiments disclosed in the present application, for different flooding occasions, the manner adopted by the intermediate node is:

The first type, after receiving the first feedback message sent by the downstream neighboring node, the first feedback message includes: leasable link resource configuration indication information indicating that the upstream neighboring node is flooded with itself;

The resource status update request message sent by the intermediate node to the upstream neighboring node, the included link between the upstream neighboring node and the intermediate node is flooded, and the intermediate node and the downstream neighboring node are shareable. Link flooding;

The unshared link between the upstream neighboring node and the intermediate node, and/or between the intermediate node and the downstream neighboring node is not flooded;

Second, the intermediate node obtains the link resource status information between the upstream neighboring node and the intermediate node included in the resource status update request message sent by the upstream neighboring node, and after being confirmed as sharable, the intermediate node is adjacent to the upstream A link that can be shared between a node and an intermediate node is flooded.

After the link resource status between the intermediate node and the downstream neighbor node is updated to be sharable, the intermediate node floods the link that can be shared between the intermediate node and the downstream neighboring node;

In the second flooding mode, after confirming the link resource state information between the upstream neighboring node and the intermediate node, the intermediate node may first perform flooding or non-flooding based on whether the result is sharable or not. After determining the link resource information of the intermediate node and the downstream neighboring node, performing flooding or no flooding based on the sharable result;

Alternatively, the link resource state information of the upstream neighboring node and the intermediate node is obtained, and the link resource state information of the intermediate node and the downstream neighboring node is determined, and then all flooding is performed based on whether the result is sharable or not. Or partial flooding, or no flooding;

For a business destination node, the specific operations are:

The service destination node receives the resource status update request message sent by the upstream neighboring node, where the resource status update request message includes link resource status information between the upstream neighboring node and the service destination node;

The service destination node obtains link resource status information between the upstream neighboring node and the service destination node in the resource status update request message sent by the upstream neighboring node;

After confirming that the link resource status information between the upstream neighboring node and the service destination node is sharable, the service destination node floods the link that can be shared between the upstream neighboring node and the service destination node;

The service destination node sends a first feedback message to the upstream neighboring node, where the first feedback message includes: sharable link resource configuration indication information indicating that the upstream neighboring node is flooded and related to itself.

In the resource sharing method disclosed in the embodiment of the present application, the service destination node does not perform flooding when it confirms that the link resource status information between the upstream neighboring node and the service destination node is not shareable;

In the resource sharing method disclosed in the embodiment of the present application, when the service source node and the intermediate node send the resource status update request message to the downstream neighboring node, the resource status update request message is required to be executed by the downstream neighboring node, and the In the process of resource sharing method, the RSVP-TE protocol is implemented. The extension adds a TLV (Type-length-value) object to the RSVP-TE protocol. The format is as follows:

Where Type (16bits, TLV type);

Length (16 bits, TLV length);

Flags (32bits, currently define an identifier: U-update (request to do resource update judgment))

The TLV can be placed in the LSP_REQUIRED_ATTRIBUTES object as an indication that the downstream neighbor nodes are required to make resource update judgments.

Similarly, in the resource sharing method disclosed in the embodiment of the present application, the service source node and the intermediate node send the sharable state of the neighboring node to the downstream neighboring node, or the intermediate node or the service destination node is adjacent to the upstream. The node, the sharable state of one or more links between the feedback nodes, in the process of performing the resource sharing method, the RSVP-TE protocol is extended, and the TLV is added in the RSVP-TE protocol ((Type-length- The value object represents the shareable state of one or more links. The specific format is as follows:

Where Type (16bits, TLV type);

Length (16 bits, TLV length);

Link ID X (link identifier, variable length): It can represent the 32-bit link IP address, and can also represent the node ID + link ID, depending on the specific link type. As long as it can be expressed to unique A network link is all right.

Status Flag (Status Indicator, Variable Productivity): In the resource sharing method disclosed in the above embodiment of the present application, the following two types of information are defined:

S (1bit): Whether it can be shared; S=1 means shareable, S=0 means shareable;

A (1 bit): Whether it has been occupied by other services. A=1: indicates occupied; A=1: indicates that it is occupied;

However, in the resource sharing method disclosed in the embodiment of the present application, the Status Flag is not limited to the two types of information, and other information may be added as needed.

In the resource sharing method disclosed in the embodiment of the present application, when the service source node, the intermediate node, and the service destination node flood the shareable link based on the OSPF protocol, a new TLV needs to be added to the OSPF protocol to indicate that the resource can be shared. Shared link resource status information. The newly defined TLV format is as follows:

Type (16 bits, TLV type), used to deliver sharable link resource status information;

Length (16 bits, TLV length);

Value (32bits), which can be used to add restrictions in the flooding process: such as Priority (3bits), which is used to indicate the highest priority of the shareable link resources that can be used.

In conjunction with the specific embodiments disclosed above, the technical solution for resource sharing disclosed in the present application, in the case of a service, fails to use the protection path to transmit data, and then passes through the nodes on the working path for the upstream and downstream. The link resources between adjacent nodes and downstream neighboring nodes are processed, which will actually belong to the working path of the service, and the fault-free link resources are updated to be shareable, and then flooded to enable sharing. The link is temporarily released for use by other services in the network, thereby improving the utilization rate of network resources while ensuring the improvement of service success rate.

Embodiment 2

Based on the resource sharing method disclosed in the foregoing embodiment of the present application, in this embodiment, for each node, a condition that the link related to the link can be shared or a link resource configuration may be set in advance, that is, each node is set in advance and related thereto. Pre-set conditions for shared or non-shareable links;

In this embodiment, before the service source node and the intermediate node update the link resource status between each of the downstream neighboring nodes to be sharable, the method further includes: the service source node and the intermediate node pair have a preset link. Resource configuration information, determining that the link resource is configured to be sharable, and/or, the service source node and the intermediate node receiving link resource configuration indication information from the downstream neighboring node, the link resource configuration indication information indicating that the information is shareable;

Before the service destination node floods the link that can be shared between the upstream neighboring node and the service destination node, the service destination node has preset link resource configuration information, and the link resource configuration information can be shared. ;

For example, each node sets link resource configuration information for a link resource between a respective node and a neighboring node, and the link resource configuration information includes link resource shareable and link resource unshareable.

The service source node sets resource configuration information for link resources between the respective nodes and downstream neighboring nodes. The intermediate node sets resource configuration information for the link resources between the intermediate node and the upstream neighboring node and the downstream neighboring node respectively. The service destination node sets resource configuration information for the link resource between the service destination node and the upstream neighbor node. If any one of the two adjacent nodes sets the link resource to be unshareable, the link resources between the two nodes are not shareable. Or, if the resource configuration information set on two adjacent nodes is inconsistent, the link resources between the two nodes are not shared.

Preferably, in performing the resource sharing method disclosed in the foregoing application embodiment, after the service source node receives the working path fault message, before performing the resource state update judgment, it is necessary to first determine whether the preset condition of the service source node includes A sharable configuration, when the preset condition of the service source node includes a sharable configuration, and then further determines whether there is no fault; when the preset condition of the service source node includes a non-shareable configuration, the downstream phase is directly executed. a step of the neighbor node sending a resource status update request message;

Or, after determining that there is no fault, determining whether the preset condition of the service source node includes a sharable configuration;

If the preset condition of the service source node includes a sharable configuration, the subsequent step is continued; when the preset condition of the service source node includes a non-shareable configuration, the direct sending of the downlink neighbor node is performed. The step of the source status update request message.

Similarly, the intermediate node and the service destination node also need to make the same judgment before receiving the resource status update status message sent by the upstream neighboring node, and determine whether the preset condition includes a shareable configuration or is not shareable. Configuration.

Alternatively, after the service source node and the intermediate node update the link resource status between itself and the downstream neighbor node to be shareable, further:

The service source node and the intermediate node send a confirmation message to the downstream neighboring node to confirm whether the link resource status update between the nodes can be shared, and if the error information fed back by the downstream neighbor node is received, the service source node and the middle The node re-marks the link resource status between the nodes, that is, it is marked as not shareable;

After the acknowledgment information is received by the downstream neighboring node, it is determined whether the resource configuration between the neighboring node and the upstream neighboring node is equal, or whether the carried service attributes are consistent, if the resource configuration is equal or the service attribute is consistent. , the correct information is fed back, and if the resource configuration is not equal or the service attributes are inconsistent, the error information is fed back;

That is, whether the link resources between the nodes can be marked as shareable, and need to be confirmed by the upstream neighbor nodes and the downstream neighbor nodes;

Specifically, the operation between the service source node A and the intermediate node E (which is the downstream neighboring node of the service source node A) is taken as an example, as shown in FIG. 3:

S200: After receiving the working path fault message, the service source node A performs a resource status update judgment, where the resource update determines to determine the link AE between the service source node A and the downstream neighboring node, and whether the link resource is faultless. If the link resource of the link AE between the service source node A and the intermediate node E is not faulty, the process proceeds to S201. If the link resource of the link AE between the service source node A and the intermediate node E is faulty, the link resource is directly executed. S202;

S201: The service source node A updates the status of the corresponding A-E link resource in the working path to be shareable.

S202: The service source node A sends the sharable A-E link resource status information to the intermediate node E.

S203: The intermediate node E receives the vestable AE link resource state information, and determines whether the resource configuration between the intermediate node E and the service source node A is equal, or determines the service attribute carried by the intermediate node E and the service source node A. Whether it is consistent, if it is identical or consistent, it feeds back the correct information to the service source node A, and executes S205; if it is not identical or inconsistent, it feeds back the error information to the service source node A, And executing S204;

S204: The service source node A updates the status of the corresponding A-E link resource in the working path to be unshared.

S205: The service source node A sends a resource status update request message to the intermediate node E.

Referring to the above example 1, whether to update the link resource state information between the nodes in the resource sharing method disclosed in the present application, and considering the resource configuration between the execution node and the downstream neighboring nodes, can more accurately mark or update the inter-nodes. The link resource status, further, makes the link resource status between the marked or updated nodes more stable when they are shareable.

Based on the foregoing resource sharing method disclosed in Embodiment 1 of the present application, in this embodiment, for each node, flooding may be performed based on a conventional manner, or the same or different flooding conditions may be set for each node, thereby Each node performs flooding based on flooding conditions;

Preferably, in the resource sharing method disclosed in Embodiment 2 of the present application, when the service source node, the intermediate node, and the service destination node are flooded to obtain link resource state information between any sharable nodes acquired by the flooding, various types of information may be used. Ways include

The first type can flood the link resource status information between the shared nodes to other nodes in the entire network;

The second type of flooding condition can be set to limit the link resource status information of the sharable nodes in the flooding of the entire network. The specific flooding conditions can be:

First, link resource status information between any sharable nodes obtained by flooding other nodes in the same routing domain with the working path of the service (ie, the service source node, the intermediate node, and the service destination node);

Second, the link resource status information between any sharable nodes obtained by flooding the nodes in the working path of the other services whose priority is lower than the service;

Third, combining the above two restriction methods to perform two-level limitation, that is, limiting the scope of flooding to other nodes in the same routing domain as the working path of the service, and limiting the use of the sharable nodes within the range The link resource status information is a node in the working path of the other service whose priority is lower than that of the service, and then flooding; it should be noted that the scope of the above-mentioned restricted flooding or flooding to a specific node is flooded. The process can be performed in any order;

Based on the resource sharing method disclosed in the foregoing embodiment of the present application, it is required that the restrictions added in the flooding process may be specifically added to the value of the newly added TLV of the OSPF protocol, such as Priority (3 bits), which is used to indicate that the resource sharing method can be used. The highest priority of this sharable link resource.

The above-mentioned flooding method disclosed in the embodiment of the present application is only a part of the present application. In the resource sharing method disclosed in the present application, the manner of flooding is not limited thereto.

Based on the foregoing resource sharing method disclosed in Embodiment 1 of the present application, in this embodiment, each node uses a signaling manner to send a link resource status related thereto to a downstream neighboring node, and then the service destination node passes In the signaling mode, the link resource status of each node in the entire working path is fed back to the service source node, so that the service source node learns the link resource status between the nodes of the entire working path;

Preferably, in the resource sharing method disclosed in the second embodiment of the present application, the service source node receives a second feedback message sent by the service destination node by using a signaling manner, where the second feedback message includes the link resource status of the working path. Information; the link resource status information refers to link resource status information between nodes constituting the working path;

By receiving the link resource status information by the service source node, it can be known that the links in the working path are sharable, and in the process of restoring the working path, refer to whether the sharable link is occupied by other services. In order to complete the corresponding recovery work path operation.

Embodiment 3

In the resource sharing method disclosed in the embodiment of the present application, in addition to the stepwise determination by each node whether the link between the nodes is faultless, a network controller may be used to make a decision on whether to share resources between the nodes (network elements). The service LSP2 is used as an example. In this embodiment, when one or more links in the working path LSP2_W of the service 2 are faulty, the protection switching needs to be performed, that is, the service 2 is switched from LSP2_W to LSP2_P. Moreover, assuming that the other link in the working path LSP2_W does not fail, the decision of the network controller can be utilized as a shared resource for other services in the network, as shown in FIG. 4:

The centralized controller K is configured to perform centralized processing on nodes in each working path in the entire network;

The service source node of the LSP2 is A1, the service destination node is B1, and the link bandwidth between the node and the node is 1, so the LSP2 can be simply referred to as LSP2 (A1, B1, 1).

The protection type of the service path is 1:1 protection, where the working path is: A1-E1-B1, and the protection path is: A1-G1-H1-J1-B1; in this example, assume node E1 and node B1 The link E1-B1 has failed. For the process of sharing the other faulty links A1-E1 in the working path of the LSP2 (A1, B1, 1) where the link failure occurs, the specific implementation process of the resource sharing method disclosed in this embodiment of the present application is as follows: The specific flow chart is shown in Figure 5:

S301: After receiving the working path fault message, the service source node A1 reports the working path fault message to the centralized controller.

S302: The centralized controller receives the working path fault message, and calculates a shareable link resource in the working path and a link resource that is not shareable based on the working path fault message and the service policy of the centralized controller, and generates a resource shareable message. And reporting to the service source node A1; wherein the resource shareable message includes link resource state information between adjacent nodes in the working path, to indicate that link resources between those nodes can be shared;

It should be noted that the resource sharing message may further include: which type or level of services may be shared by the shareable link resource;

S303: The service source node A receives the resource sharing message, reads the link resource state information between the service source node A1 and the intermediate node E1 included in the resource shareable message, and determines the link resource state information of the link A1-E1. Whether it is sharable, if the link resource status information of the link A1-E1 is sharable, then executing S304, if the link resource status information of the link A1-E1 is not shareable, directly executing S305;

S304: The service source node A1 floods the shareable link A1-E1;

S305: The service source node A1 deletes the information related to the service source node A1 in the resource shareable message, and sends the deleted resource shareable message to the intermediate node E1;

S306: The intermediate node E1 receives the resource sharable message sent by the service source node A1, and reads the link resource status information of the link A1-E1 and the link E1-B1 included in the resource sharing message, and determines the link A1- Whether there is sharable link resource status information in the E1 and the link E1-B1, because the link resource status information of the link A1-E1 can be shared, then S307 is performed;

S307: The intermediate node E1 floods the shareable link A1-E1;

In the present embodiment, in the link resource status information of the link A1-E1 and the link E1-B1, only the link resource status information of the link A1-E1 can be shared, then in S307, the intermediate node E1 is flooded. Hong can share the link A1-E1;

S308: The intermediate node E1 deletes the information related to the intermediate node E1 in the resource sharable message sent by the service source node A1, and sends the deleted resource shareable message to the service destination node B1;

S309: The service destination node B1 receives the resource sharable message sent by the intermediate node E1, and reads the link resource status information of the link E1-B1 included in the resource sharing message, and determines the link resource status of the link E1-B1. Whether the information is sharable. Because the link resource status information of the link E1-B1 is not shareable, no flooding is performed.

In the above-mentioned embodiment of the present application, it is assumed that the link E1-B1 is faulty in the working path LSP2_W of the LSP2. Therefore, the centralized controller K performs calculation according to the fault message, and the link between each adjacent node in the working path is obtained. Can be shared, or faulty, and remove the faulty link information, integrate the shareable link resource status information, generate corresponding resource shareable message feedback to the service source node; start from the service source node, according to the resource The link resource status information of each neighboring node included in the message may be shared, and the flooding judgment is performed; after the fulfilable flooding condition is met, the corresponding flooding is performed, which will actually belong to the working path of the service, The faulty link resources are temporarily released for use by other services in the network, thereby improving the utilization of network resources while ensuring the improvement of service success rate.

The above embodiment is merely an example, and does not limit the faulty link to the last segment, which is applicable to the case where any link on the working path fails.

In the resource sharing method based on the centralized controller disclosed in the embodiment of the present application, the specific operation of the service source node in the working path is:

After receiving the working path fault message, the service source node reports the working path fault message to the centralized controller.

The service source node receives the resource sharable message fed back by the centralized controller, and the resource sharable message includes link resource state information between adjacent nodes in the working path;

The service source node determines the link resource status information between the service source node and the downstream neighbor node according to the link resource state information between the service source node and the downstream neighbor node included in the resource sharable message. Whether the interest is shareable;

The service source node sends a resource sharing message to the downstream neighbor node.

Specifically, before the resource shareable message is sent, the service source node may also delete the information related to the service source node in the resource shareable message, and send the deleted resource shareable message to the downstream neighboring node.

In addition, if the link resource status information between the service source node and the downstream neighbor node is not shareable, flooding is not performed, and the resource shareable message is sent to the downstream neighboring node.

For the intermediate nodes in the working path, the specific operations are:

The intermediate node receives the resource sharable message sent by the upstream neighboring node, and reads the intermediate node and the upstream neighboring node included in the resource sharing message sent by the upstream neighboring node, and the link between the intermediate node and the downstream neighboring node. Resource status information, and determining whether there is sharable link resource status information in the link resource status information between the intermediate node and the upstream neighbor node, the intermediate node, and the downstream neighbor node;

If there is sharable link resource status information, the intermediate node floods the shareable link;

The intermediate node sends a resource shareable message to the downstream neighboring node.

Specifically, before sending the resource sharable message, the intermediate node may also delete information related to the intermediate node in the resource sharable message sent by the upstream neighboring node, and send the revoked resource sharable message to the downstream neighboring node;

In addition, if there is no sharable link resource state information, no flooding is performed, and the resource sharable message sent by the upstream neighboring node is sent to the downstream neighboring node.

For a business destination node, the specific operations are:

The service destination node receives the resource sharable message sent by the upstream neighboring node, and reads the link resource state information between the service destination node and the upstream neighboring node in the resource sharing message sent by the upstream neighboring node, and judges the service. Whether the link resource status information between the destination node and the upstream neighbor node is sharable;

If the link resource status information between the service destination node and the upstream neighbor node is sharable, the service destination node floods the shareable link;

If the link resource status information between the service destination node and the upstream neighbor node is not shareable, the service destination node does not perform flooding.

In the resource sharing method based on the centralized controller disclosed in the embodiment of the present application, the PCEP protocol can also be used between the centralized controller and the node. In the process of using, the PCEP protocol is extended, that is, a bit is extended in the PCEP protocol. A judgment request for indicating whether the PCC requests the PCE to make a resource shareable;

To extend a bit in the PCEP protocol, the following methods can be used, but not limited to this; specifically:

Add a bit in the existing LSP object, and carry it by a PCRpt message or a PCReq message to indicate the request;

U (1 bit): indicates that it is necessary to do calculations that are shareable;

In the same manner, in the centralized controller-based resource sharing method disclosed in the embodiment of the present application, in the process of generating a resource shareable message by the centralized controller, a restriction condition may be added, and the restriction condition may be carried by the following TLV, and different The restrictions can also be distinguished by Type;

For example, the constraint may be: the priority of the sharable link resource may be used, that is, the information of the PriorityNumber is added in the Value part; or the LSP may be used. Number of shared link resources, such as LSP Number;

It should be noted that, when the feature information of the link resource state that can be shared is carried in the PCEP protocol and the RSVP-TE protocol, the feature information may be carried by using the TLV defined above.

Embodiment 4

Based on the resource sharing method disclosed in Embodiments 1 to 3 of the present application, in this embodiment, the link resources between the nodes that have not failed are flooded and shared according to the flooding or flooding conditions of the entire network. a process of establishing a working path when a node that receives a flooded sharable link receives a service request;

In the fourth embodiment of the present application, based on the network topology disclosed in FIG. 1 and the related information of LSP1, LSP3 is added for description, as shown in FIG. 6: LSP3 (C, D, BW=1), LSP1 (A) Link AE and link EF in B, BW=1) are shared;

When the service source node C receives the service request (C, D, BW=1), the process of establishing a working path mainly includes the following steps:

S401. The service source node C searches for and obtains an available link CK and a link LD between the service source node C and the service destination node D in the network, and calculates an available path between the service source node C and the service destination node D. ;

S402, when the available path is not calculated, the service source node C obtains the available link E-F based on the received flooded sharable link A-E and link E-F;

S403, the service source node C recalculates the available path by using the link C-K, the link L-D, and the link E-F, and based on the calculated available path C-K-E-F-L-D including the link E-F;

S404. The service source node C sends a resource allocation request to the originating node E corresponding to the link E-F.

S405, after receiving the permission to establish the crossover of the feedback of the originating node E, the service source node C uses the RSVP-TE message to establish a corresponding working path C-K-E-F-L-D based on the available path;

S406, the service source node C sends an advertisement message to the service source node A of the original working path where the link E-F is located, where the advertisement message carries information that the link E-F is occupied.

In the shared resource method disclosed in the embodiment of the present application, in the process of calculating the service path, the node that receives the service request in the pin network first considers whether there are available resources that are not occupied by other services in the network, if not obtained. The corresponding available path is considered to be temporarily shared among other services. Link resource. And after calculating the available path, sending a resource allocation request to the starting node of the sharable link resource included in the available path, and after the starting node feedback allows the establishment of the cross, using the RSVP-TE message, based on The calculated available path establishes a corresponding service path, and sends an advertisement message to the service source node of the service path where the sharable link resource is located, to notify that the sharable link resource is occupied.

In calculating the available path based on the sharable link resource, in the resource sharing method disclosed in the embodiment of the present application, it is preferable to limit the use of the sharable link resource and use the least shareable link resource as the calculation available. Path restrictions.

Based on the foregoing various flooding methods disclosed in the embodiments of the present application, in the present embodiment, preferably, in the resource sharing method disclosed in this embodiment of the present application, after the service fault is recovered, the service data is performed on the protection path. The transmitted service needs to be rolled back from the protection path to the working path.

In the process of the rollback, some links on the working path of the service may have been shared. Therefore, in order to ensure that the service can be successfully rolled back to the working path or the success rate of the rollback is improved, the resource sharing method is different. The flooding method uses the following methods to roll back:

Based on any flooding method, after the service fault is recovered, there is one available resource in the working path that only ensures the rollback, and there is no need to strictly roll back or use the original resource, that is, the original working path.

For the resource sharing method that is determined by the respective embodiments of the present application, whether the respective nodes determine whether they are shareable, or whether the centralized controller determines whether the shares can be shared, after determining the sharable link resources, the original service needs to be rolled back. When you go to the working path, you can use the following methods:

For the case where each node judges whether it is shareable, after the service source node receives the work path failure recovery message:

Query whether there are link resources that are not used by other services in the shared link resources. If all the services are not used by other services, the protection path directly falls back to the original working path.

If part of the service is not used by other services, the protection path is rolled back to a part of the sharable link resources that are not used by other services. The partial protection path and part of the original working path constitute a new job. path;

If all are used by other businesses, the original business will be downgraded if the user policy allows it. Rationalize and release all resources to re-establish a new working path;

Or, when the queried link resource is partially or completely occupied by the service with low priority, the tradable link resource of the original service that is used in the working path of the service with the lower priority is disconnected, and directly The protection path is rolled back to the original working path.

For the case where the centralized controller determines whether it is shareable, after the service source node receives the work path failure recovery information:

The service source node sends a working path failure recovery message to the centralized controller;

The centralized controller evaluates the complexity of restoring to the original working path based on the working path failure recovery message;

If the complexity is lower than the preset complexity, the control service is rolled back from the protection path to a part of the sharable link resources that are not used by other services, according to the state in which the sharable link resources in the original working path are partially occupied. ;

Alternatively, the control service is forcibly rolled back to the original working path according to the state in which the sharable link resource in the original working path is occupied by part or all of the service with a lower priority;

If the complexity is higher than the preset complexity, recalculate a working path and feed back the service source node;

Among them, the difficulty coefficient of the preset complexity is generally based on the power consumption required to establish a new working path.

According to the resource sharing method disclosed in the foregoing application, after the tradable link resource is flooded, if the fault of the working path of the original service has been resolved, the method is used to roll back to some or all of the original working paths. Or re-establishing a new working path, further improving the success rate of the fallback, and effectively improving the utilization of network resources.

Embodiment 5

Based on the resource sharing method disclosed in the foregoing embodiment of the present application, the embodiment of the present application further correspondingly discloses a network node structure that can implement resource sharing by a service source node, an intermediate node, and a service destination node, and has a corresponding service source node. a network resource sharing system in which the network node of the intermediate node and the service destination node function constitutes a working path of the service;

When the network resource sharing system does not include a centralized controller, or each network node does not depend on the When the controller is centralized; the network nodes having the resource sharing functions of the corresponding service source node, the intermediate node, and the service destination node are respectively described in detail;

The following describes and distinguishes between different network nodes and modules with the same or similar functions in different network nodes by using "first", "second", etc.;

As shown in FIG. 7 , a schematic diagram of a structure of a first network node that can implement resource sharing by a service source node, where the first network node 100 includes: a resource sharing method performed by a service source node for performing the foregoing disclosure. The first judging module 101, the first updating module 102 and the first sending module 103. For example, the first determining module 101 is configured to: after receiving the working path fault message, the network node performs a resource status update determination, where the resource update is determined to determine that the network node is adjacent to a downstream node of the network node. Whether the link resource is not faulty; the first update module 102 is configured to: when the link resource between the network node and the downstream neighbor node is not faulty, connect the network node to the downstream The link resource status between the nodes is updated to be sharable; the first sending module 103 is configured to send a resource status update request message to the downstream neighboring node, where the resource status update request message includes the network node and the Link resource status information between downstream neighbor nodes.

The first network node 100 disclosed in the embodiment of the present invention further includes: a first management module, configured to receive a resource allocation request sent by a node corresponding to another service, and provide feedback to the node corresponding to the other service according to the resource configuration policy. Establish cross information.

The service source node 100 disclosed in the embodiment of the present invention further includes: a first flooding module, and a first determining module and/or a first receiving module, a back-off module, and the like, to implement the resource sharing of the service source node. The module of the corresponding function in the process.

As shown in FIG. 8 , it is a schematic structural diagram of a second network node that can implement resource sharing by an intermediate node, where the second network node 200 includes: a method for performing resource sharing performed by an intermediate node, which is disclosed in the foregoing application. The second determining module 201, the second updating module 202 and the second sending module 203. For example, the second determining module 201 is configured to: after receiving, by the network node, the resource status update request message sent by the upstream neighboring node, perform a resource status update determination, where the resource update is determined to determine that the network node is adjacent to the downstream neighboring node. Whether the link resource is not faulty; the second update module 202 is configured to: when the link resource between the network node and the downstream neighbor node is not faulty, The link resource status between the network node and the downstream neighboring node is updated to be sharable; the second sending module 203 is configured to send the resource status update request message to the downstream neighboring node, where the resource status The update request message includes link resource status information between the network node and the downstream neighboring node, and sends a first feedback message to the upstream neighboring node, where the first feedback message includes an indication The upstream neighboring node floods the susceptible link resource configuration indication information related to itself.

The intermediate node 200 disclosed in the embodiment of the present invention further includes: a second management module, configured to receive a resource allocation request sent by a node corresponding to another service, and feed back to the node corresponding to the other service according to the resource configuration policy to allow the establishment of the crossover. information.

The second network node 200 disclosed in the embodiment of the present invention further includes: a second flooding module 204, and a second determining module and/or a second receiving module, etc., to implement corresponding resources in the intermediate node Functional module.

As shown in FIG. 9, a schematic diagram of a structure of a third network node that can perform resource sharing by a service destination node, where the network node 300 includes: a method for performing a resource sharing method performed by a service destination node disclosed in the above application. The third judging module 301, the third flooding module 302, and the third sending module 303. For example, the third determining module 301 is configured to receive, by the network node, a resource status update request message sent by the upstream neighboring node, and obtain the resource status update message included between the upstream neighboring node and the network node. Link resource status information; the third flooding module 302, configured to: after confirming that the link resource status information between the upstream neighboring node and the network node is sharable, to the upstream neighboring node And the third communication module 303 is configured to send a first feedback message to the upstream neighboring node, where the first feedback message includes: indicating the upstream The neighboring node floods the susceptible link resource configuration indication information related to itself.

The third network node 300 disclosed in the embodiment of the present invention further includes: a third determining module or the like, and a module for implementing the corresponding function in the resource sharing process by the intermediate node.

Each of the foregoing first network node 100, the second network node 200, and the third network node 300 performs resource sharing, and a specific process or principle related to resource sharing, and the foregoing disclosure and the Within a network node, a second network node, and a third network node Corresponding to each other, they can be referred to each other, so they will not be described here.

The resource sharing method described in connection with the embodiments disclosed herein may be implemented directly in hardware, a processor-executed memory, or a combination of both in a first network node, a second network node, and a third network node. Therefore, the present application further relates to the resource sharing method disclosed in the foregoing application embodiment, and respectively discloses a first network node, a second network node, and a third network node, which have the same structure, as shown in FIG. 10, the first The network node, the second network node, and the third network node each include a memory 10 and a processor 12 coupled to the memory 10 via a bus 11.

The memory 10 has a storage medium in which an operation flow in which respective network nodes perform resource sharing is stored.

The operation flow of the resource sharing, that is, the program corresponding to the resource sharing method for each network node disclosed above, the program may include program code, and the program code may include a series of operation instructions arranged in a certain order. The processor may be a central processing unit CPU, or a specific integrated circuit, or one or more integrated circuits configured to implement embodiments of the present application.

The memory may include high speed RAM memory and may also include non-volatile memory, such as at least one disk memory.

The processor is connected to the memory through a bus. When each network node performs resource sharing, the processor calls an operation flow of the resource sharing stored in the memory.

Based on the first network node, the second network node, and the third network node disclosed in the present application, as shown in FIG. 11, a first network node 100, a second network node 200, and a third network node are also disclosed. 300 A network resource sharing system 1 constituting a working path of a service. The dotted line in FIG. 11 indicates the first network node, the second network node, the second network node, and the like in the working paths of other services.

The resource sharing method for determining whether the link between the service source node, the intermediate node, and the service destination node is sharable based on the foregoing disclosure disclosed in the present application, the present application further discloses another network resource sharing system. As shown in FIG. 12, the network resource sharing system 4 mainly includes a centralized controller 400, a service source node 401, an intermediate node 402, and a service destination node 403.

The service source node 402, the intermediate node 403, and the service destination node 404 are based on the foregoing The method can be implemented by the corresponding module, and will not be described here. The broken lines in Fig. 12 indicate service source nodes, intermediate nodes, service destination nodes, and the like in the working paths of other services.

It should be noted that the other operations involved in the service source node, the intermediate node, and the service destination node of the method for performing resource sharing disclosed in the foregoing embodiment of the present application, such as the flooding operation for setting flooding conditions, may be referred to. The corresponding parts in the resource disclosure method disclosed in the above embodiments of the present application are not described herein again.

In summary, the present application discloses a technical solution for resource sharing, which is a chain that does not fail on the working path that actually belongs to the service after the data is transmitted by the protection path due to the failure of the working path in a certain service. The road resources are temporarily released for use by other services in the network, thereby improving the utilization rate of network resources while ensuring the improvement of the service success rate.

Further, in the flooding process, the problems involved in the rollback are considered, thereby improving the success rate of the rollback and also improving the utilization of the resources in the forward.

The above description is only the preferred embodiment of the present application, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

A resource sharing method, comprising:

After receiving the working path fault message, the service source node performs a resource status update determination, where the resource update determines whether the link resource between the service source node and the downstream neighbor node is faultless.

If the link resource between the service source node and the downstream neighbor node is not faulty, update the link resource status between the service source node and the downstream neighbor node to be shareable;

Sending a resource status update request message to the downstream neighboring node, where the resource status update request message includes link resource status information between the service source node and the downstream neighboring node.
The method according to claim 1, wherein the resource status update request message further carries request information requesting the downstream neighboring node to perform the resource status update determination.
The method according to claim 1, wherein after updating the link resource status between the service source node and the downstream neighbor node to be shareable, the method further includes:

Flooding the link that can be shared between the service source node and the downstream neighbor node.
The method according to any one of claims 1 to 3, wherein the method further updates the link resource status between the service source node and the downstream neighbor node to be shareable include:

Pre-determined link resource configuration information exists in the service source node, determining that the link resource configuration information is sharable, and/or the service source node receives link resource configuration from the downstream neighboring node Instructing information that the link resource configuration indication information indicates that sharing is possible.
A network node, comprising:

a first determining module, configured to: after receiving the working path fault message, the network node performs a resource status update determination, where the resource update determines to determine a link resource between the network node and a downstream neighboring node of the network node Whether there is no fault;

The first update module, configured to: link resource status between the network node and the downstream neighboring node when link resources between the network node and the downstream neighboring node are not faulty Updated to shareable;

a first sending module, configured to send a resource status update request message to the downstream neighboring node, where the resource status update request message includes a chain between the network node and the downstream neighboring node Road resource status information.
The network node according to claim 5, further comprising:

a first flooding module, configured to share the link resource status between the network node and the downstream neighbor node after being sharable, and share the network node with the downstream neighbor node The link is flooded.
The network node according to claim 5 or 6, further comprising:

a first determining module, configured to perform preset link resource configuration information existing in the network node before updating a link resource status between the network node and the downstream neighboring node to be sharable Confirming that the link resource configuration information is sharable;

and / or,

a first receiving module, configured to receive link resource configuration indication information from the downstream neighboring node, before updating a link resource status between the network node and the downstream neighboring node to be sharable The link resource configuration indication information indicates that sharing is possible.
A resource sharing method, comprising:

After receiving the resource status update request message sent by the upstream neighboring node, the intermediate node performs a resource status update determination, where the resource status update determines that the link resource between the intermediate node and the downstream neighboring node of the intermediate node is determined. Whether there is no fault;

If the link resource between the intermediate node and the downstream neighboring node is not faulty, update the link resource status between the intermediate node and the downstream neighboring node to be shareable;

Sending, by the downstream neighboring node, the resource status update request message, where the resource status update request message includes link resource status information between the intermediate node and the downstream neighboring node;

Sending a first feedback message to the upstream neighboring node, where the first feedback message includes: sharable link resource configuration indication information indicating that the upstream neighboring node is flooded and related to itself.
The method according to claim 8, wherein the resource status update request message further carries request information requesting the downstream neighboring node to perform the resource status update determination.
The method of claim 8 further comprising:

Flooding the link that can be shared between the upstream neighboring node and the intermediate node, and flooding the link that can be shared between the intermediate node and the downstream neighboring node.
Method according to any one of claims 8 to 10, wherein said Before the link resource status between the intermediate node and the downstream neighboring node is updated to be sharable, the method further includes:

Pre-determined link resource configuration information exists in the intermediate node, determining that the link resource configuration information is sharable, and/or the intermediate node receives link resource configuration indication information from the downstream neighboring node The link resource configuration indication information indicates that the link is sharable.
A network node, comprising:

a second determining module, configured to: after receiving, by the network node, the resource status update request message sent by the upstream neighboring node, perform a resource status update determination, where the resource update is determined to determine a link between the network node and a downstream neighboring node Whether the resource is fault free;

The second update module is configured to update a link resource status between the network node and the downstream neighboring node when the link resource between the network node and the downstream neighboring node is faultless Is shareable;

a second sending module, configured to send the resource status update request message to the downstream neighboring node, where the resource status update request message includes a link resource status between the network node and the downstream neighboring node And the first feedback message is sent to the upstream neighboring node, where the first feedback message includes: leasable link resource configuration indication information indicating that the upstream neighboring node is flooded with itself.
The network node according to claim 12, further comprising:

a second flooding module, configured to flood a link that is sharable between the upstream neighboring node and the network node, and a chain that is shareable between the network node and the downstream neighboring node The road is flooded.
The network node according to claim 12 or 13, further comprising:

a second determining module, configured to confirm preset link resource configuration information existing in the network node before updating the link resource status of the network node and the downstream neighbor node to be sharable, Determining that the link resource configuration information is shareable;

and / or,

The second receiving module is configured to receive link resource configuration indication information from the downstream neighboring node before updating a link resource status between the network node and the downstream neighboring node to be sharable The link resource indication information indicates that sharing is possible.
A resource sharing method, comprising:

The service destination node receives the resource status update request message sent by the upstream neighboring node, and obtains link resource status information between the upstream neighboring node and the service destination node included in the resource status update message, and confirms the upstream Whether the link resource status information between the neighboring node and the service destination node is shareable;

After confirming that the link resource state information between the upstream neighboring node and the service destination node is sharable, performing a pan on the link that can be shared between the upstream neighboring node and the service destination node flood;

Sending a first feedback message to the upstream neighboring node, where the first feedback message includes: sharable link resource configuration indication information indicating that the upstream neighboring node is flooded and related to itself.
The method according to claim 15, wherein before the flooding of the link between the upstream neighboring node and the service destination node, the method further comprises:

A preset link resource configuration information exists in the service destination node, and the link resource configuration information is determined to be shareable.
A network node, comprising:

a third determining module, configured to receive, by the network node, a resource status update request message sent by the upstream neighboring node, and obtain a link resource between the upstream neighboring node and the network node included in the resource status update message status information;

The third flooding module is configured to: after confirming that link resource state information between the upstream neighboring node and the network node is sharable, between the upstream neighboring node and the network node Flooding of sharable links;

a third sending module, configured to send a first feedback message to the upstream neighboring node, where the first feedback message includes: a sharable link resource configuration indication indicating that the upstream neighboring node is flooded and related to itself information.
The network node according to claim 17, further comprising:

a third determining module, configured to perform preset link resource configuration information in the service destination node before flooding the link between the upstream neighboring node and the service destination node Confirming that the link resource configuration information is sharable.
A network resource sharing system, comprising: any one of claims 5-7 The network node according to any one of claims 12 to 14, and the network node according to claim 17 or 18.

The working nodes of the service are formed between the network nodes.
A resource sharing method, comprising:

After receiving the working path fault message, the service source node reports the working path fault message to the centralized controller;

Receiving, by the centralized controller, a resource shareable message, where the resource shareable message includes link resource state information between adjacent nodes in the working path;

Determining, according to the link resource status information, whether link resource status information between the service source node and a downstream neighbor node is sharable;

If the link resource status information between the service source node and the downstream neighbor node is sharable, the service source node floods the shareable link;

The service source node sends the resource shareable message to the downstream neighboring node.
The method according to claim 20, wherein when the downstream neighboring node is an intermediate node, the intermediate node receives and determines, in the resource sharable message sent by the upstream neighboring node, the included Whether the intermediate resource and the upstream neighboring node, and the link resource state information between the intermediate node and the downstream neighboring node have sharable link resource state information;

If the intermediate node and the upstream neighboring node, and the link resource state information between the intermediate node and the downstream neighboring node have sharable link resource state information, the intermediate node is panned a link that can be shared;

The intermediate node sends the resource sharable message to the downstream neighboring node.
The resource sharing method according to claim 20 or 21, wherein when the downstream neighboring node is a service destination node, the service destination node receives and determines the resource sharing message sent by the upstream neighboring node. Whether the link resource status information between the service destination node and the upstream neighbor node is sharable;

If the link resource status information between the service destination node and the upstream neighbor node is sharable, the service destination node floods the shareable link.
A network resource sharing system, comprising: a centralized controller, a service source node, an intermediate node, and a service destination node;

The service source node, the intermediate node, and the service destination node constitute a working path of the service;

The centralized controller centrally determines whether the link between the service source node, the intermediate node, and the service destination node is sharable.