Network application quality difference analysis method, device and equipment and readable storage medium

Abstract

The application provides a network application quality difference analysis method, device and equipment and a readable storage medium. The method comprises the following steps: obtaining target UDP messages received by an OLT device within a preset time; if the receiving interval time between adjacent messages in a plurality of target UDP messages is less than or equal to a threshold value, and the payload data length of all messages is less than or equal to a threshold value, then judging that the target UDP messages are heartbeat messages; recording the receiving interval time between all adjacent heartbeat messages to obtain a heartbeat analysis array, calculating the average value to obtain a heartbeat period, and calculating the standard deviation to obtain a network jitter value; screening the receiving interval time with an absolute value greater than the network jitter value from the heartbeat analysis array and summing up to obtain a total packet loss time, and calculating the ratio of the total packet loss time to the preset time to obtain a packet loss rate. The application simplifies the quality difference index analysis model, and the data required for analysis can be easily obtained through the OLT device, thereby meeting the real-time monitoring and analysis requirements.

Description

Technical Field

[0001] This invention relates to the field of network application quality analysis and diagnosis technology, and in particular to a method, apparatus, device, and readable storage medium for analyzing poor network application quality. Background Technology

[0002] With the widespread adoption of network applications and the continuous upgrading of network transmission technologies, emerging network carriers such as 5G and the Internet of Things are being deployed on a large scale. Telecommunication operators are shifting their business focus from network-centric to user-centric, paying close attention to user network experience. This necessitates real-time monitoring of user network application metrics to analyze and identify potential quality issues, facilitating rapid rectification and optimization. Therefore, OLT (Optical Line Terminal) systems urgently need to perform quality analysis and monitoring of user network application data to meet the needs of the transformation from digital networks to intelligent networks.

[0003] Existing technologies typically involve deploying third-party DPI (Deep Packet Inspection) network probe suites to analyze traffic passing through the OLT. For connectionless UDP (User Datagram Protocol) applications, application content feature libraries and specialized machine learning algorithms need to be pre-deployed. As the types of user applications increase, the feature library needs to be constantly relearned, calculated, and updated, which cannot meet the requirements of real-time monitoring and analysis. Summary of the Invention

[0004] The main objective of this invention is to provide a method, apparatus, device, and readable storage medium for analyzing poor network application quality, aiming to solve the technical problems of existing methods for analyzing poor network application quality.

[0005] In a first aspect, the present invention provides a method for analyzing network application quality issues, the method comprising:

[0006] Obtain the target UDP packets received by the OLT device within a preset time period. The source IP of the target UDP packet is the target user IP, and the destination IP is the target application IP.

[0007] If the receiving interval between adjacent packets in multiple target UDP packets is less than or equal to the interval time threshold, and the payload data length of all packets is less than or equal to the data length threshold, then these target UDP packets are determined to be heartbeat packets.

[0008] Record the reception interval between all adjacent heartbeat packets to obtain a heartbeat analysis array, calculate the average value of the heartbeat analysis array to obtain the heartbeat period, and calculate the standard deviation of the heartbeat analysis array to obtain the network jitter value;

[0009] The receiving intervals whose absolute difference from the heartbeat period is greater than the network jitter value are selected from the heartbeat analysis array and summed to obtain the total packet loss time. The packet loss rate is obtained by calculating the ratio of the total packet loss time to the preset time.

[0010] Furthermore, in one embodiment, the method further includes the following step before the step of acquiring the target UDP packet received by the OLT device within a preset time:

[0011] Acquire DNS request and response messages received by the OLT device within a preset time period;

[0012] Based on DNS request and response messages, the number of requests, responses, and DNS response time for each domain name are counted.

[0013] For each domain name, the request success rate is obtained by calculating the ratio of the number of requests to the number of responses, and the average response time is obtained by calculating the average DNS response time.

[0014] If the success rate of the domain name requests is greater than or equal to the success rate threshold, and the average response time is less than or equal to the response time threshold, then the domain name is determined to be a valid domain name, and the IP associated with the domain name is determined from the DNS response message of the domain name as a candidate IP.

[0015] Based on the access history of the candidate IPs, the target application IP and its corresponding target user IP are determined.

[0016] Furthermore, in one embodiment, the method further includes the following step before the step of acquiring the target UDP packet received by the OLT device within a preset time:

[0017] Obtain the UDP multicast packets received by the OLT device within a preset time period. The source IP of the UDP multicast packet is the user IP, and the destination IP is the multicast IP.

[0018] UDP multicast packets with an RTP encapsulation format and a payload data length that is an integer multiple of 188 are identified as legitimate multicast packets, and the multicast IP corresponding to the legitimate multicast packet is selected as a candidate IP.

[0019] Based on the access history of the candidate IPs, the target application IP and its corresponding target user IP are determined.

[0020] Furthermore, in one embodiment, the step of determining the target application IP and its corresponding target user IP based on the access status of the candidate IPs includes:

[0021] For each candidate IP, obtain the total number of bytes of UDP packets sent to it by each user IP within a preset time period;

[0022] If the total number of bytes is greater than or equal to the byte count threshold, then the corresponding user IP and the candidate IP are determined as the target user IP and the target application IP; or, the user IPs corresponding to the largest number of total bytes and the candidate IPs are determined as the target user IP and the target application IP.

[0023] Further, in one embodiment, before the step of determining that these target UDP packets are heartbeat packets if the reception interval between adjacent packets in a plurality of target UDP packets is less than or equal to an interval time threshold, and the payload data length of all packets is less than or equal to a data length threshold, the method further includes:

[0024] The first interval time is obtained by calculating the average of the reception intervals of adjacent target UDP packets; the second interval time is obtained by calculating the average of the reception intervals shorter than the first interval time; and an interval time threshold is determined based on the second interval time; and / or

[0025] The first data length is obtained by calculating the average value of the payload data length of the target UDP packet, and the second data length is obtained by calculating the average value of the payload data lengths that are less than the first data length. The data length threshold is determined based on the second data length.

[0026] Furthermore, in one embodiment, after the step of calculating the ratio of the total packet loss time to the preset time to obtain the packet loss rate, the method further includes:

[0027] The number of bytes lost is calculated based on the total number of bytes in all target UDP packets and the packet loss rate.

[0028] The range of packet loss numbers is calculated based on the number of lost bytes and the typical length range of application messages.

[0029] Furthermore, in one embodiment, after the step of acquiring the target UDP packets received by the OLT device within a preset time period, the method further includes:

[0030] Obtain the user's identity identifier from the target UDP packet;

[0031] The user's access location is determined based on the user's identity identifier.

[0032] Secondly, the present invention also provides a network application quality poor analysis device, the network application quality poor analysis device comprising:

[0033] The target packet acquisition module is used to acquire the target UDP packets received by the OLT device within a preset time. The source IP of the target UDP packet is the target user IP, and the destination IP is the target application IP.

[0034] The heartbeat message judgment module is used to determine that if the receiving interval between adjacent messages in multiple target UDP messages is less than or equal to the interval time threshold, and the payload data length of all messages is less than or equal to the data length threshold, then these target UDP messages are heartbeat messages.

[0035] The heartbeat message analysis module is used to record the reception interval time between all adjacent heartbeat messages to obtain a heartbeat analysis array, calculate the average value of the heartbeat analysis array to obtain the heartbeat period, and calculate the standard deviation of the heartbeat analysis array to obtain the network jitter value.

[0036] The packet loss analysis module is used to filter out the receiving intervals from the heartbeat analysis array whose absolute value of the difference between the heartbeat period and the receiving interval is greater than the network jitter value, sum them up to obtain the total packet loss time, and calculate the ratio of the total packet loss time to the preset time to obtain the packet loss rate.

[0037] Thirdly, the present invention also provides a network application quality poor analysis device, the network application quality poor analysis device including a processor, a memory, and a network application quality poor analysis program stored in the memory and executable by the processor, wherein when the network application quality poor analysis program is executed by the processor, it implements the steps of the above-described network application quality poor analysis method.

[0038] Fourthly, the present invention also provides a readable storage medium storing a network application quality poor analysis program, wherein when the network application quality poor analysis program is executed by a processor, it implements the steps of the above-described network application quality poor analysis method.

[0039] This invention leverages the short length and short cycle of heartbeat packets to filter heartbeat packets from target UDP packets received by the OLT device based on the payload data length and reception interval. Further analysis using the reception interval between adjacent heartbeat packets yields network jitter and packet loss rates. This invention simplifies the poor quality indicator analysis model, eliminating the need for pre-deploying application content feature libraries and machine learning algorithms to analyze jitter and packet loss indicators. Furthermore, the necessary data for analysis is easily obtained through the OLT device, meeting real-time monitoring and analysis requirements. Additionally, this invention has low hardware and software resource consumption and dependence, making it easy to implement. Attached Figure Description

[0040] Figure 1 This is a flowchart illustrating a network application quality analysis method in one embodiment of the present invention;

[0041] Figure 2 This is a schematic diagram of data interaction of an OLT device in one embodiment of the present invention;

[0042] Figure 3This is a schematic diagram of the domain name validity determination process in one embodiment of the present invention;

[0043] Figure 4 This is a schematic diagram illustrating the process of determining the target application IP and the target user IP in one embodiment of the present invention;

[0044] Figure 5 This is a schematic diagram of the hardware structure of a network application quality analysis device in one embodiment of the present invention.

[0045] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0046] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0047] In a first aspect, embodiments of the present invention provide a method for analyzing poor network application quality.

[0048] Figure 1 A flowchart illustrating a network application quality analysis method according to an embodiment of the present invention is shown.

[0049] Reference Figure 1 In one embodiment, the network application quality poor analysis method includes the following steps:

[0050] S11. Obtain the target UDP packets received by the OLT device within a preset time. The source IP of the target UDP packets is the target user IP, and the destination IP is the target application IP.

[0051] The UDP protocol provides an application with a way to send encapsulated IP packets without establishing a connection. For example, games, online education, live video streaming, and IPTV are all UDP connectionless applications. Among them, games and online education are unicast UDP applications, while live video streaming and IPTV are multicast UDP applications.

[0052] Figure 2 A schematic diagram of data interaction of an OLT device according to an embodiment of the present invention is shown.

[0053] Reference Figure 2Application UDP packets are sent from the user terminal to the application server. These packets include unicast UDP packets and multicast UDP packets. The user terminal can send multicast UDP packets to the application server using a known multicast IP address. For unicast UDP packets, the user terminal first queries a DNS (Domain Name System) server to find the unicast IP address associated with the unicast UDP application's domain name (e.g., a website address), and then sends the unicast UDP packet to the application server using the found unicast IP address. For the OLT device, the data received by the user side includes application UDP packets and DNS request packets, while the data received by the network side includes DNS response packets.

[0054] In this embodiment, after determining the target user IP and the target application IP, the target UDP packets required for subsequent analysis can be filtered from the packets received by the OLT. Optionally, the target user IP and the target application IP can be set according to actual needs, and this embodiment does not limit this.

[0055] S12. If the receiving interval between adjacent packets in multiple target UDP packets is less than or equal to the interval time threshold, and the payload data length of all packets is less than or equal to the data length threshold, then these target UDP packets are determined to be heartbeat packets.

[0056] In UDP connectionless applications, heartbeat messages are used to keep users alive during data transmission, improving the reliability of data transmission between user terminals and application servers and reducing the redundant resource overhead on the application server for offline zombie users. Heartbeat messages can be sent from the application server to the user terminal, which then responds, or they can be sent proactively by the user terminal to the application server—that is, bidirectional or unidirectional transmission. Regardless of whether it's unidirectional or bidirectional transmission, a heartbeat message is sent from the user terminal to the application server; these heartbeat messages are included in the target UDP packet.

[0057] In this embodiment, based on the short length and short cycle of heartbeat messages, heartbeat messages are selected from target UDP messages according to the payload data length and the reception interval. The payload data is the data portion following the UDP message header, and the reception interval is the time difference between two adjacent target UDP messages received by the OLT device. A short reception interval indicates a short message transmission cycle. The payload data length and reception interval are easily obtained by the OLT device, resulting in low computational resource consumption.

[0058] S13. Record the reception interval between all adjacent heartbeat messages to obtain the heartbeat analysis array, calculate the average value of the heartbeat analysis array to obtain the heartbeat period, and calculate the standard deviation of the heartbeat analysis array to obtain the network jitter value.

[0059] In this embodiment, after filtering out heartbeat packets, the reception interval between adjacent heartbeat packets is used to form a heartbeat analysis array. The average value and standard deviation (also known as the root mean square deviation) of the heartbeat analysis array are used as the heartbeat period and network jitter value, respectively.

[0060] It should be noted that the heartbeat messages selected in the previous step appear in groups. The reception time interval between adjacent heartbeat messages is for each group of heartbeat messages. There are other messages between the last heartbeat message of a group and the first heartbeat message of the next group. Therefore, these two heartbeat messages are not the "adjacent heartbeat messages" as defined in this embodiment.

[0061] Optionally, after each group of target UDP packets is determined to be a group of heartbeat packets, the reception time interval of this group of target UDP packets is stored in the heartbeat analysis array until all target UDP packets within the preset time are detected, and a complete heartbeat analysis array is obtained.

[0062] S14. Select the receiving intervals from the heartbeat analysis array whose absolute value of the difference between the heartbeat period and the receiving interval is greater than the network jitter value, sum them up, obtain the total packet loss time, and calculate the ratio of the total packet loss time to the preset time to obtain the packet loss rate.

[0063] In this embodiment, when the receiving interval is greater than the heartbeat period and the difference is greater than the network jitter value, packet loss may have occurred between the two heartbeat packets. When the receiving interval is less than the heartbeat period and the absolute value of the difference is greater than the network jitter value, the heartbeat packets may be out of order. When the out-of-order delivery is severe, packet loss will also be severe. Therefore, the judgment criterion in this embodiment is based on the absolute value of the difference. The total packet loss time is obtained by summing the receiving intervals where the absolute value of the difference is greater than the network jitter value. The longer the total packet loss time within a preset time, the more severe the packet loss. The ratio of the total packet loss time to the preset time is used as the packet loss rate.

[0064] Therefore, this embodiment, based on the short length and short cycle of heartbeat packets, filters heartbeat packets from the target UDP packets received by the OLT device according to the payload data length and reception interval. Then, it further analyzes the network jitter value and packet loss rate based on the reception interval between adjacent heartbeat packets. This embodiment simplifies the poor quality index analysis model, eliminating the need for pre-deploying application content feature libraries and machine learning algorithms to analyze jitter and packet loss indicators. Furthermore, the necessary data for analysis is easily obtained through the OLT device, meeting the requirements for real-time monitoring and analysis. In addition, this embodiment has low hardware and software resource consumption and dependence, making it easy to implement.

[0065] It should be noted that the jitter and packet loss metrics of the network application quality analysis method provided in this embodiment are based on statistical calculations. The larger the sample size within the preset time period, the more accurate the analysis results. Therefore, this factor needs to be considered when setting the preset time, target user IP, and target application IP to obtain as many target UDP packets as possible.

[0066] Below are some optional examples for determining the target user IP and the target application IP.

[0067] Figure 3 A schematic diagram of the domain name validity determination process in one embodiment of the present invention is shown; Figure 4 The diagram illustrates a process for determining the target application IP and the target user IP in one embodiment of the present invention.

[0068] Reference Figures 2 to 4 In one embodiment, the method further includes the following steps before step S11:

[0069] Acquire DNS request and response messages received by the OLT device within a preset time period;

[0070] Based on DNS request and response messages, the number of requests, responses, and DNS response time for each domain name are counted.

[0071] For each domain name, the request success rate is obtained by calculating the ratio of the number of requests to the number of responses, and the average response time is obtained by calculating the average DNS response time.

[0072] If the success rate of a domain name request is greater than or equal to the success rate threshold, and the average response time is less than or equal to the response time threshold, then the domain name is determined to be a valid domain name, and the IP associated with the domain name is determined from the DNS response message of the domain name as a candidate IP.

[0073] Based on the access history of candidate IPs, determine the target application IP and its corresponding target user IP.

[0074] In this embodiment, to obtain the target application IP from the unicast IP, DNS request messages and DNS response messages are filtered from all messages received by the OLT device. Filtering is performed according to different domain names, and the DNS request messages and DNS response messages corresponding to each domain name are matched. The success rate of the request and the average response time are used as the judgment criteria. If the success rate of the request is less than the success rate threshold (e.g., 80%), or the average response time is greater than the response time threshold (e.g., 5s), the domain name is considered unavailable or illegal. The IP associated with the domain name must not belong to the target application IP. Otherwise, the domain name is a valid domain name, and its associated unicast IP (one or more) is used as candidate IPs. Then, based on the access status of the candidate IPs, the target application IP and its corresponding target user IP are determined.

[0075] Specifically, assuming a domain receives m requests and receives n responses within a preset time period, the success rate η = n / m. The timestamps of the OLT device receiving the DNS response message and its corresponding DNS request message are T and T, respectively. pi and T qi Each DNS response time is T pi -T qi The average response time is

[0076] Optionally, if the average response time of a domain name is greater than the response time threshold, its associated IP is added to the blacklist. Subsequent data streams whose destination IPs hit the blacklist are directly discarded without further analysis or processing.

[0077] Continue to refer to Figure 2 and Figure 4 In one embodiment, the method further includes the following steps before step S11:

[0078] Obtain the UDP multicast packets received by the OLT device within a preset time period. The source IP of the UDP multicast packet is the user IP, and the destination IP is the multicast IP.

[0079] UDP multicast packets with RTP encapsulation format and payload data length that is an integer multiple of 188 are identified as legitimate multicast packets, and the multicast IP corresponding to the legitimate multicast packets is selected as a candidate IP.

[0080] Based on the access history of candidate IPs, determine the target application IP and its corresponding target user IP.

[0081] In this embodiment, in order to obtain the target application IP in the multicast IP, UDP multicast packets are filtered out from all packets received by the OLT device. The legal multicast packets are selected based on the encapsulation format and payload data length. Their corresponding multicast IPs are used as candidate IPs. Then, based on the access status of the candidate IPs, the target application IP and its corresponding target user IP are determined.

[0082] Furthermore, in one embodiment, the step of determining the target application IP and its corresponding target user IP based on the access status of candidate IPs includes:

[0083] For each candidate IP, obtain the total number of bytes of UDP packets sent to it by each user IP within a preset time period;

[0084] If the total number of bytes is greater than or equal to the byte count threshold, the corresponding user IP and candidate IP will be determined as the target user IP and target application IP; or, the user IP and candidate IP corresponding to the largest number of total bytes will be determined as the target user IP and target application IP.

[0085] In this embodiment, the total number of bytes of UDP packets sent by a single user IP to a single candidate IP within a preset time period is counted. By setting a byte count threshold or sorting according to the total byte count (for example, the top three user IPs and candidate IPs ranked by total byte count from largest to smallest), the target application IPs with large access traffic within the preset time period and their corresponding target user IPs are selected, thereby ensuring the analysis sample size within the preset time period and improving the accuracy of the analysis results.

[0086] Furthermore, in one embodiment, the method further includes the following step before step S12:

[0087] The first interval time is obtained by calculating the average of the reception intervals of adjacent target UDP packets; the second interval time is obtained by calculating the average of the reception intervals shorter than the first interval time; and an interval time threshold is determined based on the second interval time; and / or

[0088] The first data length is obtained by calculating the average of the payload data lengths of the target UDP packets, and the second data length is obtained by calculating the average of the payload data lengths that are less than the first data length. The data length threshold is determined based on the second data length.

[0089] This embodiment provides a scheme for automatically calculating the corresponding threshold based on the collected data, avoiding the need to manually repeat the threshold setting when data characteristics change, thus improving convenience while ensuring the accuracy of the judgment. Optionally, the second interval time and the second data length can be directly set as the interval time threshold and the data length threshold, or they can be multiplied by a coefficient less than 1 (e.g., 90%) and then set as the interval time threshold and the data length threshold.

[0090] Furthermore, the procedure following step S14 also includes:

[0091] The number of bytes lost is calculated based on the total number of bytes in all target UDP packets and the packet loss rate.

[0092] The range of packet loss numbers is calculated based on the number of bytes lost and the typical length range of application messages.

[0093] In this embodiment, at the packet loss rate λ d Based on this, further consider the total number of bytes R of the target UDP packet. total Calculate the number of lost bytes L based on the typical length range ΔL of the application message. ossThe range of packet loss counts, ΔD, provides more packet loss metric parameters to meet diverse needs. Specifically, the above data satisfies the following relationship: λ d =R total / (R total +L oss ), ΔD=L oss / ΔL.

[0094] Furthermore, in one embodiment, step S11 is followed by:

[0095] Obtain the user's identity identifier from the target UDP packet;

[0096] The user's access location is determined based on the user's identity identifier.

[0097] In this embodiment, user identification, user access location, and network application quality poorness indicators are linked together to facilitate rapid identification and troubleshooting of quality poorness faults when reporting to the operator's management platform. Specifically, the user identification is the source MAC address, which is mapped to the corresponding user access location (PORT) in the MAC address table.

[0098] Optionally, the source and destination IPs, source and destination ports, source MAC addresses, and mirror ports of the target UDP packets are recorded to form a feature database table.

[0099] Furthermore, with a preset monitoring period, the system continuously analyzes the jitter and packet loss metrics when the target user accesses the target application. If there are frequent packet loss or jitter data jumps or the data exceeds the preset network stability threshold, it is considered that there is a quality fault in the network channel accessed by the user. By combining the user's access location corresponding to the user's identity, the fault location can be quickly located, and bandwidth scheduling resources can be adjusted in a timely manner. In combination with the user-side optical link parameters, optical attenuation, bit errors, and other network defects can be corrected.

[0100] Continue to refer to Figure 4 The network application quality degradation analysis method provided by this invention can be deployed on a general service resource card, which is connected to the OLT device as a quality degradation analysis card. In UDP network application scenarios with encrypted data content, the quality degradation analysis card automatically extracts and identifies target data from the mirrored data streams of the OLT service cards (1 to n), and uses big data learning to calculate statistically significant jitter and packet loss indicators, which are reported to the operator's management platform in real time. Subsequently, the monitoring data and empirical benchmark data are compared, combined with user-side optical network quality degradation indicators (such as optical power, bit error rate, and guaranteed bandwidth), to define the scope of quality degradation faults in a user's network application, such as those located from the ONU (Optical Network Unit) to the OLT service line card, from the OLT service line card to the OLT, and from the OLT uplink to the upper-layer backbone network. At the same time, it provides possible specific causes and repair solutions for packet loss and jitter for the operator to choose from.

[0101] Secondly, embodiments of the present invention also provide a network application quality analysis device.

[0102] In one embodiment, the network application quality analysis device includes:

[0103] The target packet acquisition module is used to acquire the target UDP packets received by the OLT device within a preset time. The source IP of the target UDP packet is the target user IP, and the destination IP is the target application IP.

[0104] The heartbeat message judgment module is used to determine that if the receiving interval between adjacent messages in multiple target UDP messages is less than or equal to the interval time threshold, and the payload data length of all messages is less than or equal to the data length threshold, then these target UDP messages are heartbeat messages.

[0105] The heartbeat message analysis module is used to record the reception interval time between all adjacent heartbeat messages to obtain a heartbeat analysis array, calculate the average value of the heartbeat analysis array to obtain the heartbeat period, and calculate the standard deviation of the heartbeat analysis array to obtain the network jitter value.

[0106] The packet loss analysis module is used to filter out the receiving intervals from the heartbeat analysis array whose absolute value of the difference between the heartbeat period and the receiving interval is greater than the network jitter value, sum them up to obtain the total packet loss time, and calculate the ratio of the total packet loss time to the preset time to obtain the packet loss rate.

[0107] Furthermore, in one embodiment, the network application quality poor analysis device further includes a target information determination module, used for:

[0108] Acquire DNS request and response messages received by the OLT device within a preset time period;

[0109] Based on DNS request and response messages, the number of requests, responses, and DNS response time for each domain name are counted.

[0110] For each domain name, the request success rate is obtained by calculating the ratio of the number of requests to the number of responses, and the average response time is obtained by calculating the average DNS response time.

[0111] If the success rate of the domain name requests is greater than or equal to the success rate threshold, and the average response time is less than or equal to the response time threshold, then the domain name is determined to be a valid domain name, and the IP associated with the domain name is determined from the DNS response message of the domain name as a candidate IP.

[0112] Based on the access history of the candidate IPs, the target application IP and its corresponding target user IP are determined.

[0113] Furthermore, in one embodiment, the network application quality poor analysis device further includes a target information determination module, used for:

[0114] Obtain the UDP multicast packets received by the OLT device within a preset time period. The source IP of the UDP multicast packet is the user IP, and the destination IP is the multicast IP.

[0115] UDP multicast packets with an RTP encapsulation format and a payload data length that is an integer multiple of 188 are identified as legitimate multicast packets, and the multicast IP corresponding to the legitimate multicast packet is selected as a candidate IP.

[0116] Based on the access history of the candidate IPs, the target application IP and its corresponding target user IP are determined.

[0117] Furthermore, in one embodiment, the target information determination module is used to:

[0118] For each candidate IP, obtain the total number of bytes of UDP packets sent to it by each user IP within a preset time period;

[0119] If the total number of bytes is greater than or equal to the byte count threshold, then the corresponding user IP and the candidate IP are determined as the target user IP and the target application IP; or, the user IPs corresponding to the largest number of total bytes and the candidate IPs are determined as the target user IP and the target application IP.

[0120] Furthermore, in one embodiment, the network application quality poor analysis device further includes a threshold determination module, used for:

[0121] The first interval time is obtained by calculating the average of the reception intervals of adjacent target UDP packets; the second interval time is obtained by calculating the average of the reception intervals shorter than the first interval time; and an interval time threshold is determined based on the second interval time; and / or

[0122] The first data length is obtained by calculating the average value of the payload data length of the target UDP packet, and the second data length is obtained by calculating the average value of the payload data lengths that are less than the first data length. The data length threshold is determined based on the second data length.

[0123] Furthermore, in one embodiment, the packet loss analysis module further includes:

[0124] The number of bytes lost is calculated based on the total number of bytes in all target UDP packets and the packet loss rate.

[0125] The range of packet loss numbers is calculated based on the number of lost bytes and the typical length range of application messages.

[0126] Furthermore, in one embodiment, the network application quality poor analysis device further includes a user information acquisition module, used for:

[0127] Obtain the user's identity identifier from the target UDP packet;

[0128] The user's access location is determined based on the user's identity identifier.

[0129] The functions of each module in the above-mentioned network application quality poor analysis device correspond to the steps in the above-mentioned network application quality poor analysis method embodiment, and their functions and implementation processes will not be described in detail here.

[0130] Thirdly, embodiments of the present invention provide a network application quality poor analysis device, which can be a personal computer (PC), laptop computer, server or other device with data processing capabilities.

[0131] Figure 5 A schematic diagram of the hardware structure of a network application quality analysis device according to an embodiment of the present invention is shown.

[0132] Reference Figure 5 In this embodiment of the invention, the network application quality analysis device may include a processor 1001 (e.g., a Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components; the user interface 1003 may include a display screen or an input unit such as a keyboard; the network interface 1004 may optionally include a standard wired interface or a wireless interface (e.g., Wireless Fidelity, Wi-Fi); the memory 1005 may be high-speed random access memory (RAM) or stable memory (non-volatile memory), such as a disk storage device. Alternatively, the memory 1005 may also be a storage device independent of the aforementioned processor 1001. Those skilled in the art will understand that… Figure 5 The hardware structure shown does not constitute a limitation of the invention and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0133] Continue to refer to Figure 5 , Figure 5The memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a network application quality analysis program. The processor 1001 can call the network application quality analysis program stored in the memory 1005 and execute the network application quality analysis method provided in this embodiment of the invention.

[0134] Fourthly, embodiments of the present invention also provide a readable storage medium.

[0135] The present invention provides a network application quality analysis program stored on a readable storage medium, wherein when the network application quality analysis program is executed by a processor, it implements the steps of the network application quality analysis method described above.

[0136] The method implemented when the network application quality analysis program is executed can be referred to in various embodiments of the network application quality analysis method of the present invention, and will not be repeated here.

[0137] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0138] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0139] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of the present invention.

[0140] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A method for analyzing poor network application quality, characterized in that, The network application quality poor analysis method includes: Obtain the target UDP packets received by the OLT device within a preset time period. The source IP of the target UDP packet is the target user IP, and the destination IP is the target application IP. If the receiving interval between adjacent packets in multiple target UDP packets is less than or equal to the interval time threshold, and the payload data length of all packets is less than or equal to the data length threshold, then these target UDP packets are determined to be heartbeat packets. Record the reception interval between all adjacent heartbeat packets to obtain a heartbeat analysis array, calculate the average value of the heartbeat analysis array to obtain the heartbeat period, and calculate the standard deviation of the heartbeat analysis array to obtain the network jitter value; The receiving intervals whose absolute difference from the heartbeat period is greater than the network jitter value are selected from the heartbeat analysis array and summed to obtain the total packet loss time. The packet loss rate is obtained by calculating the ratio of the total packet loss time to the preset time.

2. The network application quality poor analysis method as described in claim 1, characterized in that, The method further includes the following steps before the step of obtaining the target UDP packets received by the OLT device within a preset time: Acquire DNS request and response messages received by the OLT device within a preset time period; Based on DNS request and response messages, the number of requests, responses, and DNS response time for each domain name are counted. For each domain name, the request success rate is obtained by calculating the ratio of the number of requests to the number of responses, and the average response time is obtained by calculating the average DNS response time. If the success rate of the domain name requests is greater than or equal to the success rate threshold, and the average response time is less than or equal to the response time threshold, then the domain name is determined to be a valid domain name, and the IP associated with the domain name is determined from the DNS response message of the domain name as a candidate IP. Based on the access history of the candidate IPs, the target application IP and its corresponding target user IP are determined.

3. The network application quality poor analysis method as described in claim 1, characterized in that, The method further includes the following steps before the step of obtaining the target UDP packets received by the OLT device within a preset time: Obtain the UDP multicast packets received by the OLT device within a preset time period. The source IP of the UDP multicast packet is the user IP, and the destination IP is the multicast IP. UDP multicast packets with an RTP encapsulation format and a payload data length that is an integer multiple of 188 are identified as legitimate multicast packets, and the multicast IP corresponding to the legitimate multicast packet is selected as a candidate IP. Based on the access history of the candidate IPs, the target application IP and its corresponding target user IP are determined.

4. The network application quality poor analysis method as described in claim 2 or 3, characterized in that, The step of determining the target application IP and its corresponding target user IP based on the access status of the candidate IPs includes: For each candidate IP, obtain the total number of bytes of UDP packets sent to it by each user IP within a preset time period; If the total number of bytes is greater than or equal to the byte count threshold, then the corresponding user IP and the candidate IP are determined as the target user IP and the target application IP; or, the user IPs corresponding to the largest number of total bytes and the candidate IPs are determined as the target user IP and the target application IP.

5. The network application quality poor analysis method as described in any one of claims 1 to 4, characterized in that, Before the step of determining that these target UDP packets are heartbeat packets if, in a plurality of target UDP packets, the receiving interval between adjacent packets is less than or equal to an interval threshold, and the payload data length of all packets is less than or equal to a data length threshold, the following steps are included: The first interval time is obtained by calculating the average of the reception intervals of adjacent target UDP packets; the second interval time is obtained by calculating the average of the reception intervals shorter than the first interval time; and an interval time threshold is determined based on the second interval time; and / or The first data length is obtained by calculating the average value of the payload data length of the target UDP packet, and the second data length is obtained by calculating the average value of the payload data lengths that are less than the first data length. The data length threshold is determined based on the second data length.

6. The network application quality poor analysis method as described in any one of claims 1 to 4, characterized in that, After the step of calculating the ratio of the total packet loss time to the preset time to obtain the packet loss rate, the method further includes: The number of bytes lost is calculated based on the total number of bytes in all target UDP packets and the packet loss rate. The range of packet loss numbers is calculated based on the number of lost bytes and the typical length range of application messages.

7. The network application quality poor analysis method as described in any one of claims 1 to 4, characterized in that, Following the step of obtaining the target UDP packets received by the OLT device within a preset time, the method further includes: Obtain the user's identity identifier from the target UDP packet; The user's access location is determined based on the user's identity identifier.

8. A network application quality poor analysis device, characterized in that, The network application quality analysis device includes: The target packet acquisition module is used to acquire the target UDP packets received by the OLT device within a preset time. The source IP of the target UDP packet is the target user IP, and the destination IP is the target application IP. The heartbeat message judgment module is used to determine that if the receiving interval between adjacent messages in multiple target UDP messages is less than or equal to the interval time threshold, and the payload data length of all messages is less than or equal to the data length threshold, then these target UDP messages are heartbeat messages. The heartbeat message analysis module is used to record the reception interval time between all adjacent heartbeat messages to obtain a heartbeat analysis array, calculate the average value of the heartbeat analysis array to obtain the heartbeat period, and calculate the standard deviation of the heartbeat analysis array to obtain the network jitter value. The packet loss analysis module is used to filter out the receiving intervals from the heartbeat analysis array whose absolute value of the difference between the heartbeat period and the receiving interval is greater than the network jitter value, sum them up to obtain the total packet loss time, and calculate the ratio of the total packet loss time to the preset time to obtain the packet loss rate.

9. A network application quality analysis device, characterized in that, The network application quality analysis device includes a processor, a memory, and a network application quality analysis program stored in the memory and executable by the processor, wherein when the network application quality analysis program is executed by the processor, it implements the steps of the network application quality analysis method as described in any one of claims 1 to 7.

10. A readable storage medium, characterized in that, The readable storage medium stores a network application quality analysis program, wherein when the network application quality analysis program is executed by a processor, it implements the steps of the network application quality analysis method as described in any one of claims 1 to 7.

Images