CN107819681A - Pseudo-wire load sharing retransmission method and edge router - Google Patents

Abstract

An embodiment of the present invention provides a pseudowire load sharing and forwarding method and a PE. An aggregated pseudowire group is set on the local PE and the remote PE, and the source PE and destination PE of the transmission path of each pseudowire member in the aggregated pseudowire group These are the local PE and remote PE. Based on the above settings, after receiving the service packet from the user equipment, the local PE selects one of the pseudowire members in the aggregation pseudowire group as the target pseudowire in real time according to the currently received service packet. line, and then forward the service packets to the peer PE through the target pseudo-wire. That is to say, the configuration relationship between the pseudowire and the service message in the present invention is not a fixed configuration, but a pseudowire that meets the current service message requirements is flexibly selected from the aggregated pseudowire group according to the current actual service message. Forwarding over a pseudo-wire to achieve the purpose of load-sharing forwarding and avoid packet loss due to bandwidth overrun on a pseudo-wire forwarding path.

Description

Pseudowire offload forwarding method and edge router

technical field

The invention relates to the communication field, in particular to a pseudowire load sharing and forwarding method and an edge router.

Background technique

MPLS (Multi-Protocol Label Switching, Multi-Protocol Label Switching) technology is a multi-protocol label switching technology, which ingeniously converts the three-layer forwarding technology of IP packets into two-layer switching technology, which improves the data forwarding rate, thereby improving network speed. With the development of communication technology, in order to meet the needs of users, a VPN (Virtual Private Network, virtual private network) network can be constructed based on MPLS technology. According to whether PE (Provider Edge Router, edge router) participates in VPN routing and forwarding, the VPN network is divided It is Layer 2 VPN and Layer 3 VPN.

In the Layer 2 VPN (Layer2MPLS VPN, referred to as L2VPN) technology solution, the operator network and the customer's VPN network are completely independent, that is, there will be no routing exchange between the PE equipment and the CE equipment at the operator's border. Operators simply provide customers with some layer-2-based network functions. The operator's network and the customer's VPN network are fully structured on a layered network model. From the customer's point of view, the operator only provides a simple layer-2 connection. This transparency simplifies the structure and configuration management of the operator's network.

In the L2VPN network, several concepts are involved as follows:

PE: Provider Edge Router, refers to the edge router on the backbone network, connected to the user CE (Custom EdgeRouter, user network edge router) device;

P: Provider Router, refers to the core router on the backbone network, connected to PE, not connected to CE, responsible for mpls label forwarding;

CE: Custom Edge Router, user network edge router, user equipment directly connected to the service provider;

AC: Access Circuit, access circuit, as the connection between the user and the service provider, that is, the link connecting CE and PE;

PW: Pseudo Wire, pseudo-wire, a two-way virtual connection between instances on two PE devices, which consists of a pair of unidirectional MPLS VC (Virtual Circuit, virtual circuit) in opposite directions;

Tunnel: Tunnel, used to carry PW, a tunnel can carry multiple PW, the tunnel is a direct connection between a local PE and the peer PE, to complete the transparent data transmission between PE, can be MPLS and GRE tunnel;

Outer label: Used for label exchange between PEs and between PEs and Ps, responsible for sending packets from one PE to another PE device;

Inner label: It is used to distinguish different connections of different VPNs. The PE decides which CE to send the packet to according to the VC label.

A simplified L2VPN network is shown in Figure 1. Pseudowire PWs are established between PE devices. Dynamic PWs establish connections through the LDP (Label Distribution Protocol) protocol, negotiate PW parameters, and assign forwarding labels. At present, the configuration between CE services and PWs is fixed according to the service type. For example, a certain type of service is fixedly configured to correspond to a certain PW, and all packets of the service are delivered through the fixed PW. When the number of connected CE devices increases, the service traffic carried by a certain PW is likely to be too large, and the bandwidth of the forwarding path along the PW is limited, and the bandwidth of the traffic will exceed the limit, resulting in service packet loss, affecting communication and user experience. low satisfaction

Contents of the invention

The embodiment of the present invention provides a pseudowire offload forwarding method and an edge router, mainly solving the technical problem of: solving the problem of packet loss caused by insufficient bandwidth, affecting normal communication, and low user experience satisfaction.

In order to solve the above technical problems, an embodiment of the present invention provides a pseudowire offload forwarding method, including:

receiving service packets from user equipment;

According to the service message, one of the pseudowire members in the aggregated pseudowire group is selected as the target pseudowire; the aggregated pseudowire group is: the edge router at the local end and the edge router at the opposite end are preset to belong to the same virtual private network The pseudowire set of the instance, the source edge router and the destination edge router of the transmission path of each pseudowire member in the pseudowire set are the local edge router and the peer edge router respectively, and the local edge router is the The entrance of the opposite edge router is the exit of the service message;

Forwarding the service packet to the peer edge router through the target pseudowire.

The embodiment of the present invention also provides an edge router, including:

A message receiving module, configured to receive service messages from user equipment;

A pseudowire selection module, configured to select one of the pseudowire members in the aggregated pseudowire group as a target pseudowire according to the service message; the aggregated pseudowire group is: the edge router at the local end and the edge router at the opposite end The set of pseudowires belonging to the same virtual private network instance, the source edge router and destination edge router of the transmission path of each pseudowire member in the pseudowire set are the local edge router and the opposite end edge router respectively, and the local edge router The router is the entrance of the service message, and the peer edge router is the exit of the service message;

A message forwarding module, configured to forward the service message to the peer edge router through the target pseudowire.

An embodiment of the present invention also provides a computer storage medium, where computer executable instructions are stored in the computer storage medium, and the computer executable instructions are used to execute the foregoing method for offloading and forwarding pseudowires.

The beneficial effects of the present invention are:

According to the pseudowire offload forwarding method, edge router, and computer storage medium provided by the embodiments of the present invention, an aggregated pseudowire group is first set up on the local edge router and the peer edge router, the aggregated pseudowire group is a pseudowire set, and the aggregated pseudowire group is a pseudowire set. The source edge router and the destination edge router of the transmission path of each pseudowire member in the pseudowire set are the local edge router and the peer edge router respectively. Based on the above settings, after the local edge router receives the service packet from the user equipment, it selects one of the pseudowire members in the aggregation pseudowire group as the target in real time according to the currently received service packet Pseudowire, and then forward the service packet to the peer edge router through the target pseudowire. That is to say, the configuration relationship between the pseudowire and the service message in the present invention is not a fixed configuration, but a pseudowire that meets the current service message requirements is flexibly selected from the aggregated pseudowire group according to the current actual service message. To avoid packet loss caused by bandwidth overrun on the pseudo-wire forwarding path, improve the reliability of communication, and improve the satisfaction of user experience.

Description of drawings

FIG. 1 is a schematic diagram of a L2VPN network;

FIG. 2 is a schematic flow chart of a pseudowire offloading and forwarding method in Embodiment 1 of the present invention;

FIG. 3 is a schematic flowchart of configuring a dynamically aggregated pseudowire group in Embodiment 1 of the present invention;

FIG. 4 is a schematic structural diagram of an edge router in Embodiment 2 of the present invention;

FIG. 5 is a schematic structural diagram of another edge router in Embodiment 2 of the present invention;

FIG. 6 is a schematic structural diagram of another edge router in Embodiment 2 of the present invention;

FIG. 7 is a schematic flowchart of setting a dynamically aggregated pseudowire group in Embodiment 3 of the present invention;

FIG. 8 is a schematic flow diagram of forwarding a message using a dynamically aggregated pseudowire group in Embodiment 3 of the present invention;

FIG. 9 is a schematic flowchart of abnormal handling of dynamic aggregation pseudowire groups in Embodiment 3 of the present invention;

FIG. 10 is a schematic structural diagram of an edge router in Embodiment 3 of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

Embodiment one:

In this embodiment, the problem of excessive bandwidth caused by excessive service traffic on the forwarding path of the pseudowire PW, which in turn causes packet loss, is solved. An aggregated pseudowire group is pre-set between the edge router PEs. For the convenience of description, the two PEs are referred to as the local PE and the peer PE respectively. There are multiple paths between the local PE and the peer PE. In this embodiment, the aggregated pseudowire group set on the local PE and the peer PE is: the preset pseudowire set of the local PE and the peer PE, the pseudowire set belongs to the same virtual private network instance (VPN), and the The source PE and destination PE of the transmission path of each pseudowire member in the pseudowire set are the local PE and the peer PE respectively, that is, the local PE is the entrance of the service message, and the peer PE is the gateway of the service message. Export.

Based on the above settings, when the local PE receives service packets from the L2VPN user equipment CE, it selects the corresponding pseudowire aggregation group according to the One of the pseudowire members is selected as the target pseudowire, and then the service packet is forwarded to the peer PE through the target pseudowire. In this way, the present invention can flexibly share the service packets from CE through the pseudowire members in the aggregated pseudowire group. Compared with the existing situation of binding a single PW according to the service type, the load pressure of a single pseudowire can be reduced. The bandwidth can carry more traffic more reasonably, achieving the effect similar to physical upgrade bandwidth, but at the same time can reduce costs and improve resource utilization.

It should be understood that the aggregated PW group configured on the local PE and the peer PE may include all the pseudowires configured on the local PE and the peer PE, or only include the pseudo wires configured on the local PE and the peer PE. part of the line. Based on the above settings of the aggregated pseudowire group, the forwarding process of the service message received by the local PE is taken as an example to illustrate. See Figure 2, including:

S201: Receive a service packet from a user equipment.

S202: Select one of the pseudowire members in the aggregated pseudowire group as the target pseudowire according to the content of the service message.

S203: Forward the service packet to the peer PE through the target pseudowire.

The aggregated pseudowire group configured on the PE in this embodiment may include at least one of a static (static) aggregated pseudowire group and a dynamic (dynamic) aggregated pseudowire group. When configuring a static aggregated pseudowire group, no negotiation is required between the local PE and the peer PE. However, when configuring a dynamic aggregated pseudowire group, negotiation of pseudowire members is required between the local PE and the peer PE. In order to facilitate the understanding of the present invention, the configuration processes of the dynamic aggregated pseudowire group and the static aggregated pseudowire group are taken as examples for description below.

When the aggregated pseudowire group in this embodiment includes a dynamic aggregated pseudowire group, the process of configuring the dynamic aggregated pseudowire group is shown in Figure 3, including:

S301: Receive dynamic pseudowire configuration information, and acquire dynamic aggregation attribute information.

The dynamic pseudowire configuration information in this embodiment includes the pseudowire to be configured, and the dynamic pseudowire configuration information may be configured and delivered by the user.

In this embodiment, the dynamic aggregation attribute information may also be delivered by user configuration, or acquired based on the attribute information of the first pseudowire member that joins the dynamic aggregation pseudowire group during the configuration process.

S302: Add the pseudowires matching the dynamic aggregation attribute information among the pseudowires to be configured as selected (selected) pseudowires to the dynamic aggregation pseudowire group.

When the local PE performs the above configuration process, the peer PE also performs the above configuration process.

S303: Negotiate with the peer PE, add the selected pseudowires in the dynamic aggregation pseudowire group of the local PE and the peer PE dynamic aggregation pseudowire group as pseudowire members to the respective dynamic aggregation pseudowire groups, and set the The working status of the pseudowire member.

The dynamic aggregate attribute information in this embodiment includes, but is not limited to: the aggregated pseudowire group identifier (aggregated pseudowire group id) to which the pseudowire belongs, the destination PE address (peer-ip) of the pseudowire, and the pseudowire mode (pw-mode) It is dynamic mode (dynamic), pseudowire type (pw-type), pseudowire bandwidth and pseudowire control word (pw-class). The above dynamic aggregation attribute information can be delivered by user configuration, and can also be determined as the dynamic aggregation attribute information based on the above attribute parameters of the first pseudowire member that joins the dynamic aggregation pseudowire group.

In the above S302, for each pseudowire to be configured, only the pseudowire whose attribute matches (that is, is consistent with) the dynamic aggregation attribute information will be set to a selected (selected) state. And according to the above analysis, it can be seen that the pw-mode of each pseudowire member in the dynamically aggregated pseudowire group in this embodiment must be dynamic, that is, only dynamic PW is supported.

In this embodiment, the negotiation between the local PE and the peer PE needs to be initiated by one party. In this embodiment, the party with the larger IP address among the two PEs is selected to initiate the negotiation, that is, when the IP address of the local PE is greater than the IP address of the peer PE , the local PE acts as the active end to initiate the negotiation, and the peer PE acts as the passive end. Otherwise, the opposite end PE acts as the active end to initiate the negotiation, and the local PE acts as the passive end. For the negotiation process of S302 above, this embodiment takes the active end (which may be the local PE or the peer PE) and the passive end (which may be the peer PE or the local PE) as an example. illustrate.

After the active end adds the pseudowires that match the dynamic aggregation attribute information among the pseudowires to be configured as selected pseudowires to the dynamic aggregation pseudowire group, it sends the member information of the selected pseudowires in the dynamic aggregation group at the local end to The opposite end (negotiation can be carried out through the LDP protocol message); after the passive end receives it, the working state of each selected pseudowire member in the dynamic aggregation pseudowire group of the local end is set to active (active), Feedback the information of these pseudowire members to the active end. After the active end receives it, it compares it with the pseudowire members in the dynamic aggregation group of the local end. Pseudowires are also set to active. After that, keep-alive messages can be sent regularly between the active end and the passive end to perform status keep-alive.

In this embodiment, after the dynamic aggregation pseudowire group is set based on the above negotiation process, it also includes:

When the active end or the passive end detects the port change and/or status abnormality of a PW member in the dynamic aggregation PW group at the local end, it removes the PW member from the dynamic aggregation PW group and notifies the peer PE to This pseudowire member is removed from the peer's dynamically aggregated pseudowire group. In this embodiment, removing a pseudowire member from a dynamically aggregated pseudowire includes, but is not limited to: setting the pseudowire member as unselected, and changing the status of the pseudowire member to inactive (unactive).

In addition, in this embodiment, the forwarding mode of the dynamically aggregated pseudowire group itself can also be set, and the forwarding mode includes but is not limited to: active/standby forwarding mode and load sharing mode. In the active/standby forwarding mode, only one of the pseudowire members in the dynamically aggregated pseudowire group is configured as the active pseudowire, and the other pseudowires are the standby pseudowires. In the load sharing mode, as long as the working status of each pseudowire member in the dynamic aggregation pseudowire group is active, traffic can be forwarded. At this time, the working status of the pseudowire member set in the above S303 includes:

In active-standby forwarding mode: if the currently added pseudowire member is the active pseudowire and its status is UP, set the working status of the pseudowire member to active; if the currently added pseudowire member is the standby pseudowire and its If the state is UP, set the pseudowire member to be active; if the status of the currently added pseudowire member is abnormal, set the working state of the pseudowire member to be inactive;

In load sharing mode: if the status of the currently added pseudowire member in the selected state is UP, set the working status of the pseudowire member to active status; if the status of the currently added pseudowire member is abnormal (including but not limited to down), set the working state of the pseudowire member to inactive.

When the aggregated pseudowire group includes a static aggregated pseudowire group, set the static aggregated pseudowire group to include:

The local PE receives static pseudowire configuration information and obtains static aggregation attribute information; the static pseudowire configuration information includes the pseudowire to be configured; in this embodiment, the static pseudowire configuration information can also be delivered by user configuration, and the static aggregation attribute information It may be the same as the above dynamic aggregation attribute information.

Add the pseudowire that matches the static aggregation attribute information among the pseudowires to be configured to the static aggregation pseudowire group as a pseudowire member, and set the working status of the pseudowire member. Correspondingly, the static aggregate attribute information in this embodiment includes, but is not limited to: the aggregated pseudowire group identifier (aggregated pseudowire group id) to which the pseudowire belongs, the destination PE address (peer-ip) of the pseudowire, and the pseudowire mode ( pw-mode) is a static mode (static), a pseudowire type (pw-type), a pseudowire bandwidth, and a pseudowire control word (pw-class).

For static aggregation pseudowire groups, setting the working status of pseudowire members also includes:

In active-standby forwarding mode: if the currently added pseudowire member is the active pseudowire and its status is UP, set the working status of the pseudowire member to active; if the currently added pseudowire member is the standby pseudowire and its If the state is UP, set the pseudowire member to be active; if the status of the currently added pseudowire member is abnormal, set the working state of the pseudowire member to be inactive;

In load sharing mode: if the status of the currently added pseudowire member in the selected state is UP, set the working status of the pseudowire member to active status; if the status of the currently added pseudowire member is abnormal (including but not limited to down), set the working state of the pseudowire member to inactive.

In this embodiment, after the local PE receives a service packet from the CE, when the local PE is configured with a dynamic aggregated pseudowire group and a static aggregated pseudowire group, according to the forwarding path of the service packet, it may be dynamically Select a PW member in any one of the aggregated PW group and the static aggregated PW group as the target PW, and may also use a PW other than the aggregated PW group to forward the service message. When a pseudowire member is selected as the target pseudowire in an aggregated pseudowire group or a static aggregated pseudowire group, including:

In the active-standby forwarding mode of the aggregated pseudowire group, select the primary pseudowire in the aggregated pseudowire group as the target pseudowire;

When the aggregation pseudowire group is in load sharing mode, according to the user vlan (Virtual Local Area Network, virtual local area network) or mac address (physical address) in the service message, each working state in the aggregation pseudowire group is an active pseudowire member Select one of them as the target pseudowire. In this embodiment, the destination address of the service message (the source address can also be determined) can be determined specifically according to the user vlan or mac address of the service message, and a fake address can be selected for the service message according to the destination address (or in combination with the source address). The line member is used as the target pseudo-wire, and the same pseudo-wire member is preferably used for forwarding service packets with the same destination address.

In this embodiment, the minimum number min-number of pseudowire members of actvie in the dynamic aggregation pseudowire group and/or the static aggregation pseudowire group can also be set, when the local PE or peer PE monitors the local dynamic aggregation pseudowire When the pseudowire members of the actvie in the group and/or the static aggregation pseudowire group are less than the minimum number min-number, set the working status of the dynamic aggregation pseudowire group and/or the static aggregation pseudowire group to down. At this time, the dynamic aggregation pseudowire group and/or static aggregation pseudowire group stops forwarding packets. The specific value of min-number in this embodiment can be flexibly set according to specific application scenarios, and can be set to 1 in this embodiment.

The pseudowire load sharing and forwarding method provided in this embodiment can solve the problem of insufficient link bandwidth through aggregated PWs, and does not need to upgrade the physical bandwidth. To a certain extent, it can not only reduce costs, but also improve resource utilization, and can also protect Forwarding can improve user experience satisfaction.

Embodiment two:

This embodiment also provides an edge router (PE, the PE in this embodiment is the local PE), as shown in FIG. 4 , including:

A message receiving module 41, configured to receive a service message from a user equipment;

The pseudowire selection module 42 is configured to select one of the pseudowire members in the aggregated pseudowire group as a target pseudowire according to the content of the service message; For the pseudowire set of the same VPN instance, the source PE and destination PE of the transmission path of each pseudowire member in the pseudowire set are the local PE and the peer PE respectively, and the local PE and the peer PE are in the On the forwarding path of service packets, that is, the local PE is the ingress of the service packets, and the peer PE is the egress of the service packets.

The message forwarding module 43 is configured to forward the service message to the peer PE through the target pseudowire. It should be understood that the destination PE of the forwarding path of the service message may be the peer PE or may not be the peer PE. In this way, the present invention can flexibly share the service packets from CE through the pseudowire members in the aggregated pseudowire group. Compared with the existing situation of binding a single PW according to the service type, the load pressure of a single pseudowire can be reduced. The bandwidth can carry more traffic more reasonably, achieving the effect similar to physical upgrade bandwidth, but at the same time can reduce costs and improve resource utilization.

It should be understood that the aggregated PW group configured on the local PE and the peer PE may include all the pseudowires configured on the local PE and the peer PE, or only include the pseudo wires configured on the local PE and the peer PE. part of the line. The aggregated pseudowire group configured on the PE in this embodiment may include at least one of a static (static) aggregated pseudowire group and a dynamic (dynamic) aggregated pseudowire group. When configuring a static aggregated pseudowire group, no negotiation is required between the local PE and the peer PE. However, when configuring a dynamic aggregated pseudowire group, negotiation of pseudowire members is required between the local PE and the peer PE. In order to facilitate the understanding of the present invention, the configuration processes of the dynamic aggregated pseudowire group and the static aggregated pseudowire group are taken as examples for description below.

When the aggregated pseudowire group includes a static aggregated pseudowire group, as shown in FIG. 5, the PE also includes a static aggregated pseudowire group configuration module 44, which is used to receive static pseudowire configuration information and obtain static aggregated attribute information; static pseudowire configuration The information includes pseudowires to be configured; the static aggregation pseudowire group configuration module 44 is also used to add the pseudowires that match the static aggregation attribute information in the pseudowires to be configured to the static aggregation pseudowire group as pseudowire members, and set the pseudowires Member's job status. The static aggregation attribute information in this embodiment includes but is not limited to: the aggregation pseudowire group identifier (aggregation pseudowire group id) to which the pseudowire belongs, the destination PE address (peer-ip) of the pseudowire, the pseudowire mode (pw-mode ) is a static mode (static), a pseudowire type (pw-type), a pseudowire bandwidth, and a pseudowire control word (pw-class).

In addition, in this embodiment, the forwarding mode of the static aggregation pseudowire group itself can also be set, and the forwarding mode includes but not limited to: active/standby forwarding mode and load sharing mode. In the active-standby forwarding mode, among the pseudowire members in the static aggregation pseudowire group, only one is configured as the active pseudowire, and the other pseudowires are the standby pseudowires. In load sharing mode, as long as the working status of each pseudowire member in the static aggregation pseudowire group is active, traffic can be forwarded. At this point, the static aggregation pseudowire group configuration module 44 sets the working status of the pseudowire members to include:

In active-standby forwarding mode: if the currently added pseudowire member is the active pseudowire and its status is UP, set the working status of the pseudowire member to active; if the currently added pseudowire member is the standby pseudowire and its If the state is UP, set the pseudowire member to be active; if the status of the currently added pseudowire member is abnormal, set the working state of the pseudowire member to be inactive;

In load sharing mode: if the status of the currently added pseudowire member in the selected state is UP, set the working status of the pseudowire member to active status; if the status of the currently added pseudowire member is abnormal (including but not limited to down), set the working state of the pseudowire member to inactive.

Still referring to FIG. 5 , when the aggregated pseudowire group includes a dynamic aggregated pseudowire group, the PE also includes a dynamic aggregated pseudowire group configuration module 45, configured to receive dynamic pseudowire configuration information that includes a pseudowire to be configured, and obtain a dynamic aggregated pseudowire group configuration module 45. Attribute information; the dynamic aggregation pseudowire group configuration module 45 is also used to add the pseudowire that matches the dynamic aggregation attribute information among the pseudowires to be configured into the dynamic aggregation pseudowire group as a selected pseudowire, and negotiate with the opposite end PE, and the local end The selected pseudowires shared by the PE dynamic aggregation pseudowire group and the peer PE dynamic aggregation pseudowire group are added to their respective dynamic aggregation pseudowire groups as pseudowire members, and the working status of the pseudowire members is set.

In this embodiment, the dynamic pseudowire configuration information may be delivered by user configuration. In this embodiment, the dynamic aggregation attribute information may also be delivered by user configuration, or the dynamic aggregation pseudowire group configuration module 45 may obtain it based on the attribute information of the first pseudowire member that joins the dynamic aggregation pseudowire group during the configuration process.

The dynamic aggregate attribute information in this embodiment includes, but is not limited to: the aggregated pseudowire group identifier (aggregated pseudowire group id) to which the pseudowire belongs, the destination PE address (peer-ip) of the pseudowire, and the pseudowire mode (pw-mode) It is dynamic mode (dynamic), pseudowire type (pw-type), pseudowire bandwidth and pseudowire control word (pw-class). The above dynamic aggregation attribute information can be delivered by user configuration, and can also be determined as the dynamic aggregation attribute information based on the above attribute parameters of the first pseudowire member that joins the dynamic aggregation pseudowire group.

For each pseudowire to be configured, only the pseudowire whose attribute matches (that is, is consistent with) the dynamic aggregation attribute information will be set to a selected (selected) state. And according to the above analysis, it can be seen that the pw-mode of each pseudowire member in the dynamically aggregated pseudowire group in this embodiment must be dynamic, that is, only dynamic PW is supported.

In this embodiment, the negotiation between the local PE and the peer PE needs to be initiated by one party. In this embodiment, the party with the larger IP address among the two PEs is selected to initiate the negotiation, that is, when the IP address of the local PE is greater than the IP address of the peer PE , the local PE acts as the active end to initiate the negotiation, and the peer PE acts as the passive end. Otherwise, the opposite end PE acts as the active end to initiate the negotiation, and the local PE acts as the passive end. For the above negotiation process, this embodiment takes the active end (which may be the local PE or the peer PE) and the passive end (which may be the peer PE or the local PE) as examples for illustration.

The dynamic aggregation pseudowire group configuration module of the active end adds the pseudowires that match the dynamic aggregation attribute information among the pseudowires to be configured as selected (selected) pseudowires to the dynamic aggregation pseudowire group, and then selects the selected pseudowires in the dynamic aggregation group of the local end. The member information of each pseudowire is sent to the opposite end (negotiation can be carried out through the LDP protocol message); after the dynamic aggregation pseudowire group configuration module of the passive end receives it, each selected state in the dynamic aggregation pseudowire group of the local end is the same as that of the active end The working status of the pseudowire members is set to active (active), and the information of these pseudowire members is fed back to the active end. For comparison, set the same pseudowire member at the local end as active according to the pseudowire member set as active at the peer end. After that, keep-alive messages can be sent regularly between the active end and the passive end to perform status keep-alive.

For the dynamic aggregation pseudowire group, the working state of the dynamic aggregation pseudowire group configuration module 45 setting pseudowire members also includes:

In active-standby forwarding mode: if the currently added pseudowire member is the active pseudowire and its status is UP, set the working status of the pseudowire member to active; if the currently added pseudowire member is the standby pseudowire and its If the state is UP, set the pseudowire member to be active; if the status of the currently added pseudowire member is abnormal, set the working state of the pseudowire member to be inactive;

In load sharing mode: if the status of the currently added pseudowire member in the selected state is UP, set the working status of the pseudowire member to active status; if the status of the currently added pseudowire member is abnormal (including but not limited to down), set the working state of the pseudowire member to inactive.

In this embodiment, the PE also includes a member updating module 46, as shown in FIG. 6 . The member update module 46 is configured to set up the dynamic aggregation pseudowire group based on the above-mentioned negotiation process, and when the port change and/or status of a certain pseudowire member of the local PE dynamic aggregation pseudowire group is detected to be abnormal, the pseudowire member Remove it from the dynamic aggregation pseudowire group, and notify the peer PE to remove the pseudowire member from the dynamic aggregation pseudowire group of the peer end. In this embodiment, the member update module 46 removes the pseudowire member from the dynamically aggregated pseudowires, including but not limited to: setting the pseudowire member as unselected, and changing the status of the pseudowire member to inactive.

Still referring to FIG. 6, the PE in this embodiment may also include an aggregation group state monitoring module 47, which is used to set the minimum number min- number, when it is detected that the pseudo-wire members of the dynamic aggregation pseudo-wire group and/or the static aggregation pseudo-wire group of the local PE are less than the minimum number min-number, the dynamic aggregation pseudo-wire group and/or the static aggregation pseudo-wire group The working state of the group is set to down, and the dynamic aggregation pseudowire group and/or the static aggregation pseudowire group stop forwarding packets. The specific value of min-number in this embodiment can be flexibly set according to specific application scenarios, and can be set to 1 in this embodiment.

The functions of the above modules in the embodiments may be implemented by a controller or processing inside the router. And those skilled in the art should understand that each module or each step of the above-mentioned embodiments of the present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network composed of multiple computing devices Alternatively, they can be implemented with program codes executable by a computing device, so that they can be stored in a computer storage medium (ROM/RAM, magnetic disk, optical disk) to be executed by a computing device, and in some In some cases, the steps shown or described may be performed in a different order than here, or they may be implemented as individual integrated circuit modules, or multiple modules or steps thereof may be implemented as a single integrated circuit module. Therefore, the present invention is not limited to any specific combination of hardware and software.

Embodiment three:

In order to facilitate understanding of the present invention, this embodiment further illustrates the present invention by taking the networking scene shown in FIG. 1 as an example.

Deploy a basic MPLS L2VPN network in the network shown in Figure 1, use the RSVP TE (ResourceReSerVation Protocol-Traffic Engineering) protocol to deploy tunnels, distribute outer labels, and form data forwarding paths. The pseudowire PW establishes a link through the LDP protocol and assigns inner labels. Assume that users CE1 and CE4 need to communicate with CE2 through the backbone network devices PE1, P and PE2, and through the L2VPN network between PE1 and PE2 to form a dedicated private network channel.

If the traffic of users CE1 and CE4 is heavy and the communication traffic occupies a large amount of bandwidth, the bandwidth exceeds the limit on the PE1-P-PE2 link, causing packet loss, which seriously affects the network usage behavior of users. Therefore, it is necessary to increase the bandwidth along the backbone network. This embodiment introduces a PW load sharing mode based on the solutions of the foregoing embodiments, which can effectively solve this problem without adding physical links. In addition, this method also protects the PW. The following example illustrates it as follows:

In the L2VPN network, two pseudowires PW1 and PW2 are established between two PEs, and these two PWs are bound in an aggregated PW group. The aggregated PW group is represented by pw-group, and the two PWs belong to the pw-group. Members, the paths of PW1 and PW2 can be different. As shown in Figure 1, assume that an L2VPN is established between PE1 and PE2 to implement communication between CE1CE4CE2. The path of PW1 can be selected from PE1-P-PE2 through the tunnel, and the path of PW2 can be selected from PE1-PE3-PE2. Configure pw-group on both PE1 and PE2 to aggregate the two PWs into a PW group. In a pw-group, two PWs implement load sharing, which reduces the load pressure on a single link.

According to the introduction of the above embodiment, it can be seen that Pw-group is divided into dynamic dynamic and static static aggregation methods. The static method does not require protocol negotiation, and the dynamic method requires protocol negotiation on the state of member PWs. There are three states of the member PW, one is active, one is inactive, and the other is dedicated to the standby PW in the protection mode (that is, the active-standby forwarding mode), which is represented by reactive. For static aggregation, when the PW itself is in the up state and the local PW is selected, the member PWs under the pw-group are active. When the PWs are in the abnormal state, the member PWs are in the inactive state. In dynamic aggregation mode, the status of member PWs is negotiated through the protocol.

And it should be understood that, under the Pw-group, member PWs can be added to realize the sharing mode of multiple PWs. Member minimums can also be configured. When the number of active member PWs is less than the minimum value, the pw-group status is down, and the aggregated PWs do not forward traffic.

The forwarding mode of Pw-group can be divided into two types, one is the load sharing mode, and the other is the active/standby forwarding mode. In load sharing mode, each member PW can forward traffic. In active-standby forwarding mode, only one PW is in the forwarding state, and the other PWs are in the standby state. Therefore, only two pseudowire members can be configured in this mode.

There are two load sharing methods for Pw-group, one is based on user VLAN for sharing and forwarding, and the other is based on mac address for sharing and forwarding.

Refer to FIG. 10 for the internal composition of the edge router in this embodiment. The following uses the process of Pw-group dynamic aggregation, and takes PE1 as the local PE and PE2 as the remote PE as an example to illustrate, as shown in Figure 7:

S701: Select the active end and the passive end, select the IP address of the local PE and the IP address of the peer PE, and determine whether the local IP address is greater than the peer IP address, if so, go to S702, otherwise, go to S704.

S702: The local PE obtains the dynamic aggregation pseudowire group attribute message, selects a matching pseudowire member from the pseudowires to be configured, and sets it as selected.

S703: The local PE sends a negotiation message to the peer PE, and waits for the peer to reply the negotiation message. If the peer does not reply within a period of time, it will resend the negotiation message, and go to S706.

S704: The peer PE acquires the dynamic aggregation pseudowire group attribute message, selects a matching pseudowire member from the pseudowires to be configured, and sets it as selected.

S705: The peer PE sends a negotiation message to the local PE, and waits for the peer to reply to the negotiation message. If the peer does not reply within a period of time, it will resend the negotiation message, and go to S706.

S706: Determine whether the unified PW members of the local PE and the remote PE are all selected, if yes, go to S707; otherwise, go to S710.

S707: Determine whether the unified PW member states of the local PE and the remote PE are both UP, and if yes, go to S708; otherwise, go to S710.

S708: Set the working state of the pseudowire member to active.

S709: Judging whether the number of pseudowire members whose working state is set to active in the Pw-group is less than the min-number, if yes, go to S711, otherwise, go to S712.

S710: Set the pseudo-wire as active, and return to S706 to determine the next pseudo-wire member.

S711: The state of the Pw-group is set to down.

S712: The state of the Pw-group is set to up.

Compared with the above process, there is no protocol negotiation process for the static aggregation of Pw-group. After the member PW is added to the pw-group, as long as the PW is up, traffic can be forwarded.

The minimum number of active PWs can be configured under the pw-group. When the number of active PWs is less than the min-number, the pw-group reports down, and the aggregation group stops forwarding traffic. The default value of min-number is 1.

After the pw-group is set based on the process shown in Figure 7, the PE forwarding process using the pw-group is shown in Figure 8, including:

S801: Determine whether the state of the pw-group is UP, if it is down, go to S802, otherwise go to S803.

S802: Forbid traffic forwarding.

S803: Determine whether the pw-group forwarding function is enabled, if not, go to S802, otherwise, go to S804.

S804: Determine whether the working mode of the pw-group is the active/standby forwarding mode, if yes, go to S805; otherwise, go to S806.

S805: Select the main pseudowire of the pw-group as the target pseudowire to forward traffic.

S806: Determine whether the load sharing method is based on the source/destination mac address, if so, go to S807, otherwise, go to S808;

S807: Select a PW member as a target PW according to the principle of forwarding packets with different mac addresses from different PWs.

S808: Select a pseudowire member as the target pseudowire to forward according to the principle that packets of different VLANs are forwarded from different PWs.

Refer to Figure 9 for the exception handling process of pw-group members, including:

Step S901: Abnormal situation is received.

S902: Determine whether the abnormality is that the member PW reports down, if yes, go to S903; otherwise, go to S905.

S903: Set the PW member as inactive.

S904: Turn off the forwarding function of the PW member, and go to S909.

S905: Indicate that the PW member is removed, and report the PW member as down.

S906: Remove the forwarding egress under the PW member from the pw-group, close the forwarding function of the PW member, and go to S909.

S907: The peer PE detects that the PW member state is down, and sets the PW state to inactive.

S908: Turn off the forwarding function of the PW member, and go to S909.

S909: Check whether the number of active PW members in the local pw-group is less than the min-number, if yes, go to S911, otherwise, go to S910.

S910: Continue to forward the data packet.

S911: Set pw-group to down, and disable forwarding.

This embodiment solves the problem of extending the bandwidth along the path from the software when the link bandwidth is insufficient, which can save resources and protect the forwarding link.

The above content is a further detailed description of the embodiments of the present invention in conjunction with specific implementation modes, and it cannot be assumed that the specific implementation of the present invention is limited to these descriptions. For those of ordinary skill in the technical field of the present invention, without departing from the concept of the present invention, some simple deduction or replacement can be made, which should be regarded as belonging to the protection scope of the present invention.

Claims (11)

1. A pseudowire offload forwarding method, comprising: receiving service packets from user equipment; According to the service message, one of the pseudowire members in the aggregated pseudowire group is selected as the target pseudowire; the aggregated pseudowire group is: the edge router at the local end and the edge router at the opposite end are preset to belong to the same virtual private network The pseudowire set of the instance, the source edge router and the destination edge router of the transmission path of each pseudowire member in the pseudowire set are the local edge router and the peer edge router respectively, and the local edge router is the The entrance of the opposite edge router is the exit of the service message; Forwarding the service packet to the peer edge router through the target pseudowire. 2. The pseudowire load sharing and forwarding method according to claim 1, wherein the aggregated pseudowire group comprises a static aggregated pseudowire group; setting the static aggregated pseudowire group comprises: receiving static pseudowire configuration information, and obtaining static aggregation attribute information; the static pseudowire configuration information includes a pseudowire to be configured; Adding the pseudowires matching the static aggregation attribute information among the pseudowires to be configured as pseudowire members to the static aggregation pseudowire group, and setting the working status of the pseudowire members. 3. The pseudowire offloading and forwarding method according to claim 2, wherein the static aggregation attribute information includes: the aggregation pseudowire group identification to which the pseudowire belongs, the destination edge router address of the pseudowire, and the pseudowire mode of Static mode, pseudowire type, pseudowire bandwidth, and pseudowire control word. 4. The pseudowire load sharing and forwarding method according to claim 1, wherein the aggregated pseudowire group comprises a dynamic aggregated pseudowire group, and setting the dynamic aggregated pseudowire group comprises: receiving dynamic pseudowire configuration information, and acquiring dynamic aggregation attribute information, where the dynamic pseudowire configuration information includes a pseudowire to be configured; adding a pseudowire matching the dynamic aggregation attribute information among the pseudowires to be configured to a dynamic aggregation pseudowire group as a selected pseudowire; Negotiate with the peer edge router to add the selected pseudowires shared by the dynamic aggregation pseudowire group of the local edge router and the dynamic aggregation pseudowire group of the peer edge router as pseudowire members to their respective dynamic aggregation pseudowire groups, and set The working status of this pseudowire member. 5. The pseudowire load-sharing and forwarding method according to claim 4, wherein setting the dynamically aggregated pseudowire group also includes: When it is detected that the port change and/or state of a pseudowire member of the dynamic aggregation pseudowire group is abnormal, the pseudowire member is removed from the dynamic aggregation pseudowire group, and the peer edge router is notified to transfer the Pseudowire members are removed from the peer's dynamically aggregated pseudowire group. 6. The pseudowire offloading and forwarding method according to claim 4, wherein the dynamic aggregation attribute information includes: the aggregation pseudowire group identifier to which the pseudowire belongs, the destination edge router address of the pseudowire, and the pseudowire mode of Dynamic mode, pseudowire type, pseudowire bandwidth, and pseudowire control word. 7. The pseudowire offloading and forwarding method according to any one of claims 2-6, wherein the setting of the working state of the pseudowire member comprises: In active/standby forwarding mode: if the currently added pseudowire member is the active pseudowire and its status is UP, set the working status of the pseudowire member to active; if the currently added pseudowire member is standby line and its state is UP, set the pseudo-wire member to be in the ready-to-activate state; if the status of the currently added pseudo-wire member is abnormal, set the working state of the pseudo-wire member to the inactive state; In load sharing mode: if the status of the currently added pseudowire member is UP, set the working status of the pseudowire member to active status; if the status of the currently added pseudowire member is abnormal, set the status of the pseudowire member to The working state is inactive. 8. The pseudowire load-sharing and forwarding method according to claim 7, wherein selecting one of the pseudowire members in the aggregation pseudowire group as the target pseudowire according to the service message includes: In the active/standby forwarding mode, select the primary pseudowire in the aggregated pseudowire group as the target pseudowire; In the load sharing mode, one of the activated pseudowire members in the aggregated pseudowire group is selected as the target pseudowire according to the virtual local area network or physical address of the user in the service message. 9. An edge router comprising: A message receiving module, configured to receive service messages from user equipment; A pseudowire selection module, configured to select one of the pseudowire members in the aggregated pseudowire group as a target pseudowire according to the service message; the aggregated pseudowire group is: the edge router at the local end and the edge router at the opposite end The set of pseudowires belonging to the same virtual private network instance, the source edge router and destination edge router of the transmission path of each pseudowire member in the pseudowire set are the local edge router and the opposite end edge router respectively, and the local edge router The router is the entrance of the service message, and the peer edge router is the exit of the service message; A message forwarding module, configured to forward the service message to the peer edge router through the target pseudowire. 10. The edge router according to claim 9, wherein the aggregated pseudowire group comprises a static aggregated pseudowire group; The edge router also includes a static aggregation pseudowire group configuration module, configured to receive static pseudowire configuration information, and obtain static aggregation attribute information, the static pseudowire configuration information includes a pseudowire to be configured; Among the pseudowires to be configured, the pseudowires matching the static aggregation attribute information are added to the static aggregation pseudowire group as pseudowire members, and the working status of the pseudowire members is set. 11. The edge router according to claim 9, wherein the aggregated pseudowire group comprises a dynamic aggregated pseudowire group; The edge router also includes a dynamic aggregation pseudowire group configuration module, configured to receive dynamic pseudowire configuration information, and obtain dynamic aggregation attribute information, the dynamic pseudowire configuration information includes pseudowires to be configured; Among the pseudowires to be configured, the pseudowires that match the dynamic aggregation attribute information are added to the dynamic aggregation pseudowire group as the selected pseudowire, and negotiated with the peer edge router, and the local edge router dynamically aggregates the pseudowire group with the peer edge router. The selected pseudowires shared by the dynamic aggregation pseudowire groups of the routers are added to the respective dynamic aggregation pseudowire groups as pseudowire members, and the working status of the pseudowire members is set.