A method and system for associating and distributing permissions of one person reserving a multi-person factory

Abstract

The application discloses a method and system for associating and distributing the authority of one person reserving a multi-person factory, relates to the technical field of factory equipment authority management, and solves the problems of long-term validity of static authorization, lag of authority recycling, and high risk of unauthorized operation, overtime operation and out-of-place operation in multi-person collaborative operation. The method comprises the following steps: a main account terminal creates a target factory equipment reservation order, associates at least one sub-account, and sets a reservation time range, a geographic fence and a device access level respectively; a factory scheduling server generates dynamic authority tokens corresponding to each sub-account, establishes a binding relationship between the tokens and the target factory equipment, and encrypts and distributes the tokens; the target factory equipment verifies the integrity of the tokens, the binding of the equipment, the current time, the terminal location, and the matching relationship between the requested operation and the device access level, and opens the corresponding device operation authority after verification, otherwise, the operation is rejected.

Description

Technical Field

[0001] This application relates to the field of factory equipment access control technology, specifically to a method and system for associating and distributing access permissions for one person to book multiple factories. Background Technology

[0002] In industrial production, to ensure the safe operation of factory equipment, equipment access control based on accounts or personnel identities is typically employed. Existing access control systems generally pre-establish a correspondence between operators and equipment operation permissions, and configure equipment access permissions for corresponding accounts based on personnel positions, identities, or approval results. In temporary or collaborative work scenarios, operators typically submit permission applications individually, which are then approved by management personnel, and the corresponding equipment operation permissions are configured to each operator's account or operating terminal, enabling relevant personnel to operate factory equipment within their authorized scope.

[0003] However, existing equipment permissions are mostly configured statically, meaning that once assigned, permissions are usually valid indefinitely. This makes it difficult to accurately correlate the validity period of each operator's permissions with the equipment reservation time, leading to situations where temporary personnel can still operate the equipment after the work is completed and permissions are not revoked in a timely manner. Furthermore, existing technologies often struggle to jointly verify the actual location of the operating terminal, the target device, and the specific operation requested, failing to effectively restrict time-out operations, remote operations, and unauthorized operations. When an equipment reservation task involves multiple collaborating operators, separately applying for and configuring permissions increases the complexity of the approval and permission maintenance process, making it difficult to balance the efficiency of multi-person permission distribution with equipment operation security. Summary of the Invention

[0004] This application relates to a method and system for associating and distributing permissions for one person to book multiple factories. It aims to solve the technical problems of existing factories using static configuration of equipment permissions, where the validity period of permissions is difficult to accurately correspond to the equipment booking time period, and it is difficult to jointly verify the location of the operating terminal, the target equipment, and the requested operation. This can easily lead to untimely permission revocation, time-out operations, remote operations, and unauthorized operations. Furthermore, the permission application and maintenance process is complex when multiple people are working together.

[0005] To achieve the above objectives, this application provides the following technical solution: A method for associating and distributing permissions for one person to book multiple factories includes: A factory equipment reservation order for the target factory equipment is created through the main account terminal. At least one sub-account is associated with the factory equipment reservation order, and permission constraint information is set for each sub-account. The permission constraint information includes at least the reservation time range, geofence, and equipment access level. The factory equipment reservation order and the permission constraint information corresponding to each sub-account are sent to the factory scheduling server. The factory scheduling server generates dynamic permission tokens corresponding to each sub-account based on the factory equipment reservation order, each sub-account and the corresponding permission constraint information, and establishes a binding relationship between each dynamic permission token and the target factory equipment. Each of the aforementioned dynamic permission tokens is sent to the corresponding sub-account terminal via an encrypted link; In response to the sub-account terminal submitting a corresponding dynamic permission token to the target factory device, the target factory device obtains the current time and the location information of the sub-account terminal, and verifies the integrity of the dynamic permission token, the binding relationship between the dynamic permission token and the target factory device, the matching relationship between the current time and the scheduled time range, the matching relationship between the location information and the geofence, and the matching relationship between the requested device operation and the device access level. If all verifications pass, the target factory device grants the sub-account device operation permissions corresponding to the device access level; if any verification fails, the requested device operation is rejected.

[0006] Optionally, the permission constraint information may also include the operation role type; The corresponding operation role type is determined based on the preset identity tag of each sub-account, and the corresponding device access level is determined based on the operation role type.

[0007] Optionally, setting the reservation time range and the geofence includes: The idle status of the target factory equipment is obtained, and the reservation time period selected through the main account terminal is matched with the idle status of the target factory equipment. The successfully matched reservation time period is determined as the reservation time range. The geofence is set according to the target factory area, workshop area, or equipment operation area where the target factory equipment is located.

[0008] Optionally, the device access levels include public level, authorized level, and administrator level. The public level, authorized level, and administrator level correspond to different device operation permissions in sequence, and the device operation permissions corresponding to higher device access levels include the device operation permissions corresponding to lower device access levels.

[0009] Optionally, the factory scheduling server generates the dynamic permission token according to the following formula:

[0010] Wherein, Ksec is the server's private key; OrderID is the unique identifier for the reservation order; SubID is the sub-account identifier; TimeRange is the time range encoding value; GeoHash is the geofence area hash value; and DeviceLevel is the device access level encoding. This indicates data concatenation.

[0011] Optionally, the encrypted link is an encrypted transmission link established based on a transport layer security protocol.

[0012] Optionally, the target factory equipment verifies the dynamic permission token, including: The integrity of the dynamic permission token is verified, and after the integrity verification is passed, the order identifier, sub-account identifier, appointment time range, geofence and device access level corresponding to the dynamic permission token are obtained; Based on the pre-established association between the factory equipment reservation order and the target factory equipment, verify the binding relationship between the dynamic permission token and the target factory equipment; Compare the current time with the scheduled time range; Compare the location information of the sub-account terminal with the geofence; Compare the device operation requested by the sub-account terminal with the device operation permissions corresponding to the device access level; The verification is successful when the binding relationship between the dynamic permission token and the target factory equipment is verified, the current time is within the scheduled time range, the sub-account terminal is within the geofence, and the requested device operation matches the device access level; otherwise, the requested device operation is rejected and an abnormal permission warning message is generated.

[0013] Optionally, it also includes: A permission conflict is determined when at least two sub-accounts request to perform the same or mutually exclusive device operations on the same target factory equipment within an overlapping time frame. The operation role level, remaining reservation time, and distance between the sub-account terminal and the target factory equipment are obtained for each sub-account. The operation priority of each sub-account is determined based on the operation role level, the remaining reservation time, and the distance, and the sub-account to be authorized is determined based on the operation priority.

[0014] Optionally, the operation priority corresponding to each of the sub-accounts is determined, including: The priority parameter for each sub-account is calculated using the following formula: ; Where α, β, and γ are weighting coefficients, α + β + γ = 1; RoleLevel is the operation role level; TimeUrgency is the reciprocal of the remaining reservation time; GeoProximity is the reciprocal of the distance between the terminal and the device; The sub-accounts to be authorized are determined in descending order of the priority parameters. When a permission conflict involves denying permissions and granting permissions, the denying permission takes precedence over the granting permission; when a permission conflict involves directly setting permissions and inherited permissions, the directly setting permission takes precedence over the inherited permission. The permission conflict handling result is sent to the main account terminal, and a permission conflict report is generated. The permission conflict report includes at least the sub-account information where the permission conflict occurred, the target factory equipment, the conflict time, and the permission adjustment result.

[0015] Optionally, the factory scheduling server generates dynamic permission tokens corresponding to each of the sub-accounts, including: Generate a token group identifier based on the order identifier of the factory equipment reservation order and the equipment identifier of the target factory equipment; A token serial number is generated for each of the sub-accounts, and a dynamic permission token is generated based on the token group identifier, the corresponding sub-account identifier, the token serial number, and the corresponding permission constraint information, so that the dynamic permission tokens corresponding to the same factory equipment reservation order are associated with each other through the token group identifier; In response to the first successful verification of the dynamic permission token, the target factory device writes the token serial number into the set of activated token serial numbers and creates an authorization session corresponding to the dynamic permission token, so that the sub-account terminal can request device operation through the authorization session during the validity period of the authorization session; In the absence of the authorization session, reject dynamic permission tokens that contain token serial numbers that have been written into the set of activated token serial numbers; In response to the cancellation of the factory equipment reservation order or the main account terminal issuing a permission revocation command, the token group identifier is written into the invalid token group list of the target factory equipment, and the authorization session associated with the token group identifier is terminated, so that each dynamic permission token and authorization session associated with the token group identifier becomes invalid synchronously.

[0016] Optionally, the sub-account to be authorized is determined according to the operation priority, including: Obtain the current operating status of the target factory equipment and the operation type corresponding to each device operation that has a permission conflict; Based on the preset device safety interlock relationship, determine whether each device operation is a mutually exclusive operation that cannot be executed simultaneously; When each of the device operations is a mutually exclusive operation, the target factory equipment is in operation, and the current device operation does not meet the preset interruption conditions, the device operation permissions of the current sub-account are maintained, the dynamic permission tokens corresponding to other sub-accounts are frozen, and delayed activation conditions are generated for other sub-accounts. Monitor the operating status of the target factory equipment, and after the target factory equipment switches to the security state defined by the delayed activation condition, determine the sub-account to be authorized from other sub-accounts according to the operation priority, unfreeze the dynamic permission token corresponding to the sub-account to be authorized, and open the device operation permission corresponding to the dynamic permission token.

[0017] A permission association and distribution system for one person to book multiple factories includes a main account terminal, a factory scheduling server, at least one sub-account terminal, and a factory equipment verification module set on the target factory equipment. The main account terminal is used to create a factory equipment reservation order for reserving the target factory equipment, associate at least one sub-account with the factory equipment reservation order, set permission constraint information for each sub-account, and send the factory equipment reservation order and the permission constraint information to the factory scheduling server. The permission constraint information includes at least the reservation time range, geofence, and equipment access level. The factory scheduling server is used to generate dynamic permission tokens corresponding to each sub-account based on the factory equipment reservation order, each sub-account and corresponding permission constraint information, establish a binding relationship between each dynamic permission token and the target factory equipment, and send each dynamic permission token to the corresponding sub-account terminal through an encrypted link; The sub-account terminal is used to submit the corresponding dynamic permission token to the target factory equipment and provide the target factory equipment with the location information of the sub-account terminal; The factory equipment verification module is used to obtain the current time and verify the integrity of the dynamic permission token, the binding relationship between the dynamic permission token and the target factory equipment, the matching relationship between the current time and the scheduled time range, the matching relationship between the location information and the geofence, and the matching relationship between the requested device operation and the device access level. When all verifications pass, the module controls the target factory equipment to grant the sub-account device operation permissions corresponding to the device access level. If any verification fails, the module rejects the requested device operation.

[0018] Optionally, the factory scheduling server includes: The attribute management module is used to store and manage the user attribute information of the sub-account and the equipment attribute information of the target factory equipment; The policy management module is used to generate and store corresponding permission constraint policies based on the user attribute information and the device attribute information; The conflict resolution module is used to determine the operation priority of each sub-account based on the operation role level, remaining appointment time, and distance between the sub-account terminal and the target factory equipment when at least two sub-accounts request to perform the same equipment operation or mutually exclusive equipment operation for the same target factory equipment within an overlapping time range, and to determine the sub-account to be authorized based on the operation priority.

[0019] Optionally, it also includes a blockchain storage module, which is used to write permission distribution records and device operation records into blockchain nodes; The permission distribution record and the device operation record shall include at least the operator's identifier, operation time, target factory device identifier, device operation type, and device access level; The main account terminal is also used to obtain the permission distribution record and the device operation record through the corresponding key, and to verify the integrity of the permission distribution record and the device operation record based on the hash association relationship between adjacent blocks in the blockchain node.

[0020] An electronic device includes a processor and a memory communicatively connected to the processor. The memory stores a computer program, which, when executed by the processor, implements the method for associating and distributing permissions for one person to book multiple factories.

[0021] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method for associating and distributing permissions for one person to book multiple factories.

[0022] A computer program product includes a computer program that, when executed by a processor, implements the method for associating and distributing permissions for one person to book multiple factories.

[0023] Compared with the prior art, this application has at least the following beneficial effects: By associating at least one sub-account with a reservation order for equipment in the same target factory through the main account terminal, and setting reservation time range, geofence and equipment access level for each sub-account, the equipment operation permissions required for collaborative work by multiple people can be uniformly configured and distributed with the reservation task, reducing the processing steps required for separate applications, separate approvals and manual maintenance of permissions, and improving the efficiency of temporary permission configuration.

[0024] By generating dynamic permission tokens for each sub-account through the factory scheduling server, a binding relationship is established between the dynamic permission tokens and the target factory equipment, and the tokens are distributed through an encrypted link. This allows permissions to be configured in a fine-grained manner according to specific scheduled tasks and specific operators, reducing the risk of tokens being stolen, tampered with, or used for non-target equipment during transmission.

[0025] By jointly verifying the integrity of the dynamic permission token, the device binding relationship, the matching relationship between the current time and the scheduled time range, the matching relationship between the terminal location and the geofence, and the matching relationship between the requested operation and the device access level, the corresponding device operation permission is only granted when all verifications pass. This can restrict timed-out operations, remote operations, cross-device token use, and operations exceeding the access level, thereby improving the security of factory equipment operations.

[0026] The requested device operation is rejected if any verification item fails, so that the device authorization result can directly affect the operation control of the target factory equipment, forming a technical closed loop from reservation, permission generation, encrypted distribution to device verification and operation authorization. This helps to reduce the risk of misoperation caused by the long-term validity of static authorization and the lag in permission revocation. Attached Figure Description

[0027] Figure 1 This is a flowchart illustrating the method for associating and distributing factory equipment reservation permissions for multi-user collaborative operation as described in this application.

[0028] Figure 2 This is a schematic diagram of the structure of the factory equipment reservation permission association and distribution system for multi-person collaborative operation, as described in this application. Detailed Implementation

[0029] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0030] The present application will be further described below with reference to the accompanying drawings and embodiments. It should be noted that the following embodiments are used to illustrate the technical solution of the present application, and not to limit the scope of protection of the present application. The method flow of the present application can be executed collaboratively by the main account terminal, the factory scheduling server, the sub-account terminal, and the target factory equipment.

[0031] Example 1: In one embodiment of this application, a method for associating and distributing permissions for one person to book multiple factory operations is provided. This method addresses the problems of long-term validity of static equipment permissions, inconsistencies between the validity period of permissions and the actual scheduled work time, and the difficulty in jointly constraining operators, target equipment, operation time, operation location, and operation level when multiple people are working collaboratively.

[0032] In this application, "master account" refers to the account that creates factory equipment reservation orders and configures permission constraints for sub-accounts participating in those orders; "sub-account" refers to the operator account associated with the corresponding reservation order and receiving dynamic permission tokens; "factory equipment reservation order" refers to a data object that records the target factory equipment, participating accounts, and reservation operation relationships; "permission constraint information" refers to information used to limit when, where, and at what operation level a sub-account can operate the equipment; "geofence" refers to the electronic boundary of the spatial area corresponding to the area where permissions are allowed to be activated or used; "equipment access level" refers to the permission level corresponding to the scope of executable equipment operations; "dynamic permission token" refers to a data credential generated by the factory scheduling server for reservation orders and sub-accounts, used to prove temporary equipment operation qualifications; and "binding relationship" refers to the association relationship where the dynamic permission token corresponds only to the target factory equipment and cannot be used for other equipment.

[0033] like Figure 1 As shown, this embodiment includes the following steps.

[0034] Step S101: Create a factory equipment reservation order for the target factory equipment through the main account terminal, associate at least one sub-account with the factory equipment reservation order, and set the permission constraint information for each sub-account. The permission constraint information includes at least the reservation time range, geofence, and equipment access level.

[0035] In step S101, the main account terminal receives the target factory equipment and participating personnel information input by the main account, forming an account-order association relationship under the same reservation task. The reservation time range is used to limit the time interval within which permissions are acceptable; the geofence is used to limit the spatial range where the sub-account terminal should be located; and the device access level is used to limit the range of device operations that the sub-account can request. Step S101 outputs the factory equipment reservation order and the permission constraint information corresponding to each sub-account, which serves as the input for generating the dynamic permission token in step S102. By centrally associating multiple sub-accounts around the same reservation order, the processing steps required for multiple people to apply for and maintain device permissions separately can be reduced, and subsequent token generation has a clear order source.

[0036] Step S102: Send the factory equipment reservation order and the permission constraint information corresponding to each sub-account to the factory scheduling server. The factory scheduling server generates dynamic permission tokens corresponding to each sub-account based on the factory equipment reservation order, each sub-account and the corresponding permission constraint information, and establishes a binding relationship between each dynamic permission token and the target factory equipment.

[0037] In step S102, the factory scheduling server receives the order and permission constraint information output in step S101 and generates corresponding dynamic permission tokens for each sub-account. When the same order is associated with multiple sub-accounts, each sub-account obtains its own corresponding token, preventing multiple operators from sharing the same credentials. The factory scheduling server also restricts each token to the target factory equipment, preventing the token from being used on non-scheduled equipment. Step S102 outputs dynamic permission tokens corresponding to each sub-account and bound to the target factory equipment, providing a credential basis for subsequent secure distribution and device-side verification. This step enables device permissions to be dynamically generated with the scheduled task, reducing the risk of permission residue caused by the long-term existence of static authorization.

[0038] Step S103: Send each dynamic permission token to the corresponding sub-account terminal via an encrypted link.

[0039] In step S103, the factory scheduling server transmits the dynamic permission token to the corresponding sub-account terminal based on the correspondence between the sub-account and the token. An encrypted link is used to reduce the possibility of the token being stolen, tampered with, or replaced during transmission. Step S103 follows up on the token generation result from step S102 and delivers the token to the actual submitting entity in step S104, ensuring that the authorization credential generated on the server side can securely reach the corresponding operator's terminal.

[0040] Step S104: In response to the sub-account terminal submitting the corresponding dynamic permission token to the target factory device, the target factory device obtains the current time and the location information of the sub-account terminal, and verifies the integrity of the dynamic permission token, the binding relationship between the dynamic permission token and the target factory device, the matching relationship between the current time and the scheduled time range, the matching relationship between the location information and the geofence, and the matching relationship between the requested device operation and the device access level.

[0041] In step S104, when a sub-account terminal needs to operate the target factory equipment, it submits the dynamic permission token it has received and provides location information that represents the terminal's current location. The target factory equipment first confirms that the token has not been illegally altered since its generation, then confirms whether the token corresponds to the target factory equipment for this reservation, and subsequently confirms whether the submission time is within the reservation time range, whether the terminal location is within the geofence, and whether the requested device operation falls within the operation range allowed by the corresponding device access level. This step establishes a joint verification relationship between personnel credentials, device objects, time conditions, spatial conditions, and operation range, thereby reducing the risks of cross-device use, time-out use, remote use, and unauthorized operation.

[0042] Step S105: If all verifications pass, the target factory device grants the sub-account device operation permissions corresponding to the device access level; if any verification fails, the requested device operation is rejected.

[0043] Step S105 uses the verification results from step S104 as the basis for equipment control. Only when all verifications pass will the target factory equipment be granted the corresponding operating permissions; if any condition is not met, the equipment will not execute the requested operation. This step outputs an authorization result indicating whether the operation is allowed or denied, allowing permission control to directly affect the target factory equipment, forming a continuous technical process from order creation, token generation, encrypted distribution, joint verification to equipment authorization. This ensures that temporary permissions correspond to scheduled work conditions and reduces the risk of equipment misoperation caused by delayed static permission revokeability.

[0044] Example 2: In one complete embodiment of this application, see [link to full embodiment]. Figure 1 and Figure 2 The main account terminal, the factory scheduling server, at least one sub-account terminal, the factory equipment verification module set on the target factory equipment, and the optional blockchain storage module work together to perform the association, generation, distribution, verification, conflict handling, and audit tracking of equipment reservation permissions.

[0045] Appointment order creation and permission constraint configuration: The main account creates factory equipment reservation orders through the main account terminal and associates at least one sub-account with the order. The main account can set time ranges, geofences, operation role types, and equipment access levels for different sub-accounts, so that different personnel under the same equipment reservation task have temporary permissions corresponding to their job responsibilities.

[0046] In some embodiments, the main account terminal obtains the idle status of the target factory equipment, matches the reservation time slot selected by the main account with the equipment idle status, and determines the successfully matched reservation time slot as the reservation time range. This setting ensures that the validity period of the permission corresponds to the available time of the equipment, reducing reservation conflicts.

[0047] In some implementations, geofencing can be set up based on the target factory area, workshop area, or equipment operating area where the target factory equipment is located. Geofencing can be pre-defined based on the geographical location of the target factory and access restrictions can be set at three levels: province, city, or business district. For specific industrial sites, more refined area boundaries such as factory area, workshop, or equipment operating area can be used as needed.

[0048] The role type can be determined based on the sub-account's preset identity tag, and the corresponding device access level is determined accordingly. Device access levels can include public, authorized, and administrator levels, with each level corresponding to different device operation permissions. Higher device access levels can include the device operation permissions corresponding to lower levels. For example, public level corresponds to data viewing, authorized level corresponds to approved parameter adjustments, and administrator level corresponds to device configuration and permission management. By combining roles and access levels, the scope of permissions can be aligned with the responsibilities of the personnel.

[0049] Dynamic permission token generation, binding, and encrypted distribution: The main account terminal sends the reservation order and the corresponding permission constraint information for each sub-account to the factory scheduling server. The factory scheduling server generates dynamic permission tokens based on the order, sub-account, and permission constraint information, and establishes a binding relationship between the tokens and the target factory equipment.

[0050] As one implementation method, dynamic permission tokens can be generated according to the following formula:

[0051] Wherein, Ksec is the server private key; OrderID is the unique identifier of the reservation order; SubID is the sub-account identifier; TimeRange is the time range encoding value; GeoHash is the geofence area hash value; and DeviceLevel is the device access level encoding. The binding relationship between the token and the target factory equipment can be verified based on the pre-established association between the reservation order and the target factory equipment, without changing the input fields of the HMAC formula mentioned above. This setting does not change the input fields of the token generation formula mentioned above, and ensures that tokens under the order item can only be used for reserved equipment.

[0052] In some implementations, the encrypted link may employ asymmetric encryption or a transport layer security (TLS) protocol. Optionally, a TLS-based encrypted transmission link may be established to ensure the confidentiality and integrity of the dynamic authorization token transmission process. The factory scheduling server sends tokens to the corresponding terminals based on the sub-account identifier.

[0053] Token submission and joint verification of the target device: Once the sub-account terminal arrives within the geofence area within the scheduled time, it can submit a dynamic permission token to the target factory equipment. The target factory equipment obtains the current time and the real-time location information of the sub-account terminal and performs token verification.

[0054] As one implementation method, the target factory device first verifies the integrity of the dynamic permission token, and after successful verification, obtains the order identifier, sub-account identifier, appointment time range, geofence, and device access level. The target factory device verifies the token binding relationship based on the pre-established association between the appointment order and the target factory device; compares the current time with the appointment time range; compares the real-time location of the sub-account terminal with the geofence or geofence area hash value; and compares the requested device operation with the device operation permissions corresponding to the device access level.

[0055] If the binding relationship verification is successful, the current time is within the scheduled time range, the sub-account terminal is within the geofence, and the requested operation matches the device access level, the verification is considered successful and the corresponding operation permission is granted. Otherwise, the requested device operation is rejected. In some implementations, an abnormal permission warning message can also be generated when verification fails. The above-mentioned joint verification can simultaneously block timed-out operations, operations outside the geofence, cross-device token usage, and operations exceeding the access level.

[0056] Handling user permission conflicts: A permission conflict is identified when at least two sub-accounts request to perform the same or mutually exclusive device operations on the same target factory equipment within an overlapping timeframe. The factory scheduling server retrieves the operation role level, remaining appointment time, and distance between the sub-account's terminal and the target factory equipment for each sub-account, and determines the operation priority.

[0057] As one implementation method, the priority parameter is calculated according to the following formula: The priority rules are as follows: ; Where α, β, and γ are weighting coefficients, α + β + γ = 1; RoleLevel is the operation role level; TimeUrgency is the reciprocal of the remaining reservation time; GeoProximity is the reciprocal of the distance between the terminal and the device; The factory scheduling server can determine the sub-accounts to be authorized according to the priority parameters from largest to smallest.

[0058] When permission conflicts involve denying and granting permissions, denying permissions takes precedence over granting permissions; when permission conflicts involve directly setting permissions and inheriting permissions, directly setting permissions takes precedence over inheriting permissions. Permission adjustment results can be synchronized to the main account terminal in real time and a visual conflict report is generated. The report includes information on the conflicting sub-account, the conflicting device, the conflict time, and adjustment suggestions or the permission adjustment results. This approach can shorten the coordination time when multiple users have overlapping permissions and provide the main account with traceable decision-making information.

[0059] In a further optional implementation, conflict handling can be linked to equipment operation security. The factory scheduling server or the target factory equipment obtains the current operating status of the equipment and the operation type of the conflicting operations. Based on the preset equipment security interlock relationship, it determines whether each operation is a mutually exclusive operation that cannot be executed simultaneously. When each operation is a mutually exclusive operation, the equipment is in operation, and the current operation does not meet the preset interruption condition, the equipment operation permission of the current sub-account is maintained, the dynamic permission tokens corresponding to other sub-accounts are frozen, and delayed activation conditions are generated for other sub-accounts. The equipment operating status is continuously monitored. After the equipment switches to a safe state limited by the delayed activation condition, the sub-account to be authorized is determined according to the operation priority, the corresponding token is unfrozen, and the operation permission is granted. This optional method can avoid interrupting the ongoing uninterruptible operation by switching permissions immediately based solely on priority.

[0060] Token reuse protection and group-level revocation: In a further optional implementation, the factory scheduling server can generate a token group identifier based on the reservation order identifier and the target factory equipment identifier, and generate a token serial number for each sub-account. The server generates a dynamic permission token based on the token group identifier, sub-account identifier, token serial number, and permission constraint information, so that tokens corresponding to the same reservation order are associated through the token group identifier.

[0061] After the dynamic permission token is successfully verified for the first time, the target factory device writes the token serial number into the set of activated token serial numbers and creates an authorization session corresponding to that token. Sub-account terminals can request device operation through the authorization session during its validity period. If no authorization session is established, and a subsequently submitted dynamic permission token contains a serial number already written into the set, the token is rejected to reduce the risk of duplicate token submissions.

[0062] When a reservation order is cancelled or the main account terminal issues a permission revocation command, the token group identifier can be written to the invalid token group list of the target factory equipment, and the authorization session associated with that token group identifier can be terminated, causing all dynamic permission tokens and active sessions associated with the same reservation order to become invalid synchronously. This method can reduce inconsistencies caused by revoking tokens one by one after they are distributed among multiple people.

[0063] Access audit trail: In some implementations, permission distribution records and device operation records can be written to blockchain nodes to achieve distributed storage and tamper-proof recording. The records include at least the operator's identifier, operation time, target factory equipment identifier, equipment operation type, and equipment access level. During auditing, the main account terminal can obtain the permission distribution records and device operation records using the corresponding key and verify the record integrity based on the hash association relationship between adjacent blocks in the blockchain node. The main account can also decrypt the operation logs using the key. This method provides traceable data evidence for permission changes and device operations and improves the detectability of log tampering.

[0064] like Figure 2 As shown, a system for implementing the above method may include a master account terminal, a factory scheduling server, at least one sub-account terminal, and a factory equipment verification module located on the target factory equipment. In some embodiments, the system also includes a blockchain storage module.

[0065] The main account terminal is used to create reservation orders, associate sub-accounts, set permission constraints, and submit orders to the server; the factory scheduling server is used to generate dynamic permission tokens, establish the binding relationship between tokens and target devices, distribute tokens via encrypted links, and perform order management and permission conflict decisions; the sub-account terminal is used to receive tokens, provide terminal location information, and request target device operations; the factory device verification module is used to obtain the current time, verify token integrity, device binding, time, location, and access level, and control device authorization based on the verification results; the blockchain storage module is used to record permission distribution and device operation logs.

[0066] The factory scheduling server may include an attribute management module, a policy management module, and a conflict resolution module. The attribute management module stores and manages user attributes for sub-accounts and device attributes for target factory equipment. The policy management module generates and stores permission constraint policies based on user and device attributes. The conflict resolution module determines operation priority and identifies the sub-account to be authorized when multiple users have conflicting operations, based on role level, remaining appointment time, and terminal distance. Each module can function as a software feature within the server or be implemented by interconnecting processing units as needed for deployment.

[0067] In some embodiments of this application, an electronic device is also provided, including a processor and a memory communicatively connected to the processor. The memory stores a computer program, which, when executed by the processor, implements the above-described method. The electronic device may be a factory scheduling server, a master account terminal, a sub-account terminal, a target factory equipment controller, or a computing device capable of executing corresponding programs.

[0068] In some embodiments of this application, a computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a processor, implements the above-described method. The computer-readable storage medium may, as needed, employ non-volatile memory, magnetic storage medium, optical storage medium, or other media capable of storing program instructions.

[0069] In some embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the above-described method. Thus, the above-described method can be deployed in a factory access control system in a software, hardware, or a combination of both.

[0070] I. Specific Implementation Example: Application in Equipment Maintenance Scenarios at Automotive Parts Factories 1. The main account creates a reservation order. 1.1 The factory equipment management supervisor logs into the factory MES system's access control module, selects the "Equipment Maintenance Appointment" function, and creates an appointment order with order number WO20241015001. The operation interface displays the following configuration items: 1.2 Sub-account association: Three sub-accounts were added by searching for employee IDs: Machinist Zhang (SubID:S001), Electrician Li (SubID:S002), and Quality Inspector Wang (SubID:S003). 1.3 Time Range Setting: Select October 15, 2024, 9:00-16:00. The system will automatically match and display the idle status of the target device (CNC lathe CK6140-05#) as "Available". 1.4 Geofencing Configuration: Select "Workshop No. 3" from the factory map library. The system will automatically generate a polygonal fence area with latitude 30.2345°-30.2368°N and longitude 120.1572°-120.1595°E, with an accuracy of 5 meters. 1.5 Role Assignment: Assign role tags to sub-accounts: Mechanic (RoleLevel=0.8), Electrician (RoleLevel=0.7), Quality Inspector (RoleLevel=0.6). 1.6 Equipment Access Levels: Mechanics are granted "Authorized Level" (can adjust parameters), electricians are granted "Authorized Level," and quality inspectors are granted "Public Level" (can only view data). 2. Dynamic permission token generation and distribution After the main account submits the reservation request, the factory scheduling server performs the following operations: 2.1 Dynamic tokens are generated based on permission constraints, using the HMAC-SHA512 algorithm: ; GeoHash=gh_8fj3k corresponds to the No. 3 workshop area, and DeviceLevel=2 represents the authorized level; 2.2 Tokens are distributed via a TLS 1.3 encrypted link, using the AES128-GCM-SHA256 cipher suite. The client and server complete a 0-RTT handshake, with the initial request taking 118ms. 2.3 The token is bound to the unique hardware identifier (MAC:00:1B:44:11:3A:B7) of the target device CK6140-05#. 3. Sub-account terminal operation verification After arriving at the site, mechanic Zhang performed the following steps on the industrial flat panel: 3.1 The terminal automatically obtains its GPS location (30.2352°N, 120.1581°E) and verifies that it is within the geofence; 3.2 Click the "Activate Permissions" button, and the terminal sends a token to the device control unit; 3.3 Equipment Validation Process: 3.3a ​​Decrypt token verification timestamp, current time 10:15 is within the reservation range; 3.3b Compare the terminal location hash value with the GeoHash; 3.3c Confirm that DeviceLevel=2 matches the requested parameter adjustment operation; After successful 3.3D verification, the device unlocks and displays "Authorized operation enabled"; 4. Resolving permission conflicts At 14:00, a permission conflict occurred: Mechanic Zhang and Electrician Li simultaneously requested to operate the parameter setting function of CK6140-05#. The system triggered the conflict resolution mechanism: Calculate priority parameters: Mr. Zhang: RoleLevel=0.8, TimeUrgency=1 / (16:00-14:00)=0.167, GeoProximity=1 / 5m=0.2; Gong Li: RoleLevel=0.7, TimeUrgency=0.167, GeoProximity=1 / 8m=0.125; Apply the formula Priority = 0.5 × RoleLevel + 0.3 × TimeUrgency + 0.2 × GeoProximity: Zhang Gong's priority = 0.5 × 0.8 + 0.3 × 0.167 + 0.2 × 0.2 = 0.4 + 0.05 + 0.04 = 0.49; Li Gong's priority = 0.5 × 0.7 + 0.3 × 0.167 + 0.2 × 0.125 = 0.35 + 0.05 + 0.025 = 0.425; The system automatically authorized Zhang to continue the operation, pushed a "Please wait 15 minutes and try again" message to Li's terminal, and synchronized it to the main account terminal in real time to generate a conflict report, displaying the conflicting device ID, time overlap interval, and priority calculation process; 5. Blockchain Audit Trail 5.1 After the daily maintenance work is completed, the system will automatically complete the following audit records: The blockchain node writes 23 operation records, each containing: the operator's SubID and role tag; the unique identifier of the operating device; the operation timestamp (accurate to milliseconds); the operation type and parameter values ​​before and after changes; and the token verification result. 5.2 It adopts the Hyperledger Fabric consortium blockchain architecture, where each block contains the hash value of the previous block, ensuring immutability; 5.3 The main account can view the complete log by decrypting with the key. The system generates an "Equipment Maintenance Permission Audit Report", which includes statistics on abnormal operations (0 records in this case). II. Scheme Validation Experiments and Data (1) Test scenario: Simulate equipment maintenance access management in a factory with 100 employees (2) Comparison of schemes: Traditional manual approval mode vs. this application scheme (3) Testing equipment: factory scheduling server (8-core CPU / 16GB memory), 20 industrial equipment terminals, and 50 sub-account tablet terminals. (4) Test indicators: efficiency of permission allocation, speed of conflict resolution, security protection capabilities, and efficiency of audit traceability. (4.1) Verification of permission allocation efficiency Experimental method: Simulate 10 groups of reservation requests containing 5-15 sub-accounts, using traditional manual approval (paper application + step-by-step signature) and the dynamic token mode of this application respectively, and record the effective time of the permissions.

[0071] Experimental results:

[0072] Analysis: This solution reduces the traditional 3-hour manual approval process to 30 seconds through automated token generation and encrypted distribution, meeting the national Cybersecurity Classified Protection 2.0 standard of "permission change response time ≤ 10 minutes". The use of TLS 1.3's 0-RTT handshake technology significantly reduces the time required for the initial request.

[0073] (4.2) Conflict resolution performance test Experimental method: Set up 50 permission overlap scenarios (time / device / geofencing overlap) and record the response time of system conflict detection and adjustment.

[0074] Experimental results: Average conflict identification time: 0.32 seconds; Average permission adjustment time: 0.8 seconds; Conflict resolution success rate: 100%; Main account synchronization delay: ≤1 second; Comparative data: Traditional manual coordination takes an average of 30±15 minutes to resolve a single conflict, while this solution improves conflict resolution efficiency by 2250%. The priority algorithm achieves a conflict decision accuracy of 98.7% when the role level weight is set to 0.5.

[0075] (4.3) Verification of safety protection capabilities Experimental Method: Simulate four common attack scenarios to test the system's protection effectiveness. (a) Unauthorized access: The sub-account attempted to activate the token outside the geofence. (b) Timeout Operation: Sub-accounts continue to operate after the scheduled time has expired. (c) Token forgery: Requesting authorization using a forged token with altered parameters. (d) Data tampering: Attempting to modify operation records that have been uploaded to the blockchain. Protective effect:

[0076] Analysis: Real-time geofencing verification, timestamp verification, and HMAC encrypted tokens effectively prevent unauthorized access and forgery attacks. The blockchain's chained hash structure ensures the immutability of operation records, and the tamper detection mechanism achieves 100% accuracy.

[0077] (4.4) Comparison of audit traceability efficiency Experimental method: Three abnormal equipment operation events were simulated, and the time spent tracing the problem was recorded using both traditional paper logs and the blockchain auditing system proposed in this application.

[0078] Experimental results:

[0079] Real-world example: After implementing a similar blockchain auditing solution, a research and development center saw an 89% decrease in security incidents in its core area, consistent with the results of this experiment. The audit reports generated by the system fully comply with the requirement of "log retention ≥ 6 months and traceability" in the "Basic Requirements for Network Security Level Protection of Information Security Technology".

[0080] (4.5) Long-term operational stability data During 30 consecutive days of testing: Token generation success rate: 100% (12,480 tokens generated cumulatively); Verification failure rate: 0.3% (all were normal timeout or out-of-bounds scenarios); System mean time between failures: 1,920 hours; Server resource usage: Peak CPU utilization ≤35%, memory usage ≤20%.

[0081] III. Summary of Implementation Results The implementation and verification of this solution in an automotive parts factory demonstrates that it has the following significant advantages compared to traditional access control models: Efficiency Improvement: Permission allocation efficiency is improved by 99.7%, completely solving the pain points of "slow permission application and difficult adjustment" in the traditional model. Security Enhancement: Achieves 100% interception of unauthorized access and detection of data tampering, reducing the risk of security incidents by more than 89%. Management optimization: Reduce manual coordination costs by 99% through automated conflict resolution. Compliance Assurance: Fully meets the Level 3 requirements of the Information Security Protection Scheme 2.0, with audit traceability efficiency improved by nearly 200 times. This solution is particularly suitable for industrial scenarios requiring multi-person collaborative operation and can be widely applied to equipment access management in fields such as machinery manufacturing, electronic processing, and chemical production.

[0082] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0083] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0084] This application may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, readable storage media, optical storage, etc.) containing computer-usable program code.

[0085] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0086] Obviously, the described embodiments are only some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort should fall within the scope of protection of this application.

[0087] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for associating and distributing permissions for one person to book multiple factories, characterized in that, include: A factory equipment reservation order for the target factory equipment is created through the main account terminal. At least one sub-account is associated with the factory equipment reservation order, and permission constraint information is set for each sub-account. The permission constraint information includes at least the reservation time range, geofence, and equipment access level. The factory equipment reservation order and the permission constraint information corresponding to each sub-account are sent to the factory scheduling server. The factory scheduling server generates dynamic permission tokens corresponding to each sub-account based on the factory equipment reservation order, each sub-account and the corresponding permission constraint information, and establishes a binding relationship between each dynamic permission token and the target factory equipment. Each of the aforementioned dynamic permission tokens is sent to the corresponding sub-account terminal via an encrypted link; In response to the sub-account terminal submitting a corresponding dynamic permission token to the target factory device, the target factory device obtains the current time and the location information of the sub-account terminal, and verifies the integrity of the dynamic permission token, the binding relationship between the dynamic permission token and the target factory device, the matching relationship between the current time and the scheduled time range, the matching relationship between the location information and the geofence, and the matching relationship between the requested device operation and the device access level. If all verifications pass, the target factory device grants the sub-account device operation permissions corresponding to the device access level; if any verification fails, the requested device operation is rejected.

2. The method for associating and distributing permissions for one person to book multiple factories according to claim 1, characterized in that, The permission constraint information also includes the operation role type; The corresponding operation role type is determined based on the preset identity tag of each sub-account, and the corresponding device access level is determined based on the operation role type; Setting the reservation time range and the geofence includes: The idle status of the target factory equipment is obtained, and the reservation time period selected through the main account terminal is matched with the idle status of the target factory equipment. The successfully matched reservation time period is determined as the reservation time range. The geofence is set according to the target factory area, workshop area, or equipment operation area where the target factory equipment is located; The device access levels include public level, authorized level and administrator level. The public level, authorized level and administrator level correspond to different device operation permissions in sequence, and the device operation permissions corresponding to higher device access levels include the device operation permissions corresponding to lower device access levels.

3. The method for associating and distributing permissions for one person to book multiple factories according to claim 1, characterized in that, The factory scheduling server and the target factory equipment are pre-configured with the same token verification key. The factory scheduling server generates the dynamic permission token according to the following formula: Wherein, Ksec is the server's private key; OrderID is the unique identifier for the reservation order; SubID is the sub-account identifier; TimeRange is the time range encoding value; GeoHash is the geofence area hash value; and DeviceLevel is the device access level encoding. This indicates data concatenation.

4. The method for associating and distributing permissions for one person to book multiple factories according to claim 3, characterized in that, The factory scheduling server generates dynamic permission tokens corresponding to each of the sub-accounts, including: Generate a token group identifier based on the order identifier of the factory equipment reservation order and the equipment identifier of the target factory equipment; A token serial number is generated for each of the sub-accounts, and a dynamic permission token is generated based on the token group identifier, the corresponding sub-account identifier, the token serial number, and the corresponding permission constraint information, so that the dynamic permission tokens corresponding to the same factory equipment reservation order are associated with each other through the token group identifier; In response to the first successful verification of the dynamic permission token, the target factory device writes the token serial number into the set of activated token serial numbers and creates an authorization session corresponding to the dynamic permission token, so that the sub-account terminal can request device operation through the authorization session during the validity period of the authorization session; In the absence of the authorization session, reject dynamic permission tokens that contain token serial numbers that have been written into the set of activated token serial numbers; In response to the cancellation of the factory equipment reservation order or the main account terminal issuing a permission revocation command, the token group identifier is written into the invalid token group list of the target factory equipment, and the authorization session associated with the token group identifier is terminated, so that each dynamic permission token and authorization session associated with the token group identifier becomes invalid synchronously.

5. The method for associating and distributing permissions for one person to book multiple factories according to claim 1, characterized in that, The target factory equipment verifies the dynamic permission token, including: The integrity of the dynamic permission token is verified, and after the integrity verification is passed, the order identifier, sub-account identifier, appointment time range, geofence, device access level and device identifier corresponding to the dynamic permission token are obtained. Compare the device identifier in the dynamic permission token with the native device identifier of the target factory device; Compare the current time with the scheduled time range; Compare the location information of the sub-account terminal with the geofence; Compare the device operation requested by the sub-account terminal with the device operation permissions corresponding to the device access level; The verification is successful when the device identifier matches the local device identifier, the current time is within the scheduled time range, the sub-account terminal is within the geofence, and the requested device operation matches the device access level; otherwise, the requested device operation is rejected and an abnormal permission warning is generated.

6. The method for associating and distributing permissions for one person to book multiple factories according to claim 1, characterized in that, Also includes: A permission conflict is determined when at least two sub-accounts request to perform the same or mutually exclusive device operations on the same target factory equipment within an overlapping time frame. The operation role level, remaining reservation time, and distance between the sub-account terminal and the target factory equipment are obtained for each sub-account. The operation priority of each sub-account is determined based on the operation role level, the remaining reservation time, and the distance, and the sub-account to be authorized is determined based on the operation priority.

7. The method for associating and distributing permissions for one person to book multiple factories according to claim 6, characterized in that, Determine the operation priority for each sub-account, including: Determine the operation priority for each sub-account, including: The priority parameter for each sub-account is calculated using the following formula: ； Where α, β, and γ are weighting coefficients, α + β + γ = 1; RoleLevel is the operation role level; TimeUrgency is the reciprocal of the remaining reservation time; GeoProximity is the reciprocal of the distance between the terminal and the device; The sub-accounts to be authorized are determined in descending order of the priority parameters. When a permission conflict involves denying permissions and granting permissions, the denying permission takes precedence over the granting permission; when a permission conflict involves directly setting permissions and inherited permissions, the directly setting permission takes precedence over the inherited permission. The permission conflict handling result is sent to the main account terminal, and a permission conflict report is generated. The permission conflict report includes at least the sub-account information where the permission conflict occurred, the target factory equipment, the conflict time, and the permission adjustment result.

8. The method for associating and distributing permissions for one person to book multiple factories according to claim 6, characterized in that, The sub-accounts to be authorized are determined based on the aforementioned operation priority, including: Obtain the current operating status of the target factory equipment and the operation type corresponding to each device operation that has a permission conflict; Based on the preset device safety interlock relationship, determine whether each device operation is a mutually exclusive operation that cannot be executed simultaneously; When each of the device operations is a mutually exclusive operation, the target factory equipment is in operation, and the current device operation does not meet the preset interruption conditions, the device operation permissions of the current sub-account are maintained, the dynamic permission tokens corresponding to other sub-accounts are frozen, and delayed activation conditions are generated for other sub-accounts. Monitor the operating status of the target factory equipment, and after the target factory equipment switches to the security state defined by the delayed activation condition, determine the sub-account to be authorized from other sub-accounts according to the operation priority, unfreeze the dynamic permission token corresponding to the sub-account to be authorized, and open the device operation permission corresponding to the dynamic permission token.

9. A permission association and distribution system for one person to book multiple factories, characterized in that, It includes a main account terminal, a factory scheduling server, at least one sub-account terminal, and a factory equipment verification module set on the target factory equipment; The main account terminal is used to create a factory equipment reservation order for reserving the target factory equipment, associate at least one sub-account with the factory equipment reservation order, set permission constraint information for each sub-account, and send the factory equipment reservation order and the permission constraint information to the factory scheduling server. The permission constraint information includes at least the reservation time range, geofence, and equipment access level. The factory scheduling server is used to generate dynamic permission tokens corresponding to each sub-account based on the factory equipment reservation order, each sub-account and corresponding permission constraint information, establish a binding relationship between each dynamic permission token and the target factory equipment, and send each dynamic permission token to the corresponding sub-account terminal through an encrypted link; The sub-account terminal is used to submit the corresponding dynamic permission token to the target factory equipment and provide the target factory equipment with the location information of the sub-account terminal; The factory equipment verification module is used to obtain the current time and verify the integrity of the dynamic permission token, the binding relationship between the dynamic permission token and the target factory equipment, the matching relationship between the current time and the scheduled time range, the matching relationship between the location information and the geofence, and the matching relationship between the requested device operation and the device access level. When all verifications pass, the module controls the target factory equipment to grant the sub-account device operation permissions corresponding to the device access level. If any verification fails, the module rejects the requested device operation.

10. The permission association and distribution system for one person to book multiple factories according to claim 9, characterized in that, The factory scheduling server includes: The attribute management module is used to store and manage the user attribute information of the sub-account and the equipment attribute information of the target factory equipment; The policy management module is used to generate and store corresponding permission constraint policies based on the user attribute information and the device attribute information; The conflict resolution module is used to determine the operation priority of each sub-account based on the operation role level, remaining appointment time, and distance between the sub-account terminal and the target factory equipment when at least two sub-accounts request to perform the same equipment operation or mutually exclusive equipment operation for the same target factory equipment within an overlapping time range, and to determine the sub-account to be authorized based on the operation priority. It also includes a blockchain storage module, which is used to write permission distribution records and device operation records into blockchain nodes; The permission distribution record and the device operation record shall include at least the operator's identifier, operation time, target factory device identifier, device operation type, and device access level; The main account terminal is also used to obtain the permission distribution record and the device operation record through the corresponding key, and to verify the integrity of the permission distribution record and the device operation record based on the hash association relationship between adjacent blocks in the blockchain node.

Images