Fault detection method, master device, slave device and computer-readable storage medium

Abstract

In the technical scheme of the fault detection method, the master device, the slave device and the computer readable storage medium provided by the embodiment of the application, after the master device and the slave device establish a connection, the fault category meeting the preset condition is acquired from the slave device, the corresponding fault event is generated according to the fault category, the fault event includes a plurality of detection items, whether the slave device has the faults corresponding to the plurality of detection items is detected according to the plurality of detection items, if it is detected that the slave device has any fault corresponding to the detection item, prompt information is provided to the user to prompt the user to eliminate the fault corresponding to the detection item, so that the master device can detect the fault of the slave device, and the master device can remind the user of the fault, and the maintenance cost of the slave device is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of fault detection, and in particular to a fault detection method, a master device, a slave device and a computer-readable storage medium. Background Art

[0002] Traditional electronic devices like headphones, air conditioners, speakers, and watches are gradually becoming intelligent. However, due to cost constraints, the computing and interactive capabilities of these devices are still relatively weak. When such devices malfunction, users are largely unable to identify the root cause, let alone self-repair. Users typically have to go to a service center for professional manual inspection and repair, which is costly. Summary of the Invention

[0003] In view of this, the present invention provides a fault detection method, a master device, a slave device and a computer-readable storage medium, which connect the master device to the slave device, can detect faults in the slave device through the master device, and can remind the user of faults through the master device, thereby reducing the maintenance cost of the slave device.

[0004] In one aspect, an embodiment of the present invention provides a fault detection method, which is applied to a master device and includes:

[0005] After establishing a connection with a slave device, obtaining a fault category that meets a preset condition from the slave device;

[0006] Generate a corresponding fault event according to the fault category, wherein the fault event includes multiple detection items;

[0007] detecting, according to the plurality of detection items, whether the slave device has faults corresponding to the plurality of detection items;

[0008] If it is detected that the slave device has a fault corresponding to any of the detection items, prompt information is provided to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0009] In a possible implementation manner, after detecting that the slave device has a fault corresponding to any of the detection items, the method further includes:

[0010] Fault information corresponding to the fault is sent to the slave device, so that the slave device generates the prompt information according to the fault information, and provides the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0011] In a possible implementation, the preset condition includes that the highest fault severity value is greater than or equal to a preset threshold;

[0012] Obtaining a fault category that meets a preset condition from the slave device includes:

[0013] Obtaining a fault category with the highest fault severity value from the slave device;

[0014] Determine whether the highest fault severity value is greater than or equal to a preset threshold;

[0015] If it is determined that the fault severity value is greater than or equal to the preset threshold, the fault category with the highest fault severity value is determined as the fault category that meets the preset condition.

[0016] In a possible implementation, after generating a corresponding fault event according to the fault category, where the fault event includes multiple detection items, the method further includes:

[0017] Reduce the fault severity value corresponding to the fault category to a set severity value.

[0018] In a possible implementation, after providing prompt information to the user to prompt the user to troubleshoot the fault corresponding to the detection item, the method further includes:

[0019] receiving feedback information from the user, wherein the feedback information includes operation information corresponding to the ignore operation;

[0020] Counting the number of times the ignore operation is performed according to the operation information corresponding to the ignore operation;

[0021] If it is determined that the number of the ignore operations is greater than or equal to the preset number, the detection item is removed from the fault event.

[0022] In a second aspect, an embodiment of the present invention provides a fault detection method, which is applied to a slave device and includes:

[0023] Determine multiple fault categories based on the acquired device software and hardware information;

[0024] When a fault occurs, the fault category to which the fault belongs is determined, and the fault severity value corresponding to the fault category is incremented by N according to a pre-established marking mechanism;

[0025] After establishing a connection with the master device, a fault category that meets preset conditions is sent to the master device. The preset conditions include the highest fault severity value being greater than or equal to a preset threshold value, so that the master device can generate a corresponding fault event based on the fault category. The fault event includes multiple detection items. Based on the multiple detection items, it is detected whether the slave device has faults corresponding to multiple detection items. If it is detected that the slave device has a fault corresponding to any of the detection items, a prompt message is provided to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0026] In a possible implementation, the method further includes:

[0027] Receive fault information corresponding to the fault sent by the master device, generate prompt information according to the fault information, and provide the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0028] In a third aspect, an embodiment of the present invention provides a main device, comprising: a display screen; one or more processors; a memory; a plurality of application programs; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions. When the instructions are executed by the device, the device specifically performs the following steps:

[0029] After establishing a connection with a slave device, obtaining a fault category that meets a preset condition from the slave device;

[0030] Generate a corresponding fault event according to the fault category, wherein the fault event includes multiple detection items;

[0031] detecting, according to the plurality of detection items, whether the slave device has faults corresponding to the plurality of detection items;

[0032] If it is detected that the slave device has a fault corresponding to any of the detection items, prompt information is provided to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0033] In an optional implementation, when the instruction is executed by the device, the device performs the following steps:

[0034] Fault information corresponding to the fault is sent to the slave device, so that the slave device generates the prompt information according to the fault information, and provides the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0035] In an optional implementation, the preset condition includes that the highest fault severity value is greater than or equal to a preset threshold; when the instruction is executed by the device, the device performs the following steps:

[0036] Obtaining a fault category that meets a preset condition from the slave device includes:

[0037] Obtaining a fault category with the highest fault severity value from the slave device;

[0038] Determine whether the highest fault severity value is greater than or equal to a preset threshold;

[0039] If it is determined that the fault severity value is greater than or equal to the preset threshold, the fault category with the highest fault severity value is determined as the fault category that meets the preset condition.

[0040] In an optional implementation, when the instruction is executed by the device, the device performs the following steps:

[0041] Reduce the fault severity value corresponding to the fault category to a set severity value.

[0042] In an optional implementation, when the instruction is executed by the device, the device performs the following steps:

[0043] receiving feedback information from the user, wherein the feedback information includes operation information corresponding to the ignore operation;

[0044] Counting the number of times the ignore operation is performed according to the operation information corresponding to the ignore operation;

[0045] If it is determined that the number of the ignore operations is greater than or equal to the preset number, the detection item is removed from the fault event.

[0046] In a fourth aspect, an embodiment of the present invention provides a slave device, comprising: a display screen; one or more processors; a memory; a plurality of application programs; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions. When the instructions are executed by the device, the device specifically performs the following steps:

[0047] Determine multiple fault categories based on the acquired device software and hardware information;

[0048] When a fault occurs, the fault category to which the fault belongs is determined, and the fault severity value corresponding to the fault category is added with N according to a pre-established marking mechanism; after establishing a connection with the master device, the fault category that meets the preset conditions is sent to the master device, and the preset conditions include the highest fault severity value being greater than or equal to a preset threshold, so that the master device can generate a corresponding fault event according to the fault category, and the fault event includes multiple detection items. Based on the multiple detection items, it is detected whether the slave device has multiple faults corresponding to the detection items. If it is detected that the slave device has a fault corresponding to any of the detection items, a prompt message is provided to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0049] In an optional implementation, when the instruction is executed by the device, the device performs the following steps:

[0050] Receive fault information corresponding to the fault sent by the master device, generate prompt information according to the fault information, and provide the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0051] In a fifth aspect, an embodiment of the present invention provides a computer-readable storage medium, which is a program code for execution by a device, and the program code includes instructions for executing the method in the first aspect or any possible implementation of the first aspect.

[0052] In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium is used for program code executed by a device, and the program code includes instructions for executing the method in the second aspect or any possible implementation of the second aspect.

[0053] In the technical solution provided by the embodiment of the present invention, after the master device establishes a connection with the slave device, a fault category that meets the preset conditions is obtained from the slave device, and a corresponding fault event is generated according to the fault category. The fault event includes multiple detection items. Based on the multiple detection items, it is detected whether the slave device has multiple faults corresponding to the detection items. If it is detected that the slave device has a fault corresponding to any detection item, prompt information is provided to the user to prompt the user to eliminate the fault corresponding to the detection item, so that the master device can perform fault detection on the slave device and the master device can remind the user of the fault, thereby reducing the maintenance cost of the slave device. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0055] Figure 1 Middle a to Figure 1 Figure c is a schematic diagram showing the effect of a fault detection method provided by the related art;

[0056] Figure 2 This is an architectural diagram of a fault detection system provided by one embodiment of the present invention;

[0057] Figure 3 This is a flow chart of a fault detection method provided by one embodiment of the present invention;

[0058] Figure 4 is a schematic diagram of a fault event and detection items provided by an embodiment of the present invention;

[0059] Figure 5a is a schematic diagram of an interface for providing prompt information by a master device according to an embodiment of the present invention;

[0060] Figure 5 b is a schematic diagram of an interface for providing prompt information by another master device provided in an embodiment of the present invention;

[0061] Figure 6a This is a schematic diagram of an interface for providing prompt information from a device provided in one embodiment of the present invention;

[0062] Figure 6b This is a schematic diagram of an interface in which a master device and a slave device jointly provide prompt information, provided by an embodiment of the present invention;

[0063] Figure 7 This is a schematic diagram of an interface for ignoring an operation provided by an embodiment of the present invention;

[0064] Figure 8 is a flow chart of another fault detection method provided by one embodiment of the present invention;

[0065] Figure 9 is a flow chart of another fault detection method provided by one embodiment of the present invention;

[0066] Figure 10 is a schematic block diagram of a master device provided by an embodiment of the present invention;

[0067] Figure 11 is a schematic block diagram of another slave device provided by an embodiment of the present invention;

[0068] Figure 12 A schematic structural diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0069] In order to better understand the technical solution of the present invention, the embodiments of the present invention are described in detail below with reference to the accompanying drawings.

[0070] It should be understood that the embodiments described are only a portion of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative work are within the scope of protection of the present invention.

[0071] The terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. The singular forms "a", "an", "the" and "the" used in the embodiments of the present invention and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise.

[0072] It should be understood that the term "and / or" as used herein simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A alone, A and B together, or B alone. Furthermore, the character " / " in this document generally indicates an "or" relationship between the associated objects.

[0073] Figure 1 Middle a to Figure 1 Figure c is a schematic diagram of the effect of a fault detection method in the related art. This method can detect whether there is an abnormality in the battery capacity when the mobile phone is charging. If an abnormality is detected in the battery capacity, it can remind the user of the abnormal battery capacity and guide the user to repair it. Specifically, Figure 1 As shown in a, a pop-up window displays a prompt message "The battery power is decreasing too fast, the battery may be abnormal, and it is recommended to go to a service outlet for inspection." When the user clicks operation S101 and clicks on the prompt message, as shown in FIG. Figure 1 As shown in Figure b, the display interface can display multiple options, including "booking service", "mail-in repair service" and "door-to-door service", which guide users to perform repairs. For example, when the user clicks the "mail-in repair service" option S102, as shown in Figure 103, Figure 1 As shown in Figure c, the display interface shows information such as the faulty device and fault type, allowing the user to select the fault type.

[0074] However, in the related art, electronic devices that can perform fault detection using the above-mentioned fault detection method are usually electronic devices with strong computing power and good interactive capabilities. For example, mobile phones, tablet computers, laptop computers, etc. However, the computing power and interactive capabilities of electronic devices such as headphones, electronic bracelets, watches, etc. are relatively weak. Therefore, when such electronic devices fail, they cannot be detected by the above-mentioned fault detection method and the user cannot be reminded to perform fault repairs. In other words, for electronic devices with relatively weak computing power and interactive capabilities, users cannot perceive the cause of the failure of the electronic device, let alone perform self-service repairs. Therefore, users can usually only go to service outlets for inspection or repair through professional manual inspections, resulting in the problem of high repair costs for such electronic devices.

[0075] In addition, in the process of executing the fault detection method in the related art, it is usually necessary to detect each fault detection item one by one, which causes the problems of high fault detection triggering frequency and many invalid detections.

[0076] Based on this, the technical problems to be solved by the present invention are: how to solve the problem of poor fault notification capabilities of slave devices (electronic devices with weak computing power and weak interactive capabilities, hereinafter collectively referred to as slave devices), and how to solve the problem of low cross-device fault detection efficiency. To address the above technical problems, the embodiments of the present invention provide a fault detection system, which is specifically as follows:

[0077] Figure 2 This is an architectural diagram of a fault detection system provided by one embodiment of the present invention, such as Figure 2 As shown, the system 100 includes a master device 110 and a slave device 120. The master device 110 is used to indicate terminal devices with strong computing and interactive capabilities, such as mobile phones, tablet computers, laptops, augmented reality (AR) / virtual reality (VR), vehicle-mounted terminals, servers, or cloud computing. The slave device 120 is used to indicate terminal devices with weak computing and interactive capabilities, such as headphones, electronic bracelets, and watches.

[0078] In this embodiment of the present invention, by connecting the master device 110 and the slave device 120, the master device 110 can detect faults in the slave device 120 and notify the user of faults via the master device 110, thereby reducing the maintenance cost of the slave device. Furthermore, the slave device 120 can also notify the user of faults, thereby improving the efficiency of fault notifications.

[0079] Specifically, the slave device 120 is used to determine multiple fault categories based on the acquired device software information and device hardware information. The device software information is used to indicate the software programs included in the slave device system. For example, the device software information includes multiple information such as performance, power consumption, reliability or application. The slave device 120 can determine each of the above types of information as a fault category. The device hardware information is used to indicate the hardware facilities included in the slave device system. For example, the device hardware information includes multiple information such as communication, audio, camera, battery, charging, Wi-Fi, Global Positioning System (GPS), Near Field Communication (NFC), Bluetooth, infrared, storage, motor button or fingerprint. The slave device 120 can determine each of the above types of information as a fault category.

[0080] When a fault occurs, slave device 120 is further configured to determine the fault category to which the fault belongs and, based on a pre-established dotting mechanism, add N to the fault severity value corresponding to the fault category. By determining multiple fault categories and the corresponding fault severity values ​​for each fault category, master device 110 can subsequently determine the fault category that meets pre-set conditions.

[0081] Furthermore, the master device 110 is configured to establish a connection relationship between the master device 110 and the slave device 120 by sending a connection call request to the slave device 120. After the master device 110 establishes a connection with the slave device 120, the master device 110 is further configured to send a request to the slave device 120 to obtain a fault category, requesting to obtain a fault category that meets preset conditions from the slave device 120. After receiving the request, the slave device 120 sends the fault category that meets the preset conditions to the master device 110. The preset conditions include the highest fault severity value being greater than or equal to a preset threshold, so that the master device 110 generates a corresponding fault event according to the fault category. The fault event includes multiple detection items. Based on the multiple detection items, it is detected whether the slave device has faults corresponding to the multiple detection items. If it is detected that the slave device has a fault corresponding to any detection item, a prompt message is provided to the user to prompt the user to eliminate the fault corresponding to the detection item. Among them, the preset conditions include that the highest fault severity value is greater than or equal to a preset threshold, that is, the process of the master device 110 obtaining the fault category that meets the preset conditions from the slave device 120 may include: obtaining the fault category with the highest fault severity value from the slave device, judging whether the highest fault severity value is greater than or equal to the preset threshold, and if it is judged that the fault severity value is greater than or equal to the preset threshold, determining the fault category with the highest fault severity value as the fault category that meets the preset conditions.

[0082] In addition, the master device 110 is further configured to transmit fault information corresponding to the fault to the slave device 120, so that the slave device 120 generates prompt information based on the fault information and provides the prompt information to the user, prompting the user to troubleshoot the fault corresponding to the detection item. The master device 110 is further configured to receive user feedback information, including operation information corresponding to the ignore operation, and to count the number of ignore operations based on the operation information corresponding to the ignore operation. If it is determined that the number of ignore operations is greater than or equal to a preset number, the detection item is removed from the fault event.

[0083] Optionally, the slave device 120 is further configured to receive fault information corresponding to the fault sent by the master device, generate prompt information according to the fault information, and provide the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0084] It should be noted that after the master device 110 generates a corresponding fault event according to the fault type, the master device 110 is further configured to reduce the fault severity value corresponding to the fault type to a set severity value.

[0085] In the embodiment of the present invention, through the above-mentioned system 100, it is possible to detect faults of slave devices through the master device and to remind the user of the faults through the master device. Compared with the related art which usually requires comprehensive detection of electronic devices, the embodiment of the present invention obtains the fault category that meets the preset conditions and generates the corresponding fault event according to the fault category, and detects the detection items corresponding to the fault event, thereby reducing the detection power consumption of the system and reducing the detection cost of the slave device. Figure 3 , including steps 102 to 110, the process of the fault detection method is described in detail.

[0086] Figure 3 A flowchart of a fault detection method provided by an embodiment of the present invention is shown in FIG. Figure 3 As shown, the method is applied to a master device, and the method includes:

[0087] Step 102: After establishing a connection with the slave device, obtain a fault category that meets a preset condition from the slave device.

[0088] In an embodiment of the present invention, before executing step 102, it also includes: determining multiple fault categories from the device based on the acquired device software information and device hardware information; when a fault occurs, determining the fault category to which the fault belongs, and adding N to the fault severity value corresponding to the fault category according to a pre-established marking mechanism.

[0089] In an embodiment of the present invention, device software information is used to indicate the software programs included in the slave device system. For example, the device software information includes multiple information such as performance, power consumption, reliability or application, and the slave device 120 determines each type of information as a fault category. The device hardware information is used to indicate the hardware facilities included in the slave device system. For example, the device hardware information includes multiple information such as communication, audio, camera, battery, charging, Wi-Fi, Global Positioning System (GPS), Near Field Communication (NFC), Bluetooth, infrared, storage, motor button or fingerprint, and the slave device 120 can determine each of the above types of information as a fault category.

[0090] As an optional solution, for example, the multiple fault categories determined from the device based on the device software information include performance, power consumption, reliability or application. Similarly, the multiple fault categories determined from the device based on the device hardware information include communication, audio, camera, battery, charging, Wi-Fi, Global Positioning System (GPS), Near Field Communication (NFC), Bluetooth, infrared, storage, motor button or fingerprint.

[0091] The following example illustrates the process of determining the fault category to which the fault belongs and, based on a pre-established notation mechanism, adding N to the fault severity value corresponding to the fault category when a fault occurs. For example, taking a battery short circuit fault as an example, when a battery short circuit fault occurs, it is determined that the fault category to which the battery short circuit fault belongs includes battery. Therefore, based on the pre-established notation mechanism, the fault severity value corresponding to the battery is added N. N includes 1, and other values ​​can also be set as required, which is not limited in this embodiment of the present invention.

[0092] In the embodiment of the present invention, the preset condition includes that the highest fault severity value is greater than or equal to a preset threshold. Specifically, step 102 may include:

[0093] Step 1021: Obtain the fault category with the highest fault severity value from the slave device.

[0094] In an embodiment of the present invention, for example, the fault categories in the slave device include battery, communication, multimedia, performance and reliability, where the fault severity value of the battery is 300, the fault severity value of the communication is 100, the fault severity value of the multimedia is 150, the fault severity value of the performance is 250, and the fault severity value of the reliability is 200. Since the fault severity value of the battery is the highest, the fault category with the highest fault severity value obtained from the slave device includes the battery.

[0095] It should be noted that the higher the fault severity value, the higher the level of the fault event type. Therefore, it is necessary to execute step 1021 to obtain the fault category with the highest fault severity value from the device in order to detect the fault category of the fault event level, avoiding the problem of detecting all fault categories and causing detection effect rate problems, thereby improving detection efficiency.

[0096] Step 1022 , determine whether the highest fault severity value is greater than or equal to a preset threshold value. If so, execute step 1023 ; if not, continue to execute step 1021 .

[0097] In an embodiment of the present invention, if it is determined that the highest fault severity value is greater than or equal to a preset threshold, it indicates that the fault category corresponding to the fault severity value is a fault category that meets the preset conditions; if it is determined that the highest fault severity value is less than the preset threshold, it indicates that the fault category corresponding to the fault severity value is not a fault category that meets the preset conditions, and it is necessary to continue waiting for the slave device to perform N-adding processing on the fault severity value corresponding to the fault category according to a pre-established dotting mechanism, until it is determined that the highest fault severity value is greater than or equal to the preset threshold, and then continue to execute step 102 to obtain a fault category that meets the preset conditions from the slave device.

[0098] It should be noted that the preset threshold value can be set as needed and is not limited in the embodiment of the present invention. For example, the preset threshold value includes 300. Since the battery failure degree value obtained above is 300, that is, the battery failure degree value is equal to the preset threshold value, the subsequent step 1023 can be continued.

[0099] Step 1023: Determine the fault category with the highest fault severity value as the fault category that meets the preset conditions.

[0100] In the embodiment of the present invention, the slave device records the fault severity value for each fault category so that, in subsequent steps, the master device only detects fault categories that meet the preset conditions. This avoids the problem of testing each fault detection item one by one, which would result in a high fault detection trigger frequency and a large number of invalid detections, thereby improving the efficiency of fault detection. It should be noted that the above preset conditions are for illustration only. In addition, other preset conditions can be set as needed, and the embodiment of the present invention does not limit this.

[0101] Step 104: Generate a corresponding fault event according to the fault type. The fault event includes multiple detection items.

[0102] In the embodiment of the present invention, for example, Figure 4 As shown, in Figure 4 In the embodiment, the main device can generate different types of fault events according to different fault categories. Taking the fault category including battery as an example, the corresponding battery type fault event is generated according to the battery, wherein the battery type fault event includes corresponding multiple detection items, and the multiple detection items include battery capacity detection items and battery short circuit detection items. Figure 4 For illustration purposes only, battery failure events may also include other detection items. In addition, detection items corresponding to other types of failure events may be set as needed, and the embodiments of the present invention do not limit this.

[0103] In the embodiment of the present invention, after step 104, the following steps are further included:

[0104] Step 105: Reduce the fault severity value corresponding to the fault type to a set severity value.

[0105] In the embodiment of the present invention, the set severity value can be set as needed, and the embodiment of the present invention is not limited thereto. For example, if the set severity value includes 0, that is, after a corresponding fault event is generated by the battery, the battery's fault severity value is reduced to 0. In addition, the battery's fault severity value can also be reduced by a certain ratio. For example, if the set severity value includes half of the fault severity value, the battery's fault severity value is reduced to half of the initial fault severity value. For example, if the initial fault severity value of the battery is 300, the battery's fault severity value is reduced to 150.

[0106] Step 106 : Based on the multiple detection items, detect whether the slave device has faults corresponding to the multiple detection items. If it is detected that the slave device has a fault corresponding to any detection item, execute step 108 ; otherwise, the process ends.

[0107] In an embodiment of the present invention, when the master device 110 generates a fault event, it can automatically initiate detection related to the fault event. For example, for a battery fault event, a battery health detection is initiated, wherein multiple detection items include: battery capacity, battery short circuit, etc. Based on the multiple detection items, it is detected whether the slave device has a battery capacity fault, or a fault corresponding to the detection item such as a battery short circuit fault.

[0108] In the embodiment of the present invention, as an optional solution, step 106 may further include: detecting corresponding detection frequencies with multiple detection items, and detecting whether the slave device has faults corresponding to the multiple detection items.

[0109] Specifically, by setting the detection frequency corresponding to each detection item, taking the detection items including battery capacity and battery short circuit as an example, by setting the detection frequency corresponding to battery capacity to 24h / time, and the detection frequency corresponding to battery short circuit to 12h / time, the master device can detect whether the slave device has faults corresponding to multiple detection items according to the detection frequency corresponding to each detection item. That is to say, the slave device is detected once every 12 hours to see if there is a battery short circuit fault, and once every 24 hours to see if there is a battery capacity fault.

[0110] Step 108: Prompt information is provided to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0111] In an embodiment of the present invention, each detection item has corresponding prompt information. If multiple faults corresponding to the detection items are detected in the slave device, multiple prompt information will be generated. For example, if the detection items include battery capacity and battery short circuit, if the slave device detects battery capacity and battery short circuit, prompt information corresponding to each detection item will be generated respectively, and the prompt information will be provided to the user to prompt the user to eliminate the fault corresponding to the detection item. The provision method may include: display, playback or vibration. For example, Figure 5As shown in a, the provision method includes display, the master device includes a mobile phone, and the slave device includes a headset. For example, the master device displays prompt information to the user, wherein the prompt information may include text information, for example, the text information is "XX model headset, there is a battery capacity failure", and the text information is displayed to prompt the user to eliminate the fault corresponding to the detection item. For example, Figure 5 As shown in section b, taking the provision method including playback as an example, a prompt message is played to the user, where the prompt message may include audio information, such as the audio information "XX model headphones have a battery capacity fault." By displaying the prompt message, the user is prompted to correct the fault corresponding to the detection item. Furthermore, the provision method may include any combination of display, playback, or vibration. In addition, other provision methods may also be included, which are not limited in this embodiment of the present invention.

[0112] Optionally, step 108 may further include: sending fault information corresponding to the fault to the slave device, so that the slave device generates prompt information according to the fault information, and provides the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0113] In the embodiment of the present invention, for example, when the fault is a battery capacity fault, the master device sends fault information corresponding to the battery capacity fault to the slave device, so that the slave device generates prompt information based on the fault information and provides the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item. Figure 6a As shown, taking the slave device including headphones as an example, the provided method may include playback, and the prompt information may include sound information, and the sound information is "XX model headphones, there is a battery capacity failure", that is, the user is reminded by playing voice through the headphones.

[0114] Further, as an optional solution, for example, Figure 6b As shown, the master device includes a mobile phone, and the provision method of the master device includes display. The slave device includes headphones, and the provision method of the slave device includes playback. Specifically, the master device displays prompt information to the user, wherein the prompt information may include text information, for example, the text information is "XX headphones battery is aging, you are advised to go to a service outlet to replace the battery", and the text information is displayed to prompt the user to eliminate the fault corresponding to the detection item. At the same time, the slave device plays prompt information to the user, wherein the prompt information may include sound information, and the sound information is "XX headphones battery is aging, you are advised to go to a service outlet to replace the battery", that is, the user is reminded by playing voice through the headphones. In other words, the master device and the slave device can provide prompt information to the user at the same time. In addition, any one device or any combination of devices can also be selected to provide prompt information to the user, and the embodiments of the present invention are not limited to this.

[0115] In the embodiment of the present invention, after step 108, the following steps are further included:

[0116] Step 110: Receive feedback information from the user, where the feedback information includes operation information corresponding to the ignore operation.

[0117] In the embodiment of the present invention, Figure 7 As shown, for example, after the user clicks the "Ignore" operation S103, the main device can receive the user's feedback information, wherein the feedback information includes the operation information corresponding to the ignore operation. The operation information corresponding to the ignore operation is used to indicate the log record information generated by the main device in response to the user's ignore operation.

[0118] Step 112: Count the number of ignore operations according to the operation information corresponding to the ignore operation.

[0119] In the embodiment of the present invention, each time operation information corresponding to an ignore operation is obtained, the number of ignore operations is incremented by 1, and the number of ignore operations is counted.

[0120] Step 114: If it is determined that the number of ignored operations is greater than or equal to the preset number, remove the detection item from the fault event.

[0121] In an embodiment of the present invention, if it is determined that the number of times the operation is ignored is greater than or equal to a preset number, it indicates that the user is not interested in the fault detection behavior or the fault does not need to be repaired. Therefore, the detection item can be removed from the fault event, so that when the fault event is generated again next time, since the fault event does not include the detection item, in the subsequent fault detection process, fault detection will no longer be performed through the detection item, thereby improving the user experience.

[0122] In addition, the detection frequencies of multiple detection items corresponding to the fault event may be adjusted according to the feedback information received from the users.

[0123] In an embodiment of the present invention, for example, taking the detection items including battery capacity and battery short circuit as an example, the detection frequency corresponding to the battery short circuit is set to 12h / time. When the number of times the user ignores the prompt information for the battery short circuit is greater than or equal to the preset number of times, the detection frequency of the battery short circuit is reduced, for example, the detection frequency corresponding to the battery short circuit is reduced to 48h / time.

[0124] In an embodiment of the present invention, through the fault detection method provided above, after the master device and the slave device establish a connection, a fault category that meets the preset conditions can be obtained from the slave device, and a corresponding fault event is generated according to the fault category. The fault event includes multiple detection items. Based on the multiple detection items, it is detected whether there is a fault in the slave device. If a fault is detected in the slave device, prompt information is provided to the user to prompt the user to troubleshoot the fault. Fault detection and fault reminder of the master and slave devices can be realized, thereby reducing the maintenance cost of the slave device.

[0125] Figure 8 A flowchart of another fault detection method provided by an embodiment of the present invention is shown in FIG. Figure 8 As shown, the method is applied to a slave device, and the method includes:

[0126] Step 202: Determine multiple fault categories based on the acquired device software information and device hardware information.

[0127] In an embodiment of the present invention, device software information is used to indicate the software programs included in the slave device system. For example, the device software information includes multiple information such as performance, power consumption, reliability, or application, and the slave device 120 determines each type of information as a fault category. Device hardware information is used to indicate the hardware facilities included in the slave device system. For example, the device hardware information includes multiple information such as communication, audio, camera, battery, charging, Wi-Fi, Global Positioning System (GPS), Near Field Communication (NFC), Bluetooth, infrared, storage, motor button, or fingerprint, and the slave device 120 determines each type of information as a fault category.

[0128] Step 204: When a fault occurs, determine the fault category to which the fault belongs, and perform N processing on the fault severity value corresponding to the fault category according to the pre-established marking mechanism.

[0129] In the embodiment of the present invention, for example, a battery short circuit occurs. When the battery short circuit occurs, it is determined that the fault category of the battery short circuit fault includes battery. Therefore, according to a pre-established marking mechanism, the fault severity value corresponding to the battery is incremented by N. N includes 1, and other values ​​can be set as needed, which is not limited in the embodiment of the present invention.

[0130] Step 206: After establishing a connection with the master device, a fault category that meets preset conditions is sent to the master device. The preset conditions include that the highest fault severity value is greater than or equal to a preset threshold value, so that the master device can generate a corresponding fault event according to the fault category. The fault event includes multiple detection items. Based on the multiple detection items, it is detected whether the slave device has faults corresponding to the multiple detection items. If it is detected that the slave device has a fault corresponding to any detection item, a prompt message is provided to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0131] In the embodiment of the present invention, the execution process of the master device may refer to steps 102 to 108 of the above embodiment.

[0132] Step 208: Receive fault information corresponding to the fault sent by the master device, generate prompt information according to the fault information, and provide the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0133] In the embodiment of the present invention, for example, when the fault is a battery capacity fault, the master device sends fault information corresponding to the battery capacity fault to the slave device, so that the slave device generates prompt information based on the fault information and provides the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item. Figure 6a As shown, taking the slave device including headphones as an example, the provided method may include playback, and the prompt information may include sound information, and the sound information is "XX model headphones, there is a battery capacity failure", that is, the user is reminded by playing voice through the headphones.

[0134] In an embodiment of the present invention, after a master device establishes a connection with a slave device, a fault category that meets preset conditions is obtained from the slave device, and a corresponding fault event is generated based on the fault category. The fault event includes multiple detection items. Based on the multiple detection items, it is detected whether there is a fault in the slave device. If a fault is detected in the slave device, prompt information is provided to the user to prompt the user to troubleshoot the fault. Fault detection and fault reminder of the master and slave devices can be realized, thereby reducing the maintenance cost of the slave device.

[0135] Figure 9 A flowchart of another fault detection method provided by an embodiment of the present invention is shown in FIG. Figure 9 As shown, the method includes:

[0136] Step 302: The slave device determines multiple fault categories based on the acquired device software information and device hardware information.

[0137] In the embodiment of the present invention, the execution process of this step can refer to step 202 of the above embodiment.

[0138] Step 304: When a fault occurs, the slave device determines the fault category to which the fault belongs, and adds N to the fault severity value corresponding to the fault category according to a pre-established marking mechanism.

[0139] In the embodiment of the present invention, the execution process of this step can refer to step 204 of the above embodiment.

[0140] Step 306: After establishing a connection with the slave device, the master device obtains a fault type that meets a preset condition from the slave device.

[0141] In the embodiment of the present invention, the execution process of this step can refer to step 102 of the above embodiment.

[0142] In the embodiment of the present invention, the preset condition includes that the highest fault severity value is greater than or equal to a preset threshold. Specifically, step 306 may include:

[0143] Step 3061: Obtain the fault category with the highest fault severity value from the slave device.

[0144] Step 3062: Determine whether the fault severity value is greater than or equal to a preset threshold. If so, execute step 3063; if not, continue to execute step 3061.

[0145] Step 3063: Determine the fault category with the highest fault severity value as the fault category that meets the preset conditions.

[0146] Step 308: The master device generates a corresponding fault event according to the fault type. The fault event includes multiple detection items.

[0147] Step 310: The master device reduces the fault severity value corresponding to the fault type to a set severity value.

[0148] In the embodiment of the present invention, the execution process of this step can refer to step 105 of the above embodiment.

[0149] Step 312: The master device detects, based on the multiple detection items, whether the slave device has faults corresponding to the multiple detection items.

[0150] In the embodiment of the present invention, the execution process of this step can refer to step 106 of the above embodiment.

[0151] Step 314: If the master device detects that a fault corresponding to any detection item exists in the slave device, a prompt message is provided to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0152] In the embodiment of the present invention, the execution process of this step can refer to step 108 of the above embodiment.

[0153] Optionally, step 314 may further include:

[0154] In step 314', if the master device detects a fault in the slave device, it sends fault information corresponding to the fault to the slave device, so that the slave device generates prompt information based on the fault information and provides prompt information to the user to prompt the user to eliminate the fault corresponding to the detected item, and then continues to execute step 316'.

[0155] Step 316 ′: the slave device receives the fault information corresponding to the fault sent by the master device, generates prompt information according to the fault information, and provides the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0156] In the embodiment of the present invention, the execution process of this step can refer to step 208 of the above embodiment.

[0157] It should be noted that the master device and the slave device can provide prompt information to the user at the same time, and any one device can be selected to provide prompt information to the user, which is not limited in this embodiment of the present invention.

[0158] In the embodiment of the present invention, after step 314, the following steps are further included:

[0159] Step 316: The master device receives feedback information from the user, where the feedback information includes operation information corresponding to the ignore operation.

[0160] In the embodiment of the present invention, the execution process of this step can refer to step 110 of the above embodiment.

[0161] Step 318: Count the number of ignore operations according to the operation information corresponding to the ignore operation.

[0162] In the embodiment of the present invention, the execution process of this step can refer to step 112 of the above embodiment.

[0163] Step 320: If it is determined that the number of ignored operations is greater than or equal to the preset number, remove the detection item from the fault event.

[0164] In the embodiment of the present invention, the execution process of this step can refer to step 114 of the above embodiment.

[0165] In an embodiment of the present invention, after a master device establishes a connection with a slave device, a fault category that meets preset conditions is obtained from the slave device, and a corresponding fault event is generated based on the fault category. The fault event includes multiple detection items. Based on the multiple detection items, it is detected whether there is a fault in the slave device. If a fault is detected in the slave device, prompt information is provided to the user to prompt the user to troubleshoot the fault. Fault detection and fault reminder of the master and slave devices can be realized, thereby reducing the maintenance cost of the slave device.

[0166] The following example illustrates the above fault detection method, taking a mobile phone (master device) performing fault detection on a Bluetooth headset (slave device) as an example.

[0167] The first step is to build fault categories such as battery, communication, multimedia, and reliability on the Bluetooth headset system. The Bluetooth headset system will add 1 to the fault severity value corresponding to the fault category of the fault according to the pre-established marking mechanism.

[0168] Step 2: After the phone establishes a connection with the Bluetooth headset, it retrieves the fault category with the highest severity value from the Bluetooth headset. For example, if the battery category has the highest severity value, a battery failure event is generated. Simultaneously, the phone resets the battery severity value of the headset to zero. The next time the phone connects to the Bluetooth headset, it retrieves the refreshed fault category with the highest severity value.

[0169] In the third step, the phone generates a corresponding fault event based on the fault type and performs the corresponding test items. For example, if the generated fault event includes a battery fault event, the phone will initiate a Bluetooth battery health test, including battery capacity test and battery short circuit test.

[0170] Step 4: If the phone detects a battery capacity failure, it will simultaneously notify the user on both the phone and the headset. This notification can be through a notification or pop-up window on the phone, while the headset can play a voice message. Furthermore, to enhance the user experience, the voice message can be played after the user puts on the headset to prevent them from missing the notification.

[0171] Step 5: The user “ignores” the prompt information, indicating that the user may not care about the reminder item. When the number of “ignore” operations exceeds a certain threshold, the detection item is removed from the detection items corresponding to the fault event type.

[0172] In this embodiment of the present invention, a mobile phone automatically detects and alerts Bluetooth headset faults in a highly energy-efficient manner. The phone only needs to perform lightweight detection based on the severity of the Bluetooth headset fault. It can also dynamically adjust detection items based on user feedback regarding the alert. This supports fault detection and alerts for both master and slave devices, thereby reducing Bluetooth headset maintenance costs and improving the user experience. This achieves higher energy efficiency, filters out many invalid detections, and adaptively adjusts detection and alert items to alert users to the faults they are most concerned about.

[0173] Figure 10 FIG is a schematic block diagram of a master device 110 provided in one embodiment of the present invention. It should be understood that the master device 110 is capable of executing Figure 3 To avoid repetition, the various steps in the fault detection method are not described in detail here. Figure 10 As shown, the main device 110 includes: a processing unit 401 and an interaction unit 402.

[0174] The processing unit 401 is used to establish a connection with the slave device and obtain a fault category that meets preset conditions from the slave device; generate a corresponding fault event based on the fault category, and the fault event includes multiple detection items; based on the multiple detection items, detect whether the slave device has faults corresponding to multiple detection items.

[0175] The interaction unit 402 is configured to provide prompt information to the user if it is detected that the slave device has a fault corresponding to any of the detection items, so as to prompt the user to eliminate the fault corresponding to the detection item.

[0176] In an embodiment of the present invention, the processing unit 401 is further configured to send fault information corresponding to the fault to the slave device, so that the slave device generates the prompt information according to the fault information, and provides the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0177] In an embodiment of the present invention, the preset conditions include the highest fault severity value being greater than or equal to a preset threshold value; the processing unit 401 is further used to obtain the fault category with the highest fault severity value from the slave device; determine whether the highest fault severity value is greater than or equal to the preset threshold value; if it is determined that the fault severity value is greater than or equal to the preset threshold value, determine the fault category with the highest fault severity value as the fault category that meets the preset conditions.

[0178] In the embodiment of the present invention, the processing unit 401 is further configured to reduce the fault severity value corresponding to the fault type to a set severity value.

[0179] In the embodiment of the present invention, the interaction unit 402 is further configured to receive feedback information from the user, where the feedback information includes operation information corresponding to the ignore operation.

[0180] The processing unit 401 is further configured to count the number of the ignore operations according to the operation information corresponding to the ignore operations; if it is determined that the number of the ignore operations is greater than or equal to a preset number, remove the detection item from the fault event.

[0181] It should be understood that the master device 110 herein is embodied as a functional unit. The term "unit" herein can be implemented in software and / or hardware, without specific limitation. For example, a "unit" can be a software program, a hardware circuit, or a combination thereof that implements the aforementioned functionality. The hardware circuitry may include an application-specific integrated circuit (ASIC), electronic circuitry, a processor (e.g., a shared processor, a dedicated processor, or a group processor) and memory for executing one or more software or firmware programs, combined logic circuitry, and / or other suitable components that support the described functionality.

[0182] Therefore, the various exemplary units described in the embodiments of the present invention can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0183] Figure 11 FIG is a schematic block diagram of a slave device 120 provided in one embodiment of the present invention. It should be understood that the slave device 120 is capable of executing Figure 4 To avoid repetition, the various steps in the fault detection method are not described in detail here. Figure 11 As shown, the slave device 120 includes: a processing unit 501 and an interaction unit 502 .

[0184] The processing unit 501 is used to determine multiple fault categories based on the acquired device software information and device hardware information; when a fault occurs, determine the fault category to which the fault belongs, and add N to the fault severity value corresponding to the fault category according to a pre-established dotting mechanism; after establishing a connection with the main device, send the fault category that meets the preset conditions to the main device, the preset conditions include the highest fault severity value being greater than or equal to a preset threshold, so that the main device can generate a corresponding fault event according to the fault category, the fault event includes multiple detection items, and based on the multiple detection items, detect whether the slave device has multiple faults corresponding to the detection items. If it is detected that the slave device has a fault corresponding to any of the detection items, provide a prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0185] In the embodiment of the present invention, the interaction unit 502 is configured to receive fault information corresponding to the fault sent by the master device, generate prompt information according to the fault information, and provide the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

[0186] It should be understood that the slave device 120 herein is embodied in the form of a functional unit. The term "unit" herein may be implemented in software and / or hardware form, without specific limitation. For example, a "unit" may be a software program, a hardware circuit, or a combination thereof that implements the aforementioned functionality. The hardware circuit may include an application-specific integrated circuit (ASIC), an electronic circuit, a processor (e.g., a shared processor, a dedicated processor, or a group processor) and memory for executing one or more software or firmware programs, merged logic circuits, and / or other suitable components that support the described functionality.

[0187] Therefore, the various exemplary units described in the embodiments of the present invention can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0188] An embodiment of the present invention further provides an electronic device, which includes a master device 110 or a slave device 120. The device can be used to execute the functions / steps in the above method embodiments.

[0189] Figure 12 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention is shown in FIG. Figure 12 As shown, the electronic device 900 includes a processor 910 and a transceiver 920. Optionally, the electronic device 900 may further include a memory 930. The processor 910, the transceiver 920, and the memory 930 may communicate with each other via internal connection paths to transmit control and / or data signals. The memory 930 is used to store computer programs, and the processor 910 is used to call and execute the computer programs from the memory 930.

[0190] Optionally, the electronic device 900 may further include an antenna 940 for transmitting the wireless signal output by the transceiver 920 .

[0191] The processor 910 and the memory 930 can be combined into a processing device, or more commonly, they are independent components. The processor 910 is used to execute the program code stored in the memory 930 to implement the above functions. In specific implementations, the memory 930 can also be integrated into the processor 910, or independent of the processor 910. The processor 910 can be combined with the memory 930 to form a processing device. Figure 10 The processor 910 corresponds to the processing unit 401 in the master device 110. Figure 11 Corresponding to the processing unit 501 in the slave device 120.

[0192] In addition, to further improve the functionality of the electronic device 900, the electronic device 900 may further include one or more of an input unit 960, a display unit 970, an audio circuit 980, a camera 990, and a sensor 901. The audio circuit may further include a speaker 982, a microphone 984, etc. The display unit 970 may include a display screen.

[0193] Optionally, the electronic device 900 may further include a power supply 950 for providing power to various devices or circuits in the terminal device.

[0194] It should be understood that Figure 12 The electronic device 900 shown is capable of Figure 3 、 Figure 8 and Figure 9 The various processes of the method embodiment shown. The operations and / or functions of the various units in the electronic device 900 are respectively for implementing the corresponding processes in the above method embodiment. For details, please refer to the description of the above method embodiment. To avoid repetition, detailed description is appropriately omitted here.

[0195] It should be understood that Figure 12 The processor 910 in the electronic device 900 shown may be a system on a chip (SOC). The processor 910 may include a central processing unit (CPU) and may further include other types of processors. The CPU may be referred to as a main CPU. The various processors work together to implement the preceding method flow, and each processor may selectively execute a portion of a software driver.

[0196] In summary, the various processors or processing units within the processor 910 can work together to implement the previous method flow, and the corresponding software programs of the various processors or processing units can be stored in the memory 930.

[0197] The present invention also provides a computer-readable storage medium having instructions stored therein. When the instructions are executed on a computer, the computer is caused to execute the above-mentioned Figure 3 、 Figure 8 and Figure 9 The various steps in the fault detection method shown.

[0198] In each of the above embodiments, the processor 910 involved may include, for example, a central processing unit (CPU), a microprocessor, a microcontroller, or a digital signal processor, and may also include a GPU, an NPU, and an ISP. The processor may also include necessary hardware accelerators or logic processing hardware circuits, such as application-specific integrated circuits (ASICs), or one or more integrated circuits for controlling the execution of the program of the technical solution of the present invention. In addition, the processor may have the function of operating one or more software programs, which may be stored in a memory.

[0199] The memory may be a read-only memory (ROM), other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0200] In the embodiment of the present invention, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent the existence of A alone, the existence of A and B at the same time, and the existence of B alone. Among them, A and B can be singular or plural. The character " / " generally indicates that the previous and subsequent associated objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can be represented by: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0201] Those skilled in the art will appreciate that the various units and algorithm steps described in the embodiments disclosed herein can be implemented using a combination of electronic hardware, computer software, and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0202] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0203] In the several embodiments provided by the present invention, if any function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the portion that contributes to the prior art, or the portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes various media that can store program code, such as a USB flash drive, a mobile hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0204] The above description is merely a specific embodiment of the present invention. Any modifications or substitutions that may be readily conceived by a person skilled in the art within the technical scope disclosed herein are intended to be encompassed within the scope of protection of the present invention. The scope of protection of the present invention shall be determined by the scope of protection of the claims.

Claims

1. A fault detection method, characterized in that: The method is applied to a master device, and includes: After establishing a connection with a slave device, obtaining a fault category that meets a preset condition from the slave device; the preset condition includes a maximum fault severity value being greater than or equal to a preset threshold; the fault severity value corresponds to the fault category, and is a value that the slave device performs N-adding processing according to a pre-established dotting mechanism when a fault corresponding to the fault category occurs; Generate a corresponding fault event according to the fault category, wherein the fault event includes multiple detection items; detecting, according to the plurality of detection items, whether the slave device has faults corresponding to the plurality of detection items; If it is detected that the slave device has a fault corresponding to any of the detection items, prompt information is provided to the user to prompt the user to eliminate the fault corresponding to the detection item.

2. The method according to claim 1, characterized in that After detecting that the slave device has a fault corresponding to any of the detection items, the method further includes: Fault information corresponding to the fault is sent to the slave device, so that the slave device generates the prompt information according to the fault information, and provides the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

3. The method according to claim 1, characterized in that Obtaining a fault category that meets a preset condition from the slave device includes: Obtaining a fault category with the highest fault severity value from the slave device; Determine whether the highest fault severity value is greater than or equal to a preset threshold; If it is determined that the fault severity value is greater than or equal to the preset threshold, the fault category with the highest fault severity value is determined as the fault category that meets the preset condition.

4. The method according to claim 1, wherein After generating a corresponding fault event according to the fault category, wherein the fault event includes multiple detection items, the method further includes: Reduce the fault severity value corresponding to the fault category to a set severity value.

5. The method according to claim 1 or 2, characterized in that After providing prompt information to the user to prompt the user to troubleshoot the fault corresponding to the detection item, the method further includes: receiving feedback information from the user, wherein the feedback information includes operation information corresponding to the ignore operation; Counting the number of times the ignore operation is performed according to the operation information corresponding to the ignore operation; If it is determined that the number of the ignore operations is greater than or equal to the preset number, the detection item is removed from the fault event.

6. A fault detection method, characterized in that: The method is applied to a slave device, and includes: Determine multiple fault categories based on the acquired device software and hardware information; When a fault occurs, the fault category to which the fault belongs is determined, and the fault severity value corresponding to the fault category is incremented by N according to a pre-established marking mechanism; After establishing a connection with the master device, a fault category that meets preset conditions is sent to the master device. The preset conditions include the highest fault severity value being greater than or equal to a preset threshold value, so that the master device can generate a corresponding fault event based on the fault category. The fault event includes multiple detection items. Based on the multiple detection items, it is detected whether the slave device has faults corresponding to multiple detection items. If it is detected that the slave device has a fault corresponding to any of the detection items, a prompt message is provided to the user to prompt the user to eliminate the fault corresponding to the detection item.

7. The method according to claim 6, characterized in that The method further comprises: Receive fault information corresponding to the fault sent by the master device, generate prompt information according to the fault information, and provide the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

8. A master device, characterized in that: include: Display screen; one or more processors; Memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions that, when executed by the device, cause the device to perform the following steps: After establishing a connection with a slave device, obtaining a fault category that meets a preset condition from the slave device; the preset condition includes a maximum fault severity value being greater than or equal to a preset threshold; the fault severity value corresponds to the fault category, and is a value that the slave device performs N-adding processing according to a pre-established dotting mechanism when a fault corresponding to the fault category occurs; Generate a corresponding fault event according to the fault category, wherein the fault event includes multiple detection items; detecting, according to the plurality of detection items, whether the slave device has faults corresponding to the plurality of detection items; If it is detected that the slave device has a fault corresponding to any of the detection items, prompt information is provided to the user to prompt the user to eliminate the fault corresponding to the detection item.

9. The device according to claim 8, characterized in that When the instruction is executed by the device, the device is caused to perform the following steps: Fault information corresponding to the fault is sent to the slave device, so that the slave device generates the prompt information according to the fault information, and provides the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

10. The device according to claim 8, characterized in that When the instruction is executed by the device, the device is caused to perform the following steps: Obtaining a fault category that meets a preset condition from the slave device includes: Obtaining a fault category with the highest fault severity value from the slave device; Determine whether the highest fault severity value is greater than or equal to a preset threshold; If it is determined that the fault severity value is greater than or equal to the preset threshold, the fault category with the highest fault severity value is determined as the fault category that meets the preset condition.

11. The device according to claim 8, characterized in that When the instruction is executed by the device, the device is caused to perform the following steps: Reduce the fault severity value corresponding to the fault category to a set severity value.

12. The device according to claim 8 or 9, characterized in that When the instruction is executed by the device, the device is caused to perform the following steps: receiving feedback information from the user, wherein the feedback information includes operation information corresponding to the ignore operation; Counting the number of times the ignore operation is performed according to the operation information corresponding to the ignore operation; If it is determined that the number of the ignore operations is greater than or equal to the preset number, the detection item is removed from the fault event.

13. A slave device, characterized in that: include: Display screen; one or more processors; Memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions that, when executed by the device, cause the device to perform the following steps: Determine multiple fault categories based on the acquired device software and hardware information; When a fault occurs, the fault category to which the fault belongs is determined, and the fault severity value corresponding to the fault category is incremented by N according to a pre-established marking mechanism; After establishing a connection with the master device, a fault category that meets preset conditions is sent to the master device. The preset conditions include the highest fault severity value being greater than or equal to a preset threshold value, so that the master device can generate a corresponding fault event based on the fault category. The fault event includes multiple detection items. Based on the multiple detection items, it is detected whether the slave device has faults corresponding to multiple detection items. If it is detected that the slave device has a fault corresponding to any of the detection items, a prompt message is provided to the user to prompt the user to eliminate the fault corresponding to the detection item.

14. The device according to claim 13, characterized in that When the instruction is executed by the device, the device is caused to perform the following steps: Receive fault information corresponding to the fault sent by the master device, generate prompt information according to the fault information, and provide the prompt information to the user to prompt the user to eliminate the fault corresponding to the detection item.

15. A computer-readable storage medium, characterized in that The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the fault detection method according to any one of claims 1 to 5.

16. A computer-readable storage medium, characterized in that The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the fault detection method according to claim 6 or 7.

Images