Fault reporting method, device and system for smart home equipment

Abstract

The invention discloses a fault reporting method, device and system for smart home equipment, and the method comprises the steps: generating an equipment fault state containing a fault code and a fault record according to a preset fault code comparison table when a fault of an equipment part is detected; performing duplicate removal processing on the equipment fault state, and reporting the filtered equipment fault state and the fault record to an IOT platform; receiving a start log uploading instruction issued by the IOT platform, packaging the operation log to generate a fault attachment, uploading the fault attachment to the IOT platform, forwarding the fault attachment to the operation and maintenance platform, and performing analysis and diagnosis on the fault by a manager of the operation and maintenance platform according to the fault attachment to realize fault recovery; and when detecting that the fault is recovered, updating the recovered equipment fault state and fault record, and reporting the updated equipment fault state and fault record to the IOT platform. And rapid positioning and efficient processing of the fault of the smart home system are effectively realized.

Description

Technical Field

[0001] The present invention relates to the field of equipment fault handling, and particularly to a method, device, and system for reporting faults of smart home devices. Background Art

[0002] With the continuous progress of Internet of Things technology, smart home systems are developing towards integration and interconnection. These smart home devices enable numerous devices to access the network through a unified gateway or central node, realizing information interaction and linkage control between devices. The fault reporting method has also changed from traditional local simple prompts to network-based remote reporting. However, there are still many deficiencies in the existing smart home fault handling. There is a lack of effective cooperation between devices, and the fault detection and reporting capabilities are limited. Usually, only simple indicator light flashing or local buzzer alarms are used to prompt users, and detailed and accurate fault information cannot be provided. In addition, although the device can send fault information to the user's mobile phone APP through the home Wi-Fi network, this information is often still relatively simple and rough, with limited information and difficult to accurately locate the root cause of the problem. There are also problems such as fault omission or repeated fault alarms. Summary of the Invention

[0003] In view of this, the purpose of the present invention is to propose a method, device, and system for reporting faults of smart home devices, aiming to solve the problems that the existing smart home fault handling cannot accurately locate and efficiently handle faults in the smart home system.

[0004] To achieve the above purpose, the present invention provides a method for reporting faults of smart home devices. The method is implemented based on smart home devices, and the method includes:

[0005] When a device component fault is detected, generate a device fault status and fault record containing a fault code according to a preset fault code look-up table;

[0006] Deduplicate the device fault status, and report the filtered device fault status and fault record to the IOT platform;

[0007] Receive an instruction from the IOT platform to start uploading the log, package the running log to generate a fault attachment, and upload it to the IOT platform for forwarding to the operation and maintenance platform. The management personnel of the operation and maintenance platform analyze and diagnose the fault based on the fault attachment to achieve fault recovery;

[0008] When it is detected that the fault is recovered, update the recovered device fault status and fault record and report them to the IOT platform.

[0009] Preferably, the deduplicating the device fault status and reporting the filtered device fault status and fault record to the IOT platform includes:

[0010] Cache the generated device fault status as a pending status, and set a flash interruption period for the pending status; when the same device fault status is not detected within the flash interruption period, compare the pending status with the previously reported device fault status, and if they are different, report it to the IOT platform.

[0011] Preferably, the operation log is packaged to generate a fault attachment and uploaded to the IOT platform, including:

[0012] Request a file upload token from the IOT platform through a preset protocol, package and compress the operation log according to the returned token, and upload the fault attachment to the IOT platform for storage through the HTTP protocol;

[0013] Receive the reply from the IOT platform with the file storage path URL corresponding to the fault attachment; wherein, the fault attachment includes a log file, a database file, a configuration file or a coredump file.

[0014] Preferably, the fault code comparison table is configured by the management personnel and then stored in the IOT platform for management. The fault code comparison table includes fault codes, fault levels, fault interpretations, and handling guides.

[0015] Preferably, the reporting of the device fault status or fault record to the IOT platform includes:

[0016] When there is no external network connection, the smart home device directly outputs the cached device fault status and fault record through the proximal debugging interface.

[0017] Preferably, the smart home device includes a direct-connected device and sub-devices network-connected to the direct-connected device. The sub-devices include ZigBee switch panels, and the direct-connected devices include access control devices, smart terminals, gateways, and fingerprint locks.

[0018] To achieve the above object, the present invention also provides a method for reporting faults of a smart home device. The method is implemented based on the IOT platform, and the method includes:

[0019] Receive the device fault status and fault record reported by the smart home device when a fault is detected. Among them, the device fault status includes fault codes, and the fault record includes fault codes, fault generation time, fault recovery time, and associated fault attachments;

[0020] Send a fault alarm email to the operation and maintenance platform and send a fault prompt message to the client according to the device fault status and fault record for prompting and guiding;

[0021] Receive the query request sent by the operation and maintenance platform, and provide the operation and maintenance platform with query services for device fault status, fault records, or operation logs;

[0022] Receive and store the device fault status and fault records updated and reported by the smart home device when the fault is recovered, and regularly delete the fault records and fault attachments that exceed the preset period.

[0023] To achieve the above object, the present invention also provides a fault reporting device for a smart home device. The device is implemented based on an IOT platform, and the device includes:

[0024] A receiving unit, configured to receive the device fault status and fault records reported by the smart home device when a fault is detected. Among them, the device fault status includes a fault code, and the fault record includes a fault code, a fault generation time, a fault recovery time, and an associated fault attachment;

[0025] A sending unit, configured to send a fault warning email to the operation and maintenance platform and send a fault prompt message to the client for prompting and guiding according to the device fault status and fault records;

[0026] A query unit, configured to receive the query request sent by the operation and maintenance platform, and provide the operation and maintenance platform with query services for device fault status, fault records, or operation logs;

[0027] A management unit, configured to receive and store the device fault status and fault records updated and reported by the smart home device when the fault is recovered, and regularly delete the fault records and fault attachments that exceed the preset period.

[0028] To achieve the above object, the present invention also provides a gateway device, including a processor, a memory, and a computer program stored in the memory. The computer program is executed by the processor to implement the steps of a fault reporting method for a smart home device as described in the above embodiment.

[0029] To achieve the above object, the present invention also provides a smart home system, and the system includes:

[0030] Smart home devices, including direct-connected devices and sub-devices, configured to detect the status of device components in real time, and report the generated device fault status and fault records to the IOT platform;

[0031] An IOT platform, connected to the smart home device, configured to receive and manage the device fault status and fault records reported by the smart home device, and send a fault warning email to the operation and maintenance platform and send a fault prompt message to the client for prompting and guiding according to the device fault status and fault records;

[0032] An operation and maintenance platform, connected to the IOT platform, is used to receive the fault warning emails pushed by the IOT platform and provide query services for device fault status, fault records, or operation logs through a WEB interface;

[0033] A client, connected to the IOT platform, is used to receive the fault prompt messages sent by the IOT platform and display text descriptions, customer service hotline jump options, or work order generation options according to the fault levels.

[0034] To achieve the above object, the present invention further provides a fault reporting device for smart home devices, including a processor, a memory, and a computer program stored in the memory. The computer program is executed by the processor to implement the steps of a fault reporting method for smart home devices as described in the above embodiment.

[0035] To achieve the above object, the present invention further provides a computer-readable storage medium, on which a computer program is stored. The computer program is executed by a processor to implement the steps of a fault reporting method for smart home devices as described in the above embodiment.

[0036] Beneficial effects:

[0037] In the above solution, when a device component fault is detected, a device fault status including a fault code is generated, and after deduplication processing, it is reported to the IOT platform, effectively avoiding resource waste caused by repeated reporting and improving the fault handling efficiency; by using a fault code look-up table to generate a standardized device fault status, the accuracy of fault information is improved; at the same time, through the upload of fault attachments, more comprehensive fault information is provided for operation and maintenance personnel, facilitating analysis and diagnosis, so as to accurately locate the fault to achieve fault recovery; in addition, through the update of the fault status and the reporting of fault records, the continuity and integrity of fault information are ensured, providing comprehensive information support for fault management.

[0038] By caching the device fault status and setting a flash-off period, repeated reporting caused by the same fault within the flash-off period is avoided, improving the reporting efficiency; at the same time, the suspended state is compared with the previous reported device fault status to ensure that only different fault states will be reported, avoiding multiple alarms caused by repeated detection of the same fault, reducing false alarms and repeated alarms, and reducing unnecessary network transmission and storage resource consumption by filtering out duplicate fault states.

[0039] Uploading the fault attachments to the IOT platform through the preset protocol and the HTTP protocol provides rich diagnostic information for the operation and maintenance personnel to analyze the faults, and realizes the standardized uploading process of the fault attachments, ensuring the reliability and compatibility of file transmission; at the same time, receiving the file storage path URL response sent by the IOT platform facilitates subsequent query and management of the fault attachments.

[0040] The fault code comparison table is stored in the IOT platform for management after being configured by the management personnel, which is convenient for unified management and update of the fault code information, improving the flexibility and scalability of the fault code management; at the same time, the fault code comparison table contains detailed information such as fault codes, fault levels, fault interpretations and handling guides, providing strong support for the rapid location and solution of faults, thus improving the efficiency of fault handling.

[0041] Receiving the device fault status and fault records reported by the smart home devices through the IOT platform, and sending fault warning emails to the operation and maintenance platform and sending fault prompt messages to the client, realizing the timely warning and prompt of faults; by providing query services for device fault status, fault records or operation logs, and regularly deleting the fault records and fault attachments exceeding the preset time limit, the efficiency and accuracy of fault management are improved.

[0042] Through the collaborative work of smart home devices, the IOT platform, the operation and maintenance platform and the client, this system constructs a complete fault reporting system, realizing real-time monitoring, reporting, warning, querying and management of smart home system faults, etc.; the connection and interaction between components ensure the timely transmission and processing of fault information, providing strong guarantee for the stable operation of the smart home system. Brief Description of the Drawings

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained according to these drawings.

[0044] Figure 1 It is a schematic flowchart of a fault reporting method for a smart home device provided by an embodiment of the present invention.

[0045] Figure 2 It is a schematic flowchart of the fault generation provided by an embodiment of the present invention.

[0046] Figure 3 It is a schematic flowchart of the fault recovery provided by an embodiment of the present invention.

[0047] Figure 4Schematic flowchart of a method for reporting faults of a smart home device provided in another embodiment of the present invention.

[0048] Figure 5 Schematic flowchart of a fault prompt provided in an embodiment of the present invention.

[0049] Figure 6 Schematic flowchart of uploading a fault attachment provided in an embodiment of the present invention.

[0050] Figure 7 Schematic diagram of the structure of a smart home system provided in an embodiment of the present invention.

[0051] Figure 8 Schematic diagram of the structure of a device for reporting faults of a smart home device provided in an embodiment of the present invention.

[0052] Figure 9 Schematic diagram of the structure of a device for reporting faults of a smart home device provided in another embodiment of the present invention.

[0053] The realization of the invention purpose, functional features and advantages will be further described with reference to the embodiments and the accompanying drawings. Detailed implementation manners

[0054] To make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts fall within the scope of protection of the present invention. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed present invention, but merely represents selected embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts fall within the scope of protection of the present invention.

[0055] The content of the present invention will be elaborated in detail below with reference to the embodiments.

[0056] In the current industry, the methods for reporting faults of smart homes are generally rather rough, lacking a systematic and efficient solution that can quickly locate and solve problems based on fault information. The main problems are as follows:

[0057] (1) The fault information is lacking and limited, making it difficult to accurately locate the root cause of the problem, which affects the analysis and location of faults;

[0058] (2) Fault omission in reporting, loss of fault information, which cannot guarantee the delivery of faults to the administrator, and thus cannot solve user faults in a timely manner. If the smart home system relies on the Wi-Fi network for fault reporting, when the home network is congested, interrupted, or has weak signals, the fault information may not be sent to the user terminal or the manufacturer's server in a timely manner. For example, when the intelligent smoke alarm detects smoke and triggers an alarm fault signal, due to network problems, it fails to report in a timely manner, which may delay the user or relevant departments from taking countermeasures and pose a safety hazard;

[0059] (3) Repeated fault alarms: After the fault is restored, there is no effective mechanism to avoid repeated alarms, which will not only frequently interfere with users, but also increase the burden on the network and storage.

[0060] Therefore, the present invention aims to solve the deficiencies in fault reporting and handling in existing smart home systems, and provides a fault reporting method that can provide more detailed and accurate fault reporting, so as to facilitate the rapid location and solution of problems. By designing a reliable delivery guarantee mechanism, it ensures that the fault information can be accurately and completely delivered to the designated processing module, avoiding fault omission caused by network problems; through deduplication processing, it can effectively identify and avoid repeated reporting of the same fault, reduce the amount of invalid information processing, and improve the reliability of the system.

[0061] Refer to Figure 1 The following is a schematic flowchart of a fault reporting method for a smart home device provided by an embodiment of the present invention. In this embodiment, the method is implemented based on a smart home device, and the method includes:

[0062] S11, when a device component fault is detected, generate a device fault status and a fault record containing a fault code according to a preset fault code look-up table.

[0063] Refer to Figure 2 As shown below, when there is already a fault code 1 in a sub-device of a smart home device, and a fault of code 2 is detected at this time, then the device fault status (code 1 and code 2) is formed and cached in the RAM, and the device fault status (protocol number: Z03-DEV0018) is reported immediately (current fault: code 1 and code 2, it is considered that the occurrence of the fault itself is generally low-frequency and at most 2-3 types of faults exist simultaneously). If the abnormal situation fails to receive a successful response, retry after 12 hours. Considering that the number of read and write operations of the FLASH is limited, a timer is set when the device fault status is formed, and it is stored in the FLASH after 12 hours. If the device fault status is lost due to power failure during this period, it is ignored and discarded. Among them,

[0064] Fault: A prompt message generated due to component failures or unavailable functions at the device level; mainly for device maintenance and repair personnel; faults that partially affect the use of C-end users also need to be prompted to C-end users. Faults include current faults (referring to faults that have occurred but have not been recovered) and historical faults (referring to faults that have occurred and have been recovered).

[0065] Fault code: Different code values are defined for different faults, which are used to view the fault comparison table for translation and explanation when the code value is received.

[0066] S12. Deduplicate the device fault status, and report the filtered device fault status and fault records to the IOT platform.

[0067] Further, in step S12, the process of deduplicating the device fault status and reporting the filtered device fault status and fault records to the IOT platform includes:

[0068] S12-1. Cache the generated device fault status as a pending state, and set a flash-off cycle for the pending state; when the same device fault status is not detected within the flash-off cycle, compare the pending state with the previously reported device fault status. If they are different, report it to the IOT platform.

[0069] In this embodiment, the direct-connected device is responsible for maintaining the device fault status generated by itself and reported by each sub-device, and is responsible for filtering flash-off alarms (if the interval between the generation time and the clearing time of the alarm is less than the specified time, the alarm is called a flash-off alarm, and this time period is called the flash-off cycle) and duplicate faults. Specifically, when the direct-connected device receives the device fault status generated by itself or reported by the sub-device, it caches it as a "pending state" and waits for a flash-off cycle (such as 1 minute); if there are still device fault statuses generated / reported during this period, update the "pending state" and restart the flash-off cycle; when a flash-off cycle arrives, compare the "pending state" with the previously reported device fault status for duplicate fault filtering. If they are the same, there is no need to report the fault, otherwise report it.

[0070] The direct-connected device reports the device fault status (protocol number: A03-DEV0012, fiid = 0xC053) (including all current faults of the device) generated by itself or reported by the sub-device to the IOT platform (Internet of Things platform), and the IOT platform caches it. In case of an abnormal situation, retry once without ensuring arrival. It is triggered by the C-end (client) user when opening the APP to obtain the status from the cloud and the cloud determines that the status has expired, or by the operation and maintenance / development personnel when clicking the refresh on the WEB interface to query the device fault status of the corresponding device.

[0071] The direct-connected device reports the fault record (protocol number: A03-DEV0013, fiid = 0x2063) (i.e., generated by code 2). The time when the fault record is generated is the timestamp when the direct-connected device receives the device fault status report. The fault record report needs to be ensured to arrive. In the case of an exception, when the direct-connected device is offline, it is required that 100 fault records can be cached locally and ensured to arrive after going online. If the storage space of the direct-connected device is limited, at least the last two fault records need to be ensured to arrive. Among them, the mechanism to ensure arrival is as follows: Record this fault record data through the database. Before receiving the correct response, this fault record data will be stored in the database all the time. The program will periodically attempt to send the data until the data is sent normally and the correct response is received, and then this fault record data will be erased.

[0072] When the IOT platform receives the fault record report, it forms a storage record in the record center, which is used as the record for the operation and maintenance platform to query, rather than the message record for the APP to query. The IOT platform deletes the fault records and fault attachments (file service type 0x72) three months ago every three months regularly, and checks the disk space of the server regularly. When the remaining space is insufficient, it gives an early warning and automatically performs the fault record archiving and backup process.

[0073] S13. Receive the instruction to start log upload sent by the IOT platform, package the running log to generate a fault attachment and upload it to the IOT platform for forwarding to the operation and maintenance platform. The management personnel of the operation and maintenance platform analyze and diagnose the fault according to the fault attachment to achieve fault recovery.

[0074] Further, in step S13, the packaging the running log to generate a fault attachment and uploading it to the IOT platform includes:

[0075] Request a file upload token from the IOT platform through a preset protocol, package and compress the running log according to the returned token, and upload the fault attachment to the IOT platform for storage through the HTTP protocol;

[0076] Receive the response from the IOT platform with the file storage path URL corresponding to the fault attachment; among them, the fault attachment includes a log file, a database file, a configuration file or a coredump file.

[0077] Further, the management personnel of the operation and maintenance platform analyze and diagnose the fault according to the fault attachment to achieve fault recovery, including:

[0078] When the fault analysis and diagnosis is a software fault, the device is remotely upgraded through OTA to recover the fault.

[0079] In this embodiment, if the direct-connected device determines that this fault needs to be accompanied by uploading fault attachments (logs / databases / configuration files / coredumps) to support fault diagnosis, it generates fault attachments locally, obtains a token from the IOT platform (protocol number: C07-DEV0008), and uploads the fault attachments using the HTTP file upload interface (protocol number: C07-DEV0059). The IOT platform stores the received fault attachments in file form and responds with the URL of the file storage path. Whether the response is successful / failed / time-out, the direct device needs to delete the local fault attachments. There is no need to retry for failed / time-out responses. If there is no need or inability to provide fault attachments, there is no need to upload fault attachments.

[0080] Requirements for fault attachments such as log files: Devices with a file system must be packaged and compressed, and the compression format is.tar. Devices without a file system upload a single file stream. The size limit for files received by the cloud (such as the IOT platform) is 10M to prevent devices from randomly uploading large files. The size limit for received files can be configured in the cloud.

[0081] S14. When it is detected that the fault is recovered, update the device fault status and fault record after recovery and report them to the IOT platform.

[0082] Furthermore, reporting the device fault status or fault record to the IOT platform includes:

[0083] When there is no external network connection, the smart home device directly outputs the cached device fault status and fault record through the proximal debugging interface.

[0084] In this embodiment, referring to Figure 3 As shown, for sub-devices, there are existing fault codes 1 and 2. At this time, it is detected that fault code 2 is recovered, and the remaining is code 1. Then update the device fault status (code 1) and cache it in the RAM, and immediately report the device fault status (protocol number: Z03-DEV0018) (current fault: code 1). If the abnormal situation fails to get a successful response, retry after 12 hours.

[0085] The direct-connected device reports the fault record (protocol number: A03-DEV0013, fiid = 0x2063) (code 2 is recovered, forming a historical fault). The time when the fault record is generated is the time stamp when the direct-connected device receives the device fault status report. The fault record report needs to ensure arrival.

[0086] In the abnormal situation where the direct-connected device cannot connect to the IOT platform due to the lack of external network on-site, etc., it needs to support obtaining the device fault status and fault record cached in itself and sub-devices through proximal debugging methods (such as telnet / serial port, etc.).

[0087] Further, the smart home device includes a directly-connected device and a sub-device network-connected to the directly-connected device. The sub-device includes a ZigBee switch panel, and the directly-connected device includes an access control device, a smart terminal, a gateway, and a fingerprint lock.

[0088] Further, the fault code look-up table is configured by the management personnel and then stored in the IOT platform for management. The fault code look-up table includes a fault code, a fault level, a fault interpretation, and a handling guide.

[0089] In this embodiment, the relevant data of the fault code look-up table is configured by the developer and then entered into the IOT platform for storage. The fault code look-up table includes a fault code, a fault level, a fault interpretation, a handling guide, etc.

[0090] Devices directly connected to the IOT platform for data communication are called directly-connected devices, such as gateways, WIFI fingerprint locks, extensions, etc. Devices indirectly connected to the IOT platform for data communication by connecting to directly-connected devices such as gateways are called sub-devices, such as ZigBee switch panels, Bluetooth mesh switch panels, PLC switch panels, etc.

[0091] Refer to Figure 4 The following is a schematic flow chart of a fault reporting method for a smart home device provided by another embodiment of the present invention. In this embodiment, the method is implemented based on the IOT platform, and the method includes:

[0092] S21, receiving the device fault status and fault record reported by the smart home device when a fault is detected. Among them, the device fault status includes a fault code, and the fault record includes a fault code, a fault generation time, a fault recovery time, and the associated fault attachment.

[0093] S22, sending a fault warning email to the operation and maintenance platform and sending a fault prompt message to the client according to the device fault status and fault record for prompting and guiding.

[0094] S23, receiving the query request sent by the operation and maintenance platform, and providing the operation and maintenance platform with query services for device fault status, fault record, or operation log.

[0095] S24, receiving the updated device fault status and fault record reported by the smart home device when the fault is recovered for storage, and regularly deleting the fault records and fault attachments that exceed the preset period.

[0096] In this embodiment, refer to Figure 5As shown, the fault prompt includes providing fault alarm email prompts to operation and maintenance personnel / developers and providing prompts and guidance of fault prompt messages to C-end users. Specifically, when the IOT platform receives the reported fault records, storage records are formed in the record center. At the same time, the business is transferred to the operation and maintenance platform. The operation and maintenance platform interprets the faults according to the query fault code comparison table and organizes the alarm email content to be sent to the set recipients (operation and maintenance personnel / developers). Among them, the email content includes but is not limited to the fault generation time, alarm source information (including home name, home account, device did, device name), fault interpretation (module name, fault type), and jump link URL. The operation and maintenance personnel receive the alarm email and log in to the operation and maintenance platform through the jump link in the email content to view the faults.

[0097] The operation and maintenance personnel view the device fault status. The operation and maintenance platform requests data from the IOT platform through the HTTP device fault status interface. The request parameters are device DID / MAC / home ID, and paging acquisition is supported. The response content includes device information (directDid, DID, MAC, device name, home ID, home name), online / offline status, and device fault status (fault code and corresponding fault description). When the operation and maintenance / development personnel view the fault log, the operation and maintenance platform requests data from the IOT platform through the HTTP device fault record interface. The request parameter is the device DID, and paging acquisition is supported. The response content includes timestamp, fault code, fault type (generation / restoration), fault description, and fault attachment URL.

[0098] When the C-end user enters the device control page on the APP side, the APP side determines that there is a fault status and displays a fault icon. When the user clicks on the details, the APP obtains the fault prompt message (protocol number: A12-APP0001) from the IOT platform for prompt and guidance. The guidance methods include text description, jumping to the customer service hotline, jumping to the feedback, etc. After the faults at the severe level or above are confirmed by the C-end user, work orders for on-site services can be formed. The abnormal situation is that when the APP side cannot access the external network, it cannot query the fault prompt message from the IOT platform, and the general prompt message is used for prompt by default. The screen-enabled intelligent terminal can also prompt the prompt message when the user enters the device control page.

[0099] Refer to Figure 6As shown in the figure, evtId is assigned when the operation and maintenance platform configures the enabling / disabling of running log reporting (protocol number: A03-DEV0011, fiid = 0xC054) by developers. evtId is re-assigned every time the switch is toggled. The evtId assigned each time only needs to be unique within a single device. For low-power devices such as NB locks and WIFI08 locks, they are in a sleep state (not receiving control instructions) usually. At this time, when the operation and maintenance platform enables log reporting, the operation and maintenance platform calls the cache control instruction interface from the IOT platform, and the IOT platform issues control instructions after the device wakes up and goes online.

[0100] After enabling the running log reporting configuration, the device reports logs according to the set level, duration, and frequency (protocol number: A03-DEV0013, fiid = 0xA042), and the QoS level is QoS0. The running logs are uploaded and stored in the form of files. The evtId is carried when reporting logs to associate the logs reported multiple times as the logs generated by the same transaction.

[0101] Requirements for the uploaded log files: Devices with a file system must be packed and compressed, and the compression format is.tar. Devices without a file system upload a single file stream; the size limit for the cloud to receive files each time is 10M to prevent devices from randomly uploading large files, and the size limit for receiving files can be configured in the cloud.

[0102] During the period of enabling the running log, developers can trigger the running log reporting (protocol number: A03-DEV0011, fiid = 0xA042) control at any time on the operation and maintenance platform, and the device reports logs (protocol number: A03-DEV0013, fiid = 0xA042). The IOT platform deletes the log records and log files (file service type 0x72) three months ago every three months regularly.

[0103] Refer to Figure 7 The following figure shows the structural schematic diagram of a smart home system provided by another embodiment of the present invention. In this embodiment, the system includes:

[0104] Smart home devices, including direct-connected devices and sub-devices, are used to detect the status of device components in real time and report the generated device fault status and fault records to the IOT platform;

[0105] The IOT platform is connected to the smart home devices and is used to receive and manage the device fault status and fault records reported by the smart home devices, and issue fault warning emails to the operation and maintenance platform and issue fault prompt messages to the client according to the device fault status and fault records for prompting and guiding;

[0106] An operation and maintenance platform, connected to the IOT platform, is used to receive the fault warning emails pushed by the IOT platform and provide query services for device fault status, fault records or operation logs through a WEB interface;

[0107] A client, connected to the IOT platform, is used to receive the fault prompt messages sent by the IOT platform and display text descriptions, customer service hotline jump or work order generation options according to the fault levels.

[0108] In this embodiment, smart home devices include sub-devices (such as ZigBee switch panels, etc.) and directly connected devices (such as gateways, access control devices, smart terminals, third-party single products, etc.) that are connected to the IOT platform. Operation and maintenance personnel can obtain a device list from the IOT platform by browsing the operation and maintenance platform, and display device dids, device names, home names, home accounts, and their online / offline status, fault information (fault codes, fault levels, fault interpretations, fault descriptions, handling guides, occurrence times, recovery times).

[0109] When a sub-device / directly connected device detects a fault, it defines and reports the device fault status according to a custom fault code comparison table, and the IOT platform updates the device fault status. There is no concept of fault attachments for sub-devices. The directly connected devices upload fault attachments as needed, report fault records, and the IOT platform forms fault storage records and notifies the operation and maintenance platform for fault warnings (sending warning emails, etc.). The operation and maintenance personnel immediately log in to the operation and maintenance platform, and the operation and maintenance platform obtains the device fault status from the IOT platform for display. When the operation and maintenance personnel view the device fault status and determine that a phone call or on-site handling is required, they will handle it. If the operation and maintenance personnel determine that developers need to intervene in the diagnosis, they will submit a product fault order to the developers. The developers accept the product fault order, log in to the operation and maintenance platform to view the fault status and can retrieve the fault attachments for analysis and diagnosis. If the fault attachments still cannot support fault diagnosis, the developers can trigger the device operation log reporting function through the operation and maintenance platform and continue to monitor the device operation logs. If the fault diagnosis is a software fault, the device can be remotely upgraded through OTA to recover from the fault. If the fault diagnosis is a hardware fault, such as a problem with the interface feedback hardware, after-sales technical support can carry professional detection tools for on-site preliminary diagnosis. If it is determined to be a component fault, component replacement and repair can be carried out, etc. If the fault diagnosis is a network fault, network fault recovery can be performed through methods such as network setting adjustment and configuration inspection. If the fault diagnosis is a data fault, such as determining that data anomalies or dirty data affect the system operation, device data recovery can be carried out through methods such as remotely accessing the device or technical support cooperating with development on-site.

[0110] When the C-end user enters the device control page on the APP side, the APP side determines that there is a fault status and displays a fault icon. When the user clicks on the details, the APP obtains the fault prompt message and fault guidance from the IOT platform for prompting. For faults at the severe level or above, after confirmation by the C-end user, a work order for on-site service can be generated to provide efficient service to the user and improve customer satisfaction.

[0111] Furthermore, the definitions and meanings of the fault codes are as follows:

[0112]

[0113]

[0114] Note:

[0115] The fault code is defined as 4 bytes and consists of "reserved" (1 byte), "module" (1 byte), and "fault type" (2 bytes); "fault level" is used when the operation and maintenance platform displays the interpretation and is not defined within the fault code itself; the "fault level" is divided into four levels: critical, severe, general, and prompt.

[0116] Refer to Figure 8 Shown is a schematic structural diagram of a fault reporting device for a smart home device provided by an embodiment of the present invention.

[0117] In this embodiment, the device is implemented based on a smart home device. The device 30 includes:

[0118] A detection unit 31, configured to generate a device fault status and a fault record including a fault code according to a preset fault code comparison table when detecting a fault in a device component;

[0119] A filtering unit 32, configured to perform duplicate removal processing on the device fault status and report the filtered device fault status and fault record to the IOT platform;

[0120] A processing unit 33, configured to receive an instruction for starting log upload sent by the IOT platform, package the operation log to generate a fault attachment and upload it to the IOT platform for forwarding to the operation and maintenance platform, and enable the management personnel of the operation and maintenance platform to analyze and diagnose the fault according to the fault attachment to achieve fault recovery;

[0121] A reporting unit 34, configured to update the restored device fault status and fault record and report them to the IOT platform when detecting fault recovery.

[0122] Refer to Figure 9 Shown is a schematic structural diagram of a fault reporting device for a smart home device provided by another embodiment of the present invention.

[0123] In this embodiment, the device is implemented based on the IOT platform. The device 40 includes:

[0124] A receiving unit 41, configured to receive the device fault status and fault records reported by the smart home device when a fault occurs. The device fault status includes a fault code, and the fault records include a fault code, a fault generation time, a fault recovery time, and associated fault attachments.

[0125] A sending unit 42, configured to send a fault warning email to the operation and maintenance platform and send a fault prompt message to the client for prompting and guiding according to the device fault status and fault records.

[0126] A query unit 43, configured to receive a query request sent by the operation and maintenance platform and provide a query service for the device fault status, fault records, or operation logs to the operation and maintenance platform.

[0127] A management unit 44, configured to receive and store the device fault status and fault records updated and reported by the smart home device when the fault is recovered, and regularly delete the fault records and fault attachments that exceed a preset period.

[0128] Each unit module of the device 30 / 40 can respectively execute the corresponding steps in the above method embodiment, so the unit modules will not be elaborated here. For details, please refer to the description of the corresponding steps above.

[0129] An embodiment of the present invention further provides a gateway device, including a processor, a memory, and a computer program stored in the memory. The computer program is executed by the processor to implement the steps of a method for reporting a fault of a smart home device according to any one of claims 1 to 6.

[0130] An embodiment of the present invention further provides a gateway device, which includes the above-mentioned device for reporting a fault of a smart home device. Further, the gateway device can be a wireless gateway or other smart home devices with a gateway, such as a smart screen with a gateway. The device for reporting a fault of a smart home device can adopt Figure 8 or Figure 9 the structure of the embodiment, and correspondingly, can execute Figure 1 or Figure 4 the technical solutions of the method embodiment shown. The implementation principle and technical effects are similar. For details, please refer to the relevant records in the above embodiments and will not be elaborated here.

[0131] The device includes devices with a photographing function such as a mobile phone, a digital camera, or a tablet computer, or devices with an image processing function, or devices with an image display function. The device may include components such as a memory, a processor, an input unit, a display unit, and a power supply.

[0132] Among them, the memory can be used to store software programs and modules. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory. The memory mainly includes a program storage area and a data storage area. Among them, the program storage area can store the operating system, application programs required for at least one function (such as the image playback function, etc.); the data storage area can store data created according to the use of the device, etc. In addition, the memory can include high-speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage devices. Correspondingly, the memory can also include a memory controller to provide access to the memory by the processor and the input unit.

[0133] The input unit can be used to receive input digital or character or image information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls. Specifically, in addition to including a camera, the input unit in this embodiment can also include a touch-sensitive surface (such as a touch display screen) and other input devices.

[0134] The display unit can be used to display information input by the user or information provided to the user and various graphical user interfaces of the device. These graphical user interfaces can be composed of graphics, text, icons, videos and any combination thereof. The display unit can include a display panel. Optionally, the display panel can be configured in the form of an LCD (Liquid Crystal Display), an OLED (Organic Light-Emitting Diode), etc. Further, the touch-sensitive surface can cover the display panel. When the touch-sensitive surface detects a touch operation on or near it, it is transmitted to the processor to determine the type of touch event. Subsequently, the processor provides a corresponding visual output on the display panel according to the type of touch event.

[0135] The embodiment of the present invention also provides a computer-readable storage medium. This computer-readable storage medium can be the computer-readable storage medium included in the memory in the above embodiment; it can also exist separately and be a computer-readable storage medium not assembled into the device. At least one instruction is stored in this computer-readable storage medium, and the instruction is loaded and executed by the processor to implement Figure 1 the fault reporting method of the smart home device shown. The computer-readable storage medium can be a read-only memory, a magnetic disk or an optical disc, etc.

[0136] It should be noted that the various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. For the same or similar parts among the embodiments, reference can be made to each other. For the apparatus embodiments, device embodiments, and storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple. For the relevant parts, reference can be made to the corresponding descriptions in the method embodiments.

[0137] Also, in this document, the term "comprising", "including" or any other variation thereof is intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the phrase "comprising a..." does not exclude the presence of additional identical elements in the process, method, article or device comprising the said element.

[0138] The above description shows and describes the preferred embodiments of the present invention. It should be understood that the present invention is not limited to the form disclosed herein, and should not be regarded as excluding other embodiments. Instead, it can be used in various other combinations, modifications and environments, and can be changed within the scope of the inventive concept herein through the above teachings or the skills or knowledge in related fields. Any changes and variations made by those skilled in the art without departing from the spirit and scope of the present invention shall fall within the protection scope of the appended claims of the present invention.

Claims

1. A method for reporting faults of smart home devices, characterized in that: The method is implemented based on a smart home device, and the method includes: When a device component failure is detected, a device failure status and failure record containing a failure code is generated according to a preset failure code comparison table; De-duplicate the equipment fault status and report the filtered equipment fault status and fault records to the IOT platform; Receive the log upload start instruction issued by the IOT platform, package the operation log to generate fault attachments and upload them to the IOT platform for forwarding to the operation and maintenance platform. The management personnel of the operation and maintenance platform analyze and diagnose the fault according to the fault attachments to achieve fault recovery; When fault recovery is detected, the restored device fault status and fault record are updated and reported to the IOT platform.

2. A method for reporting faults of smart home devices according to claim 1, characterized in that: The device fault status is deduplicated, and the filtered device fault status and fault records are reported to the IOT platform, including: The generated device fault status is cached as a suspended status, and a flash-off period is set for the suspended status; when the same device fault status is not detected within the flash-off period, the suspended status is compared with the previously reported device fault status, and if they are different, they are reported to the IOT platform.

3. A fault reporting method for a smart home device according to claim 1, characterized in that: The step of packaging the operation log to generate a fault attachment and uploading it to the IOT platform includes: Request a file upload token from the IOT platform through a preset protocol, package and compress the operation log according to the returned token, and upload the fault attachment to the IOT platform through the HTTP protocol for storage; Receive a response from the IOT platform with a file storage path URL corresponding to the fault attachment; wherein the fault attachment includes a log file, a database file, a configuration file or a coredump file.

4. A method for reporting faults of smart home devices according to claim 1, characterized in that: The fault code comparison table is configured by the management personnel and then stored in the IOT platform for management. The fault code comparison table includes fault codes, fault levels, fault interpretations, and processing guidelines.

5. A fault reporting method for a smart home device according to claim 1, characterized in that: Reporting the device fault status or fault record to the IOT platform includes: When there is no external network connection, the smart home device directly outputs its own cached device fault status and fault records through the local debugging interface.

6. A method for reporting faults of smart home devices according to claim 1, characterized in that: The smart home device includes a direct connection device and a sub-device connected to the direct connection device through a network. The sub-device includes a ZigBee switch panel. The direct connection device includes an access control device, a smart terminal, a gateway, and a fingerprint lock.

7. A method for reporting faults of smart home devices, characterized in that: The method is implemented based on the IOT platform, and the method includes: Receiving a device fault state and a fault record reported by a smart home device when a fault is detected, wherein the device fault state includes a fault code, and the fault record includes a fault code, a fault occurrence time, a fault recovery time, and associated fault attachments; Send fault alarm emails to the operation and maintenance platform and fault prompts to the client for prompts and guidance based on the equipment fault status and fault records; Receive a query request sent by the operation and maintenance platform, and provide the operation and maintenance platform with query services for equipment fault status, fault records or operation logs; Receive the updated device fault status and fault records reported by the smart home device when the fault is restored, store them, and regularly delete the fault records and fault attachments that exceed the preset period.

8. A fault reporting device for smart home equipment, characterized in that: The device is implemented based on the IOT platform, and the device includes: A receiving unit, configured to receive a device fault state and a fault record reported by a smart home device when a fault is detected, wherein the device fault state includes a fault code, and the fault record includes a fault code, a fault occurrence time, a fault recovery time, and associated fault attachments; The sending unit is used to send fault alarm emails to the operation and maintenance platform and send fault prompts to the client for prompts and guidance according to the equipment fault status and fault records; A query unit, used to receive a query request sent by the operation and maintenance platform, and provide the operation and maintenance platform with a query service for equipment fault status, fault records or operation logs; The management unit is used to receive and store the device fault status and fault records updated and reported by the smart home device when the fault is restored, and to regularly delete the fault records and fault attachments that exceed a preset period.

9. A gateway device, characterized in that: The method comprises a processor, a memory and a computer program stored in the memory, wherein the computer program is executed by the processor to implement the steps of a fault reporting method for a smart home device as described in any one of claims 1 to 6.

10. A smart home system, characterized in that: The system comprises: Smart home devices, including directly connected devices and sub-devices, are used to detect the status of device components in real time and report the generated device fault status and fault records to the IOT platform; The IOT platform is connected to the smart home device, and is used to receive and manage the device fault status and fault records reported by the smart home device, and send fault alarm emails to the operation and maintenance platform and send fault prompts to the client for prompts and guidance according to the device fault status and fault records; An operation and maintenance platform, connected to the IOT platform, for receiving fault warning emails pushed by the IOT platform, and providing query services for equipment fault status, fault records or operation logs through a WEB interface; The client is connected to the IOT platform and is used to receive the fault prompt issued by the IOT platform, and display text description, customer service hotline jump or work order generation options according to the fault level.

Images