CN101166137A - Method for separating different virtual LAN services - Google Patents
Method for separating different virtual LAN services Download PDFInfo
- Publication number
- CN101166137A CN101166137A CNA200610113920XA CN200610113920A CN101166137A CN 101166137 A CN101166137 A CN 101166137A CN A200610113920X A CNA200610113920X A CN A200610113920XA CN 200610113920 A CN200610113920 A CN 200610113920A CN 101166137 A CN101166137 A CN 101166137A
- Authority
- CN
- China
- Prior art keywords
- vlan
- spvid
- bridge
- shortest path
- srvice instance
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/12—Shortest path evaluation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/48—Routing tree calculation
- H04L45/484—Routing tree calculation using multiple routing trees
Abstract
The method includes following steps: assigning ID information for service instance connected to virtual local area network (VLAN) in bridge network with shortest path (BNSP); the said access bridge transfers the said ID information along direction of root ports of different entry trees in BNSP; based on the said ID information received along direction of root port of entry tree, the access bridge in BNSP identifies VLAN service instance. The method can insulate different VLAN services in BNSP so as to guarantee that VLAN service data packets are transmitted within VLAN area.
Description
Technical field
The present invention relates to network communication field, relate in particular to a kind of method that different virtual LAN services is isolated.
Background technology
Traditional passing through in the interconnected network of ethernet bridge, owing in same broadcast domain, adopt identical and unique generation is set and carried out data forwarding, therefore, can not guarantee that usually packet presses shortest path and transmit, transmit thereby can cause packet to concentrate on some link.
In order to make bridge transmit data, there are the shortest path bridge project team of the IEEE of International Standards Organization (IEEE) and TRILL (transparent interconnection in the multilink) working group of the IETF of International Standards Organization (Internet engineering duty group) studying according to two distinct methods respectively at present by shortest path.
The shortest path bridge connection technology of being set forth according to IEEE 802.1aq, in bridge coil, be that root is created one and generated tree (being called the inlet tree) with each inlet bridge, when VLAN (VLAN) business data packet from the bridge coil outside arrives the inlet bridge, the outside tag head that this packet encapsulation is new, this external head has comprised information that can discern inlet tree example, and this external head has nothing to do with customer VLAN information.So the packet inlet tree along the Tag sign in the shortest path bridging network that has encapsulated outside tag is transmitted by shortest path.
Present MSTP (Multiple Spanning Tree Protocol) is provided with different generation trees at different VLAN, and each VLAN makes up a Single Spanning Tree.When MSTP uses in the 802.1aq environment, same VLAN service needed is used a plurality of shortest path trees, simultaneously different VLAN business also can a shared shortest path tree that common inlet bridge is arranged, such as, two customer VLAN of connection on a SPVID3 tree.
Shortest path bridge environment can be called this VID SPVID (shortest path VID) to the unique VID (Visual LANIdentifier, virtual local area network identifiers) of each inlet tree example allocation.When some VLAN business data packet insert the shortest path bridging network from the outside, give this VLAN business data packet encapsulation an outside tag who comprises SPVID, the frame format of the packet after the encapsulation is roughly as follows:
| DA | SA | Type， Pri，DE， SPVID | ?Res ?t?of?the ?Fame | CRC (s) |
But the SPVID in the frame format of above-mentioned packet can not distinguish the customer VLAN business, so the business datum leakage can occur if carry out data forwarding by SPVID, promptly is forwarded on the bridge that does not have the VLAN business.With an example this point is described below.
Such as, in bridge coil shown in Figure 1, a shortest path bridging network is made of bridging nodes A, B, C, D, has generated 4 inlet trees, represents with different line segments respectively.An existing client who inserts VLAN 1 inserts the shortest path bridging network from bridge A, B, D.When the shortest path bridge bridge node in the VLAN business data packet arrival bridge coil shown in Figure 1, encapsulate an outside tag who comprises the corresponding SPVID of inlet tree.
When the tree of determining along SPVID in bridge coil when above-mentioned packet is propagated, external client VLAN ID is transparent in bridge coil inside, so, the broadcast packet (comprising unknown bag) that inserts VLAN 1 business will be diffused into the bridge node C that does not insert VLAN 1 business and get on, thereby cause the waste of business datum leakage and bandwidth resources, therefore how to guarantee different VLAN broadcast domain isolation, promptly when the packets need among the VLAN is broadcasted, it can not be leaked among other VLAN, promptly avoiding inappropriate flooding, is to need the problem that solves in the bridge coil.
At PBBN (the Provider Backbone Bridge Network that realizes at 802.1ah, the provider backbone bridging network) in the network, the data of the different srvice instance of some I-SIDs (I-SID==Service instance ID, service instance identifier) sign can a shared B-VLAN tunnel (at the spanning-tree instance that B-VID distributed) when the PBBN network delivery.
A kind of method of isolating the different business example in the B-VLAN tunnel is in the prior art: because the PBBN network is a transparent transmission to external data, therefore, this method is distributed a multicast address at each srvice instance (promptly at each I-SID), the multicast address of different I-SID correspondence can be different, and need to set up the data forwarding table of corresponding multicast address in the PBBN network.When the bridge of the border of the packet arrival PBBN of srvice instance network, if the destination address of this packet is unknown packet address, broadcast packet or multicast address, then to outside MAC head of this packet encapsulation, the destination address of outside MAC head is the pairing multicast address of I-SID.Because different Service Instances can have different multicast address, the packet that has encapsulated corresponding multicast address like this is when the PBBN network internal is transmitted, and the data that can reach the different business example are isolated mutually.
The shortcoming of the method for above-mentioned prior art is: this method only is only applicable to the PBBN network.In shortest path bridge network, business datum is transmitted and is based on the SPVID tree, can not see outside VLAN Service Instance sign.This method does not provide the collocation method that multicast address is transmitted at the shortest path bridging network environment, therefore, and the inapplicable shortest path bridging network environment of this method.
Summary of the invention
In view of above-mentioned existing in prior technology problem, the purpose of this invention is to provide a kind of method that different virtual LAN services is isolated, thereby can guarantee in the shortest path bridging network, different VLAN business are isolated.
The objective of the invention is to be achieved through the following technical solutions:
A kind of method that different virtual LAN services is isolated comprises step:
A, give the virtual LAN VLAN srvice instance allocation identification information that inserts in the shortest path bridging network;
The access bridge of B, described VLAN srvice instance is the identification information of described VLAN srvice instance, and the root port directions of different inlet trees are transmitted in the described shortest path bridging network;
Access bridge in C, the described shortest path bridging network is discerned the VLAN srvice instance of described access according to the described identification message that the root port direction from its inlet tree receives.
Described steps A specifically comprises:
Distribute a unique multicast address for the VLAN srvice instance of each access in the shortest path bridging network, as the identification information of described VLAN srvice instance; Described multicast address is configured on each access bridge of VLAN srvice instance.
Described step B specifically comprises:
Each of B1, described VLAN srvice instance inserts the root port directions of bridge different inlet trees in the described shortest path bridging network, sends the registration message that carries corresponding multicast address, inlet tree shortest path virtual local area network identifiers SPVID identification information to other bridge;
After B2, described other bridge receive described registration message, multicast address, the inlet tree SPVID sign of carrying in receiving port information and the described registration message are preserved; Described registration message is continued in the described shortest path bridging network root port directions of different inlet trees to be transmitted.
Described step B1 specifically comprises:
Head at the packet of described registration message encapsulates described corresponding multicast address, inlet tree SPVID identification information; Perhaps, described corresponding multicast address, inlet tree SPVID identification information are set in the quiet lotus content of the packet of described registration message.
Described step B specifically comprises:
When B3, each inlet tree convergence in described shortest path bridging network, each of described VLAN srvice instance inserts the designated port directions of bridge different inlet trees in the described shortest path bridging network, sends the registration message that carries corresponding multicast address, inlet tree SPVID identification information to other bridge;
After B4, described other bridge receive described registration message, multicast address, the inlet tree SPVID sign of carrying in receiving port information and the described registration message are preserved; Described registration message is continued in the described shortest path bridging network designated port directions of different inlet trees to be transmitted.
Described steps A specifically comprises:
Distribute a SPVID group for the VLAN srvice instance of each access in the shortest path bridging network, as the identification information of described VLAN srvice instance; Each SPVID that comprises in the described SPVID group is configured in respectively on each access bridge of VLAN srvice instance.
Described steps A also comprises:
In the shortest path bridging network each inserts the VLAN sign ID of the VLAN srvice instance that disposes and preserve each access on the bridge and the mapping relations of described SPVID group.
Described step B specifically comprises:
Each of B5, described VLAN srvice instance inserts the mapping relations of bridge according to described VLAN ID that preserves and SPVID group, obtains the SPVID group of described VLAN srvice instance correspondence; The root port direction of the corresponding inlet tree of SPVID that comprises in this SPVID group sends the registration message that carries corresponding SPVID identification information to other bridge;
After B6, described other bridge receive described registration message, the SPVID sign and the receiving port information of carrying in this registration message are preserved; The corresponding inlet of SPVID sign that obtains to carry in the described registration message is set information, and described registration message is continued to transmit along the root port direction of this inlet tree.
Described step C specifically comprises:
The described registration message that access bridge in the described shortest path bridging network receives according to the root port direction from its inlet tree, each VLAN srvice instance that inserts is discerned, transmitted between the access bridge with the VLAN srvice instance of each packet under it.As seen from the above technical solution provided by the invention, the present invention is by distributing a multicast address to each VLAN srvice instance, at each VLAN service access bridge, initiate the registration of VLAN incoming multicast address along the root port direction of the corresponding tree of different SPVID signs; Perhaps, distribute a SPVID group for each VLAN srvice instance, insert bridge formation at each and comprise the translation table that concerns between VLAN ID and SPVID, initiate the registration of SPVID along the root port direction of the corresponding tree of different SPVID signs.Thereby can two kinds of professional partition methods of different VLAN in the shortest path bridging network be provided for different application scenarioss.Both guaranteed the isolation of different VLAN business, guaranteed that the VLAN business datum wraps in propagation in this VLAN scope, can realize the transparent processing of service VLAN ID in the shortest path bridging network again.
Description of drawings
Fig. 1 is a kind of structural representation of bridge coil;
Fig. 2 is the concrete process chart of embodiment 1 of the present invention;
Fig. 3 is the structural representation of the bridge coil among the embodiment 1 of the present invention;
Fig. 4 is the concrete process chart of embodiment 2 of the present invention;
Fig. 5 is the structural representation of the bridge coil among the embodiment 2 of the present invention;
Fig. 6 is the registration process schematic diagram at VLAN 1 in the bridge coil shown in Figure 5.
Embodiment
The invention provides a kind of method that different virtual LAN services is isolated.The present invention is directed to different application scenarioss, two embodiment of the method for the invention are provided.
Describe the present invention in detail below in conjunction with accompanying drawing, the core of embodiment 1 is: adopt multicast address to isolate different VLAN srvice instance, and carry out the multicast address registration along the root port direction of the corresponding generation tree of different SPVID signs in the shortest path bridging network.
The concrete handling process of embodiment 1 comprises the steps: as shown in Figure 2
Step 2-1, distribute a multicast address for each VLAN srvice instance.
Such as, in bridge coil shown in Figure 3, a shortest path bridging network is made of bridging nodes A, B, C, D, has generated 4 inlet trees, represents with different line segments respectively.What VLAN 1 srvice instance was arranged now is linked into shortest path bridging network shown in Figure 3 from bridge A, B, D.Distribute a multicast address m for this VLAN 1 srvice instance.
Step 2-2, multicast address is registered along the root port direction of the corresponding tree of different SPVID sign in the shortest path bridging network.
After the VLAN srvice instance to each access had distributed a unique multicast address, the access bridge of each VLAN srvice instance need be initiated the registration process of the multicast address of distribution at different inlet trees.
When the professional corresponding SPVID of a VLAN organizes, suppose that this SPVID group has n SPVID, professional corresponding one group of VLAN service access bridge of this VLAN then, at each VLAN service access bridge, at n-1 other VLAN service access bridge is the inlet tree that tree root is determined, initiate a multicast address registration process, this moment, each registration message was propagated towards the root port direction of an inlet tree.
Present embodiment provides two registration scenarios.Introduce this two registration scenarios below respectively.
Registration scenarios 1: in the registration process of multicast address, the access node of VLAN srvice instance sends registration message along the inlet tree with SPVID sign to the root port direction, and this registration message carries multicast address, the inlet tree SPVID identification information of this VLAN srvice instance correspondence.In actual applications, can encapsulate described corresponding multicast address, inlet tree SPVID identification information at the Tag head of the packet of registration message; Perhaps, described corresponding multicast address, inlet tree SPVID identification information are set in the quiet lotus content of the packet of described registration message.
The bridge that receives above-mentioned registration message is registered a FDB entry (filterdatabase, filtered data base list item) on receiving port.This FDB entry comprises: SPVID sign, the multicast address of the inlet tree of carrying in receiving port number and the above-mentioned registration message, continue this registration message to propagate to the root port direction then.Such as, in bridge coil shown in Figure 3, VLAN1 access node A and VLAN1 access node D send to VLAN1 access node B along root port respectively and carry that (SPVID 3, registration message m); VLAN1 access node B and VLAN1 access node D send to VLAN1 access node A along root port respectively and carry that (SPVID 4, registration message m); VLAN1 access node A and VLAN1 access node B send to VLAN1 access node D along root port respectively and carry (SPVID2, registration message m).Access node C also will receive the registration message of access node A, access node B, access node D transmission, owing to do not register multicast address m on access node C, access node C can not handle the registration message that receives.
Such as, in bridge coil shown in Figure 3, VLAN1 access node A sends to VLAN1 access node D, VLAN1 access node B along designated port and carries that (SPVID 4, registration message m); VLAN1 access node B sends to VLAN1 access node D, VLAN1 access node A along designated port and carries that (SPVID 3, registration message m); VLAN1 access node D sends to VLAN1 access node A, VLAN1 access node B along designated port and carries that (SPVID 2, registration message m).Access node C also will receive the registration message of access node A, access node B, access node D transmission, owing to do not register multicast address m on access node C, access node C can not handle the registration message that receives.
In above-mentioned registration scenarios 1, need to solve the filtration problem of receiving port to the Tag packet.Owing to do not carry out the SPVID registration at port specially in the above-mentioned registration scenarios 1, promptly do not form registration entries (SPVID, port numbers).But the regulation present: adopted " enable or disable Ingress Filtering " (adopt or close inlet bridge filter type) about VLAN according to 802.1Q.As if using enable Ingress Filtering (adopting inlet bridge filter type),, receive bridge and will abandon the packet that comprises the tag head that receives owing on the reception bridge, do not form registration entries (SPVID, port numbers).Therefore, in above-mentioned registration scenarios 1,, on the receiving port of bridge, will adopt Disable Ingress Filter ingress (closing the bridge filter type that enters the mouth) for the smooth transmission of the registration packet that guarantees to comprise the tag head.
In above-mentioned registration scenarios 2, need to solve the filtration problem of the registration packet that comprises Tag (this tag carries SPVID).According to existing MMRP, when registering in the multiple spanning tree environment, registration packet will carry a tag head, and this tag head comprises VLAN ID (should be SPVID) here.Owing on the reception bridge, do not form registration entries (SPVID, port numbers), receive bridge and will abandon the registration packet that comprises tag that receives.Therefore, in above-mentioned registration scenarios 2,, on the receiving port of bridge, will adopt Disable Ingress Filter ingress (closing inlet bridge filter type) for guaranteeing the smooth transmission of registration packet.
Bridge in step 2-3, the shortest path bridging network is isolated different VLAN srvice instance according to the FDB entry that registration forms, and carries out the forwarding of vlan data bag.
After having carried out above-mentioned registration process, bridge in the shortest path bridging network just can be according to various FDB entry (the SPVID sign, multicast address and the port numbers that comprise the outlet tree) of registration formation, different VLAN srvice instance are isolated, transmit between the access bridge with the VLAN srvice instance of each packet under it.
When the bridge in the VLAN ID corresponding service packet arrival shortest path bridging network, receive bridge with external head of this packet encapsulation.If judging this packet is the unknown bag of clean culture, multicast packets or broadcast packet, then the destination address of said external head is the multicast address of this VLAN access group; In addition, need encapsulate also that to comprise to receive bridge be the outside tag head of the SPVID of root.Then, the packet after the encapsulation is transmitted along the inlet tree in this VLAN scope in the shortest path bridging network.
Such as, in bridge coil shown in Figure 3, when access bridge B receives the packet that belongs to VLAN1, if this packet is the unknown unicast address, MAC head (multicast address m) and a tag head that comprises SPVID 3 of then this packet encapsulation being comprised destination address, then, the packet after will encapsulating according to the FDB entry item that comprises SPVID3 sign, multicast address m and port numbers is again transmitted.Because be not formed into the FDBentry item that comprises SPVID3 sign, multicast address m and port numbers of bridge C on bridge B, therefore, above-mentioned packet can propagate into bridge A and D, and can not leak into bridge C.Thereby guaranteed that packet propagates in the VLAN1 scope.
The handling process of the foregoing description 1 has promptly guaranteed the isolation of different VLAN business, can realize the transparent processing of service VLAN ID in the shortest path bridging network again.
The handling process of the foregoing description 1 is suitable for the 802.1ah environment, based on the shortest path bridge connection technology, has again constituted MAC in MAC with respect to customer network in the inner forwarding of carrier network.802.1ad is being expanded, and MAC in MAC encapsulation is adopted in permission in 802.1ad after, the foregoing description 1 can be applied in the 802.1ad environment.
The core of embodiment 2 is: adopt the SPVID group to isolate different VLAN srvice instance, and carry out the registration of SPVID group along the root port direction of the corresponding generation tree of different SPVID signs in the shortest path bridging network.
The concrete handling process of embodiment 2 comprises the steps: as shown in Figure 4
Step 4-1, distribute a SPVID group for each VLAN srvice instance, form the translation table that comprises VLAN ID and SPVID intergroup relation.
Each that at first need be in the shortest path bridging network inserts bridge, and the SPVID that the customer VLAN traffic assignments of corresponding each access is is as the identification information of described VLAN srvice instance.This SPVID is unique in whole shortest path bridging network.So, just distributed one group of SPVID (SPVIDs) for a VLAN srvice instance.
If different VLAN srvice instance has inserted one group of identical bridge, then can distribute one group of same or different SPVID to them.But to same VLAN srvice instance, it is different inserting the SPVID that on the bridge difference inlet tree is distributed to it in difference.
Therefore, the one group of SPVID that distributes for different VLAN srvice instance can identify different inlet trees, also can distinguish different VLAN srvice instance, can be used for isolating different VLAN srvice instance.
In the 802.1aq network, in the generative process of each inlet tree, BPDU (the Bridge Protocol Data Unit that each bridge sends, Bridge Protocol Data Unit) to carry one or more map informations in the message: VLAN ID---SPVID, a plurality of like this SPVID are mapped on the same inlet tree example, and a SPVID can only be mapped to an inlet tree service example (each SPVID is unique) in described shortest path bridging network.
So, forming the translation table that comprises mapping relations between VLAN ID and the SPVID group on each access bridge.According to this translation table, in any one entry bridge, a VLAN ID can be mapped to one group of unique SPVID, and a SPVID group can be mapped to unique VLAN ID.
In the bridge coil as shown in fig. 5, VLAN 1 srvice instance inserts at bridge A, B, D, has distributed one group of SPVIDs{1,4,2} for this VLAN 1 srvice instance; VLAN 2 srvice instance insert at bridge C, B, D, have distributed one group of SPVIDs{10,11,12} for these VLAN 2 srvice instance.
When the data of a VLAN srvice instance arrive certain access bridge, can utilize the translation table of above-mentioned formation, corresponding SPVID is encapsulated in the packet, this SPVID can identify the inlet tree can distinguish the VLAN business again, and the packet after will encapsulating is then transmitted by the inlet tree along the SPVID sign in bridge coil.
Step 4-2, will in the shortest path bridging network, register to one group of SPVID that the VLAN srvice instance distributes.
In order to have guaranteed that packet propagates in a VLAN srvice instance scope, and can not leak on the extraneous bridge of VLAN srvice instance.Need and to register in the shortest path bridging network to one group of SPVID that the VLAN srvice instance distributes.
How to carry out the VLAN registration in the shortest path bridging network, present 802.1aq does not also provide corresponding method.Existing a kind of register method is: utilize broadcast mode announcement VLAN, multicast address information, further utilize 64 reflection vector approachs then.The method shortcoming is: more complicated, the amount of information that each bridge stores is very big.
SPVID register method in the shortest path bridging network in the present embodiment is described below.
At first, insert bridge at each VLAN ID,, find out corresponding SPVIDs, but do not comprise with this entry bridge being the corresponding SPVID of tree of root according to the VLAN ID of configuration and the mapping relations table of SPVID at each inlet.
Then, initiate a SPVID registration, promptly send the registration message that carries the SPVID that this bridge distributes along root port at the root port of the inlet tree of the sign of each SPVID among the SPVIDs.After each bridge is received this registration message, the SPVID sign and the receiving port information of carrying in this registration message are preserved.And find out corresponding spanning-tree instance according to SPVID, continue to carry the registration message of SPVID towards the root port transmission of this generations tree.
After a bridge learnt that the topological structure of the tree of a SPVID correspondence changes, if it is the VLAN access node of this SPVID correspondence, and the Root Bridge of the tree of this SPVID correspondence was not this bridge, and then this bridge needs register SPVID again.
Register flow path in the foregoing description 2 can be applied in the 802.1Q environment, is not suitable for using in 802.1ah, 802.ad environment, because 802.1ah, it is the QinQ technology that 802.ad adopts, and has embodied the support to the VLAN autgmentability.
According to the register flow path in the foregoing description 2, in bridge coil shown in Figure 5, as shown in Figure 6 at the registration process schematic diagram of VLAN1.Concrete registration process is as follows:
Inserting bridge D, at VLAN 1, the inlet tree in SPVID 1 and SPVID 4 signs initiates the registration of corresponding SPVID respectively; Inserting bridge A, at VLAN 1, the inlet tree in SPVID 1 and SPVID 2 signs initiates the registration of corresponding SPVID respectively.Inserting bridge B, at VLAN1, the inlet tree in SPVID 4 and SPVID 2 signs initiates the registration of corresponding SPVID respectively.
After VLAN 1 service instance data bag arrives access bridge A, B and D, insert bridge A, B and D and inquire about above-mentioned translation table, acquisition is inserting the corresponding SPVID that distributes at VLAN 1 srvice instance on bridge A, B and the D, this packet encapsulation is comprised the tag head of corresponding SPVID.Then, according to the port information of mapping relations and registration between the VLAN1 that preserves in the translation table and the SPVID group, packet is transmitted from the root port direction of the tree of the SPVID sign of VLAN1 correspondence.Because mapping relations do not comprise access bridge C between VLAN1 that preserves in the translation table and the SPVID group, thereby can guarantee that packet will can not leak into VLAN 2 and insert bridge C.Guaranteed to transmit between the access bridge of the VLAN srvice instance of packet under it.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.
Claims (9)
1. the method that different virtual LAN services is isolated is characterized in that, comprises step:
A, give the virtual LAN VLAN srvice instance allocation identification information that inserts in the shortest path bridging network;
The access bridge of B, described VLAN srvice instance is the identification information of described VLAN srvice instance, and the root port directions of different inlet trees are transmitted in the described shortest path bridging network;
Access bridge in C, the described shortest path bridging network is discerned the VLAN srvice instance of described access according to the described identification message that the root port direction from its inlet tree receives.
2. method according to claim 1 is characterized in that, described steps A specifically comprises:
Distribute a unique multicast address for the VLAN srvice instance of each access in the shortest path bridging network, as the identification information of described VLAN srvice instance; Described multicast address is configured on each access bridge of VLAN srvice instance.
3. method according to claim 2 is characterized in that, described step B specifically comprises:
Each of B1, described VLAN srvice instance inserts the root port directions of bridge different inlet trees in the described shortest path bridging network, sends the registration message that carries corresponding multicast address, inlet tree shortest path virtual local area network identifiers SPVID identification information to other bridge;
After B2, described other bridge receive described registration message, multicast address, the inlet tree SPVID sign of carrying in receiving port information and the described registration message are preserved; Described registration message is continued in the described shortest path bridging network root port directions of different inlet trees to be transmitted.
4. method according to claim 3 is characterized in that, described step B1 specifically comprises:
Head at the packet of described registration message encapsulates described corresponding multicast address, inlet tree SPVID identification information; Perhaps, described corresponding multicast address, inlet tree SPVID identification information are set in the quiet lotus content of the packet of described registration message.
5. method according to claim 2 is characterized in that, described step B specifically comprises:
When B3, each inlet tree convergence in described shortest path bridging network, each of described VLAN srvice instance inserts the designated port directions of bridge different inlet trees in the described shortest path bridging network, sends the registration message that carries corresponding multicast address, inlet tree SPVID identification information to other bridge;
After B4, described other bridge receive described registration message, multicast address, the inlet tree SPVID sign of carrying in receiving port information and the described registration message are preserved; Described registration message is continued in the described shortest path bridging network designated port directions of different inlet trees to be transmitted.
6. method according to claim 1 is characterized in that, described steps A specifically comprises:
Distribute a SPVID group for the VLAN srvice instance of each access in the shortest path bridging network, as the identification information of described VLAN srvice instance; Each SPVID that comprises in the described SPVID group is configured in respectively on each access bridge of VLAN srvice instance.
7. method according to claim 6 is characterized in that, described steps A also comprises:
In the shortest path bridging network each inserts the VLAN sign ID of the VLAN srvice instance that disposes and preserve each access on the bridge and the mapping relations of described SPVID group.
8. method according to claim 7 is characterized in that, described step B specifically comprises:
Each of B5, described VLAN srvice instance inserts the mapping relations of bridge according to described VLAN ID that preserves and SPVID group, obtains the SPVID group of described VLAN srvice instance correspondence; The root port direction of the corresponding inlet tree of SPVID that comprises in this SPVID group sends the registration message that carries corresponding SPVID identification information to other bridge;
After B6, described other bridge receive described registration message, the SPVID sign and the receiving port information of carrying in this registration message are preserved; The corresponding inlet of SPVID sign that obtains to carry in the described registration message is set information, and described registration message is continued to transmit along the root port direction of this inlet tree.
9. according to claim 3,5 or 8 described methods, it is characterized in that described step C specifically comprises:
The described registration message that access bridge in the described shortest path bridging network receives according to the root port direction from its inlet tree, each VLAN srvice instance that inserts is discerned, transmitted between the access bridge with the VLAN srvice instance of each packet under it.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610113920XA CN101166137B (en) | 2006-10-20 | 2006-10-20 | Method for separating different virtual LAN services |
| PCT/CN2007/070930 WO2008046359A1 (en) | 2006-10-20 | 2007-10-19 | Method and apparatus for isolating the different virtual local area network services |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610113920XA CN101166137B (en) | 2006-10-20 | 2006-10-20 | Method for separating different virtual LAN services |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101166137A true CN101166137A (en) | 2008-04-23 |
| CN101166137B CN101166137B (en) | 2011-04-06 |
Family
ID=39313628
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200610113920XA Expired - Fee Related CN101166137B (en) | 2006-10-20 | 2006-10-20 | Method for separating different virtual LAN services |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101166137B (en) |
| WO (1) | WO2008046359A1 (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102316000A (en) * | 2011-09-29 | 2012-01-11 | 杭州华三通信技术有限公司 | Method for declaring enabled virtual local area network (VLAN) and equipment thereof |
| CN102387079A (en) * | 2011-10-19 | 2012-03-21 | 华为技术有限公司 | Method and network equipment for optimizing 802.1AQ protocol multicasting treatment |
| CN102664790A (en) * | 2012-04-16 | 2012-09-12 | 福建星网锐捷网络有限公司 | Multicast data message forwarding method, system and bridge equipment |
| CN102780607A (en) * | 2012-04-19 | 2012-11-14 | 中兴通讯股份有限公司 | Method and device for dynamically configuring Ethernet service channel |
| CN103780630A (en) * | 2014-02-18 | 2014-05-07 | 迈普通信技术股份有限公司 | Method and system for isolating ports of virtual local area network |
| CN104662850A (en) * | 2012-09-28 | 2015-05-27 | 阿尔卡特朗讯公司 | Method and apparatus for communication path selection |
| CN105915458A (en) * | 2014-11-21 | 2016-08-31 | 阿瓦亚公司 | Shortest Path Bridging (SPB) - Protocol-Independent Multicast (PIM) Interactions |
| CN106533935A (en) * | 2015-09-14 | 2017-03-22 | 华为技术有限公司 | Method for obtaining business chain information in cloud computing system and devices |
| CN106936704A (en) * | 2015-12-30 | 2017-07-07 | 意法半导体公司 | Being classified using hop-by-hop VLAN carries out multipath exchange |
| CN108702322A (en) * | 2016-03-02 | 2018-10-23 | 日本电气株式会社 | network system, terminal, sensor data collection method and program |
| CN112311737A (en) * | 2019-07-31 | 2021-02-02 | 中兴通讯股份有限公司 | Flow isolation method, device and equipment and storage medium |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104579980B (en) * | 2013-10-18 | 2018-05-15 | 新华三技术有限公司 | A kind of multicast data packet forwarding method and apparatus |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6188694B1 (en) * | 1997-12-23 | 2001-02-13 | Cisco Technology, Inc. | Shared spanning tree protocol |
| US6937576B1 (en) * | 2000-10-17 | 2005-08-30 | Cisco Technology, Inc. | Multiple instance spanning tree protocol |
-
2006
- 2006-10-20 CN CN200610113920XA patent/CN101166137B/en not_active Expired - Fee Related
-
2007
- 2007-10-19 WO PCT/CN2007/070930 patent/WO2008046359A1/en active Application Filing
Cited By (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102316000A (en) * | 2011-09-29 | 2012-01-11 | 杭州华三通信技术有限公司 | Method for declaring enabled virtual local area network (VLAN) and equipment thereof |
| CN102387079A (en) * | 2011-10-19 | 2012-03-21 | 华为技术有限公司 | Method and network equipment for optimizing 802.1AQ protocol multicasting treatment |
| CN102387079B (en) * | 2011-10-19 | 2014-04-02 | 华为技术有限公司 | Method and network equipment for optimizing 802.1AQ protocol multicasting treatment |
| CN102664790A (en) * | 2012-04-16 | 2012-09-12 | 福建星网锐捷网络有限公司 | Multicast data message forwarding method, system and bridge equipment |
| CN102664790B (en) * | 2012-04-16 | 2015-03-11 | 福建星网锐捷网络有限公司 | Multicast data message forwarding method, system and bridge equipment |
| CN102780607A (en) * | 2012-04-19 | 2012-11-14 | 中兴通讯股份有限公司 | Method and device for dynamically configuring Ethernet service channel |
| CN102780607B (en) * | 2012-04-19 | 2015-06-03 | 中兴通讯股份有限公司 | Method and device for dynamically configuring Ethernet service channel |
| CN104662850A (en) * | 2012-09-28 | 2015-05-27 | 阿尔卡特朗讯公司 | Method and apparatus for communication path selection |
| CN103780630A (en) * | 2014-02-18 | 2014-05-07 | 迈普通信技术股份有限公司 | Method and system for isolating ports of virtual local area network |
| CN105915458B (en) * | 2014-11-21 | 2020-10-09 | 极进网络公司 | Method for performing shortest path bridging-protocol independent multicast interaction |
| CN105915458A (en) * | 2014-11-21 | 2016-08-31 | 阿瓦亚公司 | Shortest Path Bridging (SPB) - Protocol-Independent Multicast (PIM) Interactions |
| CN106533935A (en) * | 2015-09-14 | 2017-03-22 | 华为技术有限公司 | Method for obtaining business chain information in cloud computing system and devices |
| CN106533935B (en) * | 2015-09-14 | 2019-07-12 | 华为技术有限公司 | A kind of method and apparatus obtaining business chain information in cloud computing system |
| US10735311B2 (en) | 2015-09-14 | 2020-08-04 | Huawei Technologies Co., Ltd. | Method for obtaining information about service chain in cloud computing system and apparatus |
| WO2017045471A1 (en) * | 2015-09-14 | 2017-03-23 | 华为技术有限公司 | Method and apparatus for acquiring service chain information in cloud computing system |
| CN106936704A (en) * | 2015-12-30 | 2017-07-07 | 意法半导体公司 | Being classified using hop-by-hop VLAN carries out multipath exchange |
| CN106936704B (en) * | 2015-12-30 | 2020-08-21 | 意法半导体公司 | Multi-path switching using hop-by-hop VLAN classification |
| CN108702322A (en) * | 2016-03-02 | 2018-10-23 | 日本电气株式会社 | network system, terminal, sensor data collection method and program |
| CN108702322B (en) * | 2016-03-02 | 2022-01-07 | 日本电气株式会社 | Network system, terminal, sensor data collection method, and program |
| US11438417B2 (en) | 2016-03-02 | 2022-09-06 | Nec Corporation | Network system, terminal, sensor data collection method, and program |
| CN112311737A (en) * | 2019-07-31 | 2021-02-02 | 中兴通讯股份有限公司 | Flow isolation method, device and equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2008046359A1 (en) | 2008-04-24 |
| CN101166137B (en) | 2011-04-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101166137B (en) | Method for separating different virtual LAN services | |
| US7929554B2 (en) | Optimized forwarding for provider backbone bridges with both I and B components (IB-PBB) | |
| EP2417735B1 (en) | Enabling an ethernet ring network to scalably support a hub-and-spoke connectivity model | |
| US7633956B1 (en) | System and method for providing support for multipoint L2VPN services in devices without local bridging | |
| US7724745B1 (en) | Method and device for efficient transmission of flood data frames in a backbone network | |
| US8867555B2 (en) | Method and system for transparent LAN services in a packet network | |
| US9225640B2 (en) | Intra-domain and inter-domain bridging over MPLS using MAC distribution via border gateway protocol | |
| CN101160902B (en) | Data forwarding method and switching arrangement | |
| CN101160850B (en) | Method and device for forwarding packet | |
| US7646778B2 (en) | Support of C-tagged service interface in an IEEE 802.1ah bridge | |
| CN103326918B (en) | A kind of message forwarding method and equipment | |
| US7839800B2 (en) | Multiple I-service registration protocol (MIRP) | |
| CN101667969B (en) | Method of accessing IP/L3VPN network of L2VPN network and device thereof | |
| EP1766530A2 (en) | Scaling vlans in a data network | |
| CN103227745B (en) | Shortest path bridge net and layer 3 VLAN interoperability methods and common edge device | |
| EP2378717B1 (en) | Method for interconnecting with nested backbone provider bridges and system thereof | |
| US9264244B2 (en) | Multicasting in a provider backbone bridge network | |
| CN102136981B (en) | Method for realizing E-Tree (Ethernet tree) service in Ethernet and related device | |
| CN105591897B (en) | The MAC Address synchronous method and device of TRILL network | |
| CN101437037B (en) | Tunnel penetration transmission method for two-layer protocol message | |
| CN102594649B (en) | Tunnel multicast packet far-end clone method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110406 Termination date: 20161020 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |