WO2012062101A1

WO2012062101A1 - Method and apparatus for controlling aggregated link warnings in packet switching network

Info

Publication number: WO2012062101A1
Application number: PCT/CN2011/074929
Authority: WO
Inventors: 陈皓
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-11-12
Filing date: 2011-05-30
Publication date: 2012-05-18
Also published as: CN102468973A

Abstract

Disclosed are a method and an apparatus for controlling aggregated link warnings in a packet switching network, which include: when a fault occurs in an aggregated link, determining whether there are available bandwidth resources in the aggregated link (001); when there are available bandwidth resources in the aggregated link, switching the service flow borne on a member link in which the fault occurs to the available bandwidth resources, wherein the member link is in the aggregated link (002); when there are no available bandwidth resources in the aggregated link, or the switching fails, notifying a corresponding control node of the fault information of the service flow (003). The invention enables flexible implementation of service flow protection in aggregated links, and improves efficiency of service protection.

Description

Aggregated link alarm control method and device in packet switching network

The present invention relates to a packet switching network, and more particularly to an aggregation link alarm control method and apparatus in a packet switching network. Background technique

With the increase of data traffic and the improvement of service quality requirements, multi-protocol label switching (MPLS, Multi-Protocol Label Switching), MPLS-TP (MPLS-Transport Profile), and operation have been adopted in packet-switched networks. Traffic engineering is implemented by technologies such as PBB (Provider Backbone Bridge), Virtual Office Area (I) or Virtual Local Area Network (VLAN) switching. Before the user data is transmitted, a service level agreement (SLA) is established according to the user's request, the data forwarding path is pre-configured through the control protocol, the bandwidth resource is allocated, and a service flow with bandwidth and other quality of service guarantee is formed, and the network is formed. When the resource status changes (link failure, network resource usage, etc.), the forwarding path of the service flow is further adjusted to meet the quality of service (QoS) requirements of the user. Therefore, the traffic engineering (TE, Traffic Engineering) technology is currently in the carrier. The application of the network is more and more extensive. High bandwidth and high availability are increasingly becoming the most important features of packet switched networks. Link aggregation is an important technology to meet high network availability and high bandwidth.

The link aggregation technology (described in IEEE 802.3ad) is to combine several physical links between two devices into one logical link (called an aggregate link), which is logically a link. Overall, it appears to the other device to be a link that masks the internal composition and details of the transmitted data.

Obviously, link aggregation technology can achieve the goal of simplifying network topology. In addition, the physical links inside the aggregation can jointly complete the data transmission and reception tasks and back up each other, as long as there is still a working function. On the link of the link, the data flow on the faulty link is switched to the link of other working members. The entire aggregated link will not be invalid, so that the protection service can be achieved within the aggregated link. At the same time, if the service flow is protected in other ways (outside the aggregation link) according to the result of the processing after the internal processing of the aggregation link is completed, it is necessary to delay some time and reduce the efficiency of the service protection.

Therefore, if a technology can be provided: When some member links fail in the aggregation link, the protection action is performed inside the aggregation link as much as possible, and the service flow protection is flexibly implemented; and the aggregation link is pre-determined. Whether the resource can satisfy the protection action, if not, promptly notify the control node/node to take other protection measures (such as dynamic rerouting) to protect the service flow, then the technology will be very useful in the packet switching network. Summary of the invention

In view of this, the main purpose of the present invention is to provide an aggregation link alarm control method and apparatus in a packet switching network, which can flexibly implement service flow protection in an aggregated link, and improve efficiency for service protection.

In order to achieve the above object, the technical solution of the present invention is implemented as follows:

The present invention provides an aggregate link alarm control method in a packet switching network, and the method includes:

When the aggregated link is faulty, it is determined whether there is a usable bandwidth resource in the aggregated link. When it is determined that the available bandwidth resource exists in the aggregated link, the member link that is faulty in the aggregated link is carried. The service flow is switched to the available bandwidth resource;

When it is determined that there is no available bandwidth resource in the aggregated link, or when the switching fails, the fault information of the service flow is notified to the corresponding control node.

Further, the service flow carried by the member link that fails in the aggregation link is switched to the available bandwidth resource, and specifically includes:

When the service flow is determined to have reserved protection bandwidth resources, the service flow is switched to the Reserve protection bandwidth resources;

Correspondingly, when the failover fails, the fault information of the service flow is advertised to the corresponding control node, and the method includes: when the service flow is switched over to the reserved protection bandwidth resource, the service flow is faulty. The information is advertised to the corresponding control node.

When it is determined that the service flow does not have the reserved protection bandwidth resource, the idle bandwidth resource is searched for in the member link that has not failed in the aggregation link, and the service flow is switched to the idle bandwidth resource;

Correspondingly, when the failover fails, the fault information of the service flow is advertised to the corresponding control node, and the method includes: when the service flow is failed to be switched over to the idle bandwidth resource, the fault information of the service flow is notified. Go to the corresponding control node.

When it is determined that the service flow does not have the reserved protection bandwidth resource, and the idle bandwidth resource is not found, the preemptive bandwidth resource is searched in the member link that has not failed in the aggregation link, and the service flow is switched. Go to the preemptible bandwidth resource;

Correspondingly, when the failover fails, the fault information of the service flow is advertised to the corresponding control node, and the method includes: when the service flow is switched over to the preemptible bandwidth resource, the fault information of the service flow is Advertise to the corresponding control node.

Further, when searching for a preemptible bandwidth resource in a member link that does not fail within the aggregation link, the following principles are met:

The bandwidth resources occupied by the service flow with the lowest priority of the member link that is not faulty are selected to be preempted; and when the priorities are the same, the bandwidth resources occupied by the service flow with the smallest granularity are selected for preemption; The priority of the service flow carried before the preemptible bandwidth resource is preempted is lower than the priority of the service flow;

The preemptible bandwidth is not less than the bandwidth required by the service flow.

Further, after the service flow is switched to the preemptible bandwidth resource, the method further includes:

The preempted information of the service flow carried before the preemptible bandwidth resource is preempted is advertised to the corresponding control node.

Further, when it is determined that there is no available bandwidth resource in the aggregated link, the fault information of the service flow is advertised to the corresponding control node, which specifically includes:

When it is determined that the service flow does not have the reserved protection bandwidth resource, the idle bandwidth resource is not found, and the preemptible bandwidth resource is not found, the fault information of the service flow is advertised to the corresponding control node.

Further, the load balancing algorithm is used to find idle bandwidth resources in the member links that have not failed within the aggregated link.

Further, when the aggregation link fails, the method further includes:

When the member link that fails in the aggregation link carries multiple service flows, the multiple service flows are polled in order from highest to lowest priority;

The polled service flow determines whether there are available bandwidth resources within the aggregated link.

The present invention also provides an aggregate link alarm control apparatus in a packet switching network, the apparatus comprising:

An analysis module, configured to determine whether a bandwidth resource is available in the aggregation link when the aggregation link fails;

a protection module, configured to switch, when the available bandwidth resources are available in the aggregation link, a service flow carried by the failed member link in the aggregation link to the available bandwidth resource; The alarm module is configured to notify the fault information of the service flow to the corresponding control node when there is no available bandwidth resource in the aggregated link, or when the switchover fails in the protection module.

Further, the analyzing module is further configured to determine that the service flow has a reserved protection bandwidth resource;

The protection module is further configured to: when the service flow has reserved protection bandwidth resources, switch the service flow to the reserved protection bandwidth resource;

Correspondingly, the alarm module is further configured to: when the protection module fails to switch the service flow to the reserved protection bandwidth resource, notify the fault information of the service flow to the corresponding control node.

Further, the analyzing module is further configured to: when the service flow does not have the reserved protection bandwidth resource, search for an idle bandwidth resource in a member link that does not fail in the aggregation link; When the service module does not have the reserved protection bandwidth resource, and the analysis module searches for the idle bandwidth resource, the service flow is switched to the idle bandwidth resource;

Correspondingly, the alarm module is further configured to notify the corresponding control node of the fault information of the service flow when the protection module fails to switch the service flow to the idle bandwidth resource.

Further, the analyzing module is further configured to: when the service flow does not have the reserved protection bandwidth resource, and the unused bandwidth resource is not found, look up in a member link that does not fail in the aggregation link. Seize bandwidth resources;

The protection module is further configured to: when the service flow does not have the reserved protection bandwidth resource, cannot find the idle bandwidth resource, and the analysis module finds a preemptible bandwidth resource, the service flow is switched to The preemptible bandwidth resource;

Correspondingly, the alarm module is further configured to: when the protection module fails to switch the service flow to the preemptible bandwidth resource, notify the fault information of the service flow to a corresponding control. Node.

Further, the alarm module is further configured to: when the service flow does not have the reserved protection bandwidth resource, cannot find the idle bandwidth resource, and cannot find the preemptible bandwidth resource, The fault information of the flow is advertised to the corresponding control node; and the preempted information of the service flow carried before the preemptible bandwidth resource is preempted is advertised to the corresponding control node.

The method for controlling the alarm of the aggregated link of the present invention: after the failure of one or more member links in the aggregated link, the alarm is suppressed as much as possible within the aggregated link, that is, the available for the bearer is found within the aggregated link as much as possible. The bandwidth resources of the service flow of the faulty link are reversed, such as the reserved protection bandwidth resource, the idle bandwidth resource in the member link that has not failed in the aggregation link, and the member link in the aggregation link that has not failed. The bandwidth resource can be preempted. In this way, the service flow protection can be flexibly implemented in the aggregated link. When it is determined that there is no available bandwidth resource in the aggregated link, or when the switching fails, the fault is alarmed.其他 Protecting business flows with other protection methods increases the efficiency of business protection.

In addition, when the resource part in the aggregation link is sufficient, the present invention makes a judgment on whether the demand can be satisfied by switching or preempting, that is, whether there is a usable resource (reserved protection bandwidth resource, no failure in the aggregation link) The idle bandwidth resource in the member link and the preemptible bandwidth resource in the member link that has not failed in the aggregated link); if there is a resource that can be used, the switching/preemption operation may be performed, if not, The resource used directly advertises the fault information of the service flow to the corresponding control node. It is determined in advance whether there is a resource that can be used. The advantage of this is that it can determine whether to transmit an alarm before the switching action is performed, instead of waiting for the switching result to decide whether to transmit the alarm, which greatly improves the speed of alarm transmission. DRAWINGS

1 is a flowchart of an aggregation link alarm control method in a packet switching network according to the present invention; FIG. 2 is a schematic diagram of an aggregation link alarm control method according to an embodiment of the present invention;

3 is a schematic diagram of an aggregated link; 4 is a schematic structural diagram of an aggregate link alarm control apparatus in a packet switching network according to the present invention. detailed description

The technical solutions of the present invention are further elaborated below in conjunction with the accompanying drawings and specific embodiments. The aggregation link alarm control method in the packet switching network of the present invention, as shown in FIG. 1, includes: Step 001: When the aggregation link fails, determining whether there is a bandwidth resource that can be used in the aggregation link;

Step 002: When the available bandwidth resources are stored in the aggregation link, the service flow carried by the failed member link in the aggregation link is switched to the available bandwidth resource.

Step 003: When there is no available bandwidth resource in the aggregated link, or when the switch fails, the fault information of the service flow is advertised to the corresponding control node.

The available bandwidth resources include: reserved protection bandwidth resources, idle bandwidth resources in the member links that have not failed in the aggregation link, and preemptible bandwidth resources in the member links that have not failed in the aggregation link. The specific implementation of switching and alarming is as follows:

When the service flow has the reserved protection bandwidth resource, the service flow is switched to the reserved protection bandwidth resource. Correspondingly, when the service flow fails to be forwarded to the reserved protection bandwidth resource, the service flow failure information is notified to the corresponding control. Node

When the service flow does not reserve the protection bandwidth resource, the idle bandwidth resource is searched for in the member link that has not failed in the aggregation link, and the service flow is switched to the idle bandwidth resource; correspondingly, the service flow is switched to the idle bandwidth resource. When the failure occurs, the fault information of the service flow is notified to the corresponding control node;

If the service flow does not reserve the protection bandwidth resource and the idle bandwidth resource is not found, the pre-emptive bandwidth resource is searched for in the member link that has not failed in the aggregation link, and the service flow is switched to the preemptible bandwidth resource; When the service flow is failed to be switched to the preemptible bandwidth resource, the fault information of the service flow is notified to the corresponding control node;

The service flow does not reserve protection bandwidth resources, cannot find idle bandwidth resources, and cannot find When the bandwidth resource can be preempted, the fault information of the service flow is advertised to the corresponding control node.

In addition, after the service flow is switched to the preemptible bandwidth resource, the preempted information of the service flow carried before the preemptible bandwidth resource is preempted is also advertised to the corresponding control node.

As shown in FIG. 2, the aggregation link alarm control method in the packet switching network of the present invention includes the following steps:

Step 101: One or more member links in the aggregation link are faulty.

Step 102: Determine whether there is a service flow that needs to be protected. If yes, go to step 103. If no, go to step 116.

When one or more member links in the aggregation link are faulty, all service flows carried on the failed member link are polled, and after the service flow that needs to be protected is found, the service flow is processed, and the process proceeds to step 103; When the service flow is not carried on the faulty member link, the process proceeds to step 116.

It should be noted that when one or more member links in the aggregation link are faulty, multiple service flows that need to be protected may be found. When processing the multiple service flows, they need to be in a certain order. The service flow with higher priority is prioritized according to the order of priority of the service flow.

Further, two service flows of the same priority may be processed in descending order of granularity.

The protection process for the service flow that needs to be protected is as described in steps 103-114.

Step 103: Determine whether the service flow currently performing protection processing has reserved protection bandwidth resources. If yes, go to step 104. If no, go to step 108.

Step 104: If the service flow of the current protection process has the reserved protection bandwidth resource, determine whether the member link of the protection bandwidth resource is invalid. If the failure occurs, go to step 108. If no failure occurs, go to step 105.

Step 105: Perform a switching, and switch the service flow currently performing protection processing to the reserved protection bandwidth resource. Step 106: Determine whether the switching performed by step 105 is successful. If successful, execute step 115. If it fails, perform step 107 to notify the corresponding control node/node of the fault information of the service flow currently performing protection processing. The /node may perform a protection action such as dynamic reroute recovery on the service flow, and then step 115 is performed.

In step 108, the process proceeds to step 103. When the service flow that is currently performing the protection process does not reserve the protection bandwidth resource, the idle bandwidth resource is searched for in the member link that is not faulty. For example, according to the load balancing algorithm, the member link that is not invalid is selected. A most reasonable member link. The member link has enough free bandwidth resources to carry the service flow currently being protected.

In step 109, it is determined whether the idle bandwidth resource is found. If yes, step 105 is performed to switch the service flow currently performing protection processing to the idle bandwidth resource, and then step 106 is performed, and details are not described herein; For protection resources, go to step 110.

Step 110: Search for a preemptible bandwidth resource in the member link that is not faulty. When you choose to preempt bandwidth resources, you need to follow these guidelines:

1. The bandwidth resource occupied by the lowest-priority service flow carried by the member link that has not failed is selected for preemption;

2. When the service flows have the same priority, the bandwidth resources occupied by the service flow with the smallest granularity are selected for preemption;

3. The priority of the service flow carried by the preempted bandwidth resource is lower than the priority of the current service flow for protection processing;

4. The preempted bandwidth is not less than the bandwidth required for the service flow currently being protected.

The bandwidth resource selected according to the above principle is the preemptible bandwidth resource.

Step 111: Determine whether the preemptible bandwidth resource is found. If no, proceed to step 107 to notify the corresponding control node/node of the fault information of the service flow currently performing the protection process, and then the control node/node may serve the service flow. Perform a protection action such as dynamic reroute recovery, and then perform step 115; if yes, proceed to step 112. Step 112: Perform preemption, and when the preemptible bandwidth resource is found, the service flow currently performing protection processing preempts (ie, occupies) the resource.

Step 113: Determine whether the preemption is successful. If the success is successful, perform step 114, and perform a protection action such as dynamic rerouting recovery on the service flow (that is, the preempted service flow) carried before the preemptible bandwidth resource. Therefore, the preemption needs to be preempted. If the preemption information is advertised to the control node/node, then step 115 is performed; The node may perform a protection action such as dynamic reroute recovery on the service flow, and then perform step 115;

Step 115: Determine whether the processing of all service flows that need to be protected is completed. If yes, execute step 116. If no, return to step 103.

Step 116: Update and flood the bandwidth information of the aggregated link.

In addition, after the failed member link is restored, if the service flow carried by the member link has the returned attribute, the service flow is re-switched to the member link; otherwise, no processing is performed.

The above technical solution of the present invention will be further described in detail below with reference to the accompanying drawings. In an embodiment of the invention, one service flow is not allowed to be transmitted simultaneously across multiple member links.

Figure 3 shows that there is an aggregate link Linkl between node A and node B. The aggregate link consists of three physical member links Linkl-1, Linkl-2, and Link 1-3, where each member link The bandwidth is 20M.

Embodiment 1 Assume that the service flow carried by each member link of Linkl before the fault is as shown in Table 1, where "Service Flow 4-R" indicates the reserved protection bandwidth of Service Flow 4.

Member Link Linkl -1 Link 1-2 Linkl -3

Total bandwidth 20M 20M 20M

Free bandwidth 10M 5M 5M Bearer Service Flow Service Flow 1 Service Flow 2 Service Flow 3 Service Flow 4-R Service Flow 4 Service Flow 5 and Occupied Bandwidth 5M 5M 10M 5M 5M 10M Service Flow Priority 2 2 2 1 2

Table 1

Among them, the smaller the priority value, the higher the priority, so that the service flow 4 has the highest priority.

When the member link Linkl-3 fails:

First, the service flow carried by the member link Linkl-3, that is, the service flow that needs to be protected, is searched according to the service flow priority. The service flow 4 has a higher priority than the service flow 5, so the service flow 4 is processed first.

As shown in Table 1, the service flow 4 has 5M reserved protection bandwidth resources in the member link Linkl-2, which is sufficient to carry the service flow 4. Therefore, the service flow 4 carried by the faulty member link Linkl-3 is performed. Switch to its reserved protection bandwidth resource on Linkl-2.

The switching method can take one of the following two ways:

Single-ended switching. When a fault is detected in one direction of the link, only the link originating switch is started.

After the link detects the fault in the sending direction, the link initiates the switch to initiate the switchover, and the peer end advertises that the peer sends the same direction. The meaning of the double-ended switchover is that the two-way service flow is strictly consistent. ).

The specific implementation of the single-ended switching and the double-ended switching is the prior art, and details are not described herein again.

After the switchover process is successfully executed, find the next service flow that needs to be protected, that is, service flow 5.

Since service flow 5 does not reserve protection bandwidth resources, it first searches for idle bandwidth resources in link nodes (Linkl-1, Linkl-2); finds 10M idle bandwidth resources in Linkl-1, which is sufficient to carry services. Flow 5, the switching process can be performed, and the service flow 5 is switched to the 10M idle bandwidth resource of Linkl-1. After the execution of the switching process is completed, it is found that all the service flows carried by the failed member link have been polled, so the current bandwidth information of the aggregated link is updated and flooded. As shown in table 2:

Table 2

Embodiment 2: In the scenario of the first embodiment, after the member link Linkl-3 fails and is processed according to the first embodiment, the service flows carried by the member links of the aggregated link Link1 are as shown in Table 2. Show.

At this point, the member link Linkl-2 also failed:

First, the service flow carried by the member link Linkl-2 is searched according to the service flow priority. The service flow 4 has a higher priority than the service flow 3, so the service flow 4 is processed first.

In the first embodiment, the service flow 4 has occupied the reserved protection bandwidth resource, and there is no other reserved protection bandwidth resource. Therefore, the idle bandwidth resource is searched for in the unfailed member link, that is, Linkl-1. There is no free bandwidth resource in the aggregated link. Therefore, the preemptible bandwidth resources are searched in the aggregated link according to the order of the priority of the service flows: Service flow 1 and service flow 2 in the member link Linkl-1 And the priority of the service flow 5 is lower than the priority of the service flow 4, the service flow 1, the bandwidth occupied by the service flow 2 is 5M equal to the bandwidth required by the service 4, and the bandwidth occupied by the service flow 5 is 10M larger than the service 4 Bandwidth is required, where service stream 1 has the smallest granularity. The granularity of the service flow generally refers to the size of the resources occupied by the service flow. In this embodiment, the granularity of the service flow 1 and the service flow 2 is smaller than the service flow 5, thus selecting the service flow 1 or 2; in the case where the granularity of the service flow 1 and the service flow 2 are the same, the service flow 1 and the service The selection between the streams 2 is not strictly limited. In the embodiment of the present invention, the service stream having a small service stream ID is preferentially selected with all the conditions being equal, and thus the service stream 1 is selected here. Therefore, service Stream 4 preempts the bandwidth resources occupied by service stream 1.

After the preemption is performed, the information that the service flow 1 is preempted needs to be advertised to its control node/node, and the control node/node performs the next protection action of the service flow 1, such as dynamic rerouting.

After the service flow 4 is processed, the next service flow that needs to be protected, that is, the service flow 3 is found.

Since the service flow 3 does not reserve the protection bandwidth resource, the idle bandwidth resource is searched for in the link node that is not faulty, that is, Linkl-1. At this time, there is no idle bandwidth resource in the aggregation link. Therefore, according to the service flow priority Find the preemptible bandwidth resources in the aggregated link from low to high: Since the priority of service flow 4 in the member link Linkl-1 is higher than 1 for service flow 3, service flow 2 and service flow 5 Level 2 is equal to service flow 3, so there is no preemption of bandwidth resources.

Therefore, it can be determined that the service flow 3 cannot be protected within the aggregated link, and the fault information is immediately notified to the control node/node of the service flow 3, and the control node/node performs the next protection action of the service flow 3, such as dynamic Rerouting, etc.

It is found that all the service flows carried by the faulty member link have been polled, so the current link bandwidth information is updated and flooded, as shown in Table 3:

table 3

Embodiment 3 Assume that in the present embodiment, the service flows carried by the member links of the Linked Link before the fault are as shown in Table 4: Member Link Linkl-1 Link 1-2 Linkl -3

Total bandwidth 20M 20M 20M

Free bandwidth 5M 0M 5M

Hosted Service Flow Service Flow 1 Service Flow 2 Service Flow 3 Service Flow 4 Service Flow 5 and Occupied Bandwidth 5M 10M 20M 5M 10M Service flow priority 3 3 2 1 2

Table 4

Among them, the smaller the priority value, the higher the priority.

When member links Link 1-3 fail,

As shown in Table 4, the service flow 4 does not reserve the reserved bandwidth resources. Therefore, the idle bandwidth resources are searched for in the unfailed member links (Linkl-1, Link 1-2), and the member link Linkl-1 has 5M idle. The bandwidth resource is sufficient to carry the service flow 4 and perform the switching process.

Since the service flow 5 does not reserve the reserved bandwidth resource, the idle bandwidth resource is searched for in the link node (Linkl-1, Linkl-2) that is not faulty. The priority of the service line 1 and the service flow 2 in the member link Linkl-1 is 3, which is lower than the priority of the service flow 5, in the order of the priority of the priority of the service flow. The bandwidth occupied by the service flow 1 is 5M smaller than the bandwidth required by the service flow 5. The bandwidth occupied by the service flow 2 is 10M equal to the bandwidth required by the service flow 5. Therefore, the service flow 5 immediately preempts the bandwidth resources occupied by the service flow 2.

After the preemption is performed, the information that the service flow 2 is preempted needs to be notified to the control node/node, and the control node/node performs the next protection action of the service flow 2, such as dynamic rerouting.

After the polling process all the service flows carried by the faulty member link, the current bandwidth information of the aggregated link is updated and flooded, as shown in Table 5:

Member Link Linkl-1 Linkl-2 Linkl-3 Total Bandwidth 20M 20M 20M Free Bandwidth 5M 0M 0M Bearer Service Flow Moon Service Flow 1 Λ Good Service Flow 5 Λ Good Service Flow 4 Service Flow 3 And occupied bandwidth 5M 10M 5M 20M

Service flow priority 3 2 1 2

table 5

Embodiment 4 Assume that, in this embodiment, the service flows carried by the member links of the aggregated link Link1 before the fault are as shown in Table 6:

Table 6

When the member link Linkl-3 fails:

First, the service flow carried by the member link Linkl-3, that is, the service flow that needs to be protected, is searched according to the service flow priority. The member link Linkl-3 only carries the service flow 4, and thus the service flow 4 is processed.

It can be seen from Table 6 that the service flow 4 does not reserve the reserved bandwidth resources, so the idle bandwidth resources are searched for in the unfailed member links (Linkl-1, Linkl-2), because there is not enough idleness in the aggregated link at this time. The bandwidth resource is used to carry the service flow 4. Therefore, the preemptible bandwidth resource is searched according to the order of priority from low to high. Since the service flow 1, the service flow 2, the service flow 3, and the service flow 4 have the same priority, there is no Can grab bandwidth resources.

It can be determined that the service flow 4 cannot be protected within the aggregated link, and the fault information is immediately reported to the control node/node of the service flow 4, and the next protection action, such as dynamic rerouting, is performed. Since the bandwidth information has not changed, the flooding bandwidth information operation is not required.

In order to implement the foregoing alarm control method, the present invention further provides a convergence link alarm control apparatus in a packet switching network. As shown in FIG. 4, the apparatus includes:

An analysis module, configured to determine whether there is a usable bandwidth resource in the aggregation link when the aggregation link fails; a protection module, configured to switch the service flow carried by the failed member link in the aggregation link to the available bandwidth resource when the available bandwidth resource exists in the aggregation link;

The alarm module is configured to notify the fault information of the service flow to the corresponding control node when there is no available bandwidth resource in the aggregated link, or when the switchover fails in the protection module.

Specifically, the analysis module is further configured to: determine that the service flow has a reserved protection bandwidth resource; and the protection module is further configured to: when the service flow has the reserved protection bandwidth resource, switch the service flow to the reserved protection bandwidth resource;

Correspondingly, the alarm module is further configured to notify the fault information of the service flow to the corresponding control node when the protection module fails to switch the service flow to the reserved protection bandwidth resource.

The analysis module is further configured to: when the service flow does not reserve the protection bandwidth resource, search for the idle bandwidth resource in the member link that does not fail in the aggregation link;

The protection module is further configured to: when the service module finds the idle bandwidth resource, the service flow is switched to the idle bandwidth resource;

The analysis module is further configured to search for a preemptible bandwidth resource in a member link that has not failed in the aggregation link when the service flow does not reserve the protection bandwidth resource and the idle bandwidth resource is not found; the protection module is also used in The service flow does not reserve the protection bandwidth resource, and the idle bandwidth resource cannot be found. When the analysis module finds the preemptible bandwidth resource, the service flow is switched to the preemptible bandwidth resource.

Correspondingly, the alarm module is further configured to notify the fault information of the service flow to the corresponding control node when the protection module fails to switch the service flow to the preemptible bandwidth resource.

The alarm module is further configured to: when the service flow does not reserve the reserved bandwidth resource, the idle bandwidth resource is not found, and the preemptible bandwidth resource is not found, the fault information of the service flow is notified to the corresponding control node; Preemption of the service flow carried before the preempted bandwidth resource is preempted The information is advertised to the corresponding control node.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for controlling an aggregate link alarm in a packet switching network, the method comprising:

The aggregation link alarm control method in the packet switching network according to claim 1, wherein the service flow carried by the failed member link in the aggregation link is switched to the usable bandwidth Resources include:

And determining, when the service flow has a reserved protection bandwidth resource, switching the service flow to the reserved protection bandwidth resource;

The aggregation link alarm control method in the packet switching network according to claim 2, wherein the service flow carried by the failed member link in the aggregation link is switched to the usable bandwidth Resources include:

The aggregated link alarm control method in the packet switching network according to claim 3, wherein the service flow carried by the failed member link in the aggregated link is switched to the usable bandwidth Resources include:

The method for controlling an aggregated link alarm in a packet switching network according to claim 4, wherein, when searching for a preemptible bandwidth resource in a member link that has not failed in the aggregated link, the following principles are met:

Selecting the bandwidth resource occupied by the service flow with the lowest priority of the member link that is not faulty to be preempted; and when the priority is the same, the bandwidth resource occupied by the service flow with the smallest granularity is selected for preemption;

The priority of the service flow carried before the preemptible bandwidth resource is preempted is lower than the priority of the service flow;

The aggregated link alarm control method in the packet switching network according to claim 4, wherein after the service flow is switched over the preemptible bandwidth resource, the method further includes: preempting the preemptible The preempted information of the service flow carried by the bandwidth resource before being preempted is advertised to the corresponding control node.

The method for controlling an aggregated link alarm in a packet switching network according to claim 2, 3 or 4, wherein when the available bandwidth resource is not present in the aggregated link, the fault information of the service flow is determined. The notification to the corresponding control node specifically includes: And determining that the service flow does not have the reserved protection bandwidth resource, cannot find the idle bandwidth resource, and cannot find the preemptible bandwidth resource, and notify the corresponding control node of the fault information of the service flow.

8. The aggregate link alarm control method in a packet switching network according to claim 3, wherein the load balancing algorithm is used to find an idle bandwidth resource in a member link in the aggregated link that has not failed.

The aggregation link alarm control method in the packet switching network according to claim 1, wherein when the aggregation link fails, the method further includes:

10. An aggregate link alarm control apparatus in a packet switching network, the apparatus comprising:

a protection module, configured to switch a service flow carried by a failed member link in the aggregation link to the available bandwidth resource when a bandwidth resource is available in the aggregation link;

11. The aggregate link alarm control apparatus in a packet switching network according to claim 10, wherein:

The analyzing module is further configured to: determine that the service flow has a reserved protection bandwidth resource; and the protection module is further configured to: when the service flow has a reserved protection bandwidth resource, switch the service flow to the Reserve protection bandwidth resources; Correspondingly, the alarm module is further configured to: when the protection module fails to switch the service flow to the reserved protection bandwidth resource, notify the fault information of the service flow to the corresponding control node.

12. The aggregate link alarm control apparatus in a packet switching network according to claim 11, wherein:

The analyzing module is further configured to: when the service flow does not have the reserved protection bandwidth resource, search for an idle bandwidth resource in a member link that does not fail in the aggregation link;

The protection module is further configured to: when the service module does not have the reserved protection bandwidth resource, when the analysis module finds an idle bandwidth resource, the service flow is switched to the idle bandwidth resource;

13. The aggregate link alarm control apparatus in a packet switching network according to claim 12, wherein:

The analyzing module is further configured to: when the service flow does not have the reserved protection bandwidth resource and cannot find the idle bandwidth resource, search for a preemptible bandwidth resource in a member link that does not fail in the aggregation link. ;

Correspondingly, the alarm module is further configured to: when the protection module fails to switch the service flow to the preemptible bandwidth resource, notify the fault information of the service flow to the corresponding control node.

14. The aggregate link alarm control in the packet switching network according to claim 11, 12 or 13. Device, characterized in that

The alarm module is further configured to: when the service flow does not have the reserved protection bandwidth resource, cannot find the idle bandwidth resource, and cannot find the preemptible bandwidth resource, fail the service flow. The information is advertised to the corresponding control node; and is used to notify the corresponding control node of the preempted information of the service flow carried before the preemptible bandwidth resource is preempted.