CN109644122A - Resource share method, network node and relevant device - Google Patents

Resource share method, network node and relevant device Download PDF

Info

Publication number
CN109644122A
CN109644122A CN201680088411.8A CN201680088411A CN109644122A CN 109644122 A CN109644122 A CN 109644122A CN 201680088411 A CN201680088411 A CN 201680088411A CN 109644122 A CN109644122 A CN 109644122A
Authority
CN
China
Prior art keywords
node
link circuit
resource
link
circuit resource
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
CN201680088411.8A
Other languages
Chinese (zh)
Other versions
CN109644122B (en
Inventor
张弦
冯皓宇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202011351939.4A priority Critical patent/CN112803995B/en
Publication of CN109644122A publication Critical patent/CN109644122A/en
Application granted granted Critical
Publication of CN109644122B publication Critical patent/CN109644122B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B10/00Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/07Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems
    • H04B10/075Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal
    • H04B10/079Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal using measurements of the data signal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B10/00Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/07Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems
    • H04B10/075Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using an in-service signal
    • H04B10/079Arrangements 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/0793Network aspects, e.g. central monitoring of transmission parameters
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00Arrangements for synchronising receiver with transmitter
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/0001Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062Network aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/0001Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062Network aspects
    • H04Q2011/0086Network resource allocation, dimensioning or optimisation

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

This application discloses a kind of resource share method, network node and relevant devices; after in a certain business, it breaks down because of operating path then transmits data using Protection path; it is whether faulty to relative link by each node on operating path; judged; and without failure link circuit resource is temporarily released by each node; it is used to business other in network, thus on the basis of ensuring to improve service success rate, while improving the utilization rate of Internet resources.

Description

Resource share method, network node and relevant device Technical field
The present invention relates to technical field of optical network communication, more specifically to a kind of resource share method, network node and equipment.
Background technique
Mainly comprising management plane, data plane (transport plane) and control plane in current ASON (Automatically Switched Optical Network, automatically switching optical networks);Wherein, framework and relevant communication protocol that function provided by plane and the control plane is defined by relevant International Standards Organization is controlled to support and realize.
The current main network usage that ASON is measured by service success rate, the service success rate refer to successful by network receives and carries business number in service request sum.But during measuring the network usage of ASON, it is also necessary to consider the SLA (Service levelAgreement, professional skill agreement) of network, and SLA is usually embodied by establishing different protection mechanisms for business.Currently in order to guaranteeing that business can quickly be restored from network failure, can be protected using 1+1 protection or 1:1.
Wherein, 1+1 protection, which refers to, establishes two service paths for a business; business datum is transmitted from this two service paths simultaneously, and when by two service paths by the business data transmission to destination node, destination node then selects one to receive business datum from two service paths;1:1 protection, which then refers to, establishes the operating path for being used for transmission business datum for business, and one for only in working path failure for the Protection path of bearer service data.
It can be seen from the above, used protection mechanism is needed using additional Internet resources to ensure that business can quickly be restored from network failure.Obviously this with improve network usage there are contradictions, especially network load than it is heavier in the case where, the mode of the prior art cannot be considered in terms of service success rate and network resource utilization.
Summary of the invention
The embodiment of the present application provides a kind of resource share method, network node and relevant device, to solve the problem of that the prior art cannot be considered in terms of service success rate and network resource utilization during carrying out business data transmission.
To achieve the above object, this application provides following technical solutions:
The application is in a first aspect, disclose a kind of resource share method, comprising:
Business source node executes resource status and updates judgement after receiving working path failure message, the resource updates be judged as judge link circuit resource between the business source node and downstream neighbor whether fault-free;
If the link circuit resource fault-free between the business source node and the downstream neighbor, the link circuit resource state between the business source node and the downstream neighbor is updated to share;
Resource status is sent to the downstream neighbor and updates request message, and the resource status updates in request message comprising the link circuit resource status information between the business source node and the downstream neighbor.
In the first implementation that the application first aspect provides, further includes:
If the link circuit resource between the business source node and downstream neighbor is faulty, link circuit resource state is not updated, alternatively, the link circuit resource state between the business source node and downstream neighbor is updated to share.
In second of implementation that the application first aspect provides, the resource status, which updates also to carry in request message, requires the solicited message that downstream neighbor executes the resource status update judgement.
In the third implementation that the application first aspect provides, after the link circuit resource state between the business source node and downstream neighbor is updated to share, further includes:
The business source node floods to sharable link between the business source node and downstream neighbor.
In the third implementation based on above-mentioned resource share method, business source node is flooded using aforesaid way, without failure link circuit resource can temporarily be released, it is used to business other in network, thus on the basis of ensuring to improve service success rate, while improving the utilization rate of Internet resources.
In the 4th kind of implementation that the application first aspect provides, before the link circuit resource state between the business source node and the downstream neighbor is updated to share, the method also includes:
There are preset link circuit resource configuration informations in the business source node, determine the link circuit resource configuration information as that can share, and/or, the business source node receives the link money from the downstream neighbor Source configuration instruction information, the link circuit resource configuration instruction information instruction can be shared.
The 4th kind of implementation based on resource share method disclosed above, the condition or link circuit resource configuration whether relative link can be shared are preset to business source node, increase the condition whether to flood, can further make the more diversification that whether flooded in resource-sharing.
In the fifth procedure that the application first aspect provides, further includes: the condition that floods is set;
The condition of flooding includes the link between flooding any sharable node to other nodes being located in same routed domain, alternatively, to priority any sharable node is flooded lower than the node of other operating paths of the operating path between one or both of link combination;
Correspondingly, it is described sharable link flood include:
It floods according to the condition that floods to sharable link.
The 5th kind of implementation based on resource share method disclosed above, is flooded based on the set condition of flooding, improves the precision to flood.
In the 6th kind of mode that the application first aspect provides, further includes:
The second feedback message that business purpose node is sent by signaling method is received, includes the complete link circuit resource status information of the operating path in second feedback message;
The complete link circuit resource status information refers to the link circuit resource status information between each node for constituting the operating path.
In the 7th kind of mode that the application first aspect provides, further includes:
It receives the corresponding node of other business and sends notice message, and mark the link circuit resource between respective nodes occupied based on the notice message;
Wherein, the information that the sharable link circuit resource between the arbitrary node in the operating path carried in the notice message is occupied by the corresponding node of other business.
In the 8th kind of mode that the application first aspect provides, further includes:
After receiving working service fault recovery message, inquire in sharable link circuit resource with the presence or absence of the link circuit resource not used by other business;
If not used by other business all, directly retracted by Protection path to former operating path;
If part is not used by other business, on the case where meeting business game, retracted by Protection path into the sharable link circuit resource not used by other business partially, new operating path is constituted by the former operating path of part Protection path and part;
If all being used by other business, in the case where subscriber policy allows, downgrade processing is carried out to former business, and discharge all resources, re-establish new operating path;
Or; it is partly or entirely occupied by the low business of priority when inquiring sharable link circuit resource; the sharable link circuit resource of the former business of cross-reference in the operating path of the low business of the priority is then disconnected, and is directly retracted from Protection path into former operating path.
Based on resource share method disclosed above, during former business retracts, using the 8th kind of mode disclosed above, former business all rollback or partial rollback can be instructed, or re-establish operating path, improve the efficiency of rollback.
The application second aspect discloses a kind of network node, comprising:
First judgment module, for network node after receiving working path failure message, execute resource status and update judgement, the resource updates be judged as judge link circuit resource between the network node and the downstream neighbor of the business source node whether fault-free;
Link circuit resource state between the network node and the downstream neighbor is updated to share by first update module when for link circuit resource fault-free between the network node and the downstream neighbor;
First sending module updates request message for sending resource status to the downstream neighbor, and the resource status updates in request message comprising the link circuit resource status information between the network node and the downstream neighbor.
In the first implementation that the application second aspect provides, the first judgment module is also used to:
If the link circuit resource between the network node and the downstream neighbor is faulty, link circuit resource state is not updated;
First update module is also used to link circuit resource between the network node and the downstream neighbor in the event of failure, the link circuit resource state between the network node and downstream neighbor is updated to share.
In second of implementation that the application second aspect provides, further includes:
First flood module, for being flooded after being updated to share by the link circuit resource state between the network node and the downstream neighbor to link sharable between the network node and the downstream neighbor.
In the third implementation that the application second aspect provides, further includes:
First determining module, for before the link circuit resource state between the network node and the downstream neighbor is updated to share, preset link circuit resource configuration information present in the network node is confirmed, determines that the link circuit resource configuration information is that can share;
And/or
First receiving module, for before the link circuit resource state between the network node and the downstream neighbor is updated to share, the link circuit resource configuration instruction information from the downstream neighbor is received, the link circuit resource configuration instruction information instruction can be shared.
In the 4th kind of implementation that the application second aspect provides, first flood module, the link between any sharable node that is also used to flood according to the condition of flooding of setting;
The condition of flooding includes the link to be flooded between any sharable node to other nodes being located in same routed domain, alternatively, the combination of one or both of link between any sharable node that floods to priority lower than the node of other operating paths of the operating path.
In the 5th kind of implementation that the application second aspect provides, first receiving module is also used to receive the second feedback message that business purpose node is sent by signaling method, includes the link circuit resource status information of the operating path in second feedback message;The link circuit resource status information refers to the link circuit resource status information between each node for constituting the operating path.
In the 6th kind of implementation that the application second aspect provides, further includes: first receiving module is also used to, and is received the corresponding node of other business and is sent notice message, and marks the link circuit resource between respective nodes occupied based on the notice message;
Wherein, the information that the sharable link circuit resource between the arbitrary node in the operating path carried in the notice message is occupied by the corresponding node of other business.
In the 7th kind of implementation that the application second aspect provides, further include: rollback module, for after the network node receives working service fault recovery message, inquiring in sharable link circuit resource with the presence or absence of the link circuit resource not used by other business;If not used by other business all, directly retracted by Protection path to former operating path;If part is not used by other business, on the case where meeting business game, retracted by Protection path into the sharable link circuit resource not used by other business partially, new operating path is constituted by the former operating path of part Protection path and part;If all being used by other business, in the case where subscriber policy allows, downgrade processing is carried out to former business, and discharge all resources, re-establish new operating path;
Alternatively,
The rollback module; it is also used to partly or entirely be occupied by the low business of priority when the network node inquires sharable link circuit resource; the sharable link circuit resource of the former business of cross-reference in the operating path of the low business of the priority is then disconnected, and is directly retracted from Protection path into former operating path.
The application third method discloses a kind of network node, comprising: first memory, and the first processor being connected with the memory;
The first memory executes the operating process of resource-sharing for storing network node;
The first processor, for executing the operating process of the resource-sharing of the network node, the operating process of the resource-sharing includes: the network node after receiving working path failure message, execute resource status and update judgement, the resource updates be judged as judge link circuit resource between the network node and the downstream neighbor of the network node whether fault-free;
If the link circuit resource fault-free between the network node and the downstream neighbor, the link circuit resource state between the network node and the downstream neighbor is updated to share;
Resource status is sent to the downstream neighbor and updates request message, and the resource status updates in request message comprising the link circuit resource status information between the network node and the downstream neighbor.
The application fourth aspect discloses a kind of resource share method, comprising:
Intermediate node receives after the resource status update request message that upstream neighbor node is sent, execute resource status and update judgement, the resource status update the link circuit resource that is judged as judge between the intermediate node and the downstream neighbor of the intermediate node whether fault-free;
If the link circuit resource fault-free between the intermediate node and the downstream neighbor, the link circuit resource state between the intermediate node and the downstream neighbor is updated to share;
The resource status is sent to the downstream neighbor and updates request message, and the resource status updates in request message comprising the link circuit resource status information between the intermediate node and the downstream neighbor;
The first feedback message is sent to the upstream neighbor node, includes: that the instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message.
In the first implementation that the application fourth aspect provides, further includes:
If the link circuit resource between the intermediate node and the downstream neighbor is faulty, link circuit resource state is not updated, alternatively, the link circuit resource state between the intermediate node and downstream neighbor is updated to share.
In second of implementation that the application fourth aspect provides, the resource status, which updates also to carry in request message, requires the solicited message that downstream neighbor executes the resource status update judgement.
In the third implementation that the application fourth aspect provides, further includes:
It floods to link sharable between the upstream neighbor node and the intermediate node, and floods to link sharable between the intermediate node and downstream neighbor.
It can specifically use: after the first feedback message that the intermediate node receives downstream neighbor transmission, the resource status that the upstream neighbor node is sent is updated in request message, sharable link floods between the upstream neighbor node of acquisition and the intermediate node, and floods to link sharable between the intermediate node and downstream neighbor;
Or, obtain the link circuit resource status information in the resource status update request message that the upstream neighbor node is sent between the upstream neighbor node for including and intermediate node, after being confirmed as to share, then flood to link sharable between the upstream neighbor node and intermediate node;
After being updated to share by the link circuit resource state between the intermediate node and downstream neighbor, flood to link sharable between the intermediate node and downstream neighbor.
In the third implementation based on above-mentioned resource share method, intermediate node is flooded using aforesaid way, without failure link circuit resource can temporarily be released, it is used to business other in network, thus on the basis of ensuring to improve service success rate, while improving the utilization rate of Internet resources.
In the 4th kind of implementation that the application fourth aspect provides, further include: there are preset link circuit resource configuration informations in the intermediate node, determine that the link circuit resource configuration information is that can share, and/or, the intermediate node receives the link circuit resource configuration instruction information from the downstream neighbor, and the link circuit resource configuration instruction information instruction can be shared.
The 4th kind of implementation based on resource share method disclosed above, the condition or link circuit resource configuration whether relative link can be shared are preset to intermediate node, increase the condition whether to flood, can further make the more diversification that whether flooded in resource-sharing.
In the 5th kind of implementation that the application fourth aspect provides, further includes:
The confirmation message that upstream neighbor node is sent is received, judges whether the resource distribution between the intermediate node and upstream neighbor node is equal, alternatively, whether the service attribute carried is consistent;
If resource distribution is equivalent or service attribute is consistent, correct information is fed back;
If equivalent or service attribute is not inconsistent for resource distribution, feedback error information.
In the 6th kind of implementation that the application fourth aspect provides, further includes: the condition that floods is set;
The condition of flooding includes the link circuit resource status information between flooding any sharable node to other nodes being located in same routed domain, alternatively, to priority any sharable node is flooded lower than the node of other operating paths of the operating path between one or both of link circuit resource status information combination.
The 5th aspect of the application, discloses a kind of network node, comprising:
Second judgment module, after the resource status update request message for receiving upstream neighbor node transmission for network node, execute resource status and update judgement, the resource updates be judged as judge link circuit resource between the network node and downstream neighbor whether fault-free;
Link circuit resource state between the network node and the downstream neighbor is updated to share by second update module when for link circuit resource fault-free between the network node and the downstream neighbor;
Second sending module, request message is updated for sending the resource status to the downstream neighbor, the resource status updates in request message comprising the link circuit resource status information between the network node and the downstream neighbor, and the first feedback message is sent to the upstream neighbor node, it include indicating that the upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message.
Disclosed in the aspect of the application the 5th in the first implementation, second judgment module is also used to not update link circuit resource state then if it is determined that the link circuit resource between the network node and the downstream neighbor is faulty;
Second update module is also used to link circuit resource between the network node and the downstream neighbor in the event of failure, is then updated to share by the link circuit resource state between the network node and the downstream neighbor.
Disclosed in the aspect of the application the 5th in second of implementation, further includes:
Second flood module for flooding to link sharable between the upstream neighbor node and the network node, and floods to link sharable between the network node and the downstream neighbor.
Disclosed in the application fourth aspect in the third implementation, further includes:
Second determining module, for by the link circuit resource shape of the network node and the downstream neighbor Before state is updated to share, preset link circuit resource configuration information present in the network node is confirmed, determines that the link circuit resource configuration information is that can share;
And/or
Second receiving module, for before the link circuit resource state between the network node and the downstream neighbor is updated to share, the link circuit resource configuration instruction information from the downstream neighbor is received, the link circuit resource instruction information instruction can be shared.
Disclosed in the aspect of the application the 5th in the 4th kind of implementation, second judgment module is also used to receive the confirmation message of upstream neighbor node transmission, judges whether the resource distribution between the network node and upstream neighbor node is equal, alternatively, whether the service attribute carried is consistent;If resource distribution is equivalent or service attribute is consistent, correct information is fed back;If equivalent or service attribute is not inconsistent for resource distribution, feedback error information.
Disclosed in the aspect of the application the 5th in the 5th kind of implementation, second flood module is also used to flood according to the condition execution that floods;
The condition of flooding includes the link between flooding any sharable node to other nodes being located in same routed domain, alternatively, to priority any sharable node is flooded lower than the node of other operating paths of the operating path between one or both of link combination.
The 6th aspect of the application, discloses a kind of network node, comprising: second memory, and the second processor being connected with the second memory;
The second memory executes the operating process of resource-sharing for storing network node;
The second processor, for executing the operating process of the resource-sharing of the network node, the operating process of the resource-sharing includes: that the network node receives after the resource status that upstream neighbor node is sent updates request message, execute resource status and update judgement, the resource status update the link circuit resource that is judged as judge between network node and downstream neighbor whether fault-free;
If the link circuit resource fault-free between the network node and the downstream neighbor, the link circuit resource state between the network node and the downstream neighbor is updated to share;
The resource status is sent to the downstream neighbor and updates request message, and the resource status updates in request message comprising the link circuit resource status information between the network node and the downstream neighbor;
The first feedback message is sent to the upstream neighbor node, includes: that the instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message.
The 7th aspect of the application, discloses a kind of resource share method, comprising:
Business purpose node receives the resource status that upstream neighbor node is sent and updates request message, it obtains in the resource status update message, link circuit resource status information between the upstream neighbor node for including and the business purpose node confirms whether the link circuit resource status information between the upstream neighbor node and the business purpose node is that can share;
After confirming the link circuit resource status information between the upstream neighbor node and the business purpose node for that can share, then flood to sharable link between the upstream neighbor node and the business purpose node;
The first feedback message is sent to the upstream neighbor node, includes: that the instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message.
Disclosed in the aspect of the application the 7th in the first implementation, to before sharable link floods between the upstream neighbor node and the business purpose node, further includes:
There are preset link circuit resource configuration information in the business purpose node, determine that the link circuit resource configuration information is that can share.
The first implementation based on resource share method disclosed above, the condition or link circuit resource configuration whether relative link can be shared are preset to business purpose node, increase the condition whether to flood, can further make the more diversification that whether flooded in resource-sharing.
Disclosed in the aspect of the application the 7th in second of implementation, further includes:
The confirmation message that upstream neighbor node is sent is received, judges whether the resource distribution between the business purpose node and upstream neighbor node is equal, alternatively, whether the service attribute carried is consistent;
If resource distribution is equivalent or service attribute is consistent, correct information is fed back;
If equivalent or service attribute is not inconsistent for resource distribution, feedback error information.
In the application eighth aspect, a kind of network node is disclosed, comprising:
Third judgment module receives the resource status that upstream neighbor node is sent for network node and updates request message, obtains in the resource status update message, the link circuit resource status information between the upstream neighbor node for including and the network node;
The third flood module, for being flooded after confirming the link circuit resource status information between the upstream neighbor node and the network for that can share to link sharable between the upstream neighbor node and the network node;
Third sending module includes: that the instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message for sending the first feedback message to the upstream neighbor node.
Disclosed in the application eighth aspect in the first implementation, further include: third determining module, for before flooding to link sharable between the upstream neighbor node and the network node, to there are preset link circuit resource configuration informations to confirm in the network node, determine that the link circuit resource configuration information is that can share.
Disclosed in the application eighth aspect in second of implementation, the third judgment module is also used to receive the confirmation message of upstream neighbor node transmission, judges whether the resource distribution between the network node and upstream neighbor node is equal, alternatively, whether the service attribute carried is consistent;If resource distribution is equivalent or service attribute is consistent, correct information is fed back;If equivalent or service attribute is not inconsistent for resource distribution, feedback error information.
The 9th aspect of the application, discloses a kind of network node, comprising: third memory, and the third processor being connected with the third memory;
The third memory executes the operating process of resource-sharing for storing network node;
The third processor, for executing the operating process of the resource-sharing of the network node, the operating process of the resource-sharing includes: that the network node receives the resource status update request message that upstream neighbor node is sent, it obtains in the resource status update message, link circuit resource status information between the upstream neighbor node for including and the network node confirms whether the link circuit resource status information between the upstream neighbor node and the network node is that can share;
After confirming the link circuit resource status information between the upstream neighbor node and the network node for that can share, then flood to link sharable between the upstream neighbor node and the network node;
The first feedback message is sent to the upstream neighbor node, includes: that the instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message.
The tenth aspect of the application, disclose a kind of network resources locating system characterized by comprising network node disclosed in the application second aspect and the third aspect, network node disclosed in network node and the application eighth aspect disclosed in the 5th aspect of the application and the 6th aspect and the 9th aspect;
The operating path of business is constituted between above-mentioned network node.
On the one hand the application the tenth, discloses a kind of resource share method, comprising:
Business source node reports the working path failure message to Centralized Controller after receiving working path failure message;
The resource for receiving the Centralized Controller feedback can share message, and it includes the link circuit resource status information in the operating path between adjacent node that the resource, which can share message,;
Judge whether the link circuit resource status information between the business source node and downstream neighbor is that can share according to the link circuit resource status information;
If the link circuit resource status information between the business source node and the downstream neighbor be it is sharable, the business source node floods sharable link;
The resource can be shared message and be sent to the downstream neighbor by the business source node.
In the first implementation disclosed in the tenth one side of the application, the resource can be shared message and be sent to the downstream neighbor by the business source node, comprising:
Resource described in the service source knot removal can share information relevant to the business source node in message, and the resource after deleting can be shared message and be sent to the downstream neighbor.
It is sent to downstream neighbor by the way that the resource after deleting can be shared message, the efficiency that downstream neighbor searches information relevant to itself can be improved.
In second of implementation disclosed in the tenth one side of the application, further includes:
If the link circuit resource status information between the business source node and the downstream neighbor be it is not sharable, the business source node, which does not execute, to flood, and the resource can be shared message and be sent to the downstream neighbor.
In the third implementation disclosed in the tenth one side of the application, when the downstream neighbor is intermediate node, the intermediate node receives and the resource for judging that upstream neighbor node is sent can be shared in message, the intermediate node for including is with the link circuit resource status information between the upstream neighbor node and the intermediate node and the downstream neighbor with the presence or absence of sharable link circuit resource status information;
If there are sharable link circuit resource status information in the link circuit resource status information between the intermediate node and the upstream neighbor node and the intermediate node and the downstream neighbor, the intermediate node floods sharable link;
The resource can be shared message and be sent to the downstream neighbor by the intermediate node.
In the 4th kind of implementation disclosed in the tenth one side of the application, the resource can be shared message and be sent to the downstream neighbor by the intermediate node, comprising:
The intermediate node, which deletes the resource that the upstream neighbor node is sent, to be shared in message, information relevant to the intermediate node, and the resource after deleting can be shared message and be sent to the downstream neighbor.
It is sent to downstream neighbor by the way that the resource after deleting can be shared message, the efficiency that downstream neighbor searches information relevant to itself can be improved.
In the 5th kind of implementation disclosed in the tenth one side of the application, further includes:
If the intermediate node and the upstream neighbor node, or the link circuit resource status information between the intermediate node and the downstream neighbor is not sharable, then the intermediate node, which does not execute, floods, and the resource that the upstream neighbor node is sent can be shared message and be sent to the downstream neighbor.
In the 6th kind of implementation disclosed in the tenth one side of the application, when the downstream neighbor is business purpose node, the business purpose node receives and judges in the resource-sharing message of upstream neighbor node transmission, and whether the link circuit resource status information between the business purpose node for including and the upstream neighbor node is that can share;
If the link circuit resource status information between the business purpose node and the upstream neighbor node be it is sharable, the business purpose node floods sharable link.
In 7th kind of implementation disclosed in the tenth one side of the application, further includes:
If the link circuit resource status information between the business purpose node and the upstream neighbor node be not it is sharable, the business purpose node, which does not execute, to flood.
In the 8th kind of implementation disclosed in the tenth one side of the application, the resource, which can be shared, also carries the condition of flooding in message;
The condition of flooding includes the link between flooding any sharable node to other nodes being located in same routed domain, alternatively, to priority any sharable node is flooded lower than the node of other operating paths of the operating path between one or both of link combination.
In the 9th kind of implementation disclosed in the tenth one side of the application, after business source node, which receives working path failure, restores message, further includes:
Working path failure recovery message is sent to Centralized Controller by the business source node;
It receives the Centralized Controller and the control information that message evaluation is restored to the complexity generation of former operating path is restored based on the working path failure;
Rollback operation is carried out according to the control information;
The control information includes:
If complexity is lower than default complexity, according in former operating path can the state that is partially occupied of shared link resource, control the business and retracted by Protection path into the sharable link circuit resource not used by other business partially;Alternatively, according in former operating path can the state that is occupied by the low service part of priority or all of shared link resource, control the business and force to retract into former operating path;
If complexity is higher than default complexity, recalculates an operating path and feed back the business source node.
The 12nd aspect of the application, discloses a kind of network resources locating system, comprising: Centralized Controller, business source node, intermediate node and business purpose node;
The business source node, the intermediate node and the business purpose node constitute the operating path of business;
The Centralized Controller concentration is made whether sharable judgement to the link between the business source node, the intermediate node and the business purpose node.
The technical solution of above-mentioned carry out resource-sharing disclosed in the present application; after in a certain business, it breaks down because of operating path then transmits data using Protection path; it is whether faulty to relative link by each node on operating path; judged; and without failure link circuit resource is temporarily released by each node; it is used to business other in network, thus on the basis of ensuring to improve service success rate, while improving the utilization rate of Internet resources.
Detailed description of the invention
In order to illustrate more clearly of the application or technical solution in the prior art, below will pair or attached drawing needed to be used in the description of the prior art be briefly described, apparently, the accompanying drawings in the following description is only some examples of the invention, for those of ordinary skill in the art, without creative efforts, it is also possible to obtain other drawings based on these drawings.
Fig. 1 is the relevant information schematic diagram of network topology structure disclosed in the embodiment of the present application one and business one;
Fig. 2 is a kind of flow diagram of resource share method disclosed in the embodiment of the present application one;
Fig. 3 is a kind of flow diagram of resource share method disclosed in the embodiment of the present application two;
Fig. 4 is the relevant information schematic diagram of a kind of network topology structure disclosed in the embodiment of the present application three and business two;
Fig. 5 is a kind of flow diagram of resource share method disclosed in the embodiment of the present application three;
Fig. 6 is the relevant information schematic diagram of a kind of network topology structure disclosed in the embodiment of the present application four and business three;
Fig. 7 is a kind of structural schematic diagram of network node disclosed in the embodiment of the present application five;
Fig. 8 is the structural schematic diagram of another kind network node disclosed in the embodiment of the present application five;
Fig. 9 is the structural schematic diagram of another kind network node disclosed in the embodiment of the present application five;
Figure 10 is the hardware structural diagram of each node disclosed in the embodiment of the present application five;
Figure 11 is a kind of structural schematic diagram of network resources locating system disclosed in the embodiment of the present application five;
Figure 12 is the structural schematic diagram of another kind network resources locating system disclosed in the embodiment of the present application five.
Specific embodiment
The following are the full name of the english abbreviation arrived used in the application specific embodiment and Chinese to explain:
ITU-T:International Telecommunication Union-Telecommunication Standardization Sector, International Telecommunication Union-telecommunication standardization sector;
ASON:Automatically Switched Optical Network, automatically switching optical networks;
IETF:Internet Engineering TaskForce, internet engineering task group;
GMPLS:Generalized Multi-Protocol Label Switching, extension multi protocol label exchange;
OSPF-TE:Open Shortest Path First-Traffic Engineering, the ospf of Traffic Engineering extensions;
RSVP-TE:Resource ReserVation Protocol-Traffic Engineering, the Resource Reservation Protocol of Traffic Engineering extensions;
PCE:Path Computation Element, path-calculating element;
PCC:Path Computation Client path computing client;
PCECP:Path Computation Element Communication Protocol path computation element communication protocol, for being communicated between PCE and PCC;
LSP:Label SwitchedPath, label switched path;
SDN:Software DefinedNetwork, software defined network.
Below in conjunction with the attached drawing in the application specific embodiment, the technical solution in the application is carried out clear Chu is fully described by, it is clear that described embodiment is only a part of example of the application, rather than whole examples.Based on the embodiment in the application, every other example obtained by those of ordinary skill in the art without making creative efforts be shall fall in the protection scope of this application.
It can be seen from background technology that, in the prior art, when some link in a vocational work path breaks down, in order to ensure business can quickly be restored from network failure, the protection mechanism of use is needed using additional Internet resources, although can be improved service success rate in this way, but occupy additional Internet resources, and other normal paths in the operating path where the link to break down are also because of exclusive reason, it can not be used by other business, especially network load than it is heavier in the case where, the mode of the prior art more cannot be considered in terms of service success rate and network resource utilization.
As a result, this application discloses a kind of technical solution of resource-sharing, which refers to the general designation that can be used in the entity of business transferring data in network.Include: link circuit resource and node resource etc., wherein link circuit resource is one kind of resource, refers to using actual physics carrier (such as: an optical fiber) customer data moving another position from a position;Node resource refers to that business can be carried out necessary processing, such as: the signal type of client is converted into optical signal from electric signal;Alternatively, by business datum from an ingress switch to another outlet etc..Specific nodal function depends on specific functional requirement.In Resource Sharing Technology scheme disclosed in the present application; after relating generally to by the way that in a certain business, it transfers to transmit data using Protection path because operating path breaks down; link circuit resource without failure on the operating path for actually belonging to the business is temporarily released and is used to business other in network; thus on the basis of ensuring to improve service success rate, while improving the utilization rate of Internet resources.
Specific implementation process is described in detail by specific embodiment disclosed in the present application.
Embodiment one
As shown in Figure 1, for the relevant information schematic diagram of network topology structure disclosed in the embodiment of the present invention one and business one (LSP1);
The business source node of the business one (LSP1) is A, and business purpose node is B, and the link bandwidth between node and node is 1, therefore the business one can be referred to as LSP1 (A, B, 1)
The protection type of the service path is 1:1 protection, wherein operating path are as follows: A-E-F-B (LSP1_W), Protection path are as follows: A-G-H-I-J-B (LSP1_P).In the present embodiment, when one or more links in the operating path LSP1_W of business one break down, need to carry out pretection switch, i.e., business one from LSP1_W is switched to LSP1_P.And, it is assumed that there is no the links of failure can be used as shared resource to other business use in network for other in operating path LSP1_W.In this example, it is assumed that the link F-B between node F and node B breaks down.For LSP1 (A, B, 1) other trouble-free link A-E in operating path LSP1_W, link E-F are shared, link A-E and link E-F is specifically executed using resource share method disclosed in the present application and is shared, shown in the specific following example of shared procedure;
Example one
In this example one, it is as shown in Figure 2 that shared specific flow chart is executed to link A-E and link E-F:
S100: business source node A after receiving working path failure message, executes resource status and updates judgement, the resource updates be judged as judge link circuit resource between present node and downstream neighbor whether fault-free;
Link A-E fault-free between S101: business source node A and intermediate node E (downstream neighbor of business source node A), then it is that can share that business source node A, which updates the link circuit resource state of respective links A-E in the operating path,;
S102: business source node A, which sends first resource state to intermediate node E, updates request message;
In the present embodiment step S102, the first resource state update request message in include link A-E link circuit resource status information, because link A-E link circuit resource be it is sharable, then link A-E link circuit resource status information indicate link A-E can share;
In the example disclosed in the present application, first resource state updates request, it is preferred that it is required that downstream neighbor executes the solicited message that resource status updates judgement, can be indicated, can also independently be carried by link circuit resource status information;
S103: intermediate node E, which receives the first resource state, updates request message, executes the link E-F between intermediate node E and intermediate node F (downstream neighbor of intermediate node E), and the whether trouble-free resource status of link circuit resource updates judgement;
It is in the example disclosed in the present application, after the first resource state that intermediate node E receives business source node A transmission updates request message, i.e. execution resource updates judgement;
S104: the link circuit resource state of the link E-F between intermediate node E and intermediate node F is fault-free, then it is that can share that intermediate node E, which updates the link circuit resource state of respective links E-F in the operating path,;
S105: intermediate node E, which sends Secondary resource state to intermediate node F, updates request message;
In the step S105 of the present embodiment, it includes link E-F which, which updates request message, Link circuit resource status information, because link E-F link circuit resource state be it is sharable, then link E-F link circuit resource status information indicate link E-F can share;
S106: intermediate node F, which receives the Secondary resource state, updates request message, and executes the link F-B between intermediate node F and business purpose node B (downstream neighbor of intermediate node F), and the whether trouble-free resource status of link circuit resource updates judgement;
The link state of link F-B between S107: intermediate node F and business purpose node B is to break down, then intermediate node F sends information resources state update request message to business purpose node B;
In the step S108 of the present embodiment, which updates the link circuit resource status information in request message comprising link F-B, and because link F-B breaks down, then the link circuit resource status information of link F-B indicates that link F-B is faulty;
S108: the business purpose Node-B receiver information resources state updates request message, judges that the information resources state updates the link circuit resource status information for the link F-B for including in request message, if indicates that link F-B can share;
In the present embodiment step S108, downstream neighbor is required to execute the solicited message that resource status updates judgement although the information resources state of business purpose Node-B receiver updates to may include in request message, but, because business purpose node B is the last one node on the operating path, therefore, business purpose node B does not need the whether sharable judgement of the link circuit resource carried out itself between downstream neighbor, it is only necessary to be made whether the judgement to flood;
S109: link F-B link circuit resource status information indicates that link F-B is faulty, and for business purpose node B without flooding, which sends the first feedback message to intermediate node F (upstream neighbor node of business purpose node B);
In the present embodiment step S111, because based on the present embodiment it is assumed that the link circuit resource status information of link F-B indicates that link F-B is faulty.Therefore, after the judgement by step S108, confirmation link F-B is faulty, cannot share, then not need to flood.Wherein, include: in first feedback message instruction upstream neighbor node flood it is relevant to itself can shared link resource distribution instruction information;
S110: intermediate node F after receiving first feedback message, updates the sharable link E-F obtained in request message to the Secondary resource state having received and floods;
Because F-B link in the present embodiment is faulty, therefore during the present embodiment step S110 execution floods, intermediate node F is after receiving the first feedback message, relative to share chain to known Road E-F floods, and realizes shared in routed domain to link E-F.
S111: intermediate node F sends the first feedback message to intermediate node E (upstream neighbor node of intermediate node F), include: in first feedback message indicate upstream neighbor node flood it is relevant to itself can shared link instruction information;
S112: intermediate node E after receiving first feedback message, the sharable link A-E obtained in request message is updated to the first resource state having received, and flood via the sharable link E-F that itself judgement obtains;
In the present embodiment step S116, sharable link E-F is that intermediate node E is determined after executing step S103 and step S104;Intermediate node E is then after receiving the first feedback message, and to known, relative sharable link E-F and link A-E floods, and realizes shared in routed domain to link E-F and link A-E;
It should be noted that can be flooded based on ospf protocol, can also be flooded based on other agreements;
S113: intermediate node E sends the first feedback message to business source node A (upstream neighbor node of intermediate node E), include: in first feedback message indicate upstream neighbor node flood it is relevant to itself can shared link instruction information;
S114: business source node A after receiving first feedback message, to flooding via itself obtained sharable link A-E of judgement.
In the present embodiment step S114, sharable link A-E is that business source node A is determined after executing step S101.With above-mentioned, business source node A is after receiving the first feedback message, and to known, relative sharable link A-E floods, and realizes shared in routed domain to link A-E.
For in above-mentioned the present embodiment assume LSP1 operating path LSP1_W in link F-B it is faulty after, using Modes of Sharing Resources disclosed in the present application, by on the operating path other do not have faulty link A-E, link E-F is updated to shared, it will be relevant to itself by each node, do not have faulty link to flood in the whole network, these are updated to sharable link and can be used to realize in informing network other nodes.
That is; a certain business its because in operating path link break down; then after transmitting data using Protection path; link circuit resource without failure on the operating path for actually belonging to the business is temporarily discharged; it is used to business other in network; to on the basis of ensuring to improve service success rate The utilization rate of Internet resources is improved simultaneously.
Example two
In this example two, link A-E and link E-F are executed in shared process and example one the difference is that:
Each node is after confirmation can be shared with each autocorrelative link, directly to respectively sharable link floods between downstream neighbor, after being performed both by resource updates judgement without each node in entire operating path, and after upstream neighbor node receives the feedback message that downstream neighbor is sent, then is executed and flooded based on the feedback message;
That is, being based on above-mentioned example one, in this example two, after executing step S101, business source node A is updated to sharable link A-E to link circuit resource state and floods business source node A;
In this example two, intermediate node E is then after executing step S104, and intermediate node E updates in request message the first resource state having received, the sharable link A-E of acquisition, and floods via the sharable link E-F that itself judgement obtains;
In this example two, intermediate node F is then executing step S107, after confirming that the link circuit resource of the link F-B between intermediate node F and business purpose node B is faulty, intermediate node F updates in request message the Secondary resource state having received, and the sharable link E-F of acquisition floods;
In this example two, further, after there is no problem for each node confirmation a certain link relevant to itself, it can flood.
For example, when the intermediate node E first resource state for receiving business source node A transmission updates request message, and parsing obtains after indicating the sharable A-E link circuit resource status information of link A-E, i.e., floods to the sharable link A-E.
It is executed while this floods in intermediate node E or later, judge again the link E-F between intermediate node E and intermediate node F link circuit resource whether fault-free, and after the link circuit resource for obtaining link E-F is fault-free, flood to sharable link E-F is updated to.
That is, in this example two, intermediate node on operating path can obtain the sharable link circuit resource of upstream neighbor node and itself, and judge that itself link circuit resource with downstream neighbor for that can share, later, is once flooded;Can also be with, it after the sharable link circuit resource status information of expression link for receiving upstream neighbor node transmission, is first once flooded, is judging itself link circuit resource with downstream neighbor can to share and then once be flooded.
The opportunity to flood is executed by each node disclosed in above-mentioned example two, also can by each node obtain or confirm it is relevant to itself, trouble-free link floods in the whole network, to realize that these links for being updated to share state of other nodes can be used in informing network.
Above-described embodiment is only example given by the application, does not limit the link of failure as final stage, the case where failure it is suitable for any link on operating path.In resource share method disclosed in the present application, for the business source node in operating path, concrete operations are as follows:
After business source node receives working path failure message, execute resource status and update judgement, resource updates be judged as judge link circuit resource between business source node and downstream neighbor whether fault-free;
If the link circuit resource fault-free between business source node and downstream neighbor, the link circuit resource state between business source node and downstream neighbor is updated to share;
Downstream neighbor sends resource status and updates request message, and resource status updates in request message comprising the link circuit resource status information between business source node and downstream neighbor;
In above-described embodiment disclosed in the present application, link circuit resource state whether is updated for business source node, further include, if judging, the link circuit resource obtained between business source node and downstream neighbor is faulty, link circuit resource state is not updated then, alternatively, the link circuit resource state between business source node and downstream neighbor is updated to share;
In above-described embodiment disclosed in the present application, further includes: after being updated to share by the link circuit resource state between business source node and downstream neighbor, flood to link sharable between business source node and downstream neighbor;
It in above-described embodiment disclosed in the present application, floods opportunity for different, business source node is by the way of are as follows:
The first, business source node receives the first feedback message that downstream neighbor is sent, and includes in first feedback message, and instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself;
The business source node floods to sharable link, to not sharable link then without flooding;
Second, the link circuit resource state between business source node and downstream neighbor is updated to after can sharing, and before downstream neighbor sends resource status update request message, business source node is to business Sharable link floods between source node and downstream neighbor.
For the intermediate node in operating path, concrete operations are as follows:
Intermediate node receives after the resource status that upstream neighbor node is sent updates request message, executes resource status and updates judgement, resource updates be judged as judge link circuit resource between intermediate node and downstream neighbor whether fault-free;
If the link circuit resource state between intermediate node and downstream neighbor is updated to share by the link circuit resource fault-free between intermediate node and downstream neighbor;
Downstream neighbor sends resource status and updates request message, and resource status updates in request message comprising the link circuit resource status information between intermediate node and downstream neighbor;
Upstream adjacent node sends the first feedback message, includes: that instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message.
In above-described embodiment disclosed in the present application, link circuit resource state whether is updated for intermediate node, further include, if judging, the link circuit resource between intermediate node and downstream neighbor is faulty, link circuit resource state is not updated then, alternatively, the link circuit resource state between intermediate node and downstream neighbor is updated to share;
It in above-described embodiment disclosed in the present application, further include that intermediate node floods to link sharable between upstream neighbor node and intermediate node, and floods to link sharable between intermediate node and downstream neighbor.
In above-described embodiment disclosed in the present application, flood opportunity for different, intermediate node is by the way of are as follows:
The first, intermediate node includes that instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message after the first feedback message for receiving downstream neighbor transmission;
Intermediate node updates in request message the resource status that upstream neighbor node is sent, and sharable link floods between the upstream neighbor node for including and intermediate node, and floods to link sharable between intermediate node and downstream neighbor;
To the not sharable link between upstream neighbor node and intermediate node and/or between intermediate node and downstream neighbor then without flooding;
Second, intermediate node obtains the resource status that upstream neighbor node is sent and updates in request message, link circuit resource status information between the upstream neighbor node for including and intermediate node then floods to link sharable between upstream neighbor node and intermediate node after being confirmed as to share.
Link circuit resource state between intermediate node and downstream neighbor is updated to after can sharing, and intermediate node floods to link sharable between intermediate node and downstream neighbor;
In the mode to flood at second, intermediate node can be after the link circuit resource status information between confirmation upstream neighbor node and intermediate node, based on whether sharable result, it is first once flooded or is not flooded, it is once flooded in the link resource information for judging intermediate node and downstream neighbor and then based on sharable result or is not flooded;
It can also be to obtain the link circuit resource status information of upstream neighbor node and intermediate node, and judge the link circuit resource status information of intermediate node and downstream neighbor, later, based on whether it is sharable as a result, once all flood, perhaps part floods or does not flood;
For business purpose node, concrete operations are as follows:
Business purpose node receives the resource status that upstream neighbor node is sent and updates request message, and resource status updates in request message comprising the link circuit resource status information between upstream neighbor node and business purpose node;
Business purpose node obtains the resource status that upstream neighbor node is sent and updates in request message, the link circuit resource status information between upstream neighbor node and business purpose node;
Link circuit resource status information between confirmation upstream neighbor node and business purpose node is after can sharing, then business purpose node floods to link sharable between upstream neighbor node and business purpose node;
Upstream adjacent node sends the first feedback message to business purpose node, includes: that instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message.
It disclosed in the embodiment of the present application in resource share method, further include that link circuit resource status information of the business purpose node between confirmation upstream neighbor node and business purpose node is that can not share, then without flooding;
Disclosed in the embodiment of the present application in resource share method, when business source node and intermediate node downstream neighbor send resource status and update request message, request message is updated to indicate to need downstream neighbor to execute resource status, RSVP-TE agreement can be carried out during executing the resource share method Extension increases TLV (Type-length-value) object in RSVP-TE agreement, and specific format is as follows:
Wherein, Type (16bits, TLV type);
Length (16bits, TLV length);
Flags (32bits just defines mark: U-update (resource updates judgement is done in request) at present)
The TLV can be put into LSP_REQUIRED_ATTRIBUTES object, as the instruction information for requiring downstream neighbor to do resource updates judgement.
Similarly, disclosed in the embodiment of the present application in resource share method, in business source node and intermediate node downstream neighbor, send itself and downstream neighbor shares state, or intermediate node or business purpose node are in upstream adjacent node, one or more links between feedback node share state, during executing the resource share method, RSVP-TE agreement is extended, increase in RSVP-TE agreement TLV ((Type-length-value) object indicate one or this multiple link share state, specific format is as follows:
Wherein, Type (16bits, TLV type);
Length (16bits, TLV length);
Link ID X (link identification, variable-length): can indicate the link IP address of 32bit, can also indicate node ID+link ID, specific to indicate to depend on specific Linktype.As long as can indicate unique One network link.
Status Flag (status indicator, can degree of selling of one's property): disclosed in above-mentioned the embodiment of the present application in resource share method, it is defined as following two information:
S (1bit): whether can be shared;S=1 expression can be shared, and S=0 expression can not be shared;
A (1bit): whether occupied by other business.A=1: it indicates occupied;A=1: it indicates occupied;
But two kinds of information is not limited to that for the Status Flag, other information can also be added as needed in resource share method disclosed in the embodiment of the present application.
Disclosed in the embodiment of the present application in resource share method, when business source node, intermediate node and business purpose node flood to sharable link based on ospf protocol, it needs to increase a new TLV in ospf protocol to indicate the link circuit resource status information that can be shared, the TLV format newly defined is as follows:
Wherein, Type (16bits, TLV type), for transmitting sharable link circuit resource status information;
Length (16bits, TLV length);
Value (32bits) can be used to add restrictive condition in flooding process: such as Priority (3bits), for indicating to can be used the highest priority of the sharable link circuit resource.
In conjunction with specific embodiment disclosed above, the technical solution of resource-sharing disclosed in the present application, in a certain business, it breaks down because of operating path, then after transmitting data using Protection path, itself and upstream neighbor node are directed to by each node on operating path, link circuit resource between downstream neighbor is handled, it will be on the operating path that actually belong to the business, trouble-free link circuit resource is updated to share, then it floods again, sharable link can be made temporarily to release to use to business other in network, to on the basis of ensuring to improve service success rate, the utilization rate of Internet resources is improved simultaneously.
Embodiment two
Based on a kind of resource share method disclosed in above-mentioned the embodiment of the present application, in the present embodiment, for each node, the whether sharable condition of relative link or link circuit resource configuration can be preset, i.e., shared or not sharable preset condition can be carried out by relative link being arranged to each node in advance;
In the present embodiment, in business source node and intermediate node, before link circuit resource state respectively between downstream neighbor is updated to share, further include: business source node and intermediate node are to there are preset link circuit resource configuration informations, determine that link circuit resource is configured to share, and/or business source node and intermediate node receive the link circuit resource configuration instruction information from downstream neighbor, link circuit resource configuration instruction information instruction can be shared;
Business purpose node further includes that business purpose node determines that link circuit resource configuration information can be shared to there are preset link circuit resource configuration information before flooding to link sharable between upstream neighbor node and business purpose node;
For example, link circuit resource configuration information is arranged for the link circuit resource between respective node and adjacent node on each node, which includes that link circuit resource can be shared and can not be shared with link circuit resource.
Resource allocation information is arranged for the link circuit resource between respective node and downstream neighbor in business source node.Intermediate node is directed to the setting resource allocation information of the link circuit resource between intermediate node and upstream neighbor node, downstream neighbor respectively.Resource allocation information is arranged for the link circuit resource between business purpose node and upstream neighbor node in business purpose node.If any one node is provided with link circuit resource and can not share in two neighboring node, the link circuit resource between the two nodes can not be shared.Alternatively, link circuit resource can not be shared between the two nodes if the resource allocation information being arranged on two neighboring node is inconsistent.
Preferably, disclosed in executing above-mentioned application embodiment in a kind of resource share method, after business source node receives working path failure message, execution resource status updates before judgement, it whether needs first to judge in the preset condition of business source node comprising sharable configuration, when including sharable configuration in the preset condition of business source node, then further judge whether fault-free;When including not sharable configuration in the preset condition of business source node, then directly executes downstream neighbor and send the step of resource status updates request message;
Alternatively, whether including sharable configuration in the preset condition for judging fault-free and then judging business source node;
If including sharable configuration in the preset condition of business source node, continue subsequent step;When including not sharable configuration in the preset condition of business source node, then directly executes downstream neighbor and send money Source state updates the step of request message.
Likewise, intermediate node and business purpose node will also do identical judgement before the resource status for receiving upstream neighbor node transmission updates status message, whether judge in the preset condition of itself comprising sharable configuration, or not sharable configuration.
Can also be with, in business source node and intermediate node, updating itself link circuit resource state between downstream neighbor is after can sharing, further:
Business source node and intermediate node, downstream neighbor transmission is confirmed whether that the link circuit resource state that can be carried out between node is updated to sharable confirmation message, if receiving the error message of downstream neighbor feedback, then business source node and intermediate node are again marked the link circuit resource state between node, that is, are labeled as to share;
Wherein, downstream neighbor receives the judgement carried out after confirmation message, judge whether itself resource distribution between upstream neighbor node is equal, or, whether the service attribute carried is consistent, if resource distribution is equivalent or service attribute is consistent, feeds back correct information, if equivalent or service attribute is not inconsistent for resource distribution, feedback error information;
That is, whether the link circuit resource between node can be marked as sharing, need to be confirmed via upstream neighbor node and downstream neighbor;
Specifically with the behaviour between business source node A and intermediate node E (for the downstream neighbor of business source node A) as an example, be specifically described, as shown in Figure 3:
S200: business source node A is after receiving working path failure message, it executes resource status and updates judgement, resource updates are judged as the link A-E between judgement business source node A and downstream neighbor, link circuit resource whether fault-free, if the link circuit resource fault-free of the link A-E between business source node A and intermediate node E, S201 is then executed, if the link circuit resource of the link A-E between business source node A and intermediate node E is faulty, directly execution S202;
S201: business source node A to update in the operating path corresponding A-E link circuit resource state be that can share;
S202: business source node A sends sharable A-E link circuit resource status information to intermediate node E;
S203: intermediate node E receives the sharable A-E link circuit resource status information, and judge whether the resource distribution between intermediate node E and business source node A is equal, or whether the service attribute for judging that intermediate node E and business source node A is carried is consistent, if equivalent or consistent, correct information then is fed back to business source node A, and executes S205;If not equivalent or inconsistent, to business source node A feedback error information, And execute S204;
S204: business source node A to update in the operating path corresponding A-E link circuit resource state be that can not share;
S205: business source node A, which sends resource status to intermediate node E, updates request message.
Referring to above-mentioned example one, link circuit resource status information between executing the whether more new node in resource share method disclosed in the present application, consider to execute the resource distribution between node and downstream neighbor simultaneously, link circuit resource state between label or more new node that can be more accurate, further, make the link circuit resource state between label or updated node more stable when can share.
Based on a kind of resource share method disclosed in above-mentioned the embodiment of the present application one, in the present embodiment, for each node, it can be executed and be flooded based on conventional mode, or the identical or different condition that floods is arranged in each node, so that each node be made to flood based on the condition execution that floods;
Preferably, implement disclosed in two in resource share method in the application, when link circuit resource status information between any sharable node for the acquisition that floods of business source node, intermediate node and business purpose node, can include using various ways
The first, can other nodes into the whole network flood the link circuit resource status information between sharable node;
Second, the condition of flooding can be set, be limited in the link circuit resource status information targetedly issued between the sharable node when the whole network floods, specifically the condition of flooding can be with are as follows:
One, the acquisition that floods to other nodes that the operating path (i.e. business source node, intermediate node and business purpose node) of the business is located in same routed domain any sharable node between link circuit resource status information;
Secondly, to priority lower than the business other business operating path in node flood acquisition any sharable node between link circuit resource status information;
Thirdly, in conjunction with above two limitation mode carry out two-stage restriction, limiting the range to flood is other nodes being located in same routed domain with the operating path of the business, it is priority lower than the node in the operating path of other business of the business that limitation, which is able to use the link circuit resource status information between the sharable node, in the range again, is then flooded;It should be noted that range that above-mentioned limitation floods or flooding to specific node, can be executed using random order during flooding;
Based on resource share method disclosed in above-mentioned the embodiment of the present application, it should be noted that, the restrictive condition added in flooding process can be specifically added in the Value for the TLV that ospf protocol newly increases, such as Priority (3bits), for indicating to can be used the highest priority of the sharable link circuit resource.
The above-mentioned mode to flood disclosed in the embodiment of the present application is only a part of the application, and in resource share method disclosed in the present application, the mode to flood is not limited to that.
Based on a kind of resource share method disclosed in above-mentioned the embodiment of the present application one, in the present embodiment, each node uses signaling method, relative link circuit resource state is sent to the adjacent node in downstream, then by business purpose node by way of signaling, link circuit resource state between node each in entire operating path is fed back into business source node, business source node is made to know the link circuit resource state between each node of entire operating path;
Preferably, in the resource share method disclosed in the embodiment of the present application two, business source node receives the second feedback message that business purpose node is sent by signaling method, includes the link circuit resource status information of the operating path in second feedback message;The link circuit resource status information refers to the link circuit resource status information between each node for constituting the operating path;
The link circuit resource status information is received by business source node by above-mentioned, it can know that those links are sharable on the operating path, it is subsequent resume work path during, whether can be occupied by other business referring to sharable link, in order to the operation in path of completing to resume work accordingly.
Embodiment three
Resource share method disclosed in the embodiment of the present application, except gradually judge link between node whether in addition to fault-free by each node, can also utilize resource of the network controller between each node (network element) do whether Gong Xiang decision.It is illustrated with two LSP2 of business, in the present embodiment, when links one or more in the operating path LSP2_W of business two break down, needs to carry out pretection switch, i.e. business two is switched from LSP2_W to LSP2_P.And, it is assumed that there is no the links of failure for other in operating path LSP2_W, using the decision of the network controller, use it to other business in network as shared resource, as shown in Figure 4:
Centralized Controller K, for concentrating the processing needed for carrying out to each operating path interior joint in the whole network;
The business source node of the LSP2 is A1, and business purpose node is B1, and the link bandwidth between node and node is 1, therefore the LSP2 can be referred to as LSP2 (A1, B1,1)
The protection type of the service path is 1:1 protection, wherein operating path are as follows: A1-E1-B1, Protection path are as follows: A1-G1-H1-J1-B1;In the present example it is assumed that the link E1-B1 between node E1 and node B1 breaks down.For the LSP2 (A1 of the generation link failure, B1,1) in operating path, other link A1-E1 not broken down carry out shared process, as follows using the specific implementation procedure of resource share method disclosed in the application embodiment, specific flow chart is as shown in Figure 5:
S301: business source node A1 after receiving working path failure message, reports working path failure message to Centralized Controller;
S302: Centralized Controller receives working path failure message, and sharable link circuit resource in operating path, and not sharable link circuit resource are calculated based on the business game of working path failure message and Centralized Controller, message can be shared by generating resource, and feed back to business source node A1;Wherein, it includes the link circuit resource status information in operating path between adjacent node that resource, which can share message, and the link circuit resource for showing between those nodes can be shared;
It should be noted that can also further include in the resource-sharing message, which can specifically be shared by the business of which seed type or rank;
S303: business source node A receives resource-sharing message, the link circuit resource status information between the business source node A1 for including in message and intermediate node E1 can be shared by reading resource, and judge whether the link circuit resource status information of link A1-E1 is that can share, if the link circuit resource status information of link A1-E1 is that can share, then execute S304, if the link circuit resource status information of link A1-E1 is that can not share, directly execution S305;
S304: business source node A1 floods sharable link A1-E1;
S305: business source node A1 deletion resource can share information relevant to business source node A1 in message, and the resource after deleting can be shared information and sending to intermediate node E1;
The resource that S306: intermediate node E1 reception business source node A1 is sent can share message, and read the link circuit resource status information of the link A1-E1 and link E1-B1 that include in resource-sharing message, and judge in link A1-E1 and link E1-B1 with the presence or absence of sharable link circuit resource status information, because the link circuit resource status information of link A1-E1 can be shared, then S307 is executed;
S307: intermediate node E1 floods sharable link A1-E1;
Because in the present embodiment, in the link circuit resource status information of link A1-E1 and link E1-B1, the only link circuit resource status information of link A1-E1 can be shared, then in S307, intermediate node E1 floods sharable link A1-E1;
The resource that S308: intermediate node E1 deletion business source node A1 is sent can be shared in message, information relevant to intermediate node E1, and the resource after deleting can be shared message and be sent to business purpose node B1;
The resource that S309: business purpose node B1 reception intermediate node E1 is sent can share message, and read the link circuit resource status information for the link E1-B1 for including in resource-sharing message, and judge whether the link circuit resource status information of link E1-B1 is that can share, because the link circuit resource status information of link E1-B1 is that can not share, does not then execute and flood.
For in the operating path LSP2_W for assuming LSP2 in above-mentioned the embodiment of the present application, link E1-B1 is faulty, therefore, it is calculated using Centralized Controller K according to failure message, obtaining the link in the operating path between each adjacent node is that can share or faulty, and remove faulty link information, sharable link circuit resource status information is integrated, corresponding resource is generated and can share message feedback and give business source node;By business source node, the link circuit resource status information between each adjacent node for including in message can be shared according to resource, carries out the judgement that floods;It executes after meeting the sharable condition that floods and floods accordingly, it will be on the operating path that actually belong to the business, without failure link circuit resource is temporarily released to be used to business other in network, thus on the basis of ensuring to improve service success rate, while improving the utilization rate of Internet resources.
Above-described embodiment is only an example, does not limit the link of failure as final stage, the case where failure it is suitable for any link on operating path.
Disclosed in the embodiment of the present application in the resource share method based on Centralized Controller, for the business source node in operating path, concrete operations are as follows:
Business source node reports working path failure message to Centralized Controller after receiving working path failure message;
The resource that business source node receives Centralized Controller feedback can share message, and it includes the link circuit resource status information in operating path between adjacent node that resource, which can share message,;
Business source node can share the link circuit resource status information between the business source node for including in message and downstream neighbor according to resource, judge the link circuit resource state letter between business source node and downstream neighbor Whether breath is that can share;
If link circuit resource status information between business source node and downstream neighbor is that can share, business source node floods sharable link;
Resource-sharing message is sent to downstream neighbor by business source node.
Specifically before sending resource and can share message, business source node, which can also delete resource, can share information relevant to business source node in message, and the resource after deleting can be shared message and be sent to downstream neighbor.
In addition, not executing and flooding if the link circuit resource status information between the business source node and downstream neighbor is can not to share, and resource can be shared into message and be sent to downstream neighbor.
For the intermediate node in operating path, concrete operations are as follows:
Intermediate node, which receives the resource that upstream neighbor node is sent, can share message, and read the intermediate node for including in the resource-sharing message that upstream neighbor node is sent and upstream neighbor node, and the link circuit resource status information between intermediate node and downstream neighbor, and judge in the link circuit resource status information between intermediate node and upstream neighbor node, intermediate node and downstream neighbor with the presence or absence of sharable link circuit resource status information;
If there is sharable link circuit resource status information, then intermediate node floods sharable link;
Resource can be shared message and be sent to downstream neighbor by intermediate node.
Specifically before sending resource and can share message, the resource that intermediate node can also delete upstream neighbor node transmission can share information relevant to intermediate node in message, and the resource after deleting can be shared message and be sent to downstream neighbor;
In addition, not executing then and flooding if there is no sharable link circuit resource status information, and the resource that the upstream neighbor node is sent can be shared into message and be sent to downstream neighbor.
For business purpose node, concrete operations are as follows:
Business purpose node, which receives the resource that upstream neighbor node is sent, can share message, and it reads in the resource-sharing message of upstream neighbor node transmission, link circuit resource status information between the business purpose node for including and upstream neighbor node, and judge whether the link circuit resource status information between business purpose node and upstream neighbor node is that can share;
If the link circuit resource status information between business purpose node and upstream neighbor node is can to share, business purpose node floods sharable link;
If the link circuit resource status information between business purpose node and upstream neighbor node is can not to share, business purpose node, which does not execute, to flood.
Disclosed in the embodiment of the present application in the resource share method based on Centralized Controller, it can also use PCEP agreement between Centralized Controller and node, in use, PCEP agreement is extended, one bit are extended i.e. in PCEP agreement, for indicating that PCC request PCE does the whether sharable judgement request of resource;
In PCEP agreement extend one bit can in the following ways, but simultaneously not only limit and this;Specifically:
One bit are added in existing LSP object, and is carried by PCRpt message or PCRep message, for indicating request;
U (1bit): indicate need do whether sharable calculating;
Similarly, disclosed in the embodiment of the present application in the resource share method based on Centralized Controller, during Centralized Controller, which generates resource, to share message, restrictive condition can be added, the restrictive condition can be carried by following TLV, and different restrictive conditions can also be distinguished by Type;
For example, the restrictive condition can be with are as follows: the priority of the sharable link circuit resource can be used, i.e., the information of a PriorityNumber is added in the part Value;Or: can be used this LSP can The item number of shared link circuit resource, such as LSP Number;
It should be noted that TLV defined above also can be used and carry this feature information when carrying being needed to be able to use the characteristic information of sharable link circuit resource state in PCEP agreement and RSVP-TE agreement.
Example IV
Based on resource share method disclosed in above-mentioned the embodiment of the present application one to embodiment three, in the present embodiment, between the link circuit resource without failure node, according to such as the whole network flood or be arranged the condition of flooding flood it is shared after, for the node for receiving the sharable link to flood, it establishes the process of operating path when receiving service request;
On the basis of the relevant information schematic diagram of the application example IV network topology structure disclosed in Fig. 1 and LSP1, increases LSP3 and be illustrated, as shown in Figure 6: LSP3 (C, the D, BW=1), link A-E, link E-F in LSP1 (A, B, BW=1) are shared;
The business source node C establishes the process of operating path, mainly comprises the steps that when receiving service request (C, D, BW=1)
S401, business source node C are searched and are obtained available link C-K and link L-D in network between business source node C and business purpose node D, and calculate the available path between business source node C and business purpose node D;
S402, when not calculating available path, business source node C obtains available link E-F based on the received sharable link A-E and link E-F to be flooded;
S403, business source node C recalculate available path using link C-K, link L-D and link E-F, and based on being calculated, the available path C-K-E-F-L-D comprising link E-F;
S404, business source node C send resource allocation request to the corresponding start node E of link E-F;
S405, business source node C receive start node E feedback allow establish intersect after, using RSVP-TE message, corresponding operating path C-K-E-F-L-D is established based on available path;
The business source node A of former operating path where S406, from business source node C to link E-F sends notice message, carries the occupied information of link E-F in notice message.
Disclosed in the embodiment of the present application in shared resource method, the node of the service request received in needle network, it is during calculating service path, first consider whether there are the available resources not occupied by other business in network, if not obtaining corresponding available path, consider temporarily to be shared out in other business Link circuit resource.And after available path is calculated, resource allocation request is sent to the start node for including sharable link circuit resource in the available path, and after start node feedback allows to establish and intersect, utilize RSVP-TE message, corresponding service path is established based on the available path being calculated, and notice message is sent to the business source node of the service path where the sharable link circuit resource, inform that the sharable link circuit resource is occupied.
When calculating available path based on sharable link circuit resource, disclosed in the embodiment of the present application in resource share method, it is preferred that limitation uses sharable link circuit resource, and least sharable link circuit resource will be used as the restrictive condition of calculating available path.
Based on a variety of different methods that flood disclosed in above-mentioned the embodiment of the present application; in the present embodiment; preferably; disclosed in the application embodiment in resource share method; after service failure recovery; the business of business data transmission is carried out in Protection path, needs to retract from Protection path into operating path.
Because during rollback, part of links on the operating path of the business may be shared, therefore it is retracted based on the mode that floods different in resource share method using following methods in order to ensure business can successfully retract into operating path or improve the success rate to retract:
Based on any one mode that floods, after service failure recovery, using there are a available resources in the operating path to go back that only ensures to retract, does not need strictly rollback or use original resource, i.e., in original operating path.
It carries out respectively judging whether to share by each node for disclosed in above-mentioned the embodiment of the present application, or concentrate by Centralized Controller and judge whether sharable resource share method, after determining sharable link circuit resource, it, can be in the following way when former business needs to return back on operating path:
Respectively judged whether sharable situation for by each node, after business source node, which receives working path failure, restores message:
It inquires with the presence or absence of the link circuit resource not used by other business in sharable link circuit resource, if not used by other business all, is directly retracted by Protection path to former operating path;
If part is not used by other business, on the basis of meeting business game, retracted by Protection path into the sharable link circuit resource not used by other business partially, new operating path is constituted by the former operating path of part Protection path and part;
If all being used by other business, in the case where subscriber policy allows, former business is carried out at degradation Reason, and all resources are discharged, re-establish new operating path;
Or; it is partly or entirely occupied by the low business of priority when inquiring sharable link circuit resource; the sharable link circuit resource of the former business of cross-reference in the operating path of the low business of priority is then disconnected, and is directly retracted from Protection path into former operating path.
Judge whether sharable situation for concentrate by Centralized Controller, after business source node, which receives working path failure, restores information:
Working path failure recovery message is sent to Centralized Controller by business source node;
Centralized Controller restores the complexity that message evaluation is restored to former operating path based on working path failure;
If complexity is lower than default complexity, according in former operating path can the state that is partially occupied of shared link resource, control business retracts by Protection path into the sharable link circuit resource not used by other business partially;
Alternatively, according in former operating path can the state that is occupied by the low service part of priority or all of shared link resource, control business forces to retract into former operating path;
If complexity is higher than default complexity, recalculates an operating path and feed back the business source node;
Wherein, the degree-of-difficulty factor of complexity is preset generally on the basis of the power consumption for establishing consuming required for a new operating path.
Pass through resource share method disclosed in above-mentioned the embodiment of the present application, after sharable link circuit resource is flooded, if the failure of the operating path of former business has solved, it is retracted at this time using aforesaid way into part or all of former operating path, or re-establish new operating path, the success rate for further improving rollback, also effectively raises the utilization for Internet resources.
Embodiment five
Based on resource share method disclosed in above-mentioned the embodiment of the present application, the network node structure that business source node, intermediate node and business purpose node carry out resource-sharing accordingly may be implemented in the application embodiment also corresponding disclose, and the network resources locating system with the operating path for being accordingly made of business the network node with business source node, intermediate node and business purpose nodal function;
When in network resources locating system not comprising Centralized Controller or each network node independent of this When Centralized Controller;It is described in detail respectively for the network node of the resource-sharing function with corresponding service source node, intermediate node and business purpose node;
It is marked and distinguishes using " first " " second " etc. below for the module with same or similar function in different network node and different network node;
As shown in Figure 7, for the structural schematic diagram that business source node carries out the first network node of resource-sharing may be implemented, the first network node 100 includes: above-mentioned disclosed in the present application for executing, by the first judgment module 101 for the resource share method that business source node executes, the first update module 102 and the first sending module 103.Such as, first judgment module 101, for network node after receiving working path failure message, execute resource status and update judgement, the resource updates be judged as judge link circuit resource between the network node and the downstream neighbor of the network node whether fault-free;Link circuit resource state between the network node and the downstream neighbor is updated to share by first update module 102 when for link circuit resource fault-free between the network node and the downstream neighbor;First sending module 103 updates request message for sending resource status to the downstream neighbor, and the resource status updates in request message comprising the link circuit resource status information between the network node and the downstream neighbor.
In the first network node 100 disclosed by the embodiments of the present invention, further include: the first management module, the resource allocation request sent for receiving the corresponding node of other business, and allow to establish intersection information to the corresponding node feeding back of other business according to resource allocation strategy.
In the business source node 100 disclosed by the embodiments of the present invention, further includes: the first flood module and the first determining module and/or the first receiving module, rollback module etc. realize the module of corresponding function during above-mentioned business source node carries out resource-sharing.
As shown in Figure 8, for the structural schematic diagram that intermediate node carries out the second network node of resource-sharing may be implemented, second network node 200 includes: above-mentioned disclosed in the present application for executing, by the second judgment module 201 of the resource share method that intermediate node executes, the second update module 202 and the second sending module 203.Such as, second judgment module 201, received after the resource status that upstream neighbor node is sent updates request message for network node, execute resource status and update judgement, the resource updates be judged as judge link circuit resource between the network node and downstream neighbor whether fault-free;Second update module 202 will when for link circuit resource fault-free between the network node and the downstream neighbor Link circuit resource state between the network node and the downstream neighbor is updated to share;Second sending module 203, request message is updated for sending the resource status to the downstream neighbor, the resource status updates in request message comprising the link circuit resource status information between the network node and the downstream neighbor, and the first feedback message is sent to the upstream neighbor node, it include indicating that the upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message.
In the intermediate node 200 disclosed by the embodiments of the present invention, further include: the second management module, the resource allocation request sent for receiving the corresponding node of other business, and allow to establish intersection information to the corresponding node feeding back of other business according to resource allocation strategy.
In second network node 200 disclosed by the embodiments of the present invention, further includes: the second flood module 204 and the second determining module and/or the second receiving module etc. realize the module of corresponding function during above-mentioned intermediate node carries out resource-sharing.
As shown in Figure 9, for the structural schematic diagram that business purpose node carries out the third network node of resource-sharing may be implemented, the network node 300 includes: above-mentioned disclosed in the present application for executing, by the third judgment module 301 for the resource share method that business purpose node executes, third flood module 302 and third sending module 303.Such as, third judgment module 301, the resource status that upstream neighbor node is sent is received for network node and updates request message, is obtained in the resource status update message, the link circuit resource status information between the upstream neighbor node for including and the network node;The third flood module 302, for being flooded after confirming the link circuit resource status information between the upstream neighbor node and the network node for that can share to link sharable between the upstream neighbor node and the network node;Third sending module 303 includes: that the instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message for sending the first feedback message to the upstream neighbor node.
In the third network node 300 disclosed by the embodiments of the present invention, further includes: third determining module etc. realizes the module of corresponding function during above-mentioned intermediate node carries out resource-sharing.
Modules in above-mentioned first network node 100, the second network node 200 and third network node 300 are executing resource-sharing, and detailed process relevant to resource-sharing or principle, it is disclosed relevant to first network node, the second network node and third network node interior in above-mentioned the embodiment of the present application Hold it is corresponding, can cross-reference be therefore not discussed here.
In conjunction with the resource share method that disclosed embodiments describe, can directly be implemented with the combination of hardware, the memory that processor executes or the two in first network node, the second network node and third network node.Therefore, the application also corresponds to resource share method disclosed in above-mentioned the embodiment of the present application, individually disclose a kind of first network node, the second network node and third network node, its structure is identical, as shown in Figure 10, in the first network node, the second network node and third network node, including memory 10 and the processor 12 being connect by bus 11 with memory 10.
The memory 10 has storage medium, and the operating process that respective network node executes resource-sharing is stored in the storage medium.
The operating process of the resource-sharing, i.e., the corresponding program of resource share method for each network node disclosed above, the program may include program code, and said program code may include a series of operational orders arranged according to certain in-line arrangement.Processor may be a central processor CPU or specific integrated circuit, or be arranged to implement one or more integrated circuits of the embodiment of the present application.
Memory may include high speed RAM memory, it is also possible to and it further include nonvolatile memory, a for example, at least magnetic disk storage.
The processor is connect by bus with memory, and when each network node executes resource-sharing, which calls the operating process of the resource-sharing stored in memory.
Based on above-mentioned first network node, the second network node and third network node disclosed in the present application, as shown in figure 11, a kind of network resources locating system 1 of operating path that business is made of above-mentioned first network node 100, the second network node 200 and third network node 300 is also disclosed.Wherein, the dotted line in Figure 11 indicates first network node, the second network node and second network node in the operating path of other business etc..
The link between business source node, intermediate node and business purpose node is made whether using Centralized Controller to share the resource share method of judgement based on the application is disclosed above, the application also correspondence discloses another network resources locating system, such as Figure 12, the network resources locating system 4 specifically includes that Centralized Controller 400, business source node 401, intermediate node 402 and business purpose node 403.
Wherein, based on above-mentioned corresponding in business source node 402, intermediate node 403 and business purpose node 404 Method can be executed using corresponding module, be not discussed here.Dotted line in Figure 12 indicates business source node, intermediate node and business purpose node in the operating path of other business etc..
It should be noted that, other operations that the disclosed business source node for executing resource share method of above-mentioned the embodiment of the present application, intermediate node and business purpose node its all parts are related to, such as the operation that floods that the condition that floods is arranged, it may refer to the corresponding portion in resource published method disclosed in above-mentioned the embodiment of the present application, be not discussed here.
To sum up; this application discloses a kind of technical solutions of resource-sharing; after in a certain business, it breaks down because of operating path then transmits data using Protection path; link circuit resource without failure on the operating path for actually belonging to the business is temporarily released and is used to business other in network; thus on the basis of ensuring to improve service success rate, while improving the utilization rate of Internet resources.
Further, problem involved when retracting is considered in flooding process, to improve the success rate of rollback, also improves the utilization rate of resource inward simultaneously.
The foregoing is merely preferred embodiment of the present application, are not intended to restrict the invention, and for those skilled in the art, the invention may be variously modified and varied.All within the spirits and principles of the present invention, any modification, equivalent replacement, improvement and so on should all be included in the protection scope of the present invention.

Claims (23)

  1. A kind of resource share method characterized by comprising
    Business source node executes resource status and updates judgement after receiving working path failure message, the resource updates be judged as judge link circuit resource between the business source node and downstream neighbor whether fault-free;
    If the link circuit resource fault-free between the business source node and the downstream neighbor, the link circuit resource state between the business source node and the downstream neighbor is updated to share;
    Resource status is sent to the downstream neighbor and updates request message, and the resource status updates in request message comprising the link circuit resource status information between the business source node and the downstream neighbor.
  2. The method according to claim 1, wherein the resource status, which updates also to carry in request message, requires the solicited message that downstream neighbor executes the resource status update judgement.
  3. The method according to claim 1, wherein after the link circuit resource state between the business source node and the downstream neighbor is updated to share, further includes:
    It floods to sharable link between the business source node and the downstream neighbor.
  4. Method according to any one of claims 1 to 3, which is characterized in that before the link circuit resource state between the business source node and the downstream neighbor is updated to share, the method also includes:
    There are preset link circuit resource configuration informations in the business source node, determine that the link circuit resource configuration information is that can share, and/or the business source node receives the link circuit resource configuration instruction information from the downstream neighbor, the link circuit resource configuration instruction information instruction can be shared.
  5. A kind of network node characterized by comprising
    First judgment module executes resource status and updates and judge for network node after receiving working path failure message, the resource updates be judged as judge link circuit resource between the network node and the downstream neighbor of the network node whether fault-free;
    Link circuit resource state between the network node and the downstream neighbor is updated to share by first update module when for link circuit resource fault-free between the network node and the downstream neighbor;
    First sending module updates request message for sending resource status to the downstream neighbor, and the resource status updates in request message comprising the chain between the network node and the downstream neighbor Road resource state information.
  6. Network node according to claim 5, which is characterized in that further include:
    First flood module, for being flooded after being updated to share by the link circuit resource state between the network node and the downstream neighbor to link sharable between the network node and the downstream neighbor.
  7. The network node according to claim 5 or 6, which is characterized in that further include:
    First determining module, for before the link circuit resource state between the network node and the downstream neighbor is updated to share, preset link circuit resource configuration information present in the network node is confirmed, determines that the link circuit resource configuration information is that can share;
    And/or
    First receiving module, for before the link circuit resource state between the network node and the downstream neighbor is updated to share, the link circuit resource configuration instruction information from the downstream neighbor is received, the link circuit resource configuration instruction information instruction can be shared.
  8. A kind of resource share method characterized by comprising
    Intermediate node receives after the resource status update request message that upstream neighbor node is sent, execute resource status and update judgement, the resource status update the link circuit resource that is judged as judge between the intermediate node and the downstream neighbor of the intermediate node whether fault-free;
    If the link circuit resource fault-free between the intermediate node and the downstream neighbor, the link circuit resource state between the intermediate node and the downstream neighbor is updated to share;
    The resource status is sent to the downstream neighbor and updates request message, and the resource status updates in request message comprising the link circuit resource status information between the intermediate node and the downstream neighbor;
    The first feedback message is sent to the upstream neighbor node, includes: that the instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message.
  9. According to the method described in claim 8, it is characterized in that, the resource status, which updates also to carry in request message, requires the solicited message that downstream neighbor executes the resource status update judgement.
  10. According to the method described in claim 8, it is characterized by further comprising:
    It floods to link sharable between the upstream neighbor node and the intermediate node, and floods to link sharable between the intermediate node and downstream neighbor.
  11. The method according to any one of claim 8~10, which is characterized in that will be described Before link circuit resource state between intermediate node and the downstream neighbor is updated to share, the method also includes:
    There are preset link circuit resource configuration informations in the intermediate node, determine that the link circuit resource configuration information is that can share, and/or the intermediate node receives the link circuit resource configuration instruction information from the downstream neighbor, the link circuit resource configuration instruction information instruction can be shared.
  12. A kind of network node characterized by comprising
    Second judgment module, after the resource status update request message for receiving upstream neighbor node transmission for network node, execute resource status and update judgement, the resource updates be judged as judge link circuit resource between the network node and downstream neighbor whether fault-free;
    Link circuit resource state between the network node and the downstream neighbor is updated to share by second update module when for link circuit resource fault-free between the network node and the downstream neighbor;
    Second sending module, request message is updated for sending the resource status to the downstream neighbor, the resource status updates in request message comprising the link circuit resource status information between the network node and the downstream neighbor, and the first feedback message is sent to the upstream neighbor node, it include indicating that the upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message.
  13. Network node according to claim 12, which is characterized in that further include:
    Second flood module for flooding to link sharable between the upstream neighbor node and the network node, and floods to link sharable between the network node and the downstream neighbor.
  14. Network node according to claim 12 or 13, which is characterized in that further include:
    Second determining module, for before the link circuit resource state of the network node and the downstream neighbor is updated to share, preset link circuit resource configuration information present in the network node is confirmed, determines that the link circuit resource configuration information is that can share;
    And/or
    Second receiving module, for before the link circuit resource state between the network node and the downstream neighbor is updated to share, the link circuit resource configuration instruction information from the downstream neighbor is received, the link circuit resource instruction information instruction can be shared.
  15. A kind of resource share method characterized by comprising
    Business purpose node receives the resource status that upstream neighbor node is sent and updates request message, it obtains in the resource status update message, link circuit resource status information between the upstream neighbor node for including and the business purpose node confirms whether the link circuit resource status information between the upstream neighbor node and the business purpose node is that can share;
    After confirming the link circuit resource status information between the upstream neighbor node and the business purpose node for that can share, then flood to sharable link between the upstream neighbor node and the business purpose node;
    The first feedback message is sent to the upstream neighbor node, includes: that the instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message.
  16. According to the method for claim 15, which is characterized in that before sharable link floods between the upstream neighbor node and the business purpose node, further includes:
    There are preset link circuit resource configuration information in the business purpose node, determine that the link circuit resource configuration information is that can share.
  17. A kind of network node characterized by comprising
    Third judgment module receives the resource status that upstream neighbor node is sent for network node and updates request message, obtains in the resource status update message, the link circuit resource status information between the upstream neighbor node for including and the network node;
    The third flood module, for being flooded after confirming the link circuit resource status information between the upstream neighbor node and the network node for that can share to link sharable between the upstream neighbor node and the network node;
    Third sending module includes: that the instruction upstream neighbor node floods sharable link circuit resource configuration instruction information relevant to itself in first feedback message for sending the first feedback message to the upstream neighbor node.
  18. Network node according to claim 17, which is characterized in that further include:
    Third determining module, for to before sharable link floods between the upstream neighbor node and the business purpose node, to there are preset link circuit resource configuration informations to confirm in the business purpose node, determine that the link circuit resource configuration information is that can share.
  19. A kind of network resources locating system characterized by comprising any one in claim 5~7 Network node described in, network node described in network node and claim 17 or 18 described in any one of claim 12~14;
    The operating path of business is constituted between the network node.
  20. A kind of resource share method characterized by comprising
    Business source node reports the working path failure message to Centralized Controller after receiving working path failure message;
    The resource for receiving the Centralized Controller feedback can share message, and it includes the link circuit resource status information in the operating path between adjacent node that the resource, which can share message,;
    Judge whether the link circuit resource status information between the business source node and downstream neighbor is that can share according to the link circuit resource status information;
    If the link circuit resource status information between the business source node and the downstream neighbor be it is sharable, the business source node floods sharable link;
    The resource can be shared message and be sent to the downstream neighbor by the business source node.
  21. According to the method for claim 20, it is characterized in that, when the downstream neighbor is intermediate node, the intermediate node receives and the resource for judging that upstream neighbor node is sent can be shared in message, the intermediate node for including is with the link circuit resource status information between the upstream neighbor node and the intermediate node and the downstream neighbor with the presence or absence of sharable link circuit resource status information;
    If there are sharable link circuit resource status information in the link circuit resource status information between the intermediate node and the upstream neighbor node and the intermediate node and the downstream neighbor, the intermediate node floods sharable link;
    The resource can be shared message and be sent to the downstream neighbor by the intermediate node.
  22. The resource share method according to claim 20 or 21, it is characterized in that, when the downstream neighbor is business purpose node, the business purpose node receives and judges in the resource-sharing message of upstream neighbor node transmission, and whether the link circuit resource status information between the business purpose node for including and the upstream neighbor node is that can share;
    If the link circuit resource status information between the business purpose node and the upstream neighbor node be it is sharable, the business purpose node floods sharable link.
  23. A kind of network resources locating system characterized by comprising Centralized Controller, business source node, intermediate node and business purpose node;
    The business source node, the intermediate node and the business purpose node constitute the operating path of business;
    The Centralized Controller concentration is made whether sharable judgement to the link between the business source node, the intermediate node and the business purpose node.
CN201680088411.8A 2016-09-22 2016-09-22 Resource sharing method, network node and related equipment Active CN109644122B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011351939.4A CN112803995B (en) 2016-09-22 2016-09-22 Resource sharing method, network node and related equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/099705 WO2018053747A1 (en) 2016-09-22 2016-09-22 Resource sharing method, network node, and associated apparatus

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN202011351939.4A Division CN112803995B (en) 2016-09-22 2016-09-22 Resource sharing method, network node and related equipment

Publications (2)

Publication Number Publication Date
CN109644122A true CN109644122A (en) 2019-04-16
CN109644122B CN109644122B (en) 2020-12-15

Family

ID=61689325

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202011351939.4A Active CN112803995B (en) 2016-09-22 2016-09-22 Resource sharing method, network node and related equipment
CN201680088411.8A Active CN109644122B (en) 2016-09-22 2016-09-22 Resource sharing method, network node and related equipment

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN202011351939.4A Active CN112803995B (en) 2016-09-22 2016-09-22 Resource sharing method, network node and related equipment

Country Status (2)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110167032A (en) * 2019-04-30 2019-08-23 陕西师范大学 The network-building method and system of the software definition wireless self-organization network of unmanned aerial vehicle (UAV) control
CN113823040A (en) * 2020-06-19 2021-12-21 中国移动通信集团福建有限公司 Management method and system for shared bicycle
CN114116200A (en) * 2021-10-27 2022-03-01 北京百度网讯科技有限公司 Resource sharing method, service creation method, device and electronic equipment

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101001170A (en) * 2006-01-10 2007-07-18 华为技术有限公司 Service failure recovery method
CN101309525A (en) * 2008-06-30 2008-11-19 中兴通讯股份有限公司 Route recovery method according to failure positioning in automatic exchange optical network
CN101420331A (en) * 2008-12-12 2009-04-29 北京邮电大学 Fast fault locating method for ultra-long connection in T-MPLS network
CN101610203A (en) * 2008-06-16 2009-12-23 华为技术有限公司 Realize method, the Apparatus and system of multicast heavy-route
CN102143065A (en) * 2011-02-09 2011-08-03 华为技术有限公司 Fault protection method and equipment
US20110188397A1 (en) * 2009-10-16 2011-08-04 Mccann Thomas M Methods, systems, and computer readable media for multi-interface monitoring and correlation of diameter signaling information
CN102164051A (en) * 2011-05-18 2011-08-24 西安交通大学 Service-oriented fault detection and positioning method
CN102333250A (en) * 2011-10-26 2012-01-25 西安电子科技大学 Low-congestion communication method and router for realizing shared path transmission of optical network on chip

Family Cites Families (9)

* 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
CN101471693B (en) * 2007-12-27 2013-04-17 华为技术有限公司 Method and apparatus for sharing grid protection
CN101232453A (en) * 2008-01-11 2008-07-30 北京邮电大学 Heavy route method for fast searching path in T-MPLS network
CN101754316B (en) * 2008-12-12 2012-12-26 上海电机学院 QoS energy-saving routing method based on maximization network life cycle
CN101800913B (en) * 2009-02-11 2013-02-27 中兴通讯股份有限公司 Realization method for protecting and restoring multiplex section of automatically switched optical network
CN102098591B (en) * 2009-12-11 2013-08-21 中兴通讯股份有限公司 Method for sharing resources in automatic switched optical network (ASON) and service node
CN102136865B (en) * 2010-08-09 2014-04-16 华为技术有限公司 Service recovering method, system and node device
WO2014131155A1 (en) * 2013-02-27 2014-09-04 华为技术有限公司 Protection switching method, system, and node
JP2014183539A (en) * 2013-03-21 2014-09-29 Panasonic Corp Radio communication device

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101001170A (en) * 2006-01-10 2007-07-18 华为技术有限公司 Service failure recovery method
CN101610203A (en) * 2008-06-16 2009-12-23 华为技术有限公司 Realize method, the Apparatus and system of multicast heavy-route
CN101309525A (en) * 2008-06-30 2008-11-19 中兴通讯股份有限公司 Route recovery method according to failure positioning in automatic exchange optical network
CN101420331A (en) * 2008-12-12 2009-04-29 北京邮电大学 Fast fault locating method for ultra-long connection in T-MPLS network
US20110188397A1 (en) * 2009-10-16 2011-08-04 Mccann Thomas M Methods, systems, and computer readable media for multi-interface monitoring and correlation of diameter signaling information
CN102143065A (en) * 2011-02-09 2011-08-03 华为技术有限公司 Fault protection method and equipment
CN102164051A (en) * 2011-05-18 2011-08-24 西安交通大学 Service-oriented fault detection and positioning method
CN102333250A (en) * 2011-10-26 2012-01-25 西安电子科技大学 Low-congestion communication method and router for realizing shared path transmission of optical network on chip

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110167032A (en) * 2019-04-30 2019-08-23 陕西师范大学 The network-building method and system of the software definition wireless self-organization network of unmanned aerial vehicle (UAV) control
CN113823040A (en) * 2020-06-19 2021-12-21 中国移动通信集团福建有限公司 Management method and system for shared bicycle
CN114116200A (en) * 2021-10-27 2022-03-01 北京百度网讯科技有限公司 Resource sharing method, service creation method, device and electronic equipment
CN114116200B (en) * 2021-10-27 2024-04-05 北京百度网讯科技有限公司 Resource sharing method, service creation method, device and electronic equipment

Also Published As

Publication number Publication date
CN112803995B (en) 2022-07-19
CN112803995A (en) 2021-05-14
CN109644122B (en) 2020-12-15
WO2018053747A1 (en) 2018-03-29

Similar Documents

Publication Publication Date Title
CN111587580B (en) Interior gateway protocol flooding minimization
CN112104551B (en) Border gateway protocol for communication between software defined network controllers
CN101861714B (en) Method for establishing hierarchical segmented label switched paths and network therefor
EP1863235B1 (en) Method and system for multi-domain route computation
US7058845B2 (en) Communication connection bypass method capable of minimizing traffic loss when failure occurs
US8009677B2 (en) Path setting method and communication device in network segmented into plurality of areas
KR101468763B1 (en) Rsvp-te enhancement for mpls-frr bandwidth optimization
EP1345364A1 (en) Routing control method and routing control apparatus for the same
CN103166848A (en) Method and point for selecting multi-protocol label switching traffic engineering bypass tunnel
CN109644122A (en) Resource share method, network node and relevant device
CN101321115B (en) Method and system for establishing business route, and node equipment
WO2012071909A1 (en) Method and device for service recovery
US8542687B2 (en) Node apparatus and route calculation method
CN113542120B (en) Path selection method and device and computer readable storage medium
US7590051B1 (en) Method and apparatus for redialing a connection on a communication network
CN112804140B (en) Transmission path switching method, device, network node, medium and network system
CN116319549A (en) Distributed flow scheduling method and device
KR20110129413A (en) Routing device, communications system, and routing method
CN112055954B (en) Resource reservation and maintenance of preferred path routes in a network
CN113169939B (en) Method, network equipment and system for establishing service path
Ajiardiawan et al. Performance analysis of segment routing on MPLS L3VPN using PNETLAB
CN113453095B (en) Method and device for restoring path configuration
US20210218668A1 (en) Tearing Down a Label Switched Path through a Communications Network
CN114598596A (en) Method, device and system for managing tunnel
Bernstein et al. Optical network control—concepts, standardization and interoperability

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant