A management method, device and equipment of an intelligent door lock and a storage medium

Abstract

The application provides a management method, device and equipment of an intelligent door lock and a storage medium, and belongs to the technical field of intelligent household appliances. The method comprises the following steps: receiving and reading the nearest node of a target door lock parameter acquisition ZigBee device in an ad hoc network sent by a target door lock device; performing door lock parameter inspection with the ZigBee device of the nearest node; and reporting an instruction execution result to a server based on the parameter inspection result. By loading a ZigBee element in the intelligent door lock, the door lock devices can communicate with each other, automatically select a nearby node device and read data, perform door lock parameter verification, and upload the instruction execution result to the server. The door lock parameters generated by mutual inspection of the management instructions are made, the intelligent door lock system is more secure and reliable, and the ZigBee device is used for ad hoc network data transmission and inspection, and has the characteristics of low power consumption, low time delay, high reliability and short distance.

Description

Technical Field

[0001] This application relates to the field of smart home appliance technology, and in particular to a management method, device, equipment and storage medium for a smart door lock. Background Technology

[0002] With the development of IoT technology and the increasing demand for hotel and dormitory management services, the market demand for smart door locks is growing.

[0003] In hotels, guesthouses, dormitories, and similar settings, multiple smart locks are typically installed. These locks can connect to the network via a gateway device and communicate with the server. The server manages the smart locks within its jurisdiction in batches, but this batch management presents certain security risks. For example, when the server issues a password change command to cause a batch password change for the smart locks, data loss, gateway device malfunction, or other factors may cause some locks to fail to receive the command. Summary of the Invention

[0004] This application provides a management method, device, equipment, and storage medium for smart locks, which can make smart lock systems more secure and reliable. The technical solution is as follows:

[0005] On one hand, embodiments of this application provide a management method for a smart lock, the method being applied to a ZigBee device in a smart lock system, the method comprising:

[0006] Receive and read target lock parameters sent by the target lock device, wherein the target lock parameters are generated by the target lock device executing management instructions issued by the server, and the target lock device is connected to the ZigBee device;

[0007] Find the nearest node of the ZigBee device in the self-organizing network, where the self-organizing network is the self-organizing network formed by the ZigBee devices in the smart door lock system;

[0008] Perform door lock parameter verification with the ZigBee device of the nearest node;

[0009] Based on the parameter verification results, the system reports the instruction execution results to the server. The instruction execution results are used to indicate whether the instruction execution of the target door lock device is correct or incorrect.

[0010] Optionally, the target door lock device receives the management command issued by the server via the NB-IoT protocol, performs protocol conversion, and sends the target door lock parameters to the ZigBee via the ZigBee protocol;

[0011] The process of receiving and reading the target door lock parameters sent by the target door lock device includes:

[0012] The target door lock parameters are received and read via the ZigBee protocol.

[0013] Optionally, reporting the instruction execution result to the server based on the parameter verification includes:

[0014] The ZigBee protocol is converted to the NB-IoT protocol using a coordinator.

[0015] Based on the parameter verification results, the execution result of the instruction is reported to the server via the NB-IoT protocol.

[0016] Optionally, the management instruction carries header information indicating the operation type, and the target door lock device is used to send the target door lock parameters to the ZigBee device when the operation type is a batch operation;

[0017] The door lock parameter verification of the ZigBee device with the nearest node includes:

[0018] Verify the management command received by the door lock device in the nearest node;

[0019] In response to the operation type indicated by the header information in the management instruction being the batch operation, the door lock parameters are checked with the nearest ZigBee device.

[0020] Optionally, reporting the instruction execution result to the server based on the parameter verification includes:

[0021] In response to the inconsistency between the target lock parameters and the lock parameters of the nearest node, the ad hoc network matches the next nearest node and performs lock parameter verification with the ZigBee device of the next nearest node;

[0022] In response to the inconsistency between the target lock parameters and the lock parameters of the next nearest node, the system reports the instruction execution result to the server to indicate an instruction execution error. The instruction execution result also includes the error reason, the MAC address and IP address of the target lock device.

[0023] On the other hand, embodiments of this application provide a management method for a smart door lock, the method being applied to a door lock device in a smart door lock system, the method comprising:

[0024] Receive management instructions from the server;

[0025] Based on the management instructions, the parameters are updated to generate the target door lock parameters;

[0026] The target ZigBee device sends the target lock parameters to the target ZigBee device, which is connected to the lock device. The target ZigBee device is used to verify the lock parameters with the nearest ZigBee device in the ad hoc network, and reports the command execution result to the server based on the parameter verification result.

[0027] Optionally, receiving management instructions from the server includes:

[0028] In response to the device wake-up time, the management command issued by the server is received via the NB-IoT protocol;

[0029] Sending the target door lock parameters to the target ZigBee device includes:

[0030] The NB-IoT protocol is converted to the ZigBee protocol using a coordinator.

[0031] The target door lock parameters are sent to the target ZigBee device via the ZigBee protocol.

[0032] On the other hand, embodiments of this application provide a management device for a smart door lock, the device comprising:

[0033] The first receiving module is used to receive and read the target lock parameters sent by the target lock device. The target lock parameters are generated by the target lock device executing the management instructions issued by the server. The target lock device is connected to the ZigBee device.

[0034] The acquisition module is used to acquire the nearest node of the ZigBee device in the self-organizing network, wherein the self-organizing network is the self-organizing network formed by the ZigBee devices in the smart door lock system;

[0035] The verification module is used to verify the door lock parameters with the ZigBee device of the nearest node;

[0036] The first sending module is used to report the instruction execution result to the server based on the parameter verification results. The instruction execution result is used to indicate whether the instruction execution of the target door lock device is correct or incorrect.

[0037] On the other hand, embodiments of this application provide a management device for a smart door lock, the device comprising:

[0038] The second receiving module is used to receive management instructions issued by the server;

[0039] The generation module is used to update parameters based on the management instructions and generate target door lock parameters;

[0040] The second sending module is used to send the target door lock parameters to the target ZigBee device. The target ZigBee device is connected to the door lock device. The target ZigBee device is used to verify the door lock parameters with the ZigBee device of the nearest node in the ad hoc network, and report the instruction execution result to the server based on the parameter verification result.

[0041] On the other hand, embodiments of this application provide an electronic device, which includes a memory and a processor. The memory stores a computer program, which, when executed by the processor, performs a smart lock management method as described above.

[0042] On the other hand, this application provides a smart door lock, which includes the electronic device, door lock module, and ZigBee module described above. The door lock device is used to control the opening and closing of the door lock and to receive and execute instructions sent by the server. The ZigBee device is used to communicate with other smart door locks to perform parameter verification. The electronic device is communicatively connected to the door lock device and the ZigBee device, and is used to control the door lock device to send door lock parameters to the ZigBee device, and to control the ZigBee device to perform parameter verification and report the instruction execution results.

[0043] On the other hand, embodiments of this application provide a computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, at least one program, code set, or instruction set is loaded and executed by a processor to implement a smart lock management method as described above.

[0044] On the other hand, embodiments of this application provide a computer program product that runs on the processor of a computer device, causing the computer device to perform a smart lock management method as described above.

[0045] The technical solution provided in this application includes at least the following beneficial effects:

[0046] This application provides a management method, device, equipment, and storage medium for smart locks. By incorporating ZigBee components into the smart lock, communication between lock devices is enabled. After a management command is issued from the server, the dynamic routing within the ZigBee devices automatically selects nearby node devices, reads data, verifies lock parameters, and uploads the command execution results to the server. This mutual verification of the lock parameters generated by the executed management commands enhances the security and reliability of the smart lock system. Furthermore, the use of ZigBee devices for self-organizing network data transmission and verification offers advantages such as low power consumption, low latency, high reliability, and short range. Attached Figure Description

[0047] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0048] Figure 1 This is a flowchart illustrating a smart lock management method provided in an exemplary embodiment of this application;

[0049] Figure 2 This is a flowchart of a smart lock management method provided in another exemplary embodiment of this application;

[0050] Figure 3 This is a flowchart of a smart lock management method provided in another exemplary embodiment of this application;

[0051] Figure 4 This is a flowchart of a smart lock management method provided in another exemplary embodiment of this application;

[0052] Figure 5 This is a flowchart of a smart lock management method provided in another exemplary embodiment of this application;

[0053] Figure 6 This is a structural block diagram of a smart door lock management device provided in an exemplary embodiment of this application;

[0054] Figure 7 This is a structural block diagram of a smart door lock management device provided in another exemplary embodiment of this application;

[0055] Figure 8 This is a structural block diagram of an electronic device provided in an exemplary embodiment of this application. Detailed Implementation

[0056] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0057] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0058] If the application documents contain similar descriptions such as "first, second, third", the following explanation shall be added: In the following description, the terms "first, second, third" are used only to distinguish similar objects and do not represent a specific order of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0059] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0060] To address the problems existing in related technologies, this application provides a management method for smart locks, which is applied to electronic devices. In some embodiments, the electronic device can be a controller for a smart lock, which includes a controller, a lock device, and a ZigBee device. The lock device controls the opening and closing of the lock and receives and executes instructions sent by a server. The ZigBee device communicates with other smart locks to perform parameter verification. The electronic device is communicatively connected to the lock device and the ZigBee device, controlling the lock device to send lock parameters to the ZigBee device and controlling the ZigBee device to perform parameter verification and report the instruction execution results.

[0061] The smart lock management method provided in this application can achieve its functions by having the processor of an electronic device call program code, wherein the program code can be stored in a computer storage medium.

[0062] Please refer to Figure 1 This document illustrates a flowchart of a smart lock management method provided in an exemplary embodiment of this application, applied to a ZigBee device within a smart lock system. The method includes the following steps:

[0063] Step 101: Receive and read the target door lock parameters sent by the target door lock device. The target door lock parameters are generated by the target door lock device executing the management instructions issued by the server. The target door lock device is connected to the ZigBee device.

[0064] In one possible implementation, the smart lock system in this application mainly consists of a server, lock devices, ZigBee devices, and client devices. The client runs a smart lock management platform, through which users (e.g., hotel managers, dormitory administrators) can perform batch management operations, such as changing passwords. The client sends corresponding instructions to the server based on user actions. The server sends management instructions to the corresponding lock devices. Upon waking up, the lock devices receive and execute the management instructions from the server, generating corresponding lock parameters (e.g., a new password) and sending these parameters to the associated ZigBee devices.

[0065] Optionally, the smart lock system has at least one node, each node containing a lock device and a ZigBee device, which are connected in communication.

[0066] The ZigBee device receives and reads the target door lock parameters sent by the target door lock device, which is the door lock device associated with the ZigBee device.

[0067] Step 102: Obtain the nearest node of the ZigBee device in the self-organizing network, which is the self-organizing network formed by ZigBee devices in the smart door lock system.

[0068] In a smart lock system, multiple nodes communicate with each other via ZigBee devices. During system initialization, the ZigBee devices self-organize to find the nearest node for mutual verification.

[0069] In one possible implementation, the ZigBee device obtains device information such as the Media Access Control Address (MAC address) and phone card identification code of the door lock device, and automatically obtains the nearest neighboring node through a self-organizing network. This nearest neighbor node refers to the node with the shortest path to it within the self-organizing network.

[0070] Optionally, considering that smart lock systems may experience updates such as new devices being added or old devices being removed, ZigBee devices can self-organize at preset time intervals to determine the latest nodes.

[0071] Step 103: Verify the door lock parameters with the nearest ZigBee device.

[0072] ZigBee devices perform cross-validation between the target lock parameters provided by the lock device at their current node and the lock parameters of the nearest node to determine if the parameters are consistent. For batch-issued management commands, the execution results should be consistent; if they are inconsistent, one of the commands has been executed incorrectly.

[0073] By adding ZigBee devices to enable communication between smart locks, the locks can check each other's lock parameters and detect errors in the command execution process.

[0074] Step 104: Based on the parameter verification results, report the instruction execution results to the server. The instruction execution results are used to indicate whether the instruction execution of the target door lock device is correct or incorrect.

[0075] When a ZigBee device determines that the door lock device in its node has executed an error, it reports it to the server, enabling the server to promptly learn about the execution status of the instruction and provide feedback to the user's client.

[0076] Optionally, the ZigBee device may report the result of the instruction regardless of whether the instruction execution result is correct or incorrect, or the ZigBee device may only report the result of the instruction execution error.

[0077] As an illustration, ZigBee devices report command execution results via an acknowledgment character (ACK). If the target door lock device executes the command correctly, the ZigBee device sends "ack=true"; if the target door lock device executes the command incorrectly, the ZigBee device sends "ack=false".

[0078] In summary, the method provided in this application, by incorporating ZigBee components into smart locks, enables communication between lock devices. After a management command is issued by the server, the dynamic routing within the ZigBee devices automatically selects nearby node devices, reads data, verifies lock parameters, and uploads the command execution results to the server. This mutual verification of the lock parameters generated by the executed management commands enhances the security and reliability of the smart lock system. Furthermore, the use of ZigBee devices for self-organizing network data transmission and verification offers advantages such as low power consumption, low latency, high reliability, and short range.

[0079] Please refer to Figure 2 This illustration shows a flowchart of a smart lock management method provided by another exemplary embodiment of this application, applied to a ZigBee device in a smart lock system. The method includes the following steps:

[0080] Step 201: Receive and read the target door lock parameters via the ZigBee protocol.

[0081] In one possible implementation, the target door lock device receives management instructions from the server via the NB-IoT protocol, performs protocol conversion, and sends the target door lock parameters to ZigBee via the ZigBee protocol.

[0082] The NB-IoT protocol allows door lock devices to directly receive commands sent by the server through the base station, without needing a gateway. In Discontinuous Reception (DRX) mode, NB-IoT door lock devices wake up and receive commands from the server within fixed time periods. For example, hotel check-out time is typically 12:00 PM, and users can choose to periodically wake up the door lock devices between 12:00 PM and 12:30 PM to perform batch operations.

[0083] After receiving management instructions from the server via the NB-IoT protocol, if the received management instructions are batch management instructions (i.e., unified management instructions issued to at least two door lock devices simultaneously), the door lock device sends the target door lock parameters obtained from the instruction execution to the corresponding ZigBee device. Before sending the parameters, protocol conversion is required, and the target door lock parameters are sent to ZigBee via the ZigBee protocol.

[0084] Step 202: Based on the device information, form a self-organizing network with other ZigBee devices in the smart door lock system and obtain the nearest node.

[0085] The specific implementation of step 202 can be referred to step 102 above, and will not be repeated here in the embodiments of this application.

[0086] Step 203: Verify the management instructions received by the door lock device in the nearest node.

[0087] In one possible implementation, the management instruction carries header information indicating the operation type, which includes individual operations and batch operations. The target lock device sends target lock parameters to the ZigBee device when the operation type is batch operation. Individual operation refers to an operation performed on a single lock device, such as changing the password of a room lock; batch operation refers to a unified operation performed on at least two lock devices, such as updating access cards for 10 locks in batches.

[0088] Before performing parameter verification, the ZigBee device first verifies the management instructions received by the door lock device in the nearest node.

[0089] Step 204: In response to the operation type indicated by the header information in the management command as batch operation, perform door lock parameter verification with the nearest ZigBee device.

[0090] When the operation type is a standalone operation, ZigBee devices cannot determine whether the door lock device has correctly executed the instruction by cross-checking parameters. When the operation type is a batch operation, ZigBee devices can determine whether the door lock device has correctly executed the instruction by cross-checking whether the parameters are consistent. Therefore, when the operation type indicated by the header information in the management instruction is a batch operation, each ZigBee device checks the door lock parameters with the ZigBee device in the nearest node.

[0091] Step 205: Convert the ZigBee protocol to the NB-IoT protocol through the coordinator.

[0092] Since NB-IoT door lock devices can only receive information when they are woken up by themselves, ZigBee devices do not have the authority to actively wake up door lock devices to upload data. ZigBee devices are responsible for uploading the results.

[0093] In one possible implementation, in order to communicate with the server, the ZigBee device is equipped with a coordinator, which converts the ZigBee protocol into the NB-IoT protocol, and then uses the NB-IoT protocol to report the results.

[0094] Step 206: Based on the parameter verification results, report the command execution results to the server via the NB-IoT protocol.

[0095] Optionally, if the target lock parameters are consistent with the lock parameters of the nearest node, the ZigBee device determines that the instruction was executed correctly; if the target lock parameters are inconsistent with the lock parameters of the nearest node, the ZigBee device determines that the instruction was executed incorrectly.

[0096] ZigBee devices report command execution results to the server via the NB-IoT protocol. In one possible implementation, the server reads the command execution results; if the result is incorrect, it reissues the management command to the corresponding door lock device, or provides feedback to the user client based on the error reason to remind the user to perform device maintenance.

[0097] In this embodiment, by incorporating ZigBee components into the smart lock, the lock devices can communicate with each other and verify the lock parameters generated by executing management commands, making the smart lock system more secure and reliable. Furthermore, utilizing ZigBee devices for self-organizing network data transmission and verification offers advantages such as low power consumption, low latency, high reliability, and short range. The use of NB-IoT technology enables multiple devices to join the network without the need for a gateway, simplifying the data transmission process and improving parameter verification efficiency.

[0098] In one possible implementation, when the parameter verification results are inconsistent, it may be due to an error in the command execution result of the target door lock device, or it may be due to an error in the command execution result of the door lock device in the nearest node. In order to further determine the command execution status and avoid false alarms, the above step 104 further includes the following steps:

[0099] Step 1: In response to the target lock parameters being consistent with the lock parameters of the nearest node, report the instruction execution result (first instruction execution result) to the server to indicate that the instruction was executed correctly.

[0100] Step 2: In response to the inconsistency between the target lock parameters and the lock parameters of the nearest node, the ad hoc network matches the next nearest node and performs lock parameter verification with the ZigBee device of the next nearest node.

[0101] Step 3: In response to the inconsistency between the target door lock parameters and the door lock parameters of the next nearest node, report the instruction execution result (second instruction execution result) to the server to indicate the instruction execution error. The instruction execution result also includes the error reason, the MAC address and IP address of the target door lock device.

[0102] If the target lock parameters are consistent with the lock parameters of the nearest node, it means that both have correctly executed the management instructions issued by the server. Therefore, the ZigBee device can directly report the execution result of the first instruction.

[0103] If the target lock parameters are inconsistent with the lock parameters of the nearest node, it indicates that at least one of them has incorrectly executed the management command. To further determine whether the target lock parameters are incorrect, the ZigBee device needs to perform parameter verification with another ZigBee device at another node. In one possible implementation, in response to the inconsistency between the target lock parameters and the lock parameters of the nearest node, the ZigBee device self-organizes the network to match the next nearest node, which is the node with the shortest path to the target lock (excluding the nearest node). The ZigBee device then performs parameter verification again with the ZigBee device in the next nearest node. If they match, it indicates that the target lock device has correctly executed the command, and the lock device in the nearest node has an error. The device then reports the first command execution result to the server. If they do not match, it indicates that the target lock device has incorrectly executed the command, and the device reports the second command execution result to the server.

[0104] In another possible real-time approach, in response to a discrepancy between the target lock parameters and the lock parameters of the next nearest node, and the lock parameters of the next nearest node are consistent with those of the nearest node, the execution result of the second instruction is reported to the server. If, in response to a discrepancy between the target lock parameters and the lock parameters of the next nearest node, and the lock parameters of the next nearest node are inconsistent with those of the nearest node, the search continues for the next node to perform parameter checks until an incorrect node is identified.

[0105] The execution result of the second instruction also includes the error reason, the MAC address and IP address of the target door lock device. Based on the execution result of the second instruction, the server can resend the management instruction to the target door lock device separately, or report the faulty device and the error reason to the user client.

[0106] Please refer to Figure 3 This document illustrates a flowchart of a smart lock management method provided in an exemplary embodiment of this application, which is applied to a lock device in a smart lock system. The method includes the following steps:

[0107] Step 301: Receive management instructions from the server.

[0108] In one possible implementation, the smart lock system in this application mainly consists of a server, lock devices, ZigBee devices, and client devices. The client runs a smart lock management platform, through which users (e.g., hotel managers, dormitory administrators) can perform batch management operations, such as changing passwords. The client sends corresponding instructions to the server based on user actions. The server sends management instructions to the corresponding lock devices. Upon waking up, the lock devices receive the management instructions from the server.

[0109] Step 302: Update parameters based on management instructions to generate target door lock parameters.

[0110] The door lock device executes management commands issued by the server to generate target door lock parameters. For example, the door lock device executes a password modification command and generates a new door lock password according to the server's instructions.

[0111] Step 303: Send the target door lock parameters to the target ZigBee device. The target ZigBee device is connected to the door lock device. The target ZigBee device is used to verify the door lock parameters with the ZigBee device of the nearest node in the ad hoc network, and reports the command execution result to the server based on the parameter verification result.

[0112] After executing the management command, the door lock device sends the target door lock parameters to the target ZigBee device, enabling parameter verification between devices. For details on the parameter verification and result reporting process of the ZigBee device, please refer to [link / reference]. Figure 1 and Figure 2 Corresponding implementation examples.

[0113] In one possible implementation, the management instruction carries header information indicating the operation type, which includes individual operation and batch operation. When the operation type is batch operation, the door lock device sends the target door lock parameters to the target ZigBee device for data verification.

[0114] In this embodiment, by incorporating ZigBee components into the smart lock, the lock devices can communicate with each other. After the server issues a management command, the dynamic routing within the ZigBee device automatically selects nearby node devices, reads data, verifies the lock parameters, and uploads the command execution result to the server. This mutual verification of the lock parameters generated by the executed management commands enhances the security and reliability of the smart lock system. Furthermore, the use of ZigBee devices for self-organizing network data transmission and verification offers advantages such as low power consumption, low latency, high reliability, and short range.

[0115] Please refer to Figure 4 This illustration shows a flowchart of a smart lock management method provided in another exemplary embodiment of this application, which is applied to a door lock device in a smart lock system. The method includes the following steps:

[0116] Step 401: In response to the device wake-up time being reached, receive management instructions issued by the server via the NB-IoT protocol.

[0117] In one possible implementation, the target door lock device receives management commands from the server via the NB-IoT protocol. The NB-IoT protocol allows the door lock device to directly receive commands sent by the server through a base station, without needing a gateway device. In Discontinuous Reception (DRX) mode, the NB-IoT door lock device wakes up and receives commands from the server at fixed intervals. For example, hotel check-out time is typically 12:00, and users can choose to periodically wake up the door lock device between 12:00 and 12:30 to perform batch operations.

[0118] Step 402: Update parameters based on management instructions to generate target door lock parameters.

[0119] The specific implementation of step 402 can be referred to step 302 above, and will not be repeated here in the embodiments of this application.

[0120] Step 403: Convert the NB-IoT protocol to the ZigBee protocol through the coordinator.

[0121] After the door lock device receives the management command issued by the server via the NB-IoT protocol, if the received management command is a batch management command (i.e., a unified management command issued to at least two door lock devices at the same time), the door lock device sends the target door lock parameters obtained by the command execution to the corresponding ZigBee device. Before the parameters are sent, the protocol needs to be converted, and the NB-IoT protocol is converted to the ZigBee protocol by the coordinator.

[0122] Step 404: Send the target door lock parameters to the target ZigBee device via the ZigBee protocol.

[0123] After the door lock device converts the communication protocol from NB-IoT to ZigBee, it sends the target door lock parameters to the target ZigBee device via the ZigBee protocol, enabling the target ZigBee device to perform parameter verification in the self-organizing network.

[0124] In summary, the above embodiments, Figure 5 A parameter verification process for a smart door lock is shown.

[0125] First, the server sends out commands, adding identifiers to the header to distinguish between batch processing and individual processing. The batch processing identifier is "head": "batch", and the individual processing identifier is "head": "alone". The NB-IoT door lock wakes up at a set time, receives data, and first checks the header information. If it's a batch, after updating the data, the ZigBee device reads the door lock parameters and automatically obtains the nearest neighboring node device via self-organizing networking for parameter matching. When inconsistencies are found, the ZigBee device reports the door lock's IP address, MAC address, and error reason to the coordinator. The coordinator then converts the data to the NB-IoT protocol and reports the error. The server receives the data, parses it, and resends the commands using the device's IP address and MAC address.

[0126] Figure 6 This is a structural block diagram of a smart door lock management device provided in an exemplary embodiment of this application. The device includes the following structure:

[0127] The first receiving module 601 is used to receive and read the target door lock parameters sent by the target door lock device. The target door lock parameters are generated by the target door lock device executing the management instructions issued by the server. The target door lock device is connected to the ZigBee device.

[0128] The acquisition module 602 is used to acquire the nearest node of the ZigBee device in the self-organizing network, wherein the self-organizing network is the self-organizing network formed by the ZigBee devices in the smart door lock system;

[0129] The verification module 603 is used to verify the door lock parameters with the ZigBee device of the nearest node;

[0130] The first sending module 604 is used to report the instruction execution result to the server based on the parameter verification status. The instruction execution result is used to indicate whether the instruction execution of the target door lock device is correct or incorrect.

[0131] Optionally, the target door lock device receives the management command issued by the server via the NB-IoT protocol, performs protocol conversion, and sends the target door lock parameters to the ZigBee via the ZigBee protocol;

[0132] The first receiving module 601 is further configured to:

[0133] The target door lock parameters are received and read via the ZigBee protocol.

[0134] Optionally, the first transmitting module 604 is further configured to:

[0135] The ZigBee protocol is converted to the NB-IoT protocol using a coordinator.

[0136] Based on the parameter verification results, the execution result of the instruction is reported to the server via the NB-IoT protocol.

[0137] Optionally, the management instruction carries header information indicating the operation type, and the target door lock device is used to send the target door lock parameters to the ZigBee device when the operation type is a batch operation;

[0138] The inspection module 603 is also used for:

[0139] Verify the management command received by the door lock device in the nearest node;

[0140] In response to the operation type indicated by the header information in the management instruction being the batch operation, the door lock parameters are checked with the nearest ZigBee device.

[0141] Optionally, the first transmitting module 604 is further configured to:

[0142] In response to the inconsistency between the target lock parameters and the lock parameters of the nearest node, the ad hoc network matches the next nearest node and performs lock parameter verification with the ZigBee device of the next nearest node;

[0143] In response to the inconsistency between the target lock parameters and the lock parameters of the next nearest node, the system reports the instruction execution result to the server to indicate an instruction execution error. The instruction execution result also includes the error reason, the MAC address and IP address of the target lock device.

[0144] Figure 7 This is a structural block diagram of a smart door lock management device provided in an exemplary embodiment of this application. The device includes the following structure:

[0145] The second receiving module 701 is used to receive management instructions issued by the server;

[0146] The generation module 702 is used to update parameters based on the management instructions and generate target door lock parameters;

[0147] The second sending module 703 is used to send the target door lock parameters to the target ZigBee device. The target ZigBee device is connected to the door lock device. The target ZigBee device is used to perform door lock parameter verification with the ZigBee device of the nearest node in the ad hoc network, and report the instruction execution result to the server based on the parameter verification result.

[0148] Optionally, the second receiving module 701 is further configured to:

[0149] In response to the device wake-up time, the management command issued by the server is received via the NB-IoT protocol;

[0150] The second transmitting module 703 is further configured to:

[0151] The NB-IoT protocol is converted to the ZigBee protocol using a coordinator.

[0152] The target door lock parameters are sent to the target ZigBee device via the ZigBee protocol.

[0153] It should be noted that, in the embodiments of this application, if the above-described intelligent door lock management method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, 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 and includes several instructions to cause an electronic device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0154] Accordingly, this application provides a storage medium storing a computer program thereon, characterized in that the computer program, when executed by a processor, implements the steps in the smart lock management method provided in the above embodiments.

[0155] This application provides an electronic device; Figure 8 This is a schematic diagram of the composition structure of the electronic device provided in the embodiments of this application, such as... Figure 8As shown, the electronic device 800 includes: a processor 801, at least one communication bus 802, a user interface 803, at least one external communication interface 804, and a memory 805. The communication bus 802 is configured to enable communication between these components. The user interface 803 may include a display screen, and the external communication interface 804 may include standard wired and wireless interfaces. The processor 801 is configured to execute a program stored in the memory for a smart lock management method, to implement the steps in the smart lock management method provided in the above embodiment.

[0156] This application provides a smart door lock, including the electronic device, door lock device, and ZigBee device described in the above embodiments. The door lock device is used to control the opening and closing of the door lock and to receive and execute instructions sent by the server. The ZigBee device is used to communicate with other smart door locks to perform parameter verification. The electronic device is communicatively connected to the door lock device and the ZigBee device, and is used to control the door lock device to send door lock parameters to the ZigBee device, and to control the ZigBee device to perform parameter verification and report the instruction execution results.

[0157] It should be noted that the descriptions of the storage media, electronic devices, and cooking appliances described above are similar to the descriptions of the method embodiments described above, and have similar beneficial effects. For technical details not disclosed in the storage media and device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0158] This application provides a computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set. The at least one instruction, at least one program, code set, or instruction set is loaded and executed by a processor to implement a smart lock management method as described in the above embodiments.

[0159] This application provides a computer program product that runs on the processor of an electronic device, causing the electronic device to execute a smart lock management method as described in the above embodiments.

[0160] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above-described processes do not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above-described embodiments are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0161] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, object, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, object, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, object, or apparatus that includes that element.

[0162] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0163] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units. They may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0164] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0165] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, read-only memory (ROM), magnetic disks, or optical disks.

[0166] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a controller to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0167] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A management method for a smart door lock, characterized in that, The method is applied to ZigBee devices in a smart door lock system, and the method includes: Receive and read target lock parameters sent by the target lock device, wherein the target lock parameters are generated by the target lock device executing management instructions issued by the server, and the target lock device is connected to the ZigBee device; Find the nearest node of the ZigBee device in the self-organizing network, where the self-organizing network is the self-organizing network formed by the ZigBee devices in the smart door lock system; Perform door lock parameter verification with the ZigBee device of the nearest node; Based on the parameter verification results, the system reports the instruction execution results to the server. The instruction execution results are used to indicate whether the instruction execution of the target door lock device is correct or incorrect. The step of reporting the instruction execution result to the server based on parameter verification includes: In response to the inconsistency between the target lock parameters and the lock parameters of the nearest node, the ad hoc network matches the next nearest node and performs lock parameter verification with the ZigBee device of the next nearest node; In response to the inconsistency between the target door lock parameters and the door lock parameters of the next nearest node, an instruction execution result indicating an instruction execution error is reported to the server. The instruction execution result also includes the error reason, the MAC address and IP address of the target door lock device. Specifically, in response to the inconsistency between the target lock parameters and the lock parameters of the next nearest node, and the inconsistency between the lock parameters of the next nearest node and the lock parameters of the nearest node, the execution result of the second instruction is reported to the server. If the target lock parameter is inconsistent with the lock parameter of the next nearest node, and the lock parameter of the next nearest node is inconsistent with the lock parameter of the nearest node, then continue to search for the next node for parameter verification until the erroneous node is identified. The execution result of the second instruction also includes the error reason, the MAC address and IP address of the target door lock device.

2. The method according to claim 1, characterized in that, The target door lock device receives the management command issued by the server via the NB-IoT protocol, performs protocol conversion, and sends the target door lock parameters to the ZigBee via the ZigBee protocol; The process of receiving and reading the target door lock parameters sent by the target door lock device includes: The target door lock parameters are received and read via the ZigBee protocol.

3. The method according to claim 2, characterized in that, The step of reporting the instruction execution result to the server based on parameter verification includes: The ZigBee protocol is converted to the NB-IoT protocol using a coordinator. Based on the parameter verification results, the execution result of the instruction is reported to the server via the NB-IoT protocol.

4. The method according to any one of claims 1 to 3, characterized in that, The management instruction carries header information indicating the operation type, and the target door lock device is used to send the target door lock parameters to the ZigBee device when the operation type is a batch operation. The door lock parameter verification of the ZigBee device with the nearest node includes: Verify the management command received by the door lock device in the nearest node; In response to the operation type indicated by the header information in the management instruction being the batch operation, the door lock parameters are checked with the nearest ZigBee device.

5. A management method for a smart door lock, characterized in that, The method is applied to a door lock device in a smart door lock system, and the method includes: Receive management instructions from the server; Based on the management instructions, the parameters are updated to generate the target door lock parameters; The target ZigBee device sends the target door lock parameters to the target ZigBee device, which is connected to the door lock device. The target ZigBee device is used to verify the door lock parameters with the ZigBee device of the nearest node in the ad hoc network, and reports the instruction execution result to the server based on the parameter verification result. The step of reporting the instruction execution result to the server based on parameter verification includes: In response to the inconsistency between the target lock parameters and the lock parameters of the nearest node, the ad hoc network matches the next nearest node and performs lock parameter verification with the ZigBee device of the next nearest node; In response to the inconsistency between the target door lock parameters and the door lock parameters of the next nearest node, an instruction execution result indicating an instruction execution error is reported to the server. The instruction execution result also includes the error reason, the MAC address and IP address of the target door lock device. Specifically, in response to the inconsistency between the target lock parameters and the lock parameters of the next nearest node, and the inconsistency between the lock parameters of the next nearest node and the lock parameters of the nearest node, the execution result of the second instruction is reported to the server. If the target lock parameter is inconsistent with the lock parameter of the next nearest node, and the lock parameter of the next nearest node is inconsistent with the lock parameter of the nearest node, then continue to search for the next node for parameter verification until the erroneous node is identified. The execution result of the second instruction also includes the error reason, the MAC address and IP address of the target door lock device.

6. The method according to claim 5, characterized in that, The management instructions received from the receiving server include: In response to the device wake-up time, the management command issued by the server is received via the NB-IoT protocol; Sending the target door lock parameters to the target ZigBee device includes: The NB-IoT protocol is converted to the ZigBee protocol using a coordinator. The target door lock parameters are sent to the target ZigBee device via the ZigBee protocol.

7. A management device for an intelligent door lock, characterized in that, The device includes: The first receiving module is used to receive and read the target lock parameters sent by the target lock device. The target lock parameters are generated by the target lock device executing the management instructions issued by the server. The target lock device is connected to the ZigBee device. The acquisition module is used to acquire the nearest node of the ZigBee device in the self-organizing network, wherein the self-organizing network is the self-organizing network formed by the ZigBee devices in the smart door lock system; The verification module is used to verify the door lock parameters with the ZigBee device of the nearest node; The first sending module is used to report the instruction execution result to the server based on the parameter verification, and the instruction execution result is used to indicate whether the target door lock device executed the instruction correctly or incorrectly. The first sending module is further configured to: In response to the inconsistency between the target lock parameters and the lock parameters of the nearest node, the ad hoc network matches the next nearest node and performs lock parameter verification with the ZigBee device of the next nearest node; In response to the inconsistency between the target door lock parameters and the door lock parameters of the next nearest node, an instruction execution result indicating an instruction execution error is reported to the server, and the instruction execution result also includes the error reason, the MAC address and IP address of the target door lock device; Specifically, in response to the inconsistency between the target lock parameters and the lock parameters of the next nearest node, and the inconsistency between the lock parameters of the next nearest node and the lock parameters of the nearest node, the execution result of the second instruction is reported to the server. If the target lock parameter is inconsistent with the lock parameter of the next nearest node, and the lock parameter of the next nearest node is inconsistent with the lock parameter of the nearest node, then continue to search for the next node for parameter verification until the erroneous node is identified. The execution result of the second instruction also includes the error reason, the MAC address and IP address of the target door lock device.

8. A management device for an intelligent door lock, characterized in that, The device includes: The second receiving module is used to receive management instructions issued by the server; The generation module is used to update parameters based on the management instructions and generate target door lock parameters; The second sending module is used to send the target door lock parameters to the target ZigBee device. The target ZigBee device is connected to the door lock device. The target ZigBee device is used to perform door lock parameter verification with the ZigBee device of the nearest node in the ad hoc network, and report the instruction execution result to the server based on the parameter verification result. The step of reporting the instruction execution result to the server based on parameter verification includes: In response to the inconsistency between the target lock parameters and the lock parameters of the nearest node, the ad hoc network matches the next nearest node and performs lock parameter verification with the ZigBee device of the next nearest node; In response to the inconsistency between the target door lock parameters and the door lock parameters of the next nearest node, an instruction execution result indicating an instruction execution error is reported to the server. The instruction execution result also includes the error reason, the MAC address and IP address of the target door lock device. Specifically, in response to the inconsistency between the target lock parameters and the lock parameters of the next nearest node, and the inconsistency between the lock parameters of the next nearest node and the lock parameters of the nearest node, the execution result of the second instruction is reported to the server. If the target lock parameter is inconsistent with the lock parameter of the next nearest node, and the lock parameter of the next nearest node is inconsistent with the lock parameter of the nearest node, then continue to search for the next node for parameter verification until the erroneous node is identified. The execution result of the second instruction also includes the error reason, the MAC address and IP address of the target door lock device.

9. An electronic device, characterized in that, The electronic device includes a memory and a processor. The memory stores a computer program, which, when executed by the processor, performs a smart lock management method as described in any one of claims 1 to 4, or a smart lock management method as described in claim 5 or 6.

10. A smart door lock, characterized in that, The smart door lock includes the electronic device, door lock device, and ZigBee device as described in claim 9, wherein the door lock device is used to control the opening and closing of the door lock, and to receive and execute instructions sent by the server, the ZigBee device is used to communicate with other smart door locks to perform parameter verification, the electronic device is communicatively connected to the door lock device and the ZigBee device, and is used to control the door lock device to send door lock parameters to the ZigBee device, and to control the ZigBee device to perform parameter verification and report the instruction execution results.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, at least one program, code set, or instruction set is loaded and executed by a processor to implement a smart lock management method as described in any one of claims 1 to 4, or a smart lock management method as described in claim 5 or 6.

12. A computer program product, characterized in that, The computer program product runs on the processor of a computer device, causing the computer device to execute a smart lock management method as described in any one of claims 1 to 4, or a smart lock management method as described in claim 5 or 6.

Images