Multicast forwarding method, electronic device and computer readable storage medium

Abstract

A multicast forwarding method, an electronic device, a computer-readable storage medium, and a computer program product. The multicast forwarding method comprises: acquiring multicast traffic to be forwarded and sending a first multicast auto-discovery route to a target node (S100); when both an encapsulation extended community attribute carried by the first multicast auto-discovery route and a supplier multicast service interface meet a preset condition, generating forwarding route information on the basis of the supplier multicast service interface (S200); and forwarding said multicast traffic to the target node on the basis of the forwarding route information (S300).

Description

Multicast forwarding method, electronic device and computer readable storage medium

[0001] Cross-reference to Related Applications

[0002] The present application is based on and claims priority to Chinese Patent Application No. 2024106300662, filed on May 20, 2024, the entire contents of which are incorporated herein by reference. TECHNICAL FIELD

[0003] Embodiments of the present application relate to, but are not limited to, the technical field of communication, and particularly relate to a multicast forwarding method, an electronic device, a computer readable storage medium and a computer program product. BACKGROUND

[0004] Virtual eXtensible Local Area Network (VXLAN) is a commonly used data plane technology for Ethernet Virtual Private Network (EVPN). In the application scenario of interworking between layer 2 and layer 3 multicast that has appeared recently, in order to simplify the data plane, it is required that the traffic of layer 3 multicast is also forwarded through VXLAN. Different from the EVPN technology which can carry VXLAN Network Identifier (VNI) and other related information through Border Gateway Protocol (BGP) EVPN address family routing, the BGP Multicast Virtual Private Network (MVPN) multicast protocol address family routing used by the MVPN technology does not carry any VXLAN information. At present, the main solution in the industry is to let the Provider Edge (PE) of the MVPN configure the same static VXLAN, and only support the case of using Protocol Independent Multicast-Sparse Mode (PIM-SM) shared tree at the bottom layer of VXLAN, which will make the process of multicast forwarding traffic not flexible enough. SUMMARY

[0005] The following is an overview of subject matter of the detailed description herein. This overview is not intended to limit the scope of the claims.

[0006] Embodiments of the present application provide a multicast forwarding method, an electronic device, a computer readable storage medium and a computer program product.

[0007] In a first aspect, an embodiment of the present application provides a multicast forwarding method, which comprises: obtaining multicast traffic to be forwarded and sending a first multicast automatic discovery route to a target node; in a case where an encapsulated extended community attribute and a vendor multicast service interface carried by the first multicast automatic discovery route both meet preset conditions, generating a forwarding route information according to the vendor multicast service interface; and forwarding the multicast traffic to be forwarded to the target node according to the forwarding route information.

[0008] In a second aspect, an embodiment of the present application provides a multicast forwarding method, which comprises: obtaining a first multicast automatic discovery route sent by a source node, and receiving multicast traffic to be forwarded forwarded by the source node according to a forwarding route information; wherein in a case where an encapsulated extended community attribute and a vendor multicast service interface carried by the first multicast automatic discovery route both meet preset conditions, the forwarding route information is generated according to the vendor multicast service interface.

[0009] In a third aspect, an embodiment of the present application provides an electronic device, which comprises: at least one processor; at least one memory configured to store at least one program; and a multicast forwarding method as described above is implemented when the at least one program is executed by the at least one processor.

[0010] In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, which stores computer executable instructions, and the computer executable instructions are used to execute a multicast forwarding method as described above.

[0011] In a fifth aspect, an embodiment of the present application provides a computer program product, which comprises a computer program or computer instructions, and the computer program or the computer instructions are stored in a computer readable storage medium, a processor of a computer device reads the computer program or the computer instructions from the computer readable storage medium, and the processor executes the computer program or the computer instructions, so that the computer device executes a multicast forwarding method as described above. BRIEF DESCRIPTION OF DRAWINGS

[0012] The accompanying drawings are used to further understand the technical scheme of the present application, and constitute a part of the specification, and are used to explain the technical scheme of the present application together with embodiments of the present application, and do not constitute a limitation to the technical scheme of the present application.

[0013] FIG. 1 is a flowchart of a multicast forwarding method provided by an embodiment of the present application;

[0014] FIG. 2 is a flowchart of generating a forwarding route information provided by an embodiment of the present application;

[0015] FIG. 3 is a flowchart of forwarding multicast traffic to be forwarded provided by an embodiment of the present application;

[0016] Figure 4 is a flow chart of generating forwarding route information according to another embodiment of the present application;

[0017] Figure 5 is a flow chart of forwarding multicast traffic according to another embodiment of the present application;

[0018] Figure 6 is a flow chart of generating forwarding route information according to another embodiment of the present application;

[0019] Figure 7 is a flow chart of forwarding multicast traffic according to another embodiment of the present application;

[0020] Figure 8 is a flow chart of a multicast forwarding method according to another embodiment of the present application;

[0021] Figure 9 is a flow chart of a multicast forwarding method according to another embodiment of the present application;

[0022] Figure 10 is a schematic diagram of an encapsulating extended group attribute structure according to an embodiment of the present application;

[0023] Figure 11 is a schematic diagram of a provider multicast service interface tunnel attribute structure according to an embodiment of the present application;

[0024] Figure 12 is a schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and should not be used to limit the present application.

[0026] It should be noted that although the functional modules are divided in the device schematic diagram and the logical order is shown in the flow chart, in some cases, the steps shown or described can be executed in a manner different from the module division in the device or the order in the flow chart. The terms "first", "second", etc. in the specification and claims and the above-described drawings are used to distinguish similar objects and do not necessarily describe a specific order or sequence.

[0027] In the description of the present application, the meaning of "one or more" is one or more, the meaning of "more" is two or more, greater than, less than, more than, etc. are understood as not including the number, above, below, etc. are understood as including the number. If it is described as first, second, etc. is only used to distinguish technical features for the purpose, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features or implicitly indicating the sequence of indicated technical features.

[0028] In the description of the present application, the words such as setting, installing, connecting and the like should be understood in a broad sense unless otherwise explicitly limited, and the skilled in the art can determine the specific meaning of the above words in the present application in combination with the specific content of the technical solution.

[0029] The embodiment of the present application provides a multicast forwarding method, an electronic device, a computer readable storage medium and a computer program product. In the process of multicast forwarding, first, the to-be-forwarded multicast traffic is acquired and a first multicast automatic discovery route is sent to a target node; then, in the case that the encapsulated extended group attribute carried by the first multicast automatic discovery route and the vendor multicast service interface both meet preset conditions, the forwarding route information can be generated according to the vendor multicast service interface; finally, the to-be-forwarded multicast traffic is forwarded to the target node according to the forwarding route information. According to the technical solution provided by the embodiment of the present application, in the case that the encapsulated extended group attribute carried by the first multicast automatic discovery route and the vendor multicast service interface both meet preset conditions, the forwarding route information can be generated according to the vendor multicast service interface, which can well improve the flexibility of multicast forwarding.

[0030] The embodiment of the present application is further described below with reference to the accompanying drawings.

[0031] As shown in FIG. 1, the embodiment of the first aspect of the present application provides a flow chart of a multicast forwarding method. The method includes but is not limited to step S100, step S200 and step S300.

[0032] Step S100, acquiring to-be-forwarded multicast traffic and sending a first multicast automatic discovery route to a target node.

[0033] Step S200, in the case that the encapsulated extended group attribute carried by the first multicast automatic discovery route and the vendor multicast service interface both meet preset conditions, generating forwarding route information according to the vendor multicast service interface.

[0034] Step S300, forwarding the to-be-forwarded multicast traffic to the target node according to the forwarding route information.

[0035] In some embodiments of the present application, first, the to-be-forwarded multicast traffic is acquired and a first multicast automatic discovery route is sent to a target node; then, in the case that the encapsulated extended group attribute carried by the first multicast automatic discovery route and the vendor multicast service interface both meet preset conditions, the forwarding route information can be generated according to the vendor multicast service interface; finally, the to-be-forwarded multicast traffic is forwarded to the target node according to the forwarding route information. According to the technical solution provided by the embodiment of the present application, in the case that the encapsulated extended group attribute carried by the first multicast automatic discovery route and the vendor multicast service interface both meet preset conditions, the forwarding route information can be generated according to the vendor multicast service interface, which can well improve the flexibility of multicast forwarding.

[0036] It is worth noting that the multicast traffic to be forwarded is multicast data that needs to be processed for forwarding, where the multicast data can be video stream data, audio stream data, image data, or text data, which is not limited herein. In the present application, the multicast automatic discovery route can be a BGP MVPN MCAST Intra-AS I-PMSI A-D route; where BGP stands for Border Gateway Protocol, which is an inter-domain routing protocol; MVPN stands for Multicast Virtual Private Network, which is a multicast virtual private network; MCAST stands for multicast; Intra-AS I-PMSI A-D route stands for Intra-AS Inclusive-Provider Multicast Service Interface Auto-Discovery route, which is an autonomous system intra-inclusive provider multicast service interface automatic discovery route. The encapsulation extended community in the present application is Encapsulation EC, which stands for Encapsulation Extended Community, where the tunnel type field in the extended community attribute is set to VXLAN (Virtual eXtensible Local Area Network). The provider multicast service interface in the present application is PMSI Tunnel, which stands for Provider Multicast Service Interface Tunnel Attribute.

[0037] It is worth noting that the network node in the multicast virtual private network can generate corresponding forwarding route information according to the provider multicast service interface when both the encapsulation extended community attribute carried by the multicast automatic discovery route and the provider multicast service interface satisfy the preset condition; and the received multicast traffic can be processed for forwarding according to the forwarding route information.

[0038] In some embodiments of the present application, the preset condition in the present application can include that the tunnel type field of the encapsulation extended community attribute carried by the first multicast automatic discovery route is a virtual extended local area network, the tunnel type of the provider multicast service interface is a preset tunnel type, and the label field of the provider multicast service interface is a network identifier of the virtual extended local area network. It can be understood that the second multicast automatic discovery route can also generate corresponding forwarding route information when the preset condition is satisfied.

[0039] It is worth noting that the received first multicast automatic discovery route carries a tunnel type field encapsulating an extended community attribute, which is a virtual extended local area network, and the multicast automatic discovery route carries a tunnel type of a provider multicast service interface, which is a preset tunnel type, and a label field of the provider multicast service interface is a network identifier of the virtual extended local area network, and the forwarding route information is generated according to the provider multicast service interface when the three conditions are met. The preset tunnel type includes a protocol independent multicast-sparse mode (PIM-SM), a protocol independent multicast-source-specific multicast (PIM-SSM), and ingress replication (IR). The application provides a method for generating a BGP MVPN control plane protocol route for a data plane of VXLAN, allowing the edge device of the MVPN to dynamically learn the VXLAN information of other edge devices and establish a VXLAN tunnel with a PIM-SM, PIM-SSM, or IR as the underlying layer.

[0040] As shown in FIG. 2, the tunnel type includes a protocol independent multicast-source-specific multicast, and the tunnel identifier of the provider multicast service interface includes a first public network root node address and a first public network multicast group address. The step S200 includes but is not limited to step S210.

[0041] In step S210, a protocol independent multicast-source-specific multicast join message is sent from the target node to the first public network root node address to generate a protocol independent multicast-source-specific multicast forwarding tree of the public network, and the protocol independent multicast-source-specific multicast forwarding tree is virtual extended local area forwarding route information.

[0042] In some embodiments of the application, in the process of generating the forwarding route information according to the provider multicast service interface, a protocol independent multicast-source-specific multicast join message is sent from the target node to the first public network root node address to generate a protocol independent multicast-source-specific multicast forwarding tree of the public network, and the protocol independent multicast-source-specific multicast forwarding tree is virtual extended local area forwarding route information. Subsequently, the related to-be-forwarded multicast traffic can be forwarded according to the protocol independent multicast-source-specific multicast forwarding tree.

[0043] As shown in FIG. 3, the step S300 includes but is not limited to step S310 and step S320.

[0044] Step S310, encapsulating the first virtual extended local area network encapsulation header and the first network layer encapsulation header in sequence to obtain encapsulated multicast traffic, wherein the identifier field of the first virtual extended local area network encapsulation header is the network identifier of the virtual extended local area network, the source address of the first network layer encapsulation header is the first public network root node address, and the destination address of the first network layer encapsulation header is the first public network multicast group address.

[0045] Step S320, forwarding the encapsulated multicast traffic to the target node according to the protocol-independent multicast designated source multicast forwarding tree.

[0046] In some embodiments of the present application, in the process of forwarding the to-be-forwarded multicast traffic to the target node according to the forwarding routing information, the first virtual extended local area network encapsulation header and the first network layer encapsulation header can be encapsulated in sequence to obtain encapsulated multicast traffic, and then the encapsulated multicast traffic can be forwarded to the target node according to the protocol-independent multicast designated source multicast forwarding tree, so as to realize the forwarding processing of the multicast traffic. The whole process is relatively simple and fast, and makes the forwarding of multicast data more flexible, which can select the corresponding tunnel type for data forwarding processing according to actual needs.

[0047] It is worth noting that the identifier field of the first virtual extended local area network encapsulation header is the network identifier of the virtual extended local area network, the source address of the first network layer encapsulation header is the first public network root node address, and the destination address of the first network layer encapsulation header is the first public network multicast group address.

[0048] As shown in FIG. 4, the tunnel type includes a protocol-independent multicast sparse mode, the tunnel attribute of the vendor multicast service interface includes a second public network multicast group address, and the above step S200 includes but is not limited to step S220.

[0049] Step S220, sending a protocol-independent multicast generic membership join message to the rendezvous point of the second public network multicast group address by the target node to generate a protocol-independent multicast sparse mode shared forwarding tree of the public network, wherein the protocol-independent multicast sparse mode shared forwarding tree is the forwarding routing information of the virtual extended local area network.

[0050] In some embodiments of the present application, in the process of generating the forwarding routing information according to the vendor multicast service interface, a protocol-independent multicast generic membership join message is sent to the rendezvous point of the second public network multicast group address by the target node to generate a protocol-independent multicast sparse mode shared forwarding tree of the public network, wherein the protocol-independent multicast sparse mode shared forwarding tree is the forwarding routing information of the virtual extended local area network, and then the related to-be-forwarded multicast traffic can be forwarded according to the protocol-independent multicast sparse mode shared forwarding tree.

[0051] As shown in FIG. 5, the tunnel attribute of the provider multicast service interface includes a second public network sending address, and the step S300 includes but is not limited to a step S330 and a step S340.

[0052] The step S330 encapsulates a second virtual extended local area network header and a second network layer header in the multicast traffic to be forwarded in sequence to obtain encapsulated multicast traffic, wherein the identification field of the second virtual extended local area network header is a network identifier of the virtual extended local area network, the source address of the second network layer header is the second public network sending address, and the destination address of the second network layer header is the second public network multicast group address.

[0053] The step S340 forwards the encapsulated multicast traffic to the target node according to a public network protocol-independent multicast sparse mode shared forwarding tree.

[0054] In some embodiments of the present application, in the process of forwarding processing the multicast traffic to be forwarded according to the forwarding routing information, a second virtual extended local area network header and a second network layer header are encapsulated in the multicast traffic to be forwarded in sequence to obtain encapsulated multicast traffic, and then the encapsulated multicast traffic is forwarded to the target node according to a public network protocol-independent multicast sparse mode shared forwarding tree. The whole process is relatively simple and fast, and makes the multicast data forwarding more flexible, which can select a corresponding tunnel type for data forwarding processing according to actual needs.

[0055] It is worth noting that the identification field of the second virtual extended local area network header is a network identifier of the virtual extended local area network, the source address of the second network layer header is the second public network sending address, and the destination address of the second network layer header is the second public network multicast group address.

[0056] As shown in FIG. 6, the tunnel type is ingress replication, the tunnel attribute of the provider multicast service interface includes a third public network routing address, and the step S200 includes but is not limited to a step S230 and a step S240.

[0057] The step S230 generates an ingress replication list according to the third public network routing address carried by the second multicast automatic discovery route, wherein the second multicast automatic discovery route is announced and sent by the target node.

[0058] The step S240 determines the ingress replication list as the forwarding routing information of the virtual extended local area network.

[0059] In some embodiments of the present application, in the process of generating the forwarding routing information according to the provider multicast service interface, an ingress replication list is generated according to the third public network routing address carried by the second multicast automatic discovery route, and then the ingress replication list is determined as the forwarding routing information of the virtual extended local area network, and subsequent forwarding processing of the related multicast traffic to be forwarded can be performed according to the ingress replication list.

[0060] It is worth noting that the second multicast automatic discovery route sends a notification for the target node.

[0061] As shown in FIG. 7, the above step S300 includes but is not limited to step S350 and step S360.

[0062] In step S350, a third virtual extended local area network encapsulation header and a third network layer encapsulation header are sequentially encapsulated on the to-be-forwarded multicast traffic to obtain an encapsulated multicast traffic, wherein the identification field of the third virtual extended local area network encapsulation header is a network identifier of a virtual extended local area network carried by the second multicast automatic discovery route, the source address of the third network layer encapsulation header is the third public network route address, and the destination address of the third network layer encapsulation header is the third public network route address carried by the second multicast automatic discovery route.

[0063] In step S360, the encapsulated multicast traffic is forwarded to the target node according to the ingress replication list.

[0064] In some embodiments of the present application, in the process of forwarding processing the to-be-forwarded multicast traffic according to the forwarding route information, a third virtual extended local area network encapsulation header and a third network layer encapsulation header are sequentially encapsulated on the to-be-forwarded multicast traffic to obtain an encapsulated multicast traffic, and then the encapsulated multicast traffic is forwarded to the target node according to the ingress replication list, so as to realize the forwarding processing of the multicast traffic, and make the multicast data forwarding more flexible.

[0065] It is worth noting that the identification field of the third virtual extended local area network encapsulation header is a network identifier of a virtual extended local area network carried by the second multicast automatic discovery route, the source address of the third network layer encapsulation header is the third public network route address, and the destination address of the third network layer encapsulation header is the third public network route address carried by the second multicast automatic discovery route.

[0066] As shown in FIG. 8, after the above step S300 is executed, the multicast forwarding method can further include but is not limited to step S400.

[0067] In step S400, the target node receives the encapsulated multicast traffic, and determines the corresponding multicast virtual private network instance according to the network identifier in the encapsulated multicast traffic.

[0068] In some embodiments of the present application, after the to-be-forwarded multicast traffic is processed according to the forwarding route information, the target node receives the encapsulated multicast traffic, and determines the corresponding multicast virtual private network instance according to the network identifier in the encapsulated multicast traffic; in the embodiments of the present application, each network identifier has uniqueness, and each network identifier corresponds to a multicast virtual private network instance; by identifying the network identifier in the encapsulated multicast traffic, the corresponding multicast virtual private network instance can be obtained, and the whole identification process is simple and fast.

[0069] As shown in FIG. 9, the second aspect of the present application provides a flow chart of a multicast forwarding method. The method includes but is not limited to step S500.

[0070] In step S500, a first multicast automatic discovery route sent by a source node is acquired, and a forwarding route information is generated according to a provider multicast service interface, and a to-be-forwarded multicast traffic forwarded by the source node is received according to the forwarding route information; wherein, in a case that the encapsulation extended community attribute carried by the first multicast automatic discovery route and the provider multicast service interface both meet preset conditions, the forwarding route information is generated according to the provider multicast service interface.

[0071] In some embodiments of the present application, in the process of multicast forwarding, a first multicast automatic discovery route sent by a source node is acquired, and a forwarding route information is generated according to a provider multicast service interface, and a to-be-forwarded multicast traffic forwarded by the source node is received according to the forwarding route information; wherein, in a case that the encapsulation extended community attribute carried by the first multicast automatic discovery route and the provider multicast service interface both meet preset conditions, the forwarding route information is generated according to the provider multicast service interface. According to the technical solution provided by the embodiments of the present application, in a case that the encapsulation extended community attribute carried by the first multicast automatic discovery route and the provider multicast service interface both meet preset conditions, the forwarding route information can be generated according to the provider multicast service interface, which can improve the flexibility of multicast forwarding.

[0072] In some embodiments of the present application, the preset conditions include: a tunnel type field of the encapsulation extended community attribute carried by the first multicast automatic discovery route is a virtual extended local area network, a tunnel type of the provider multicast service interface is a preset tunnel type, and a label field of the provider multicast service interface is a network identifier of the virtual extended local area network.

[0073] In order to more clearly illustrate the flow of the multicast forwarding method provided by the embodiments of the present application, the following will be described with specific examples.

[0074] As shown in FIG. 10, FIG. 10 is a structure diagram of an encapsulation extended community attribute carried by a BGP MVPN MCAST address family Intra-AS I-PMSI A-D route.

[0075] The application is to solve the problem that the underlying can only use PIM-SM shared tree when the data plane is VXLAN. In the attribute field of BGP MVPN MCAST address family Intra-AS I-PMSI A-D route, an Encapsulation extended community attribute as shown in FIG. 10 will be added. The Type Code and Flags fields respectively represent the type and corresponding flag bit of the extended community attribute, and the specific values remain consistent with RFC9012. The Tunnel Type field represents the tunnel type, which is set to 0x0008 when the data plane is VXLAN, which is the value allocated by The Internet Assigned Numbers Authority (IANA) for VXLAN Encapsulation.

[0076] As shown in FIG. 11, FIG. 11 is a structural diagram of a provider multicast service interface tunnel attribute carried in a BGP MVPN MCAST address family Intra-AS I-PMSI A-D route.

[0077] Wherein, Tunnel Type is 0x03 and 0x04 respectively corresponding to tunnel type PIM-SSM and PIM-SM. RFC6514 specifies that when tunnel type is PIM-SSM and PIM-SM, MPLS Label field needs to be set to 0, Tunnel ID field needs to carry <P-Root Node Address, P-Multicast Group> information, wherein P-Root Node Address is a public routable address on the MVPN PE device, and P-Multicast Group is a public multicast group address. In RFC6514, when PE receives Intra-AS I-PMSI A-D route with PMSI indicating tunnel type PIM-SSM, it will send PIM SG join message to multicast group P-Multicast Group, wherein the source is P-Root Node Address, and generate public PIM-SSM forwarding tree; when PE receives Intra-AS I-PMSI A-D route with PMSI indicating tunnel type PIM-SM, it will send PIM SG join message to the rendezvous point of multicast group P-Multicast Group, and generate public PIM-SM shared forwarding tree. When ingress PE receives private multicast traffic, it first encapsulates generic routing encapsulation (GRE) header and then encapsulates outer IP header, the source address of outer IP is P-Root Node Address of ingress PE, and the destination address of outer IP is P-Multicast Group, and the traffic is sent along the public multicast forwarding tree, and the egress PE receives the traffic from the public network and determines the corresponding MVPN instance according to the outer destination IP address. Tunnel Type field in PMSI Tunnel Attribute is 0x06 indicating tunnel type ingress replication, and RFC6514 specifies that when tunnel type is ingress replication, Tunnel ID field is the public routable address of PE, and MPLS Label field is the non-0 label allocated by the downstream. Ingress PE receives BGP MVPN MCAST Intra-AS I-PMSI A-D route announced by each egress PE, generates ingress replication list using MPLS Label and Tunnel ID information carried by the route, and when receiving private multicast traffic, encapsulates the label announced by egress PE in PMSI in the inner layer and encapsulates unicast tunnel label in the outer layer, and the egress PE determines the corresponding MVPN instance according to the label information encapsulated by the traffic when receiving the traffic.

[0078] In the present application, the data plane of the VXLAN MVPN PE device adds an Encapsulation extension community when announcing the Intra-AS I-PMSI A-D route. The PMSI carried originally also has a corresponding modification. When the underlying layer of VXLAN uses PIM-SSM or PIM-SM, the MPLS Label field in the PMSI, which should be set to 0 originally, is set to the VXLAN VNI configured by the PE this time, and the settings of other fields remain unchanged. The process of establishing a multicast forwarding tree in the public network also remains unchanged. When the ingress PE receives private network multicast traffic, the VXLAN header and the outermost IP header are encapsulated, the VNI field of the VXLAN header is filled with the value of the MPLS Label in the PMSI, and the outermost IP header is filled with the source and group addresses of the multicast forwarding tree in the public network. The egress PE receives traffic from the public network and determines the corresponding MVPN instance according to the VNI in the VXLAN header.

[0079] When the underlying layer of VXLAN uses IR, the MPLS Label field in the PMSI, which should be allocated to the downstream and is not 0 originally, is set to the VXLAN VNI configured by the PE this time, and the settings of other fields remain unchanged. The way of generating the ingress replication list also remains unchanged. When the ingress PE receives private network multicast traffic, the VXLAN header and the outermost IP header are encapsulated, the VNI field of the VXLAN header is filled with the MPLS Label in the PMSI announced by the egress PE, that is, the VXLAN VNI of the remote PE, and the source IP address of the outermost IP header is the Tunnel ID of the ingress PE in the PMSI, and the destination IP address is the Tunnel ID of the PMSI announced by the egress PE. The egress PE receives traffic from the public network and determines the corresponding MVPN instance according to the VNI in the VXLAN header.

[0080] In some embodiments of the present application, if the received Intra-AS I-PMSI A-D route does not carry the Encapsulation extension community attribute in the BGP attribute, continue to process according to the provisions of the MVPN related protocols such as RFC6514. If the Tunnel Type field in the Encapsulation extension community attribute carried by the route indicates the VXLAN type, and the tunnel type in the PMSI tunnel attribute carried is PIM-SSM or PIM-SM or IR, and the label field in the PMSI tunnel attribute is not 0, establish the underlying multicast forwarding tree or unicast replication list of VXLAN according to the information of the PMSI, otherwise, go to the exception handling. The process of establishing the multicast forwarding tree and the unicast replication list remains consistent with the MVPN protocols such as RFC6514, except that VXLAN encapsulation is used for data forwarding.

[0081] In the related art, the current MVPN uses a VXLAN data plane, because the Intra-ASI-PMSI A-D route advertised between PEs cannot carry the PMSI attribute, so the underlying layer of the VXLAN can only use a PIM-SM shared tree, and it is impossible to confirm whether the configurations between PEs are consistent. The application allows the underlying layer of the VXLAN to interact with the information used by the VXLAN between PEs, thereby allowing the underlying layer of the VXLAN to use PIM-SSM and IR tunnels.

[0082] In order to solve the problem that when the MVPN multicast virtual private network uses a VXLAN virtual extended local area network data plane to forward a layer 3 multicast flow, the underlying layer of the VXLAN can only use a PIM-SM shared tree, and cannot use a protocol-independent multicast specified source multicast and ingress replication, the application provides a generation method for a BGP MVPN control plane protocol route of a data plane being a VXLAN, allowing the PE device of the MVPN to dynamically learn the VXLAN information of other PEs, and establishing a VXLAN tunnel with the underlying layer being PIM-SSM or IR.

[0083] In the BGP MVPN MCAST address family route, the Intra-AS I-PMSI A-D route carries an encapsulation extended community attribute, in which the tunnel type field is set to VXLAN; in the BGP MVPN MCAST Intra-AS I-PMSI A-D route, the label field in the provider multicast service interface tunnel attribute is set to the VNI of the VXLAN, the tunnel type field is set to PIM-SM, PIM-SSM or IR according to the underlying layer configuration of the VXLAN, and the tunnel identifier is set to (PE local address, multicast group address) or the PE local address according to the tunnel type field. When the MVPN PE device learns the BGP MVPN MCAST address family Intra-AS I-PMSI A-D route of a remote PE, and the route carries the tunnel type field as VXLAN in the Encapsulation EC, the PMSI tunnel attribute carried by the route will be parsed in the VXLAN mode, that is, the label field in the PMSI is parsed as the VNI of the VXLAN. The address of the remote PE is learned from the tunnel identifier information, and the underlying PIM-SM, PIM-SSM or IR tunnel of the VXLAN is constructed.

[0084] In addition, as shown in FIG. 12, one embodiment of the application further provides an electronic device 700, which comprises:

[0085] The memory 720, the processor 710, and the computer program stored in the memory 720 and executable on the processor 710.

[0086] The processor 710 and the memory 720 can be connected by a bus or other means.

[0087] It should be noted that the electronic device 700 in the embodiment and the multicast forwarding method in the above embodiment belong to the same inventive concept, and therefore the embodiments have the same implementation principles and technical effects, which will not be described in detail here.

[0088] The non-transitory software programs and instructions required to implement the multicast forwarding method of the above embodiment are stored in the memory 720, and when executed by the processor 710, the multicast forwarding method in the above embodiment is executed.

[0089] In addition, one embodiment of the present application also provides a computer readable storage medium, which stores computer executable instructions, and the computer executable instructions are executed by a processor 710, for example, a processor 710 in the above electronic device 700 embodiment, so that the above processor 710 executes the multicast forwarding method in the above embodiment.

[0090] In addition, one embodiment of the present application also provides a computer program product, which includes a computer program or computer instructions, and the computer program or the computer instructions are stored in a computer readable storage medium, and a processor of a computer device reads the computer program or the computer instructions from the computer readable storage medium, and the processor executes the computer program or the computer instructions, so that the computer device executes the multicast forwarding method in the above embodiment.

[0091] The embodiment of the present application includes: in the process of multicast forwarding, first, obtaining the to-be-forwarded multicast traffic and sending a first multicast automatic discovery route to a target node; then, in the case that the encapsulated extended group attribute carried by the first multicast automatic discovery route and the provider multicast service interface both meet preset conditions, the forwarding route information can be generated according to the provider multicast service interface; finally, the to-be-forwarded multicast traffic is forwarded to the target node according to the forwarding route information. According to the technical scheme provided by the embodiment of the present application, in the case that the encapsulated extended group attribute carried by the first multicast automatic discovery route and the provider multicast service interface both meet preset conditions, the forwarding route information can be generated according to the provider multicast service interface, which can well improve the flexibility of multicast forwarding.

[0092] As will be appreciated by one of ordinary skill in the art, all or some of the steps, systems, and techniques disclosed herein can be embodied in software, firmware, hardware, and / or suitable combination thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a micro-processing unit, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on computer readable media, which can comprise computer storage media (or non-transitory media), and communication media (or transitory media). As is well known to those of ordinary skill in the art, the term computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Further, as is well known to those of ordinary skill in the art, communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media.

[0093] The above description is implemented by several embodiments of the present application, but the present application is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or replacements without departing from the scope of the present application. These equivalent modifications or replacements are included in the scope defined by the claims of the present application.

Claims

1. A multicast forwarding method, the method comprising: acquiring multicast traffic to be forwarded and sending a first multicast auto-discovery route to a target node; in a case where both an encapsulation extended community attribute carried by the first multicast auto-discovery route and a vendor multicast service interface meet preset conditions, generating a forwarding route information according to the vendor multicast service interface; forwarding the multicast traffic to be forwarded to the target node according to the forwarding route information.

2. The multicast forwarding method according to claim 1, wherein, the preset conditions comprise: a tunnel type field of the encapsulation extended community attribute carried by the first multicast auto-discovery route is a virtual extended local area network, a tunnel type of the vendor multicast service interface is a preset tunnel type, and a label field of the vendor multicast service interface is a network identifier of the virtual extended local area network.

3. The multicast forwarding method according to claim 2, wherein, the tunnel type of the vendor multicast service interface is protocol independent multicast specified source multicast, a tunnel identifier of the vendor multicast service interface comprises a first public network root node address and a first public network multicast group address, and the generating the forwarding route information according to the vendor multicast service interface comprises: sending a protocol independent multicast specified source group join message to the first public network root node address through the target node to generate a public network protocol independent multicast specified source multicast forwarding tree, wherein the protocol independent multicast specified source multicast forwarding tree is the forwarding route information of the virtual extended local area network.

4. The multicast forwarding method according to claim 3, wherein, the forwarding the multicast traffic to be forwarded to the target node according to the forwarding route information comprises: encapsulating a first virtual extended local area network encapsulation header and a first network layer encapsulation header on the multicast traffic to be forwarded in sequence to obtain encapsulated multicast traffic, wherein an identifier field of the first virtual extended local area network encapsulation header is the network identifier of the virtual extended local area network, a source address of the first network layer encapsulation header is the first public network root node address, and a destination address of the first network layer encapsulation header is the first public network multicast group address; forwarding the encapsulated multicast traffic to the target node according to the protocol independent multicast specified source multicast forwarding tree.

5. The multicast forwarding method according to claim 2, wherein, the tunnel type of the vendor multicast service interface is protocol independent multicast sparse mode, a tunnel attribute of the vendor multicast service interface comprises a second public network multicast group address, and the generating the forwarding route information according to the vendor multicast service interface comprises: sending a protocol independent multicast general entry group join message to a convergence point of the second public network multicast group address through the target node to generate a public network protocol independent multicast sparse mode shared forwarding tree, wherein the protocol independent multicast sparse mode shared forwarding tree is the forwarding route information of the virtual extended local area network.

6. The multicast forwarding method of claim 5, wherein, the tunnel attribute of the vendor multicast service interface further comprises a second public network sending address, and the forwarding the multicast traffic to be forwarded to the target node according to the forwarding route information comprises: encapsulate a second virtual extended local area network encapsulation header and a second network layer encapsulation header in sequence to obtain encapsulated multicast traffic, wherein an identifier field of the second virtual extended local area network encapsulation header is the network identifier of the virtual extended local area network, a source address of the second network layer encapsulation header is the second public network sending address, and a destination address of the second network layer encapsulation header is the second public network multicast group address; forward the encapsulated multicast traffic to the target node according to the public network protocol independent multicast sparse mode shared forwarding tree.

7. The multicast forwarding method of claim 2, wherein, The tunnel type of the provider multicast service interface is ingress replication, and the tunnel attribute of the provider multicast service interface includes a third public network routing address. The generating of the forwarding routing information according to the provider multicast service interface includes: generating an ingress replication list according to a third public network routing address carried by a second multicast automatic discovery route, wherein the second multicast automatic discovery route is announced and sent by the target node; determining the ingress replication list as the forwarding routing information of the virtual extended local area network.

8. The multicast forwarding method of claim 7, wherein, The forwarding of the to-be-forwarded multicast traffic to the target node according to the forwarding routing information includes: encapsulating a third virtual extended local area network encapsulation header and a third network layer encapsulation header in sequence to obtain encapsulated multicast traffic, wherein an identifier field of the third virtual extended local area network encapsulation header is the network identifier of the virtual extended local area network carried by the second multicast automatic discovery route, a source address of the third network layer encapsulation header is the third public network routing address, and a destination address of the third network layer encapsulation header is the third public network routing address carried by the second multicast automatic discovery route; forwarding the encapsulated multicast traffic to the target node according to the ingress replication list.

9. The multicast forwarding method according to claim 4 or 6 or 8, wherein, After the forwarding of the to-be-forwarded multicast traffic to the target node according to the forwarding routing information, the multicast forwarding method further includes: the target node receives the encapsulated multicast traffic, and determines a corresponding multicast virtual private network instance according to the network identifier in the encapsulated multicast traffic.

10. A multicast forwarding method, the method comprising: obtaining a first multicast automatic discovery route sent by a source node, and receiving to-be-forwarded multicast traffic forwarded by the source node according to forwarding routing information; wherein, in a case where an encapsulation extended community attribute carried in the first multicast automatic discovery route and a provider multicast service interface both meet preset conditions, the forwarding routing information is generated according to the provider multicast service interface.

11. The multicast forwarding method of claim 10, wherein, The preset conditions include: a tunnel type field of the encapsulation extended community attribute carried in the first multicast automatic discovery route is a virtual extended local area network, a tunnel type of the provider multicast service interface is a preset tunnel type, and a label field of the provider multicast service interface is a network identifier of the virtual extended local area network.

12. An electronic device, comprising: at least one processor; at least one memory configured to store at least one program; and The computer program product comprises computer executable instructions stored in a computer readable storage medium, and when the computer executable instructions are executed by a processor of a computer device, the processor executes the computer executable instructions, so that the computer device performs the multicast forwarding method according to any one of claims 1 to 11.

13. A computer-readable storage medium storing computer-executable instructions, wherein, The computer executable instructions are used for executing the multicast forwarding method according to any one of claims 1 to 11.

14. A computer program product comprising computer programs or computer instructions, wherein, The computer program or the computer executable instructions are stored in a computer readable storage medium, and a processor of a computer device reads the computer program or the computer executable instructions from the computer readable storage medium, and the processor executes the computer program or the computer executable instructions, so that the computer device performs the multicast forwarding method according to any one of claims 1 to 11.

Images