CN102271048B - Service protecting method in aggregated links and device - Google Patents
Service protecting method in aggregated links and device Download PDFInfo
- Publication number
- CN102271048B CN102271048B CN201010196424.1A CN201010196424A CN102271048B CN 102271048 B CN102271048 B CN 102271048B CN 201010196424 A CN201010196424 A CN 201010196424A CN 102271048 B CN102271048 B CN 102271048B
- Authority
- CN
- China
- Prior art keywords
- link
- service
- bandwidth
- member link
- traffic
- 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.)
- Expired - Fee Related
Links
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses the service protecting method in a kind of aggregated links and device, wherein, described method comprises: detect that the business of the bandwidth of operation transmission of the first Member Link in described aggregated links breaks down; Judge that the bandwidth reserved of the described business of the second Member Link in described aggregated links is effective; The bandwidth reserved of described second Member Link is used to continue the described business of transmission.By the present invention, achieve the flexible switching of the business that aggregated links is transmitted, ensure that the service quality of transport service.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method and an apparatus for protecting a service in an aggregated link.
Background
With the increase of data traffic and the improvement of the requirement for quality of service, in the packet-switched Network, the traffic engineering is currently implemented by adopting the techniques of MPLS (Multi-Protocol Label Switching), MPLS-TP (MPLS Transport Profile, packet Transport Network), PBB (Provider Backbone Bridge), VLAN (Virtual local area Network) Switching, and the like. Before user data is transmitted, an SLA (Service-Level Agreement) is formulated according to user requirements, a forwarding path of the data is configured in advance through a control protocol, bandwidth resources are allocated, a Service flow with Service quality assurance such as bandwidth is formed, and when a network resource state changes (link failure, network resource utilization rate and the like), the forwarding path of the Service flow is further adjusted, so that QoS (quality of Service) requirements of users are met, so that a Traffic Engineering (TE) technology is currently applied to an operator network more and more widely. High bandwidth, high availability is increasingly becoming the most important feature of packet-switched networks. Link aggregation is an important technique to satisfy high availability and high bandwidth of a network.
The link aggregation technology (described in IEEE 802.3 ad) is a technology that combines several physical links between two devices into one logical link (called an aggregated link), which is a logical whole and looks like a link to other devices, and shields the details of internal components and data transmission.
In order to effectively protect services according to different levels of service flows, the related art maps different service flows onto different member links according to service types on a logical link (namely, an aggregation link) formed by a plurality of physical member links, and allocates working bandwidth resources and protection bandwidth resources for the service flows according to the service types; the aggregation link comprises at least one working link and at least one backup link, wherein the working link bears the service flow with high priority, and the backup link bears the service flow with low priority; when the working link fails, the service flow with high priority is switched from the failed link to the backup link for transmission. The effective protection of the service flow is realized through the priority level of the service flow and the reserved resources, but the technology limits the link attribute and the use, when the fault occurs, the fault link with the working link attribute can only be switched to the link with the backup link attribute, and other switching modes are lacked, so that the switching flexibility is not enough, and the bandwidth of the aggregation link cannot be fully utilized.
Disclosure of Invention
The present invention mainly aims to provide a method and an apparatus for protecting a service in an aggregated link, so as to solve the problems that the service switching in the related art lacks flexibility and cannot fully utilize the aggregated link bandwidth.
According to an aspect of the present invention, a method for protecting traffic in an aggregated link is provided, including: detecting that a service transmitted by a working bandwidth of a first member link in an aggregation link fails; judging that the reserved bandwidth of the service of a second member link in the aggregation link is effective; and continuing to transmit the service by using the reserved bandwidth of the second member link.
According to another aspect of the present invention, there is provided a traffic protection device in an aggregated link, including: the first judgment module is used for detecting that the working bandwidth transmission service of a first member link in the aggregation link fails; the second judgment module is used for judging that the reserved bandwidth of the service of a second member link in the aggregation link is effective; and the protection module is used for continuously transmitting the service by using the reserved bandwidth of the second member link.
The service protection function in the aggregation link faces to services (service flows), and by adopting a mutual protection mode among member links of the aggregation link, the idle bandwidth of each member link in the aggregation link is effectively utilized, so that the problems that flexible switching cannot be performed and the bandwidth of the aggregation link cannot be fully utilized when a working link of the aggregation link fails in the related art are solved, the flexible switching of the services transmitted on the aggregation link is realized, and the service quality of the transmitted services is ensured.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a flowchart illustrating steps of a method for protecting traffic in an aggregated link according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating another step of a method for protecting traffic in an aggregated link according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a first aggregated link reservation protection resource according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a second aggregated link reservation protection resource according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a third aggregated link reservation protection resource according to an embodiment of the present invention;
fig. 6 is a schematic diagram of aggregating link bearer traffic and reserving protection resources according to an embodiment of the present invention;
FIG. 7 is a schematic illustration of traffic protection after failure of a member link of the aggregated link shown in FIG. 6;
FIG. 8 is a schematic diagram of traffic protection after failure of a member link of the aggregated link shown in FIG. 6;
fig. 9 is a flowchart of steps of a traffic protection method in an aggregated link according to another embodiment of the present invention;
fig. 10 is a block diagram of a traffic protection device in an aggregated link according to an embodiment of the present invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
The invention refers to service flow as SFlow/SFlows. Corresponding to different SLAs (Service LEVEL agreements), the protection modes and the method requirements of the Service flows are different, and in order to describe intuitively, the invention defines the height of the Service flows to the protection requirements by priority and expresses the height by quantity values.
In the following description, the following description is made:
linka represents the identification of an aggregation link, and Linka-b represents the identification of member links of the aggregation link Linka;
T-BW in Linka-b (T-BW, F-BW) represents the maximum reservable bandwidth information of one member link (i.e. the maximum reserved bandwidth capability of the member link), and F-BW represents the reservable free bandwidth of the link (i.e. the free bandwidth actually existed currently).
MaxLspBW in Linka (MaxLspBW) represents unreserved maximum LSP (Label Switched Path) bandwidth of aggregated link Linka (i.e., the maximum remaining free bandwidth that can be continuously carried in all member links of aggregated link Linka). To avoid out-of-order in packet delivery, the embodiments of the present invention take the example that SFlow is not allowed to be transmitted across multiple member links at the same time, so MaxLspBW should be the maximum value of the remaining free bandwidth of all member links.
SFlow (CIR, link) represents some key eigenvalue information of SFlow, where: CIR represents the committed bandwidth; link represents the member link identification of SFlow passing through the aggregation link, and if no member link is allocated to SFlow, the value is null.
The following embodiments of the present invention are all described by way of example, which do not allow one SFlow to be transmitted across multiple member links at the same time.
Referring to fig. 1, a flowchart illustrating steps of a method for protecting traffic of an aggregated link according to an embodiment of the present invention is shown, including the following steps:
step S102: detecting that a service transmitted by a working bandwidth of a first member link in an aggregation link fails;
if the sum of the bandwidths of the first member links is 10M, the member link transmits a service, and the service occupies a bandwidth of 4M, then the bandwidth of 4M is the working bandwidth of the first member link. For another example, the sum of the bandwidths of the first member links is 10M, two services are transmitted on the member links, the two services occupy a total bandwidth of 6M, and the bandwidth of 6M is the working bandwidth of the first member link.
In this step, the packet node detects that a service transmitted by the working bandwidth of the first member link in the aggregated link fails.
Step S104: judging that the reserved bandwidth of the service of a second member link in the aggregation link is effective;
for example, the packet switching node reserves bandwidth resources on the other member links for the service on the failed member link in advance, and at this time, it may be determined whether the reserved bandwidth resources are valid, that is, not invalid or occupied by other services.
If the service on the failed member link does not reserve bandwidth on other member links, the packet switching node may determine whether there is remaining free bandwidth in the normal member links in the aggregated link that can satisfy the service transmission on the failed member link.
Step S106: and continuing to transmit the traffic by using the reserved bandwidth of the second member link.
For example: and under the condition that the reserved bandwidth of the second member link is effective, the packet switching node uses the reserved bandwidth to continuously transmit the service on the failed member link.
In the related art, the link attributes and the usage of the member links in the aggregated link are limited, and when the member links fail, the failed links with the working link attributes can only be switched to the links with the backup link attributes, so that the switching is not flexible enough, and the bandwidth of the aggregated link cannot be fully utilized. Through the embodiment, each member link of the aggregation link is a backup for each other, and any member link which fails can be switched to all other member links with idle bandwidth, so that the idle bandwidth of each member link is effectively utilized, and the switching flexibility is improved.
Referring to fig. 2, there is shown another step flowchart of a method for protecting traffic in an aggregated link according to an embodiment of the present invention, including the following steps:
step S202: when an SFlow passes through an aggregation link, one member link is selected to reserve working bandwidth resources according to the information of the bandwidth of the SFlow and the like, and the SFlows with the priority greater than the set value are reserved with protection bandwidth resources in the rest member links, and the SFlows with the priority less than the set value do not need to reserve bandwidth.
By setting the priority, the important service with high priority is guaranteed to be protected preferentially when the aggregation link encounters a fault.
When the protection resource is reserved, the protection bandwidth can be reserved for the member link for which protection is provided in advance. For SFlows carried on different member links, the protection reserved bandwidth can be shared, or the bandwidth can be independently reserved for each SFlows, and for SFlows on the same member link, the protection reserved bandwidth cannot be shared.
Further, the forwarding table entry configured by the link receiving end does not specify a specific member link position of a service flow in the aggregated link, and a data packet of a service flow received from any member link of the aggregated link is forwarded according to the configured corresponding forwarding entry. If the ingress port identifier in the receiving end forwarding table of the link receiving end is set to correspond to the entire aggregation link, the link receiving end can receive the traffic transmitted by each member link of the aggregation link by using the ingress port identifier. The purpose of this is to modify the forwarding table at the link sending end and not at the receiving end when the protection switching is performed due to failure, so as to simplify the configuration implementation and reduce the protection switching time.
Step S204: when the member link fails, the reserved bandwidth is invalid, or the bandwidth is not reserved, and whether effective residual idle bandwidth is available for transmitting the service transmitted on the failed member link is judged;
step S206: the effective residual idle bandwidth resources exist in the residual member links of the aggregation link, the service flows SFlows which are carried by the failed member link and need to be protected are transferred to the residual member links for transmission according to the priority, and a data forwarding table corresponding to the service flows is reconfigured at a sending end, so that the service flows influenced by the failure are quickly recovered and transmitted;
preferably, the SFlows with the highest priority is transferred to the remaining member links for transmission, so as to ensure the transmission of the high-priority traffic on the aggregated link.
For an SFlow, if the protection bandwidth resource is reserved in advance and the protection link thereof is not failed, switching the SFlow from the failed link to the protection link on which the protection bandwidth resource is reserved, as shown in the embodiment of the figure one; if the SFlow has no reserved protection bandwidth resource or the protection link also fails, it needs to apply for protection resource from the member link that has not failed yet and has the remaining idle bandwidth, and complete the switching. And if the residual idle bandwidth in all the non-failed member links is insufficient, preempting from other reserved protection resources with lower priority. In this way, the maximum possible guarantee is provided for the traffic transmission on the aggregated link.
Further, the protection switching may be performed in the following manner:
(1) when detecting the failure of the service flow transmitting direction, the packet node immediately executes switching and sends a switching notice to the opposite end, and the opposite end determines whether to execute switching for the SFlow in the same way or not according to the single-end switching/double-end switching configuration;
(2) when detecting the receiving direction fault of the service flow, the packet node immediately sends a fault notice to the opposite end, and determines whether to execute switching in the transmitting direction of the SFlow of the local end according to the single-end switching/double-end switching configuration, if so, the switching is carried out, and the switching information is added to the fault notice to realize the rapid protection switching;
(3) the packet node receives the fault notice of the opposite terminal and immediately starts the switching.
When protection switching is performed, the packet node may adopt a mode supporting multiple service priorities and a mode not supporting multiple service priorities. When the multiple service priorities are not supported, the SFlows passing through the aggregation link are treated equally when protection switching is carried out according to the sequencing of the bandwidth size and the bandwidths are the same; when supporting the service priority of the SFlows, when needing to protect the failed link to bear the SFlows, if the available bandwidth is not enough, the protection should be preferentially provided for the SFlows with high service priority, and the protection bandwidth resource reserved by the unused SFlows with low service priority can be preempted when the resource is insufficient.
The switching mode of the packet node can adopt one of the following two modes:
single-end switching, when one direction of the link detects a fault, only starting the switching of the transmitting end of the link;
double-end switching, when the link detects failure in the sending direction, starting the link sending end switching, and notifying the opposite end to switch the sending direction of the opposite end in the same way; the double-end switching ensures that the receiving and transmitting channels of the bidirectional SFlows are strictly consistent.
If the above measures fail, a notification needs to be initiated, and the process jumps to step S210.
Step S208: when the component link failure disappears, the link can be reused. And (4) determining to return from the protection link to the current link according to the attribute of 'return or not' of the SFlows, and not processing the non-returned SFlows.
And after the failure of the member link disappears, the original service is transmitted on the member link again, so that the transmission load of the protection link is reduced, and the transmission risk of the whole aggregation link is reduced.
Step S210: the remaining idle bandwidth of the remaining member link is not enough to support the protection of SFlows, and the protection fails, so that the control module corresponding to SFlows is notified, and the control module can take further measures for SFlows, such as rerouting, end-to-end switching, and the like.
Hereinafter, the aggregated link reservation protection resource according to the embodiment of the present invention will be described with reference to fig. 3 to 5.
Referring to fig. 3, a schematic diagram of a first aggregated link reserved protection resource according to an embodiment of the present invention is shown. The aggregation link reservation protection resource of this embodiment adopts a dedicated protection reservation mode, that is, a dedicated protection resource is reserved for each working SFlows.
As shown in FIG. 3, the aggregated Link2 includes four member links 2-1, Link2-2, Link2-3, and Link 2-4. The packet switching node a receives three service flows SFlow1, SFlow2 and SFlow 3. At this time, the packet switching node a or the upper management plane allocates an idle bandwidth of a member link to each service flow, as a reserved protection resource dedicated to the service flow, where the reserved protection resource is dedicated to one service flow and cannot be used by other service flows. For example, the packet switching node A or the upper management plane allocates idle bandwidth for SFlow1 on Link2-2 as the reserved protection resource of SFlow 1; allocating free bandwidth on Link2-3 for SFlow2 as reserved protection resources of SFlow 2; and allocating free bandwidth on Link2-4 for SFlow3 as reserved protection resources of SFlow 3.
Referring to fig. 4, a schematic diagram of a second aggregated link reserved protection resource according to an embodiment of the present invention is shown. The aggregation link reservation protection resource of this embodiment adopts a shared protection reservation manner, that is, for a plurality of different member links, a protection resource is reserved for one working SFlows on each member link, and the reserved protection resource is shared by the plurality of working SFlows of the plurality of different member links.
As shown in FIG. 4, the aggregated Link2 includes four member links 2-1, Link2-2, Link2-3, and Link 2-4. The packet switching node a receives three service flows SFlow1, SFlow2 and SFlow 3. At this time, the packet switching node a or the upper management plane allocates free bandwidth on the member Link2-2 for SFlow1, SFlow2, and SFlow3 as shared reserved protection resources of SFlow1, SFlow2, and SFlow3, which are commonly used by SFlow1, SFlow2, and SFlow 3.
Referring to fig. 5, a schematic diagram of a third aggregated link reserved protection resource according to an embodiment of the present invention is shown. The aggregation link reservation protection resource of this embodiment adopts a hybrid protection reservation manner, that is, for a plurality of different member links, a dedicated protection resource is reserved for the working SFlows on one or some of the member links, and a shared protection resource is reserved for the working SFlows on other member links. The hybrid protection reservation mode avoids excessive concentration of risks by limiting the sharing degree, and reserves other protection resources for subsequent SFlows when the sharing number exceeds a set value.
In this embodiment, the upper limit of the number of SFlows for setting the shared protection resource should not exceed 2, and SFlow1 and SFlow2 are set to share the protection resource, but SFlow3 cannot be shared any more, and the protection resource needs to be allocated independently.
As shown in FIG. 5, the aggregated Link2 includes four member links 2-1, Link2-2, Link2-3, and Link 2-4. The packet switching node a receives three service flows SFlow1, SFlow2 and SFlow 3. At this time, the packet switching node a or the upper management plane allocates the shared free bandwidth on the member Link2-2 for SFlow1 and SFlow2 as the shared reserved protection resource of SFlow1 and SFlow2, which is commonly used by SFlow1 and SFlow 2. Meanwhile, the packet switching node a or the upper management plane allocates a dedicated free bandwidth for SFlow3 on the member Link2-3 as a dedicated reserved protection resource for SFlow3, which is used only by SFlow 3.
The protection resource reservation strategy in the above embodiments all adopts the reservation of protection resources for all SFlows passing through the aggregated link, but the present invention is not limited to this strategy, and may also adopt a mode of reserving protection resources for SFlows with priority higher than or equal to a set value (such as a set value configured by a user), and not reserving protection resources for SFlows with priority lower than the set value.
Referring to fig. 6, a schematic diagram of aggregating link bearer traffic and reserving protection resources according to an embodiment of the present invention is shown.
In the embodiment, an aggregation Link2 is arranged between the packet switching node A and the packet switching node B, and the aggregation Link is composed of 3 physical member links 2-1, Link2-2 and Link 2-3. Assume in this embodiment that the current primary status information of the aggregated link consists of two sets of values:
Link2-1(20M，5M)、Link2-2(20M，10M)、Link2-3(20M，20M)；
Link2(20M)。
where Link2 is visible to other nodes in the network and where Link2-1 already carries part of the SFlows and where Link2-2 reserves guard bandwidth resources for these SFlows.
Firstly, SFlow1 (the CIR of the guaranteed bandwidth is 4M) is established in the network through distributed RSVP-TE signaling, Link2 is needed to be established through route calculation SFlow1, and in the process of establishing SFlow1 by adopting a distributed signaling mode, when the signaling reaches an aggregated Link endpoint, Link2-3 is selected according to the illustration in fig. 6, and the steps are as follows:
step S602: the SFlow1 establishes a signaling to reach the node A, and determines that the SFlow1 needs to pass through the Link2 according to the routing information carried by the signaling.
Step S604: according to the bandwidth information of the SFlow1, a member link needs to be selected as a bearing link of the member link, and necessary protection bandwidth resources are reserved for the member link; in order to balance the burden, Link2-3 is selected as a bearing Link of SFlow1, and 4M resources are reserved in Link2-2 member links to provide protection for SFlow 1.
After SFlow1 is assigned to the completer link, the aggregated link primary status information consists of two sets of values:
Link2-1(20M，5M)、Link2-2(20M，10M)、Link2-3(20M，16M)；
Llnk2(16M)。
since the protection resources can be shared by the LSPs passing through different member links, the protection bandwidth resources reserved on Link2-2 for the SFlows carried on Link2-1 are shared by SFlow1, and therefore the reserved bandwidth cannot be reduced.
Step S606: through RSVP-TE signaling interaction, all incoming labels and outgoing labels of SFlow1 passing through A, Z are determined, and A, Z nodes establish data forwarding table entries corresponding to the LSP. The forwarding table entry is shown in fig. 6. Where A denotes the start node of SFlow1 and Z denotes the target node of SFlow 1.
Wherein, the following steps are required: the forwarding table entry shown in fig. 6 does not constrain that received label 2 must be associated with a specific physical Link, e.g., at node B, ingress label 2 does not have Link2-3 association, which means that any packet received from any member Link in Link2 with label value 2 is forwarded from the physical port of Link 3. The purpose of this is to modify the forwarding table entry only at the sending end and keep the forwarding table entry unchanged at the receiving end during protection switching, so that member links do not need to be protected through signaling negotiation at both ends of the links, configuration implementation is simplified, and protection switching time is further reduced.
Referring to fig. 7, a schematic diagram of traffic protection after a member link failure of the aggregated link shown in fig. 6 is shown. The method comprises the following steps:
step S702: at node A, a member Link2-3 failure notification is received (for example, a Link2-3 remote alarm indication is received from a Link2-2 port), it is determined that the failed Link currently carries SFlow1, and the process proceeds to step S704. And if the fault link does not carry the SFlows, ending the process.
Step S704: at the node A, the protection bandwidth resources reserved for the SFlow1 on the Link2-2 are judged to be effective, the SFlow1 is switched to the Link2-2 for transmission, the forwarding table of the SFlow1 at the point A is modified, and the forwarding relation is switched from the Link2-3 to the Link-2, as shown in FIG. 7. And after the switching is finished, notifying the switching information of the node B.
At node B, the normal receive process SFlow1 data flow is still configured as the original data forwarding table. If the configuration is double-end switching, the reverse data stream of the SFlow1 is forwarded and modified according to the switching information sent by the a end, and is switched from Link-3 to Link-2, as shown in fig. 7.
After the protection switching is completed, the idle continuously available bandwidth of the current Link2 has become 10M.
Referring to fig. 8, a schematic diagram of traffic protection after a member link failure of another aggregated link shown in fig. 6 is shown. This embodiment is a process of preempting low priority protection resources by high priority SFlow in a switching process after a link failure.
In the embodiment, the SFlows carried by the aggregated Link have a higher-priority SFlow1 and a lower-priority SFlow2, and no other free bandwidth exists on the member Link2-1 except for the reserved protection resources.
Setting the aggregation link main state information as follows:
Link2-1(20M，3M)、Link2-2(20M，2M)、Link2-3(20M，2M)；
CIR of SFlow1 is 4M, and CIR of SFlow2 is 5M.
If the member link fails to cause the reserved protection resources to fail, the step of implementing the protection of the aggregation link is as follows:
step S802: at the node A, the failure notice of the member links Link2-2 and Link2-3 is received, the failure is determined to cause the failure of SFlow1 and SFlow2, and as the priority of the SFlow1 is higher, the priority processing is carried out, and the step S804 is carried out.
Step S804: during the processing, the reserved protection resources of the SFlow1 are found to be invalid, and then idle resources of other member links are searched for protection. Currently, only Link2-1 in the member Link is not failed, and the remaining bandwidth in Link2-1 is 3M, which is not enough to protect SFlow1(CIR ═ 4M), so that the protection switching is performed by preempting the reserved protection resources of SFlow 2. The switching success process SFlow2 proceeds to step S806.
Step S806: the reserved protection resources of SFlow2 are preempted, insufficient bandwidth is not found in the non-failed member link for protection, and rerouting (or other recovery measures) recovery service is initiated.
Fig. 9 is a flowchart of steps of a traffic protection method in an aggregated link according to another embodiment of the present invention, including the following steps:
step S902: the packet switching node detects the failure of the aggregation link;
step S904: the packet switching node searches a fault member link;
step S906: judging whether SFrows influenced by the failed member link exist, if so, turning to step S908, otherwise, turning to step S924;
step S908: judging whether the affected SFols reserve the protection bandwidth, if so, turning to the step S910, otherwise, turning to the step S914;
step S910: judging whether the reserved protection bandwidth is invalid or occupied, if so, turning to the step S912, and if not, turning to the step S916;
step S912: judging whether the link without the failed member has free bandwidth for providing protection, if so, turning to the step S914, otherwise, turning to the step S920;
step S914: selecting a proper member link as protection according to the requirements of bandwidth and the like, and executing step S916;
step S916: switching according to the designated protection link, retransmitting the forwarding table, and executing step S918;
step S918: carrying the switching information to notify the opposite terminal to switch, and executing step S924;
step S920: judging whether the reserved protection bandwidth of the low-priority SFlows is preempted, if so, executing a step S916, and if not, executing a step S922;
step S922: reporting failure of protection of the aggregated link to a control module of the sfrows, and executing step S924;
step S924: the process is ended.
Referring to fig. 10, a block diagram of a traffic protection device 100 in an aggregated link according to an embodiment of the present invention is shown, including:
a first determining module 1002, configured to detect that a working bandwidth transmission service of a first member link in an aggregated link fails; a second determining module 1004, configured to determine that a reserved bandwidth of the service of a second member link in the aggregated links is valid; and a protection module 1006, configured to continue to transmit the traffic using the reserved bandwidth of the second member link.
Preferably, the apparatus for protecting traffic of the aggregated link may further include: a third determining module 1008, configured to determine, when creating a service, that the priority of the service transmitted by the first member link is higher than or equal to the set priority; a reservation module 1010 for reserving bandwidth for the service on the second member link.
The technical scheme of the invention can be applied to any specific technical range such as MPLS, MPLS-TP, VLAN switching and the like. From the above description, it can be seen that the present invention implements efficient and flexible service flow protection in the aggregated link, and fully utilizes the remaining bandwidth in the aggregated link to protect QoS characteristic requirements such as the bandwidth of the service flow to the greatest extent.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (13)
1. A method for protecting traffic in an aggregated link, comprising:
detecting that a service transmitted by a working bandwidth of a first member link in the aggregated link fails, wherein each member link of the aggregated link is a backup link;
judging that the reserved bandwidth of the service of a second member link in the aggregated link is effective;
and continuing to transmit the service by using the reserved bandwidth of the second member link.
2. The method of claim 1, further comprising:
when a service is created, judging that the priority of the service transmitted by the first member link is higher than or equal to a set priority;
and selecting a second member link for the service and reserving bandwidth.
3. The method of claim 2, wherein the step of selecting a second member link and reserving bandwidth for the service comprises:
reserving bandwidth for the traffic transmitted on the first member link in an idle bandwidth of a second member link in the aggregated link;
or,
reserving a shared bandwidth for the traffic in a reserved bandwidth of other traffic of a second member link in the aggregated link.
4. The method of claim 2, further comprising:
when a service is created, judging that the priority of the service transmitted by the first member link is lower than a set priority;
no bandwidth is reserved for the traffic.
5. The method of claim 4, further comprising:
detecting that the traffic transmitted by a first member link in the aggregated link without reserved bandwidth fails;
judging that the second member link has residual idle bandwidth meeting the service bandwidth requirement of the unreserved bandwidth;
continuing to transmit the traffic using the remaining free bandwidth of the second member link.
6. The method of claim 1, further comprising:
judging the second member link failure;
judging that other member links have residual idle bandwidth meeting the bandwidth requirement of the transmission service;
and continuing to transmit the traffic by using the remaining idle bandwidth of the other member links.
7. The method of claim 1, further comprising:
judging the second member link failure;
judging that other member links are normal and the residual idle bandwidth which does not meet the bandwidth requirement of the transmission service is not available;
and occupying the reserved bandwidth of other services of the other member links, and continuously transmitting the services.
8. The method of claim 1, wherein the step of continuing to transmit the traffic using the reserved bandwidth of the second member link comprises:
the sending end of the service modifies the output port identification of the service in the sending end forwarding table of the service into the port identification corresponding to the second member link;
and transmitting the service to the receiving end of the transmission service by using the member link of the egress port indicated by the egress port identification.
9. The method of claim 8, further comprising:
when a service is created, a receiving end forwarding table of a receiving end of the service is set, an ingress port identifier in the receiving end forwarding table corresponds to the aggregation link, and the receiving end is instructed to receive the service transmitted by each member link of the aggregation link by using the ingress port identifier.
10. The method of claim 1, wherein the traffic transmitted over the first member link comprises a plurality of traffic, and the step of continuing to transmit the traffic using the reserved bandwidth of the second member link comprises:
and preferentially transmitting the service with high priority by using the reserved bandwidth of the second member link.
11. The method of claim 1, further comprising:
judging that the first member link is recovered to be normal;
judging whether the service returns to indicate yes;
and restoring the service to the first member link transmission.
12. A traffic protection device in an aggregated link, comprising:
the first judgment module is used for detecting that a working bandwidth transmission service of a first member link in the aggregation link fails, wherein each member link of the aggregation link is a backup link;
a second judging module, configured to judge that a reserved bandwidth of the service of a second member link in the aggregated link is valid;
and the protection module is used for continuously transmitting the service by using the reserved bandwidth of the second member link.
13. The apparatus of claim 12, further comprising:
the third judging module is used for judging that the priority of the service transmitted by the first member link is higher than or equal to the set priority when the service is established;
and the reservation module is used for reserving bandwidth for the service on the second member link.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010196424.1A CN102271048B (en) | 2010-06-02 | 2010-06-02 | Service protecting method in aggregated links and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010196424.1A CN102271048B (en) | 2010-06-02 | 2010-06-02 | Service protecting method in aggregated links and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102271048A CN102271048A (en) | 2011-12-07 |
| CN102271048B true CN102271048B (en) | 2015-08-12 |
Family
ID=45053219
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010196424.1A Expired - Fee Related CN102271048B (en) | 2010-06-02 | 2010-06-02 | Service protecting method in aggregated links and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102271048B (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103227994B (en) * | 2012-01-31 | 2018-09-04 | 中兴通讯股份有限公司 | The management method and system of shared resource |
| CN103312628B (en) * | 2012-03-16 | 2018-10-26 | 南京中兴软件有限责任公司 | The dispatching method and device of aggregated links in a kind of packet network |
| WO2012126412A2 (en) * | 2012-04-28 | 2012-09-27 | 华为技术有限公司 | Method, network device and system for ethernet ring protection switching |
| CN103731285B (en) * | 2012-10-11 | 2019-01-04 | 中兴通讯股份有限公司 | The switching handling method and device of distributed elastic network interconnection DRNI |
| CN104486124B (en) * | 2014-12-19 | 2018-09-04 | 盛科网络（苏州）有限公司 | The device and method of multisystem link aggregation is realized using logic port |
| CN105791108B (en) * | 2014-12-25 | 2019-07-12 | 中兴通讯股份有限公司 | A kind of method and device that the tunnel bandwidth based on bundle interface is reserved |
| US20180027571A1 (en) * | 2015-03-05 | 2018-01-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Resource Allocation Method, Control Entity and Access Node Using the Same |
| CN106411555B (en) * | 2015-08-03 | 2020-02-14 | 阿里巴巴集团控股有限公司 | Communication link configuration method, device and related system |
| CN105227456B (en) * | 2015-09-07 | 2019-03-08 | 浙江宇视科技有限公司 | A kind of aggregated link failures restore the method and device of transmission |
| CN108540380B (en) * | 2017-03-02 | 2021-08-20 | 华为技术有限公司 | Multi-sub-stream network transmission method and device |
| CN109309530B (en) * | 2017-07-28 | 2023-08-01 | 中兴通讯股份有限公司 | A data transmission method and device |
| CN112714036B (en) * | 2019-10-25 | 2023-02-28 | 中国移动通信集团有限公司 | Network quality measurement method, apparatus, device and medium for bundled link |
| CN111385144B (en) * | 2020-03-04 | 2022-04-15 | 苏州盛科通信股份有限公司 | Master and slave priority control method and device based on static link aggregation group |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101013995A (en) * | 2007-02-12 | 2007-08-08 | 华为技术有限公司 | Network node equipment, network system and tunnel establishment method |
| CN101340381A (en) * | 2008-08-04 | 2009-01-07 | 中兴通讯股份有限公司 | Aggregation link management method and apparatus |
| CN101656630A (en) * | 2009-09-09 | 2010-02-24 | 中兴通讯股份有限公司 | Service protection method and system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8472325B2 (en) * | 2007-05-10 | 2013-06-25 | Futurewei Technologies, Inc. | Network availability enhancement technique for packet transport networks |
| CN101132320B (en) * | 2007-09-18 | 2010-06-16 | 华为技术有限公司 | Method for detecting interface trouble and network node equipment |
-
2010
- 2010-06-02 CN CN201010196424.1A patent/CN102271048B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101013995A (en) * | 2007-02-12 | 2007-08-08 | 华为技术有限公司 | Network node equipment, network system and tunnel establishment method |
| CN101340381A (en) * | 2008-08-04 | 2009-01-07 | 中兴通讯股份有限公司 | Aggregation link management method and apparatus |
| CN101656630A (en) * | 2009-09-09 | 2010-02-24 | 中兴通讯股份有限公司 | Service protection method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102271048A (en) | 2011-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102271048B (en) | Service protecting method in aggregated links and device | |
| US10432514B2 (en) | Multiprotocol label switching traffic engineering tunnel establishing method and device | |
| US10250459B2 (en) | Bandwidth on-demand services in multiple layer networks | |
| US8767532B2 (en) | Optimization of distributed tunnel rerouting in a computer network with path computation at an intermediate node | |
| US7660254B2 (en) | Optimization of distributed tunnel rerouting in a computer network with coordinated head-end node path computation | |
| US9253097B1 (en) | Selective label switched path re-routing | |
| EP2624590B1 (en) | Method, apparatus and system for interconnected ring protection | |
| US20020116669A1 (en) | System and method for fault notification in a data communication network | |
| US20050007954A1 (en) | Network device and method for categorizing packet data flows and loading balancing for packet data flows | |
| US8477600B2 (en) | Composite transport functions | |
| EP1433287A4 (en) | PROTECTION IN A COMMUNICATION NETWORK WITH LABEL SWITCHING | |
| US20170310581A1 (en) | Communication Network, Communication Network Management Method, and Management System | |
| CN104753823B (en) | Establish the method and node of QoS reservation | |
| CN1731768A (en) | Method for forwarding traffic in a connectionless communication network | |
| WO2016101469A1 (en) | Method and apparatus for tunnel bandwidth reservation based on binding interface | |
| CN108092909A (en) | Data flow control method, apparatus and system | |
| JP2009519666A (en) | Resource sharing between network and tunnel | |
| CN103312628B (en) | The dispatching method and device of aggregated links in a kind of packet network | |
| Wang et al. | Reliability as an interdomain service | |
| CN102480411A (en) | Reservation method and system for protected bandwidth resources | |
| CN110892687B (en) | Multistage resource reservation | |
| CN102546199B (en) | A kind of guard method of aggregated links and Packet Switching Node | |
| Petersson | MPLS based recovery mechanisms | |
| CN109104367B (en) | Method, network equipment and system for establishing tunnel | |
| CN106453145B (en) | A transmission link control method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20150812 Termination date: 20170602 |