CN102340446B - Method for realizing Ethernet-tree (E-tree) service in virtual private local area network service (VPLS) network and provider edge (PE) equipment - Google Patents

Abstract

The embodiment of the invention provides a method for realizing an Ethernet-tree (E-tree) service in a virtual private local area network service (VPLS) network and provider edge (PE) equipment. The method comprises the following steps of: receiving a data packet from customer edge (CE) equipment; judging whether the CE equipment transmitting the data packet is a root node or a leaf node; if the data packet is transmitted by the root node, adding a root tag into the data packet, and if the data packet is transmitted by the leaf node, adding a leaf tag into the data packet; performing pseudo wire (PW) packaging on the data packet; and transmitting the data packet by using a PW. By the method and the equipment provided by the embodiment of the invention, the E-tree service in the VPLS network is realized and can be well compatible with the conventional PE equipment; moreover, only one PW is required and more PWs and virtual switch instances are not required between two pieces of PE equipment.

Description

Implementation method and PE equipment of E-tree service in VPLS network

technical field

The embodiment of the present invention relates to the field of communication technologies, and in particular to a method for realizing an Ethernet tree (E-tree) service in a Virtual Private LAN Service (VPLS) network and a Provider Edge (PE for short) equipment.

Background technique

E-tree is a service defined by the Metro Ethernet Forum (MEF for short). E-tree has the following characteristics: the relationship between the root node and the leaf nodes is one-to-many, and there can be multiple root nodes. Node; the root node can send data packets to any root node and leaf node, and the leaf node can also send data packets to any root node.

VPLS is a technology that utilizes a wide area network architecture to virtualize an Ethernet LAN. Point connection, which is convenient for users to simultaneously access the MPLS network from multiple geographically dispersed points and access each other, just like these points are directly connected to the LAN. Since the core network mainly adopts IP/MPLS technology at present, there are more and more demands for providing virtual Ethernet services through VPLS.

Since VPLS technology is used in more and more networks, how to realize E-tree service in VPLS network is an urgent problem to be solved.

A method for implementing an E-tree service in a VPLS network in the prior art includes: implementing the E-tree service between two PE devices through two PWs, that is, the data packet sent by the root node is transmitted through one PW, The data packet sent from the leaf node is transmitted through another PW. After the egress PE device receives the data packet, it can determine whether the data packet is sent from the root node or the leaf node according to the PW.

The problem with this method is that two PWs are needed between each pair of PE devices, and two Virtual Switch Instances (VSI for short) are required at the same time, and both PWs and VSIs are very precious resources. When there are a large number of E-tree services, the PW and VSI may not be sufficient, and if the E-tree service occupies too many PW and VSI resources, other services (such as transparent Ethernet (E-LAN) services) will be required The PW and VSI resources are not enough.

Contents of the invention

Embodiments of the present invention provide a method for implementing an E-tree service in a VPLS network and a PE device, which can implement the E-tree service in the VPLS network without occupying many PWs and VSIs.

The embodiment of the present invention provides a method for realizing the E-tree service in a VPLS network, including:

receiving a data packet sent by a CE device, where the CE device is a root node or a leaf node;

judging whether the CE device is a root node or a leaf node;

If the data packet is sent by the root node, a root label is added to the data packet, and if the data packet is sent by a leaf node, a leaf label is added to the data packet;

Perform PW encapsulation on the data packet, and send the encapsulated data packet through the PW.

The embodiment of the present invention also provides a method for realizing the E-tree service in the VPLS network, including:

Receive ingress PE device data packets through PW;

parsing the data packet;

If the data packet includes a root label, then send the data packet to the root node and the leaf node connected to itself;

If the data packet includes a leaf label, then send the data packet to the root node connected to itself.

The embodiment of the present invention also provides a PE device, including:

A first processing module, configured to receive a data packet sent by a CE device, and determine whether the CE device is a root node or a leaf node;

The second processing module is configured to add a root label to the data packet when the data packet received by the first processing module is sent by the root node; If the data packet is sent from a leaf node, a leaf label is added to the data packet, and the data packet is encapsulated by the PW and then sent out through the PW.

The embodiment of the present invention also provides a PE device, including:

The PW egress module corresponding to each PW is used to receive the data packet of the ingress PE device through the PW, and parse the data packet;

The third processing module is used to send the data packet to the root node and the leaf node connected to itself when the data packet received by the PW egress module includes a root label; When the data packet includes the leaf label, the data packet is sent to the root node connected to itself.

The implementation method and PE equipment of the E-tree service in the VPLS network provided by the embodiment of the present invention add a root label or a leaf label to the received data packet to identify that the data packet is sent by the root node or the leaf node. In this way, the PE device receiving the data packet through the PW can forward or filter the data packet accordingly according to the root label or leaf label in the data packet. Specifically, if the data packet includes the root label, the data packet can be sent to all root nodes and leaf nodes connected to itself, and if the data packet includes the leaf label, the data packet can be sent to communicate with itself All the root nodes realize the forwarding and filtering of data packets, thereby realizing the E-tree service.

In the embodiment of the present invention, the root label and the leaf label are used to distinguish the data packets sent by the root node and the leaf node. Only one PW is needed between the two PE devices, and the realization of the E-tree service does not need to occupy more PW and VSI, therefore, when there are many types of services in the E-tree service, the PW and VSI required by the E-tree service will not be insufficient, nor will the PW and VSI resources required by other services be insufficient.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained according to these drawings without any creative effort.

Fig. 1 shows the flowchart of the implementation method embodiment one of the E-tree service in the VPLS network of the present invention;

Fig. 2 shows the flowchart of the implementation method embodiment two of the E-tree service in the VPLS network of the present invention;

Fig. 3 shows a kind of schematic diagram of the realization method of E-tree service in the VPLS network of the present invention;

FIG. 4 is a schematic diagram of the encapsulation form of data packets involved in various embodiments of the present invention;

FIG. 5 is a schematic diagram of negotiation between PE devices;

Fig. 6 shows another schematic diagram of the realization method of E-tree service in the VPLS network of the present invention;

FIG. 7 is a schematic structural diagram of Embodiment 1 of the PE equipment of the present invention;

FIG. 8 is a schematic structural diagram of Embodiment 2 of the PE equipment of the present invention;

FIG. 9 is a schematic structural view of Embodiment 3 of the PE equipment of the present invention;

FIG. 10 is a schematic structural diagram of Embodiment 4 of the PE equipment of the present invention;

FIG. 11 is a schematic structural diagram of Embodiment 5 of the PE equipment of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of preferred embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

As shown in Figure 1, it is the flow chart of the implementation method embodiment one of the E-tree service in the VPLS network of the present invention, including:

Step 101, receiving a data packet sent by a customer edge (Customer Edge, CE for short) device. When the VPLS network provides E-Tree services, each CE device can be a leaf node or a root node.

In a VPLS network, a PE device is connected to a CE device. When a data packet is sent from a CE device to a PE device, the PE device that receives the data packet is called an ingress PE device. The ingress PE device sends the data packet to other PE devices through the PW, and the other PE devices send the data packet to the destination CE device. A PE that receives data packets sent by an ingress PE through a PW is called an egress PE. The root node and the leaf node in each embodiment of the present invention are each CE device in the VPLS network.

Step 102, judging whether the CE device sending the data packet is a root node or a leaf node.

Specifically, when receiving the Ethernet data packet sent by the CE device, the PE device can identify from the port where the data packet is received whether the data packet is sent by the root node or by the leaf node. The PE device can further add a virtual local area network (Virtual Local Area Network, referred to as VLAN) tag in the data packet, and use the VLAN tag to identify whether the data packet is sent by the root node or by the leaf node.

Step 103, if the data packet is sent by the root node, then add the root label (Root Label) in the data packet, if the data packet is sent by the leaf node, then add the leaf label (Leaf Label) in the data packet .

In this step, the PE device can judge whether the data packet is sent from the root node or the leaf node according to the port attribute of the received packet or according to the VLAN tag. If the VLAN label in the data packet identifies that the data packet is sent by the root node, then add the root label in the data packet and delete the VLAN label; if the VLAN label identifies that the data packet is sent by the leaf node, then in the data packet Add a leaf label to and delete the VLAN label.

Step 104, PW-encapsulates the data packet, and sends the PW-encapsulated data packet through the PW.

As shown in Figure 2, it is the flow chart of the implementation method embodiment two of the E-tree service in the VPLS network of the present invention, including:

Step 201: Receive the data packet sent by the ingress PE device through the PW.

Step 202, analyzing the data packet.

Specifically, the data packet can be decapsulated, and the root label or leaf label in the data packet can be parsed out; then a VLAN tag can be added to the data packet according to the root label or leaf label in the data packet, wherein the VLAN tag is used to identify Whether the packet includes a root label or a leaf label before decapsulation.

A VLAN tag may be used to identify that the data packet includes a root tag before decapsulation, and another VLAN tag may be used to identify that the data packet includes a leaf tag before decapsulation.

Step 203, if the data packet includes a root label, send the data packet to all root nodes and leaf nodes connected to itself; if the data packet includes a leaf label, send the data packet to all root nodes connected to itself.

Specifically, it may be identified according to the VLAN tag in the data packet whether the data packet includes a root tag or a leaf tag before decapsulation. If the VLAN label in the data packet includes the root label before decapsulating the packet, delete the VLAN label, and send the data packet after deleting the VLAN label to the root node and the leaf node connected to itself; The VLAN label identifies the leaf label before the packet is decapsulated, delete the VLAN label, and send the data packet after deleting the VLAN label to the root node connected to itself, and send the data packet to the leaf node connected to itself Filtered.

In the E-tree service, the data packet sent by the root node can be sent to other root nodes and leaf nodes, and the data packet sent by the leaf node can be sent to the root node, but cannot be sent to other leaf nodes.

The implementation process of Embodiment 1 and Embodiment 2 of the present invention will be described below in conjunction with a specific network structure.

As shown in Fig. 3, it is a kind of schematic diagram of the implementation method of E-tree service in the VPLS network of the present invention, comprises three PE equipments of PE1, PE2 and PE3 in this VPLS network, PE1 is connected with root node R1 and leaf node L1, PE2 is connected to root node R2 and leaf node L2, and PE3 is connected to root node R3 and leaf node L3. PE1 and PE2 communicate through pseudowire PW1, PE1 and PE3 communicate through pseudowire PW2, and PE2 and PE3 communicate through pseudowire PW1. Pseudowire PW3 communication.

For example, the root node R1 sends a data packet (for example, an Ethernet data packet) to PE1, and the module receiving the data packet in PE1 can determine whether the data packet is sent by the leaf node or the root node according to the port of the received data packet. Then the module receiving the data packet can further add a VLAN tag to the data packet.

The destination address in the data packet may be a multicast address or a unicast address. The module in PE1 that receives the data packet can send the data packet to the corresponding VSI after adding the VLAN tag. Different VPLS services correspond to different VSIs.

The VSI searches the Media Access Control (MAC) address forwarding table, and if it finds that the destination address of the data packet is a multicast address, it sends the data packet to the PW entry module corresponding to each PW.

If the destination address of the data packet is found to be a unicast address, the PW corresponding to the destination address of the data packet is searched according to the MAC address forwarding table, and the data packet is sent to the PW entry module corresponding to the PW.

Since the data packet is sent by the root node (can be determined according to the VLAN tag in the data packet), the PW entry module adds the root tag to the data packet and deletes the VLAN tag before sending the data packet through the PW, and then sends the data The packet is encapsulated by the PW, and can be further encapsulated by the tunnel, and finally the data packet is sent to the peer PE device through the PW. For example, a data packet whose destination address is a multicast address is sent to PE2 and PE3 through PW2 and PW3.

For example, the leaf node L1 sends a data packet (for example, an Ethernet data packet) to PE1, and the module receiving the data packet in PE1 can determine whether the data packet is sent by the leaf node or the root node according to the port of the received data packet. Then the module receiving the data packet can further add a VLAN tag to the data packet.

The destination address in the data packet may be a multicast address or a unicast address. The module in PE1 that receives the data packet can send the data packet to the corresponding VSI after adding the VLAN tag. .

Through the MAC address forwarding table, if the VSI finds that the destination address of the data packet is a multicast address, it sends the data packet to the PW entry module corresponding to each PW.

If the destination address of the data packet is found to be a unicast address, the PW corresponding to the destination address of the data packet is searched according to the MAC address forwarding table, and the data packet is sent to the PW entry module corresponding to the PW.

Since the data packet is sent by the leaf node (can be determined according to the VLAN tag in the data packet), the PW entry module adds the leaf tag to the data packet and deletes the VLAN tag before sending the data packet through the PW, and then sends the data packet The packet is encapsulated by PW, and can be further encapsulated by tunnel, and then the data packet is sent to the peer PE device through the PW. For example, the data packet whose destination address is the multicast address is sent to PE2 and PE3 through PW2 and PW3.

After receiving the data packet, the PW egress module in PE2 parses the data packet. If the data packet includes a root label, the processing module in PE2 sends the data packet to all root nodes and leaf nodes connected to PE2, and if the data packet includes a leaf label, then sends the data packet to all root nodes connected to PE2 node.

Specifically, after receiving the data packet, PE2 can decapsulate the data packet, pop out the root label or leaf label, and can also add a VLAN tag to the data packet to identify whether the data packet includes the root label or the leaf label before parsing. Label. The data packet after adding the VLAN tag can be sent to the VSI, and the VSI sends it to the sending module corresponding to each CE device according to the data packet. If the VLAN tag indicates that the data packet includes a root tag before parsing, the sending module in PE2 deletes the VLAN tag, and sends the data packet to the root node and the leaf node connected to itself. If the VLAN tag identifies that the data packet includes a root tag before parsing, the sending module in PE2 deletes the VLAN tag and sends the data packet to the root node connected to itself.

In FIG. 3 , PE3 also receives the data packet, and the processing method of PE3 after receiving the data packet is the same as that of PE2.

In the embodiment shown in FIG. 1, steps 101-104 may be performed by an ingress PE device, such as PE1. In the embodiment shown in FIG. 2, steps 201 and 202 may be performed by an egress PE device, such as PE2 or PE3.

In the implementation method of the E-tree service in the VPLS network provided by the embodiment of the present invention, the ingress PE device adds a root label or a leaf label to the received data packet to identify that the data packet is sent by the root node or the leaf node. In this way, after the egress PE device receives a data packet from a PW, it can forward or filter the data packet accordingly according to the root label or leaf label in the data packet. Specifically, if the data packet includes a root label, the egress PE device can send the data packet to all root nodes and leaf nodes connected to itself; if the data packet includes a leaf label, the egress PE device can send the data The packet is sent to all root nodes connected to itself, so as to realize the forwarding and filtering of E-tree service data packets.

In the method provided by the embodiment of the present invention, since a root label or a leaf label is added to the data packet, the data packet can be forwarded or filtered at the Ethernet forwarding level, and there is no need to change the VSI, which can be well integrated with the existing The device is compatible.

In the embodiment of the present invention, the root label or leaf label is used to distinguish the data packets sent by the root node and the leaf node. Only one PW is needed between the two PE devices, and there is no need to set two PWs, and there is no need to use two VSIs. , reducing the requirements for PW and VSI resources. Therefore, when there are many types of services in the E-tree service, the PW and VSI required by the E-tree service will not be insufficient, and the PW and VSI resources required by other services will not be insufficient.

In each embodiment of the present invention, the root label or the leaf label may be added at the bottom of the multi-protocol label switching (Multi-Protocol Label Switching, MPLS for short) label stack of the data packet. As shown in Figure 4, it is a schematic diagram of the encapsulation form of the data packets involved in each embodiment of the present invention, the embodiment of the present invention includes this item of E-tree label (E-tree Label), which is usually related to packet payload (Ethernet Payload) ) is called the bottom of the MPLS label stack. In Figure 4, the control word (Control Word) is an optional item, so the E-tree label is the bottom of the MPLS label stack. In the figure, the value of the bottom identification field S in the MPLS label stack and the PW label is 0, and the value of the field S in the E-tree label is 1. In Figure 4, between the Ethernet payload and the optional control word is an Ethernet header (Ethernet Header).

E-tree takes different values, that is, it can represent root labels or leaf labels respectively. For example, you can set the value of the E-tree root label to 100, indicating that the label 100 under the E-tree service is the root label, and set the value of the E-tree leaf label to 200, indicating that the label 200 under the E-tree service is leaf label.

Since the MPLS system contains some reserved labels, such as 0-15, in the embodiment of the present invention, the values of the leaf label and the root label should be other values other than these values, so as to avoid confusion with the reserved labels of the MPLS system.

Compared with the method of using control words and other methods to identify whether the data packet is sent by the root node or the leaf node, in the embodiment of the present invention, an E-tree tag is added to the data packet to identify whether the data packet is sent by the root node or the leaf node In this way, there is no need to design a new forwarding engine, the data packet can be forwarded or filtered at the Ethernet forwarding level, and there is no need to change the VSI, which can be well compatible with existing equipment.

The VPLS network can be a full mesh network (full mesh), and each PE device in the network can pre-negotiate the attribute information of the root label or the leaf label. The attribute information of the root label and the leaf label may be, for example, a numerical value used to indicate the root label and the leaf label.

In a VPLS network, PWs can be established between each PE device based on a Label Distribute Protocol (LDP for short) protocol. The steps for each PE device to negotiate the attribute information of the root label or the leaf label may specifically include: each PE device exchanges LDP negotiation messages with each other, and the LDP negotiation message carries a Type-Length-Value (TLV for short) field , the TLV field includes the attribute information of the root label and the leaf label. Figure 5 is a schematic diagram of the negotiation between PE devices. Two PE devices send each other an LDP negotiation message with a TLV field. The TLV field includes the attribute information of the root label and the leaf label, for example, it may include the leaf label. Attribute information with a value of 200 and a root tag with a value of 100.

Of course, PE devices can also communicate based on the Border Gateway Protocol (BGP) protocol, and the message in the BGP protocol can carry the attribute information of the root label and the leaf label.

Alternatively, one PE device may send a message to each other PE device, and the message includes the attribute information of the root label and the leaf label.

In step 102, the ingress PE device may specifically add a root label or a leaf label to the data packet according to the pre-negotiated attribute information of the root label or the leaf label.

In the E-tree service, some PE devices are only connected to the leaf nodes, but not to the root node. In the embodiment of the present invention, such PE devices are called leaf node type PE devices. In this way, the PE device of the leaf node type can send a notification message to other PE devices, and the notification message includes the information of the PE device connected to the leaf node but not to the root node, that is, includes the information of the PE device of the leaf node type. After receiving the notification message, other PE devices can know which PE devices are leaf node type PE devices.

In this case, after other PE devices receive the data sent by the leaf node to which they are connected, they may not forward the data packet to the PE device of the leaf node type. That is to say, if the peer PE devices of a certain PW are all connected to leaf nodes, the ingress PE device can filter the data packets received from the leaf nodes in the PW ingress module, that is, for the The ingress PE device will not send the data packet through the PW corresponding to the PE device of the leaf node type, thus avoiding the occupation of communication resources by these data packets.

As shown in Figure 6, it is another schematic diagram of the implementation method of the E-tree service in the VPLS network of the present invention. In this embodiment, PE3 is only connected to the leaf node L3, but not connected to the root node, and is a leaf node type PE equipment. In this case, PE3 can send a notification message to PE1 and PE2 to declare that it is a leaf node type PE device, so that PE1 and PE2 can learn that PE3 is a leaf node type PE device. If L1 sends data packets to PE1, since PE3 is a leaf node type PE device, PE1 does not need to send data packets to PE3, thus preventing the data packets sent from PE1 to PE3 from occupying network resources. In essence, even if PE1 sends a data packet to PE3, because the data packet carries a leaf label, PE3 will filter the data packet instead of sending the data packet to L3.

For the embodiment shown in Figure 1, if the label added by the ingress PE device in the data packet is a leaf label, and the PE device corresponding to the opposite end of the PW is a leaf node type PE device, then the data is filtered out at the PW ingress module Bag.

This embodiment may further include a step of receiving a notification message. If the notification message includes information of a leaf node type PE device, the ingress PE device associates the notification information with a PW corresponding to the leaf node type PE device.

After the ingress PE device receives the notification message, the ingress PE device can learn which PW's opposite end is a PE device of the leaf node type. In step 104, if the data packet received by the ingress PE device is sent by a leaf node, and the PE device corresponding to the opposite end of the PW is a leaf node type PE device, then the PW ingress module filters out the data packet. If the data packet received by the ingress device is sent by the root node, the PW ingress module can perform PW encapsulation on the data packet and send it out through the PW without filtering.

FIG. 7 is a schematic structural diagram of Embodiment 1 of a PE device according to the present invention. The PE device includes a first processing module 11 and a second processing module 12 . The first processing module 11 is configured to receive a data packet sent by a CE device, and determine whether the CE device sending the data packet is a root node or a leaf node. The second processing module is connected with the first processing module 11, and is used for adding the root label in the data packet when the data packet received by the first processing module 11 is sent by the root node, and in the first processing module 11 If the received data packet is sent by a leaf node, add a leaf label to the data packet, and then send the data packet through the PW after PW encapsulation.

FIG. 8 is a schematic structural diagram of Embodiment 2 of the PE device of the present invention. In the PE device, the second processing module 12 includes a first VSI module 121 and a PW entry module 122 corresponding to each PW. The VSI module 121 is configured to send the data packet received by the first processing module 11 to the PW entry module 122 corresponding to the destination address in the data packet. The PW entry module 122 includes: a first processing submodule 122a, an encapsulation submodule 122b, and a sending submodule 122c. The first processing sub-module 122a is used to add a root label to the data packet when the data packet received by the first processing module 11 is sent by the root node, and the data packet received by the first processing module 11 is When the leaf node sends it, the leaf label is added to the data packet. The encapsulation submodule 122b is configured to perform PW encapsulation on the data packet processed by the first processing submodule 122a. The sending sub-module 122c is configured to send the data packet encapsulated by the encapsulating sub-module 122b through the PW.

Wherein, the first processing module 11 can specifically be used to receive the data packet sent by the CE device, determine whether the CE device sending the data packet is a root node or a leaf node, and can further add a VLAN tag to the data packet to identify whether the data packet is What is sent by the root node is still sent by the leaf node. Specifically, the first processing module 11 may determine whether the CE device sending the data packet is a root node or a leaf node according to the port attribute. Specifically, the first processing sub-module 122a can be used to add a root label to the data packet when the data packet received by the first processing module 11 is sent by the root node. Add the root label at the bottom; when the data packet received by the first processing module 11 is sent by the leaf node, add the leaf label in the data packet, specifically the leaf label can be added at the bottom of the MPLS label stack of the data packet. The first processing submodule 122a can also be specifically used to add the root tag in the data packet and delete the VLAN tag when the VLAN tag in the data packet identifies that the data packet is sent by the root node; If it is identified that the data packet is sent by a leaf node, a leaf label is added to the data packet, and the VLAN label is deleted.

FIG. 9 is a schematic structural diagram of Embodiment 3 of the PE device of the present invention. The PE device further includes a negotiation module 13 on the basis of the embodiment shown in FIG. 9, and the negotiation module 13 is connected to the first processing sub-module 122a. , which is used to negotiate the attribute information of the root label and leaf label with the peer PE device. The first processing module 12 may add a root label or a leaf label to the data packet according to the attribute information of the root label and the leaf label.

Specifically, the first processing sub-module 122a is used to add a root tag to the data packet according to the attribute information of the root tag or the leaf tag when the data packet received by the first processing module 11 is sent by the root node, In the case that the data packet received by the first processing module 11 is sent by the leaf node, a leaf label is added to the data packet according to the attribute information of the leaf label.

It may also include a message processing module 14, which is connected to the first processing sub-module 122a, and is used to receive notification messages sent by other PE devices, and in the case where the notification messages include leaf node type PE device information , associating the notification message with the PW corresponding to the PE device of the leaf node type.

Specifically, the message processing module 14 may include a message receiving submodule 141 , a processing submodule 142 and an associating submodule 143 . The message receiving sub-module 141 is configured to receive the notification message sent by other PE devices. The processing sub-module 142 is connected with the message receiving sub-module 141, and is used to determine whether the notification message includes the information of the PE device of the leaf node type. The associating sub-module 143 is connected to the PW entry processing module 122, and is used for associating the notification message with the PW corresponding to the PE device of the leaf node type. If the first processing submodule 122a adds a leaf label to the received data packet, and its PW is associated with a PE device of the leaf node type, then the data packet may be filtered out.

FIG. 10 is a schematic structural diagram of Embodiment 4 of a PE device according to the present invention. The PE device includes a PW egress module 21 and a third processing module 22 corresponding to each PW. The PW egress module 21 corresponding to each PW is used to receive data packets through the PW and analyze the data packets. The third processing module 22 is connected to each PW egress module 21, and is used to send the data packet to the root node and the leaf node connected to itself when the data packet received by the PW egress module 21 includes a root label; If the data packet received by the egress module 21 includes a leaf label, it sends the data packet to the root node connected to itself.

FIG. 11 is a schematic structural diagram of Embodiment 5 of the PE device of the present invention. In this embodiment, the PW egress module 21 corresponding to each PW includes a receiving submodule 211, a decapsulating submodule 212, and a second processing submodule 213. . The receiving sub-module 211 is used for receiving data packets through the PW. The decapsulation sub-module 212 is connected to the receiving sub-module 211, and is used for decapsulating the data packet received by the receiving sub-module 211, and popping the root label or leaf label in the data packet. The second processing submodule 213 is connected with the decapsulation submodule 212, and is used to add a VLAN tag to the data packet processed by the decapsulation submodule 212. The VLAN tag identifies whether the data packet includes a root label or a leaf label before decapsulation. .

In this embodiment, the decapsulation submodule 212 may specifically pop out the E-tree label from the bottom of the MPLS label stack of the data packet received by the receiving submodule, and the E-tree label is a leaf label or a root label.

The third processing module 22 may include a second VSI module 221 and a sending module 222 corresponding to each CE device.

The second VSI module 221 is connected to the second processing sub-module 213, and is configured to send the data packet received by the PW entry module to the sending module corresponding to each CE device.

The sending module 222 corresponding to each CE device is used to receive the data packet, if the VLAN tag in the data packet identifies that the data packet includes a root tag before decapsulation, and the CE device corresponding to the sending module is a root node or a leaf node , then delete the VLAN label in the data packet, and send the data packet after deleting the VLAN label to the CE device corresponding to the sending module; if the VLAN label in the data packet indicates that the data packet includes a leaf label before decapsulating, and The CE equipment corresponding to the sending module is a root node, then delete the VLAN label in the data packet, and send the data packet after deleting the VLAN label to the CE equipment corresponding to the sending module; if the VLAN label in the data packet identifies The data packet includes a leaf label before decapsulation, and the CE device corresponding to the sending module is a leaf node, then the data packet sent to the CE device corresponding to the sending module is filtered out.

The implementation method and PE equipment of the E-tree service in the VPLS network provided by the embodiment of the present invention add a root label or a leaf label to the received data packet to identify that the data packet is sent by the root node or the leaf node. In this way, the PE device receiving the data packet through the PW can forward or filter the data packet accordingly according to the root label or leaf label in the data packet. Specifically, if the data packet includes the root label, the data packet can be sent to all root nodes and leaf nodes connected to itself, and if the data packet includes the leaf label, the data packet can be sent to communicate with itself All the root nodes realize the forwarding and filtering of data packets, thus realizing the E-tree service.

In the embodiment of the present invention, the first processing module adds a root label or a leaf label to the data packet to distinguish the data packet sent by the root node and the leaf node. Only one PW is needed between two PE devices to realize the E-tree Services do not need to occupy a large number of PWs and VSIs. Therefore, when there are many types of services in the E-tree service, the PWs and VSIs required by the E-tree service will not be insufficient, and will not cause other services. The PW and VSI resources are not enough.

Those of ordinary skill in the art can understand that all or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the It includes the steps of the above method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still be Modifications are made to the technical solutions described in the foregoing embodiments, or equivalent replacements are made to some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims (8)

1. an implementation method of Ethernet tree service in a virtual private local area network service network, is characterized in that, comprising: receiving a data packet sent by a client edge device, where the client edge device is a root node or a leaf node; Adding a virtual local area network label to the data packet, the virtual local area network label is used to identify whether the data packet is sent by the root node or by the leaf node; judging whether the client edge device is a root node or a leaf node; If the data packet is sent by the root node, a root label is added to the data packet, and if the data packet is sent by a leaf node, a leaf label is added to the data packet, and the root The label or the leaf label is set at the bottom of the MPLS label stack of the data packet; Encapsulating the data packet with a pseudowire, and sending the encapsulated data packet through a pseudowire; If the data packet is sent by the root node, adding a root label to the data packet specifically includes: if the virtual local area network label in the data packet identifies that the data packet is sent by the root node , then add a root label in the data packet, and delete the virtual local area network label; If the data packet is sent from a leaf node, adding a leaf label to the data packet specifically includes: if the virtual local area network label identifies that the data packet is sent from a leaf node, then adding a leaf label to the data packet Add the leaf label to the package, and delete the vlan label. 2. The method according to claim 1, further comprising: negotiating with the peer operator edge device on the attribute information of the root label or the leaf label before receiving the data packet sent by the client edge device. 3. The method according to claim 1, further comprising: if the data packet is sent by a leaf node, and the opposite carrier edge device is a leaf node type carrier edge device, filtering drop the packet. 4. an implementation method of ether tree service in a virtual private area network service network, characterized in that, comprising: Receive data packets from the edge device of the ingress operator through the pseudowire; parsing the data packet; If the data packet includes a root label, then send the data packet to the root node and the leaf node connected to itself; If the data packet includes a leaf label, the data packet is sent to the root node connected to itself, and the root label or the leaf label is set at the bottom of the multi-protocol label switching label stack of the data packet; The parsing of the data packet includes: decapsulating the data packet, and popping the root label or leaf label in the data packet; adding a virtual local area network label to the data packet, and the virtual local area network label is used for Identify whether the data packet includes a root label or a leaf label before decapsulation. 5. The method according to claim 4, wherein if the data packet includes a root label, sending the data packet to the root node and the leaf node connected to itself, comprising: If the virtual local area network label in the data packet identifies that the data packet includes a root label before decapsulating, then delete the virtual local area network label, and send the data packet after deleting the virtual local area network label to the server connected to itself root node and leaf node; If the data packet includes a leaf label, the data packet is sent to the root node connected to itself, including: If the virtual local area network label in the data packet identifies that the data packet includes a leaf label before decapsulating, then delete the virtual local area network label; if it is the root node connected with itself, then delete the virtual local area network label The data packet sent to the root node; If the virtual local area network label in the data packet identifies that the data packet includes a leaf label before decapsulating, then delete the virtual local area network label; if it is a leaf node connected to itself, then delete the virtual local area network label packets are filtered out. 6. A carrier edge device, characterized in that it comprises: A first processing module, configured to receive a data packet sent by a client edge device, and determine whether the client edge device is a root node or a leaf node; The second processing module is configured to add a root label at the bottom of the multi-protocol label switching label stack of the data packet when the data packet received by the first processing module is sent by the root node. root label; when the data packet received by the first processing module is sent by a leaf node, a leaf label is added to the bottom of the MPLS label stack of the data packet, and the data packet is After the pseudowire is encapsulated, it is sent out through the pseudowire; The first processing module is specifically configured to receive a data packet sent by a client edge device, determine whether the client edge device is a root node or a leaf node, and add a virtual local area network tag to the data packet to identify the data packet Whether the packet is sent by the root node or by a leaf node; The second processing module includes a first virtual switching instance module and a pseudowire entry module corresponding to each pseudowire; The first virtual switching instance module is configured to send the data packet received by the first processing module to the pseudowire entry module corresponding to the destination address in the data packet; The pseudowire entry module includes: The first processing sub-module is used to add a root label to the data packet when the data packet received by the first processing module is sent by the root node; When the data packet is sent by a leaf node, a leaf label is added to the data packet; The first processing sub-module is specifically configured to add a root label to the data packet and delete the virtual local area network label when the virtual local area network label identifies that the data packet is sent by the root node; If the virtual local area network label identifies that the data packet is sent by a leaf node, then add a leaf label to the data packet, and delete the virtual local area network label; An encapsulation submodule, configured to perform pseudowire encapsulation on the data packet processed by the first processing submodule; The sending sub-module is configured to send out the data packet encapsulated by the encapsulating sub-module through the pseudowire. 7. The operator edge device according to claim 6, further comprising a negotiation module, configured to negotiate with the opposite operator edge device on the attribute information of the root label or the leaf label. 8. A carrier edge device, characterized in that it comprises: The pseudowire egress module corresponding to each pseudowire is used to receive the data packet of the edge device of the ingress operator through the pseudowire, and analyze the data packet; The third processing module is used to send the data packet to the root node and the leaf node connected to itself when the data packet received by the pseudowire egress module includes a root label; when the pseudowire egress module receives In the case that the received data packet includes a leaf label, the data packet is sent to the root node connected to itself; The pseudowire export modules corresponding to each pseudowire include: The receiving submodule is used to receive data packets through pseudowires; The decapsulation submodule is used to decapsulate the data packet received by the receiving submodule, and pop up the root label or leaf label in the data packet; The second processing submodule is configured to add a virtual local area network label to the data packet, and the virtual local area network label is used to identify whether the data packet includes a root label or a leaf label before decapsulation.