Lock end log storage method and system
By connecting the lock end to the cloud server, the problem of insufficient storage space of the lock end log and inconvenient acquisition of log data is solved, efficient storage and convenient access of the lock end log data is realized, and the prediction and processing capabilities of fault problems are improved.
Patent Information
- Application Number
- CN202411314875.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-20
- Publication Date
- 2024-12-10
AI Technical Summary
The existing lock-end log storage technology has problems such as small storage volume and inconvenience of maintenance personnel to obtain log data, especially because the lock-end memory space is limited, it is impossible to effectively store a large amount of log data, and maintenance personnel need to obtain log data on site to understand the fault problem.
By connecting the lock end to the cloud server, the trigger event will be stored as a run log if it is normal when it runs. If it is abnormal, a fault log will be generated and uploaded to the cloud server with the previous run log for storage, which will take advantage of the larger storage space and convenience of the cloud server. Access method to improve the storage of log data and the convenience of maintenance personnel to obtain log data.
It improves the storage volume of lock-end log data and the convenience of maintenance personnel to obtain log data, allowing cloud servers to independently store fault logs and operation logs, helping maintenance personnel understand and prepare to solve lock-end fault problems in advance.
Smart Images
Figure CN119109774A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of lock-end log storage, and in particular to a lock-end log storage method and system. Background Art
[0002] Electronic intelligent locks are often used in homes, hotels, offices and other places. During the operation of the lock, hardware failures, software failures, network failures, etc. may occur, and these failures will be recorded and stored by the lock in the form of logs. However, due to the limited size of the lock, its memory space is small, so it is impossible to store a large amount of log data. Moreover, maintenance personnel often need to go to the site to obtain the log data stored in the lock to understand the fault problems in the log data. Therefore, the existing lock log storage has the technical defects of small storage capacity and inconvenience for maintenance personnel to obtain the log data of the lock. Summary of the invention
[0003] The purpose of the present application is to overcome the shortcomings and deficiencies in the prior art and to provide a lock-end log storage method and system, which can increase the storage capacity of the lock-end log data and improve the convenience for maintenance personnel to obtain the lock-end log data.
[0004] A first aspect of an embodiment of the present application provides a lock end log storage method, which is applied to a lock end, wherein the lock end is connected to a cloud server; the method comprises:
[0005] operating in response to a triggering event;
[0006] If the operation based on the triggering event is normal, storing the operation record based on the triggering event as an operation log;
[0007] If the operation based on the triggering event is abnormal, the operation record based on the triggering event is used as a fault log, and the fault log and the previous operation log of the fault log are uploaded to the cloud server, so that the fault log and the previous operation log of the fault log are stored by the cloud server.
[0008] A second aspect of an embodiment of the present application provides a lock-end log storage method, which is applied to a cloud server, wherein the cloud server is connected to the lock-end, and the method includes:
[0009] Receive the fault log uploaded by the lock end and the previous operation log of the fault log; the fault log is an operation record of the lock end running abnormally based on the trigger event, and the operation log is an operation record of the lock end running normally based on the trigger event; when the lock end runs abnormally based on the trigger event, upload the fault log and the previous operation log of the fault log;
[0010] The fault log and a previous operation log of the fault log are stored.
[0011] A third aspect of an embodiment of the present application provides a lock end log storage system, comprising: a lock end and a cloud server, wherein the lock end is connected to the cloud server;
[0012] The lock end operates in response to the trigger event, and if the operation is normal based on the trigger event, the operation record based on the trigger event is stored as an operation log; if the operation is abnormal based on the trigger event, the operation record based on the trigger event is used as a fault log, and the fault log and the previous operation log of the fault log are uploaded to the cloud server;
[0013] The cloud server receives and stores the fault log and a previous operation log of the fault log.
[0014] Compared with the related art, the present application can generate operation log and fault log data of the operation record of the lock end in response to the triggering event, and when the fault log occurs, upload the fault log and the previous operation log of the fault log to the cloud server, so as to store the fault log and operation log through the cloud server. Since the cloud server and the lock end exist independently in physical space, the size of the cloud server will not be limited by the size of the lock end, and the cloud server can also use hardware devices with larger storage capacity. Therefore, by storing the fault log and operation log of the lock end through the cloud server, the storage capacity of the log data of the lock end can be increased; at the same time, maintenance personnel can access the cloud server through the networked device to obtain the fault log and operation log of the lock end, which improves the convenience for maintenance personnel to obtain the log data of the lock end, and helps maintenance personnel to understand the fault problem in advance based on the fault log and operation log of the lock end, so as to make adequate preparations for the maintenance of the lock end.
[0015] In order to provide a clearer understanding of the present application, the specific implementation of the present application will be described below in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] Figure 1 The present invention is a flowchart of a lock end log storage method applied to a lock end according to an embodiment of the present application.
[0017] Figure 2 This is a flowchart of a lock-end log storage method applied to a cloud server according to an embodiment of the present application.
[0018] Figure 3 This is a schematic diagram of device connections of a lock-end log storage system according to an embodiment of the present application.
[0019] 100. Lock-end log storage system; 101. Lock-end; 102. Cloud server. DETAILED DESCRIPTION
[0020] In order to make the objectives, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.
[0021] It should be clear that the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the embodiments of the present application.
[0022] When the following description relates to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. In the description of the present application, it should be understood that the terms "first", "second", "third", etc. are only used to distinguish similar objects, and do not have to be used to describe a specific order or sequence, nor can they be understood as indicating or implying relative importance. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood according to the specific circumstances. The singular forms of "a", "said" and "the" used in the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. The words "if" / "if" used herein can be interpreted as "at the time of" or "when" or "in response to determination".
[0023] In addition, in the description of this application, unless otherwise specified, "plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.
[0024] See also Figure 1 , which is a flow chart of a lock end log storage method applied to a lock end according to the first embodiment of the present application, including:
[0025] S11: Execute in response to a triggering event.
[0026] The triggering events may include, but are not limited to, unlocking, locking, feature information entry, feature information deletion, brightness adjustment, lock terminal display theme setting, lock terminal broadcast sound setting, etc. The feature information may include, but are not limited to, fingerprint features, voiceprint features, face features, and eye features.
[0027] S12: If the operation based on the triggering event is normal, the operation record based on the triggering event is stored as an operation log.
[0028] Since the data storage space of the lock end is limited, the lock end can store the operation log by updating the log data. For example, when the lock end executes a new trigger event, the lock end operates normally, the lock end will delete the previous operation log, and keep the operation log corresponding to the new trigger event to improve the utilization efficiency of the storage space of the lock end.
[0029] S13: If the operation based on the triggering event is abnormal, the operation record based on the triggering event is used as a fault log, and the fault log and the previous operation log of the fault log are uploaded to the cloud server, so that the fault log and the previous operation log of the fault log are stored by the cloud server.
[0030] The lock end uses the operation record as a fault log, which means that the lock end generates a fault log based on the operation record. Optionally, in addition to uploading the fault log to the cloud server, the lock end can also store the fault log locally on the lock end. At this time, due to the limited data storage space of the lock end, the lock end can be set with an upper limit on the storage number of fault logs. When the storage number of fault logs reaches the upper limit, the latest fault log will replace the oldest stored fault log to improve the utilization efficiency of the storage space of the lock end.
[0031] Among them, in order to reduce the excessive log data stored in the cloud server, the lock end will upload the fault log and the previous operation log of the fault log to the cloud server only when the fault log appears. Since the operation log is the log data of the normal operation of the lock end, the data of the operation log is generally not much different. Therefore, only uploading the previous operation log of the fault log to the cloud server can effectively save the storage space occupied by the log data on the cloud server. And because the fault log is the log data directly related to the abnormal operation of the lock end, it needs to be uploaded to the cloud server every time a fault log appears, so that the maintenance personnel can directly view the fault log on the cloud server, and compare the fault log with the operation log to determine the fault problem of the lock end.
[0032] Compared with the related art, the present application can generate operation log and fault log data of the operation record of the lock end in response to the triggering event, and when the fault log occurs, upload the fault log and the previous operation log of the fault log to the cloud server, so as to store the fault log and operation log through the cloud server. Since the cloud server and the lock end exist independently in physical space, the size of the cloud server will not be limited by the size of the lock end, and the cloud server can also use hardware devices with larger storage capacity. Therefore, by storing the fault log and operation log of the lock end through the cloud server, the storage capacity of the log data of the lock end can be increased; at the same time, maintenance personnel can access the cloud server through the networked device to obtain the fault log and operation log of the lock end, which improves the convenience for maintenance personnel to obtain the log data of the lock end, and helps maintenance personnel to understand the fault problem in advance based on the fault log and operation log of the lock end, so as to make adequate preparations for the maintenance of the lock end.
[0033] In a feasible embodiment, the step of uploading the fault log and the previous operation log of the fault log to the cloud server in S13 includes:
[0034] S131: Upload the fault log, the previous operation log of the fault log, and the encryption instruction to the cloud server, so that the cloud server encrypts and stores the fault log and the operation log based on the encryption instruction.
[0035] Among them, the encryption instruction may include an encryption key, so that the cloud server encrypts and stores the fault log and operation log according to the encryption key. When the lock end uploads the fault log and operation log, whether to upload the encryption instruction can be set by the manufacturer or maintenance personnel. For example, if the manufacturer or maintenance personnel activates the log encryption function of the lock end, the lock end will upload the encryption instruction to the cloud server when uploading the fault log and operation log. After the cloud server encrypts and stores the fault log and operation log, the maintenance personnel need to perform decryption operations according to the corresponding decryption key to accurately obtain the fault log and operation log.
[0036] In this embodiment, when uploading the fault log and the operation log, the encryption instruction is also uploaded to the cloud server, which can drive the cloud server to encrypt and store the fault log and the operation log, thereby improving the security of the log storage.
[0037] In a feasible embodiment, the step of uploading the fault log and the previous operation log of the fault log to the cloud server in S13 includes:
[0038] S132: Upload the fault log, the previous operation log of the fault log, and the access restriction instruction to the cloud server, so that the cloud server adds access restriction to the stored fault log and the operation log based on the access restriction instruction.
[0039] The access restrictions corresponding to the access restriction instructions can be set by the manufacturer or maintenance personnel. For example, if the manufacturer or maintenance personnel activates the log access restriction function of the lock end, the lock end will upload the access restriction instructions to the cloud server when uploading the fault log and operation log. The cloud server adds access restrictions to the stored fault logs and operation logs. The maintenance personnel need to pass the access restrictions according to the pre-granted access rights to accurately obtain the fault logs and operation logs.
[0040] In this embodiment, when uploading the fault log and the operation log, the access restriction instruction is also uploaded to the cloud server, which can drive the cloud server to add access restrictions to the fault log and the operation log, thereby improving the security of log storage.
[0041] In a feasible embodiment, the cloud server includes a first storage unit and a second storage unit; the step of uploading the fault log and a previous operation log of the fault log to the cloud server in S13 includes:
[0042] S133: Upload the fault log, the previous operation log of the fault log, and the backup instruction to the cloud server, so that the cloud server stores the fault log and the operation log in the first storage unit based on the backup instruction, and stores the backup data of the fault log and the operation log in the second storage unit
[0043] Among them, the first storage unit is a general term for storage devices used to store the fault log and the operation log. The first storage unit can store multiple fault logs and multiple operation logs through several storage devices to realize a distributed storage method, which can prevent a large amount of log data from being affected by problems with the storage device and improve the security of log storage.
[0044] The second storage unit is a general term for storage devices used to store backup data of fault logs and operation logs. The second storage unit can also store backup data of multiple fault logs and multiple operation logs through multiple storage devices. When the log stored in the first storage unit is lost, data recovery can be performed based on the backup data stored in the second storage unit. When the first storage unit is damaged, the backup data stored in the second storage unit can be directly used, thereby maintaining the continuity and integrity of the log data.
[0045] In this embodiment, the continuity and integrity of the stored log data can be maintained through the first storage unit and the second storage unit.
[0046] In a feasible embodiment, the step of uploading the fault log and the previous operation log of the fault log to the cloud server in S13 includes:
[0047] S134: Upload the fault log, the previous operation log of the fault log and the score acquisition instruction to the cloud server, so that the cloud server scores the fault log based on the score acquisition instruction, the operation log and the fault log, and sends the operation log and the fault log to a preset terminal device when the fault log score is higher than a preset score threshold; wherein the fault log score is used to indicate the severity of the fault problem in the fault log.
[0048] The scoring acquisition instruction can be set by the manufacturer or maintenance personnel. For example, if the manufacturer or maintenance personnel activates the fault scoring function of the lock terminal, the lock terminal will upload the scoring acquisition instruction to the cloud server simultaneously when uploading the fault log and operation log, so that the cloud server will send the operation log and fault log to the preset terminal device when the fault log score is higher than the preset scoring threshold. The preset terminal device is a networked device used by the maintenance personnel.
[0049] The cloud server obtains the fault log score based on the operation log and fault log, which can be achieved through the following steps:
[0050] S1341: According to a preset content association relationship, a plurality of groups of associated fault contents and a plurality of independent fault contents having an association relationship are obtained from the plurality of fault contents; each group of associated fault contents includes at least two associated fault contents.
[0051] The content association relationship may be set by the manufacturer or maintenance personnel. For example, it may be set that there is an association relationship between the fault contents corresponding to different unlocking methods.
[0052] S1342: According to the preset association relationship and the correspondence between the operation symbols, the operation function corresponding to each group of associated fault contents is obtained.
[0053] The operation function may be a variety of operation methods such as multiplication of values, addition of squared values, etc.
[0054] S1343: Obtaining the fault correlation score of each group of associated fault contents according to each of the operation functions and the fault reference value of each of the associated fault contents.
[0055] The fault correlation score of the group of associated fault contents can be obtained by directly substituting the fault reference value of each associated fault content of the same group into the operation function for operation.
[0056] S1344: Obtain the fault log score according to the fault association score of each group of associated fault contents and the fault reference value of the independent fault contents.
[0057] The fault log score is the sum of the fault correlation score of each group of associated fault contents and the fault reference value of each independent fault content.
[0058] For example, if a lock terminal supports four unlocking methods, if two unlocking methods fail in the trigger event, that is, the trigger event corresponds to a fault log, and the fault log includes two fault contents of the two unlocking methods failing to run. Considering that there are multiple unlocking methods, if only one fault content is the unlocking method, the impact on unlocking is small. However, when two or more fault contents are all unlocking methods, the impact on unlocking is large. At this time, the fault correlation score of the associated fault content can be obtained through multiplication, square addition and other correlation relationships to calculate the fault log score. The severity of the fault problem corresponding to the fault log can be judged in combination with the correlation of the fault content.
[0059] In this embodiment, the severity of the fault problem corresponding to the fault log can be judged according to the fault log score, so that the fault log with serious fault problem is sent to the terminal device to remind the maintenance personnel to give priority to solving the fault problem corresponding to the fault log.
[0060] See also Figure 2 The second embodiment of the present application provides a lock-end log storage method, which is applied to a cloud server, and the cloud server is connected to the lock-end. The method includes:
[0061] S21: Receive the fault log uploaded by the lock end and the previous operation log of the fault log; the fault log is an operation record of the abnormal operation of the lock end based on the triggering event, and the operation log is an operation record of the normal operation of the lock end based on the triggering event; when the lock end operates abnormally based on the triggering event, the fault log and the previous operation log of the fault log are uploaded.
[0062] S22: storing the fault log and a previous operation log of the fault log.
[0063] In a feasible embodiment, the step of S21: receiving the fault log uploaded by the lock end and the previous operation log of the fault log includes:
[0064] S211: receiving the fault log, the previous operation log of the fault log and the encryption instruction uploaded by the lock end;
[0065] The step of storing the fault log and the operation log in S22 includes:
[0066] S221: Based on the encryption instruction, encrypt and store the fault log and the operation log.
[0067] In a feasible embodiment, the step of S21: receiving the fault log uploaded by the lock end and the previous operation log of the fault log includes:
[0068] S212: receiving the fault log, the previous operation log of the fault log, and the access restriction instruction uploaded by the lock end;
[0069] The step of storing the fault log and the operation log in step S22 includes:
[0070] S222: Based on the access restriction instruction, add access restriction to the stored fault log and the operation log.
[0071] In a feasible embodiment, the cloud server includes a first storage unit and a second storage unit;
[0072] The step of S21: receiving the fault log uploaded by the lock end and the previous operation log of the fault log, comprises:
[0073] S213: receiving the fault log, the previous operation log of the fault log, and the backup instruction uploaded by the lock end;
[0074] The step of storing the fault log and the operation log in step S22 includes:
[0075] S223: Based on the backup instruction, the fault log and the operation log are stored in a first storage unit, and the backup data of the fault log and the operation log are stored in a second storage unit.
[0076] In a feasible embodiment, the step of S21: receiving the fault log uploaded by the lock end and the previous operation log of the fault log includes:
[0077] S214: receiving the fault log, the previous operation log of the fault log, and the score acquisition instruction uploaded by the lock end;
[0078] The step S22 of storing the fault log and the operation log includes:
[0079] S224: Based on the score acquisition instruction, scoring the fault log according to the operation log and the fault log includes:
[0080] S2241: Compare the operation log and the fault log to obtain the fault content of the fault log.
[0081] S2242: Obtaining the fault reference value of each fault content according to the preset corresponding relationship between the fault content and the fault reference value.
[0082] S2243: Obtain a fault log score according to the fault reference value of each fault content; the fault log score is used to indicate the severity of the fault problem in the fault log.
[0083] Among them, S2243: may include:
[0084] S22431: According to a preset content association relationship, a plurality of groups of associated fault contents and a plurality of independent fault contents having an association relationship are obtained from the plurality of fault contents; each group of associated fault contents includes at least two associated fault contents.
[0085] S22432: According to the preset association relationship and the correspondence between the operation symbols, obtain the operation function corresponding to each group of associated fault contents.
[0086] S22433: Obtaining the fault correlation score of each group of associated fault contents according to each of the operation functions and the fault reference value of each of the associated fault contents.
[0087] S22434: Obtain the fault log score according to the fault association score of each group of associated fault contents and the fault reference value of the independent fault contents.
[0088] S225: If the fault log score is higher than a preset score threshold, the operation log and the fault log are sent to a preset terminal device.
[0089] It should be noted that the lock-end log storage method provided in the second embodiment of the present application belongs to the same concept as the lock-end log storage method in the first embodiment of the present application. The implementation process thereof is detailed in the first embodiment and will not be repeated here.
[0090] See also Figure 3 , the third embodiment of the present application provides a lock end log storage system 100, including: a lock end 101 and a cloud server 102, wherein the lock end 101 is connected to the cloud server 102;
[0091] The lock end 101 operates in response to the trigger event. If the operation is normal based on the trigger event, the operation record based on the trigger event is stored as an operation log; if the operation is abnormal based on the trigger event, the operation record based on the trigger event is used as a fault log, and the fault log and the previous operation log of the fault log are uploaded to the cloud server 102;
[0092] The cloud server 102 receives and stores the fault log and a previous operation log of the fault log.
[0093] It should be noted that the lock-end log storage system 100 provided in the third embodiment of the present application only uses the division of the above-mentioned functional modules as an example when executing the lock-end log storage method. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the lock-end log storage system 100 provided in the third embodiment of the present application and the lock-end log storage method of the first embodiment of the present application are of the same concept. The implementation process thereof is detailed in the method embodiment and will not be repeated here.
[0094] The device embodiments described above are merely illustrative, wherein the components described as separate parts may or may not be physically separated, and the parts displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present application. Ordinary technicians in this field can understand and implement it without creative work.
[0095] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.
[0096] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the function selected in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 function selected in a box or multiple boxes.
[0097] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 steps for the function selected in a box or multiple boxes.
[0098] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0099] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.
[0100] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0101] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0102] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.
Claims
1. A lock-end log storage method, characterized in that: Applied to a lock terminal, the lock terminal is connected to a cloud server; the method includes: operating in response to a triggering event; If the operation based on the triggering event is normal, storing the operation record based on the triggering event as an operation log; If the operation based on the triggering event is abnormal, the operation record based on the triggering event is used as a fault log, and the fault log and the previous operation log of the fault log are uploaded to the cloud server, so that the fault log and the previous operation log of the fault log are stored by the cloud server.
2. The lock-end log storage method according to claim 1, characterized in that: The step of uploading the fault log and a previous operation log of the fault log to the cloud server includes: The fault log, the previous operation log of the fault log and the encryption instruction are uploaded to the cloud server, so that the cloud server encrypts and stores the fault log and the operation log based on the encryption instruction.
3. The lock-end log storage method according to claim 1, characterized in that: The step of uploading the fault log and a previous operation log of the fault log to the cloud server includes: The fault log, the previous operation log of the fault log and the access restriction instruction are uploaded to the cloud server, so that the cloud server adds access restriction to the stored fault log and the operation log based on the access restriction instruction.
4. The lock-end log storage method according to claim 1, characterized in that: The cloud server includes a first storage unit and a second storage unit; the step of uploading the fault log and a previous operation log of the fault log to the cloud server includes: The fault log, the previous operation log of the fault log and the backup instruction are uploaded to the cloud server, so that the cloud server stores the fault log and the operation log in a first storage unit based on the backup instruction, and stores the backup data of the fault log and the operation log in a second storage unit.
5. The lock-end log storage method according to claim 1, characterized in that: The step of uploading the fault log and a previous operation log of the fault log to the cloud server includes: The fault log, the previous operation log of the fault log and the score acquisition instruction are uploaded to the cloud server, so that the cloud server scores the fault log based on the score acquisition instruction, the operation log and the fault log, and sends the operation log and the fault log to a preset terminal device when the fault log score is higher than a preset score threshold; wherein the fault log score is used to indicate the severity of the fault problem in the fault log.
6. A lock-end log storage method, characterized in that: Applied to a cloud server, the cloud server is connected to a lock terminal, and the method includes: Receive the fault log uploaded by the lock end and the previous operation log of the fault log; the fault log is an operation record of the lock end running abnormally based on the trigger event, and the operation log is an operation record of the lock end running normally based on the trigger event; when the lock end runs abnormally based on the trigger event, upload the fault log and the previous operation log of the fault log; The fault log and a previous operation log of the fault log are stored.
7. The lock-end log storage method according to claim 6, characterized in that: The step of receiving the fault log uploaded by the lock end and the previous operation log of the fault log includes: Receiving the fault log, the previous operation log of the fault log and the encryption instruction uploaded by the lock end; The step of storing the fault log and the operation log comprises: Based on the encryption instruction, the fault log and the operation log are encrypted and stored.
8. The lock-end log storage method according to claim 6, characterized in that: The step of receiving the fault log uploaded by the lock end and the previous operation log of the fault log includes: Receiving the fault log, the previous operation log of the fault log and the access restriction instruction uploaded by the lock end; The step of storing the fault log and the operation log comprises: Based on the access restriction instruction, access restrictions are added to the stored fault log and the operation log.
9. The lock-end log storage method according to claim 6, characterized in that: The cloud server includes a first storage unit and a second storage unit; The step of receiving the fault log uploaded by the lock end and the previous operation log of the fault log includes: Receiving the fault log, the previous operation log of the fault log and the backup instruction uploaded by the lock end; The step of storing the fault log and the operation log comprises: Based on the backup instruction, the fault log and the operation log are stored in a first storage unit, and backup data of the fault log and the operation log are stored in a second storage unit.
10. A lock-end log storage system, characterized in that: include: A lock terminal and a cloud server, wherein the lock terminal is connected to the cloud server; The lock end operates in response to the trigger event, and if the operation is normal based on the trigger event, the operation record based on the trigger event is stored as an operation log; if the operation is abnormal based on the trigger event, the operation record based on the trigger event is used as a fault log, and the fault log and the previous operation log of the fault log are uploaded to the cloud server; The cloud server receives and stores the fault log and a previous operation log of the fault log.