WO2013044740A1

WO2013044740A1 - Multicast implementation method and device supporting non-single vlan

Info

Publication number: WO2013044740A1
Application number: PCT/CN2012/081560
Authority: WO
Inventors: 于立元; 金飞蔡; 王恒
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-09-26
Filing date: 2012-09-18
Publication date: 2013-04-04
Also published as: CN102340450A

Abstract

Disclosed is a multicast implementation method supporting a non-single VLAN, comprising: running a multicast protocol at a network layer, and running multicast snooping at a link layer; creating a three-layer interface encapsulated or aggregated by more than two VLANs; delivering multicast data traffic to a two-layer VLAN corresponding to a multicast data receiver through the three-layer interface, and then delivering the multicast data traffic to a physical port corresponding to the multicast data receiver through the two-layer VLAN. Also disclosed is a multicast implementation device supporting a non-single VLAN. The multicast solution provided by the present invention solves the multicast implementation problem for a non-single VLAN environment, and has advantages that the bandwidth utilization ratio is high and the communication data is secure.

Description

Multicast implementation method and device supporting non-single VLAN

The present invention relates to the field of communications technologies, and in particular, to a non-single virtual local area network

(VLAN, Virtual Local Area Network) multicast implementation method and device. Background technique

1. Unicast, broadcast, multicast

Unicast mode is a point-to-point transmission method. When transmitting information in unicast mode, each user who needs the information needs to establish a separate data transmission path and send a separate copy information for the user. . Communication between any two points does not interfere with other communication points within the network (except for shared channel contention).

Different from the unicast mode, the broadcast mode is a point-to-point transmission method, and the information transmission in the broadcast mode, all the users in the network receive the broadcast information whether or not they need it. This will undoubtedly increase the processing load on users who are not interested in broadcast information. The transmission mode of the broadcast is poor in terms of information confidentiality and compensation. In addition, if the users who need the information in the network are small, the network resource utilization rate will be very low, the bandwidth will be seriously wasted, and the serious broadcast may be caused by the route loopback. storm.

From the characteristics of unicast and broadcast information transmission, the unicast mode is suitable for users with less network, and the broadcast mode is suitable for users with dense networks. When the amount of users who need certain information in the network is uncertain, the efficiency of these two methods is relatively low, that is, the traditional unicast and broadcast methods can not effectively solve the problem of single-point transmission and multi-point reception. Multicast technology emerges as the times require, which can effectively solve this problem and achieve efficient point-to-multipoint data transmission in IP networks.

Multicast is a point-to-multipoint transmission mode. When some users in the network need specific information, the multicast source only sends information once (the destination address in the message is a multicast address). All receiving users in the broadcast group can receive the same copy of the information, and other users on the network that are not in the multicast group cannot receive it. Compared with the traditional unicast and broadcast methods, the advantages of multicast are obvious. First, regardless of the number of receivers, the same multicast data stream has only one copy on each link, and the increase in the number of users does not increase significantly. The load of the network. Second, the multicast data stream is only sent to the recipient of the required data, making reasonable use of bandwidth. Unicast and broadcast can also be understood as a special form of multicast, that is, when only one user or all users in the network request the same information.

With the rapid development of the Internet and the emergence of various emerging businesses, the importance of multicast has become increasingly prominent. People can make full use of the multicast features of the network to provide a variety of value-added services, including live broadcast, IPTV, distance education, telemedicine, Internet radio, real-time video conferencing, and more.

Second, Layer 2 multicast, Layer 3 multicast

IGMP Snooping is short for Internet Group Management Protocol Snooping. It is a multicast constraint mechanism running on Layer 2 devices to manage and control multicast groups.

The Layer 2 device running IGMP Snooping analyzes the received IGMP messages and establishes a mapping relationship between the port and the Medium/Media Access Control (MAC) multicast address, and forwards the multicast according to the mapping relationship. data. When Layer 2 devices are not running IGMP Snooping, multicast data is broadcast on the Layer 2 device. After the Layer 2 device runs IGMP Snooping, the multicast data of the multicast group is not broadcast on the Layer 2 but on the Layer 2 device. Multicast to the intended recipient.

IGMP Snooping, like the IGMP (Internet Group Management Protocol) protocol, is used for the management and control of multicast groups. They all use IGMP messages. The IGMP protocol runs on the network layer, that is, Layer 3, and IGMP Snooping runs on the link layer, that is, Layer 2. When a Layer 2 Ethernet switch receives IGMP messages transmitted between the host and the router, IGMP Snooping analysis is performed. The information carried in the IGMP message is used to establish and maintain the MAC address table. The multicast packets sent from the router are forwarded according to the MAC address table. IGMP Snooping will only send IGMP group-specific queries to the port when it receives an IGMP Leave message from a port or the aging timer of a port expires. Otherwise, it does not send packets to the port. Any IGMP message.

Generally, multicast snooping running on the link layer is called Layer 2 multicast. Multicast snooping is for IGMP, Multicast Listener Discovery (MLD), Protocol Independent Multicast. (PIM, Protocol Independent Multicast), ΡΙΜνό and other four multicast protocol snooping collectively; The multicast protocol running on the network layer (including the above four multicast protocols) is called Layer 3 multicast.

Third, supervlan

Supervlan, also known as VLAN aggregation (VLAN Aggregation), is a Layer 3 VLAN technology that saves VLAN interfaces and IP addresses. The principle is that a supervlan contains multiple sub-VLANs, each sub-VLAN is a broadcast domain, and two sub-VLANs are between two sub-VLANs. The layers are isolated from each other. A super-VLAN is configured with a Layer 3 interface. A sub-VLAN cannot be configured with a Layer 3 interface. When a user in a sub-VLAN needs to perform Layer 3 communication, the IP address of the supervlan Layer 3 interface is used as the gateway address, so that multiple sub-VLANs share one IP network segment, thus saving IP address resources.

Supervlan does not have its own member port. Ports are specified in the sub-VLAN. As a member of supervlan, the sub-VLAN does not have its own IP address. Instead, it uses the IP address of supervlan as its own routing interface address.

Supervlan can be used to isolate ports in the same VLAN. Sub-VLANs of different VLANs still retain their own independent broadcast domains. One or more sub-VLANs belong to the same supervlan, and the interface address of the supervlan is the default gateway IP address. . Once VLAN aggregation is used, clients are allowed to use different broadcast domains on the same subnet, but these clients use the same routing interface to enhance the utilization of IP addresses. Fourth, multicast under supervlan

Multicast Snooping supports the Layer 2 VLAN (Virtual Local Area Network) and VPLS (Virtual Private Network Service) environment. Currently, there is no standard for multicast snooping in the supervlan environment.

The supervlan is a Layer 3 interface. The Layer 3 interface is an interface that needs to be configured with an IP address for Layer 3 protocol. After Layer 3 multicast pushes traffic to the Layer 3 supervlan interface, if there is no Snooping support, multicast traffic can only be broadcasted in all sub-VLANs. This greatly reduces bandwidth utilization and lacks security. The vendor supports the multicast service of the supervlan port. If Snooping is enabled, the multicast data stream will be sent only to the receivers that require the data. If there is no receiver, Layer 3 multicast will no longer push traffic to the Layer 3 supervlan interface.

In summary, the prior art lacks an effective multicast implementation method that supports non-single VLANs such as supervlan. Summary of the invention

The present invention provides a multicast implementation method and apparatus for supporting non-single VLANs to solve the problem of lacking a multicast implementation scheme supporting non-single VLANs in the prior art.

The present invention provides a multicast implementation method for supporting a non-single VLAN, including:

Running the multicast protocol at the network layer and running multicast snooping on the link layer;

Create a Layer 3 interface that is encapsulated or aggregated by more than two VLANs.

The multicast data is sent to the Layer 2 VLAN corresponding to the receiver of the multicast data through the Layer 3 interface, and then sent to the physical port corresponding to the receiver of the multicast data by the Layer 2 VLAN.

Preferably, the Layer 3 interface is a supervlan interface, or a VLAN range sub-interface, or a VLAN QinQ range sub-interface.

Preferably, the network layer (ie, Layer 3 multicast) is responsible for interacting with the upstream protocol and directing multicast data traffic to a Layer 3 interface that receives upstream multicast data traffic, where the link layer (ie, Layer 2 multicast) Responsible for downstream user management and VLAN and physical port corresponding to the specified user. The downstream device of the aggregated Layer 3 interface sends a general query packet.

Preferably, the multicast data traffic is sent to the multicast data receiver by using an integrated entry forwarding or a secondary lookup table forwarding.

The present invention further provides a multicast implementation apparatus for supporting a non-single VLAN, including: a protocol operation module, configured to run a multicast protocol at a network layer, and run multicast snooping on a link layer;

A Layer 3 interface creation module is used to create a Layer 3 interface encapsulated or aggregated by more than two VLANs.

The traffic delivery module is configured to send the multicast data traffic to the Layer 2 VLAN corresponding to the receiver of the multicast data through the Layer 3 interface, and then send the data to the physical entity corresponding to the multicast data receiver through the Layer 2 VLAN. mouth.

The beneficial effects of the present invention are as follows:

The multicast implementation method and apparatus provided by the present invention solve the problem that the multicast method in the prior art does not support multicast in a non-single VLAN environment such as a supervlan interface, and can be a supervlan interface, a VLAN range sub-interface, or a VLAN QinQ. In a non-single-VLAN environment such as a range sub-interface, multicast data traffic is multicast to the Layer 2 VLAN and physical port corresponding to the receiver of the multicast data. Receiver. The multicast scheme provided by the present invention not only solves the multicast implementation problem for a non-single VLAN environment, but also has the advantages of high bandwidth utilization and secure communication data. DRAWINGS

1 is a schematic flowchart of a multicast implementation method for supporting a non-single VLAN according to the present invention; FIG. 2 is a schematic overall flow chart of the method of the present invention as a specific embodiment; 3 is a schematic diagram of a networking configuration and a second and third layer multicast function division according to an embodiment of the present invention; FIG. 4 is a schematic diagram of basic steps of traffic forwarding according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of forwarding of an integrated entry according to an embodiment of the present invention; FIG.

6 is a schematic diagram of secondary table lookup forwarding according to an embodiment of the present invention;

7 is a schematic diagram of sending a query message according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of receiving a join message and leaving a message according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of sending a specific query message according to an embodiment of the present invention; FIG.

FIG. 10 is a schematic diagram of a Layer 3 route for notifying Layer 3 multicast addition and deleting a supervlan according to an embodiment of the present invention;

FIG. 11 is a schematic structural diagram of a multicast implementation apparatus supporting a non-single VLAN according to the present invention. detailed description

The present invention will be further described in detail below in conjunction with the drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

Method embodiment

According to an embodiment of the present invention, a multicast implementation method for supporting a non-single VLAN is provided. FIG. 1 is a schematic flowchart of a multicast implementation method for supporting a non-single VLAN according to the present invention. As shown in FIG. 1, the present invention supports non-single The multicast implementation method of the VLAN includes the following processing:

In step 101, the multicast protocol is run on the network layer, and the multicast snooping is run on the link layer. Step 102: Create a Layer 3 interface that is encapsulated or aggregated by two or more VLANs. Step 103: Perform multicast data traffic. The Layer 3 interface created in step 102 is sent to the Layer 2 VLAN corresponding to the receiver of the multicast data, and then sent to the multicast data receiver through the Layer 2 VLAN.

The Layer 3 interface created in the step 102 can be a super-VLAN interface, or a VLAN-size sub-interface, or a VLAN-based QinQ range sub-interface. The Layer 3 interface can be encapsulated or aggregated by two or more VLANs. Any of the three layer interfaces. The following specific The supervlan interface is used as an example to further describe the multicast implementation method of the present invention supporting non-single VLAN.

FIG. 2 is a schematic diagram of the overall process of the method of the present invention as a specific embodiment. As shown in FIG. 2, in the embodiment of the present invention, Layer 3 multicast is responsible for interacting with the upstream protocol and directing the traffic to the uplink three-layer interface, that is, A Layer 3 interface that receives upstream multicast data traffic. Layer 2 multicast is responsible for downstream user management and VLANs and physical interfaces corresponding to the specified user. The forwarding plane (that is, the driver or microcode) is delivered according to Layer 2 multicast and Layer 3 multicast. The entry is used to forward multicast data traffic. Specifically, the Layer 3 multicast is responsible for performing the following processing: interacting with the upstream protocol and directing the multicast data traffic to the Layer 3 interface that receives the upstream multicast data traffic, creating the routing forwarding entry as the supervlan interface, and the supervlan interface The downstream device on the interface sends a general query protocol packet. Layer 2 multicast is responsible for the following operations: Layer 2 multicast snooping is responsible for processing the joining of the downstream devices on the supervlan interface, leaving the protocol packets, and sending the specific query protocol packets. Layer 2 multicast snooping notifies the Layer 3 multicast supervlan interface. Whether there is a user in the downstream device. In Figure 2, the device refers to a Layer 3 device, which is a Layer 3 switch or a Layer 3 router. " ' L3" refers to a Layer 3 multicast module. " ' S " refers to a multicast routing forwarding entry that Layer 3 multicast points to the supervlan interface. '1' refers to the multicast forwarding entry of Layer 2 multicast to the specified VLAN 1 and physical port 1 of the supervlan interface.

In the embodiment of the present invention, the multicast data traffic is sent to the multicast data receiver by means of integrated entry forwarding or secondary lookup table forwarding.

The method of the present invention operates on a three-layer device, including a three-layer switch or a three-layer router.

FIG. 3 is a schematic diagram of a networking configuration and a second and third layer multicast function division according to an embodiment of the present invention. As shown in FIG. 3, the networking configuration of the embodiment of the present invention includes:

1) connecting the upstream device through the physical port 9;

2) Enable the Layer 3 interface on the physical port 9 for Layer 3 multicast, for example, Layer 3 VLAN 9 port, and Layer 3 VLAN 9 port is the interface for receiving traffic, that is, receiving upstream multicast data traffic;

3) Create a three-layer interface supervlanl, and the three-layer supervlan is an outgoing traffic interface. The multicast data traffic received by the Layer 9 VLAN interface is delivered to the Layer 2 VLAN. The Layer 3 VLAN 9 interface and the Layer 3 supervlan interface are used together for Layer 3 multicast.

4) Layer 2 VLAN 1, Layer 2 VLAN 2, Layer 2 VLAN 3 are all bound to supervlanl;

5) Physical port 1-3 is bound to Layer 2 VLAN 1, physical port 4-6 is bound to Layer 2 VLAN 2, and physical port 6-7 is bound to Layer 2 VLAN 3. Physical interface 6 is bound to Layer 2 VLAN 2 at the same time. , Layer 2 VLAN 3;

6) Physical port 1-7 connects downstream devices.

As shown in FIG. 3, in the embodiment of the present invention, the Layer 2 multicast and Layer 3 multicast functions are divided as follows: 1) Layer 3 multicast is responsible for interacting with the upstream protocol and directing traffic to the uplink Layer 3 interface, that is, VLAN9 port;

2) The outgoing interface of the Layer 3 multicast routing and forwarding entry is a supervlan interface.

3) Layer 3 multicast is responsible for sending general query protocol packets to downstream devices on the supervlan interface.

4) Layer 2 multicast notification Layer 3 multicast Whether there is a user on the downstream device under the supervlan interface;

5) Layer 2 multicast is responsible for processing the joining and leaving protocol packets of the downstream devices on the supervlan interface, and is responsible for sending specific query protocol packets.

FIG. 4 is a schematic diagram of the basic steps of the traffic forwarding according to the embodiment of the present invention. As shown in FIG. 4, in the embodiment of the present invention, the forwarding of the multicast data traffic includes the following steps:

Step 401, start;

Step 402, the traffic is sent from the upstream to the physical port 9;

Step 403, after querying the Layer 3 multicast routing table, find the outbound interface supervlanl;

Step 404: The traffic is sent to the VLAN that needs to be forwarded by the supervlanl, and the traffic is forwarded to the physical interface that needs to forward the traffic. Bandwidth resources, reducing equipment load;

Step 405, ending. FIG. 5 is a schematic diagram of the forwarding of the integrated entry according to the embodiment of the present invention. As shown in FIG. 5, in the embodiment of the present invention, the method for forwarding the integrated entry includes the following steps:

1) Integrate Layer 2 multicast and Layer 3 multicast entries, and integrate a generated forwarding entry to directly write the chip;

2) When the drive is forwarded, the Layer 3 supervlan interface and the determined VLAN and physical port are directly found by checking the integrated entry. The determined VLAN and the physical interface are the VLANs and physical interfaces that need to deliver traffic, that is, the multicast data receivers. VLAN and physical port.

Compared with the secondary table lookup forwarding, the hardware forwarding efficiency is high by using the integrated table entry forwarding mode.

FIG. 6 is a schematic diagram of the secondary table lookup forwarding according to the embodiment of the present invention. As shown in FIG. 6, in the embodiment of the present invention, the secondary table lookup forwarding manner includes the following steps:

1) Layer 2 multicast and Layer 3 multicast write their respective entries independently;

2) When the driver forwards, check the Layer 3 multicast forwarding table to find the Layer 3 supervlan interface, and then check the Layer 2 multicast forwarding table to find the specified VLAN and physical interface, that is, the VLAN and physical port that need to deliver traffic, that is, multicast. The VLAN and physical port corresponding to the data receiver.

The secondary table lookup forwarding does not require the integration of Layer 3 multicast and Layer 2 multicast entries. The relative consolidated entry is forwarded. The secondary lookup table forwarding mode is simple to implement and the device stability is high.

FIG. 7 is a schematic diagram of sending a general query message according to an embodiment of the present invention. As shown in FIG. 7, in the embodiment of the present invention, sending a general query message includes the following steps:

1) Layer 3 multicast enables the querier on the supervlanl interface to periodically send general query messages.

2) Send a general query message to all VLANs and physical port copies of the supervlanl interface;

3) Send a general query message to the downstream device in broadcast mode.

FIG. 8 is a schematic diagram of receiving a join message and leaving a message according to an embodiment of the present invention. As shown in FIG. 8, in the embodiment of the present invention, receiving a join message and leaving a message includes the following steps:

1) In the embodiment of the present invention, Layer 2 multicast does not support receiving query messages, and does not support static configuration. The routing port does not need to be forwarded to the upstream routing port after receiving the join message or leaving the packet.

2) Generate, update, or delete Layer 2 multicast forwarding entries.

FIG. 9 is a schematic diagram of sending a specific query message according to an embodiment of the present invention. As shown in FIG. 9, in the embodiment of the present invention, sending a specific query message includes the following steps:

1) Determine the VLAN of the Layer 2 multicast on the supervlan interface, and determine whether the physical interface receives the Leave message and processes it according to whether the fast leave function is enabled.

2) When fast leave is configured, a specific query packet is sent to avoid the problem that traffic may be interrupted during a common query cycle when there are other downstream devices on the same VLAN and the same physical interface. 3) When the configuration is fast, directly Delete the Layer 2 multicast forwarding entry.

FIG. 10 is a schematic diagram of a Layer 3 route for informing a Layer 3 multicast to be added and deleted to a supervlan according to an embodiment of the present invention. As shown in FIG. 10, in the embodiment of the present invention, a Layer 3 multicast is added and a Layer 3 route directed to a supervlan is added. Including the following steps:

Step 1001: After receiving the join message, generate a Layer 2 multicast forwarding entry 1;

Step 1002: If the first member in the same group, the same source, and the supervlan interface are added, notify the Layer 3 multicast to add a Layer 3 routing entry s pointing to the supervlan;

Step 1003: After receiving the join message, update the Layer 2 multicast forwarding entry 1; update the Layer 2 multicast forwarding entry in the same group, the same source, and the supervlan interface, and do not need to notify the Layer 3 multicast again; Step 1004, Receive After the packet is added, the Layer 2 multicast forwarding entry is generated. The Layer 2 multicast forwarding entry is added to the same group, the same source, and the supervlan interface.

Step 1005: After receiving the leave message, the second layer multicast forwarding entry 2 is deleted, and the second layer multicast forwarding entry in the same group, the same source, and the supervlan interface is deleted, and the layer 3 multicast is not required to be notified.

Step 1006: After receiving the leaving message, the method finally deletes the Layer 2 multicast forwarding entry 1; Step 1007: Delete the last Layer 2 multicast forwarding entry in the same group, the same source, and the supervlan interface, and notify the Layer 3 multicast to delete the Layer 3 routing entry s of the supervlan.

The supervlan interface is used as an example to describe the multicast implementation method of the present invention. The method of the present invention is also applicable to a VLAN range sub-interface (for a single-layer VLAN encapsulation) scenario and a VLAN QinQ range sub-interface (for a dual Layer VLAN encapsulation scenario. In VLAN range mode, Layer 2 multicast manages downstream users based on VLANs and physical interfaces. In VLAN QinQ range mode, Layer 2 multicast manages downstream users based on inner and outer VLANs and physical interfaces. For details about the implementation scheme, refer to the description of the supervlan interface scenario, and no further details are provided here.

If no snooping is supported, multicast traffic can be sent in broadcast mode in all VLAN range or VLAN QinQ range. If there is Snooping support, that is, when the method provided by the present invention is used, the multicast data stream is only sent to the receiver of the required data. When there is no receiver, the Layer 3 multicast does not push traffic to the Layer 3 interface in these scenarios. .

Device embodiment

According to an embodiment of the present invention, a multicast implementation apparatus for supporting a non-single VLAN is provided, and FIG. 11 is a schematic structural diagram of a multicast implementation apparatus supporting a non-single VLAN according to an embodiment of the present invention, as shown in FIG. The multicast implementation device supporting the non-single VLAN of the embodiment includes a protocol running module 1101, a layer 3 interface creating module 1102, and a traffic sending module 1103. The modules of the embodiments of the present invention are described in detail below.

Specifically, the protocol running module 1101 is configured to run the multicast protocol on the network layer, and run the multicast snooping on the link layer.

The Layer 3 interface creation module 1102 is configured to create a Layer 3 interface encapsulated or aggregated by two or more VLANs.

The traffic delivery module 1103 is configured to send the multicast data traffic to the Layer 2 VLAN corresponding to the receiver of the multicast data through the Layer 3 interface created by the Layer 3 interface creation module 1102, and then send the multicast data to the multicast data through the Layer 2 VLAN. The physical port corresponding to the receiver. The Layer 3 interface created by the Layer 3 interface creation module 1102 can be a supervlan interface, a VLAN range sub-interface, or a VLAN QinQ range sub-interface. Of course, the three inventions support a non-single VLAN multicast implementation device. For the implementation scheme, refer to the description of the multicast implementation method for supporting the non-single VLAN of the present invention, and details are not described herein again.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be accomplished by instructions to the associated hardware, which may be stored in a computer readable storage medium, such as a read only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

While the preferred embodiments of the present invention have been disclosed for purposes of illustration, those skilled in the art will recognize that various modifications, additions and substitutions are possible, and the scope of the invention should not be limited to the embodiments described above.

Industrial applicability

The technical solution of the present invention solves the problem that the multicast method in the prior art does not support multicasting in a non-single VLAN environment such as a supervlan, and can be non-single on a supervlan interface, a VLAN range sub-interface, a VLAN QinQ range sub-interface, and the like. In a VLAN environment, multicast data traffic is multicast to the receiver by sending the multicast data traffic to the receiver through the Layer 2 interface created by the network layer to the Layer 2 VLAN and physical port corresponding to the receiver of the multicast data.

Claims

Claim

A multicast implementation method for supporting a non-single virtual local area network (VLAN) VLAN, comprising: running a multicast protocol on a network layer, running a multicast snooping snooping on a link layer; creating a package or aggregation of two or more VLANs Three-layer interface;

The multicast implementation method for supporting a non-single VLAN according to claim 1, wherein the Layer 3 interface is a supervlan interface.

The multicast implementation method for supporting a non-single VLAN according to claim 1, wherein the Layer 3 interface is a VLAN range sub-interface.

The multicast implementation method for supporting a non-single VLAN according to claim 1, wherein the Layer 3 interface is a VLAN QinQ range sub-interface.

The multicast implementation method for supporting a non-single VLAN according to claim 1, wherein the network layer is responsible for interacting with an upstream protocol and directing multicast data traffic to a Layer 3 interface for receiving upstream multicast data traffic. The link layer is responsible for the management of the downstream user and the VLAN and physical port corresponding to the specified user.

The multicast implementation method for supporting a non-single VLAN according to claim 5, wherein the downstream device of the interface sends a general query message.

The multicast implementation method for supporting a non-single VLAN according to any one of claims 1 to 6, wherein the multicast data traffic is sent by using an integrated entry forwarding or a secondary lookup table forwarding. To the recipient of the multicast data.

8. A multicast implementation apparatus for supporting a non-single virtual local area network (VLAN) VLAN, comprising: a protocol operation module, configured to run a multicast protocol on a network layer, and multicast snooping snooping Running on the link layer;

The multicast implementation device for supporting a non-single VLAN according to claim 8, wherein the Layer 3 interface is a supervlan interface.

The multicast implementation device for supporting a non-single VLAN according to claim 8, wherein the Layer 3 interface is a VLAN range sub-interface or a VLAN QinQ range sub-interface.