WO2008046359A1

WO2008046359A1 - Method and apparatus for isolating the different virtual local area network services

Info

Publication number: WO2008046359A1
Application number: PCT/CN2007/070930
Authority: WO
Inventors: Faming Yang; Hongguang Guan
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-10-20
Filing date: 2007-10-19
Publication date: 2008-04-24
Also published as: CN101166137A; CN101166137B

Abstract

A method and apparatus for isolating the different virtual local area network services. The method mainly includes : assigning the identification information to the VLAN (virtual local area network) service instances accessed to the shortest path bridge network; transferring the identification information of the VLAN service instance along the root port direction of the different spanning trees in the shortest path bridge network by the access network bridge of the VLAN service instance; identifying the accessed VLAN service instance according to the identification information received from the root port direction of the spanning tree by theaccess network bridge in the shortest path bridge network. By use of the method, it can be realized to isolate the different VLAN services in the shortest path bridge network, thereby it is ensured that the VLAN service data packet is propagated in the range of the VLAN.

Description

Method and apparatus for isolating different virtual local area network services

[1] Technical field

[2] The present invention relates to the field of network communications, and in particular, to a method and apparatus for isolating different virtual local area network services.

[3] Background Art

[4] In traditional networks interconnected by Ethernet bridges, because the same and unique spanning tree is used for data forwarding in the same broadcast domain, it is usually not guaranteed that packets are forwarded by the shortest path. As a result, packets are concentrated on certain links.

[5] In order to enable bridges to forward data on the shortest path, there is currently the International Standards Organization IEEE (Institute for

Electrical and Electronics

Engineers, Institute of Electrical and Electronics Engineers) Shortest Path Bridge Project Team and International Standards Organization IETF (In ternet Engineering Task Force, Internet Workforce Task Force) TRILL (interconnection of Lots of

Links, transparent interconnections in multiple links) The working group is studied in two different ways.

[6] According to IEEE

The shortest path bridging technique described in 802.1aq creates a spanning tree (called an ingress tree) with each ingress bridge as the root in the bridged network, when VLAN (virtual local area network) traffic packets from outside the bridging network arrive at the ingress network. Bridge, encapsulates the packet with a new external tag header that contains information that identifies the entry tree instance, and that is independent of the customer VLAN information. Thus, the data packet encapsulating the external tag is forwarded by the shortest path along the entry tree identified by the Tag in the shortest path bridged network.

[7] Current MSTP (Multiple Spanning Tree

Protocol, multiple spanning tree protocol) Set different spanning trees for different VLANs, and build a single spanning tree for each VLAN. When MSTP is used in an 802.1aq environment, the same VLAN service needs to use multiple shortest path trees. Similarly, different VLAN services can share a shortest path tree with a common ingress bridge. For example, connect two on one SPVID3 tree. Customer VLAN.

[8] The shortest path bridge environment assigns a unique VID to each entry tree instance (Visual LAN) Identifier, virtual local area network identifier), this VID can be called SPVID (Shortest Path Visual LAN)

Identifier, shortest path VID). When a VLAN service data packet is externally connected to the shortest path bridge network, the VLAN service data packet is encapsulated with an external tag containing the SPVID. The frame format of the encapsulated data packet is as follows:

However, the SPVID in the frame format of the above data packet cannot distinguish the customer VLAN service. Therefore, if data forwarding is performed according to the S PVID, service data leakage occurs, that is, it is forwarded to the bridge without the VLAN service. Let's use an example to illustrate this point.

For example, in the bridged network shown in Figure 1, a shortest path bridged network consists of bridge nodes A, B, C, and D, and four entry trees are generated, each represented by a different line segment. An existing client accessing VLAN 1 accesses the shortest path bridged network from bridges A, B, and D. When the VLAN service data packet arrives at the shortest path bridge node in the bridged network shown in Figure 1, an external tag containing the SPVID corresponding to the entry tree is encapsulated.

When the above data packet is propagated along the tree determined by the SPVID in the bridged network, the external customer VLAN ID is transparent inside the bridged network, and thus, the access VLAN

1 service broadcast packet (including unknown packet) will spread to no access VLAN

1 The bridge node C of the service goes up, which causes service data leakage and waste of bandwidth resources. Therefore, how to ensure different VLAN broadcast domain isolation, that is, when a packet in a VLAN needs to be broadcast, it cannot be leaked into other VLANs. , that is, to avoid inappropriate flooding, is a problem that needs to be solved in the bridged network. PBBN (Provider Backbone Bridge) for 802.1ah implementation

Network, Carrier Backbone Network) In the network, several I-SIDs (i-SID == Service instance

ID, Service Instance Identifier) The data of the different service instances identified in the PBBN network will share a B-VLAN tunnel (that is, the spanning tree instance assigned to the B-VID).

A method for isolating different service instances in a B-VLAN tunnel in the prior art is: due to the PBBN network The network is transparently transmitted to external data. Therefore, the method assigns a multicast address to each service instance (that is, for each I-SID), and the multicast addresses corresponding to different I-SIDs can be different, and in PBBN. A data forwarding table of the corresponding multicast address needs to be established in the network. When a data packet of a service instance reaches the border bridge of the PBB N network, if the destination address of the data packet is an unknown packet address, a broadcast packet, or a multicast address, the data packet is encapsulated with an external MAC header, and the external MAC header is encapsulated. The destination address is the multicast address corresponding to the I-SID. Since different service instances may have different multicast addresses, the data packets encapsulating the corresponding multicast addresses are transmitted inside the PBBN network, and the data of different service instances can be isolated from each other.

[15] A disadvantage of the above prior art method is that the method is only applicable to the PBBN network. In the shortest path bridge network, the service data forwarding is based on the SPVID tree, and the external VLAN service instance identifier cannot be seen. This method does not provide a method for configuring the multicast address forwarding table for the shortest path bridging network environment. Therefore, this method is not applicable to the shortest path bridging network environment.

[16] Summary of the invention

[17] It is an object of the present invention to provide a method and apparatus for isolating different virtual local area network services, thereby ensuring isolation of different VLAN services in the shortest path bridged network.

[18] The object of the present invention is achieved by the following technical solutions:

[19] A method of isolating different virtual local area network services, including:

[20] assigning identification information to the virtual local area network VLAN service instance accessed in the shortest path bridged network;

[21] The access bridge of the VLAN service instance transmits the identifier information of the VLAN service instance along a root port direction of different entry trees in the shortest path bridge network;

[22] The access bridge in the shortest path bridging network identifies the accessed VLAN service instance according to the identification message received from the root port direction of the ingress tree.

[23] An access bridge in a shortest path bridged network, including:

[24] an identifier information distribution module, configured to allocate identification information to a VLAN service instance accessed in the shortest path bridge network;

[25] an identifier information transmission module, configured to transmit identification information of a VLAN service instance allocated by the identifier information distribution module along a root port direction of different entry trees in the shortest path bridge network;

[26] The VLAN service instance identification module is configured to identify the VLAN service instance accessed in the shortest path bridge network according to the identifier message received from the root port direction of the entry tree. [27] It can be seen from the technical solution provided by the present invention that the present invention assigns a multicast address to each VLAN service instance, and accesses the bridge in each VLAN service, and identifies the corresponding tree along different SPVIDs. The root port direction initiates the registration of the VLAN access multicast address; or, assigns an SPVID group to each VLAN service instance, and forms a VLAN in each access bridge.

A translation table of the relationship between the ID and the SPVID, and the registration of the SPVID is initiated along the root port direction of the tree corresponding to the different SPVID identifiers. Therefore, two different VLAN service isolation methods in the shortest path bridged network can be provided for different application scenarios. It ensures the isolation of different VLAN services, ensures that VLAN service data packets are transmitted within the VLAN, and implements service VLANs.

The ID is transparently processed within the shortest path bridged network.

[28] BRIEF DESCRIPTION OF THE DRAWINGS

[29] Figure 1 is a schematic structural diagram of a bridge network;

2 is a flowchart of a specific process of Embodiment 1 of the present invention;

3 is a schematic structural diagram of a bridge network in Embodiment 1 of the present invention;

4 is a flowchart of a specific process of Embodiment 2 of the present invention;

FIG. 5 is a schematic structural diagram of a bridge network according to Embodiment 2 of the present invention; FIG.

[34] FIG. 6 is a schematic diagram of a registration process for VLAN 1 in the bridge network shown in FIG. 5.

[35] Specific implementation

[36] The present invention provides a method and apparatus for isolating different virtual local area network services. The present invention provides two embodiments of the method of the present invention for different application scenarios.

[37] The present invention is described in detail below with reference to the accompanying drawings. The core of Embodiment 1 is: Configuring different VLAN service instances by using multicast addresses, and identifying corresponding spanning trees along different SPVIDs in the shortest path bridged network. Multicast address registration in the root port direction.

[38] The specific processing flow of Embodiment 1 is as shown in FIG. 2, and includes the following steps:

[39] Step 2-1. Assign a multicast address to each VLAN service instance.

[40] Embodiment 1 utilizes and extends existing MMRP (Multiple Multicast Registration Protocol) technology. First, a unique multicast address is assigned to each of the access client VLAN service instances in the shortest path bridging network as the identification information of the VLAN service instance. The multicast address is a MAC address space belonging to the shortest path bridged network. The multicast address can be assigned before the access tree of the access bridge is generated, or it can be entered. The port tree is allocated after it is generated.

[41] For example, in the bridged network shown in Figure 3, a shortest path bridged network consists of bridge nodes A, B, C, and D, and four entry trees are generated, each represented by a different line segment. There is now a VLAN 1 service instance from bridges A, B, and D to the shortest path bridge network shown in Figure 3. Assign a multicast address m to the VLAN 1 service instance.

[42] Step 2-2. Register the multicast address in the shortest path bridging network along the root port direction of the tree corresponding to the different SPVID identifiers.

[43] After assigning a unique multicast address to each access VLAN service instance, the access bridge of each VLAN service instance needs to initiate the registration process of the assigned multicast address for different entry trees.

[44] When a VLAN service corresponds to an SPVID group, assuming that the SPVID group has n SPVIDs, the V LAN service corresponds to a set of VLAN service access bridges, and each VLAN service access bridge, for n - 1 other VLAN service access bridge is an entry tree determined by the root of the tree, and initiates a multicast address registration process, where each registration message propagates toward the root port of an entry tree.

[45] This embodiment provides two registration schemes. The two registration schemes are described separately below.

[46] Registration scheme 1: In the registration process of the multicast address, the access node of the VLAN service instance sends a registration message to the root port along the ingress tree with the S PVID identifier, where the registration message carries the corresponding VLAN service instance. Multicast address and entry tree SPVID identification information. In an actual application, the corresponding multicast address, the entry tree SPVID identification information may be encapsulated in a Tag header of the data packet of the registration message; or the corresponding group is set in the static load content of the data packet of the registration message. Broadcast address, entry tree SPVID identifier

Ι π Λ∑! ,.

[47] The bridge that received the above registration message registers an FDB entry (filter) on the receiving port.

Database, filter database table entries). The FDB

The entry includes: receiving the port number and the SPVID identifier and the multicast address of the entry tree carried in the foregoing registration message, and then continuing to propagate the registration message to the root port. For example, in the bridged network shown in Figure 3, VLAN 1 access node A and VLAN 1 access node D are respectively carried along the root port to VLAN 1 access node B (SPVID).

3, m) registration message; VLAN 1 access node B and VLAN 1 access node D respectively send along the root port to V LAN1 access node A carrying (SPVID 4, m) registration message; VLAN 1 access node A and VLAN 1 access node B respectively send a registration message carrying (SPVID2, m) to the V LAN1 access node D along the root port. The access node C will also receive the registration message sent by the access node, the access node 8, and the access node D. Since the multicast address m is not registered on the access node C, the access node C may not process the received message. Registration message.

[48] Registration scheme 2: Before the SPVID tree is generated, the management system assigns a corresponding multicast address to each access bridge to access the VLAN service instance. After each SPVID tree converges, the VLAN service instance is connected. The inbound bridge sends a registration message along the designated port direction of the SPVID tree, and the bridge that receives the registration message registers one of the above FDB entries on the receiving port.

[49] For example, in the bridged network shown in Figure 3, VLAN 1 access node A is connected to VLAN 1 along node 1 and VLAN 1 is connected to node B to transmit (SPVID).

4, m) registration message; VLAN1 access node B sends a carry along the designated port to the VLAN1 access node 1), VL AN1 access node A (SPVID

3, m) registration message; VLAN 1 access node D along the designated port to the VLAN1 access node VIII, VL AN1 access node B send carry (SPVID

2, m) registration message. The access node C will also receive the registration message sent by the access node A, the access node 8, and the access node D. Since the multicast address m is not registered on the access node C, the access node C may not process the received message. Registration message.

[50] In the above registration scheme 1, it is necessary to solve the problem of filtering the tag data packet by the receiving port. Since there is no SPVID registration for the port in the above registration scheme 1, no registration item (SPVID, port number) is formed. However, according to the current 802.1Q regulations: "Enable or disable Ingress Filtering" is used for VLANs. If you use enable Ingress

Filtering (ingress gateway filtering), because the registration entry (SPVI D, port number) is not formed on the receiving bridge, the receiving bridge will discard the received packet containing the tag header. Therefore, in the above registration scheme 1, in order to ensure the smooth delivery of the registration packet including the tag header, the Disable Ingress Filter ingress is disabled on the receiving port of the bridge.

[51] In the above registration scheme 2, the filtering problem of the registration package containing the Tag (the tag carries the SPVID) needs to be solved.

. According to the existing MMRP, after registering in a multiple spanning tree environment, the registration package must carry a tag header. , the tag header contains a VLAN

ID (here should be SPVID). Since no registration item is formed on the receiving bridge (SPVID, port number)

), the receiving bridge will discard the received registration packet containing the tag. Therefore, in the above registration scheme 2, in order to ensure the smooth delivery of the registration packet, the Disable Ingress Filter ingress is disabled on the receiving port of the bridge.

[52] Step 2-3, the shortest path bridges the bridge in the network according to the registration of the FDB

Entry, isolates different VLAN service instances and forwards VLAN packets.

[53] After the above registration process, the bridges in the shortest path bridged network can be based on various FDBs formed by registration.

The entry (including the SPVID ID, multicast address, and port number of the egress tree) is used to isolate different VLAN service instances and forward each packet between access bridges of the VLAN service instance to which it belongs.

[54] When a VLAN

The service data packet corresponding to the ID arrives at the bridge in the shortest path bridged network, and the receiving bridge encapsulates the data packet with an external header. If it is determined that the data packet is a unicast unknown packet, a multicast packet, or a broadcast packet, the destination address of the external header is a multicast address of the VLAN access group. In addition, the SPVID including the receiving bridge as a root is also encapsulated. The external tag header. The encapsulated packets are then forwarded along the entry tree within the VLAN within the shortest path bridged network.

[55] For example, in the bridged network shown in Figure 3, when access bridge B receives a packet belonging to VLAN1吋

If the data packet is an unknown unicast address, the data packet is encapsulated with a MAC header (the multicast address m) and a SPVID containing the destination address.

The tag header of 3, and then forward the encapsulated packet according to the FDB entry containing the SPVID3 identifier, the multicast address m, and the port number. Since the bridge B is not formed on the bridge B, the SP is included.

FID of VID3 identifier, multicast address m and port number

The entry entry, therefore, will propagate to the bridges A and D without leaking to bridge C. This ensures that packets are transmitted within the scope of VLAN 1.

[56] The processing flow of the foregoing Embodiment 1 ensures isolation of different VLAN services and implements a service VLAN.

The ID is transparently processed within the shortest path bridged network.

[57] The processing flow of the foregoing Embodiment 1 is suitable for the 802.1ah environment, and the forwarding is shortest within the carrier network. Path bridging technology, which constitutes MAC in in relation to the customer network

MACo is extending 802. lad, allowing MAC in 802. lad

After MAC encapsulation, the above embodiment 1 can be applied in an 802.1ad environment.

The core of the embodiment 2 is as follows: SP SPVID group is used to isolate different VLAN service instances, and SPVID group registration is performed in the shortest path bridge network along the root port direction of the corresponding spanning tree of different SPVID identifiers.

[59] The specific processing flow of Embodiment 2 is as shown in FIG. 4, and includes the following steps:

[60] Step 4-1. Assign an SPVID group to each VLAN service instance to form a VLAN.

A translation table of the relationship between ID and SPVID groups.

[61] First, each access bridge in the shortest path bridging network needs to allocate one SPVID for each accessed client VLAN service as the identification information of the VLAN service instance. This SPVID is unique across the shortest path bridged network. Thus, a set of SPs is assigned to a VLAN service instance.

VID (SPVIDs).

[62] If different VLAN service instances access a group of identical bridges, they can be assigned a set of identical or different SPVIDs. However, for the same VLAN service instance, the SPVID assigned to different access trees on different access bridges is different.

[63] Therefore, a group of SPVIDs assigned to different VLAN service instances can identify different entry trees and different VLAN service instances.

[64] In an 802.1aq network, BPDUs sent by each bridge during the generation of each entry tree (Bridg e Protocol Data

Unit, bridging protocol data unit) The message carries one or more mapping information: VLAN ID - SPVID, so that multiple SPVIDs are mapped to the same entry tree instance, and one SPVID can only be mapped to one ingress tree service instance (per The SPVIDs are unique within the shortest path bridged network described).

[65] Thus, a VLAN is formed on each access bridge.

A translation table for the mapping between ID and SPVID groups. According to the translation table, at any entry bridge, a VLAN ID can be mapped to a unique set of SPVIDs, and an SPVID group can be mapped to a unique VLAN ID.

[66] As in the bridged network shown in Figure 5, VLAN

1 service instance in the bridge eight, B, D access, give the VLAN 1 business instance is assigned a set of SPVIDs { l, 4, 2}; VLAN

2 The business instance is on the bridge. , B, D access, give the VLAN

2 The business instance is assigned a set of SPVIDs { 10, 11 , 12}.

[67] When the data of a _VLAN service instance reaches an access bridge, the corresponding SPVID can be encapsulated into a data packet by using the translation table formed above, and the SPVID can identify both the entry tree and the VLAN service. The encapsulated data packet is then forwarded along the entry tree identified by the SPVID within the bridged network.

[68] Step 4-2. Register a set of SPVIDs assigned to the VLAN service instance in the shortest path bridged network.

[69] To ensure that packets are spread within a VLAN service instance, they do not leak to bridges outside the VLAN service instance. A set of SPVIDs assigned to VLAN service instances needs to be registered in the shortest path bridged network.

[70] How to perform VLAN registration in the shortest path bridged network, the current 802.1aq has not given a corresponding method. An existing registration method is as follows: Broadcasting a VLAN, multicast address information, and then further utilizing a ₆₄ -bit reflection vector method. The disadvantages of this method are: More complex, each bridge stores a large amount of information.

The SPVID registration method in the shortest path bridge network in this embodiment will be described below.

[72] First, at each ingress access bridge for each VLAN ID, based on the configured VLAN ID

The SPVID mapping table is used to find the corresponding SPVIDs, but does not include the SPVID corresponding to the tree whose root is the entry bridge.

[73] Then, initiate an SPVID registration for the root port of the entry tree identified by each SPVID in the SPVIDs

, that is, the registration message carrying the SPVID assigned by the bridge is sent along the root port. After receiving the registration message, each bridge saves the SPVID identifier and the receiving port information carried in the registration message. Find the corresponding spanning tree instance based on the S PVID and continue to send the port to the root port of the spanning tree.

SPVID registration message.

[74] When a bridge learns that the topology of the tree corresponding to the SPVID changes, if it is the VLAN access node corresponding to the SPVID, and the root bridge of the tree corresponding to the SPVID is not the local bridge, The bridge needs to re-register the SPVID.

[75] The registration process in the above Embodiment 2 can be applied to an 802.1Q environment, and is not suitable for 802.1ah, 802.a. Used in the d environment, because 802.1ah, 802.ad is used in QinQ technology, which reflects the support for VLAN scalability.

[76] According to the registration procedure in Embodiment 2 above, in the bridge network shown in FIG. 5, for the VLAN

The registration process of 1 is shown in Figure 6. The specific registration process is as follows:

[77] On access bridge D, for VLAN 1, respectively in SPVID 1 and SPVID

4 identified entry tree initiates registration of the corresponding SPVID; at access bridge A, for VLAN

1 , in SPVID 1 and SPVID respectively

2 The identified entry tree initiates the registration of the corresponding SPVID. On access bridge B, for VLAN

1. Initiate the registration of the corresponding SPVID in the entry tree identified by SPVID 4 and SPVID 2 respectively.

[78] When VLAN

1 After the service instance data packet arrives at the access bridges VIII, B, and D, the access bridges VIII, B, and D query the above translation table, and obtain the VLANs on the access bridges 8, B, and D.

1 The corresponding SPVID assigned by the service instance, and the data packet is encapsulated with a tag header containing the corresponding SPVID. Then, according to the mapping relationship between the VLAN1 and SPVID groups stored in the translation table and the registered port information, the data packet is forwarded from the root port direction of the tree identified by the SPVID corresponding to VL AN1. Since the mapping between the VLAN1 and SPVID groups saved in the translation table does not include the access bridge C, it can ensure that the data packet will not leak to the VLAN.

2 access to the bridge. . Ensure that the data packet is forwarded between the access bridges of the VLAN service instance to which it belongs.

The above description is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of within the technical scope disclosed by the present invention. Changes or substitutions are intended to be included within the scope of the invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

Claim

[1] A method for isolating different virtual local area network services, comprising: assigning identification information to a virtual local area network (VLAN) service instance accessed in a shortest path bridging network; and accessing the VLAN service instance The bridge transmits the identification information of the VLAN service instance along a root port direction of different entry trees in the shortest path bridge network; the access bridge in the shortest path bridge network is based on a root port from the entry tree thereof The identifier message received in the direction is used to identify the accessed VLAN service instance.

[2] The method according to claim 1, wherein the process of assigning identification information to the virtual local area network (VLAN) service instance accessed in the shortest path bridging network comprises: providing the shortest path in the network Each of the accessed VLAN service instances is assigned a unique multicast address as the identification information of the VLAN service instance. The multicast address is configured on each access bridge of the VLAN service instance.

[3] The method according to claim 2, wherein the access bridge of the VLAN service instance bridges the identification information of the VLAN service instance along the shortest path to bridge different entries in the network. The root port direction of the tree is transmitted, including:

Each access bridge of the VLAN service instance sends a corresponding multicast address and an entry tree shortest path virtual local area network identifier (SPVID) identifier to other bridges along the root port direction of the different entry trees in the shortest path bridge network. Registration message of information;

After receiving the registration message, the other bridge saves the receiving port information and the multicast address and the entry tree SPVID identifier carried in the registration message; and continues to register the registration message along the shortest path bridge network. The root port direction of different entry trees is forwarded.

[4] The method according to claim 3, wherein the corresponding multicast address, the entry tree SPVID identification information is encapsulated in a header of the data packet of the registration message; or, in the registration message The corresponding multicast address and the entry tree SPVID identification information are set in the static payload content of the data packet.

[5] The method according to claim 2, wherein the access bridge of the VLAN service instance bridges the identification information of the VLAN service instance along the shortest path to bridge different entries in the network. The root port direction of the tree is transmitted, including: Each of the access tree bridges in the shortest path bridging network converges, and each access bridge of the VLAN service instance transmits and carries to other bridges along the designated port direction of different entry trees in the shortest path bridging network. a registration message of the corresponding multicast address and the entry tree SPVID identification information; after receiving the registration message, the other bridge saves the receiving port information and the multicast address and the entry tree SPVID identifier carried in the registration message; The registration message continues to be forwarded along the designated port direction of the different entry trees in the shortest path bridged network.

[6] The method according to claim 1, wherein the process of assigning identification information to the virtual local area network (VLAN) service instance accessed in the shortest path bridge network comprises: providing the shortest path in the network Each of the accessed VLAN service instances is assigned an SPVID group as the identification information of the VLAN service instance. Each SPVID included in the SPVID group is configured on each access bridge of the VLAN service instance.

[7] The method according to claim 6, wherein the process of assigning identification information to the virtual local area network (VLAN) service instance accessed in the shortest path bridging network further comprises: in the shortest path bridging network The mapping between the VLAN ID of each VLAN service instance and the SPVID group is configured and saved on each access bridge.

[8] The method according to claim 7, wherein the access bridge of the VLAN service instance bridges the identification information of the VLAN service instance along the shortest path to bridge different entries in the network. The root port direction of the tree is transmitted, including:

Each access bridge of the VLAN service instance is based on the saved VLAN

The mapping relationship between the ID and the SPVID group, the SPVID group corresponding to the VLAN service instance is obtained; the SPVID included in the SPVID group corresponds to the root port direction of the entry tree, and the registration message carrying the corresponding SPVID identification information is sent to other bridges;

After receiving the registration message, the other bridge saves the SPVID identifier and the receiving port information carried in the registration message, and obtains the entry tree information corresponding to the SPVID identifier carried in the registration message, and the registration message is sent. Continue forwarding along the root port of the entry tree.

[9] 9. The method according to claim 3, 5 or 8, wherein the access bridge in the shortest path bridged network receives the identifier according to a direction from a root port of its entry tree. The process of identifying the accessed VLAN service instance includes: The access bridge in the shortest path bridging network identifies the accessed VLAN service instances according to the registration message received from the root port direction of the ingress tree, and sets each data packet in the VLAN service to which it belongs. Forwarding between the access bridges of the instance.

[10] 10. An access bridge in a shortest path bridged network, comprising:

An identifier information distribution module, configured to allocate identifier information to a VLAN service instance accessed in the shortest path bridge network;

And an identifier information transmission module, configured to transmit, by using the identifier information of the VLAN service instance allocated by the identifier information distribution module, along a root port direction of different entry trees in the shortest path bridge network;

The VLAN service instance identification module is configured to identify the VLAN service instance accessed in the shortest path bridge network according to the identifier message received from the root port direction of the entry tree.