CN117354186A

CN117354186A - Network line quality monitoring method, device, equipment and storage medium

Info

Publication number: CN117354186A
Application number: CN202311307233.1A
Authority: CN
Inventors: 瞿毅力; 李云龙; 龙晓颖; 裴斐
Original assignee: China Merchants Bank Co Ltd
Current assignee: China Merchants Bank Co Ltd
Priority date: 2023-10-09
Filing date: 2023-10-09
Publication date: 2024-01-05

Abstract

The invention discloses a network line quality monitoring method, a device, equipment and a storage medium, and belongs to the technical field of network quality monitoring. The network line quality monitoring method comprises the steps of acquiring a monitoring time period and a plurality of single line monitoring task data acquired by a simple network management protocol acquisition unit aiming at a monitoring line of access equipment; determining all target single task execution time and all target single task quality index data corresponding to the same opposite-end interface address data from a plurality of single line monitoring task data; and aiming at the same opposite-end interface address data, obtaining the line continuous monitoring data of the line monitoring item in the monitoring time period based on the target single task execution time and all the target single task quality index data in the monitoring time period. The method realizes the effective monitoring of network abnormal conditions such as network continuous packet loss, network continuous time delay exceeding threshold value and the like.

Description

Network line quality monitoring method, device, equipment and storage medium

Technical Field

The present invention relates to the field of network quality monitoring, and in particular, to a method, an apparatus, a device, and a storage medium for monitoring network line quality.

Background

In the field of network quality monitoring, accurate, real-time and stable monitoring is required for network line quality monitoring. In the related art, the collection of network delay and packet loss rate in the network line is mainly implemented by using pulling (Remote Ping) technology for sending a Ping command to a target host through a network and obtaining a response, NQA (Network Quality Analyzer, a network quality monitoring technology), SQA (Service Quality Assurance, a technology for comprehensively managing network service quality), ipla (IP Service Level Agreement, a network management technology) and other dial-up measurement technologies.

However, the related technology can only complete the instantaneous index acquired at the time, and cannot realize effective monitoring of network abnormal scenes such as continuous packet loss of the network, super-threshold of continuous time delay of the network and the like.

Disclosure of Invention

The invention mainly aims to provide a network line quality monitoring method, device, equipment and storage medium, and aims to solve the technical problem that related technologies cannot effectively monitor network abnormal scenes such as network continuous packet loss, network continuous time delay exceeding a threshold value and the like.

In order to achieve the above object, the present invention provides a network line quality monitoring method, including:

Acquiring a monitoring time period and a plurality of single line monitoring task data acquired by a simple network management protocol acquisition unit aiming at a monitoring line of an access device; the single line monitoring task data comprise single task execution time, acquisition task execution sequence numbers, opposite-end interface address data connected with the access equipment and single task quality index data;

determining all target single task execution time and all target single task quality index data corresponding to the same interface address data from a plurality of single line monitoring task data;

aiming at the same interface address data of the opposite interfaces, based on the target single task execution time and all target single task quality index data in the monitoring time period, obtaining the line continuous monitoring data of the line monitoring item in the monitoring time period

Optionally, determining all target single task execution times and all target single task quality index data corresponding to the same interface address data from the plurality of single line monitoring task data includes:

acquiring opposite-end interface address result data and single-task quality index result data based on a plurality of single-time line monitoring task data; the method comprises the steps of obtaining interface address result data and single task quality index result data, wherein the interface address result data and the single task quality index result data are key value pairs, attribute keys of the interface address result data and the single task quality index result data are object identifiers, character ASCII codes of parameter values of task configuration items, character ASCII codes of single dial test collection task names, collection task execution serial numbers and collection result codes obtained by task type splicing, attribute values of the interface address result data are interface address data, and attribute values of the single task quality index result data are single task quality index data;

Traversing the interface address result data of the opposite end, determining all target acquisition result codes corresponding to the interface address data of the same opposite end, and obtaining a first key value pair; wherein, the attribute keys of the first key value pair are the same pair interface address data, and the attribute values are target acquisition result codes;

and inquiring single task quality index result data based on the target acquisition result codes, and determining all target single task execution time and all target single task quality index data corresponding to the same opposite-end interface address data.

Optionally, before acquiring the monitoring time period and the plurality of single line monitoring task data collected by the simple network management protocol collector for the monitoring line of the access device, the method further includes:

acquiring line monitoring item data, dial testing global configuration parameters and alarm index data of a line monitoring item; the dial-up global configuration parameters comprise detection task frequency, detection message quantity and message sending interval, the alarm index data are related to single task quality index data, and the line monitoring item data comprise an access interface address and an opposite interface address;

determining a dial testing configuration template and a dial testing task checking instruction corresponding to the application technology type of the access equipment; the application technology type is a network quality analysis NQA type, an Internet protocol service level protocol IPSLA type or a network line quality assurance SQA type;

Filling a dial testing configuration template based on the line monitoring item data, dial testing global configuration parameters and alarm index data to obtain dial testing task configuration content of the line monitoring item;

and transmitting the configuration content of the dial testing task and the checking instruction of the dial testing task of the single line monitoring task to the access equipment through the equipment operation layer.

Optionally, issuing, by the device operation layer, a dial testing task configuration content and a dial testing task inspection instruction of the single line monitoring task to the access device, including:

issuing a dial testing task checking command to the access equipment through the equipment operation layer;

if the execution feedback content of the dial testing task checking command is obtained, judging whether the same-name task of the single line monitoring task exists or not according to the execution feedback content;

if the configuration content does not exist, transmitting a dial testing task configuration content to the access equipment through the equipment operation layer, and returning to execute a dial testing task checking command transmitted to the access equipment through the equipment operation layer;

if yes, the single dial testing task is determined to be successfully configured in the access equipment.

Optionally, for the same pair of interface address data, after obtaining the line continuous monitoring data of the line monitoring item in the monitoring period based on the target single task execution time and all the target single task quality index data in the monitoring period, the method further includes:

If the single task packet loss rate in the at least 1 target single task quality index data is 100%, triggering a line interruption alarm event;

if the line interruption alarm event is not triggered, judging whether the average multi-task packet loss rate in the line continuous monitoring data is greater than or equal to a first preset alarm threshold value;

if the average packet loss rate of the continuous multiple tasks is larger than or equal to the first preset alarm threshold value, triggering an alarm event with the average packet loss rate exceeding the threshold value;

if the line interruption alarm event and the average packet loss rate of a plurality of continuous tasks exceed the threshold alarm event are not triggered, judging whether the packet loss rate of a single task is greater than or equal to a second preset alarm threshold;

and if the packet loss rate exceeds the threshold value, triggering a packet loss rate exceeding threshold value alarm event.

if the line interruption alarm event is not triggered, judging whether the average time delay of the multitasking in the line continuous monitoring data is larger than or equal to a third preset alarm threshold value;

If the average time delay of the continuous tasks is greater than or equal to the third preset alarm threshold value, triggering an alarm event with the average time delay exceeding the threshold value;

if the line interruption alarm event and the average time delay of a plurality of continuous tasks exceed the threshold value alarm event are not triggered, judging whether the single task time delay in at least 1 target single task quality index data is larger than or equal to a fourth preset alarm threshold value;

if so, triggering a time delay exceeding a threshold value alarm event.

acquiring the actual acquisition quantity and the theoretical acquisition quantity of single line monitoring task data acquired by a simple network management protocol acquisition unit aiming at a monitoring line within a preset duration;

and if the actual acquisition number is smaller than the theoretical acquisition number, triggering a dial testing acquisition data missing alarm event.

In addition, to achieve the above object, the present invention further provides a network line quality monitoring device, including:

the monitoring task data acquisition module is used for acquiring a monitoring time period and a plurality of single line monitoring task data acquired by the simple network management protocol acquisition unit aiming at a monitoring line of the access equipment;

The first data analysis module is used for determining all target single task execution time and all target single task quality index data corresponding to the same interface address data from a plurality of single line monitoring task data;

the second data analysis module is used for obtaining the line continuous monitoring data of the line monitoring item in the monitoring time period based on the target single task execution time and all target single task quality index data in the monitoring time period aiming at the same opposite-end interface address data.

In addition, to achieve the above object, the present invention also provides a network line quality monitoring device, including: the system comprises a memory, a processor and a network line quality monitoring program stored on the memory and executable on the processor, wherein the network line quality monitoring program is configured to implement the steps of the network line quality monitoring method as described above.

In addition, in order to achieve the above object, the present invention further provides a computer readable storage medium, on which a network line quality monitoring program is stored, which when executed by a processor, implements the steps of the network line quality monitoring method as described above.

The invention provides a network line quality monitoring method, which comprises the following steps: acquiring a monitoring time period and a plurality of single line monitoring task data acquired by a simple network management protocol acquisition unit aiming at a monitoring line of an access device; determining all target single task execution time and all target single task quality index data corresponding to the same interface address data from a plurality of single line monitoring task data; and aiming at the same interface address data of the opposite ends, obtaining the continuous line monitoring data of the line monitoring item in the monitoring time period based on the target single task execution time and all target single task quality index data in the monitoring time period.

Therefore, according to the opposite-end interface address data in the line monitoring task data, all target single task quality index data and all target single task execution time are determined from a plurality of continuous single line monitoring task data. On the basis, the continuous monitoring data of the lines such as the average packet loss rate and the average time delay of the network lines in the monitoring time period can be obtained, so that the effective monitoring of network abnormal scenes such as the continuous packet loss rate and the continuous time delay exceeding the threshold value is realized.

Drawings

FIG. 1 is a schematic diagram of a network line quality monitoring device of a hardware operating environment according to an embodiment of the present invention;

fig. 2 is a flowchart of a first embodiment of a network line quality monitoring method according to the present invention;

FIG. 3 is a flowchart of a second embodiment of the network line quality monitoring method of the present invention;

FIG. 4 is a flowchart of a third embodiment of a network line quality monitoring method according to the present invention;

FIG. 5 is a flowchart of a fourth embodiment of a network line quality monitoring method according to the present invention;

fig. 6 is a flowchart of a fifth embodiment of a network line quality monitoring method according to the present invention;

fig. 7 is a schematic flow chart of an example 1 of the network line quality monitoring method of the present invention;

fig. 8 is a schematic flow chart of an example 2 of the network line quality monitoring method of the present invention;

fig. 9 is a flowchart illustrating an example 3 of a network line quality monitoring method according to the present invention;

fig. 10 is a schematic diagram of an architecture of an example 4 of the network line quality monitoring method of the present invention;

fig. 11 is a schematic functional block diagram of a first embodiment of a network line quality monitoring method according to the present invention.

The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.

Detailed Description

It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.

Analysis of the related art shows that, currently, a general RPING monitoring mode is generally based on Telnet Protocol (text-based Telnet Protocol) or SSH (Secure Shell Protocol a Protocol for secure Telnet and file transfer) Protocol, AAA (Authentication, authorization, accounting) authentication service or other authentication modes, and ICMP (Internet Control Message Protocol ) Protocol, which implements logging in a line access device first and then initiates a certain size and number of probe messages to an opposite end according to a set PING (a computer network tool) parameter, and determines connectivity of a line and analyzes line quality through number of packets and time. In the invention, the service realizing network equipment login, command issuing and feedback receiving through a Telnet protocol or an SSH protocol, an AAA authentication service or other authentication modes is called an equipment operation layer, and the equipment operation layer can be used for remote operation and configuration acquisition of network equipment.

Because the RPING mode needs to log in the device through the device operation layer every time, and the frequently logged in device issuing command needs to consume higher device resources and performance, and the frequently logged in device and issuing command may have other potential risks, the upper limit of the detection frequency of the RPING mode is lower, the upper limit of the detection frequency of the general RPING data is about 3 minutes/time, about 20 detection data packets can be sent every time, and the higher frequency message number is likely to affect the device performance to cause a security event or be unable to be executed in the detection interval. Under many business scenes with high concurrency of big data, the data collection amount is insufficient to effectively judge the line quality in terms of the safety configuration of detecting 20 packets every 3 minutes, and the collection frequency cannot meet the requirement of emergency operation. The conventional RPING monitoring scheme is not flexible enough in index dimension because a threshold is set to judge the line quality through the packet loss rate and the time delay index. Under the configuration that 20 detection data packets are sent each time, the timeout time of a single RPING task is about 20 seconds, the RPING acquisition tasks are backlogged when a plurality of lines are interrupted, part of the RPING tasks can not be executed in the acquisition period, and the acquired data is empty. The RPING depends on a device operation layer, the SSH of the device operation layer logs in the network device and depends on AAA authentication service, the failure of the device operation layer and the AAA service can lead to a large number of lines RPING to be unable to collect data and to cause monitoring failure, and extreme conditions can lead to influencing the global line RPING. The reasons for the degradation of the quality of the line (network link) may be that the operator transmits equipment failure, the quality of the line of the last kilometer, the failure of the network equipment of the opposite end (partner) and the like, and the local network equipment index cannot directly find the line failure, so that the real-time performance of the RPING is not high except when the RPING is used for the interruption of the line monitoring item, and the quality degradation of the line (network link) cannot be effectively monitored because the collected data quantity is insufficient.

In summary, the RPING monitoring mode cannot meet the requirements of sensitivity, instantaneity, accuracy and stability of the line quality monitoring in many current scenes.

PING command detection based on ICMP is also used, and most of network devices of mainstream brands provide active dial-up detection functions of periodic detection, such as NQA technology, ipla technology and SQA technology. NQA, SQA, IPSLA can periodically initiate PING detection by configuring parameters such as source end information and destination end information of a detection link on equipment, and can support acquisition of detection results through SNMP (Simple Network Management Protocol simple network management protocol) protocol. However, because the technologies and functions supported by the network devices of all manufacturers are not uniform, the device configuration and configuration parameters required for realizing the same monitoring effect are greatly different, and currently, there are no unified monitoring products and schemes for the three main flow dial testing functions of compatibility adaptation NQA, SQA, IPSLA.

In view of the technical problems that various dial testing technologies in the related art cannot be compatible and complex scenes such as continuous packet loss of a network and super-threshold of continuous time delay of the network cannot be dealt with, the invention provides a network line quality monitoring method.

The method, the device, the equipment and the storage medium for monitoring the network line quality are described in detail by specific examples and implementation modes with reference to the attached drawings.

Referring to fig. 1, fig. 1 is a schematic structural diagram of a network line quality monitoring device in a hardware running environment according to an embodiment of the present invention.

As shown in fig. 1, the network line quality monitoring apparatus may include: a processor 1001, such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, a memory 1005. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display, an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may further include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WIreless-FIdelity (WI-FI) interface). The Memory 1005 may be a high-speed random access Memory (Random Access Memory, RAM) Memory or a stable nonvolatile Memory (NVM), such as a disk Memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.

Those skilled in the art will appreciate that the architecture shown in fig. 1 is not limiting of the network line quality monitoring device and may include more or fewer components than shown, or may combine certain components, or may be a different arrangement of components.

As shown in fig. 1, an operating system, a data storage module, a network communication module, a user interface module, and a network line quality monitoring program may be included in a memory 1005, which is a computer-readable storage medium.

In the network line quality monitoring device shown in fig. 1, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the network line quality monitoring device of the present invention may be disposed in the network line quality monitoring device, and the network line quality monitoring device invokes the network line quality monitoring program stored in the memory 1005 through the processor 1001 and executes the network line quality monitoring method provided by the embodiment of the present invention.

An embodiment of the present invention provides a network line quality monitoring method, and referring to fig. 2, fig. 2 is a flow chart of a first embodiment of a network line quality monitoring method according to the present invention.

In this embodiment, the network line quality monitoring method includes:

step S500: and acquiring a monitoring time period and a plurality of single line monitoring task data acquired by the simple network management protocol acquirer aiming at a monitoring line of the access equipment.

In particular, in the process of monitoring the quality of network lines, each access device typically involves a plurality of network interfaces, and each network line corresponding to each network interface is a line monitoring item. The line monitoring task data can be obtained by acquiring the line monitoring task data once for each line monitoring item. And continuously collecting line monitoring task data for the target line monitoring item to obtain a plurality of single line monitoring task data and monitoring time periods for subsequent analysis and processing.

The simple network management protocol collector is used for acquiring line monitoring item data at fixed time according to the established timing task, traversing the line monitoring item on the basis, and initiating a collection request to the corresponding access equipment to obtain a collection result, namely single line monitoring task data. The collector may be any one of device data collection services employing SNMP protocol.

The single line monitoring task data comprises single task execution time, acquisition task execution sequence numbers, opposite port interface address data connected with the access equipment, single task quality index data and other information. The single-task quality index data is an acquisition result corresponding to the network line quality monitoring index, and in a specific scene, the single-task quality index data can be network quality monitoring indexes such as packet loss rate, time delay, bandwidth, jitter, throughput or network availability.

Step S600: and determining all target single task execution time and all target single task quality index data corresponding to the same interface address data from the plurality of single line monitoring task data.

Specifically, after a plurality of continuous single-time line monitoring task data are obtained, analysis is performed to obtain a set of single-time task quality index data. And acquiring the corresponding target single task execution time and target single task quality index data from the set according to the opposite port interface address in each single line monitoring task data.

Further, as an embodiment, step S600 specifically includes the following steps:

step S610: acquiring opposite-end interface address result data and single-task quality index result data based on a plurality of single-time line monitoring task data;

step S620: traversing the interface address result data of the opposite end, determining all target acquisition result codes corresponding to the interface address data of the same opposite end, and obtaining a first key value pair;

step S630: and inquiring single task quality index result data based on the target acquisition result codes, and determining all target single task execution time and all target single task quality index data corresponding to the same opposite-end interface address data.

Specifically, in the present embodiment, in order to obtain the target single-task execution time and the target single-task quality index data, it is necessary to separate the interface address result data and the single-task quality index result data from the single-line monitoring task data.

The opposite-end interface address result data and the single task quality index result data exist in the form of key value pairs. The attribute keys of the opposite-end interface address result data and the single-task quality index result data are all acquisition result codes formed by splicing a plurality of related acquisition result parameters, wherein the related acquisition result parameters can be at least one of an object identifier, a character ASCII code of a parameter value of a task configuration item, a character ASCII code of a single dial testing acquisition task name, an acquisition task execution sequence number or a task type. The attribute value of the opposite-end interface address result data is the opposite-end interface address data, and the attribute value of the single-task quality index result data is the single-task quality index data.

After the opposite port interface address result data and the single task quality index result data are obtained through separation, traversing all the opposite port interface address result data to obtain all the opposite port interface address data. And constructing a first key value pair by taking the obtained opposite port interface address data as an attribute key and the corresponding acquisition result number as an attribute value.

Traversing the first key value pair to obtain a target acquisition result code list, sequencing the target acquisition result codes according to the acquisition task execution sequence numbers contained in the target acquisition result code list from low to high, continuing traversing the sequenced target acquisition result code list to obtain the target acquisition result code currently traversed, inquiring single task quality index result data by taking the target acquisition result code as an inquiry condition, and determining all target single task execution time and all target single task quality index data corresponding to the opposite port interface address data.

Step S700: and aiming at the same interface address data of the opposite ends, obtaining the line continuous monitoring data of the line monitoring item in the monitoring time period based on the target single task execution time and all target single task quality index data in the monitoring time period.

Specifically, after the execution time of all target single tasks and the quality index data of all target single tasks of the same opposite-end interface address data are obtained, the initial monitoring time of a plurality of continuous tasks can be calculated according to the current time of the system, then all the quality index data of the target single tasks between the initial monitoring time and the current time are obtained, and the average value is obtained to obtain the corresponding line continuous monitoring data.

For example: in a specific application scenario, the method is executed on the premise that the access equipment has completed opening of SNMP protocol functions, completes configuration of dial test SNMP collector service IP, supported SNMP protocol version and unified SNMP group name (community), and completes strategy opening of network interview with the dial test SNMP collector.

The dial testing SNMP collector creates a timing task according to the set SNMP collection frequency, acquires latest dial testing configuration state as 'successful issuing' line monitoring item data at fixed time, traverses line monitoring items, initiates SNMP collection requests to equipment according to given OID, access equipment information, SNMP group names, SNMP version numbers and other SNMP protocols to be configured uniformly, receives a response collection result, packages single task execution time, traversed current line monitoring item data and collection result, and finally transmits the current line monitoring item data to dial testing data consumption service processing through an interface or message middleware such as kafka.

In the method, the OID to be collected by each technical type of equipment is as follows:

NQA (first class) set of OIDs to be acquired:

NQA (second class) set of OIDs to be acquired:

OID	index name	Meaning of index
			1.3.6.1.4.1.25506.8.3.1.11.1.3	hh3cNqaStatResIpTargetAddress	Destination address
1.3.6.1.4.1.25506.8.3.1.11.1.6	hh3cNqaStatResAverageRtt	Average time delay
			1.3.6.1.4.1.25506.8.3.1.11.1.19	hh3cNqaStatResLostPacketRatio	Packet loss rate

Set of OIDs required to be acquired by ipla:

OID group required to be collected by SQA:

in addition, an acquisition result database can be set in the network line quality monitoring system, and the single task quality index data is stored in the acquisition result database, for example, the single task execution time, the line monitoring item data, the acquisition task execution sequence number, the time delay D and the packet loss rate LR data are included. Consumption of the collected data is achieved through the answering interface or the message middleware, after the collected data is consumed, the consumed collected data is analyzed, and the line monitoring items and the collection results are separated. The method specifically comprises the following steps:

acquisition results for NQA (first class) devices:

step one: and separating and obtaining the acquisition results of the nqaResultsAddress, nqaResultsRttAvg, nqaResultsLostPacketRatio three indexes from the acquisition data. The three collection results are all data by using ASCII codes of OID and NQA task test-instance configuration item parameter VALUEs (the VALUEs are uniformly set as 'admin' in the example), collection task name ASCII codes, collection task execution serial numbers and collection result IDs of one integer task type which are spliced by 'KEY', and KEY VALUE pairs of corresponding index collection results as VALUEs (VALUE). The nqaResultsAddress is VALUE, nqaResultsRttAvg as a target interface address configured by tasks, VALUE, nqaResultsLostPacketRatio as an average time delay millisecond VALUE and VALUE as an integer packet loss rate.

Step two: traversing nqaaResultsAddress acquisition results, and constructing data IP_IDS_MAP by taking a target interface address as a KEY and acquiring a KEY VALUE of which the result ID is VALUE.

Step three: traversing the KEY value pair IP_IDS_MAP to obtain an acquisition result ID list of each target interface address, sequencing the acquisition result ID list from low to high according to the acquisition task execution sequence number contained in each item of ID, continuing traversing the sequenced acquisition result ID list to obtain the currently traversed acquisition result ID, and inquiring nqaResulttsRttAvg and nqaResulttsLostPacketRatio by taking the acquisition result ID as a KEY to obtain single-task quality index data.

Acquisition results for NQA (second class) devices:

step one: the acquisition results of three indexes of hh3cNqaStatResIpTargetAddress, hh3cNqaStatResAverageRtt, hh cNqaStatRacesLostPacketRatio are separated from the acquisition data. The three acquisition results are all data by taking an ASCII code of an OID and NQA task entry configuration item parameter VALUE (the VALUE is uniformly set as ' admin ' in the example), an ASCII code of an acquisition task name and an acquisition task execution sequence number which are spliced by ' KEY (KEY) and taking a KEY VALUE pair of which the corresponding index acquisition result is a VALUE (VALUE). The destination address configured by the following NQA task is a VALUE by the following data type prefix ' STRING: ' the hh3cNqaStatRESAVERAGERt is a VALUE by the following data type prefix ' Gauge32: ' the millisecond VALUE of the following average time delay is a VALUE by the following data type prefix ' hh3cNqaStatRESLostPacketRatio is a VALUE by the following data type prefix ' Gauge32: ' the following integer packet loss rate is a VALUE by the following data type prefix ' Gauge32 '.

Step two: traversing the collection result of the hh3 cNqaStatRESTRIPTARGETAGEADDRESS, and constructing the data IP_IDS_MAP by taking the destination address as a KEY and taking the KEY VALUE of the collection result ID list as a VALUE.

Step three: traversing the KEY value pairs IP_IDS_MAP to obtain an acquisition result ID list of each destination IP, sequencing the acquisition result ID list from low to high according to the acquisition task execution sequence number contained in each item of ID, continuing traversing the sequenced acquisition result ID list to obtain the currently traversed acquisition result ID, and inquiring two KEY value pairs of hh3 cNqaStatRacesAverage Rt and hh3 cNqaStatRastPacketRatio by taking the acquisition result ID as a KEY to obtain single-task quality index data.

Acquisition results for ipsela devices:

step one: and separating and obtaining the acquisition results of the rttMonHistoryCollectionAddress, rttMonHistoryCollectionCompletionTime, ttMonHistoryCollectionSense three indexes from the acquisition data. The three collection results are all KEY VALUE pair data with the collection result ID spliced by OID, collection task name (integer), collection task execution sequence number (i.e. task execution times) and fixed separation identification number as KEYs and the corresponding index collection result as a VALUE (VALUE). Wherein rttmomrostrycollelectionadd ddress is configured with an ipla task with a destination address VALUE, rttMonHistoryCollectionCompletionTime separated by 16-ary codes and half-angle colon with an average latency millisecond VALUE VALUE, ttMonHistoryCollectionSense and an integer packet loss state VALUE.

Step two: traversing rttMonHistoryCollectionaddress acquisition results, and constructing data IP_IDS_MAP by taking a destination address as a KEY and taking a KEY VALUE of an acquisition result ID list as a VALUE.

Step three: traversing the key value pair IP_IDS_MAP to obtain an acquisition result ID list of each destination address IP. And sequencing the acquisition result ID list from low to high according to the acquisition task execution sequence number contained in each item of ID, continuously traversing the sequenced acquisition result ID list to acquire the acquisition result ID which is traversed currently, and querying two KEY value pairs of rttMonHistonyCollectin Time and ttMonHistonyCollectin sense by taking the acquisition result ID as a KEY to acquire single-task quality index data.

Acquisition results for the SQA device:

step one: and separating and obtaining the acquisition results of the sqaTestIcmpResultDesIP, sqaTestIcmpResultAvgRTT, sqaTestIcmpResultPacketLossRate, sqaTestIcmpResultProbeTime four indexes from the acquisition data. The four acquisition results are KEY VALUE pair data with the acquisition result ID spliced by OID and acquisition task name ASCII codes and the corresponding index acquisition result VALUE (VALUE). Wherein, the destination address of the SQA test icmpreasltdesip configured by the SQA task is VALUE, sqaTestIcmpResultAvgRTT, the millisecond VALUE of average delay is VALUE, sqaTestIcmpResultPacketLossRate, the integer packet loss rate is added with the suffix of VALUE, sqaTestIcmpResultProbeTime, and the date and time character string of the 'yyyy-MM-dd HH: MM: ss' format is VALUE.

Step two: traversing the SqaTestIcmpResultDesIP acquisition result, and constructing data IP_IDS_MAP by taking a destination address as a KEY and taking an acquisition result ID list as a KEY VALUE of a VALUE.

Step three: traversing the KEY value pair IP_IDS_MAP to obtain an acquisition result ID list of each destination IP, sequencing the acquisition result ID list from low to high according to the acquisition task execution sequence number contained in each item of ID, continuing traversing the sequenced acquisition result ID list to obtain the currently traversed acquisition result ID, and obtaining single-task quality index data by taking the acquisition result ID as three KEY value pairs of KEY query sqaTestIcmpResultAvgRTT, sqaTestIcmpResultPacketLossRate and sqaTestIcmpResultProbeTime.

The single task quality index data comprises time delay D and packet loss rate LR, and the task configuration item parameter values comprise detection task frequency F and statistical task number C of average packet loss rate of a plurality of continuous tasks _avgloss And a statistical task number C for continuously averaging the time delays of a plurality of tasks _avgdelay The line continuous monitoring data comprises continuous multiple task average packet loss rate LR _avg And average time delay D of continuous multiple tasks _avg 。

Acquiring the current time T of the system _now The starting time T for counting the average packet loss rate of a plurality of continuous tasks can be obtained by calculation according to a formula I _avgloss 。

The first formula is: t (T) _avgloss ＝T _now -F*C _avgloss ；

Wherein T is _avgloss To count the starting time of the average packet loss rate of a plurality of continuous tasks, T _now F is the detection task frequency, C is the current time of the system _avgloss And counting the number of tasks which are continuous and average packet loss rate of a plurality of tasks.

The starting time T for counting the average time delay of a plurality of continuous tasks can be obtained by calculation according to a formula II _avgdelay 。

The formula II is: t (T) _avgdelay ＝T _now -F*C _avgdelay ；

Wherein T is _avgdelay To count the start time of the average delay of a plurality of continuous tasks, T _now F is the detection task frequency, C is the current time of the system _avgloss The number of tasks is counted as the average time delay of a plurality of continuous tasks.

According to the calculated T _avgloss And T _now Querying that the execution time of a single task in the acquisition result database is in the time period to obtain T _avgloss To T _now All the packet loss values in between are averaged to obtain the average packet loss rate LR of a plurality of continuous tasks _avg 。

According to the calculated T _avgdelay And T _now Querying a collection result database to obtain T _avgdelay To T _now All the time delay values in between are averaged to obtain the average time delay D of a plurality of continuous tasks _avg 。

In this embodiment, the continuous multiple single-time line monitoring task data in the monitoring period are respectively analyzed to obtain corresponding target single-time task quality index data and execution time of the target single-time task, and on this basis, the continuous line monitoring data in the monitoring period are obtained by converting in a preset conversion mode, so that the network line quality indexes such as average packet loss rate and average time delay of the network line in the continuous monitoring period can be monitored, and effective monitoring of network abnormal scenes such as continuous packet loss rate and continuous time delay exceeding a threshold value is realized.

Further, a second embodiment is proposed based on the first embodiment, referring to fig. 3, fig. 3 is a flow chart of a second embodiment of a network line quality monitoring method according to the present invention.

In this embodiment, before step S500, the method includes:

step S100: and acquiring line monitoring item data, dial testing global configuration parameters and alarm index data of the line monitoring item.

Step S200: and determining a dial testing configuration template and a dial testing task checking instruction corresponding to the application technology type of the access equipment.

Step S300: and filling a dial testing configuration template based on the line monitoring item data, the dial testing global configuration parameters and the alarm index data to obtain dial testing task configuration content of the line monitoring item.

Step S400: and transmitting the configuration content of the dial testing task and the checking instruction of the dial testing task of the single line monitoring task to the access equipment through the equipment operation layer.

It can be understood that, in general, the access devices may be devices of different brands, and the applied related technologies are different, so that in order to realize unified monitoring on all network line quality, a corresponding dial testing task configuration template needs to be selected for each device, and parameter filling is performed on the dial testing task configuration template according to line monitoring item data of the line monitoring item, so as to obtain respective dial testing task configuration content for issuing operation of subsequent dial testing task configuration content.

Therefore, aiming at the access equipment applying different technologies, the dial testing task configuration content is generated on the basis of the corresponding dial testing configuration template, the bottom layer difference of the different technologies can be shielded, and unified monitoring of the different access equipment is realized.

For example: in a specific application scenario, the line monitoring item data of the line monitoring item includes a line unique identifier, a line description, an access device IP, an access device brand model, an access interface IP, an opposite end interface IP, and an interface VPN instance name, the dial-up global configuration parameters include a probing task frequency F (including a task execution duration, a default value of 60 seconds), a probing message number N (i.e., a sending PING message number, a default value of 50), a sending message interval T (a default value of 1 second), and the alarm indicator data includes a single task packet loss rate, a single task delay, a continuous multiple task average packet loss rate, a continuous multiple task average delay, and whether the line is interrupted.

The related dial testing task configuration template comprises:

NQA (first class) configuration templates:

system-view
	nqa test-instance admin [ task name ]
test-type icmp
	records result 10
Destination-address ipv4 [ interface IP ]
	Source-address ipv4 [ interface IP ]
Interval seconds [ NQA packet Interval ]
	timeout [ NQA packet interval ]
Probe-count [ NQA probe packet count ]
	[ VPN-instance [ VPN instance name ]]
frequency (NQA detection task frequency)
	start now
commit
	quit
quit
	save
Y

NQA (second class) configuration templates:

system-view
	nqa entry admin [ task name ]
type icmp-echo
	Destination IP [ opposite interface IP ]
Source IP (interface IP)
	probe count [ NQA probe packet count ]
Probe timeout [ NQA packet interval ]
	frequency (NQA detection task frequency)
system-view
	history-record enable
history-record number 10
	[ VPN-instance [ VPN instance name ]]
quit
	nqa schedule admin (task name) start-time now lifetime forever
return
	save force

Ipla (IOS-XR) configuration template:

IPSLA (IOS-XE) configures templates:

configure terminal
	ip sla task name
icmp-echo [ interface IP ] source-IP [ interface IP ]
	icmp-echo [ interface IP ] source-IP [ interface IP ]
[ vrf [ VPN example name ]]
	threshold (IPSLA packet interval)
timeout [ IPSLA packet interval ]
	frequency [ IPSLA packet interval ]
history lives-kept 1
	history packets-kept [ IPSLA probe packet count ]
history filter all
	ip sla schedule [ task name ] life forever start-time now
end
	write

SQA configuration templates:

wherein, the space occupation parameter which needs to be completed according to the line monitoring item data is marked by [ and the optional configuration item is marked by [ which is to generate the configuration content of [ when the space occupation parameter in [ exists ], otherwise, the whole [ configuration item takes the empty string.

Specifically: taking a line monitoring item dial-testing task name field value; an opposite interface IP field value of an opposite interface of a line monitoring item is fetched; the interface IP field value of the access interface of the line monitoring item is taken; taking a line monitoring item interface VPN instance name field value; the method comprises the steps of (1) taking a line monitoring item dial test configuration and sending a message interval parameter T in an alarm parameter set; the method comprises the steps of (1) acquiring a detection task frequency parameter F in a line monitoring item dial testing configuration and an alarm parameter set; the method comprises the steps of (1) taking a dialing measurement configuration of a line monitoring item and a detection message quantity parameter N in an alarm parameter set; the method comprises the steps of (1) taking a dialing measurement configuration of a line monitoring item and sending a message interval parameter T1000 in an alarm parameter set; taking a detection task frequency parameter F1000 in a line monitoring item dial testing configuration and an alarm parameter set; the method comprises the steps of (1) taking a dialing measurement configuration of a line monitoring item and a detection message quantity parameter N in an alarm parameter set; the method comprises the steps of (1) acquiring a line monitoring item dial test configuration and sending a message interval parameter T in an alarm parameter set; the method comprises the steps of (1) taking a probe message number parameter N in a line monitoring item dial test configuration and an alarm parameter set; the method comprises the steps of (1) taking a line monitoring item dial test configuration and a message interval parameter T which is 1000 in a message interval parameter transmission set; the method comprises the steps of (1) taking a detection task frequency parameter F in a line monitoring item dial testing configuration and an alarm parameter set; the number of detection messages in the parameter set of the dialing and measuring configuration and the alarm of the line monitoring item is taken as SQA detection packet number.

Each line monitoring item determines a configuration template according to the brand model of the equipment, and then completes configuration parameter filling according to the value relationship, thereby completing configuration content generation of the monitoring item.

And likewise, after the configuration content is generated, selecting a corresponding dial testing task checking command according to the brand and model of the equipment. The method for checking the command and judging whether the task exists or not by the dial testing task comprises the following steps:

NQA (first type) check command:

checking a command: "display nqa result test-instance admin [ task name ], wherein [ task name ] takes the line monitoring item dial-up task name field value.

Judging method for judging whether the task exists or not: the analysis command executes the back display content to judge whether the character string 'testflag is active' is contained, and if so, the task exists.

NQA (second class) check command:

checking a command: "display nqa result admin [ task name ], wherein [ task name ] takes the line monitoring item dial-up task name field value.

Judging method for judging whether the task exists or not: the analysis command executes the back display content to judge whether the character string 'Last succeeded probe time' is contained, and if so, the task exists.

IPSLA (IOS-XR) check command:

Checking a command: "show ipsla statistics".

Judging method for judging whether the task exists or not: and analyzing the command execution back display content, judging whether the character string' Entry number: [ task name ] is contained, and if so, the task already exists, wherein the [ task name ] takes a line monitoring item dialing and measuring task name field value.

IPSLA (IOS-XE) check command:

checking a command: "show ip sla summary".

Judging method for judging whether the task exists or not: and analyzing the command execution echo content, judging whether a character string is included or not (task name), and if so, the task exists, wherein the task name takes a line monitoring item dial-up task name field value.

SQA check command:

checking a command: "show running-config sqa".

Judging method for judging whether the task exists or not: and analyzing the command execution back display content, judging whether the character string 'sqa-test' is contained or not, and if so, the task already exists, wherein the [ task name ] takes a line monitoring item dialing and measuring task name field value.

The different dial testing technologies have the following corresponding relations with different OID groups, different dial testing task configuration templates and different dial testing task inspection commands:

the NQA (first class) dial testing technology corresponds to an OID group required to be collected by the NQA (first class), an NQA (first class) configuration template and an NQA (first class) checking command;

The NQA (second class) dial testing technology corresponds to the OID group required to be collected by the NQA (second class), the NQA (second class) configuration template and the NQA (second class) checking command;

the IPSLA (IOS-XR) dial testing technology corresponds to an OID group required to be acquired by the IPSLA, an IPSLA (IOS-XR) configuration template and an IPSLA (IOS-XR) checking command;

the IPSLA (IOS-XE) dial testing technology corresponds to an OID group required to be acquired by the IPSLA, an IPSLA (IOS-XE) configuration template and an IPSLA (IOS-XE) checking command;

the SQA dial testing technology and the OID group, the SQA configuration template and the SQA checking command which need to be collected by the SQA.

Further, the step S400 specifically includes:

step S410: and issuing a dial testing task checking command to the access equipment through the equipment operation layer.

Step S420: if the execution feedback content of the dial testing task checking command is obtained, judging whether the same-name task of the single line monitoring task exists or not according to the execution feedback content.

Step S430: if not, the dial testing task configuration content is issued to the access device through the device operation layer, and the execution step S410 is returned.

Step S440: if yes, the single dial testing task is determined to be successfully configured in the access equipment.

Specifically, the corresponding dial testing task configuration content is issued one by one for each access device until all the dial testing task configuration content is issued. In the issuing process, a dial testing task checking command needs to be issued, whether the same-name task of the single line monitoring task exists in the access equipment is verified through the execution and playback content of the command, and if the same-name task exists, the successful issuing of the corresponding dial testing task configuration content is indicated. The device operation layer realizes network device login, command issuing and echo receiving through a Telnet protocol or an SSH protocol, an AAA authentication service or other authentication modes.

Therefore, whether the same-name task of the single line monitoring task exists in the access equipment is verified through the execution and display content of the dial testing task checking command, and further the issuing state of the dial testing task configuration content is judged and returned, so that automatic issuing of the dial testing task configuration content is realized.

In a specific application scenario, the flow of dial testing configuration generation and automatic issuing is shown in fig. 7. The specific steps of issuing and verifying are as follows:

step one: and acquiring the line monitoring item information, and generating dial testing configuration content and a dial testing task checking command according to the line monitoring item information.

Step two: and issuing a dial testing task checking command to the access equipment through the equipment operation layer, terminating and returning the error reporting content and the status value of 'issuing failure' of the equipment operation layer if the issuing failure occurs, acquiring the command execution feedback content if the issuing success occurs, analyzing and judging whether the equipment has a task with the same name as the task name of the monitoring item in operation, terminating and issuing if the equipment has the task with the same name as the task name, returning the status value of 'issuing success', and continuing if the equipment has no task.

Step three: and issuing a dial testing task configuration content to the access equipment through the equipment operation layer, terminating and returning the error content and the status value of 'issuing failure' of the equipment operation layer if the issuing failure occurs, and continuing if the issuing is successful.

Step four: and issuing a task inspection command to the access equipment through the equipment operation layer, terminating and returning the error content and the status value of 'issuing failure' of the equipment operation layer if the issuing failure occurs, acquiring the command execution feedback content if the issuing is successful, analyzing and judging whether the equipment has a task with the same name as the task name of the monitoring item in operation, terminating the issuing if the task exists, returning the status value of 'issuing success', and returning the status value of 'issuing failure' if the task does not exist.

Step five: and updating the dial testing configuration state of the line monitoring item with the acquired status value of 'successful issuing' to be 'successful issuing', and updating the dial testing configuration state of the line monitoring item with the acquired status value of 'failed issuing' to be 'failed issuing'.

Step six: and checking the dial testing configuration state to be the dial testing configuration content and the access equipment state generated by the line monitoring item with 'failed issuing', and retrying automatic issuing or manual configuration.

Further, a third embodiment is proposed based on the first embodiment, referring to fig. 4, fig. 4 is a flow chart of a third embodiment of a network line quality monitoring method according to the present invention.

In this embodiment, after step S700, the method further includes:

Step a1: and if the single task packet loss rate in the at least 1 target single task quality index data is 100%, triggering a line interruption alarm event.

Step a2: if the line interruption alarm event is not triggered, judging whether the average multi-task packet loss rate in the line continuous monitoring data is larger than or equal to a first preset alarm threshold value.

Step a3: and if the average packet loss rate of the continuous multiple tasks is larger than or equal to the first preset alarm threshold value, triggering an alarm event with the average packet loss rate exceeding the threshold value.

Step a4: if the line interruption alarm event and the average packet loss rate of the continuous multiple tasks exceed the threshold alarm event are not triggered, judging whether the packet loss rate of the single task is larger than or equal to a second preset alarm threshold.

Step a5: and if the packet loss rate exceeds the threshold value, triggering a packet loss rate exceeding threshold value alarm event.

It will be appreciated that network line quality issues typically include line breaks, single-task packet loss, continuous-task packet loss. In this embodiment, whether the line is interrupted is determined by judging whether the single-task packet loss rate is 100%. If the line is not interrupted, determining whether to trigger a continuous multi-task average packet loss rate super-threshold alarm event by comparing the calculated multi-task average packet loss rate with a first preset alarm threshold. If the first two do not occur, determining whether to trigger the packet loss rate exceeding the threshold value alarm event by comparing the single task packet loss rate with a second preset alarm threshold value.

Therefore, by taking the first preset alarm threshold value and the second preset alarm threshold value as the judgment standards, the single-task packet loss rate and the multi-task average packet loss rate are analyzed and compared, and the network line quality problems such as line interruption, single-task packet loss, continuous-task packet loss and the like can be effectively monitored.

Further, a fourth embodiment is proposed based on the first embodiment, referring to fig. 5, and fig. 5 is a flow chart of a fourth embodiment of a network line quality monitoring method according to the present invention.

In this embodiment, after step S700, the method includes:

step b1: if the line interruption alarm event is not triggered, judging whether the average time delay of a plurality of tasks in the line continuous monitoring data is larger than or equal to a third preset alarm threshold value.

Step b2: and if the average time delay of the continuous multiple tasks exceeds the threshold value, triggering an alarm event.

Step b3: if the line interruption alarm event and the average time delay of a plurality of continuous tasks exceed the threshold value alarm event are not triggered, judging whether the single task time delay in at least 1 target single task quality index data is larger than or equal to a fourth preset alarm threshold value.

Step b4: if so, triggering a time delay exceeding a threshold value alarm event.

It will be appreciated that network line quality problems typically include single-task delays and continuous-task delays in addition to the aforementioned problems. In this embodiment, if the line is not interrupted, it is determined whether to trigger an alarm event with the average delay of multiple tasks exceeding the threshold value continuously by comparing the calculated average delay of multiple tasks with a third preset alarm threshold value. If the line is not interrupted and the average time delay of a plurality of continuous tasks exceeds the threshold value alarm event is not triggered, determining whether the time delay exceeds the threshold value alarm event is triggered by comparing the time delay of a single task with a fourth preset alarm threshold value.

Therefore, the third preset alarm threshold value and the fourth preset alarm threshold value are used as judgment standards to analyze and compare the single task time delay and the average time delay of a plurality of tasks, so that the effective monitoring of the network line quality problems such as the single task time delay and the continuous task time delay can be realized.

In a specific application scenario, the circuit quality monitor indicator alarm and recovery logic flow is shown in fig. 8. The specific event alarming steps are as follows:

acquiring various parameters in a current line monitoring item dial testing configuration parameter set: single-task packet loss rate alarm threshold TH _loss Super-threshold alert level L _loss Single-task delay alarm threshold TH _delay Super-threshold alert level L _delay Statistical task number C of average packet loss rate of continuous multiple tasks _avgloss Alarm threshold TH _avgloss Super-threshold alert level L _avgloss Statistical task number C of average time delay of continuous multiple tasks _avgdelay Alarm threshold TH _avgdelay Super-threshold alert level L _avgdelay Line break alarm level L _down . Wherein, the average packet loss rate alarm threshold TH of a plurality of continuous tasks _avgloss Namely a first preset alarm threshold value, a single-task packet loss rate alarm threshold value TH _loss Namely a second preset alarm threshold value, and a continuous multiple tasks average time delay alarm threshold value TH _avgdelay And the third preset alarm threshold value is obtained.

Judging whether the packet loss rate is 100%, if so, packaging the single task execution time, the line monitoring item data and the packet loss rate LR, and pushing L _down And (3) recording the event information in an event cache database, setting the data item to be overtime after 24 hours, or automatically clearing the data item after 24 hours through a timing task, if not, inquiring the event cache database for all historical line interrupt alarm events of the line monitoring item, if the inquiring result is not empty, clearing the cached historical line interrupt alarm events, and packaging the execution time of a single task, the line monitoring item data and the packet loss rate LR and then pushing the line interrupt recovery event.

If the line interruption alarm event is not triggered, judging the average packet loss rate LR of a plurality of continuous tasks _avg Whether or not to exceed the threshold value TH _avgloss If yes, the single task execution time, the line monitoring item data and the average packet loss rate LR of a plurality of continuous tasks are carried out _avg Push L after encapsulation _avgloss Super-threshold notification of average packet loss rate of multiple tasks with continuous levelsAlert event, record this event information in event cache database and presume the overtime after 24 hours of this data item or clear this data item automatically after 24 hours through the timing task, if not, inquire event cache database this line monitoring item all history continuous multiple task average packet loss rate warning event, if inquire result is not empty, clear these cached history warning event, and carry out time, line monitoring item data, continuous multiple task average packet loss rate LR of single task _avg And pushing the average packet loss rate super-threshold recovery event of a plurality of continuous tasks after packaging.

If the line interruption alarm event is not triggered and the average packet loss rate of a plurality of continuous tasks exceeds the threshold value alarm event, judging whether the packet loss rate LR exceeds the threshold value TH _loss If yes, packaging the single task execution time, the line monitoring item data and the packet loss rate LR, and pushing L _loss And recording the event information in an event cache database and setting overtime after 24 hours or automatically clearing the data item after 24 hours through a timing task, if not, inquiring the event cache database about all historical packet loss rate super-threshold alarm events of the line monitoring item, and if the inquiry result is not null, clearing the cached historical alarm events, and packaging the execution time of a single task, the line monitoring item data and the packet loss rate LR, and then pushing the packet loss rate super-threshold recovery event.

If the line interruption alarm event is not triggered, judging the average time delay D of a plurality of continuous tasks _avg Whether or not to exceed the threshold value TH _avgdelay If yes, the single task execution time, the line monitoring item data and the average time delay D of a plurality of continuous tasks are carried out _avg Push L after encapsulation _avgdelay If the query result is not empty, the cached historical alarm events are cleared, and the single task execution time, the line monitoring item data and the average time delay D of the continuous multiple tasks are carried out _avg Sealing is carried outAnd pushing the average time delay exceeding the threshold value recovery event of a plurality of continuous tasks after the loading.

If the line interruption alarm event is not triggered and the average delay alarm event of a plurality of continuous tasks is not triggered, judging whether the delay D exceeds the threshold value TH _delay If yes, packaging the single task execution time, the line monitoring item data and the time delay D, and then pushing L _delay And (3) recording the event information in an event cache database and setting the event information to be overtime after 24 hours or automatically clearing the data item after 24 hours by timing tasks, if not, inquiring the event cache database about all the historical delay threshold alarm events of the line monitoring items, if not, clearing the cached historical alarm events, and packaging the execution time of a single task, the line monitoring item data and the delay D and then pushing the delay threshold recovery event.

Further, a fifth embodiment is proposed based on the first embodiment, referring to fig. 6, fig. 6 is a flowchart of a fifth embodiment of a network line quality monitoring method according to the present invention.

In this embodiment, after step S700, the method includes:

step S800: the method comprises the steps of obtaining the actual collection quantity and the theoretical collection quantity of single line monitoring task data collected by a simple network management protocol collector aiming at a monitoring line within a preset time length.

Step S900: and if the actual acquisition number is smaller than the theoretical acquisition number, triggering a dial testing acquisition data missing alarm event.

It can be appreciated that in addition to the foregoing quality problems, there may be situations where the acquisition results are lost during the monitoring of the network line quality. In this embodiment, the theoretical collection number of the single line monitoring task data in the monitoring period can be calculated according to the detection task frequency, and the theoretical collection number is compared with the actual collection number, so that whether the collection result is lost or not can be determined, and further a dial test collection data missing alarm event can be triggered. The effective monitoring of the dial testing acquisition data missing scene is realized.

In a specific applicationIn the scenario, the logic flow of the acquisition continuity check alarm is shown in fig. 9. By creating a timing task, the latest line monitoring item data with the dial testing configuration state of successful issuing is acquired every 5 minutes, each line monitoring item is traversed, and the number N of the acquisition results actually recorded in the last five minutes in the acquisition result database by the currently traversed line monitoring item is queried _record Acquiring detection task frequency F in a line monitoring item dial testing configuration parameter set, calculating (5 x 60)/F, and rounding up to acquire the number N of acquisition results to be recorded _th Calculate N _th -N _record Obtaining the number of missing results N _loss If N _loss If the number is larger than 0, the defect of the acquired data is indicated, and the current time, the line monitoring item data and the number N of the actually recorded acquired results are obtained _record Number of acquisition results N to be recorded _th Number of missing results N _loss And pushing the dial testing acquisition data missing alarm event of the ALERT level after encapsulation.

In addition, in order to realize high availability of the whole network line quality monitoring method, the deployment mode of the collectors is multi-activity deployment, and all the collectors are mutually standby; the transmission mode of the acquisition result is distributed transmission, and all transmission paths are reserved; the deployment mode of the dial testing data consumption service is multi-activity deployment, and each dial testing data consumption service is standby.

In one specific application scenario, a high availability architecture line quality monitoring system architecture is shown in fig. 10. Specifically, a high availability deployment includes the following aspects:

the SNMP collector adopts a server cluster to realize multi-activity deployment, and realizes that acquisition tasks are created and executed every other set acquisition task frequency (default 1 minute in the example) for each line monitoring item. Before each collector creates a collection task, a collection task record is queried through a Redis database, then a new collection task which is not in the record is created, the new collection task is recorded in the Redis database, and the overtime time is set to be the collection task frequency (default 1 minute in the example), so that preemptive load sharing of multiple active clusters can be realized, and the creation and collection of the collection task are not affected when any service is unavailable.

The data transmission of the acquired results is realized by using distributed kafka. At the time of transmission, each SNMP collector creates a producer producing data into the same kafka topic. When the data is consumed, all the data consumption processing services consume the data in the topic by using the same group id, and the kafka server realizes the load distribution of the data.

The data consumption processing service realizes multi-activity deployment in a container or a server cluster, and when any one service is unavailable, other services can still consume the data for analysis and processing.

Both MySQL, elasticsearch and Redis database middleware used support the implementation of high availability with built distributed clusters.

To enable those skilled in the art to better understand the scope of the claims of the present application. The following description is made by way of specific examples of embodiments in specific application scenarios, and it is understood that the following examples are only used to explain the present application, and are not intended to limit the scope of the claims of the present application.

In one network line quality monitoring scenario, access devices in the network include device a and device B. According to the relevant information of the brand and model inquiry of the equipment A and the equipment B, the equipment A is found to apply NQA technology, and the equipment B is found to apply SQA technology. Filling configuration parameters on the basis of the NQA configuration template to obtain the dial testing task configuration content of each line monitoring item of the equipment A, and filling configuration parameters on the basis of the SQA configuration template to obtain the dial testing task configuration content of each line monitoring item of the equipment B. Therefore, the bottom technical difference of the equipment A and the equipment B can be shielded, and unified configuration and equivalent monitoring effects are realized.

Corresponding dial testing task checking commands are selected for the equipment A and the equipment B, the corresponding dial testing task checking commands are respectively issued to the equipment A and the equipment B, the equipment A and the equipment B execute the corresponding dial testing task checking commands and return command execution results. And judging whether the equipment A and the equipment B have the dial testing task with the same name as the dial testing task configuration content according to the command execution result. If the configuration content does not exist, the corresponding dial testing task configuration content is respectively issued to the equipment A and the equipment B. And issuing a corresponding dial testing task checking command to the equipment A and the equipment B again, verifying whether the equipment A and the equipment B have dial testing tasks with the same name as the dial testing task configuration content, and if so, indicating that the dial testing task configuration content is successfully issued. Therefore, automatic generation and issuing of the dial testing configuration content can be realized.

And respectively sending acquisition requests to the equipment A and the equipment B by using collectors deployed by the clusters according to acquisition requirements, and acquiring a plurality of single line monitoring task data. And packaging and sending the plurality of single line monitoring task data to a dial testing data consumption service deployed by a cluster through a distributed middleware for data processing, and determining all single task packet loss rates, single task time delays and all target single task execution times corresponding to the same interface address data in the equipment A or the equipment B. And simultaneously, storing all acquired single line monitoring task data into a collection result database. And calculating to obtain the average packet loss rate of the continuous multiple tasks and the average time delay of the continuous multiple tasks according to the packet loss rates of all the single tasks, the single task time delay and the execution time of all the target single tasks. By adopting the collector deployed by the cluster, the dial testing data consumption service deployed by the cluster and the distributed middleware, the reliability of the collector, the dial testing data consumption service and the middleware can be improved, and the high availability of the network line quality monitoring system is further realized.

And sending the obtained single-task packet loss rate, single-task time delay, average packet loss rate of a plurality of continuous tasks and average time delay package of a plurality of continuous tasks to an event alarm system. The event warning system comprises an event cache database for storing historical warning events, and if the warning event storage event exceeds a preset time, the event cache database deletes the corresponding warning event. And comparing the single task packet loss rate, the single task time delay, the average packet loss rate of the continuous multiple tasks and the average time delay of the continuous multiple tasks with corresponding set thresholds. If the average packet loss rate of the continuous multiple tasks of the line monitoring item M is larger than the average packet loss rate alarm threshold value of the continuous multiple tasks, pushing an event that the average packet loss rate of the continuous multiple tasks exceeds the threshold value; and if the average packet loss rate of the continuous multiple tasks of the line monitoring item M is smaller than or equal to the average packet loss rate alarm threshold value of the continuous multiple tasks at the moment, querying and clearing all the continuous multiple task average packet loss rate super-threshold event of the line monitoring item M in the event cache database, and pushing the continuous multiple task average packet loss rate super-threshold recovery event. Similarly, there are cases of single task packet loss rate, single task time delay, average time delay of multiple continuous tasks exceeding a threshold, line interruption, and the like, and the pushing method of the corresponding event is the same as above, and will not be described here again. Therefore, monitoring and alarming of various scenes such as time delay exceeding threshold, packet loss rate exceeding threshold, continuous packet loss, continuous time delay exceeding threshold, line interruption and the like can be realized.

Meanwhile, the theoretical acquisition result number aiming at the equipment A and the equipment B in the monitoring time period is obtained through calculation according to the set acquisition frequency, the corresponding actual acquisition result number is inquired from an acquisition result database, and if the theoretical acquisition result number is smaller than the actual acquisition result number, the missing alarm event of the measurement acquisition data is pushed and dialed, so that the self-monitoring of the acquisition continuity can be realized.

And finally, unified monitoring of the line quality of the equipment A applying the NQA technology and the equipment B applying the SQA technology is realized.

Further, to achieve the above object, the present invention further provides a network line quality monitoring device, where the network line quality monitoring device may include:

It should be noted that, the functions and the corresponding technical effects that can be achieved by each module in the network line quality monitoring device provided in this embodiment may refer to descriptions of specific embodiments in each embodiment of the network line quality monitoring method of the present invention, and for brevity of description, details are not repeated here.

In addition, the embodiment of the invention also provides a computer readable storage medium, wherein the computer readable storage medium is stored with a network line quality monitoring program, and the network line quality monitoring program realizes the steps of the network line quality monitoring method when being executed by a processor. Therefore, a detailed description will not be given here. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the embodiments of the computer-readable storage medium according to the present invention, please refer to the description of the method embodiments of the present invention. As an example, the program instructions may be deployed to be executed on one computing device or on multiple computing devices at one site or distributed across multiple sites and interconnected by a communication network.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising a network line quality monitor" does not exclude the presence of additional identical elements in a process, method, article, or system that comprises the element.

The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a computer readable storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as above, comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method of the embodiments of the present invention.

The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims

1. The network line quality monitoring method is characterized by comprising the following steps:

determining all target single task execution time and all target single task quality index data corresponding to the same opposite-end interface address data from a plurality of single line monitoring task data;

and aiming at the same opposite-end interface address data, obtaining the line continuous monitoring data of the line monitoring item in the monitoring time period based on the target single task execution time and all the target single task quality index data in the monitoring time period.

2. The network line quality monitoring method of claim 1, wherein determining all target single-task execution times and all target single-task quality index data corresponding to the same interface address data from the plurality of single-line monitoring task data comprises:

Obtaining interface address result data and single task quality index result data based on a plurality of single line monitoring task data; the interface end interface address result data and the single task quality index result data are key value pairs, attribute keys of the interface end address result data and the single task quality index result data are object identifiers, character ASCII codes of task configuration item parameter values, character ASCII codes of single dial test collection task names, collection task execution serial numbers and collection result codes obtained by task type splicing, the attribute values of the interface end interface address result data are the interface end interface address data, and the attribute values of the single task quality index result data are the single task quality index data;

traversing the interface address result data of the opposite port, determining all target acquisition result codes corresponding to the same interface address data of the opposite port, and obtaining a first key value pair; wherein, the attribute keys of the first key value pair are the same interface address data of the opposite end, and the attribute values are the target acquisition result codes;

and inquiring the single task quality index result data based on the target acquisition result code, and determining all target single task execution time and all target single task quality index data corresponding to the same opposite-end interface address data.

3. The network line quality monitoring method of claim 1, wherein prior to the acquiring the monitoring period and the plurality of single line monitoring task data acquired by the simple network management protocol acquirer for the monitoring line of the access device, the method further comprises:

acquiring line monitoring item data of the line monitoring item, dial testing global configuration parameters and alarm index data; the dial-up global configuration parameters comprise detection task frequency, detection message quantity and message sending interval, the alarm index data are related to the single task quality index data, and the line monitoring item data comprise an access interface address and an opposite interface address;

determining a dial testing configuration template and a dial testing task checking instruction corresponding to the application technology type of the access equipment; the application technology type is a network quality analysis type, an Internet protocol service level protocol type or a network line quality assurance type;

filling the dial testing configuration template based on the line monitoring item data, the dial testing global configuration parameters and the alarm index data to obtain dial testing task configuration content of the line monitoring item;

and issuing the configuration content of the dial testing task and the checking instruction of the dial testing task of the single line monitoring task to the access equipment through an equipment operation layer.

4. The network line quality monitoring method according to claim 3, wherein the issuing of the dial testing task configuration content and dial testing task check instruction of a single line monitoring task to the access device through the device operation layer includes:

issuing the dial testing task checking command to the access equipment through an equipment operation layer;

if not, the dial testing task configuration content is issued to the access equipment through the equipment operation layer, and the dial testing task checking command is issued to the access equipment through the equipment operation layer in a return mode;

if yes, the single dial testing task is determined to be configured successfully in the access equipment.

5. The network line quality monitoring method according to any one of claims 1 to 4, wherein the method further comprises, for the same pair of interface address data, after obtaining line continuous monitoring data of the line monitoring item in the monitoring period based on the target single task execution time and all the target single task quality index data in the monitoring period:

If the single task packet loss rate in at least 1 target single task quality index data is 100%, triggering a line interruption alarm event;

if the line interruption alarm event and the average packet loss rate of a plurality of continuous tasks exceed the threshold alarm event are not triggered, judging whether the packet loss rate of the single task is greater than or equal to a second preset alarm threshold;

6. The network line quality monitoring method according to claim 5, wherein the method further comprises, for the same opposite-end interface address data, after obtaining line continuous monitoring data of the line monitoring item in the monitoring period based on the target single-task execution time and all the target single-task quality index data in the monitoring period:

if so, triggering a time delay exceeding a threshold value alarm event.

7. The network line quality monitoring method according to claim 5, wherein the method further comprises, for the same opposite-end interface address data, after obtaining line continuous monitoring data of the line monitoring item in the monitoring period based on the target single-task execution time and all the target single-task quality index data in the monitoring period:

acquiring the actual acquisition quantity and the theoretical acquisition quantity of the single line monitoring task data acquired by the simple network management protocol acquisition unit aiming at the monitoring line within a preset time length;

And if the actual collection number is smaller than the theoretical collection number, triggering a dial testing collection data missing alarm event.

8. A network line quality monitoring device, the device comprising:

and the second data analysis module is used for obtaining the line continuous monitoring data of the line monitoring item in the monitoring time period based on the target single task execution time and all the target single task quality index data in the monitoring time period aiming at the same opposite-end interface address data.

9. A network line quality monitoring device, the device comprising: a memory, a processor and a network line quality monitoring program stored on the memory and operable on the processor, the network line quality monitoring program being configured to implement the steps of the network line quality monitoring method of any one of claims 1 to 7.

10. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a network line quality monitoring program, which when executed by a processor, implements the steps of the network line quality monitoring method according to any of claims 1 to 7.