CN107294861B

CN107294861B - Multicast traffic control method and device

Info

Publication number: CN107294861B
Application number: CN201610194347.3A
Authority: CN
Inventors: 王翠; 张征
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2016-03-30
Filing date: 2016-03-30
Publication date: 2022-11-18
Anticipated expiration: 2036-03-30
Also published as: WO2017166918A1; CN107294861A

Abstract

The invention provides a method and a device for controlling multicast flow, wherein the control method comprises the following steps: advertising, via a routing protocol, to a network device at least one of: the bit index displays and copies the BIER stream description rule and the action set corresponding to the BIER stream description rule, wherein the network equipment controls the multicast flow according to at least one of the received BIER stream description rule and the action set.

Description

Multicast traffic control method and device

Technical Field

The present invention relates to the field of communications, and in particular, to a method and an apparatus for controlling multicast traffic.

Background

The Bit Index display Replication (Bit Index Replication, abbreviated as BIER) technology is a multicast forwarding technology recently studied by the Internet Engineering Task Force (IETF), and its core idea is shown in fig. 1, where nodes in a network are all represented by only one Bit, multicast traffic is transmitted in an intermediate network, and is not represented in the form of a multicast IP packet, but a specific BIER header is encapsulated, where the BIER header directly or indirectly includes BIER basic information (which may directly include Sub-domain subdomain information, bit String Length information, and Set Identifier information, and may also uniquely identify these three element information indirectly by means of a label) and Bit String information.

The BIER basic information is used for positioning a Bit Index Forwarding Table (Bit Index Forwarding Table, for short), bit String information marks all destination nodes of the multicast stream, and the intermediate network searches for the BIFT for routing according to the information in the BIER header, so that the multicast flow can be forwarded and sent to all the destination nodes by an optimal path.

The Flow Specification technology is a technology that is researched on IETF and used for expanding and announcing a Flow Specification rule based on a Border Gateway Protocol (BGP), and dynamically controlling a received Flow on a router based on the Flow Specification rule. Specifically, a flow specification rule is composed of a series of Component types (Component types) whose granularity can be coarse or fine; the BGP protocol is used as a control surface to realize dynamic and rapid notification and cancellation Of the upstream description rules Of the BGP Speakers, improve the capability Of preventing Distributed Denial Of Service (DDOS) attacks in the network, and avoid the static configuration method in the traditional network to ensure that the control Of the network flow is more dynamic and flexible.

Fig. 2 is a schematic diagram of a technical principle of BGP Flow Specification in the related art, and referring to fig. 2, a BGP Flow control device advertises a Flow Specification rule to each BGP Speaker by extending a BGP protocol, and each BGP Speaker stores the received Flow Specification rule in a forwarding table, and when receiving a Flow, first matches the Flow Specification rule, and if the matching is successful, executes corresponding actions, including filtering, redirecting, packet loss, and the like, according to an Action instruction corresponding to the Flow Specification rule.

Currently, the main format of Flow Specification is shown in fig. 3, wherein the Flow Specification rule defined in the current RFC5575 for the network layer reachable information Value field NLRI Value is shown in table 1 below.

As can be seen from table 1 below, currently, no control description for BIER multicast traffic is defined, so that the network cannot implement dynamic control of multicast traffic based on BIER technology.

TABLE 1

Aiming at the problem that an effective technical scheme is not provided for the dynamic control of the multicast traffic based on the BIER technology in the related art, an effective solution is not provided.

Disclosure of Invention

In order to solve the above technical problem, the present invention provides a method and an apparatus for controlling multicast traffic.

According to an aspect of the present invention, there is provided a method for controlling multicast traffic, including: advertising, by a routing protocol, to a network device, at least one of: the network equipment controls the multicast traffic according to at least one of the received BIER flow description rule and the action set.

Preferably, the BIER flow specification rule includes: sub-domain subdomain component type information, bitStringLength bit string length component type information, set Identifier component type information, bitString bit string component type information, BIER entry forwarding device identification information, service type TOS information, entry entropy value information, and tag component type information for BIER forwarding.

Preferably, the BIER flow specifies an action set corresponding to a rule, including:

one or more of limiting traffic of the multicast traffic of the BIER, sampling traffic of the multicast traffic of the BIER, redirecting traffic of the multicast traffic of the BIER, and re-identifying the multicast traffic of the BIER.

Preferably, the BIER flow specifies an action set corresponding to a rule, and further includes:

the BIER header or the information in the BIER header is manipulated.

Preferably, the network device is advertised by the routing protocol at least one of: before the BIER flow specification rule, the method further includes:

obtaining, from the centralized control device, at least one of: the BIER flow explains rules, and the BIER flow explains action sets corresponding to the rules; or

Obtaining at least one of the following from other network element devices in the network except the centralized control device: the BIER flow describes the rule, and the BIER flow describes the action set corresponding to the rule.

Preferably, the method further comprises:

revoking, by the routing protocol, at least one of: the BIER flow describes the rule, and the BIER flow describes the action set corresponding to the rule.

Preferably, the routing protocol comprises: BGP, interior Gateway Protocol (IGP for short).

According to another aspect of the present invention, there is also provided a method for controlling multicast traffic, including: receiving information advertised by a routing protocol, wherein the information includes at least one of: the bit index displays and copies BIER stream description rules, and action sets corresponding to the BIER stream description rules; and controlling the multicast flow according to the received information.

Preferably, the BIER flow specification rule includes: sub-domain Sub-field component type information, bitStringLength bit string length component type information, set Identifier component type information, bitString bit string component type information, BIER entry forwarding device identification information, service type TOS information, entropy value information of entropy, and label component type information for BIER forwarding.

the BIER header or the information in the BIER header is manipulated.

Preferably, before controlling the multicast traffic according to the received information, the method further includes:

and storing the received information locally to the equipment.

According to another aspect of the present invention, there is also provided a multicast traffic control apparatus, including: an advertising module for advertising to the network device via the routing protocol at least one of: the network equipment controls the multicast traffic according to at least one of the received BIER flow description rule and the action set.

According to another aspect of the present invention, there is also provided a multicast traffic control apparatus, including: a receiving module, configured to receive information advertised by a routing protocol, where the information includes at least one of: the bit index displays and copies BIER stream description rules, and action sets corresponding to the BIER stream description rules; and the control module is used for controlling the multicast flow according to the received information.

According to the invention, the BIER stream description rule, or the action set corresponding to the BIER stream description rule and the BIER stream description rule are notified through the routing protocol, and the multicast flow is controlled according to one of the three technical schemes, so that the problem that an effective technical scheme is not provided for the dynamic control of the multicast flow based on the BIER technology in the related technology is solved, and the dynamic control of the multicast based on the BIER technology is further realized.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

FIG. 1 is a reference diagram of BIER architecture in the related art;

FIG. 2 is a schematic diagram illustrating the technical principle of Flow Specification in BGP Flow in the related art;

FIG. 3 is a schematic diagram illustrating a BGP Flow Specification format in the related art;

fig. 4 is a flowchart of a method for controlling multicast traffic according to an embodiment of the present invention;

fig. 5 is a schematic diagram of revoking BIER flow specification rules based on the BGP protocol in an embodiment of the present invention;

fig. 6 is a block diagram of a control apparatus for multicast traffic according to an embodiment of the present invention;

fig. 7 is another flowchart of a method for controlling multicast traffic according to an embodiment of the present invention;

fig. 8 is another block diagram of a control apparatus for multicast traffic according to an embodiment of the present invention;

fig. 9 is a schematic diagram of advertising BIER flow specification rules based on the BGP protocol according to an embodiment of the present invention;

FIG. 10 illustrates an extended BIER flow specification rule and reference format in accordance with a preferred embodiment of the present invention;

FIG. 11 is a schematic diagram illustrating the control of multicast traffic based on Sub-domain flow specification rules in accordance with a preferred embodiment of the present invention;

fig. 12 is a diagram illustrating control of multicast traffic based on a bit string length bitstringelength stream specification rule according to a preferred embodiment of the present invention;

fig. 13 is a schematic diagram illustrating multicast traffic is controlled based on Set Identifier flow specification rule according to a preferred embodiment of the present invention;

fig. 14 is a diagram illustrating the control of multicast traffic based on BitString stream specification rules according to a preferred embodiment of the present invention;

FIG. 15 is a schematic diagram of controlling multicast traffic based on TOS flow specification rules in accordance with a preferred embodiment of the present invention;

fig. 16 is a diagram illustrating control of multicast traffic based on an action set corresponding to a BIER-MPLS flow specification rule according to a preferred embodiment of the present invention;

fig. 17 is a schematic diagram (one) of controlling multicast traffic according to a preferred embodiment of the present invention;

fig. 18 is a schematic diagram (two) of controlling multicast traffic according to a preferred embodiment of the present invention;

fig. 19 is a schematic diagram (three) of controlling multicast traffic according to a preferred embodiment of the present invention;

fig. 20 is a schematic diagram (four) of controlling multicast traffic according to a preferred embodiment of the present invention;

fig. 21 is a schematic diagram (five) of controlling multicast traffic according to a preferred embodiment of the present invention;

fig. 22 is a schematic diagram (six) of controlling multicast traffic according to a preferred embodiment of the present invention.

Detailed Description

The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, shall fall within the protection scope of the present invention.

In an embodiment of the present invention, a method for controlling multicast traffic is further provided, and fig. 4 is a flowchart of the method for controlling multicast traffic according to the embodiment of the present invention, as shown in fig. 4, including the following steps:

step S402, at least one of the following is obtained: BIER flow description rule corresponding action set;

step S404, notifying the network equipment of at least one of the following through a routing protocol: the network device controls the multicast traffic according to at least one of the received BIER flow description rule and the action set.

Through the steps, the BIER stream description rule, or the action set corresponding to the BIER stream description rule and the BIER stream description rule are notified through the routing protocol, and the multicast flow is controlled according to one of the steps, so that the problem that an effective technical scheme is not provided for the dynamic control of the multicast flow based on the BIER technology in the related technology is solved, and the dynamic control of the multicast based on the BIER technology is further realized.

It should be noted that the network device in the embodiment of the present invention may be an entity physical device, and may also be a logical node embodied by a virtual network element, and in addition, the execution main bodies of steps S402 to S404 may be a flow control device, and may also be other execution network elements, which are not limited in the embodiment of the present invention.

In an alternative embodiment, the BIER flow specification rule includes: sub-domain Sub-field component type information, bitStringLength bit string length component type information, set Identifier component type information, bitString bit string component type information, BIER entrance forwarding equipment Identifier information, service type TOS information, entropy information of entropy, and one or more of label component type information for BIER forwarding; the action set corresponding to the BIER flow description rule includes: one or more of limiting the traffic of the BIER multicast traffic, sampling the traffic of the BIER multicast traffic, redirecting the traffic of the BIER multicast traffic and re-identifying the BIER multicast traffic; the above BIER flow description rule corresponding action set further includes: the BIER header or the information in the BIER header is manipulated.

Advertising, by a routing protocol, to a network device, at least one of: before the bit index shows and copies the BIER stream description rule, and the action set corresponding to the BIER stream description rule, the method can also execute the following technical scheme:

obtaining, from the centralized control device, at least one of: the BIER flow explains rules, and the BIER flow explains action sets corresponding to the rules; or obtaining at least one of the following from other network element devices in the network except the centralized control device: the BIER flow describes the rule, and the BIER flow describes the action set corresponding to the rule.

In order to improve the above technical solution, an embodiment of the present invention further provides the following technical solution, where at least one of the following is withdrawn through a routing protocol: the BIER flow specifies the rule, and the BIER flow specifies the action set corresponding to the rule, as shown in fig. 5.

The above mentioned routing protocols include, but are not limited to, the following two: border gateway protocol BGP, interior gateway protocol IGP.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required for the invention.

In this embodiment, a multicast traffic control apparatus is further provided, which is used to implement the foregoing embodiments and preferred embodiments, and is not described again, and modules involved in the apparatus are described below. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated. Fig. 6 is a block diagram of a control device for multicast traffic according to an embodiment of the present invention. As shown in fig. 6, the apparatus includes:

an advertising module 60, configured to advertise to the network device, via the routing protocol, at least one of: and the bit index displays and copies the BIER stream description rule and the action set corresponding to the BIER stream description rule, wherein the network equipment controls the multicast flow according to at least one of the received BIER stream description rule and the action set.

Through the function of the modules, the BIER stream description rule, or the action set corresponding to the BIER stream description rule and the BIER stream description rule are notified through the routing protocol, and the multicast flow is controlled according to one of the three technical schemes, so that the problem that an effective technical scheme is not provided for the dynamic control of the multicast flow based on the BIER technology in the related technology is solved, and the dynamic control of the multicast based on the BIER technology is further realized.

In another improved solution of the embodiment of the present invention, a method for controlling multicast traffic is further provided, and fig. 7 is another flowchart of the method for controlling multicast traffic according to the embodiment of the present invention, as shown in fig. 7, including the following steps:

step S702, receiving information advertised by a routing protocol, wherein the information includes at least one of: the bit index displays and copies BIER stream description rules, and action sets corresponding to the BIER stream description rules;

step S704, controlling the multicast traffic according to the received information.

Through the steps, the multicast flow is controlled according to the information announced by the flow control device through the routing protocol and the information, wherein the information comprises at least one of the following information: the bit index displays and copies the BIER stream description rule and the action set corresponding to the BIER stream description rule, and by adopting the technical scheme, the problem that an effective technical scheme is not provided for the dynamic control of the multicast flow based on the BIER technology in the related technology is solved, and further the dynamic control of the multicast based on the BIER technology is realized.

The main body of the steps S702 to S704 may be a network device, that is, in an optional example of the embodiment of the present invention, the network device may receive the information notified by the flow control device through the routing protocol.

Optionally, the BIER flow specification rule includes: sub-domain subdomain component type information, bitStringLength bit string length component type information, set Identifier component type information, bitString bit string component type information, BIER entry forwarding device identification information, service type TOS information, entry entropy value information, and one or more of tag component type information for BIER forwarding; the action set corresponding to the BIER flow description rule includes: one or more of limiting the traffic of the BIER multicast traffic, sampling the BIER multicast traffic, redirecting the traffic of the BIER multicast traffic, and re-identifying the BIER multicast traffic, and may further include operating the BIER header or information in the BIER header.

In this embodiment of the present invention, before controlling the multicast traffic according to the received information, the method further includes: and storing the received information to the local device.

In this embodiment, a multicast traffic control apparatus is further provided, which is used to implement the foregoing embodiments and preferred embodiments, and is not described again, and modules involved in the apparatus are described below. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated. Fig. 8 is another block diagram of a control device for multicast traffic according to an embodiment of the present invention. As shown in fig. 8, the apparatus includes:

a receiving module 80, configured to receive information advertised by a routing protocol, where the information includes at least one of: the bit index displays and copies BIER stream description rules, and action sets corresponding to the BIER stream description rules;

and the control module 82 is configured to control the multicast traffic according to the received information.

Through the function of each module, according to the information of receiving the stream control device announced by the routing protocol, and according to the information, the multicast flow is controlled, wherein the information includes at least one of the following: the bit index display copies the BIER stream description rule, and the action set corresponding to the BIER stream description rule, and by adopting the technical scheme, the problem that an effective technical scheme is not provided for the dynamic control of the multicast flow based on the BIER technology in the related technology is solved, and further the dynamic control of the multicast based on the BIER technology is realized.

It should be noted that, in an embodiment of the foregoing step S402, a general flow may be seen from fig. 9, and the BGP flow control device notifies the BGP network of the BIER flow description rule, which is not described herein again. The following describes the control method of the multicast traffic with reference to the preferred embodiment, but the scope of the present invention is not limited thereto.

Fig. 10 is an extended BIER flow specification rule and reference format according to a preferred embodiment of the present invention, as shown in fig. 10, wherein the BIER flow specification rule includes one or more of the following: sub-domain Sub-field component type information, bitStringLength bit string length component type information, set Identifier Set identification component type information, bitString bit string component type information, BIER entry forwarding device identification information, service type TOS information, entry entropy value information, and label component type information for BIER forwarding. Their respective corresponding reference formats are also shown in fig. 10. When the BIER flow description rule is expanded through a BGP protocol, the BIER flow description rule is carried and announced by BGP flow description network layer reachable information NLRI; when extended by IGP protocol, the BIER flow specification rule is carried and advertised by an IGP flow specification reachable TLV. Further, when the BIER stream description rule is expanded through a BGP protocol, an action set corresponding to the BIER stream description rule is carried and announced through a BGP expanded community attribute; when the message is extended by an IGP protocol, the action set corresponding to the BIER flow description rule is carried and advertised by an IGP flow description filtering TLV.

Fig. 11 is a diagram illustrating the control of multicast traffic based on Sub-domain flow specification rules according to a preferred embodiment of the present invention. As shown in fig. 11:

the BGP flow control device establishes BGP neighbors as a BGP Peer and a BGP Speaker device (which may be understood as the network device of the foregoing embodiment) BFIR/BFER1/BFER2/BFER3, and the BGP flow control device learns that the multicast traffic from Sub-domain 1 is aggressive through other means (for example, in a manner issued by a controller, or through other DPI deep packet inspection devices, etc.), and then issues the component type information of Sub-domain 1 to each BGP Speaker device BFIR/BFER1/BFER2/BFER3 through a BGP flow description technique;

and after receiving the flow specification rule, each BGP Speaker device BFIR/BFER1/BFER2/BFER3 stores the flow specification rule into a local routing information base.

Fig. 12 is a diagram illustrating control of multicast traffic based on a bit string length bitstringelength stream specification rule according to a preferred embodiment of the present invention. As shown in fig. 12:

the BGP flow control equipment is used as a BGP Peer Peer and as a BGP Speaker equipment BFIR/BFER1/BFER2/BFER3 to establish BGP neighbors, the BGP flow control equipment learns that a forwarding black hole is generated when BitStringLength is 512 through other means (such as a mode issued by a controller or other DPI deep packet inspection equipment and the like), and then issues component type information with the BitStringLength of 512 to each BGP Speaker equipment BFIR/BFER1/BFER2/BFER3 through a BGP flow description technology;

and after receiving the flow description rule, each BGP Speaker device BFIR/BFER1/BFER2/BFER3 stores the flow description rule into a local routing information base.

Fig. 13 is a schematic diagram illustrating multicast traffic control based on Set Identifier stream specification rule according to a preferred embodiment of the present invention. As shown in fig. 13:

the BGP flow control equipment is used as a BGP Peer Peer and used as a BGP Speaker equipment BFIR/BFER1/BFER2/BFER3 to establish BGP neighbors, the BGP flow control equipment learns that the multicast flow with the Set Identifier 2 is attacked through other means (such as a mode issued by a controller or other DPI deep packet inspection equipment and the like), and then sends the component type information with the Set Identifier 2 to each BGP Speaker equipment BFIR/BFER1/BFER2/BFER3 through a BGP flow description technology;

Fig. 14 is a schematic diagram of controlling multicast traffic based on a bit string BitString stream specification rule according to a preferred embodiment of the present invention. As shown in fig. 14:

the BGP flow control equipment is used as a BGP Peer Peer and as BGP Speaker equipment, namely BFIR/BFER1/BFER2/BFER3, BGP neighbors are established, the BGP flow control equipment learns that the multicast flow with the BitString of 010101 is attacked by other means (such as a mode issued by a controller or other DPI deep packet inspection equipment and the like), and then the BGP flow control equipment issues the component type information with the BitString of 010101 to each BGP Speaker equipment, namely BFIR/BFER1/BFER2/BFER3, through a BGP flow description technology;

Fig. 15 is a diagram illustrating the control of multicast traffic based on TOS stream specification rules according to a preferred embodiment of the present invention. As shown in fig. 15:

the BGP flow control equipment is used as a BGP Peer Peer and as BGP Speaker equipment, namely BFIR/BFER1/BFER2/BFER3, BGP neighbors are established, the BGP flow control equipment learns that the multicast flow with the TOS field of 3 needs to be prioritized through other means (such as a mode issued by a controller or other DPI deep packet inspection equipment) and then issues the component type information with the TOS field of 3 to each BGP Speaker equipment, namely BFIR/BFER1/BFER2/BFER3 through a BGP flow description technology;

Fig. 16 is a diagram illustrating control of multicast traffic based on an action set corresponding to a BIER-MPLS flow specification rule according to a preferred embodiment of the present invention. As shown in fig. 16:

the BGP flow control equipment is used as a BGP Peer and as a BGP Speaker equipment BFIR/BFER1/BFER2/BFER3 to establish BGP neighbors, the BGP flow control equipment acquires that the multicast flow with the BIER-MPLS field of 46712 needs to be reduced in priority level through other means (such as a mode issued by a controller or other DPI deep packet inspection equipment and the like), and then issues the BGP traffic control equipment BFIR/BFER1/BFER2/BFER3 with the action of reducing the priority level of the multicast flow with the BIER-MPLS field of 46712 through a BGP flow description technology;

and after receiving the action set corresponding to the flow description rule, each BGP Speaker device BFIR/BFER1/BFER2/BFER3 stores the action set into a local routing information base.

Fig. 17 is a schematic diagram (one) of controlling multicast traffic according to a preferred embodiment of the present invention. As shown in fig. 17:

the BGP flow control equipment is used as a BGP Peer Peer and as a BGP Speaker equipment BFIR/BFER1/BFER2/BFER3 to establish BGP neighbors, the BGP flow control equipment acquires that the multicast flow with Sub-domain 1 has aggressivity through other means (such as a mode issued by a controller or other DPI deep packet inspection equipment) and then issues the component type information with Sub-domain 1 to each BGP Speaker equipment BFIR/BFER1/BFER2/BFER3 through a BGP flow description technology; meanwhile, informing BGP community attributes to carry discarding action instructions to each BGP Speaker device, informing BFIR/BFER1/BFER2/BFER3 of receiving multicast messages with Sub-domain of 1, and executing packet loss action;

after receiving the flow description rule, each BGP Speaker device BFIR/BFER1/BFER2/BFER3 stores the flow description rule in a local routing information base; when receiving the discarding action command, storing the discarding action command into a local routing information base;

after BGP Speaker equipment BFIR receives the multicast flow, the multicast flow is found to belong to Sub-domain 1, and then corresponding discarding action is executed, and the message is discarded; DDOS attacks are effectively prevented.

Fig. 18 is a schematic diagram (two) illustrating multicast traffic control according to a preferred embodiment of the present invention. As shown in fig. 18:

the BGP flow control equipment is used as a BGP Peer Peer and as a BGP Speaker equipment BFIR/BFER1/BFER2/BFER3 to establish BGP neighbors, the BGP flow control equipment acquires that the multicast flow with Sub-domain 1 needs to be redirected through other means, and then sends the component type information with Sub-domain 1 to each BGP Speaker equipment BFIR/BFER1/BFER2/BFER3 through a BGP flow description technology; meanwhile, informing BGP community attributes to carry a Redirect action instruction to each BGP Speaker device, informing BFIR/BFER1/BFER2/BFER3 of receiving a multicast message with Sub-domain of 1, and executing a Redirect action;

after receiving the flow description rule, each BGP Speaker device BFIR/BFER1/BFER2/BFER3 stores the flow description rule into a local routing information base; when receiving the Redirect action command, storing the Redirect action command in a local routing information base;

after BGP Speaker equipment BFIR receives the multicast flow, the multicast flow is found to belong to Sub-domain 1, then, a corresponding Redirect action is executed, and the message is redirected to Sub-domain 2; redirection functions between BIER domains are effectively implemented.

Fig. 19 is a schematic diagram (three) of controlling multicast traffic according to a preferred embodiment of the present invention. As shown in fig. 19:

the BGP flow control equipment is used as a BGP Peer Peer and as BGP Speaker equipment, namely BFIR/BFER1/BFER2/BFER3, BGP neighbors are established, the BGP flow control equipment obtains that the multicast flow from which the Sub-domain is 2 and the TOS field is 3 needs to be prioritized through other means, and then component type information of which the Sub-domain is 2 and the TOS field is 3 is transmitted to each BGP Speaker equipment, namely BFIR/BFER1/BFER2/BFER3 through a BGP flow description technology; meanwhile, notifying BGP community attributes to carry a Set action instruction for setting a TOS field to be 5 to each BGP Speaker device, notifying BFIR/BFER1/BFER2/BFER3 of receiving a multicast message with Sub-domain of 2 and TOS field of 3, and executing a Set action;

after receiving the flow description rule, each BGP Speaker device BFIR/BFER1/BFER2/BFER3 stores the flow description rule in a local routing information base; when receiving the Set action command, storing the Set action command in a local routing information base;

after BGP Speaker equipment BFIR receives the multicast flow, finding that the multicast flow belongs to Sub-domain 2 and TOS field is 3, then executing corresponding Set action and setting TOS field to be 5; and carrying out traffic forwarding on the multicast traffic according to the TOS of 5.

Fig. 20 is a fourth schematic diagram illustrating multicast traffic control according to a preferred embodiment of the present invention. As shown in fig. 20:

BGP flow control equipment serving as a BGP Peer Peer and BGP Speaker equipment BFIR/BFER1/BFER2/BFER3 both establish BGP neighbors, the BGP flow control equipment acquires that multicast flow from a Sub-domain of 2 and a BitStringLength of 512 appears a forwarding black hole in a forwarding process through other means, and then component type information of the Sub-domain of 2 and the BitStringLength of 512 is issued to each BGP Speaker equipment BFIR/BFER1/BFER2/BFER3 through a BGP flow description technology; meanwhile, informing BGP community attributes to carry a Set action instruction for setting BitStringLength to 128 to each BGP Speaker device, informing BFIR/BFER1/BFER2/BFER3 of receiving a multicast message with Sub-domain of 2 and BitStringLength of 512, and executing the Set action;

after receiving the flow description rule, each BGP Speaker device BFIR/BFER1/BFER2/BFER3 stores the flow description rule into a local routing information base; when receiving the Set action command, storing the Set action command in a local routing information base;

after BGP Speaker equipment BFIR receives the multicast flow, it finds that the multicast flow belongs to Sub-domain 2 and BitStringLength is 512, then executes corresponding Set action, and sets BitStringLength to be 128; and carrying out traffic forwarding on the multicast traffic according to the BitStringLength being 128.

Fig. 21 is a schematic diagram (v) of controlling multicast traffic according to a preferred embodiment of the present invention. As shown in fig. 21:

the BFER1 is used as BGP flow control equipment and BGP Speaker equipment BFIR/BFER2/BFER3 to establish BGP neighbors, the BGP flow control equipment BFER1 learns that multicast flow with Sub-domain of 2 and BFIR-id of 1 is not needed by the BFER1 through other means, and then component type information with Sub-domain of 2 and BFIR-id of 1 is notified to each BGP Speaker equipment BFIR/BFER2/BFER3 through BGP flow description technology; meanwhile, notifying BGP community attributes to carry a Set action instruction for setting BitString as not including BFER1 to each BGP Speaker device, notifying BFIR/BFER2/BFER3 to receive a multicast message of which Sub-domain is 2 and BFIR-id is 1, and executing a Set BitString action;

after receiving the flow description rule, each BGP Speaker device BFIR/BFER2/BFER3 stores the rule in a local routing information base; when receiving the Set action command, storing the Set action command into a local routing information base;

after BGP Speaker equipment BFIR receives the multicast flow, the multicast flow is found to belong to Sub-domain 2 and the BFIR-id of the multicast flow is 1, then, a corresponding Set bitString action is executed, and the bitString is Set as a new bitString which does not comprise the BFIR-id of 1; and carrying out flow forwarding on the multicast flow according to the new BitString.

Fig. 22 is a schematic diagram (vi) of controlling multicast traffic according to a preferred embodiment of the present invention. As shown in fig. 22:

BFER1 establishes IGP neighbors as IGP flow control equipment and IGP direct connection neighbor equipment or IGP indirect connection neighbor equipment BFIR/BFER2/BFER3, IGP flow control equipment BFER1 learns that multicast flow from which Sub-domain is 2 and BFIR-id is 1 is not needed by itself through other means, and then notifies component type information of Sub-domain is 2 and BFIR-id is 1 to each IGP neighbor equipment BFIR/BFER2/BFER3 through IGP flow description technology; meanwhile, the notice carries a Set action instruction which sets the BitString as not including BFER1 to each IGP neighbor device, informs BFIR/BFER2/BFER3 of receiving a multicast message of which Sub-domain is 2 and BFIR-id is 1, and executes the Set BitString action;

after receiving the flow description rule, each IGP neighbor device BFIR/BFER2/BFER3 stores the flow description rule into a local routing information base; when receiving the Set action command, storing the Set action command in a local routing information base;

after receiving the multicast flow, the IGP neighbor device BFIR finds that the multicast flow belongs to Sub-domain 2 and the BFIR-id of the IGP neighbor device BFIR is 1, then executes a corresponding Set BitString action, and sets the BitString as a new BitString without the BFIR-id being 1; and carrying out flow forwarding on the multicast flow according to the new BitString.

In summary, the embodiment of the invention achieves the following technical effects: the problem that an effective technical scheme is not provided for the dynamic control of the multicast flow based on the BIER technology in the related technology is solved, and the dynamic control of the multicast based on the BIER technology is further realized.

In another embodiment, a software is provided, and the software is used for executing the technical solutions described in the above embodiments and preferred embodiments.

In another embodiment, a storage medium is provided, where the software is stored, and the storage medium includes but is not limited to: optical disks, floppy disks, hard disks, erasable memory, etc.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the objects so used are interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Moreover, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for controlling multicast traffic, comprising:

advertising, by a routing protocol, to a network device, at least one of: the bit index displays and copies BIER stream description rules and action sets corresponding to the BIER stream description rules, wherein the network equipment controls the multicast traffic according to at least one of the received BIER stream description rules and the action sets;

wherein at least one of the following is withdrawn by the routing protocol: the BIER flow describes the rule, and the BIER flow describes the action set corresponding to the rule.

2. The method of claim 1, wherein the BIER flow specification rule comprises: sub-domain Sub-field component type information, bitStringLength bit string length component type information, set Identifier component type information, bitString bit string component type information, BIER entry forwarding device identification information, service type TOS information, entropy value information of entropy, and label component type information for BIER forwarding.

3. The method of claim 1, wherein the BIER flow specifies a set of actions corresponding to a rule, comprising:

4. The method of claim 3, wherein the BIER flow specifies a set of actions corresponding to a rule, further comprising:

the BIER header or the information in the BIER header is manipulated.

5. The method of claim 1, wherein at least one of the following is advertised to the network device via a routing protocol: before the BIER flow specification rule, the method further includes:

6. The method according to any of claims 1-5, wherein the routing protocol comprises: border gateway protocol BGP, interior gateway protocol IGP.

7. A method for controlling multicast traffic, comprising:

receiving information advertised by a routing protocol, wherein the information includes at least one of: the bit index displays and copies BIER stream description rules, and action sets corresponding to the BIER stream description rules;

controlling the multicast flow according to the received information;

receiving information revoked through a routing protocol, wherein the revoked information includes at least one of: the BIER flow describes the rule, and the BIER flow describes the action set corresponding to the rule.

8. The method of claim 7, wherein the BIER flow specification rule comprises: sub-domain subdomain component type information, bitStringLength bit string length component type information, set Identifier component type information, bitString bit string component type information, BIER entry forwarding device identification information, service type TOS information, entry entropy value information, and tag component type information for BIER forwarding.

9. The method of claim 7, wherein the BIER flow specifies a set of actions corresponding to a rule, comprising:

10. The method of claim 9, wherein the BIER flow specifies a set of actions corresponding to a rule, further comprising:

the BIER header or the information in the BIER header is manipulated.

11. The method of claim 7, wherein before controlling multicast traffic according to the received information, the method further comprises:

and storing the received information locally to the equipment.

12. A multicast traffic control apparatus, comprising:

an advertising module for advertising to the network device via the routing protocol at least one of: the bit index displays and copies BIER stream description rules and action sets corresponding to the BIER stream description rules, wherein the network equipment controls the multicast flow according to at least one of the received BIER stream description rules and the action sets;

wherein the advertisement module is further configured to revoke at least one of the following through a routing protocol: the BIER flow describes the rule, and the BIER flow describes the action set corresponding to the rule.

13. A multicast traffic control apparatus, comprising:

a receiving module, configured to receive information advertised by a routing protocol, where the information includes at least one of: the bit index displays and copies BIER stream description rules, and action sets corresponding to the BIER stream description rules;

the control module is used for controlling the multicast flow according to the received information;

in the process of cutting, the receiving module is further configured to receive information revoked through a routing protocol, where the revoked information includes at least one of: the BIER flow describes the rule, and the BIER flow describes the action set corresponding to the rule.