Methods, apparatus and electronic equipment for determining service paths based on flow detection
By using flow detection technology, service flow data from network devices is acquired and sorted. Combined with LLDP information, service paths are determined, solving the problem that traditional tools cannot accurately reconstruct service paths in complex network environments. This enables precise tracking and analysis of network management.
Patent Information
- Application Number
- CN202510183852.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2025-02-19
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2045-02-19
AI Technical Summary
In modern network communication, traditional network management and monitoring tools struggle to accurately reconstruct business paths in complex network environments.
By using flow detection technology, the service flow data of each target device is obtained. By using flow node identifier, timestamp, flow direction and interface information, combined with LLDP information, the interface order and connection of multiple transmission devices corresponding to each service flow are determined, so as to accurately restore the service path.
It can accurately reproduce a single service path in complex network environments, improve network management, and ensure service quality.
Smart Images

Figure CN120034481B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the technical field of network communication, and in particular to a method, apparatus, and electronic device for determining service paths based on flow detection. Background Technology
[0002] In the field of modern network communication, with the rapid development of the Internet and the diversification of network applications, network structures have become exceptionally complex. Enterprises and service providers are constantly implementing multi-layered, multi-protocol network architectures to provide more stable and efficient network services. This network environment makes business paths—the routing of data from the sender to the receiver—difficult to trace and analyze. Traditional network management and monitoring tools typically only provide static network topology information, making it difficult for existing technologies to meet the demand for accurate reconstruction of business paths in the current network environment. Summary of the Invention
[0003] The purpose of this invention is to provide a method, apparatus, and electronic device for determining service paths based on flow detection, so as to accurately reconstruct a single service path from complex network traffic.
[0004] This invention provides a method for determining service paths based on flow detection, the method comprising:
[0005] Acquire the flow detection data of at least one service flow corresponding to each target device; wherein each target device is pre-configured with the flow detection function;
[0006] Based on each flow detection data, multiple transmission devices corresponding to each service flow are determined from multiple target devices; wherein, each flow detection data includes: flow node identification information, timestamp information, flow direction information, and interface information;
[0007] Based on the flow node identifier, timestamp, flow direction, and interface information of each flow detection data, as well as the LLDP information pre-configured for each transmission device, the interfaces of multiple transmission devices corresponding to each service flow are sorted and connected to determine the service path corresponding to each service flow; wherein, the LLDP information pre-configured for each transmission device is used to indicate the target transmission device connected to the transmission device and the interface information of the target transmission device.
[0008] Furthermore, the step of obtaining follow-up detection data for at least one service flow corresponding to each target device includes:
[0009] Obtain the configuration message of the first device; the first device is a disabled device.
[0010] Each configuration message is sent to the corresponding first device via NETCONF to perform global configuration for flow detection on each first device, resulting in a target device list; the target device list includes multiple target devices configured with flow detection function;
[0011] Based on at least one pre-configured flow detection task, the source device corresponding to each flow detection task is determined from multiple target devices; wherein, each flow detection task corresponds to a service flow; the flow detection task includes reporting configuration information;
[0012] Each follow-up detection task is sent to the corresponding source device, and follow-up detection data of at least one service flow reported to the acquisition machine by each target device according to the reporting configuration information is obtained.
[0013] Furthermore, each flow-following detection data also includes: flow identifier information and period ID information; the steps for determining multiple transmission devices corresponding to each service flow from multiple target devices based on each flow-following detection data include:
[0014] The target devices corresponding to the flow detection data with the same flow identifier information and period ID information are grouped together to obtain at least one grouping result corresponding to the flow identifier information. Each grouping result includes multiple transmission devices corresponding to the flow identifier information.
[0015] Furthermore, based on the flow node identifier information, timestamp information, flow direction information, interface information of each flow-following detection data, and the LLDP information pre-configured for each transmission device, the steps of sorting and connecting the interfaces of multiple transmission devices corresponding to each service flow to determine the service path corresponding to each service flow include:
[0016] For each service flow, based on the flow node identification information, flow direction information, and interface information in the flow detection data corresponding to the service flow, the source device, terminal device, inbound and outbound interfaces of the source device, and inbound and outbound interfaces of the terminal device are determined from multiple transmission devices corresponding to the service flow.
[0017] If there are two transmission devices corresponding to the service flow, the inbound interface of the source device, the outbound interface of the source device, the inbound interface of the terminal device, and the outbound interface of the terminal device are connected in sequence according to the pre-set first connection order to obtain the service path corresponding to the service flow.
[0018] Furthermore, the methods also include:
[0019] If the number of transmission devices corresponding to the service flow is greater than two, the intermediate device corresponding to the service flow is determined based on the source device, terminal device, and multiple transmission devices corresponding to the service flow; wherein, the intermediate device is any device other than the source device and terminal device among the multiple transmission devices.
[0020] Based on the flow node identifier information, timestamp information, flow direction information, and interface information in the target flow detection data of the service flow corresponding to the intermediate device, the interfaces of the intermediate device corresponding to the service flow are sorted and connected in ascending order of timestamp to obtain the first intermediate path corresponding to the service flow.
[0021] Based on the LLDP information of the intermediate devices obtained in advance, the second intermediate path corresponding to the service flow is obtained;
[0022] If the first intermediate path is the same as the second intermediate path, the first intermediate path is determined as the target intermediate path; if the first intermediate path is different from the second intermediate path, the second intermediate path is determined as the target intermediate path.
[0023] Based on the target intermediate path, the inbound and outbound interfaces of the source device, and the inbound and outbound interfaces of the terminal device, the service path corresponding to the service flow is determined.
[0024] Furthermore, based on the target intermediate path, the inbound and outbound interfaces of the source device, and the inbound and outbound interfaces of the terminal device, the steps to determine the service path corresponding to this service flow include:
[0025] If the target intermediate path is the first intermediate path, connect the inbound interface of the source device, the outbound interface of the source device, and the inbound interface of the first intermediate device in sequence; then connect the outbound interface of the second intermediate device, the inbound interface of the terminal device, and the outbound interface of the terminal device in sequence to obtain the service path corresponding to the service flow; wherein, the inbound interface of the first intermediate device is the interface indicated by the interface information corresponding to the first target flow detection data with the smallest timestamp in the target flow detection data of the service flow corresponding to the intermediate device; the outbound interface of the second intermediate device is the interface indicated by the interface information corresponding to the second target flow detection data with the largest timestamp in the target flow detection data of the service flow corresponding to the intermediate device.
[0026] If the target intermediate path is the second intermediate path, the inbound interface of the third intermediate device to be connected to the source device is determined based on the LLDP information of the source device obtained in advance; the outbound interface of the fourth intermediate device to be connected to the terminal device is determined based on the LLDP information of the terminal device obtained in advance.
[0027] The service path corresponding to the service flow is obtained by sequentially connecting the inbound interface of the source device, the outbound interface of the source device, and the inbound interface of the third intermediate device; then sequentially connecting the outbound interface of the fourth intermediate device, the inbound interface of the terminal device, and the outbound interface of the terminal device. The inbound interface of the third intermediate device is the interface indicated by the interface information of the target transmission device corresponding to the LLDP information of the source device; the outbound interface of the fourth intermediate device is the interface indicated by the interface information of the target transmission device corresponding to the LLDP information of the terminal device.
[0028] Furthermore, each stream-following detection data set also includes message count information; each stream-following detection task also includes business source information and customer information; the method also includes:
[0029] The flow detection data of each service flow is restored to the corresponding transmission device on the service path in real time;
[0030] Based on the packet count, timestamp, and interface information corresponding to each flow detection data, the status information of the transmission path between every two adjacent transmission devices in the service path corresponding to each service flow is determined in real time; the status information includes latency information, packet loss information, and jitter information; the status information is presented in a timeline format.
[0031] Based on the status information of the transmission path between every two adjacent transmission devices and the pre-set status information threshold, abnormal transmission paths are determined in real time, and abnormal interfaces are determined based on the abnormal transmission paths.
[0032] Based on the status information of the transmission path between every two adjacent transmission devices, determine the average status information of the service path corresponding to each service flow;
[0033] Based on the average value of the business source information, customer information and the status information of the business path corresponding to each business flow, the average business information corresponding to each customer information and each business source information is obtained.
[0034] Based on the average business information corresponding to each customer information and each business source information, the customer information and business source information are sorted according to multiple preset sorting requirements to obtain the customer sorting result and business source sorting result corresponding to each sorting requirement.
[0035] This invention provides a service path determination device based on flow detection, the device comprising:
[0036] The acquisition module is used to acquire the follow-up detection data of at least one service flow corresponding to each target device; wherein, each target device is pre-configured with the follow-up detection function;
[0037] The first determining module is used to determine multiple transmission devices corresponding to each service flow from multiple target devices based on each flow detection data; wherein each flow detection data includes: flow node identification information, timestamp information, flow direction information, and interface information;
[0038] The second determining module is used to sort and connect the interfaces of multiple transmission devices corresponding to each service flow based on the flow node identification information, timestamp information, flow direction information, interface information of each flow detection data, and the LLDP information pre-configured by each transmission device, so as to determine the service path corresponding to each service flow; wherein, the LLDP information pre-configured by each transmission device is used to indicate the target transmission device connected to the transmission device and the interface information of the target transmission device.
[0039] The present invention provides an electronic device, which includes a processor and a memory. The memory stores computer-executable instructions that can be executed by the processor. The processor executes the computer-executable instructions to implement the above-mentioned method for determining a service path based on flow detection.
[0040] The present invention provides a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are invoked and executed by a processor, the computer-executable instructions cause the processor to implement any of the above-mentioned methods for determining service paths based on flow detection.
[0041] The present invention provides a method, apparatus, and electronic device for determining service paths based on flow detection. The method includes: acquiring flow detection data for at least one service flow corresponding to each target device; wherein each target device is pre-configured with flow detection functionality; determining multiple transmission devices corresponding to each service flow from multiple target devices based on each flow detection data; and sorting and connecting the interfaces of the multiple transmission devices corresponding to each service flow based on the flow node identifier information, timestamp information, flow direction information, interface information, and LLDP information pre-configured for each transmission device of each flow detection data, to determine the service path corresponding to each service flow. In this method, service path reconstruction based on flow detection can accurately reconstruct a single service path from complex network traffic, thereby solving the problem that traditional network monitoring methods cannot accurately reconstruct service paths in complex network environments. Attached Figure Description
[0042] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.
[0043] Figure 1 A flowchart illustrating a method for determining a service path based on flow detection, provided in an embodiment of the present invention;
[0044] Figure 2 A flowchart of another method for determining a service path based on flow detection provided in an embodiment of the present invention;
[0045] Figure 3 This is a schematic diagram illustrating the configuration of a flow detection task according to an embodiment of the present invention;
[0046] Figure 4 This is a schematic diagram of flow-fed detection data provided in an embodiment of the present invention;
[0047] Figure 5 A schematic diagram of a visualized business topology provided in an embodiment of the present invention;
[0048] Figure 6 This is another visualized business topology diagram provided in an embodiment of the present invention;
[0049] Figure 7 A schematic diagram of a service path determination device based on flow detection provided in an embodiment of the present invention;
[0050] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation
[0051] The technical solutions of the present invention have been clearly and completely described in conjunction with the embodiments. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0052] In the field of modern network communication, with the rapid development of the Internet and the diversification of network applications, network structures have become exceptionally complex. Enterprises and service providers are constantly implementing multi-layered, multi-protocol network architectures to provide more stable and efficient network services. This network environment makes business paths—the routes of data from sender to receiver—difficult to trace and analyze. Traditional network management and monitoring tools, such as Simple Network Management Protocol (SNMP) and Network Monitoring Systems (NMS), typically only provide static network topology information and cannot track dynamically changing business flows in real time. Therefore, accurately reconstructing a single business path from complex network traffic remains a technical challenge.
[0053] In summary, existing technologies are insufficient to meet the demands for accurate tracking and restoration of service paths in today's network environment. Therefore, developing a method that can effectively address complex network environments and accurately reconstruct service paths is of significant practical importance for improving network management and ensuring service quality.
[0054] Based on this, the present invention provides a method, apparatus and electronic device for determining service paths based on flow detection, which can accurately reconstruct service paths from complex network environments through flow detection technology.
[0055] To facilitate understanding of this embodiment, a method for determining a service path based on flow detection, as disclosed in this embodiment of the invention, will first be described in detail; such as Figure 1 As shown, the method includes the following steps:
[0056] Step S102: Obtain the flow detection data of at least one service flow corresponding to each target device; wherein each target device is pre-configured with the flow detection function.
[0057] Flow-based detection can be understood as a network traffic monitoring technology that can identify and track specific traffic in the network based on packet header information.
[0058] A service path refers to the routing path in a network from the source to the destination for transmitting specific service or application data.
[0059] In the specific implementation process, the follow-up detection data of a specific service flow detected by each target device can be obtained. This specific service flow can be one or multiple, and can be set according to actual needs.
[0060] Step S104: Based on each flow detection data, determine multiple transmission devices corresponding to each service flow from multiple target devices; wherein each flow detection data includes: flow node identification information, timestamp information, flow direction information, and interface information.
[0061] In practice, the transmission device corresponding to each service flow is actually the target device through which the service flow passes when transmitting specific service or application data in the network. It should be noted that there are multiple transmission devices corresponding to each service flow, because each service flow passes through at least two target devices when transmitting specific service or application data in the network.
[0062] In the specific implementation process, each target device may detect the following detection data of one service flow or multiple service flows; therefore, each target device may correspond to one following detection data or multiple following detection data. Based on the one or more following detection data corresponding to each target device, the target devices (i.e., multiple transmission devices corresponding to each service flow) that each service flow passes through when transmitting specific service or application data in the network can be determined from multiple target devices.
[0063] Step S106: Based on the flow node identifier information, timestamp information, flow direction information, interface information, and LLDP information pre-configured for each flow detection data, sort and connect the interfaces of multiple transmission devices corresponding to each service flow to determine the service path corresponding to each service flow; wherein, the LLDP information of each transmission device is used to indicate the target transmission device connected to the transmission device and the interface information of the target transmission device.
[0064] In actual implementation, each flow detection data can include: flow node identification information, timestamp information, flow direction information, and interface information.
[0065] The aforementioned stream node identification information can be understood as the identification information of the target device corresponding to the currently acquired stream detection data;
[0066] The flow direction information mentioned above can be any one of Ingress (starting direction), Trans Input (incoming direction), TransOutput (outgoing direction), and Egress (ending direction);
[0067] The timestamp information mentioned above can be understood as the time point at which the target device corresponding to the currently acquired follow-up detection data acquired the follow-up detection data.
[0068] The aforementioned interface information can be the inbound or outbound interface name of the target device corresponding to the currently acquired flow detection data.
[0069] LLDP (Link Layer Discovery Protocol) is a data link layer protocol that allows network devices to notify other devices of their own status by sending LLDP messages within the local network.
[0070] In the specific implementation process, after determining the multiple transmission devices corresponding to each service flow from multiple target devices, the LLDP information of each transmission device can be obtained in advance. The LLDP information is used to indicate the target transmission device (i.e., neighboring device) connected to the transmission device and the interface information of the target transmission device (such as interface name, type, etc.).
[0071] Then, by combining the flow node identification information, timestamp information, flow direction information, and interface information of the flow detection data of the service flow corresponding to each transmission device, as well as the LLDP information corresponding to each transmission device, the interfaces of multiple transmission devices corresponding to each service flow are sorted (that is, the arrival and departure order of each service flow on the corresponding multiple transmission devices is determined), and the interfaces of multiple transmission devices are connected according to the sorting to obtain the service path corresponding to each service flow.
[0072] Flow tracking, as an emerging network traffic monitoring method, can identify specific service flows based on packet header information. Through real-time analysis of data packets, flow tracking can provide information such as the source / destination address, port number, and protocol type of the service flow. This technology has the ability to trace the path of a service flow and is key to reconstructing the service path.
[0073] The present invention provides a method for determining service paths based on flow detection. The method includes: acquiring flow detection data for at least one service flow corresponding to each target device; wherein each target device is pre-configured with flow detection functionality; determining multiple transmission devices corresponding to each service flow from multiple target devices based on each flow detection data; and sorting and connecting the interfaces of the multiple transmission devices corresponding to each service flow based on the flow node identifier information, timestamp information, flow direction information, interface information, and LLDP information pre-configured for each transmission device of each flow detection data, so as to determine the service path corresponding to each service flow. In this method, service path reconstruction based on flow detection can accurately reconstruct a single service path from complex network traffic, thereby solving the problem that traditional network monitoring methods cannot accurately reconstruct service paths in complex network environments.
[0074] This invention also provides another method for determining service paths based on flow detection, which is implemented based on the methods described in the above embodiments; such as Figure 2 As shown, the method includes the following steps:
[0075] Step S202: Obtain the follow-up detection data of at least one service flow corresponding to each target device.
[0076] In the specific implementation process, the above step S202 can be achieved through the following steps one to four:
[0077] Step 1: Obtain the configuration message of the first device; the first device is an disabled device.
[0078] In actual implementation, the first device can be a device from the first device list. Specifically, a selected device list (equivalent to the first device list) can be obtained first. This selected device list includes disabled devices (equivalent to the aforementioned first device, i.e., devices that have not yet been configured with the flow detection function). The information presented in the selected device list includes the device name, device address, device manufacturer, device model, device type, and affiliation of each disabled device. Based on the device manufacturer of each disabled device, the configuration message corresponding to the manufacturer information of each disabled device can be obtained. Then, the configuration message corresponding to the manufacturer information of each disabled device can be determined as the configuration message for the corresponding disabled device (first device).
[0079] Step 2: Send each configuration message to the corresponding first device via NETCONF to perform global configuration for flow detection on each first device and obtain a target device list; the target device list includes multiple target devices configured with flow detection function.
[0080] Specifically, when retrieving the list of selected devices, you can select devices that support and require flow detection from the candidate device list using a header filter based on the network topology corresponding to the current network environment. Then, you can add devices from the candidate device list to the selected device list in batches using a shuttle box, or delete devices from the selected device list to the candidate device list. The devices displayed in the candidate device list are all disabled devices, meaning they haven't yet been configured with flow detection. The information displayed in the selected device list includes device name, device address, device manufacturer, device model, device type, and ownership. A reset operation is also supported; click "Reset" and then "OK" for secondary confirmation, clearing the selected device list and allowing you to add devices again.
[0081] The devices presented in the selected device list (i.e., each first device in the first device list) are actually devices that support and need to be detected by the flow. In actual implementation, batch enable configurations can be asynchronously distributed to all devices in the selected device list to obtain an enabled device list (equivalent to a target device list).
[0082] NETCONF (Network Configuration Protocol) provides a set of protocols for communication between network administrators and network devices. Network administrators can use the NETCONF protocol to distribute, modify, and delete configurations for remote devices.
[0083] NETCONF can obtain configuration messages for various vendors based on custom message template management functions, enabling configurable message delivery for newly added vendors. This transforms management information into a computer-understandable database, improving the computer's ability to process network management data and thus enhancing network management capabilities.
[0084] In the specific implementation process, based on the device manufacturer (i.e., manufacturer information, such as Huawei, ZTE, etc.) of each device in the selected device list, the configuration message of each manufacturer can be obtained through NETCONF configuration. Then, each configuration message is sent to the corresponding device in the selected device list through NETCONF, which means that the devices in the selected device list are enabled in batches. The global configuration of following the flow detection is sent through NETCONF to realize the ability to add and delete devices to enable following the flow detection. The devices (i.e., target devices) that have been sent the global configuration of following the flow detection are presented as an enabled device list (i.e., target device list). The information presented in the enabled device list includes device name, device address, device manufacturer, device model, device type, affiliation, and sending status.
[0085] Step 3: Based on at least one pre-configured flow detection task, determine the source device corresponding to each flow detection task from multiple target devices; wherein, each flow detection task corresponds to a service flow; the flow detection task includes reporting configuration information.
[0086] Specifically, it supports querying issued follow-up detection tasks. The query results are presented in list format. The information presented in the follow-up detection task list generally includes task name, source device name (i.e., the name of the source device), VPN instance name, measurement period, measurement type, latency detection switch, task creation time, and issuance status. It also supports viewing the task details and reported data corresponding to each task in the follow-up detection task list; task details can include task information, source network element, and flow information.
[0087] In actual implementation, it also supports adding new follow-up detection tasks. Specifically, it supports custom configuration or selection of existing service methods to configure follow-up detection tasks, and then the configured follow-up detection tasks can be sent to the corresponding source devices through NETCONF.
[0088] See also Figure 3The diagram illustrates the configuration of a flow-following detection task. The configuration includes five parts: selecting a network element, configuring the detection flow, binding the detection inflow port, configuring flow-following detection information, and configuring flow-following detection reporting. Specifically, selecting a network element includes the source device and instance name. The target of the flow-following detection task is the source device, i.e., the head node of the flow-following detection, and it supports selecting the source device from the enabled device list. The instance name refers to Huawei and ZTE instances, in string format, case-sensitive, without spaces, and with a length range of 1 to 31. Both ZTE and Huawei have an instance name attribute; that is, when the source device's manufacturer is Huawei or ZTE, its instance name is "instance". In actual implementation, the source device and instance name can be configured according to actual needs.
[0089] When configuring the detection flow, it supports customizing the business flow to be detected (i.e., the business flow corresponding to the flow detection task) by using information such as 5-tuples. In actual implementation, the following information can be configured according to actual needs:
[0090] (1) Source IP, destination IP; IPv4 address, string in dotted decimal notation; IPv6 address, hexadecimal string; empty represents Any: no address specified;
[0091] (2) Source port, destination port;
[0092] (3) IP address type; supports IPv4 and IPv6 addresses;
[0093] (4) Protocol number, differential service code (dscp);
[0094] (5) VRF / VPN name; Huawei VPN name, ZTE VRF name.
[0095] It should be noted that when configuring the detection flow, it is also possible to select a defined service from the SDN controller as the target flow for the flow detection, that is, the service flow to be detected. Specifically, the information presented in the list of candidate services includes the service name, deployment city, customer name, IPv4 address range, and IPv6 address range; select a defined service in the list of candidate services, and generate the parameter information corresponding to (1)-(5) above based on the service information of the selected service and fill it back into the custom form.
[0096] When binding an incoming port for detection, the system supports selecting the target incoming port for binding, and can filter by port name and address. Specifically, ordinary sub-interfaces are deployed using VRF and the main interface; aggregated interfaces are bound to the main interface according to the Trunk logic; sub-interfaces are usually bound to their respective main interfaces; if the bound interface is a sub-interface, the device needs to convert the bound interface to the main interface based on the sub-interface name and then issue the binding on the main interface.
[0097] When configuring flow detection information, you can configure the following information according to your actual needs:
[0098] (1) Task name; (2) Measurement type, which can be end-to-end e2e or hop-by-hop trace; (3) Measurement period, which is usually 10s, 30s or 60s; (4) Delay detection switch, which can be on or off.
[0099] When configuring streaming detection and reporting, you can configure the following information according to your actual needs:
[0100] (1) Telemetry (which can be understood as a technology for remotely acquiring data at high speed from physical or virtual devices) subscription, including enabling and disabling;
[0101] (2) Telemetry acquisition machine IP: Supports IPv4 and IPv6;
[0102] (3) Telemetry acquisition machine listening port: Default 10100;
[0103] (4) Sampling period: 30s or 60s.
[0104] In practice, the system also supports deleting streaming detection tasks. Specifically, you can select the task and its configuration to delete from the streaming detection task list, and batch deletion is supported. Click "Delete" for secondary confirmation, and the result will be returned after successful deletion.
[0105] Step 4: Distribute each follow-up detection task to the corresponding source device, and obtain follow-up detection data of at least one service flow reported to the acquisition machine by each target device according to the reporting configuration information.
[0106] In the specific implementation process, after the following detection task is configured, one or more following detection tasks can be selected for distribution. Specifically, each following detection task corresponds to a target device (that is, the source device of the following detection task), and different following detection tasks can be distributed to the same target device.
[0107] After each configured flow detection task is sent to the corresponding source device, each target device can report the data of the business flow corresponding to each sent flow detection task (i.e., flow detection data) through the telemetry acquisition machine to the probe analyzer for real-time collection and analysis. It can also perform multi-instance collection and has independently implemented real-time collection and parsing of telemetry reporting data of measurement results from multiple vendors, including Huawei, ZTE, H3C and other vendors. It has also achieved a high availability and load balancing solution for collection instances.
[0108] In actual implementation, each target device can generate measurement results every period according to the statistical period (that is, the flow detection data of the service flow corresponding to each issued flow detection task). The generated measurement results are reported to the analyzer through the telemetry's GPB mode. Specifically, the reports can be made according to the detection period or the subscription period. The inbound and outbound interfaces of the target device usually generate a set of data respectively. That is, the flow detection data of any service flow detected by each target device includes two sets of data.
[0109] Deploying flow detection at critical network nodes is the foundation of this solution. The deployment strategy considers network topology, traffic distribution, and performance requirements to ensure that information on critical business flows is fully monitored, while avoiding unnecessary resource consumption and network interference. Flow detection functionality is configured and managed uniformly across different network equipment vendors to ensure accurate tracking and reporting of data flows.
[0110] Step S204: Based on each flow detection data, determine multiple transmission devices corresponding to each service flow from multiple target devices.
[0111] For details, please refer to, for example Figure 4 The diagram illustrates a flow detection data pattern. The flow detection data for any service flow detected by each target device includes FlowMonID (flow identifier, which can be understood as the identifier of the service flow corresponding to the currently acquired flow detection data), FlowNodeID (flow node identifier, i.e., the identifier of the target device that detected the current service flow's flow detection data), Period (period information, i.e., the statistical period, in seconds, typically 1s, 10s, 30s, 60s, 300s, etc.), PeriodID (period ID information, the number of seconds since 1970 to the start of the statistical period divided by Period; used to identify the same time period across the entire network), Direction (flow direction information, generally including Ingress, Trans Input, Trans Output, Egress), IfName (interface information, i.e., the interface name of the packet carried by the current service flow in the inbound or outbound direction; for trunk interfaces, reported according to trunk member ports), and timestamp information (composed of seconds and nanoseconds). Figure 4In the diagram, TimestampSecond represents the integer value of the second portion from 1970 to the time the delay measurement message is received, and TimestampNanoSecond represents the remaining nanosecond portion. This information is the basis for path reconstruction. In specific implementation, the target devices corresponding to the flow detection data with the same flow identification information and period ID information can be grouped together to obtain at least one grouping result corresponding to the flow identification information. Each grouping result includes multiple transmission devices corresponding to the flow identification information. That is, the flow information from different target devices can be associated through FlowMonID and period ID, because FlowMonID and period ID are the same for the detection of the same flow on different target devices.
[0112] Specifically, after obtaining the flow detection data corresponding to each target device, assuming that by comparison it is found that the FlowMonID of the flow detection data corresponding to target device A and target device B is both a and the period ID is both b, then target device A and target device B can be considered as two transmission devices corresponding to service flow a. That is, when service flow a is transmitted over the network, it passes through target device A and target device B. Target device A and target device B are both transmission devices in the service path corresponding to service flow a.
[0113] Step S206: Based on the flow node identifier information, timestamp information, flow direction information, interface information of each flow detection data, and the LLDP information pre-configured for each transmission device, sort and connect the interfaces of multiple transmission devices corresponding to each service flow to determine the service path corresponding to each service flow.
[0114] In the specific implementation process, the above step S206 can be achieved through the following steps five to eleven:
[0115] Step 5: For each service flow, based on the flow node identification information, flow direction information, and interface information in the flow detection data corresponding to the service flow, determine the source device, terminal device, inbound and outbound interfaces of the source device, and inbound and outbound interfaces of the terminal device from the multiple transmission devices corresponding to the service flow.
[0116] In fact, the collected follow-up detection data can be used to reconstruct the transmission path of packets (i.e., service flows) in the network, thereby obtaining the service path of each service flow corresponding to each issued follow-up detection task.
[0117] In practice, for each grouping result corresponding to the flow identifier information (i.e., for each service flow), based on the flow node identifier information and flow direction information in the flow detection data of each transmission device corresponding to the flow identifier information, the source device (also called the source device, the head node of the transmission path) and the terminal device (i.e., the tail node of the transmission path) corresponding to the flow identifier information can be determined from the grouping result corresponding to the flow identifier information. Based on the interface information and flow direction information in the flow detection data of the source device corresponding to the flow identifier information, the inbound and outbound interfaces of the source device corresponding to the flow identifier information, as well as the inbound and outbound interfaces of the terminal device corresponding to the flow identifier information, can be determined. Among them, the inbound interface of the source device is the starting point of the transmission path (i.e., the service path), and the outbound interface of the terminal device is the ending point of the transmission path.
[0118] In the specific implementation process, the flow detection data for any service flow detected by each target device includes two sets of data, and the flow direction information and interface information in these two sets of data are different. Assume that the flow identifier information corresponding to a group result is 'a', and this group result includes two transmission devices, one transmission device is target device A, and the other transmission device is target device B. The flow detection data corresponding to target device A includes two sets of data, data A1 and data A2, and the flow detection data corresponding to target device B includes two sets of data, data B1 and data B2. The flow direction information in data A1 is Ingress (starting direction) and the interface information is a1; the flow direction information in data A2 is Trans Output (outgoing direction) and the interface information is a2; the flow direction information in data B1 is Trans Input (incoming direction) and the interface information is b1; the flow direction information in data B2 is Egress (ending direction) and the interface information is b2.
[0119] Therefore, the transmission device (i.e., target device A) corresponding to the flow detection data with flow direction information of Ingress can be identified as the source device of the service flow a, and the transmission device (i.e., target device B) corresponding to the flow detection data with flow direction information of Egress can be identified as the terminal device of the service flow a. Since the flow direction information in data A1 is Ingress and the flow direction information in data A2 is Trans Output, the interface information a1 in data A1 is actually the inbound interface of target device A (i.e., the inbound interface of the source device), and the interface information a2 in data A2 is actually the outbound interface of target device A (i.e., the outbound interface of the source device). Also, since the flow direction information in data B1 is Trans Input and the flow direction information in data B2 is Egress, the interface information b1 in data B1 is actually the inbound interface of target device B (i.e., the inbound interface of the terminal device), and the interface information b2 in data B2 is actually the outbound interface of target device B (i.e., the outbound interface of the terminal device).
[0120] Step 6: If there are two transmission devices corresponding to the service flow, connect the inbound interface of the source device, the outbound interface of the source device, the inbound interface of the terminal device, and the outbound interface of the terminal device in sequence according to the pre-set first connection order to obtain the service path corresponding to the service flow.
[0121] In practice, if the measurement type is configured as end-to-end when configuring the flow detection information of a flow detection task, the number of transmission devices corresponding to the service flow detected by the flow detection task is two, one as the source device and the other as the terminal device; if the measurement type is configured as hop-by-hop, the number of transmission devices corresponding to the service flow detected by the flow detection task is generally greater than two (e.g., three or four), one as the source device, one as the terminal device, and the rest as intermediate devices.
[0122] Therefore, the first connection sequence is generally set as follows: source device inbound interface - source device outbound interface - terminal device inbound interface - terminal device outbound interface. It should be noted that the inbound and outbound interfaces of each device need to be connected through that device. Taking target device A as an example, when connecting the inbound interface a1 and outbound interface a2 of target device A, it is necessary to go through target device A. After connecting according to the first connection sequence, the first intermediate path corresponding to the service flow a is actually: a1-a2-b1-b2.
[0123] Step 7: If the number of transmission devices corresponding to the service flow is greater than two, determine the intermediate device corresponding to the service flow based on the source device, terminal device, and multiple transmission devices corresponding to the service flow; wherein, the intermediate device is any device other than the source device and terminal device among the multiple transmission devices.
[0124] Step 8: Based on the flow node identifier information, timestamp information, flow direction information, and interface information in the target flow detection data of the service flow corresponding to the intermediate device, sort and connect the interfaces of the intermediate device corresponding to the service flow in ascending order of timestamp to obtain the first intermediate path corresponding to the service flow.
[0125] In practice, by comparing the timestamps in the target flow detection data corresponding to the intermediate devices, the interfaces of the intermediate devices (that is, the interfaces indicated by the interface information in the target flow detection data) can be arranged in ascending order of timestamps to determine the arrival and departure order of the packets carried by the corresponding service flow on each intermediate device. This helps to determine the transmission path of the packets in the network, that is, to determine the service path corresponding to the service flow.
[0126] In the specific implementation process, the number of intermediate devices may be one or more. Assume that the packet result corresponding to flow identifier information 'a' includes four transmission devices: target device A, target device B, target device C, and target device D. Target device A is the source device, target device B is the terminal device, and target devices C and D are intermediate devices. The flow detection data corresponding to target device C includes two sets of data, data C1 and data C2, and the flow detection data corresponding to target device D includes two sets of data, data D1 and data D2. In data C1, the flow node identifier is C, the timestamp is t1, the flow direction is Trans Input, and the interface information is c1. In data C2, the flow node identifier is also C, the timestamp is t2, the flow direction is Trans Output, and the interface information is c2. In data D1, the flow node identifier is D, the timestamp is t3, the flow direction is Trans Input, and the interface information is d1. In data D2, the flow node identifier is also D, the timestamp is t4, the flow direction is Trans Output, and the interface information is d2.
[0127] Assuming that comparing timestamp information t1, t2, t3, and t4 yields t2>t1>t4>t3, and since the interface information corresponding to t1 is c1, t2 is c2, t3 is d1, and t4 is d2, then sorting the interfaces of the intermediate devices according to the ascending order of timestamps and connecting them in sequence, the first intermediate path corresponding to service flow a is: d1-d2-c1-c2. That is, the arrival and departure order of the packets carried by service flow a on the above intermediate devices (target device C and target device D) is as follows: the packet arrives at target device D via the inbound interface d1, then arrives at target device C via the outbound interface d2 of target device D and the inbound interface c1 of target device C, and finally is received via the outbound interface c2 of target device C.
[0128] Step 9: Based on the LLDP information of each transmission device obtained in advance, obtain the second intermediate path corresponding to the service flow.
[0129] In actual implementation, the LLDP information of each transmission device is used to indicate the target transmission device connected to that transmission device and the interface information of that target transmission device. If the transmission devices of service flow a include target device A (source device), target device B (terminal device), target device C (intermediate device), and target device D (intermediate device), and the LLDP information of target device A indicates that target device A is connected to interface c1 of target device C, the LLDP information of target device C indicates that target device C is connected to interface a2 of target device A and d1 of target device D, the LLDP information of target device D indicates that target device D is connected to interface c2 of target device C and b1 of target device B, and the LLDP information of target device B indicates that target device B is connected to interface d2 of target device D; then the second intermediate path corresponding to the above service flow a can be determined as: c1-c2-d1-d2.
[0130] Step 10: If the first intermediate path is the same as the second intermediate path, the first intermediate path is determined as the target intermediate path; if the first intermediate path is different from the second intermediate path, the second intermediate path is determined as the target intermediate path.
[0131] In practical implementation, the timestamp information in the target flow detection data corresponding to the intermediate device may differ from the actual situation. Therefore, the first intermediate path obtained based on the ascending order of timestamps may not be accurate. To address this, the LLDP information of each transmission device can be combined to obtain information about the directly connected neighboring devices (i.e., the target transmission device) of each transmission device, thus obtaining a second intermediate path. This allows for a better understanding of the network topology, discovery of device neighbors, and determination of the packet transmission path within the network. Then, by comparing the first and second intermediate paths, the target intermediate path is determined, avoiding the problem of an inaccurate first intermediate path due to incorrect timestamp information.
[0132] Specifically, when obtaining the second intermediate path corresponding to the service flow based on the pre-acquired LLDP information of each transmission device, since timestamps are not considered, the accuracy of the second intermediate path is generally considered to be high. Therefore, when comparing the first and second intermediate paths, if the first and second intermediate paths are the same, the timestamp information is generally considered to match the actual situation, and the first intermediate path can be determined as the target intermediate path. If the first and second intermediate paths are different, the timestamp information is generally considered to be inconsistent with the actual situation. That is, the accuracy of the first intermediate path obtained according to the order of timestamps from smallest to largest is low, and the second intermediate path can be determined as the target intermediate path.
[0133] It should be noted that in actual execution, there may be cases where the LLDP information of a certain transmission device corresponding to the service flow is missing. It is impossible to obtain the LLDP information of each transmission device, so the second intermediate path corresponding to the service flow cannot be obtained. In this case, the first intermediate path corresponding to the service flow can be directly determined as the target intermediate path.
[0134] Step 11: Based on the target intermediate path, the inbound and outbound interfaces of the source device, and the inbound and outbound interfaces of the terminal device, determine the service path corresponding to the service flow.
[0135] In the specific implementation process, step eleven above can be achieved through the following steps A to B:
[0136] Step A: If the target intermediate path is the first intermediate path, connect the inbound interface of the source device, the outbound interface of the source device, and the inbound interface of the first intermediate device in sequence; then connect the outbound interface of the second intermediate device, the inbound interface of the terminal device, and the outbound interface of the terminal device in sequence to obtain the service path corresponding to the service flow; wherein, the inbound interface of the first intermediate device is the interface indicated by the interface information corresponding to the first target flow detection data with the smallest timestamp in the target flow detection data of the service flow corresponding to the intermediate device; the outbound interface of the second intermediate device is the interface indicated by the interface information corresponding to the second target flow detection data with the largest timestamp in the target flow detection data of the service flow corresponding to the intermediate device.
[0137] In practice, by utilizing the target intermediate path of the service flow, the inbound and outbound interfaces of the source device, and the inbound and outbound interfaces of the terminal device, the analyzer can begin to reconstruct the actual transmission path of the message (i.e., the service path of the service flow).
[0138] Specifically, when the target intermediate path of business flow a is the first intermediate path, assuming the first intermediate path is d1-d2-c1-c2, the inbound interface of the source device is the inbound interface a1 of the target device A, and the outbound interface of the source device is the outbound interface a2 of the target device A; the inbound interface of the terminal device is the inbound interface b1 of the target device B, and the outbound interface of the terminal device is the outbound interface b2 of the target device B; the inbound interface of the first intermediate device is the inbound interface d1 of the target device D, and the outbound interface of the second intermediate device is the outbound interface c2 of the target device C; then, after connecting according to the above step A, the business path corresponding to business flow a is: a1-a2-d1-d2-c1-c2-b1-b2.
[0139] Step B: If the target intermediate path is the second intermediate path, determine the inbound interface of the third intermediate device to be connected to the source device based on the pre-acquired LLDP information of the source device; determine the outbound interface of the fourth intermediate device to be connected to the terminal device based on the pre-acquired LLDP information of the terminal device; connect the inbound interface of the source device, the outbound interface of the source device, and the inbound interface of the third intermediate device in sequence; then connect the outbound interface of the fourth intermediate device, the inbound interface of the terminal device, and the outbound interface of the terminal device in sequence to obtain the service path corresponding to the service flow; wherein, the inbound interface of the third intermediate device is the interface indicated by the interface information of the target transmission device corresponding to the LLDP information of the source device; the outbound interface of the fourth intermediate device is the interface indicated by the interface information of the target transmission device corresponding to the LLDP information of the terminal device.
[0140] Specifically, when the target intermediate path of business flow a is the second intermediate path, assuming the second intermediate path is c1-c2-d1-d2, the inbound interface of the source device is the inbound interface a1 of the target device A, and the outbound interface of the source device is the outbound interface a2 of the target device A; the inbound interface of the terminal device is the inbound interface b1 of the target device B, and the outbound interface of the terminal device is the outbound interface b2 of the target device B; the inbound interface of the third intermediate device is the inbound interface c1 of the target device C, and the outbound interface of the fourth intermediate device is the outbound interface d2 of the target device D; then, after connecting according to the above step B, the business path corresponding to business flow a is: a1-a2-c1-c2-d1-d2-b1-b2.
[0141] Step S208: Real-time restoration of the follow-up detection data of each service flow to the corresponding transmission device on the service path.
[0142] Step S210: Based on the packet quantity information, timestamp information and interface information corresponding to each flow detection data, determine in real time the status information of the transmission path between every two adjacent transmission devices in the service path corresponding to each service flow; wherein, the status information includes latency information, packet loss information and jitter information; the status information is presented in the form of a timeline.
[0143] In the specific implementation process, each stream detection data also includes packet count information (see details). Figure 4 The `PacketCount` in the context of the detection period is the number of packets within the detection cycle. Each flow detection task also includes service source information and customer information. Using the timestamp data on each device, the analyzer can calculate the processing time of the packet on each transmission device (i.e., the difference between the timestamp information in the two sets of data included in the flow detection data corresponding to that transmission device) and the transmission delay between nodes (i.e., the delay information of the transmission path between two adjacent transmission devices; specifically, it can be understood as the difference between the timestamp information of the inbound interface of the later transmission device and the timestamp information of the outbound interface of the earlier transmission device). Based on the transmission delay between nodes, the analyzer can calculate the jitter between nodes (i.e., the difference between the transmission delay between the nodes in the current detection cycle and the transmission delay between the nodes in the previous detection cycle). Using the packet count information on each device, the analyzer can calculate the packet loss rate between nodes (i.e., the difference between the packet count information of the inbound interface of the later transmission device and the packet count information of the outbound interface of the earlier transmission device).
[0144] Step S212: Based on the status information of the transmission path between every two adjacent transmission devices and the pre-set status information threshold, determine the abnormal transmission path in real time, and determine the abnormal interface based on the abnormal transmission path.
[0145] The aforementioned status information thresholds generally include latency thresholds, jitter thresholds, and packet loss thresholds. Specifically, the status information thresholds can be set according to actual conditions. Typically, the latency threshold is configured to 10µs, the jitter threshold to 10µs, and the packet loss threshold to 0.2%. If the status information of the transmission path between two adjacent transmission devices is greater than the status information threshold, that is, if the three conditions of latency information greater than the latency threshold, packet loss information greater than the packet loss threshold, and jitter information greater than the jitter threshold are met simultaneously, then the transmission path between these two adjacent transmission devices is determined to be an abnormal transmission path, and the outgoing and incoming interfaces at both ends of this abnormal transmission path are abnormal interfaces.
[0146] To help network administrators better understand packet transmission paths and network performance, the analyzer may generate a visual service topology map to display packet transmission paths (i.e., the service paths corresponding to service flows), latency, jitter, packet loss rate (i.e., the status information of the transmission path between every two adjacent transmission devices in the service path), and potential congestion points (i.e., the abnormal interfaces corresponding to the above abnormal transmission paths). In actual implementation, the data reported by each node in the flow detection can be restored to the topology and the status information of the day can be presented in a timeline format. The latest status information is displayed by default, and the timeline can be dragged to query historical information.
[0147] In actual implementation, it supports viewing performance data of different flow detection reports, and the topology presentation of performance data is linked when switching flows; it also supports viewing flow summary data, which aggregates all flow detection performance reports and presents the maximum end-to-end latency, jitter, and packet loss values; moreover, the transmission path, device interface, time axis, and service status in the service topology diagram can be displayed in different colors according to the threshold configuration results. Specifically, green indicates a normal service status, while red and yellow indicate abnormal status.
[0148] To better understand the above embodiments, please refer to the following: Figure 5 The diagram shown is a visual representation of a business topology. Figure 5The data presented here is related to the service flow corresponding to the end-to-end flow detection task, including the service path corresponding to the service flow PE1_GigabitEthemet8 / 0 / 4-PE5_GigabitEthemet8 / 0 / 5, the status information of the transmission path between the two adjacent transmission devices PE1 and PE5 in this service path (where the latency is 102us, the jitter is 89us, and the packet loss rate is 0%), the end-to-end maximum packet loss rate, maximum latency, and maximum jitter of this service path. Since the packet loss rate is less than the preset packet loss threshold, there is no abnormal transmission path or abnormal interface displayed, so the service status is displayed as normal. Since the time axis is displayed at 9:37 on March 18, 2024, from 00:00 to 24:00, it can be known that the data presented in the figure is the relevant data of the corresponding service flow at that time point.
[0149] For more details, please refer to, for example, Figure 6 This is another visual representation of the business topology. Figure 6 The data presented here is related to the service flow corresponding to the hop-by-hop flow detection task, including the service path corresponding to the service flow PE1_GigabitEthemet8 / 0 / 4-PE5_GigabitEthemet8 / 0 / 5. According to this service path, PE1 is the source device, PE5 is the terminal device, and PC1 and PB1 are intermediate devices. Specifically, the status information of the transmission path between the two adjacent transmission devices PE1 and PC1 is: latency 531µs, jitter 99µs, and packet loss rate 26.31%; the status information of the transmission path between the two adjacent transmission devices PC1 and PB1 is: latency 313µs, jitter 56µs, and packet loss rate 0%; the status information of the transmission path between the two adjacent transmission devices PB1 and PE5 is: latency 132µs, jitter 23µs, and packet loss rate 0%. The maximum end-to-end packet loss rate of the path is 26.31%, the maximum latency is 531µs, and the maximum jitter is 99µs. Since the latency of 531µs and the jitter of 99µs are greater than the latency threshold and the packet loss rate of 26.31% are greater than the packet loss threshold, the transmission path between the two adjacent transmission devices PE1 and PC1 is displayed as an abnormal transmission path. The outgoing interface of the transmission device PE1 and the incoming interface (PC1_GigabitEthemet8 / 0 / 1) of the transmission device PC1 corresponding to this abnormal transmission path are displayed as abnormal interfaces. Therefore, the service status is displayed as abnormal. Since the timeline is displayed at 15:31 during the period from 00:00 to 24:00 on March 18, 2024, it can be known that the data presented in the figure is the relevant data of the corresponding service flow at that time point.
[0150] In reality, issues such as uneven link quality, device performance differences, configuration errors, or congestion within the network often lead to significant variations in Quality of Service (QoS) across different network segments. These QoS discrepancies not only impact user experience but may also conceal deeper network problems. However, existing network monitoring solutions often focus on overall network performance metrics, such as total bandwidth utilization and device load, rather than analyzing QoS discrepancies specific to service flows. This makes it difficult to accurately pinpoint the root cause of problems and optimize network performance. In conclusion, current technologies are insufficient to meet the demands for QoS analysis of service paths in today's network environment.
[0151] This application, based on flow detection, can perform business path reconstruction and quality difference analysis, solving the problem that traditional network monitoring methods cannot accurately track business paths and assess service quality differences in complex network environments. Through advanced data collection, processing and analysis technologies, it can achieve high-accuracy reconstruction and quality analysis of network business flow (that is, analyze the differences in network service quality at different stages), thereby improving the network management level and service quality.
[0152] Step S214: Determine the average value of the status information of the service path corresponding to each service flow based on the status information of the transmission path between every two adjacent transmission devices.
[0153] In fact, each target flow for flow detection (i.e., the service flow to be detected) also corresponds to a service source and customer information (customer name). Flow detection data can be statistically analyzed by service dimension, including service ID, service name, service source, deployment city, category, customer name, IPv4 address range, IPv6 address range, maximum latency, minimum latency, average latency, maximum jitter, minimum jitter, average jitter, maximum packet loss, minimum packet loss, and average packet loss. Specifically, each flow detection task corresponds to a service (the service information can include service ID, service name, service source, deployment city, category, customer name, IPv4 address range, and IPv6 address range). This service corresponds to a service flow. Based on the latency, packet loss, and jitter information of the transmission path between every two adjacent transmission devices in the service path corresponding to this service flow, the average latency, average packet loss, and average jitter information corresponding to this service flow are calculated (equivalent to determining the average status information of the service path corresponding to each service flow; generally, the default value is an integer).
[0154] Specifically, it can be in the form of Figure 6 The following explanation uses the latency, packet loss, and jitter information of the transmission path between every two adjacent transmission devices in the service path corresponding to the service flow shown as an example. Figure 6As shown, the latency information of the transmission path between every two adjacent transmission devices in the service path corresponding to the service flow PE1_GigabitEthemet8 / 0 / 4-PE5_GigabitEthemet8 / 0 / 5 is 531us, 313us, and 132us, respectively; the jitter information is 99us, 56us, and 23us, respectively; and the packet loss information is 26.31%, 0%, and 0%, respectively. Therefore, the average latency information of this service flow is (531+313+132) / 3 = 325us, the average jitter information is (99+56+23) / 3 = 59us, and the average packet loss information is (26.31%+0%+0%) / 3 = 9%.
[0155] Step S216: Based on the average value of the business source information, customer information, and business path status information of the follow-up detection task corresponding to each business flow, obtain the average business information corresponding to each customer information and each business source information.
[0156] In practice, the average latency, average packet loss, and average jitter of all customers can be calculated according to the customer to which the business belongs (i.e., customer information); the average latency, average packet loss, and average jitter of the four business sources (including in-province own, out-of-province own, in-province and out-of-province and out-of-province and out-of-province and out-of-province) can also be calculated according to the business source (including in-province own, out-of-province own, in-province and out-of ...
[0157] Specifically, the system can obtain the following detection task and customer information for each business flow, and then group business flows with the same customer information into a group to obtain at least one first group result. For each first group result, the system can calculate the average latency, average packet loss, and average jitter information corresponding to the customer information of the business flow in that group result based on the average latency, average packet loss, and average jitter information of each business flow in that first group result (which is equivalent to determining the average business information corresponding to each customer information; in general, the default value is an integer).
[0158] Assuming that the customer information for business flows a, b, and c all belongs to Kunming XX Game Company, we can group business flows a, b, and c together. If the average latency, packet loss, and jitter for business flow a are 20µs, 10%, and 10µs respectively; the average latency, packet loss, and jitter for business flow b are 5µs, 5%, and 15µs respectively; and the average latency, packet loss, and jitter for business flow c are 5µs, 0%, and 5µs respectively, then we can calculate the average latency for the customer information of Kunming XX Game Company as (20+5+5) / 3 = 10µs, the average packet loss as (10+5+0) / 3 = 5%, and the average jitter as (10+15+5) / 3 = 10µs. Similarly, using the same calculation method, we can also calculate the average latency, average packet loss, and average jitter for other customer information, which will not be elaborated here.
[0159] In the specific implementation process, the business source information of the following detection task corresponding to each business flow can also be obtained. Then, business flows with the same business source information are grouped together to obtain at least one second grouping result. For each second grouping result, the average latency information, average packet loss information, and average jitter information corresponding to the business source information of the business flow in the grouping result can be calculated based on the average latency information, average packet loss information, and average jitter information corresponding to each business flow in the second grouping result (which is equivalent to determining the average business information corresponding to each business source information. In general, the default value is taken as an integer).
[0160] Assuming that the business source information for business flows a, b, and d are all within the province, we can group business flows a, b, and d together. If the average latency information for business flow a is 20µs, the average packet loss information is 10%, and the average jitter information is 10µs; the average latency information for business flow b is 5µs, the average packet loss information is 5%, and the average jitter information is 15µs; and the average latency information for business flow d is 14µs, the average packet loss information is 0%, and the average jitter information is 5µs, then we can calculate the average latency information for the business source information within the province as (20+5+14) / 3 = 13µs, the average packet loss information as (10+5+0) / 3 = 5%, and the average jitter information as (10+15+5) / 3 = 10µs. Similarly, using the same calculation method, we can also calculate the average latency information, average packet loss information, and average jitter information for other business source information, which will not be elaborated here.
[0161] Step S218: Based on the average business information corresponding to each customer information and each business source information, sort each customer information and business source information according to multiple preset sorting requirements to obtain the customer sorting result and business source sorting result corresponding to each sorting requirement.
[0162] The above sorting requirements can be set according to the actual situation. For example, they can be sorted in ascending order (from smallest to largest) or descending order of average latency, or in ascending or descending order of average jitter information, or in ascending or descending order of average packet loss information. However, in actual implementation, after obtaining the average latency information, average packet loss information, and average jitter information corresponding to each customer information and each business source information, it is generally preferred to sort in ascending order of average latency.
[0163] Specifically, when obtaining customer ranking results, the default is to sort by average latency in ascending order. Clicking the indicator triangle allows you to switch to descending order or change the sorting criteria (i.e., switch the sorting requirements). This customer ranking result reflects differences in customer service quality; that is, when ranked in ascending order by average latency, customers ranked higher have better service quality, while those ranked lower have poorer service quality. Similarly, the business source ranking result also reflects differences in customer service quality; that is, when ranked in ascending order by average latency, business sources ranked higher have better service quality, while those ranked lower have poorer service quality.
[0164] In practical implementation, quality difference analysis is performed by comparing service traffic quality metrics across different nodes, such as latency, jitter, packet loss rate, and throughput. By constructing a quality scoring model, the performance differences between different network segments can be quantified, and performance bottlenecks or potential fault points can be located. Quality difference analysis not only supports real-time monitoring but also historical data analysis, revealing performance change trends and providing data support for network optimization.
[0165] This application provides a method for determining service paths based on flow-following detection. Through an efficient deployment strategy for flow-following detection probes, it can not only cover key network nodes but also avoid resource waste; through an efficient service path calculation algorithm, it can achieve rapid path reconstruction with minimal computational cost; and through a multi-dimensional quality indicator comparison method, it can comprehensively evaluate the quality differences of network services.
[0166] This application integrates in-band performance monitoring data. Due to the large volume of data and the need for high real-time performance and accuracy, this solution adopts Flink (Apache Flink is an open-source stream processing framework developed by the Apache Software Foundation. Its core is a distributed streaming data stream engine written in Java and Scala. Flink executes arbitrary streaming data programs in a data parallel and pipelined manner. Flink's pipeline runtime system can execute batch processing and stream processing programs. In addition, Flink's runtime itself also supports the execution of iterative algorithms) as the data processing engine. The entire processing architecture is reasonably designed: Telemetry -> Probe -> Kafka (a high-throughput distributed publish-subscribe messaging system that can handle all action stream data of consumers on a website) -> Flink -> MySQL, enabling real-time network log analysis. Since this solution requires real-time correlation between large amounts of data to ensure the accuracy of the program, ensuring the reliability of the correlation and adapting the speed to real-time requirements while guaranteeing real-time processing of large amounts of data becomes crucial. In addition, the NETCONF message template management function can be customized to enable the configuration distribution messages of newly added vendors; this makes management information a database that computers can understand, improves the computer's ability to process network management data, and thus enhances network management capabilities.
[0167] The system's functional architecture, design, and development were all independently developed. Through testing, the system has achieved visualized configuration and deployment of Tencent Games' dedicated network monitoring instance tasks.
[0168] Redis (Remote Dictionary Service) is an open-source, network-enabled, in-memory or persistent, log-structured, key-value database written in ANSI C, and provides APIs for multiple languages.
[0169] IFIT (in-situ Flow Information Telemetry) is a passive detection technology that follows the flow. Its basic principle is similar to that of IPFPM, and it uses the RFC 8321 staining mechanism for performance measurement.
[0170] This invention also provides a device for determining service paths based on flow detection, such as... Figure 7As shown, the apparatus includes: an acquisition module 10, used to acquire flow detection data of at least one service flow corresponding to each target device; wherein each target device is pre-configured with a flow detection function; a first determination module 11, used to determine multiple transmission devices corresponding to each service flow from multiple target devices based on each flow detection data; wherein each flow detection data includes: flow node identification information, timestamp information, flow direction information, and interface information; a second determination module 12, used to sort and connect the interfaces of multiple transmission devices corresponding to each service flow based on the flow node identification information, timestamp information, flow direction information, interface information of each flow detection data, and LLDP information pre-configured for each transmission device, so as to determine the service path corresponding to each service flow; wherein the LLDP information of each transmission device is used to indicate the target transmission device connected to the transmission device and the interface information of the target transmission device.
[0171] The device for determining service paths based on flow detection provided in this invention includes: acquiring flow detection data for at least one service flow corresponding to each target device; wherein each target device is pre-configured with flow detection functionality; determining multiple transmission devices corresponding to each service flow from multiple target devices based on each flow detection data; and sorting and connecting the interfaces of the multiple transmission devices corresponding to each service flow based on the flow node identifier information, timestamp information, flow direction information, interface information, and LLDP information pre-configured for each transmission device of each flow detection data, so as to determine the service path corresponding to each service flow. This device, based on flow detection for service path reconstruction, can accurately reconstruct a single service path from complex network traffic, thereby solving the problem that traditional network monitoring methods cannot accurately reconstruct service paths in complex network environments.
[0172] The device for determining service paths based on flow detection provided in this embodiment of the invention has the same implementation principle and technical effects as the aforementioned method embodiment for determining service paths based on flow detection. For the embodiment of the device for determining service paths based on flow detection, please refer to the corresponding content in the aforementioned method embodiment for determining service paths based on flow detection, which will not be repeated here.
[0173] This invention also provides an electronic device, see [link to relevant documentation]. Figure 8 As shown, the electronic device includes a processor 130 and a memory 131. The memory 131 stores machine-executable instructions that can be executed by the processor 130. The processor 130 executes the machine-executable instructions to implement the above-described method for determining service paths based on flow detection.
[0174] Furthermore, Figure 8The electronic device shown also includes a bus 132 and a communication interface 133, with the processor 130, the communication interface 133 and the memory 131 connected via the bus 132.
[0175] The memory 131 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 133 (which can be wired or wireless), such as the Internet, wide area network, local area network, or metropolitan area network. The bus 132 may be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 8 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.
[0176] Processor 130 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 130 or by instructions in software form. Processor 130 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this invention can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 131, and processor 130 reads the information in memory 131 and, in conjunction with its hardware, completes the steps of the method described in the foregoing embodiments.
[0177] This invention also provides a computer-readable storage medium storing computer-executable instructions. When these computer-executable instructions are invoked and executed by a processor, they cause the processor to implement the aforementioned method for determining service paths based on flow detection. For specific implementation details, please refer to the method embodiments, which will not be repeated here.
[0178] The method, apparatus, and electronic device for determining service paths based on flow detection provided in this invention include a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods described in the preceding method embodiments. For specific implementation details, please refer to the method embodiments, which will not be repeated here.
[0179] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0180] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.
Claims
1. A method for determining a service path based on in-line detection, characterized in that, The method includes: Acquire follow-up detection data for at least one service flow corresponding to each target device; wherein each target device is pre-configured with follow-up detection function; Based on each flow detection data, multiple transmission devices corresponding to each service flow are determined from multiple target devices; wherein each flow detection data includes: flow node identification information, timestamp information, flow direction information, and interface information; For each service flow, based on the flow node identification information, flow direction information, and interface information in the flow detection data corresponding to the service flow, the source device and terminal device corresponding to the service flow, as well as the inbound and outbound interfaces of the source device and the inbound and outbound interfaces of the terminal device, are determined from multiple transmission devices corresponding to the service flow; wherein, the LLDP information pre-configured for each transmission device is used to indicate the target transmission device connected to the transmission device and the interface information of the target transmission device; If there are two transmission devices corresponding to the service flow, the inbound interface of the source device, the outbound interface of the source device, the inbound interface of the terminal device, and the outbound interface of the terminal device are connected in sequence according to the pre-set first connection order to obtain the service path corresponding to the service flow. If the number of transmission devices corresponding to the service flow is greater than two, the intermediate device corresponding to the service flow is determined based on the source device, terminal device, and multiple transmission devices corresponding to the service flow; wherein, the intermediate device is any device other than the source device and terminal device among the multiple transmission devices. Based on the flow node identifier information, timestamp information, flow direction information, and interface information in the target flow detection data of the service flow corresponding to the intermediate device, the interfaces of the intermediate device corresponding to the service flow are sorted and connected in ascending order of timestamp to obtain the first intermediate path corresponding to the service flow. Based on the LLDP information of the intermediate device obtained in advance, the second intermediate path corresponding to the service flow is obtained; If the first intermediate path is the same as the second intermediate path, the first intermediate path is determined as the target intermediate path; if the first intermediate path is not the same as the second intermediate path, the second intermediate path is determined as the target intermediate path. Based on the target intermediate path, the inbound and outbound interfaces of the source device, and the inbound and outbound interfaces of the terminal device, the service path corresponding to the service flow is determined.
2. The method according to claim 1, characterized in that, The steps for obtaining flow detection data for at least one service flow corresponding to each target device include: Obtain the configuration message of the first device; the first device is a disabled device. Each configuration message is sent to the corresponding first device via NETCONF to perform global configuration for flow detection on each first device, thereby obtaining a target device list; wherein, the target device list includes multiple target devices configured with flow detection function; Based on at least one pre-configured flow detection task, the source device corresponding to each flow detection task is determined from a plurality of target devices; wherein, each flow detection task corresponds to a service flow; the flow detection task includes reporting configuration information; Each follow-up detection task is sent to the corresponding source device, and follow-up detection data of at least one service flow reported to the acquisition machine by each target device according to the reporting configuration information is obtained.
3. The method according to claim 2, characterized in that, Each flow-following detection data also includes: flow identifier information and period ID information; the step of determining multiple transmission devices corresponding to each service flow from multiple target devices based on each flow-following detection data includes: The target devices corresponding to the flow detection data with the same flow identifier information and period ID information are grouped together to obtain at least one grouping result corresponding to the flow identifier information. Each grouping result includes multiple transmission devices corresponding to the flow identifier information.
4. The method according to claim 1, characterized in that, The steps for determining the service path corresponding to the service flow based on the target intermediate path, the inbound and outbound interfaces of the source device, and the inbound and outbound interfaces of the terminal device include: If the target intermediate path is the first intermediate path, connect the inbound interface of the source device, the outbound interface of the source device, and the inbound interface of the first intermediate device in sequence; then connect the outbound interface of the second intermediate device, the inbound interface of the terminal device, and the outbound interface of the terminal device in sequence to obtain the service path corresponding to the service flow; wherein, the inbound interface of the first intermediate device is the interface indicated by the interface information corresponding to the first target flow detection data with the smallest timestamp in the target flow detection data of the service flow corresponding to the intermediate device; the outbound interface of the second intermediate device is the interface indicated by the interface information corresponding to the second target flow detection data with the largest timestamp in the target flow detection data of the service flow corresponding to the intermediate device. If the target intermediate path is the second intermediate path, the inbound interface of the third intermediate device to be connected to the source device is determined according to the LLDP information of the source device obtained in advance; the outbound interface of the fourth intermediate device to be connected to the terminal device is determined according to the LLDP information of the terminal device obtained in advance. The service path corresponding to the service flow is obtained by sequentially connecting the inbound interface of the source device, the outbound interface of the source device, and the inbound interface of the third intermediate device; then sequentially connecting the outbound interface of the fourth intermediate device, the inbound interface of the terminal device, and the outbound interface of the terminal device; wherein, the inbound interface of the third intermediate device is the interface indicated by the interface information of the target transmission device corresponding to the LLDP information of the source device; and the outbound interface of the fourth intermediate device is the interface indicated by the interface information of the target transmission device corresponding to the LLDP information of the terminal device.
5. The method according to claim 2, characterized in that, Each stream-following detection data also includes message count information; each stream-following detection task also includes service source information and customer information; the method further includes: The flow detection data of each service flow is restored to the corresponding transmission device on the service path in real time; Based on the packet quantity information, timestamp information, and interface information corresponding to each flow detection data, the status information of the transmission path between every two adjacent transmission devices in the service path corresponding to each service flow is determined in real time; wherein, the status information includes latency information, packet loss information, and jitter information; the status information is presented in a timeline format; Based on the status information of the transmission path between every two adjacent transmission devices and the pre-set status information threshold, abnormal transmission paths are determined in real time, and abnormal interfaces are determined based on the abnormal transmission paths. Based on the status information of the transmission path between every two adjacent transmission devices, determine the average status information of the service path corresponding to each service flow; Based on the average value of the business source information, customer information and the status information of the business path corresponding to each business flow, the average business information corresponding to each customer information and each business source information is obtained. Based on the average business information corresponding to each customer information and each business source information, the customer information and business source information are sorted according to multiple preset sorting requirements to obtain the customer sorting result and business source sorting result corresponding to each sorting requirement.
6. A device for determining a service path based on flow detection, characterized in that, The device includes: The acquisition module is used to acquire the flow detection data of at least one service flow corresponding to each target device; wherein each target device is pre-configured with the flow detection function; The first determining module is used to determine multiple transmission devices corresponding to each service flow from multiple target devices based on each flow detection data; wherein each flow detection data includes: flow node identification information, timestamp information, flow direction information, and interface information; The second determining module is used, for each service flow, to determine, based on the flow node identification information, flow direction information, and interface information in the flow detection data corresponding to the service flow, the source device, terminal device, and the inbound and outbound interfaces of the source device and the terminal device from multiple transmission devices corresponding to the service flow. The LLDP information pre-configured for each transmission device is used to indicate the target transmission device connected to that transmission device and the interface information of that target transmission device. If there are two transmission devices corresponding to the service flow, the inbound interface of the source device, the outbound interface of the source device, the inbound interface of the terminal device, and the outbound interface of the terminal device are connected sequentially according to a pre-set first connection order to obtain the service path corresponding to the service flow. If there are more than two transmission devices corresponding to the service flow, the source device, terminal device, and multiple transmission devices corresponding to the service flow are used to determine the source device, terminal device, and the inbound and outbound interfaces of the terminal device from multiple transmission devices corresponding to the service flow. The transmission equipment identifies the intermediate device corresponding to the service flow; wherein the intermediate device is any device other than the source device and the terminal device among multiple transmission equipment; based on the flow node identification information, timestamp information, flow direction information, and interface information in the target flow detection data of the service flow corresponding to the intermediate device, the interfaces of the intermediate device corresponding to the service flow are sorted and connected in ascending order of timestamp to obtain the first intermediate path corresponding to the service flow; based on the pre-acquired LLDP information of the intermediate device, the second intermediate path corresponding to the service flow is obtained; if the first intermediate path and the second intermediate path are the same, the first intermediate path is determined as the target intermediate path; if the first intermediate path and the second intermediate path are different, the second intermediate path is determined as the target intermediate path; based on the target intermediate path, the inbound and outbound interfaces of the source device, and the inbound and outbound interfaces of the terminal device, the service path corresponding to the service flow is determined.
7. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing computer-executable instructions that can be executed by the processor, the processor executing the computer-executable instructions to implement the service path determination method based on flow detection as described in any one of claims 1 to 5.
8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when invoked and executed by a processor, cause the processor to implement the method for determining a service path based on flow detection as described in any one of claims 1 to 5.
Citation Information
Patent Citations
Real-time service diagnosis method and device based on stream detection
CN115914041A
Service topology generation method and device for stream detection
CN115987802A
Path overlap detection method and device
CN118590404A
