WO2012068834A1

WO2012068834A1 - Method and system for managing aggregation link

Info

Publication number: WO2012068834A1
Application number: PCT/CN2011/073929
Authority: WO
Inventors: 吴建红; 孙德胜; 杨发明
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-11-25
Filing date: 2011-05-11
Publication date: 2012-05-31
Also published as: CN102480377B; CN102480377A

Abstract

A method for managing an aggregation link is provided by the present invention. After receiving the request for configuring the aggregation link, the aggregation control module of the control plane judges the type of the configuration operation according to the request for configuring the aggregation link, wherein the request for configuring the aggregation link is a static request or a dynamic request; the aggregation control module performs the corresponding configuration operation to the aggregation link according to the type of the configuration operation and the configuration situation of the service flow of the aggregation link to which the configuration operation relates. A system for managing the aggregation link is provided by the present invention accordingly. With the present invention, the dynamic management for the aggregation link can be implemented.

Description

Method and system for managing aggregated links

The present invention relates to a packet switching network, and in particular, to a method and system for managing an aggregated link. Background technique

As data traffic grows and service quality requirements increase, high bandwidth provides an increasingly important feature of packet switching networks. Link aggregation is an important technology to meet the high bandwidth requirements of the network. The link aggregation technology (described in IEEE 802.3ad) is to combine several physical links (or data links) between two devices into one logical link (also called an aggregate link). The link is logically a whole, and the internal composition and details of the transmitted data are transparent to the upper layer service.

In the packet switching network, Multi-Protocol Label Switching (MPLS), MPLS-TP (MPLS-Transport Profile), Carrier Backbone Bridge (PBB), and Virtual Office i are currently used. Traffic Engineering (TE) is implemented in technologies such as Virtual Local Area Network (VLAN) switching. According to the current TE traffic engineering technology, the control plane and the data plane are separated. Before transmitting user data, the service provider first establishes a Service Level Agreement (SLA) according to the user requirements, and the SLA includes satisfying the user service quality (QoS, Quality of Service) The bandwidth parameters of different service flows required by the control plane, and the control plane configures the forwarding path of the service flow to the data plane according to the bandwidth parameters of different service flows determined in advance and the current network resource usage status, and the resource usage status of the network. When the change occurs (such as the deletion or addition of the LSP ( Label Switched Path), the increase or decrease of the network link, etc.), the forwarding path of the existing service flow is further modified and the data plane is notified, and the data plane receives the service flow data packet according to the control. The forwarding path of the plane configuration performs data forwarding, thereby ensuring the QoS requirements of the user service flow and optimizing the network resources. The use of the source, therefore, TE traffic engineering technology is now more and more widely used in the operator network. Since service providers need to charge different bandwidths for different users, "pre-planning to determine service flow bandwidth parameters" is a must, and is one of the important features of TE traffic engineering technology. Further, if the control plane can make full use of it This feature effectively controls the distribution of different service flows on the member links of the aggregated link according to the predetermined service flow bandwidth, implements link aggregation, and solves the problem that link aggregation technology cannot solve link congestion. Disadvantages, then the link aggregation control technology will be very useful in the packet switching network; for the convenience of description, all relevant technologies on the aggregation link are collectively referred to herein as TE-Tmnk technology.

However, for the TE-Tmnk technology, most of the existing technologies only describe how to perform control processing once the aggregated link fails or is congested, and the existing link aggregation technology cannot configure the service flow forwarding path. Dynamic adjustment on the aggregated link. In other words, the prior art lacks how to describe how the aggregated link is implemented and how to aggregate the aggregated link of the configured service flow. Therefore, how to effectively manage these aggregated links dynamically It seems quite important. Summary of the invention

In view of this, the main object of the present invention is to provide a method and system for managing an aggregated link, which can implement dynamic management of an aggregated link.

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

A method for managing an aggregated link includes:

After receiving the request for configuring the aggregated link, the control plane of the control plane determines the type of the configuration operation according to the request for configuring the aggregated link, where the request for configuring the aggregated link is a static request or a dynamic request;

The aggregation control module performs a corresponding configuration operation on the aggregated link according to the operation type of the configuration operation and the service flow configuration of the aggregated link involved in the configuration operation.

The request for configuring the aggregated link carries: operation type, aggregated link identifier, and each member The identity of the link and its available bandwidth;

The operation types include: a new operation, a delete operation, and a modification operation.

When the operation type of the configuration operation is a new operation, the aggregation control module performs corresponding configuration operations on the aggregation link according to the configuration of the service flow of the aggregation link involved in the configuration operation:

a. determining whether a new aggregated link needs to be generated. If yes, a new aggregated link is formed, and the newly added data link is configured as a member of the aggregated link according to the request for configuring the aggregated link. Go to step c; otherwise, the member link needs to be added to the aggregated link, and the newly added data link is configured as a member of the aggregated link according to the request for configuring the aggregated link, and the process proceeds to step b;

And determining, by the policy control module, a control policy, the policy control module performs the control policy according to the control policy, if the forwarding path of the service flow is configured on the aggregation link, and the forwarding path of the service flow is configured on the aggregation link. Controlling or redistributing the service flow, when the service path of the service flow is changed, the policy control module sends the configuration to the data plane according to the scheduling result of the policy, and feeds the configuration result to the aggregation control module;

c. The aggregation control module notifies the configuration result to other modules or management planes of the control plane. When the operation type of the configuration operation is a deletion operation, the aggregation control module performs corresponding configuration operations on the aggregation link according to the configuration of the service flow of the aggregation link involved in the configuration operation:

And determining whether the service flow is carried on the aggregation link involved in the deletion operation, and the service flow is carried on the aggregation link involved in the deletion operation, and then the process proceeds to step e; if the service flow is not carried on the aggregation link involved in the deletion operation, The member link is directly removed from the aggregated link according to the request for configuring the aggregated link;

e. Determine whether to exclude the member link to be deleted, whether there are enough resources on the aggregated link to carry the service flow on the deleted member link, if there are sufficient resources, go to step f; If sufficient resources are available, the aggregation control module notifies the other modules or management planes of the control plane that the deletion fails.

f. The aggregation control module obtains a control policy from the policy control module, and the policy control module performs control or redistribution of the service flow according to the control policy. If the service path of the service flow changes, the configuration is delivered to the data plane according to the scheduling result of the policy, and Feeding the result to the aggregation control module; then, the aggregation control module notifies the configuration result to other modules or management planes of the control plane, and moves the member link from the aggregation link according to the request for configuring the aggregation link. except.

After the member link is removed from the aggregated link, the method further includes: determining whether a member link exists in the aggregated link, and deleting the aggregated link when no member link exists.

When the operation type of the configuration operation is a modification operation, the aggregation control module performs corresponding configuration operations on the aggregation link according to the configuration of the service flow of the aggregation link involved in the configuration operation:

g. Determine whether the aggregation link of the service operation is configured with the forwarding path of the service flow, and if the forwarding path of the service flow is configured, go to step h; if the forwarding path of the service flow is not configured, the aggregation control module directly modifies the aggregation link. Attribute

The aggregation control module requests the policy control module to perform the scheduling, and transfers the service flow carried on the aggregation link related to the modification operation to another aggregation link. After the policy control module returns the result, the attribute of the aggregation link is modified.

An aggregation link management system, including an aggregation control module of a control plane, configured to determine a type of a configuration operation according to the request for configuring an aggregated link after receiving a request for configuring an aggregated link, where the configuration aggregation chain The request of the route is a static request or a dynamic request; and the corresponding configuration operation is performed on the aggregated link according to the operation type of the configuration operation and the service flow configuration of the aggregated link involved in the configuration operation.

The system further includes a policy control module of the control plane. When the operation type of the configuration operation is a new operation, the aggregation control module configures the service flow of the aggregated link according to the configuration operation. The corresponding configuration operations on the aggregated link are as follows:

a, determining whether a new aggregated link needs to be generated, and if so, forming a new aggregated link, and configuring the newly added data link as a member of the aggregated link according to the request for configuring the aggregated link. Go to step c'; otherwise, you need to add a member link to the aggregated link, and configure the newly added data link as a member of the aggregated link according to the request to configure the aggregated link. Go to step b';

And determining, by the policy control module, the control policy, the policy control module according to the control policy, determining whether the aggregation link has been configured with a forwarding path of the service flow, and the aggregation link has configured a forwarding path of the service flow. When the service flow is controlled or redistributed, and the service path of the service flow is changed, the policy control module sends the configuration to the data plane according to the scheduling result of the policy, and feeds the configuration result to the aggregation control module;

c', the aggregation control module notifies the configuration result to other modules or management planes of the control plane. The system further includes a policy control module of the control plane, and when the operation type of the configuration operation is a delete operation, the aggregation control module performs corresponding configuration operations on the aggregated link according to the service flow configuration of the aggregated link involved in the configuration operation. For:

And determining whether the service flow is carried on the aggregation link involved in the deletion operation, and the service flow is carried on the aggregation link involved in the deletion operation, and then the process proceeds to step e'; the service flow is not carried on the aggregation link involved in the deletion operation. And removing the member link from the aggregated link according to the request for configuring the aggregated link;

e', judging to exclude the member link to be deleted, whether there are enough resources on the aggregated link to carry the service flow on the deleted member link, if there are sufficient resources, go to step f; there is not enough resources, The aggregation control module notifies the other modules of the control plane or the management plane that the deletion fails.

f. The aggregation control module acquires a control policy from the policy control module, and the policy control module controls or redistributes the service flow according to the control policy. If the service path of the service flow changes, The scheduling result of the policy is delivered to the data plane, and the result is fed back to the aggregation control module. After that, the aggregation control module notifies the configuration result to other modules or management planes of the control plane, and according to the request of the configuration aggregation link The member link is removed from the aggregated link.

The aggregation control module is further configured to: after the member link is removed from the aggregation link, determine whether a member link exists in the aggregation link, and if no member link exists, delete the aggregation link. .

The system further includes a policy control module of the control plane. When the operation type of the configuration operation is a modification operation, the aggregation control module performs corresponding configuration operations on the aggregated link according to the service flow configuration of the aggregated link involved in the configuration operation. For:

g', determining whether the aggregation link of the modification operation is configured with the forwarding path of the service flow, and configuring the forwarding path of the service flow to go to step h'; if the forwarding path of the service flow is not configured, the aggregation control module directly modifies the aggregation The properties of the link;

h'. The aggregation control module requests the policy control module to perform scheduling, and transfers the service flow carried on the aggregation link related to the modification operation to another aggregation link. After the policy control module returns the result, the attribute of the aggregation link is modified.

The method and system for managing the aggregated link of the present invention, after receiving the request for configuring the aggregated link, the aggregation control module of the control plane determines the type of the configuration operation according to the request for configuring the aggregated link; And configuring the service flow of the aggregated link involved in the configuration operation to perform corresponding configuration operations on the aggregated link. According to the present invention, dynamic management of the aggregated link can be implemented. DRAWINGS

1 is a schematic flowchart of a method for managing an aggregated link according to the present invention;

2 is a schematic structural diagram of a management system of an aggregated link according to the present invention;

3 is a schematic diagram of an initial configuration aggregation link in Embodiment 1 of the present invention;

4 is a schematic diagram of adding service link redistribution caused by member links according to Embodiment 2 of the present invention; FIG. 5 is a schematic diagram of deleting a member link on an aggregated link according to Embodiment 3 of the present invention; FIG. 6 is a schematic diagram of modifying an identifier of an aggregated link according to Embodiment 4 of the present invention. detailed description

The purpose of the present invention is to: determine whether the service flow path has been configured on the member link of the aggregated link during the maintenance operation of the aggregated link, and adjust the aggregation chain according to the service flow bandwidth requirement. The existing configured service flow on the road is located on the member link, which effectively implements link aggregation management, maintains the aggregated link, and ensures the bandwidth service quality requirement of each service flow, making the TE-Trunk technology more It is implementable and operative.

In general, the member link information of the aggregation link is used locally. Other nodes in the network cannot view the member link information inside the aggregation link. The information of the aggregation link can be used by other nodes through route flooding. . Since the current route flooding technology has supported flooding of aggregated link information, the implementation of this patent does not describe the link information flooding process for the aggregated link in detail. In addition, in the description of the present invention, an aggregated link is also referred to as a logical link.

The basic idea of the present invention is: after receiving the request for configuring the aggregation link, the aggregation control module of the control plane determines the type of the configuration operation according to the request for configuring the aggregation link; the aggregation control module operates according to the type and configuration operation of the configuration operation. A service flow configuration involving an aggregated link performs a corresponding configuration operation on the aggregated link.

1 is a schematic flowchart of a method for managing an aggregated link according to the present invention. As shown in FIG. 1, the method includes:

Step 101: The aggregation control module of the control plane receives the request for configuring the aggregation link.

Generally, the control plane needs to check the received request for configuring the aggregated link, and the request for configuring the aggregated link may carry: an operation type, an aggregated link identifier, an identifier of each member link, and The bandwidth is used, where the operation type generally includes: a new operation, a delete operation, and a modification operation.

It should be noted that the aggregated link identifier must uniquely identify an aggregate within a node. Link, but the form can be various, such as using ip address, using special values, etc. When adding an aggregated link, this identifier is either assigned by the management plane, or automatically assigned by the control plane, and must be deleted and falsified. Specify this ID.

The triggering condition for decomposing and aggregating the aggregated link request in the process of the present invention may be a static request (such as a network management configuration request) or a dynamic request (such as a signaling request). In addition, the identifier of the service flow in the present invention may be multiple. The Sflow (service flow) is used to describe the service flow. When the number of service flows is more than one, the SFlows are commonly used. The SFlow can be the service flows corresponding to the identifiers such as LSP, VLAN, VLAN, MAC, and MAC.

Step 102: The control plane determines the type of the configuration operation according to the request for configuring the aggregation link. If the configuration operation is a new operation, the process proceeds to step 103. If the configuration operation is a delete operation, the process proceeds to step 109. The configuration operation is a modification operation. , then go to step 115.

Step 103: Determine whether a new aggregated link needs to be generated. If yes, go to step 104; otherwise, add a member link to the aggregated link, and go to step 105.

The determining whether a new aggregated link needs to be generated may be: if the management plane allocates the aggregated link identifier, the same aggregated link identifier is found, and if it does not exist, the new aggregated link is added. If the control plane automatically assigns an aggregated link identifier, the aggregated link identifier does not exist at this time, and the control plane needs to be automatically generated. Otherwise, it is regarded as adding a member link.

Step 104: Form a new aggregated link, configure the newly added data link as a member of the aggregated link according to the request for configuring the aggregated link, and go to step 108.

Step 105: Configure the newly added data link as a member of the aggregated link according to the request for configuring the aggregated link.

Step 106: Determine whether the aggregated link involved in the new operation carries the service flow (that is, whether the forwarding path of the service flow is configured). If the forwarding path of the service flow is configured, go to step 107; otherwise, the process ends.

Step 107: Perform service flow scheduling according to the control policy, that is, the aggregation control module controls the policy. The module obtains the control policy, and the policy control module performs the control or redistribution of the service flow according to the control policy. If the service path of the service flow changes, the policy control module determines that the configuration needs to be sent to the data plane according to the scheduling result of the policy, and the configuration result is configured. Feedback to the aggregation control module.

Step 108: The aggregation control module notifies the configuration result to other modules or management planes of the control plane, and the process ends.

Step 109: Determine whether the service flow is carried on the aggregation link involved in the deletion operation, and if yes, go to step 110; otherwise, go to step 114.

Step 110: Determine whether to exclude the member link that needs to be deleted, whether there are enough resources on the aggregated link to carry the service flow on the deleted member link, if there are sufficient resources, go to step 111; otherwise, go to Step 113. .

Step 111: Perform service flow scheduling according to the control policy, that is, the aggregation control module acquires a control policy from the policy control module, and the policy control module controls or redistributes the service flow according to the control policy. If the service path of the service flow changes, according to the policy The scheduling result is delivered to the data plane (the policy control technology is not within the scope of the description), and the result is fed back to the aggregation control module.

Step 112: The aggregation control module notifies the configuration result to other modules or management planes of the control plane, and removes the member link from the aggregation link according to the request for configuring the aggregation link, and the process ends.

Step 113: If the aggregation link does not have sufficient resources, the aggregation control module notifies the other modules or management planes of the control plane that the deletion fails, and the process ends.

After the aggregation control module notifies the other modules or management planes of the control plane that the deletion fails, the control plane or management plane can determine the next step. For example, the control plane can start the rerouting mechanism.

Step 114: The member link is directly removed from the aggregation link according to the request for configuring the aggregated link, and the process ends. It should be noted that the aggregation control module can further determine whether a member link exists in the aggregation link. If no member link exists, the aggregation link is deleted.

Step 115: Determine whether the aggregated link related to the modification operation carries the service flow (the forwarding path of the service flow is configured). If the forwarding path of the service flow is configured, go to step 116; otherwise, go to step 117.

Step 116: Perform service flow scheduling according to the control policy, that is, the aggregation control module requests the policy control module to perform scheduling, and transfers the service flow carried on the aggregation link related to the modification operation to another aggregation link. After the policy control module returns the result, Go to step 117.

Step 117: The aggregation control module directly modifies the attribute of the aggregated link to a new attribute, and the process ends.

Here, the modification refers to modifying the attributes of the aggregated link itself, including the identity of the aggregated link and the protection attribute of the aggregated link, without deleting the members of the aggregated link.

It should be noted that, in the management process of the foregoing aggregation link, the control plane generally needs to distinguish the control policies of different service flows, and the control policy may be pre-configured by the management plane, or the control plane may select appropriate control according to different scenarios. Strategy. Here, the control strategy refers to: 釆 Using a certain technology to make the service flow load balanced and reduce the blocking probability.

It should be noted that, in the management process of the foregoing aggregation link, the configuration of the aggregation link needs to update the related bandwidth of the aggregation link according to different conditions and scenarios, and perform flooding of the aggregation link. Within the scope of the program description.

It should be noted that, in the management process of the foregoing aggregation link, the service flow of the aggregated link may be a one-way service flow or a two-way service flow.

The present invention also provides a management system for an aggregated link. FIG. 2 is a schematic structural diagram of a management system for an aggregated link according to the present invention. As shown in FIG. 2, the system includes an aggregation control module of a control plane, which is used to receive configuration aggregation. After the request of the link, the type of the configuration operation is determined according to the request for configuring the aggregated link, where the request for configuring the aggregated link is a static request or a dynamic request; The corresponding configuration operation is performed on the aggregated link according to the operation type of the configuration operation and the service flow configuration of the aggregated link involved in the configuration operation.

The system further includes a policy control module of the control plane. When the operation type of the configuration operation is a new operation, the aggregation control module configures the aggregation link according to the service flow configuration of the aggregated link involved in the configuration operation. The operation is:

e', judging to exclude the member link to be deleted, whether there are enough resources on the aggregated link to carry the service flow on the deleted member link, if there are sufficient resources, go to step f; If sufficient resources are available, the aggregation control module notifies the other modules or management planes of the control plane that the deletion fails.

It can be seen that the method of the present invention can flexibly and conveniently manage the aggregation link, whether static or dynamic, whether the service flow forwarding path is configured on the aggregation link or not configured. Control processing effectively implements link aggregation management, ensuring bandwidth service quality requirements for each service flow while maintaining aggregated links.

The solution of the present invention will be further described in detail below through specific embodiments. It should be noted that, in the detailed description of all the implementations below, the following conventions are described: Linka-b represents a member link of a logical link Linka, and the link is also a physical link;

BW1 in Linka-b (BW1) indicates the available bandwidth of the physical link;

The LSP (CIR, link ID) indicates some key eigenvalue information of an LSP. The CIR indicates the committed bandwidth. The link ID indicates the member link identifier of the LSP through the aggregated link.

During the process of configuring an aggregation link, you need to update the related bandwidth of the aggregation link and flood the aggregation link according to different conditions and scenarios. For the sake of simplicity, the following description is omitted in the following embodiment. Example 1

FIG. 3 is a schematic diagram of an initial configuration of an aggregated link in Embodiment 1 of the present invention, and no service flow is created on an aggregated link.

For node A, the initial configuration process is as follows:

Add an aggregated link interface: Linkl-1 (10M), Linkl-2 (10M), and Linkl-3 (10M). 10M indicates that the link bandwidth is lOMbit/s and uses the same aggregated link identifier: Link- Agl.

The three new data link interfaces are processed in sequence: Linkl-1, Linkl-2, and Linkl-3. After processing one, the latter one is processed. When processing the first data link interface: Linkl-1, the data link interface is first generated: Link-agl. Since the aggregate link identifier Link-agl is not configured, a corresponding new aggregation interface is generated: Link-agl (the temporary value is the same as the aggregated link identifier, the same below), and the data link interface: Linkl-1 is set as the aggregate link interface: member link of Link-agl.

When processing the new data link interface: Linkl-2, the data link interface is first generated: Linkl-2. Because of its aggregated link identifier: Link-agl has been configured, the data link interface is: Linkl-2 is set to aggregate link interface: member link of Link-agl.

When the third data link interface is added: Linkl-3, the data link interface is generated first: Linkl-3. Because of its aggregated link identifier: Link-agl has been configured, the data link interface is: Linkl -3 is set to aggregate link interface: member link of Link-agl. At this time, it is also necessary to update the bandwidth information of the aggregated link, and use link flooding to let other nodes know the logical link information.

Similarly, by repeating the above steps on Node B, the initial configuration of the aggregated link shown in Figure 3 can be completed. Example 2

FIG. 4 is a schematic diagram of adding service link redistribution caused by member links according to Embodiment 2 of the present invention. As shown in FIG. 4, the aggregated link identifiers are: Link-agl, Linkl-1 (10M), and Linkl-2 (10M). The service flow LSPs that have been created are as follows: LSP1 (2M, Linkl-1), LSP2 (2M, Linkl-2), LSP3 (2M, Linkl-2);

Add the member links of the aggregation link: Linkl-3 (10M) and Linkl-4 (10M) aggregation links are identified as: Link-agl.

For node A, the specific process is as follows:

The data link interfaces are processed sequentially on node A: Linkl-3 and Linkl-4; one is processed and the latter is processed. When processing the first data link interface: Linkl-3, the data link interface is first generated: Linkl-3. Because of its aggregated link identifier: Link-agl has been configured, the data link interface is: Linkl-3 is set to aggregate link interface: member link of Link-agl.

The second new data link Link-l-4 is processed in the same manner as Linkl-3 above.

Node B repeats the same steps above to complete the process. After the configuration is complete, you need to update the bandwidth information of the aggregated link. Use link flooding to let other nodes know the logical link information.

Then, the aggregation control module further checks whether an LSP is configured on the aggregation link, and the aggregation control module notifies the policy control module to schedule the service flow at this time. For the sake of clarity, the control policy is assumed to be load balancing; 2 LSP2 and LSP3 are configured, and the occupied bandwidth is 4M. The bandwidth occupied by LSP1 on Linkl-1 is 2M. The policy control module adjusts LSP3 to Link1-4, so that the bandwidth of member links is evenly distributed, which reduces the blocking probability. .

The policy control module returns the result to the aggregation control module, and the aggregation control module reports the result. End. Example 3

FIG. 5 is a schematic diagram of deleting a member link on an aggregated link according to Embodiment 3 of the present invention. As shown in FIG. 5, the aggregated link identifiers are: Link-agl, Linkl-1 (10M), Linkl-2 (10M), The service flow LSPs that have been created on Linkl-3 (10M) and Linkl-4 (10M) are as follows: LSP1 (2M, Linkl-1), LSP2 (2M, Linkl-2), LSP3 (2M, Linkl-4);

Delete the member link of the aggregation link: Linkl-4 (10M), and the aggregation link identifier is: Link-agl„ The specific process is as follows:

After calculating the member link Linkl-3 (10M), whether the bandwidth on the aggregate link Link-ag1 has sufficient bandwidth to carry the current service flow LSP3 (2M, Linkl-4), because there is another member chain of the aggregated link. The Linkl-3 is unused and has a bandwidth of 10M. Therefore, it is determined that Linkl-3 can meet the bandwidth requirement of LSP3.

The aggregation control module requests the policy control module to perform control of the service flow control, and the policy control module returns the adjustment result to the aggregation control module. LSP3 is adjusted to Linkl-3. The aggregation control module moves Linkl-4 out of the aggregated link;

If the aggregation link still has the member links Linkl-1, Link1-2, and Link1-4, the aggregation link does not need to be deleted and the configuration ends.

Similarly, repeat the above steps on Node B to complete the process. Example 4

FIG. 6 is a schematic diagram of modifying an identifier of an aggregated link according to Embodiment 4 of the present invention. As shown in FIG. 6, the aggregated link identifiers are: Link-agl, Linkl-1 (10M), Linkl-2 (10M), and Linkl-3. (10M), Linkl-4 (10M) The service flow LSPs created above are as follows: LSP1 (2M, Linkl-1), LSP2 (2M, Linkl-2), LSP3 (2M, Linkl-2).

Modify the identity of the aggregated link: The specific process of Link-agl as Link-ag2 is as follows: First, it is determined whether the service flow is configured on the member link of the link-agl of the aggregation link. The LSP is configured on the link-ag1. The aggregation control module requests the policy control module to control the service flow control. The policy control module returns the adjustment result. The aggregation control module LSP3 is adjusted to Linkl-4. The aggregation control module modifies the aggregation link identifier Link-ag1 to Link-ag2, and the configuration ends.

Similarly, repeat the above steps on Node B to complete the process.

In summary, the present invention implements link aggregation and decomposition functions in a packet switching network, which facilitates dynamic management and maintenance of an aggregated link.

Of course, the invention may be embodied in various other forms without departing from the spirit and scope of the invention.

Claims

Claim

A method for managing an aggregated link, the method comprising:

2. The method according to claim 1, wherein the request for configuring an aggregated link carries: an operation type, an aggregated link identifier, an identifier of each member link, and a usable bandwidth thereof, and the operation type Including: new operations, delete operations, modify operations.

The method according to claim 2, wherein, when the operation type of the configuration operation is a new operation, the aggregation control module performs the aggregation link according to the service flow configuration of the aggregated link involved in the configuration operation. The corresponding configuration operation is as follows:

a. determining whether a new aggregated link needs to be generated. If yes, a new aggregated link is formed, and the newly added data link is configured as a member of the aggregated link according to the request for configuring the aggregated link. Go to step c; otherwise, the member link needs to be added to the aggregated link, and the newly added data link is configured as a member of the aggregated link according to the request for configuring the aggregated link, and the process proceeds to step b; And determining, by the policy control module, a control policy, the policy control module performs the control policy according to the control policy, if the forwarding path of the service flow is configured on the aggregation link, and the forwarding path of the service flow is configured on the aggregation link. Controlling or redistributing the service flow, when the service path of the service flow is changed, the policy control module sends the configuration to the data plane according to the scheduling result of the policy, and feeds the configuration result to the aggregation control module;

c. The aggregation control module notifies the configuration result to other modules or management planes of the control plane.

The method according to claim 2, wherein, when the operation type of the configuration operation is a deletion operation, the aggregation control module allocates a service flow according to the aggregation link involved in the configuration operation. The corresponding configuration operation of the aggregated link is as follows:

e. Determine whether to exclude the member link to be deleted, whether there are enough resources on the aggregated link to carry the service flow on the deleted member link, if there are sufficient resources, go to step f; if there are not enough resources, The aggregation control module notifies the other modules or management planes of the control plane that the deletion fails.

The method according to claim 4, wherein after the member link is removed from the aggregated link, the method further includes: determining whether a member link still exists in the aggregated link, and no member chain When the path exists, the aggregated link is deleted.

The method according to claim 2, wherein, when the operation type of the configuration operation is a modification operation, the aggregation control module performs the aggregation link according to the service flow configuration of the aggregated link involved in the configuration operation. The corresponding configuration operation is:

h, the aggregation control module requests the policy control module to perform scheduling, and transfers the service flow carried on the aggregation link related to the modification operation to another aggregation link, after the policy control module returns the result, Modify the attributes of the aggregated link.

A management system for an aggregated link, characterized in that the system includes an aggregation control module of the control plane, and is configured to determine a configuration operation according to the request for configuring the aggregated link after receiving the request for configuring the aggregated link. The configuration of the aggregated link is a static request or a dynamic request; and the corresponding configuration operation is performed on the aggregated link according to the operation type of the configuration operation and the service flow configuration of the aggregated link involved in the configuration operation.

The system according to claim 7, wherein the system further comprises a policy control module of the control plane, and when the operation type of the configuration operation is a new operation, the aggregation control module is configured to perform an aggregated link according to the configuration operation. The service flow configuration situation performs corresponding configuration operations on the aggregated link as follows:

a, determining whether a new aggregated link needs to be generated, and if so, forming a new aggregated link, and configuring the newly added data link as a member of the aggregated link according to the request for configuring the aggregated link. Go to step c'; otherwise, you need to add a member link to the aggregated link, configure the newly added data link as a member of the aggregated link according to the request to configure the aggregated link, and go to the step. b'; b', determining whether the aggregation link has been configured with a forwarding path of the service flow, and the aggregation link has configured a forwarding path of the service flow, and the aggregation control module acquires a control policy from the policy control module, and the policy control module The service flow is controlled or re-allocated according to the control policy. When the service path of the service flow is changed, the policy control module sends the configuration to the data plane according to the scheduling result of the policy, and feeds the configuration result to the aggregation control module.

C', the aggregation control module notifies the configuration result to other modules or management planes of the control plane.

The system according to claim 7, wherein the system further comprises a policy control module of the control plane, and when the operation type of the configuration operation is a delete operation, the aggregation control module according to the configuration operation involves an aggregated link. The configuration of the service flow is performed on the aggregated link as follows:

D', determining whether the service flow is carried on the aggregated link involved in the deletion operation, and the deletion operation involves If the service flow is carried on the aggregated link, go to step e'; if the service flow is not carried on the aggregated link involved in the delete operation, the member link is directly connected to the aggregate link according to the request for configuring the aggregated link. Remove

The system according to claim 9, wherein the aggregation control module is further configured to: after the member link is removed from the aggregation link, determine whether a member chain still exists in the aggregation link. On the road, when no member link exists, the aggregated link is deleted.

The system according to claim 7, wherein the system further comprises a policy control module of the control plane, and when the operation type of the configuration operation is a modification operation, the aggregation control module according to the configuration operation involves an aggregated link. The configuration of the service flow is performed on the aggregated link as follows: