WO2016086721A1 - 在trill网络中传输组播数据的方法、装置和系统 - Google Patents

在trill网络中传输组播数据的方法、装置和系统 Download PDF

Info

Publication number
WO2016086721A1
WO2016086721A1 PCT/CN2015/091864 CN2015091864W WO2016086721A1 WO 2016086721 A1 WO2016086721 A1 WO 2016086721A1 CN 2015091864 W CN2015091864 W CN 2015091864W WO 2016086721 A1 WO2016086721 A1 WO 2016086721A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
multicast data
urb
srb
user equipment
Prior art date
Application number
PCT/CN2015/091864
Other languages
English (en)
French (fr)
Inventor
张伟东
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016086721A1 publication Critical patent/WO2016086721A1/zh

Links

Images

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, apparatus and system for transmitting multicast data in a TRILL network.
  • TRILL Transparent Interconnection of lots of links
  • IP Internet Protocol
  • the network interconnection protocol is applied to the Ethernet frame forwarding, and the Layer 2 routing is implemented by extending the IS-IS protocol (Intermediate System to Intermediate System Routing Protocol).
  • the Ethernet switch running the TRILL protocol is It is called a routing bridge (RB), and a network set composed of multiple RBs is called a TRILL network.
  • RB routing bridge
  • Each device in the TRILL network uses its own node as the source node, and calculates the shortest path to all other nodes based on the shortest path algorithm. If there are multiple equal-cost links, load balancing can be performed. This ensures the forwarding efficiency of the data center network and circumvents the shortcomings of technologies such as STP/MSTP (Spanning Tree Protocol)/Multi-Service Transfer Platform (SDH-based multi-service transport platform).
  • STP/MSTP Shortning Tree Protocol
  • SDH-based multi-service transport platform Multi-Service Transfer Platform
  • TRILL technology has gradually become the basic technology for improving the performance of data center networks.
  • the TRILL network is increasingly demanding various business support, and the group of Virtual Local Area Network (Virtual Local Area Network) Broadcast one of them.
  • the TRILL network is based on the Layer 2 VLAN as the forwarding path of the multicast tree, the multicast user and the multicast source must be in the same VLAN to receive multicast traffic. This makes the implementation of multicast across VLANs difficult.
  • FIG. 1 is a schematic diagram of a networking for implementing cross-VLAN multicast on a TRILL network in the related art.
  • RB1 to RB7 form a TRILL network
  • RB1 and RB2 are respectively connected to switch 1 and switch 2
  • switch 1 and switch 2 are respectively connected to multicast server 1 and multicast server 2 to represent different multicast sources distributed on the TRILL network in different places
  • RB5 ⁇ RB7 respectively hangs user equipments 1 to 3.
  • Multicast service The device 1 and the multicast server 2 provide different multicast data content
  • the switch 1 and the switch 2 are respectively responsible for performing multicast forwarding across the VLAN to the user equipment.
  • the multicast join request packet sent by the user equipment needs to be forwarded to the switch 1 or 2 directly connected to the TRILL network through the TRILL network. Binding of the multicast VLAN to the user VLAN is performed on 2. After receiving the request message, the switch 1 or 2 copies the multicast data in the multicast VLAN to the corresponding user VLAN. The multicast data is forwarded to the user equipment through the TRILL network.
  • This cross-VLAN multicast implementation has many drawbacks, including:
  • the multicast request packet sent by the user will flood the entire TRILL network. If there are many multicast request packets sent by the user equipment, the TRILL network will have a large impact, which may cause network congestion and switch 1 at the same time. And 2 will also have a certain impact;
  • switches 1 and 2 when switches 1 and 2 perform multicast data cross-VLAN replication, they will copy one copy to each user VLAN for on-demand, so that multiple copies of the same multicast data will be transmitted in the TRILL network, which is a very A large waste, and if multicast server 1 and multicast server 2 send the same multicast data, the user may receive duplicate multicast traffic, causing an on-demand exception;
  • the TRILL network only supports data forwarding based on Layer 2 VLANs, and must rely on switches connected to the multicast source for multicast cross-VLAN replication, which increases network construction costs;
  • the binding between the multicast VLAN and the user VLAN needs to be performed on multiple switches connected to different multicast sources, which increases configuration complexity and dispersion, and is not conducive to management. maintain.
  • the embodiment of the invention provides a method, a device and a system for transmitting multicast data in a TRILL network, which solves the problem that the TRILL network itself cannot perform cross-VLAN multicast replication, and can implement centralized management of cross-VLAN multicast of the TRILL network, and can Avoid bandwidth waste and simplify networking configuration.
  • the embodiment of the present invention provides the following technical solutions:
  • a method of transmitting multicast data in a multi-link transparent interconnect (TRILL) network comprising: a multicast access RBridge (SRB) receiving a group in a first virtual local area network (VLAN) The multicast data sent by the broadcast server; the SRB sends the description information of the multicast data and the address information of the SRB to a multicast management RBridge (MRB); the SRB receives the user access route sent by the MRB The address information of the bridge (URB), wherein the URB is connected to the user equipment that requests the multicast data, and the user equipment is in the second VLAN; the SRB sends the multicast according to the address information of the URB. data.
  • SRB multicast access RBridge
  • VLAN virtual local area network
  • the description information of the multicast data includes at least one of the following: a multicast IP address of the multicast server, a source IP address, a port that receives the multicast data, and VLAN information.
  • a method for transmitting multicast data in a multi-link transparent interconnect (TRILL) network comprising: a user access RBB (URB) receiving a multicast request sent by a user equipment in a second virtual local area network (VLAN) Transmitting, by the URB, the description information of the multicast request and the address information of the SRB to a multicast management RBridge (MRB); the URB receiving address information of a multicast source RBridge (SRB) sent by the MRB
  • the SRB is connected to a multicast server that sends the multicast data requested by the user equipment, and the multicast server is in a first VLAN; the URB obtains multicast data according to the address information of the SRB; The URB sends the multicast data to the user equipment.
  • the description information of the multicast request includes at least one of the following: a multicast IP address requested by the user, a port that receives the multicast request, and a VLAN.
  • the URB sends the multicast data to the user equipment, where the URB replaces the label of the first VLAN of the multicast data with the label of the second VLAN, and the label is replaced.
  • the multicast data is sent to the user equipment,
  • a method for transmitting multicast data in a multi-link transparent interconnect (TRILL) network comprising: a multicast management RBridge (MRB) detecting that a user access RB (URB) receives a user equipment transmission After the multicast request and the multicast source RB (SRB) receive the multicast data sent by the multicast server, determine whether the multicast data is forwarded to the user equipment, where the user equipment and the multicast server In the different virtual local area network (VLAN); if yes, the MRB sends the address information of the SRB to the URB, notifies the URB to receive the multicast data, and sends the address information of the URB to the SRB to notify the SRB to The URB sends the multicast data.
  • MRB multicast management RBridge
  • URB user access RB
  • SRB multicast source RB
  • the MRB sends a multicast request by determining whether the URB is received. Determining whether the URB receives the multicast request sent by the user equipment, and/or the MRB determines whether the SRB receives the message including the description information of the multicast data by determining whether the SRB receives the message including the description information of the multicast data. Multicast data sent to the multicast server.
  • the method further includes: the MRB sending an advertisement message to all other RBs, where the advertisement message is a message carrying the address information of the MRB.
  • the determining, by the MRB, whether the multicast data is forwarded to the user equipment further includes: the MRB receiving the description information of the at least two multicast data, and determining the at least two multicast data. Whether the multicast IP addresses are the same; if they are the same, one of the multicast data is selected as the data sent to the user equipment; if different, the multicast data is determined according to the multicast IP address requested by the user equipment.
  • a method for transmitting multicast data in a multi-link transparent interconnect (TRILL) network wherein the network includes a plurality of routing bridges (RBs), the plurality of routing bridges including user access RBs (URBs), groups The source access RB (SRB) and the multicast management RB (MRB), the method includes: the URB receiving a multicast request sent by the user equipment; and the SRB receiving the multicast data sent by the multicast server; After detecting that the URB receives the multicast request and the SRB receives the multicast data, it determines whether the multicast data is forwarded to the user equipment, and if yes, sends the SRB address information to the URB to the SRB.
  • TRILL multi-link transparent interconnect
  • the SRB sends the URB request to the URB Multicast data; the URB receives the multicast data according to the address information of the SRB, and sends the multicast data to the user equipment.
  • VLANs virtual local area networks
  • An apparatus for transmitting multicast data in a multi-link transparent interconnect (TRILL) network comprising: a first receiving module configured to receive multicast data sent by a multicast server in a first virtual local area network (VLAN)
  • the first sending module is configured to send the description information of the multicast data and the address information of the SRB to a multicast management RBridge (MRB), and the second receiving module is configured to receive the user access sent by the MRB
  • the address information of the RBB wherein the URB is connected to the user equipment that requests the multicast data, and the user equipment is in the second VLAN; and the second sending module is configured to be based on the address information of the URB. Send the multicast data.
  • the description information of the multicast data includes at least one of: a multicast IP address of the multicast server, a source IP address, a port that receives the multicast data, and VLAN information.
  • An apparatus for transmitting multicast data in a multi-link transparent interconnect (TRILL) network comprising: a third receiving module, configured to receive a multicast request sent by a user equipment in a second virtual local area network (VLAN);
  • the third sending module is configured to send the description information of the multicast request and the address information of the SRB to a multicast management RBridge (MRB), and the fourth receiving module is configured to receive the multicast source route sent by the MRB Address information of a bridge (SRB), wherein the SRB is connected to a multicast server that sends multicast data requested by the user equipment, and the multicast server is in a first VLAN; and an obtaining module is set according to the SRB
  • the address information is obtained by acquiring the multicast data
  • the fourth sending module is configured to send the multicast data to the user equipment.
  • the description information of the multicast request includes at least one of the following: a multicast IP address requested by the user, a port that receives the multicast request, and a VLAN.
  • the fourth sending module includes:
  • a replacement unit configured to replace the label of the first VLAN of the multicast data with the label of the second VLAN
  • the sending unit is configured to send the multicast data after the label replacement is completed to the user equipment.
  • An apparatus for transmitting multicast data in a multi-link transparent interconnect (TRILL) network comprising: a determining module configured to receive a multicast request sent by a user equipment after detecting that a user access RB (URB) is received After the multicast source RB (SRB) receives the multicast data sent by the multicast server, it determines whether the multicast data is forwarded to the user equipment, where the user equipment is different from the multicast server.
  • a determining module configured to receive a multicast request sent by a user equipment after detecting that a user access RB (URB) is received
  • SRB multicast source RB
  • a fifth sending module configured to: if the multicast data is forwarded to the user equipment, send the address information of the SRB to the URB, notify the URB to receive the multicast data, and, to the SRB Sending the address information of the URB, and notifying the SRB to send the multicast data to the URB.
  • VLAN local area network
  • the determining module is configured to determine whether the URB receives the multicast request sent by the user equipment by determining whether the URB sends the packet that includes the description information of the multicast request, and/or, by determining Whether the SRB receives the message including the description information of the multicast data to determine whether the SRB receives the multicast data sent by the multicast server.
  • the device further includes: a sixth sending module, configured to send an advertisement message to all other RBs, where the advertisement message is a packet carrying the address information of the MRB.
  • a sixth sending module configured to send an advertisement message to all other RBs, where the advertisement message is a packet carrying the address information of the MRB.
  • the device further includes: a determining unit, configured to: after receiving the description information of the at least two multicast data, determine whether the multicast IP addresses of the at least two multicast data are the same; and the processing unit is configured to If the multicast IP addresses of the at least two multicast data are the same, one of the multicast data is selected as the data sent to the user equipment; if the multicast IP addresses of the at least two multicast data are different, according to the user The multicast IP address requested by the device determines the distribution of multicast data.
  • a determining unit configured to: after receiving the description information of the at least two multicast data, determine whether the multicast IP addresses of the at least two multicast data are the same; and the processing unit is configured to If the multicast IP addresses of the at least two multicast data are the same, one of the multicast data is selected as the data sent to the user equipment; if the multicast IP addresses of the at least two multicast data are different, according to the user The multicast IP address requested by the device determines the distribution of multicast data.
  • a system for transmitting multicast data in a multi-link transparent interconnect (TRILL) network comprising a plurality of routing bridges (RBs), the plurality of routing bridges including a multicast source access RB (SRB), a user Access RB (URB) and Multicast Management RB (MRB).
  • TRILL multi-link transparent interconnect
  • RBs routing bridges
  • SRB multicast source access RB
  • URB user Access RB
  • MRB Multicast Management RB
  • the MRB determines whether the multicast data received by the SRB is sent to the user equipment, notifies the SRB to send to the URB, and solves the problem that the TRILL network itself cannot perform cross-VLAN multicast replication, and can implement cross-VLAN multicast of the TRILL network. Centralized management and avoiding wasted bandwidth and simplifying network configuration.
  • FIG. 1 is a schematic diagram of a networking for implementing cross-VLAN multicast on a TRILL network in the related art
  • FIG. 2 is a schematic diagram of networking for implementing inter-VLAN multicast in a TRILL network according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of interaction of a method for transmitting multicast data in a TRILL network according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of another method for transmitting multicast data in a TRILL network according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart diagram of still another method for transmitting multicast data in a TRILL network according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of still another method for transmitting multicast data in a TRILL network according to an embodiment of the present disclosure
  • FIG. 7 is an LSP message sent by an MRB to other RBs in the method according to the embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a format of a multicast interactive LSP packet TLV sent by the SRB to the MRB in the method according to the embodiment of the present invention
  • FIG. 9 is a schematic diagram of a format of a multicast interactive LSP packet TLV sent by a URB to an MRB according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a format of a multicast interactive LSP packet TLV sent by an MRB to an SRB according to the method in the embodiment of the present invention
  • FIG. 11 is a schematic diagram of a format of a multicast interactive LSP packet TLV sent by an MRB to a URB according to an embodiment of the present disclosure
  • FIG. 12 is a schematic structural diagram of an apparatus for transmitting multicast data in a TRILL network according to an embodiment of the present disclosure
  • FIG. 13 is a schematic structural diagram of another apparatus for transmitting multicast data in a TRILL network according to an embodiment of the present disclosure
  • FIG. 14 is a schematic structural diagram of another apparatus for transmitting multicast data in a TRILL network according to an embodiment of the present invention.
  • the RBs in the TRILL network provided by the embodiments of the present invention are divided into four roles, including:
  • the management RB is selected from all the RBs that constitute the TRILL network, and is responsible for the centralized management of the on-demand and multicast data distribution of the multicast service by the user equipment.
  • the multicast source accesses the RB (Source RB, SRB) and connects to the TRILL network edge RB of the multicast server, and is responsible for receiving and transmitting multicast data under the management of the MRB.
  • the user equipment accesses the RB (User RB, URB), and is responsible for receiving the user request under the management of the MRB, and forwarding the received multicast data to the user VLAN;
  • a normal RB in a TRILL network is all RBs except MRB, SRB, and URB.
  • FIG. 2 is a schematic diagram of networking for implementing inter-VLAN multicast in a TRILL network according to an embodiment of the present invention.
  • the difference between the networking diagram shown in Figure 2 and that shown in Figure 1 is that the multicast servers 1 and 2 are directly connected to RB1 and RB2 in the TRILL network, and the intermediate connected switch devices are removed. Because the method in the embodiment of the present invention does not need to implement cross-VLAN multicast through a switch, the multicast VLAN that transmits the multicast data sent by the multicast server can directly access the TRILL network RB device.
  • RB4 is selected as the multicast management RB, that is, its role is MRB; RB1 and RB2 are directly connected to the multicast server, and receive multicast data, that is, its role is SRB; RB5 and RB6 are directly connected to the user equipment, that is, The role is URB.
  • FIG. 3 is a schematic diagram of interaction of a method for transmitting multicast data in a TRILL network according to an embodiment of the present invention.
  • the network includes a plurality of RBs, and the plurality of RBs include a URB, an SRB, and an MRB, where:
  • Step 301 The URB receives a multicast request sent by the user equipment.
  • Step 302 The SRB receives multicast data sent by a multicast server.
  • Step 303 After detecting that the URB receives the multicast request and the SRB receives the multicast data, the MRB determines whether the multicast data is forwarded to the user equipment, where the user equipment is in the same manner as the multicast server. Different VLANs;
  • Step 304 The MRB sends the address information of the SRB to the URB.
  • Step 305 The MRB sends the address information of the URB to the SRB.
  • Step 306 After obtaining the address information of the URB, the SRB sends the URB information to the URB.
  • Step 307 The URB receives the multicast data according to the address information of the SRB, and sends the multicast data to the user equipment.
  • the MRB determines whether the multicast data received by the SRB is sent to the user equipment, notifies the SRB to send to the URB, and solves the problem that the TRILL network itself cannot perform cross-VLAN multicast replication, and can implement the TRILL network cross-VLAN group. Centralized management of broadcasts, avoiding wasted bandwidth and simplifying network configuration.
  • MRB Multicast management RB
  • the MRB is responsible for centralized management of the multicast data received by the multicast server access RB and the multicast request message received by the multicast user access RB.
  • the MRB sends an advertised message to all other RBs, and the advertised message is an LSP message carrying the address information of the MRB.
  • the announcement message After all other RBs receive the announcement message, they calculate and record the forwarding path to the MRB.
  • the RB in the TRILL network When the RB in the TRILL network receives the multicast request packet sent by the user equipment, the RB role automatically becomes the user access RB (User RB, URB) connected to the multicast user equipment, and then the URB establishes the user locally.
  • the information entry the entry records the multicast IP address requested by the user, the port receiving the multicast request, the VLAN, and the like, and then the URB sends the multicast carrying the multicast request message and the URB address information to the MRB. Interworking LSP packets.
  • the RB role automatically becomes the multicast source access RB (Source RB, SRB) connected to the multicast server, and then the SRB establishes the multicast source information entry locally.
  • the entry records the multicast IP address of the multicast server, the source IP address, the port that receives the multicast data, the VLAN, and the like, and then the SRB sends the group that carries the multicast source information and the address information of the SRB to the MRB. Broadcast interactive LSP packets.
  • the RBs in the TRILL network can simultaneously become one or more roles in the MRB, URB, or SRB.
  • the binding information of the multicast VLAN and the user VLAN is received on the MRB.
  • the multicast data is determined according to the multicast VLAN and the user VLAN binding information.
  • User equipment forwarding. If the MRB receives the multicast inter-LSPs sent by different SRBs, but the multicast IP addresses carried in the packets are the same (that is, the same multicast data is received by different SRBs), the MRBs are pre-configured or specific.
  • the election rule determines which multicast data received by the SRB is forwarded to the user equipment.
  • the MRB sends a multicast interactive LSP message carrying the information such as the URB address and the multicast IP address of the user equipment to the SRB.
  • the MRB sends a Label Switched Path (LSP) packet carrying the information such as the SRB address, the multicast IP address, and the multicast VLAN of the multicast source to the URB;
  • LSP Label Switched Path
  • the SRB After receiving the multicast interactive LSP message sent by the MRB, the SRB receives the LSP packet according to the LSP packet.
  • the carrying information adds the URB address information of the user equipment to the corresponding multicast source information table, calculates a multicast distribution tree, and then sends the multicast data to the URB according to the TRILL multicast distribution tree.
  • the URB After receiving the multicast interactive LSP message sent by the MRB, the URB adds the URB address information and the multicast VLAN information to the corresponding user information table according to the LSP packet carrying information, and the URB receives the secondary multicast VLAN.
  • the multicast data sent is replaced with the multicast VLAN tag of the multicast data and then forwarded to the corresponding multicast user port.
  • the method provided by the embodiment of the present invention provides centralized management of cross-VLAN multicast of all multicast sources and multicast users by selecting one RB in the TRILL network as the multicast management RB, and the multicast data can be
  • the multicast distribution tree of the TRILL network is sent to the multicast user to access the RB in the multicast VLAN. After the user accesses the RB, the multicast VLAN tag is switched to the user VLAN tag and then sent to the multicast user equipment.
  • the embodiment of the present invention implements cross-VLAN multicast in a TRILL network, and the multicast server can directly access the TRILL network without first connecting the multicast server to the switch supporting cross-VLAN multicast. Enter the TRILL network.
  • cross-VLAN multicast unified management can be realized, and the utilization of TRILL network resources is maximized.
  • FIG. 4 is a schematic flowchart diagram of another method for transmitting multicast data in a TRILL network according to an embodiment of the present invention.
  • the method shown in Figure 4 includes:
  • Step 401 The SRB receives the multicast data sent by the multicast server in the first VLAN.
  • Step 402 The SRB sends the description information of the multicast data and the address information of the SRB to the MRB.
  • Step 403 The SRB receives the address information of the URB sent by the MRB, where the URB is connected to the user equipment that requests the multicast data, and the user equipment is in the second VLAN.
  • Step 404 The SRB sends the multicast data according to the address information of the URB.
  • the description information of the multicast data includes at least one of the following: a multicast IP address of the multicast server, a source IP address, a port for receiving multicast data, and VLAN information.
  • the SRB after receiving the multicast data, the SRB obtains the address information of the URB through the MRB, so that the user equipments in different VLANs can receive the multicast number.
  • the TRILL network itself cannot solve the problem of cross-VLAN multicast replication, which reduces the number of times of multicast data replication and effectively controls the traffic transmitted on the network.
  • FIG. 5 is a schematic flowchart diagram of still another method for transmitting multicast data in a TRILL network according to an embodiment of the present invention.
  • the method shown in Figure 5 includes:
  • Step 501 The URB receives the multicast request sent by the user equipment in the second VLAN.
  • Step 502 The URB sends the description information of the multicast request and the address information of the SRB to the MRB.
  • Step 503 The URB receives the address information of the SRB sent by the MRB, where the SRB is connected to a multicast server that sends the multicast data requested by the user equipment, and the multicast server is in the first VLAN;
  • Step 504 The URB acquires multicast data according to the address information of the SRB.
  • Step 505 The URB sends the multicast data to the user equipment.
  • the description information of the multicast request includes at least one of the following: a multicast IP address requested by the user, a port that receives the multicast request, and a VLAN.
  • the URB sends the multicast data to the user equipment, including:
  • the URB replaces the label of the first VLAN of the multicast data with the label of the second VLAN, and sends the multicast data after the label replacement is completed to the user equipment.
  • the URB after receiving the multicast request, the URB obtains the address information of the SRB through the MRB, so that the user equipments in different VLANs can receive the multicast data, and the TRILL network itself cannot perform cross-VLAN multicast.
  • the problem of copying reduces the number of times of multicast data replication and effectively controls the traffic transmitted on the network.
  • FIG. 6 is a schematic flowchart diagram of still another method for transmitting multicast data in a TRILL network according to an embodiment of the present invention.
  • the method shown in Figure 6 includes:
  • Step 601 After detecting that the URB receives the multicast request sent by the user equipment, and the SRB receives the multicast data sent by the multicast server, the MRB determines whether the multicast data is forwarded to the user equipment, where the user The device is in a different VLAN from the multicast server;
  • Step 602 If yes, the MRB sends the address information of the SRB to the URB, notifies the URB to receive the multicast data, and sends the address information of the URB to the SRB, and notifies the SRB to send the information to the URB. Multicast data.
  • the MRB determines whether the URB receives the multicast request sent by the user equipment by determining whether the URB sends the packet that includes the description information of the multicast request; and/or, the MRB determines whether Receiving, by the SRB, a message including description information of the multicast data to determine whether the SRB receives the multicast data sent by the multicast server.
  • Both the URB and the SRB send the information reception status to the MRB, which facilitates the data processing of the URB and the SRB by the MRB.
  • the URB and the SRB obtain the MRB address information in the following manner: the MRB sends an advertisement message to all other RBs, where the advertisement message is a packet carrying the address information of the MRB.
  • the MRB determines whether the multicast data is forwarded to the user equipment, and further includes:
  • the MRB receives the description information of the at least two multicast data, and determines whether the multicast IP addresses of the at least two multicast data are the same; if the same, selects one of the multicast data as the data sent to the user equipment. If different, the distribution of multicast data is determined according to the multicast IP address requested by the user equipment.
  • the MR when determining that the multicast data is sent to the user equipment, the MR sends the address information of the SRB to the URB, notifies the URB to receive the multicast data, and sends the multicast data to the SRB.
  • the address information of the URB is sent to the SRB to send the multicast data to the URB, so that the user equipments in different VLANs can receive the multicast data, and the TRILL network itself cannot solve the problem of cross-VLAN multicast replication, and the group is reduced. The number of times the data is copied, effectively controlling the traffic transmitted on the network.
  • the following takes the schematic diagram of the network shown in FIG. 2 as an example to describe the transmission process of the multicast service flow of the user equipment 1 on the multicast server 1.
  • the method of selecting MRB service processing in the TRILL network is as follows:
  • Step A01 After the RB4 is selected as the MRB, the advertised message is sent to all the other RBs, and the advertised message is an LSP message carrying the RB4 address information.
  • Step A02 After all other non-MRBs receive the notification message, calculate and record the forwarding path to the MRB.
  • the method for processing multicast source access services in a TRILL network is as follows:
  • Step B01 After receiving the multicast data sent by the multicast server 1, the RB1 automatically becomes the SRB corner. Color (SRB1), a multicast source information entry is created locally. The entry records the multicast IP address of the multicast server, the port that receives the multicast data, and the VLAN.
  • Step B02 The SRB1 sends a multicast interactive LSP message carrying the multicast source information and the address information of the SRB1 to the MRB.
  • the message format can be seen in Figure 7.
  • Step B03 After receiving the multicast interactive LSP message sent by the SRB1, the MRB determines whether to notify the SRB1 to forward the multicast data to the URB according to the binding information of the multicast VLAN and the user VLAN on the MRB.
  • the first type is that the multicast data sent by the multicast server 1 and the multicast server 2 are different, that is, the multicast IP address is different.
  • the MBR receives the multicast interactive LSP message from SRB1 and SRB2, the multicast IP address is requested by the user equipment. The address determines the distribution of multicast data;
  • the second type is that the multicast data sent by the multicast server 1 and the multicast server 2 are the same, that is, the multicast IP address is the same.
  • the MBR receives the multicast interactive LSP message from SRB1 and SRB2
  • the MBR is pre-configured or specified according to the MRB.
  • the selection rule determines which device in SRB1 and SRB2 forwards multicast data to the URB.
  • the method for implementing user cross-VLAN on-demand multicast service processing in a TRILL network is as follows:
  • Step D01 The user equipment 1 sends a multicast request message to the RB5 in the VLAN 10, and the multicast service of the multicast server 1 is requested.
  • Step D02 After receiving the multicast request of the user equipment, the RB5 automatically becomes the URB role (URB1), and establishes a user information entry locally, where the entry records the multicast IP address requested by the user, and the port and VLAN that receives the multicast request.
  • the information is sent to the MRB to send the multicast interactive LSP message carrying the multicast request message information and the URB1 address information.
  • Step D03 After receiving the multicast interactive LSP message sent by the URB1, the MRB determines whether the multicast data is forwarded to the user equipment according to the multicast VLAN and the user VLAN binding information.
  • Step D04 If the multicast data of the SRB1 is allowed to be forwarded to the user equipment, the MRB sends a multicast interactive LSP message carrying the information such as the URB1 address and the multicast IP address to the SRB1.
  • the message format can be seen in Figure 9.
  • the MRB sends a multicast interactive LSP message to the URB1, such as the SRB1 address, the multicast IP address, and the multicast VLAN.
  • Step D05 After receiving the multicast interactive LSP message sent by the MRB, the SRB1 adds the URB1 address information of the user equipment to the corresponding multicast source information table according to the LSP packet carrying information, and starts to use the TRILL multicast distribution tree. Send multicast data to URB1.
  • Step D06 After receiving the multicast interactive LSP message sent by the MRB, the URB1 adds the URB1 address information and the multicast VLAN information to the corresponding user information table according to the LSP packet carrying information.
  • Step D07 After receiving the multicast data sent by the SRB1, the URB1 replaces the VLAN 100 tag of the multicast data with the VLAN 10 tag, and then sends the packet to the user equipment 1.
  • the user equipment 1 receives the multicast data, and completes the cross-VLAN on-demand broadcast of the multicast service of the multicast server 1.
  • FIG. 7 is a schematic diagram of a TLV format of an advertisement LSP message sent by an MRB to other RBs in the method according to the embodiment of the present invention.
  • the Type field represents the LSP message type, here is the Management RB Announcement, the length is 1 byte; the Length field represents the length of the Value field, which occupies 1 byte; the Value field is filled with the nickname of the MRB, etc., and can be expanded as needed.
  • FIG. 8 is a schematic diagram of a format of a multicast interactive LSP packet TLV sent by an SRB to an MRB according to an embodiment of the present invention, where a Type field represents an LSP message type, where is a Source RB Report, and a length is 1 byte; and a Length field represents a Value field. The length is 1 byte; the Value field is filled with the nickname of the SRB, the Multicast Server IP Address, the Multicast VLAN ID, and the Multicast IP Address. Expand as needed.
  • FIG. 9 is a schematic diagram of a format of a multicast interactive LSP packet TLV sent by a URB to an MRB according to an embodiment of the present invention, where a Type field represents an LSP message type, where is a User RB Report, and a length is 1 byte; and a Length field represents a Value field. The length of the value is 1 byte.
  • the value field is filled with the nickname of the URB, the User RB Report Type (the URB report type, which has two types, Join and Leave, which means user join and user leave), User VLAN ID (User VLAN ID), and Multicast IP Address, etc., can also be expanded as needed.
  • a Type field represents an LSP message type, where is a Reply to Source RB, length is 1 byte; Length field represents the length of the Value field, occupying 1 byte; Value field is filled with URB nickname, Reply Type (MRB Reply type, there are two types of Start and Stop, respectively, representing multicast data traffic starts to send And stop sending), Multicast Server IP Address and Multicast VLAN ID, etc., can also be expanded as needed.
  • a Type field represents an LSP message type, where is a Reply to Source RB, length is 1 byte; Length field represents the length of the Value field, occupying 1 byte; Value field is filled with URB nickname, Reply Type (MRB Reply type, there are two types of Start and Stop, respectively, representing multicast data traffic starts to send And stop sending), Multicast Server IP Address and Multicast VLAN ID, etc., can also be expanded as needed.
  • FIG. 11 is a schematic diagram of a format of a multicast interactive LSP packet TLV sent by an MRB to a URB according to the method in the embodiment of the present invention, where the Type field represents an LSP message type, where is a Reply to User RB, and the length is 1 byte; the Length field represents a Value. The length of the field occupies 1 byte; the Value field is filled with the nickname of the SRB, the multicast VLAN ID, the multicast server IP address, and the multicast IP address. Can be expanded as needed.
  • the above format can be used to transmit information in a simple and efficient manner using the format of the message.
  • FIG. 12 is a schematic structural diagram of an apparatus for transmitting multicast data in a TRILL network according to an embodiment of the present invention.
  • the device shown in Figure 12 includes:
  • the first receiving module 1201 is configured to receive multicast data sent by a multicast server in a first virtual local area network (VLAN);
  • VLAN virtual local area network
  • the first sending module 1202 is configured to send the description information of the multicast data and the address information of the SRB to a multicast management RBridge (MRB);
  • MRB multicast management RBridge
  • the second receiving module 1203 is configured to receive address information of a user access RB (URB) sent by the MRB, where the URB is connected to a user equipment that requests the multicast data, and the user equipment is in the second VLAN;
  • URB user access RB
  • the second sending module 1204 is configured to send the multicast data according to the address information of the URB.
  • the description information of the multicast data includes at least one of the following: a multicast IP address of the multicast server, a source IP address, a port for receiving multicast data, and VLAN information.
  • the device provided by the present invention obtains the address information of the URB through the MRB after receiving the multicast data, so that the user equipments in different VLANs can receive the multicast data, and the TRILL network itself cannot perform the cross-VLAN multicast replication.
  • the problem is to reduce the number of times of multicast data replication and effectively control the traffic transmitted on the network.
  • FIG. 13 is a schematic structural diagram of another apparatus for transmitting multicast data in a TRILL network according to an embodiment of the present invention.
  • the device shown in Figure 13 includes:
  • the third receiving module 1301 is configured to receive a multicast request sent by the user equipment in the second VLAN.
  • the third sending module 1302 is configured to send, to the MRB, description information of the multicast request and address information of the SRB;
  • the fourth receiving module 1303 is configured to receive the address information of the SRB sent by the MRB, where the SRB is connected to a multicast server that sends the multicast data requested by the user equipment, and the multicast server is in the first VLAN. ;
  • the obtaining module 1304 is configured to acquire multicast data according to the address information of the SRB.
  • the fourth sending module 1305 is configured to send the multicast data to the user equipment.
  • the description information of the multicast request includes at least one of the following: a multicast IP address requested by the user, a port that receives the multicast request, and a VLAN.
  • the fourth sending module includes:
  • a replacement unit configured to replace the label of the first VLAN of the multicast data with the label of the second VLAN
  • the sending unit is configured to send the multicast data after the label replacement is completed to the user equipment.
  • the URB after receiving the multicast request, the URB obtains the address information of the SRB through the MRB, so that the user equipments in different VLANs can receive the multicast data, and the TRILL network itself cannot perform cross-VLAN multicast.
  • the problem of copying reduces the number of times of multicast data replication and effectively controls the traffic transmitted on the network.
  • FIG. 14 is a schematic structural diagram of another apparatus for transmitting multicast data in a TRILL network according to an embodiment of the present invention.
  • the device shown in Figure 14 includes:
  • the determining module 1401 is configured to: after detecting that the user access RB (URB) receives the multicast request sent by the user equipment and the multicast source RB (SRB) receives the multicast data sent by the multicast server, determine the location Whether the multicast data is forwarded to the user equipment, where the user equipment and the multicast server are in different virtual local area networks (VLANs);
  • URB user access RB
  • SRB multicast source RB
  • the fifth sending module 1402 is configured to: if the multicast data is forwarded to the user equipment, send the address information of the SRB to the URB, notify the URB to receive the multicast data, and, Sending the address information of the URB to the SRB, and notifying the SRB to send the multicast data to the URB.
  • the determining module 1401 is configured to determine whether the URB receives the multicast request sent by the user equipment by determining whether the URB sends the packet including the description information of the multicast request, and/or, by determining whether to receive the multicast request. Sending a message including the description information of the multicast data to the SRB to determine whether the SRB receives the multicast data sent by the multicast server.
  • the device further includes:
  • the sixth sending module is configured to send an advertisement message to all other RBs, where the advertisement message is a packet carrying the address information of the MRB.
  • the device further includes:
  • the determining unit is configured to: after receiving the description information of the at least two multicast data, determine whether the multicast IP addresses of the at least two multicast data are the same;
  • a processing unit configured to: if the multicast IP addresses of the at least two multicast data are the same, select one of the multicast data as the data sent to the user equipment; if the multicast IP address of the at least two multicast data Differently, the distribution of multicast data is determined according to the multicast IP address requested by the user equipment.
  • the MR when determining that the multicast data is sent to the user equipment, the MR sends the address information of the SRB to the URB, notifies the URB to receive the multicast data, and sends the multicast data to the SRB.
  • the address information of the URB is sent to the SRB to send the multicast data to the URB, so that the user equipments in different VLANs can receive the multicast data, and the TRILL network itself cannot solve the problem of cross-VLAN multicast replication, and the group is reduced. The number of times the data is copied, effectively controlling the traffic transmitted on the network.
  • an embodiment of the present invention further provides a system for transmitting multicast data in a TRILL network, where the network includes multiple routing bridges (RBs), and the multiple routing bridges include user access RBs (URBs) and multicasts.
  • RBs multiple routing bridges
  • URBs user access RBs
  • MRB Multicast Management RB
  • the SRB includes the device shown in Figure 12;
  • the URB includes the device shown in Figure 13;
  • the MRB includes the device shown in FIG.
  • the system provided by the embodiment of the present invention performs centralized management of cross-VLAN multicast of all multicast sources and multicast users by selecting one RB in the TRILL network as a multicast management RB, and the multicast data can directly pass through the TRILL network group.
  • the broadcast distribution tree is sent to the multicast user to access the RB in the multicast VLAN, and is sent to the multicast user equipment after the user accesses the RB to complete the switching of the multicast VLAN tag to the user VLAN tag.
  • the embodiment of the present invention implements cross-VLAN multicast in a TRILL network, and the multicast server can directly access the TRILL network without first connecting the multicast server to the switch supporting cross-VLAN multicast. Enter the TRILL network.
  • cross-VLAN multicast unified management can be realized, and the utilization of TRILL network resources is maximized.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.
  • Each of the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • Each device/function module/functional unit in the above embodiments may be stored in a computer readable storage medium when implemented in the form of a software function module and sold or used as a standalone product.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the MRB determines whether the multicast data received by the SRB is sent to the user equipment, notifies the SRB to send to the URB, and solves the problem that the TRILL network itself cannot perform cross-VLAN multicast replication, and can implement cross-VLAN multicast of the TRILL network. Centralized management and avoiding wasted bandwidth and simplifying network configuration.

Abstract

一种在多链路透明互联(TRILL)网络中传输组播数据的方法、装置和系统,其中所述方法包括:组播接入路由桥(SRB)接收处于第一虚拟局域网(VLAN)的组播服务器发送的组播数据(401);所述SRB向组播管理路由桥(MRB)发送所述组播数据的描述信息和所述SRB的地址信息(402);所述SRB接收所述MRB发送的用户接入路由桥(URB)的地址信息,其中所述URB与请求所述组播数据的用户设备相连,且所述用户设备处于第二VLAN(403);所述SRB根据所述URB的地址信息,发送所述组播数据(404)。

Description

在TRILL网络中传输组播数据的方法、装置和系统 技术领域
本发明涉及通讯领域,尤其涉及一种在TRILL网络中传输组播数据的方法、装置和系统。
背景技术
TRILL(Transparent Interconnection of lots of links,多链路透明互联)是IETF(Internet Engineering Task Force,互联网工程任务组)为实现数据中心大二层扩展制定的一个标准,它将应用于IP(Internet Protocol,网络互连协议)转发的思路应用到以太帧转发,通过拓展IS-IS协议(Intermediate System to Intermediate System Routing Protocol,中间系统到中间系统路由协议)实现二层路由,运行TRILL协议的以太网交换机被称为路由桥(Rrouting Bridge,RB),多台RB组成的网络集合称为TRILL网络。TRILL网络中每台设备都以自身节点作为源节点,基于最短路径算法计算到达其他所有节点的最短路径,如果存在多条等价链路,能够进行负载分担。这样能够保障数据中心网络的转发效率,规避STP/MSTP(Spanning Tree Protocol,生成树协议)/(Multi-Service Transfer Platform,基于SDH的多业务传送平台)等技术的缺陷。
伴随着下一代数据中心的不断发展,TRILL技术逐渐成为数据中心网络性能提高的基础性技术,TRILL网络对各种业务支持的需求也日益迫切,跨VLAN(Virtual Local Area Network,虚拟局域网)的组播就其中之一。由于TRILL网络是根据二层VLAN做为组播树的转发路径,组播用户和组播源必须处于相同VLAN才能接收组播流量,这样对跨VLAN的组播的实施造成了一定的难度。
图1为相关技术中在TRILL网络上实现跨VLAN组播的组网的示意图。RB1~RB7组成TRILL网络,RB1和RB2分别连接交换机1和交换机2,交换机1和交换机2分别连接组播服务器1和组播服务器2,以代表TRILL网络上分布于异地的不同组播源,RB5~RB7分别下挂用户设备1~3。组播服务 器1和组播服务器2提供不同的组播数据内容,并由交换机1和交换机2分别负责向用户设备进行跨VLAN的组播转发。当用户设备需要点播组播服务器1或2提供的组播业务内容时,用户设备发出的组播加入请求报文需要经过TRILL网络转发到与TRILL网络直连的交换机1或2,在交换机1和2上进行了组播VLAN和用户VLAN关系的绑定。交换机1或2收到用户加入请求报文后,将组播VLAN中的组播数据向相应的用户VLAN复制一份,组播数据再通过TRILL网络向用户设备转发。
这种跨VLAN组播的实现方式有很多弊端,包括:
首先,用户发送的组播请求报文会在整个TRILL网络泛洪,如果用户设备发送的组播请求报文较多,会对TRILL网络形成较大的冲击,可能造成网络拥塞,同时对交换机1和2也会有一定的冲击;
其次,交换机1和2进行组播数据跨VLAN复制时会向每个点播的用户VLAN复制一份,这样同时会有多份相同的组播数据在TRILL网络中传输,对网络资源是一种很大的浪费,而且如果组播服务器1和组播服务器2发送的是相同组播数据,用户可能会收到双份重复的组播流量,造成点播异常;
再其次,TRILL网络只支持基于二层VLAN的数据转发,必须依靠连接组播源的交换机进行组播跨VLAN复制,增加了网络建设成本;
最后,对于分布于异地的多个组播源,需要在连接不同组播源的多个交换机上分别进行组播VLAN和用户VLAN关系的绑定,增加了配置复杂度和分散性,不利于管理维护。
发明内容
本发明实施例提供一种在TRILL网络中传输组播数据的方法、装置和系统,解决TRILL网络本身不能进行跨VLAN组播复制的问题,能够实现TRILL网络跨VLAN组播的集中管理,并能避免带宽浪费,简化组网配置。
为解决上述技术问题,本发明实施例提供了如下技术方案:
一种在多链路透明互联(TRILL)网络中传输组播数据的方法,所述方法包括:组播接入路由桥(SRB)接收处于第一虚拟局域网(VLAN)的组 播服务器发送的组播数据;所述SRB向组播管理路由桥(MRB)发送所述组播数据的描述信息和所述SRB的地址信息;所述SRB接收所述MRB发送的用户接入路由桥(URB)的地址信息,其中所述URB与请求所述组播数据的用户设备相连,且所述用户设备处于第二VLAN;所述SRB根据所述URB的地址信息,发送所述组播数据。
可选地,所述组播数据的描述信息包括如下至少一个:组播服务器的组播IP地址、源IP地址、接收组播数据的端口、VLAN信息。
一种在多链路透明互联(TRILL)网络中传输组播数据的方法,所述方法包括:用户接入路由桥(URB)接收处于第二虚拟局域网(VLAN)的用户设备发送的组播请求;所述URB向组播管理路由桥(MRB)发送所述组播请求的描述信息和所述SRB的地址信息;所述URB接收所述MRB发送的组播源路由桥(SRB)的地址信息,其中所述SRB与发送所述用户设备请求的组播数据的组播服务器相连,且所述组播服务器处于第一VLAN;所述URB根据所述SRB的地址信息,获取组播数据;所述URB将所述组播数据发送给所述用户设备。
可选地,所述组播请求的描述信息包括如下至少一个:用户请求的组播IP地址、接收组播请求的端口和VLAN。
可选地,所述URB将所述组播数据发送给所述用户设备,包括:所述URB将所述组播数据的第一VLAN的标签替换为第二VLAN的标签,将完成标签替换后的组播数据发送至所述用户设备,
一种在多链路透明互联(TRILL)网络中传输组播数据的方法,所述方法包括:组播管理路由桥(MRB)在检测到用户接入路由桥(URB)接收到用户设备发送的组播请求以及组播源路由桥(SRB)接收到组播服务器发送给的组播数据后,判断所述组播数据是否向所述用户设备转发,其中所述用户设备与所述组播服务器处于不同虚拟局域网(VLAN);如果是,则所述MRB向URB发送所述SRB的地址信息,通知URB接收所述组播数据,以及,向SRB发送所述URB的地址信息,通知SRB向所述URB发送所述组播数据。
可选地,所述MRB通过判断是否接收到所述URB发送包括组播请求的 描述信息的报文来确定URB是否接收到用户设备发送的组播请求;和/或,所述MRB通过判断是否接收到所述SRB发送包括组播数据的描述信息的报文来确定SRB是否接收到组播服务器发送的组播数据。
可选地,所述方法还包括:所述MRB向其他所有RB发送通告消息,通告消息为携带所述MRB的地址信息的报文。
可选地,所述MRB判断所述组播数据是否向所述用户设备转发,还包括:所述MRB在接收到至少两个组播数据的描述信息,判断所述至少两个组播数据的组播IP地址是否相同;如果相同,则选择其中一个组播数据作为发送给用户设备的数据;如果不同,则根据用户设备请求的组播IP地址决定组播数据的分发。
一种在多链路透明互联(TRILL)网络中传输组播数据的方法,其中,所述网络包括多个路由桥(RB),所述多个路由桥包括用户接入RB(URB)、组播源接入RB(SRB)以及组播管理RB(MRB),所述方法包括:所述URB接收所述用户设备发送的组播请求;所述SRB接收组播服务器发送的组播数据;所述MRB在检测到URB接收到组播请求以及SRB接收到组播数据后,判断所述组播数据是否向所述用户设备转发,如果是,则向URB发送所述SRB的地址信息,向SRB发送所述URB的地址信息;其中所述用户设备与所述组播服务器处于不同虚拟局域网(VLAN);所述SRB在得到所述URB的地址信息后,向所述URB发送所述URB请求的组播数据;所述URB根据所述SRB的地址信息,接收所述组播数据,并向所述用户设备发送所述组播数据。
一种在多链路透明互联(TRILL)网络中传输组播数据的装置,所述装置包括:第一接收模块,设置为接收处于第一虚拟局域网(VLAN)的组播服务器发送的组播数据;第一发送模块,设置为向组播管理路由桥(MRB)发送所述组播数据的描述信息和所述SRB的地址信息;第二接收模块,设置为接收所述MRB发送的用户接入路由桥(URB)的地址信息,其中所述URB与请求所述组播数据的用户设备相连,且所述用户设备处于第二VLAN;第二发送模块,设置为根据所述URB的地址信息,发送所述组播数据。
可选地,所述组播数据的描述信息包括如下至少一个:组播服务器的组播IP地址、源IP地址、接收组播数据的端口和VLAN信息。
一种在多链路透明互联(TRILL)网络中传输组播数据的装置,所述装置包括:第三接收模块,设置为接收处于第二虚拟局域网(VLAN)的用户设备发送的组播请求;第三发送模块,设置为向组播管理路由桥(MRB)发送所述组播请求的描述信息和所述SRB的地址信息;第四接收模块,设置为接收所述MRB发送的组播源路由桥(SRB)的地址信息,其中所述SRB与发送所述用户设备请求的组播数据的组播服务器相连,且所述组播服务器处于第一VLAN;获取模块,设置为根据所述SRB的地址信息,获取组播数据;第四发送模块,设置为将所述组播数据发送给所述用户设备。
可选地,所述组播请求的描述信息包括如下至少一个:用户请求的组播IP地址、接收组播请求的端口和VLAN。
可选地,所述第四发送模块包括:
替换单元,设置为将所述组播数据的第一VLAN的标签替换为第二VLAN的标签;
发送单元,设置为将完成标签替换后的组播数据发送至所述用户设备。
一种在多链路透明互联(TRILL)网络中传输组播数据的装置,所述装置包括:判断模块,设置为在检测到用户接入路由桥(URB)接收到用户设备发送的组播请求以及组播源路由桥(SRB)接收到组播服务器发送给的组播数据后,判断所述组播数据是否向所述用户设备转发,其中所述用户设备与所述组播服务器处于不同虚拟局域网(VLAN);第五发送模块,设置为如果所述组播数据是向所述用户设备转发,则向URB发送所述SRB的地址信息,通知URB接收所述组播数据,以及,向SRB发送所述URB的地址信息,通知SRB向所述URB发送所述组播数据。
可选地,所述判断模块,设置为通过判断是否接收到所述URB发送包括组播请求的描述信息的报文来确定URB是否接收到用户设备发送的组播请求;和/或,通过判断是否接收到所述SRB发送包括组播数据的描述信息的报文来确定SRB是否接收到组播服务器发送的组播数据。
可选地,所述装置还包括:第六发送模块,设置为向其他所有RB发送通告消息,通告消息为携带所述MRB的地址信息的报文。
可选地,所述装置还包括:判断单元,设置为在接收到至少两个组播数据的描述信息,判断所述至少两个组播数据的组播IP地址是否相同;处理单元,设置为如果所述至少两个组播数据的组播IP地址相同,则选择其中一个组播数据作为发送给用户设备的数据;如果所述至少两个组播数据的组播IP地址不同,则根据用户设备请求的组播IP地址决定组播数据的分发。
一种在多链路透明互联(TRILL)网络中传输组播数据的系统,所述网络包括多个路由桥(RB),所述多个路由桥包括组播源接入RB(SRB)、用户接入RB(URB)以及组播管理RB(MRB)。
本发明提供的实施例,MRB通过判断SRB接收的组播数据是否向用户设备发送,通知SRB向URB发送,解决TRILL网络本身不能进行跨VLAN组播复制的问题,能够实现TRILL网络跨VLAN组播的集中管理,并能避免带宽浪费,简化组网配置。
附图概述
图1为相关技术中在TRILL网络上实现跨VLAN组播的组网的示意图;
图2为本发明实施例提供的在TRILL网络中实现跨VLAN组播的组网示意图;
图3为本发明实施例提供的在TRILL网络中传输组播数据的方法的交互示意图;
图4为本发明实施例提供的另一种在TRILL网络中传输组播数据的方法的流程示意图;
图5为本发明实施例提供的又一种在TRILL网络中传输组播数据的方法的流程示意图。
图6为本发明实施例提供的又一种在TRILL网络中传输组播数据的方法的流程示意图;
图7为本发明实施例所述方法中MRB向其他RB发送的通告LSP报文 TLV格式示意图;
图8为本发明实施例所述方法中SRB向MRB发送的组播交互LSP报文TLV格式示意图;
图9为本发明实施例所述方法中URB向MRB发送的组播交互LSP报文TLV格式示意图;
图10为本发明实施例所述方法中MRB向SRB发送的组播交互LSP报文TLV格式示意图;
图11为本发明实施例提供的MRB向URB发送的组播交互LSP报文TLV格式示意图;
图12为本发明实施例提供的一种在TRILL网络中传输组播数据的装置的结构示意图;
图13为本发明实施例提供的另一种在TRILL网络中传输组播数据的装置的结构示意图;
图14为本发明实施例提供的又一种在TRILL网络中传输组播数据的装置的结构示意图。
本发明的较佳实施方式
下面将结合附图及实施例对本发明实施例作详细描述。需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互任意组合。
本发明实施例提供的TRILL网络中的RB分为4种角色,包括:
组播管理RB(Management RB,MRB),从组成TRILL网络的所有RB中选择出来,负责用户设备对组播业务的点播和组播数据分发的集中管理;
组播源接入RB(Source RB,SRB),连接组播服务器的TRILL网络边缘RB,负责在MRB管理下进行组播数据接收和发送;
用户设备接入RB(User RB,URB),负责在MRB管理下接收用户请求,并将收到的组播数据向用户VLAN转发;
TRILL网络中的普通RB,是除MRB、SRB和URB以外的其他所有RB。
图2为本发明实施例提供的在TRILL网络中实现跨VLAN组播的组网示意图。图2所示的组网示意图与图1所示的区别是组播服务器1和2直接与TRILL网络中的RB1和RB2相连,去除了中间连接的交换机设备。因为本发明实施例所述方法不需要通过交换机来实现跨VLAN组播,传输组播服务器发送的组播数据的组播VLAN可以直接接入TRILL网络RB设备。
在图2中,RB4被选择成为组播管理RB,即其角色为MRB;RB1和RB2直连组播服务器,接收组播数据,即其角色为SRB;RB5和RB6直连用户设备,即其角色为URB。
图3为本发明实施例提供的在TRILL网络中传输组播数据的方法的交互示意图。所述网络包括多个RB,所述多个路由桥包括URB、SRB以及MRB,其中:
步骤301、所述URB接收所述用户设备发送的组播请求;
步骤302、所述SRB接收组播服务器发送的组播数据;
步骤303、所述MRB在检测到URB接收到组播请求以及SRB接收到组播数据后,判断所述组播数据是否向所述用户设备转发,其中所述用户设备与所述组播服务器处于不同VLAN;
如果是,则执行步骤304和305;
步骤304、所述MRB向URB发送所述SRB的地址信息;
步骤305、所述MRB向SRB发送所述URB的地址信息;
步骤306、所述SRB在得到所述URB的地址信息后,向所述URB发送所述URB信息;
步骤307、所述URB根据所述SRB的地址信息,接收所述组播数据,并向所述用户设备发送所述组播数据。
本发明提供的方法实施例,MRB通过判断SRB接收的组播数据是否向用户设备发送,通知SRB向URB发送,解决TRILL网络本身不能进行跨VLAN组播复制的问题,能够实现TRILL网络跨VLAN组播的集中管理,并能避免带宽浪费,简化组网配置。
在图3所示方法中:
在TRILL网络的RB中间选择一个组播管理RB(Management RB, MRB)。所述MRB负责对组播服务器接入RB上接收到的组播数据和组播用户接入RB收到的组播请求报文进行集中管理。所述MRB在所述MRB选择出来以后,向其他所有RB发送通告消息,通告消息为携带所述MRB的地址信息的LSP报文。其他所有RB收到该通告消息后,计算并记录到所述MRB的转发路径。
当TRILL网络中的RB收到用户设备发送的组播请求报文时,所述RB角色自动成为连接组播用户设备的用户接入RB(User RB,URB),之后所述URB在本地建立用户信息表项,表项中记录用户请求的组播IP地址,接收组播请求的端口、VLAN等信息,然后所述URB向MRB发送携带所述组播请求报文信息和URB地址信息的组播交互LSP报文。
当TRILL网络中的RB收到组播数据时,所述RB角色自动成为连接组播服务器的组播源接入RB(Source RB,SRB),之后所述SRB在本地建立组播源信息表项,表项中记录组播服务器的组播IP地址、源IP地址,接收组播数据的端口、VLAN等信息,然后所述SRB向MRB发送携带所述组播源信息和SRB的地址信息的组播交互LSP报文。
其中,TRILL网络中的RB可以同时成为MRB,URB或SRB中的一种或多种角色。
在所述MRB上有组播VLAN和用户VLAN的绑定信息,当收到URB和SRB发来的组播交互LSP报文后,根据组播VLAN和用户VLAN绑定信息决定组播数据是否向用户设备转发。如果所述MRB收到了不同SRB发送的组播交互LSP报文,但报文中携带的组播IP地址相同(即代表不同SRB收到了相同的组播数据),MRB会根据预先配置或特定的选优规则决定哪个SRB收到的组播数据向用户设备转发。
如果组播数据允许向用户设备转发,那么所述MRB向所述SRB发送携带用户设备所在URB地址和组播IP地址等信息的组播交互LSP报文。同时,所述MRB向所述URB发送携带组播源所在SRB地址和组播IP地址、组播VLAN等信息的组播交互LSP(Label Switched Path,标签交换路径LSP)报文;如果组播数据不允许向用户设备转发,则所述MRB无动作。
所述SRB收到MRB发送的组播交互LSP报文后,根据所述LSP报文 携带信息将用户设备所在URB地址信息添加到相应的组播源信息表中,计算组播分发树,然后根据TRILL组播分发树向URB发送组播数据。
所述URB收到MRB发送的组播交互LSP报文后,根据所述LSP报文携带信息将URB地址信息和组播VLAN信息添加到相应的用户信息表中,当URB收到从组播VLAN发送过来的组播数据,将组播数据的组播VLAN标签替换为用户VLAN标签,然后向相应组播用户端口转发。
综上所述,本发明实施例提供的方法,通过选择TRILL网络中的一台RB为组播管理RB,对所有组播源和组播用户的跨VLAN组播进行集中管理,组播数据可直接通过TRILL网络组播分发树在组播VLAN内发送给组播用户接入RB,并在用户接入RB上完成组播VLAN标签到用户VLAN标签的切换之后发送给组播用户设备。与相关技术比较,本发明实施例是在TRILL网络中实现跨VLAN组播,组播服务器可直接接入TRILL网络,不需要先将组播服务器先接到支持跨VLAN组播的交换机上再接入TRILL网络。并且即使有多个组播服务器接入不同RB,也能实现跨VLAN组播统一管理,实现了TRILL网络资源利用的最大化。
下面对每种不同角色的路由器进行分别说明:
图4为本发明实施例提供的另一种在TRILL网络中传输组播数据的方法的流程示意图。图4所示方法包括:
步骤401、SRB接收处于第一VLAN的组播服务器发送的组播数据;
步骤402、所述SRB向MRB发送所述组播数据的描述信息和所述SRB的地址信息;
步骤403、所述SRB接收所述MRB发送的URB的地址信息,其中所述URB与请求所述组播数据的用户设备相连,且所述用户设备处于第二VLAN;
步骤404、所述SRB根据所述URB的地址信息,发送所述组播数据。
其中,所述组播数据的描述信息包括如下至少一个:组播服务器的组播IP地址、源IP地址、接收组播数据的端口、VLAN信息。
本发明提供的方法实施例,SRB在接收到组播数据后,通过MRB获取URB的地址信息,从而使得处于不同VLAN的用户设备能够接收到组播数 据,解决TRILL网络本身不能进行跨VLAN组播复制的问题,减少了组播数据的复制次数,有效控制网络上传输的流量。
图5为本发明实施例提供的又一种在TRILL网络中传输组播数据的方法的流程示意图。图5所示方法包括:
步骤501、URB接收处于第二VLAN的用户设备发送的组播请求;
步骤502、所述URB向MRB发送所述组播请求的描述信息和所述SRB的地址信息;
步骤503、所述URB接收所述MRB发送的SRB的地址信息,其中所述SRB与发送所述用户设备请求的组播数据的组播服务器相连,且所述组播服务器处于第一VLAN;
步骤504、所述URB根据所述SRB的地址信息,获取组播数据;
步骤505、所述URB将所述组播数据发送给所述用户设备。
其中,所述组播请求的描述信息包括如下至少一个:用户请求的组播IP地址、接收组播请求的端口和VLAN。
其中,所述URB将所述组播数据发送给所述用户设备,包括:
所述URB将所述组播数据的第一VLAN的标签替换为第二VLAN的标签,将完成标签替换后的组播数据发送至所述用户设备。
本发明提供的方法实施例,URB在接收到组播请求后,通过MRB获取SRB的地址信息,从而使得处于不同VLAN的用户设备能够接收到组播数据,解决TRILL网络本身不能进行跨VLAN组播复制的问题,减少了组播数据的复制次数,有效控制网络上传输的流量。
图6为本发明实施例提供的又一种在TRILL网络中传输组播数据的方法的流程示意图。图6所示方法包括:
步骤601、MRB在检测到URB接收到用户设备发送的组播请求以及SRB接收到组播服务器发送给的组播数据后,判断所述组播数据是否向所述用户设备转发,其中所述用户设备与所述组播服务器处于不同VLAN;
步骤602、如果是,则所述MRB向URB发送所述SRB的地址信息,通知URB接收所述组播数据,以及,向SRB发送所述URB的地址信息,通知SRB向所述URB发送所述组播数据。
可选的,所述MRB通过判断是否接收到所述URB发送包括组播请求的描述信息的报文来确定URB是否接收到用户设备发送的组播请求;和/或,所述MRB通过判断是否接收到所述SRB发送包括组播数据的描述信息的报文来确定SRB是否接收到组播服务器发送的组播数据。
URB和SRB均将信息的接收状况发送给MRB,方便MRB对URB和SRB的数据处理情况。
其中,URB和SRB是通过如下方式获取MRB地址信息的:所述MRB向其他所有RB发送通告消息,通告消息为携带所述MRB的地址信息的报文。
其中,所述MRB判断所述组播数据是否向所述用户设备转发,还包括:
所述MRB在接收到至少两个组播数据的描述信息,判断所述至少两个组播数据的组播IP地址是否相同;如果相同,则选择其中一个组播数据作为发送给用户设备的数据;如果不同,则根据用户设备请求的组播IP地址决定组播数据的分发。
本发明提供的方法实施例,MR在判断所述组播数据向所述用户设备发送时,向URB发送所述SRB的地址信息,通知URB接收所述组播数据,以及,向SRB发送所述URB的地址信息,通知SRB向所述URB发送所述组播数据,从而使得处于不同VLAN的用户设备能够接收到组播数据,解决TRILL网络本身不能进行跨VLAN组播复制的问题,减少了组播数据的复制次数,有效控制网络上传输的流量。
下面以图2组网的示意图为例,对用户设备1点播组播服务器1的组播业务流程的传输流程进行说明。
在TRILL网络中选择MRB业务处理的方法流程如下:
步骤A01:RB4被选为MRB后,向其他所有RB发送通告消息,通告消息为携带RB4地址信息的LSP报文。步骤A02:其他所有非MRB收到该通告消息后,计算并记录到MRB的转发路径。
在TRILL网络中组播源接入业务处理的方法流程如下:
步骤B01:RB1收到组播服务器1发送的组播数据后,自动成为SRB角 色(SRB1),在本地建立组播源信息表项,表项中记录组播服务器的组播IP地址,接收组播数据的端口、VLAN等信息。
步骤B02:SRB1向MRB发送携带所述组播源信息和SRB1的地址信息的组播交互LSP报文。报文格式可参见图7。
步骤B03:MRB收到SRB1发来的组播交互LSP报文后,根据MRB上有组播VLAN和用户VLAN的绑定信息决定是否通知SRB1向URB转发组播数据。
以图2组网为例,根据组播服务器1和组播服务器2发送的组播数据是否相同,考虑两种情况:
第一种,组播服务器1和组播服务器2发送的组播数据不同,即组播IP地址不同,MBR收到SRB1和SRB2的组播交互LSP报文后,根据用户设备请求的组播IP地址决定组播数据的分发;
第二种,组播服务器1和组播服务器2发送的组播数据相同,即组播IP地址相同,MBR收到SRB1和SRB2的组播交互LSP报文后,根据MRB上的预先配置或特定的选优规则决定SRB1和SRB2中的哪个设备向URB转发组播数据。
在TRILL网络中实现用户跨VLAN点播组播业务处理的方法流程如下:
步骤D01:用户设备1在VLAN10内向RB5发送组播请求报文,点播组播服务器1的组播业务。
步骤D02:RB5收到用户设备组播点播请求后,自动成为URB角色(URB1),在本地建立用户信息表项,表项中记录用户请求的组播IP地址,接收组播请求的端口、VLAN等信息,向MRB发送携带所述组播请求报文信息和URB1地址信息的组播交互LSP报文。
步骤D03:MRB收到URB1发来的组播交互LSP报文后,根据组播VLAN和用户VLAN绑定信息决定组播数据是否向用户设备转发。
步骤D04:如果SRB1的组播数据允许向用户设备转发,MRB向SRB1发送携带URB1地址和组播IP地址等信息的组播交互LSP报文。报文格式可参见图9。同时,MRB向URB1发送SRB1地址和组播IP地址、组播VLAN等信息的组播交互LSP报文。
步骤D05:SRB1收到MRB发送的组播交互LSP报文后,根据所述LSP报文携带信息将用户设备所在URB1地址信息添加到相应的组播源信息表中,开始根据TRILL组播分发树向URB1发送组播数据。
步骤D06:URB1收到MRB发送的组播交互LSP报文后,根据所述LSP报文携带信息将URB1地址信息和组播VLAN信息添加到相应的用户信息表中。
步骤D07:URB1收到SRB1发送过来的组播数据后,将组播数据的VLAN100标签替换为VLAN10标签,然后向用户设备1发送。
至此,用户设备1收到了组播数据,完成了对组播服务器1组播业务的跨VLAN点播。
下面,对本发明实施例中定义的五种组播交互LSP报文格式进行说明。
图7为本发明实施例所述方法中MRB向其他RB发送的通告LSP报文TLV格式示意图。其中Type字段代表LSP消息类型,此处为Management RB Announcement,长度为1byte;Length字段代表Value字段的长度,占用1byte;Value字段填充的是MRB的nickname等,还可根据需要扩充。
图8为本发明实施例所述方法中SRB向MRB发送的组播交互LSP报文TLV格式示意图,其中Type字段代表LSP消息类型,此处为Source RB Report,长度为1byte;Length字段代表Value字段的长度,占用1byte;Value字段填充的是SRB的nickname、Multicast Server IP Address(组播服务器IP地址)、Multicast VLAN ID(组播VLAN ID)和Multicast IP Address(组播IP地址)等,还可根据需要扩充。
图9为本发明实施例所述方法中URB向MRB发送的组播交互LSP报文TLV格式示意图,其中Type字段代表LSP消息类型,此处为User RB Report,长度为1byte;Length字段代表Value字段的长度,占用1byte;Value字段填充的是URB的nickname、User RB Report Type(URB报告类型,有Join和Leave两种类型,分别代表用户加入和用户离开)、User VLAN ID(用户VLAN ID)和Multicast IP Address(组播IP地址)等,还可根据需要扩充。
图10为本发明实施例所述方法中MRB向SRB发送的组播交互LSP报文TLV格式示意图,其中Type字段代表LSP消息类型,此处为Reply to  Source RB,长度为1byte;Length字段代表Value字段的长度,占用1byte;Value字段填充的是URB的nickname、Reply Type(MRB Reply类型,有Start和Stop两种类型,分别代表组播数据流量开始发送和停止发送)、Multicast Server IP Address(组播服务器IP地址)和Multicast VLAN ID(组播VLAN ID)等,还可根据需要扩充。
图11为本发明实施例所述方法中MRB向URB发送的组播交互LSP报文TLV格式示意图,其中Type字段代表LSP消息类型,此处为Reply to User RB,长度为1byte;Length字段代表Value字段的长度,占用1byte;Value字段填充的是SRB的nickname、Multicast VLAN ID(组播VLAN ID)、Multicast Server IP Address(组播服务器IP地址)和Multicast IP Address(组播IP地址)等,还可根据需要扩充。
由上可以看出,利用上述格式可以简单有效地利用报文的格式传输信息。
图12为本发明实施例提供的一种在TRILL网络中传输组播数据的装置的结构示意图。图12所示装置包括:
第一接收模块1201,设置为接收处于第一虚拟局域网(VLAN)的组播服务器发送的组播数据;
第一发送模块1202,设置为向组播管理路由桥(MRB)发送所述组播数据的描述信息和所述SRB的地址信息;
第二接收模块1203,设置为接收所述MRB发送的用户接入路由桥(URB)的地址信息,其中所述URB与请求所述组播数据的用户设备相连,且所述用户设备处于第二VLAN;
第二发送模块1204,设置为根据所述URB的地址信息,发送所述组播数据。
其中,所述组播数据的描述信息包括如下至少一个:组播服务器的组播IP地址、源IP地址、接收组播数据的端口、VLAN信息。
本发明提供的装置实施例,在接收到组播数据后,通过MRB获取URB的地址信息,从而使得处于不同VLAN的用户设备能够接收到组播数据,解决TRILL网络本身不能进行跨VLAN组播复制的问题,减少了组播数据的复制次数,有效控制网络上传输的流量。
图13为本发明实施例提供的另一种在TRILL网络中传输组播数据的装置的结构示意图。图13所示装置包括:
第三接收模块1301,设置为接收处于第二VLAN的用户设备发送的组播请求;
第三发送模块1302,设置为向MRB发送所述组播请求的描述信息和所述SRB的地址信息;
第四接收模块1303,设置为接收所述MRB发送的SRB的地址信息,其中所述SRB与发送所述用户设备请求的组播数据的组播服务器相连,且所述组播服务器处于第一VLAN;
获取模块1304,设置为根据所述SRB的地址信息,获取组播数据;
第四发送模块1305,设置为将所述组播数据发送给所述用户设备。
其中,所述组播请求的描述信息包括如下至少一个:用户请求的组播IP地址、接收组播请求的端口和VLAN。
其中,所述第四发送模块包括:
替换单元,设置为将所述组播数据的第一VLAN的标签替换为第二VLAN的标签;
发送单元,设置为将完成标签替换后的组播数据发送至所述用户设备。
本发明提供的装置实施例,URB在接收到组播请求后,通过MRB获取SRB的地址信息,从而使得处于不同VLAN的用户设备能够接收到组播数据,解决TRILL网络本身不能进行跨VLAN组播复制的问题,减少了组播数据的复制次数,有效控制网络上传输的流量。
图14为本发明实施例提供的又一种在TRILL网络中传输组播数据的装置的结构示意图。图14所示装置包括:
判断模块1401,设置为在检测到用户接入路由桥(URB)接收到用户设备发送的组播请求以及组播源路由桥(SRB)接收到组播服务器发送给的组播数据后,判断所述组播数据是否向所述用户设备转发,其中所述用户设备与所述组播服务器处于不同虚拟局域网(VLAN);
第五发送模块1402,设置为如果所述组播数据是向所述用户设备转发,则向URB发送所述SRB的地址信息,通知URB接收所述组播数据,以及, 向SRB发送所述URB的地址信息,通知SRB向所述URB发送所述组播数据。
其中所述判断模块1401,设置为通过判断是否接收到所述URB发送包括组播请求的描述信息的报文来确定URB是否接收到用户设备发送的组播请求;和/或,通过判断是否接收到所述SRB发送包括组播数据的描述信息的报文来确定SRB是否接收到组播服务器发送的组播数据。
可选的,所述装置还包括:
第六发送模块,设置为向其他所有RB发送通告消息,通告消息为携带所述MRB的地址信息的报文。
可选的,所述装置还包括:
判断单元,设置为在接收到至少两个组播数据的描述信息,判断所述至少两个组播数据的组播IP地址是否相同;
处理单元,设置为如果所述至少两个组播数据的组播IP地址相同,则选择其中一个组播数据作为发送给用户设备的数据;如果所述至少两个组播数据的组播IP地址不同,则根据用户设备请求的组播IP地址决定组播数据的分发。
本发明提供的装置实施例,MR在判断所述组播数据向所述用户设备发送时,向URB发送所述SRB的地址信息,通知URB接收所述组播数据,以及,向SRB发送所述URB的地址信息,通知SRB向所述URB发送所述组播数据,从而使得处于不同VLAN的用户设备能够接收到组播数据,解决TRILL网络本身不能进行跨VLAN组播复制的问题,减少了组播数据的复制次数,有效控制网络上传输的流量。
另外,本发明实施例还提供一种在TRILL网络中传输组播数据的系统,所述网络包括多个路由桥(RB),所述多个路由桥包括用户接入RB(URB)、组播源接入RB(SRB)以及组播管理RB(MRB),其中:
所述SRB包括图12所示的装置;
所述URB包括图13所示的装置;
所述MRB包括图14所示的装置。
本发明实施例提供的系统,通过选择TRILL网络中的一台RB为组播管理RB,对所有组播源和组播用户的跨VLAN组播进行集中管理,组播数据可直接通过TRILL网络组播分发树在组播VLAN内发送给组播用户接入RB,并在用户接入RB上完成组播VLAN标签到用户VLAN标签的切换之后发送给组播用户设备。与相关技术比较,本发明实施例是在TRILL网络中实现跨VLAN组播,组播服务器可直接接入TRILL网络,不需要先将组播服务器先接到支持跨VLAN组播的交换机上再接入TRILL网络。并且即使有多个组播服务器接入不同RB,也能实现跨VLAN组播统一管理,实现了TRILL网络资源利用的最大化。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现,所述计算机程序可以存储于一计算机可读存储介质中,所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行,在执行时,包括方法实施例的步骤之一或其组合。
可选地,上述实施例的全部或部分步骤也可以使用集成电路来实现,这些步骤可以被分别制作成一个个集成电路模块,或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样,本发明实施例不限制于任何特定的硬件和软件结合。
上述实施例中的每个装置/功能模块/功能单元可以采用通用的计算装置来实现,它们可以集中在单个的计算装置上,也可以分布在多个计算装置所组成的网络上。
上述实施例中的每个装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器,磁盘或光盘等。
以上所述,仅为本发明实施例的实施方式。因此,本发明的保护范围应以权利要求所述的保护范围为准。
工业实用性
本发明提供的实施例,MRB通过判断SRB接收的组播数据是否向用户设备发送,通知SRB向URB发送,解决TRILL网络本身不能进行跨VLAN组播复制的问题,能够实现TRILL网络跨VLAN组播的集中管理,并能避免带宽浪费,简化组网配置。

Claims (20)

  1. 一种在多链路透明互联TRILL网络中传输组播数据的方法,所述方法包括:
    组播接入路由桥SRB接收处于第一虚拟局域网VLAN的组播服务器发送的组播数据;
    所述SRB向组播管理路由桥MRB发送所述组播数据的描述信息和所述SRB的地址信息;
    所述SRB接收所述MRB发送的用户接入路由桥URB的地址信息,其中所述URB与请求所述组播数据的用户设备相连,且所述用户设备处于第二VLAN;
    所述SRB根据所述URB的地址信息,发送所述组播数据。
  2. 根据权利要求1所述的方法,其中,所述组播数据的描述信息包括如下至少一个:组播服务器的组播IP地址、源IP地址、接收组播数据的端口、VLAN信息。
  3. 一种在多链路透明互联TRILL网络中传输组播数据的方法,包括:
    用户接入路由桥URB接收处于第二虚拟局域网VLAN的用户设备发送的组播请求;
    所述URB向组播管理路由桥MRB发送所述组播请求的描述信息和所述SRB的地址信息;
    所述URB接收所述MRB发送的组播源路由桥SRB的地址信息,其中所述SRB与发送所述用户设备请求的组播数据的组播服务器相连,且所述组播服务器处于第一VLAN;
    所述URB根据所述SRB的地址信息,获取组播数据;
    所述URB将所述组播数据发送给所述用户设备。
  4. 根据权利要求3所述的方法,其中,所述组播请求的描述信息包括如下至少一个:用户请求的组播IP地址、接收组播请求的端口和VLAN。
  5. 根据权利要求3或4所述的方法,其中,所述URB将所述组播数据发送给所述用户设备,包括:
    所述URB将所述组播数据的第一VLAN的标签替换为第二VLAN的标签,将完成标签替换后的组播数据发送至所述用户设备。
  6. 一种在多链路透明互联TRILL网络中传输组播数据的方法,所述方法包括:
    组播管理路由桥MRB在检测到用户接入路由桥URB接收到用户设备发送的组播请求以及组播源路由桥SRB接收到组播服务器发送给的组播数据后,判断所述组播数据是否向所述用户设备转发,其中所述用户设备与所述组播服务器处于不同虚拟局域网VLAN;
    如果是,则所述MRB向URB发送所述SRB的地址信息,通知URB接收所述组播数据,以及,向SRB发送所述URB的地址信息,通知SRB向所述URB发送所述组播数据。
  7. 根据权利要求6所述的方法,其中,
    所述MRB通过判断是否接收到所述URB发送包括组播请求的描述信息的报文来确定URB是否接收到用户设备发送的组播请求;和/或,
    所述MRB通过判断是否接收到所述SRB发送包括组播数据的描述信息的报文来确定SRB是否接收到组播服务器发送的组播数据。
  8. 根据权利要求7所述的方法,所述方法还包括:
    所述MRB向其他所有RB发送通告消息,通告消息为携带所述MRB的地址信息的报文。
  9. 根据权利要求6至8任一所述的方法,其中,所述MRB判断所述组播数据是否向所述用户设备转发,还包括:
    所述MRB在接收到至少两个组播数据的描述信息,判断所述至少两个组播数据的组播IP地址是否相同;如果相同,则选择其中一个组播数据作为发送给用户设备的数据;如果不同,则根据用户设备请求的组播IP地址决定 组播数据的分发。
  10. 一种在多链路透明互联TRILL网络中传输组播数据的方法,其中,所述网络包括多个路由桥RB,所述多个路由桥包括用户接入RBURB、组播源接入RBSRB以及组播管理RBMRB,所述方法包括:
    所述URB接收所述用户设备发送的组播请求;
    所述SRB接收组播服务器发送的组播数据;
    所述MRB在检测到URB接收到组播请求以及SRB接收到组播数据后,判断所述组播数据是否向所述用户设备转发,如果是,则向URB发送所述SRB的地址信息,向SRB发送所述URB的地址信息;其中所述用户设备与所述组播服务器处于不同虚拟局域网VLAN;
    所述SRB在得到所述URB的地址信息后,向所述URB发送所述URB请求的组播数据;
    所述URB根据所述SRB的地址信息,接收所述组播数据,并向所述用户设备发送所述组播数据。
  11. 一种在多链路透明互联TRILL网络中传输组播数据的装置,所述装置包括:
    第一接收模块,设置为接收处于第一虚拟局域网VLAN的组播服务器发送的组播数据;
    第一发送模块,设置为向组播管理路由桥MRB发送所述组播数据的描述信息和所述SRB的地址信息;
    第二接收模块,设置为接收所述MRB发送的用户接入路由桥URB的地址信息,其中所述URB与请求所述组播数据的用户设备相连,且所述用户设备处于第二VLAN;
    第二发送模块,设置为根据所述URB的地址信息,发送所述组播数据。
  12. 根据权利要求11所述的装置,其中,所述组播数据的描述信息包括如下至少一个:组播服务器的组播IP地址、源IP地址、接收组播数据的 端口和VLAN信息。
  13. 一种在多链路透明互联TRILL网络中传输组播数据的装置,所述装置包括:
    第三接收模块,设置为接收处于第二虚拟局域网VLAN的用户设备发送的组播请求;
    第三发送模块,设置为向组播管理路由桥MRB发送所述组播请求的描述信息和所述SRB的地址信息;
    第四接收模块,设置为接收所述MRB发送的组播源路由桥SRB的地址信息,其中所述SRB与发送所述用户设备请求的组播数据的组播服务器相连,且所述组播服务器处于第一VLAN;
    获取模块,设置为根据所述SRB的地址信息,获取组播数据;
    第四发送模块,设置为将所述组播数据发送给所述用户设备。
  14. 根据权利要求13所述的装置,其中,所述组播请求的描述信息包括如下至少一个:用户请求的组播IP地址、接收组播请求的端口和VLAN。
  15. 根据权利要求13或14所述的装置,其中,所述第四发送模块包括:
    替换单元,设置为将所述组播数据的第一VLAN的标签替换为第二VLAN的标签;
    发送单元,设置为将完成标签替换后的组播数据发送至所述用户设备。
  16. 一种在多链路透明互联TRILL网络中传输组播数据的装置,所述装置包括:
    判断模块,设置为在检测到用户接入路由桥URB接收到用户设备发送的组播请求以及组播源路由桥SRB接收到组播服务器发送给的组播数据后,判断所述组播数据是否向所述用户设备转发,其中所述用户设备与所述组播服务器处于不同虚拟局域网VLAN;
    第五发送模块,设置为如果所述组播数据是向所述用户设备转发,则向URB发送所述SRB的地址信息,通知URB接收所述组播数据,以及,向SRB发送所述URB的地址信息,通知SRB向所述URB发送所述组播数据。
  17. 根据权利要求16所述的装置,还包括:
    所述判断模块,设置为通过判断是否接收到所述URB发送包括组播请求的描述信息的报文来确定URB是否接收到用户设备发送的组播请求;和/或,通过判断是否接收到所述SRB发送包括组播数据的描述信息的报文来确定SRB是否接收到组播服务器发送的组播数据。
  18. 根据权利要求17所述的装置,还包括:
    第六发送模块,设置为向其他所有RB发送通告消息,通告消息为携带所述MRB的地址信息的报文。
  19. 根据权利要求16至18任一所述的装置,还包括:
    判断单元,设置为在接收到至少两个组播数据的描述信息,判断所述至少两个组播数据的组播IP地址是否相同;
    处理单元,设置为如果所述至少两个组播数据的组播IP地址相同,则选择其中一个组播数据作为发送给用户设备的数据;如果所述至少两个组播数据的组播IP地址不同,则根据用户设备请求的组播IP地址决定组播数据的分发。
  20. 一种在多链路透明互联TRILL网络中传输组播数据的系统,其中,所述网络包括多个路由桥,所述多个路由桥包括用户接入路由桥、组播源接入路由桥以及组播管理路由桥,其中:
    所述组播源接入路由桥包括如权利要求11或12所述的装置;
    所述用户接入路由桥包括如权利要求13至15任一所述的装置;
    所述组播管理路由桥包括如权利要求16至19任一所述的装置。
PCT/CN2015/091864 2014-12-03 2015-10-13 在trill网络中传输组播数据的方法、装置和系统 WO2016086721A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410727810.7 2014-12-03
CN201410727810.7A CN105721322A (zh) 2014-12-03 2014-12-03 在trill网络中传输组播数据的方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2016086721A1 true WO2016086721A1 (zh) 2016-06-09

Family

ID=56090976

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/091864 WO2016086721A1 (zh) 2014-12-03 2015-10-13 在trill网络中传输组播数据的方法、装置和系统

Country Status (2)

Country Link
CN (1) CN105721322A (zh)
WO (1) WO2016086721A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107528847A (zh) * 2017-09-01 2017-12-29 天津赞普科技股份有限公司 一种基于mac分流的保护方法
CN114448740A (zh) * 2022-01-14 2022-05-06 绿盟科技集团股份有限公司 一种组播方法、装置、介质、产品和设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103457821A (zh) * 2013-08-28 2013-12-18 杭州华三通信技术有限公司 基于trill网络的跨vlan组播实现方法和装置
US20140071987A1 (en) * 2012-09-07 2014-03-13 Dell Products L.P. Systems and methods providing reverse path forwarding compliance for a multihoming virtual routing bridge
CN103873373A (zh) * 2012-12-11 2014-06-18 杭州华三通信技术有限公司 一种组播数据报文转发方法及设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3703345A1 (en) * 2010-06-29 2020-09-02 Huawei Technologies Co., Ltd. Asymmetric network address encapsulation
CN102957620B (zh) * 2011-08-26 2017-04-26 华为技术有限公司 一种trill网络中mac地址表项的管理方法和设备
CN103227757B (zh) * 2012-08-31 2016-12-28 杭州华三通信技术有限公司 一种报文转发方法及设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140071987A1 (en) * 2012-09-07 2014-03-13 Dell Products L.P. Systems and methods providing reverse path forwarding compliance for a multihoming virtual routing bridge
CN103873373A (zh) * 2012-12-11 2014-06-18 杭州华三通信技术有限公司 一种组播数据报文转发方法及设备
CN103457821A (zh) * 2013-08-28 2013-12-18 杭州华三通信技术有限公司 基于trill网络的跨vlan组播实现方法和装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107528847A (zh) * 2017-09-01 2017-12-29 天津赞普科技股份有限公司 一种基于mac分流的保护方法
CN107528847B (zh) * 2017-09-01 2020-10-27 天津赞普科技股份有限公司 一种基于mac分流的保护方法
CN114448740A (zh) * 2022-01-14 2022-05-06 绿盟科技集团股份有限公司 一种组播方法、装置、介质、产品和设备
CN114448740B (zh) * 2022-01-14 2023-11-07 绿盟科技集团股份有限公司 一种组播方法、装置、介质、产品和设备

Also Published As

Publication number Publication date
CN105721322A (zh) 2016-06-29

Similar Documents

Publication Publication Date Title
US7515535B2 (en) Technique for efficiently managing bandwidth for multipoint-to-multipoint services in a provider network
JP6491241B2 (ja) クラウドベースのサービス交換
US8537816B2 (en) Multicast VPN support for IP-VPN lite
WO2017059708A1 (zh) Bier信息的发送方法、接收方法及装置
CN101047636B (zh) 端到端伪线仿真虚拟租用线接入虚拟专用网的方法及系统
CN100433730C (zh) 组播点播方法及系统
WO2021007963A1 (zh) 路由分发方法及控制器、信息路由方法及网络节点设备
CN105991432A (zh) 提供商边缘路由器及方法
CN107666397A (zh) Pe路由器之间传送多播组离开请求的方法和pe路由器
CN103067286B (zh) 一种组播数据传输方法和设备
WO2016198017A1 (zh) 一种组播地址的传输方法和装置
WO2007134551A1 (fr) Procédé et dispositif noeud de réservation de ressources de réseau
CN103873373A (zh) 一种组播数据报文转发方法及设备
WO2015055016A1 (zh) 网元设备配置和管理方法、装置及网元设备
CN100481817C (zh) 一种基于ip/mpls/bgp的多域组播一体化数据分发结构及方法
JP2022533238A (ja) Tsn内のコントローラ間の通信のための方法、装置、およびシステム
CN102035729A (zh) 一种组播数据转发方法及其装置
CN104243270A (zh) 一种建立隧道的方法和装置
US20140226525A1 (en) Safe Multicast Distribution with Predictable Topology Changes
WO2009082905A1 (fr) Procédé système et dispositif commutateur permettant l'établissement dynamique de réseau local virtuel de multidiffusion
CN105162704A (zh) Overlay网络中组播复制的方法及装置
CN108964940A (zh) 消息发送方法及装置、存储介质
WO2018014767A1 (zh) 一种信息确定方法、装置及存储介质
CN107040441B (zh) 跨数据中心的数据传输方法、装置及系统
WO2013107245A1 (zh) 在透明多链路互联(trill)网络中实现组播的方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15865311

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15865311

Country of ref document: EP

Kind code of ref document: A1