A method, apparatus, equipment, medium, and product for network traffic monitoring.

By combining NetFlow and BGP protocols, the system monitors network traffic characteristics and routing configuration information, and uses segment routing information to match prefix segment identifiers. This solves the problem of existing technologies being unable to identify SRv6 network traffic, enabling accurate capture and classification of mixed SRv6 and MPLS network traffic, and improving operational efficiency.

CN121711191BActive Publication Date: 2026-11-10深圳市万里眼技术有限公司
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202610195637.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2026-02-11
Publication Date
2026-11-10
Estimated Expiration
2046-02-11

AI Technical Summary

Technical Problem

Existing technologies cannot identify SRv6 network traffic, have low processing efficiency, cannot meet operators' support needs for new network technologies, and rely on manual pre-configuration for traffic type identification, resulting in insufficient processing efficiency.

Method used

By combining the NetFlow and BGP protocols, the system monitors network traffic characteristics and routing configuration information, and uses segment routing information to match prefix segment identifiers to automatically identify SRv6 network traffic, achieving accurate capture and classification of mixed SRv6 and MPLS network traffic.

Benefits of technology

It enables accurate identification and classification of SRv6 network traffic, reduces operational complexity, improves traffic analysis efficiency, avoids errors caused by manual configuration, and meets operators' needs for refined management of SRv6 services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121711191B_ABST
    Figure CN121711191B_ABST
Patent Text Reader

Abstract

This application discloses a network traffic monitoring method, apparatus, device, medium, and product, relating to the field of network analysis technology. The method includes: monitoring network traffic characteristic information when a target device transmits network traffic, wherein the traffic characteristic information includes segment routing information corresponding to a target Internet Protocol (IPP) based on segment routing technology; monitoring routing configuration information for network traffic monitored using a preset border gateway protocol, wherein the routing configuration information includes a prefix segment identifier; matching the segment routing information in the first target information with the prefix segment identifier in the second target information; and, based on the obtained first matching result, determining the first target network traffic corresponding to the target IPP from the network traffic to obtain the corresponding network traffic monitoring result. This method can accurately filter out the target network traffic of SRv6 from mixed network traffic, automatically matching segment routing information and prefix segment identifiers to avoid errors caused by manual operation and improve traffic analysis efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of network analysis technology, and in particular to a network traffic monitoring method, apparatus, equipment, medium, and product. Background Technology

[0002] With the widespread deployment of IPv6 (Internet Protocol Version 6) technology and the rapid development of emerging services such as 5G (5th Generation Mobile Communication Technology) and cloud computing, Segment Routing over IPv6 (SRv6) technology, based on the IPv6 forwarding plane, has become a core technology for building next-generation intelligent IP (Internet Protocol) networks due to its flexible path control capabilities, good scalability, and ability to guarantee the quality of service for high-value services. Meanwhile, network traffic monitoring and analysis, as a key means to ensure network service quality and improve operational efficiency, needs to adapt to the network architecture changes brought about by SRv6 technology.

[0003] Currently, most mainstream network traffic monitoring systems are deployed based on the NetFlow protocol. They achieve traffic monitoring through a process of collecting traffic data using NDE (NetFlow Data Exporter), storing data using NSC (NetFlow Collector), and analyzing data using NDA (NetFlow Data Analyzer). Existing technologies have attempted to combine NetFlow with Border Gateway Protocol (BGP) to enhance traffic analysis capabilities. For example, for Multi-Protocol Label Switching (MPLS) VPNs (Virtual Private Networks), NetFlow is used to obtain traffic 5-tuples and MPLS labels, which are then combined with routing information obtained through BGP to achieve MPLS VPN traffic identification and statistics.

[0004] However, existing solutions only support MPLS network traffic analysis and cannot identify SRv6 network traffic, thus failing to meet operators' support needs for new network technologies. Furthermore, traffic type identification relies heavily on manual pre-configuration or intervention, and its processing efficiency is insufficient. As network traffic grows exponentially, it is difficult to adapt to the refined operation and maintenance needs of large-scale networks. Summary of the Invention

[0005] This application discloses a network traffic monitoring method, apparatus, equipment, medium, and product, which solves the problem that current traffic analysis technologies only support MPLS network traffic analysis, cannot identify SRv6 network traffic, and have low processing efficiency.

[0006] In a first aspect, this application provides a network traffic monitoring method, comprising: monitoring first target information and second target information when a target device transmits network traffic; the first target information is traffic characteristic information of the network traffic monitored using a preset traffic monitoring protocol, and the second target information is routing configuration information of the network traffic monitored using a preset border gateway protocol; matching segment routing information in the first target information and prefix segment identifier in the second target information to obtain a first matching result; the segment routing information is routing information corresponding to a target Internet Protocol, and the target Internet Protocol is an Internet Protocol based on segment routing; based on the first matching result, determining first target network traffic corresponding to the target Internet Protocol from the network traffic to obtain a corresponding network traffic monitoring result. This solution monitors network traffic characteristics of target devices transmitting network traffic, including segment routing information corresponding to the target Internet Protocol (IPP) based on segment routing technology. Simultaneously, it monitors routing configuration information for network traffic monitored using a preset border gateway protocol, which includes prefix segment identifiers. The solution then matches the segment routing information in the first target information with the prefix segment identifiers in the second target information to filter and determine the target network traffic corresponding to the target IPP. Addressing the issue that existing flow sampling systems cannot identify and statistically analyze SRv6 network traffic, this solution achieves SRv6 network traffic identification through the collaboration of the preset traffic monitoring protocol NetFlow and the preset border gateway protocol BGP. It can accurately filter out the target network traffic corresponding to SRv6 from mixed network traffic without requiring manual configuration of the matching process. Automatic matching via segment routing information and prefix segment identifiers avoids errors caused by manual operation and improves traffic analysis efficiency.

[0007] In one possible implementation, the first target information further includes a target label, and the second target information further includes routing address information; wherein, the target label represents the target device transmitting network traffic based on Multiprotocol Label Switching (MPLS), and the routing address information is the address information of the target device when transmitting network traffic based on MPLS. In this implementation, the first target information further includes a target label, which is used to represent the target device transmitting network traffic based on MPLS technology; the second target information further includes routing address information, which is key address data of the target device when transmitting traffic based on MPLS. This addresses the current limitation of only being able to monitor MPLS traffic alone, which cannot adapt to mixed SRv6 and MPLS network scenarios, by enabling simultaneous collection of both SRv6 and MPLS traffic data, effectively reducing operational complexity.

[0008] In one possible implementation, before matching the segment routing information in the first target information and the prefix segment identifier in the second target information, the method further includes: constructing a first information group based on the prefix segment identifier in the second target information and the target routing information; the target routing information is the routing information when the target device transmits network traffic based on a virtual private network; constructing a second information group based on the routing address information in the second target information and the target routing information; wherein, the first information group is used to characterize the target device transmitting network traffic based on the target Internet Protocol, and the second information group is used to characterize the target device transmitting network traffic based on the Multiprotocol Label Switching. In this embodiment, a first information group is constructed based on the prefix segment identifier and target routing information in the second target information. This can characterize that the target device transmits network traffic based on the target Internet Protocol SRv6. A second information group is constructed based on the MPLS routing address information and target routing information in the second target information. This can characterize that the target device transmits network traffic based on Multiprotocol Label Switching (MPLS). This achieves the classification and aggregation of routing configuration information. To address the problem of low matching efficiency when processing massive NetFlow data, by pre-grouping, the data range for subsequent traffic matching is narrowed from the full routing information to the corresponding type of information group. This can reduce invalid traversal and improve the matching efficiency of mixed traffic.

[0009] In one possible implementation, the target routing information includes an address family identifier, a sub-address family identifier, and network layer reachability information for the Ethernet Virtual Private Network (VPN). In this embodiment, the target routing information includes an address family identifier, a sub-address family identifier, and network layer reachability information for the Ethernet VPN; wherein, the address family identifier is used to identify the routing address type, the sub-address family identifier is used to identify the routing type, and the network layer reachability information is used to describe the reachability of the route. Given the current inability to accurately distinguish the specific type of traffic, the VPN layer corresponding to the traffic can be directly determined through the combined identifiers in the target routing information, and the accuracy of VPN layer identification is further improved by combining it with reachability information.

[0010] In one possible implementation, after determining the first target network traffic corresponding to the target Internet Protocol from the network traffic based on the first matching result, the method further includes: determining the target routing type of the first target network traffic based on the target routing information in the first information group; the target routing type is the routing type when the target device routes the first target network traffic based on the virtual private network; and constructing the corresponding network traffic monitoring result based on the target routing type of the first target network traffic. In this implementation, after determining the first target network traffic from the network traffic, the target routing type corresponding to the first target network traffic is determined based on the target routing information contained in the first information group, that is, the hierarchical type when the target device routes the first target network traffic based on the virtual private network. The determined target routing type is then integrated into the monitoring result of the first target network traffic to form a refined monitoring result. This addresses the current problem of not being able to further subdivide the corresponding hierarchical level after identifying network traffic, enabling refined classification of SRv6, meeting the operator's refined management needs for SRv6 services, improving the dimensions of monitoring results, and further enhancing operational efficiency.

[0011] In one possible implementation, after matching the segment routing information in the first target information and the prefix segment identifier in the second target information to obtain a first matching result, the method further includes: matching the target label in the first target information and the routing address information in the second information group to obtain a second matching result; and based on the second matching result, determining the second target network traffic corresponding to the Multiprotocol Label Switching (MPLS) from the network traffic. In this implementation, after obtaining the first matching result, a further matching operation is performed on the target label in the first target information and the routing address information in the second information group to generate a second matching result. This allows for the filtering and determination of the second target network traffic corresponding to MPLS from the overall network traffic. This addresses the current problem of simultaneously failing to identify SRv6 and MPLS traffic, requiring multiple tools for separate processing. This solution enables unified identification of mixed traffic, simultaneously achieving accurate identification of both SRv6 and MPLS traffic, thus helping to reduce operation and maintenance costs and data integration difficulties.

[0012] In one possible implementation, after determining the second target network traffic corresponding to the Multiprotocol Label Switching (MPLS) from the network traffic based on the second matching result, the method further includes: matching the routing address information in the second information group with the target label in the first target information to obtain a third matching result; determining the target route type of the second target network traffic based on the third matching result; and constructing a corresponding network traffic monitoring result based on the target route type of the second target network traffic. In this implementation, after determining the second target network traffic, a secondary matching is performed between the routing address information in the second information group and the target label in the first target information to verify the correlation between the MPLS label and the route type in the routing address information, thereby determining the target route type corresponding to the second target network traffic. This allows the target route type of MPLS traffic to be integrated into the monitoring results, forming further refined monitoring results. Addressing the current problem of inaccurate MPLS traffic type identification, MPLS traffic can be further subdivided, which helps to achieve comprehensive monitoring of mixed traffic and meets the operation and maintenance needs of mixed networks.

[0013] In one possible implementation, after determining the first target network traffic corresponding to the target Internet Protocol from the network traffic based on the first matching result, the method further includes: determining segment list information in the segment routing information; the segment list information being the transmission path information during the transmission of the first target network traffic; determining the target operating mode corresponding to the first target network traffic based on the segment list information; the target operating mode being the protocol operating mode when the target device transmits the first target network traffic based on the target Internet Protocol; and constructing a network traffic monitoring result corresponding to the first target network traffic based on the target operating mode. In this implementation, after determining the first target network traffic, segment list information representing the path sequence during SRv6 traffic transmission is extracted from the segment routing information of the first target information, and the SRv6 protocol operating mode corresponding to the first target network traffic is determined based on the configuration attributes of the segment list information. The determined target operating mode is then integrated into the monitoring result of the first target network traffic, further forming a complete monitoring result for SRv6 traffic. This addresses the current problem of not being able to distinguish the operating modes of SRv6 traffic, which prevents focused monitoring of target services. It enables accurate differentiation of SRv6 operating modes, ensuring the transmission quality of high-value services and facilitating comprehensive monitoring and management of SRv6 traffic.

[0014] Secondly, this application provides a network traffic monitoring device, comprising: An information matching module is used to monitor first target information and second target information when a target device transmits network traffic; match segment routing information in the first target information and prefix segment identifier in the second target information to obtain a first matching result; based on the first matching result, determine the first target network traffic corresponding to the target Internet Protocol from the network traffic to obtain the corresponding network traffic monitoring result; the first target information is the traffic characteristic information of the network traffic monitored using a preset traffic monitoring protocol, and the second target information is the routing configuration information of the network traffic monitored using a preset border gateway protocol; the segment routing information is the routing information corresponding to the target Internet Protocol, and the target Internet Protocol is an Internet Protocol based on segment routing.

[0015] Thirdly, this application provides an electronic device, which includes a processor and a memory; wherein the memory is used to store a computer program, which is loaded and executed by the processor to implement the aforementioned network traffic monitoring method.

[0016] Fourthly, this application provides a computer-readable storage medium for storing a computer program, which, when executed by a processor, implements the aforementioned network traffic monitoring method.

[0017] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the aforementioned network traffic monitoring method.

[0018] Based on the above technical solution, this application can collect traffic feature information containing segment routing information through a preset traffic monitoring protocol, and collect routing configuration information containing prefix segment identifiers through a preset border gateway protocol. Since segment routing information is a unique identifier for SRv6 traffic, and the prefix segment identifier is a unique identifier for SRv6 routes, the problem of existing technologies being unable to identify SRv6 network traffic can be solved by matching segment routing information with prefix segment identifiers. This achieves accurate capture of SRv6 traffic without the need for manual pre-configuration of traffic identification rules or intervention in the matching process. It can automatically distinguish the first target network traffic corresponding to SRv6 from mixed network traffic, avoiding the inefficiency and latency caused by manual configuration in traditional methods. It can achieve rapid response and only focuses on the feature association between segment routing information and prefix segment identifiers, avoiding full parsing of massive traffic data, reducing the complexity of data processing, and alleviating the performance bottleneck of traffic analysis in large-scale networks. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 A network traffic monitoring device architecture diagram provided in this application embodiment; Figure 2 A flowchart of a network traffic monitoring method provided in this application embodiment; Figure 3 A flowchart for network traffic monitoring provided in this application embodiment; Figure 4 A flowchart illustrating a specific network traffic monitoring method provided in this application embodiment; Figure 5 A schematic diagram of network traffic classification provided in an embodiment of this application; Figure 6 A schematic diagram of a network traffic monitoring device provided in this application embodiment; Figure 7 This is a structural diagram of an electronic device provided in an embodiment of this application.

[0021] Explanation of reference numerals in the attached figures: 11-Data Information Acquisition Module; 12-Information Matching Module: —121- Data information association module; 122- Data information statistics module; 123- Statistical result display module. Detailed Implementation

[0022] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0023] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0024] Most mainstream network traffic monitoring systems are currently deployed based on the NetFlow protocol, which monitors traffic by analyzing the flow of data. However, most current technical solutions only support MPLS network traffic analysis and cannot identify SRv6 network traffic, thus failing to meet operators' support requirements for new network technologies. This application can collect traffic feature information containing segment routing information and routing configuration information containing prefix segment identifiers. By matching segment routing information with prefix segment identifiers, it can accurately capture SRv6 traffic and focus only on the feature association between segment routing information and prefix segment identifiers, avoiding full parsing of massive traffic data and effectively alleviating the performance bottleneck of traffic analysis in large-scale networks.

[0025] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0026] First, it should be noted that the technical solution in this application is mainly used for fine-grained traffic monitoring in SRv6 / MPLS hybrid network environments, and is intended to cover mainstream network deployment forms such as operators, enterprises, and cloud data centers. For example, in operator 5G network scenarios, it can adapt to the SRv6 bearer requirements of 5G architecture, and solve the problem of traffic differentiation and monitoring when high-value services (such as telemedicine) and traditional MPLS VPN services are mixed; in enterprise campus interconnection scenarios, it can adapt to the multi-campus and cross-regional branch networking of large enterprises, support mixed traffic analysis during the SRv6 upgrade stage, and meet the fine-grained management of different services such as office and production.

[0027] Specifically, the technical solution of this application can be embedded in an enterprise operation and maintenance system to realize traffic analysis. For example, in an enterprise SD-WAN (Software-Defined Wide Area Network) system, an SD-WAN gateway supporting SRv6 can be adapted to distinguish VPN types of traffic. In this case, the operation and maintenance system may include: a traffic analysis device, i.e., an independently deployed analysis device for implementing the technical solution of this application, capable of receiving network traffic mirroring data; a router / switch, which can be used to directly collect and analyze local NetFlow / BGP data; and a campus gateway, i.e., the egress gateway of the enterprise campus, which can be used to implement SRv6 / MPLS VPN traffic statistics functions. For example, such as... Figure 1 As shown, in one specific implementation, a router can be connected through a specific port to receive raw traffic (including SRv6 segment routing information and MPLS labels) forwarded by the router, and traffic characteristics can be collected through the NetFlow protocol. At the same time, a switch can be connected through other specific ports, such as the TCP (Transmission Control Protocol) port, and VPN routing information can be obtained through BGP. After traffic analysis based on the technical solution of this application, the visualization results such as traffic classification reports can be output through a visualization platform.

[0028] Example 1

[0029] See Figure 2 As shown in the figure, this application discloses a network traffic monitoring method, including: Step S11: Monitor the target device's network traffic transmission with first target information and second target information; the first target information is the traffic characteristic information of the network traffic monitored using a preset traffic monitoring protocol, and the second target information is the routing configuration information of the network traffic monitored using a preset border gateway protocol.

[0030] In this embodiment, as Figure 1 and Figure 3As shown, the traffic analysis function in this embodiment can be integrated into the target device. When external traffic enters this device, it receives raw traffic from routers, switches, and other network devices through the network I / O (Input / Output) hardware interface. It should be noted that in this embodiment, the external traffic can be sampled through the router, for example, selecting one traffic item from every thousand traffic items of the same type for subsequent analysis. Further, after the external traffic enters the left-side network I / O, this device performs traffic replication without affecting the original traffic. The replicated traffic is then passed to the device's internal processing unit to organize basic traffic information, such as source IP (Internet Protocol Address), destination IP, and packet size. Afterward, the organized traffic is replicated again and passed to the processing unit within the device for traffic analysis. The device can call pre-stored routing configuration information, such as SRv6 / MPLS routes obtained via BGP, to perform traffic type matching. After matching, the classified traffic is replicated for traffic statistics, and the results of the traffic statistics are replicated and passed to the processing unit. Figure 1 The network I / O hardware interface on the right side ultimately outputs to visualization tools or other third-party systems.

[0031] Specifically, such as Figure 3As shown, NetFlow protocol traffic and BGP protocol traffic can be collected first and second target information when monitoring network traffic transmitted by the target device. The first target information is the traffic characteristic information of the network traffic monitored using the preset traffic monitoring protocol, namely NetFlow protocol, and the second target information is the routing configuration information of the network traffic monitored using the preset border gateway protocol, namely BGP protocol. It is understood that the first target information mentioned above is traffic characteristic data collected based on the NetFlow protocol, including but not limited to: the source IP address of the flow (e.g., 192.168.1.1), the destination IP address of the flow (e.g., 2001:db8::1), the total number of bytes of the flow in the interface inbound direction (e.g., 1,048,576 bytes), the total number of packets of the flow in the interface inbound direction (e.g., 1,000), the SRv6 segment routing information of the flow (e.g., inner destination IP: 2001:db8:1::1, segment list: [2001:db8:2::1, 2001:db8:3::1]), MPLS label (e.g., 24-bit binary label value: 0x006400), etc.; the second target information is routing configuration data collected based on the preset Border Gateway Protocol (BGP), including but not limited to: Prefix Segment Identifier (Prefix-SID), reachable routing information (AFI=2 (AFI, Address Family)). The default traffic monitoring protocol is NetFlow, which runs in the network device and can receive and send traffic data through port 9996 / UDP (User Datagram Protocol). The default border gateway protocol is BGP, which runs in the routing protocol module of the network device and establishes neighbor relationships through TCP port 179. It is used to exchange routing configuration information and supports the transmission of SRv6 / MPLS VPN related routing attributes such as Prefix-SID, AFI / SAFI, and EVPN NLRI.It is understood that the above Prefix-SID includes, but is not limited to, the following fields: SRv6 SID Value:2022:2022:1::1:0:4f, SRv6 SID Flags:0x00, SRv6 Endpoint Behavior:End.DT2U, etc., which together form a Prefix-SID attribute; and the above SID is specifically an IPv6 address.

[0032] Based on the above technical solution, it can be understood that the first target information in this embodiment also includes a target label, and the second target information also includes routing address information. The target label represents the target device's network traffic transmission based on Multiprotocol Label Switching (MPLS), and the routing address information is the address information of the target device when transmitting network traffic based on MPLS. The target label is a 32-bit binary identifier used to represent network traffic transmitted based on MPLS, encapsulated in a label stack between the Ethernet frame header and the IP header. Its specific format is: label value (20 bits) + experimental bits (3 bits) + time to live (8 bits) + bottom marker (1 bit), for example: 0x00000064. The routing address information is the routing information for network traffic transmitted based on MPLS, and may include: target next-hop information (e.g., 192.168.0.1, the forwarding next-hop IP of the MPLS route) and label information (the label value corresponding to the MPLS route), stored in the BGP routing attributes. In other words, the first target information in this embodiment also includes a target label used to characterize the network traffic transmission of the target device based on multi-protocol label switching technology, and the second target information also includes the routing address information of the target device when transmitting traffic based on MPLS. In this way, it can address the problem that the current system can only monitor MPLS traffic alone and cannot adapt to the mixed network scenario of SRv6 and MPLS, and realize the simultaneous collection of SRv6 and MPLS traffic data, effectively reducing the complexity of operation and maintenance.

[0033] Step S12: Match the segment routing information in the first target information with the prefix segment identifier in the second target information to obtain a first matching result; the segment routing information is routing information corresponding to the target Internet Protocol, and the target Internet Protocol is an Internet Protocol based on segment routing.

[0034] In this embodiment, as Figure 3As shown, matching the segment routing information in the first target information with the prefix segment identifier (Prefix-SID) in the second target information yields the first matching result. The segment routing information is the routing information corresponding to the target Internet Protocol (IP), which is an IIP based on segment routing. It can be understood that in this embodiment, the segment routing information is the routing identifier bound to the SRv6 protocol, encapsulated in the SRH (Segment Routing Header) following the IPv6 header. Specifically, it may include: the inner destination IP address (IPv6 format, such as 2001:db8:1::1), the segment list (IPv6 address sequence, such as [2001:db8:2::1, 2001:db8:3::1]), and the last segment element of the segment list (such as 2001:db8:3::1), used to identify the transmission path of the SRv6 traffic. The prefix segment identifier (Prefix-SID) is the unique identifier of the SRv6 route, in the format "IPv6 prefix + SID value", such as "2001:db8:1:: / 48". "Sid=100" means that the IPv6 prefix is ​​used to locate the network segment to which the route belongs, and the SID value (32-bit integer) is used to uniquely identify the SRv6 route corresponding to the network segment. The target Internet Protocol refers to the segment routing protocol SRv6 based on the IPv6 forwarding plane, which carries segment routing information through the SRH header to achieve path control and supports two working modes: BE (Best Effort) and TE Policy (Traffic Engineering). The first matching result mentioned above refers to the judgment result obtained by comparing the segment routing information in the first target information with the Prefix-SID in the second target information. For example, in a specific embodiment, the first matching result may include a successful match identifier (such as "Success") + the matched Prefix-SID + the corresponding SRv6 route information (such as 2001:db8:1:: / 48).

[0035] It should be noted that, before matching the segment routing information and the prefix segment identifier in this embodiment, a first information group can be constructed based on the prefix segment identifier and the target routing information in the second target information, and a second information group can be constructed based on the routing address information and the target routing information in the second target information. The target routing information is the routing information when the target device transmits network traffic based on a VPN. Correspondingly, the first information group is used to characterize the target device's network traffic transmission based on the target Internet Protocol, and the second information group is used to characterize the target device's network traffic transmission based on Multiprotocol Label Switching (MPLS). Furthermore, the aforementioned target routing information is the routing attribute information when network traffic is transmitted based on a VPN, including but not limited to: address family identifiers (AFI, e.g., 2 corresponds to IPv6), sub-address family identifiers (SAFI, e.g., 25 corresponds to L2 VPN, 128 corresponds to L3 VPN), and Ethernet VPN network layer reachability information (EVPN NLRI, e.g., MAC+IP advertising route: 00:11:22:33:44:55+2001:db8::1). This allows for pre-grouping of VPN routing information. For example, Prefix-SID and reachable routing information can be grouped together to represent SRv6 VPN routing information; target next-hop information, label information, and reachable routing information can be grouped together to represent MPLS VPN routing information. Therefore, in this embodiment, a first information group can be constructed based on the prefix segment identifier in the second target information and the target routing information, which can characterize that the target device transmits network traffic based on the target Internet Protocol SRv6. Furthermore, a second information group can be constructed based on the MPLS routing address information and the target routing information in the second target information, which can characterize that the target device transmits network traffic based on Multiprotocol Label Switching (MPLS). This achieves the classification and aggregation of routing configuration information. Addressing the problem of low matching efficiency when processing massive NetFlow data, pre-grouping reduces the data range for subsequent traffic matching from the entire routing information to the corresponding type of information group. Pre-grouping can reduce the amount of data for SRv6 or MPLS network traffic matching and improve processing efficiency.

[0036] In this embodiment, after matching the segment routing information in the first target information and the prefix segment identifier in the second target information to obtain the first matching result, the target label in the first target information and the routing address information in the second information group can also be matched to obtain the second matching result. Based on the second matching result, the second target network traffic corresponding to Multiprotocol Label Switching (MPLS) is determined from the network traffic. The aforementioned second matching result is the determination result obtained by comparing the target label in the first target information with the routing address information in the second information group. For example, it may include a successful matching indicator (such as "Success") + the matched label value (such as 0x00C800) + the corresponding MPLS routing information (next hop 192.168.0.1), or a failed matching indicator (such as "Fail") + the reason for failure (such as "label has no corresponding next hop"). In this way, after obtaining the first matching result, this embodiment further performs a matching operation between the target label in the first target information and the routing address information in the second information group to generate a second matching result. Then, it filters and determines the second target network traffic corresponding to Multiprotocol Label Switching from the overall network traffic. This can address the current problem that it is impossible to simultaneously identify SRv6 and MPLS traffic and that multiple tools are needed to process them separately. This solution can achieve unified identification of mixed traffic and accurately identify both SRv6 and MPLS traffic at the same time, which helps to reduce operation and maintenance costs and data integration difficulty.

[0037] Step S13: Based on the first matching result, determine the first target network traffic corresponding to the target Internet protocol from the network traffic to obtain the corresponding network traffic monitoring result.

[0038] In this embodiment, as shown... Figure 3 As shown, based on the first matching result, the first target network traffic corresponding to the target Internet Protocol is determined from the network traffic to obtain the corresponding network traffic monitoring results. Specifically, based on the "successful match" judgment in the first matching result, the first target network traffic corresponding to SRv6 can be filtered from the original network traffic to form basic network traffic monitoring results containing SRv6 traffic identifiers and basic traffic characteristic data. These results are then organized, such as by calculating the total bandwidth and total number of data packets of SRv6 traffic, and presented to the operation and maintenance terminal or third-party system in a visual form such as lists and charts, providing basic support for subsequent refined classification and multi-dimensional statistics.

[0039] Based on the above technical solution, this embodiment can monitor network traffic characteristic information when the target device transmits network traffic, and the traffic characteristic information includes segment routing information corresponding to the target Internet Protocol based on segment routing technology; at the same time, it monitors the routing configuration information of network traffic monitored using a preset border gateway protocol, and the routing configuration information includes a prefix segment identifier, and then matches the segment routing information in the first target information with the prefix segment identifier in the second target information to filter and determine the target network traffic corresponding to the target Internet Protocol. In view of the problem that the existing flow sampling system cannot identify and count SRv6 network traffic, the identification of SRv6 network traffic is realized through the collaboration of the preset traffic monitoring protocol NetFlow and the preset border gateway protocol BGP. It can accurately filter out the target network traffic corresponding to SRv6 from mixed network traffic, and there is no need for manual configuration of the matching process. The segment routing information and prefix segment identifier are automatically matched to avoid errors caused by manual operation and improve the efficiency of traffic analysis.

[0040] Example 2

[0041] Based on the above embodiments, such as Figure 4 As shown, this embodiment provides a specific method for network traffic monitoring, including: Step S21: Determine the target routing type of the first target network traffic based on the target routing information in the first information group; the target routing type is the routing type when the target device routes the first target network traffic based on the virtual private network.

[0042] In this embodiment, as Figure 3The association matching shown in this embodiment can be further subdivided into SRv6 and MPLS traffic. First, the target route type of the first target network traffic can be determined based on the target routing information in the first information group. This target route type is the routing type when the target device routes the first target network traffic based on a virtual private network. The aforementioned target route type, i.e., the routing classification of network traffic based on VPN transmission, can include: L2 VPN (Layer 2 Virtual Private Network) route (corresponding to SAFI=25) and L3 VPN (Layer 3 Virtual Private Network) route (corresponding to SAFI=128). It can be determined by parsing the AFI and SAFI fields in the target routing information, and is used to clarify the VPN service type in the monitoring results. Accordingly, in this embodiment, the target routing information includes an address family identifier, a sub-address family identifier, and network layer reachability information for the Ethernet Virtual Private Network (EVPN). The address family identifier (AFI) is a 16-bit integer used to identify the route address type; for example, 1 corresponds to the IPv4 address family, and 2 corresponds to the IPv6 address family. It is stored in the address family negotiation field of the BGP route and is used to distinguish the network layer protocol type corresponding to the route. The sub-address family identifier (SAFI) is an 8-bit integer used to identify the VPN type; for example, 25 corresponds to L2VPN, and 128 corresponds to L3VPN. It is stored in the sub-address family negotiation field of the BGP route and can be used in conjunction with the AFI to determine the VPN attributes of the route. The network layer reachability information for the Ethernet Virtual Private Network (EVPN NLRI) describes the specific attributes of the EVPN VPN route. Specific types include MAC+IP advertising routes, IP prefix advertising routes, etc., for example, "MAC=00:11:22:33:44:55, IP=2001:db8::1", used to convey reachability information within the VPN. In this way, for situations where it is currently impossible to accurately distinguish the specific type of traffic, the virtual private network (VPN) level corresponding to the traffic can be directly determined by the combined identifiers in the target routing information, and the accuracy of VPN level identification can be further improved by combining reachability information.

[0043] Furthermore, after determining the second target network traffic corresponding to Multiprotocol Label Switching (MPLS) based on the second matching result, the routing address information in the second information group and the target label in the first target information can be matched to obtain a third matching result. Based on the third matching result, the target route type of the second target network traffic is determined, and then the corresponding network traffic monitoring result is constructed based on the target route type of the second target network traffic. The third matching result is the judgment result obtained after a secondary comparison between the routing address information in the second information group and the target label in the first target information. For example, a successful match indicator (e.g., "Success") + the corresponding target route type (e.g., "MPLS L3 VPN"), or a failed match indicator (e.g., "Fail") + the reason for failure (e.g., "routing address information and label do not match"), is used to verify the VPN type of the MPLS traffic. Figure 5 As shown, MPLS network traffic also has corresponding VPN classifications. After determining the second target network traffic, a secondary matching can be performed between the routing address information in the second information group and the target label in the first target information to verify the correlation between the MPLS label and the routing type in the routing address information. This allows the determination of the target routing type corresponding to the second target network traffic. The target routing type of MPLS traffic can be integrated into the monitoring results to form further refined monitoring results. To address the current problem of inaccurate identification of MPLS traffic types, MPLS traffic can be further subdivided, which helps to achieve comprehensive monitoring of mixed traffic and meet the operation and maintenance needs of mixed networks.

[0044] Step S22: Construct corresponding network traffic monitoring results based on the target routing type of the first target network traffic.

[0045] In this embodiment, as Figure 3 As shown, corresponding network traffic monitoring results can be constructed based on the target routing type of the first target network traffic. In this way, after identifying the first target network traffic from the network traffic, the target routing type corresponding to the first target network traffic is determined based on the target routing information contained in the first information group. That is, the hierarchical type at which the target device routes the first target network traffic based on the virtual private network, and the determined target routing type is integrated into the monitoring results of the first target network traffic. This results in refined monitoring results. Addressing the current problem of not being able to further subdivide the corresponding hierarchical level after identifying network traffic, this allows for refined classification of SRv6, meeting the operator's needs for refined management of SRv6 services, improving the dimensions of monitoring results, and further enhancing operational efficiency.

[0046] Furthermore, after determining the first target network traffic corresponding to the target Internet Protocol based on the first matching result, the segment list information in the segment routing information can also be determined. This segment list information is the transmission path information when the first target network traffic is transmitted. Then, based on the segment list information, the target operating mode corresponding to the first target network traffic is determined, and the network traffic monitoring result corresponding to the first target network traffic is constructed based on the target operating mode. The aforementioned target operating mode is the protocol operating mode when the target device transmits the first target network traffic based on the target Internet Protocol, which is the transmission mode of SRv6 traffic, including BE and TE Policy. It can be determined through the configuration attributes of the segment list, such as whether it contains the TEPolicy identifier. The aforementioned segment list information is the transmission path sequence contained in the SRv6 segment routing information, consisting of one or more IPv6 addresses, for example [2001:db8:2::1, 2001:db8:3::1]. Each IPv6 address corresponds to an SRv6 node, which is used to identify the forwarding path of SRv6 traffic and to distinguish between BE and TE Policy modes. In this way, after determining the first target network traffic, segment list information representing the path sequence of SRv6 traffic transmission is extracted from the segment routing information of the first target information. Based on the configuration attributes of the above segment list information, the SRv6 protocol working mode corresponding to the first target network traffic is determined. Then, the determined target working mode is integrated into the monitoring results of the first target network traffic to further form a complete monitoring result of SRv6 traffic. In view of the current problem that the working mode of SRv6 traffic cannot be distinguished, resulting in the inability to focus on monitoring target services, the segment list and the last segment element of the segment list can be used to identify SRv6 BE and SRv6 TE Policy network traffic, which can further classify SRv6 network traffic, thereby realizing fine-grained monitoring and management of SRv6 network traffic and enabling rapid response to high-value services.

[0047] Based on the above technical solutions, such as Figure 5As shown, this embodiment first obtains network traffic from the network device via the NetFlow protocol, and simultaneously obtains VPN routing information from the network device via the BGP protocol. Then, it receives the network traffic and VPN routing information, maps the SRv6 segment routing information in the network traffic to the Prefix-SID in the VPN routing information, and obtains VPN type information through the reachable routing information in the VPN routing information. It then outputs a fine-grained classification result of the SRv6 network traffic, including SRv6 L2 VPN network traffic and SRv6 L3 VPN network traffic. Based on the classification result, it performs multi-dimensional statistics and generates statistical reports based on the network traffic. Furthermore, to achieve further subdivision of traffic types, since the SRv6 segment routing information of the flow in this embodiment includes the inner destination IP address of the flow, the segment list, and the last segment element of the segment list, the SRv6 network traffic can be further subdivided into SRv6 BE network traffic and SRv6 TE Policy network traffic based on the segment list information. Simultaneously considering the underlying MPLS traffic within the mixed network traffic, the destination IP address, MPLS label, and target next-hop and label information of the network traffic flow can be mapped to output the VPN classification results of the MPLS network traffic. These classification results include MPLS L2 VPN network traffic and MPLS L3 VPN network traffic. In other words, this embodiment can map the SRv6 segment routing information in the network traffic to the Prefix-SID in the VPN routing information, and obtain VPN type information through the AFI and SAFI in the VPN routing information. This enables the identification of different VPN types in SRv6 network traffic without manual intervention, allowing for fine-grained monitoring and management of SRv6 network traffic. It solves the inefficiency and latency problem caused by relying on manual configuration for identification, thereby achieving rapid response to high-value services. Furthermore, it can obtain MPLS labels through the NetFlow protocol and target next-hop and label information through the BGP protocol, increasing the VPN classification processing of MPLS network traffic and expanding the scope of fine-grained service analysis, better meeting users' network monitoring and management needs.

[0048] In one specific embodiment, the technical solution in this embodiment can be deployed and implemented through servers within the company's campus. The network adopts an "SRv6+MPLS hybrid architecture". A high-performance server is deployed in the data center within the campus, and the traffic analysis system in this embodiment is configured. First, the server connects to the campus switch, mirroring all campus traffic (including SRv6 and MPLS traffic) to the server's network interface card (NIC). Then, the server uses the NetFlow protocol to collect SRv6 and MPLS characteristics of the mirrored traffic, such as segment lists ([2001:db8:core::1, 2001:db8:factory::1]), segment list tail elements, MPLS labels, destination IP (192.168.10.20), etc. Simultaneously, it obtains VPN routing information from the core router via the BGP protocol: Prefix-SID (2001:db8:prod:: / 48 Sid=200), AFI=2, SAFI=128 (L3 VPN), EVPN NLRI, destination next hop (192.168.0.1), label information (24-bit label), SAFI=25 (L2 VPN), etc. Then, it pre-groups the routing information obtained from BGP. Group 1 (SRv6 VPN): Prefix-SID + AFI / SAFI (2 / 128) + EVPN NLRI; Packet 2 (MPLS VPN): Destination next hop (192.168.0.1) + Label (24-bit label) + SAFI=25. Then, SRv6 traffic matching can be performed. The "segment list tail element (2001:db8:factory::1)" collected by NetFlow is associated with the Prefix-SID of Packet 1 (2001:db8:prod:: / 48 Sid=200). SAFI=128 identifies it as "SRv6 L3 VPN traffic," and the absence of a TE Policy identifier in the segment list determines it as "SRv6 BE L3 VPN traffic." Similarly, MPLS traffic matching is performed. The "MPLS label + destination IP (192.168.10.20)" collected by NetFlow is associated with the "label + destination next hop" of Packet 2. SAFI=25 identifies it as "MPLS L2 VPN traffic." Once matching is complete, the server can perform statistics on the categorized traffic, including business dimensions such as total bandwidth of SRv6 TE Policy traffic today (10GB), packet loss rate, and latency; and time dimensions such as peak SRv6 BE traffic of 3GB between 8-9 AM. Reports are then generated and pushed to the campus operations and maintenance visualization platform, allowing operations personnel to check for any abnormal transmissions of SRv6 TE Policy traffic. This enables accurate differentiation of network traffic, preventing low-value services from consuming bandwidth intended for high-value services and improving network resource utilization.

[0049] Example 3

[0050] Based on the above embodiments, this embodiment also provides a network traffic monitoring device, including: The data information acquisition module 11 is used to monitor first target information and second target information when the target device transmits network traffic; the first target information is the traffic characteristic information of the network traffic monitored by a preset traffic monitoring protocol, and the second target information is the routing configuration information of the network traffic monitored by a preset border gateway protocol. The information matching module 12 is used to match the segment routing information in the first target information and the prefix segment identifier in the second target information to obtain a first matching result; the segment routing information is routing information corresponding to the target Internet Protocol, and the target Internet Protocol is an Internet Protocol based on segment routing; based on the first matching result, the first target network traffic corresponding to the target Internet Protocol is determined from the network traffic to obtain the corresponding network traffic monitoring result.

[0051] Specifically, such as Figure 6 As shown, the aforementioned information matching module 12 may specifically include a data information association module 121 for obtaining VPN classification results of SRv6 network traffic; a data information statistics module 122 for performing multi-dimensional statistics on network traffic; and a statistics result display module 123 for displaying the statistics results. This enables refined monitoring and management of SRv6 network traffic, solves the inefficiency and latency problems caused by relying on manual configuration management, and achieves rapid response for high-value services.

[0052] For a description of the features in the embodiments of the network traffic monitoring device described above, please refer to the relevant descriptions in the embodiments of the network traffic monitoring method described above, which will not be repeated here.

[0053] Furthermore, embodiments of this application also disclose an electronic device, Figure 7 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application.

[0054] Figure 7 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. Specifically, the electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the network traffic monitoring method disclosed in any of the foregoing embodiments. Furthermore, the electronic device 20 in this embodiment may specifically be a computer.

[0055] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0056] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored thereon can include operating system 221, computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0057] The operating system 221 is used to manage and control the various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program capable of performing the network traffic monitoring method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include a computer program capable of performing other specific tasks.

[0058] In addition, this application also provides a computer-readable storage medium storing computer instructions that, when executed on a computer, cause the methods in the various method embodiments of this application to be performed.

[0059] This application also provides a computer program product, which includes computer program code or instructions, such that when the computer program code or instructions are run on a computer, the methods in the various method embodiments of this application are executed.

[0060] Furthermore, this application also provides a chip including a processor. A memory for storing a computer program is provided independently of the chip, and the processor is used to execute the computer program stored in the memory to perform the methods in the various method embodiments of this application.

[0061] Furthermore, the chip may also include a communication interface. The communication interface may be an input / output interface or an interface circuit, etc. Furthermore, the chip may also include a memory.

[0062] It should be understood that the processor in the embodiments of this application can be an integrated circuit chip with the ability to process signals. In implementation, each step of the above method embodiments can be completed by the integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware encoding processor, or implemented by a combination of hardware and software modules in the encoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0063] The memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), and synchronous link dynamic memory (SLDRAM).

[0064] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory can be integrated into the processor.

[0065] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0066] The foregoing preferred embodiments have further illustrated the objectives, technical solutions, and advantages of the present invention. It should be understood that the above descriptions are merely preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for monitoring network traffic, characterized in that, include: First and second target information when monitoring network traffic transmitted by target devices; The first target information is the traffic characteristic information of the network traffic monitored using a preset traffic monitoring protocol, and the second target information is the routing configuration information of the network traffic monitored using a preset border gateway protocol. A first matching result is obtained by matching the segment routing information in the first target information with the prefix segment identifier in the second target information, and a second matching result is obtained by matching the target label in the first target information with the routing address information in the second target information; the segment routing information is routing information corresponding to the target Internet Protocol, and the segment routing information is encapsulated in the segmented routing header, including the inner destination IP address, the segment list, and the last segment element of the segment list; the target Internet Protocol is an Internet Protocol based on segment routing, and the prefix segment identifier is a unique identifier for the segment route; Based on the first matching result, a first target network traffic corresponding to the target Internet Protocol is determined from the network traffic, and based on the second matching result, a second target network traffic corresponding to Multiprotocol Label Switching is determined from the network traffic; Determine the segment list information corresponding to the first target network traffic, determine the protocol working mode corresponding to the first target network traffic based on the segment list information, and construct network traffic monitoring results based on the protocol working mode; The segment list information is the address sequence in the segment routing information encapsulated in the segment routing header.

2. The network traffic monitoring method according to claim 1, characterized in that, The first target information also includes a target label, and the second target information also includes routing address information; The target label represents the target device transmitting network traffic based on multiprotocol label switching, and the routing address information is the address information of the target device when transmitting network traffic based on multiprotocol label switching.

3. The network traffic monitoring method according to claim 2, characterized in that, After monitoring the first target information and the second target information, and before matching the segment routing information in the first target information and the prefix segment identifier in the second target information, the method further includes: A first information group is constructed based on the prefix segment identifier and target routing information in the second target information; the target routing information is the routing information when the target device transmits network traffic based on a virtual private network. A second information group is constructed based on the routing address information and the target routing information in the second target information; The first information group is used to characterize the target device transmitting network traffic based on the target Internet Protocol, and the second information group is used to characterize the target device transmitting network traffic based on the Multiprotocol Label Switching.

4. The network traffic monitoring method according to claim 3, characterized in that, The target routing information includes address family identifiers, sub-address family identifiers, and network layer reachability information for the Ethernet virtual private network.

5. The network traffic monitoring method according to claim 3 or 4, characterized in that, After determining the first target network traffic corresponding to the target Internet Protocol from the network traffic based on the first matching result, the method further includes: The target routing type of the first target network traffic is determined based on the target routing information in the first information group; the target routing type is the routing type when the target device routes the first target network traffic based on the virtual private network. The corresponding network traffic monitoring results are constructed based on the target routing type of the first target network traffic.

6. The network traffic monitoring method according to claim 5, characterized in that, After matching the segment routing information in the first target information with the prefix segment identifier in the second target information to obtain the first matching result, the method further includes: The target label in the first target information and the routing address information in the second information group are matched to obtain a second matching result; Based on the second matching result, a second target network traffic corresponding to the Multiprotocol Label Switching is determined from the network traffic.

7. The network traffic monitoring method according to claim 6, characterized in that, After determining the second target network traffic corresponding to the Multiprotocol Label Switching from the network traffic based on the second matching result, the method further includes: A third matching result is obtained by matching the routing address information in the second information group with the target label in the first target information; The target route type of the second target network traffic is determined based on the third matching result; Based on the target routing type of the second target network traffic, a corresponding network traffic monitoring result is constructed.

8. The network traffic monitoring method according to claim 1, characterized in that, After determining the first target network traffic corresponding to the target Internet Protocol from the network traffic based on the first matching result, the method further includes: Determine the segment list information in the segment routing information; the segment list information is the transmission path information when the first target network traffic is transmitted. The target operating mode corresponding to the first target network traffic is determined based on the segment list information; the target operating mode is the protocol operating mode when the target device transmits the first target network traffic based on the target Internet protocol; Based on the target operating mode, construct the network traffic monitoring results corresponding to the first target network traffic.

9. A network traffic monitoring device, characterized in that, include: The data information acquisition module is used to monitor the first target information and the second target information when the target device transmits network traffic. The first target information is the traffic characteristic information of the network traffic monitored using a preset traffic monitoring protocol, and the second target information is the routing configuration information of the network traffic monitored using a preset border gateway protocol. The information matching module is used to match the segment routing information in the first target information with the prefix segment identifier in the second target information to obtain a first matching result, and to match the target label in the first target information with the routing address information in the second target information to obtain a second matching result; the segment routing information is routing information corresponding to the target Internet Protocol, and the segment routing information is encapsulated in the segmented routing header, including the inner destination IP address, the segment list, and the last segment element of the segment list; the target Internet Protocol is an Internet Protocol based on segment routing, and the prefix segment identifier is a unique identifier for the segment routing; Furthermore, based on the first matching result, a first target network traffic corresponding to the target Internet Protocol is determined from the network traffic, and based on the second matching result, a second target network traffic corresponding to Multiprotocol Label Switching is determined from the network traffic; Determine the segment list information corresponding to the first target network traffic, determine the protocol working mode corresponding to the first target network traffic based on the segment list information, and construct network traffic monitoring results based on the protocol working mode; The segment list information is the address sequence in the segment routing information encapsulated in the segment routing header.

10. An electronic device, characterized in that, The electronic device includes a processor and a memory; wherein the memory is used to store a computer program, which is loaded and executed by the processor to implement the network traffic monitoring method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, Used to store a computer program, which, when executed by a processor, implements the network traffic monitoring method as described in any one of claims 1 to 8.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the network traffic monitoring method as described in any one of claims 1 to 8.

Citation Information

Patent Citations

  • Route anomaly detection method and device of autonomous system and electronic equipment

    CN121056217A