CN104639344A - Sending method and sending device for user multicast message - Google Patents
Sending method and sending device for user multicast message Download PDFInfo
- Publication number
- CN104639344A CN104639344A CN201510069047.8A CN201510069047A CN104639344A CN 104639344 A CN104639344 A CN 104639344A CN 201510069047 A CN201510069047 A CN 201510069047A CN 104639344 A CN104639344 A CN 104639344A
- Authority
- CN
- China
- Prior art keywords
- user multicast
- user
- message
- vlan
- multicast
- 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
Landscapes
- Small-Scale Networks (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a sending method and a sending device for a user multicast message. The sending method comprises the following steps: when an RB receives the user multicast message sent by a user side and if a user multicast tree corresponding to a user multicast address of the user multicast message exists, sending the received user multicast message along the user multicast tree, wherein the user multicast tree is a multicast tree corresponding to the same VLAN (virtual local area network) and used for forbidding message copying on a downstream port which is not connected with a user multicast address receiver. Based on the same inventive concept, the invention discloses a user multicast message sending device which can reduce bandwidth waste of a TRILL network and improves transmission performance of the TRILL network.
Description
Technical field
The present invention relates to communication technical field, particularly a kind of user multicast file transmitting method and device.
Background technology
Current multilink transparent interconnection (Transparent Interconnection of Lots of Links, TRILL) multicast in network, unknown unicast and broadcast are all along user's VLAN (Virtual Local Area Network, VLAN) corresponding distribution tree forwards, arbitrary routing bridge (Routing Bridge, RB) multicast message that user side enters all can be multicast on every other RB, no matter whether this RB exists recipient.
Flood although can be reduced by the vlan information noticed in a network on RB, but can flood on the RB of all this user vlans of existence for the multicast service in VLAN, and no matter whether there is multicast receivers under this RB, especially when when the RB in network is many only there is demand in multicast service on a small amount of RB, just waste is very serious for the bandwidth of TRILL network, also very large on the impact of other regular traffics.
Summary of the invention
In view of this, the application provides a kind of user multicast file transmitting method and device, to solve the problem of the waste of the bandwidth of TRILL network.
For solving the problems of the technologies described above, the technical scheme of the application is achieved in that
A kind of user multicast file transmitting method, be applied on the arbitrary routing bridge RB in multilink transparent interconnection TRILL network, the method comprises:
This RB obtains the user multicast information that in same virtual LAN VLAN, on other RB, this VLAN is corresponding, and generates user multicast address accept person list item according to the user multicast information obtained; Described user multicast information comprises: VLAN identifies ID, user multicast address and RB pet name Nickname; Described RB pet name Nickname is the Nickname of the RB be connected with the equipment as described user multicast address accept person;
When this RB receives the user multicast message of user side transmission, determine whether there is the user multicast tree that the user multicast address of this user multicast message is corresponding;
When determining to there is not corresponding user multicast tree, if determine local user multicast address accept person list item corresponding to VLAN ID and user multicast address that there is this user multicast message further, then this user multicast message is sent in the multicast tree that this VLAN ID is corresponding, user multicast tree is generated for described user multicast address, and notify that the RB in the VLAN that described VLAN ID is corresponding generates user multicast tree for this user multicast address, wherein, identical as the multicast tree that the user multicast tree that the RB of leaf node generates is corresponding with described VLAN ID in the multicast tree that described VLAN ID is corresponding, as the multicast tree that the user multicast tree that the RB of non-leaf nodes generates is copied for port blocking message that downstream is not connected described user multicast address accept person by multicast tree corresponding to described VLAN ID,
When determining to there is corresponding user multicast tree, along the user multicast message that the transmission and reception of this user multicast tree are arrived.
A kind of user multicast packet transmission device, be applied in the arbitrary routing bridge RB in multilink transparent interconnection TRILL network, it is characterized in that, this device comprises: receiving element, generation unit and process transmitting element;
Described receiving element, for receiving the user multicast message that user side sends;
Described generation unit, for obtaining the user multicast information that in same virtual LAN VLAN, on other RB, this VLAN is corresponding, and generates user multicast address accept person list item according to the user multicast information obtained; Described user multicast information comprises: VLAN identifies ID, user multicast address and RB pet name Nickname; Described RB pet name Nickname is the Nickname of the RB be connected with the equipment as described user multicast address accept person;
Described process transmitting element, during for receiving user multicast message that user side sends when described receiving element, determines whether there is the user multicast tree that the user multicast address of this user multicast message is corresponding, when determining to there is not corresponding user multicast tree, if determine the user multicast address accept person list item that local described generation unit corresponding to VLAN ID and user multicast address that there is this user multicast message generates further, then this user multicast message is sent in the multicast tree that this VLAN ID is corresponding, user multicast tree is generated for described user multicast address, and notify that the RB in the VLAN that described VLAN ID is corresponding generates user multicast tree for this user multicast address, wherein, identical as the multicast tree that the user multicast tree that the RB of leaf node generates is corresponding with described VLAN ID in the multicast tree that described VLAN ID is corresponding, as the multicast tree that the user multicast tree that the RB of non-leaf nodes generates is copied for port blocking message that downstream is not connected described user multicast address accept person by multicast tree corresponding to described VLAN ID, when determining to there is corresponding user multicast tree, along the user multicast message that the transmission and reception of this user multicast tree are arrived.
From technical scheme above, on RB, user multicast tree is set up for user multicast address in the application, when receiving user multicast message corresponding to this user multicast address, this user multicast message is sent along this user multicast tree, this user multicast message is not sent for the RB that there is not this user multicast address accept person, the waste of the bandwidth of TRILL network can be reduced, thus improve the transmission performance of TRILL network.
Accompanying drawing explanation
Fig. 1 is TRILL network schematic diagram in the embodiment of the present application;
Fig. 2 is user multicast file transmitting method schematic flow sheet in the embodiment of the present application one;
Fig. 3 is user multicast message transmission flow schematic diagram in the embodiment of the present application two;
Fig. 4 is the structural representation of the device being applied to above-mentioned technology in the embodiment of the present application.
Embodiment
In order to make object of the present invention, technical scheme and advantage clearly understand, to develop simultaneously embodiment below in conjunction with accompanying drawing, technical scheme of the present invention is described in detail.
A kind of user multicast file transmitting method is provided, on the arbitrary RB in application TRILL network in the embodiment of the present application.On RB, user multicast tree is set up for user multicast address in present application example, when receiving this user multicast address respective user multicast message, this user multicast message is sent along this user multicast tree, this user multicast message is not sent for the RB that there is not this user multicast address accept person, the waste of the bandwidth of TRILL network can be reduced, thus improve the transmission performance of TRILL network.
When the multicast group that certain user multicast address accept person that arbitrary RB receives user side sends joins message, create the user multicast address repeat listing that this user multicast address is corresponding, user multicast address repeat listing comprises: VLAN mark (ID), user multicast address and receive this multicast and to join message the port numbers of port.
User multicast information corresponding for this user multicast address is carried at user multicast group and adds in message by this RB, sends this user multicast group add message along the multicast tree that VLAN is corresponding; Described user multicast information comprises: the VLAN ID in the user multicast address repeat listing that this VLAN is corresponding and user multicast address, and the RB pet name (Nickname) of this RB, be namely connected with this user multicast address accept person the RB Nickname of RB.
RB in this VLAN receives user multicast group when adding message, obtains this user multicast group and adds the user multicast information of carrying in message, and generates user multicast address accept person list item according to the user multicast information obtained.The user multicast address accept person list item generated comprises: VLAN ID, user multicast address and RB Nickname; Described RB Nickname is the Nickname of the RB be connected with the equipment as described user multicast address accept person.
Below in conjunction with accompanying drawing, describe the generative process of user multicast address repeat listing and user multicast recipient list item in detail.
Be TRILL network schematic diagram in the embodiment of the present application see Fig. 1, Fig. 1.In Fig. 1, the multicast tree root of the multicast tree of VLAN 1 correspondence is RB5, RB1 be the RB be connected with multicast source PC10, RB4 is the RB be connected with multicast receivers PC40.
RB4 receives multicast group that PC40 sends when joining message, and generate user multicast address repeat listing in this locality, this user multicast address repeat listing comprises: VLAN 1, user multicast address (224.1.1.1), port one.
RB4 sends user multicast group and adds message in the multicast tree that VLAN1 is corresponding, carries user multicast information within the message, is specially: VLAN 1, user multicast address (224.1.1.1) and RB Nickname (RB4).
Each RB in the multicast tree of VLAN 1 correspondence receives this user multicast group when adding message, and processing procedure is identical, receives this user multicast group add message for RB5:
RB5 receives this user multicast group when adding message, generates user multicast recipient list item according to the user multicast information of carrying in this message.See table 1, table 1 is the content that the user multicast recipient list item in the embodiment of the present application, RB5 generated comprises.
| VLAN ID | User multicast address | RB Nickname |
| VLAN 1 | 224.1.1.1 | RB4 |
Table 1
Follow-up when arbitrary RB receive again user multicast group add message time, if when there is corresponding VLAN ID and user multicast recipient list item corresponding to user multicast address, this user multicast group is added the RB Nickname carried in message and add in corresponding user multicast recipient list item; Otherwise, add the user multicast information of carrying in message for the user multicast group received and generate user multicast recipient list item.
When arbitrary RB receives user multicast group exit message, the RB Nickname carried in this user multicast group exit message in user multicast recipient list item corresponding to the VLAN ID carried in this user multicast group exit message and user multicast address is deleted, if after deleting this RB Nickname, RB Nickname in this user multicast recipient list item is empty, then by this user multicast receiver-table entry deletion.
Below in conjunction with accompanying drawing, to describe in detail in the embodiment of the present application and how to send user multicast message.
Embodiment one
Be user multicast file transmitting method schematic flow sheet in the embodiment of the present application one see Fig. 2, Fig. 2.Concrete steps are:
Step 201, when RB receives the user multicast message of user side transmission, determines whether there is the user multicast tree that the user multicast address of this multicast message is corresponding.
Step 202, this RB is when determining to there is not corresponding user multicast tree, if determine local user multicast address accept person list item corresponding to VLAN ID and user multicast address that there is this user multicast message further, then this user multicast message is sent in the multicast tree that this VLAN ID is corresponding, user multicast tree is generated for described user multicast address, and notify that the RB in the VLAN that described VLAN ID is corresponding generates user multicast tree for this user multicast address, process ends.
Identical as the user multicast tree multicast tree corresponding with this VLAN ID that the RB of leaf node generates in the multicast tree that the ID of VLAN described in this step is corresponding, setting as the user multicast that the RB of non-leaf nodes generates is the multicast tree that port blocking message that downstream is not connected described user multicast address accept person by multicast tree that described VLAN ID is corresponding copies.
Generate user multicast tree for described user multicast address in this step, and notify that the RB in the VLAN that described VLAN ID is corresponding generates user multicast tree for this user multicast address, comprising:
This RB sets for the user multicast that the multicast tree that described user multicast address creation is corresponding with described VLAN ID is identical, and notifies that the RB in the VLAN that described VLAN ID is corresponding sets for the user multicast that this user multicast address creation is identical with the multicast tree in this VLAN;
If the non-leaf nodes in the multicast tree that this VLAN ID of this RB is corresponding, then the port blocking message user multicast of establishment tree upstream and downstream not being connected this user multicast address accept person copies;
This RB sends the renewal message for this multicast address to each RB in VLAN corresponding to this VLAN ID, and the port blocking message that the user multicast of establishment tree upstream and downstream does not connect this user multicast address accept person is copied by the non-leaf nodes receiving this renewal message.
Still for Fig. 1, in Fig. 1, RB1 receives user multicast address in VLAN 1 when being the user multicast message of 224.1.1.1, if determine there is not user multicast tree corresponding to user multicast address 224.1.1.1 in this locality, and determine to there is user multicast address accept person list item corresponding to VLAN 1 and user multicast address 224.1.1.1, as table 1, then the multicast tree of this user multicast message along VLAN 1 correspondence is sent; And create user multicast tree for user multicast address 224.1.1.1, during specific implementation, unique tree mark Tree1 can be distributed, for identifying this user multicast tree for this user multicast tree.
RB1 notifies that the RB (RB5, RB2, RB3 and RB4) in VLAN 1 creates the user multicast identical with the multicast tree in this VLAN for this user multicast address 224.1.1.1 and sets.
When RB5, RB2, RB3 and RB4 receive this notice, create the user multicast tree that user multicast address 224.1.1.1 is corresponding in this locality, and the multicast tree creating user multicast tree corresponding with VLAN 1 is identical, copies the multicast tree of VLAN 1 correspondence.
RB1 determines the leaf node of this RB as the multicast tree in VLAN 1, then do not do further process to the user multicast tree created.
RB1 sends the renewal message for user multicast address 224.1.1.1 to RB (RB5, RB2, RB3 and RB4) in VLAN 1.
When RB2, RB3 and RB4 receive this renewal message, determine that this RB is the leaf node of multicast tree, the user multicast tree created is not upgraded.
When RB5 receives this renewal message, determine that this RB is the non-leaf nodes of multicast tree, then the port blocking message user multicast of establishment tree upstream and downstream not being connected this user multicast address accept person copies.As Fig. 1 middle port 1, port 2 and port 3 all forbid that message copies, such ports having 4 can copy packet forwarding.
By the renewal of above-mentioned user multicast message, RB1 receives user multicast address again when being the user multicast message of 244.1.1.1, can send along the user multicast tree of setting up, such multicast message would not be sent on RB2 and RB3, only can be sent on the RB4 of recipient.
There is not the recipient of this user multicast address in the present embodiment for RB1 this locality, if this locality also exists the recipient of this user multicast address, then this user multicast message is forwarded in this locality yet.
Step 203, this RB when determining to there is corresponding user multicast tree, along the user multicast message that the transmission and reception of this user multicast tree are arrived.
Embodiment two
Be user multicast message transmission flow schematic diagram in the embodiment of the present application two see Fig. 3, Fig. 3.Concrete steps are:
Step 301, RB receives the user multicast message that user side sends.
Step 302, this RB determine the local user multicast address that whether there is this user multicast message corresponding abandon list item, if so, perform step 303; Otherwise, perform step 304.
Step 303, this RB by this user multicast packet loss, process ends.
Step 304, this RB determines whether there is user multicast tree corresponding to the user multicast address of this user multicast message, if so, performs step 305; Otherwise, perform step 306.
Step 305, the user multicast message that this RB arrives along the transmission and reception of this user multicast tree, process ends.
Step 306, this RB determines local user multicast address accept person list item corresponding to VLAN ID and user multicast address that whether there is this user multicast message, if so, performs step 307; Otherwise, perform step 308.
Step 307, this user multicast message sends by this RB in the multicast tree that described VLAN ID is corresponding; For described user multicast address creation user multicast tree, and notify that the RB in the VLAN that described VLAN ID is corresponding sets for this user multicast address creation user multicast, process ends.
Step 308, this RB determines the local recipient that whether there is this user multicast address, if so, performs step 309; Otherwise, perform step 310.
The recipient of user multicast address in the present embodiment, namely receiver address is the equipment of the user multicast message of this user multicast address.
Step 309, this RB forwards this user multicast message in this locality, process ends.
Step 310, the user multicast packet loss that this RB will receive, and generate described user multicast address corresponding abandon list item.
In the present embodiment for generate user multicast address corresponding abandon list item time, arrange ageing time for this abandons list item, ageing time then, is deleted this and is abandoned list item.
In the embodiment of the present application, RB receives multicast group that user multicast address accept person sends when exiting message, deletes local corresponding user multicast group address forwarding-table item, and sends user multicast group exit message to RB in corresponding VLAN; This user multicast group exit message carries the Nickname of VLAN ID, user multicast group address and this RB.
When this RB receives the user multicast group exit message that other RB send, the RB Nickname that the VLAN ID carried in this user multicast group exit message in local user's multicast receivers list item and described user multicast group exit message corresponding to user multicast group address carry is deleted;
If the RB Nickname deleted in the user multicast address accept person list item of described RB Nickname for empty, then deletes this user multicast address accept list item.
If the RB Nickname deleted in the user multicast address accept person list item of described RB Nickname is not for empty, and this RB as the multicast source corresponding with this user multicast address be connected RB time, in corresponding VLAN, RB sends the renewal message for this user multicast address, makes the RB as non-leaf nodes upgrade corresponding user multicast tree for this user multicast address;
If the RB Nickname deleted in the user multicast address accept person list item of described RB Nickname is for time empty, and this RB as the multicast source corresponding with this user multicast address be connected RB time, delete the user multicast tree that this user multicast address is corresponding, and deletion message is sent to RB in described VLAN, make RB in described VLAN delete user multicast tree corresponding to described user multicast address.
Based on same inventive concept, the application also proposes a kind of user multicast packet transmission device, is applied in the arbitrary RB in TRILL network.It is the structural representation of the device being applied to above-mentioned technology in the embodiment of the present application see Fig. 4, Fig. 4.This device comprises: receiving element 401, generation unit 402 and process transmitting element 403;
Receiving element 401, for receiving the user multicast message that user side sends;
Generation unit 402, for obtaining the user multicast information that in same virtual LAN VLAN, on other RB, this VLAN is corresponding, and generates user multicast address accept person list item according to the user multicast information obtained; Described user multicast information comprises: VLAN identifies ID, user multicast address and RB pet name Nickname; Described RB pet name Nickname is the Nickname of the RB be connected with the equipment as described user multicast address accept person;
Process transmitting element 403, during for receiving user multicast message that user side sends when receiving element 401, determines whether there is user multicast corresponding to the user multicast address of this user multicast message and sets, when determining to there is not corresponding user multicast tree, if determine the user multicast address accept person list item that local generation unit 402 corresponding to VLAN ID and user multicast address that there is this user multicast message generates further, then this user multicast message is sent in the multicast tree that this VLAN ID is corresponding, user multicast tree is generated for described user multicast address, and notify that the RB in the VLAN that described VLAN ID is corresponding generates user multicast tree for this user multicast address, wherein, identical as the multicast tree that the user multicast tree that the RB of leaf node generates is corresponding with described VLAN ID in the multicast tree that described VLAN ID is corresponding, as the multicast tree that the user multicast tree that the RB of non-leaf nodes generates is copied for port blocking message that downstream is not connected described user multicast address accept person by multicast tree corresponding to described VLAN ID, when determining to there is corresponding user multicast tree, along the user multicast message that the transmission and reception of this user multicast tree are arrived.
Preferably,
Process transmitting element 403, the user multicast identical specifically for the multicast tree corresponding with described VLAN ID for described user multicast address creation is set, and notifies that the RB in the VLAN that described VLAN ID is corresponding sets for the user multicast that the multicast tree that this user multicast address creation is corresponding with described VLAN ID is identical; If the non-leaf nodes in the multicast tree that this RB described VLAN ID is corresponding, then the port blocking message user multicast of establishment tree upstream and downstream not being connected this user multicast address accept person copies; RB in the VLAN that described VLAN ID is corresponding sends the renewal message for this user multicast address, and the port blocking message that the user multicast of establishment tree upstream and downstream does not connect this user multicast address accept person is copied by the RB as non-leaf nodes receiving this renewal message.
Preferably,
Process transmitting element 403, be further used for when determining to there is not corresponding user multicast tree, if determine local user multicast address accept person list item corresponding to VLAN ID and user multicast address that there is not this user multicast message further, then determine the local recipient that whether there is this user multicast address, if so, this user multicast message is forwarded in this locality; Otherwise, generate described user multicast address corresponding abandon list item; And for this abandons list item, ageing time is set, when ageing time then, delete this and abandon list item.
Preferably,
Process transmitting element 403, before determining whether there is user multicast tree corresponding to the user multicast address of this multicast message further, determine the local user multicast address that whether there is this user multicast message corresponding abandon list item, if so, by this user multicast packet loss; Otherwise, described in execution, determine whether there is the user multicast tree operations that the user multicast address of this multicast message is corresponding.
Preferably,
Process transmitting element 403, be further used for this RB and add message along the multicast tree transmission user multicast group that arbitrary VLAN ID is corresponding, the VLAN ID in user multicast address repeat listing corresponding to this VLAN ID and user multicast address is carried in this message, and the RB Nickname of this RB;
Receiving element 401, the user multicast group being further used for receiving other RB transmission adds message;
Generation unit 402, the user multicast group sent specifically for being received other RB by receiving element 401 adds message, obtains this user multicast group and adds the user multicast information of carrying in message.
Preferably,
Receiving element 401, the multicast group sent for receiving user multicast address accept person exits message; Receive the user multicast group exit message that other RB send;
Process transmitting element 403, be further used for receiving element 401 and receive multicast group that user multicast address accept person sends when exiting message, in corresponding VLAN, RB sends user multicast group exit message; This user multicast group exit message carries the Nickname of VLAN ID, user multicast group address and this RB;
Generation unit 402, be further used for, when receiving element 401 receives the user multicast group exit message that other RB send, the RB Nickname that the VLAN ID carried in this user multicast group exit message in local user's multicast receivers list item and described user multicast group exit message corresponding to user multicast group address carry being deleted; If the RB Nickname deleted in the user multicast address accept person list item of described RB Nickname for empty, then deletes this user multicast address accept list item.
Preferably,
Process transmitting element 403, the RB Nickname deleted if be further used in the user multicast address accept person list item of described RB Nickname is not sky, and this RB as the multicast source corresponding with this user multicast address be connected RB time, in corresponding VLAN, RB sends the renewal message for this user multicast address, makes the RB as non-leaf nodes upgrade corresponding user multicast tree for this user multicast address; If the RB Nickname deleted in the user multicast address accept person list item of described RB Nickname is for time empty, and this RB as the multicast source corresponding with this user multicast address be connected RB time, delete the user multicast tree that this user multicast address is corresponding, and deletion message is sent to RB in described VLAN, make RB in described VLAN delete user multicast tree corresponding to described user multicast address.
The unit of above-described embodiment can be integrated in one, and also can be separated deployment; A unit can be merged into, also can split into multiple subelement further.
In sum, the application by setting up user multicast tree for user multicast address on RB, when receiving this user multicast address respective user multicast message, this user multicast message is sent along this user multicast tree, this user multicast message is not sent for the RB that there is not this user multicast address accept person, the waste of the bandwidth of TRILL network can be reduced, thus improve the transmission performance of TRILL network.
The foregoing is only preferred embodiment of the present invention, not in order to limit the present invention, within the spirit and principles in the present invention all, any amendment made, equivalent replacement, improvement etc., all should be included within the scope of protection of the invention.
Claims (14)
1. a user multicast file transmitting method, be applied on the arbitrary routing bridge RB in multilink transparent interconnection TRILL network, it is characterized in that, the method comprises:
This RB obtains the user multicast information that in same virtual LAN VLAN, on other RB, this VLAN is corresponding, and generates user multicast address accept person list item according to the user multicast information obtained; Described user multicast information comprises: VLAN identifies ID, user multicast address and RB pet name Nickname; Described RB pet name Nickname is the Nickname of the RB be connected with the equipment as described user multicast address accept person;
When this RB receives the user multicast message of user side transmission, determine whether there is the user multicast tree that the user multicast address of this user multicast message is corresponding;
When determining to there is not corresponding user multicast tree, if determine local user multicast address accept person list item corresponding to VLAN ID and user multicast address that there is this user multicast message further, then this user multicast message is sent in the multicast tree that this VLAN ID is corresponding, user multicast tree is generated for described user multicast address, and notify that the RB in the VLAN that described VLAN ID is corresponding generates user multicast tree for this user multicast address, wherein, identical as the multicast tree that the user multicast tree that the RB of leaf node generates is corresponding with described VLAN ID in the multicast tree that described VLAN ID is corresponding, as the multicast tree that the user multicast tree that the RB of non-leaf nodes generates is copied for port blocking message that downstream is not connected described user multicast address accept person by multicast tree corresponding to described VLAN ID,
When determining to there is corresponding user multicast tree, along the user multicast message that the transmission and reception of this user multicast tree are arrived.
2. method according to claim 1, is characterized in that, described for described user multicast address generation user multicast tree, and notifies that the RB in the VLAN that described VLAN ID is corresponding generates user multicast tree for this user multicast address, comprising:
This RB sets for the user multicast that the multicast tree that described user multicast address creation is corresponding with described VLAN ID is identical, and notifies that the RB in the VLAN that described VLAN ID is corresponding sets for the user multicast that the multicast tree that this user multicast address creation is corresponding with described VLAN ID is identical;
If the non-leaf nodes in the multicast tree that this RB described VLAN ID is corresponding, then the port blocking message user multicast of establishment tree upstream and downstream not being connected this user multicast address accept person copies;
This RB sends the renewal message for this user multicast address to the RB in VLAN corresponding to described VLAN ID, and the port blocking message that the user multicast of establishment tree upstream and downstream does not connect this user multicast address accept person is copied by the RB as non-leaf nodes receiving this renewal message.
3. method according to claim 1, is characterized in that, described method comprises further:
When determining to there is not corresponding user multicast tree, if determine local user multicast address accept person list item corresponding to VLAN ID and user multicast address that there is not this user multicast message further, then determine the local recipient that whether there is this user multicast address, if so, this user multicast message is forwarded in this locality; Otherwise, generate described user multicast address corresponding abandon list item; And for this abandons list item, ageing time is set, when ageing time then, delete this and abandon list item.
4. method according to claim 3, is characterized in that, when this RB described receives the user multicast message that user side sends, described in determine whether there is user multicast tree corresponding to the user multicast address of this multicast message before, described method comprises further:
This RB determine the local user multicast address that whether there is this user multicast message corresponding abandon list item, if so, by this user multicast packet loss; Otherwise, described in execution, determine whether there is the user multicast tree step that the user multicast address of this multicast message is corresponding.
5. the method according to claim 1-4 any one, is characterized in that, described method comprises further:
This RB sends user multicast group along the multicast tree that arbitrary VLAN ID is corresponding and adds message, carries the VLAN ID in user multicast address repeat listing corresponding to this VLAN ID and user multicast address in this message, and the RB Nickname of this RB;
This RB described obtains the user multicast information that in same VLAN, on other RB, this VLAN is corresponding, comprising:
This RB receives user multicast group that other RB send when adding message, obtains this user multicast group and adds the user multicast information of carrying in message.
6. the method according to claim 1-4 any one, is characterized in that, described method comprises further:
This RB receives multicast group that user multicast address accept person sends when exiting message, and in corresponding VLAN, RB sends user multicast group exit message; This user multicast group exit message carries the Nickname of VLAN ID, user multicast group address and this RB;
When this RB receives the user multicast group exit message that other RB send, the RB Nickname that the VLAN ID carried in this user multicast group exit message in local user's multicast receivers list item and described user multicast group exit message corresponding to user multicast group address carry is deleted;
If the RB Nickname deleted in the user multicast address accept person list item of described RB Nickname for empty, then deletes this user multicast address accept list item.
7. method according to claim 6, is characterized in that, described method comprises further:
If the RB Nickname deleted in the user multicast address accept person list item of described RB Nickname is not for empty, and this RB as the multicast source corresponding with this user multicast address be connected RB time, in corresponding VLAN, RB sends the renewal message for this user multicast address, makes the RB as non-leaf nodes upgrade corresponding user multicast tree for this user multicast address;
If the RB Nickname deleted in the user multicast address accept person list item of described RB Nickname is for time empty, and this RB as the multicast source corresponding with this user multicast address be connected RB time, delete the user multicast tree that this user multicast address is corresponding, and deletion message is sent to RB in described VLAN, make RB in described VLAN delete user multicast tree corresponding to described user multicast address.
8. a user multicast packet transmission device, be applied in the arbitrary routing bridge RB in multilink transparent interconnection TRILL network, it is characterized in that, this device comprises: receiving element, generation unit and process transmitting element;
Described receiving element, for receiving the user multicast message that user side sends;
Described generation unit, for obtaining the user multicast information that in same virtual LAN VLAN, on other RB, this VLAN is corresponding, and generates user multicast address accept person list item according to the user multicast information obtained; Described user multicast information comprises: VLAN identifies ID, user multicast address and RB pet name Nickname; Described RB pet name Nickname is the Nickname of the RB be connected with the equipment as described user multicast address accept person;
Described process transmitting element, during for receiving user multicast message that user side sends when described receiving element, determines whether there is the user multicast tree that the user multicast address of this user multicast message is corresponding, when determining to there is not corresponding user multicast tree, if determine the user multicast address accept person list item that local described generation unit corresponding to VLAN ID and user multicast address that there is this user multicast message generates further, then this user multicast message is sent in the multicast tree that this VLAN ID is corresponding, user multicast tree is generated for described user multicast address, and notify that the RB in the VLAN that described VLAN ID is corresponding generates user multicast tree for this user multicast address, wherein, identical as the multicast tree that the user multicast tree that the RB of leaf node generates is corresponding with described VLAN ID in the multicast tree that described VLAN ID is corresponding, as the multicast tree that the user multicast tree that the RB of non-leaf nodes generates is copied for port blocking message that downstream is not connected described user multicast address accept person by multicast tree corresponding to described VLAN ID, when determining to there is corresponding user multicast tree, along the user multicast message that the transmission and reception of this user multicast tree are arrived.
9. device according to claim 8, is characterized in that,
Described process transmitting element, the user multicast identical specifically for the multicast tree corresponding with described VLAN ID for described user multicast address creation is set, and notifies that the RB in the VLAN that described VLAN ID is corresponding sets for the user multicast that the multicast tree that this user multicast address creation is corresponding with described VLAN ID is identical; If the non-leaf nodes in the multicast tree that this RB described VLAN ID is corresponding, then the port blocking message user multicast of establishment tree upstream and downstream not being connected this user multicast address accept person copies; RB in the VLAN that described VLAN ID is corresponding sends the renewal message for this user multicast address, and the port blocking message that the user multicast of establishment tree upstream and downstream does not connect this user multicast address accept person is copied by the RB as non-leaf nodes receiving this renewal message.
10. device according to claim 8, is characterized in that,
Described process transmitting element, be further used for when determining to there is not corresponding user multicast tree, if determine local user multicast address accept person list item corresponding to VLAN ID and user multicast address that there is not this user multicast message further, then determine the local recipient that whether there is this user multicast address, if so, this user multicast message is forwarded in this locality; Otherwise, generate described user multicast address corresponding abandon list item; And for this abandons list item, ageing time is set, when ageing time then, delete this and abandon list item.
11. devices according to claim 10, is characterized in that,
Described process transmitting element, before determining whether there is user multicast tree corresponding to the user multicast address of this multicast message further, determine the local user multicast address that whether there is this user multicast message corresponding abandon list item, if so, by this user multicast packet loss; Otherwise, described in execution, determine whether there is the user multicast tree operations that the user multicast address of this multicast message is corresponding.
12. devices according to Claim 8 described in-11 any one, is characterized in that,
Described process transmitting element, be further used for this RB and add message along the multicast tree transmission user multicast group that arbitrary VLAN ID is corresponding, the VLAN ID in user multicast address repeat listing corresponding to this VLAN ID and user multicast address is carried in this message, and the RB Nickname of this RB;
Described receiving element, the user multicast group being further used for receiving other RB transmission adds message;
Described generation unit, the user multicast group sent specifically for being received other RB by described receiving element adds message, obtains this user multicast group and adds the user multicast information of carrying in message.
13. devices according to Claim 8 described in-11 any one, is characterized in that,
Described receiving element, the multicast group sent for receiving user multicast address accept person exits message; Receive the user multicast group exit message that other RB send;
Described process transmitting element, be further used for described receiving element and receive multicast group that user multicast address accept person sends when exiting message, in corresponding VLAN, RB sends user multicast group exit message; This user multicast group exit message carries the Nickname of VLAN ID, user multicast group address and this RB;
Described generation unit, be further used for, when described receiving element receives the user multicast group exit message that other RB send, the RB Nickname that the VLAN ID carried in this user multicast group exit message in local user's multicast receivers list item and described user multicast group exit message corresponding to user multicast group address carry being deleted; If the RB Nickname deleted in the user multicast address accept person list item of described RB Nickname for empty, then deletes this user multicast address accept list item.
14. devices according to claim 13, is characterized in that,
Described process transmitting element, the RB Nickname deleted if be further used in the user multicast address accept person list item of described RB Nickname is not sky, and this RB as the multicast source corresponding with this user multicast address be connected RB time, in corresponding VLAN, RB sends the renewal message for this user multicast address, makes the RB as non-leaf nodes upgrade corresponding user multicast tree for this user multicast address; If the RB Nickname deleted in the user multicast address accept person list item of described RB Nickname is for time empty, and this RB as the multicast source corresponding with this user multicast address be connected RB time, delete the user multicast tree that this user multicast address is corresponding, and deletion message is sent to RB in described VLAN, make RB in described VLAN delete user multicast tree corresponding to described user multicast address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510069047.8A CN104639344B (en) | 2015-02-10 | 2015-02-10 | A kind of user multicast file transmitting method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510069047.8A CN104639344B (en) | 2015-02-10 | 2015-02-10 | A kind of user multicast file transmitting method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104639344A true CN104639344A (en) | 2015-05-20 |
| CN104639344B CN104639344B (en) | 2017-12-15 |
Family
ID=53217699
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510069047.8A Active CN104639344B (en) | 2015-02-10 | 2015-02-10 | A kind of user multicast file transmitting method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104639344B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106789644A (en) * | 2016-11-29 | 2017-05-31 | 深圳市楠菲微电子有限公司 | A kind of retransmission method and device of TRILL multicast messages |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011144079A2 (en) * | 2011-05-25 | 2011-11-24 | 华为技术有限公司 | Method and apparatus for generating distribution trees, and routing bridge |
| US20110299527A1 (en) * | 2010-06-08 | 2011-12-08 | Brocade Communications Systems, Inc. | Supporting multiple multicast trees in trill networks |
| CN102299845A (en) * | 2011-09-20 | 2011-12-28 | 神州数码网络(北京)有限公司 | Multi-link transparent interconnection multicast frame transmission method and system thereof |
| CN103209132A (en) * | 2012-01-16 | 2013-07-17 | 华为技术有限公司 | Method, device and system for achieving multicast in transparent interconnection of lots of links (TRILL) network |
| CN103873373A (en) * | 2012-12-11 | 2014-06-18 | 杭州华三通信技术有限公司 | Multicast data message forwarding method and equipment |
-
2015
- 2015-02-10 CN CN201510069047.8A patent/CN104639344B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110299527A1 (en) * | 2010-06-08 | 2011-12-08 | Brocade Communications Systems, Inc. | Supporting multiple multicast trees in trill networks |
| WO2011144079A2 (en) * | 2011-05-25 | 2011-11-24 | 华为技术有限公司 | Method and apparatus for generating distribution trees, and routing bridge |
| CN102299845A (en) * | 2011-09-20 | 2011-12-28 | 神州数码网络(北京)有限公司 | Multi-link transparent interconnection multicast frame transmission method and system thereof |
| CN103209132A (en) * | 2012-01-16 | 2013-07-17 | 华为技术有限公司 | Method, device and system for achieving multicast in transparent interconnection of lots of links (TRILL) network |
| CN103873373A (en) * | 2012-12-11 | 2014-06-18 | 杭州华三通信技术有限公司 | Multicast data message forwarding method and equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106789644A (en) * | 2016-11-29 | 2017-05-31 | 深圳市楠菲微电子有限公司 | A kind of retransmission method and device of TRILL multicast messages |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104639344B (en) | 2017-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100379226C (en) | Virtual special network multicast method by virtual router mode | |
| CN102035729B (en) | Multicast data forwarding method | |
| EP2989755B1 (en) | Efficient multicast delivery to dually connected (vpc) hosts in overlay networks | |
| WO2000064100A1 (en) | Method and apparatus for forwarding multicast data | |
| CN102281181B (en) | Method, device and system for realizing multicast forwarding in EVB (Extended VLAN (Virtual Local Area Network) Bridge) equipment | |
| CN103067286A (en) | Multicast data transmission method and equipment | |
| CN104579982B (en) | A kind of Layer 2 Multicast data message forwarding method and device | |
| CN103795626A (en) | Method and device for rapid protection switching during multicast process | |
| CN102916888B (en) | Multicast data transmission method and multicast data transmission device | |
| CN109981308A (en) | Message transmitting method and device | |
| CN104539545A (en) | Multicast message forwarding method and device of TRILL network | |
| KR101491397B1 (en) | Efficient multicasting in a distributed system architecture | |
| CN101163103A (en) | Method of implementing fast rerouting | |
| CN104113483B (en) | A kind of method for multicast communication and convergence switch | |
| CN102316083B (en) | Method and device for realizing multicast service in Internet protocol (IP) network | |
| CN113472656B (en) | Two-layer switching equipment and method for forwarding multicast data message | |
| CN104639344A (en) | Sending method and sending device for user multicast message | |
| CN110868353B (en) | Message processing method and device | |
| CN102843303B (en) | Multicast message processing method in PIM and device | |
| CN102394813B (en) | Multicast routing table item management method and router | |
| WO2014199924A1 (en) | Control device, communication system, and control method and program of relay device | |
| CN108011828A (en) | A kind of multicast switching method, device, core layer switch and storage medium | |
| CN108111323A (en) | Realization system of igmpsnooping protocol under vxworks system | |
| CN104283796A (en) | Multicast distribution tree establishment method and device | |
| CN106330645B (en) | Method and device for fast convergence of Ethernet ring multicast Proxy mode service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant before: Huasan Communication Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |