Operation safety management and control system and method, and storage medium

Abstract

Provided are an operation safety management and control system and method, and a storage medium. A background device issues task information of a first operation task for an intelligent lock to a key management device; the key management device issues the first operation task to an intelligent key on the basis of the task information, wherein every time the first operation task is issued, a different task sub-identifier will be allocated; every time the intelligent key executes the first operation task on the intelligent lock, the intelligent key generates an operation record on the basis of the corresponding task sub-identifier; and finally, the key management device / background device obtains the corresponding operation record from the intelligent key. By flexibly allocating different task sub-identifiers during task issuing, a complex scenario in which multiple operations are performed on a same lock can be covered, an operation process can be effectively recorded, the safety of the operation process can be improved, and experience accumulation and positive prevention for safety accidents can be realized.

Description

Operational safety control system, method and storage medium Technical Field

[0001] The present application relates to the field of industrial safety technology, and in particular to an operation safety management and control system, method, and storage medium. Background Art

[0002] Under the traditional energy production model, because the process involves personnel from different disciplines working simultaneously or overlapping, production teams are divided into operation teams and maintenance teams to ensure worker safety. These teams are further subdivided by specialty, such as boiler teams, electrical teams, and thermal engineering teams. When overseeing the same equipment, each team has its own distinct tasks. To ensure their own safety, each team implements safety measures on the equipment before maintenance and removes them after completing their tasks.

[0003] Currently, mechanical locks are primarily used as a safety measure in practical operations, resulting in multiple mechanical locks being installed on the same equipment. On one hand, the mechanical keys corresponding to the mechanical locks present a certain risk of mutual unlocking. Unlocking errors can easily lead to safety accidents such as casualties and equipment damage. On the other hand, mechanical locks are operated manually by operators, making the process difficult to effectively record and document. This makes it impossible to record and analyze operational data, hindering the accumulation of accident experience and the prevention of safety incidents.

[0004] Therefore, there is an urgent need for a technical solution that can effectively avoid the risk of mechanical locks opening each other and support data recording of the operation process. Summary of the Invention

[0005] In order to achieve the above objectives, the present application provides an operation safety management and control system, method and storage medium, which support data recording of equipment operation processes, and realize experience accumulation and active prevention of safety accidents while improving operation safety.

[0006] In a first aspect, the present application provides an operation security management and control system, which includes: a background device, a key management device, a smart lock and a smart key;

[0007] The background device is used to: send task information of the smart lock to the key management device, where the task information describes a first operation task for the smart lock;

[0008] The key management device is configured to: assign a task sub-identifier corresponding to the first operation task each time the first operation task is issued to the smart key according to the task information, wherein the assigned task sub-identifier is different each time;

[0009] The smart key is used to: perform a first operation task on the smart lock, and generate an operation record of the first operation task according to the task sub-identifier assigned this time;

[0010] The key management device / the background device is further configured to obtain one or more operation records of the first operation task from the smart key.

[0011] In a possible implementation, data is transmitted between the background device in the operation safety management and control system and the smart key via wireless communication.

[0012] In a second aspect, an operation safety management method for the operation safety management system provided in the first aspect is provided, the method comprising:

[0013] S1. The background device sends task information of the smart lock to the key management device, where the task information describes a first operation task for the smart lock;

[0014] S2. The key management device assigns a task sub-identifier corresponding to the first operation task to the smart key each time the first operation task is issued according to the task information, wherein the assigned task sub-identifier is different each time;

[0015] S3. The smart key performs a first operation task on the smart lock, and generates an operation record of the first operation task according to the task sub-identifier assigned this time;

[0016] S4. The key management device / the backend device obtains one or more operation records of the first operation task from the smart key.

[0017] In one possible implementation, the method further includes:

[0018] The background device directly sends the task information of the smart lock to the smart key.

[0019] In one possible implementation, before step S1, the method further includes:

[0020] The background device creates the first operation task and generates the task information according to the device identification of the smart lock and the type of the operation to be performed;

[0021] The task information includes: device identifications of one or more smart locks, types of one or more operations to be performed, a task identification of the first operation task, and multiple task sub-identities corresponding to the task identification.

[0022] In one possible implementation, step S3 includes:

[0023] S31, the smart key parses the received first operation task to determine the task identifier of the first operation task, the type of the operation to be performed, the first task sub-identifier, and the device identifier of the smart lock;

[0024] S32: If the device identifier read from the smart lock is consistent with the device identifier corresponding to the first operation task, the smart key sends an operation instruction to the smart lock according to the type of the operation to be performed, the task identifier, and the first task sub-identifier;

[0025] S33: The smart lock performs data analysis according to the operation instruction and returns the execution result of the first operation task to the smart key;

[0026] S34. The smart key generates a first operation record of the first operation task according to the execution result.

[0027] In one possible implementation, step S33 includes:

[0028] A. The smart lock analyzes the type of operation to be performed in the operation instruction, wherein the type includes: unlocking, locking, executing a security measure, and releasing a security measure;

[0029] B. The smart lock reads its own historical records, performs logical judgment on the type based on the task identifier and task sub-identifier contained in the historical records, and determines the execution result of the first operation task.

[0030] In one possible implementation, step B includes:

[0031] B1. When the type is execution of a security measure, if the historical record does not contain both the first task sub-identifier and the task identifier carried in the operation instruction, the smart lock executes the security measure and stores the first task sub-identifier and the task identifier, and then returns a result of completion of the security measure execution; if the historical record contains both the first task sub-identifier and the task identifier carried in the operation instruction, the smart lock returns a result of failure to execute the security measure;

[0032] B2. When the type is to release the security measure, if the historical record contains both the first task sub-identifier and the task identifier carried in the operation instruction, the smart lock device releases the security measure and deletes the first task sub-identifier and the task identifier in the historical record, and returns a result of completing the security measure release; if the historical record does not contain both the first task sub-identifier and the task identifier carried in the operation instruction, the smart lock device returns a result of failing to release the security measure;

[0033] B3. When the type is unlocking / locking, if the historical record does not include any task identifier and does not include any task sub-identifier, the smart lock performs the unlocking / locking operation and returns the unlocking / locking completion result; if the historical record includes any task identifier or any task sub-identifier, the smart lock returns the unlocking / locking failure result.

[0034] In one possible implementation, step S31 includes:

[0035] Parsing the received first operation task to determine the task identifier, time information, type of operation to be performed, first task sub-identifier, and device identifier of the smart lock of the first operation task;

[0036] Determine whether the first operation task exceeds a time range based on the time information, and read the device identification of the smart lock if it does not exceed the time range.

[0037] In one possible implementation, the method further includes:

[0038] The key management device charges multiple smart keys in the operation safety management and control system and manages the multiple smart keys in the operation safety management and control system.

[0039] In a third aspect, an electronic device is provided, comprising a memory and a processor, wherein the memory stores at least one program, and the at least one program is executed by the processor to implement the operation security management method provided in the second aspect.

[0040] In a fourth aspect, a computer-readable storage medium is provided, in which at least one program is stored, and the at least one program is executed by a processor to implement the operation security management method provided in the second aspect.

[0041] The technical solution provided by this application includes at least the following technical effects:

[0042] In the technical solution of this application, a backend device sends task information about a smart lock to a key management device. The key management device then sends a first operation task to the smart key based on the task information, assigning a different task sub-identifier each time it sends the first operation task. Each time the smart key performs the first operation task on the smart lock, an operation record is generated based on the corresponding task sub-identifier. Finally, the key management device / backend device retrieves the corresponding operation record from the smart key. By flexibly assigning different task sub-identifiers when sending tasks, complex scenarios involving multiple operations on the same lock can be covered, effectively recording the operation process, improving the safety of the operation process, and accumulating experience and proactively preventing safety incidents.

[0043] BRIEF DESCRIPTION OF THE DRAWINGS

[0044] FIG1 is a schematic diagram of an operation safety management and control system provided in an embodiment of the present application;

[0045] FIG2 is a flow chart of an operation safety management method provided in an embodiment of the present application;

[0046] FIG3 is a flow chart of another operation safety management method provided in an embodiment of the present application;

[0047] FIG4 is a schematic diagram of the interaction between a smart key and a smart lock provided in an embodiment of the present application;

[0048] FIG5 is a flow chart of another operation safety management method provided in an embodiment of the present application;

[0049] FIG6 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application.

[0050] DETAILED DESCRIPTION

[0051] To further illustrate each embodiment, the present application provides drawings. These drawings are part of the disclosure of the present application, which are mainly used to illustrate the embodiments and can be used in conjunction with the relevant descriptions in the specification to explain the operating principles of the embodiments. With reference to these contents, a person of ordinary skill in the art should be able to understand other possible implementations and the advantages of the present application. The components in the figures are not drawn to scale, and similar component symbols are generally used to represent similar components. The term "at least one" in the present application means one or more, and the term "multiple" in the present application means two or more, for example, multiple tasks means two or more tasks.

[0052] The present application will now be further described with reference to the accompanying drawings and specific implementation methods.

[0053] The present application provides an operation safety management system, which includes: a backend device, a key management device, a smart lock, and a smart key. Figure 1 is a schematic diagram of an operation safety management system provided by an embodiment of the present application.

[0054] In one possible implementation, referring to FIG1 , the background device and the key management device are connected via Ethernet (e.g., via an RJ45 crystal connector), data can be transmitted between the background device and the smart key via wireless communication, and data can be transmitted between the key management device and the smart key via wired / wireless communication.

[0055] In an embodiment of the present application, the background device is used to: send task information of the smart lock to the key management device, and the task information describes the first operation task for the smart lock; the key management device is used to: assign a task sub-identifier corresponding to the first operation task each time the first operation task is sent to the smart key according to the task information, and the assigned task sub-identifier is different each time; the smart key is used to: execute the first operation task on the smart lock, and generate an operation record of the first operation task based on the task sub-identifier assigned this time; the key management device / background device is also used to: obtain one or more operation records of the first operation task from the smart key.

[0056] Specifically, the key management device receives task information issued by the backend device. The system includes multiple key management devices, each deployed in the production area of ​​each work team based on their division. The key management device is used to charge smart keys, issue tasks, receive operation records, and manage the device.

[0057] Specifically, the smart key can receive task information issued by the key management device or wirelessly obtain task information from the backend device. The smart key is used to perform operations on the smart lock (including unlocking, locking, executing security measures, and releasing security measures), and the generated operation records are returned to the key management device or backend device for storage.

[0058] In another possible implementation, the backend device also exchanges data with an external system via Ethernet (e.g., an RJ45 connector). The external system may be a remote cloud platform that manages operational safety across an entire campus, factory, or workshop, or a server in a central computer room. This external system is optional and is indicated by a dashed box in Figure 1.

[0059] For example, smart locks are a safety measure during the operation of industrial equipment. Before or after operating the industrial equipment, the operator operates the smart locks hung on the cabinet doors, box doors and other components of the industrial equipment to execute or release the safety measures.

[0060] In the operational safety management and control system provided by the embodiments of the present application, smart locks can replace mechanical locks as a safety measure. Smart locks support repeated operations, and one lock can be used to implement multiple security measures. Only when all security measures are released can the smart lock be opened. Replacing multiple mechanical locks with one smart lock can effectively avoid the problem of mismatched locks, reduce asset management, and improve ease of use. In addition, the operational safety management and control system provided by the present application flexibly assigns different task sub-identifiers when issuing tasks, which can cover complex scenarios where the same lock is operated multiple times, effectively records the operational process, improves the safety of the operational process, and can achieve experience accumulation and active prevention of safety accidents.

[0061] The following describes the operation safety management method provided by the embodiment of the present application in conjunction with the operation safety management system shown in Figure 1. Figure 2 is a flow chart of an operation safety management method provided by the embodiment of the present application. Referring to Figure 2, the operation safety management method includes the following steps S1 to S4, which are executed by the corresponding devices in the operation safety management system. S1. The background device sends the task information of the smart lock to the key management device.

[0062] In the embodiment of the present application, the task information describes a first operation task for the smart lock. The first operation task is, for example, unlocking, locking, executing a security measure, or releasing a security measure for the smart lock.

[0063] In a possible implementation, before sending the task information, the background device creates a first operation task and generates task information according to the device identification of the smart lock and the type of operation to be performed.

[0064] The task information includes: device identifications of one or more smart locks, types of one or more operations to be performed, a task identification of the first operation task, and multiple task sub-identities corresponding to the task identification.

[0065] Specifically, the task information also includes a work ticket identifier, which is used to distinguish different work tickets issued for smart locks. The task information also includes: time information and operator identification; the time information includes the task start time and task end time, which can be used to determine whether the first operation task currently to be executed has expired; the operator identification can be used to verify the identity of the operator performing the corresponding operation task. This embodiment of the application provides a parameter definition table for task information issued by the background device, see Table 1.

[0066] Table 1

[0067]

[0068] S2. The key management device assigns a task sub-identifier corresponding to the first operation task each time the first operation task is issued to the smart key according to the task information.

[0069] In this embodiment of the present application, the assigned task sub-identifier is different each time it is issued. Specifically, after the key management device obtains the task information of the first operation task, it can assign the first operation task to the smart key multiple times (the smart key assigned each time can be the same or different). Each time the first operation task is assigned to a smart key, a task sub-identifier is assigned to distinguish each first operation task.

[0070] For example, when the key management device assigns the first operation task to smart key A, it carries the task identifier (SID1) and the first task sub-identifier (SCID1) of the first operation task; when the key management device assigns the first operation task to smart key B, it carries the task identifier (SID1) and the first task sub-identifier (SCID1.1) of the first operation task.

[0071] In one possible implementation, the first operation task corresponds to a task identified by a work ticket identifier (TID);

[0072] When the key management device issues the first operation task to the smart key for the first time, it generates a copy of the first operation task (TID1.1), which includes the task identifier SID1 and the newly generated first task sub-identifier (SCID1.1), and issues it to the smart key. When the key management device issues the first operation task to the smart key for the second time, it generates a copy of the first operation task (TID1.2), which includes the task identifier SID1 and the newly generated second task sub-identifier (SCID1.2), and issues it to the smart key. Therefore, TID1.1 and TID1.2 are equivalent to work tickets for the same smart lock, but both work tickets perform the first operation task, meaning that both have the same operational permissions. For the smart key, TID1.1 and TID1.2 are treated as two different operation tasks. Therefore, the same main work ticket can be expanded into multiple sub-tickets based on usage needs, without conflict between the sub-tickets, and the operation process can be clearly recorded.

[0073] Through the above process, the problem of confusion in the returned records after the same work ticket is issued to different teams for operation can be solved.

[0074] This embodiment of the present application provides a definition table of parameters transmitted between a key management device and a smart key, see Table 2.

[0075] Table 2

[0076]

[0077] In one possible implementation, the backend device can directly issue task information for the smart lock to the smart key without going through the key management device. In this example, after creating the first operation task TID1, the backend device directly sends the task information to the smart key. When issuing the first operation task, the smart key can directly generate a duplicate task (TID1.1) and perform the same issuance process as described above, and return the relevant information to the key management device for data synchronization.

[0078] FIG3 is a flow chart of another operation security management method provided by an embodiment of the present application. Referring to FIG1 , after the backend device creates an operation task, it can directly send task information to the smart key or send task information to the key management device;

[0079] The smart key receives task information from the key management device and can also obtain task information from the backend device wirelessly. The smart key is used to perform operations on the smart lock (including unlocking, locking, executing security measures, and releasing security measures) and transmits the generated operation records back to the key management device or backend device for storage.

[0080] S3. The smart key performs the first operation task on the smart lock, and generates an operation record of the first operation task according to the task sub-identifier assigned this time.

[0081] In the embodiment of the present application, this step S3 includes the following steps S31 to S33.

[0082] S31. The smart key parses the received first operation task to determine the task identifier of the first operation task, the type of the operation to be performed, the first task sub-identifier, and the device identifier of the smart lock.

[0083] Specifically, the smart key parses the received first operation task to determine the task identifier, time information, type of operation to be performed, first task sub-identifier, and device identifier of the smart lock. It then determines whether the first operation task exceeds the time range based on the time information. If it does not, it reads the device identifier of the smart lock. The time information includes the task start time and task end time, and the time range is from the task start time to the task end time.

[0084] S32. If the device identification read from the smart lock is consistent with the device identification corresponding to the first operation task, the smart key sends an operation instruction to the smart lock according to the type of the operation to be performed, the task identification and the first task sub-identifier.

[0085] Specifically, the operation instruction carries the type of operation to be performed (OP), the task identifier (SID1), and the first task sub-identifier (SCID1.1). If the device identifier read from the smart lock matches the device identifier corresponding to the first operation task, it means that the smart key has permission to perform the corresponding operation on the smart lock.

[0086] S33. The smart lock performs data analysis according to the operation instruction and returns the execution result of the first operation task to the smart key.

[0087] Specifically, step S33 includes the following steps A and B.

[0088] Step A: The smart lock device parses the type of operation to be performed in the operation instruction, which includes any one of: unlocking, locking, executing security measures, and releasing security measures;

[0089] Step B: The smart lock reads its own history records, performs logical judgment on the type based on the task identifier and task sub-identifier contained in the history records, and determines the execution result of the first operation task.

[0090] According to different types of operations to be performed, step B includes the following cases B1, B2 and B3.

[0091] B1. When the type is execution of security measure, if the historical record does not contain both the first task sub-identifier and the task identifier carried in the operation instruction, the smart lock executes the security measure and stores the first task sub-identifier and the task identifier, and then returns the result of completion of the security measure execution; if the historical record contains both the first task sub-identifier and the task identifier carried in the operation instruction, the smart lock returns the result of failure to execute the security measure.

[0092] When the operation to be executed is to execute a security measure, if the smart lock determines that there is a task ID and task sub-ID that are exactly the same as the current task, it means that the current task has been executed, so there is no need to execute it again; if there is no task ID and task sub-ID that are exactly the same, then the corresponding operation (execute security measure) is executed and the executed task ID and task sub-ID are recorded.

[0093] B2. When the type is to release the security measure, if the historical record contains both the first task sub-identifier and the task identifier carried in the operation instruction, the smart lock will release the security measure and delete the first task sub-identifier and the task identifier in the historical record, and then return the result of completing the security measure release; if the historical record does not contain both the first task sub-identifier and the task identifier carried in the operation instruction, the smart lock will return the result of failing to release the security measure.

[0094] When the operation to be executed is to release the security measure, if the smart lock determines that there is no task ID and task sub-ID that are exactly the same as the current task, it means that the security measure release operation for these task IDs and task sub-IDs has been executed, so there is no need to repeat it; if there is a task ID and task sub-ID that are exactly the same, the corresponding operation (release the security measure) is executed, and the task ID and task sub-ID that have been released are deleted.

[0095] B3. In the case of unlocking / locking, if the historical record does not include any task identifier and any task sub-identifier, the smart lock will perform the unlocking / locking operation and return the unlocking / locking completion result; if the historical record includes any task identifier or any task sub-identifier, the smart lock will return the unlocking / locking failure result.

[0096] When the operation to be executed is opening / closing the lock, if the smart lock determines that there are task IDs and task sub-IDs stored internally, it means that there are security measures that have not been released, so opening / closing the lock is not allowed; if the lock determines that there are no task IDs and task sub-IDs internally, it means that all security measures executed before have been released, so opening / closing the lock is allowed.

[0097] In the situations described in B1 to B3 above, for different task IDs and task sub-IDs (for example, SID1 and SID2 are different task IDs, and SID1.2 and SID2.3 are different task sub-IDs), operations can be performed in a certain order (for example, in ascending order of ID numbers) or randomly, and this application does not limit this.

[0098] S34. The smart key generates a first operation record of the first operation task according to the execution result.

[0099] Exemplarily, the first operation record includes: an execution result, a task identifier of the first operation task, a first task sub-identifier of the first operation task, a return time of the execution result, and a device identifier of the lock.

[0100] To facilitate understanding of the interaction process described in steps S31 to S34 above, an embodiment of the present application provides a schematic diagram of the interaction between a smart key and a smart lock. Referring to Figure 4, after receiving a task, the smart key decrypts the task and then parses it to obtain specific task information (SID, SCID, OP, T1, T2, etc.). If the current operation task to be executed does not exceed the time range, it connects to the smart lock and reads the status of the smart lock. The smart lock returns its current device ID, switch status, and security status. The smart key determines whether it has permission to perform the corresponding operation based on the device ID. If so, the smart key sends an operation instruction to the smart lock. The lock decrypts the operation instruction, performs data analysis, and returns the execution result to the smart key. The smart key then saves the operation record based on the execution result.

[0101] S4. The key management device / background device obtains one or more operation records of the first operation task from the smart key.

[0102] The first operation record includes: the execution result, the task identifier of the first operation task, the first task sub-identifier of the first operation task, the return time of the execution result, and the device identifier of the lock.

[0103] Specifically, the key management device / background device may obtain one or more operation records corresponding to the first operation task from one or more smart keys.

[0104] In one possible implementation, the key management device charges multiple smart keys in the operation safety management system, and the charging method can be wired charging or wireless charging; the key management device manages multiple smart keys in the operation safety management system, for example, updating the usage status or ID of the smart keys.

[0105] Figure 5 is a flow chart of another operation security management method provided by an embodiment of the present application. Referring to Figure 5, the background system creates a first operation task (TID1) and generates a task identifier (SID1) and a task sub-identifier (SCID1), selects a key management device and issues the first operation task according to the task information, and the task information includes at least SID1 and SCID1; the key management device saves the task information of the first operation task (TID1), and generates a task copy (TID1.1) and a first task sub-ID (SCID1.1) of the first operation task (TID1), and sends the task copy (TID1.1, SID1, SCID1.1) to the smart key; the smart key receives the task copy (TID1.1), saves SID1 and SCID1.1, and sends an operation instruction (including (SID1 and SCID1.1)) to the smart lock; the smart lock parses and judges the operation instruction, and saves SID1 and SCID1.1 after performing the corresponding operation (unlocking, locking or executing security measures).

[0106] In the operational safety management and control system provided by the embodiments of the present application, smart locks can replace mechanical locks as a safety measure. Smart locks support repeated operations, and one lock can be used to implement multiple security measures. Only when all security measures are released can the smart lock be opened. Replacing multiple mechanical locks with one smart lock can effectively avoid the problem of mismatched locks, reduce asset management, and improve ease of use. In addition, the operational safety management and control system provided by the present application flexibly assigns different task sub-identifiers when issuing tasks, which can cover complex scenarios where the same lock is operated multiple times, effectively records the operational process, improves the safety of the operational process, and can achieve experience accumulation and active prevention of safety accidents.

[0107] Furthermore, through the task sub-identification mechanism, the same main work ticket can be expanded into multiple sub-tickets according to usage requirements, and there will be no conflict between multiple sub-tickets. The operation process can be clearly recorded, thus solving the problem of confusion in the returned records after the same work ticket is issued to the key by different team members for operation during the operation process.

[0108] The present application also provides an electronic device, which can be implemented as a background device, key management device, smart key or smart lock in the above-mentioned operation safety management system to perform some or all of the steps in the above-mentioned operation safety management method. Figure 6 is a hardware structure diagram of an electronic device provided in an embodiment of the present application. As shown in Figure 6, the electronic device includes a processor 601, a memory 602, a bus 603, and a computer program stored in the memory 602 and capable of running on the processor 601. The processor 601 includes one or more processing cores, and the memory 602 is connected to the processor 601 via the bus 603. The memory 602 is used to store program instructions. When the processor executes the computer program, all or part of the steps in the above-mentioned method embodiment provided in the present application are implemented.

[0109] Furthermore, as an executable solution, the electronic device may be a computer unit, which may be an electronic device such as a desktop computer, a notebook, a PDA, or a cloud server. The computer unit may include, but is not limited to, a processor and a memory. Those skilled in the art will appreciate that the composition of the computer unit described above is merely an example of a computer unit and does not constitute a limitation of the computer unit. The computer unit may include more or fewer components than described above, or a combination of certain components, or different components. For example, the computer unit may also include input and output devices, network access devices, a bus, etc., which are not limited in the present embodiment.

[0110] Furthermore, as an executable solution, the processor may be a central processing unit (CPU), other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc. The processor is the control center of the computer unit and connects the various parts of the entire computer unit using various interfaces and lines.

[0111] The memory can be used to store the computer programs and / or modules. The processor implements the various functions of the computer unit by running or executing the computer programs and / or modules stored in the memory and accessing the data stored in the memory. The memory may primarily include a program storage area and a data storage area. The program storage area may store an operating system and at least one application required for a function; the data storage area may store data generated based on the use of the mobile phone. Furthermore, the memory may include high-speed random access memory and non-volatile memory, such as a hard disk, internal memory, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, at least one disk storage device, a flash memory device, or other volatile solid-state storage device.

[0112] The present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements all or part of the steps in the above-mentioned operation security management method in the embodiment of the present application.

[0113] If the modules / units integrated into the computer unit are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the present application can also implement all or part of the process steps in the above-mentioned method embodiments by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When executed by a processor, the computer program can implement the steps of each of the above-mentioned method embodiments. The computer program includes computer program code, which can be in source code form, object code form, executable file, or some intermediate form. The computer-readable medium can include any entity or device capable of carrying the computer program code, recording medium, USB flash drive, removable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased based on the requirements of legislation and patent practice in a jurisdiction.

[0114] Although the present application has been specifically shown and described in conjunction with preferred embodiments, it should be understood by those skilled in the art that various changes in form and details may be made to the present application without departing from the spirit and scope of the present application as defined by the appended claims, and all such changes are within the scope of protection of the present application.

Claims

1. An operation safety control and management system, characterized in that, The system includes: background equipment, key management equipment, smart locks and smart keys; The background device is used to: send task information of the smart lock to the key management device, where the task information describes a first operation task for the smart lock; The key management device is used to: assign a task sub-identifier corresponding to the first operation task to the smart key each time the first operation task is issued according to the task information, and the assigned task sub-identifier is different each time; The smart key is used to: perform a first operation task on the smart lock, and generate an operation record of the first operation task according to the task sub-identifier assigned this time; The key management device / the background device is further used to obtain one or more operation records of the first operation task from the smart key.

2. An operation safety control method for the operation safety control system according to claim 1, characterized in that, The method comprises: S1. The background device sends task information of the smart lock to the key management device, where the task information describes a first operation task for the smart lock; S2. The key management device allocates a task sub-identifier corresponding to the first operation task to the smart key each time according to the task information, and the task sub-identifier allocated each time is different; S3, the smart key performs a first operation task on the smart lock, and generates an operation record of the first operation task according to the task sub-identifier assigned this time; S4. The key management device / the background device obtains one or more operation records of the first operation task from the smart key.

3. The operation safety control method according to claim 2, wherein, The method further comprises: The background device directly sends the task information of the smart lock to the smart key.

4. The operation safety control method according to claim 2 or 3, characterized in that, Before step S1, the method further includes: The background device creates the first operation task and generates the task information according to the device identification of the smart lock and the type of the operation to be performed; The task information includes: device identifications of one or more smart locks, types of one or more operations to be performed, a task identification of the first operation task, and multiple task sub-identifications corresponding to the task identification.

5. The operation safety control method according to claim 4, characterized in that The step S3 comprises: S31, the smart key parses the received first operation task to determine the task identifier of the first operation task, the type of operation to be performed, the first task sub-identifier and the device identifier of the smart lock; S32: If the device identifier read from the smart lock is consistent with the device identifier corresponding to the first operation task, the smart key sends an operation instruction to the smart lock according to the type of the operation to be performed, the task identifier and the first task sub-identifier; S33, the smart lock performs data parsing according to the operation instruction, and returns the execution result of the first operation task to the smart key; S34. The smart key generates a first operation record of the first operation task according to the execution result.

6. The operation safety control method according to claim 5, characterized in that, The step S33 comprises: A. The smart lock analyzes the type of operation to be performed in the operation instruction, and the type includes: unlocking, locking, executing security measures, and releasing security measures; B. The smart lock reads its own historical records, performs logical judgment on the type according to the task identifier and task sub-identifier contained in the historical records, and determines the execution result of the first operation task.

7. The operation safety control method according to claim 6, wherein The step B comprises: B1. In the case where the type is execution of security measures, if the historical record does not contain both the first task sub-identifier and the task identifier carried in the operation instruction, the smart lock executes the security measure and stores the first task sub-identifier and the task identifier, and then returns a result of completion of the execution of the security measure; if the historical record contains both the first task sub-identifier and the task identifier carried in the operation instruction, the smart lock returns a result of failure to execute the security measure; B2. In the case where the type is to release the security measure, if the historical record contains both the first task sub-identifier and the task identifier carried in the operation instruction, the smart lock returns a result of completing the security measure release after releasing the security measure and deleting the first task sub-identifier and the task identifier in the historical record; if the historical record does not contain both the first task sub-identifier and the task identifier carried in the operation instruction, the smart lock returns a result of failing to release the security measure; B3. When the type is unlocking / locking, if the historical record does not include any task identifier and does not include any task sub-identifier, the smart lock performs the unlocking / locking operation and returns the unlocking / locking completion result; if the historical record includes any task identifier or any task sub-identifier, the smart lock returns the unlocking / locking failure result.

8. The operation safety control method according to claim 5, characterized in that The step S31 comprises: Parsing the received first operation task to determine the task identifier, time information, type of operation to be performed, first task sub-identifier, and device identifier of the smart lock of the first operation task; Determine whether the first operation task exceeds a time range according to the time information, and read the device identification of the smart lock if it does not exceed the time range.

9. The operation safety control method according to claim 2, wherein The method further comprises: The key management device charges multiple smart keys in the operation safety management and control system and manages the multiple smart keys in the operation safety management and control system.

10. A computer-readable storage medium, characterized in that, The storage medium stores at least one program, and the at least one program is executed by a processor to implement the operation safety management method as described in any one of claims 2 to 9.

Images