CN115580527A

CN115580527A - Network communication troubleshooting method, device, equipment and storage medium

Info

Publication number: CN115580527A
Application number: CN202211216203.5A
Authority: CN
Inventors: 李传飞; 徐志豪
Original assignee: Shenzhen Topband Software Technology Co ltd; Shenzhen Topband Co Ltd
Current assignee: Shenzhen Topband Software Technology Co ltd; Shenzhen Topband Co Ltd
Priority date: 2022-09-30
Filing date: 2022-09-30
Publication date: 2023-01-06

Abstract

The invention discloses a network communication troubleshooting method, a network communication troubleshooting device, network communication troubleshooting equipment and a storage medium, and relates to the technical field of network fault detection. The method comprises the following steps: judging whether the network equipment has communication faults or not; if the network equipment has communication faults, sending a data acquisition instruction to the network equipment; receiving first network monitoring data of a network device, and acquiring second network monitoring data of the network device at the network server; the fault type of the network equipment is determined according to the first network monitoring data and/or the second network monitoring data, so that when the network equipment breaks down, the first network monitoring data of the network equipment and the second network monitoring data of a network server can be automatically acquired, the fault type of the network equipment can be automatically analyzed according to the first network monitoring data and/or the second network monitoring data, manual participation is not needed in the whole process, manpower is greatly saved, efficiency is improved, and accuracy is high.

Description

Network communication troubleshooting method, device, equipment and storage medium

Technical Field

The invention relates to the technical field of network fault detection, in particular to a network communication fault troubleshooting method, a network communication fault troubleshooting device, network communication equipment and a storage medium.

Background

With the development of the internet of things technology, the application of network devices becomes more and more extensive. There are situations where a network failure occurs in a network device. Generally, when a network device fails, an operation and maintenance worker can only manually acquire monitoring data, and presume the reason for the abnormality of the device side according to the acquired monitoring data. Due to the need of manually acquiring data and manually checking, the efficiency is extremely low, and the fault reason is difficult to accurately determine.

Disclosure of Invention

The invention provides a network communication troubleshooting method, a network communication troubleshooting device and a storage medium, and aims to solve the problems that in the prior art, the efficiency is extremely low and the cause of a fault is difficult to accurately determine through manual data acquisition and manual troubleshooting.

In a first aspect, the present invention provides a method for troubleshooting network communication, including:

judging whether the network equipment has communication faults or not;

if the network equipment has a communication fault, sending a data acquisition instruction to the network equipment, wherein the data acquisition instruction is used for enabling the network equipment to acquire first network monitoring data of the network equipment and sending the first network monitoring data to a network server;

receiving the first network monitoring data and acquiring second network monitoring data of the network equipment at the network server;

and determining the fault type of the network equipment according to the first network monitoring data and/or the second network monitoring data.

The further technical scheme is that the judging whether the network equipment has communication faults comprises:

acquiring the number of offline times of the network equipment in a preset time period;

judging whether the number of times of disconnection of the network equipment is greater than a preset number threshold value;

and if the number of times of disconnection of the network equipment is greater than a preset number threshold, judging that the network equipment has communication faults.

A further technical solution is that the first network monitoring data includes an equipment malfunction code, and the determining the fault type of the network equipment according to the first network monitoring data and/or the second network monitoring data includes:

and inquiring the fault type of the network equipment in a preset equipment function fault code-fault type table according to the equipment function fault code.

A further technical solution is that the second network monitoring data includes a number of TCP transceiving packets at a service port and a number of MQTT protocol packets at a service port, and the determining a fault type of the network device according to the first network monitoring data and/or the second network monitoring data includes:

acquiring a first absolute value of a difference value between the number of TCP (transmission control protocol) receiving and sending packets of the server-side network port and the number of MQTT protocol packets of the server side;

judging whether the first absolute value is larger than a preset first quantity threshold value or not;

and if the first absolute value is larger than a preset first quantity threshold, judging that the fault type of the network equipment comprises service function software errors.

A further technical solution is that the first network monitoring data includes a number of TCP transceiving packets at a device port, the second network monitoring data includes a number of TCP transceiving packets at a service port, and the determining a fault type of the network device according to the first network monitoring data and/or the second network monitoring data includes:

acquiring a second absolute value of a difference value between the number of TCP (transmission control protocol) receiving and sending packets of the equipment port and the number of MQTT protocol packets of the server port;

judging whether the second absolute value is larger than a preset second quantity threshold value or not;

and if the second absolute value is larger than a preset second quantity threshold, judging that the fault type of the network equipment comprises equipment network access errors.

A further technical solution is that the first network monitoring data includes signal strengths of the network device at a plurality of preset sampling points, and the determining the fault type of the network device according to the first network monitoring data and/or the second network monitoring data includes:

acquiring a signal intensity average value, a signal intensity maximum value, a signal intensity minimum value and a signal intensity variance of the signal intensity of the network equipment at a plurality of preset sampling points;

judging whether the signal intensity average value, the signal intensity maximum value, the signal intensity minimum value and the signal intensity variance meet a preset first abnormity judgment rule or not;

and if the signal intensity average value, the signal intensity maximum value, the signal intensity minimum value and the signal intensity variance accord with a preset first abnormity judgment rule, judging that the fault type of the network equipment comprises equipment network access errors.

A further technical solution is that the first network monitoring data includes first location information and IP change frequency of the network device, the second network monitoring data includes second location information of a network server, and determining a fault type of the network device according to the first network monitoring data and/or the second network monitoring data includes:

determining distance information and cross-domain information of the network equipment and the network server according to the first position information and the second position information;

judging whether the distance information, the cross-domain information and the IP change frequency meet a preset second abnormity judgment rule or not;

and if the distance information, the cross-domain information and the IP change frequency accord with a preset second abnormity judgment rule, judging that the fault type of the network equipment comprises an internet communication error.

In a second aspect, the present invention further provides a network communication troubleshooting apparatus, which includes a unit for executing the above method.

In a third aspect, the present invention further provides a computer device, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the above method when executing the computer program.

In a fourth aspect, the invention also provides a computer-readable storage medium, storing a computer program which, when executed by a processor, is operable to carry out the method described above.

The invention provides a network communication troubleshooting method, a network communication troubleshooting device and a storage medium. The method comprises the steps of judging whether the network equipment has communication faults or not; if the network equipment has communication faults, sending a data acquisition instruction to the network equipment; receiving the first network monitoring data and acquiring second network monitoring data of the network equipment at the network server; the fault type of the network equipment is determined according to the first network monitoring data and/or the second network monitoring data, so that when the network equipment breaks down, the first network monitoring data of the network equipment and the second network monitoring data of a network server can be automatically acquired, the fault type of the network equipment can be automatically analyzed according to the first network monitoring data and/or the second network monitoring data, manual participation is not needed in the whole process, manpower is greatly saved, efficiency is improved, and accuracy is high.

Drawings

In order to more clearly illustrate the technical solution of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic view of an application scenario of a network communication troubleshooting method provided by the present invention;

fig. 2 is a schematic flow chart of a network communication troubleshooting method according to the present invention;

fig. 3 is a schematic block diagram of a network communication troubleshooting apparatus provided in the present invention;

FIG. 4 is a schematic block diagram of a computer device provided by the present invention.

Detailed Description

The technical solutions in the present invention will be described clearly and completely with reference to the accompanying drawings, and it should be understood that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It should be further understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items and includes such combinations.

As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".

Referring to fig. 1, fig. 1 is a schematic view of an application scenario of the network communication troubleshooting method provided by the present invention. As shown in fig. 1, the network communication troubleshooting method includes a network server 100 and a network device 200 in an application scenario.

Fig. 2 is a schematic flow chart of a network communication troubleshooting method provided by the present invention. The network communication troubleshooting method is applied to a network server. As shown in fig. 2, the method comprises the following steps S1-S4.

S1, judging whether the network equipment has communication faults or not.

In a specific implementation, the network device includes a terminal device accessing to the internet. First, it is determined whether a communication fault exists in the network device, which may be specifically determined by network abnormal data such as a dropped time, a dropped frequency, and dropped times of the network device, which is not specifically limited in the present invention.

In one embodiment, the above step S1 specifically includes the following steps S11 to S13.

S11, obtaining the number of times of disconnection of the network equipment in a preset time period.

In a specific implementation, the predetermined time period may be a day, i.e. 0 to 24 points per day. And collecting the number of the offline times of the network equipment in one day.

And S12, judging whether the number of times of the disconnection of the network equipment is greater than a preset number threshold value.

In a specific implementation, the number threshold may be set by a user according to an actual situation, and the present invention is not limited to this, for example, the number threshold may be specifically set to 100. Therefore, in an embodiment, it is determined whether the number of dropped calls of the network device is greater than 100.

And S13, if the number of times of disconnection of the network equipment is greater than a preset number threshold, judging that the network equipment has communication faults.

In specific implementation, if the number of times of disconnection of the network device is greater than a preset number threshold, it is determined that the network device has a communication fault.

And if the number of times of disconnection of the network equipment is not more than a preset number threshold, judging that the network equipment has communication faults.

Further, the number of the network devices is usually multiple, so that all the network devices with the connection drop times larger than the preset threshold value of the number of times can be added to the preset abnormal device list, and the user can conveniently view the network devices.

And S2, if the network equipment has communication faults, sending a data acquisition instruction to the network equipment, wherein the data acquisition instruction is used for enabling the network equipment to acquire first network monitoring data of the network equipment and sending the first network monitoring data to a network server.

In specific implementation, if the network equipment has communication fault, a data acquisition instruction is sent to the network equipment.

Correspondingly, when the network equipment receives the data acquisition instruction, the first network monitoring data of the network equipment are acquired, and the first network monitoring data are sent to a network server. The first network monitoring data may specifically include the number of TCP packets received and transmitted by the device, the device function fault code, the signal strength, and the like, which is not specifically limited in the present invention. It should be noted that TCP (Transmission Control Protocol) is a connection-oriented, reliable transport layer communication Protocol based on byte stream.

It is understood that, in order to reduce data traffic, the network device that does not receive the data collection instruction will not collect the first network monitoring data.

And S3, receiving the first network monitoring data and acquiring second network monitoring data of the network equipment at the network server.

In a specific implementation, a network server receives the first network monitoring data sent by a network device, and acquires second network monitoring data of the network device at the network server. The second network monitoring data refers to monitoring data related to the network device at the network server, and includes, for example, the number of TCP transceiving packets at the service port and the number of MQTT protocol packets at the service port, which is not specifically limited in the present invention.

It should be noted that MQTT (Message Queuing Telemetry Transport) is a Message protocol based on a publish/subscribe paradigm under the ISO standard (ISO/IEC PRF 20922).

And S4, determining the fault type of the network equipment according to the first network monitoring data and/or the second network monitoring data.

In specific implementation, an abnormality determination rule is preset, and based on the abnormality determination rule, the fault type of the network device is determined according to the first network monitoring data and/or the second network monitoring data.

In an embodiment, the first network monitoring data includes an equipment malfunction code, and the step S4 specifically includes:

The method comprises the steps that a one-to-one corresponding relation exists between equipment function fault codes and fault types of network equipment, the corresponding relation between the equipment function fault codes and the fault types of the network equipment is recorded in an equipment function fault code-fault type table in advance, and the fault types of the network equipment can be inquired in the equipment function fault code-fault type table when the equipment function fault codes are known.

For example, the device malfunction code-failure type table is shown in table 1 below.

Equipment function fault code	Type of failure
		0	Mqtt connection failure
1	Device restart
		2	Heartbeat packet timeout
3	Read data exception
		4	Write data exception
5	Actively breaking a link
		6	Router disconnection

TABLE 1 Equipment malfunction code-Fault type Table

In an embodiment, the second network monitoring data includes a number of TCP transceiving packets at the service port and a number of MQTT protocol packets at the service port, and the step S4 specifically includes the following steps S11 to S13.

S11, a first absolute value of a difference value between the number of TCP receiving and sending packets of the network port of the service end and the number of MQTT protocol packets of the service end is obtained.

In specific implementation, the number of the TCP receiving and sending packets of the network port of the service end and the number of the MQTT protocol packets of the service end should be the same under normal conditions. The larger the first absolute value of the difference value between the number of the TCP receiving and sending packets of the network port of the service end and the number of the MQTT protocol packets of the service end is, the larger the probability of the error of the service function software is.

S12, judging whether the first absolute value is larger than a preset first quantity threshold value.

In a specific implementation, the first quantity threshold may be determined by a person skilled in the art according to practical situations, and the present invention is not limited to this.

S13, if the first absolute value is larger than a preset first quantity threshold, judging that the fault type of the network equipment comprises a service function software error.

In an embodiment, the first network monitoring data includes a number of TCP packets received and transmitted by the device port, the second network monitoring data includes a number of TCP packets received and transmitted by the server port, and the step S4 specifically includes the following steps S21 to S23.

S21, a second absolute value of the difference value between the TCP receiving and sending packet quantity of the equipment port and the MQTT protocol packet quantity of the server side is obtained.

In specific implementation, the number of TCP transceiving packets of the device-side network port and the number of MQTT protocol packets of the server-side network port should be the same. The larger the second absolute value of the difference value between the number of the TCP receiving and sending packets of the device port and the number of the MQTT protocol packets of the server port is, the larger the probability of the network access error of the device is.

S22, judging whether the second absolute value is larger than a preset second quantity threshold value.

In a specific implementation, the second number threshold may be determined by a person skilled in the art according to practical situations, and the present invention is not limited to this.

And S23, if the second absolute value is larger than a preset second quantity threshold, determining that the fault type of the network equipment comprises equipment network access errors.

In an embodiment, the first network monitoring data includes signal strengths of the network device at a plurality of preset sampling points, and the step S4 includes the following steps S31 to S33.

S31, acquiring the signal intensity average value, the signal intensity maximum value, the signal intensity minimum value and the signal intensity variance of the signal intensity of the network equipment at a plurality of preset sampling points.

In specific implementation, the preset sampling point can be set by a person skilled in the art according to actual conditions, for example, one sampling point is set every 10min from the zero point of each day.

And calculating the signal strength average value, the signal strength maximum value, the signal strength minimum value and the signal strength variance of the signal strength of the network equipment at a plurality of preset sampling points.

And S32, judging whether the signal intensity average value, the signal intensity maximum value, the signal intensity minimum value and the signal intensity variance meet a preset first abnormity judgment rule.

In a specific implementation, the smaller the signal strength average value is, the larger the signal strength variance is, the smaller the signal strength maximum value is, and the smaller the signal strength minimum value is, which indicates that the probability of the presence of the device network access error is higher.

In one embodiment, the first abnormality determination rule includes:

and if the signal strength average value is smaller than a preset first signal strength average value threshold value (for example, -69 dBm), judging that the fault type of the network equipment comprises equipment network access errors. The first signal strength average value threshold may be set by a person skilled in the art according to actual situations, and the present invention is not limited to this.

And if the maximum signal strength value is smaller than a preset maximum signal strength threshold value (for example, -50 dBm), and the minimum signal strength value is smaller than a preset minimum signal strength threshold value (for example, -80 dBm), judging that the fault type of the network equipment comprises equipment network access errors. The signal strength maximum threshold and the signal strength minimum threshold may be set by those skilled in the art according to actual situations, and the present invention is not limited to this.

If the signal strength mean value is less than a predetermined second signal strength mean value threshold (e.g., -54 dBm) and the signal strength variance is greater than a predetermined signal strength variance threshold (e.g., 66 dBm) ² ) And judging that the fault type of the network equipment comprises equipment network access errors. The second signal strength average threshold and the signal strength variance threshold may be set by those skilled in the art according to actual situations, which is not specifically limited by the present invention.

It should be noted that the above first abnormality determination rule is only a specific example, and those skilled in the art may also use other first abnormality determination rules without departing from the scope of the present invention.

And S33, if the signal intensity average value, the signal intensity maximum value, the signal intensity minimum value and the signal intensity variance accord with a preset first abnormity judgment rule, judging that the fault type of the network equipment comprises equipment network access errors.

In an embodiment, the first network monitoring data includes first location information of the network device and an IP change frequency, the second network monitoring data includes second location information of a network server, and the step S4 specifically includes the following steps S41 to S43.

S41, determining distance information and cross-domain information of the network equipment and the network server according to the first position information and the second position information.

In specific implementation, the cross-domain information indicates whether the network device and the network server are cross-country. The cross-domain information includes cross-country as well as non-cross-country.

And S42, judging whether the distance information, the cross-domain information and the IP change frequency meet a preset second abnormity judgment rule.

In a specific implementation, the cross-domain information includes cross-country and non-cross-country. The cross-domain information is that the farther the cross-country network equipment is away from the geographic position of the network server, the larger the IP change frequency is, the larger the probability of internet communication error is.

In one embodiment, the second abnormality determination rule includes:

if the cross-domain information is not cross-country, the distance is smaller than a preset first distance threshold value, and the IP change frequency is greater than 1 time per minute, and the fault type of the network equipment is judged to comprise an internet communication error; the first distance threshold may be set by a person skilled in the art according to actual conditions, and the present invention is not limited to this.

If the cross-domain information is cross-country, the distance is greater than a preset second distance threshold, and the IP change frequency is greater than 1 time per hour, and the fault type of the network equipment is judged to comprise an internet communication error; the second distance threshold may be set by a person skilled in the art according to actual conditions, and the present invention is not limited to this.

And if the cross-domain information is cross-country, the distance is smaller than a preset third distance threshold, and the IP change frequency is greater than 1 time per day, and the fault type of the network equipment is judged to comprise an internet communication error. The third distance threshold may be set by a person skilled in the art according to actual conditions, and the present invention is not limited to this.

It should be noted that the above second abnormality determination rule is only a specific example, and those skilled in the art may also use other second abnormality determination rules without departing from the scope of the present invention.

S43, if the distance information, the cross-domain information and the IP change frequency accord with a preset second abnormity judgment rule, judging that the fault type of the network equipment comprises an Internet communication error.

By applying the technical scheme of the invention, whether the network equipment has communication faults or not is judged; if the network equipment has communication faults, sending a data acquisition instruction to the network equipment; receiving the first network monitoring data and acquiring second network monitoring data of the network equipment at the network server; the fault type of the network equipment is determined according to the first network monitoring data and/or the second network monitoring data, so that when the network equipment breaks down, the first network monitoring data of the network equipment and the second network monitoring data of a network server can be automatically acquired, the fault type of the network equipment can be automatically analyzed according to the first network monitoring data and/or the second network monitoring data, manual participation is not needed in the whole process, manpower is greatly saved, efficiency is improved, and accuracy is high.

Referring to fig. 3, fig. 3 is a schematic block diagram of a network communication troubleshooting apparatus 30 provided in the present invention. Corresponding to the network communication troubleshooting method, the invention also provides a network communication troubleshooting device 30. The network communication troubleshooting apparatus 30 includes a unit for executing the network communication troubleshooting method described above, and the network communication troubleshooting apparatus 30 may be configured in a server. Specifically, the network communication troubleshooting device 30 includes a judging unit 31, a transmitting unit 32, a receiving unit 33, and a determining unit 34.

A judging unit 31, configured to judge whether a communication fault exists in the network device;

a sending unit 32, configured to send a data acquisition instruction to a network device if a communication fault exists in the network device, where the data acquisition instruction is used to enable the network device to acquire first network monitoring data of the network device and send the first network monitoring data to a network server;

a receiving unit 33, configured to receive the first network monitoring data, and obtain second network monitoring data of the network device at the network server;

a determining unit 34, configured to determine a fault type existing in the network device according to the first network monitoring data and/or the second network monitoring data.

In an embodiment, the determining whether the network device has a communication failure includes:

In an embodiment, the determining, by the first network monitoring data and/or the second network monitoring data, the type of fault existing in the network device according to the device function fault code includes:

In an embodiment, the determining, by the second network monitoring data, the fault type of the network device according to the first network monitoring data and/or the second network monitoring data includes:

and if the first absolute value is larger than a preset first quantity threshold, judging that the fault type of the network equipment comprises a service function software error.

In an embodiment, the determining, by the first network monitoring data and the second network monitoring data, the fault type of the network device according to the first network monitoring data and/or the second network monitoring data includes:

In an embodiment, the determining the type of the fault existing in the network device according to the first network monitoring data and/or the second network monitoring data includes:

In an embodiment, the determining, by the first network monitoring data, a type of a fault existing in the network device according to the first network monitoring data and/or the second network monitoring data includes:

It should be noted that, as can be clearly understood by those skilled in the art, the detailed implementation process of the network communication troubleshooting device 30 and each unit may refer to the corresponding description in the foregoing method embodiment, and for convenience and conciseness of description, no further description is provided herein.

The network communication troubleshooting apparatus 30 may be implemented in the form of a computer program that can be run on a computer device as shown in fig. 4.

As shown in fig. 4, the embodiment of the present application provides a computer device, which includes a processor 111, a communication interface 112, a memory 113 and a communication bus 114, wherein the processor 111, the communication interface 112, the memory 113 complete mutual communication through the communication bus 114,

a memory 113 for storing a computer program;

in an embodiment of the present application, the processor 111 is configured to execute the program stored in the memory 113 to perform a network communication troubleshooting method according to any one of the above-mentioned method embodiments.

It will be understood by those skilled in the art that all or part of the flow of the method implementing the above embodiments may be implemented by a computer program instructing associated hardware. The computer program may be stored in a storage medium that is computer-readable. The computer program is executed by at least one processor in the computer system to implement the flow steps of the embodiments of the method described above.

Accordingly, the present invention also provides a storage medium. The storage medium may be a computer-readable storage medium. The storage medium stores a computer program. The computer program, when executed by a processor, causes the processor to perform a method for troubleshooting network communication as set forth in any of the above method embodiments.

The storage medium is an entity and non-transitory storage medium, and may be various entity storage media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk. The computer readable storage medium may be non-volatile or volatile.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative. For example, the division of each unit is only one logic function division, and there may be another division manner in actual implementation. For example, various elements or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented.

The steps in the method of the invention can be adjusted, combined and deleted in sequence according to actual needs. The units in the device can be merged, divided and deleted according to actual needs. In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a storage medium. Based on such understanding, the technical solution of the present invention essentially or partially contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a terminal, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, while the invention has been described with respect to the above-described embodiments, it will be understood that the invention is not limited thereto but may be embodied with various modifications and changes.

While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A network communication troubleshooting method is characterized by comprising the following steps:

judging whether the network equipment has communication faults or not;

2. The method of claim 1, wherein the determining whether the network device has the communication failure comprises:

3. The method according to claim 1, wherein the first network monitoring data includes a device function fault code, and the determining the type of the network device that has a fault according to the first network monitoring data and/or the second network monitoring data includes:

4. The method according to claim 1, wherein the second network monitoring data includes a number of service port TCP transceiving packets and a number of service port MQTT protocol packets, and the determining the type of the network device fault according to the first network monitoring data and/or the second network monitoring data includes:

5. The method according to claim 1, wherein the first network monitoring data includes a number of TCP transceiving packets of a device port, and the second network monitoring data includes a number of TCP transceiving packets of a service port, and the determining the type of the fault existing in the network device according to the first network monitoring data and/or the second network monitoring data includes:

6. The method according to claim 1, wherein the first network monitoring data includes signal strengths of the network device at a plurality of preset sampling points, and the determining the type of the fault existing in the network device according to the first network monitoring data and/or the second network monitoring data includes:

7. The method according to claim 1, wherein the first network monitoring data includes first location information of the network device and IP change frequency, the second network monitoring data includes second location information of a network server, and the determining the type of the fault existing in the network device according to the first network monitoring data and/or the second network monitoring data includes:

8. A network communication troubleshooting device comprising means for performing the method of any one of claims 1-7.

9. A computer arrangement, characterized in that the computer arrangement comprises a memory having stored thereon a computer program and a processor implementing the method according to any of claims 1-7 when executing the computer program.

10. A computer-readable storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method according to any one of claims 1-7.