Fault type determination method and device, storage medium and electronic device

Abstract

The application discloses a fault type determination method and device, a storage medium and an electronic device, relates to the technical field of smart home, and the fault type determination method comprises the following steps: obtaining reported data of a target device in a fault state; in the case that it is determined through the reported data that the target device is in a continuous fault, determining temperature data corresponding to the target device and a continuous duration of the continuous fault of the target device by identifying a fault code carried in the reported data; determining a target matching result of the temperature data and a preset temperature rule, and determining size information of the continuous duration and a preset continuous duration; and determining a fault type of the target device according to the target matching result and the size information. By adopting the technical solution, the problem that the fault type of the device cannot be determined in advance based on the reported data corresponding to the target device in the related technology, thereby causing poor user experience, is solved.

Description

Technical Field

[0001] This application relates to the field of smart home technology, and more specifically, to a method and apparatus for identifying fault types, a storage medium, and an electronic device. Background Technology

[0002] In related technologies, refrigerator filter screens may experience malfunctions during use, such as abnormal cooling in the refrigerator compartment or freezer compartment. Repairing the filter screen only after the problem has been discovered by the user can negatively impact the user experience.

[0003] In the context of related technologies, the inability to determine the fault type of a device in advance based on the reported data of the target device, resulting in a poor user experience, existing technologies do not offer a good solution to the above problem. Summary of the Invention

[0004] This invention provides a method and apparatus for confirming fault types, a storage medium, and an electronic device, to at least solve the problem in related technologies where the fault type of a device cannot be determined in advance based on the reported data corresponding to the target device, resulting in a poor user experience.

[0005] According to one aspect of the present invention, a method for confirming a fault type includes: acquiring reported data of a target device in a fault state; if it is determined from the reported data that the target device is in a continuous fault, determining the temperature data corresponding to the target device and the duration of the continuous fault of the target device by identifying the fault code carried in the reported data; determining the target matching result of the temperature data and a preset temperature rule, and determining the magnitude information of the duration and the preset duration; and determining the fault type of the target device based on the target matching result and the magnitude information.

[0006] In an optional embodiment, determining the target matching result between the temperature data and a preset temperature rule includes: acquiring multiple temperature ranges corresponding to the preset temperature rule, wherein the multiple temperature ranges include at least one of the following: a first temperature range corresponding to a refrigeration sensor, and a second temperature range corresponding to a freezing sensor; when the temperature data includes temperature data collected by multiple sensors, determining the first temperature corresponding to the refrigeration sensor and / or the second temperature corresponding to the freezing sensor; determining a first matching result between the first temperature and the first temperature range and determining a second matching result between the second temperature and the second temperature range; and determining the target matching result between the temperature data and the preset temperature rule based on the first matching result and / or the second matching result.

[0007] In an optional embodiment, determining the fault type of the target device based on the target matching result and the size information includes: determining the fault type of the target device as a temporary fault when the target matching result indicates that the temperature data meets the preset temperature rule and the size information indicates that the duration is less than the preset duration; and determining the fault type of the target device as a data reporting anomaly when the target matching result indicates that the temperature data meets the preset temperature rule and the size information indicates that the duration is greater than or equal to the preset duration.

[0008] In an optional embodiment, determining the fault type of the target device based on the target matching result and the size information further includes: determining the fault type of the target device as a data reporting anomaly when the target matching result indicates that the temperature data does not meet the preset temperature rule and the size information indicates that the duration is less than a preset duration; and determining the fault type of the target device as a device fault when the target matching result indicates that the temperature data does not meet the preset temperature rule and the size information indicates that the duration is greater than or equal to the preset duration.

[0009] In an optional embodiment, after determining that the fault type of the target device is a device fault, the method further includes: labeling the device fault; if the device fault is determined to be caused by an abnormal refrigeration sensor, determining that the refrigeration temperature of the target device is abnormal; if the device fault is determined to be caused by an abnormal freezing sensor, determining that the freezing temperature of the target device is abnormal.

[0010] In an optional embodiment, before determining that the target device is in a continuous fault through the reported data, the method further includes: determining whether the reported data contains alarm clearance information; if the reported data contains alarm clearance information, assuming that the target device corresponding to the reported data is operating normally; if the reported data does not contain alarm clearance information, continuously reporting device information corresponding to the target device based on a preset reporting frequency.

[0011] In an optional embodiment, after determining the fault type of the target device based on the target matching result and the size information, the method further includes: sending the fault type in a push message to the service outlet corresponding to the target device, and counting the number of times the target device reports the same fault type; if the number of times the target device reports the same fault type is greater than a preset threshold, sending a device replacement prompt to the bound object of the target device; if the number of times the target device reports the same fault type is less than or equal to the preset threshold, designating the target device as a key monitoring object.

[0012] According to another aspect of the present invention, a fault type confirmation device is also provided, comprising: an acquisition module for acquiring reported data of a target device in a fault state; a first determination module for determining, when the target device is determined to be in a continuous fault state by identifying a fault code carried in the reported data, the temperature data corresponding to the target device and the duration of the continuous fault state of the target device; a second determination module for determining the target matching result of the temperature data with a preset temperature rule, and determining the magnitude information of the duration and the preset duration; and a third determination module for determining the fault type of the target device based on the target matching result and the magnitude information.

[0013] According to another aspect of the present invention, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer program, wherein the computer program is configured to execute the above-described fault type confirmation method when running.

[0014] According to another aspect of the present invention, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the fault type confirmation method through the computer program.

[0015] This invention acquires reported data from a target device in a fault state. When the reported data indicates a persistent fault, the invention identifies the corresponding temperature data and the duration of the persistent fault by recognizing the fault code carried in the reported data. It then determines the target device's temperature data against a preset temperature rule and the magnitude of the duration's difference from the preset duration. Finally, it determines the fault type of the target device based on the matching result and the magnitude information. This technical solution solves the problem in related technologies where the fault type cannot be determined in advance based on the reported data, leading to a poor user experience. Furthermore, it enables the early detection of the target device's fault type through calculation, allowing for timely repair and maintenance, thus improving the user experience when using the target device (e.g., a smart refrigerator). Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a schematic diagram of the hardware environment for an optional fault type determination method according to an embodiment of this application;

[0019] Figure 2 This is a flowchart of an optional method for determining a fault type according to an embodiment of this application;

[0020] Figure 3 This is a structural block diagram of an optional fault type determination method according to an embodiment of this application;

[0021] Figure 4 This is a schematic diagram of an optional method for determining a fault type according to an embodiment of the present invention;

[0022] Figure 5 This is a flowchart of an optional fault type determination device according to an embodiment of the present invention. Detailed Implementation

[0023] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0024] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0025] According to one aspect of the embodiments of this application, a method for determining a fault type is provided. This method for determining the fault type is widely applicable to whole-house intelligent digital control application scenarios such as smart homes, smart home ecosystems, and intelligence house ecosystems. Optionally, in this embodiment, the above-mentioned method for determining the fault type can be applied to, for example... Figure 1 The hardware environment shown consists of multiple terminal devices 102 and a server 104. For example... Figure 1 As shown, server 104 is connected to multiple terminal devices 102 via a network and can be used to provide services (such as application services) to terminals or clients installed on terminals. A database can be set up on the server or independently of the server to provide data storage services for server 104. Cloud computing and / or edge computing services can be configured on the server or independently of the server to provide data processing services for server 104.

[0026] The aforementioned network may include, but is not limited to, at least one of the following: wired network, wireless network. The aforementioned wired network may include, but is not limited to, at least one of the following: wide area network, metropolitan area network, local area network. The aforementioned wireless network may include, but is not limited to, at least one of the following: Wi-Fi (Wireless Fidelity), Bluetooth. The terminal device 102 may not be limited to PC, mobile phone, tablet computer, smart air conditioner, smart range hood, smart refrigerator, smart oven, smart stove, smart washing machine, smart water heater, smart washing equipment, smart dishwasher, smart projector, smart TV, smart clothes rack, smart curtains, smart audio-visual equipment, smart socket, smart speaker, smart speaker box, smart fresh air equipment, smart kitchen and bathroom equipment, smart bathroom equipment, smart robot vacuum cleaner, smart window cleaning robot, smart mopping robot, smart air purifier, smart steam oven, smart microwave oven, smart water heater, smart air purifier, smart water dispenser, smart door lock, etc.

[0027] This embodiment provides a method for determining fault types, including but not limited to applications in cloud servers. Figure 2 This is a flowchart of a method for determining the fault type according to an embodiment of the present invention, the process including the following steps:

[0028] Step S202: Obtain the reported data of the target device in a fault state;

[0029] Step S204: If it is determined through the reported data that the target device is in a continuous fault, the temperature data corresponding to the target device and the duration of the continuous fault of the target device are determined by identifying the fault code carried in the reported data;

[0030] Step S206: Determine the target matching result between the temperature data and the preset temperature rule, and determine the magnitude information of the duration and the preset duration;

[0031] Step S208: Determine the fault type of the target device based on the target matching result and the size information.

[0032] This invention acquires reported data from a target device in a fault state. When the reported data indicates a persistent fault, the invention identifies the corresponding temperature data and the duration of the persistent fault by recognizing the fault code carried in the reported data. It then determines the target device's temperature data and the duration of the persistent fault by comparing the temperature data with a preset temperature rule, and the magnitude of the duration's difference from the preset duration. Finally, it determines the fault type of the target device based on the matching result and the magnitude information. This technical solution solves the problem in related technologies where the fault type of a device cannot be determined in advance based on the reported data, leading to a poor user experience. Furthermore, it enables the calculation to predict the fault type of the target device in advance and allows for timely repair, improving the user experience when using the target device (e.g., a refrigerator).

[0033] Optionally, when the target device is a smart refrigerator, the above fault codes may be E1 (freezerFanErr: freezer fan fault), E2 (coolingFanErr: cooling fan fault), E6 (refrigeratorFanErr: refrigerator fan fault), Ed (freezerDefrostingErr: freezer defrosting fault), or EC (refrigeratorDefrostingErr: refrigerator defrosting fault).

[0034] Optionally, performing step S206 includes: determining the target matching result between the temperature data and a preset temperature rule, including: acquiring multiple temperature ranges corresponding to the preset temperature rule, wherein the multiple temperature ranges include at least one of the following: a first temperature range corresponding to a refrigeration sensor, a second temperature range corresponding to a freezing sensor; when the temperature data includes temperature data collected by multiple sensors, determining the first temperature corresponding to the refrigeration sensor and / or the second temperature corresponding to the freezing sensor; determining a first matching result between the first temperature and the first temperature range and determining a second matching result between the second temperature and the second temperature range; and determining the target matching result between the temperature data and the preset temperature rule based on the first matching result and / or the second matching result.

[0035] It is clear that, depending on the type of target device, the aforementioned temperature data may include temperature data collected by multiple sensors installed within the target device. Since different sensor types correspond to different temperature ranges for temperature judgment, it is necessary to compare the preset temperature ranges corresponding to different sensors with the temperature data reported in real-time by the target device to determine if the temperature data is abnormal. For example, when the target device is a smart refrigerator, the comparison results of the freezing and refrigeration sensors with their corresponding temperature ranges can be determined. If the real-time temperature value corresponding to the freezing sensor and / or refrigeration sensor is not within the corresponding temperature range, it indicates that the current temperature data is abnormal.

[0036] Optionally, step S208 above is performed: determining the fault type of the target device based on the target matching result and the size information, including: when the target matching result indicates that the temperature data meets the preset temperature rule and the size information indicates that the duration is less than the preset duration, determining the fault type of the target device as a temporary fault; when the target matching result indicates that the temperature data meets the preset temperature rule and the size information indicates that the duration is greater than or equal to the preset duration, determining the fault type of the target device as a data reporting anomaly.

[0037] It is understandable that equipment may experience abnormal error messages during use, or the equipment malfunction may not affect its operation within a certain timeframe. Therefore, preset temperature and preset duration can be used to determine the type of malfunction. By comprehensively analyzing the data from these abnormal error messages, the source of the malfunction in this type of equipment can be effectively identified.

[0038] In one alternative embodiment, taking a smart refrigerator as an example:

[0039] The preset normal operating temperature range for the refrigeration compartment sensor is 12℃~120℃, and the operating temperature range for the freezer compartment sensor is -10℃~50℃; the preset time range is 3 hours. If the refrigeration compartment sensor temperature exceeds 12℃~120℃ and reports a fault for less than 3 hours, or if the freezer compartment sensor temperature exceeds -10℃~50℃ and the duration is less than 3 hours, the fault type is determined to be a temporary fault.

[0040] If the sensor temperature in the refrigerated area is between 12℃ and 120℃ and the reported fault lasts for more than 3 hours, or if the sensor temperature in the freezer is between -10℃ and 50℃ and lasts for more than 3 hours, the fault type is determined to be abnormal data reporting.

[0041] Optionally, performing the above steps: determining the fault type of the target device based on the target matching result and the size information further includes: determining the fault type of the target device as a data reporting anomaly when the target matching result indicates that the temperature data does not meet the preset temperature rule and the size information indicates that the duration is less than the preset duration; and determining the fault type of the target device as a device fault when the target matching result indicates that the temperature data does not meet the preset temperature rule and the size information indicates that the duration is greater than or equal to the preset duration.

[0042] For example, if the preset normal operating temperature range for the refrigeration compartment sensor is 12℃~120℃, and the preset operating temperature range for the freezing compartment sensor is -10℃~50℃, with a preset time range of 3 hours, then if the refrigeration compartment sensor temperature is between 12℃ and 120℃ and the reported fault duration is less than 3 hours, or if the freezing compartment sensor temperature is between -10℃ and 50℃ and the reported fault duration is less than 3 hours, the fault type is determined to be data reporting anomaly. If the refrigeration compartment sensor temperature exceeds 12℃~120℃ and the reported fault duration is greater than 3 hours, or if the freezing compartment sensor temperature exceeds -10℃~50℃ and the reported fault duration is greater than 3 hours, the fault type is determined to be equipment failure.

[0043] In one example, after determining that the fault type of the target device is a device fault, the method further includes: labeling the device fault; if the device fault is determined to be caused by an abnormality in the refrigeration sensor, determining that the refrigeration temperature of the target device is abnormal; if the device fault is determined to be caused by an abnormality in the freezing sensor, determining that the freezing temperature of the target device is abnormal.

[0044] Optionally, after determining the cause of the above-mentioned equipment failure, the method may further include at least one of the following:

[0045] 1) If the equipment malfunction is determined to be caused by a faulty refrigeration sensor, restart the system corresponding to the refrigeration sensor;

[0046] 2) If the equipment malfunction is determined to be caused by a faulty refrigeration sensor, restart the system corresponding to the refrigeration sensor;

[0047] 3) If the equipment malfunction is determined to be due to an abnormal freezing sensor or a malfunctioning refrigeration sensor, restart the refrigerator's overall temperature control system.

[0048] Optionally, the above step S204 is performed: before determining that the target device is in a continuous fault through the reported data, the method further includes: determining whether the reported data contains alarm clearance information; if the reported data contains alarm clearance information, assuming that the target device corresponding to the reported data is operating normally; if the reported data does not contain alarm clearance information, continuously reporting the device information corresponding to the target device based on a preset reporting frequency.

[0049] In simple terms, in practical use, after a fault occurs, monitoring begins to check for alarm clearance information reports, and this monitoring continues for two hours. If alarm clearance information is reported within two hours, it is assumed that no target device is operating normally. If no alarm clearance information is reported within two hours, the fault information that occurred two hours ago is provided to the refrigeration industry. The information provided includes, but is not limited to: MAC address, machine code, model code, model description, fault code, fault description, and fault occurrence time.

[0050] Optionally, after performing step S208 above: determining the fault type of the target device based on the target matching result and the size information, the method further includes: sending the fault type in a push message to the service outlet corresponding to the target device, and counting the number of times the target device reports the same fault type; if the number of times the target device reports the same fault type is greater than a preset threshold, sending a device replacement prompt to the bound object of the target device; if the number of times the target device reports the same fault type is less than or equal to the preset threshold, designating the target device as a key monitoring object.

[0051] Optionally, after determining the fault type, the geographical location of the faulty device is obtained, and the fault information is pushed to nearby after-sales service outlets based on the geographical location of the faulty device.

[0052] The push methods include, but are not limited to: email, iHaier, WeChat, and SMS;

[0053] The push message includes at least one of the following: MAC address, machine code, model code, model description, fault code, fault description, fault occurrence time and fault conclusion, and relevant temperature data.

[0054] The push notification may include the device model, the date the malfunction occurred, the number of malfunctioning devices, and the type of malfunction of the malfunctioning devices.

[0055] Optionally, if the number of E faults in Type A equipment exceeds 5, the fault information will be pushed to the head of the electrical control module.

[0056] If the number of E-faults in Type A equipment exceeds 10, the fault information will be pushed to the head of the electrical control module and the project manager; if the number of E-faults in Type A equipment exceeds 15, the fault information will be pushed to the head of the electrical control module, the project manager, the micro-management leader, and the quality node.

[0057] Obviously, the embodiments described above are only some embodiments of the present invention, and not all embodiments. To better understand the above method for determining fault types, the process is described below with reference to embodiments, but this is not intended to limit the technical solutions of the embodiments of the present invention. Specifically:

[0058] Figure 3 This is a flowchart illustrating an optional method for determining a fault type according to an embodiment of this application, such as... Figure 3 As shown:

[0059] Step 1: Send a local fault code, which includes the fault type;

[0060] Step 2: Determine if any alarms have been cleared. If so, return to the logical starting point; otherwise, continue monitoring the fault.

[0061] It should be noted that the corresponding interface data 1 here includes: typeid, model code, model description, fault code, fault description, date, fault occurrence MAC (deduplicated), and fault occurrence count (not deduplicated);

[0062] Step 3: If the fault code reporting time is less than 2 hours, return to the previous logic unit. If the fault code reporting time is more than 2 hours, monitor the possible problems (refrigeration / freezing / variable temperature / refrigeration defrosting / freezing defrosting / variable temperature defrosting) corresponding to the specific fault code (E1 / E2 / E6 / Ed / Ec).

[0063] It should be noted that the corresponding interface data 2 here includes: MAC, device name, model code, model description, fault code, fault description, and fault occurrence time.

[0064] Step 4: Continuously monitor specific fault codes. If the specific fault code is reported for less than 10 hours, it is determined that the fault reporting has ended. If the specific fault code is reported for more than 10 hours, monitor the temperature range of the refrigeration or freezing sensor for 3 hours (freezing sensor temperature range -10℃~50℃, refrigeration sensor temperature range 12℃~120℃).

[0065] Step 5: If the temperature of the refrigeration sensor or the freezer sensor is abnormal for more than three hours, determine whether the machine's MAC address is unique and has not been repeatedly pushed within 7 days, and then push the message.

[0066] It should be noted that the corresponding interface data 3 here includes: MAC, device name, model code, model description, fault code, fault description, fault occurrence time, fault conclusion + 26 temperature data (data from 3 days before and after the fault push, fault data is not taken).

[0067] To better illustrate the point, the following examples are provided:

[0068] 1) After a fault occurs, the gateway begins to determine whether there is an alarm cancellation report, i.e., whether the alarm cancellation alarmCancel is reported.

[0069] If alarmCancel is reported: the judgment ends.

[0070] If alarmCancel is not reported: continue checking for 2 hours;

[0071] If alarmCancel is reported within 2 hours: the logical judgment ends;

[0072] If alarmCancel is not reported within 2 hours: Provide the information about the fault that occurred 2 hours ago to the refrigeration industry.

[0073] The data provided to the refrigerator industry includes, but is not limited to: MAC address, machine code, model code, model description, fault code, fault description, and fault occurrence time. The frequency of provision can be: statistical data for day T-1 is provided on day T. The data provision period can be: daily statistical data within a month.

[0074] For example, within a single day, a fault is reported at 14:54; a fault is reported at 14:55; the fault is resolved at 15:00; a fault is reported again at 15:01; a fault is reported again at 15:02; ... a fault is reported again; and the fault is resolved at 17:03. Through the above example, it is clear that the first round of judgment ends at 15:00, and a new round of judgment begins at 15:01; the fault is not resolved until 17:03, so the fault reported at 15:01 should be pushed; if another fault is reported after 17:03, the process starts again from the beginning.

[0075] 2) After condition 1) is met, continue to perform in-depth judgment of fault codes and temperature.

[0076] When the fault code in 1) is as follows, further judgment is required.

[0077] E1 (freezerFanErr: Freezer compartment fan malfunction);

[0078] E2 (coolingFanErr: Cooling fan malfunction);

[0079] E6 (refrigeratorFanErr: Refrigerator compartment fan malfunction);

[0080] Ed (freezerDefrostingErr: Freezer defrosting failure);

[0081] EC (refrigerator defrostingErr: refrigerator defrosting failure);

[0082] When 120℃ > refrigeration sensor temperature ≥ 12℃ or 50℃ > freezing sensor temperature ≥ -10℃: as long as either of the two temperatures is satisfied, and 3h <= duration.

[0083] If either of the above two conditions is not met (neither temperature is met; duration > 3 hours or total monitoring time > 10 hours), the process ends and proceeds to the next fault logic flow. For the same MAC address, only the first reported fault is monitored within 12 hours. If other faults are reported within 12 hours, no monitoring is performed. If both of the above conditions are met: after a duration of 3 hours or more, the fault is immediately pushed to after-sales service (according to the original fault self-feedback push content and logic limitations), and data is provided to the refrigeration industry: MAC address, machine code, model code, model description, fault code, fault description, fault occurrence time + fault conclusion, and relevant temperature data (data for 3 days before and after the MAC address of E1 / E2 / E6 / Ed / EC faults only, data is in "Local Data Information.xlsx" -- "Local Data", with a total of 26 relevant fields. This part of the temperature data is the data of the MAC address that meets the conditions for pushing to after-sales service, regardless of whether a work order is generated).

[0084] Figure 4 This is a schematic diagram of an optional fault type determination method according to an embodiment of this application, such as... Figure 4 As shown:

[0085] Step 1: After the trigger condition is met, the temperature monitoring cycle T begins;

[0086] Step 2: Start monitoring the temperature of the refrigerator and freezer sensors. Start timing when the refrigerator sensor temperature is greater than or equal to limit A or the freezer sensor temperature is greater than or equal to limit B.

[0087] Step 3: If the time exceeding the limit is ≥ t, and the push conditions are met (A: abnormal refrigeration temperature, B: abnormal freezing temperature), the judgment ends (if t exceeds cycle T, then cycle T is delayed until the end of this judgment) and "After-sales inquiry" and "Abnormal freezing / refrigeration temperature" are pushed; if the time exceeding the limit is < t, then monitoring continues until cycle T ends.

[0088] Optionally, the fault conclusions include, but are not limited to: if the fault is caused by a malfunction of the refrigeration sensor, it is marked as a refrigeration temperature malfunction; if the fault is caused by a malfunction of the freezer sensor, it is marked as a freezer temperature malfunction; if both the refrigeration and freezer sensors are malfunctioning, it is marked as both a refrigeration temperature malfunction and a freezer temperature malfunction.

[0089] Understandably, the interface method is provided every H-1 hours. Historical data is retained for the past month.

[0090] In summary, by combining the above methods with the reported data from the refrigerator's network device, utilizing the logical judgment of the set freezing-not-cooling algorithm, and the troubleshooting process of the R&D personnel for abnormal refrigerator problems, the reported data is processed to determine the cause of the corresponding equipment malfunction. Simultaneously, this data is pushed to product R&D personnel for further analysis of aspects requiring iterative optimization during product development, and can also provide guidance to after-sales on-site repair personnel.

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

[0092] This embodiment also provides a fault type determination device, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0093] Figure 5 This is a structural block diagram of an optional fault type determination device according to an embodiment of the present invention, the device comprising:

[0094] The acquisition module 40 is used to acquire the reported data of the target device in a fault state;

[0095] The first determining module 42 is used to determine the temperature data of the target device and the duration of the target device in the fault state by identifying the fault code carried in the reported data when it is determined through the reported data that the target device is in a continuous fault state.

[0096] The second determining module 44 is used to determine the target matching result between the temperature data and the preset temperature rule, and to determine the magnitude information of the duration and the preset duration;

[0097] The third determining module 46 is used to determine the fault type of the target device based on the target matching result and the size information.

[0098] This invention acquires reported data from a target device in a fault state. When the reported data indicates a persistent fault, the invention identifies the corresponding temperature data and the duration of the persistent fault by recognizing the fault code carried in the reported data. It then determines the target device's temperature data against a preset temperature rule and the magnitude of the duration's difference from the preset duration. Finally, it determines the fault type of the target device based on the matching result and the magnitude information. This technical solution solves the problem in related technologies where the fault type cannot be determined in advance based on the reported data, leading to a poor user experience. Furthermore, it enables the early detection of the target device's fault type through calculation, allowing for timely repair and maintenance, thus improving the user experience when using the target device (e.g., a smart refrigerator).

[0099] In an optional embodiment, the third determining module 46 is used to determine the fault type of the target device based on the target matching result and the size information. Determining the fault type of the target device based on the target matching result and the size information includes: determining the fault type of the target device as a temporary fault when the target matching result indicates that the temperature data meets the preset temperature rule and the size information indicates that the duration is less than a preset duration; and determining the fault type of the target device as a data reporting anomaly when the target matching result indicates that the temperature data meets the preset temperature rule and the size information indicates that the duration is greater than or equal to the preset duration.

[0100] It is understandable that equipment may experience abnormal error messages during use, or the equipment malfunction may not affect its operation within a certain timeframe. Therefore, preset temperature and preset duration can be used to determine the type of malfunction. By comprehensively analyzing the data from these abnormal error messages, the source of the malfunction in this type of equipment can be effectively identified.

[0101] In one alternative embodiment, taking a refrigerator as an example:

[0102] The preset normal operating temperature range for the refrigeration compartment sensor is 12℃~120℃, and the operating temperature range for the freezer compartment sensor is -10℃~50℃; the preset time range is 3 hours. If the refrigeration compartment sensor temperature exceeds 12℃~120℃ and reports a fault for less than 3 hours, or if the freezer compartment sensor temperature exceeds -10℃~50℃ and the duration is less than 3 hours, the fault type is determined to be a temporary fault.

[0103] If the sensor temperature in the refrigerated area is between 12℃ and 120℃ and the reported fault lasts for more than 3 hours, or if the sensor temperature in the freezer is between -10℃ and 50℃ and lasts for more than 3 hours, the fault type is determined to be abnormal data reporting.

[0104] Optionally, the third determining module 46 is further configured to determine the fault type of the target device as a data reporting anomaly when the target matching result indicates that the temperature data does not meet the preset temperature rule and the duration of the size information indication is less than the preset duration; and to determine the fault type of the target device as a device fault when the target matching result indicates that the temperature data does not meet the preset temperature rule and the duration of the size information indication is greater than or equal to the preset duration.

[0105] The preset normal operating temperature range for the refrigeration zone sensor is 12℃~120℃, and the operating temperature range for the freezer zone sensor is -10℃~50℃; the preset time range is 3 hours. If the refrigeration zone sensor reports a fault for less than 3 hours when the temperature is between 12℃ and 120℃, or if the freezer zone sensor reports a fault for less than 3 hours when the temperature is between -10℃ and 50℃, the fault type is determined to be data reporting anomaly.

[0106] If the sensor temperature in the cold storage area exceeds 12℃ to 120℃ and the reported fault lasts for more than 3 hours, or if the sensor temperature in the freezing area exceeds -10℃ to 50℃ and the reported fault lasts for more than 3 hours, the fault type is determined to be equipment fault.

[0107] After determining that the fault type of the target device is a device fault, the method further includes: labeling the device fault; if the device fault is determined to be caused by an abnormal refrigeration sensor, determining that the refrigeration temperature of the target device is abnormal; if the device fault is determined to be caused by an abnormal freezing sensor, determining that the freezing temperature of the target device is abnormal.

[0108] Optionally, after determining the cause of the above-mentioned equipment failure, the method may further include at least one of the following: if it is determined that the equipment failure is caused by an abnormality in the refrigeration sensor, restart the system corresponding to the refrigeration sensor; if it is determined that the equipment failure is caused by an abnormality in the freezing sensor, restart the system corresponding to the freezing sensor.

[0109] If the equipment malfunction is determined to be due to a faulty freezer sensor or a faulty refrigerator sensor, restart the refrigerator's overall temperature control system.

[0110] In an optional embodiment, the first determining module 42 is used to determine the temperature data of the target device and the duration of the target device in the fault state by identifying the fault code carried in the reported data when it is determined through the reported data that the target device is in a continuous fault state. Before determining that the target device is in a continuous fault state through the reported data, the method further includes: determining whether the reported data contains alarm clearance information; if the reported data contains alarm clearance information, defaulting to the target device corresponding to the reported data operating normally; if the reported data does not contain alarm clearance information, continuously reporting device information corresponding to the target device based on a preset reporting frequency.

[0111] After a fault occurs, monitoring begins to check for alarm clearance information reports, and this monitoring continues for two hours. If alarm clearance information is reported within two hours, it is assumed that no target device is operating normally. If no alarm clearance information is reported within two hours, the fault information that occurred two hours prior will be provided to the refrigeration industry. The information provided includes, but is not limited to: MAC address, machine code, model code, model description, fault code, fault description, and fault occurrence time.

[0112] In an optional embodiment, the third determining module 46 is used to determine the fault type of the target device based on the target matching result and the size information. After determining the fault type of the target device based on the target matching result and the size information, the method further includes: sending the fault type in a push message to the service outlet corresponding to the target device, and counting the number of times the target device reports the same fault type; if the number of times exceeds a preset threshold, sending a device replacement prompt to the bound object of the target device; if the number of times is less than or equal to the preset threshold, designating the target device as a key monitoring object.

[0113] Optionally, after determining the fault type, the geographical location of the faulty device is obtained, and the fault information is pushed to nearby after-sales service outlets based on the geographical location of the faulty device.

[0114] The push methods include, but are not limited to: email, iHaier, WeChat, and SMS;

[0115] The push message includes at least one of the following: MAC address, machine code, model code, model description, fault code, fault description, fault occurrence time + fault conclusion, and relevant temperature data.

[0116] The push notification may include the device model, the date the malfunction occurred, the number of malfunctioning devices, and the type of malfunction of the malfunctioning devices.

[0117] Optionally, if the number of E faults in Type A equipment exceeds 5, the fault information will be pushed to the head of the electrical control module.

[0118] If the number of E-faults in Type A equipment exceeds 10, the fault information will be pushed to the head of the electrical control module and the project manager; if the number of E-faults in Type A equipment exceeds 15, the fault information will be pushed to the head of the electrical control module, the project manager, the micro-management leader, and the quality node.

[0119] Embodiments of the present invention also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to perform the steps in any of the above method embodiments when executed.

[0120] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps:

[0121] S1, Obtain the reported data of the target device in a fault state;

[0122] S2, if it is determined through the reported data that the target device is in a continuous fault, the temperature data corresponding to the target device and the duration of the continuous fault of the target device are determined by identifying the fault code carried in the reported data;

[0123] S3, determine the target matching result of the temperature data and the preset temperature rule, and determine the magnitude information of the duration and the preset duration;

[0124] S4, determine the fault type of the target device based on the target matching result and the size information.

[0125] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0126] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0127] Embodiments of the present invention also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0128] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0129] S1, Obtain the reported data of the target device in a fault state;

[0130] S2, if it is determined through the reported data that the target device is in a continuous fault, the temperature data corresponding to the target device and the duration of the continuous fault of the target device are determined by identifying the fault code carried in the reported data;

[0131] S3, determine the target matching result of the temperature data and the preset temperature rule, and determine the magnitude information of the duration and the preset duration;

[0132] S4, determine the fault type of the target device based on the target matching result and the size information.

[0133] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0134] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0135] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those described herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0136] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method of identifying a fault type, characterized by, The method comprises: obtaining reported data of a target device in a fault state; in a case where it is determined through the reported data that the target device is in a persistent fault, determining temperature data corresponding to the target device and a duration of the persistent fault of the target device through a fault code carried in the reported data; determining a target matching result of the temperature data and a preset temperature rule, and determining size information of the duration; determining a fault type of the target device according to the target matching result and the size information; wherein determining the fault type of the target device according to the target matching result and the size information comprises: in a case where the target matching result indicates that the temperature data satisfies the preset temperature rule, and the size information indicates that the duration is less than a preset duration, determining that the fault type of the target device is a temporary fault; in a case where the target matching result indicates that the temperature data satisfies the preset temperature rule, and the size information indicates that the duration is greater than or equal to the preset duration, determining that the fault type of the target device is a data reporting exception; in a case where the target matching result indicates that the temperature data does not satisfy the preset temperature rule, and the size information indicates that the duration is less than the preset duration, determining that the fault type of the target device is a data reporting exception; in a case where the target matching result indicates that the temperature data does not satisfy the preset temperature rule, and the size information indicates that the duration is greater than or equal to the preset duration, determining that the fault type of the target device is a device fault.

2. The method of claim 1, wherein, determining a target matching result of the temperature data and a preset temperature rule comprises: obtaining a plurality of temperature intervals corresponding to the preset temperature rule, wherein the plurality of temperature intervals comprise at least one of a first temperature interval corresponding to a refrigeration sensor and a second temperature interval corresponding to a freezing sensor; in a case where the temperature data contains temperature data collected by multiple sensors, determining a first temperature corresponding to the refrigeration sensor and / or a second temperature corresponding to the freezing sensor; determining a first matching result of the first temperature and the first temperature interval and a second matching result of the second temperature and the second temperature interval; determining a target matching result of the temperature data and the preset temperature rule based on the first matching result and / or the second matching result.

3. The method of claim 1, wherein, After determining that the fault type of the target device is a device fault, the method further comprises: performing fault labeling on the device fault; in a case where it is determined that the device fault is caused by a refrigeration sensor exception, determining a refrigeration temperature exception of the target device; in a case where it is determined that the device fault is caused by a freezing sensor exception, determining a freezing temperature exception of the target device.

4. The method of claim 1, wherein, Before determining that the target device is in a persistent fault through the reported data, the method further comprises: determining whether the reported data contains alarm release information; in a case where the reported data contains alarm release information, defaulting that a target device corresponding to the reported data is running normally; In a case where the alarm release information is not included in the reported data, the device information corresponding to the target device is continuously reported based on a preset reporting frequency.

5. The method of claim 1, wherein, After determining the fault type of the target device according to the target matching result and the size information, the method further comprises: sending the fault type to a service point corresponding to the target device in a push message, and counting a target number of times of reporting the same fault type by the target device; in a case where the target number of times is greater than a preset threshold, sending prompt information of replacing the device to a bound object of the target device; in a case where the target number of times is less than or equal to the preset threshold, taking the target device as a key monitoring object.

6. An apparatus for confirming a failure type, characterized by comprising: comprises: an acquisition module configured to acquire reported data of a target device in a fault state; a first determination module configured to, in a case where it is determined through the reported data that the target device is in a continuous fault, determine temperature data corresponding to the target device and a continuous time of the continuous fault of the target device through a fault code carried in the reported data; a second determination module configured to determine a target matching result of the temperature data and a preset temperature rule, and determine size information of the continuous time and a preset continuous time; a third determination module configured to determine a fault type of the target device according to the target matching result and the size information; the third determination module is further configured to, in a case where the target matching result indicates that the temperature data satisfies the preset temperature rule, and the size information indicates that the continuous time is less than the preset continuous time, determine that the fault type of the target device is a temporary fault; in a case where the target matching result indicates that the temperature data satisfies the preset temperature rule, and the size information indicates that the continuous time is greater than or equal to the preset continuous time, determine that the fault type of the target device is data reporting abnormity; in a case where the target matching result indicates that the temperature data does not satisfy the preset temperature rule, and the size information indicates that the continuous time is less than the preset continuous time, determine that the fault type of the target device is data reporting abnormity; in a case where the target matching result indicates that the temperature data does not satisfy the preset temperature rule, and the size information indicates that the continuous time is greater than or equal to the preset continuous time, determine that the fault type of the target device is a device fault.

7. A computer readable storage medium, characterized in that, The computer-readable storage medium comprises a stored program, wherein the program executes the method of any one of claims 1 to 5 when running. 8.An electronic device comprising a memory and a processor, the electronic device comprising: The memory stores a computer program, and the processor is configured to execute the method of any one of claims 1 to 5 through the computer program.

Images