Multicast traffic forwarding method, device and computer equipment

Abstract

The present application relates to a multicast traffic forwarding method, apparatus and computer equipment. The method includes: receiving traffic source data corresponding to the traffic to be forwarded, and traffic destination data corresponding to the traffic to be forwarded; the traffic source data is sent by the first forwarding gateway corresponding to the traffic generating end; the traffic destination data is sent by the first forwarding gateway corresponding to the traffic receiving end; the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment; based on the traffic source data and the traffic destination data, a traffic forwarding path corresponding to the traffic to be forwarded is generated; based on the traffic forwarding path, the traffic to be forwarded is forwarded and controlled. By adopting this method, when the traffic generating end is deployed in the cloud environment, and the multicast controller is deployed in the cloud environment, on-demand traffic forwarding between the traffic generating end and the traffic receiving end can be achieved.

Description

Technical Field

[0001] The present application relates to the field of network communication technology, and in particular to a multicast traffic forwarding method, apparatus, and computer equipment. Background Art

[0002] With the widespread adoption of cloud computing, the multicast service architecture of traditional switching and routing networks faces significant challenges in cloud environments. Traditional multicast transmission relies on Layer 2 and Layer 3 devices for data distribution, but it is no longer able to meet the dynamic business demands of the cloud era in terms of multi-tenant elastic scalability, link resource utilization, and network convergence speed.

[0003] Especially when some hosts in the off-cloud Internet Data Center (IDC) are migrated to the cloud, multicast services need to support both intra-cloud forwarding and extra-cloud detours, forming complex hybrid multicast scenarios, including multicast sources outside / inside the cloud, receivers distributed inside and outside the cloud, or across virtual private clouds (VPCs), and other situations.

[0004] In scenarios where the multicast source is outside the cloud and the receivers exist both inside and outside the cloud, there is an urgent need to achieve intelligent on-demand distribution of multicast traffic inside and outside the cloud without reconstructing the existing network. Summary of the Invention

[0005] Based on this, it is necessary to provide a multicast traffic forwarding method, device and computer equipment to address the above technical problems, which can realize on-demand forwarding of traffic between the traffic generation end and the traffic receiving end when the traffic generation end is deployed in an environment outside the cloud and the multicast controller is deployed in an environment within the cloud.

[0006] In a first aspect, the present application provides a multicast traffic forwarding method, applied to a multicast controller, comprising:

[0007] Receive traffic source data corresponding to the traffic to be forwarded, and traffic destination data corresponding to the traffic to be forwarded; the traffic source data is sent by the first forwarding gateway corresponding to the traffic generating end; the traffic destination data is sent by the first forwarding gateway corresponding to the traffic receiving end; the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end, and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the off-cloud environment;

[0008] Generate the traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and traffic destination data;

[0009] Based on the traffic forwarding path, forwarding control is performed on the traffic to be forwarded.

[0010] In one embodiment, the traffic source data includes first identification information of a traffic generating end and second identification information of a first forwarding gateway corresponding to the traffic generating end; the traffic destination data includes third identification information of a traffic receiving end and fourth identification information of a first forwarding gateway corresponding to the traffic receiving end; accordingly, generating a traffic forwarding path corresponding to the to-be-forwarded traffic based on the traffic source data and the traffic destination data includes:

[0011] Generate a traffic output path according to the first identification information and the second identification information;

[0012] generating a traffic receiving path according to the third identification information and the fourth identification information;

[0013] The traffic output path and the traffic receiving path are connected in order to obtain a traffic forwarding path corresponding to the traffic to be forwarded.

[0014] In one of the embodiments, when the traffic receiving end is deployed in a cloud environment, the first forwarding gateway corresponding to the traffic generating end is the same as the first forwarding gateway corresponding to the traffic receiving end;

[0015] In the case where the traffic receiving end is deployed in an off-cloud environment, the first forwarding gateway corresponding to the traffic generating end is communicatively connected to the first forwarding gateway corresponding to the traffic receiving end.

[0016] In one embodiment, forwarding control of traffic to be forwarded is performed based on the traffic forwarding path, including:

[0017] According to the traffic source data, the first forwarding gateway corresponding to the traffic generating end is controlled to obtain the traffic to be forwarded from the traffic generating end, and send the traffic to be forwarded to the first forwarding gateway corresponding to the traffic receiving end;

[0018] According to the traffic destination data, the first forwarding gateway corresponding to the traffic receiving end is controlled to send the traffic to be forwarded to the traffic receiving end.

[0019] In a second aspect, the present application provides a multicast traffic forwarding method, which is applied to a first forwarding gateway corresponding to a traffic generating end, comprising:

[0020] Receive the traffic to be forwarded from the traffic generating end and determine the traffic source data corresponding to the traffic to be forwarded;

[0021] Sending the traffic source data to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and the traffic destination data determined by the first forwarding gateway corresponding to the traffic receiving end, and perform forwarding control on the traffic to be forwarded based on the traffic forwarding path;

[0022] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0023] In a third aspect, the present application provides a multicast traffic forwarding method, which is applied to a first forwarding gateway corresponding to a traffic receiving end, comprising:

[0024] Receive a multicast on-demand request from a traffic receiving end; the multicast on-demand request is used to request the sending of traffic to be forwarded;

[0025] Determine the traffic destination data corresponding to the traffic to be forwarded;

[0026] Sending the traffic destination data to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic destination data and the traffic source data determined by the first forwarding gateway corresponding to the traffic generating end, and perform forwarding control on the traffic to be forwarded based on the traffic forwarding path;

[0027] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0028] In a fourth aspect, the present application further provides a multicast traffic forwarding device, which is deployed in a multicast controller and includes:

[0029] A first receiving module is configured to receive traffic source data corresponding to the traffic to be forwarded, and traffic destination data corresponding to the traffic to be forwarded; the traffic source data is sent by a first forwarding gateway corresponding to the traffic generating end; and the traffic destination data is sent by a first forwarding gateway corresponding to the traffic receiving end; the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end, and the multicast controller are respectively deployed in a cloud environment; and the traffic generating end is deployed in an off-cloud environment;

[0030] A generation module, used to generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and the traffic destination data;

[0031] The forwarding module is used to control the forwarding of the traffic based on the traffic forwarding path.

[0032] In a fifth aspect, the present application further provides a multicast traffic forwarding device, which is deployed at a first forwarding gateway corresponding to a traffic generating end, comprising:

[0033] A first determining module is configured to receive traffic to be forwarded from a traffic generating end and determine traffic source data corresponding to the traffic to be forwarded;

[0034] a first sending module, configured to send traffic source data to a multicast controller, so that the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and traffic destination data determined by a first forwarding gateway corresponding to the traffic receiving end, and performs forwarding control on the traffic to be forwarded based on the traffic forwarding path;

[0035] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0036] In a sixth aspect, the present application further provides a multicast traffic forwarding device, which is deployed at a first forwarding gateway corresponding to a traffic receiving end, comprising:

[0037] The second receiving module is used to receive a multicast on-demand request from a traffic receiving end; the multicast on-demand request is used to request the sending of traffic to be forwarded;

[0038] A second determining module is used to determine the traffic destination data corresponding to the traffic to be forwarded;

[0039] a second sending module, configured to send the traffic destination data to the multicast controller, so that the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic destination data and the traffic source data determined by the first forwarding gateway corresponding to the traffic generating end, and performs forwarding control on the traffic to be forwarded based on the traffic forwarding path;

[0040] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0041] In a seventh aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0042] Receive traffic source data corresponding to the traffic to be forwarded, and traffic destination data corresponding to the traffic to be forwarded; the traffic source data is sent by the first forwarding gateway corresponding to the traffic generating end; the traffic destination data is sent by the first forwarding gateway corresponding to the traffic receiving end; the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end, and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the off-cloud environment;

[0043] Generate the traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and traffic destination data;

[0044] Based on the traffic forwarding path, forwarding control is performed on the traffic to be forwarded.

[0045] In an eighth aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0046] Receive the traffic to be forwarded from the traffic generating end and determine the traffic source data corresponding to the traffic to be forwarded;

[0047] Sending the traffic source data to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and the traffic destination data determined by the first forwarding gateway corresponding to the traffic receiving end, and perform forwarding control on the traffic to be forwarded based on the traffic forwarding path;

[0048] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0049] In a ninth aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0050] Receive a multicast on-demand request from a traffic receiving end; the multicast on-demand request is used to request the sending of traffic to be forwarded;

[0051] Determine the traffic destination data corresponding to the traffic to be forwarded;

[0052] Sending the traffic destination data to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic destination data and the traffic source data determined by the first forwarding gateway corresponding to the traffic generating end, and perform forwarding control on the traffic to be forwarded based on the traffic forwarding path;

[0053] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0054] In a tenth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0055] Receive traffic source data corresponding to the traffic to be forwarded, and traffic destination data corresponding to the traffic to be forwarded; the traffic source data is sent by the first forwarding gateway corresponding to the traffic generating end; the traffic destination data is sent by the first forwarding gateway corresponding to the traffic receiving end; the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end, and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the off-cloud environment;

[0056] Generate the traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and traffic destination data;

[0057] Based on the traffic forwarding path, forwarding control is performed on the traffic to be forwarded.

[0058] In an eleventh aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0059] Receive the traffic to be forwarded from the traffic generating end and determine the traffic source data corresponding to the traffic to be forwarded;

[0060] Sending the traffic source data to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and the traffic destination data determined by the first forwarding gateway corresponding to the traffic receiving end, and perform forwarding control on the traffic to be forwarded based on the traffic forwarding path;

[0061] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0062] In a twelfth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0063] Receive a multicast on-demand request from a traffic receiving end; the multicast on-demand request is used to request the sending of traffic to be forwarded;

[0064] Determine the traffic destination data corresponding to the traffic to be forwarded;

[0065] Sending the traffic destination data to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic destination data and the traffic source data determined by the first forwarding gateway corresponding to the traffic generating end, and perform forwarding control on the traffic to be forwarded based on the traffic forwarding path;

[0066] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0067] In a thirteenth aspect, the present application further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the following steps:

[0068] Receive traffic source data corresponding to the traffic to be forwarded, and traffic destination data corresponding to the traffic to be forwarded; the traffic source data is sent by the first forwarding gateway corresponding to the traffic generating end; the traffic destination data is sent by the first forwarding gateway corresponding to the traffic receiving end; the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end, and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the off-cloud environment;

[0069] Generate the traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and traffic destination data;

[0070] Based on the traffic forwarding path, forwarding control is performed on the traffic to be forwarded.

[0071] In a fourteenth aspect, the present application further provides a computer program product, including a computer program, which, when executed by a processor, implements the following steps:

[0072] Receive the traffic to be forwarded from the traffic generating end and determine the traffic source data corresponding to the traffic to be forwarded;

[0073] Sending the traffic source data to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and the traffic destination data determined by the first forwarding gateway corresponding to the traffic receiving end, and perform forwarding control on the traffic to be forwarded based on the traffic forwarding path;

[0074] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0075] In a fifteenth aspect, the present application further provides a computer program product, including a computer program, which, when executed by a processor, implements the following steps:

[0076] Receive a multicast on-demand request from a traffic receiving end; the multicast on-demand request is used to request the sending of traffic to be forwarded;

[0077] Determine the traffic destination data corresponding to the traffic to be forwarded;

[0078] Sending the traffic destination data to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic destination data and the traffic source data determined by the first forwarding gateway corresponding to the traffic generating end, and perform forwarding control on the traffic to be forwarded based on the traffic forwarding path;

[0079] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0080] The above-mentioned multicast traffic forwarding method, apparatus, and computer device enable the traffic to be forwarded to be transmitted between the two first forwarding gateways by deploying a first forwarding gateway corresponding to the traffic generating end and a first forwarding gateway corresponding to the traffic receiving end between the traffic generating end and the traffic receiving end, thereby forwarding the traffic to be forwarded from the traffic generating end to the traffic receiving end. Specifically, when the traffic generating end is deployed in an off-cloud environment, the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded by receiving traffic source data sent by the first forwarding gateway corresponding to the traffic generating end and traffic destination data sent by the first forwarding gateway corresponding to the traffic receiving end, and forwards the traffic to be forwarded based on the traffic forwarding path. This process opens up a transmission channel for forwarding the traffic to be forwarded from the traffic generating end to the traffic receiving end when the traffic generating end is in an off-cloud environment and the traffic receiving end is in an off-cloud environment or in an on-cloud environment. This solves the problem of high network maintenance costs for in-cloud and out-of-cloud forwarding traffic, which requires both cloud reception and detour forwarding via the physical network, when some of the IDCs at the traffic generating end and the traffic receiving end are on the cloud. It also saves physical equipment costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments of the present application or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying any creative work.

[0082] Figure 1 This is an application environment diagram of a multicast traffic forwarding method in one embodiment;

[0083] Figure 2 1 is a flow chart of a multicast traffic forwarding method according to an embodiment;

[0084] Figure 3 A schematic diagram of a flow chart of steps for generating a quantitative forwarding path in one embodiment;

[0085] Figure 4 Schematic diagram of a flow chart of a multicast traffic forwarding method according to another embodiment;

[0086] Figure 5 Schematic diagram of a flow chart of a multicast traffic forwarding method according to another embodiment;

[0087] Figure 6 Schematic diagram of a flow chart of a multicast traffic forwarding method according to another embodiment;

[0088] Figure 7is a structural block diagram of a multicast traffic forwarding device in one embodiment;

[0089] Figure 8 It is a structural block diagram of a multicast traffic forwarding device in another embodiment;

[0090] Figure 9 It is a structural block diagram of a multicast traffic forwarding device in another embodiment;

[0091] Figure 10 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0092] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0093] Before introducing the multicast traffic forwarding method provided in this application, it's important to note that traditional switching and routing networks rely on multicast Layer 2 and Layer 3 equipment for multicast service transmission. With the advent of the cloud era, this transmission method has increasingly exposed several shortcomings. First, with the dramatic increase in the number of multi-tenants and the demand for flexibility, traditional networks cannot meet these requirements in terms of link utilization and convergence speed. Second, deploying multicast services requires deploying multicast-capable equipment, which is quite costly. Currently, after some IDC hosts are migrated to the cloud (i.e., deployed within the cloud), the original multicast services must be forwarded not only within the cloud but also outside the cloud to ensure the original services. In this scenario, multicast visibility scenarios include: the multicast source (i.e., the traffic generator) is outside the cloud, and the multicast receivers (i.e., the traffic receivers) are both inside and outside the cloud; the multicast source is outside the cloud, and the multicast receivers are only inside the cloud; the multicast source is inside the cloud, and the multicast receivers are only outside the cloud; the multicast source is inside the cloud, and the multicast receivers are within a VPC within the cloud; the multicast source is inside the cloud, and the multicast receivers are between VPCs within the cloud, etc. In the scenario where the multicast source is outside the cloud and the multicast receivers are both inside and outside the cloud, it is a problem to be solved to achieve on-demand multicast forwarding by leveraging the advantages of the cloud without changing the networking.

[0094] The current solution to this problem is to connect the off-cloud IDC to the on-cloud VPC through a dedicated line, configure the multicast domain range, the off-cloud multicast source, the on-cloud virtual machine as the multicast receiver, and the on-cloud multicast gateway for forwarding. This allows the multicast source to be located in the offline IDC and the multicast receiver to receive multicast traffic within the cloud. When the multicast receiver is outside the cloud, it is still received through the off-cloud switching and routing network.

[0095] However, the above method has the following problems: (1) It requires the router device to support functions such as Internet Group Management Protocol (IGMP) and Protocol Independent Multicast (PIM). When the device model is old or the version is low, the multicast distribution function cannot be realized, which places high demands on the physical device; (2) When the IDCs corresponding to the multicast source and multicast receiver are partially on the cloud, the intra-cloud and inter-cloud forwarding traffic must not only be received on the cloud but also be forwarded to the outside of the cloud via the physical network, which increases the network maintenance cost. Therefore, this application provides a new multicast traffic forwarding method to solve the above problems.

[0096] The multicast traffic forwarding method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown in the figure, first, let's explain the abbreviations in the figure: Virtual Gateway (VGW), Virtual Machine (VM), and Layer 2 Gateway (L2GW). IDC has been introduced in the previous content and will not be repeated here.

[0097] The traffic generation end can be deployed in IDC1, the traffic receiving end can be deployed in IDC2, and VM1 can also be understood as the traffic receiving end. Figure 1 L2GW1 in the figure) and the first forwarding gateway 106 (i.e. Figure 1 L2GW2 in the network) are connected to each other; IDC1 is connected to L2GW1 through VGW1; IDC2 is connected to L2GW2 through VGW2; and L2GW1 is connected to VM1. Typically, the traffic generator, or multicast source, is deployed in IDC1, and the traffic receiver, or multicast receiver, is deployed in IDC2. For ease of explanation, in this embodiment, IDC1 can be directly understood as the traffic generator, and IDC2 as the traffic receiver. VGW1 can be understood as the second forwarding gateway corresponding to the traffic generator; VGW2 can be understood as the second forwarding gateway corresponding to the traffic receiver.

[0098] It is worth noting that understanding IDC1 as the traffic generating end and IDC2 as the traffic receiving end is only an example provided in the embodiment of the present application, and is not a limitation on the traffic generating end and the traffic receiving end. In some scenarios, IDC1 can also be understood as the traffic receiving end and IDC2 can be understood as the traffic generating end.

[0099] Specifically, L2GW1, L2GW2, and multicast controller 102 are deployed within the cloud environment; traffic generator IDC1 is deployed outside the cloud environment. Multicast controller 102 receives traffic source data and traffic destination data corresponding to the traffic to be forwarded. The traffic source data is sent by L2GW1, and the traffic destination data is sent by L2GW2. Based on the traffic source data and traffic destination data, multicast controller 102 generates a traffic forwarding path for the traffic to be forwarded. Based on the traffic forwarding path, multicast controller 102 controls the forwarding of the traffic to be forwarded.

[0100] In an exemplary embodiment, Figure 2 As shown, a multicast traffic forwarding method is provided, which is applied to Figure 1 The multicast controller in the example is used to illustrate the process, which includes the following steps:

[0101] S210, receiving traffic source data corresponding to the traffic to be forwarded, and traffic destination data corresponding to the traffic to be forwarded.

[0102] Among them, the traffic to be forwarded is the traffic that needs to be multicast forwarded. It can be understood that due to the differences in traffic requirements of different traffic receiving ends, the corresponding traffic to be forwarded may be different. The traffic source data is used to characterize the traffic source of the traffic to be forwarded. Generally, the traffic source data is used to indicate the entities involved in the path from the traffic generating end to the first forwarding gateway corresponding to the traffic generating end. The traffic destination data is used to characterize the traffic destination of the traffic to be forwarded. Generally, the traffic destination data is used to indicate the entities involved in the path from the first forwarding gateway corresponding to the traffic receiving end to the traffic receiving end.

[0103] For example, Figure 1 Taking the application environment diagram shown as an example, traffic source data may include IDC1, VGW1, and L2GW1, and traffic destination data may include L2GW2, VGW2, and IDC2.

[0104] The traffic source data is sent by the first forwarding gateway (L2GW1) corresponding to the traffic generation end; the traffic destination data is sent by the first forwarding gateway (L2GW2) corresponding to the traffic receiving end; the first forwarding gateway (L2GW1) corresponding to the traffic generation end, the first forwarding gateway (L2GW2) corresponding to the traffic receiving end, and the multicast controller are deployed in the cloud environment respectively; the traffic generation end (IDC1) is deployed in the non-cloud environment.

[0105] In an optional embodiment, when the traffic receiving end is deployed in a cloud environment, the first forwarding gateway corresponding to the traffic generating end is the same as the first forwarding gateway corresponding to the traffic receiving end. Figure 1Taking the application environment diagram shown as an example, the traffic receiving end VM1 is deployed in the cloud environment, the first forwarding gateway corresponding to the traffic generating end IDC1 is L2GW1, and the first forwarding gateway corresponding to the traffic receiving end VM1 is also L2GW1.

[0106] In another optional embodiment, when the traffic receiving end is deployed in an off-cloud environment, the first forwarding gateway corresponding to the traffic generating end is in communication connection with the first forwarding gateway corresponding to the traffic receiving end. Figure 1 Taking the application environment diagram shown as an example, the traffic receiving end IDC2 is deployed in an off-cloud environment, the first forwarding gateway corresponding to the traffic generating end IDC1 is L2GW1, and the first forwarding gateway corresponding to the traffic receiving end IDC2 is L2GW2. L2GW1 and L2GW2 are communicated with each other.

[0107] For example, L2GW1 and L2GW2 establish a Virtual eXtensible LAN (VXLAN) tunnel for communication. It should be noted that for the same multicast group, the tunnels between the L2GWs in the group have the same VXLAN Network Identifier (VNI).

[0108] S220: Generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and the traffic destination data.

[0109] Illustratively, in this embodiment, the traffic source data and the traffic destination data may be connected according to the traffic transmission direction to generate a traffic forwarding path corresponding to the traffic to be forwarded.

[0110] by Figure 1 Taking the application environment diagram shown in the figure as an example, based on the traffic source data (IDC1, VGW1, and L2GW1), the traffic destination data (L2GW2, VGW2, and IDC2), and the traffic transmission direction, IDC1->VGW1->L2GW1->L2GW2->VGW2->IDC2 can be generated as the traffic forwarding path corresponding to the traffic to be forwarded.

[0111] S230: Based on the traffic forwarding path, forwarding control is performed on the traffic to be forwarded.

[0112] Exemplarily, based on the traffic source data, the first forwarding gateway corresponding to the traffic generating end is controlled to obtain the traffic to be forwarded from the traffic generating end, and send the traffic to be forwarded to the first forwarding gateway corresponding to the traffic receiving end; based on the traffic destination data, the first forwarding gateway corresponding to the traffic receiving end is controlled to send the traffic to be forwarded to the traffic receiving end.

[0113] Specifically, Figure 1Taking the application environment diagram shown as an example, the multicast controller controls L2GW1 to obtain the traffic to be forwarded from IDC1 through VGW1, and controls L2GW1 to transmit the traffic to be forwarded to L2GW2; and controls L2GW2 to transmit the traffic to be forwarded to IDC2 through VGW2.

[0114] In the above-mentioned multicast traffic forwarding method, by deploying a first forwarding gateway corresponding to the traffic generating end and a first forwarding gateway corresponding to the traffic receiving end between the traffic generating end and the traffic receiving end, the traffic to be forwarded can be transmitted between the two first forwarding gateways, thereby forwarding the traffic to be forwarded from the traffic generating end to the traffic receiving end. Specifically, when the traffic generating end is deployed in an off-cloud environment, the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded by receiving traffic source data sent by the first forwarding gateway corresponding to the traffic generating end and traffic destination data sent by the first forwarding gateway corresponding to the traffic receiving end, and forwards the traffic to be forwarded based on the traffic forwarding path. This process opens up a transmission channel for forwarding the traffic to be forwarded from the traffic generating end to the traffic receiving end when the traffic generating end is in an off-cloud environment and the traffic receiving end is in an off-cloud environment or in an on-cloud environment. This solves the problem of high network maintenance costs for in-cloud and out-of-cloud forwarding traffic that needs to be received in the cloud and forwarded via the physical network when part of the IDCs of the traffic generating end and the traffic receiving end are on the cloud, while saving physical equipment costs.

[0115] Based on the technical solutions of the above embodiments, this application also provides an optional embodiment. In this optional embodiment, the traffic source data includes the first identification information of the traffic generating end and the second identification information of the first forwarding gateway corresponding to the traffic generating end; the traffic destination data includes the third identification information of the traffic receiving end and the fourth identification information of the first forwarding gateway corresponding to the traffic receiving end. In this case, the specific process of generating the traffic forwarding path corresponding to the to-be-forwarded traffic based on the traffic source data and traffic destination data is provided.

[0116] See also Figure 3 The steps for generating a traffic forwarding path include:

[0117] S310: Generate a traffic output path according to the first identification information and the second identification information.

[0118] The first identification information indicates basic information about the traffic generating end, for example, IDC1. The second identification information indicates basic information about the first forwarding gateway corresponding to the traffic generating end, for example, L2GW1. The traffic output path indicates the path along which the traffic to be forwarded flows from the traffic generating end to the first forwarding gateway corresponding to the traffic generating end.

[0119] For example, IDC1->L2GW1 can be used as the traffic output path. In this embodiment, since IDC1 is usually unable to directly transmit traffic to L2GW1, Figure 1 Taking the application environment diagram shown as an example, the traffic output path can be IDC1->VGW1->L2GW1.

[0120] S320: Generate a traffic receiving path according to the third identification information and the fourth identification information.

[0121] The third identification information indicates basic information about the traffic receiving end, for example, it may include IDC2. The fourth identification information indicates basic information about the first forwarding gateway corresponding to the traffic receiving end, for example, it may include L2GW2. The traffic receiving path indicates the path along which the traffic to be forwarded flows from the first forwarding gateway corresponding to the traffic receiving end to the traffic receiving end.

[0122] For example, when the traffic receiving end is deployed in an off-cloud environment, L2GW2->IDC2 can be used as the traffic receiving path. In this embodiment, since IDC2 is usually unable to directly transmit traffic to L2GW2, Figure 1 Taking the application environment diagram shown as an example, the traffic receiving path can be L2GW2->VGW2->IDC2.

[0123] For example, when the traffic receiving end is deployed in a cloud environment, L2GW1->VM1 can be used as the traffic receiving path.

[0124] S330 , connecting the traffic output path and the traffic receiving path in order to obtain a traffic forwarding path corresponding to the traffic to be forwarded.

[0125] For example, taking the traffic output path as IDC1->VGW1->L2GW1 and the traffic receiving path as L2GW2->VGW2->IDC2 as an example, the traffic output path and the traffic receiving path are connected, and the resulting traffic forwarding path can be IDC1->VGW1->L2GW1->L2GW2->VGW2->IDC2.

[0126] For example, when IDC1 is a traffic generating end and VM1 is a traffic receiving end, the corresponding traffic output path may be IDC1->VGW1->L2GW1, and the traffic receiving path may be L2GW1->VM1.

[0127] In the above embodiment, a specific process for generating a traffic forwarding path corresponding to the traffic to be forwarded is given. Specifically, the first identification information of the traffic generating end, the second identification information of the first forwarding gateway corresponding to the traffic generating end, the third identification information of the traffic receiving end, and the fourth identification information of the first forwarding gateway corresponding to the traffic receiving end are used as the basis for generating the traffic forwarding path, so that the generated traffic forwarding path is clearer.

[0128] In an exemplary embodiment, Figure 4 As shown, a multicast traffic forwarding method is provided, which is applied to Figure 1 Taking L2GW1 (i.e., the first forwarding gateway corresponding to the traffic generation end) in the example, the following steps are included:

[0129] S410, receiving traffic to be forwarded from a traffic generating end, and determining traffic source data corresponding to the traffic to be forwarded.

[0130] by Figure 1 Taking the application environment diagram shown as an example, L2GW1 may receive the traffic to be forwarded from IDC1 through VGW1, and determine the traffic source data corresponding to the traffic to be forwarded.

[0131] For example, L2GW1 receives a traffic service message sent by VGW1. Since the traffic service message is a two-layer VXLAN encapsulated message, L2GW1 can decapsulate the two-layer VXLAN and identify the traffic service message. When it is determined that the traffic service message includes traffic to be forwarded, L2GW1 uses the decapsulated information as traffic source data and sends the traffic source data to the multicast controller.

[0132] The traffic service packets are encapsulated in two layers of VXLAN: the inner encapsulation includes the identification information of L2GW1; the outer encapsulation includes the identification information of IDC1 and its corresponding VPC. It is worth noting that there is a one-to-one correspondence between L2GWs and VPCs, and a one-to-one correspondence between L2GW connections and subnets within a VPC. Accordingly, the identification information of L2GW1 can also include the identification information of its corresponding VPC. Similarly, the identification information of L2GW2 can also include the identification information of its corresponding VPC.

[0133] Optionally, the traffic service message sent by VGW1 to L2GW1 is processed. Exemplarily, the processing process can be as follows: VGW1 receives the initial service message encapsulated in two layers of VXLAN sent by IDC1, and decapsulates the outer VXLAN; VGW1 determines the identification information of the VPC corresponding to L2GW1 based on the information of the inner VXLAN, and re-encapsulates the initial service message based on the identification information of the VPC to obtain the traffic service message.

[0134] The two-layer VXLAN encapsulation of the initial service message is as follows: the inner encapsulation includes the identification information of L2GW1; and the outer encapsulation includes the identification information of IDC1 and the identification information of VGW1.

[0135] S420, sending the traffic source data to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and the traffic destination data determined by the first forwarding gateway corresponding to the traffic receiving end, and perform forwarding control on the traffic to be forwarded based on the traffic forwarding path.

[0136] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0137] In the above-mentioned multicast traffic forwarding method, by deploying a first forwarding gateway corresponding to the traffic generating end and a first forwarding gateway corresponding to the traffic receiving end between the traffic generating end and the traffic receiving end, the traffic to be forwarded can be transmitted between the two first forwarding gateways, thereby forwarding the traffic to be forwarded from the traffic generating end to the traffic receiving end. Specifically, when the traffic generating end is deployed in an off-cloud environment, the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded by receiving traffic source data sent by the first forwarding gateway corresponding to the traffic generating end and traffic destination data sent by the first forwarding gateway corresponding to the traffic receiving end, and forwards the traffic to be forwarded based on the traffic forwarding path. This process opens up a transmission channel for forwarding the traffic to be forwarded from the traffic generating end to the traffic receiving end when the traffic generating end is in an off-cloud environment and the traffic receiving end is in an off-cloud environment or in an on-cloud environment. This solves the problem of high network maintenance costs for in-cloud and out-of-cloud forwarding traffic that needs to be received in the cloud and forwarded via the physical network when part of the IDCs of the traffic generating end and the traffic receiving end are on the cloud, while saving physical equipment costs.

[0138] In an exemplary embodiment, Figure 5 As shown, a multicast traffic forwarding method is provided, which is applied to Figure 1 Taking L2GW2 (i.e., the first forwarding gateway corresponding to the traffic receiving end) in the example, the following steps are included:

[0139] S510: Receive a multicast on-demand request from a traffic receiving end.

[0140] The multicast on-demand request is used to request the sending of traffic to be forwarded.

[0141] by Figure 1 Taking the application environment diagram shown as an example, L2GW2 may receive a multicast on-demand request from IDC2 through VGW2.

[0142] For example, L2GW2 receives the multicast on-demand request sent by VGW2. Since the multicast on-demand request is a two-layer VXLAN encapsulated message, L2GW2 can decapsulate the two-layer VXLAN and identify the multicast on-demand request. When it is determined that the multicast on-demand request is used to request multicast traffic forwarding, L2GW2 uses the decapsulated information as traffic destination data and sends the traffic destination data to the multicast controller.

[0143] The two-layer VXLAN encapsulation of the multicast on-demand request is as follows: the inner encapsulation includes the identification information of L2GW2; and the outer encapsulation includes the identification information of IDC2 and the identification information of its corresponding VPC.

[0144] Optionally, the multicast on-demand request sent by VGW2 to L2GW2 is processed. Exemplarily, the processing process can be as follows: VGW2 receives the initial request message encapsulated in two layers of VXLAN sent by IDC2, and decapsulates the outer VXLAN; VGW2 determines the identification information of the VPC corresponding to L2GW2 based on the information of the inner VXLAN, and re-encapsulates the initial request message according to the identification information of the VPC to obtain the multicast on-demand request.

[0145] The two-layer VXLAN encapsulation of the initial request message is as follows: the inner encapsulation includes the identification information of L2GW2; and the outer encapsulation includes the identification information of IDC2 and the identification information of VGW2.

[0146] S520: Determine traffic destination data corresponding to the traffic to be forwarded.

[0147] Specifically, in this embodiment, the information obtained after decapsulating the multicast on-demand request can be used as traffic destination data.

[0148] S530, sending the traffic destination data to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic destination data and the traffic source data determined by the first forwarding gateway corresponding to the traffic generating end, and perform forwarding control on the traffic to be forwarded based on the traffic forwarding path.

[0149] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0150] In the above-mentioned multicast traffic forwarding method, by deploying a first forwarding gateway corresponding to the traffic generating end and a first forwarding gateway corresponding to the traffic receiving end between the traffic generating end and the traffic receiving end, the traffic to be forwarded can be transmitted between the two first forwarding gateways, thereby forwarding the traffic to be forwarded from the traffic generating end to the traffic receiving end. Specifically, when the traffic generating end is deployed in an off-cloud environment, the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded by receiving traffic source data sent by the first forwarding gateway corresponding to the traffic generating end and traffic destination data sent by the first forwarding gateway corresponding to the traffic receiving end, and forwards the traffic to be forwarded based on the traffic forwarding path. This process opens up a transmission channel for forwarding the traffic to be forwarded from the traffic generating end to the traffic receiving end when the traffic generating end is in an off-cloud environment and the traffic receiving end is in an off-cloud environment or in an on-cloud environment. This solves the problem of high network maintenance costs for in-cloud and out-of-cloud forwarding traffic that needs to be received in the cloud and forwarded via the physical network when part of the IDCs of the traffic generating end and the traffic receiving end are on the cloud, while saving physical equipment costs.

[0151] It should be noted that, taking L2GW2 as an example, if L2GW2 receives the first addition of a user multicast group or the last user leaves a multicast group, it can report an IGMP Report or IGMP Leave message to the multicast controller. The multicast group on-demand request / leave path is IDC2 -> VGW2 -> L2GW2 -> multicast controller -> L2GW1. If L2GW1 receives an IGMP request message from VM1 in the cloud, the multicast group on-demand request / leave path is VM1 -> L2GW1 -> multicast controller. Furthermore, if the multicast controller receives an IGMP Report or IGMP Leave message from L2GW1, it can maintain the L2GW1 -> L2GW2 multicast distribution information table.

[0152] Based on the technical solutions of the above embodiments, this application also provides an optional embodiment. In this optional embodiment, the multicast traffic forwarding method provided by this application is applied to Figure 1 The application environment shown in FIG. 1 is used as an example to introduce the method in detail.

[0153] See also Figure 6 The multicast traffic forwarding method shown includes:

[0154] S601: L2GW2 receives a multicast on-demand request from a traffic receiving end. The multicast on-demand request is used to request the sending of traffic to be forwarded.

[0155] For example, when VGW2 receives the double-VXLAN encapsulated Overlay IGMPReport initial request message from IDC2 via the dedicated line, it decapsulates the outer dedicated line VXLAN and identifies the MAC address of the VXLAN tunnel endpoint (VTEP) of L2GW2 based on the tunnel media access control address (MAC) of the inner VXLAN message. It then identifies the initial request message as relay traffic, searches for the L2GW2 connection, re-encapsulates the outer VXLAN, obtains the multicast on-demand request, and sends the multicast on-demand request to L2GW2.

[0156] S602, L2GW2 determines the traffic destination data corresponding to the traffic to be forwarded;

[0157] The traffic destination data includes the third identification information of the traffic receiving end and the fourth identification information of L2GW2;

[0158] For example, L2GW2 decapsulates the Layer 2 VXLAN encapsulation of the multicast on-demand request, identifies the Overlay IGMP Report message as proxy traffic, configures a Layer 3 logical interface L2GWLOOPm (where m is the logical interface number), and maintains the L2GW2 multicast VXLAN connection table, that is, establishes a connection record between L2GW2 and L2GW1.

[0159] S603: L2GW2 sends the traffic destination data to the multicast controller.

[0160] S604: L2GW1 receives the traffic to be forwarded from the traffic generating end and determines the traffic source data corresponding to the traffic to be forwarded.

[0161] The traffic source data includes the first identification information of the traffic generating end and the second identification information of L2GW1;

[0162] For example, VGW1 receives an overlay initial service packet encapsulated in two layers of VXLAN from IDC1 outside the cloud via a dedicated line. It decapsulates the outer dedicated line VXLAN and identifies the MAC address of L2GW1's VTEP based on the tunnel DMAC of the inner VXLAN packet. This identifies the packet as relay traffic. It then searches for the L2GW1 connection and re-encapsulates the outer VXLAN packet to obtain a traffic service packet. The packet is then sent to L2GW1. Furthermore, L2GW1 decapsulates the two layers of VXLAN, identifies the packet as an overlay traffic service packet, and updates the L2GW1 connection multicast VXLAN table, establishing a connection record between L2GW1 and L2GW2.

[0163] S605, L2GW1 sends the traffic source data to the multicast controller;

[0164] L2GW1, L2GW2, and the multicast controller are deployed in the cloud environment. The traffic generator is deployed outside the cloud. When the traffic receiver is deployed in the cloud environment, L2GW1 and L2GW2 are identical. When the traffic receiver is deployed outside the cloud environment, L2GW1 and L2GW2 are connected.

[0165] S606, the multicast controller generates a traffic output path according to the first identification information and the second identification information;

[0166] S607: The multicast controller generates a traffic receiving path according to the third identification information and the fourth identification information;

[0167] S608, the multicast controller connects the traffic output path and the traffic receiving path in the order of the traffic output path and the traffic receiving path to obtain a traffic forwarding path corresponding to the traffic to be forwarded;

[0168] S609: The multicast controller sends the traffic output path to L2GW1.

[0169] S610: The multicast controller sends the traffic receiving path to L2GW2.

[0170] S611: The multicast controller controls L2GW1 to obtain the traffic to be forwarded from the traffic generator based on the traffic output path, and sends the traffic to be forwarded to L2GW2.

[0171] L2GW1 is configured with a Layer 3 logical interface Internet Protocol (IP) address, and a transparent transmission tunnel is created from L2GW1 to L2GW2.

[0172] S612: The multicast controller controls L2GW2 to send the traffic to be forwarded to the traffic receiving end according to the traffic receiving path.

[0173] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0174] Based on the same inventive concept, embodiments of the present application also provide a multicast traffic forwarding device for implementing the multicast traffic forwarding method described above. The implementation solution provided by this device is similar to the implementation solution described in the above-mentioned method. Therefore, the specific limitations of one or more multicast traffic forwarding device embodiments provided below can be found in the above-mentioned limitations of the multicast traffic forwarding method and will not be repeated here.

[0175] In an exemplary embodiment, Figure 7 As shown, a multicast traffic forwarding device is provided, including: a first receiving module 710, a generating module 720 and a forwarding module 730, wherein:

[0176] The first receiving module 710 is used to receive traffic source data corresponding to the traffic to be forwarded, and traffic destination data corresponding to the traffic to be forwarded; the traffic source data is sent by the first forwarding gateway corresponding to the traffic generating end; the traffic destination data is sent by the first forwarding gateway corresponding to the traffic receiving end; the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end, and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment; when the traffic receiving end is deployed in the cloud environment, the first forwarding gateway corresponding to the traffic generating end is the same as the first forwarding gateway corresponding to the traffic receiving end; when the traffic receiving end is deployed in the cloud environment, the first forwarding gateway corresponding to the traffic generating end is communicatively connected to the first forwarding gateway corresponding to the traffic receiving end.

[0177] The generation module 720 is used to generate a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic source data and the traffic destination data.

[0178] The forwarding module 730 is used to control the forwarding of the traffic based on the traffic forwarding path.

[0179] In one embodiment, the traffic source data includes the first identification information of the traffic generating end and the second identification information of the first forwarding gateway corresponding to the traffic generating end; the traffic destination data includes the third identification information of the traffic receiving end and the fourth identification information of the first forwarding gateway corresponding to the traffic receiving end; accordingly, the generation module 720 includes a first generation unit, which is used to generate a traffic output path based on the first identification information and the second identification information; a second generation unit, which is used to generate a traffic receiving path based on the third identification information and the fourth identification information; and a third generation unit, which is used to connect the traffic output path and the traffic receiving path in the order of the traffic output path and the traffic receiving path to obtain the traffic forwarding path corresponding to the traffic to be forwarded.

[0180] In one embodiment, the forwarding module 730 includes a first forwarding unit, which is used to control the first forwarding gateway corresponding to the traffic generating end to obtain the traffic to be forwarded from the traffic generating end according to the traffic source data, and send the traffic to be forwarded to the first forwarding gateway corresponding to the traffic receiving end; and a second forwarding unit, which is used to control the first forwarding gateway corresponding to the traffic receiving end to send the traffic to be forwarded to the traffic receiving end according to the traffic destination data.

[0181] In an exemplary embodiment, Figure 8 As shown, a multicast traffic forwarding device is provided, including: a first determining module 810 and a first sending module 820, wherein:

[0182] The first determining module 810 is configured to receive traffic to be forwarded from a traffic generating end and determine traffic source data corresponding to the traffic to be forwarded.

[0183] The first sending module 820 is used to send the traffic source data to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and the traffic destination data determined by the first forwarding gateway corresponding to the traffic receiving end, and perform forwarding control on the traffic to be forwarded based on the traffic forwarding path.

[0184] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0185] In an exemplary embodiment, Figure 9 As shown, a multicast traffic forwarding device is provided, including: a second receiving module 910, a second determining module 920 and a second sending module 930, wherein:

[0186] The second receiving module 910 is configured to receive a multicast on-demand request from a traffic receiving end; the multicast on-demand request is used to request the sending of traffic to be forwarded.

[0187] The second determining module 920 is configured to determine traffic destination data corresponding to the traffic to be forwarded.

[0188] The second sending module 930 is used to send the traffic destination data to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic destination data and the traffic source data determined by the first forwarding gateway corresponding to the traffic generating end, and perform forwarding control on the traffic to be forwarded based on the traffic forwarding path.

[0189] Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment.

[0190] Each module in the multicast traffic forwarding device can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in hardware form, or can be stored in a memory in the computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0191] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 10 As shown. The computer device includes a processor, memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals via wired or wireless means, and the wireless means can be implemented via Wi-Fi, a mobile cellular network, near-field communication (NFC), or other technologies. When executed by the processor, the computer program implements a multicast traffic forwarding method. The display unit of the computer device is used to form a visually visible image, and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse.

[0192] Those skilled in the art will understand that Figure 10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0193] In an exemplary embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0194] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0195] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0196] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0197] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the above-mentioned embodiments. Among them, any reference to memory, database or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), quantum computing-based data processing logic devices, artificial intelligence (AI) processors, and the like.

[0198] The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0199] The above embodiments merely illustrate several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art may make various modifications and improvements without departing from the spirit of the present invention, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A multicast traffic forwarding method, characterized in that: Applied to a multicast controller, the method includes: Receive traffic source data corresponding to the traffic to be forwarded, and traffic destination data corresponding to the traffic to be forwarded; the traffic source data is sent by the first forwarding gateway corresponding to the traffic generating end; the traffic destination data is sent by the first forwarding gateway corresponding to the traffic receiving end; the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end, and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment; the traffic receiving end is deployed in the cloud environment or the cloud environment; the traffic source data includes the first identification information of the traffic generating end, and the second identification information of the first forwarding gateway corresponding to the traffic generating end; the traffic destination data includes the third identification information of the traffic receiving end, and the fourth identification information of the first forwarding gateway corresponding to the traffic receiving end; generating a traffic output path according to the first identification information and the second identification information; generating a traffic receiving path according to the third identification information and the fourth identification information; Connecting the traffic output path and the traffic receiving path in order to obtain a traffic forwarding path corresponding to the traffic to be forwarded; According to the traffic source data, control the first forwarding gateway corresponding to the traffic generating end to obtain the traffic to be forwarded from the traffic generating end, and send the traffic to be forwarded to the first forwarding gateway corresponding to the traffic receiving end; According to the traffic destination data, the first forwarding gateway corresponding to the traffic receiving end is controlled to send the traffic to be forwarded to the traffic receiving end.

2. The method according to claim 1, characterized in that In the case where the traffic receiving end is deployed in a cloud environment, the first forwarding gateway corresponding to the traffic generating end is the same as the first forwarding gateway corresponding to the traffic receiving end; In the case where the traffic receiving end is deployed in an off-cloud environment, the first forwarding gateway corresponding to the traffic generating end is communicatively connected to the first forwarding gateway corresponding to the traffic receiving end.

3. A multicast traffic forwarding method, characterized in that: Applied to a first forwarding gateway corresponding to a traffic generating end, the method includes: Receive traffic to be forwarded from a traffic generating end, and determine traffic source data corresponding to the traffic to be forwarded; The traffic source data is sent to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded based on the traffic source data and the traffic destination data determined by the first forwarding gateway corresponding to the traffic receiving end, and control the first forwarding gateway corresponding to the traffic generating end to send the traffic to be forwarded to the first forwarding gateway corresponding to the traffic receiving end according to the traffic source data; control the first forwarding gateway corresponding to the traffic receiving end to send the traffic to be forwarded to the traffic receiving end according to the traffic destination data; the traffic source data includes the first identification information of the traffic generating end and the second identification information of the first forwarding gateway corresponding to the traffic generating end ; The traffic destination data includes the third identification information of the traffic receiving end and the fourth identification information of the first forwarding gateway corresponding to the traffic receiving end; accordingly, the traffic forwarding path corresponding to the traffic to be forwarded is generated based on the traffic source data and the traffic destination data determined by the first forwarding gateway corresponding to the traffic receiving end, including: generating a traffic output path based on the first identification information and the second identification information; generating a traffic receiving path based on the third identification information and the fourth identification information; connecting the traffic output path and the traffic receiving path in the order of the traffic output path and the traffic receiving path to obtain the traffic forwarding path corresponding to the traffic to be forwarded; Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment; the traffic receiving end is deployed in the cloud environment or the cloud environment.

4. The method according to claim 3, characterized in that The receiving of the to-be-forwarded traffic from the traffic generating end and determining traffic source data corresponding to the to-be-forwarded traffic includes: Receive a traffic service message sent by a virtual gateway corresponding to the traffic generating end; the traffic service message is a message encapsulated by a two-layer virtual local area network; Decapsulating two layers of virtual local area network encapsulation and identifying the traffic service message; When it is determined that the traffic service message includes traffic to be forwarded, the information obtained by decapsulation is used as traffic source data.

5. A multicast traffic forwarding method, characterized in that: Applied to a first forwarding gateway corresponding to a traffic receiving end, the method includes: Receiving a multicast on-demand request from a traffic receiving end; the multicast on-demand request is used to request sending of traffic to be forwarded; Determining traffic destination data corresponding to the traffic to be forwarded; The traffic destination data is sent to the multicast controller, so that the multicast controller can generate a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic destination data and the traffic source data determined by the first forwarding gateway corresponding to the traffic generating end, and control the first forwarding gateway corresponding to the traffic generating end to obtain the traffic to be forwarded from the traffic generating end according to the traffic source data, and send the traffic to be forwarded to the first forwarding gateway corresponding to the traffic receiving end; according to the traffic destination data, control the first forwarding gateway corresponding to the traffic receiving end to send the traffic to be forwarded to the traffic receiving end; the traffic source data includes the first identification information of the traffic generating end, and the first forwarding gateway corresponding to the traffic generating end. the second identification information of the gateway; the traffic destination data includes the third identification information of the traffic receiving end and the fourth identification information of the first forwarding gateway corresponding to the traffic receiving end; accordingly, the traffic forwarding path corresponding to the traffic to be forwarded is generated according to the traffic destination data and the traffic source data determined by the first forwarding gateway corresponding to the traffic generating end, including: generating a traffic output path according to the first identification information and the second identification information; generating a traffic receiving path according to the third identification information and the fourth identification information; connecting the traffic output path and the traffic receiving path in the order of the traffic output path and the traffic receiving path to obtain the traffic forwarding path corresponding to the traffic to be forwarded; Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment; the traffic receiving end is deployed in the cloud environment or the cloud environment.

6. A multicast traffic forwarding device, characterized in that: Deployed on a multicast controller, the device includes: The first receiving module is used to receive traffic source data corresponding to the traffic to be forwarded, and traffic destination data corresponding to the traffic to be forwarded; the traffic source data is sent by the first forwarding gateway corresponding to the traffic generating end; the traffic destination data is sent by the first forwarding gateway corresponding to the traffic receiving end; the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment; the traffic receiving end is deployed in the cloud environment or the cloud environment; the traffic source data includes the first identification information of the traffic generating end, and the second identification information of the first forwarding gateway corresponding to the traffic generating end; the traffic destination data includes the third identification information of the traffic receiving end, and the fourth identification information of the first forwarding gateway corresponding to the traffic receiving end; a generating module, configured to generate a traffic output path based on the first identification information and the second identification information; generate a traffic receiving path based on the third identification information and the fourth identification information; and connect the traffic output path and the traffic receiving path in the order of the traffic output path and the traffic receiving path to obtain a traffic forwarding path corresponding to the traffic to be forwarded; A forwarding module is used to control the first forwarding gateway corresponding to the traffic generating end to obtain the traffic to be forwarded from the traffic generating end according to the traffic source data, and send the traffic to be forwarded to the first forwarding gateway corresponding to the traffic receiving end; and control the first forwarding gateway corresponding to the traffic receiving end to send the traffic to be forwarded to the traffic receiving end according to the traffic destination data.

7. A multicast traffic forwarding device, characterized in that: A first forwarding gateway deployed at a traffic generating end includes: A first determining module is configured to receive traffic to be forwarded from a traffic generating terminal and determine traffic source data corresponding to the traffic to be forwarded; The first sending module is used to send the traffic source data to the multicast controller, so that the multicast controller can generate the traffic forwarding path corresponding to the to-be-forwarded traffic according to the traffic source data and the traffic destination data determined by the first forwarding gateway corresponding to the traffic receiving end, and control the first forwarding gateway corresponding to the traffic generating end to send the to-be-forwarded traffic to the first forwarding gateway corresponding to the traffic receiving end according to the traffic source data; control the first forwarding gateway corresponding to the traffic receiving end to send the to-be-forwarded traffic to the traffic receiving end according to the traffic destination data; the traffic source data includes the first identification information of the traffic generating end and the second identification information of the first forwarding gateway corresponding to the traffic generating end; the traffic destination data includes the third identification information of the traffic receiving end and the first The fourth identification information of the forwarding gateway; accordingly, the traffic forwarding path corresponding to the traffic to be forwarded is generated according to the traffic source data and the traffic destination data determined by the first forwarding gateway corresponding to the traffic receiving end, including: generating a traffic output path according to the first identification information and the second identification information; generating a traffic receiving path according to the third identification information and the fourth identification information; connecting the traffic output path and the traffic receiving path in the order of the traffic output path and the traffic receiving path to obtain the traffic forwarding path corresponding to the traffic to be forwarded; wherein, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment; and the traffic receiving end is deployed in the cloud environment or the cloud environment.

8. A multicast traffic forwarding device, characterized in that: A first forwarding gateway deployed at a corresponding traffic receiving end includes: A second receiving module is configured to receive a multicast on-demand request from a traffic receiving end; the multicast on-demand request is used to request sending of traffic to be forwarded; A second determining module is used to determine the traffic destination data corresponding to the traffic to be forwarded; The second sending module is used to send the traffic destination data to the multicast controller, so that the multicast controller can generate the traffic forwarding path corresponding to the traffic to be forwarded according to the traffic destination data and the traffic source data determined by the first forwarding gateway corresponding to the traffic generating end, and control the first forwarding gateway corresponding to the traffic generating end to obtain the traffic to be forwarded from the traffic generating end according to the traffic source data, and send the traffic to be forwarded to the first forwarding gateway corresponding to the traffic receiving end; according to the traffic destination data, control the first forwarding gateway corresponding to the traffic receiving end to send the traffic to be forwarded to the traffic receiving end; the traffic source data includes the first identification information of the traffic generating end, and the first forwarding gateway corresponding to the traffic generating end. the second identification information of the first forwarding gateway; the traffic destination data includes the third identification information of the traffic receiving end and the fourth identification information of the first forwarding gateway corresponding to the traffic receiving end; accordingly, the traffic forwarding path corresponding to the traffic to be forwarded is generated according to the traffic destination data and the traffic source data determined by the first forwarding gateway corresponding to the traffic generating end, including: generating a traffic output path according to the first identification information and the second identification information; generating a traffic receiving path according to the third identification information and the fourth identification information; connecting the traffic output path and the traffic receiving path in the order of the traffic output path and the traffic receiving path to obtain the traffic forwarding path corresponding to the traffic to be forwarded; Among them, the first forwarding gateway corresponding to the traffic generating end, the first forwarding gateway corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generating end is deployed in the cloud environment; the traffic receiving end is deployed in the cloud environment or the cloud environment.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 5 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed, the steps of the method according to any one of claims 1 to 5 are implemented.

Images