CN110391919B

CN110391919B - Multicast traffic forwarding method and device, and electronic device

Info

Publication number: CN110391919B
Application number: CN201910628921.5A
Authority: CN
Inventors: 吴带成; 岳林
Original assignee: Hangzhou DPTech Technologies Co Ltd
Current assignee: Hangzhou DPTech Technologies Co Ltd
Priority date: 2019-07-12
Filing date: 2019-07-12
Publication date: 2021-03-23
Anticipated expiration: 2039-07-12
Also published as: CN110391919A

Abstract

The application provides a multicast traffic forwarding method, a multicast traffic forwarding device, an electronic device and a machine-readable storage medium. In the application, a plurality of multicast grouping messages respectively corresponding to a plurality of multicast receiving ends are received; the multicast group adding message at least comprises a multicast IP address and a VLAN identification; based on the multicast grouping messages, generating corresponding cross-VLAN two-layer forwarding table entries in a preset cross-VLAN two-layer forwarding table; receiving multicast traffic from the multicast source forwarded via the three-layer network device; based on the cross-VLAN two-layer forwarding table, the multicast flow is forwarded to the corresponding target multicast receiving end, and therefore resource consumption of network equipment and network maintenance cost of users are reduced.

Description

Multicast traffic forwarding method and device, and electronic device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a multicast traffic forwarding method and apparatus, an electronic device, and a machine-readable storage medium.

Background

Multicast, which is a one-to-many network protocol for data distribution; based on multicast, only one message which is required to be sent by a multicast source in a network can be realized, the message is copied into N parts through network equipment and is distributed to a plurality of multicast receiving ends which are added into a multicast group corresponding to the multicast, and other hosts which are not added into the multicast group cannot receive the message.

VLAN (Virtual Local Area Network), a Network protocol operating at layers 2 and 3 of the OSI (Open System Interconnection) model. Based on VLANs, devices within a large two-tier Network in a Local Area Network (Local Area Network) can be logically divided (note that they are not physically divided) into a number of smaller two-tier networks (or smaller Local Area networks LANs); each small two-layer network corresponds to one VLAN, and is indicated and distinguished by different VLAN IDs (namely VLAN identifications), and the broadcast domains of the two-layer networks in which the devices in different VLANs are positioned are mutually isolated, so that service isolation can be realized and broadcast storms can be effectively avoided.

Disclosure of Invention

The application provides a multicast flow forwarding method, which is applied to two-layer network equipment in a multicast network, wherein the multicast network further comprises a multicast source, three-layer network equipment and a plurality of multicast receiving ends; wherein, a plurality of said multicast receiving terminals access to said two-layer network device, said multicast source access to said three-layer network device, said multicast source is connected with said multicast receiving terminal through network via said two-layer network device and said three-layer network device, said method comprises:

receiving a plurality of multicast grouping messages respectively corresponding to the plurality of multicast receiving ends; the multicast group adding message at least comprises a multicast IP address and a VLAN identification;

based on the multicast grouping messages, generating corresponding cross-VLAN two-layer forwarding table entries in a preset cross-VLAN two-layer forwarding table;

receiving multicast traffic from the multicast source forwarded via the three-layer network device;

and forwarding the multicast flow to a corresponding target multicast receiving end based on the cross-VLAN two-layer forwarding table.

Optionally, the generating, based on the multiple multicast group adding packets, a corresponding cross-VLAN two-layer forwarding table entry in a preset cross-VLAN two-layer forwarding table includes:

comparing whether a plurality of multicast IP addresses and a plurality of VLAN identifications which are respectively corresponding to the plurality of multicast grouping messages are the same or not;

if the multicast IP addresses are the same and the VLAN identifications are different, electing to determine target multicast VLAN identifications corresponding to the VLAN identifications;

and generating a cross-VLAN two-layer forwarding table entry corresponding to the target multicast VLAN identification.

Optionally, the network device in layer two supports IGMP Snooping, and the electing determines the target multicast VLAN id corresponding to the VLAN ids, including:

counting the number of VLANs corresponding to the VLAN identifications as a first VLAN number;

counting the number of VLANs corresponding to the VLAN interfaces of the two-layer network equipment which start IGMP Snooping as the number of second VLANs; the number of the second VLANs is larger than that of the first VLANs;

taking the difference value of the number of the second VLAN and the number of the first VLAN as a reference multicast VLAN mark;

if the reference multicast VLAN identification is in the VLAN identifications, the reference multicast VLAN identification is elected as the target multicast VLAN identification; otherwise, selecting the VLAN identifier with the minimum difference value with the reference multicast VLAN identifier from the plurality of VLAN identifiers as the target multicast VLAN identifier.

Optionally, the cross-VLAN two-layer forwarding table at least includes a multicast VLAN identifier, a user VLAN identifier group, a multicast MAC address, and an ingress port group, and the generating a cross-VLAN two-layer forwarding table entry corresponding to the target multicast VLAN identifier includes:

calculating a corresponding target multicast MAC address based on the plurality of multicast IP addresses;

acquiring a plurality of target input ports corresponding to the plurality of multicast group-adding messages respectively;

and in the cross-VLAN two-layer forwarding table, respectively storing the target multicast VLAN identification, the VLAN identifications, the target multicast MAC address and the target input ports as corresponding table entries in the cross-VLAN two-layer forwarding table.

Optionally, after generating the cross-VLAN two-layer forwarding entry corresponding to the target multicast VLAN identifier, the method further includes:

if a plurality of new multicast group adding messages carrying the new VLAN identifications are received; wherein, the multicast IP address of the new multicast group adding messages is the same as the multicast IP address of the cross-VLAN two-layer forwarding table entry corresponding to the target multicast VLAN identification;

and updating the new VLAN identification and the corresponding input port thereof into the user VLAN identification group of the cross-VLAN two-layer forwarding table entry corresponding to the target multicast VLAN identification.

Optionally, the forwarding the multicast traffic to a corresponding target multicast receiving end based on the cross-VLAN two-layer forwarding table includes:

acquiring a flow multicast MAC address corresponding to the multicast flow;

using the flow multicast MAC address as a search index, and searching whether a matched cross-VLAN two-layer forwarding table item matched with the flow multicast MAC address exists in the cross-VLAN two-layer forwarding table;

if the forwarding table entries exist, forwarding the multicast traffic to the corresponding target multicast receiving ends respectively based on the port group of the matched cross-VLAN two-layer forwarding table entry.

Optionally, the method further includes:

and if the matched cross-VLAN two-layer forwarding table item matched with the flow multicast MAC address does not exist, forwarding the multicast flow to the target multicast receiving end based on an IGMP Snooping forwarding table.

The application also provides a multicast flow forwarding device, which is applied to two-layer network equipment in a multicast network, wherein the multicast network further comprises a multicast source, three-layer network equipment and a plurality of multicast receiving ends; wherein, a plurality of multicast receiving terminals access two layer network equipment, the multicast source access three layer network equipment, the multicast source warp two layer network equipment and three layer network equipment, with the multicast receiving terminal links to each other through the network, the device includes:

the receiving module receives a plurality of multicast grouping messages respectively corresponding to the plurality of multicast receiving ends; the multicast group adding message at least comprises a multicast IP address and a VLAN identification;

the generating module generates a corresponding cross-VLAN two-layer forwarding table item in a preset cross-VLAN two-layer forwarding table based on the plurality of multicast grouping messages;

the receiving module further receives multicast traffic forwarded by the three-layer network device from the multicast source;

and the forwarding module forwards the multicast flow to a corresponding target multicast receiving end based on the cross-VLAN two-layer forwarding table.

The application also provides an electronic device, which comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are mutually connected through the bus;

the memory stores machine-readable instructions, and the processor executes the method by calling the machine-readable instructions.

The present application also provides a machine-readable storage medium having stored thereon machine-readable instructions which, when invoked and executed by a processor, implement the above-described method.

Through the embodiment, the method comprises the steps that a plurality of multicast group adding messages are received on the basis of two-layer network equipment; and selecting and generating a target multicast VLAN identification and a corresponding cross-VLAN two-layer forwarding table item thereof based on the plurality of multicast grouping messages, so that the multicast flow is forwarded to a corresponding target multicast receiving end based on the cross-VLAN two-layer forwarding table, and the resource consumption of network equipment and the network maintenance cost of users are reduced.

Drawings

FIG. 1 is a topology diagram of a multicast network provided by an exemplary embodiment;

fig. 2 is a flow chart of a method for forwarding multicast traffic in accordance with an illustrative embodiment;

FIG. 3 is a topology diagram of another multicast network provided by an exemplary embodiment;

fig. 4 is a block diagram of a multicast traffic forwarding apparatus provided in an example embodiment;

fig. 5 is a hardware block diagram of an electronic device according to an exemplary embodiment.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

In order to make those skilled in the art better understand the technical solution in the embodiment of the present application, a brief description will be given below to the related technology of multicast traffic forwarding according to the embodiment of the present application.

Referring to fig. 1, fig. 1 is a topology diagram of a multicast network according to an embodiment of the present application.

The multicast network shown in fig. 1 comprises: a multicast Source (SRC), a three-layer network device (RT1), a two-layer network device (SW1), and a plurality of multicast receivers (H1, H2, H3);

the multicast receiving ends (H1, H2 and H3) are respectively accessed to the two-layer network equipment (SW1) through different VLANs (H1, H2 and H3 which respectively correspond to VLAN 10, VLAN 20 and VLAN 30), the multicast Source (SRC) is accessed to the three-layer network equipment (RT1), and the multicast Source (SRC) is connected and communicated through the three-layer network equipment (RT1) and the two-layer network equipment (SW1) through the network.

As shown in fig. 1, multicast traffic sent by a multicast Source (SRC) is forwarded to a layer-two network device (SW1) via a layer-three network device (RT1), and the layer-two network device (SW1) copies the multicast traffic by 3 copies, and forwards the multicast traffic to

VLANs

10,20, and 30, respectively, and further to multicast receivers H1, H2, and H3 located in

VLANs

10,20, and 30.

On the basis of the networking architecture shown above, the present application aims to provide a technical scheme for generating a target multicast VLAN identifier and a corresponding cross-VLAN two-layer forwarding entry thereof based on a plurality of received multicast group adding messages, and performing multicast traffic forwarding based on the cross-VLAN two-layer forwarding entry.

When the method is realized, the multicast network comprises two-layer network equipment, a multicast source, three-layer network equipment and a plurality of multicast receiving ends; the multicast receiving ends are accessed to the two-layer network equipment, the multicast source is accessed to the three-layer network equipment, and the multicast source is connected with the multicast receiving ends through the network through the two-layer network equipment and the three-layer network equipment.

Further, the two-layer network equipment receives a plurality of multicast grouping messages respectively corresponding to the plurality of multicast receiving ends; the multicast group adding message at least comprises a multicast IP address and a VLAN identification; based on the multicast grouping messages, generating corresponding cross-VLAN two-layer forwarding table entries in a preset cross-VLAN two-layer forwarding table; receiving multicast traffic from the multicast source forwarded via the three-layer network device; and forwarding the multicast flow to a corresponding target multicast receiving end based on the cross-VLAN two-layer forwarding table.

In the scheme, a plurality of multicast grouping messages are received on the basis of two-layer network equipment; and selecting and generating a target multicast VLAN identification and a corresponding cross-VLAN two-layer forwarding table item thereof based on the plurality of multicast grouping messages, so that the multicast flow is forwarded to a corresponding target multicast receiving end based on the cross-VLAN two-layer forwarding table, and the resource consumption of network equipment and the network maintenance cost of users are reduced.

The present application is described below with reference to specific embodiments and specific application scenarios.

Referring to fig. 2, fig. 2 is a flowchart of a multicast traffic forwarding method according to an embodiment of the present application, where the method is applied to a two-layer network device in a multicast network, and the multicast network further includes a multicast source, a three-layer network device, and a plurality of multicast receivers; wherein, said several multicast receiving terminals access said two-layer network device, said multicast source access said three-layer network device, said multicast source passes said two-layer network device and said three-layer network device, and said multicast receiving terminal is connected through the network, the above-mentioned method executes the following steps:

step 202, receiving a plurality of multicast grouping messages respectively corresponding to the plurality of multicast receiving ends; the multicast group adding message at least comprises a multicast IP address and a VLAN identification.

And step 204, based on the multicast grouping messages, generating corresponding cross-VLAN two-layer forwarding table entries in a preset cross-VLAN two-layer forwarding table.

And step 206, receiving the multicast traffic forwarded by the three-layer network device from the multicast source.

And step 208, forwarding the multicast traffic to a corresponding target multicast receiving end based on the cross-VLAN two-layer forwarding table.

In this specification, the above-mentioned two-layer network device refers to any network device that supports OSI two-layer protocols including multicast.

For example, in practical applications, the two-layer network device may specifically include a switch supporting a two-layer multicast protocol and a VLAN protocol, a router supporting a two-layer multicast protocol and a VLAN protocol, a firewall supporting a two-layer multicast protocol and a VLAN protocol, and the like.

In an embodiment shown, the two-layer network device supports IGMP Snooping (Internet Group Management Protocol Snooping);

the IGMP Snooping refers to a mechanism of multicast constraint running on a layer two network device, and is used to manage and control multicast groups, and establish a mapping relationship between an ingress port corresponding to the multicast group adding message and the multicast MAC address.

In this specification, the three-layer network device refers to any network device that supports OSI two-layer and three-layer protocols including multicast.

For example, in practical applications, the three-layer network device may specifically include a switch supporting a two-layer multicast protocol, a VLAN protocol, and a three-layer routing protocol, a router supporting a two-layer multicast protocol, a VLAN protocol, and a three-layer routing protocol, a firewall supporting a two-layer multicast protocol, a VLAN protocol, and a three-layer routing protocol, and the like.

In this specification, the multicast source may include any device that is connected to the three-layer network device and is capable of generating multicast traffic.

For example, in practical applications, the multicast source may specifically include a PC, a server, a mobile terminal, a cluster, a source station playing radio and television programs, a source station playing the internet, and the like, where multicast traffic may occur.

In this specification, the multicast receivers may include any devices that are connected to the two-layer network device and can receive multicast traffic.

For example, in practical applications, the multicast receiving ends may specifically include a plurality of PCs, servers, mobile terminals, clusters, and the like that can receive multicast traffic.

In this specification, the multicast traffic includes a plurality of multicast packets sent by the multicast source, in any data format and content, and the plurality of multicast receivers are located in a plurality of VLANs based on multicast.

For example, in practical applications, please refer to fig. 1, the multicast traffic may be an audio stream, a video stream, an audio/video stream, etc. of a multicast source SRC that sends multicast-based multicast receivers (H1, H2, H3) located in multiple VLANs.

In this specification, the multicast network refers to an IP network including the two-layer network device, the three-layer network device, and the plurality of multicast receiving terminals; the multicast receiving ends are accessed to the two-layer network equipment, the multicast source is accessed to the three-layer network equipment, and the multicast source is connected with the multicast receiving ends through the network and communicates with the multicast receiving ends through the two-layer network equipment and the three-layer network equipment.

For example, please refer to fig. 1 for the multicast network, and refer to the foregoing description for the detailed description of the multicast network shown in fig. 1, which is not repeated herein.

In this specification, the multicast source transmits the multicast traffic in the multicast network, and the two-layer network device and the three-layer network device in the multicast network trigger generation of a multicast group corresponding to the multicast traffic.

For example, please refer to fig. 1 in implementation, if the multicast source SRC sends multicast traffic to the multicast IP address 224.100.1.1 in the multicast network, a multicast group corresponding to the multicast traffic is triggered to be generated on the two-layer network device SW1 and the three-layer network device RT1, and the address corresponding to the multicast group is also the multicast IP address 224.100.1.1.

In this specification, the multicast group adding messages include a plurality of multicast group adding messages which are respectively sent by the multicast receiving terminals and added into the same multicast group;

wherein, the multicast group adding message at least comprises a multicast IP address and a VLAN identification;

in implementation, the multicast receiving ends may respectively send multicast group adding messages (join messages) for adding multicast group addresses based on IGMP Snooping.

Continuing the example from the above example, the above multicast group adding messages may include a multicast receiving end H1 located in VLAN 10, a multicast receiving end H2 located in VLAN 20, and a multicast receiving end H3 located in VLAN 30, and 3 multicast group adding messages carrying VLAN identifiers (that is, VLAN IDs) of 10,20, and 30 for the multicast group 224.100.1.1 are respectively initiated to SW1 in VLAN 10, VLAN 20, and VLAN 30.

In this specification, when the multicast receiving ends need to acquire the multicast traffic, the multicast adding packet for adding the multicast group corresponding to the multicast traffic needs to be sent to the two-layer network device first.

Continuing with the example above, please refer to fig. 1, where the multicast receiver H1 located in VLAN 10, the multicast receiver H2 located in VLAN 20, and the multicast receiver H3 located in VLAN 30 initiate the above-mentioned 3 multicast group adding messages for the multicast group 224.100.1.1 to SW1 in VLAN 10, VLAN 20, and VLAN 30, respectively.

In this specification, the two-layer network device receives the multicast grouping messages from the multicast receiving ends respectively corresponding to the multicast receiving ends.

Continuing the example from the above example, SW1 receives the multicast group add messages from multicast receivers H1, H2, and H3, which correspond to 3 multicast groups, respectively.

In this specification, the multicast VLAN id refers to a VLAN id bound to the multicast traffic across a plurality of VLANs on the layer two network device.

In implementation, the multicast VLAN id may be one of a plurality of existing VLAN ids on the layer-two network device, or a VLAN id newly created on the layer-two network device.

Continuing with the above example, the multicast VLAN id may be any one of 10,20, and 30, or a VLAN id (i.e., VLAN 100) newly created on the layer two network device and having a value of 100.

It should be noted that, the VLAN indicated by the VLAN ids configured by the user on the layer two network device is also referred to as "user VLAN", and the VLAN id included in the "user VLAN" is also referred to as "user VLAN id". Such as: VLAN 10, VLAN 20, VLAN 30 are all "customer VLANs", and the corresponding "customer VLAN ids" are 10,20,30, respectively.

In this specification, the user VLAN id group refers to a set of a plurality of "user VLAN ids" corresponding to the multicast traffic across a plurality of VLANs, which are bound to the multicast VLAN id on the two-layer network device.

Continuing with the above example, referring to fig. 1, the user VLAN id group may be any one or more of 10,20, and 30 VLAN id sets in SW1, and is, for example, {10,20, and 30 }.

In this specification, the multicast MAC address refers to a two-layer multicast MAC address corresponding to a multicast IP address carried in the multicast group adding packet.

When the multicast MAC address is realized, the multicast MAC address occupies 48 bits, and is formed by heading a high 24-bit corresponding value of 01005E (hexadecimal) and splicing with a low 24-bit of the multicast IP address (occupying 32 bits).

Continuing the example from the above example, if the multicast IP address carried in the multicast group adding messages is 224.100.1.1, the low-24-bit corresponding to the multicast IP address 224.100.1.1 is "640101" (hexadecimal), and the multicast MAC address corresponding to the multicast IP address 224.100.1.1 is "01005E 640101".

In this specification, the ingress port group refers to a set of network ports corresponding to the two-layer network device receiving the multicast group-added packet.

Continuing with the above example, if the network ports corresponding to the multicast group-adding packets received from H1, H2, and H3 by the two-layer network device SW1 are divided into ports P1, P2, and P3, the ingress port group is { P1, P2, and P3 }.

In this specification, the cross-VLAN two-layer forwarding table refers to a forwarding table on the two-layer network device, which is used for performing two-layer forwarding on multicast traffic that spans multiple VLANs;

the cross-VLAN two-layer forwarding table at least comprises the multicast VLAN identification, the user VLAN identification group, the multicast MAC address and the input port group.

Continuing with the above example, please refer to the example shown in table 1 for the cross-VLAN two-layer forwarding table

TABLE 1

In this specification, further, the two-layer network device generates a corresponding cross-VLAN two-layer forwarding entry in a preset cross-VLAN two-layer forwarding table based on the multiple multicast group addition packets.

Continuing the example from the above example, the two-layer network device SW1 generates a corresponding cross-VLAN two-layer forwarding entry in the cross-VLAN two-layer forwarding table based on the multiple multicast group adding messages from H1, H2, and H3, and please refer to the entry corresponding to the forwarding entry number 1 shown in table 1.

In this specification, the target multicast VLAN id refers to a multicast VLAN id that is selected by the two-layer network device based on the multiple multicast group adding messages.

Continuing the example from the above example, please refer to fig. 1, where the target multicast VLAN id may be any one of 10,20, and 30 or other values.

In an embodiment shown in the above, in the generating process of the cross-VLAN two-layer forwarding entry, the two-layer network device compares whether a plurality of multicast IP addresses and a plurality of VLAN identifiers corresponding to the plurality of multicast group-added packets are the same.

Continuing the example from the above example, the two-layer network device SW1 compares the 3 multicast group adding packets from H1, H2, and H3, and checks whether the multicast IP addresses corresponding to the 3 multicast group adding packets are the same, and whether the VLAN identifiers carried by the 3 multicast group adding packets are the same.

In this specification, if the plurality of multicast IP addresses are all the same and the plurality of VLAN tags are different, the two-layer network device elects to determine the target multicast VLAN tag corresponding to the plurality of VLAN tags.

Continuing with the above example, if the two-layer network device SW1 compares the 3 multicast group adding packets from H1, H2, and H3, and checks that the multicast IP addresses corresponding to the 3 multicast group adding packets are all the same (all 224.100.1.1), and that the VLAN identifiers carried by the 3 multicast group adding packets are different (the VLAN identifiers include 10,20, and 30), SW1 elects to determine the target multicast VLAN identifier corresponding to the VLAN identifiers.

In this specification, the plurality of VLAN identifiers refer to a set of VLAN identifiers included in a plurality of multicast grouping messages corresponding to the target multicast VLAN identifier.

Continuing to exemplify the above example, the plurality of VLAN identifiers include a VLAN identifier set included in the plurality of multicast group adding messages, where the multicast IP addresses corresponding to the target multicast VLAN identifiers are all the same and the plurality of VLAN identifiers are different: {10,20,30 }.

In this specification, the first number of VLANs means the number of VLANs corresponding to the plurality of VLAN tags.

Continuing with the above example, the first number of VLANs is set as {10,20,30} of the VLAN identifiers, and the set corresponds to VLAN number 3.

In an embodiment shown, in the process of electing the target multicast VLAN identifier, the two-layer network device counts the number of VLANs corresponding to the VLAN identifiers as a first VLAN number;

continuing the example with the above example, the two-layer network device counts the number of VLANs 3 corresponding to the VLAN ids, that is, the number of the first VLAN is 3.

In this specification, the number of the second VLANs refers to the number of VLANs corresponding to the VLAN interface where IGMP Snooping has been enabled by the two-layer network device; the number of the second VLANs is larger than that of the first VLANs;

continuing to exemplify the above example, the VLAN interfaces of the two-layer network device that have enabled IGMP Snooping include, in addition to VLAN 10, VLAN 20, and VLAN 30 that have enabled IGMP Snooping, also have enabled IGMP Snooping at VLAN interfaces such as VLAN 40, VLAN 50, and VLAN 60, that is, the VLAN set corresponding to the VLAN interfaces of the two-layer network device that have enabled IGMP Snooping is {10,20,30, 40, 50, and 60}, where the second VLAN number is the VLAN number corresponding to the VLAN set, and the set corresponds to VLAN number 6; the number (6) of the second VLAN is larger than the number (3) of the first VLAN, namely before the multicast VLAN is started, IGMP Snooping is started.

In this specification, the reference multicast VLAN id refers to a reference VLAN id for determining the target multicast VLAN id;

and the reference multicast VLAN identification is the difference value between the number of the second VLAN and the number of the first VLAN.

Continuing the example from the above example, the reference multicast VLAN id may be a difference between the second VLAN number (6) and the first VLAN number (3), that is, the reference multicast VLAN id is 3. Of course, the above example is only one of several possible cases, and in another possible case, if the number of the second VLANs is 20 and the number of the first VLANs is 10, the reference multicast VLAN id is 10.

In this specification, further, after the layer two network device obtains the reference multicast VLAN id through calculation, the layer two network device determines the target multicast VLAN id based on the reference multicast VLAN id.

In one embodiment, if the reference multicast VLAN id is included in the plurality of VLAN ids, the layer two network device elects the reference multicast VLAN id as the target multicast VLAN id.

Taking the reference multicast VLAN id as 10, and continuing the above example, if the reference multicast VLAN id (10) is one of the VLAN ids {10,20, and 30}, then 10 (the reference multicast VLAN id) is used as the target multicast VLAN id.

In another embodiment, if the reference multicast VLAN id is not among the VLAN ids, the layer two network device selects a VLAN id having a smallest difference from the reference multicast VLAN id among the VLAN ids as the target multicast VLAN id.

Taking the reference multicast VLAN id 28 as above, and continuing the above example, if the reference multicast VLAN id (28) is not among the VLAN ids {10,20,30}, and if the difference between 30 and 28 is the smallest among the VLAN ids {10,20,30}, then 30 is selected as the target multicast VLAN id from {10,20,30 }.

It should be noted that, compared with the existing implementation of multicast VLAN, the multicast VLAN identifier (the target multicast VLAN identifier) is automatically generated by the two-layer network device through election, and does not need manual pre-configuration, thereby reducing the network maintenance cost of the user.

In this specification, after the target multicast VLAN identifier is elected and determined, the two-layer network device generates a cross-VLAN two-layer forwarding entry corresponding to the target multicast VLAN identifier.

In one illustrated embodiment, the layer two network device calculates the corresponding target multicast MAC address based on the plurality of multicast IP addresses.

Continuing the example from the above example, the SW1 calculates the corresponding target multicast MAC address to be 01005E640101 based on the multiple multicast IP addresses (the multiple multicast IP addresses are all the same and the corresponding multicast IP addresses are corresponding to the multiple VLANs with different identifiers) 224.100.1.1, and the specific multicast IP address and multicast MAC address calculation method is described in the foregoing "multicast MAC address", and is not described again here.

In this specification, further, the two-layer network device obtains a plurality of target ingress ports corresponding to the plurality of multicast group-added packets, respectively.

Continuing the example, the SW1 obtains a plurality of target ingress ports P1, P2, and P3 corresponding to the plurality of multicast group-added packets, respectively, that is, the plurality of target ingress ports include P1, P2, and P3.

In this specification, further, the two-layer network device stores the target multicast VLAN id, the VLAN ids, the target multicast MAC address, and the target ingress ports in the cross-VLAN two-layer forwarding table as corresponding entries in the cross-VLAN two-layer forwarding table, respectively.

Taking the target multicast VLAN id as 10, continuing with the above example, SW1 stores the target multicast VLAN id (10), the VLAN ids {10,20, and 30}, the target multicast MAC address "01005E 640101", and the target entry ports { P1, P2, and P3} in the cross-VLAN two-layer forwarding table in a corresponding entry, which is shown as forwarding entry number 1 in table 1.

It should be noted that the two-layer network device can implement cross-VLAN multicast traffic forwarding only based on one multicast VLAN id and its corresponding entry in the cross-VLAN two-layer forwarding table, and does not need to configure multiple association policies compared with the existing implementation of multicast VLANs; in addition, the ingress port of the cross-VLAN two-layer forwarding table also does not need to meet the requirement that the ingress port must be configured as a hybrid type in the existing implementation of the multicast VLAN, thereby reducing the resource consumption of network equipment.

Referring to fig. 3, fig. 3 is a topology diagram of another multicast network according to an embodiment of the present application.

Fig. 3 is a variation on fig. 1, and fig. 3 differs from fig. 1 in that: fig. 3 is a view compared with fig. 1, in which a multicast receiving end H4 located on VLAN 40 is added.

In this specification, the new multicast group adding packets refer to a plurality of multicast group adding packets carrying new VLAN identifiers to be added to a multicast group corresponding to the target multicast VLAN identifier;

and the multicast IP address of the new multicast adding group messages is the same as the multicast IP address of the cross-VLAN two-layer forwarding table entry corresponding to the target multicast VLAN identification.

Continuing the example from the above example, please refer to fig. 3, where the new multicast group adding messages are multicast receiving end H4, and the multicast IP address 224.100.1.1 of the multicast receiving end H4 carries VLAN 40 (new VLAN id); wherein, the multicast IP address of the new multicast group adding message is the same as the multicast IP address corresponding to the target multicast VLAN identifier 10 shown in table 1, and both are 224.100.1.1; the new VLAN id is also 40.

In an embodiment shown, after the cross-VLAN two-layer forwarding table corresponding to the target multicast VLAN id is generated, and after receiving the new multicast group packets, the two-layer network device updates the new VLAN id and the corresponding ingress port to the user VLAN id group corresponding to the cross-VLAN two-layer forwarding table corresponding to the target multicast VLAN id.

Continuing the example from the above example, after receiving the new multicast group packets, the SW1 updates 40 (the new VLAN id) and the corresponding ingress port P4 to the user VLAN id group of the cross-VLAN two-layer forwarding entry (as shown in table 1) corresponding to 10 (the target multicast VLAN id), and then the updated 10 (the target multicast VLAN id) corresponds to the cross-VLAN two-layer forwarding entry, please refer to the example shown in table 2 below:

TABLE 2

As shown in table 2, 40 (the new VLAN id) is added to the user VLAN id group corresponding to the forwarding entry number 1, and P4 (the new VLAN id corresponds to the ingress port) is added to the ingress port group corresponding to the forwarding entry number 1.

In this specification, after the cross-VLAN two-layer forwarding entry corresponding to the target multicast VLAN id is generated, the two-layer network device receives the multicast traffic from the multicast source and forwarded via the three-layer network device.

Continuing the example from the above example, after a cross-VLAN two-layer forwarding entry (as shown by table 2 forwarding entry number 1) corresponding to 10 (the above target multicast VLAN id) is generated, SW1 receives multicast traffic sent to the multicast IP address 224.100.1.1 from the multicast source SRC by forwarding through RT 1.

In this specification, further, the two-layer network device forwards the multicast traffic to a corresponding target multicast receiving end based on the cross-VLAN two-layer forwarding table.

In an embodiment shown in the above, the layer two network device obtains a traffic multicast MAC address corresponding to the multicast traffic.

Continuing the example following the above example, the above two-layer network device obtains the multicast MAC address of the corresponding traffic through the multicast IP address calculation of the multicast traffic, which is 01005E 640101.

In an embodiment shown in the present invention, the two-layer network device uses the traffic multicast MAC address as a lookup index, and searches whether a matching cross-VLAN two-layer forwarding entry matching the traffic multicast MAC address exists in the cross-VLAN two-layer forwarding table; if yes, based on the port group of the matched cross-VLAN two-layer forwarding table entry, the multicast flow is respectively forwarded to the corresponding target multicast receiving end.

Continuing the example from the above example, the SW1 uses 01005E640101 (the traffic multicast MAC address) as a lookup index to lookup whether there is a matching cross-VLAN two-layer forwarding entry matching the traffic multicast MAC address in the cross-VLAN two-layer forwarding table shown in table 2; if there is a matching cross-VLAN two-layer forwarding entry (as shown in table 2 forwarding entry number 1), based on the ingress port set { P1, P2, P3, P4} of the matching cross-VLAN two-layer forwarding entry, the multicast traffic is forwarded to target multicast receiving ends H1, H2, H3, H4 respectively corresponding to P1, P2, P3, P4.

In another embodiment shown, the two-layer network device uses the traffic multicast MAC address as a lookup index, and searches whether a matching cross-VLAN two-layer forwarding entry matching the traffic multicast MAC address exists in the cross-VLAN two-layer forwarding table; and if the matched cross-VLAN two-layer forwarding table item matched with the flow multicast MAC address does not exist, forwarding the multicast flow to the target multicast receiving end based on an IGMP Snooping forwarding table.

Continuing the example from the above example, the SW1 uses 01005E640101 (the traffic multicast MAC address) as a lookup index to lookup whether there is a matching cross-VLAN two-layer forwarding entry matching the traffic multicast MAC address in the cross-VLAN two-layer forwarding table shown in table 2; if there is no matching cross-VLAN two-layer forwarding entry, the two-layer network device forwards the multicast traffic to the target multicast receiving end based on an IGMP Snooping forwarding table, and specifically, the multicast traffic is based on an IGMP Snooping forwarding process, please refer to the existing IGMP Snooping forwarding principle description, which is not described herein again.

In the technical scheme, a plurality of multicast grouping messages are received on the basis of two-layer network equipment; and selecting and generating a target multicast VLAN identification and a corresponding cross-VLAN two-layer forwarding table item thereof based on the plurality of multicast grouping messages, so that the multicast flow is forwarded to a corresponding target multicast receiving end based on the cross-VLAN two-layer forwarding table, and the resource consumption of network equipment and the network maintenance cost of users are reduced.

Fig. 4 is a block diagram of a multicast traffic forwarding apparatus according to an exemplary embodiment of the present application. Corresponding to the above method embodiment, the present application also provides an embodiment of a multicast traffic forwarding apparatus, where the apparatus is applied to a two-layer network device in a multicast network, and the multicast network further includes a multicast source, a three-layer network device, and a plurality of multicast receiving terminals; wherein, the plurality of multicast receiving terminals access the two-layer network device, the multicast source accesses the three-layer network device, the multicast source is connected to the multicast receiving terminals via the two-layer network device and the three-layer network device via the network, please refer to a multicast traffic forwarding apparatus 40 illustrated in fig. 4, the apparatus includes:

In this embodiment, the generating module further:

In this embodiment, the layer-two network device supports IGMP Snooping, and the generating module further:

In this embodiment, the cross-VLAN two-layer forwarding table at least includes a multicast VLAN identifier, a user VLAN identifier group, a multicast MAC address, and an ingress port group, and the generating module further:

In this embodiment, after the cross-VLAN two-layer forwarding entry corresponding to the target multicast VLAN identifier is generated, the method further includes:

the receiving module further receives a plurality of new multicast group adding messages carrying the new VLAN identifications; wherein, the multicast IP address of the new multicast group adding messages is the same as the multicast IP address of the cross-VLAN two-layer forwarding table entry corresponding to the target multicast VLAN identification;

the generating module further updates the new VLAN identification and the corresponding input port thereof to the user VLAN identification group of the cross-VLAN two-layer forwarding table entry corresponding to the target multicast VLAN identification.

In this embodiment, the forwarding module further forwards the multicast traffic to a corresponding target multicast receiving end based on the cross-VLAN two-layer forwarding table, and:

acquiring a flow multicast MAC address corresponding to the multicast flow;

In this embodiment, the forwarding module further:

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, wherein the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.

The systems, devices, modules or modules illustrated in the above embodiments may be implemented by a computer chip or an entity, or by an article of manufacture with certain functionality. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

The embodiment of the multicast traffic forwarding apparatus of the present application may be applied to the electronic device shown in fig. 5. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is a machine executable instruction formed by reading a corresponding computer program instruction in a machine readable storage medium through a processor of the electronic device where the device is located and then running the computer program instruction. In terms of hardware, as shown in fig. 5, the present application is a hardware structure diagram of an electronic device where a multicast traffic forwarding apparatus is located, and except for the processor, the communication interface, the bus, and the machine-readable storage medium shown in fig. 5, the electronic device where the apparatus is located in the embodiment may also include other hardware according to an actual function of the electronic device, which is not described again.

Correspondingly, an embodiment of the present application further provides a hardware structure of an electronic device of the apparatus shown in fig. 4, please refer to fig. 5, and fig. 5 is a schematic diagram of the hardware structure of the electronic device provided in the embodiment of the present application. The apparatus comprises: a communication interface 501, a processor 502, a machine-readable storage medium 503, and a bus 504; the communication interface 501, the processor 502 and the machine-readable storage medium 503 are configured to communicate with each other via a bus 504. The communication interface 501 is used for performing network communication. The processor 502 may be a Central Processing Unit (CPU), and the processor 502 may execute machine-readable instructions stored in the machine-readable storage medium 503 to implement the methods described above.

The machine-readable storage medium 503 referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: volatile memory, non-volatile memory, or similar storage media. In particular, the machine-readable storage medium 503 may be a RAM (random Access Memory), a flash Memory, a storage drive (e.g., a hard disk drive), a solid state disk, any type of storage disk (e.g., a compact disk, a DVD, etc.), or similar storage medium, or a combination thereof.

To this end, the description of the hardware configuration shown in fig. 5 is completed.

Furthermore, the present application also provides a machine-readable storage medium, such as machine-readable storage medium 503 in fig. 5, including machine-executable instructions, which can be executed by processor 502 in the data processing apparatus to implement the data processing method described above.

The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.

The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims

1. A multicast flow forwarding method is characterized in that the method is applied to two-layer network equipment in a multicast network, and the multicast network further comprises a multicast source, three-layer network equipment and a plurality of multicast receiving ends; wherein, a plurality of said multicast receiving terminals access to said two-layer network device, said multicast source access to said three-layer network device, said multicast source is connected with said multicast receiving terminal through network via said two-layer network device and said three-layer network device, said method comprises:

generating a cross-VLAN two-layer forwarding table entry corresponding to the target multicast VLAN identification in a preset cross-VLAN two-layer forwarding table;

and forwarding the multicast flow to a corresponding target multicast receiving end based on a cross-VLAN two-layer forwarding table corresponding to the target multicast VLAN identification.

2. The method of claim 1, wherein the layer two network device supports IGMP Snooping, and wherein the electing to determine the target multicast VLAN id corresponding to the VLAN ids comprises:

3. The method of claim 1, wherein the cross-VLAN two-layer forwarding table at least comprises a multicast VLAN id, a user VLAN id group, a multicast MAC address, and an ingress port group, and wherein the generating a cross-VLAN two-layer forwarding table entry corresponding to the target multicast VLAN id comprises:

4. The method of claim 3, wherein after the generating of the cross-VLAN two-layer forwarding entry corresponding to the target multicast VLAN identifier, further comprising:

5. The method of claim 3, wherein forwarding the multicast traffic to a corresponding target multicast receiver based on the cross-VLAN two-layer forwarding table comprises:

acquiring a flow multicast MAC address corresponding to the multicast flow;

6. The method of claim 5, further comprising:

7. A multicast flow forwarding device is characterized in that the device is applied to two-layer network equipment in a multicast network, and the multicast network further comprises a multicast source, three-layer network equipment and a plurality of multicast receiving ends; wherein, a plurality of multicast receiving terminals access two layer network equipment, the multicast source access three layer network equipment, the multicast source warp two layer network equipment and three layer network equipment, with the multicast receiving terminal links to each other through the network, the device includes:

the generating module is used for comparing whether a plurality of multicast IP addresses and a plurality of VLAN identifications which are respectively corresponding to the plurality of multicast grouping messages are the same or not; if the multicast IP addresses are the same and the VLAN identifications are different, electing to determine target multicast VLAN identifications corresponding to the VLAN identifications; generating a cross-VLAN two-layer forwarding table entry corresponding to the target multicast VLAN identification in a preset cross-VLAN two-layer forwarding table;

and the forwarding module forwards the multicast flow to a corresponding target multicast receiving end based on a cross-VLAN two-layer forwarding table corresponding to the target multicast VLAN identification.

8. An electronic device is characterized by comprising a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;

the memory has stored therein machine-readable instructions, the processor executing the method of any of claims 1 to 6 by calling the machine-readable instructions.

9. A machine-readable storage medium having stored thereon machine-readable instructions which, when invoked and executed by a processor, carry out the method of any of claims 1 to 6.