[go: up one dir, main page]

CN116012981A - Lockset management method and device and computer readable storage medium - Google Patents

Lockset management method and device and computer readable storage medium Download PDF

Info

Publication number
CN116012981A
CN116012981A CN202211640680.4A CN202211640680A CN116012981A CN 116012981 A CN116012981 A CN 116012981A CN 202211640680 A CN202211640680 A CN 202211640680A CN 116012981 A CN116012981 A CN 116012981A
Authority
CN
China
Prior art keywords
information
target
lock
database server
lockset
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211640680.4A
Other languages
Chinese (zh)
Inventor
马铮
吕楚键
梁健民
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sgsg Science & Technology Co ltd Zhuhai
Original Assignee
Sgsg Science & Technology Co ltd Zhuhai
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sgsg Science & Technology Co ltd Zhuhai filed Critical Sgsg Science & Technology Co ltd Zhuhai
Priority to CN202211640680.4A priority Critical patent/CN116012981A/en
Publication of CN116012981A publication Critical patent/CN116012981A/en
Pending legal-status Critical Current

Links

Images

Landscapes

  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The embodiment of the application discloses a lockset management method, a lockset management device and a computer readable storage medium, which are used for improving the safety of locksets. The method comprises the following steps: when an activation instruction sent by a target lockset is received, activating information is generated according to the activation instruction; sending the activation information to the target lockset; receiving target lock information sent by the target lock; the target lock information is sent to a database server and a first blockchain node respectively, so that the database server stores the target lock information, and the first blockchain node adds the target lock information to a first blockchain; and verifying whether the target lockset information in the database server is tampered or not through the target lockset information in the first blockchain.

Description

Lockset management method and device and computer readable storage medium
Technical Field
The embodiment of the application relates to the technical field of locks, in particular to a lock management method, a lock management device and a computer readable storage medium.
Background
When the bank side needs to add the cash to the ATM at regular or irregular time, the bank side needs to open the lockset of the ATM at first so as to add the cash to the ATM. With the continuous development of society, locks adopting static passwords in automatic teller machines cannot meet the security requirements of banks, so dynamic password locks have been developed.
In the prior art, after a lock in an automatic teller machine is activated, a server changes a password of the lock every certain time, when a user inputs the password to open the lock, the lock uploads the password input by the user to the server for verification, and the server determines whether to unlock the lock by comparing the received password with a password updated last locally.
However, such a lock management method, although the password is constantly changed, may have serious consequences of the lock being illegally opened if the password that is updated last locally by the server is tampered with.
Disclosure of Invention
The embodiment of the application provides a lockset management method, a lockset management device and a computer readable storage medium, which can improve the safety of locksets.
An embodiment of the present application provides a lock management method, including:
when an activation instruction sent by a target lockset is received, activating information is generated according to the activation instruction;
sending the activation information to the target lockset;
receiving target lock information sent by the target lock;
the target lock information is sent to a database server and a first blockchain node respectively, so that the database server stores the target lock information, and the first blockchain node adds the target lock information to a first blockchain;
and verifying whether the target lockset information in the database server is tampered or not through the target lockset information in the first blockchain.
Optionally, the verifying whether the target lock information in the database server is tampered with by the target lock information in the first blockchain includes:
receiving an unlocking request sent by the target lockset;
according to the unlocking request query, target lockset information in the database server and target lockset information in the first blockchain are respectively obtained;
and determining whether the target lockset information in the database server is tampered according to the target lockset information in the first blockchain.
Optionally, if it is determined that the target lock information in the database server is not tampered, the lock management method further includes:
generating an unlocking code according to the unlocking request and target lockset information in the database server;
and sending the unlocking code to the target lockset so that the target lockset can be unlocked according to the unlocking code.
Optionally, before the receiving the unlocking request sent by the target lock, the lock management method further includes:
receiving a banknote adding task request, wherein the banknote adding task request comprises banknote adding information, a target banknote box identifier and a target lock identifier, the target banknote box identifier is the identification information of the target banknote box, the target lock identifier is the identification information of the target lock, and the target banknote box is associated with the target lock;
generating banknote adding task information according to the banknote adding task request;
and respectively sending the banknote adding task information to the database server and the second block chain node so that the database server stores the banknote adding task information, and the second block chain node adds the banknote adding task information to the second block chain.
Optionally, after receiving the unlocking request sent by the target lock, the lock management method further includes:
respectively acquiring banknote adding task information in the database server and banknote adding task information in the second block chain according to the unlocking request;
and determining whether the banknote adding task information in the database server is tampered according to the banknote adding task information in the second block chain.
Optionally, after the banknote adding task information is sent to the database server and the second blockchain node, the lock management method further includes:
receiving a banknote adding task tracing request;
respectively acquiring banknote adding task information in the database server and banknote adding task information in the second block chain according to the banknote adding task tracing request;
and determining whether the banknote adding task information in the database server is tampered according to the banknote adding task information in the second block chain.
Optionally, the target lock information includes sensitive information, and before the target lock information is sent to the database server and the first blockchain node, the lock management method further includes:
encrypting the sensitive information to obtain a first hash value of the sensitive information;
and replacing the plaintext of the sensitive information in the target lockset information with the first hash value.
A second aspect of the embodiments of the present application provides a lock management device, including:
the generation unit is used for generating activation information according to the activation instruction when receiving the activation instruction sent by the target lockset;
the first sending unit is used for sending the activation information to the target lockset;
the first receiving unit is used for receiving target lockset information sent by the target lockset;
the second sending unit is used for sending the target lock information to a database server and a first block chain node respectively, so that the database server stores the target lock information, and the first block chain node adds the target lock information to a first block chain;
and the verification unit is used for verifying whether the target lockset information in the database server is tampered or not through the target lockset information in the first blockchain.
A third aspect of the embodiments of the present application provides a lock management device, including:
a processor, a memory, an input-output unit, and a bus;
the processor is connected with the memory, the input/output unit and the bus;
the memory stores a program, and the processor invokes the program to execute the lock management method according to any one of the first aspect and any one of the possible implementation manners of the first aspect.
A fourth aspect of the embodiments of the present application provides a computer-readable storage medium, where a program is stored, where the program when executed on a computer causes the computer to perform the lock management method according to the first aspect and any one of possible implementation manners of the first aspect.
From the above technical solutions, the embodiments of the present application have the following advantages:
according to the lockset management method, after target lockset information sent by the target lockset is received, the target lockset information is sent to the database server, and the target lockset information is also sent to the first blockchain node, so that the database server stores the target lockset information, and the first blockchain node stores the target lockset information to the first blockchain. And finally verifying whether the target lockset information in the database server is tampered or not through the target lockset information in the first blockchain node. After the target lock information stored in the database server is tampered, due to the characteristic that the data stored in the blockchain is difficult to modify, tamper-proof verification can be performed on the target lock information stored in the database server through the target lock information in the first blockchain, so that the fact that the target lock information stored in the database server is tampered is found, and the improvement of safety of the target lock is facilitated.
Drawings
FIG. 1 is a flow chart of an embodiment of a lock management method according to an embodiment of the present application;
FIG. 2 is a flowchart of another embodiment of a lock management method according to an embodiment of the present application;
FIG. 3 is a schematic structural view of an embodiment of a lock management device according to the present application;
FIG. 4 is a schematic structural view of another embodiment of a lock management device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of another embodiment of a lock management device according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a lockset management method, a lockset management device and a computer readable storage medium, which are used for improving the safety of locksets.
The method of the present application may be applied to a server, a terminal, or other devices with logic processing capabilities, which is not limited in this application. For convenience of description, the following description will take an execution subject as a service server as an example.
Embodiments in the present application will be described below with reference to the accompanying drawings.
Referring to fig. 1, an embodiment of lock management in the present application includes:
101. when an activation instruction sent by a target lockset is received, activating information is generated according to the activation instruction;
when the service server receives the activation instruction, the service server may generate activation information according to the activation instruction. The activation instruction comprises information such as a target lockset identifier, a lockset activation state and the like, and after the service server receives the activation instruction, the service server can acquire the information such as the target lockset identifier, the lockset activation state and the like and then generate activation information according to the information such as the target lockset identifier, the lockset activation state and the like.
102. Sending the activation information to the target lockset;
after the service server generates the activation information, the activation information may be sent to the target lock, and after the target lock receives the activation information from the service server, the data update may be performed according to the activation information, so as to complete activation of the target lock.
103. Receiving target lock information sent by the target lock;
after the target lockset is activated, target lockset information is generated, the generated target lockset information is sent to a service server, and the service server can receive the target lockset information. The target lockset information comprises information such as a locking code, a target lockset identifier, a lockset activation state and the like. The locking code is generated after each time the target lock is locked or after the target lock is activated, and the locking code generated by each time the target lock is not the same. After each time of locking code generation, the target lockset generates target lockset information according to the locking code and sends the target lockset information to the service server.
104. The target lock information is sent to a database server and a first blockchain node respectively, so that the database server stores the target lock information, and the first blockchain node adds the target lock information to a first blockchain;
after generating the target lock information, the service server may send the target lock information to the database server and the first blockchain node, respectively, so that the database server stores the target lock information, and simultaneously, the first blockchain node stores the target lock information to the first blockchain.
A blockchain is a chain of blocks one by one. Each block holds certain information which is linked in a chain according to the time sequence of their respective generation. This chain is kept in all the service servers, and the whole blockchain is safe as long as one service server can work in the whole system. These traffic servers, referred to as nodes in the blockchain system, provide storage space and computational support for the entire blockchain system. If the information in the blockchain is to be modified, it is necessary to sign consent of more than half of the nodes and modify the information in all the nodes, which are usually held in different subject hands, so it is an extremely difficult thing to tamper with the information in the blockchain. Compared with the traditional network, the blockchain has two main core characteristics: firstly, the data is difficult to tamper, and secondly, the data is decentralised. Based on the two characteristics, the information recorded by the blockchain is more real and reliable, and can help solve the problem that people are not trusted each other.
105. And verifying whether the target lockset information in the database server is tampered or not through the target lockset information in the first blockchain.
In this embodiment, after receiving the target lock information sent by the target lock, the service server sends the target lock information to the database server, and in addition, sends the target lock information to the first blockchain node, so that the database server stores the target lock information, and further, the first blockchain node stores the target lock information to the first blockchain. And finally verifying whether the target lockset information in the database server is tampered or not through the target lockset information in the first blockchain node. After the target lock information stored in the database server is tampered, due to the characteristic that the data stored in the blockchain is difficult to modify, tamper-proof verification can be performed on the target lock information stored in the database server through the target lock information in the first blockchain, so that the fact that the target lock information stored in the database server is tampered is found, and the improvement of safety of the target lock is facilitated.
Referring to fig. 2, another embodiment of lock management in the present application includes:
201. when an activation instruction sent by a target lockset is received, activating information is generated according to the activation instruction;
202. sending the activation information to the target lockset;
203. receiving target lock information sent by the target lock;
in this embodiment, steps 201 to 203 are similar to steps 101 to 103 in the previous embodiment, and are not repeated here.
204. Encrypting the sensitive information to obtain a first hash value of the sensitive information;
the target lockset information comprises a plurality of pieces of information, wherein the information can be divided into general information and sensitive information, the general information is information which can be directly disclosed, and the sensitive information is information which is not suitable for being directly disclosed. Wherein, the unlocking password belongs to sensitive information. Since the sensitive information is not suitable for direct disclosure, it cannot be unsuitable for directly sending the plaintext of the unlocking password to the database server and the first blockchain node. Therefore, before sending the target lockset information to the database server and the first block link, the service server can encrypt the sensitive information in the target lockset information, so as to obtain a first hash value of the sensitive information. It should be noted that the sensitive information does not necessarily include only the unlocking password, and therefore, the first hash value is not one value, but is a set of hash values corresponding to all information in the sensitive information.
205. Replacing the plaintext of the sensitive information in the target lockset information with the first hash value;
after the service server obtains the first hash value, the plaintext of the sensitive information in the target lockset information can be replaced by the first hash value, so that the sensitive information stored in the target lockset information is the hash value and is not the plaintext, and even if the target lockset information is intercepted or stolen by personnel in a bank, the person who steals or intercepts the target lockset information cannot read the plaintext through the first hash value, thereby being beneficial to improving the safety when the target lockset is activated.
206. The target lock information is sent to a database server and a first blockchain node respectively, so that the database server stores the target lock information, and the first blockchain node adds the target lock information to a first blockchain;
in this embodiment, step 206 is similar to step 104 in the previous embodiment, and will not be described again.
207. Receiving a banknote adding task request;
in practical applications, after the atm associated with the target lock is used for a period of time, the pre-stored banknotes in the banknote boxes are gradually reduced, so that the banknote boxes in the atm are usually required to be subjected to banknote adding treatment in order not to affect normal use. Therefore, when the banknote adding requirement exists, the banknote adding manager can send a banknote adding task request to the service server through the personal computer, the tablet personal computer, the smart phone and other equipment, and the service server can receive the banknote adding task request. The banknote adding task request comprises banknote adding manager information, a target banknote box identifier, a target lockset identifier and the like. The target banknote box identification is identification information of the target banknote box (such as the serial number of the target banknote box); the target lockset is identified as the identification information of the target lockset (such as the number of the target lockset); the banknote adding information is information of the banknote adding person, and can comprise information such as name, gender, age, fingerprint, iris, face and the like of the banknote adding person, and the banknote adding information is not limited in specific places; the banknote adding manager information is information of the banknote adding manager, and can include information such as name, gender, age, fingerprint, iris, face and the like of the banknote adding manager, and is not limited in specific terms herein. The banknote adding job request may also include other information, and is not limited in particular herein.
208. Generating banknote adding task information according to the banknote adding task request;
after receiving the banknote adding task request, the service server can generate corresponding banknote adding task information according to the information included in the banknote adding task request, wherein the banknote adding task information also includes banknote adding task numbers, and the banknote adding task numbers are used for representing the uniqueness of the banknote adding task information.
209. The banknote adding task information is sent to the database server and a second block chain node respectively, so that the banknote adding task information is stored in the database server, and the banknote adding task information is added to the second block chain by the second block chain node;
after generating the banknote adding task information, the service server can send the banknote adding task information to the database server and the second block chain node respectively, so that the database server stores the banknote adding task information, and the second block chain link node stores the banknote adding task information to the second block chain. Thus, even if the database server crashes, the corresponding banknote adding task information can be found by querying the second block chain.
210. Receiving a banknote adding task tracing request;
in practical applications, a user may need to query the banknote adding task information, for example, after the banknote adding manager sends a banknote adding task request to the service server and the service server generates the banknote adding task information according to the received banknote adding task request, the banknote adding manager cannot query the banknote adding task information on the database server through the service server for some unknown reasons. When the situation occurs, the banknote adding manager can send a banknote adding task tracing request to the service server, and the service server can receive the banknote adding task tracing request. The banknote adding task traceability request comprises one or more of banknote adding information, task number, banknote adding manager information, target lockset information and the like, and the information is used as a query condition of the service server.
211. Respectively acquiring banknote adding task information in the database server and banknote adding task information in the second block chain according to the banknote adding task tracing request;
after receiving the banknote adding task tracing request, the service server can respectively inquire the database server and the second block chain according to the information in the banknote adding task tracing request, and respectively acquire banknote adding task information from the database server and the second block chain.
212. Determining whether the banknote adding task information in the database server is tampered according to the banknote adding task information in the second block chain;
after the banknote adding task information is obtained from the database server and the second blockchain respectively, the service server can compare the banknote adding task information in the database server with the banknote adding task information of the second blockchain, so that whether the banknote adding task information is consistent with the banknote adding task information of the second blockchain is determined. If the banknote adding task information is consistent, the service server can determine that banknote adding task information in the database server is not tampered, and the reason that the banknote adding manager cannot inquire the banknote adding task information may be that the network signal is poor, the service server is busy, the equipment is incompatible and the like; if the banknote adding task information is inconsistent, the service server can determine that banknote adding task information in the database server is tampered.
In this embodiment, the service server may perform tracing of the banknote adding task information, so as to facilitate quick determination of whether the data in the database server is tampered.
213. Receiving an unlocking request sent by the target lockset;
in practical application, before the bill adder opens the target lockset, firstly, unlocking verification needs to be performed, and besides unlocking password verification, the unlocking verification can further comprise identity verification of the bill adder, bill adding task verification and the like, and the method is not limited in detail herein. After the bill adder passes the verification, the target lockset sends an unlocking request to the service server, and the service server can receive the unlocking request from the target lockset.
214. Respectively acquiring banknote adding task information in the database server and banknote adding task information in the second block chain according to the unlocking request;
after receiving the unlocking request, the service server can obtain banknote adding task information from the database server and the second block chain according to information in the unlocking request, such as a target lockset identifier, a task number and the like.
215. Determining whether the banknote adding task information in the database server is tampered according to the banknote adding task information in the second block chain;
after the banknote adding task information is obtained from the database server and the second blockchain respectively, the service server can compare the banknote adding task information of the database server with the banknote adding task information of the second blockchain, so that whether the banknote adding task information of the database server is consistent with the banknote adding task information of the second blockchain is determined. If the banknote adding task information is consistent with the banknote adding task information, the service server can determine that banknote adding task information in the database server is not tampered; if the banknote adding task information is inconsistent, the service server can determine that banknote adding task information in the database server is tampered.
In this embodiment, before the cashier opens the target lock, the service server may trace the banknote adding task information to determine whether the banknote adding task information in the database server is tampered, which is beneficial to improving the security of the target lock.
216. Respectively acquiring target lockset information in the database server and target lockset information in the first blockchain according to the unlocking request;
after receiving the unlocking request query, the service server can acquire target lock information from the database server and the first blockchain according to information in the unlocking request query, such as target lock identification and the like.
217. Determining whether target lockset information in the database server is tampered according to the target lockset information in the first blockchain;
after the target lock information is obtained from the database server and the first blockchain respectively, the service server can compare the target lock information of the database server with the target lock information of the first blockchain, so as to determine whether the target lock information of the database server and the target lock information of the first blockchain are consistent. If the target lockset information is consistent with the target lockset information, the service server can determine that the target lockset information in the database server is not tampered; if the target lockset information is inconsistent, the service server can determine that the target lockset information in the database server is tampered.
In this embodiment, before the bill adder opens the target lock, the service server may trace the source of the target lock information to determine whether the target lock information in the database server is tampered with, which is beneficial to improving the security of the target lock.
218. Generating an unlocking code according to the unlocking request and target lockset information in the database server;
after the service server receives the unlocking request and performs tamper-proof verification on the target lock information in the database server, if the service server determines that the target lock information in the database server is not tampered, an unlocking code can be generated according to the unlocking request and the target lock information in the database server. The unlocking code is used for unlocking the target lockset.
219. And sending the unlocking code to the target lockset so that the target lockset can be unlocked according to the unlocking code.
After the service server generates the unlocking code, the unlocking code can be sent to the target lockset so as to unlock the target lockset. After the target lockset receives the unlocking code, unlocking operation can be performed according to the unlocking code, so that service personnel can perform subsequent service flow. Further, after the service personnel re-locks the target lock, the target lock generates a new locking code, generates target lock information according to the newly generated locking code, and sends the target lock information to the service server, so that the service server performs tamper-proof verification when receiving a new unlocking request.
Referring to fig. 3, an embodiment of a lock management device in an embodiment of the present application includes:
a generating unit 301, configured to generate activation information according to an activation instruction sent by a target lock when the activation instruction is received;
a first sending unit 302, configured to send the activation information to the target lock;
a first receiving unit 303, configured to receive target lock information sent by the target lock;
a second sending unit 304, configured to send the target lock information to a database server and a first blockchain node, respectively, so that the database server stores the target lock information, and the first blockchain node adds the target lock information to a first blockchain;
and a verification unit 305, configured to verify whether the target lock information in the database server is tampered with by using the target lock information in the first blockchain.
In this embodiment, after receiving the target lock information sent by the target lock, the first receiving unit 303 sends the target lock information to the first blockchain node in addition to sending the target lock information to the database server, so that the database server stores the target lock information, and further, the first blockchain node stores the target lock information to the first blockchain. The last verification unit 305 verifies whether the target lockset information in the database server is tampered with by the target lockset information in the first blockchain node. After the target lock information stored in the database server is tampered, due to the characteristic that the data stored in the blockchain is difficult to modify, tamper-proof verification can be performed on the target lock information stored in the database server through the target lock information in the first blockchain, so that the fact that the target lock information stored in the database server is tampered is found, and the improvement of safety of the target lock is facilitated.
Referring to fig. 4, another embodiment of the lock management apparatus in the embodiment of the present application includes:
a generating unit 401, configured to generate activation information according to an activation instruction sent by a target lock when the activation instruction is received;
a first sending unit 402, configured to send the activation information to the target lock;
a first receiving unit 403, configured to receive target lock information sent by the target lock;
a second sending unit 404, configured to send the target lock information to a database server and a first blockchain node, respectively, so that the database server stores the target lock information, and the first blockchain node adds the target lock information to a first blockchain;
and a verification unit 405, configured to verify whether the target lock information in the database server is tampered with by using the target lock information in the first blockchain.
In this embodiment, the lock management apparatus further includes an unlocking unit 406, a banknote adding unit 407, a first tamper resistant unit 408, a second tamper resistant unit 409, and an encryption unit 410.
An encryption unit 410 for:
encrypting the sensitive information to obtain a first hash value of the sensitive information;
and replacing the plaintext of the sensitive information in the target lockset information with the first hash value.
Unlocking unit 406 for:
generating an unlocking code according to the unlocking request and target lockset information in the database server;
and sending the unlocking code to the target lockset so that the target lockset can be unlocked according to the unlocking code.
A banknote adding unit 407 for:
receiving a banknote adding task request, wherein the banknote adding task request comprises banknote adding information, a target banknote box identifier and a target lock identifier, the target banknote box identifier is the identification information of the target banknote box, the target lock identifier is the identification information of the target lock, and the target banknote box is associated with the target lock;
generating banknote adding task information according to the banknote adding task request;
and respectively sending the banknote adding task information to the database server and the second block chain node so that the database server stores the banknote adding task information, and the second block chain node adds the banknote adding task information to the second block chain.
A first tamper resistant unit 408 for:
respectively acquiring banknote adding task information in the database server and banknote adding task information in the second block chain according to the unlocking request;
and determining whether the banknote adding task information in the database server is tampered according to the banknote adding task information in the second block chain.
A second tamper resistant unit 409 for:
receiving a banknote adding task tracing request;
respectively acquiring banknote adding task information in the database server and banknote adding task information in the second block chain according to the banknote adding task tracing request;
and determining whether the banknote adding task information in the database server is tampered according to the banknote adding task information in the second block chain.
In this embodiment, the verification unit 405 is specifically configured to:
receiving an unlocking request sent by the target lockset;
respectively acquiring target lockset information in the database server and target lockset information in the first blockchain according to the unlocking request;
and determining whether the target lockset information in the database server is tampered according to the target lockset information in the first blockchain.
In this embodiment, the functions of the units correspond to the steps in the embodiment shown in fig. 2, and are not described herein.
Referring to fig. 5, another embodiment of a lock management device in an embodiment of the present application includes:
a processor 501, a memory 502, an input-output unit 503, and a bus 504;
the processor 501 is connected to the memory 502, the input/output unit 503, and the bus 504;
the memory 502 has a program stored thereon, and the processor 501 invokes the program to perform the steps of the embodiments shown in fig. 1-2.
In this embodiment, the functions of the processor 501 correspond to the steps in the embodiments shown in fig. 1 to 2, and are not described herein.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM, random access memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Claims (10)

1. A method of lock management, comprising:
when an activation instruction sent by a target lockset is received, activating information is generated according to the activation instruction;
sending the activation information to the target lockset;
receiving target lock information sent by the target lock;
the target lock information is sent to a database server and a first blockchain node respectively, so that the database server stores the target lock information, and the first blockchain node adds the target lock information to a first blockchain;
and verifying whether the target lockset information in the database server is tampered or not through the target lockset information in the first blockchain.
2. The lock management method of claim 1, wherein the verifying whether the target lock information in the database server is tampered with by the target lock information in the first blockchain comprises:
receiving an unlocking request sent by the target lockset;
respectively acquiring target lockset information in the database server and target lockset information in the first blockchain according to the unlocking request;
and determining whether the target lockset information in the database server is tampered according to the target lockset information in the first blockchain.
3. The lock management method according to claim 2, wherein if it is determined that the target lock information in the database server has not been tampered with, the lock management method further comprises:
generating an unlocking code according to the unlocking request and target lockset information in the database server;
and sending the unlocking code to the target lockset so that the target lockset can be unlocked according to the unlocking code.
4. The lock management method according to claim 2, wherein prior to receiving the unlock request sent by the target lock, the lock management method further comprises:
receiving a banknote adding task request, wherein the banknote adding task request comprises banknote adding information, a target banknote box identifier and a target lock identifier, the target banknote box identifier is the identification information of the target banknote box, the target lock identifier is the identification information of the target lock, and the target banknote box is associated with the target lock;
generating banknote adding task information according to the banknote adding task request;
and respectively sending the banknote adding task information to the database server and the second block chain node so that the database server stores the banknote adding task information, and the second block chain node adds the banknote adding task information to the second block chain.
5. The lock management method according to claim 4, wherein after receiving the unlock request sent by the target lock, the lock management method further comprises:
respectively acquiring banknote adding task information in the database server and banknote adding task information in the second block chain according to the unlocking request;
and determining whether the banknote adding task information in the database server is tampered according to the banknote adding task information in the second block chain.
6. The lock management method according to claim 4, wherein after the sending the banknote adding task information to the database server and the second blockchain node, the lock management method further comprises:
receiving a banknote adding task tracing request;
respectively acquiring banknote adding task information in the database server and banknote adding task information in the second block chain according to the banknote adding task tracing request;
and determining whether the banknote adding task information in the database server is tampered according to the banknote adding task information in the second block chain.
7. The lock management method according to any one of claims 1 to 6, wherein the target lock information includes sensitive information, the lock management method further comprising, prior to transmitting the target lock information to a database server and a first blockchain node, respectively:
encrypting the sensitive information to obtain a first hash value of the sensitive information;
and replacing the plaintext of the sensitive information in the target lockset information with the first hash value.
8. A lock management apparatus, comprising:
the generation unit is used for generating activation information according to the activation instruction when receiving the activation instruction sent by the target lockset;
the first sending unit is used for sending the activation information to the target lockset;
the first receiving unit is used for receiving target lockset information sent by the target lockset;
the second sending unit is used for sending the target lock information to a database server and a first block chain node respectively, so that the database server stores the target lock information, and the first block chain node adds the target lock information to a first block chain;
and the verification unit is used for verifying whether the target lockset information in the database server is tampered or not through the target lockset information in the first blockchain.
9. A lock management apparatus, comprising:
a processor, a memory, an input-output unit, and a bus;
the processor is connected with the memory, the input/output unit and the bus;
the memory stores a program, and the processor calls the program to execute the lock management method according to any one of claims 1 to 7.
10. A computer-readable storage medium having a program stored thereon, which when executed on a computer, causes the computer to perform the lock management method as claimed in any one of claims 1 to 7.
CN202211640680.4A 2022-12-20 2022-12-20 Lockset management method and device and computer readable storage medium Pending CN116012981A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211640680.4A CN116012981A (en) 2022-12-20 2022-12-20 Lockset management method and device and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211640680.4A CN116012981A (en) 2022-12-20 2022-12-20 Lockset management method and device and computer readable storage medium

Publications (1)

Publication Number Publication Date
CN116012981A true CN116012981A (en) 2023-04-25

Family

ID=86037468

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211640680.4A Pending CN116012981A (en) 2022-12-20 2022-12-20 Lockset management method and device and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN116012981A (en)

Similar Documents

Publication Publication Date Title
US12149515B2 (en) Distributed key secret for rewritable blockchain
CA1124864A (en) Cryptographic architecture for use with a high security personal identification system
US20210266170A1 (en) System and method of trustless confidential positive identification and de-anonymization of data using blockchain
CN109478280A (en) Method and system for realizing block chain
CN111327564B (en) Access method and device for alliance chain
EP3821586A1 (en) Systems and methods for secure custodial service
JP2010165323A (en) Biometric authentication method and system
CN113704718B (en) Computer data protection system based on identity authentication
WO2020000777A1 (en) Method and apparatus for acquiring individual credit information on the basis of block chain, and computer device
CN106936588A (en) A kind of trustship method, the apparatus and system of hardware controls lock
CN111768523A (en) CTID-based NFC intelligent door lock unlocking method, system, equipment and medium
CN111461731A (en) Block chain monitoring system and method applied to financial transactions
CN114499875A (en) Service data processing method and device, computer equipment and storage medium
CN116057554A (en) Method for managing transaction data sets, participant unit, transaction register and payment system
CN118395477A (en) Electronic license user information security and privacy protection method
Ahmed et al. A self-sovereign identity architecture based on blockchain and the utilization of customer’s banking cards: The case of bank scam calls prevention
CN112328975A (en) A product software authorization management method, terminal device and medium
Said et al. A multi-factor authentication-based framework for identity management in cloud applications
CN109190725B (en) A kind of RFID two-way authentication method
CN115296794A (en) Key management method and device based on block chain
US12147952B2 (en) Method, terminal, monitoring entity, and payment system for managing electronic coin datasets
CN114969786A (en) Block chain-based insurance function data processing method, node and system
CN114786160A (en) NFC label key management system
CN116012981A (en) Lockset management method and device and computer readable storage medium
CN113487766B (en) Unlocking method and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination