CN102891788B - VPLS service establishing methods and device - Google Patents

Abstract

The present invention discloses a method and device for establishing a VPLS service. The method includes: creating a VPLS service on a PE device, and generating a service ID uniquely identifying a service instance within the scope of the PE device for the VPLS service; according to the above service ID Establishing one or more pseudowire PWs, designating the above one or more PWs to correspond to the above VPLS service; establishing a binding relationship between the above one or more PWs and the above VPLS service. The technical scheme provided by the invention solves the problem that the PW between PEs (or between NPEs) has no protection function in the VPLS service, and further achieves the effect of strengthening the robustness of the VPLS service and improving the availability of the VPLS service.

Description

Method and device for establishing VPLS service

technical field

The present invention relates to the communication field, in particular to a method and device for establishing a VPLS (Virtual Private LAN Service, Virtual Private LAN Service) service.

Background technique

Today's IP networks have spread all over the world. How to use the existing IP networks to provide low-cost forwarding services for enterprises is gradually attracting the attention of various operators. Therefore, MPLS (Multi-Protocol Label Switching, multi-protocol label switching) VPN (VirtualPrivate Network, virtual private network) technology emerges at the historic moment, this technology can provide VPN service on the IP network, and has the convenience of setting the bandwidth rate, Features such as simple configuration.

There are two types of MPLS-based VPN services, namely L3 (Layer 3) MPLS VPN and L2 (Layer 2) MPLS VPN. L2 MPLS VPN includes VPLS and VPWS (Virtual Pfivate Wire Service, virtual private line service), of which VPWS is only suitable for point-to-point networking, and VPLS can realize multipoint-to-multipoint VPN networking, so it can provide operators with Provide a more complete solution, and also avoid access to user internal routes like L3 VPN. In this way, operators can manage and operate only one network, and provide traditional IP services, L3VPN, L2VPN and other services on one network at the same time, thus avoiding a large amount of construction, maintenance and operation costs for operators.

VPLS is a service that provides services similar to LAN (Local Area Network, local area network) on MPLS network. , these devices are directly connected to a LAN like. VPLS is the user's extension of the LAN to the MAN (Metro Area Network, Metropolitan Area Network), or even the WAN (Wide Area Network, Wide Area Network).

VPLS simulates the forwarding mechanism of LAN, that is, forwards Ethernet (Ethernet) packets through the MAC (Medium Access Control, Media Access Control) address, and floods the frames that fail to find the MAC address, that is, copies the frames to belong to all other ports in the same LAN except the receiving source port). VPLS also simulates the MAC address learning function of LAN. When a frame is received, it learns the mapping relationship between the source MAC address of the frame and the incoming port. In addition, VPLS also simulates the broadcast function of LAN, and floods the message when receiving a frame whose destination MAC address is a broadcast address or a multicast address. In addition, VPLS also simulates the MAC address aging function of the LAN. After learning a certain MAC address, if no frame is received from the MAC address within a certain period of time, the MAC address is considered invalid and a local mapping relationship is required. delete from the table. The VPLS simulates a PW (Pseudo Wire) as an Ethernet port, that is, when learning a MAC address, the port number in the MAC-to-port mapping table can also be the corresponding relationship between the MAC and the PW.

In the VPLS technology, all LAN emulations are implemented by PE (ProviderEdge, operator's edge) equipment.

In the application of VPLS technology, when the PE equipment connected to the CE (Custom Edge, user edge) equipment fails, the entire user service may be interrupted. The device can be connected to two PE devices of the same VPLS service at the same time, and the CE device can control one connection to be in the active state and the other connection to be in the standby state; the two PE devices involved in dual-homing can also control one connection to be One is the main one, and the other one is the backup. When the active link fails, the CE device can quickly switch the service flow to the standby link, thus avoiding service interruption.

In VPLS technology, there is also a H-VPLS (Hierarchy of VPLS) technology, which belongs to hierarchical VPLS, in which PE equipment is divided into NPE (network side PE) and UPE (user side PE), and CE equipment is connected to UPE equipment , the UPE device is connected to the NPE device, and a full link is used between the NPEs. This technology can alleviate the N-square problem of PW caused by the full link of PE, and solve the scalability problem to a large extent. In addition, similar to the aforementioned dual-homing protection mechanism, a UPE device can also be dual-homing connected to two NPE devices to form a backup protection mechanism.

Combining the above two protection technologies, they are similar to the protection of the link between the operator and the customer. Once the PW between PE and PE (non-H-VPLS) or between NPE and NPE (H-VPLS) fails, No effective method has been proposed yet.

A relatively key technology of VPLS is the creation of PW. The PWE3 (end-to-end pseudowire emulation) working group of IETF (Internet Engineering Task Force, Internet Engineering Task Force) has defined several standards of PW. In addition, IETF also formulated the RFC (Request for Comments) of VPLS, and clearly pointed out that PWID (Pseudowire IP) is used to indicate the service ID. Since VPLS is composed of multiple independent PWs, the PWID of the PW is limited. Must be consistent. In addition, in terms of standard definitions, a PW is uniquely determined for a triplet (the IP address of the local PE device, the IP address of the peer PE device, and the PWID). Therefore, for a VPLS service, it is required that the PWIDs must be consistent, and because of the limitation of triplets, only one PW can be established between two PEs. Then, according to the current common processing method in the industry, the PW between PE and PE (non-H-VPLS) or between NPE and NPE (H-VPLS) of VPLS has no protection function. For this problem, no effective solution has been proposed yet.

Contents of the invention

The main purpose of the present invention is to provide a VPLS service establishment method and device to solve the above problems.

According to one aspect of the present invention, a method for establishing a VPLS service is provided, including: creating a VPLS service on a PE device, and generating a unique service ID for determining a service instance within the scope of the PE device for the VPLS service; according to the above-mentioned service The ID establishes one or more PWs, specifies that the one or more PWs correspond to the above-mentioned VPLS service; and establishes a binding relationship between the above-mentioned one or more PWs and the above-mentioned VPLS service.

Establish one or more PWs according to the service ID, and designate the above-mentioned one or more PWs to correspond to VPLS services, including one of the following: Establish multiple PWs between the local PE and the peer PE, where the services corresponding to the multiple PWs The IDs are the same; a PW is established between the local PE and the remote PE, and the service ID corresponding to the PW is different from the service ID corresponding to the PW between the local PE and other peer PEs.

Establishing the binding relationship between PW and VPLS service includes: setting the binding relationship between PW and VPLS service between the local PE and the peer PE; setting the binding relationship between PW and VPLS service between the peer PE and the local PE .

Setting the binding relationship between the PW and the VPLS service between the local PE and the remote PE includes: specifying the working PW and the protection PW in the PW between the local PE and the remote PE, and setting both the working PW and the protection PW to In the binding relationship; specify the PW to be protected for the protected PW.

Establishing the binding relationship between PW and VPLS service also includes: setting the binding relationship between PW and VPLS service between the local PE and other peer PEs; setting the binding relationship between PW and VPLS service between other peer PEs and local PE binding relationship.

According to another aspect of the present invention, a device for establishing a VPLS service is provided, including: a service module, configured to create a VPLS service on a PE device, and generate a unique service instance for the VPLS service within the scope of the PE device Service ID; Pseudowire module, used to establish one or more PWs according to the above-mentioned service ID, specifying that the above-mentioned one or more PWs correspond to the above-mentioned VPLS service; binding module, used to establish the above-mentioned one or more PWs and the above-mentioned VPLS service binding relationship.

The pseudowire module includes at least one of the following: a first establishment unit, configured to establish multiple PWs between the local PE and the peer PE, wherein the service IDs corresponding to the multiple PWs are the same; the second establishment unit is used to A PW is established between the local PE and the peer PE, where the service ID corresponding to a PW is different from the service ID corresponding to the PW between the local PE and other peer PEs.

The binding module includes: a first setting unit, which is used to set the binding relationship between the PW and the VPLS service between the local PE and the peer PE; the second setting unit, which is used to set the binding relationship between the peer PE and the local PE. Binding relationship between PW and VPLS service.

The first setting unit includes: a first specifying subunit, which is used to specify a working PW and a protection PW in the PW between the local PE and the peer PE, and set both the working PW and the protection PW into the binding relationship; Specifies the subunit, which is used to specify the PW to be protected for the protected PW.

The binding module also includes: a third setting unit, which is used to set the binding relationship between the PW and the VPLS service between the local PE and other peer PEs; the fourth setting unit, which is used to set other peer PEs to the local PE The binding relationship between the PW and the VPLS service.

Through the present invention, a unique service ID is generated for the service when the VPLS service is created, the PE device creates a PW according to the service ID, and finally binds the required PW with the VPLS service, which solves the problem of VPLS service The problem that the PW between PEs (or between NPEs) has no protection function can further achieve the effect of strengthening the robustness of VPLS services and improving the availability of VPLS services.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations to the present invention. In the attached picture:

Fig. 1 is the flow chart of the method for establishing a VPLS service according to an embodiment of the present invention;

Fig. 2 is the structural representation of the PE that bears the weight of VPLS service according to the example of the present invention;

Fig. 3 is a flow chart of creating a PW according to an example of the present invention;

Fig. 4 is the flow chart of VPLS service and PW binding according to the example of the present invention;

Fig. 5 is a structural block diagram of a device for establishing a VPLS service according to an embodiment of the present invention.

detailed description

Hereinafter, the present invention will be described in detail with reference to the drawings and examples. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

Fig. 1 is a flowchart of a method for establishing a VPLS service according to an embodiment of the present invention. As shown in Figure 1, the VPLS service establishment method according to the embodiment of the present invention includes:

Step S102, creating a VPLS service on the PE device, and generating a service ID that can uniquely determine a service instance within the scope of the PE device for the VPLS service;

Step S104, establishing one or more PWs according to the above-mentioned service ID, and specifying that the above-mentioned one or more PWs correspond to the above-mentioned VPLS service;

Step S106, establishing a binding relationship between the above-mentioned one or more PWPWs and the above-mentioned VPLS service.

The VPLS service establishment method provided by this implementation example, on the basis of the original VPLS service establishment method, improves the VPLS service by adding a dedicated Service ID (service ID) that does not have a one-to-one correspondence with the PWID in the protocol message The PW protection function between PE and PE (non-H-VPLS) or between NPE and NPE (H-VPLS), thus strengthening the robustness of VPLS services and improving the availability of VPLS services. The PE equipment mentioned in this example includes PE and NPE.

In this preferred embodiment, two ways of establishing a PW according to a service ID are listed. Preferably, step S104 may further include one of the following processes:

(1) Multiple PWs are established between the local PE and the remote PE, and the service IDs corresponding to the multiple PWs are the same;

(2) A PW is established between the local PE and the peer PE, and the service ID corresponding to the PW is different from the service ID corresponding to the PW between the local PE and other peer PEs.

If the PW needs a protection mechanism, perform processing (1), establish multiple PWs between the local PE and the remote PE, and the service IDs of these PWs are the same, but the PWID is different; if the PW does not require a protection mechanism, perform processing (2) A PW is established between the local PE and the peer PE, and the service ID of the PW is different from that of any other PW between the local PE and the peer PE, but the PWID can be the same.

Preferably, step S106 may further include the following processing:

(1) Set the binding relationship between the PW and the VPLS service between the local PE and the peer PE;

(2) Set the binding relationship between the PW and the VPLS service between the remote PE and the local PE.

The local PE and the remote PE are relative terms. When establishing the binding relationship between the PW and the VPLS service, you must first set the binding relationship between the PW and the VPLS service between the local PE and the remote PE. Complete the setting of the binding relationship between the PW and the VPLS service between the remote PE and the local PE.

There are many ways to set the binding relationship between the PW and the VPLS service, and this preferred embodiment provides a preferred way. Preferably, setting the binding relationship between the PW and the VPLS service between the local PE and the peer PE may include the following processing:

(1) Specify the working PW and protection PW in the PW between the local PE and the peer PE, and set both the working PW and the protection PW into the binding relationship;

(2) Designate the PW to be protected for the protected PW.

This preferred example provides a simple and practical method for setting the binding relationship. If the PW between the local PE and the remote PE needs PW protection, when setting the binding between the PW and the service, you need to specify the working PW and the protection PW and set all the PWs involved in the PW protection into the binding relationship, and then Specify whether the PW involved in PW protection is a working PW or a protection PW. The protection PW can protect the working PW, or protect another protection PW, that is, double protection. Of course, if the PW between the local PE and the remote PE does not require PW protection, when setting the binding between the PW and the service, you only need to specify the bound PW.

Preferably, step S106 may further include the following processing:

(1) Set the binding relationship between the PW and the VPLS service between the local PE and other peer PEs;

(2) Set the binding relationship between the PW and the VPLS service between other peer PEs and the local PE.

Multiple PWs can be established between all PEs corresponding to a VPLS service for protection according to the service ID. Of course, protection can only be carried out between certain PEs. The specific scope depends on the actual situation.

The above preferred embodiments will be described in detail below in conjunction with examples.

The PE structure in this example is shown in Figure 2, and the entire VPLS service establishment process is described as follows:

First, create a VPLS service on the local PE, and the Service ID of the VPLS service is different from the Service ID of other VPLS services.

As shown in Figure 2, the VPLS service VPLS-1 is jointly established by PE1, PE2, and PE3. PE1, PE2, and PE3 establish VPLS services locally, and the Service IDs of the created VPLS services are all 1.

After the Service ID is generated, start to create a PW, as shown in Figure 3, the process of creating a PW includes:

Step S302, creating a PW according to the service id, the PWID and the IP address of the peer PE.

The PW defined in the RFC 4447 standard of the IETF is bidirectional. The PW is composed of a pair of unidirectional LSPs between the two endpoints PE. The PWID of the pair of unidirectional LSPs is the same, that is, the unique identifier of a PW is Triple information (local PE IP address, peer PE IP address, PWID).

In the example, the original protocol is extended. When the local PE assigns a PW label to the peer PE, the signaling message not only carries the peer PE IP address and PWID information, but also additionally carries the Service ID field. , at this time, the PW is still unidirectional, and the PW is composed of a pair of unidirectional LSPs between the PW endpoints PE, and the two-tuple (ServiceID, PWID) of the pair of unidirectional LSPs are the same, that is, the unique identifier of a PW is Four-tuple information (local PE IP address, peer PE IP address, ServiceID, PWID).

Step S304, judging whether the PW has a protection attribute.

In this example, whether the PW has the protection attribute needs to be determined according to the user's input.

Step S306, if the PW has the protection attribute, multiple PWs are created between the local PE and the peer PE. These PWs have the same Service ID as the established PWs belonging to the same PW protection group, but different PWIDs.

In step S308, if the PW does not have the protection attribute, no additional PW needs to be established between the local PE and the remote PE.

By completely executing the above steps, a PW between a pair of PEs can be established according to the user's protection attribute settings for the PW. The Service IDs of these PWs are the same, but the PWIDs are different.

Since the VPLS service is a multi-point service, multiple PEs are required to complete service forwarding together, so it is necessary to establish a PW between any two PEs in the set of multiple PEs. The preceding steps can already establish a PW between a pair of PEs. Therefore, it is only necessary to perform the preceding steps S302, S304, S306, and S308 step by step between two PEs in all PE sets to complete the establishment of all PWs. The implementation is as follows:

For PE1 shown in Figure 2, since the PW between PE1 and PE2 has protection attributes, PE1 executes steps S302, S304, and S306 twice to establish the unidirectional pseudo-wire PW-1 and unidirectional pseudo-wire PW-1 between PE1 and PE2. Line PW-2. Since the PW between PE1 and PE3 does not have the protection attribute, PE1 establishes a unidirectional pseudo-wire PW-4 between PE1 and PE3 by performing steps S302, S304, and S308. The Service IDs of these pseudo-wires are 1.

For PE2 shown in Figure 2, since the PW between PE2 and PE1 has protection attributes, PE2 establishes unidirectional pseudowires PW-1 and PW- 2. Since the PW between PE2 and PE3 does not have the protection attribute, PE2 establishes a unidirectional pseudowire PW-4 between PE2 and PE3 by performing steps S302, S304, and S308. The Service IDs of these pseudowires are all 1.

For PE3 shown in Figure 2, since the PW between PE3 and PE2 does not have protection attributes, PE3 establishes a unidirectional pseudowire PW-4 between PE3 and PE2 by performing steps S302, S304, and S308. The PWs between PE3 and PE1 do not have the protection attribute. PE3 establishes a unidirectional pseudowire PW-3 between PE3 and PE1 by performing steps S302, S304, and S308. The Service IDs of these pseudowires are all 1.

When all pseudowires are established according to the protection attribute, and the VPLS service has been established, then enter the binding step of the VPLS service and the pseudowire, as shown in Figure 4, including:

Step S402, setting the binding between the PW and the VPLS service between the local PE and the remote PE.

The VPLS service is carried by the pseudowire, and through the setting and binding in this step, a corresponding relationship is formed between the service and the pseudowire.

Step S404, judging whether the pseudowire has a protection attribute.

According to step S304, it can be obtained whether the pseudowire has a protection attribute, and the protection attribute is specified by the user according to the VPLS service requirement. For example, as shown in Figure 1, protection is required between PE-1 and PE-2 of the VPLS-1 service, and protection is not required between PE-2 and PE-3. Then, the user can set PE-1 and PE- The pseudowire between 2 has a protection attribute, and it can be set that the pseudowire between PE-2 and PE-3 does not have a protection attribute. If it has a protection attribute, proceed to step S406, and if it does not have a protection attribute, proceed to step S406. S408.

Step S406, binding the VPLS service to the protected pseudowire with the same Service ID and the same peer PE IP.

Referring to step S404, there is a protection attribute between PE-1 and PE-2 of the VPLS-1 service, and two pseudowires are created in steps S304 and S306, respectively PW1 and PW2, and PW1 and PW2 have a protection relationship, Step S404 has bound one of the PW1 and VPLS-1 services, after judging that there is a protection attribute between PE-1 and PE-2 of the VPLS-1 service, then in this step, bind PW2 and VPLS-1 Certainly.

Step S408, no additional binding needs to be set.

Since the pseudowire does not have the protection attribute, after step S404, there is no need to set an additional binding relationship between the VPLS service and the pseudowire.

The foregoing step S402 to step S404 can already create a VPLS service of a PE, and bind the PW and VPLS service of this PE and a peer PE in the VPLS service. Since the VPLS service is a multipoint service, pseudowires have been established between the PE and all other PEs, and these pseudowires must be bound to the service. This PE can follow the requirements of steps S402, S404, S406, and S408 to connect the VPLS services involved All pseudowires between other PEs except this PE and this PE are bound to the VPLS service.

As shown in Figure 2, PE1 first completes the setting of the pseudowire and VPLS service binding relationship between the VPLS-1 service and PE2. By setting the PW-1 and VPLS-1 service binding relationship respectively, the Service binding relationship; then according to the order of S402, S404, S408, set the pseudowire and VPLS service binding relationship between PE1 and PE3, that is, set the PW-3 and VPLS-1 service binding relationship.

Since the VPLS service is a multipoint service, each PE in the VPLS service needs to create a VPLS service, and each PE needs to bind the pseudowire and the VPLS service. It can be completed according to the aforementioned steps S402, S404, S406, and S408, and the specific implementation is as follows:

For PE2 shown in Figure 2, first: PE2 creates a VPLS-1 service by executing step S402, and then, because the pseudowire between PE2 and PE1 has protection attributes, PE2 executes steps S402, S404, and S406 to complete the connection between PE2 and PE1. Binding settings between PW1, PW2 and VPLS-1. Finally, because the pseudowire between PE2 and PE3 does not have protection attributes, PE2 performs steps S402, S404, and S408 to complete the PW-4 and VPLS-1 between PE2 and PE3. 1 for binding settings.

For PE3 shown in Figure 2, first: PE3 creates a VPLS-1 service by executing step S402, and then, because the pseudowire between PE3 and PE1 does not have protection attributes, PE3 executes steps S402, S404, and S408 to complete the connection between PE3 and PE1. Binding settings between PW-3 and VPLS-1, and finally, because the pseudowire between PE3 and PE2 does not have protection attributes, PE3 performs steps S402, S404, and S408 to complete PW-4 and VPLS between PE3 and PE2 -1 for binding settings.

In this example, the pseudowire triplet (IP address of the local PE device, IP address of the peer PE device, PWID) is extended to a pseudowire quadruple (IP address of the local PE device, IP address of the peer PE device, Service ID, PWID), determine whether they belong to the same VPLS service through the ServiceID, so that multiple pseudowires with protection relationship can be established between a pair of PE equipment for the same VPLS service, and finally the protection of the VPLS service can be provided.

Fig. 5 is a structural block diagram of a VPLS service establishment device according to an embodiment of the present invention. As shown in Fig. 5, the VPLS service establishment device according to an embodiment of the present invention includes:

A service module 52, configured to create a VPLS service on the PE device, and generate a service ID that can uniquely determine a service instance within the scope of the PE device for the VPLS service;

The pseudowire module 54 is connected to the service module 52, and is used to establish one or more PWs according to the above-mentioned service ID, and specify that the above-mentioned one or more PWs correspond to the above-mentioned VPLS service;

The binding module 56 is connected to the pseudowire module 54 and configured to establish a binding relationship between the above-mentioned one or more PWs and the above-mentioned VPLS service.

The VPLS service establishment device provided by this implementation example improves the relationship between VPLS service PE and PE (non-H-VPLS) or The PW protection function between NPE and NPE (H-VPLS), thereby strengthening the robustness of VPLS services and improving the availability of VPLS services.

Preferably, the pseudowire module 54 may include at least one of the following units:

The first establishment unit is used to establish multiple PWs between the local PE and the peer PE, and the service IDs corresponding to the multiple PWs are the same;

The second establishment unit is used to establish a PW between the local PE and the peer PE, and the service ID corresponding to the PW is different from the service ID corresponding to the PW between the local PE and other peer PEs.

If the PW needs a protection mechanism, the first establishment unit will establish multiple PWs between the local PE and the peer PE, and the service IDs of these PWs are the same, but the PWIDs are different; if the PW does not require a protection mechanism, the second establishment unit The unit will establish a PW between the local PE and the peer PE, and the service ID of this PW is different from that of any other PW between the local PE and the peer PE, but the PWID can be the same.

Preferably, the binding module 56 may include:

The first setting unit is used to set the binding relationship between the PW and the VPLS service between the local PE and the peer PE;

The second setting unit is used to set the binding relationship between the PW and the VPLS service between the peer PE and the local PE.

The local PE and the remote PE are relative terms. When establishing the binding relationship between the PW and the VPLS service, you must first set the binding relationship between the PW and the VPLS service between the local PE and the remote PE. After completing the setting of the binding relationship between the PW and the VPLS service between the peer PE and the local PE, the first setting unit and the second setting unit can complete the above functions.

Preferably, the above-mentioned first setting unit may include:

The first specifying subunit is used to specify a working PW and a protection PW in the PW between the local PE and the peer PE, and set both the working PW and the protection PW into the binding relationship;

The second specifying subunit is used for specifying the PW to be protected for the protected PW.

If the PW between the local PE and the remote PE needs PW protection, when setting the binding between PW and service, the first designated subunit will designate the working PW and protection PW and set all PWs involved in PW protection to the binding In the fixed relationship, the second specifying subunit specifies whether the PW involved in PW protection is a working PW or a protection PW. The protection PW can protect the working PW, or can protect another protection PW, that is, double protection. If the PW between the local PE and the remote PE does not require PW protection, you only need to specify the bound PW when setting the binding between the PW and the service.

Preferably, the binding module 56 may also include:

The third setting unit is used to set the binding relationship between the PW and the VPLS service between the local PE and other peer PEs;

The fourth setting unit is used to set the binding relationship between the PW and the VPLS service between other peer PEs and the local PE.

Multiple PWs can be established between all PEs corresponding to a VPLS service for protection according to the service ID. Of course, protection can only be carried out between certain PEs. The specific scope depends on the actual situation.

From the above description, it can be seen that the technical solution provided by the present invention improves the VPLS service PE and PE (non-H-VPLS) by adding a dedicated service ID that does not have a one-to-one correspondence with the PWID in the protocol message. The PW protection function between NPEs or between NPEs (H-VPLS), thus enhancing the robustness of VPLS services and improving the availability of VPLS services.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned 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 formed by multiple computing devices Alternatively, they may be implemented in program code executable by a computing device so that they may be stored in a storage device to be executed by a computing device, and in some cases in an order different from that shown here The steps shown or described are carried out, or they are separately fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present invention is not limited to any specific combination of hardware and software.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. a kind of VPLS VPLS service establishing methods, it is characterised in that including：

In Provider Edge PE equipment create VPLS business, and for the VPLS service generations in the range of the PE equipment only The traffic ID of one one srvice instance of determination；

One or more pseudo-wire PW is set up according to the traffic ID, specifies the PW to correspond to the VPLS business；

Set up the PW and the VPLS business binding relationship；

Wherein, one or more pseudo-wire PW is set up according to the traffic ID, specifying the PW to correspond to the VPLS business includes： A plurality of PW is set up between local end PE and opposite end PE, wherein, the corresponding traffic ID of a plurality of PW is identical.

2. according to the method described in claim 1, it is characterised in that one or more pseudo-wire PW is set up according to the traffic ID, Specifying the PW to correspond to the VPLS business also includes：

When PW does not need protection mechanism, a PW is set up between local end PE and opposite end PE, wherein, a PW is corresponding The corresponding traffic ID of PW between traffic ID and the local end PE and other opposite ends PE is different from.

3. method according to claim 2, it is characterised in that set up the PW and the VPLS business binding relationship bag Include：

The local end PE is set to the PW between the opposite end PE and the binding relationship of the VPLS business；

The opposite end PE to the PW between the local end PE and the VPLS business binding relationship are set.

4. method according to claim 3, it is characterised in that set the local end PE to the PW between the opposite end PE and The binding relationship of the VPLS business includes：

The local end PE into the PW between the opposite end PE assigned work PW and protection PW, by the work PW and the guarantor Shield PW is set in binding relationship；

Claimed PW is specified for the protection PW.

5. the method according to claim 3 or 4, it is characterised in that set up the PW and the binding of the VPLS business is closed System also includes：

The local end PE is set to the PW and the binding relationship of the VPLS business between other opposite ends PE；

Other opposite ends PE to the PW between the local end PE and the binding relationship of the VPLS business are set.

6. a kind of VPLS VPLS business sets up device, it is characterised in that including：

Business module, in Provider Edge PE equipment create VPLS business, and for the VPLS service generations described The traffic ID of a srvice instance is uniquely determined in the range of PE equipment；

Pseudo- wire module, for setting up one or more pseudo-wire PW according to the traffic ID, specifies the PW to correspond to the VPLS Business；

Binding module, the binding relationship for setting up the PW and the VPLS business；

The pseudo- wire module includes：First sets up unit, for setting up a plurality of PW between local end PE and opposite end PE, wherein, institute State the corresponding traffic IDs of a plurality of PW identical.

7. device according to claim 6, it is characterised in that the pseudo- wire module also includes：

Second sets up unit, for when PW does not need protection mechanism, a PW to be set up between local end PE and opposite end PE, its In, the corresponding traffic ID of PW traffic ID corresponding with the PW between the local end PE and other opposite ends PE not phases Together.

8. device according to claim 7, it is characterised in that the binding module includes：

First setting unit, for setting the binding of the local end PE to the PW between the opposite end PE and the VPLS business to close System；

Second setting unit, for setting the opposite end PE to the PW between the local end PE and the binding of the VPLS business to close System.

9. device according to claim 8, it is characterised in that the first setting unit includes：

First specify subelement, for the local end PE into the PW between the opposite end PE assigned work PW and protection PW, The work PW and the protection PW are set in binding relationship；

Second specifies subelement, for specifying claimed PW for the protection PW.

10. device according to claim 8 or claim 9, it is characterised in that the binding module also includes：

3rd setting unit, for setting the local end PE tying up to the PW between other opposite ends PE and the VPLS business Determine relation；

4th setting unit, for setting tying up for other opposite ends PE to the PW between the local end PE and the VPLS business Determine relation.