WO2018053747A1 - Procédé de partage de ressources, nœud de réseau et appareil associé - Google Patents

Procédé de partage de ressources, nœud de réseau et appareil associé Download PDF

Info

Publication number
WO2018053747A1
WO2018053747A1 PCT/CN2016/099705 CN2016099705W WO2018053747A1 WO 2018053747 A1 WO2018053747 A1 WO 2018053747A1 CN 2016099705 W CN2016099705 W CN 2016099705W WO 2018053747 A1 WO2018053747 A1 WO 2018053747A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
link
resource
service
link resource
Prior art date
Application number
PCT/CN2016/099705
Other languages
English (en)
Chinese (zh)
Inventor
张弦
冯皓宇
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201680088411.8A priority Critical patent/CN109644122B/zh
Priority to PCT/CN2016/099705 priority patent/WO2018053747A1/fr
Priority to CN202011351939.4A priority patent/CN112803995B/zh
Publication of WO2018053747A1 publication Critical patent/WO2018053747A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/07—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems
    • H04B10/075—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal
    • H04B10/079—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal using measurements of the data signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/07—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems
    • H04B10/075—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal
    • H04B10/079—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal using measurements of the data signal
    • H04B10/0793—Network aspects, e.g. central monitoring of transmission parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00—Arrangements for synchronising receiver with transmitter
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0086—Network resource allocation, dimensioning or optimisation

Definitions

  • 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.
  • the management plane, the data plane (transport plane) and the control plane are mainly included; wherein the control plane and the functions provided by the control plane are all related to the relevant international standards organization.
  • the network usage rate of the ASON is measured by the service success rate.
  • the service success rate refers to the number of services that are successfully received and carried by the network among the total number of service requests.
  • SLA Service Level Agreement
  • the SLA is usually embodied by establishing different protection mechanisms for the service.
  • 1+1 protection or 1:1 protection is adopted.
  • the 1+1 protection refers to establishing two service paths for one service, and the service data is transmitted from the two service paths at the same time.
  • the destination node is Select one of the two service paths to receive service data;
  • 1:1 protection refers to establishing a work path for transmitting service data for the service, and a protection path for carrying service data only when the work path is faulty.
  • the embodiment of the present application provides a resource sharing method, a network node, and related equipment, so as to solve the problem that the prior art cannot balance the service success rate and the network resource utilization rate in the process of performing service data transmission.
  • a resource sharing method including:
  • the service source node After receiving the working path fault message, the service source node performs a resource status update determination, where the resource update determines whether the link resource between the service source node and the downstream neighbor node is faultless.
  • the method further includes:
  • the link resource between the service source node and the downstream neighbor node is faulty, the link resource status is not updated, or the link resource status between the service source node and the downstream neighbor node is updated to Not shareable.
  • the resource status update request message further carries request information that requires the downstream neighboring node to perform the resource status update determination.
  • the method further includes:
  • the service source node floods the link that can be shared between the service source node and the downstream neighbor node.
  • the service source node is flooded in the foregoing manner, and the link resources that are not faulty are temporarily released to be used by other services in the network, thereby ensuring service success. Based on the rate, the utilization of network resources is also improved.
  • the method before updating the link resource status between the service source node and the downstream neighboring node to be sharable, the method further includes:
  • Pre-determined link resource configuration information exists in the service source node, determining that the link resource configuration information is sharable, and/or the service source node receives a link resource from the downstream neighboring node.
  • the source configuration indication information indicates that the link resource configuration indication information is shareable.
  • the service source node is pre-set with the condition that the link related to the link can be shared or the link resource configuration, and the condition for flooding is increased, and the resource sharing can be further implemented. Whether or not flooding is more diversified.
  • the method further includes: setting a flooding condition
  • the flooding condition includes flooding the links between the arbitrarily shareable nodes to other nodes located in the same routing domain, or flooding the nodes to other working paths having a lower priority than the working path.
  • the flooding of the shareable link includes:
  • flooding is performed based on the set flooding conditions to improve the accuracy of flooding.
  • the method further includes:
  • the complete link resource status information refers to link resource status information between the nodes constituting the working path.
  • the method further includes:
  • the information that the sharable link resources between any nodes in the working path that are carried in the advertisement message are occupied by nodes corresponding to other services.
  • the method further includes:
  • the eighth method disclosed above can be used to guide all the original services to fall back, or partially fall back, or re-establish the working path, and improve the efficiency of the rollback.
  • a network node including:
  • a first determining module configured to: after receiving the working path fault message, the network node performs a resource status update determining, where the resource update is determined to determine a link between the network node and a downstream neighboring node of the service source node Whether the resource is fault free;
  • the first update module configured to: link resource status between the network node and the downstream neighboring node when link resources between the network node and the downstream neighboring node are not faulty Updated to shareable;
  • 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.
  • the first determining module is further configured to:
  • the link resource state is not updated
  • the first update module is further configured to update a link resource status between the network node and a downstream neighboring node when a link resource between the network node and the downstream neighboring node is faulty Not shareable.
  • the method further includes:
  • a first flooding module configured to share the link resource status between the network node and the downstream neighbor node after being sharable, and share the network node with the downstream neighbor node The link is flooded.
  • the method further includes:
  • a first determining module configured to perform preset link resource configuration information existing in the network node before updating a link resource status between the network node and the downstream neighboring node to be sharable Confirming that the link resource configuration information is sharable;
  • a first receiving module configured to receive link resource configuration indication information from the downstream neighboring node, before updating a link resource status between the network node and the downstream neighboring node to be sharable
  • the link resource configuration indication information indicates that sharing is possible.
  • the first flooding module is further configured to flood a link between any sharable nodes according to the set flooding condition
  • the flooding condition includes flooding the links between the arbitrarily shareable nodes to other nodes located in the same routing domain, or flooding the nodes with other working paths having a lower priority than the working path. A combination of one or both of the links between any shareable nodes.
  • the first receiving module is further configured to receive a second feedback message that is sent by the service destination node by using a signaling manner, where the second feedback message includes the working path.
  • Link resource status information refers to link resource status information between nodes constituting the working path.
  • the first receiving module is further configured to: receive a notification message sent by a node corresponding to another service, and mark a chain between the corresponding nodes based on the notification message. Road resources are occupied;
  • the information that the sharable link resources between any nodes in the working path that are carried in the advertisement message are occupied by nodes corresponding to other services.
  • the method further includes: a back-off module, configured to: after the network node receives the working service failure recovery message, query whether there is any unshared link resource
  • the link resources used by other services if all are not used by other services, the protection path directly falls back to the original working path; if some of the services are not used by other services, the protection path is rolled back to the case where the service policy is satisfied.
  • the partial protection path and part of the original working path form a new working path; if all are used by other services, the original service is downgraded if the user policy allows Process and release all resources to re-establish a new working path;
  • the fallback module is further configured to: when the network node queries that part or all of the sharable link resources are occupied by a service with a low priority, disconnecting the working path of the low priority service The shareable link resource of the original service and directly fall back from the protection path to the original working path.
  • a third method of the present application discloses a network node, including: a first memory, and a first processor connected to the memory;
  • the first memory is configured to store an operation process of the network node performing resource sharing
  • the first processor is configured to perform an operation flow of the resource sharing of the network node, where the operation flow of the resource sharing includes: after receiving the working path fault message, the network node performs a resource status update judgment The resource update is determined to determine whether the link resource between the network node and a downstream neighboring node of the network node is faultless;
  • a resource sharing method including:
  • the intermediate node After receiving the resource status update request message sent by the upstream neighboring node, the intermediate node performs a resource status update determination, where the resource status update determines that the link resource between the intermediate node and the downstream neighboring node of the intermediate node is determined. Whether there is no fault;
  • the method further includes:
  • the link resource between the intermediate node and the downstream neighboring node is faulty, the link resource state is not updated, or the link resource status between the intermediate node and the downstream neighboring node is updated to Not shareable.
  • the resource status update request message further carries request information that requires the downstream neighboring node to perform the resource status update determination.
  • the method further includes:
  • the upstream neighboring node and the obtained resource status update request message sent by the upstream neighboring node are obtained.
  • the link that can be shared between the intermediate nodes is flooded, and the link that can be shared between the intermediate node and the downstream neighboring node is flooded;
  • the upstream phase is A link that can be shared between the neighboring node and the intermediate node is flooded;
  • the link that can be shared between the intermediate node and the downstream neighbor node is flooded.
  • the intermediate node is flooded in the foregoing manner, and the link resources that are not faulty are temporarily released to be used by other services in the network, thereby ensuring the improvement of the service success rate. On the basis of, while improving the utilization of network resources.
  • the method further includes: the preset link resource configuration information exists in the intermediate node, determining that the link resource configuration information is shareable, and/or The intermediate node receives link resource configuration indication information from the downstream neighboring node, and the link resource configuration indication information indicates that it is shareable.
  • the intermediate node is pre-set whether the link related to the link can be shared or the link resource configuration, and whether the condition for flooding is increased, and the resource sharing can be further implemented. Whether or not flooding is more diversified.
  • the method further includes:
  • the method further includes: setting a flooding condition
  • the flooding condition includes flooding the link resource state information between the arbitrarily shareable nodes to other nodes located in the same routing domain, or flooding the nodes with other working paths having a lower priority than the working path.
  • a network node including:
  • a second determining module configured to: after receiving, by the network node, the resource status update request message sent by the upstream neighboring node, perform a resource status update determination, where the resource update is determined to determine a link between the network node and a downstream neighboring node Whether the resource is fault free;
  • the second update module is configured to update a link resource status between the network node and the downstream neighboring node when the link resource between the network node and the downstream neighboring node is faultless Is shareable;
  • a second sending module configured to send the resource status update request message to the downstream neighboring node, where the resource status update request message includes a link resource status between the network node and the downstream neighboring node And the first feedback message is sent to the upstream neighboring node, where the first feedback message includes: leasable link resource configuration indication information indicating that the upstream neighboring node is flooded with itself.
  • the second determining module is further configured to not update if the link resource between the network node and the downstream neighboring node is faulty.
  • Link resource status
  • the second update module is further configured to: when the link resource between the network node and the downstream neighboring node is faulty, connect the link between the network node and the downstream neighboring node The resource status is updated to be unshareable.
  • the method further includes:
  • a second flooding module configured to flood a link that is sharable between the upstream neighboring node and the network node, and a chain that is shareable between the network node and the downstream neighboring node The road is flooded.
  • the method further includes:
  • a second determining module configured to link resource resources of the network node and the downstream neighboring node Before the state is updated to be sharable, the preset link resource configuration information existing in the network node is confirmed, and the link resource configuration information is determined to be shareable;
  • the second receiving module is configured to receive link resource configuration indication information from the downstream neighboring node before updating a link resource status between the network node and the downstream neighboring node to be sharable
  • the link resource indication information indicates that sharing is possible.
  • the second determining module is further configured to receive the acknowledgement information sent by the upstream neighboring node, and determine the resource configuration between the network node and the upstream neighboring node. If the resource attributes are the same or the service attributes are the same, the correct information is fed back; if the resource configuration is not equal or the service attributes are inconsistent, the error information is fed back.
  • the second flooding module is further configured to perform flooding according to the flooding condition
  • the flooding condition includes flooding the links between the arbitrarily shareable nodes to other nodes located in the same routing domain, or flooding the nodes to other working paths having a lower priority than the working path.
  • a network node including: a second memory, and a second processor connected to the second memory;
  • the second storage is configured to store an operation process of the network node performing resource sharing
  • the second processor is configured to perform an operation flow of the resource sharing of the network node, where the operation flow of the resource sharing includes: after receiving, by the network node, a resource status update request message sent by an upstream neighboring node, Performing a resource status update determination, where the resource status update is determined to determine whether the link resource between the network node and the downstream neighbor node is faultless;
  • a seventh aspect of the present application discloses a resource sharing method, including:
  • the service destination node receives the resource status update request message sent by the upstream neighboring node, and obtains link resource status information between the upstream neighboring node and the service destination node included in the resource status update message, and confirms the upstream Whether the link resource status information between the neighboring node and the service destination node is shareable;
  • the method before the flooding of the link between the upstream neighboring node and the service destination node, the method further includes:
  • a preset link resource configuration information exists in the service destination node, and the link resource configuration information is determined to be shareable.
  • the service destination node is pre-set with the condition that the link related to the link can be shared or the link resource configuration, and the condition for flooding is increased, and the resource sharing can be further implemented. Whether or not flooding is more diversified.
  • the method further includes:
  • Receiving the acknowledgment information sent by the upstream neighboring node determining whether the resource configuration between the service destination node and the upstream neighboring node is equal, or whether the carried service attributes are consistent;
  • a network node including:
  • a third determining module configured to receive, by the network node, a resource status update request message sent by the upstream neighboring node, and obtain a link resource between the upstream neighboring node and the network node included in the resource status update message status information;
  • the third flooding module is configured to: after confirming that link resource state information between the upstream neighboring node and the network is sharable, between the upstream neighboring node and the network node The shared link is flooded;
  • a third sending module configured to send a first feedback message to the upstream neighboring node, where the first feedback message includes: a sharable link resource configuration indication indicating that the upstream neighboring node is flooded and related to itself information.
  • the method further includes: a third determining module, configured to: before flooding the link between the upstream neighboring node and the network node, A preset link resource configuration information is confirmed in the network node, and the link resource configuration information is determined to be shareable.
  • the third determining module is further configured to receive the acknowledgement information sent by the upstream neighboring node, and determine the resource configuration between the network node and the upstream neighboring node. If the resource attributes are the same or the service attributes are the same, the correct information is fed back; if the resource configuration is not equal or the service attributes are inconsistent, the error information is fed back.
  • a ninth aspect of the present application discloses a network node, including: a third memory, and a third processor connected to the third memory;
  • the third storage is configured to store an operation process of the network node performing resource sharing
  • the third processor is configured to perform an operation process of resource sharing of the network node, where the operation process of the resource sharing includes: receiving, by the network node, a resource status update request message sent by an upstream neighboring node, acquiring the In the resource status update message, the link resource status information between the upstream neighbor node and the network node is included, and it is confirmed whether the link resource status information between the upstream neighbor node and the network node is shareable. ;
  • a network resource sharing system is disclosed in the tenth aspect of the present application, comprising: the network node disclosed in the second aspect and the third aspect of the present application, the network node disclosed in the fifth aspect and the sixth aspect of the present application, and a network node disclosed in the eighth aspect and the ninth aspect of the present application;
  • the working nodes of the above network nodes form a service.
  • a resource sharing method including:
  • the service source node 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 floods the shareable link
  • the service source node sends the resource shareable message to the downstream neighboring node.
  • the service source node sends the resource shareable message to the downstream neighboring node, including:
  • the service source node deletes information related to the service source node in the resource sharable message, and sends the truncated resource sharable message to the downstream neighboring node.
  • the efficiency of the downstream neighboring node to find information related to itself can be improved.
  • the method further includes:
  • the service source node does not perform flooding, and sends the resource shareable message to the Downstream neighbors.
  • the intermediate node when the downstream neighboring node is an intermediate node, the intermediate node receives and determines, in the resource sharable message sent by the upstream neighboring node, Whether the included intermediate node and the upstream neighboring node, and the link resource state information between the intermediate node and the downstream neighboring node have sharable link resource state information;
  • the intermediate node and the upstream neighboring node, and the link resource state information between the intermediate node and the downstream neighboring node have sharable link resource state information, the intermediate node is panned a link that can be shared;
  • the intermediate node sends the resource sharable message to the downstream neighboring node.
  • the intermediate node sends the resource shareable message to the downstream neighboring node, including:
  • the efficiency of the downstream neighboring node to find information related to itself can be improved.
  • the method further includes:
  • the intermediate node does not perform flooding, and The resource shareable message sent by the upstream neighboring node is sent to the downstream neighboring node.
  • the service destination node when the downstream neighboring node is a service destination node, the service destination node receives and determines the resource sharing message sent by the upstream neighboring node. Whether the link resource status information between the service destination node and the upstream neighbor node is sharable;
  • the service destination node floods the shareable link.
  • the method further includes:
  • the service destination node does not perform flooding.
  • the resource shareable message further carries a flooding condition
  • the flooding condition includes flooding the links between the arbitrarily shareable nodes to other nodes located in the same routing domain, or flooding the nodes to other working paths having a lower priority than the working path.
  • the method further includes:
  • the control information includes:
  • the service is controlled to fall back from the protection path to a part of the shareable link that is not used by other services according to the state in which the shareable link resource in the original working path is partially occupied.
  • the resource is forcibly rolled back to the original working path according to the state in which the sharable link resource in the original working path is occupied by part or all of the service with low priority;
  • a twelfth aspect of the present application discloses a network resource sharing system, including: a centralized controller, a service source node, an intermediate node, and a service destination node;
  • the service source node, the intermediate node, and the service destination node constitute a working path of the service
  • the centralized controller centrally determines whether the link between the service source node, the intermediate node, and the service destination node is sharable.
  • the above-mentioned technical solution for resource sharing disclosed in the present application is performed by using a protection path to transmit data after a service has failed due to a failure of a working path, and whether each link on the working path has a fault with the related link. It is judged that the link resources that have not failed are temporarily released from each node and used by other services in the network, thereby improving the utilization rate of the network resources while ensuring the improvement of the service success rate.
  • FIG. 1 is a schematic diagram of a network topology structure and related information of service 1 according to Embodiment 1 of the present application;
  • FIG. 2 is a schematic flowchart of a resource sharing method according to Embodiment 1 of the present application.
  • FIG. 3 is a schematic flowchart of a resource sharing method according to Embodiment 2 of the present application.
  • FIG. 4 is a schematic diagram of a network topology structure and related information of service 2 according to Embodiment 3 of the present application;
  • FIG. 5 is a schematic flowchart of a resource sharing method according to Embodiment 3 of the present application.
  • FIG. 6 is a schematic diagram of a network topology structure and related information of service 3 according to Embodiment 4 of the present application;
  • FIG. 7 is a schematic structural diagram of a network node according to Embodiment 5 of the present application.
  • FIG. 8 is a schematic structural diagram of another network node according to Embodiment 5 of the present application.
  • FIG. 9 is a schematic structural diagram of another network node according to Embodiment 5 of the present application.
  • FIG. 10 is a schematic structural diagram of hardware of each node disclosed in Embodiment 5 of the present application.
  • FIG. 11 is a schematic structural diagram of a network resource sharing system according to Embodiment 5 of the present application.
  • FIG. 12 is a schematic structural diagram of another network resource sharing system according to Embodiment 5 of the present application.
  • ITU-T International Telecommunication Union-Telecommunication Standardization Sector, International Telecommunication Union - Telecommunication Standardization Sector;
  • ASON Automatically Switched Optical Network, automatic switched optical network
  • GMPLS Generalized Multi-Protocol Label Switching, extended multi-protocol label switching
  • OSPF-TE Open Shortest Path First-Traffic Engineering, open shortest path priority for traffic engineering extensions
  • RSVP-TE Resource ReserVation Protocol-Traffic Engineering, resource reservation protocol for traffic engineering extension
  • PCE Path Computation Element, path calculation unit
  • PCC Path Computation Client path calculation client
  • PCECP Path Computation Element Communication Protocol, used for communication between PCE and PCC;
  • LSP Label SwitchedPath, label switching path
  • SDN Software DefinedNetwork, software defined network.
  • the present application discloses a technical solution for resource sharing, which refers to a collective name of an entity in a network that can be used to deliver service data.
  • resource sharing refers to a collective name of an entity in a network that can be used to deliver service data.
  • link resources and node resources, etc. wherein the link resource is a kind of resource, which refers to using an actual physical carrier (such as: a fiber) to move customer data from one location to another; node resources, It refers to the ability to perform necessary processing on the business, for example, to convert the signal type of the customer from an electrical signal to an optical signal; or to exchange business data from one entry to another.
  • the specific node function depends on the specific functional requirements.
  • the resource sharing technical solution disclosed in the present application mainly relates to a link resource that does not fail on a working path that actually belongs to the service after the data is transmitted by the protection path due to the failure of the working path in a certain service. It is temporarily released for use by other services in the network, thereby improving the utilization rate of network resources while ensuring the improvement of business success rate.
  • FIG. 1 it is a schematic diagram of a network topology structure and service related information (LSP1) disclosed in Embodiment 1 of the present invention
  • LSP1 The service source node of the service one (LSP1) is A, the service destination node is B, and the link bandwidth between the node and the node is 1, so the service 1 can be simply referred to as LSP1 (A, B, 1).
  • the protection type of the service path is 1:1 protection.
  • the working path is: A-E-F-B (LSP1_W), and the protection path is: A-G-H-I-J-B (LSP1_P).
  • LSP1_W when one or more links in the working path LSP1_W of the service one fails, protection switching needs to be performed, that is, the service is from LSP1_W is switched to LSP1_P.
  • other links in the working path LSP1_W that have not failed can be used as shared resources for other services in the network.
  • the link F-B between the node F and the node B fails.
  • the link EF is shared, that is, the link AE and the link EF are specifically shared by using the resource sharing method disclosed in the present application.
  • the sharing process is shown in the following example;
  • FIG. 2 a specific flowchart for performing sharing on the link A-E and the link E-F is as shown in FIG. 2:
  • the service source node A After receiving the working path fault message, the service source node A performs a resource status update determination, where the resource update determines whether the link resource between the current node and the downstream neighbor node is faultless.
  • S102 The service source node A sends a first resource status update request message to the intermediate node E.
  • the first resource status update request message includes the link resource status information of the link AE, and the link resource of the link AE is the link resource of the link AE.
  • Status information indicates that the link AE can be shared;
  • the first resource status update request preferably, the request information that requires the downstream neighboring node to perform the resource status update determination may be represented by the link resource status information, or may be independently carried;
  • the intermediate node E receives the first resource status update request message, and performs a link EF between the intermediate node E and the intermediate node F (the downstream neighboring node of the intermediate node E), and the resource status update judgment of whether the link resource is faultless ;
  • the resource update determination is performed after the intermediate node E receives the first resource status update request message sent by the service source node A.
  • the intermediate node E sends a second resource status update request message to the intermediate node F.
  • the second resource status update request message includes the link E-F.
  • Link resource status information because the link resource status of the link E-F is sharable, the link resource status information of the link E-F indicates that the link E-F can be shared;
  • the intermediate node F receives the second resource status update request message, and performs a link FB between the intermediate node F and the service destination node B (the downstream neighboring node of the intermediate node F), and whether the link resource has a faultless resource status. Update judgment
  • the third resource status update request message includes link resource status information of the link FB. If the link FB fails, the link resource status information of the link FB indicates the link. FB has a fault;
  • the service destination node B receives the third resource status update request message, and determines whether the link resource status information of the link F-B included in the third resource status update request message indicates that the link F-B is shareable.
  • the third resource status update request message received by the service destination node B may include request information that requires the downstream neighboring node to perform the resource status update determination, but because the service destination node B is the working path. The last node on the node, therefore, the service destination node B does not need to judge whether the link resources between itself and the downstream neighbor nodes are sharable, and only needs to make a judgment on whether to flood;
  • the link resource status information of the link FB indicates that the link FB is faulty, and the service destination node B does not perform flooding, and the service destination node B sends the first to the intermediate node F (the upstream adjacent node of the service destination node B) Feedback message
  • the link resource state information of the link F-B indicates that the link F-B is faulty due to the assumption based on the present embodiment. Therefore, after the judgment of step S108 is passed, it is confirmed that the link F-B is faulty and cannot be shared, and flooding is not required.
  • the first feedback message includes: sharable link resource configuration indication information indicating that the upstream neighboring node is flooded and related to itself;
  • the intermediate node F floods the sharable link E-F obtained in the received second resource status update request message.
  • the intermediate node F is aware of the known shared chain.
  • the road E-F floods to share the link E-F in the routing domain.
  • the intermediate node F sends a first feedback message to the intermediate node E (the upstream neighboring node of the intermediate node F), where the first feedback message includes: an indication indicating that the upstream neighboring node floods the susceptible link related to itself information;
  • the intermediate node E After receiving the first feedback message, the intermediate node E performs the sharable link AE obtained in the received first resource status update request message, and the sharable link EF obtained through the self-determination. Flooding
  • step S116 of the embodiment the shareable link EF is determined by the intermediate node E after performing step S103 and step S104; the intermediate node E is known to be related to the first feedback message after receiving the first feedback message.
  • the sharable link EF and the link AE are flooded to share the link EF and the link AE in the routing domain;
  • flooding may be performed based on the OSPF protocol, or flooding may be performed based on other protocols;
  • the intermediate node E sends a first feedback message to the service source node A (the upstream neighboring node of the intermediate node E), where the first feedback message includes: indicating that the upstream neighboring node floods the susceptible link related to itself. Indication information;
  • step S114 of this embodiment the shareable link A-E is determined by the service source node A after performing step S101. As described above, after receiving the first feedback message, the service source node A floods the known LINK-shared links A-E, and implements sharing of the links A-E in the routing domain.
  • the resource sharing mode disclosed in the present application is used to update the link EF and the link EF of the working path to the shared link.
  • the nodes that are related to themselves and have no faults are flooded across the network, so that other nodes in the network can be notified that these updates are sharable links.
  • the flow of performing sharing on the link A-E and the link E-F is different from that in the first example in that:
  • each node After confirming that the respective related links are sharable, each node directly floods the link that can be shared between the respective neighboring nodes, and does not need to perform resource update judgment on each node in the entire working path.
  • the upstream neighboring node receives the feedback message sent by the downstream neighboring node, performing flooding based on the feedback message;
  • the service source node A after the service source node A performs step S101, the service source node A floods the link resource status update to the shareable link A-E;
  • the intermediate node E obtains the shareable link AE obtained in the received first resource state update request message, and the shareable information obtained through the self judgment.
  • Link EF for flooding
  • the intermediate node F performs step S107 to confirm that the link resource of the link FB between the intermediate node F and the service destination node B is faulty, and the intermediate node F pairs the received second resource.
  • the obtained shareable link EF is flooded;
  • the flooding can be performed.
  • the intermediate node E receives the first resource status update request message sent by the service source node A and parses the AE link resource status information indicating that the link AE can be shared, the LINK link AE is performed. Flooding.
  • the intermediate node E performs the current flooding, it is determined whether the link resource of the link EF between the intermediate node E and the intermediate node F is faultless, and the link resource of the link EF is obtained as a faultless After that, the link EF updated to be shareable is flooded.
  • the intermediate node located on the working path can obtain the contiguous link resources of the upstream neighboring node and itself, and determine that the link resources of the neighboring node and the downstream neighboring node are shareable. After that, a flooding is performed; after receiving the link resource state information indicating that the link can be shared by the upstream neighboring node, the flooding is performed first, and the link between the neighboring node and the downstream neighboring node is determined. Once the resource is shareable, perform another flood.
  • each node Through the timing of performing flooding by each node disclosed in the foregoing example 2, it is also possible for each node to obtain or confirm the fault-free link related to itself, flooding the entire network, thereby realizing notification to other nodes in the network. These updates can be used as links in a shareable state.
  • the service source node After receiving the working path fault message, the service source node performs a resource status update judgment, and the resource update determines whether the link resource between the service source node and the downstream neighbor node is faultless.
  • whether the service source node updates the link resource status further includes: if it is determined that the link resource between the service source node and the downstream neighbor node is faulty, the link resource is not updated. Status, or, update the link resource status between the service source node and the downstream neighbor node to be non-shareable;
  • the method further includes: sharing, after the link resource status between the service source node and the downstream neighbor node is sharable, shareable between the service source node and the downstream neighbor node.
  • Link flooding
  • the service source node adopts the following manner:
  • the service source node receives the first feedback message sent by the downstream neighboring node, where the first feedback message includes leasable link resource configuration indication information indicating that the upstream neighboring node is flooded with itself;
  • the service source node floods the shareable link and does not flood the unshareable link.
  • the service source node pairs the service before sending the resource status update request message to the downstream neighbor node.
  • the link that can be shared between the source node and the downstream neighboring node is flooded.
  • the intermediate node After receiving the resource status update request message sent by the upstream neighboring node, the intermediate node performs a resource status update determination, and the resource update determines whether the link resource between the intermediate node and the downstream neighboring node is faultless.
  • whether the intermediate node updates the link resource status further includes: if it is determined that the link resource between the intermediate node and the downstream neighbor node is faulty, the link resource status is not updated, or Updating the link resource status between the intermediate node and the downstream neighbor node to be non-shareable;
  • the method further includes: the intermediate node floods the link that can be shared between the upstream neighboring node and the intermediate node, and the link that can be shared between the intermediate node and the downstream neighboring node. Flooding.
  • the manner adopted by the intermediate node is:
  • the first type after receiving the first feedback message sent by the downstream neighboring node, the first feedback message includes: leasable link resource configuration indication information indicating that the upstream neighboring node is flooded with itself;
  • the resource status update request message sent by the intermediate node to the upstream neighboring node, the included link between the upstream neighboring node and the intermediate node is flooded, and the intermediate node and the downstream neighboring node are shareable.
  • Link flooding
  • the unshared link between the upstream neighboring node and the intermediate node, and/or between the intermediate node and the downstream neighboring node is not flooded;
  • the intermediate node obtains the link resource status information between the upstream neighboring node and the intermediate node included in the resource status update request message sent by the upstream neighboring node, and after being confirmed as sharable, the intermediate node is adjacent to the upstream A link that can be shared between a node and an intermediate node is flooded.
  • the intermediate node floods the link that can be shared between the intermediate node and the downstream neighboring node;
  • the intermediate node may first perform flooding or non-flooding based on whether the result is sharable or not. After determining the link resource information of the intermediate node and the downstream neighboring node, performing flooding or no flooding based on the sharable result;
  • the link resource state information of the upstream neighboring node and the intermediate node is obtained, and the link resource state information of the intermediate node and the downstream neighboring node is determined, and then all flooding is performed based on whether the result is sharable or not. Or partial flooding, or no flooding;
  • the service destination node receives the resource status update request message sent by the upstream neighboring node, where the resource status update request message includes link resource status information between the upstream neighboring node and the service destination node;
  • the service destination node obtains link resource status information between the upstream neighboring node and the service destination node in the resource status update request message sent by the upstream neighboring node;
  • the service destination node After confirming that the link resource status information between the upstream neighboring node and the service destination node is sharable, the service destination node floods the link that can be shared between the upstream neighboring node and the service destination node;
  • the service destination node sends a first feedback message to the upstream neighboring node, where the first feedback message includes: sharable link resource configuration indication information indicating that the upstream neighboring node is flooded and related to itself.
  • the service destination node does not perform flooding when it confirms that the link resource status information between the upstream neighboring node and the service destination node is not shareable;
  • the resource sharing method when the service source node and the intermediate node send the resource status update request message to the downstream neighboring node, the resource status update request message is required to be executed by the downstream neighboring node, and the In the process of resource sharing method, the RSVP-TE protocol is implemented.
  • the extension adds a TLV (Type-length-value) object to the RSVP-TE protocol.
  • TLV Type-length-value
  • the TLV can be placed in the LSP_REQUIRED_ATTRIBUTES object as an indication that the downstream neighbor nodes are required to make resource update judgments.
  • the service source node and the intermediate node send the sharable state of the neighboring node to the downstream neighboring node, or the intermediate node or the service destination node is adjacent to the upstream.
  • the node, the sharable state of one or more links between the feedback nodes in the process of performing the resource sharing method, the RSVP-TE protocol is extended, and the TLV is added in the RSVP-TE protocol ((Type-length- The value object represents the shareable state of one or more links.
  • the specific format is as follows:
  • Link ID X (link identifier, variable length): It can represent the 32-bit link IP address, and can also represent the node ID + link ID, depending on the specific link type. As long as it can be expressed to unique A network link is all right.
  • the Status Flag is not limited to the two types of information, and other information may be added as needed.
  • the service source node, the intermediate node, and the service destination node flood the shareable link based on the OSPF protocol
  • a new TLV needs to be added to the OSPF protocol to indicate that the resource can be shared. Shared link resource status information.
  • the newly defined TLV format is as follows:
  • Type (16 bits, TLV type), used to deliver sharable link resource status information
  • the technical solution for resource sharing disclosed in the present application in the case of a service, fails to use the protection path to transmit data, and then passes through the nodes on the working path for the upstream and downstream.
  • the link resources between adjacent nodes and downstream neighboring nodes are processed, which will actually belong to the working path of the service, and the fault-free link resources are updated to be shareable, and then flooded to enable sharing.
  • the link is temporarily released for use by other services in the network, thereby improving the utilization rate of network resources while ensuring the improvement of service success rate.
  • a condition that the link related to the link can be shared or a link resource configuration may be set in advance, that is, each node is set in advance and related thereto. Pre-set conditions for shared or non-shareable links;
  • the method before the service source node and the intermediate node update the link resource status between each of the downstream neighboring nodes to be sharable, the method further includes: the service source node and the intermediate node pair have a preset link. Resource configuration information, determining that the link resource is configured to be sharable, and/or, the service source node and the intermediate node receiving link resource configuration indication information from the downstream neighboring node, the link resource configuration indication information indicating that the information is shareable;
  • the service destination node Before the service destination node floods the link that can be shared between the upstream neighboring node and the service destination node, the service destination node has preset link resource configuration information, and the link resource configuration information can be shared. ;
  • each node sets link resource configuration information for a link resource between a respective node and a neighboring node, and the link resource configuration information includes link resource shareable and link resource unshareable.
  • the service source node sets resource configuration information for link resources between the respective nodes and downstream neighboring nodes.
  • the intermediate node sets resource configuration information for the link resources between the intermediate node and the upstream neighboring node and the downstream neighboring node respectively.
  • the service destination node sets resource configuration information for the link resource between the service destination node and the upstream neighbor node. If any one of the two adjacent nodes sets the link resource to be unshareable, the link resources between the two nodes are not shareable. Or, if the resource configuration information set on two adjacent nodes is inconsistent, the link resources between the two nodes are not shared.
  • the service source node after the service source node receives the working path fault message, before performing the resource state update judgment, it is necessary to first determine whether the preset condition of the service source node includes A sharable configuration, when the preset condition of the service source node includes a sharable configuration, and then further determines whether there is no fault; when the preset condition of the service source node includes a non-shareable configuration, the downstream phase is directly executed. a step of the neighbor node sending a resource status update request message;
  • the subsequent step is continued; when the preset condition of the service source node includes a non-shareable configuration, the direct sending of the downlink neighbor node is performed.
  • the step of the source status update request message is performed.
  • the intermediate node and the service destination node also need to make the same judgment before receiving the resource status update status message sent by the upstream neighboring node, and determine whether the preset condition includes a shareable configuration or is not shareable. Configuration.
  • the service source node and the intermediate node update the link resource status between itself and the downstream neighbor node to be shareable, further:
  • the service source node and the intermediate node send a confirmation message to the downstream neighboring node to confirm whether the link resource status update between the nodes can be shared, and if the error information fed back by the downstream neighbor node is received, the service source node and the middle The node re-marks the link resource status between the nodes, that is, it is marked as not shareable;
  • the downstream neighboring node After the acknowledgment information is received by the downstream neighboring node, it is determined whether the resource configuration between the neighboring node and the upstream neighboring node is equal, or whether the carried service attributes are consistent, if the resource configuration is equal or the service attribute is consistent. , the correct information is fed back, and if the resource configuration is not equal or the service attributes are inconsistent, the error information is fed back;
  • the operation between the service source node A and the intermediate node E (which is the downstream neighboring node of the service source node A) is taken as an example, as shown in FIG. 3:
  • the service source node A After receiving the working path fault message, the service source node A performs a resource status update judgment, where the resource update determines to determine the link AE between the service source node A and the downstream neighboring node, and whether the link resource is faultless. If the link resource of the link AE between the service source node A and the intermediate node E is not faulty, the process proceeds to S201. If the link resource of the link AE between the service source node A and the intermediate node E is faulty, the link resource is directly executed. S202;
  • the service source node A updates the status of the corresponding A-E link resource in the working path to be shareable.
  • the service source node A sends the sharable A-E link resource status information to the intermediate node E.
  • the intermediate node E receives the vestable AE link resource state information, and determines whether the resource configuration between the intermediate node E and the service source node A is equal, or determines the service attribute carried by the intermediate node E and the service source node A. Whether it is consistent, if it is identical or consistent, it feeds back the correct information to the service source node A, and executes S205; if it is not identical or inconsistent, it feeds back the error information to the service source node A, And executing S204;
  • the service source node A updates the status of the corresponding A-E link resource in the working path to be unshared.
  • S205 The service source node A sends a resource status update request message to the intermediate node E.
  • flooding may be performed based on a conventional manner, or the same or different flooding conditions may be set for each node, thereby Each node performs flooding based on flooding conditions;
  • the first type can flood the link resource status information between the shared nodes to other nodes in the entire network
  • the second type of flooding condition can be set to limit the link resource status information of the sharable nodes in the flooding of the entire network.
  • the specific flooding conditions can be:
  • link resource status information between any sharable nodes obtained by flooding other nodes in the same routing domain with the working path of the service ie, the service source node, the intermediate node, and the service destination node
  • the link resource status information is a node in the working path of the other service whose priority is lower than that of the service, and then flooding; it should be noted that the scope of the above-mentioned restricted flooding or flooding to a specific node is flooded.
  • the process can be performed in any order;
  • the restrictions added in the flooding process may be specifically added to the value of the newly added TLV of the OSPF protocol, such as Priority (3 bits), which is used to indicate that the resource sharing method can be used.
  • Priority 3 bits
  • the above-mentioned flooding method disclosed in the embodiment of the present application is only a part of the present application.
  • the manner of flooding is not limited thereto.
  • each node uses a signaling manner to send a link resource status related thereto to a downstream neighboring node, and then the service destination node passes In the signaling mode, the link resource status of each node in the entire working path is fed back to the service source node, so that the service source node learns the link resource status between the nodes of the entire working path;
  • the service source node receives a second feedback message sent by the service destination node by using a signaling manner, where the second feedback message includes the link resource status of the working path.
  • the link resource status information refers to link resource status information between nodes constituting the working path;
  • the link resource status information By receiving the link resource status information by the service source node, it can be known that the links in the working path are sharable, and in the process of restoring the working path, refer to whether the sharable link is occupied by other services. In order to complete the corresponding recovery work path operation.
  • a network controller may be used to make a decision on whether to share resources between the nodes (network elements).
  • the service LSP2 is used as an example.
  • the protection switching needs to be performed, that is, the service 2 is switched from LSP2_W to LSP2_P.
  • the decision of the network controller can be utilized as a shared resource for other services in the network, as shown in FIG. 4:
  • the centralized controller K is configured to perform centralized processing on nodes in each working path in the entire network;
  • the service source node of the LSP2 is A1, the service destination node is B1, and the link bandwidth between the node and the node is 1, so the LSP2 can be simply referred to as LSP2 (A1, B1, 1).
  • the protection type of the service path is 1:1 protection, where the working path is: A1-E1-B1, and the protection path is: A1-G1-H1-J1-B1; in this example, assume node E1 and node B1 The link E1-B1 has failed.
  • the specific implementation process of the resource sharing method disclosed in this embodiment of the present application is as follows: The specific flow chart is shown in Figure 5:
  • the centralized controller receives the working path fault message, and calculates a shareable link resource in the working path and a link resource that is not shareable based on the working path fault message and the service policy of the centralized controller, and generates a resource shareable message. And reporting to the service source node A1; wherein the resource shareable message includes link resource state information between adjacent nodes in the working path, to indicate that link resources between those nodes can be shared;
  • the resource sharing message may further include: which type or level of services may be shared by the shareable link resource;
  • the service source node A receives the resource sharing message, reads the link resource state information between the service source node A1 and the intermediate node E1 included in the resource shareable message, and determines the link resource state information of the link A1-E1. Whether it is sharable, if the link resource status information of the link A1-E1 is sharable, then executing S304, if the link resource status information of the link A1-E1 is not shareable, directly executing S305;
  • the service source node A1 deletes the information related to the service source node A1 in the resource shareable message, and sends the deleted resource shareable message to the intermediate node E1;
  • the intermediate node E1 receives the resource sharable message sent by the service source node A1, and reads the link resource status information of the link A1-E1 and the link E1-B1 included in the resource sharing message, and determines the link A1- Whether there is sharable link resource status information in the E1 and the link E1-B1, because the link resource status information of the link A1-E1 can be shared, then S307 is performed;
  • the intermediate node E1 deletes the information related to the intermediate node E1 in the resource sharable message sent by the service source node A1, and sends the deleted resource shareable message to the service destination node B1;
  • the service destination node B1 receives the resource sharable message sent by the intermediate node E1, and reads the link resource status information of the link E1-B1 included in the resource sharing message, and determines the link resource status of the link E1-B1. Whether the information is sharable. Because the link resource status information of the link E1-B1 is not shareable, no flooding is performed.
  • the centralized controller K performs calculation according to the fault message, and the link between each adjacent node in the working path is obtained.
  • the link resource status information of each neighboring node included in the message may be shared, and the flooding judgment is performed; after the fulfilable flooding condition is met, the corresponding flooding is performed, which will actually belong to the working path of the service,
  • the faulty link resources are temporarily released for use by other services in the network, thereby improving the utilization of network resources while ensuring the improvement of service success rate.
  • the above embodiment is merely an example, and does not limit the faulty link to the last segment, which is applicable to the case where any link on the working path fails.
  • the specific operation of the service source node in the working path is:
  • the service source node After receiving the working path fault message, the service source node reports the working path fault message to the centralized controller.
  • the service source node receives the resource sharable message fed back by the centralized controller, and the resource sharable message includes link resource state information between adjacent nodes in the working path;
  • the service source node determines the link resource status information between the service source node and the downstream neighbor node according to the link resource state information between the service source node and the downstream neighbor node included in the resource sharable message. Whether the interest is shareable;
  • the service source node floods the shareable link
  • the service source node sends a resource sharing message to the downstream neighbor node.
  • the service source node may also delete the information related to the service source node in the resource shareable message, and send the deleted resource shareable message to the downstream neighboring node.
  • the intermediate node receives the resource sharable message sent by the upstream neighboring node, and reads the intermediate node and the upstream neighboring node included in the resource sharing message sent by the upstream neighboring node, and the link between the intermediate node and the downstream neighboring node. Resource status information, and determining whether there is sharable link resource status information in the link resource status information between the intermediate node and the upstream neighbor node, the intermediate node, and the downstream neighbor node;
  • the intermediate node floods the shareable link
  • the intermediate node sends a resource shareable message to the downstream neighboring node.
  • the intermediate node may also delete information related to the intermediate node in the resource sharable message sent by the upstream neighboring node, and send the revoked resource sharable message to the downstream neighboring node;
  • the service destination node receives the resource sharable message sent by the upstream neighboring node, and reads the link resource state information between the service destination node and the upstream neighboring node in the resource sharing message sent by the upstream neighboring node, and judges the service. Whether the link resource status information between the destination node and the upstream neighbor node is sharable;
  • the service destination node floods the shareable link
  • the service destination node does not perform flooding.
  • the PCEP protocol can also be used between the centralized controller and the node.
  • the PCEP protocol is extended, that is, a bit is extended in the PCEP protocol. A judgment request for indicating whether the PCC requests the PCE to make a resource shareable;
  • a restriction condition in the process of generating a resource shareable message by the centralized controller, a restriction condition may be added, and the restriction condition may be carried by the following TLV, and different The restrictions can also be distinguished by Type;
  • the constraint may be: the priority of the sharable link resource may be used, that is, the information of the PriorityNumber is added in the Value part; or the LSP may be used. Number of shared link resources, such as LSP Number;
  • the feature information of the link resource state that can be shared is carried in the PCEP protocol and the RSVP-TE protocol
  • the feature information may be carried by using the TLV defined above.
  • the link resources between the nodes that have not failed are flooded and shared according to the flooding or flooding conditions of the entire network. a process of establishing a working path when a node that receives a flooded sharable link receives a service request;
  • the process of establishing a working path mainly includes the following steps:
  • the service source node C searches for and obtains an available link CK and a link LD between the service source node C and the service destination node D in the network, and calculates an available path between the service source node C and the service destination node D. ;
  • the service source node C obtains the available link E-F based on the received flooded sharable link A-E and link E-F;
  • the service source node C recalculates the available path by using the link C-K, the link L-D, and the link E-F, and based on the calculated available path C-K-E-F-L-D including the link E-F;
  • the service source node C sends a resource allocation request to the originating node E corresponding to the link E-F.
  • the service source node C uses the RSVP-TE message to establish a corresponding working path C-K-E-F-L-D based on the available path;
  • the service source node C sends an advertisement message to the service source node A of the original working path where the link E-F is located, where the advertisement message carries information that the link E-F is occupied.
  • the node that receives the service request in the pin network first considers whether there are available resources that are not occupied by other services in the network, if not obtained.
  • the corresponding available path is considered to be temporarily shared among other services.
  • Link resource and after calculating the available path, sending a resource allocation request to the starting node of the sharable link resource included in the available path, and after the starting node feedback allows the establishment of the cross, using the RSVP-TE message, based on
  • the calculated available path establishes a corresponding service path, and sends an advertisement message to the service source node of the service path where the sharable link resource is located, to notify that the sharable link resource is occupied.
  • the service data is performed on the protection path.
  • the transmitted service needs to be rolled back from the protection path to the working path.
  • the flooding method uses the following methods to roll back:
  • the protection path is rolled back to a part of the sharable link resources that are not used by other services.
  • the partial protection path and part of the original working path constitute a new job. path;
  • the queried link resource is partially or completely occupied by the service with low priority
  • the tradable link resource of the original service that is used in the working path of the service with the lower priority is disconnected, and directly The protection path is rolled back to the original working path.
  • the centralized controller determines whether it is shareable, after the service source node receives the work path failure recovery information:
  • the service source node sends a working path failure recovery message to the centralized controller
  • the centralized controller evaluates the complexity of restoring to the original working path based on the working path failure recovery message
  • control service is rolled back from the protection path to a part of the sharable link resources that are not used by other services, according to the state in which the sharable link resources in the original working path are partially occupied. ;
  • control service is forcibly rolled back to the original working path according to the state in which the sharable link resource in the original working path is occupied by part or all of the service with a lower priority;
  • the difficulty coefficient of the preset complexity is generally based on the power consumption required to establish a new working path.
  • the method is used to roll back to some or all of the original working paths. Or re-establishing a new working path, further improving the success rate of the fallback, and effectively improving the utilization of network resources.
  • the embodiment of the present application further correspondingly discloses a network node structure that can implement resource sharing by a service source node, an intermediate node, and a service destination node, and has a corresponding service source node.
  • a network resource sharing system in which the network node of the intermediate node and the service destination node function constitutes a working path of the service;
  • each network node does not depend on the When the controller is centralized; the network nodes having the resource sharing functions of the corresponding service source node, the intermediate node, and the service destination node are respectively described in detail;
  • FIG. 7 a schematic diagram of a structure of a first network node that can implement resource sharing by a service source node, where the first network node 100 includes: a resource sharing method performed by a service source node for performing the foregoing disclosure.
  • the first determining module 101 is configured to: after receiving the working path fault message, the network node performs a resource status update determination, where the resource update is determined to determine that the network node is adjacent to a downstream node of the network node.
  • the first update module 102 is configured to: when the link resource between the network node and the downstream neighbor node is not faulty, connect the network node to the downstream The link resource status between the nodes is updated to be sharable; the first sending module 103 is configured to send a resource status update request message to the downstream neighboring node, where the resource status update request message includes the network node and the Link resource status information between downstream neighbor nodes.
  • the first network node 100 disclosed in the embodiment of the present invention further includes: a first management module, configured to receive a resource allocation request sent by a node corresponding to another service, and provide feedback to the node corresponding to the other service according to the resource configuration policy. Establish cross information.
  • the service source node 100 disclosed in the embodiment of the present invention further includes: a first flooding module, and a first determining module and/or a first receiving module, a back-off module, and the like, to implement the resource sharing of the service source node.
  • the module of the corresponding function in the process is not limited to: a first flooding module, and a first determining module and/or a first receiving module, a back-off module, and the like.
  • FIG. 8 it is a schematic structural diagram of a second network node that can implement resource sharing by an intermediate node, where the second network node 200 includes: a method for performing resource sharing performed by an intermediate node, which is disclosed in the foregoing application.
  • the second determining module 201 is configured to: after receiving, by the network node, the resource status update request message sent by the upstream neighboring node, perform a resource status update determination, where the resource update is determined to determine that the network node is adjacent to the downstream neighboring node.
  • the second update module 202 is configured to: when the link resource between the network node and the downstream neighbor node is not faulty, The link resource status between the network node and the downstream neighboring node is updated to be sharable; the second sending module 203 is configured to send the resource status update request message to the downstream neighboring node, where the resource status
  • the update request message includes link resource status information between the network node and the downstream neighboring node, and sends a first feedback message to the upstream neighboring node, where the first feedback message includes an indication
  • the upstream neighboring node floods the susceptible link resource configuration indication information related to itself.
  • the intermediate node 200 disclosed in the embodiment of the present invention further includes: a second management module, configured to receive a resource allocation request sent by a node corresponding to another service, and feed back to the node corresponding to the other service according to the resource configuration policy to allow the establishment of the crossover. information.
  • a second management module configured to receive a resource allocation request sent by a node corresponding to another service, and feed back to the node corresponding to the other service according to the resource configuration policy to allow the establishment of the crossover. information.
  • the second network node 200 disclosed in the embodiment of the present invention further includes: a second flooding module 204, and a second determining module and/or a second receiving module, etc., to implement corresponding resources in the intermediate node Functional module.
  • FIG. 9 a schematic diagram of a structure of a third network node that can perform resource sharing by a service destination node, where the network node 300 includes: a method for performing a resource sharing method performed by a service destination node disclosed in the above application.
  • the third determining module 301 is configured to receive, by the network node, a resource status update request message sent by the upstream neighboring node, and obtain the resource status update message included between the upstream neighboring node and the network node.
  • Link resource status information the third flooding module 302, configured to: after confirming that the link resource status information between the upstream neighboring node and the network node is sharable, to the upstream neighboring node And the third communication module 303 is configured to send a first feedback message to the upstream neighboring node, where the first feedback message includes: indicating the upstream The neighboring node floods the susceptible link resource configuration indication information related to itself.
  • the third network node 300 disclosed in the embodiment of the present invention further includes: a third determining module or the like, and a module for implementing the corresponding function in the resource sharing process by the intermediate node.
  • Each of the foregoing first network node 100, the second network node 200, and the third network node 300 performs resource sharing, and a specific process or principle related to resource sharing, and the foregoing disclosure and the Within a network node, a second network node, and a third network node Corresponding to each other, they can be referred to each other, so they will not be described here.
  • the resource sharing method described in connection with the embodiments disclosed herein may be implemented directly in hardware, a processor-executed memory, or a combination of both in a first network node, a second network node, and a third network node. Therefore, the present application further relates to the resource sharing method disclosed in the foregoing application embodiment, and respectively discloses a first network node, a second network node, and a third network node, which have the same structure, as shown in FIG. 10, the first The network node, the second network node, and the third network node each include a memory 10 and a processor 12 coupled to the memory 10 via a bus 11.
  • the memory 10 has a storage medium in which an operation flow in which respective network nodes perform resource sharing is stored.
  • the operation flow of the resource sharing that is, the program corresponding to the resource sharing method for each network node disclosed above, the program may include program code, and the program code may include a series of operation instructions arranged in a certain order.
  • the processor may be a central processing unit CPU, or a specific integrated circuit, or one or more integrated circuits configured to implement embodiments of the present application.
  • the memory may include high speed RAM memory and may also include non-volatile memory, such as at least one disk memory.
  • the processor is connected to the memory through a bus.
  • the processor calls an operation flow of the resource sharing stored in the memory.
  • a first network node 100, a second network node 200, and a third network node are also disclosed.
  • 300 A network resource sharing system 1 constituting a working path of a service.
  • the dotted line in FIG. 11 indicates the first network node, the second network node, the second network node, and the like in the working paths of other services.
  • the network resource sharing system 4 mainly includes a centralized controller 400, a service source node 401, an intermediate node 402, and a service destination node 403.
  • the service source node 402, the intermediate node 403, and the service destination node 404 are based on the foregoing The method can be implemented by the corresponding module, and will not be described here.
  • the broken lines in Fig. 12 indicate service source nodes, intermediate nodes, service destination nodes, and the like in the working paths of other services.
  • the present application discloses a technical solution for resource sharing, which is a chain that does not fail on the working path that actually belongs to the service after the data is transmitted by the protection path due to the failure of the working path in a certain service.
  • the road resources are temporarily released for use by other services in the network, thereby improving the utilization rate of network resources while ensuring the improvement of the service success rate.
  • the problems involved in the rollback are considered, thereby improving the success rate of the rollback and also improving the utilization of the resources in the forward.

Abstract

L'invention concerne un procédé de partage de ressources, un nœud de réseau et un appareil associé. Le procédé comprend les étapes suivantes : lors d'une défaillance d'un service se produisant dans une route opérationnelle, et une route de repli étant adoptée pour une transmission de données, déterminer, par un nœud sur un itinéraire de travail, si une défaillance a été trouvée dans une liaison associée, et libérer temporairement une ressource de liaison du nœud sans défaillance à utiliser par un autre service dans un réseau. Par conséquent, le mode de réalisation est utilisé pour augmenter un taux d'utilisation de ressources de réseau tout en garantissant un taux de réussite accru d'un service.
PCT/CN2016/099705 2016-09-22 2016-09-22 Procédé de partage de ressources, nœud de réseau et appareil associé WO2018053747A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201680088411.8A CN109644122B (zh) 2016-09-22 2016-09-22 资源共享方法、网络节点及相关设备
PCT/CN2016/099705 WO2018053747A1 (fr) 2016-09-22 2016-09-22 Procédé de partage de ressources, nœud de réseau et appareil associé
CN202011351939.4A CN112803995B (zh) 2016-09-22 2016-09-22 资源共享方法、网络节点及相关设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/099705 WO2018053747A1 (fr) 2016-09-22 2016-09-22 Procédé de partage de ressources, nœud de réseau et appareil associé

Publications (1)

Publication Number Publication Date
WO2018053747A1 true WO2018053747A1 (fr) 2018-03-29

Family

ID=61689325

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/099705 WO2018053747A1 (fr) 2016-09-22 2016-09-22 Procédé de partage de ressources, nœud de réseau et appareil associé

Country Status (2)

Country Link
CN (2) CN112803995B (fr)
WO (1) WO2018053747A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110167032A (zh) * 2019-04-30 2019-08-23 陕西师范大学 无人机控制的软件定义无线自组织网络的组网方法和系统
CN113823040A (zh) * 2020-06-19 2021-12-21 中国移动通信集团福建有限公司 共享单车的管理方法及系统
CN114116200B (zh) * 2021-10-27 2024-04-05 北京百度网讯科技有限公司 资源共享方法、服务创建方法、装置和电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101754316A (zh) * 2008-12-12 2010-06-23 上海电机学院 基于最大化网络生命周期的QoS节能路由方法
CN101800913A (zh) * 2009-02-11 2010-08-11 中兴通讯股份有限公司 自动交换光网络复用段的保护及恢复的实现方法
CN102136865A (zh) * 2010-08-09 2011-07-27 华为技术有限公司 业务恢复方法、系统和节点设备
CN102333250A (zh) * 2011-10-26 2012-01-25 西安电子科技大学 实现光片上网络共享路径传输的低阻塞通信方法及路由器
EP2782373A2 (fr) * 2013-03-21 2014-09-24 Panasonic Corporation Appareil de radiocommunication

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6735390B1 (en) * 2000-10-31 2004-05-11 Lucent Technologies Inc. Method and apparatus for terminating optical links in an optical network
CN100490390C (zh) * 2006-01-10 2009-05-20 华为技术有限公司 业务故障恢复方法
CN101471693B (zh) * 2007-12-27 2013-04-17 华为技术有限公司 一种实现共享网格保护的方法和装置
CN101232453A (zh) * 2008-01-11 2008-07-30 北京邮电大学 T-mpls网络中快速寻找路径的重路由方法
CN101610203A (zh) * 2008-06-16 2009-12-23 华为技术有限公司 实现组播重路由的方法、装置及系统
CN101309525B (zh) * 2008-06-30 2011-03-16 中兴通讯股份有限公司 一种自动交换光网络中依据故障定位的路由恢复方法
CN101420331A (zh) * 2008-12-12 2009-04-29 北京邮电大学 一种t-mpls网络中的超长连接快速故障定位方法
US8750126B2 (en) * 2009-10-16 2014-06-10 Tekelec, Inc. Methods, systems, and computer readable media for multi-interface monitoring and correlation of diameter signaling information
CN102098591B (zh) * 2009-12-11 2013-08-21 中兴通讯股份有限公司 一种ason中资源共享的方法和业务节点
CN102143065B (zh) * 2011-02-09 2014-02-19 华为技术有限公司 一种故障保护方法及设备
CN102164051B (zh) * 2011-05-18 2013-11-06 西安交通大学 面向业务的故障检测与定位方法
EP2953294B1 (fr) * 2013-02-27 2017-03-29 Huawei Technologies Co., Ltd. Procédé, système, et noeud pour une commutation de protection

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101754316A (zh) * 2008-12-12 2010-06-23 上海电机学院 基于最大化网络生命周期的QoS节能路由方法
CN101800913A (zh) * 2009-02-11 2010-08-11 中兴通讯股份有限公司 自动交换光网络复用段的保护及恢复的实现方法
CN102136865A (zh) * 2010-08-09 2011-07-27 华为技术有限公司 业务恢复方法、系统和节点设备
CN102333250A (zh) * 2011-10-26 2012-01-25 西安电子科技大学 实现光片上网络共享路径传输的低阻塞通信方法及路由器
EP2782373A2 (fr) * 2013-03-21 2014-09-24 Panasonic Corporation Appareil de radiocommunication

Also Published As

Publication number Publication date
CN109644122A (zh) 2019-04-16
CN109644122B (zh) 2020-12-15
CN112803995A (zh) 2021-05-14
CN112803995B (zh) 2022-07-19

Similar Documents

Publication Publication Date Title
JP4960443B2 (ja) 複数ドメインルート計算の方法とシステム
EP2522104B1 (fr) Renvoi d'informations à élément de calcul de trajet
US8885460B2 (en) Technique for determining whether to reestablish fast rerouted primary tunnels based on backup tunnel path quality feedback
EP1974226B1 (fr) Protection dynamique contre une défaillance d'un noeud de tête de réseau d'un ou de plusieurs TE-LSPS
US8693349B2 (en) Methods for establishing a traffic connection and an associated monitoring connection
EP3055948B1 (fr) Routage de services point à multipoint dans un réseau multi-domaines
CN104718732B (zh) 用于为在通信网络的两个节点之间建立路径而交换信息的方法
EP1056234A2 (fr) Système et procédé pour la commutation pour protection d'un réseau en anneau à protocole internet
US20130232193A1 (en) Control-Plane Interface Between Layers in a Multilayer Network
WO2008098451A1 (fr) Procédé d'établissement de tunnel, dispositif de noeud de réseau et système de réseau
WO2009043256A1 (fr) Procédé, système et dispositif d'obtention de trajets à commutation par étiquette
EP2658177B1 (fr) Procédé de détection de défauts de tunnel et noeud d'ingénierie de trafic
WO2008098452A1 (fr) Procédé, système et dispositif de réseau pour le calcul de trajet entre systèmes autonomes
EP2997700B1 (fr) Procede pour configuration d'etat de reseau assuree et retour en arriere dans des reseaux a paquet d'etat de liaison
WO2018053747A1 (fr) Procédé de partage de ressources, nœud de réseau et appareil associé
WO2015024440A1 (fr) Procédé et système d'obtention de la valeur de surdébit de liaison d'une liaison ip
WO2008148315A1 (fr) Procédé et système servant à établir un chemin de service, et dispositif de nœud
EP3419228B1 (fr) Procédé, dispositif de noeud et système d'établissement de chemin de service
WO2008040254A1 (fr) Procédé de traitement destiné aux informations de liaison d'ingénierie de trafic
CN112154628B (zh) 拆除经过通信网络的标签交换路径
JP2009290589A (ja) 通信システム、ルータ及び通信経路の変更方法
US20160315854A1 (en) System and method of signaling protection path bindings

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16916486

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16916486

Country of ref document: EP

Kind code of ref document: A1