Information processing method, network device, storage medium, and program product

Abstract

The present application discloses an information processing method, a network device, a storage medium, and a program product. The information processing method includes: receiving a BIER stream flowing through a current node; and calculating statistics of the BIER stream to obtain node statistics information of the BIER stream.

Description

[Technical Field]

[0001] This application is filed based on a Chinese patent application bearing application number 202210607018.2 and filed on May 31, 2022, and claims priority to that Chinese patent application, the entire contents of which are incorporated herein by reference.

[0002] The present application relates to the technical field of communications, and more particularly to an information processing method, a network device, a storage medium, and a program product. [Background technology]

[0003] Bit Index Explicit Replication (BIER) is a new multicast technology based on bit index explicit replication. This technology does not require the explicit establishment of a multicast distribution tree, nor does it require intermediate network nodes to store the state of the multicast stream. Specifically, BIER technology uses only one BIT (bit) to represent network nodes at the edge of the network. Multicast traffic is transmitted over intermediate networks and is further encapsulated with a specific BIER header. This message header marks all destination network node Bit-Forwarding Egress Routers (BFERs) of the multicast stream in the form of a BIT bit string. Intermediate network nodes then perform routing according to the BIT bit, thereby ensuring that traffic is delivered to all destination network nodes.

[0004] However, there is currently no method for collecting information about BIER streams, so network administrators cannot grasp the status of BIER traffic within the network, and therefore cannot grasp the traffic quality or possible abnormalities in the network. Summary of the Invention [Problem to be solved by the invention]

[0005] The embodiments of the present application provide an information processing method, a network device, a storage medium, and a program product that realize the collection of BIER streams, perform statistics on information related to traffic engineering, and facilitate the detection of abnormalities that may exist in the network. [Means for solving the problem]

[0006] According to a first aspect, an embodiment of the present application provides an information processing method including steps of receiving a BIER stream flowing through a current node, and performing statistics on the BIER stream to obtain node statistical information of the BIER stream.

[0007] According to a second aspect, an embodiment of the present application further provides an information processing method, including: obtaining node statistics of a BIER stream and encoding information corresponding to the node statistics; and determining a current network state based on the node statistics and the encoding information.

[0008] According to a third aspect, an embodiment of the present application further provides a network device including a memory, a processor, and a computer program stored in the memory and operable on the processor, wherein the processor executes the above-mentioned information processing method when it runs the computer program.

[0009] According to a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions for performing the above information processing method.

[0010] According to a fifth aspect, an embodiment of the present application further provides a computer program product including a computer program or computer instructions stored on a computer-readable storage medium, wherein a processor of a computing 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 to cause the computing device to perform the above-mentioned information processing method. [Effects of the Invention]

[0011] In the embodiment of the present application, for the BIER stream flowing through the current node, the embodiment of the present application can collect statistics on the BIER stream to obtain node statistical information of the BIER stream, thereby realizing BIER stream collection. Therefore, the embodiment of the present application can easily perform subsequent statistics on traffic engineering information and detect possible abnormalities in the network based on the collected BIER stream. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a schematic diagram of an implementation environment for performing an information processing method according to an embodiment of the present application; [Figure 2] 2 is a schematic diagram of an implementation environment for performing an information processing method according to another embodiment of the present application; [Figure 3] 2 is a schematic diagram of an implementation environment for performing an information processing method according to another embodiment of the present application; [Figure 4] 1 is a flowchart of an information processing method according to an embodiment of the present application. [Figure 5] 10 is a flowchart of an analysis process by a collector in an information processing method according to an embodiment of the present application. [Figure 6] 1 is a flowchart of an analysis process by a BIER observation point itself in an information processing method according to an embodiment of the present application. [Figure 7]1 is a flowchart of classification according to a preset statistical rule in an information processing method according to an embodiment of the present application; [Figure 8] FIG. 2 is a schematic diagram of a BIER header format according to an embodiment of the present application; [Figure 9] 1 is a flowchart of BIER stream processing and statistics according to one embodiment of the present application; [Figure 10] 10 is a detailed flowchart of step S400 in the case of MPLS encapsulation and a pre-defined statistical rule based on traffic flow classification information in the information processing method according to an embodiment of the present application; [Figure 11] 10 is a detailed flowchart of step S400 in the case of Ethernet type encapsulation and a pre-defined statistical rule based on differentiated services codepoint information in the information processing method according to an embodiment of the present application; [Figure 12] 10 is a detailed flowchart of step S400 in the case of IPv6 encapsulation and a pre-defined statistical rule based on differentiated services codepoint information in the information processing method according to an embodiment of the present application; [Figure 13] 10 is a detailed flowchart of step S400 in the case of IPv6 encapsulation and a pre-defined statistical rule based on differentiated services codepoint information in the information processing method according to another embodiment of the present application; [Figure 14] 10 is a detailed flowchart of step S400 in the case of IPv6 encapsulation and a pre-defined statistical rule based on differentiated services codepoint information in the information processing method according to another embodiment of the present application; [Figure 15] 10 is a detailed flowchart of step S400 in the case of a preset statistical rule based on bit string length information in the information processing method according to an embodiment of the present application. [Figure 16] 10 is a detailed flowchart of step S400 in the case of a preset statistical rule based on bit string length information in the information processing method according to another embodiment of the present application; [Figure 17] 10 is a detailed flowchart of step S400 in the case of a pre-set statistical rule based on sub-domain information in the information processing method according to an embodiment of the present application; [Figure 18] 10 is a specific flowchart of step S400 in the case of a pre-set statistical rule based on sub-domain information in the information processing method according to another embodiment of the present application; [Figure 19] 10 is a detailed flowchart of step S400 in the case of a preset statistical rule based on bit forwarding ingress router device identity information in the information processing method according to an embodiment of the present application; [Figure 20] 10 is a detailed flowchart of step S400 in the case of a preset statistical rule based on bit forwarding egress router device identity information in the information processing method according to an embodiment of the present application; [Figure 21] 10 is a flowchart of processing and statistics by forwarding entries according to one embodiment of the present application; [Figure 22] 10 is a specific flowchart of step S400 in the case of a preset statistical rule based on a source address and a destination address in the information processing method according to an embodiment of the present application. [Figure 23] 10 is a specific flowchart of step S400 in the case of a preset statistical rule based on a source address and a destination address in an information processing method according to another embodiment of the present application; [Figure 24] 10 is a specific flowchart of step S400 in the case of a preset statistical rule based on a source address and a destination address in an information processing method according to another embodiment of the present application; [Figure 25] 1 is a flowchart illustrating a method for processing information according to an embodiment of the present application, where all BIER streams are statistically analyzed without a predetermined statistical rule; [Figure 26] 1 is a flowchart of an information processing method according to another embodiment of the present application. [Figure 27]14 is a detailed flowchart of step S1400 in the information processing method according to an embodiment of the present application. [Figure 28] FIG. 10 is a schematic diagram of template data in which a DSCP value of 6 is associated with a specific BIER SD according to an embodiment of the present application. [Figure 29] FIG. 10 is a schematic diagram of template data with a BSL of 256 for a specific BFIR device according to one embodiment of the present application. [Figure 30] FIG. 2 is a schematic diagram of template data for a particular multicast stream according to one embodiment of the present application; [Figure 31] FIG. 2 is a schematic diagram of template data for a particular BFER device and a particular BIER encapsulation type, according to one embodiment of the present application. [Figure 32] 10 is a specific flowchart of step S1400 in the information processing method according to an embodiment of the present application, in which the node statistical information includes a timestamp when the BIER stream arrives at the node and a timestamp when the BIER stream leaves the node. [Figure 33] 10 is a specific flowchart of step S1400 in the information processing method according to an embodiment of the present application, when the number of discarded BIER stream messages is included in the node statistical information. [Figure 34] 10 is a detailed flowchart of step S1400 in the information processing method according to an embodiment of the present application, when the node statistical information includes an ingress interface that receives a BIER stream and an egress interface that transmits a BIER stream. [Figure 35] 14 is a specific flowchart of step S1400 in the information processing method according to an embodiment of the present application, when the number of messages in the BIER stream is included in the node statistical information and the message information includes a source address and a destination address. [Figure 36] FIG. 1 is a schematic diagram illustrating the configuration of a network device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0013] In order to clarify the purpose, technical solution and advantages of the present application, the present application will be described in more detail below with reference to the drawings and examples. It should be understood that the specific examples described in this specification are only used to interpret the present application, and are not used to limit the present application.

[0014] It should be noted that although the flowchart depicts a logical order, in some cases the steps shown or described may be performed in an order different from that depicted in the flowchart. Terms such as "first," "second," etc. in this specification and claims, as well as in the drawings, are used to distinguish between similar entities and are not necessarily used to describe a particular order or priority.

[0015] Bit Index Explicit Replication (BIER) (RFC8279) is a new multicast data forwarding technology. BIER technology uses only one BIT (bit) to represent the nodes at the edge of the network, and multicast traffic is transmitted over intermediate networks and further encapsulated with a specific BIER header. This message header marks all destination network nodes Bit-Forwarding Egress Routers (BFERs) of the multicast stream in the form of a BIT bit string, and intermediate network nodes route according to the BIT bit, thereby ensuring that traffic is sent to all destination network nodes.

[0016] In the case of a Bit-Forwarding Ingress Router (BFIR) in a BIER domain, to transmit a certain multicast traffic, it needs to know which egress BFER in the BIER domain needs this multicast traffic, and the multicast traffic status is communicated between the BFIR and BFER using BIER Overlay technology. An intermediate Bit-Forwarding Router (BFR) device used only for BIER forwarding does not need to know this multicast traffic information.

[0017] To build BIER forwarding entries, BIER underlay protocols such as Open Shortest Path First (OSPF) and Intermediate System-to-Intermediate System (ISIS) support BIER message announcements through signaling extensions to build BIER forwarding entries.

[0018] On the other hand, the current IP Flow Information eXport (IPFIX) RFC5470 is a network traffic monitoring method. However, this method does not currently have a method for collecting information based on the BIER stream, so it is not possible to perform statistics and collection of the BIER stream. Also, RFC8296 defines the structure of the BIER header and specifies the fields within it. However, network devices cannot correctly classify, filter, and collect statistics on BIER messages based on this message header.

[0019] In response to this, the present application provides an information processing method, a network device, a storage medium, and a program product. The information processing method, in one embodiment, includes receiving a BIER stream flowing through a current node and collecting statistics on the BIER stream to obtain node statistics on the BIER stream. That is, the present application collects BIER stream statistics on the BIER stream flowing through the current node and obtains node statistics on the BIER stream. Therefore, the present application can perform subsequent statistics on traffic engineering information based on the collected BIER stream, making it easier to discover possible anomalies in the network.

[0020] The present invention will be further described below with reference to the accompanying drawings.

[0021] As shown in FIG. 1, FIG. 1 is a schematic diagram of an implementation environment for performing an information processing method according to an embodiment of the present application.

[0022] 1, the implementation environment includes, but is not limited to, a BIER observation point 110 and a collector 120, where the BIER observation point 110 and the collector 120 are communicatively coupled.

[0023] In one embodiment, the relative positions and numbers of the BIER observation points 110 and the collectors 120 may be set according to a specific application scenario, for example, the BIER observation points 110 may include at least one of BFIR, BFER, or intermediate BFR.

[0024] Here, the BIER observation point 110 may be located in one or more devices. As shown in Figure 2, in the BIER observation domain, the BIER observation point 110 may be a BFIR, a BFER, and an intermediate BFR, and the collector 120 is communicatively connected to the BFIR, the BFER, and the intermediate BFR, respectively.

[0025] 1 and 2, the BIER observation point 110 may only have a function of collecting the BIER stream, that is, the BIER observation point 110 may only be responsible for collecting the BIER stream. Furthermore, the collector 120 may be responsible for the subsequent information analysis of the collected BIER stream.

[0026] 1 and 2, in one embodiment, the BIER observation point 110 may be a router or switch device itself, an interface of a router or switch, or a line card including a set of interfaces. The router or switch device may directly perform traffic statistics and measurement operations, or may send traffic to another router or switch device with measurement capabilities, or to a server with measurement capabilities, which then performs measurement statistics and sends the traffic to the collector 120. However, this embodiment is not particularly limited to this.

[0027] In the example of FIG. 3, the implementation environment may include, but is not limited to, a BIER observation point 110 .

[0028] In one embodiment, the locations and number of BIER observation points 110 may be set according to a specific application scenario. For example, the BIER observation points 110 may include at least one of a BFIR, a BFER, or an intermediate BFR.

[0029] Here, in the implementation environment of Figure 3, the BIER observation point 110 may have both the collection function and the analysis function of the BIER stream, that is, after collecting the BIER stream, the BIER observation point 110 analyzes the subsequent information of the collected BIER stream.

[0030] 3, in one embodiment, the BIER observation point 110 may be a router or switch device itself, an interface of a router or switch, or a line card including a set of interfaces. The router or switch device may directly perform traffic statistics, measurement, and analysis, but this embodiment is not particularly limited thereto.

[0031] The implementation environment for executing the information processing method is applicable to 3G communication network systems, LTE communication network systems, 5G communication network systems, 6G communication network systems, and subsequently evolving mobile / fixed communication network systems, but is not particularly limited to these in this embodiment.

[0032] The implementation environments shown in Figures 1-3 are not intended to limit the scope of the present application and may include more or fewer components than those shown, or may combine certain components or have different component arrangements.

[0033] Based on the above implementation environment, various embodiments of the information processing method of the present application will be proposed below.

[0034] As shown in FIG. 4, FIG. 4 is a flowchart of an information processing method according to one embodiment of the present application, which may be applied to the BIER observation points of FIGS. 1 to 3 and may include, but is not limited to, steps S100 to S200.

[0035] Step S100: The BIER stream flowing through the current node is received.

[0036] Step S200: Calculate statistics on the BIER stream to obtain node statistics information of the BIER stream.

[0037] Specifically, a BIER observation point may receive a BIER stream flowing through its own node, and then perform statistics on the BIER stream to obtain node statistical information of the BIER stream.

[0038] In one embodiment, the node statistics may include at least one of the following: a number of BIER stream messages received, a number of BIER stream bytes received, an egress interface sending the BIER stream, a number of BIER stream messages sent, a number of BIER stream bytes sent, a number of BIER stream messages discarded, a number of BIER stream bytes discarded, a timestamp when the BIER stream arrives at the current node, and a timestamp when the BIER stream leaves the current node.

[0039] According to an embodiment of the present application, for the BIER stream flowing through the current node, the embodiment of the present application can collect statistics on the BIER stream to obtain node statistical information of the BIER stream, thereby realizing BIER stream collection. Therefore, the embodiment of the present application can easily perform subsequent statistics on traffic engineering information and detect possible abnormalities in the network based on the collected BIER stream.

[0040] Also, as shown in FIG. 5, FIG. 5 is a flowchart of the analysis process by the collector in an information processing method according to one embodiment of the present application, and after the above step S200, this information processing method may further include, but is not limited to, step S311 and step S312.

[0041] Step S311: Generate coding information corresponding to the node statistical information.

[0042] Step S312: Send the node statistical information and the encoding information to the collector, so that the collector determines the current network state based on the node statistical information and the encoding information.

[0043] Specifically, for analysis by the collector, when a BIER observation point transmits node statistics, it carries encoding information of the relevant data for the collector to decode. The encoding information includes two parts: a template and data. The template includes one or more elements such as the number of messages or bytes in the BIER stream, the egress interface transmitting the BIER stream, the number of messages or bytes in the BIER stream transmitted, the number of messages or bytes in the BIER stream discarded, the timestamps at which the BIER stream arrives at the device and the timestamps at which the BIER stream leaves the device, as well as one or more elements such as the bit string length, the ingress BFIR device ID, the designated traffic class (TC) / differentiated services code point (DSCP), the designated BIER subdomain, the designated egress BFIR device, and the designated multicast traffic.

[0044] The collector may obtain the transmission delay of the BIER stream in the network based on the timestamp information of the node statistics and use it as a parameter for traffic engineering. Alternatively, the collector may determine whether counterfeit traffic or attack traffic exists in the network based on a comparison between traffic entering the BIER domain and traffic leaving the BIER domain.

[0045] Also, as shown in FIG. 6, FIG. 6 is a flowchart of the analysis process by the BIER observation point itself in an information processing method according to one embodiment of the present application, and after the above step S200, this information processing method may further include, but is not limited to, step S320.

[0046] Step S320: Determine the current network state based on the node statistics information.

[0047] Specifically, in the case of analysis processing by the BIER observation point itself, the BIER observation point obtains node statistical information and then determines the current network status based on the node statistical information. For example, the BIER observation point may obtain the transmission delay of the BIER stream in the network based on the timestamp information in the node statistical information and use it as a parameter for traffic engineering. Alternatively, the BIER observation point may determine whether counterfeit traffic or attack traffic exists in the network based on a comparison of traffic entering the BIER domain with traffic leaving the BIER domain.

[0048] Also, as shown in FIG. 7, FIG. 7 is a flowchart of classification according to a preset statistical rule in an information processing method according to one embodiment of the present application, and after the above step S100, this information processing method may further include step S400, but is not limited thereto.

[0049] Step S400: To perform statistics on a target BIER stream, a target BIER stream to be statistically analyzed is determined from the received BIER streams according to message information of the BIER stream and a preset statistical rule.

[0050] Specifically, to perform statistics on a BIER stream, the BIER observation point must identify and classify the BIER stream and perform necessary filtering before performing statistics. The following TC / DSCP, Bit String Length (BSL), BFIR-ID, and BitString are derived from the BIER header format definition specified in RFC8296, as shown in Figure 8. The processing and statistical flow for a BIER stream is shown in Figure 9.

[0051] In one embodiment, the BIER observation point may perform statistics on only a portion of the BIER stream according to a predetermined preset statistical rule, which may be set by a network administrator as needed or notified to the observation point by a controller through a YANG model, a Border Gateway Protocol-Link State (BGP-LS) extension, etc. In other words, for the preset statistical rule, the current node may be obtained by any of the following methods, including but not limited to, a method obtained by the configuration information of the current node, a method obtained by extending a YANG model to the current node, and a method obtained by extending BGP-LS to the current node.

[0052] In one embodiment, the above-mentioned preset statistical rules may perform statistics based on at least one of encapsulation type information, bit string length information, subdomain information, TC information, DSCP information, bit forwarding ingress router device identity information, bit forwarding egress router device identity information, preset traffic elements, source address, destination address, source port number, and destination port number.

[0053] Here, the above-mentioned preset statistical rules may perform statistics based on a single element or a combination of multiple elements, and the embodiments of the present application merely exemplify a single element or a combination of some elements, and are not limited to being implemented based on such a combination.

[0054] Regarding the statistical method of the above-mentioned preset statistical rules, examples of some elements are given below.

[0055] As shown in FIG. 10, FIG. 10 is a specific flowchart of step S400 in the case of MPLS encapsulation and a pre-set statistical rule based on traffic flow classification information in an information processing method according to one embodiment of the present application, and the above step S400 may include, but is not limited to, step S510 and step S520.

[0056] Step S510: Read the MPLS label stack information and traffic flow classification information fields in the message information.

[0057] Step S520: Calculate statistics of the BIER stream according to the MPLS label stack information and the traffic flow classification information field.

[0058] In one embodiment, when the preset statistical rule is a statistical rule based on traffic flow classification information, it is necessary to count BIER streams whose TC domain is set to 2. In this case, it is necessary to filter the BIER streams and count only streams whose TC based on MPLS encapsulation is set to 2.

[0059] Specifically, in the embodiment of the present application, when statistics are required, the MPLS label stack information and traffic flow classification information fields in the message information are read, and then, based on the data in the MPLS label stack information and traffic flow classification information fields, it is determined whether this BIER stream requires statistics.

[0060] As shown in FIG. 11, FIG. 11 is a specific flowchart of step S400 in an information processing method according to one embodiment of the present application, in the case of Ethernet type encapsulation and a pre-set statistical rule based on differentiated services code point information, and the above step S400 may include, but is not limited to, step S611 and step S612.

[0061] Step S611: Read the Ethernet type information and differentiated services code point information fields in the message information.

[0062] Step S612: Statistic the BIER stream according to the Ethernet type information and differentiated services codepoint information fields.

[0063] In one embodiment, if the preset statistical rule is a statistical rule based on differentiated services code point information, it is necessary to count a BIER stream with DSCP set to 6. In this case, it is necessary to count a BIER stream based on Ethernet encapsulation and IPv6 encapsulation with DSCP domain set to 6.

[0064] When performing statistics on a BIER stream based on Ethernet encapsulation, the Ethernet type information and differentiated services code point information fields in the message information may be read, and then based on the data in the Ethernet type information and differentiated services code point information fields, it may be determined whether or not the BIER stream needs to be statistically processed.

[0065] 12, which is a specific flowchart of step S400 in the case of IPv6 encapsulation and a pre-defined statistical rule based on differentiated services codepoint information in an information processing method according to an embodiment of the present application. The above step S400 may include, but is not limited to, step S621 and step S622.

[0066] Step S621: Read the Next Header field and the Differentiated Services Code Point Information field in the message information.

[0067] Step S622: Calculate statistics of the BIER stream based on the Next Header field and the Differentiated Services Codepoint Information field.

[0068] In one embodiment, if the preset statistical rule is a statistical rule based on differentiated services code point information, it is necessary to count a BIER stream with DSCP set to 6. In this case, it is necessary to count a BIER stream based on Ethernet encapsulation and IPv6 encapsulation with DSCP domain set to 6.

[0069] When performing statistics on a BIER stream based on IPv6 encapsulation, there are various types of IPv6-encapsulated BIER streams. For a stream in which the IPv6 Next Header is set to the BIER type, in the embodiment of the present application, the Next Header field and the Differentiated Services Code Point Information field in the message information are read, and then it is determined whether the BIER stream requires statistics based on the data in the Next Header field and the Differentiated Services Code Point Information field.

[0070] 13, which is a specific flowchart of step S400 in the case of IPv6 encapsulation and a pre-defined statistical rule based on differentiated services codepoint information in an information processing method according to another embodiment of the present application. The above step S400 may include, but is not limited to, step S631 and step S632.

[0071] Step S631: Read the Destination Options Header field and the Differentiated Services Code Point Information field in the message information.

[0072] Step S632: Calculate statistics of the BIER stream based on the Destination Options Header field and the Differentiated Services Codepoint Information field.

[0073] In one embodiment, if the preset statistical rule is a statistical rule based on differentiated services code point information, it is necessary to count a BIER stream with DSCP set to 6. In this case, it is necessary to count a BIER stream based on Ethernet encapsulation and IPv6 encapsulation with DSCP domain set to 6.

[0074] When performing statistics on a BIER stream based on IPv6 encapsulation, there are various types of IPv6-encapsulated BIER streams. For streams in which the IPv6 Next Header is set to 60, i.e., the Destination Options Header (DOH) contains a BIER-type option, in the embodiment of the present application, the Destination Options Header field and the Differentiated Services Code Point Information field in the message information are read, and then it is determined whether or not this BIER stream requires statistics based on the data in the Destination Options Header field and the Differentiated Services Code Point Information field.

[0075] 14, which is a specific flowchart of step S400 in the case of IPv6 encapsulation and a pre-defined statistical rule based on differentiated services codepoint information in an information processing method according to another embodiment of the present application. The above step S400 may include, but is not limited to, step S641 and step S642.

[0076] Step S641: Read the Routing Header field and the Differentiated Services Code Point Information field in the message information.

[0077] Step S642: Calculate statistics of the BIER stream based on the Routing Header field and the Differentiated Services Codepoint Information field.

[0078] In one embodiment, if the preset statistical rule is a statistical rule based on differentiated services code point information, it is necessary to count a BIER stream with DSCP set to 6. In this case, it is necessary to count a BIER stream based on Ethernet encapsulation and IPv6 encapsulation with DSCP domain set to 6.

[0079] When performing statistics on a BIER stream based on IPv6 encapsulation, there are various types of IPv6-encapsulated BIER streams. For streams where the IPv6 Next Header is set to 43, i.e., the Routing Header (RH) contains a BIER type, in the embodiment of the present application, the Routing Header field and the Differentiated Services Code Point Information field in the message information are read, and then it is determined whether or not this BIER stream requires statistics based on the data in the Routing Header field and the Differentiated Services Code Point Information field.

[0080] Based on the above embodiments of Figures 11 to 14, the embodiments of the present application may implement any one or more of the above embodiments of Figures 11 to 14 when the differentiated service code point information is a preset statistical rule.

[0081] 15, which is a specific flowchart of step S400 in the case of a preset statistical rule based on bit string length information in an information processing method according to an embodiment of the present application. The above step S400 may include, but is not limited to, step S711 and step S712.

[0082] Step S711: The bit string length information field in the message information is read.

[0083] Step S712: Calculate statistics of the BIER stream based on the bit string length information field.

[0084] In one embodiment, if the preset statistical rule is to perform statistics based on bit string length information, it is necessary to count BIER streams with BSL set to 256. In this case, it is necessary to filter the BIER streams and count only BIER streams with BSL domain set to 3 based on Ethernet, MPLS, and IPv6 encapsulation.

[0085] Therefore, in the embodiment of the present application, the bit string length information field in the message information is read, and then based on the data in the bit string length information field, it is determined whether this BIER stream requires statistics.

[0086] 16, which is a specific flowchart of step S400 in the case of a preset statistical rule based on bit string length information in an information processing method according to another embodiment of the present application. The above step S400 may include, but is not limited to, step S721 and step S722.

[0087] Step S721: The bit index transfer table is obtained.

[0088] Step S722: Calculate statistics of the BIER stream based on the bit string length information in the bit index forwarding table.

[0089] In one embodiment, when the preset statistical rule is to perform statistics based on bit string length information, in addition to performing statistics as shown in Figure 15 above, in an embodiment of the present application, entries in the Bit Index Forwarding Table (BIFT) with a BSL of 256 may be flagged as requiring statistics, and BIER stream statistics may be performed only when such entries are used for forwarding.If the method of flagging entries as statistics is not adopted, when processing a BIER stream, if it is found that the BSL value corresponding to the searched entry is a BSL requiring statistics, the corresponding statistics may be performed.

[0090] Therefore, in an embodiment of the present application, a bit index forwarding table may be obtained, and then based on the bit string length information in the bit index forwarding table, it may be determined whether this BIER stream requires statistics.

[0091] 17, which is a specific flowchart of step S400 in the case of a preset statistical rule based on sub-domain information in an information processing method according to an embodiment of the present application. The above step S400 may include, but is not limited to, step S811 and step S812.

[0092] Step S811: The sub-domain information field in the message information is read.

[0093] Step S812: Calculate statistics of the BIER stream based on the sub-domain information field.

[0094] 18, which is a specific flowchart of step S400 in the case of a preset statistical rule based on sub-domain information in an information processing method according to another embodiment of the present application. The above step S400 may include, but is not limited to, step S821 and step S822.

[0095] Step S821: The bit index transfer table is obtained.

[0096] Step S822: Calculate statistics of the BIER stream based on the sub-domain information of the bit index forwarding table.

[0097] Based on the above embodiments of FIGS. 17 and 18, the embodiments of the present application may execute the above method steps of FIG. 17 or FIG. 18 when the sub-domain information is the preset statistical rule.

[0098] In one embodiment, if statistics are required for a BIER stream of a certain subdomain (SD), a statistics flag may be attached to the entry corresponding to that SD in the BIFT, and if that entry is found when processing the BIER stream, the corresponding statistics may be performed. For example, if the BIFT contains entries with an SD of 0 and an SD of 1, and statistics are required for the BIER stream with an SD of 0, a statistics flag may simply be attached to the entry corresponding to the SD of 0. If the method of attaching statistics flags to entries is not employed, the corresponding statistics may be performed only if, when processing the BIER stream, it is found that the SD value corresponding to the searched entry is a subdomain for which statistics are required. Alternatively, if the values ​​of some bits in the BIFT-ID in the BIER stream are directly determined to be SDs for which statistics are required, for example, if the values ​​of bits 5 to 12 in the BIFT-ID in the BIER stream are 0 and the SD of the BIER stream for which statistics are required is 0, then the BIER stream is traffic for which statistics are required.

[0099] 19, which is a specific flowchart of step S400 in the case of a preset statistical rule based on bit forwarding ingress router device identity information in the information processing method according to an embodiment of the present application. The above step S400 may include, but is not limited to, step S910 and step S920.

[0100] Step S910: Read the bit forwarding ingress router device identity information field in the message information.

[0101] Step S920: Statistic the BIER stream according to the bit forwarding ingress router device identity information field.

[0102] In one embodiment, if a pre-configured statistics rule performs statistics based on bit-forwarding ingress router device identity information, statistics are required for BIER streams from one or more ingress BFIR devices. In this case, statistics are performed only if the BFIR-id field value in the message is found to be identical to the value of the BFIR device for which statistics are required when processing the BIER stream. For example, if statistics are required only for BIER streams sent from BFIR1 device, statistics are performed only if the BFIR-ID value in the BIER message is set to the BFIR-ID value of this device when processing the BIER stream.

[0103] Therefore, in the embodiment of the present application, the bit forwarding ingress router device identity information field in the message information is read, and then based on the data in the bit forwarding ingress router device identity information field, it is determined whether this BIER stream requires statistics.

[0104] 20, which is a specific flowchart of step S400 in the case of a preset statistical rule based on bit forwarding egress router device identity information in the information processing method according to an embodiment of the present application, the above step S400 may include, but is not limited to, steps S1010, S1020, and S1030.

[0105] Step S1010: Read the BitString, bit string length information and set identifier in the message information.

[0106] Step S1020: Determine a target position in the BitString based on the bit string length information and the set identifier.

[0107] Step S1030: The BIER stream is statistically calculated according to the setting status of the target position.

[0108] In one embodiment, if the pre-defined statistics rule performs statistics based on bit-forwarding egress router device identity information, it is necessary to perform statistics on BIER streams to one or more BFER devices. In this case, when processing a BIER stream, traffic statistics need to be performed only if the corresponding BFR-id bit in the BitString is set. The method for determining the set is as follows: upon receiving a BIER stream, first determine the corresponding BSL and Set Identifier (SI), and then determine whether the Set in the BitString corresponds to the BFR-id of the BFER for which statistics are required. The set is determined by k = BFR-id - SI * BSL, where k corresponds to the kth Bit in the BitString. Assume that the BFR-id values ​​of the target BFER devices for which statistics are required are 1 and 258, respectively, and the BSLs corresponding to the entries in the BIFT are 64 and 256, respectively. If the received BIER stream corresponds to the entry with a BSL of 64 and the SI is 0, traffic statistics need to be performed if the first bit in the BitString is set. If the received BIER stream corresponds to an entry with a BSL of 64 and an SI of 4, and the second bit in the BitString is set, traffic statistics must be performed. If the received BIER stream corresponds to an entry with a BSL of 256 and an SI of 0, and the first bit in the BitString is set, traffic statistics must be performed. If the received BIER stream corresponds to an entry with a BSL of 256 and an SI of 1, traffic statistics must be performed.

[0109] Therefore, in the embodiment of the present application, the BitString, bit string length information, and set identifier in the message information are read, and then the target position in the BitString is determined based on the bit string length information and the set identifier, and based on the set status of the target position, it is determined whether this BIER stream requires statistics.

[0110] Based on the method steps of the above embodiment, BIER stream encapsulation identification realizes the most basic BIER stream identification, and other filtering methods based on BSL, TC / DSCP, SD, ingress BFIR-ID, BFER, designated traffic, etc. must be based on the correct identification of the BIER stream. These filtering methods may be used alone or in any combination with BIER stream encapsulation identification.

[0111] In addition, the determination of whether traffic is to be counted can be realized by attaching a statistics flag to the corresponding forwarding entry, or by determining whether the traffic belongs to the range to be counted based on the contents of the forwarding entry when searching for the forwarding entry without changing it.The specific determination flow is shown in Figure 21.

[0112] BIER stream statistics may include, but are not limited to, the number of BIER stream messages or BIER stream bytes received, the egress interface sending the BIER stream, the number of BIER stream messages or BIER stream bytes sent, the number of BIER stream messages or BIER stream bytes discarded, timestamps of the BIER stream arriving at and leaving the device, etc.

[0113] 22, which is a specific flowchart of step S400 in the case of a preset statistical rule based on a source address and a destination address in an information processing method according to an embodiment of the present application. The above step S400 may include, but is not limited to, step S1111 and step S1112.

[0114] Step S1111: If the current node is an ingress node or an egress node, read the source address field and the destination address field in the message information.

[0115] Step S1112: Calculate statistics of the BIER stream based on the source address field and the destination address field.

[0116] 23, which is a specific flowchart of step S400 in the case of a preset statistical rule based on a source address and a destination address in an information processing method according to another embodiment of the present application. The above step S400 may include, but is not limited to, step S1121 and step S1122.

[0117] Step S1121: If the current node is an ingress node, an intermediate node, or an egress node, read the first field and the second field in the message information.

[0118] Step S1122: Statistic the BIER stream based on the first field including the Ethernet type information, the MPLS label stack information, the Next Header field or the Routing Header field, and the second field including the Proto field and the payload field.

[0119] 24, which is a specific flowchart of step S400 in the case of a preset statistical rule based on a source address and a destination address in an information processing method according to another embodiment of the present application. The above step S400 may include, but is not limited to, step S1131 and step S1132.

[0120] Step S1131: If the current node is an ingress node, an intermediate node, or an egress node, read the third and fourth fields in the message information.

[0121] Step S1132: Statistical processing is performed on the BIER stream based on the third field including the Destination Options Header field or the Routing Header field, and the fourth field including the source address field and / or the payload field.

[0122] Based on the above embodiments of FIGS. 22 to 24, the embodiments of the present application may implement one or more of the above embodiments of FIGS. 22 to 24 when the source address and the destination address are set as a preset statistical rule.

[0123] In one embodiment, assuming that some multicast traffic entering this BIER domain needs to be counted, the message needs to be further evaluated to determine whether it falls within the required range. Since the ingress node BFIR and the egress node BFER need to encapsulate and decapsulate the BIER header for multicast traffic, they may perform direct counting based on traffic characteristics such as 2-tuple (source address, destination address) or multi-tuple (source address, destination address, source port number, and destination port number). If the multicast traffic belongs to a Virtual Private Network (VPN), the VPN value may be added to determine whether to perform traffic identification and statistics.

[0124] However, for intermediate device BFRs in the BIER domain, further distinction is required for identification and statistics. First, a distinction is made based on the BIER encapsulation as follows: For BIER streams based on Ethernet encapsulation and MPLS encapsulation, and when the Next Header in the IPv6 header indicates BIER-type encapsulation, or when the IPv6 Next Header is set to RH and contains a BIER-type encapsulation method, determining whether this stream is traffic to be counted requires auxiliary judgment based on the values ​​of the Proto domain and other domains in the BIER header and the payload field after the BIER header. When the IPv6 Next Header is set to DOH and contains a BIER-type option, or when the IPv6 Next Header is set to RH and contains a BIER-type encapsulation method, determining whether this stream is traffic to be counted requires auxiliary judgment based on the source address field in the IPv6 header and / or the payload field after the IPv6 extension header.

[0125] In one embodiment, assuming that it is necessary to count multicast traffic (source address 201.1.1.1, destination address 224.1.1.1) that does not belong to any VPN and whose BIER domain encapsulation method is MPLS encapsulation method, after receiving the BIER stream, the intermediate device BFR needs to further determine whether the Proto domain value of the BIER is set to a value indicating IPv4 (e.g., 4), and further analyze the IPv4 source address and destination address after the BIER header to determine whether they are the same as (source address 201.1.1.1, destination address 224.1.1.1), and if they are the same, it will count this traffic.

[0126] In one embodiment, it is assumed that one multicast traffic (source address 201.1.1.1, destination address 224.1.1.1) needs to be counted, and that this multicast traffic belongs to a VPN assumed to be VPN 1, and that this traffic is injected into the BIER domain via ingress device BFIR1, and that the encapsulation method is BIER Ethernet® encapsulation. In this case, the intermediate device BFR needs to know the identification value assigned to the traffic by the ingress node BFIR1. Assuming that the ingress node BFIR assigns an MPLS label value of 200 to the traffic or the VPN, after receiving the BIER stream, the intermediate device BFR determines whether the Proto field is represented by an MPLS value (e.g., 2), and if the BFIR-ID field of the BIER header is filled in with the BFR-ID of BFIR1, further determines whether the label value following the BIER header is equal to 200. If all of the above conditions are met, the intermediate device BFR will count the traffic.

[0127] In one embodiment, assuming that the traffic is multicast traffic from the same VPN1, the Next Header in the IPv6 header is set to BIER type as the encapsulation method in the BIER domain, and the ingress device BFIR1 assigns 2001::201 as the IPv6 SID (Service Identifier) ​​value, after receiving the BIER stream, the intermediate device BFR determines whether the Proto field is represented by a value of IPv6 SID type, and if the BFIR-ID field in the BIER header is filled in with the BFR-ID of BFIR1, it further determines whether the value following the BIER header is equal to 2001::201, and if all of the above conditions are met, it records the traffic statistics.

[0128] In one embodiment, assume that the IPv6 multicast traffic from VPN1 is encapsulated in the BIER domain with the Next Header of the IPv6 header set to DOH, the DOH includes a BIER type option, and the ingress device BFIR1 assigns 2001::201 as the IPv6 SID (Service Identifier) ​​value. After receiving the BIER stream, the intermediate device BFR determines whether the source address field of the IPv6 header is the same as this IPv6 SID value, and if so, records statistics on this traffic. If the IPv6 SID value assigned by BFIR1 to all multicast traffic in VPN1 is 2001::202, after receiving the BIER stream, the intermediate device BFR determines based on encapsulation that the source address field of the IPv6 header is the same as the IPv6 SID value, then further examines the payload portion following the IPv6 header and its extension header (DOH), determines whether it represents IPv6 based on the Next Header value of the DOH, and also determines whether the source address and destination address of the IPv6 message in the payload match the IPv6 multicast traffic to be counted, and if they match, performs statistics.

[0129] In one embodiment, assuming that the traffic requiring statistics is BUM (Broadcast, Unknown, Multicast) traffic from an Ethernet VPN (EVPN), the determination may be made in the same manner as above, and the traffic after the BIER header may be identified by a Media Access Control (MAC) address matching method, thereby realizing statistics on Layer 2 traffic.

[0130] In addition, in the embodiment of the present application, in addition to setting pre-set statistical rules for statistically analyzing the above-mentioned BIER streams, statistical rules may not be set. In other words, in the embodiment of the present application, statistics may be performed without the need to restrict the statistical analysis of all BIER streams, and the statistical procedure is shown in Figure 25.

[0131] 25, which is a flowchart illustrating a method for processing all BIER streams without a preset statistical rule according to an embodiment of the present application, the method may further include, but is not limited to, steps S1210, S1220, S1230, S1240, S1250, and S1260 after step S100.

[0132] Step S1210: Read the Ethertype information in the message information of the BIER stream, and select the BIER stream based on the Ethertype information.

[0133] Step S1220: Read the MPLS label stack information in the message information of the BIER stream, and sort the BIER stream based on the MPLS label stack information.

[0134] Step S1230: Read the Next Header field in the message information of the BIER stream, and select the BIER stream based on the Next Header field.

[0135] Step S1240: Read the Destination Options Header field in the message information of the BIER stream, and select the BIER stream based on the Destination Options Header field.

[0136] Step S1250: Read the Routing Header field in the message information of the BIER stream, and sort the BIER stream based on the Routing Header field.

[0137] Step S1260: The selected BIER stream is set as a target BIER stream to be subjected to statistics, and statistics are performed on the target BIER stream.

[0138] Specifically, if it is necessary to count all BIER streams without any restrictions, the BIER observation point must count BIER streams based on Ethernet encapsulation, BIER streams based on MPLS encapsulation, and BIER streams based on IPv6 encapsulation. A BIER stream based on Ethernet encapsulation is characterized by a stream with the Ethernet type set to 0xAB37. A BIER stream based on MPLS encapsulation has the MPLS label stack bottom label as a label indicating BIER forwarding. A BIER stream based on IPv6 encapsulation includes the following three cases. The first case is a stream with the IPv6 Next Header set to a BIER type. The second case is a stream with the IPv6 Next Header set to 60, i.e., DOH, and the DOH contains a BIER type option. The third case is a stream with the IPv6 Next Header set to 43, i.e., RH, and the RH contains a BIER type.

[0139] As shown in FIG. 26, FIG. 26 is a flowchart of an information processing method according to another embodiment of the present application, which may be applied to the collector of FIGS. 1 and 2 or to the BIER observation point of FIG. 2, and may include steps S1300 to S1400, but is not limited thereto.

[0140] Step S1300: The node statistical information of the BIER stream and the coding information corresponding to the node statistical information are obtained.

[0141] Step S1400: Determine the current network state based on the node statistics information and the coding information.

[0142] In one embodiment, for analysis by a collector, when a BIER observation point transmits node statistics, it carries encoded information of the relevant data for the collector to decode. The encoded information includes two parts: a template and data. The template may include one or more elements such as the number of messages or bytes in the BIER stream, the egress interface transmitting the BIER stream, the number of messages or bytes in the BIER stream transmitted, the number of messages or bytes in the BIER stream discarded, the timestamps at which the BIER stream arrives at the device and the timestamps at which it leaves the device, as well as qualification elements such as the bit string length, the ingress BFIR device ID, the designated TC / DSCP, the designated BIER subdomain, the designated egress BFIR device, and the designated multicast traffic.

[0143] The collector may obtain the network transmission delay of the BIER stream based on the timestamp information of the node statistics information, and use it as a parameter for traffic engineering. Alternatively, the collector may determine whether counterfeit traffic or attack traffic exists in the network based on a comparison between the traffic entering the BIER domain and the traffic leaving the BIER domain.

[0144] In one embodiment, when the BIER observation point performs the analysis process itself, the BIER observation point obtains node statistics and then determines the current network status based on the node statistics. For example, the BIER observation point may obtain the transmission delay of the BIER stream in the network based on the timestamp information in the node statistics and use this as a parameter for traffic engineering. Alternatively, the BIER observation point may determine whether counterfeit traffic or attack traffic exists in the network based on a comparison of traffic entering the BIER domain with traffic leaving the BIER domain.

[0145] 27, which is a specific flowchart of step S1400 in an information processing method according to an embodiment of the present application. The encoding information includes a template and data parameters of the template, and the above step S1400 may include, but is not limited to, step S1510 and step S1520.

[0146] Step S1510: Analyze the node statistical information based on the structure and data parameters of the template to obtain analysis information.

[0147] Step S1520: Determine the current network status based on the analysis information.

[0148] Specifically, after collecting statistics on the corresponding traffic at the observation point, the statistical data can be sent to the collector by combining the data with a template. The template exists so that the structure of the data sent by the collector can be known and the data can be correctly analyzed.

[0149] Figure 28 shows the status of a BIER stream with a DSCP value of 6 when an observation point (e.g., BFR1) collects statistics on a specific BIER SD (e.g., 0). The statistics include the number of received BIER stream messages and bytes, the number of discarded BIER stream messages, and the timestamps of the BIER stream arriving at and departing from the device. The values ​​listed after the statistical data (e.g., 501-512, 152, 153, etc.) are type values ​​of information elements that the collector can identify, and the collector can understand the corresponding meaning based on these type values. For example, bierSubDomainId indicates the BIER SD, and this value is entered as the subdomain value 0 for which statistics are required in the BIER stream record following this template. bierDiffServCodePoint indicates the DSCP field, and this value is entered as the DSCP value 6 for which statistics are required in the BIER stream record following this template. bierPacketTotalCount refers to the number of messages in the BIER stream, bierOctetTotalCount refers to the number of bytes in the BIER stream, bierDroppedPacketCount refers to the number of messages in the BIER stream that were dropped, etc., and flowStartMilliseconds and flowEndMilliseconds refer to the time it takes for the BIER stream to enter and exit the observation point device.

[0150] Figure 29 shows the status of a BIER stream with a BSL of 256 from a specific BFIR device, as collected by an observation point (e.g., BFR3 or BFER1), including the number of messages and the number of bytes in the BIER stream. Similarly, the values ​​listed after the statistical data, such as 503, 504, 513, and 514, are type values ​​of information elements that the collector can identify, and the collector can understand the corresponding meaning based on the type value. For example, bierBsl indicates the length of BitStringLength, and this value is entered as 256 in the BIER stream record that follows this template. bierBfirId indicates the BFR-ID of the specified BFIR device, and this value is entered as the BFR-ID value of the specified BFIR device in the BIER stream record that follows this template. bierPacketDeltaCount refers to the number of messages in the BIER stream received since the record was last sent, and bierOctetDeltaCount refers to the number of bytes in the BIER stream received since the record was last sent.

[0151] Figure 30 shows the status of the transmission of a specific multicast stream, as collected by an observation point (let's say BFR1), including the number of messages and bytes of the received BIER stream, and the time the traffic entered and left the observation point device. Similarly, the values ​​added after the statistical data, such as 8, 12, 501, 502, 152, and 153, are type values ​​of information elements that the collector can identify, and the collector can understand the corresponding meaning based on the type value. For example, sourceIPv4Address indicates the source address of a specific multicast stream, and destinationIPv4Address indicates the destination address of a specific multicast stream.

[0152] Figure 31 shows the status of a BIER stream of a specific BIER encapsulation type for a specific BFER device (e.g., BFER1) collected by an observation point (e.g., BFR3), including the ingress and egress interfaces receiving that type of traffic and the number of messages of that type. Similarly, the values ​​listed after the statistical data (e.g., 10, 14, 501, 521, and 522) are type values ​​of information elements that the collector can identify, and the collector can understand the corresponding meaning based on these type values. For example, bierEncapType is the encapsulation type of the BIER stream, and values ​​1, 2, and 3 represent Ethernet encapsulation, MPLS encapsulation, and IPv6 encapsulation, respectively. bierBferId represents the BFR-ID value of a specific BFER device, ingressInterface represents the ingress interface number receiving the traffic, and egressInterface represents the egress interface number used to forward the message.

[0153] The corresponding statistical data is sent by the observation point to the collector together with the template. The sending method is to send the statistical data immediately after sending the template. The order and length of the statistical data are exactly the same as the description in the template, so the collector can successfully parse these statistical data based on the template.

[0154] The above are merely some examples shown in the embodiments of the present application, and in the actual application process, the above elements may be freely combined, but the embodiments of the present application are not limited thereto.

[0155] 32 is a specific flowchart of step S1400 in an information processing method according to an embodiment of the present application, in which the node statistical information includes a timestamp when the BIER stream arrives at the node and a timestamp when the BIER stream leaves the node. Step S1400 may include, but is not limited to, step S1610 and step S1620.

[0156] Step S1610: Analyze the node statistics based on the encoding information to obtain the timestamps when the BIER stream arrives at the node and when the BIER stream leaves the node.

[0157] Step S1620: Determine the transmission time of the BIER stream in the BIER domain based on the timestamp when the BIER stream arrives at the node and the timestamp when the BIER stream leaves the node.

[0158] In one embodiment, for example, by collecting statistical data from BFIR1, BFR1, BFR3, and BFER1 as shown in the template in Figure 28, the processing time of each device for a BIER stream with DSCP set to 6 in the subdomain of BIER SD 0 can be obtained, i.e., the difference between flowStartMilliseconds and flowEndMilliseconds of each device can be used to obtain the time it takes each device to process that type of traffic. Adding these times together gives the transmission time of that type of traffic in this BIER domain, and this transmission time is useful as an important parameter for traffic engineering.

[0159] 33 is a specific flowchart of step S1400 in the case where the number of discarded BIER stream messages is included in the node statistical information in the information processing method according to an embodiment of the present application. Step S1400 may include, but is not limited to, step S1710 and step S1720.

[0160] Step S1710: Analyze the node statistics information based on the encoding information to obtain the number of discarded messages of the BIER stream.

[0161] Step S1720: Determine the current network load situation based on the number of discarded BIER stream messages.

[0162] In one embodiment, if the collector collects statistical data from BFR1, for example using the template similar to that shown in Figure 28, and finds that the number of BIER messages discarded by this device has reached a certain level, this indicates that this device may be in an overload situation, so the collector should notify the network administrator or network controller, which should then issue an adjustment configuration to alleviate or eliminate the overload situation for this device.

[0163] 34, which is a specific flowchart of step S1400 in the case where the node statistical information includes an ingress interface that receives a BIER stream and an egress interface that transmits a BIER stream in the information processing method according to an embodiment of the present application. The above step S1400 may include, but is not limited to, step S1810 and step S1820.

[0164] Step S1810: Analyze the node statistics information based on the encoding information to obtain the ingress interface for receiving the BIER stream and the egress interface for transmitting the BIER stream.

[0165] Step S1820: Determine the current network configuration status based on the ingress interface that receives the BIER stream and the egress interface that transmits the BIER stream.

[0166] In one embodiment, if the collector collects statistical data of a BIER stream of a specific encapsulation type from a BFR1 device to a specific BFER device using the template shown in Figure 31 and finds that there is no traffic or that the collected ingress / egress interface numbers do not match those expected, this indicates that there may be a configuration error or other abnormality in the network. In order to detect the problem early, the collector records this abnormality and notifies the network administrator or controller of this and prompts them to troubleshoot the network configuration, etc.

[0167] 35, which is a specific flowchart of step S1400 in an information processing method according to an embodiment of the present application, when the number of messages in a BIER stream is included in the node statistical information and the message information includes a source address and a destination address. The above step S1400 may include, but is not limited to, step S1910 and step S1920.

[0168] Step S1910: Analyze the node statistics information based on the encoding information to obtain the number of messages, source address, and destination address of the BIER stream.

[0169] Step S1920: Determine the current network attack situation according to the number of messages, source address, and destination address of the BIER stream.

[0170] In one embodiment, assume that a collector collects statistical data for a specific multicast stream (assuming a source address of 201.1.1.1 and a destination address of 224.1.1.1) using the template shown in Figure 30. Normally, the two data should not differ significantly. However, if an abnormality occurs in the network, for example, if the number of BIER messages for a specific multicast stream on BFIR1 is much larger than the number of BIER messages for the multicast stream on BFIR1, and this multicast stream can only enter this BIER domain through BFIR1, this indicates the possibility of forged attack traffic in the network. For example, there is a node in the network that copies BIER messages sent from BFIR1 to occupy network bandwidth. In this case, the collector needs to notify the network administrator or network controller of the abnormality to prevent the forged attack traffic from continuing to occupy bandwidth.

[0171] 36 is a schematic diagram of a configuration of a network device according to an embodiment of the present application. The embodiment of the present application also discloses a network device 200 including a memory 220, a processor 210, and a computer program stored in the memory 220 and operable by the processor 210, wherein the processor 210 executes the computer program to perform the information processing method of any of the above embodiments.

[0172] Memory 220 may be used as a non-transitory computer-readable storage medium to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory 220 may include high-speed random access memory, as well as non-transitory memory such as at least one magnetic disk memory device, flash memory device, or other non-transitory solid-state memory device. In some embodiments, memory 220 optionally includes memory located remotely from processor 210, and these remote memories may be connected to the implementation environment via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0173] The network device 200 in this embodiment may correspond to a BIER observation point or collector in the implementation environment of the embodiment shown in Figures 1 to 3. Since both belong to the same application concept, they have the same realization principles and beneficial effects, and will not be described in detail here.

[0174] The non-transitory software programs and instructions necessary to realize the information processing methods of the above embodiments are stored in memory 220, and when executed by processor 210, the information processing methods of the above embodiments are performed, for example, the method steps of Figures 4 to 7, Figures 10 to 20, Figures 22 to 27, and Figures 32 to 35 above are performed.

[0175] For specific embodiments and technical effects of the network device 200 according to the embodiment of the present application, reference may be made to the specific embodiments and technical effects of the information processing method described above.

[0176] Furthermore, an embodiment of the present application further discloses a computer-readable storage medium storing computer-executable instructions for performing an information processing method such as any of the above embodiments.

[0177] Furthermore, one embodiment of the present application further discloses a computer program product including a computer program or computer instructions stored in a computer-readable storage medium, wherein a processor of the computer device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, thereby causing the computer device to perform the information processing method of any of the above embodiments.

[0178] All or part of the steps in the methods and systems disclosed above may be implemented as software, firmware, hardware, and any suitable combination thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processor, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (e.g., 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 disk (DVD) or other optical disk storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or any other medium that can be used to store desired information and that can be accessed by a computer. Additionally, communication media typically includes computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery media, as known to those skilled in the art.

Claims

1. An information processing method executed by a network device, comprising: receiving a BIER stream flowing through a current node; performing statistics on the BIER stream to obtain node statistics information of the BIER stream; generating coded information corresponding to the node statistics and transmitting the node statistics and the coded information to a collector so that the collector determines a current network state based on the node statistics and the coded information.

2. After the step of receiving the BIER stream flowing through the current node, The information processing method of claim 1, further comprising a step of determining a target BIER stream to be statistically analyzed from among the received BIER streams based on message information of the BIER stream and a predetermined statistical rule for the statistics of the target BIER stream.

3. The predetermined statistical rule is: A method obtained by the configuration information of the current node; The scheme obtained by extending the YANG model to the current node; and 3. The information processing method according to claim 2, wherein the information is obtained by any of the methods obtained by extending a BGP-LS to the current node.

4. 3. The information processing method according to claim 2, wherein the predetermined statistical rule performs statistics based on at least one of encapsulation type information, bit string length information, subdomain information, traffic flow classification information, differentiated services code point information, bit forwarding ingress router device identity information, bit forwarding egress router device identity information, predetermined traffic elements, source address, destination address, source port number, and destination port number.

5. The node statistical information is 2. The information processing method of claim 1, wherein the information includes at least one of the number of messages received for the BIER stream, the number of bytes received for the BIER stream, the egress interface transmitting the BIER stream, the number of messages sent for the BIER stream, the number of bytes sent for the BIER stream, the number of messages discarded for the BIER stream, the number of bytes discarded for the BIER stream, a timestamp at which the BIER stream arrives at the current node, and a timestamp at which the BIER stream leaves the current node.

6. The information processing method of claim 1 , further comprising determining a current network state based on the node statistical information.

7. An information processing method executed by a network device, comprising: obtaining node statistics of a BIER stream and coding information corresponding to the node statistics; determining a current network state based on the node statistical information and the encoded information.

8. The coded information includes a template and data parameters of the template, and the step of determining a current network state based on the node statistical information and the coded information includes: analyzing the node statistical information based on the template structure and the data parameters to obtain analysis information; and determining a current network state based on the analyzed information.

9. If the node statistics information includes timestamps at which the BIER stream arrives at a node and timestamps at which the BIER stream leaves a node, the step of determining a current network state based on the node statistics information and the encoding information includes: analyzing the node statistics based on the encoding information to obtain timestamps of BIER streams arriving at a node and timestamps of BIER streams leaving a node; and determining a transmission time of the BIER stream in a BIER domain based on a timestamp at which the BIER stream arrives at a node and a timestamp at which the BIER stream leaves a node.

10. If the number of discarded BIER stream messages is included in the node statistics information, the step of determining a current network state based on the node statistics information and the encoding information includes: analyzing the node statistics based on the encoding information to obtain the number of discarded BIER stream messages; and determining a current network load situation based on the number of messages of the discarded BIER stream.

11. When the node statistics information includes an ingress interface that receives a BIER stream and an egress interface that transmits a BIER stream, the step of determining a current network state based on the node statistics information and the encoding information includes: analyzing the node statistics based on the encoding information to obtain an ingress interface for receiving the BIER stream and an egress interface for transmitting the BIER stream; and determining a current network configuration status based on an ingress interface that receives the BIER stream and an egress interface that transmits the BIER stream.

12. When the number of messages of a BIER stream is included in the node statistics information and the message information of the BIER stream includes a source address and a destination address, the step of determining a current network state based on the node statistics information and the encoding information includes: analyzing the node statistics based on the encoding information to obtain the number of messages, source addresses, and destination addresses of BIER streams; and determining a current network attack situation based on the number of messages in the BIER stream, the source address, and the destination address.

13. A network device comprising a memory, a processor, and a computer program stored in the memory and operable by the processor, wherein the processor, when operating the computer program, executes the information processing method according to any one of claims 1 to 6 and / or the information processing method according to any one of claims 7 to 12.

14. A computer-readable storage medium storing computer-executable instructions for executing the information processing method according to any one of claims 1 to 6 and / or the information processing method according to any one of claims 7 to 12.

Images