Fault detection method and related apparatus

Abstract

A fault detection method and a related apparatus, which are applied to the technical field of ambient power-enabled Internet of Things (AIoT). In the present application, after a first message is received, identity information of a faulty AIoT terminal device (i.e., a faulty terminal) can be acquired. Furthermore, in the present application, sensor information of the AIoT terminal device can be acquired, and on the basis of the sensor information of the AIoT terminal device, it is determined whether the AIoT terminal device itself is faulty. If the AIoT terminal device itself is faulty, the present application can greatly simplify fault localization steps and optimize a fault localization process, without sequentially performing alarming or abnormal information checking on an IoT platform, a core network, a base station, and a terminal, which can effectively improve the fault localization efficiency of an AIoT terminal in a fault scenario.

Description

Fault detection methods and related devices

[0001] This application claims priority to Chinese Patent Application No. 202510126296.X, filed on January 26, 2025, entitled "Fault Detection Method and Related Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of environmental power supply Internet of Things technology, and in particular to fault detection methods and related devices. Background Technology

[0003] Ambient Power-enabled Internet of Things (AIoT) is an Internet of Things (IoT) technology that utilizes ambient energy for power generation, enabling low-cost, self-powered IoT device connectivity. AIoT powers devices by collecting energy from the environment (such as light, heat, wind, waves, sound, electromagnetic radiation, and mechanical vibration), thus eliminating reliance on traditional batteries, reducing maintenance costs, and improving device usability.

[0004] In current AIoT terminal operation and maintenance troubleshooting scenarios, fault location is typically handled using the following method. When an AIoT terminal malfunctions, the application server detects that the AIoT terminal information cannot be reported or is abnormal. This requires sequentially checking the Internet of Things (IoT) platform, core network, base station, and finally the AIoT terminal for alarms or anomalies. Even if the AIoT terminal itself malfunctions, this troubleshooting process still requires sequentially checking the IoT platform, core network, base station, and finally the terminal for alarms or anomalies. However, the fault location steps involving the IoT platform, core network, and base station are redundant, resulting in low efficiency in fault location during AIoT terminal malfunction scenarios.

[0005] Therefore, how to improve the efficiency of fault location in AIoT terminal failure scenarios is a hot topic that those skilled in the art are researching. Summary of the Invention

[0006] This application provides a fault detection method and related apparatus, which can determine whether the faulty terminal itself has malfunctioned based on the sensor information of the faulty terminal. If the faulty terminal itself has malfunctioned, this application can simplify the fault location steps, optimize the fault location process, and improve the fault location efficiency in AIoT terminal fault scenarios.

[0007] Firstly, this application provides a fault location method, which can be executed by a device with computing capabilities or a component of a device with computing capabilities (such as a chip or module). For example, the method can be executed by an AIoT fault producer or the device in which the AIoT fault producer is located. Alternatively, the method can be executed by an AIoT agent. The following description uses an AIoT fault producer as the executing entity of this method as an example; in actual implementation, the executing entity of this method can be other devices or have other names.

[0008] The fault location method includes: receiving a first message from an AIoT consumer device, obtaining first sensor information of the problematic terminal, and sending a fault indication to the AIoT consumer device. The first message includes the identity information of the problematic terminal, which is an AIoT terminal device, and the AIoT terminal device includes sensors. The fault indication is obtained based on the first sensor information and is used to indicate whether the problematic terminal itself has malfunctioned.

[0009] Optionally, AIoT terminal devices can also be called AIoT terminals or AIoT user devices, etc., and there are no restrictions on the naming.

[0010] Based on the above scheme, after receiving the first message, the AIoT fault handling module can obtain the identity information of the problematic AIoT terminal device. Furthermore, the AIoT fault handling module can acquire the sensor information of the AIoT terminal device and determine whether the AIoT terminal device itself has malfunctioned based on this sensor information. If the AIoT terminal device itself malfunctions, this application can greatly simplify the fault location steps and optimize the fault location process, eliminating the need to sequentially check alarms or abnormal information at the IoT platform, core network, base station, and finally the terminal, thus effectively improving the fault location efficiency in AIoT terminal fault scenarios.

[0011] In one possible implementation of the first aspect, the problematic terminal is an AIoT terminal device that has not reported data, and / or, the problematic terminal is an AIoT terminal device with data anomalies.

[0012] In another possible implementation of the first aspect, the service type of the problematic terminal includes sensing services.

[0013] Optionally, the service type of the problematic terminal includes sensing-related services, meaning the sensor information of the problematic terminal is directly used for the services targeted by the problematic terminal. Alternatively, the service type of the problematic terminal includes sensing-related services, meaning the sensor information of the problematic terminal is not directly used for the services targeted by the problematic terminal, but rather reflects the environmental state of the problematic terminal itself.

[0014] In conjunction with the first aspect, the above embodiments illustrate that the service types of AIoT faulty terminals include sensing services. Therefore, the AIoT fault handling module can determine whether the AIoT terminal device itself has malfunctioned based on the sensor information of the AIoT terminal device.

[0015] In another possible implementation of the first aspect, the first sensor information is used to indicate the service status of the problematic terminal, or the environmental state in which the problematic terminal is located.

[0016] The first sensor information is used to indicate the service status of the problematic terminal. For example, the first sensor information is directly used for the services that the problematic terminal is dealing with. If the sensor information is abnormal, the service status of the problematic terminal is likely to malfunction, and the problematic terminal itself is also likely to malfunction. The environmental conditions in which the problematic terminal is located, such as the ambient temperature or humidity, also play a role. When the ambient temperature of the problematic terminal is too high, the probability of it malfunctioning is also high.

[0017] In another possible implementation of the first aspect, the first sensor information includes sensing data, and the first sensor information also includes at least one of the following: the identity information of the problematic terminal, the service type, the sensing parameter type, the sensing time, and the sensing location.

[0018] In yet another possible implementation of the first aspect, the first message further includes a fault time, the sensing data being data prior to the fault time, and / or the first message further includes a fault location, the sensing data being related to the fault location.

[0019] In the above embodiments, the fault time and / or fault location can be used to acquire sensor data, which can acquire the required sensor data more accurately and avoid acquiring too much sensor data, thus wasting transmission resources.

[0020] In another possible implementation of the first aspect, the first message further includes a fault type, which is used to determine a fault indication, and / or, the fault type is used to acquire first sensor information.

[0021] Optionally, the fault type can be used to initially determine the fault indication. For example, if the fault type is offline, the problem terminal itself is more likely to have malfunctioned, and other steps in this application can be used to determine whether the problem terminal itself has malfunctioned. Similarly, if the fault type is data transmission failure or reduced transmission rate, the problem terminal is more likely to have malfunctioned on the network side, and anomaly checks on the network side can be prioritized.

[0022] In another possible implementation of the first aspect, obtaining the first sensor information of the problematic terminal includes: sending a second message to a first device and receiving the first sensor information from the first device. The second message includes the identity information of the problematic terminal, and the first device is an AIoT monitoring module or a knowledge base.

[0023] In the above implementation, the AIoT fault handling module sends the identity information of the problematic terminal to the first device, enabling the AIoT fault handling module to receive the sensor information corresponding to the problematic terminal, obtain the required sensor information more accurately, and avoid wasting transmission resources.

[0024] In another possible implementation of the first aspect, the first message further includes a fault time, and the second message further includes a fault time.

[0025] In another possible implementation of the first aspect, the first message further includes the fault location, and the second message further includes the fault location.

[0026] In another possible implementation of the first aspect, obtaining the first sensor information of the problem terminal includes: receiving the first sensor information from the AIoT consumer device.

[0027] In the above embodiments, the sensor information of the problematic terminal can be obtained from the AIoT consumer device, so as to determine whether the problematic terminal itself has malfunctioned based on the sensor information of the problematic terminal, thereby simplifying the fault location steps, optimizing the fault location process, and effectively improving the fault location efficiency in AIoT terminal fault scenarios.

[0028] In another possible implementation of the first aspect, when the first sensor information meets a predefined abnormal condition, a fault indication is used to indicate that the problematic terminal itself has malfunctioned. The abnormal condition includes at least one of the following: the number of data points in the first sensor information that exceed the normal value range is greater than a first threshold; the first sensor information includes multiple data points; the measured value of a parameter in the first sensor information related to the normal operation of the problematic terminal is close to or exceeds the threshold value of the parameter for normal operation of the problematic terminal; or the first sensor information contains an abnormal value.

[0029] When sensor information meets predefined abnormal conditions, it can be determined that the faulty terminal itself has malfunctioned. This can simplify the fault location steps, optimize the fault location process, and effectively improve the fault location efficiency in AIoT terminal fault scenarios.

[0030] In another possible implementation of the first aspect, the method further includes: determining a fault indication based on first sensor information and environmental sensor information, wherein the first sensor information and environmental sensor information include data of the same type of sensing parameter.

[0031] In another possible implementation of the first aspect, the second message further includes a first source type, wherein the source type corresponding to the first sensor information is the first source type, which is used to indicate that the source of the sensing data is an AIoT terminal device. The method further includes: determining the abnormal sensing information of the problematic terminal based on the first sensor information, sending a third message to the AIoT monitoring module, and receiving environmental sensor information from the AIoT monitoring module. The abnormal sensing information belongs to the first sensor information. The third message includes a second source type and the first information. The second source type indicates that the source of the sensing data is not an AIoT terminal device. The first information includes an abnormal sensing parameter type, which is the sensing parameter type of the abnormal information. The sensing parameter type of the environmental sensor information includes the abnormal parameter type.

[0032] In the above embodiments, the sensor data in the sensor information of the problematic terminal comes from the AIoT terminal device. The AIoT fault handling module can determine the abnormal sensor information based on the sensor information of the problematic terminal, and obtain environmental sensor information whose sensor data does not come from the AIoT terminal device (e.g., from a non-AIoT terminal device). The sensor parameter types of the environmental sensor information include the abnormal sensor parameter types corresponding to the abnormal sensor information. Therefore, the AIoT fault handling module can jointly determine whether the problematic terminal itself has malfunctioned based on the sensor information of the problematic terminal and the environmental sensor information, which can improve the accuracy of the judgment.

[0033] In another possible implementation of the first aspect, the first information further includes the abnormal time corresponding to the abnormal sensing information, and the environmental sensor information further includes the sensor information corresponding to the abnormal time.

[0034] In the above embodiments, the environmental sensor information needs to include sensor information corresponding to the abnormal time, so that it can be used together with the sensor information of the problematic terminal to determine whether the problematic terminal itself has malfunctioned, thereby improving the accuracy of the judgment.

[0035] In another possible implementation of the first aspect, the first information further includes the abnormal location corresponding to the abnormal sensing information, and the environmental sensor information further includes the sensor information corresponding to the abnormal location.

[0036] In the above embodiments, the environmental sensor information needs to include sensor information corresponding to the abnormal location, so that it can be used together with the sensor information of the problematic terminal to determine whether the problematic terminal itself has malfunctioned, thereby improving the accuracy of the judgment.

[0037] In another possible implementation of the first aspect, when the difference between the abnormal sensing information and the environmental sensor information meets a preset difference condition, the fault indication is used to indicate that the problematic terminal itself has malfunctioned.

[0038] For example, if the preset difference condition is that the difference between the abnormal sensor information and the environmental sensor information is greater than the preset difference threshold, the probability of the problematic terminal itself malfunctioning is relatively high. The AIoT fault handling module can determine that the problematic terminal itself has malfunctioned, which can simplify the fault location steps, optimize the fault location process, and effectively improve the fault location efficiency in AIoT terminal fault scenarios.

[0039] In another possible implementation of the first aspect, obtaining the first sensor information of the problematic terminal includes: receiving a fourth message from the problematic terminal, the fourth message including the abnormal time and / or abnormal location corresponding to the sensor information of the problematic terminal.

[0040] In the above embodiments, the faulty terminal can determine whether it has malfunctioned based on sensor information and send the abnormal time and / or abnormal location to the AIoT fault handling module. This allows the AIoT fault handling module to determine whether the faulty terminal has malfunctioned based on the abnormal time and / or abnormal location, which simplifies the fault location steps, optimizes the fault location process, and effectively improves the fault location efficiency in AIoT terminal fault scenarios.

[0041] In another possible implementation of the first aspect, the first message further includes the fault location, the fourth message includes the abnormal location corresponding to the sensor information of the problematic terminal, and the method further includes: determining a fault indication based on the fault location and the abnormal location.

[0042] For example, if the abnormal location is near the fault location multiple times, the probability of the problematic terminal itself malfunctioning is relatively high. The AIoT fault handling module can determine that the problematic terminal itself has malfunctioned, which can simplify the fault location steps, optimize the fault location process, and effectively improve the fault location efficiency in AIoT terminal fault scenarios.

[0043] In another possible implementation of the first aspect, the first message further includes a fault time, the fourth message includes an abnormal time corresponding to the sensor information of the problematic terminal, and the method further includes: determining a fault indication based on the fault time and the abnormal time.

[0044] For example, if the abnormal time is repeatedly close to the fault time, the probability of the problematic terminal itself malfunctioning is relatively high. The AIoT fault handling module can determine that the problematic terminal itself has malfunctioned, which can simplify the fault location steps, optimize the fault location process, and effectively improve the fault location efficiency in AIoT terminal fault scenarios.

[0045] In another possible implementation of the first aspect, the first device is a knowledge base, the first sensor information includes sensing parameter types, and the method further includes: determining a sensor troubleshooting tool based on the sensing parameter types, sending a fifth message to the tool library, receiving sensor troubleshooting tool call results from the tool library, and determining a fault indication based on the sensor troubleshooting tool call results. The fifth message includes the name of the sensor troubleshooting tool, the sensing data of the problematic terminal, and application data reference values.

[0046] In the above embodiments, the fault location method of this application can also be applied to the A-Platform architecture. The AIoT fault handling module can call the corresponding sensor troubleshooting tools through the tool library, and determine whether the faulty terminal itself has malfunctioned based on the call results of the sensor troubleshooting tools. This can simplify the fault location steps, optimize the fault location process, and effectively improve the fault location efficiency in AIoT terminal fault scenarios.

[0047] Secondly, this application provides another fault location method, which can be executed by a device with computing capabilities or a component (such as a chip or module) of a device with computing capabilities. For example, the method can be executed by an AIoT terminal device (such as an AIoT UE) or a component (such as a chip or module) within an AIoT terminal device. The following description uses an AIoT terminal device as the executing entity of this method as an example. In actual implementation, the executing entity of this method can be other devices or have other names.

[0048] The fault location method includes sending a fourth message to the AIoT fault handling module. The AIoT fault handling module determines whether the problematic terminal itself has malfunctioned. The problematic terminal is an AIoT terminal device, which includes sensors. The fourth message includes the abnormal time and / or abnormal location corresponding to the sensor information of the problematic terminal.

[0049] Based on the above solution, the AIoT terminal device can determine whether it has malfunctioned based on sensor information and send the abnormal time and / or abnormal location to the AIoT fault handling module. This allows the AIoT fault handling module to determine whether the terminal itself has malfunctioned based on the abnormal time and / or abnormal location, which simplifies the fault location steps, optimizes the fault location process, and effectively improves the fault location efficiency in AIoT terminal fault scenarios.

[0050] In one possible implementation of the second aspect, the measured values ​​of parameters related to the normal operation of the problematic terminal in the sensor information of the problematic terminal are close to or exceed the threshold values ​​of the parameters for the normal operation of the problematic terminal.

[0051] In the above embodiments, the problematic terminal is in a working extreme environment. At this time, the problematic terminal actively sends the abnormal time and / or abnormal location so that the AIoT fault handling module can determine whether the problematic terminal itself has failed based on the abnormal time and / or abnormal location. This can simplify the fault location steps, optimize the fault location process, and effectively improve the fault location efficiency in AIoT terminal failure scenarios.

[0052] In another possible implementation of the second aspect, the method further includes: sending sensor information of the AIoT terminal device. The sensor information of the AIoT terminal device includes sensing data, and further includes at least one of the following: the AIoT terminal device's identity information, service type, sensing parameter type, sensing time, and sensing location.

[0053] In the above embodiments, the AIoT terminal device sends its sensor information so that the AIoT fault handling module can determine whether the AIoT terminal device itself has malfunctioned based on the sensor information. This simplifies the fault location steps, optimizes the fault location process, and effectively improves the fault location efficiency in AIoT terminal fault scenarios.

[0054] Thirdly, this application provides another fault location method, which can be executed by a device with computing capabilities or a component (such as a chip or module) of a device with computing capabilities. For example, the method can be executed by an AIoT consumer device or a component (such as a chip or module) within an AIoT consumer device. The following description uses an AIoT consumer device as the executing entity for example; in actual implementation, the executing entity of this method can be other devices or have other names.

[0055] The fault location method includes: sending a first message to the AIoT fault handling module and receiving a fault indication from the AIoT fault handling module. The first message includes the identity information of the problematic terminal, which is an AIoT terminal device. The AIoT terminal device includes sensors, and the fault indication is used to indicate whether the problematic terminal itself has malfunctioned.

[0056] Based on the above scheme, when an AIoT consumer device discovers an AIoT terminal device that has not reported data, and / or an AIoT terminal device with abnormal data, it can send the identity information of the AIoT terminal device (i.e., the problematic terminal) to the AIoT fault handling module. This allows the AIoT fault handling module to obtain the sensor information of the problematic terminal and determine whether the problematic terminal itself has malfunctioned based on the sensor information. This simplifies the fault location steps, optimizes the fault location process, and effectively improves the fault location efficiency in AIoT terminal fault scenarios.

[0057] In one possible implementation of the third aspect, the method further includes: sending first sensor information of the problematic terminal to the AIoT fault handling module. The first sensor information is used to determine a fault indication, and includes sensing data. The first sensor information also includes at least one of the following: the problematic terminal's identity information, service type, sensing parameter type, sensing time, and sensing location.

[0058] Fourthly, this application provides another fault location method, which can be executed by a device with computing capabilities or a component (such as a chip or module) of a device with computing capabilities. For example, the method can be executed by an AIoT monitoring module or the device in which the AIoT monitoring module is located. Alternatively, the method can be executed by a knowledge base or the device in which the knowledge base is located. The following explanation uses an AIoT monitoring module as the executing entity of this method; in actual implementation, the executing entity of this method can be other devices or have other names.

[0059] The fault location method includes: sending a sixth message, receiving sensor information from the AIoT terminal device, and sending the first sensor information of the problematic terminal to the AIoT fault handling module. The sixth message includes the identity information of the AIoT terminal device, and the sensor information includes the sensing data of the AIoT terminal device. The problematic terminal is an AIoT terminal device, which includes sensors. The first sensor information is the sensor information of the AIoT terminal device and is used to determine a fault indication, which indicates whether the problematic terminal itself has malfunctioned.

[0060] Based on the above scheme, the AIoT monitoring module can receive sensor information from AIoT terminal devices and send the sensor information of the problematic terminal to the AIoT fault handling module. This allows the AIoT fault handling module to determine whether the problematic terminal itself has malfunctioned based on the sensor information of the problematic terminal, which can simplify the fault location steps, optimize the fault location process, and effectively improve the fault location efficiency in AIoT terminal fault scenarios.

[0061] In one possible implementation of the fourth aspect, the sensor information of the AIoT terminal device further includes at least one of the following: the identity information of the AIoT terminal device, the service type, the sensing parameter type, the sensing time, and the sensing location.

[0062] In one possible implementation of the fourth aspect, the method further includes: receiving a second message from the AIoT fault handling module, the second message including the identity information of the faulty terminal.

[0063] Fifthly, this application provides a fault location device, which includes a transceiver unit. The transceiver unit receives a first message from an AIoT consumer device, obtains first sensor information of a faulty terminal, and sends a fault indication to the AIoT consumer device. The first message includes the identity information of the faulty terminal, which is an AIoT terminal device, and the AIoT terminal device includes sensors. The fault indication is obtained based on the first sensor information and is used to indicate whether the faulty terminal itself has malfunctioned.

[0064] In one possible implementation of the fifth aspect, the problematic terminal is an AIoT terminal device that has not reported data, and / or, the problematic terminal is an AIoT terminal device with data anomalies.

[0065] In another possible implementation of the fifth aspect, the service type of the problematic terminal includes sensing services.

[0066] In another possible implementation of the fifth aspect, the first sensor information is used to indicate the service status of the problematic terminal, or the environmental state in which the problematic terminal is located.

[0067] In another possible implementation of the fifth aspect, the first sensor information includes sensing data, and the first sensor information also includes at least one of the following: the identity information of the problematic terminal, the service type, the sensing parameter type, the sensing time, and the sensing location.

[0068] In another possible implementation of the fifth aspect, the first message further includes a fault time, the sensing data being data prior to the fault time, and / or the first message further includes a fault location, the sensing data being related to the fault location.

[0069] In another possible implementation of the fifth aspect, the first message further includes a fault type, which is used to determine a fault indication, and / or, the fault type is used to acquire first sensor information.

[0070] In another possible implementation of the fifth aspect, the transceiver unit is further configured to send a second message to the first device and receive first sensor information from the first device. The second message includes the identity information of the problematic terminal, and the first device is an AIoT monitoring module or a knowledge base.

[0071] In another possible implementation of the fifth aspect, the first message further includes the fault time, and the second message further includes the fault time.

[0072] In another possible implementation of the fifth aspect, the first message further includes the fault location, and the second message further includes the fault location.

[0073] In another possible implementation of the fifth aspect, the transceiver unit is also configured to receive first sensor information from an AIoT consumer device.

[0074] In another possible implementation of the fifth aspect, when the first sensor information meets a predefined abnormal condition, a fault indication is used to indicate that the problematic terminal itself has malfunctioned. The abnormal condition includes at least one of the following: the number of data points in the first sensor information that exceed the normal range is greater than a first threshold; the first sensor information includes multiple data points; the measured value of a parameter in the first sensor information related to the normal operation of the problematic terminal is close to or exceeds the threshold value of the parameter for normal operation of the problematic terminal; or the first sensor information contains an abnormal value.

[0075] In another possible implementation of the fifth aspect, the fault location device further includes a processing unit for determining a fault indication based on first sensor information and environmental sensor information, wherein the first sensor information and environmental sensor information include data of the same type of sensing parameters.

[0076] In another possible implementation of the fifth aspect, the second message further includes a first source type, the source type corresponding to the first sensor information being the first source type, which indicates that the source of the sensing data is an AIoT terminal device. The processing unit is further configured to determine the abnormal sensing information of the problematic terminal based on the first sensor information. The transceiver unit is further configured to send a third message to the AIoT monitoring module and receive environmental sensor information from the AIoT monitoring module. The abnormal sensing information belongs to the first sensor information. The third message includes a second source type and the first information. The second source type indicates that the source of the sensing data is not an AIoT terminal device. The first information includes an abnormal sensing parameter type, which is the sensing parameter type of the abnormal sensing information. The sensing parameter type of the environmental sensor information includes the abnormal parameter type.

[0077] In another possible implementation of the fifth aspect, the first information further includes the abnormal time corresponding to the abnormal sensing information, and the environmental sensor information further includes the sensor information corresponding to the abnormal time.

[0078] In another possible implementation of the fifth aspect, the first information further includes the abnormal location corresponding to the abnormal sensing information, and the environmental sensor information further includes the sensor information corresponding to the abnormal location.

[0079] In another possible implementation of the fifth aspect, when the difference between the abnormal sensing information and the environmental sensor information meets a preset difference condition, the fault indication is used to indicate that the problematic terminal itself has malfunctioned.

[0080] In another possible implementation of the fifth aspect, the transceiver unit is further configured to receive a fourth message from the problematic terminal, the fourth message including the abnormal time and / or abnormal location corresponding to the sensor information of the problematic terminal.

[0081] In another possible implementation of the fifth aspect, the first message further includes the fault location, the fourth message includes the abnormal location corresponding to the sensor information of the problematic terminal, and the processing unit is further configured to determine a fault indication based on the fault location and the abnormal location.

[0082] In another possible implementation of the fifth aspect, the first message further includes the fault time, the fourth message includes the abnormal time corresponding to the sensor information of the problematic terminal, and the processing unit is further configured to determine a fault indication based on the fault time and the abnormal time.

[0083] In another possible implementation of the fifth aspect, the first device is a knowledge base, the first sensor information includes sensing parameter types, and the processing unit is further configured to determine a sensor troubleshooting tool based on the sensing parameter types. The transceiver unit is further configured to send a fifth message to the tool library and receive sensor troubleshooting tool call results from the tool library. The processing unit is further configured to determine a fault indication based on the sensor troubleshooting tool call results. The fifth message includes the name of the sensor troubleshooting tool, the sensing data of the problematic terminal, and application data reference values.

[0084] Sixthly, this application provides another fault location device, which includes a transceiver unit for sending a fourth message to an AIoT fault handling module. The AIoT fault handling module determines whether the faulty terminal itself has malfunctioned. The faulty terminal is an AIoT terminal device, which includes sensors. The fourth message includes the abnormal time and / or abnormal location corresponding to the sensor information of the faulty terminal.

[0085] In one possible implementation of the sixth aspect, the measured values ​​of parameters related to the normal operation of the problematic terminal in the sensor information of the problematic terminal are close to or exceed the threshold values ​​of the parameters for the normal operation of the problematic terminal.

[0086] In another possible implementation of the sixth aspect, the transceiver unit is further configured to transmit sensor information of the AIoT terminal device. The sensor information includes sensing data, and further includes at least one of the following: the problem terminal's identity information, service type, sensing parameter type, sensing time, and sensing location.

[0087] Seventhly, this application provides another fault location device, which includes a transceiver unit for sending a first message to an AIoT fault handling module and receiving a fault indication from the AIoT fault handling module. The first message includes the identity information of the problematic terminal, which is an AIoT terminal device including sensors. The fault indication is used to indicate whether the problematic terminal itself has malfunctioned.

[0088] In one possible implementation of the seventh aspect, the transceiver unit is further configured to send first sensor information of the problematic terminal to the AIoT fault handling module. The first sensor information is used to determine a fault indication, and includes sensing data. The first sensor information also includes at least one of the following: the problematic terminal's identity information, service type, sensing parameter type, sensing time, and sensing location.

[0089] Eighthly, this application provides another fault location device, which includes a transceiver unit for sending a sixth message, receiving sensor information from an AIoT terminal device, and sending first sensor information of the problematic terminal to an AIoT fault handling module. The sixth message includes the identity information of the AIoT terminal device, and the sensor information includes the sensing data of the AIoT terminal device. The problematic terminal is an AIoT terminal device, which includes sensors. The first sensor information is the sensor information of the AIoT terminal device and is used to determine a fault indication, which indicates whether the problematic terminal itself has malfunctioned.

[0090] In one possible implementation of the eighth aspect, the sensor information of the AIoT terminal device further includes at least one of the following: the identity information of the AIoT terminal device, the service type, the sensing parameter type, the sensing time, and the sensing location.

[0091] In another possible implementation of the eighth aspect, the transceiver unit is further configured to receive a second message from the AIoT fault handling module, the second message including the identity information of the faulty terminal.

[0092] Ninthly, embodiments of this application provide a chip system including at least one processor and a communication interface. The communication interface is used to send and / or receive data. The at least one processor is used to call a computer program stored in at least one memory, so that a fault location device in which the chip system is located implements the method described in the first aspect or any possible implementation of the first aspect, implements the method described in the second aspect or any possible implementation of the second aspect, implements the method described in the third aspect or any possible implementation of the third aspect, or implements the method described in the fourth aspect or any possible implementation of the fourth aspect.

[0093] In a tenth aspect, embodiments of this application provide yet another fault location device, including at least one processor and a communication interface, the communication interface being used to send and / or receive data, and the at least one processor being used to invoke a computer program stored in at least one memory, so that the fault location device implements the method described in the first aspect or any possible implementation of the first aspect, implements the method described in the second aspect or any possible implementation of the second aspect, implements the method described in the third aspect or any possible implementation of the third aspect, or implements the method described in the fourth aspect or any possible implementation of the fourth aspect.

[0094] Eleventhly, embodiments of this application provide a network system including the aforementioned problematic terminal, AIoT fault handling module, and AIoT consumer device. The problematic terminal includes the fault location device as described in the fifth aspect, the AIoT fault handling module includes the fault location device as described in the sixth aspect, and the AIoT consumer device includes the fault location device as described in the seventh aspect. The network system is used to implement the method described in any possible implementation of the first, second, or third aspect.

[0095] In a twelfth aspect, embodiments of this application provide yet another network system, including the aforementioned problematic terminal, first device, AIoT fault handling module, and AIoT consumer device. The problematic terminal includes a fault location device as described in the fifth aspect, the first device includes a fault location device as described in the eighth aspect, the AIoT fault handling module includes a fault location device as described in the sixth aspect, and the AIoT consumer device includes a fault location device as described in the seventh aspect. The network system is used to implement the methods described in any possible implementation of the first, second, third, or fourth aspects. Optionally, the first device may be an AIoT monitoring module or a knowledge base.

[0096] In a thirteenth aspect, embodiments of this application disclose a computer-readable storage medium storing a computer program that, when executed on one or more processors, causes a fault location device on which the computer-readable storage medium is located to implement the method described in the first aspect or any possible implementation of the first aspect, the method described in the second aspect or any possible implementation of the second aspect, the method described in the third aspect or any possible implementation of the third aspect, or the method described in the fourth aspect or any possible implementation of the fourth aspect.

[0097] In a fourteenth aspect, embodiments of this application disclose a computer program product that, when running on one or more processors, causes a fault location device containing the computer program product to implement the method described in the first aspect or any possible implementation of the first aspect, the method described in the second aspect or any possible implementation of the second aspect, the method described in the third aspect or any possible implementation of the third aspect, or the method described in the fourth aspect or any possible implementation of the fourth aspect.

[0098] The solutions provided in aspects five through fourteen above are used to implement or cooperate with the methods provided in aspects one, two, three, or four above. Therefore, they can achieve the same or corresponding beneficial effects as the methods in aspects one, two, three, or four above, which will not be elaborated here. Attached Figure Description

[0099] The accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0100] Figure 1a is a schematic diagram of the architecture of an AIoT network system according to an embodiment of this application;

[0101] Figure 1b is a schematic diagram of the connection relationship of an AIoT network system according to an embodiment of this application;

[0102] Figure 2a is a schematic diagram of the architecture of another AIoT network system provided in an embodiment of this application;

[0103] Figure 2b is a schematic diagram of the connection relationship of another AIoT network system provided in an embodiment of this application;

[0104] Figure 3 is a flowchart illustrating a fault location method provided in an embodiment of this application;

[0105] Figure 4 is a flowchart illustrating another possible fault location method provided in an embodiment of this application;

[0106] Figure 5 is a flowchart illustrating another possible fault location method provided in an embodiment of this application;

[0107] Figure 6 is a flowchart illustrating another possible fault location method provided in an embodiment of this application;

[0108] Figure 7 is a flowchart illustrating another possible fault location method provided in an embodiment of this application;

[0109] Figure 8 is a flowchart illustrating another possible fault location method provided in an embodiment of this application;

[0110] Figure 9 is a structural schematic diagram of a fault location device provided in an embodiment of this application;

[0111] Figure 10 is a structural schematic diagram of another fault location device provided in an embodiment of this application;

[0112] Figure 11 is a structural schematic diagram of another fault location device provided in an embodiment of this application;

[0113] Figure 12 is a structural schematic diagram of another fault location device provided in an embodiment of this application;

[0114] Figure 13 is a structural schematic diagram of another fault location device provided in an embodiment of this application. Detailed Implementation

[0115] The following describes the architecture and business scenarios of communication systems to which the embodiments of this application can be applied. It should be noted that the system architecture and business scenarios described in this application are for the purpose of more clearly illustrating the technical solutions of this application and do not constitute a limitation on the technical solutions provided in this application. It should be understood that as system architectures evolve and new business scenarios emerge, the technical solutions provided in this application are also applicable to similar technical problems.

[0116] This application can be applied to AIoT systems, which are Internet of Things (IoT) technologies that utilize ambient energy for power supply, enabling low-cost, self-powered IoT device connectivity. AIoT powers devices by collecting energy from the environment (such as light, heat, wind, waves, sound, electromagnetic radiation, and mechanical vibration), thereby eliminating reliance on traditional batteries, reducing maintenance costs, and improving device usability.

[0117] The architecture of an AIoT network system is described below with reference to Figure 1a. The AIoT network system 10 shown in Figure 1a includes an AIoT terminal device 101, an AIoT consumer device 102, and an AIoT fault handling module 103. Optionally, the AIoT network system 10 also includes an AIoT monitoring module 104. Wherein:

[0118] AIoT terminal device 101, also referred to in some embodiments as an AIoT terminal or AIoT user equipment (UE), is a device with communication capabilities. AIoT terminal device 101 includes sensors, such as smart locks, smart lights, and smart meters. For example, sensors in a smart lock can determine the unlocking and locking delays, sensors in a smart light can determine the turning-on and turning-off delays, and sensors in a smart meter can acquire the user's heartbeat data. Optionally, AIoT terminal device 101 can report the sensor data (also known as application data) from its sensors to AIoT consumer device 102 via a network.

[0119] AIoT consumer device 102, also referred to as AIoT consumer in some embodiments, is a device with communication capabilities.

[0120] Optionally, the server hosting the AIoT consumer device 102 can obtain sensor data (also known as application data) from the sensors in the AIoT terminal device 101 and perform business processing based on the sensor data. In one possible implementation, the AIoT terminal device 101 may not report data to the server hosting the AIoT consumer device 102. In this case, the server hosting the AIoT consumer device 102 can consider the AIoT terminal device 101 to have a problem and mark it as a problematic terminal. In another possible implementation, the data of the AIoT terminal device 101 may be abnormal. In this case, the server hosting the AIoT consumer device 102 can consider the AIoT terminal device 101 to have a problem and mark it as a problematic terminal. The server hosting the AIoT consumer device 102 can send a first message to the AIoT consumer device 102. The first message includes the identity information of the problematic terminal. The identity information of the problematic terminal is used to identify the identity of the problematic terminal and may be an identification (ID), account, unique code, exclusive number, address, etc. The problematic terminal belongs to the AIoT terminal device 101. Optionally, the AIoT consumer device 102 has processing capabilities. For example, AIoT consumer device 102 can acquire sensor data (also known as application data) from sensors in AIoT terminal device 101 and perform business processing based on the sensor data. For instance, AIoT consumer device 102 can acquire heartbeat data from a smart meter and monitor the user's physical condition based on the heartbeat data. In one possible implementation, AIoT terminal device 101 may fail to report data to AIoT consumer device 102. In this case, AIoT consumer device 102 can consider AIoT terminal device 101 to have a problem and mark it as a problematic terminal. For example, if the smart meter loses heartbeat data packets, AIoT consumer device 102 can consider the smart meter a problematic terminal. In another possible implementation, the data from AIoT terminal device 101 may be abnormal. In this case, AIoT consumer device 102 can consider AIoT terminal device 101 to have a problem and mark it as a problematic terminal. For example, if the unlocking or locking delay of a smart lock exceeds the normal delay threshold, AIoT consumer device 102 can consider the smart lock a problematic terminal.

[0121] Furthermore, the AIoT consumer device 102 can send a first message to the AIoT fault handling module 103.

[0122] The AIoT fault handling module 103, also referred to in some embodiments as an AIoT fault producer, is a device with communication and processing capabilities. Optionally, the AIoT fault handling module 103 can acquire sensor information of the problematic terminal and determine a fault indication based on this information. The fault indication indicates whether the problematic terminal itself has malfunctioned. Optionally, the AIoT fault handling module 103 sends the fault indication to the AIoT consumer device 102. In one possible implementation, the AIoT fault handling module 103 can directly acquire the sensor information of the problematic terminal through communication between the AIoT terminal device 101 and the AIoT fault handling module 103. In another possible implementation, the AIoT fault handling module 103 can directly acquire the sensor information of the problematic terminal through communication between the AIoT consumer device 102 and the AIoT fault handling module 103. In yet another possible implementation, the AIoT fault handling module 103 can indirectly acquire the sensor information of the problematic terminal through the AIoT monitoring module 104.

[0123] The AIoT monitoring module 104, also referred to as the AIoT monitoring module in some embodiments, is a device with communication capabilities. Exemplarily, the AIoT monitoring module 104 can be used to store sensor information of the AIoT terminal device 101 and send the sensor information of the problematic terminal to the AIoT fault handling module 103. Alternatively, the AIoT monitoring module 104 can receive and process the sensor information of the AIoT terminal device 101, and then send the sensor information of the problematic terminal to the AIoT fault handling module 103. For example, the AIoT monitoring module 104 acquires the sensing data of the AIoT terminal device 101 at time A and the sensing data at time B, calculates the result (e.g., the difference between the sensing data at time B and the sensing data at time A), and sends the calculated result (e.g., the difference between the sensing data at time B and the sensing data at time A) to the AIoT fault handling module 103.

[0124] In one possible implementation, the AIoT monitoring module 104 sends a sixth message to the radio access network (RAN). The RAN obtains the sensor information of the corresponding AIoT terminal device 101 based on the sixth message and sends this sensor information back to the AIoT monitoring module 104. The sixth message includes the identity information of the AIoT terminal device 101, which identifies the AIoT terminal device 101 and can be an identification ID, account, unique code, dedicated number, address, etc.

[0125] AIoT consumer device 102 and AIoT terminal device 101 are network connected, as shown in Figure 1b. In Figure 1b, the AIoT consumer device resides on a third-party entity server (e.g., a third-party entity). The AIoT consumer device can send a first message, which includes the identity information of the problematic terminal. The first message is forwarded by the cross-domain manager (network management system, NMS) to the single-domain manager (element management system, EMS). The AIoT fault handling module and the AIoT monitoring module reside on the EMS. The AIoT fault handling module receives the first message. The AIoT monitoring module acquires and saves the sensor information of the AIoT terminal device through the RAN. The RAN acquires the sensor information of the AIoT terminal device sent by the AIoT terminal device and sends it to the AIoT monitoring module. The AIoT monitoring module sends the sensor information of the problematic terminal to the AIoT fault handling module, so that the AIoT fault handling module can determine whether the problematic terminal itself has malfunctioned based on the sensor information of the problematic terminal.

[0126] In this application, the AIoT consumer device 102 can send a first message to the AIoT fault handling module 103, which can obtain the identity information of the problematic terminal. The AIoT fault handling module 103 can acquire the sensor information of the problematic terminal and determine a fault indication based on the sensor information. The first message includes the identity information of the problematic terminal, and the fault indication indicates whether the problematic terminal itself has malfunctioned. In other words, the AIoT fault handling module can determine whether the problematic terminal itself has malfunctioned based on the sensor information of the problematic terminal. If the AIoT terminal device itself malfunctions, this application can greatly simplify the fault location steps and optimize the fault location process, eliminating the need to sequentially check alarms or abnormal information at the IoT platform, core network, base station, and finally the terminal, effectively improving the efficiency of fault location in AIoT terminal fault scenarios.

[0127] The following describes the architecture of another AIoT network system with reference to Figure 2a. The AIoT network system 20 shown in Figure 2a includes an AIoT terminal device 101, an AIoT consumer device 102, an AIoT fault handling module 103, a knowledge base 105, and a tool library 106. Among them:

[0128] The AIoT terminal device 101, AIoT consumer device 102, and AIoT fault handling module 103 are described in the foregoing. In the AIoT network system 20, the AIoT fault handling module 103 can be referred to as an AIoT agent.

[0129] In some embodiments, the knowledge base 105, also referred to as a Data Base, is a device with communication capabilities. For example, the knowledge base 105 can be used to store sensor information of the AIoT terminal device 101 and send the sensor information of the problematic terminal to the AIoT fault handling module 103. Alternatively, the knowledge base 105 can be used to receive and process the sensor information of the AIoT terminal device 101, and then send the sensor information of the problematic terminal to the AIoT fault handling module 103. For instance, the knowledge base 105 acquires the sensing data of the AIoT terminal device 101 at time A and the sensing data at time B, calculates the result (e.g., the difference between the sensing data at time B and the sensing data at time A), and sends the result calculated by the AIoT monitoring module 104 (e.g., the difference between the sensing data at time B and the sensing data at time A) to the AIoT fault handling module 103.

[0130] In one possible implementation, the knowledge base 105 sends a sixth message to the radio access network (RAN). The RAN obtains the sensor information of the corresponding AIoT terminal device 101 based on the sixth message and sends the sensor information of the AIoT terminal device 101 back to the knowledge base 105. The sixth message includes the identity information of the AIoT terminal device 101.

[0131] Tool library 106 is a device with communication and processing capabilities. For example, tool library 106 can receive a fifth message sent by AIoT fault handling module 103, the fifth message including the name of a sensor troubleshooting tool, the sensor data of the problematic terminal, and application data reference values. Tool library 106 can invoke the corresponding tool based on the name of the sensor troubleshooting tool, and obtain the sensor troubleshooting tool invocation result based on the sensor data and application data reference values ​​of the problematic terminal. Further, tool library 106 can send the sensor troubleshooting tool invocation result to AIoT fault handling module 103, so that AIoT fault handling module 103 can determine a fault indication based on the sensor troubleshooting tool invocation result.

[0132] AIoT consumer device 102 and AIoT terminal device 101 are network-connected, as shown in Figure 2b. In Figure 2b, the AIoT consumer device resides on a third-party entity server (e.g., a 3rd party entity). The AIoT consumer device can send a first message, which includes the identity information of the problematic terminal. The AIoT agent (i.e., the AIoT fault handling module 103), knowledge base, and tool library reside in the Operation Support Systems (OSS). The AIoT agent receives the first message through the agent communication interface-network (ACI-N) or R1 interface. The knowledge base stores sensor information of the AIoT terminal device, and the tool library stores sensor troubleshooting tools related to the sensor information of the AIoT terminal device. The knowledge base obtains the sensor information of the AIoT terminal device sent by the core network (CN) through the agent communication interface-policy (ACI-P). The CN obtains the sensor information of the AIoT terminal device sent by the AIoT terminal device and sends it to the knowledge base. The knowledge base sends sensor information of the problematic terminal to the AIoT agent, so that the AIoT agent can determine whether the problematic terminal itself has malfunctioned based on the sensor information of the problematic terminal.

[0133] In this application, the AIoT consumer device 102 can send a first message to the AIoT fault handling module 103, which can obtain the identity information of the problematic terminal. The AIoT fault handling module 103 can obtain the sensor information of the problematic terminal, call the corresponding tool through the tool library 106, and obtain the sensor troubleshooting tool call result. Further, the AIoT fault handling module 103 can determine the fault indication based on the sensor troubleshooting tool call result. The first message includes the identity information of the problematic terminal, and the fault indication is used to indicate whether the problematic terminal itself has malfunctioned. That is, the AIoT fault handling module can determine whether the problematic terminal itself has malfunctioned based on the sensor information of the problematic terminal. If the AIoT terminal device itself malfunctions, this application can greatly simplify the fault location steps and optimize the fault location process, eliminating the need to sequentially check the IoT platform, core network, base station, and finally the terminal for alarms or abnormal information, effectively improving the fault location efficiency in AIoT terminal fault scenarios.

[0134] The fault location method provided in this application will be described below.

[0135] Please refer to Figure 3, which is a flowchart illustrating a fault location method provided in an embodiment of this application. Optionally, this fault location method can be applied to the AIoT network system 10 shown in Figure 1a or the AIoT network system 20 shown in Figure 2a. The fault location method shown in Figure 3 may include one or more steps S301 to S303. It should be understood that, for ease of description, the description is based on the order of steps S301 to S303, and is not intended to limit the execution to the above order. This application embodiment does not limit the order of execution, the execution time, or the number of executions of the above one or more steps. Steps S301 to S303 are as follows:

[0136] Step S301: The AIoT consumer device sends a first message to the AIoT fault handling module.

[0137] Accordingly, the AIoT fault handling module receives the first message from the AIoT consumer device.

[0138] In this context, an AIoT consumer device is a device with communication capabilities. Optionally, an AIoT consumer device may also have processing capabilities. This application embodiment is described using an AIoT consumer device possessing both communication and processing capabilities as an example. For instance, the AIoT consumer device could be AIoT consumer device 102 in the AIoT network system 10 shown in FIG1a, or AIoT consumer device 102 in the AIoT network system 20 shown in FIG2a.

[0139] The AIoT fault handling module has communication and processing capabilities. It is used to determine whether the AIoT terminal device itself has malfunctioned. For example, the AIoT fault handling module is the AIoT fault handling module 103 in the AIoT network system 10 shown in Figure 1a, or the AIoT fault handling module 103 in the AIoT network system 20 shown in Figure 2a.

[0140] AIoT consumer devices can acquire sensor data (also known as application data) from sensors in AIoT terminal devices and perform business processing based on this data. For example, an AIoT consumer device can acquire heartbeat data from a smart meter and monitor the user's physical condition based on this data. Here, the AIoT terminal device, also referred to in some embodiments as an AIoT terminal or AIoT UE, is a device with communication capabilities. AIoT terminal devices include sensors; for example, AIoT terminal devices include smart locks, smart lights, smart meters, and other similar devices.

[0141] Problematic terminals belong to AIoT terminal devices. In one possible implementation, an AIoT terminal device may fail to report data to the AIoT consumer device. In this case, the AIoT consumer device can consider the AIoT terminal device to be faulty and mark it as a problematic terminal. For example, if a smart meter loses heartbeat data packets, the AIoT consumer device can consider the smart meter a problematic terminal. In other words, a problematic terminal is an AIoT terminal device that fails to report data. In another possible implementation, the data from the AIoT terminal device may be abnormal. In this case, the AIoT consumer device can consider the AIoT terminal device to be faulty and mark it as a problematic terminal. For example, if the unlocking or locking delay of a smart lock exceeds the normal delay threshold, the AIoT consumer device can consider the smart lock a problematic terminal. In other words, a problematic terminal is an AIoT terminal device with abnormal data.

[0142] Furthermore, the AIoT consumer device can send a first message to the AIoT fault handling module. This first message includes the identity information of the problematic terminal, such as the identity information of the aforementioned smart meter. The identity information of the problematic terminal is used to identify its identity and can be an identification ID, account number, unique code, dedicated number, address, etc.

[0143] Optionally, the first message may also include at least one of the following: fault time, fault location, fault type, and application data reference value. For example, the fault type may include at least one of offline, data transmission failure, and decreased transmission rate. The application data reference value may include at least one of the following: normal range of data values, outlier tolerance, and threshold values ​​for parameters related to the normal operation of the AIoT terminal device. The outlier tolerance may be a threshold for the number of outliers (which may be referred to as the first threshold for ease of description).

[0144] Step S302: The AIoT fault handling module obtains the first sensor information of the faulty terminal.

[0145] The sensor information of the problematic terminal, for ease of description, can be referred to as the first sensor information. This first sensor information is used to indicate the service status of the problematic terminal; for example, it is directly used for the services the problematic terminal is engaged with. Alternatively, the first sensor information is used to indicate the environmental conditions of the problematic terminal, such as the ambient temperature or humidity.

[0146] In one possible implementation, the first sensor information includes sensing data, such as heartbeat data. The first sensor information also includes at least one of the following: the problematic terminal's identity information, service type, sensing parameter type, sensing time, and sensing location. Wherein, the problematic terminal's service type includes sensing-related services; therefore, this application can determine whether the problematic terminal itself has malfunctioned based on the problematic terminal's sensor information. Optionally, if the problematic terminal's service type includes sensing-related services, the sensor information of the problematic terminal is directly used for the services the problematic terminal serves. Further optional, if the problematic terminal's service type includes sensing-related services, the sensor information of the problematic terminal is not directly used for the services the problematic terminal serves, but rather reflects the environmental state of the problematic terminal itself. For example, the service type includes inventory, positioning, and sensing. The sensing parameter type includes temperature, humidity, and pressure.

[0147] Optionally, the first message also includes a fault time, and the sensing data is data prior to the fault time. For example, if the fault time is time A, the sensing data is sensing data prior to time A. Further optional, the first message also includes a fault location, and the sensing data is related to the fault location. For example, if the fault location is address X, the sensing data includes sensing data near address X, such as sensing data from devices near address X. Still optional, the first message also includes a fault type, which is used to acquire the first sensor information. For example, if the fault type is offline, the problematic terminal may be offline due to being in a location with weak communication signals, and the AIoT fault handling module can acquire sensing data related to the location of the problematic terminal.

[0148] The following describes several possible implementations for AIoT fault handling modules to obtain information from the first sensor.

[0149] In implementation 1, the AIoT fault handling module can send a second message to the first device and receive first sensor information from the first device, thereby obtaining the first sensor information of the problematic terminal. The second message includes the identity information of the problematic terminal. Correspondingly, the first device receives the second message from the AIoT fault handling module, obtains the identity information of the problematic terminal, and sends the sensor information corresponding to the problematic terminal, i.e., the first sensor information, to the AIoT fault handling module. The first device is an AIoT monitoring module or a knowledge base; for example, the first device is the AIoT monitoring module 104 in the AIoT network system 10 shown in Figure 1a, or the knowledge base 105 in the AIoT network system 20 shown in Figure 2a.

[0150] For example, the first device may send a sixth message to receive sensor information from the AIoT terminal device, receive a second message from the AIoT fault handling module, and send the first sensor information of the problematic terminal to the AIoT fault handling module. The sixth message includes the identity information of the AIoT terminal device, which identifies the AIoT terminal device and may be an ID, account, unique code, exclusive number, address, etc. Optionally, the sixth message may also include at least one of the following: the service type for which sensor information needs to be reported, the type of sensing parameters to be reported, the sensing time to be reported, the sensing location to be reported, the sensing data to be reported, and the update interval. The sensor information of the AIoT terminal device includes sensing data. The sensor information of the AIoT terminal device may also include at least one of the following: the identity information of the AIoT terminal device, the service type, the sensing parameter type, the sensing time, and the sensing location.

[0151] For example, the first device sends a sixth message to the RAN, which receives the sixth message and obtains the identity information of the AIoT terminal device. Based on the identity information, the RAN obtains the corresponding sensor information of the AIoT terminal device and sends this sensor information back to the first device. The first device receives the sensor information from the AIoT terminal device, receives a second message from the AIoT fault handling module, obtains the identity information of the problematic terminal, and sends the corresponding sensor information (i.e., the first sensor information) to the AIoT fault handling module. The AIoT fault handling module receives the first sensor information from the first device, thus acquiring the first sensor information of the problematic terminal.

[0152] Optionally, the first message also includes a fault time, and the second message also includes a fault time. Upon receiving the second message and obtaining the fault time, the first device can send sensor data of the problematic terminal prior to the fault time to the AIoT fault handling module. That is, the first sensor information includes sensor data of the problematic terminal prior to the fault time. Alternatively, the first message also includes a fault location, and the second message also includes a fault location. Upon receiving the second message and obtaining the fault location, the first device can send sensor data related to the fault location to the AIoT fault handling module. That is, the first sensor information includes sensor data related to the fault location.

[0153] In implementation 2, the AIoT fault handling module can obtain first sensor information from the AIoT consumer device. For example, the AIoT consumer device sends the first sensor information to the AIoT fault handling module, and the AIoT fault handling module receives the first sensor information from the AIoT consumer device, thereby enabling the AIoT fault handling module to obtain the first sensor information of the problematic terminal. Optionally, the first sensor information can be carried in a first message.

[0154] In implementation 3, the AIoT fault handling module can obtain first sensor information from the AIoT terminal device. For example, the AIoT terminal device sends a fourth message to the AIoT fault handling module, which receives the fourth message. The fourth message includes the abnormal time and / or abnormal location corresponding to the sensor information of the problematic terminal, thereby enabling the AIoT fault handling module to obtain the first sensor information of the problematic terminal. In this case, the fourth message is the first sensor information. Optionally, the fourth message also includes the identity information of the AIoT terminal device to identify the identity of the AIoT terminal device that has malfunctioned. For example, malfunction can be understood as the presence of an abnormal value in the sensor information of the AIoT terminal device, the abnormal time being the time corresponding to the abnormal value, and the abnormal location being the location corresponding to the abnormal value.

[0155] The above examples illustrate several possible implementations of AIoT fault handling modules acquiring first sensor information. In actual use, there may be more possible implementations, which will not be listed here.

[0156] Step S303: The AIoT fault handling module sends a fault indication to the AIoT consumer device.

[0157] Accordingly, the AIoT consumer device receives a fault indication from the AIoT fault handling module.

[0158] The fault indicator is used to indicate whether the problematic terminal itself has malfunctioned.

[0159] As one possible implementation, the AIoT fault handling module determines a fault indication based on the first sensor information of the problematic terminal. Further, the AIoT fault handling module sends the fault indication to the AIoT consumer device.

[0160] The following describes several possible designs for AIoT fault handling modules to determine fault indications based on information from the first sensor.

[0161] Design 1: When the first sensor information meets predefined abnormal conditions, a fault indication is used to indicate that the problematic terminal itself has malfunctioned. The abnormal conditions are related to the application data reference values ​​mentioned earlier. For example, the application data reference values ​​include the normal range of data values, and the abnormal condition includes the presence of abnormal values ​​in the first sensor information. Abnormal values ​​can be data that exceeds the normal range; for example, if the normal range is 30-50, and the sensor data is 15, it is determined to be an abnormal value. Alternatively, the application data reference values ​​include the normal range of data values ​​and an abnormal value tolerance. The abnormal condition includes data in the first sensor information that exceeds the normal range exceeding the abnormal value tolerance, i.e., the number of abnormal values ​​in the first sensor information is greater than a first threshold. Another example is that the application data reference values ​​include thresholds for parameters related to the normal operation of the AIoT terminal device, and the abnormal condition includes measured values ​​of parameters in the first sensor information related to the normal operation of the problematic terminal that are close to or exceed the thresholds for parameters that allow the problematic terminal to operate normally. For example, the first sensor information includes temperature data, which is related to the normal operation of the problematic terminal. When the temperature data in the first sensor information exceeds the temperature threshold related to the normal operation of the problematic terminal, such as 70°C, when the temperature data in the first sensor information is greater than or equal to 70°C, it is determined that the first sensor information meets the predefined abnormal conditions, and the fault indication is used to indicate that the problematic terminal itself has malfunctioned.

[0162] The foregoing has introduced several possible abnormal conditions. In actual use, there may be many more possible abnormal conditions, which will not be described one by one here.

[0163] Design 2: The AIoT fault handling module can jointly determine a fault indication based on information from the first sensor and environmental sensors. The first sensor information and environmental sensor information include data of the same type of sensing parameter. For example, both the first sensor information and environmental sensor information include temperature data.

[0164] For example, the second message also includes a first source type, where the source type corresponding to the first sensor information is the first source type, which indicates that the source of the sensing data is an AIoT terminal device. In other words, the sensing data in the first sensor information originates from an AIoT terminal device and is collected by sensors within the AIoT terminal device.

[0165] In one possible implementation, the AIoT fault handling module can determine the abnormal sensing information of the problematic terminal based on the first sensor information. Further, the AIoT fault handling module determines a fault indication based on the abnormal sensing information and environmental sensor information. The abnormal sensing information is part of the first sensor information. For example, when the difference between the abnormal sensing information and the environmental sensor information meets a preset difference condition, the fault indication is used to indicate that the problematic terminal itself has malfunctioned. For instance, the preset difference condition is that the difference between the abnormal sensing information and the environmental sensor information is greater than a preset difference threshold. The preset difference threshold includes a preset temperature difference threshold, for example, 3°C. When the difference between the temperature data in the abnormal sensing information and the temperature data in the environmental sensor information is greater than 3°C, the AIoT fault handling module determines that the probability of the problematic terminal itself malfunctioning is relatively high, and the fault indication is used to indicate that the problematic terminal itself has malfunctioned.

[0166] Optionally, the AIoT fault handling module can determine the abnormal sensing information of the problematic terminal based on the first sensor information and the application data reference values ​​mentioned above. For example, the application data reference values ​​include the normal range of data values, and the abnormal sensing information of the problematic terminal includes data in the first sensor information that exceeds the normal range of data values ​​(e.g., abnormal values ​​in the first sensor information). As another example, the application data reference values ​​include threshold values ​​of parameters related to the normal operation of the AIoT terminal device, and the abnormal sensing information of the problematic terminal includes data in the first sensor information where the measured values ​​of parameters related to the normal operation of the problematic terminal are close to or exceed the threshold values ​​of the parameters for normal operation of the problematic terminal.

[0167] Furthermore, the AIoT fault handling module can send a third message to the AIoT monitoring module and receive environmental sensor information from the AIoT monitoring module. The third message includes a second source type and first information. The second source type indicates that the source of the sensing data is not an AIoT terminal device. That is, the sensing data in the environmental sensor information does not originate from an AIoT terminal device (for ease of description, it can be referred to as a non-AIoT terminal device) and is collected by sensors in a non-AIoT terminal device. The first information includes an abnormal sensing parameter type, which is the sensing parameter type of the abnormal sensing information. The sensing parameter type of the environmental sensor information includes the abnormal sensing parameter type. For example, the sensing parameter type of the abnormal information includes temperature, and the environmental sensor information includes temperature data. Exemplarily, the AIoT monitoring module receives the third message from the AIoT fault handling module, obtains the second source type and the abnormal sensing parameter type, acquires the environmental sensor information whose sensing data source is not an AIoT terminal device based on the abnormal sensing parameter type, and sends the environmental sensor information to the AIoT fault handling module.

[0168] Optionally, the first information may also include the abnormal time corresponding to the abnormal sensing information, and the environmental sensor information may also include the sensor information corresponding to the abnormal time. For example, the abnormal time corresponding to the abnormal sensing information is time C, and the environmental sensor information may also include the sensor information of the non-AIoT terminal device corresponding to time C.

[0169] Optionally, the first information may also include the abnormal location corresponding to the abnormal sensing information, and the environmental sensor information may also include the sensor information corresponding to the abnormal location. For example, if the abnormal location corresponding to the abnormal sensing information is location D, the environmental sensor information may also include the sensor information of the non-AIoT terminal device corresponding to location D.

[0170] Design 3: The first sensor information includes a fourth message acquired by the AIoT fault handling module from the AIoT terminal device. The first message also includes the fault location, and the fourth message includes the abnormal location corresponding to the sensor information of the problematic terminal. The AIoT fault handling module can determine a fault indication based on the fault location and the abnormal location. Specifically, the measured values ​​of parameters related to the normal operation of the problematic terminal in its sensor information are close to or exceed the threshold values ​​of the parameters for normal operation (or the problematic terminal is in a working extreme environment). For example, if the abnormal location is repeatedly near the fault location (e.g., the number of times the distance between the abnormal location and the fault location is less than the distance threshold is greater than the first time the threshold is reached), the probability of the problematic terminal itself malfunctioning is relatively high. The AIoT fault handling module can determine that the problematic terminal itself has malfunctioned, and the fault indication is used to indicate that the problematic terminal itself has malfunctioned.

[0171] Optionally, the fourth message may also include the identity information of the AIoT terminal device to identify the AIoT terminal device that has malfunctioned. Optionally, the fourth message may also include the abnormal sensing parameter type and / or abnormal sensing parameter value, which can be used to determine a fault indication.

[0172] Design 4: The first sensor information includes a fourth message acquired by the AIoT fault handling module from the AIoT terminal device. The first message also includes the fault time, and the fourth message includes the abnormal time corresponding to the sensor information of the problematic terminal. The AIoT fault handling module can determine a fault indication based on the fault time and the abnormal time. For example, if the abnormal time is repeatedly near the fault time (e.g., the number of times the time interval between the abnormal time and the fault time is less than the time interval threshold is greater than the second threshold), the probability of the problematic terminal itself malfunctioning is relatively high. The AIoT fault handling module can determine that the problematic terminal itself has malfunctioned, and the fault indication is used to indicate that the problematic terminal itself has malfunctioned.

[0173] Design 5: The first device is a knowledge base. The first sensor information includes sensor parameter types. The AIoT fault handling module can determine the sensor troubleshooting tool based on the sensor parameter type, send a fifth message to the tool library, receive the sensor troubleshooting tool call result from the tool library, and determine the fault indication based on the sensor troubleshooting tool call result. The fifth message includes the name of the sensor troubleshooting tool, the sensor data of the problematic terminal, and the application data reference value. In one possible implementation, the tool library receives the fifth message, obtains the name of the sensor troubleshooting tool, calls the corresponding tool based on the name, obtains the sensor troubleshooting tool call result based on the sensor data and application data reference value of the problematic terminal, and sends the sensor troubleshooting tool call result to the AIoT fault handling module. For example, if the sensor parameter type is F, the corresponding sensor troubleshooting tool is M2, the fifth message includes the name of sensor troubleshooting tool M2, the tool library can call sensor troubleshooting tool M2 based on its name, and obtain the sensor troubleshooting tool call result based on the sensor data and application data reference value of the problematic terminal in the first sensor information.

[0174] Furthermore, the AIoT fault handling module determines the fault indication based on the result of the sensor troubleshooting tool call. For example, the result of the sensor troubleshooting tool call is a value between 0 and 1. If the value is close to 0, it means that the probability of the faulty terminal itself is close to 0. If the value is close to 1, it means that the probability of the faulty terminal itself is close to 1. That is, the faulty terminal itself is considered to have failed.

[0175] Design 6 further includes a fault type in the first message, which is used to determine the fault indication. For example, the AIoT fault handling module receives the first message from the AIoT consumer device, obtains the fault type, and determines the fault indication based on the fault type. For instance, the fault type can be used to initially determine the fault indication. For example, if the fault type is "offline," the probability of the problematic terminal itself malfunctioning is relatively high, and other steps in this application can be used to determine whether the problematic terminal itself has malfunctioned. As another example, if the fault type is "data transmission failure" or "reduced transmission rate," the probability of the problematic terminal malfunctioning due to a network-side fault is relatively high, and the probability of the problematic terminal itself malfunctioning is relatively low, so network-side anomaly investigation can be prioritized.

[0176] The above examples illustrate several possible designs for AIoT fault handling modules to determine fault indications based on information from the first sensor. In actual use, there may be many more possible designs, which will not be listed here.

[0177] Optionally, the fault indication may include the identity information of the problematic terminal, such as the fault indication being "The problematic AIoT terminal device H has itself malfunctioned".

[0178] Optionally, the AIoT consumer device receives a fault indication from the AIoT fault handling module. For example, when the fault indication indicates that the faulty terminal is itself malfunctioning, the AIoT consumer device may prioritize troubleshooting the faulty terminal.

[0179] In the embodiment shown in Figure 3, after receiving the first message, the AIoT fault handling module can obtain the identity information of the problematic AIoT terminal device. Further, the AIoT fault handling module can acquire the sensor information of the AIoT terminal device and determine whether the AIoT terminal device itself has malfunctioned based on this sensor information. If the AIoT terminal device itself malfunctions, this application can greatly simplify the fault location steps and optimize the fault location process, eliminating the need to sequentially check alarms or abnormal information at the IoT platform, core network, base station, and finally the terminal, thus effectively improving the fault location efficiency in AIoT terminal fault scenarios.

[0180] The embodiments in Figure 3 above encompass a variety of possible scenarios. Some possible implementations will be described below with reference to Figures 4 to 8. Any terms, logic, etc., not explained in the following description can be found in the above description.

[0181] Please refer to Figure 4, which is a flowchart illustrating another possible fault location method provided in this application embodiment. This fault location method may include one or more steps from S401 to S408. It should be understood that, for ease of description, the method is described in the order of steps S401 to S408, and is not intended to limit the execution to this specific order. This application embodiment does not limit the order of execution, the execution time, or the number of executions of the above one or more steps. Steps S401 to S408 are as follows:

[0182] Step S401: The AIoT monitoring module sends the sixth message to the RAN.

[0183] The sixth message includes the identity information of the AIoT terminal device, which identifies the device and can be an ID, account, unique code, exclusive number, address, etc. Optionally, the sixth message may also include at least one of the following: the service type requiring sensor information reporting, the type of sensor parameters requiring reporting, the sensing time requiring reporting, the sensing location requiring reporting, the sensing data requiring reporting, and the update interval. For example, service types include inventory, positioning, and sensing. Sensor parameter types include temperature, humidity, and pressure.

[0184] Accordingly, the RAN receives the sixth message from the AIoT monitoring module to obtain the identity information of the AIoT terminal devices that need to be reported.

[0185] Step S402: The AIoT terminal device sends its sensor information to the RAN.

[0186] Accordingly, the RAN receives sensor information from the AIoT terminal devices.

[0187] Optionally, the RAN sends a sixth message to the AIoT terminal device, causing the corresponding AIoT terminal device that needs to report to send its sensor information to the RAN. For example, the sixth message includes the identity information of the AIoT terminal device H. After receiving the sixth message, the AIoT terminal device H sends its sensor information to the RAN.

[0188] Similarly, after receiving the sixth message, AIoT terminal device H sends its sensor information to the RAN according to the requirements in the sixth message. For example, the sixth message may also include an update time interval. After receiving the sixth message, AIoT terminal device H sends its sensor information to the RAN periodically or periodically according to the update time interval.

[0189] Step S403: RAN sends sensor information of AIoT terminal devices to the AIoT monitoring module.

[0190] Accordingly, the AIoT monitoring module receives sensor information from the AIoT terminal devices in the RAN. This sensor information includes sensing data. It also includes at least one of the following: the AIoT terminal device's identity information, service type, sensing parameter type, sensing time, and sensing location.

[0191] Step S404: The AIoT consumer device sends a first message to the AIoT fault handling module.

[0192] Accordingly, the AIoT fault handling module receives the first message from the AIoT consumer device.

[0193] The first message includes the problematic terminal's identity information. This identity information identifies the problematic terminal and can be an ID, account, unique code, unique number, address, etc.

[0194] Optionally, the first message may also include at least one of the following: fault time, fault location, fault type, and application data reference value. For example, the fault type may include at least one of offline, data transmission failure, and decreased transmission rate. The application data reference value may include at least one of the following: normal range of data values, outlier tolerance, and threshold values ​​for parameters related to the normal operation of the AIoT terminal device. The outlier tolerance may be a threshold for the number of outliers (which may be referred to as the first threshold for ease of description).

[0195] Specifically, please refer to the relevant description in step S301 above.

[0196] Step S405: The AIoT fault handling module sends a second message to the AIoT monitoring module.

[0197] Accordingly, the AIoT monitoring module receives a second message from the AIoT fault handling module.

[0198] The second message includes the identity information of the problematic terminal. Optionally, the first message also includes the fault time, and the second message also includes the fault time. The fault time is used by the AIoT fault handling module to obtain the first sensor information of the problematic terminal. Further optionally, the first message also includes the fault location, and the second message also includes the fault location. The fault location is used by the AIoT fault handling module to obtain the first sensor information of the problematic terminal.

[0199] Optionally, before step S405, the AIoT fault handling module can determine the service type of the problematic terminal based on its identity information. If the service type of the problematic terminal includes sensing services, then step S405 and the steps following step S405 are executed. If the service type of the problematic terminal includes sensing services, the sensor information of the problematic terminal can be used, as described in this application, to determine whether the problematic terminal itself has malfunctioned.

[0200] Optionally, the service type of the problematic terminal may include sensing-related services, where the sensor information of the problematic terminal is directly used for the services it serves. Alternatively, the service type of the problematic terminal may include sensing-related services, where the sensor information is not directly used for the services it serves, but rather reflects the environmental state of the problematic terminal itself. For example, service types may include inventory management, positioning, and sensing. Sensing parameter types may include temperature, humidity, and pressure.

[0201] Step S406: The AIoT monitoring module sends the first sensor information of the problematic terminal to the AIoT fault handling module.

[0202] Accordingly, the AIoT fault handling module receives the first sensor information from the faulty terminal of the AIoT monitoring module.

[0203] The sensor information of the problematic terminal, for ease of description, can be referred to as the first sensor information. This first sensor information is used to indicate the service status of the problematic terminal; for example, it is directly used for the services the problematic terminal is engaged with. Alternatively, the first sensor information is used to indicate the environmental conditions of the problematic terminal, such as the ambient temperature or humidity.

[0204] The first sensor information includes sensing data, such as heartbeat data. It also includes at least one of the following: the problematic terminal's identity information, service type, sensing parameter type, sensing time, and sensing location.

[0205] Optionally, the first message also includes the fault time, and the second message also includes the fault time. The AIoT monitoring module receives the second message, obtains the fault time, and can send the sensor data of the problematic terminal prior to the fault time to the AIoT fault handling module. That is, the first sensor information includes the sensor data of the problematic terminal prior to the fault time. Alternatively, the first message also includes the fault location, and the second message also includes the fault location. The AIoT monitoring module receives the second message, obtains the fault location, and can send sensor data related to the fault location to the AIoT fault handling module. That is, the first sensor information includes sensor data related to the fault location.

[0206] Specifically, please refer to the relevant description in step S302 of the preceding text, which is part of implementation 1.

[0207] Step S407: The AIoT fault handling module determines the fault indication based on the first sensor information of the faulty terminal.

[0208] The fault indicator is used to indicate whether the problematic terminal itself has malfunctioned.

[0209] Optionally, when the first sensor information meets a predefined abnormal condition, a fault indication is used to indicate that the problematic terminal itself has malfunctioned. Specifically, refer to the relevant description in Design 1 of step S303 above.

[0210] Step S408: The AIoT fault handling module sends a fault indication to the AIoT consumer device.

[0211] Optionally, the fault indication may include the identity information of the problematic terminal, such as the fault indication being "The problematic AIoT terminal device H has itself malfunctioned".

[0212] Accordingly, the AIoT consumer device receives a fault indication from the AIoT fault handling module. For example, when the fault indication indicates that the faulty terminal is itself malfunctioning, the AIoT consumer device can prioritize troubleshooting the faulty terminal.

[0213] In the embodiment shown in Figure 4, after receiving the first message, the AIoT fault handling module can obtain the identity information of the problematic AIoT terminal device. Furthermore, the AIoT fault handling module can obtain the first sensor information of the problematic terminal through the AIoT monitoring module, and determine whether the problematic terminal itself has malfunctioned based on the first sensor information. If the AIoT terminal device itself malfunctions, this application can greatly simplify the fault location steps and optimize the fault location process, eliminating the need to sequentially check alarms or abnormal information at the IoT platform, core network, base station, and finally the terminal, effectively improving the fault location efficiency in AIoT terminal fault scenarios.

[0214] Please refer to Figure 5, which is a flowchart illustrating another possible fault location method provided in this application embodiment. This fault location method may include one or more steps S501 to S511. It should be understood that, for ease of description, the method is described in the order of steps S501 to S511, and is not intended to limit the execution to this specific order. This application embodiment does not limit the order of execution, the execution time, or the number of executions of the above one or more steps. Steps S501 to S511 are as follows:

[0215] Step S501: The AIoT monitoring module sends the sixth message to the RAN.

[0216] Accordingly, the RAN receives the sixth message from the AIoT monitoring module to obtain the identity information of the AIoT terminal devices that need to be reported.

[0217] Specifically, please refer to the relevant description in step S401 above.

[0218] Step S502: The AIoT terminal device sends the sensor information of the AIoT terminal device to the RAN.

[0219] Accordingly, the RAN receives sensor information from the AIoT terminal devices.

[0220] Specifically, please refer to the relevant description in step S402 above.

[0221] Step S503: RAN sends sensor information of AIoT terminal devices to the AIoT monitoring module.

[0222] Accordingly, the AIoT monitoring module receives sensor information from the AIoT terminal devices in the RAN. This sensor information includes sensor data and source type, which indicates whether the sensor data originates from an AIoT terminal device.

[0223] For example, the sensing data of AIoT terminal device S may include sensing data that is not from the AIoT terminal device itself (for ease of description, it may be referred to as a non-AIoT terminal device). For instance, the sensing data of AIoT terminal device S may include temperature data, which is collected by a non-AIoT terminal device (e.g., an ambient thermometer). In this case, the source of the temperature data from AIoT terminal device S is not the AIoT terminal device (i.e., a non-AIoT terminal device). In other words, the sensor information of the AIoT terminal device includes temperature data, and the sensing source of the temperature data indicates that the source of the temperature data is not the AIoT terminal device.

[0224] Optionally, the sensor information of the AIoT terminal device may also include at least one of the following: the AIoT terminal device's identity information, service type, sensing parameter type, sensing time, and sensing location.

[0225] Specifically, please refer to the relevant description in step S403 above.

[0226] Step S504: The AIoT consumer device sends a first message to the AIoT fault handling module.

[0227] Accordingly, the AIoT fault handling module receives the first message from the AIoT consumer device.

[0228] The first message includes the problematic terminal's identity information. This identity information identifies the problematic terminal and can be an ID, account, unique code, unique number, address, etc.

[0229] Specifically, please refer to the relevant description in step S404 above.

[0230] Step S505: The AIoT fault handling module sends a second message to the AIoT monitoring module.

[0231] Accordingly, the AIoT monitoring module receives a second message from the AIoT fault handling module.

[0232] The second message includes the identity information of the problematic terminal. Optionally, the first message also includes the fault time, and the second message also includes the fault time. The fault time is used by the AIoT fault handling module to obtain the first sensor information of the problematic terminal. Further optionally, the first message also includes the fault location, and the second message also includes the fault location. The fault location is used by the AIoT fault handling module to obtain the first sensor information of the problematic terminal.

[0233] The second message also includes a first source type, which indicates that the sensor data originates from an AIoT terminal device. The AIoT fault handling module needs to obtain sensor data from the problematic terminal's sensor information that originates from an AIoT terminal device; that is, the source type corresponding to the problematic terminal's first sensor information is the first source type. In other words, the sensor data in the first sensor information originates from an AIoT terminal device and is collected by sensors within the AIoT terminal device.

[0234] Specifically, please refer to the relevant descriptions in steps S405 and S303 above.

[0235] Step S506: The AIoT monitoring module sends the first sensor information of the problematic terminal to the AIoT fault handling module.

[0236] Accordingly, the AIoT fault handling module receives the first sensor information from the faulty terminal of the AIoT monitoring module.

[0237] Specifically, please refer to the relevant descriptions in steps S406 and S302 of the preceding text in implementation 1.

[0238] Step S507: The AIoT fault handling module determines the abnormal sensing information based on the first sensor information of the problematic terminal.

[0239] Among them, abnormal sensing information belongs to the first sensor information.

[0240] Optionally, the AIoT fault handling module can determine the abnormal sensing information of the problematic terminal based on the first sensor information and the application data reference values ​​mentioned above. For example, the application data reference values ​​include the normal range of data values, and the abnormal sensing information of the problematic terminal includes data in the first sensor information that exceeds the normal range of data values ​​(e.g., abnormal values ​​in the first sensor information). As another example, the application data reference values ​​include threshold values ​​of parameters related to the normal operation of the AIoT terminal device, and the abnormal sensing information of the problematic terminal includes data in the first sensor information where the measured values ​​of parameters related to the normal operation of the problematic terminal are close to or exceed the threshold values ​​of the parameters for normal operation of the problematic terminal.

[0241] Specifically, please refer to the relevant description in Design 2 of step S303 above.

[0242] Step S508: The AIoT fault handling module sends a third message to the AIoT monitoring module.

[0243] The third message includes a second source type and a first message. The second source type indicates that the source of the sensing data is not an AIoT terminal device (which can be referred to as a non-AIoT terminal device for ease of description). In other words, the sensing data was collected by sensors in a non-AIoT terminal device. The first message includes an abnormal sensing parameter type, which refers to the sensing parameter type of the abnormal sensing information.

[0244] Accordingly, the AIoT monitoring module receives a third message from the AIoT fault handling module.

[0245] Specifically, please refer to the relevant description in Design 2 of step S303 above.

[0246] Step S509: The AIoT monitoring module sends environmental sensor information to the AIoT fault handling module.

[0247] Accordingly, the AIoT fault handling module receives environmental sensor information from the AIoT monitoring module.

[0248] For example, the AIoT monitoring module receives a third message from the AIoT fault handling module, obtains the abnormal sensing parameter type, acquires environmental sensor information whose sensing data source is not the AIoT terminal device based on the abnormal sensing parameter type, and sends the environmental sensor information to the AIoT fault handling module.

[0249] The environmental sensor information does not originate from AIoT terminal devices (i.e., non-AIoT terminal devices); the data is collected by sensors within non-AIoT terminal devices. The sensor parameter types in the environmental sensor information include abnormal sensor parameter types. In other words, the sensor parameter types in the environmental sensor information include those of abnormal sensor information. For example, abnormal sensor information may include temperature, and the environmental sensor information will include temperature data.

[0250] Specifically, please refer to the relevant description in Design 2 of step S303 above.

[0251] Step S510: The AIoT fault handling module determines the fault indication based on the abnormal sensing information and environmental sensor information.

[0252] The fault indicator is used to indicate whether the problematic terminal itself has malfunctioned.

[0253] For example, when the difference between abnormal sensing information and environmental sensor information meets a preset difference condition, a fault indication is used to indicate that the problematic terminal itself has malfunctioned.

[0254] Specifically, please refer to the relevant description in Design 2 of step S303 above.

[0255] Step S511: The AIoT fault handling module sends a fault indication to the AIoT consumer device.

[0256] Optionally, the fault indication may include the identity information of the problematic terminal, such as the fault indication being "The problematic AIoT terminal device H has itself malfunctioned".

[0257] Accordingly, the AIoT consumer device receives a fault indication from the AIoT fault handling module. For example, when the fault indication indicates that the faulty terminal is itself malfunctioning, the AIoT consumer device can prioritize troubleshooting the faulty terminal.

[0258] In the embodiment shown in Figure 5, after receiving the first message, the AIoT fault handling module can obtain the identity information of the problematic AIoT terminal device. Further, the AIoT fault handling module can obtain the first sensor information of the problematic terminal through the AIoT monitoring module. The sensor data in the first sensor information of the problematic terminal originates from the AIoT terminal device. Based on the first sensor information of the problematic terminal, the AIoT fault handling module can determine the abnormal sensor information and obtain environmental sensor information whose sensor data does not originate from the AIoT terminal device (e.g., from a non-AIoT terminal device). The sensor parameter types of the environmental sensor information include the abnormal sensor parameter types corresponding to the abnormal sensor information. Therefore, the AIoT fault handling module can jointly determine whether the problematic terminal itself has malfunctioned based on the first sensor information of the problematic terminal and the environmental sensor information, which can improve the accuracy of the judgment. Moreover, if the AIoT terminal device itself malfunctions, this application can greatly simplify the fault location steps and optimize the fault location process, eliminating the need to sequentially check the IoT platform, core network, base station, and finally the terminal for alarms or abnormal information, effectively improving the fault location efficiency in AIoT terminal fault scenarios.

[0259] Please refer to Figure 6, which is a flowchart illustrating another possible fault location method provided in this application embodiment. This fault location method may include one or more steps from S601 to S604. It should be understood that, for ease of description, the method is described in the order of steps S601 to S604, and is not intended to limit the execution to this specific order. This application embodiment does not limit the order of execution, the execution time, or the number of executions of the above one or more steps. Steps S601 to S604 are as follows:

[0260] Step S601: The AIoT terminal device sends a fourth message to the AIoT fault handling module.

[0261] Accordingly, the AIoT fault handling module receives a fourth message from the AIoT terminal device.

[0262] The fourth message includes the abnormal time and / or abnormal location corresponding to the sensor information of the AIoT terminal device. Optionally, the fourth message also includes the identity information of the AIoT terminal device to identify the identity of the AIoT terminal device that has experienced the abnormality. For example, an abnormality can be understood as the presence of an abnormal value in the sensor information of the AIoT terminal device, the abnormal time being the time corresponding to the abnormal value, and the abnormal location being the location corresponding to the abnormal value.

[0263] Optionally, the fourth message may also include the abnormal sensor parameter type and / or abnormal sensor parameter value, which can be used to determine a fault indication.

[0264] Optionally, before step S601, the AIoT terminal device can determine whether it is in a working extreme environment based on the sensing data of its own sensing services. If the AIoT terminal device is in a working extreme environment, step S601 is executed. For example, if the measured values ​​of parameters related to the normal operation of the AIoT terminal device in the sensor information of the AIoT terminal device are close to or exceed the threshold values ​​of the parameters for the normal operation of the AIoT terminal device (this can be referred to as the AIoT terminal device being in a working extreme environment).

[0265] Optionally, the AIoT terminal device can send a fourth message to the AIoT fault handling module via the RAN. For example, the AIoT terminal device can send a fourth message to the RAN, and the RAN can then send the fourth message to the AIoT fault handling module, thereby enabling the AIoT terminal device to send a fourth message to the AIoT fault handling module.

[0266] Specifically, please refer to the relevant description in step S302 above.

[0267] Step S602: The AIoT consumer device sends a first message to the AIoT fault handling module.

[0268] Accordingly, the AIoT fault handling module receives the first message from the AIoT consumer device.

[0269] The first message includes the problematic terminal's identity information. This identity information identifies the problematic terminal and can be an ID, account, unique code, unique number, address, etc.

[0270] Optionally, the first message may also include the fault location, and the fourth message may include the abnormal location corresponding to the sensor information of the problematic terminal. Further optional, the first message may also include the fault time, and the fourth message may include the abnormal time corresponding to the sensor information of the problematic terminal.

[0271] Specifically, please refer to the relevant description in step S303 above.

[0272] Step S603: The AIoT fault handling module determines the fault indication based on the fourth message and the first message.

[0273] The problematic terminal belongs to the AIoT terminal device that sent the fourth message to the AIoT fault handling module. Specifically, the fourth message includes the abnormal time and / or abnormal location corresponding to the sensor information of the problematic terminal. Therefore, the AIoT fault handling module can determine whether the problematic terminal itself has malfunctioned based on the fourth message and the first message. For example, the AIoT fault handling module can query the fourth message of the corresponding AIoT consumer device based on the identity information of the problematic terminal in the first message.

[0274] Optionally, the first message also includes the fault location, and the fourth message includes the abnormal location corresponding to the sensor information of the problematic terminal. The AIoT fault handling module can determine the fault indication based on the fault location and the abnormal location. Specifically, please refer to the relevant description in Design 3 in step S303 above.

[0275] Alternatively, the first message may also include the fault time, and the fourth message may include the abnormal time corresponding to the sensor information of the faulty terminal. The AIoT fault handling module can determine the fault indication based on the fault time and the abnormal time. For details, please refer to the relevant description in Design 4 in step S303 above.

[0276] Optionally, before step S603, the AIoT fault handling module can determine the service type of the problematic terminal based on its identity information. If the service type of the problematic terminal includes sensing services, then step S603 and the steps following step S603 are executed. If the service type of the problematic terminal includes sensing services, the fourth message used in this application can be used preferentially to determine whether the problematic terminal itself has malfunctioned.

[0277] Step S604: The AIoT fault handling module sends a fault indication to the AIoT consumer device.

[0278] Optionally, the fault indication may include the identity information of the problematic terminal, such as the fault indication being "The problematic AIoT terminal device H has itself malfunctioned".

[0279] Accordingly, the AIoT consumer device receives a fault indication from the AIoT fault handling module. For example, when the fault indication indicates that the faulty terminal is itself malfunctioning, the AIoT consumer device can prioritize troubleshooting the faulty terminal.

[0280] In the embodiment shown in Figure 6, after receiving the fourth message, the AIoT fault handling module can obtain the abnormal time and / or abnormal location of the AIoT terminal device that malfunctioned. After receiving the first message, the AIoT fault handling module can obtain the fault time and / or fault location of the problematic terminal. Further, the AIoT fault handling module can determine whether the problematic terminal itself has malfunctioned based on the abnormal time of the AIoT terminal device and the fault time of the problematic terminal. Alternatively, the AIoT fault handling module can determine whether the problematic terminal itself has malfunctioned based on the abnormal location of the AIoT terminal device and the fault location of the problematic terminal. If the AIoT terminal device itself malfunctions, this application can greatly simplify the fault location steps and optimize the fault location process, eliminating the need to sequentially check alarms or abnormal information at the IoT platform, core network, base station, and finally the terminal, effectively improving the fault location efficiency in AIoT terminal fault scenarios.

[0281] Please refer to Figure 7, which is a flowchart illustrating another possible fault location method provided in this application embodiment. This fault location method may include one or more steps S701 to S704. It should be understood that, for ease of description, the method is described in the order of steps S701 to S704, and is not intended to limit the execution to this specific order. This application embodiment does not limit the order of execution, the execution time, or the number of executions of the above one or more steps. Steps S701 to S704 are as follows:

[0282] Step S701: The AIoT consumer device sends a first message to the AIoT fault handling module.

[0283] Accordingly, the AIoT fault handling module receives the first message from the AIoT consumer device.

[0284] The first message includes the problematic terminal's identity information. This identity information identifies the problematic terminal and can be an ID, account, unique code, unique number, address, etc.

[0285] Specifically, please refer to the relevant description in step S404 above.

[0286] Step S702: The AIoT consumer device sends the first sensor information of the problematic terminal to the AIoT fault handling module.

[0287] Accordingly, the AIoT fault handling module receives the first sensor information from the faulty terminal of the AIoT consumer device.

[0288] Specifically, please refer to the relevant descriptions in steps S406 and S302 above.

[0289] Optionally, the first sensor information may be carried in the first message. For example, the fault location method shown in FIG7 does not include step S702, and the first message in step S701 also includes the first sensor information of the faulty terminal.

[0290] Step S703: The AIoT fault handling module determines the fault indication based on the first sensor information of the faulty terminal.

[0291] The fault indicator is used to indicate whether the problematic terminal itself has malfunctioned.

[0292] Optionally, when the first sensor information meets a predefined abnormal condition, a fault indication is used to indicate that the problematic terminal itself has malfunctioned. Specifically, refer to the relevant description in Design 1 of step S303 above.

[0293] Step S704: The AIoT fault handling module sends a fault indication to the AIoT consumer device.

[0294] Optionally, the fault indication may include the identity information of the problematic terminal, such as the fault indication being "The problematic AIoT terminal device H has itself malfunctioned".

[0295] Accordingly, the AIoT consumer device receives a fault indication from the AIoT fault handling module. For example, when the fault indication indicates that the faulty terminal is itself malfunctioning, the AIoT consumer device can prioritize troubleshooting the faulty terminal.

[0296] In the embodiment shown in Figure 7, after receiving the first message and the first sensor information of the problematic terminal, the AIoT fault handling module can obtain the identity information of the problematic AIoT terminal device and determine whether the problematic terminal itself has malfunctioned based on the first sensor information of the problematic terminal. If the AIoT terminal device itself malfunctions, this application can greatly simplify the fault location steps and optimize the fault location process. It eliminates the need to sequentially check the IoT platform, core network, base station, and finally the terminal for alarms or abnormal information, effectively improving the fault location efficiency in AIoT terminal fault scenarios.

[0297] Please refer to Figure 8, which is a flowchart illustrating another possible fault location method provided in this application embodiment. This fault location method may include one or more steps from S801 to S811. It should be understood that, for ease of description, the method is described in the order of steps S801 to S811, and is not intended to limit the execution to this specific order. This application embodiment does not limit the order of execution, the execution time, or the number of executions of the above one or more steps. Steps S801 to S811 are as follows:

[0298] Step S801: The knowledge base sends the sixth message to the RAN.

[0299] Accordingly, the RAN receives the sixth message from the knowledge base to obtain the identity information of the AIoT terminal devices that need to be reported.

[0300] Similarly, see the relevant description in step S401 above.

[0301] Step S802: The AIoT terminal device sends its sensor information to the RAN.

[0302] Accordingly, the RAN receives sensor information from the AIoT terminal devices.

[0303] Specifically, please refer to the relevant description in step S402 above.

[0304] Step S803: RAN sends sensor information of AIoT terminal devices to the knowledge base.

[0305] Accordingly, the knowledge base receives sensor information from AIoT terminal devices in the RAN.

[0306] Similarly, see the relevant description in step S403 above.

[0307] Step S804: The AIoT consumer device sends the first message to the AIoT fault handling module.

[0308] Accordingly, the AIoT fault handling module receives the first message from the AIoT consumer device.

[0309] The first message includes the problematic terminal's identity information. This identity information identifies the problematic terminal and can be an ID, account, unique code, unique number, address, etc.

[0310] Specifically, please refer to the relevant description in step S404 above.

[0311] Step S805: The AIoT fault handling module sends a second message to the knowledge base.

[0312] Accordingly, the knowledge base receives a second message from the AIoT fault handling module.

[0313] The second message includes the identity information of the problematic terminal. Optionally, the first message also includes the fault time, and the second message also includes the fault time. The fault time is used by the AIoT fault handling module to obtain the first sensor information of the problematic terminal. Further optionally, the first message also includes the fault location, and the second message also includes the fault location. The fault location is used by the AIoT fault handling module to obtain the first sensor information of the problematic terminal.

[0314] Similarly, see the relevant descriptions in steps S405 and S303 above.

[0315] Step S806: The knowledge base sends the first sensor information of the problematic terminal to the AIoT fault handling module.

[0316] Accordingly, the AIoT fault handling module receives the first sensor information from the problematic terminal in the knowledge base.

[0317] The first sensor information includes sensing data and sensing parameter types.

[0318] Similarly, see the relevant descriptions in steps S406 and S302 of the preceding text for implementation 1.

[0319] Step S807: The AIoT fault handling module determines the sensor troubleshooting tool based on the sensor parameter type.

[0320] For example, different sensor parameter types can correspond to different sensor troubleshooting tools. For instance, if the sensor parameter type is E, the corresponding sensor troubleshooting tool is M1; if the sensor parameter type is F, the corresponding sensor troubleshooting tool is M2. The AIoT fault handling module can determine the corresponding sensor troubleshooting tool based on the sensor parameter type in the first sensor information.

[0321] Step S808: The AIoT fault handling module sends the fifth message to the tool library.

[0322] Accordingly, the tool library receives the fifth message from the AIoT fault handling module.

[0323] The fifth message includes the name of the sensor troubleshooting tool, the sensor data of the problematic terminal, and application data reference values. Optionally, the fifth message may also include the sensor parameter type.

[0324] Step S809: The tool library sends the sensor troubleshooting tool call results to the AIoT fault handling module.

[0325] Accordingly, the AIoT fault handling module receives the results of sensor troubleshooting tool calls from the tool library.

[0326] In one possible implementation, the tool library receives a fifth message from the AIoT fault handling module to obtain the name of the sensor troubleshooting tool. Based on this name, the tool library calls the corresponding tool and obtains the result of the tool call based on the sensor data and application data reference values ​​of the problematic terminal. For example, if the sensor parameter type is F and the corresponding sensor troubleshooting tool is M2, the fifth message includes the name of sensor troubleshooting tool M2. The tool library can call sensor troubleshooting tool M2 based on its name and obtain the result based on the sensor data and application data reference values ​​of the problematic terminal in the first sensor information.

[0327] Step S810: The AIoT fault handling module determines the fault indication based on the result of the sensor troubleshooting tool call.

[0328] The fault indicator is used to indicate whether the problematic terminal itself has malfunctioned.

[0329] For example, the result of the sensor troubleshooting tool is a value between 0 and 1. If the value is close to 0, it means that the probability of the problem terminal itself malfunctioning is close to 0. If the value is close to 1, it means that the probability of the problem terminal itself malfunctioning is close to 1. That is, it is considered that the problem terminal itself has malfunctioned.

[0330] This is just an example illustrating one possible implementation of determining fault indication based on the result of calling a sensor troubleshooting tool. In actual use, there may be many more possible implementations, which will not be listed here.

[0331] Step S811: The AIoT fault handling module sends a fault indication to the AIoT consumer device.

[0332] Optionally, the fault indication may include the identity information of the problematic terminal, such as the fault indication being "The problematic AIoT terminal device H has itself malfunctioned".

[0333] Accordingly, the AIoT consumer device receives a fault indication from the AIoT fault handling module. For example, when the fault indication indicates that the faulty terminal is itself malfunctioning, the AIoT consumer device can prioritize troubleshooting the faulty terminal.

[0334] In the embodiment shown in Figure 8, the fault location method of this application can also be applied to the agent automation platform (A-Platform) architecture. After receiving the first message and the first sensor information of the problematic terminal, the AIoT fault handling module can call the corresponding sensor troubleshooting tool through the tool library to obtain the sensor troubleshooting tool call result, and determine whether the problematic terminal itself has failed based on the sensor troubleshooting tool call result. If the AIoT terminal device itself fails, this application can greatly simplify the fault location steps and optimize the fault location process. It eliminates the need to sequentially check the IoT platform, core network, base station, and finally the terminal for alarms or abnormal information, which can effectively improve the fault location efficiency in AIoT terminal fault scenarios.

[0335] The methods of the embodiments of this application have been described in detail above. Below, some apparatuses for implementing the foregoing methods are described. It should be understood that the division of units in the apparatuses provided in the embodiments of this application is only a logical functional division; in actual implementation, they can be fully or partially integrated onto a single physical entity, or they can be physically separated.

[0336] Furthermore, the units or modules in the device can be implemented in the form of processor calling software. For example, the device includes a processor connected to a memory, which stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of each unit of the device. The processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is either internal or external to the device.

[0337] Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all units can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), and the functionality of some or all of the above units is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD), such as a field-programmable gate array (FPGA). This PLD can include a large number of logic gates, and the connection relationships between these logic gates can be configured through configuration files to achieve the functionality of some or all of the above units. All units of the above device can be implemented entirely through processor-invoked software, entirely through hardware circuits, or partially through processor-invoked software with the remaining parts implemented through hardware circuits.

[0338] In this application embodiment, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a central processing unit (CPU) or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. These logical relationships are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. Therefore, each unit in the device can be one or more processors (or processing circuits) configured to implement the above methods, such as a CPU, GPU, microprocessor, DSP, ASIC, FPGA, or a combination of at least two of these processor types.

[0339] Furthermore, the units or modules in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these units or modules are integrated together as a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or implementing the functions of the units in the device. The at least one processor may be of different types, such as CPU and FPGA.

[0340] Several possible devices are listed below.

[0341] Please refer to Figure 9, which is a schematic diagram of a fault location device provided in an embodiment of this application, namely, the fault location device 90. Optionally, the fault location device 90 can be an independent device, such as the AIoT fault processing module 103 shown in Figure 1a or Figure 2a. Alternatively, the fault location device 90 can also be a component in an independent device (such as a node), such as a chip or integrated circuit. The fault location device 90 is used to perform the steps executed by the AIoT fault processing module in the fault location methods shown in Figures 3, 4, 5, 6, 7, or 8.

[0342] As shown in Figure 9, the fault location device 90 includes a transceiver unit 901 and a processing unit 902. The transceiver unit 901 performs one or more operations such as acquiring, receiving, listening, transmitting, and sending. For example, it receives a first message from an AIoT consumer device, acquires first sensor information from the problematic terminal, and sends a fault indication to the AIoT consumer device. The first message includes the identity information of the problematic terminal, indicating that the problematic terminal is an AIoT terminal device, and the AIoT terminal device includes sensors. The fault indication is obtained based on the first sensor information and is used to indicate whether the problematic terminal itself has malfunctioned. The device further includes other operations for implementing the fault location method.

[0343] The processing unit 902 is used to perform one or more operations such as processing, calculation, determination, generation, and updating. For example, it is used to determine a fault indication based on first sensor information and environmental sensor information, wherein the first sensor information and environmental sensor information include data of the same type of sensing parameters. It further includes other operations for implementing a fault location method.

[0344] For related descriptions, please refer to the descriptions of the embodiments shown in Figures 3, 4, 5, 6, 7, or 8, which will not be described in detail here.

[0345] Please refer to Figure 10, which is a schematic diagram of another fault location device provided in this application embodiment, namely, fault location device 100. Optionally, the fault location device 100 can be an independent device, such as the AIoT terminal device 101 shown in Figure 1a or Figure 2a. Alternatively, the fault location device 100 can also be a component in an independent device (such as a node), such as a chip or integrated circuit. The fault location device 100 is used to perform the steps executed by the AIoT terminal device in the fault location methods shown in Figures 3, 4, 5, 6, or 8.

[0346] As shown in Figure 10, the fault location device 100 includes a transceiver unit 1001. The transceiver unit 1001 is used to perform one or more operations such as acquiring, receiving, listening, transmitting, and sending, for example, to send a fourth message to the AIoT fault handling module. The AIoT fault handling module is used to determine whether the problematic terminal itself has malfunctioned. The problematic terminal is an AIoT terminal device, which includes sensors. The fourth message includes the abnormal time and / or abnormal location corresponding to the sensor information of the problematic terminal. It further includes other operations for implementing the fault location method.

[0347] For related descriptions, please refer to the descriptions of the embodiments shown in Figures 3, 4, 5, 6, or 8, which will not be described in detail here.

[0348] Please refer to Figure 11, which is a schematic diagram of another fault location device provided in this application embodiment, namely fault location device 110. Optionally, the fault location device 110 can be an independent device, such as the AIoT consumer device 102 shown in Figure 1a or Figure 2a. Alternatively, the fault location device 110 can also be a component in an independent device (such as a node), such as a chip or integrated circuit. The fault location device 110 is used to perform the steps performed by the AIoT consumer device in the fault location methods shown in Figures 3, 4, 5, 6, 7, or 8.

[0349] As shown in Figure 11, the fault location device 110 includes a transceiver unit 1101. The transceiver unit 1101 is used to perform one or more operations such as acquiring, receiving, listening, transmitting, and sending, for example, sending a first message to the AIoT fault handling module and receiving a fault indication from the AIoT fault handling module. The first message includes the identity information of the problematic terminal, indicating that the problematic terminal belongs to an AIoT terminal device, which includes sensors, and the fault indication indicates whether the problematic terminal itself has malfunctioned. It further includes other operations for implementing the fault location method.

[0350] For related descriptions, please refer to the descriptions of the embodiments shown in Figures 3, 4, 5, 6, 7, or 8, which will not be described in detail here.

[0351] Please refer to Figure 12, which is a schematic diagram of another fault location device provided in this application embodiment, namely fault location device 120. Optionally, the fault location device 120 can be an independent device, such as the AIoT monitoring module 104 shown in Figure 1a or the knowledge base 105 shown in Figure 2a. Alternatively, the fault location device 120 can also be a component in an independent device (such as a node), such as a chip or integrated circuit. The fault location device 120 is used to perform the steps performed by the first device in the fault location method shown in Figure 3, the steps performed by the AIoT monitoring module in the fault location methods shown in Figures 4 and 5, or the steps performed by the knowledge base in the fault location method shown in Figure 8.

[0352] As shown in Figure 12, the fault location device 120 includes a transceiver unit 1201. The transceiver unit 1201 is used to perform one or more operations such as acquiring, receiving, listening, transmitting, and sending. For example, it is used to send a sixth message, receive sensor information from the AIoT terminal device, and send the first sensor information of the problematic terminal to the AIoT fault handling module. The sixth message includes the identity information of the AIoT terminal device, and the sensor information of the AIoT terminal device includes the sensor data of the AIoT terminal device. The problematic terminal is an AIoT terminal device, and the AIoT terminal device includes sensors. The first sensor information is the sensor information of the AIoT terminal device and is used to determine a fault indication, which indicates whether the problematic terminal itself has malfunctioned. It further includes other operations for implementing the fault location method.

[0353] For related descriptions, please refer to the descriptions of the embodiments shown in Figures 3, 4, 5 or 8, which will not be described in detail here.

[0354] Please refer to Figure 13, which is a schematic diagram of another fault location device provided in an embodiment of this application. The fault location device 130 can be a device or a component within the device, such as a chip or integrated circuit. The fault location device 130 may include at least one processor 1302 and a communication interface 1304. Further optionally, the fault location device may also include at least one memory 1301. Even more optionally, it may also include a bus 1303, wherein the memory 1301, processor 1302, and communication interface 1304 are connected via the bus 1303.

[0355] The memory 1301 provides storage space, which can store data such as the operating system and computer programs. The memory 1301 can be one or a combination of several of the following: random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0356] Processor 1302 is a module that performs arithmetic and / or logical operations. Specifically, it can be one or a combination of processing modules such as a central processing unit (CPU), graphics processing unit (GPU), microprocessor unit (MPU), application specific-integrated circuit (ASIC), field programmable gate array (FPGA), complex programmable logic device (CPLD), coprocessor (to assist the central processing unit in completing corresponding processing and applications), and micro controller unit (MCU).

[0357] The communication interface 1304 can be used to provide information input or output to at least one processor. And / or the communication interface can be used to receive and / or send data to externally transmitted data, and can be a wired link interface including an Ethernet cable, or a wireless link interface (Wi-Fi, Bluetooth, general wireless transmission, vehicular short-range communication technology, etc.). Optionally, the communication interface 1304 may also include a transmitter (such as a radio frequency transmitter, antenna, etc.) or a receiver coupled to the interface.

[0358] The processor 1302 in the fault location device 130 is used to read the computer program stored in the memory 1301 and to execute the aforementioned fault location method, such as the fault location method described in the embodiments shown in FIG3, FIG4, FIG5, FIG6, FIG7 or FIG8.

[0359] In one design, the fault location device 130 can be the AIoT fault processing module shown in the embodiments of Figures 3, 4, 5, and 6. The processor 1302 in the fault location device 130 is used to read the computer program stored in the memory 1301 and to perform the following operations:

[0360] Receive the first message from the environmentally powered IoT AIoT consumer device. The first message includes the identity information of the problematic terminal. The problematic terminal belongs to the AIoT terminal device, and the AIoT terminal device includes sensors.

[0361] Obtain the first sensor information of the problematic terminal;

[0362] A fault indication is sent to the AIoT consumer device. The fault indication is based on the information from the first sensor and is used to indicate whether the terminal itself has malfunctioned.

[0363] The processor 1302 in the fault location device 130 is used to read the computer program stored in the memory 1301, and is also used to execute other operations of the AIoT fault handling module in the embodiments shown in Figures 3, 4, 5, 6, 7 or 8, which will not be described in detail here.

[0364] In another design, the fault location device 130 can be an AIoT terminal device as shown in the embodiments of Figures 3, 4, 5, 6, or 8. The processor 1302 in the fault location device 130 is used to read the computer program stored in the memory 1301 and to perform the following operations:

[0365] Send a fourth message to the environmental power supply IoT (AIoT) fault handling module;

[0366] The AIoT fault handling module is used to determine whether the problematic terminal itself has malfunctioned. The problematic terminal is an AIoT terminal device, which includes sensors. The fourth message includes the abnormal time and / or abnormal location corresponding to the sensor information of the problematic terminal.

[0367] The processor 1302 in the fault location device 130 is used to read the computer program stored in the memory 1301, and is also used to execute other operations of the AIoT terminal device in the embodiments shown in Figures 3, 4, 5, 6 or 8, which will not be described in detail here.

[0368] In another design, the fault location device 130 can be an AIoT consumer device as shown in the embodiments of Figures 3, 4, 5, 6, 7, or 8. The processor 1302 in the fault location device 130 is used to read the computer program stored in the memory 1301 to perform the following operations:

[0369] Send a first message to the environmental power supply IoT (AIoT) fault handling module. The first message includes the identity information of the problematic terminal. The problematic terminal belongs to the AIoT terminal device, and the AIoT terminal device includes sensors.

[0370] Receive fault indications from the AIoT fault handling module. The fault indications are used to indicate whether the problematic terminal itself has malfunctioned.

[0371] The processor 1302 in the fault location device 130 is used to read the computer program stored in the memory 1301, and is also used to execute other operations of the AIoT consumer device in the embodiments shown in Figures 3, 4, 5, 6, 7 or 8, which will not be described in detail here.

[0372] In another design, the fault location device 130 can be the first device in the embodiment shown in FIG3, the AIoT monitoring module in the embodiments shown in FIG4 and 5, or the knowledge base in the embodiment shown in FIG8. The processor 1302 in the fault location device 130 is used to read the computer program stored in the memory 1301 to perform the following operations:

[0373] Send a sixth message, which includes the identity information of the AIoT terminal device;

[0374] Receive sensor information from AIoT terminal devices, which includes sensor data from AIoT terminal devices;

[0375] Send the first sensor information of the problematic terminal to the environmental power supply IoT (AIoT) fault handling module;

[0376] Among them, the problematic terminal belongs to the AIoT terminal device, which includes sensors. The first sensor information belongs to the sensor information of the AIoT terminal device. The first sensor information is used to determine the fault indication, which is used to indicate whether the problematic terminal itself has malfunctioned.

[0377] The processor 1302 in the fault location device 130 is used to read the computer program stored in the memory 1301, and is also used to execute other operations of the first device in the embodiment shown in FIG3, other operations of the AIoT monitoring module in the embodiments shown in FIG4 and FIG5, or other operations of the knowledge base in the embodiment shown in FIG8, which will not be described in detail here.

[0378] This application also provides a computer-readable storage medium storing a computer program that, when executed on one or more processors, causes the fault location device containing the computer-readable storage medium to implement the method of the embodiment shown in FIG3, FIG4, FIG5, FIG6, FIG7, or FIG8.

[0379] This application also provides a chip system, which includes at least one processor and a communication interface. The communication interface is used to send and / or receive data, and the at least one processor is used to call a computer program stored in at least one memory, so that the fault location device in which the chip system is located implements the method of the embodiment shown in FIG3, FIG4, FIG5, FIG6, FIG7, or FIG8.

[0380] Furthermore, at least one processor may include at least one of a CPU, MPU, MCU, or coprocessor.

[0381] This application also provides a network system, including the aforementioned AIoT terminal device (including the faulty terminal), an AIoT fault handling module, and an AIoT consumer device. The network system is used to implement the methods of the embodiments shown in FIG3, FIG4, FIG5, FIG6, FIG7, or FIG8.

[0382] This application also provides a network system, including the aforementioned AIoT terminal device (including the problematic terminal), a first device, an AIoT fault handling module, and an AIoT consumer device. The network system is used to implement the methods of the embodiments shown in Figures 3, 4, 5, 6, 7, or 8. Optionally, the first device may be an AIoT monitoring module or a knowledge base.

[0383] This application also provides a computer program product that, when running on one or more processors, enables the fault location device containing the computer program product to implement the fault location method described in the embodiments shown in Figures 3, 4, 5, 6, 7, or 8.

[0384] In the above embodiments, it can be implemented entirely or partially by software, hardware, firmware, or any combination thereof.

[0385] When implemented using software, it can be implemented in whole or in part as a product of computer instructions.

[0386] When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application can be implemented. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in or transmitted through a computer-readable storage medium. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. Available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks (SSDs)).

[0387] The steps in the method embodiments of this application can be adjusted, combined, or deleted according to actual needs.

[0388] The modules in the device embodiments of this application can be merged, divided, and deleted according to actual needs.

Claims

1. A fault location method, characterized in that, include: Receive a first message from an ambient power supply IoT (AIoT) consumer device. The first message includes the identity information of the problematic terminal, which is an AIoT terminal device and includes sensors. Obtain the first sensor information of the problematic terminal; A fault indication is sent to the AIoT consumer device. The fault indication is obtained based on the information from the first sensor and is used to indicate whether the problematic terminal itself has malfunctioned.

2. The method according to claim 1, characterized in that, The problematic terminal is an AIoT terminal device that has not reported data, and / or, the problematic terminal is an AIoT terminal device with abnormal data.

3. The method according to claim 1 or 2, characterized in that, The problematic terminal's service type includes sensor-related services.

4. The method according to any one of claims 1-3, characterized in that, The first sensor information includes sensing data, and the first sensor information also includes at least one of the following: the identity information of the problematic terminal, service type, sensing parameter type, sensing time, and sensing location.

5. The method according to claim 4, characterized in that, The first message also includes the fault time, and the sensing data is data prior to the fault time; And / or, the first message may also include the fault location, and the sensing data may be related to the fault location.

6. The method according to any one of claims 1-5, characterized in that, The step of obtaining the first sensor information of the problematic terminal includes: Send a second message to the first device, the second message including the identity information of the problematic terminal; Receive the first sensor information from a first device, which is an AIoT monitoring module or a knowledge base.

7. The method according to claim 6, characterized in that, The first message also includes the fault time, and the second message also includes the fault time; And / or, the first message may also include the fault location, and the second message may also include the fault location.

8. The method according to any one of claims 1-5, characterized in that, The step of obtaining the first sensor information of the problematic terminal includes: Receive the first sensor information from the AIoT consumer device.

9. The method according to any one of claims 1-8, characterized in that, When the first sensor information meets a predefined abnormal condition, the fault indication is used to indicate that the problematic terminal itself has malfunctioned; The abnormal condition includes at least one of the following: The number of data points in the first sensor information that exceed the normal value range is greater than the first threshold. The first sensor information includes multiple data items. The measured values ​​of the parameters related to the normal operation of the problematic terminal in the first sensor information are close to or exceed the threshold values ​​of the parameters for the normal operation of the problematic terminal; The first sensor information contains anomalies.

10. The method according to claim 6 or 7, characterized in that, The method further includes: The fault indication is determined based on the first sensor information and the environmental sensor information, wherein the first sensor information and the environmental sensor information include data of the same type of sensing parameter.

11. The method according to claim 10, characterized in that, The second message also includes a first source type, wherein the source type corresponding to the first sensor information is the first source type, and the first source type is used to indicate that the source of the sensor data is an AIoT terminal device; The method further includes: Based on the first sensor information, the abnormal sensing information of the problematic terminal is determined, and the abnormal sensing information belongs to the first sensor information; Send a third message to the AIoT monitoring module. The third message includes a second source type and first information. The second source type indicates that the source of the sensing data is not an AIoT terminal device. The first information includes an abnormal sensing parameter type, which is the sensing parameter type of the abnormal sensing information. Receive environmental sensor information from the AIoT monitoring module, wherein the sensing parameter type of the environmental sensor information includes the abnormal sensing parameter type.

12. The method according to claim 11, characterized in that, The first information also includes the abnormal time corresponding to the abnormal sensing information, and the environmental sensor information also includes the sensor information corresponding to the abnormal time; And / or, the first information may also include the abnormal location corresponding to the abnormal sensing information, and the environmental sensor information may also include sensor information corresponding to the abnormal location.

13. The method according to claim 11 or 12, characterized in that, When the difference between the abnormal sensing information and the environmental sensor information meets a preset difference condition, the fault indication is used to indicate that the problematic terminal itself has malfunctioned.

14. The method according to any one of claims 1-3, characterized in that, The step of obtaining the first sensor information of the problematic terminal includes: A fourth message is received from the problematic terminal, the fourth message including the abnormal time and / or abnormal location corresponding to the sensor information of the problematic terminal.

15. The method according to claim 14, characterized in that, The first message also includes the fault location, the fourth message includes the abnormal location corresponding to the sensor information of the problematic terminal, and the method further includes: The fault indication is determined based on the fault location and the abnormal location.

16. The method according to claim 14 or 15, characterized in that, The first message also includes the fault time, the fourth message includes the abnormal time corresponding to the sensor information of the problematic terminal, and the method further includes: The fault indication is determined based on the fault time and the abnormal time.

17. The method according to claim 6, characterized in that, The first device is a knowledge base, the first sensor information includes sensing parameter types, and the method further includes: Determine the sensor troubleshooting tool based on the sensor parameter type; Send a fifth message to the tool library, the fifth message including the name of the sensor troubleshooting tool, the sensor data of the problematic terminal, and the application data reference value; Receive the results of sensor troubleshooting tool calls from the tool library; The fault indication is determined based on the result of the sensor troubleshooting tool call.

18. A fault location method, characterized in that, include: Send a fourth message to the environmental power supply IoT (AIoT) fault handling module; The AIoT fault handling module is used to determine whether the problematic terminal itself has malfunctioned. The problematic terminal is an AIoT terminal device, which includes sensors. The fourth message includes the abnormal time and / or abnormal location corresponding to the sensor information of the problematic terminal.

19. A fault location method, characterized in that, include: Send a first message to the environmental power supply IoT (AIoT) fault handling module. The first message includes the identity information of the problematic terminal, which belongs to the AIoT terminal device, and the AIoT terminal device includes sensors. The system receives a fault indication from the AIoT fault handling module, which indicates whether the problematic terminal itself has malfunctioned.

20. The method according to claim 19, characterized in that, The method further includes: The first sensor information of the problematic terminal is sent to the AIoT fault handling module. The first sensor information is used to determine the fault indication. The first sensor information includes sensing data and also includes at least one of the following: the identity information of the problematic terminal, service type, sensing parameter type, sensing time, and sensing location.

21. A fault location method, characterized in that, include: Send a sixth message, which includes the identity information of the AIoT terminal device; Receive sensor information from the AIoT terminal device, wherein the sensor information from the AIoT terminal device includes the sensing data of the AIoT terminal device; Send the first sensor information of the problematic terminal to the environmental power supply IoT (AIoT) fault handling module; The problematic terminal belongs to the AIoT terminal device, which includes sensors. The first sensor information belongs to the sensor information of the AIoT terminal device. The first sensor information is used to determine a fault indication, which is used to indicate whether the problematic terminal itself has malfunctioned.

22. The method according to claim 21, characterized in that, The sensor information of the AIoT terminal device also includes at least one of the following: the identity information of the AIoT terminal device, service type, sensing parameter type, sensing time, and sensing location.

23. A fault location device, characterized in that, include: Transceiver unit, used for: Receive a first message from an ambient power supply IoT (AIoT) consumer device. The first message includes the identity information of the problematic terminal, which is an AIoT terminal device and includes sensors. Obtain the first sensor information of the problematic terminal; A fault indication is sent to the AIoT consumer device. The fault indication is obtained based on the information from the first sensor and is used to indicate whether the problematic terminal itself has malfunctioned.

24. A fault location device, characterized in that, include: The transceiver unit is used to send a fourth message to the environmental power supply IoT (AIoT) fault handling module. The AIoT fault handling module is used to determine whether the problematic terminal itself has malfunctioned. The problematic terminal is an AIoT terminal device, which includes sensors. The fourth message includes the abnormal time and / or abnormal location corresponding to the sensor information of the problematic terminal.

25. A fault location device, characterized in that, include: Transceiver unit, used for: Send a first message to the environmental power supply IoT (AIoT) fault handling module. The first message includes the identity information of the problematic terminal, which belongs to the AIoT terminal device, and the AIoT terminal device includes sensors. The system receives a fault indication from the AIoT fault handling module, which indicates whether the problematic terminal itself has malfunctioned.

26. A fault location device, characterized in that, include: Transceiver unit, used for: Send a sixth message, which includes the identity information of the AIoT terminal device; Receive sensor information from the AIoT terminal device, wherein the sensor information from the AIoT terminal device includes the sensing data of the AIoT terminal device; Send the first sensor information of the problematic terminal to the environmental power supply IoT (AIoT) fault handling module; The problematic terminal belongs to the AIoT terminal device, which includes sensors. The first sensor information belongs to the sensor information of the AIoT terminal device. The first sensor information is used to determine a fault indication, which is used to indicate whether the problematic terminal itself has malfunctioned.

27. A chip system, characterized in that, The chip system includes at least one processor and a communication interface, the communication interface being used to send and / or receive data, and the at least one processor being used to invoke a computer program stored in at least one memory, so that the device in which the chip system is located implements the method as described in any one of claims 1-22.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on one or more processors, performs the method as described in any one of claims 1-22.

29. A network system, characterized in that, This includes faulty terminals, environmental power supply IoT (AIoT) fault handling modules, and AIoT consumer devices; The problematic terminal includes the fault location device as described in claim 24, the AIoT fault handling module includes the fault location device as described in claim 23, and the AIoT consumer device includes the fault location device as described in claim 25.

30. A network system, characterized in that, It includes a problematic terminal, a first device, an AIoT fault handling module, and an AIoT consumer device, wherein the first device is an environmental power supply IoT AIoT monitoring module or a knowledge base; The problematic terminal includes the fault location device as described in claim 24, the first device includes the fault location device as described in claim 26, the AIoT fault handling module includes the fault location device as described in claim 23, and the AIoT consumer device includes the fault location device as described in claim 25.

Images