Multicast traffic forwarding method and device and computer equipment

By deploying outside the cloud at the traffic generation end and multicast controllers in the cloud to generate and control the traffic forwarding path, the problem that traditional multicast services are difficult to meet dynamic business needs in the cloud environment is solved, and intelligent on-demand distribution of multicast traffic inside and outside the cloud is realized, reducing network maintenance costs and saving physical equipment costs.

CN120034477AActive Publication Date: 2025-05-23CHINA TELECOM CLOUD TECH CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202510511953.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-04-23
Publication Date
2025-05-23
Estimated Expiration
2045-04-23

AI Technical Summary

Technical Problem

Traditional multicast services are difficult to meet the needs of multi-tenant elastic expansion, link resource utilization and network convergence speed in the cloud environment. Especially in complex scenarios where the multicast source is located outside the cloud and the receiver is distributed inside and outside the cloud, it is necessary to realize intelligent on-demand distribution of multicast traffic inside and outside the cloud.

Method used

When the traffic generation end is deployed outside the cloud and the multicast controller is deployed in the cloud, it generates a traffic forwarding path by receiving traffic source data and traffic destination data, and performs forwarding control based on this path to realize traffic forwarding between the traffic generation end and the receiving end on demand.

Benefits of technology

It solves the problem of high maintenance costs for forwarding traffic in and out of the cloud, which requires both to be received on the cloud and forwarded by the physical network, and at the same time saves physical equipment costs and realizes intelligent on-demand distribution of multicast traffic.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120034477A_ABST
    Figure CN120034477A_ABST
Patent Text Reader

Abstract

The invention relates to a multicast traffic forwarding method and device and computer equipment. The method comprises the following steps: receiving traffic source data corresponding to a to-be-forwarded traffic and traffic destination data corresponding to the to-be-forwarded traffic; the traffic source data is sent by a first forwarding gateway corresponding to the traffic generation end; the traffic destination data is sent by a first forwarding gateway corresponding to the traffic receiving end; the first forwarding gateway corresponding to the flow generating end, the first forwarding gateway corresponding to the flow receiving end and the multicast controller are respectively deployed in the in-cloud environment; the traffic generation end is deployed in an external cloud environment; according to the traffic source data and the traffic destination data, generating a traffic forwarding path corresponding to the to-be-forwarded traffic; and performing forwarding control on the to-be-forwarded traffic based on the traffic forwarding path. By adopting the method, on-demand forwarding of the flow between the flow generation end and the flow receiving end can be realized under the condition that the flow generation end is deployed in the outside-cloud environment and the multicast controller is deployed in the inside-cloud environment.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] With the popularization of cloud computing technology, the multicast service architecture of traditional switching and routing networks faces significant challenges in cloud environments. Traditional multicast transmission relies on layer 2 and 3 devices to achieve data distribution, but it is difficult to meet the dynamic business needs of the cloud era in terms of multi-tenant elastic expansion, link resource utilization, and network convergence speed.

[0003] Especially when some hosts in the Internet Data Center (IDC) under the cloud 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 the cloud / inside the cloud, receivers distributed inside and outside the cloud or across virtual private clouds (VPCs), and other situations.

[0004] In the scenario where the multicast source is outside the cloud and the receiver exists both inside and outside the cloud, it is urgent to realize the 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 generating end and the traffic receiving end when the traffic generating 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, which is applied to a multicast controller, including:

[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 generation 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 generation end, the first forwarding gateway corresponding to the traffic receiving end, and the multicast controller are respectively deployed in the cloud environment; the traffic generation end is deployed in the cloud environment;

[0008] Generate a 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 the traffic generating end and second identification information of the first forwarding gateway corresponding to the traffic generating end; the traffic destination data includes third identification information of the traffic receiving end and fourth identification information of the first forwarding gateway corresponding to the traffic receiving end; accordingly, generating a traffic forwarding path corresponding to the traffic to be forwarded according to 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] Generate 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 environment outside the cloud, the first forwarding gateway corresponding to the traffic generating end is communicatively connected with the first forwarding gateway corresponding to the traffic receiving end.

[0016] In one embodiment, forwarding control is performed on the traffic to be forwarded 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 the traffic to be forwarded is sent 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 generation end, including:

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

[0021] The traffic source data is sent to the multicast controller, so that the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic source data and the traffic destination data determined by the 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;

[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] 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;

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

[0026] The traffic destination data is sent to the multicast controller, so that the multicast controller generates 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 performs 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, including:

[0029] 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;

[0030] A generation module, used for generating a traffic forwarding path corresponding to the traffic to be forwarded according to 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 generation end, and includes:

[0033] A first determination module is used to receive the traffic to be forwarded from the traffic generation end, and determine the traffic source data corresponding to the traffic to be forwarded;

[0034] A first sending module is used to send the traffic source data to the multicast controller, so that the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic source data and the traffic destination data determined by the 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, and includes:

[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 to send the traffic to be forwarded;

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

[0039] A second sending module is used 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 according to 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, including 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 generation 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 generation end, the first forwarding gateway corresponding to the traffic receiving end, and the multicast controller are respectively deployed in the cloud environment; the traffic generation end is deployed in the cloud environment;

[0043] Generate a 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, including 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 generation end, and determine the traffic source data corresponding to the traffic to be forwarded;

[0047] The traffic source data is sent to the multicast controller, so that the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic source data and the traffic destination data determined by the 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;

[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, including 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] 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;

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

[0052] The traffic destination data is sent to the multicast controller, so that the multicast controller generates 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 performs 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, and when the computer program is executed by a processor, the following steps are implemented:

[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 generation 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 generation end, the first forwarding gateway corresponding to the traffic receiving end, and the multicast controller are respectively deployed in the cloud environment; the traffic generation end is deployed in the cloud environment;

[0056] Generate a 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, and when the computer program is executed by a processor, the following steps are implemented:

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

[0060] The traffic source data is sent to the multicast controller, so that the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic source data and the traffic destination data determined by the 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;

[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, and when the computer program is executed by a processor, the following steps are implemented:

[0063] 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;

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

[0065] The traffic destination data is sent to the multicast controller, so that the multicast controller generates 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 performs 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, including a computer program, which implements the following steps when executed by a processor:

[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 generation 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 generation end, the first forwarding gateway corresponding to the traffic receiving end, and the multicast controller are respectively deployed in the cloud environment; the traffic generation end is deployed in the cloud environment;

[0069] Generate a 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 implements the following steps when executed by a processor:

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

[0073] The traffic source data is sent to the multicast controller, so that the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic source data and the traffic destination data determined by the 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;

[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 implements the following steps when executed by a processor:

[0076] 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;

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

[0078] The traffic destination data is sent to the multicast controller, so that the multicast controller generates 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 performs 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, device and computer equipment, by deploying the first forwarding gateway corresponding to the traffic generating end and the first forwarding gateway corresponding to the traffic receiving end between the traffic generating end and the traffic receiving end, enables the traffic to be forwarded to 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 the traffic source data sent by the first forwarding gateway corresponding to the traffic generating end and the 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 the 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, and solves the problem of high network maintenance cost for the on-cloud and off-cloud forwarding traffic that needs to be received on the cloud and forwarded via the physical network when part of the IDC of the traffic generating end and the traffic receiving end is on the cloud, while saving the cost of physical equipment. 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 drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. 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 creative work.

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

[0083] Figure 2 A schematic diagram of a flow chart of a multicast traffic forwarding method in an embodiment;

[0084] Figure 3 A schematic diagram of a flow chart of a step of generating a forwarding path in an embodiment;

[0085] Figure 4 It is a flowchart of a multicast traffic forwarding method in another embodiment;

[0086] Figure 5 It is a flowchart of a multicast traffic forwarding method in another embodiment;

[0087] Figure 6 It is a flowchart of a multicast traffic forwarding method in another embodiment;

[0088] Figure 7It is 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] Fig. 9 It is a structural block diagram of a multicast traffic forwarding device in another embodiment;

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

[0092] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0093] Before introducing the multicast traffic forwarding method provided by this application, it should be noted that the multicast service transmission of the traditional switching routing network needs to rely on multicast layer 2 and 3 devices, and with the advent of the cloud era, this transmission method has increasingly exposed some shortcomings. First, the number of multi-tenants and elasticity requirements have increased dramatically, and the traditional network cannot meet the requirements in terms of link utilization and convergence speed; secondly, the deployment of multicast services requires the deployment of related equipment that supports multicast functions, and the investment cost is relatively high. At present, after some hosts of IDC are migrated to the cloud (that is, deployed in the cloud environment), the original multicast service must not only be forwarded in the cloud, but also bypass the cloud to ensure the original service. Based on this situation, the visible multicast scenarios are: the multicast source (that is, the traffic generation end) is outside the cloud, and the multicast receiver (that is, the traffic receiving end) is both inside and outside the cloud; the multicast source is outside the cloud, and the multicast receiver is only in the cloud; the multicast source is in the cloud, and the multicast receiver is only outside the cloud; the multicast source is in the cloud, and the multicast receiver is in the cloud VPC; the multicast source is in the cloud, and the multicast receiver is between the cloud VPCs, etc. For 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 within the cloud without changing the networking.

[0094] The current solution to this problem is to connect the IDC outside the cloud to the VPC on the cloud through a dedicated line, configure the multicast domain range, the multicast source outside the cloud, and the virtual machine inside the cloud as the multicast receiver. The multicast gateway inside the cloud forwards the multicast source to the offline IDC and the multicast receiver receives the multicast traffic in the cloud. When the multicast receiver is outside the cloud, it is still implemented through the switching and routing network outside the cloud.

[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, and the physical device requirements are high; (2) When the IDCs corresponding to the multicast source and multicast receiver are partially on the cloud, the intra-cloud and extra-cloud forwarding traffic must not only be received on the cloud but also forwarded to the cloud via the physical network, which increases the network maintenance cost. To this end, 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 of all, the English abbreviations in the figure are explained: Virtual Gateway (VGW), Virtual Machine (VM), Layer 2 Gateway (L2GW). IDC has been introduced in the previous content and will not be repeated here.

[0097] The traffic generation end may be deployed in IDC1, the traffic receiving end may be deployed in IDC2, and VM1 may also be understood as the traffic receiving end. The multicast controller 102 and the first forwarding gateway 104 (i.e. Figure 1 L2GW1 in the figure) and the first forwarding gateway 106 (i.e. Figure 1 L2GW2 in the communication connection between each other; IDC1 is connected to L2GW1 through VGW1; IDC2 is connected to L2GW2 through VGW2; L2GW1 is connected to VM1. Normally, the traffic generation end, that is, the multicast source will be deployed in IDC1, and the traffic receiving end, that is, the multicast receiver will be deployed in IDC2. For the convenience of explanation, in this embodiment, IDC1 can be directly understood as the traffic generation end, and IDC2 can be understood as the traffic receiving end. Among them, VGW1 can be understood as the second forwarding gateway corresponding to the traffic generation end; VGW2 can be understood as the second forwarding gateway corresponding to the traffic receiving end.

[0098] It is worth noting that understanding IDC1 as a traffic generating end and IDC2 as a 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 a traffic receiving end and IDC2 can be understood as a traffic generating end.

[0099] Specifically, L2GW1, L2GW2 and multicast controller 102 are respectively deployed in the cloud environment; traffic generation end IDC1 is deployed in the cloud environment. Multicast controller 102 receives 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 L2GW1; the traffic destination data is sent by L2GW2; the multicast controller 102 generates a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic source data and the traffic destination data; the multicast controller 102 performs forwarding control on the traffic to be forwarded based on the traffic forwarding path.

[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, including 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. Usually, the traffic source data is used to indicate the entities involved in the path from the traffic generation end to the first forwarding gateway corresponding to the traffic generation end. The traffic destination data is used to characterize the traffic destination of the traffic to be forwarded. Usually, 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] Among them, the traffic source data is sent by the first forwarding gateway (i.e. L2GW1) corresponding to the traffic generation end; the traffic destination data is sent by the first forwarding gateway (i.e. L2GW2) corresponding to the traffic receiving end; the first forwarding gateway (i.e. L2GW1) corresponding to the traffic generation end, the first forwarding gateway (i.e. L2GW2) corresponding to the traffic receiving end and the multicast controller are respectively deployed in the cloud environment; the traffic generation end (i.e. IDC1) is deployed in the cloud environment.

[0105] In an optional implementation, 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 alternative implementation, when the traffic receiving end is deployed in an external 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. Exemplarily, taking Figure 1 the application environment diagram shown as an example, the traffic receiving end IDC2 is deployed in the external cloud environment, the first forwarding gateway corresponding to the traffic generating end IDC1 is L2GW1, the first forwarding gateway corresponding to the traffic receiving end IDC2 is L2GW2, and L2GW1 and L2GW2 are communicatively connected.

[0107] Exemplarily, an extensible virtual local area network (Virtual eXtensible LAN, VXLAN) tunnel is formed between L2GW1 and L2GW2 for communication. It should be noted that for the same multicast group, the VXLAN network identifiers (VXLAN Network Identifier, VNI) of the tunnels formed between its respective L2GWs are the same.

[0108] S220, generate a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic source data and the traffic destination data.

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

[0110] Taking Figure 1 the application environment diagram shown as an example, according to the traffic source data (IDC1, VGW1, and L2GW1) and 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, perform forwarding control on the traffic to be forwarded based on the traffic forwarding path.

[0112] Exemplarily, 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, control the first forwarding gateway corresponding to the traffic receiving end to send the traffic to be forwarded to the traffic receiving end.

[0113] Specifically, taking 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 multicast traffic forwarding method, by deploying the first forwarding gateway corresponding to the traffic generating end and the 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 the traffic source data sent by the first forwarding gateway corresponding to the traffic generating end and the 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 the 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, and solves the problem of high network maintenance cost for on-cloud and off-cloud forwarding traffic that needs to be received on the cloud and forwarded via the physical network when part of the IDC of the traffic generating end and the traffic receiving end is on the cloud, while saving the cost of physical equipment.

[0115] Based on the technical solutions of the above embodiments, the present 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 traffic to be forwarded based on the traffic source data and the traffic destination data is given.

[0116] See also Figure 3 The steps of 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 is used to indicate basic information of the traffic generation end, for example, the first identification information may include IDC1. The second identification information is used to indicate basic information of the first forwarding gateway corresponding to the traffic generation end, for example, the second identification information may include L2GW1. The traffic output path is used to indicate the path of the traffic to be forwarded from the traffic generation end to the first forwarding gateway corresponding to the traffic generation 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 is used to indicate basic information of the traffic receiving end, for example, the third identification information may include IDC2. The fourth identification information is used to indicate basic information of the first forwarding gateway corresponding to the traffic receiving end, for example, the fourth identification information may include L2GW2. The traffic receiving path is used to indicate the path of the traffic to be forwarded 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] Exemplarily, when the traffic receiving end is deployed in a cloud environment, L2GW1->VM1 can be used as a 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] Exemplarily, 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] Exemplarily, 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 (that is, the first forwarding gateway corresponding to the traffic generation end) in FIG. 1 as an 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 sent by IDC1 through VGW1, and determine the traffic source data corresponding to the traffic to be forwarded.

[0131] Exemplarily, L2GW1 receives a traffic service message sent by VGW1. Since the traffic service message is a message encapsulated by two layers of VXLAN, L2GW1 can decapsulate the two layers of 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 two-layer VXLAN encapsulation of the traffic service message is as follows: the inner encapsulation includes the identification information of L2GW1; the outer encapsulation includes the identification information of IDC1 and the identification information of its corresponding VPC. It is worth noting that L2GW corresponds to VPC one-to-one, and L2GW connection corresponds to subnet in VPC one-to-one. 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 by two layers of VXLAN sent by IDC1, and unpacks 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 according to 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 multicast traffic forwarding method, by deploying the first forwarding gateway corresponding to the traffic generating end and the 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 the traffic source data sent by the first forwarding gateway corresponding to the traffic generating end and the 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 the 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, and solves the problem of high network maintenance cost for on-cloud and off-cloud forwarding traffic that needs to be received on the cloud and forwarded via the physical network when part of the IDC of the traffic generating end and the traffic receiving end is on the cloud, while saving the cost of physical equipment.

[0138] In an exemplary embodiment, Figure 5 As shown, a multicast traffic forwarding method is provided, which is applied to Figure 1 Taking L2GW2 (that is, the first forwarding gateway corresponding to the traffic receiving end) in FIG. 1 as an 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 sent by IDC2 through VGW2.

[0142] Exemplarily, 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, the decapsulated information is used as traffic destination data and the traffic destination data is sent 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 by two layers of VXLAN sent by IDC2, and unpacks 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, determining 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 the 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 multicast traffic forwarding method, by deploying the first forwarding gateway corresponding to the traffic generating end and the 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 the traffic source data sent by the first forwarding gateway corresponding to the traffic generating end and the 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 the 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, and solves the problem of high network maintenance cost for on-cloud and off-cloud forwarding traffic that needs to be received on the cloud and forwarded via the physical network when part of the IDC of the traffic generating end and the traffic receiving end is on the cloud, while saving the cost of physical equipment.

[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 of a user multicast group leaves, it can report an IGMP Report or IGMP Leave message to the multicast controller, and 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, the multicast controller can maintain the L2GW1->L2GW2 multicast distribution information table.

[0152] Based on the technical solutions of the above embodiments, the present application also provides an optional embodiment. In this optional embodiment, the multicast traffic forwarding method provided by the present application is applied to Figure 1 Taking the application environment shown in the figure as an example, the method is described 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 sending of traffic to be forwarded;

[0155] For example, when VGW2 receives the Overlay IGMPReport initial request message of two-layer VXLAN encapsulation sent by IDC2 through the dedicated line, it decapsulates the outer dedicated line VXLAN, and identifies the MAC address of the VXLAN tunnel endpoint (VXLAN Tunnel EndPoint, VTEP) of L2GW2 according to the media access control address (Media Access Control Address, MAC) of the inner VXLAN message tunnel, and then identifies the initial request message as relay traffic, searches for the L2GW2 connection to re-encapsulate the outer VXLAN, obtains the multicast on-demand request, and sends the multicast on-demand request to L2GW2;

[0156] S602, L2GW2 determines 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] Exemplarily, L2GW2 decapsulates the two-layer VXLAN encapsulation of the multicast on-demand request, identifies the Overlay IGMP Report message, and further identifies it as proxy traffic, configures the three-layer logical port L2GWLOOPm (m is the logical port number), and maintains the L2GW2 connection multicast VXLAN table, that is, establishes the 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 generation 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 the overlay initial service message of two-layer VXLAN encapsulation sent by IDC1 outside the cloud through a dedicated line, decapsulates the outer dedicated line VXLAN, and identifies the MAC address of the VTEP of L2GW1 according to the dmac of the inner VXLAN message tunnel, and further identifies it as relay traffic, searches for L2GW1 to connect and re-encapsulate the outer VXLAN, obtains the traffic service message, and sends the traffic service message to L2GW1; further, L2GW1 decapsulates the two-layer VXLAN, identifies it as an overlay traffic service message, and refreshes the L2GW1 connection multicast VXLAN table, that is, establishes the connection record between L2GW1 and L2GW2;

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

[0164] Among them, L2GW1, L2GW2 and multicast controller are deployed in the cloud environment respectively; the traffic generation end is deployed in the cloud environment; when the traffic receiving end is deployed in the cloud environment, L2GW1 is the same as L2GW2; when the traffic receiving end is deployed in the cloud environment, L2GW1 is connected to L2GW2 for communication;

[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 generation end according to the traffic output path, and sends the traffic to be forwarded to L2GW2;

[0171] Among them, L2GW1 configures the Layer 3 logical interface Internet Protocol (IP) address and creates a transparent transmission tunnel 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 above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed 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 part of the steps or stages in other steps.

[0174] Based on the same inventive concept, the embodiment of the present application also provides a multicast traffic forwarding device for implementing the multicast traffic forwarding method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more multicast traffic forwarding device embodiments provided below can refer to the limitations on the multicast traffic forwarding method above, 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 with 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 to be forwarded 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 according to the first identification information and the second identification information; a second generation unit, which is used to generate a traffic receiving path according to 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 determination module 810 and a first sending module 820, wherein:

[0182] The first determination module 810 is used to receive the traffic to be forwarded from the traffic generation end, and determine the 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, Fig. 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 used to receive a multicast on-demand request from a traffic receiving end; the multicast on-demand request is used to request to send the traffic to be forwarded.

[0187] The second determination module 920 is used to determine the 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 by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to 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. Fig.10 As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through 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 an 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 the 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 an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, a multicast traffic forwarding method is implemented. The display unit of the computer device is used to form a visually visible picture, which 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 shell, or an external keyboard, touchpad or mouse.

[0192] Those skilled in the art will understand that Fig.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 those shown in the figure, or combine certain components, or have a different arrangement of components.

[0193] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned 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 can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and 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 embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (Read->OnlyMemory, 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. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0198] The technical features of the above embodiments may be combined arbitrarily. 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 only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A multicast traffic forwarding method, characterized in that: Applied to a multicast controller, the method comprises: 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 a traffic generating end; the traffic destination data is sent by a first forwarding gateway corresponding to a 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; the traffic generating end is deployed in an out-of-cloud environment; Generate a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic source data and the traffic destination data; Based on the traffic forwarding path, forwarding control is performed on the traffic to be forwarded.

2. The method according to claim 1, characterized in that 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, generating the traffic forwarding path corresponding to the to-be-forwarded traffic according to the traffic source data and the traffic destination data includes: Generate a traffic output path according to the first identification information and the second identification information; Generate a traffic receiving path according to the third identification information and the fourth identification information; 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.

3. 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 out-of-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.

4. The method according to any one of claims 1 to 3, characterized in that The forwarding control of the to-be-forwarded traffic based on the traffic forwarding path includes: 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.

5. A multicast traffic forwarding method, characterized in that: Applied to a first forwarding gateway corresponding to a traffic generation end, the method comprises: Receive the traffic to be forwarded from the traffic generating end, and determine the traffic source data corresponding to the traffic to be forwarded; The traffic source data is sent to a multicast controller, so that the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic source data and the traffic destination data determined by the 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; 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.

6. 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; Determine the traffic destination data corresponding to the traffic to be forwarded; The traffic destination data is sent to a multicast controller, so that the multicast controller generates 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 performs forwarding control on the traffic to be forwarded based on the traffic forwarding path; 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.

7. A multicast traffic forwarding device, characterized in that: Deployed on a multicast controller, the device includes: A 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 a first forwarding gateway corresponding to the traffic generating end; 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; the traffic generating end is deployed in an out-of-cloud environment; A generation module, used for generating a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic source data and the traffic destination data; A forwarding module is used to control the forwarding of the to-be-forwarded traffic based on the traffic forwarding path.

8. A multicast traffic forwarding device, characterized in that: A first forwarding gateway deployed at a traffic generation end, the device comprising: A first determination module is used to receive the to-be-forwarded traffic from the traffic generation end, and determine the traffic source data corresponding to the to-be-forwarded traffic; A first sending module, used to send the traffic source data to the multicast controller, so that the multicast controller generates a traffic forwarding path corresponding to the traffic to be forwarded according to the traffic source data and the traffic destination data determined by the 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; 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.

9. A multicast traffic forwarding device, characterized in that: A first forwarding gateway deployed at a traffic receiving end, the device comprising: A 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 to send the traffic to be forwarded; A second determination module is used to determine the traffic destination data corresponding to the traffic to be forwarded; A second sending module is used 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 according to 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; 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.

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

Citation Information

Patent Citations

  • Multicast communication method, device and system, computer equipment and storage medium

    CN116996585A

  • Multicast forwarding method and device of cloud network, computer equipment and storage medium

    CN117880184A

  • Implementation method and device for receiving out-of-cloud multicast traffic in cloud and storage medium

    CN118748741A

  • Implementation method and device for sending intra-cloud multicast source to outside of cloud and storage medium

    CN118803378A

  • Multicast traffic forwarding device, method, equipment and medium

    CN119052196A