CN112803995A

CN112803995A - Resource sharing method, network node and related equipment

Info

Publication number: CN112803995A
Application number: CN202011351939.4A
Authority: CN
Inventors: 张弦; 冯皓宇
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2016-09-22
Filing date: 2016-09-22
Publication date: 2021-05-14
Anticipated expiration: 2036-09-22
Also published as: CN109644122A; WO2018053747A1; CN109644122B; CN112803995B

Abstract

After a certain service adopts a protection path to transmit data due to the fault of a working path, each node on the working path judges whether a link related to the service has the fault or not, and the link resource without the fault is temporarily released by each node to be used by other services in the network, so that the utilization rate of the network resource is improved on the basis of ensuring the success rate of the 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

The current ASON (automatic Switched Optical Network) mainly includes a management plane, a data plane (transport plane), and a control plane; the control plane and the functions provided by the control plane are supported and realized by the related architecture defined by the international standards organization and the related communication protocol.

At present, the network utilization rate of the ASON is mainly measured by the service success rate, which is the number of services successfully received and carried by the network in the total number of service requests. However, in the process of measuring the network usage of the ASON, the SLA (Service level Agreement) of the network needs to be considered, and the SLA is usually embodied by establishing different protection mechanisms for the Service. At present, in order to ensure that the service can be quickly recovered from the network failure, 1+1 protection or 1:1 protection is adopted.

The 1+1 protection refers to establishing two service paths for a service, transmitting service data from the two service paths simultaneously, and when the service data is transmitted to a destination node through the two service paths, the destination node selects one of the two service paths to receive the service data; 1:1 protection refers to establishing a working path for transmitting service data and a protection path for carrying the service data only when the working path fails.

As can be seen from the above, the adopted protection mechanism needs to use extra network resources in order to ensure that the traffic can be recovered from the network failure quickly. Obviously, there is a contradiction between this and the improvement of the network utilization rate, and especially under the condition of a heavy network load, the method in the prior art cannot give consideration to both the service success rate and the network resource utilization rate.

Disclosure of Invention

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

In order to achieve the purpose, the application provides the following technical scheme:

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

after receiving a working path fault message, a service source node executes resource state updating judgment, wherein the resource updating judgment is to judge whether a link resource between the service source node and a downstream adjacent node has no fault;

if the link resource between the service source node and the downstream adjacent node has no fault, updating the link resource state between the service source node and the downstream adjacent node to be shareable;

and sending a resource state updating request message to the downstream adjacent node, wherein the resource state updating request message comprises link resource state information between the service source node and the downstream adjacent node.

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

and if the link resource between the service source node and the downstream adjacent node has a fault, not updating the link resource state, or updating the link resource state between the service source node and the downstream adjacent node to be not sharable.

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

In a third implementation manner provided in the first aspect of the present application, after the 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 a sharable link between the service source node and a downstream neighboring node.

In a third implementation manner based on the resource sharing method, the service source node performs flooding in the manner described above, and can temporarily release the link resource that does not fail to be used by other services in the network, so that the utilization rate of the network resource is improved on the basis of ensuring that the success rate of the service is improved.

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

the service source node has preset link resource configuration information, and determines that the link resource configuration information is sharable, and/or the service source node receives link resource configuration indication information from the downstream adjacent node, wherein the link resource configuration indication information indicates sharable.

Based on the fourth implementation manner of the resource sharing method disclosed above, the condition whether the link related to the service source node can be shared or the link resource configuration is preset for the service source node, and the condition whether flooding is performed is increased, so that whether flooding is performed in resource sharing can be further diversified.

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

the flooding condition comprises one or two of flooding the link between any sharable nodes to other nodes in the same routing domain, or flooding the link between any sharable nodes to nodes of other working paths with lower priority than the working paths;

correspondingly, the flooding the sharable link includes:

flooding the sharable link according to the flooding condition.

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

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

receiving a second feedback message sent by a service destination node in a signaling mode, wherein the second feedback message comprises link resource state information with a complete working path;

the complete link resource state information refers to the link resource state information among the nodes constituting the working path.

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

receiving notification messages sent by nodes corresponding to other services, and marking occupied link resources among corresponding nodes based on the notification messages;

wherein, the notification message carries information that sharable link resources between any nodes in the working path are occupied by nodes corresponding to other services.

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

after receiving the work service fault recovery message, inquiring whether link resources which are not used by other services exist in shareable link resources;

if all the services are not used by other services, the protection path directly backs to the original working path;

if part of the link resources are not used by other services, the protection path is returned to sharable link resources which are not used by other services on the condition of meeting the service strategy, and a new working path is formed by the part of the protection path and the part of the original working path;

if all the services are used by other services, performing degradation processing on the original service under the condition that a user policy allows, releasing all resources, and reestablishing a new working path;

or, when inquiring that part or all of sharable link resources are occupied by the service with low priority, disconnecting the sharable link resources of the original service crossed and used in the working path of the service with low priority, and directly returning from the protection path to the original working path.

Based on the above-disclosed resource sharing method, in the process of backing the original service, the eighth disclosed manner is adopted, so that the original service can be guided to fully back, or partially back, or a working path is reestablished, and the efficiency of the backing is improved.

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

the first judgment module is used for executing resource state updating judgment after the network node receives the working path fault message, wherein the resource updating judgment is to judge whether the link resource between the network node and the downstream adjacent node of the service source node has no fault;

the first updating module is configured to update a state of a link resource between the network node and the downstream neighboring node to be sharable when the link resource between the network node and the downstream neighboring node is not faulty;

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 a 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 adjacent node is faulty, not updating the link resource state;

the first updating module is further configured to update the state of the link resource between the network node and the downstream neighboring node to be not sharable when the link resource between the network node and the downstream neighboring node has a fault.

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

a first flooding module, configured to flood a sharable link between the network node and the downstream neighboring node after updating a link resource state between the network node and the downstream neighboring node to sharable.

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

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

and/or the presence of a gas in the gas,

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, where the link resource configuration indication information indicates sharability.

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

the flooding condition includes one or a combination of two of flooding the link between the arbitrary sharable nodes to other nodes located in the same routing domain, or flooding the link between the arbitrary sharable nodes to a node of other working path having a lower priority than the working path.

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

In a sixth implementation manner provided by the second aspect of the present application, the method further includes: the first receiving module is further configured to receive an advertisement message sent by a node corresponding to another service, and mark that a link resource between corresponding nodes is occupied based on the advertisement message;

In a seventh implementation manner provided by the second aspect of the present application, the method further includes: a rollback module, configured to query whether a link resource that is not used by another service exists in sharable link resources after the network node receives a working service failure recovery message; if all the services are not used by other services, the protection path directly backs to the original working path; if part of the link resources are not used by other services, the protection path is returned to sharable link resources which are not used by other services on the condition of meeting the service strategy, and a new working path is formed by the part of the protection path and the part of the original working path; if all the services are used by other services, performing degradation processing on the original service under the condition that a user policy allows, releasing all resources, and reestablishing a new working path;

alternatively, the first and second electrodes may be,

the rollback module is further configured to, when the network node queries that part or all of sharable link resources are occupied by the low-priority service, disconnect the sharable link resources of the original service that is cross-used in the working path of the low-priority service, and directly rollback the sharable link resources from the protection path to the original working path.

In a third aspect of the present application, a network node is disclosed, which includes: the system comprises a first memory and a first processor connected with the memory;

the first memory is used for storing an operation flow of the network node for executing resource sharing;

the first processor is configured to execute an operation procedure of the resource sharing of the network node, where the operation procedure of the resource sharing includes: after receiving a working path fault message, the network node executes resource state updating judgment, wherein the resource updating judgment is to judge whether a link resource between the network node and a downstream adjacent node of the network node is fault-free;

if the link resource between the network node and the downstream adjacent node has no fault, updating the link resource state between the network node and the downstream adjacent node to be shareable;

and sending a resource state updating request message to the downstream adjacent node, wherein the resource state updating request message comprises link resource state information between the network node and the downstream adjacent node.

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

after receiving a resource state updating request message sent by an upstream adjacent node, an intermediate node executes resource state updating judgment, wherein the resource state updating judgment is to judge whether a link resource between the intermediate node and a downstream adjacent node of the intermediate node is faultless or not;

if the link resource between the intermediate node and the downstream adjacent node has no fault, updating the state of the link resource between the intermediate node and the downstream adjacent node to be sharable;

sending the resource state updating request message to the downstream adjacent node, wherein the resource state updating request message comprises link resource state information between the intermediate node and the downstream adjacent node;

sending a first feedback message to the upstream neighbor node, where the first feedback message includes: instructing the upstream neighboring node to flood sharable link resource configuration indication information associated with itself.

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

and if the link resource between the intermediate node and the downstream adjacent node has a fault, not updating the link resource state, or updating the link resource state between the intermediate node and the downstream adjacent node to be not sharable.

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

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

flooding links sharable between the upstream neighboring node and the intermediate node, and flooding links sharable between the intermediate node and a downstream neighboring node.

Specifically, there may be adopted: after the intermediate node receives a first feedback message sent by a downstream adjacent node, flooding an acquired sharable link between the upstream adjacent node and the intermediate node in the resource state updating request message sent by the upstream adjacent node, and flooding the sharable link between the intermediate node and the downstream adjacent node;

or, obtaining link resource state information between the upstream neighboring node and the intermediate node, which is included in the resource state update request message sent by the upstream neighboring node, and after determining that the link resource state information can be shared, flooding the sharable link between the upstream neighboring node and the intermediate node;

after updating the link resource state between the intermediate node and a downstream neighboring node to shareable, flooding the shareable link between the intermediate node and the downstream neighboring node.

In a third implementation manner based on the resource sharing method, the intermediate node performs flooding in the manner described above, and can temporarily release the link resource that does not have a fault to be used by other services in the network, so that the utilization rate of the network resource is improved on the basis of ensuring that the success rate of the services is improved.

In a fourth implementation manner provided in the fourth aspect of the present application, the method further includes: the intermediate node has preset link resource configuration information, and determines that the link resource configuration information is sharable, and/or the intermediate node receives link resource configuration indication information from the downstream adjacent node, wherein the link resource configuration indication information indicates sharable.

Based on the fourth implementation manner of the resource sharing method disclosed above, the intermediate node is preset with a condition whether the link related to the intermediate node can be shared or a link resource configuration, and a condition whether flooding is performed is increased, so that whether flooding is performed in resource sharing can be further diversified.

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

receiving confirmation information sent by an upstream adjacent node, and judging whether the resource configuration between the intermediate node and the upstream adjacent node is equal or not, or whether the loaded service attributes are consistent or not;

if the resource configuration is equal or the service attributes are consistent, feeding back correct information;

and if the resource configuration is not identical or the service attributes are not identical, feeding back error information.

In a sixth implementation manner provided by the fourth aspect of the present application, the method further includes: setting flooding conditions;

the flooding condition includes one or a combination of two of flooding the link resource state information between any sharable nodes to other nodes located in the same routing domain, or flooding the link resource state information between any sharable nodes to nodes of other working paths having a lower priority than the working paths.

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

the second judgment module is used for executing resource state updating judgment after the network node receives the resource state updating request message sent by the upstream adjacent node, wherein the resource updating judgment is to judge whether the link resource between the network node and the downstream adjacent node has no fault;

the second updating module is configured to update a state of a link resource between the network node and the downstream neighboring node to be sharable when the link resource between the network node and the downstream neighboring node is not faulty;

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 link resource status information between the network node and the downstream neighboring node, and send a first feedback message to the upstream neighboring node, where the first feedback message includes indication information indicating that the upstream neighboring node floods sharable link resource configuration information related to the upstream neighboring node.

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

the second updating module is further configured to update the state of the link resource between the network node and the downstream neighboring node to be not sharable when the link resource between the network node and the downstream neighboring node has a fault.

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 sharable link between the upstream neighboring node and the network node, and to flood a sharable link between the network node and the downstream neighboring node.

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

a second determining module, configured to determine preset link resource configuration information existing in the network node before updating the link resource statuses of the network node and the downstream neighboring node to be sharable, and determine that the link resource configuration information is sharable;

and/or the presence of a gas in the gas,

the second receiving module is configured to receive link resource configuration indication information from the downstream neighboring node before updating the link resource status between the network node and the downstream neighboring node to be sharable, where the link resource configuration indication information indicates sharability.

In a fourth implementation manner disclosed in the fifth aspect of the present application, the second determining module is further configured to receive confirmation information sent by an upstream neighboring node, and determine whether resource configurations between the network node and the upstream neighboring node are equal, or whether service attributes carried by the network node and the upstream neighboring node are consistent; if the resource configuration is equal or the service attributes are consistent, feeding back correct information; and if the resource configuration is not identical or the service attributes are not identical, feeding back error information.

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

the flooding condition includes one or a combination of two of flooding the link between any sharable nodes to other nodes located in the same routing domain, or flooding the link between any sharable nodes to a node of other working path having a lower priority than the working path.

In a sixth aspect of the present application, a network node is disclosed, which includes: the second processor is connected with the second memory;

the second memory is used for storing the operation flow of the network node for executing resource sharing;

the second processor is configured to execute an operation procedure of the resource sharing of the network node, where the operation procedure of the resource sharing includes: after receiving a resource state updating request message sent by an upstream adjacent node, the network node executes resource state updating judgment, wherein the resource state updating judgment is to judge whether a link resource between the network node and the downstream adjacent node has no fault;

if the link resource between the network node and the downstream adjacent node has no fault, updating the link resource state between the network node and the downstream adjacent node to be sharable;

sending the resource state update request message to the downstream neighboring node, wherein the resource state update request message includes link resource state information between the network node and the downstream neighboring node;

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

a service destination node receives a resource state updating request message sent by an upstream adjacent node, acquires link resource state information between the upstream adjacent node and the service destination node contained in the resource state updating message, and confirms whether the link resource state information between the upstream adjacent node and the service destination node is sharable or not;

after confirming that the link resource state information between the upstream neighboring node and the service destination node is sharable, flooding the sharable link between the upstream neighboring node and the service destination node;

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

and the service destination node has preset link resource configuration information, and the link resource configuration information is determined to be sharable.

Based on the first implementation manner of the resource sharing method disclosed above, the condition whether the link related to the service destination node can be shared or the link resource configuration is preset, the condition whether flooding is performed is increased, and whether flooding is performed in resource sharing can be further diversified.

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

receiving confirmation information sent by an upstream adjacent node, and judging whether the resource configuration between the service destination node and the upstream adjacent node is equal or not, or whether the carried service attributes are consistent or not;

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

a third judging module, configured to receive, by a network node, a resource status update request message sent by an upstream neighboring node, and acquire link resource status information between the upstream neighboring node and the network node, which is included in the resource status update message;

the third flooding module is configured to flood a sharable link between the upstream neighboring node and the network node after confirming that the link resource state information between the upstream neighboring node and the network is sharable;

a third sending module, configured to send a first feedback message to the upstream neighboring node, where the first feedback message includes: instructing the upstream neighboring node to flood sharable link resource configuration indication information associated with itself.

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

In a second implementation manner disclosed in the eighth aspect of the present application, the third determining module is further configured to receive confirmation information sent by an upstream neighboring node, and determine whether resource configurations between the network node and the upstream neighboring node are equal, or whether service attributes carried by the network node and the upstream neighboring node are consistent; if the resource configuration is equal or the service attributes are consistent, feeding back correct information; and if the resource configuration is not identical or the service attributes are not identical, feeding back error information.

In a ninth aspect of the present application, a network node is disclosed, comprising: a third memory, and a third processor coupled to the third memory;

the third memory is used for storing the operation flow of the network node for executing resource sharing;

the third processor is configured to execute an operation procedure of resource sharing of the network node, where the operation procedure of resource sharing includes: the network node receives a resource state updating request message sent by an upstream adjacent node, acquires link resource state information between the upstream adjacent node and the network node contained in the resource state updating message, and confirms whether the link resource state information between the upstream adjacent node and the network node is sharable or not;

after confirming that the link resource state information between the upstream neighboring node and the network node is sharable, flooding the sharable link between the upstream neighboring node and the network node;

In a tenth aspect of the present application, a network resource sharing system is disclosed, which includes: network nodes disclosed in the second and third aspects of the present application, network nodes disclosed in the fifth and sixth aspects of the present application, and network nodes disclosed in the eighth and ninth aspects of the present application;

and the network nodes form a service working path.

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

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

receiving a resource sharable message fed back by the centralized controller, wherein the resource sharable message comprises link resource state information between adjacent nodes in the working path;

judging whether the link resource state information between the service source node and the downstream adjacent node is sharable or not according to the link resource state information;

if the link resource state information between the service source node and the downstream neighboring node is sharable, the service source node floods the sharable link;

and the service source node sends the resource sharable message to the downstream adjacent node.

In a first implementation manner disclosed in the eleventh aspect of the present application, the sending, by the service source node, the resource sharable message to the downstream neighboring node includes:

and the service source node deletes the information related to the service source node in the resource sharable message and sends the deleted resource sharable message to the downstream adjacent node.

By sending the deleted resource sharable message to the downstream neighboring node, the efficiency of searching the information related to the downstream neighboring node can be improved.

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

and if the link resource state information between the service source node and the downstream adjacent node is not sharable, the service source node does not execute flooding and sends the resource sharable message to the downstream adjacent node.

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 whether sharable link resource state information exists in the resource sharable message sent by the upstream neighboring node, the intermediate node and the upstream neighboring node, and link resource state information between the intermediate node and the downstream neighboring node;

if sharable link resource state information exists in the link resource state information between the intermediate node and the upstream neighboring node and between the intermediate node and the downstream neighboring node, the intermediate node floods the sharable link;

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 sending, by the intermediate node, the resource sharable message to the downstream neighboring node includes:

and the intermediate node deletes the information related to the intermediate node in the resource sharable message sent by the upstream adjacent node, and sends the deleted resource sharable message to the downstream adjacent node.

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

if the link resource state information between the intermediate node and the upstream neighbor node or between the intermediate node and the downstream neighbor node is not sharable, the intermediate node does not perform flooding and transmits the resource sharable message transmitted by the upstream neighbor node to the downstream neighbor 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 whether link resource state information between the service destination node and the upstream neighboring node, which is included in the resource sharing message sent by the upstream neighboring node, is sharable;

the traffic destination node floods the sharable link if the link resource state information between the traffic destination node and the upstream neighboring node is sharable.

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

the service destination node does not perform flooding if the link resource state information between the service destination node and the upstream neighbor node is not sharable.

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

In a 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:

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

receiving control information generated by the centralized controller based on the complexity of the working path fault recovery message evaluation recovery to the original working path;

carrying out rollback operation according to the control information;

the control information includes:

if the complexity is lower than the preset complexity, controlling the service to be backed from the protection path to part of sharable link resources which are not used by other services according to the state that the sharable link resources in the original working path are partially occupied; or, according to the state that the sharable link resource in the original working path is partially or completely occupied by the service with low priority, controlling the service to forcibly roll back to the original working path;

and if the complexity is higher than the preset complexity, recalculating a working path and feeding back the service source node.

In a twelfth aspect of the present application, a network resource sharing system is disclosed, which includes: the system comprises an integrated 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 form a service working path;

and the centralized controller is used for judging whether the links among the service source node, the intermediate node and the service destination node can be shared or not in a centralized manner.

According to the technical scheme for resource sharing, after a certain service adopts a protection path to transmit data due to the fact that a working path fails, whether a link related to the service fails or not is judged by each node on the working path, and link resources which do not fail are released temporarily by each node and used by other services in a network, so that the utilization rate of network resources is improved on the basis of ensuring that the success rate of the service is improved.

Drawings

In order to more clearly illustrate the technical solutions of the present application or prior art, the drawings that are needed in the description of the prior art or in the description of the prior art will be briefly described below, and it is obvious that the drawings in the description below are only examples of the present invention, and that other drawings can be obtained by those skilled in the art without inventive effort.

Fig. 1 is a schematic diagram of a network topology and information related to a first service disclosed in an embodiment of the present application;

fig. 2 is a schematic flowchart illustrating a resource sharing method according to an embodiment of the present application;

fig. 3 is a schematic flowchart of a resource sharing method disclosed in the second embodiment of the present application;

fig. 4 is a schematic diagram of a network topology and information related to a service two disclosed in the third embodiment of the present application;

fig. 5 is a schematic flowchart of a resource sharing method disclosed in the third embodiment of the present application;

fig. 6 is a schematic diagram of related information of a network topology and a service three disclosed in the fourth embodiment of the present application;

fig. 7 is a schematic structural diagram of a network node according to the fifth embodiment of the present application;

fig. 8 is a schematic structural diagram of another network node disclosed in the fifth embodiment of the present application;

fig. 9 is a schematic structural diagram of another network node disclosed in the fifth embodiment of the present application;

fig. 10 is a schematic hardware structure diagram of each node disclosed in the fifth embodiment of the present application;

fig. 11 is a schematic structural diagram of a network resource sharing system according to a fifth embodiment of the present application;

fig. 12 is a schematic structural diagram of another network resource sharing system disclosed in the fifth embodiment of the present application.

Detailed Description

The following are full names and Chinese explanations of English abbreviations used in the detailed description of the present application:

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

ASON: automatic Switched Optical Network;

IETF: internet Engineering Task Force, Internet Engineering Task Force;

GMPLS: extended multiprotocol Label Switching, Generalized Multi-Protocol Label Switching;

OSPF-TE: open Shortest Path First-Traffic Engineering, which is expanded by Traffic Engineering, is preferred;

RSVP-TE: resource ReserVation Protocol-Traffic Engineering, Traffic Engineering extension;

PCE: path Computation Element, Path Computation Element;

PCC: path Computation Client;

PCECP: a Path Computation Element Communication Protocol for Communication between PCE and PCC;

LSP: label Switched Path;

SDN: software Defined Network, Software Defined Network.

The technical solutions in the present application will be described clearly and completely with reference to the accompanying drawings in the detailed description of the present application, and it is obvious that the described embodiments are only a part of examples of the present application, and not all examples. All other examples, which can be obtained by a person skilled in the art without making creative efforts based on the embodiments in the present application, belong to the protection scope of the present application.

As can be seen from the background art, in the prior art, when a certain link in a service working path fails, in order to ensure that a service can be quickly recovered from a network failure, an additional network resource needs to be used by an adopted protection mechanism, so that although the service success rate can be improved, the additional network resource is occupied, and other normal paths in the working path where the failed link is located cannot be used by other services due to monopolization, especially under the condition of heavy network load, the service success rate and the network resource utilization rate cannot be taken into consideration in the prior art.

Therefore, the present application discloses a technical solution for resource sharing, where the resource is a generic name of an entity capable of being used for transmitting service data in a network. Comprises the following steps: link resources, node resources and the like, wherein the link resources are one kind of resources, and refer to that customer data is moved from one position to another position by using an actual physical carrier (such as an optical fiber); node resources, refer to the resources that can perform the necessary processing on the traffic, such as: converting the signal type of the customer from an electrical signal to an optical signal; or switching traffic data from one ingress to another egress, etc. The specific node function depends on the specific functional requirements. In the resource sharing technical scheme disclosed by the application, after a certain service adopts a protection path to transmit data due to the fault of a working path, link resources which do not actually have faults on the working path belonging to the service are temporarily released to other services in a network for use, so that the utilization rate of network resources is improved on the basis of ensuring the success rate of the service.

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

Example one

Fig. 1 is a schematic diagram of a disclosed network topology and information related to a service one (LSP1) according to an embodiment 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 nodes is 1, so the service one can be abbreviated as LSP1(A, B, 1)

The protection type of the service path is 1:1 protection, wherein the working path is as follows: A-E-F-B (LSP1_ W), 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 first service fail, protection switching needs to be performed, that is, the first service is switched from LSP1_ W to LSP1_ P. Also, it is assumed that other non-failed links in working path LSP1_ W may be used as shared resources for other traffic 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 other non-faulty links a-E in the working path LSP1_ W of LSP1(a, B, 1), link E-F is shared, that is, the resource sharing method disclosed in the present application is used to specifically perform sharing on link a-E and link E-F, and the specific sharing process is shown in the following example;

example 1

In the first example, a specific flowchart for performing sharing on links a-E and links E-F is shown in fig. 2:

s100: after receiving the working path fault message, the service source node A executes resource state updating judgment, wherein the resource updating judgment is to judge whether the link resource between the current node and the downstream adjacent node has no fault;

s101: if the link A-E between the service source node A and the intermediate node E (the downstream adjacent node of the service source node A) has no fault, the service source node A updates the link resource state of the corresponding link A-E in the working path to be shareable;

s102: a service source node A sends a first resource state updating request message to an intermediate node E;

in step S102 in this embodiment, the first resource status update request message includes link resource status information of the link a-E, and since the link resource of the link a-E is sharable, the link resource status information of the link a-E indicates that the link a-E is sharable;

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

s103: the intermediate node E receives the first resource state updating request message, executes the link E-F between the intermediate node E and the intermediate node F (the downstream adjacent node of the intermediate node E), and judges whether the link resource has a fault resource state updating;

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: if the link resource state of the link E-F between the intermediate node E and the intermediate node F is failure-free, the intermediate node E updates the link resource state of the corresponding link E-F in the working path to shareable;

s105: the intermediate node E sends a second resource state updating request message to the intermediate node F;

in step S105 of this embodiment, the second resource status update request message includes link resource status information of the link E-F, and since 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 is sharable;

s106: the intermediate node F receives the second resource state updating request message, and executes the resource state updating judgment of whether the link resource has no fault or not by the link F-B between the intermediate node F and the service destination node B (the downstream adjacent node of the intermediate node F);

s107: if the link state of the link F-B between the intermediate node F and the service destination node B is a fault, the intermediate node F sends a third resource state updating 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 F-B, and if the link F-B fails, the link resource status information of the link F-B indicates that the link F-B fails;

s108: the service destination node B receives the third resource state updating request message, and judges whether the link resource state information of the link F-B contained in the third resource state updating request message indicates that the link F-B can be shared or not;

in step S108 of this embodiment, although the third resource status update request message received by the service destination node B may include request information for requesting the downstream neighboring node to perform resource status update judgment, because the service destination node B is the last node on the working path, the service destination node B does not need to perform judgment on whether the link resource between itself and the downstream neighboring node is sharable, but only needs to perform judgment on whether flooding is performed;

s109: the link resource state information of the link F-B indicates that the link F-B is faulty, the service destination node B does not flood, and the service destination node B sends a first feedback message to an intermediate node F (an upstream neighbor node of the service destination node B);

in step S111 of this embodiment, the link resource status information of link F-B indicates that link F-B has a failure, because of the assumption based on this embodiment. Therefore, after the determination in step S108, it is determined that the link F-B is faulty and cannot be shared, and flooding is not necessary. Wherein the first feedback message includes: instructing an upstream neighboring node to flood sharable link resource configuration indicating information related to itself;

s110: after receiving the first feedback message, the intermediate node F floods the sharable link E-F acquired from the received second resource state updating request message;

since 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 floods the known sharable link E-F related to the intermediate node F, so as to implement sharing of 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 neighbor node of the intermediate node F), where the first feedback message includes: indicating information indicating that an upstream neighboring node floods a sharable link related to itself;

s112: after receiving the first feedback message, the intermediate node E floods the sharable link A-E obtained in the received first resource state updating request message and the sharable link E-F obtained by self judgment;

in step S116 of the present embodiment, the sharable link E-F is determined by the intermediate node E after performing step S103 and step S104; after receiving the first feedback message, the intermediate node E floods the known sharable link E-F and the link A-E related to the intermediate node E, so as to realize the sharing of the link E-F and the link A-E in the routing domain;

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

s113: the intermediate node E sends a first feedback message to the service source node a (an upstream neighbor node of the intermediate node E), where the first feedback message includes: indicating information indicating that an upstream neighboring node floods a sharable link related to itself;

s114: after receiving the first feedback message, the service source node a floods the sharable link a-E which is judged by the service source node a.

In step S114 of this embodiment, the sharable links a-E are determined after the service source node a performs step S101. As above, after receiving the first feedback message, the service source node a floods the known sharable links a-E related to the service source node a, so as to implement sharing of the links a-E in the routing domain.

In the embodiment, after it is assumed that the link F-B in the working path LSP1_ W of the LSP1 has a failure, the resource sharing method disclosed in the present application is adopted to update the other non-failed links a-E and E-F on the working path to be shared, and each node floods the non-failed links related to itself in the whole network, so as to notify other nodes in the network that the updated sharable links can be used.

That is, after a certain service uses a protection path to transmit data due to a failure of a link in a working path, link resources which actually belong to the service and have no failure on the working path are temporarily released for use by other services in the network, so that the utilization rate of network resources is improved on the basis of ensuring that the success rate of the service is improved.

Example two

In this second example, the flow of performing sharing on links a-E and E-F differs from that in first example in that:

after confirming that the links related to each node are sharable, each node directly floods the sharable links between each node and the downstream adjacent nodes, without the need that after each node in the whole working path executes resource updating judgment, and after receiving feedback information sent by the downstream adjacent nodes, the upstream adjacent nodes execute flooding based on the feedback information;

that is, based on the above-mentioned first example, in the second example, after the service source node a executes step S101, the service source node a floods the link a-E whose link resource status is updated to be sharable;

in the second example, after the intermediate node E executes step S104, the intermediate node E floods the sharable links a-E obtained in the received first resource status update request message and the sharable links E-F determined by the intermediate node E;

in the second example, after the intermediate node F performs step S107, and confirms that the link resource of the link F-B between the intermediate node F and the service destination node B is faulty, the intermediate node F floods the sharable link E-F obtained in the received second resource status update request message;

in the second example, further, after each node confirms that there is no problem with a certain link associated with itself, flooding may 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 a-E link resource status information indicating that the link a-E can share, the sharable link a-E is flooded.

And when or after the intermediate node E executes the flooding, judging whether the link resources of the link E-F between the intermediate node E and the intermediate node F are failure-free, and after the link resources of the link E-F are failure-free, flooding the link E-F updated to be sharable.

That is, in the second example, the intermediate node located on the working path may perform the first flooding after obtaining the sharable link resources of the upstream neighboring node and the intermediate node, determining that the link resources of the intermediate node and the downstream neighboring node are sharable, and then performing the first flooding; after receiving the link resource state information indicating that the link is sharable and sent by the upstream adjacent node, the method may perform flooding once first, and perform flooding once again after determining that the link resource of the upstream adjacent node and the link resource of the downstream adjacent node are sharable.

Through the above-mentioned time for each node to perform flooding, each node can also obtain or confirm that the link related to itself and without failure performs flooding in the whole network, thereby realizing that the link updated to the sharable state in the network can be used by other nodes.

The above embodiments are only examples given in the present application, and do not limit the failed link to be the last segment, which is suitable for 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 operations are:

after receiving the working path fault message, the service source node executes resource state updating judgment, and the resource updating judgment is to judge whether the link resource between the service source node and the downstream adjacent node has no fault;

if the link resource between the service source node and the downstream adjacent node has no fault, updating the link resource state between the service source node and the downstream adjacent node to be sharable;

sending a resource state updating request message to a downstream adjacent node, wherein the resource state updating request message comprises link resource state information between a service source node and the downstream adjacent node;

in the embodiments disclosed in the present application, whether the link resource state is updated by the service source node further includes not updating the link resource state if it is determined that the link resource between the service source node and the downstream neighboring node is faulty, or updating the link resource state between the service source node and the downstream neighboring node to be not sharable;

in the above embodiments disclosed in the present application, the method further includes: after the link resource state between the service source node and the downstream adjacent node is updated to be sharable, the sharable link between the service source node and the downstream adjacent node is flooded;

in the above embodiments disclosed in the present application, for different flooding occasions, the service source node adopts the following manner:

firstly, a service source node receives a first feedback message sent by a downstream adjacent node, wherein the first feedback message comprises sharable link resource configuration indication information indicating that the upstream adjacent node floods and is related to the upstream adjacent node;

the service source node floods sharable links, and does not flood non-sharable links;

secondly, after the link resource state between the service source node and the downstream neighboring node is updated to be sharable, before the resource state update request message is sent to the downstream neighboring node, the service source node floods the sharable link between the service source node and the downstream neighboring node.

For the intermediate node in the working path, the specific operation is as follows:

after receiving a resource state updating request message sent by an upstream adjacent node, the intermediate node executes resource state updating judgment, and the resource updating judgment is to judge whether a link resource between the intermediate node and the downstream adjacent node has no fault;

if the link resource between the intermediate node and the downstream adjacent node has no fault, updating the link resource state between the intermediate node and the downstream adjacent node to be sharable;

sending a resource state updating request message to a downstream adjacent node, wherein the resource state updating request message comprises link resource state information between the intermediate node and the downstream adjacent node;

sending a first feedback message to an upstream neighbor node, wherein the first feedback message comprises: instructing the upstream neighboring node to flood sharable link resource configuration indication information associated with itself.

In the above embodiments disclosed in the present application, whether the link resource state is updated by the intermediate node further includes not updating the link resource state if it is determined that the link resource between the intermediate node and the downstream adjacent node is faulty, or updating the link resource state between the intermediate node and the downstream adjacent node to be not sharable;

in the above embodiments disclosed in the present application, the method further includes flooding, by the intermediate node, the link sharable between the upstream neighboring node and the intermediate node, and flooding the link sharable between the intermediate node and the downstream neighboring node.

In the above embodiments disclosed in the present application, for different flooding occasions, the intermediate node adopts the following manner:

firstly, after receiving a first feedback message sent by a downstream adjacent node, an intermediate node includes sharable link resource configuration indication information indicating that the upstream adjacent node floods and is related to the intermediate node;

the intermediate node floods sharable links between the upstream adjacent node and the intermediate node and floods sharable links between the intermediate node and the downstream adjacent node in the resource state updating request message sent by the upstream adjacent node;

non-sharable links between the upstream adjacent node and the intermediate node and/or between the intermediate node and the downstream adjacent node are not flooded;

and secondly, the intermediate node acquires link resource state information between the upstream adjacent node and the intermediate node, which is contained in the resource state updating request message sent by the upstream adjacent node, and floods the sharable link between the upstream adjacent node and the intermediate node after confirming that the sharable link can be shared.

After the link resource state between the intermediate node and the downstream adjacent node is updated to be sharable, the intermediate node floods the sharable link between the intermediate node and the downstream adjacent node;

in the second flooding manner, the intermediate node may perform first flooding or non-flooding based on whether the sharable result is obtained after determining the link resource state information between the upstream neighboring node and the intermediate node, and perform first flooding or non-flooding based on the sharable result after determining the link resource information between the intermediate node and the downstream neighboring node;

or, after obtaining the link resource state information of the upstream neighboring node and the intermediate node and judging the link resource state information of the intermediate node and the downstream neighboring node, performing a full flood, or a partial flood, or no flood based on the sharable result;

for a traffic destination node, it is specifically operative to:

a service destination node receives a resource state updating request message sent by an upstream adjacent node, wherein the resource state updating request message comprises link resource state information between the upstream adjacent node and the service destination node;

a service destination node acquires link resource state information between an upstream adjacent node and the service destination node in a resource state updating request message sent by the upstream adjacent node;

after confirming that the link resource state information between the upstream adjacent node and the service destination node is sharable, the service destination node floods the sharable link between the upstream adjacent node and the service destination node;

the service destination node sends a first feedback message to an upstream adjacent node, wherein the first feedback message comprises: instructing the upstream neighboring node to flood sharable link resource configuration indication information associated with itself.

The resource sharing method disclosed in the embodiment of the application further includes that the service destination node does not perform flooding when confirming that the link resource state 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 a service source node and an intermediate node send a resource status update request message to a downstream neighboring node, in order to indicate that the downstream neighboring node needs to execute the resource status update request message, in the process of executing the resource sharing method, an RSVP-TE protocol may be extended, and a TLV (Type-length-value) object is added to the RSVP-TE protocol, where the specific format is as follows:

among them, Type (16bits, TLV Type);

length (16bits, TLV Length);

flags (32bits, currently defining an identification of U-update (request for resource update judgment))

The TLV may be placed in the LSP _ REQUERED _ ATTRIBUTES object as an indication to request downstream neighboring nodes to make resource update decisions.

Similarly, in the resource sharing method disclosed in the embodiment of the present application, in the service source node and the intermediate node, the sharable state of the service source node and the downstream neighboring node is sent to the downstream neighboring node, or the intermediate node or the service destination node feeds back the sharable state of one or more links between the nodes to the upstream neighboring node, during the execution of the resource sharing method, the RSVP-TE protocol is extended, and a TLV (Type-length-value) object is added to the RSVP-TE protocol to indicate the sharable state of one or more links, where the specific format is as follows:

among them, Type (16bits, TLV Type);

length (16bits, TLV Length);

link ID X (Link identification, variable length): it may represent a 32bit link IP address or node ID + link ID, depending on the specific link type. As long as it can represent a unique network link.

Status Flag (Status Flag, variable productivity): in the resource sharing method disclosed in the embodiment of the present application, the following two types of information are defined:

s (1bit): whether it can be shared; s ═ 1 indicates shareable, and S ═ 0 indicates unshared;

a (1bit): whether it is already occupied by other traffic. A is 1: indicates that it is occupied; a is 0, which means that it is not occupied;

however, in the resource sharing method disclosed in the embodiment of the present application, the Status Flag is not limited to these 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 a service source node, an intermediate node, and a service destination node flood a sharable link based on an OSPF protocol, a new TLV needs to be added in the OSPF protocol to indicate sharable link resource state information, where the newly defined TLV format is as follows:

the Type (16bits, TLV Type) is used for transferring sharable link resource state information;

length (16bits, TLV Length);

value (32bits), can be used to add constraints during flooding: such as Priority (3bits), to indicate the highest Priority at which the sharable link resource may be used.

In combination with the above-described specific embodiments, according to the resource sharing technical scheme disclosed in the present application, after a certain service fails in a working path and data is transmitted by using a protection path, each node on the working path processes link resources between the node and an upstream neighboring node and between the node and a downstream neighboring node, and updates the link resources that actually belong to the service and are not failed to be shareable on the working path, and then performs flooding, so that shareable links can be temporarily released to be used by other services in a network, thereby improving the utilization rate of network resources on the basis of ensuring that the success rate of the service is improved.

Example two

Based on the resource sharing method disclosed in the embodiment of the present application, in this embodiment, for each node, a condition whether a link related to the node is sharable or a link resource configuration may be preset, that is, a preset condition that the link related to the node is sharable or not sharable is preset for each node;

in this embodiment, before the service source node and the intermediate node update the state of the link resource between each node and the downstream neighboring node to be sharable, the method further includes: the service source node and the intermediate node determine that the link resource configuration can be shared when preset link resource configuration information exists, and/or the service source node and the intermediate node receive link resource configuration indication information from a downstream adjacent node, wherein the link resource configuration indication information indicates that the link resource configuration can be shared;

before flooding a sharable link between an upstream adjacent node and a service destination node, the service destination node also comprises a step of determining that the link resource configuration information can be shared by the service destination node according to preset link resource configuration information;

for example, each node sets link resource configuration information for link resources between the respective node and a neighboring node, the link resource configuration information including link resource sharable and link resource non-sharable.

The service source node sets resource configuration information for link resources between the respective node and a downstream neighboring node. The intermediate node sets resource configuration information respectively aiming at the link resources between the intermediate node and the upstream adjacent node and between the intermediate node and the downstream adjacent node. The service destination node sets resource configuration information for link resources between the service destination node and an upstream neighboring node. If any one of the two adjacent nodes sets that the link resource is not shareable, the link resource between the two nodes is not shareable. Or, if the resource configuration information set on two adjacent nodes is inconsistent, the link resource between the two nodes is not sharable.

Preferably, in the method for resource sharing disclosed in the above application embodiment, after the service source node receives the working path failure message, before performing the resource state updating judgment, it needs to first judge whether the preset condition of the service source node includes sharable configuration, and when the preset condition of the service source node includes sharable configuration, then further judge whether there is no failure; when the preset condition of the service source node comprises the non-shareable configuration, directly executing the step of sending a resource state updating request message to the downstream adjacent node;

or after judging that no fault exists, judging whether the preset condition of the service source node contains shareable configuration;

if the preset condition of the service source node comprises shareable configuration, continuing the subsequent steps; and when the preset condition of the service source node comprises the non-sharable configuration, directly executing the step of sending the resource state updating request message to the downstream adjacent node.

Similarly, before receiving the resource status update status message sent by the upstream neighboring node, the intermediate node and the service destination node also need to make the same judgment to judge whether the preset conditions of the intermediate node and the service destination node contain sharable configuration or non-sharable configuration.

Or, after the service source node and the intermediate node update the link resource state between itself and the downstream neighboring node to be sharable, further:

the service source node and the intermediate node send confirmation information to the downstream adjacent node to confirm whether the link resource state between the nodes can be updated to be shareable, and if the error information fed back by the downstream adjacent node is received, the service source node and the intermediate node mark the link resource state between the nodes again, namely mark the link resource state as not shareable;

after receiving the confirmation information, the downstream adjacent node judges whether the resource allocation between the downstream adjacent node and the upstream adjacent node is equal or not, or whether the carried service attributes are consistent or not, if the resource allocation is equal or the service attributes are consistent, correct information is fed back, and if the resource allocation is not equal or the service attributes are not consistent, incorrect information is fed back;

that is, whether link resources between nodes can be marked as shareable or not requires confirmation via an upstream neighbor node and a downstream neighbor node;

specifically, taking an operation between the service source node a and the intermediate node E (which is a downstream adjacent node of the service source node a) as an example, a specific description is made, as shown in fig. 3:

s200: after receiving the working path fault message, the service source node A executes resource state updating judgment, wherein the resource updating judgment is to judge whether a link A-E between the service source node A and a downstream adjacent node has no fault or not, if the link resource of the link A-E between the service source node A and the intermediate node E has no fault, S201 is executed, and if the link resource of the link A-E between the service source node A and the intermediate node E has fault, S202 is directly executed;

s201: the service source node A updates the corresponding A-E link resource state in the working path to be sharable;

s202: the service source node A sends sharable A-E link resource state information to the intermediate node E;

s203: the intermediate node E receives the sharable A-E link resource state information, and judges whether the resource configuration between the intermediate node E and the service source node A is equal or not, or judges whether the service attributes carried by the intermediate node E and the service source node A are consistent or not, if so, the correct information is fed back to the service source node A, and S205 is executed; if not, feeding back error information to the service source node A, and executing S204;

s204: the service source node A updates the corresponding A-E link resource state 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 first example, whether to update the link resource state information between nodes in the resource sharing method disclosed in the present application is performed, and the resource configuration between the executing node and the downstream neighboring node is considered, so that the link resource state between nodes can be marked or updated more accurately, and further, the marked or updated link resource state between nodes is more stable when the link resource state is sharable.

Based on the resource sharing method disclosed in the first embodiment of the present application, in this embodiment, for each node, flooding may be performed based on a conventional manner, and the same or different flooding conditions may also be set for each node, so that each node performs flooding based on the flooding conditions;

preferably, in the resource sharing method disclosed in the second implementation of the present application, when the service source node, the intermediate node, and the service destination node obtain the link resource state information between any sharable nodes in the flooding, the method may adopt a plurality of modes including

First, link resource state information between sharable nodes may be flooded to other nodes within the entire network;

second, a flooding condition may be set, which limits the targeted release of link resource state information between sharable nodes during full-network flooding, and the specific flooding condition may be:

firstly, flooding link resource state information between any sharable nodes acquired by other nodes in the same routing domain with the working path (namely a service source node, an intermediate node and a service destination node) of the service;

secondly, flooding the obtained link resource state information between any sharable nodes to the nodes in the working paths of other services with the priority lower than the service;

thirdly, combining the two limiting modes to carry out two-stage limitation, namely limiting the flooding range to be other nodes which are positioned in the same routing domain with the working path of the service, limiting the link resource state information which can be shared among the nodes to be nodes in the working path of other services with the priority lower than that of the service in the range, and then carrying out flooding; it should be noted that, the above-mentioned limitation of the flooding range or after flooding to a specific node, can be performed in any order during the flooding process;

based on the resource sharing method disclosed in the embodiment of the present application, it should be noted that the restriction condition added in the flooding process may be specifically added to the Value of the TLV newly added in the OSPF protocol, such as Priority (3bits), for indicating the highest Priority that the sharable link resource can be used.

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

Based on the resource sharing method disclosed in the first embodiment of the present application, in this embodiment, each node uses a signaling mode to send a link resource state related to each node to a downstream neighboring node, and then a service destination node feeds back the link resource state between each node in the whole working path to a service source node in a signaling mode, so that the service source node learns the link resource state between each node in the whole 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 in a signaling manner, where the second feedback message includes link resource state information of the working path; the link resource state information refers to link resource state information among nodes forming the working path;

by receiving the link resource state information by the service source node, it can be known that the links on the working path are shareable, and in the subsequent working path restoration process, it can be referred to whether the shareable links are occupied by other services, so as to complete the operation of the corresponding working path restoration.

EXAMPLE III

In the resource sharing method disclosed in the embodiment of the present application, besides the step-by-step judgment of whether a link between nodes is free from a fault is performed by each node, a decision of whether to share resources between each node (network element) can be made by using a network controller. For example, by using the second service LSP2, in this embodiment, when one or more links in the working path LSP2_ W of the second service fail, protection switching needs to be performed, that is, the second service is switched from LSP2_ W to LSP2_ P. Also, assuming that no other failed links in the working path LSP2_ W are available, the decision of the network controller can be used as a shared resource for other traffic in the network, as shown in fig. 4:

the centralized controller K is used for carrying out required processing on the nodes in all the working paths in the whole network in a centralized manner;

the service source node of the LSP2 is a1, the service destination node is B1, and the link bandwidth between nodes is 1, so the LSP2 can be abbreviated as LSP2(a1, B1, 1)

The protection type of the service path is 1:1 protection, wherein the working path is as follows: A1-E1-B1, the protection path is: A1-G1-H1-J1-B1; in this example, assume that the link E1-B1 between node E1 and node B1 fails. For the process of sharing other non-failed links a1-E1 in the working path of the LSP2(a1, B1, 1) with the link failure, the resource sharing method disclosed in this embodiment of the present application is specifically implemented as follows, and a specific flowchart is shown in fig. 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, calculates sharable link resources and non-sharable link resources in the working path based on the working path fault message and the service policy of the centralized controller, generates a resource sharable message, and feeds back the resource sharable message to the service source node a 1; wherein the resource sharable 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 that the sharable link resource may be specifically shared by which type or level of service;

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 contained in the resource sharable message, and judges whether the link resource state information of the links A1-E1 is sharable or not, if the link resource state information of the links A1-E1 is sharable, S304 is executed, and if the link resource state information of the links A1-E1 is not sharable, S305 is directly executed;

s304: the traffic source node a1 floods the sharable link a 1-E1;

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

s306: the intermediate node E1 receives the resource sharable message sent by the service source node a1, reads the link resource state information of the links a1-E1 and the links E1-B1 contained in the resource shared message, and determines whether sharable link resource state information exists in the links a1-E1 and the links E1-B1, if the link resource state information of the links a1-E1 is sharable, S307 is executed;

s307: intermediate node E1 floods shareable link A1-E1;

in this embodiment, only the link resource state information of the links a1 to E1 among the link resource state information of the links a1 to E1 and the links E1 to B1 can be shared, and in S307, the intermediate node E1 floods the sharable links a1 to E1;

s308: the intermediate node E1 deletes information related to the intermediate node E1 from the resource sharable message sent by the service source node a1, and sends the deleted resource sharable message to the service destination node B1;

s309: the service destination node B1 receives the resource sharable message sent by the intermediate node E1, reads the link resource state information of the links E1-B1 contained in the resource sharable message, and determines whether the link resource state information of the links E1-B1 is sharable, and does not perform flooding because the link resource state information of the links E1-B1 is not sharable.

For the assumption that links E1-B1 in working path LSP2_ W of LSP2 have a fault in the embodiment of the present application, therefore, the centralized controller K performs calculation according to the fault message to obtain whether the links between adjacent nodes in the working path are sharable or faulty, removes the faulty link information, integrates sharable link resource status information, and generates a corresponding resource sharable message to be fed back to the service source node; starting from a service source node, carrying out flooding judgment according to link resource state information between adjacent nodes contained in a resource sharable message; after the sharable flooding condition is met, corresponding flooding is executed, and the link resources which actually belong to the service and do not have faults are temporarily released to other services in the network for use, so that the utilization rate of the network resources is improved on the basis of ensuring the improvement of the success rate of the service.

The above embodiment is only an example, and does not limit the failed link to be the last segment, which is suitable for the case that 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, for a service source node in a working path, the specific operations are as follows:

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 resource sharable messages fed back by the controller, wherein the resource sharable messages comprise link resource state information between adjacent nodes in the working path;

the service source node judges whether the link resource state information between the service source node and the downstream adjacent node is sharable or not according to the link resource state information between the service source node and the downstream adjacent node contained in the resource sharable message;

if the link resource state information between the service source node and the downstream adjacent node is sharable, the service source node floods the sharable link;

and the service source node sends the resource sharing message to the downstream adjacent node.

Specifically, before sending the resource sharable message, the service source node may further delete information related to the service source node in the resource sharable message, and send the deleted resource sharable message to a downstream neighboring node.

In addition, if the link resource state information between the service source node and the downstream neighbor node is not sharable, the flooding is not performed and the resource sharable message is transmitted to the downstream neighbor node.

the intermediate node receives the resource sharable message sent by the upstream adjacent node, reads the link resource state information between the intermediate node and the upstream adjacent node and between the intermediate node and the downstream adjacent node contained in the resource sharable message sent by the upstream adjacent node, and judges whether sharable link resource state information exists in the link resource state information between the intermediate node and the upstream adjacent node and between the intermediate node and the downstream adjacent node;

if sharable link resource state information exists, the intermediate node floods the sharable link;

the intermediate node sends a resource sharable message to the downstream neighbor node.

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

in addition, if sharable link resource state information does not exist, flooding is not performed, and the resource sharable message transmitted by the upstream neighbor node is transmitted to a downstream neighbor node.

For a traffic destination node, it is specifically operative to:

a service destination node receives a resource sharable message sent by an upstream adjacent node, reads link resource state information between the service destination node and the upstream adjacent node contained in the resource sharable message sent by the upstream adjacent node, and judges whether the link resource state information between the service destination node and the upstream adjacent node is sharable or not;

if the link resource state information between the service destination node and the upstream adjacent node is shareable, the service destination node floods the shareable link;

the traffic destination node does not perform flooding if the link resource state information between the traffic destination node and the upstream neighbor node is not shareable.

In the resource sharing method based on the centralized controller disclosed in the embodiment of the application, the centralized controller and the nodes can also use a PCEP protocol, and in the using process, the PCEP protocol is extended, that is, a bit is extended in the PCEP protocol to indicate that the PCC requests the PCE to make a judgment request whether resources can be shared;

extending a bit in the PCEP protocol may be, but is not limited to, the following; the method specifically comprises the following steps:

adding a bit in the existing LSP object, wherein the bit is carried by a PCRpt message or a PCReq message and is used for representing a request;

u (1bit) indicates whether shareable calculations need to be made;

similarly, in the resource sharing method based on the centralized controller disclosed in the embodiment of the present application, in the process of generating the resource sharable message by the centralized controller, a restriction condition may be added, where the restriction condition may be carried by TLV as follows, and different restriction conditions may also be distinguished by Type;

for example, the limitation may be: the Priority of the sharable link resource can be used, namely, information of Priority Number is added in the Value part; the following steps can be also included: the Number of sharable link resources that can use that LSP, e.g., LSP Number;

it should be noted that, when the PCEP protocol and the RSVP-TE protocol need to carry the feature information capable of using the sharable link resource state, the TLV defined above may also be used to carry the feature information.

Example four

Based on the resource sharing method disclosed in the first to third embodiments of the present application, in this embodiment, after performing flood sharing on link resources between nodes that do not have a fault according to, for example, full-network flooding or a set flooding condition, a process of establishing a working path is performed for a node that receives a flooded sharable link when receiving a service request;

in the fourth embodiment of the present application, on the basis of the network topology disclosed in fig. 1 and the schematic diagram of the relevant information of LSP1, an LSP3 is added for explanation, as shown in fig. 6: the LSP3(C, D, BW 1), and the links a to E and E to F in the LSP1(a, B, BW 1) are shared;

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

s401, a service source node C searches and acquires an available link C-K and an available link L-D between the service source node C and a service destination node D in a 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 an available link E-F based on the received flooded sharable link A-E and the link E-F;

s403, the service source node C utilizes the link C-K, the link L-D and the link E-F to recalculate the available path, 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 starting node E corresponding to the link E-F;

s405, after receiving the allowance of establishing the intersection fed back by the starting node E, the service source node C establishes a corresponding working path C-K-E-F-L-D based on the available path by using RSVP-TE information;

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

In the method for sharing resources disclosed in the embodiment of the present application, for a node of a service request received in a network, in a process of calculating a service path, whether there is an available resource that is not occupied by other services in the network is considered first, and if a corresponding available path is not obtained, link resources that are temporarily shared in other services are considered. And after the available path is obtained by calculation, sending a resource allocation request to an initial node of sharable link resources contained in the available path, and after the initial node feeds back permission to establish crossing, establishing a corresponding service path based on the available path obtained by calculation by using RSVP-TE information, and sending a notification message to a service source node of the service path where the sharable link resources are located to inform that the sharable link resources are occupied.

In calculating an available path based on sharable link resources, in the resource sharing method disclosed in the embodiment of the present application, it is preferable to limit the sharable link resources to be used, and use the sharable link resources with the least use as a limiting condition for calculating the available path.

Based on the foregoing multiple different flooding methods disclosed in the embodiments of the present application, in this embodiment, it is preferable that, in the resource sharing method disclosed in this embodiment of the present application, after a service failure is recovered, a service for performing service data transmission on a protection path needs to be backed from the protection path to a working path.

In the rollback process, part of links on the working path of the service may have been shared, so to ensure that the service can be successfully rolled back to the working path or improve the success rate of rolling back, based on different flooding manners in the resource sharing method, the following method is adopted for rolling back:

based on any flooding mode, after the service failure is recovered, only one available resource in the returned working path is ensured, and the original resource, namely the original working path, does not need to be strictly returned or used.

For the resource sharing method disclosed in the embodiment of the present application, in which each node determines whether sharable resources are available, or the centralized controller determines whether sharable resources are available, after determining sharable link resources, when an original service needs to fall back to a working path, the following method may be used:

aiming at the situation that each node respectively judges whether the nodes can share, after the service source node receives the working path fault recovery message:

inquiring whether link resources which are not used by other services exist in sharable link resources, and if all the link resources are not used by other services, directly returning to the original working path from the protection path;

if part of the link resources are not used by other services, on the basis of meeting the service policy, the protection path is returned to sharable link resources which are not used by other services, and a new working path is formed by the part of the protection path and the part of the original working path;

or, when inquiring that part or all of the sharable link resources are occupied by the low-priority service, disconnecting the sharable link resources of the original service crossed in the working path of the low-priority service, and directly returning from the protection path to the original working path.

Aiming at the situation that the centralized controller performs centralized judgment on whether the shared network is available, after the service source node receives the working path fault recovery information:

the service source node sends the working path fault recovery message to the centralized controller;

the integrated controller evaluates the complexity of restoring to the original working path based on the working path fault restoration message;

if the complexity is lower than the preset complexity, controlling the service to be backed from the protection path to part of sharable link resources which are not used by other services according to the state that the sharable link resources in the original working path are partially occupied;

or, according to the state that the sharable link resource in the original working path is partially or completely occupied by the service with low priority, the service is controlled to be forcibly returned to the original working path;

if the complexity is higher than the preset complexity, recalculating a working path and feeding back the service source node;

the preset complexity difficulty coefficient is generally based on power consumption consumed for establishing a new working path.

By the resource sharing method disclosed in the embodiment of the present application, after the sharable link resource is flooded, if the failure of the working path of the original service is resolved, the above manner is adopted to rollback to part or all of the original working paths, or a new working path is reestablished, so that the success rate of rollback is further improved, and the utilization of the network resource is also effectively improved.

EXAMPLE five

Based on the resource sharing method disclosed in the embodiment of the present application, the embodiment of the present application also correspondingly discloses a network node structure capable of correspondingly realizing resource sharing among the service source node, the intermediate node and the service destination node, and a network resource sharing system having a working path of a service correspondingly formed by the network nodes having the functions of the service source node, the intermediate node and the service destination node;

when the network resource sharing system does not contain the centralized controller or each network node does not depend on the centralized controller; the detailed description is respectively carried out on network nodes with the resource sharing function of corresponding service source nodes, intermediate nodes and service destination nodes;

different network nodes and modules with the same or similar functions in different network nodes are marked and distinguished by adopting a first function, a second function and the like;

as shown in fig. 7, in order to illustrate a structure of a first network node that can implement resource sharing by a service source node, the first network node 100 includes: a first judging module 101, a first updating module 102 and a first sending module 103, which are used for executing the resource sharing method executed by the service source node disclosed in the present application. For example, the first determining module 101 is configured to, after receiving a working path failure message, execute a resource status update determination that whether a link resource between the network node and a downstream neighboring node of the network node is failure-free is determined by the resource update determination; the first updating module 102 is configured to update a state of a link resource between the network node and the downstream neighboring node to be sharable when the link resource between the network node and the downstream neighboring node is not faulty; a first sending module 103, 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 network node 100 disclosed in the embodiment of the present invention, the method further includes: and the first management module is used for receiving resource allocation requests sent by nodes corresponding to other services and feeding back allowable cross information to the nodes corresponding to the other services according to the resource allocation strategy.

In the service source node 100 disclosed in the embodiment of the present invention, the method further includes: the first flooding module, the first determining module and/or the first receiving module, the rollback module, and the like, implement the modules of the corresponding functions in the resource sharing process of the service source node.

As shown in fig. 8, in order to schematically illustrate a structure of a second network node that can implement resource sharing by an intermediate node, the second network node 200 includes: a second judging module 201, a second updating module 202 and a second sending module 203 for executing the resource sharing method executed by the intermediate node disclosed in the present application. For example, the second determining module 201 is configured to, after receiving a resource status update request message sent by an upstream neighboring node, execute a resource status update determination, where the resource update determination is to determine whether there is no fault in a link resource between the network node and a downstream neighboring node; the second updating module 202 is configured to update a state of a link resource between the network node and the downstream neighboring node to be sharable when the link resource between the network node and the downstream neighboring node is not faulty; a second sending module 203, configured to send the 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, and send a first feedback message to the upstream neighboring node, where the first feedback message includes indication information indicating that the upstream neighboring node floods sharable link resource configuration information related to itself.

In the intermediate node 200 disclosed in the embodiment of the present invention, the method further includes: and the second management module is used for receiving resource allocation requests sent by nodes corresponding to other services and feeding back allowable cross information to the nodes corresponding to the other services according to the resource allocation strategy.

In the second network node 200 disclosed in the embodiment of the present invention, the method further includes: a second flooding module 204, a second determining module and/or a second receiving module, and so on, which are modules for implementing corresponding functions in the resource sharing process performed by the intermediate node.

As shown in fig. 9, in order to schematically illustrate a structure of a third network node that can implement resource sharing by a service destination node, the network node 300 includes: a third determining module 301, a third flooding module 302 and a third sending module 303, which are used for executing the resource sharing method executed by the service destination node disclosed in the present application. For example, the third determining module 301 is configured to receive, by a network node, a resource status update request message sent by an upstream neighboring node, and acquire link resource status information between the upstream neighboring node and the network node, where the link resource status information is included in the resource status update message; the third flooding module 302 is configured to flood a sharable link between the upstream neighboring node and the network node after confirming that the link resource state information between the upstream neighboring node and the network node is sharable; a third sending module 303, configured to send a first feedback message to the upstream neighboring node, where the first feedback message includes: instructing the upstream neighboring node to flood sharable link resource configuration indication information associated with itself.

In the third network node 300 disclosed in the embodiment of the present invention, the method further includes: a third determining module and the like, which realize the modules of the corresponding functions in the resource sharing process of the intermediate node.

The above modules in the first network node 100, the second network node 200, and the third network node 300 perform resource sharing, and a specific process or principle related to resource sharing, which correspond to the contents disclosed in the foregoing embodiments of the present application and related to the first network node, the second network node, and the third network node, may be referred to each other, and therefore, details are not repeated here.

The resource sharing method described in connection with the embodiments disclosed herein may be implemented directly in hardware, in a processor-implemented memory, or in a combination of the two, in the first network node, the second network node, and the third network node. Therefore, the present application also discloses a first network node, a second network node and a third network node respectively corresponding to the resource sharing methods disclosed in the embodiments of the present application, and the structures of the first network node, the second network node and the third network node are the same, as shown in fig. 10, each of the first network node, the second network node and the third network node includes a memory 10 and a processor 12 connected to the memory 10 through a bus 11.

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

The resource sharing operation flow, namely the program corresponding to the above-disclosed resource sharing method for each network node, may include a program code, where 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 comprise high speed RAM memory and may also include non-volatile memory, such as at least one disk memory.

The processor is connected with the memory through the bus, and when each network node executes resource sharing, the processor calls the 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 network resource sharing system 1 is also disclosed, in which the first network node 100, the second network node 200, and the third network node 300 form a working path of a service. Wherein the dashed lines in fig. 11 indicate the first network node, the second network node and the second network node, etc. in the working paths of other traffic.

Based on the resource sharing method disclosed above in the present application, in which an integrated controller is used to determine whether links between a service source node, an intermediate node, and a service destination node can be shared, the present application also correspondingly discloses another network resource sharing system, as shown in fig. 12, where 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 may be executed by using corresponding modules based on the above corresponding methods, which is not described herein again. The dotted lines in fig. 12 indicate a service source node, an intermediate node, a service destination node, and the like in the working path of other services.

It should be noted that, for other operations related to each component of the service source node, the intermediate node, and the service destination node that execute the resource sharing method disclosed in the embodiment of the present application, such as a flooding operation for setting a flooding condition, reference may be made to corresponding parts in the resource disclosing method disclosed in the embodiment of the present application, and details are not described here again.

In summary, the present application discloses a resource sharing technical solution, after a certain service uses a protection path to transmit data due to a failure of a working path, a link resource that does not actually fail on the working path belonging to the service is temporarily released to other services in a network for use, so as to ensure that the success rate of the service is improved, and at the same time, improve the utilization rate of the network resource.

Furthermore, the problems involved in rollback are considered in the flooding process, so that the success rate of rollback is improved, and the utilization rate of inward resources is also improved.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for resource sharing, comprising:

after receiving a working path fault message, a service source node executes resource state updating judgment, wherein the resource state updating judgment is to judge whether a link resource between the service source node and a downstream adjacent node has no fault;

2. The method of claim 1, wherein after updating the link resource status between the traffic source node and the downstream neighboring node to shareable, the method further comprises:

and judging whether the link resources between the service source node and the downstream adjacent node are occupied or not.

3. The method of claim 2, wherein the link resource status between the traffic source node and the downstream neighboring node is updated to available if the link resource between the traffic source node and the downstream neighboring node is not occupied.

4. The method according to any one of claims 1 to 3, wherein the resource status update request message further carries request information for requesting a downstream neighboring node to perform the resource status update judgment.

5. The method according to any of claims 1 to 4, further comprising, after updating the link resource status between the traffic source node and the downstream neighboring node to shareable, the following steps:

flooding a sharable link between the traffic source node and the downstream neighboring node.

6. The method according to any of claims 1-5, wherein before updating the link resource status between the traffic source node and the downstream neighbor node to shareable, the method further comprises:

7. A network node, comprising:

the first judgment module is used for executing resource state updating judgment after a network node receives a working path fault message, wherein the resource updating judgment is to judge whether link resources between the network node and a downstream adjacent node of the network node are faultless or not;

a first updating module, configured to update a state of a link resource between the network node and the downstream neighboring node to be sharable when the link resource between the network node and the downstream neighboring node is not faulty;

8. The network node of claim 7, wherein after the link resource status between the network node and the downstream neighboring node is updated to be sharable, the first determining module is further configured to:

and judging whether the link resources between the network node and the downstream adjacent node are occupied or not.

9. The network node according to claim 7 or 8, wherein if the link resources between the network node and the downstream neighboring node are not occupied, the first updating module is further configured to:

updating a link resource status between the network node and the downstream neighboring node as available.

10. The network node according to any of claims 7 to 9, further comprising:

11. The network node according to any of claims 7 to 10, further comprising:

and/or the presence of a gas in the gas,

12. A method for resource sharing, comprising:

13. The method of claim 12, wherein after updating the link resource status between the intermediate node and the downstream neighboring node to shareable, the method further comprises:

and judging whether the link resources between the intermediate node and the downstream adjacent node are occupied or not.

14. The method of claim 13, wherein the link resource status between the intermediate node and the downstream neighboring node is updated as available if the link resource between the intermediate node and the downstream neighboring node is not occupied.

15. The method according to any one of claims 12 to 14, wherein the resource status update request message further carries request information for requesting a downstream neighboring node to perform the resource status update judgment.

16. The method of any one of claims 12 to 15, further comprising:

17. The method according to any of claims 12-16, wherein before updating the link resource status between the intermediate node and the downstream neighboring node as shareable, the method further comprises:

the intermediate node has preset link resource configuration information, and determines that the link resource configuration information is sharable, and/or the intermediate node receives link resource configuration indication information from the downstream adjacent node, wherein the link resource configuration indication information indicates sharable.

18. A network node, comprising:

a second updating module, configured to update a state of a link resource between the network node and the downstream neighboring node to be sharable when the link resource between the network node and the downstream neighboring node is not faulty;

19. The network node of claim 18, wherein the link resource status between the network node and the downstream neighboring node is updated to be sharable, and wherein the second determining module is further configured to:

20. The method according to claim 18 or 19, wherein if the link resources between the network node and the downstream neighboring node are not occupied, the second update module is further configured to:

21. The network node according to any of claims 18 to 20, further comprising:

22. The network node according to any of claims 18 to 21, further comprising:

and/or the presence of a gas in the gas,

a second 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, where the link resource configuration indication information indicates sharability.

23. A method for resource sharing, comprising:

24. The method of claim 23, wherein after confirming that the link resource status information between the upstream neighboring node and the traffic destination node is shareable, the method further comprises:

confirming whether a sharable link between the upstream neighboring node and the service destination node is available;

flooding the sharable link after confirming that the sharable link between the upstream neighbor node and the traffic destination node is available.

25. The method according to claim 23 or 24, further comprising, prior to flooding the sharable link between the upstream neighboring node and the traffic destination node:

26. A network node, comprising:

a third flooding module, configured to flood a sharable link between the upstream neighboring node and the network node after determining that the link resource state information between the upstream neighboring node and the network node is sharable;

27. The network node of claim 26, further comprising:

a third determining module, configured to determine that preset link resource configuration information exists in the service destination node before flooding the sharable link between the upstream neighboring node and the service destination node, and determine that the link resource configuration information is sharable.

28. A network resource sharing system, comprising: the network node of any one of claims 7 to 11, the network node of any one of claims 18 to 22, and the network node of claim 26 or 27;

and the network nodes form a service working path.

29. A method for resource sharing, comprising:

30. The method according to claim 29, wherein when the downstream neighboring node is an intermediate node, the intermediate node receives and determines whether sharable link resource status information exists in the resource sharable message sent by an upstream neighboring node, the link resource status information included in the resource sharable message between the intermediate node and the upstream neighboring node, and the link resource status information between the intermediate node and the downstream neighboring node;

31. The method according to claim 29 or 30, wherein when the downstream neighboring node is a service destination node, the service destination node receives and determines whether link resource status information included in the resource sharing message sent by the upstream neighboring node between the service destination node and the upstream neighboring node is sharable;

32. A network resource sharing system, comprising: the system comprises an integrated controller, a service source node, an intermediate node and a service destination node;

the centralized controller centrally judges whether the links among the service source node, the intermediate node and the service destination node are shareable;

the centralized controller, the service source node, the intermediate node and the service destination node, configured to perform the method of any of claims 29 to 31.