A multi-module software hierarchical authorization management method, device and computer equipment

Abstract

The present application relates to a multi-module software hierarchical authorization management method, device and computer equipment. The method includes: matching the top-level management terminal storage information in the upper-level authority management file with the distributed operation terminal storage information; if the matching result is successful, according to the intermediate administrator role authority requirement information, using the upper-level administrator account to set up the intermediate administrator account in the power equipment engineering simulation calculation platform; distributing the intermediate authorization file from the upper-level administrator account to the intermediate administrator account; according to the lower-level administrator role authority requirement information, using the intermediate administrator account to set up the lower-level administrator account; distributing the lower-level authorization application file from the intermediate administrator account to the upper-level administrator account to generate the lower-level authorization file; the upper-level administrator account distributes the lower-level authorization file from the upper-level administrator account to the lower-level administrator account through the intermediate administrator account. It can improve the efficiency of software use and thus promote the efficiency of enterprises in software use and operation.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a multi-module software hierarchical authorization management method, apparatus, and computer equipment. Background Art

[0002] Multi-physics simulation of power equipment involves the coupling of multiple physical fields, including electricity, magnetism, heat, force, flow, and sound. With the development of computer technology, engineering simulation calculations for power equipment have emerged. The analysis and evaluation of these field quantities often involve a variety of different software and modules. Software applications also have different material parameter libraries, simulation model libraries, engineering case libraries, and corresponding standards and specifications, along with numerous intellectual property rights and data information. Existing technology typically generates and encrypts authorization files for each software application. When used by different users, the authorization files need to be reinstalled based on the user account's permissions, and the permissions of the corresponding users need to be updated. The management process is cumbersome, and it is difficult to manage the permissions of lower-level departments and users, the number of accounts, and other aspects of top-down control within the enterprise. This results in inefficient software use, which in turn affects the efficiency of the enterprise in software use and operation. Summary of the Invention

[0003] Based on this, it is necessary to provide a multi-module software hierarchical authorization management method, device, computer equipment, computer-readable storage medium and computer program product to address the above technical problems, which can improve software usage efficiency and thus promote the efficiency of enterprises in software usage and operation.

[0004] In a first aspect, the present application provides a multi-module software hierarchical authorization management method. The method comprises:

[0005] In response to an operation of inputting the upper-level administrator account into the upper-level authority management file, matching the top-level management terminal storage information in the upper-level authority management file with the distributed operation terminal storage information;

[0006] If the matching result is successful, the intermediate administrator account is set up in the power equipment engineering simulation computing platform using the upper administrator account according to the intermediate administrator role authority requirement information;

[0007] Distributing the intermediate authorization file from the senior administrator account to the intermediate administrator account;

[0008] According to the subordinate administrator role authority requirement information, use the intermediate administrator account to set up a subordinate administrator account on the power equipment engineering simulation computing platform;

[0009] Distribute the subordinate authorization application file from the intermediate administrator account to the superior administrator account to generate a subordinate authorization file;

[0010] The superior administrator account distributes the subordinate authorization file from the superior administrator account to the subordinate administrator account through the intermediate administrator account; the superior administrator account, the intermediate administrator account and the subordinate administrator account are used to use the software in different modules in the power equipment engineering simulation computing platform according to corresponding permissions.

[0011] In a second aspect, the present application also provides a multi-module software hierarchical authorization management device. The device includes:

[0012] an information matching module for matching top-level management terminal storage information with distributed operation terminal storage information in the upper-level authority management file in response to an operation inputted into the upper-level authority management file by the upper-level administrator account;

[0013] An account setting module is used to set an intermediate administrator account in the power equipment engineering simulation computing platform using the superior administrator account according to the intermediate administrator role authority requirement information when the matching result is successful;

[0014] The permission setting module is used to distribute the intermediate authorization file from the upper-level administrator account to the intermediate administrator account;

[0015] The account setting module is further used to use the intermediate administrator account to set a subordinate administrator account in the power equipment engineering simulation computing platform according to the subordinate administrator role authority requirement information;

[0016] The permission application module is used to distribute the lower-level authorization application file from the intermediate administrator account to the upper-level administrator account to generate a lower-level authorization file;

[0017] The permission setting module is also used for the superior administrator account to distribute the subordinate authorization file from the superior administrator account to the subordinate administrator account through the intermediate administrator account; the superior administrator account, the intermediate administrator account and the subordinate administrator account are used to use the software in different modules in the power equipment engineering simulation calculation platform according to the corresponding permissions.

[0018] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are performed:

[0019] In response to an operation of inputting the upper-level administrator account into the upper-level authority management file, matching the top-level management terminal storage information in the upper-level authority management file with the distributed operation terminal storage information;

[0020] If the matching result is successful, the intermediate administrator account is set up in the power equipment engineering simulation computing platform using the upper administrator account according to the intermediate administrator role authority requirement information;

[0021] Distributing the intermediate authorization file from the senior administrator account to the intermediate administrator account;

[0022] According to the subordinate administrator role authority requirement information, use the intermediate administrator account to set up a subordinate administrator account on the power equipment engineering simulation computing platform;

[0023] Distribute the subordinate authorization application file from the intermediate administrator account to the superior administrator account to generate a subordinate authorization file;

[0024] The superior administrator account distributes the subordinate authorization file from the superior administrator account to the subordinate administrator account through the intermediate administrator account; the superior administrator account, the intermediate administrator account and the subordinate administrator account are used to use the software in different modules in the power equipment engineering simulation computing platform according to corresponding permissions.

[0025] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0026] In response to an operation of inputting the upper-level administrator account into the upper-level authority management file, matching the top-level management terminal storage information in the upper-level authority management file with the distributed operation terminal storage information;

[0027] If the matching result is successful, the intermediate administrator account is set up in the power equipment engineering simulation computing platform using the upper administrator account according to the intermediate administrator role authority requirement information;

[0028] Distributing the intermediate authorization file from the senior administrator account to the intermediate administrator account;

[0029] According to the subordinate administrator role authority requirement information, use the intermediate administrator account to set up a subordinate administrator account on the power equipment engineering simulation computing platform;

[0030] Distribute the subordinate authorization application file from the intermediate administrator account to the superior administrator account to generate a subordinate authorization file;

[0031] The superior administrator account distributes the subordinate authorization file from the superior administrator account to the subordinate administrator account through the intermediate administrator account; the superior administrator account, the intermediate administrator account and the subordinate administrator account are used to use the software in different modules in the power equipment engineering simulation computing platform according to corresponding permissions.

[0032] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the following steps:

[0033] In response to an operation of inputting the upper-level administrator account into the upper-level authority management file, matching the top-level management terminal storage information in the upper-level authority management file with the distributed operation terminal storage information;

[0034] If the matching result is successful, the intermediate administrator account is set up in the power equipment engineering simulation computing platform using the upper administrator account according to the intermediate administrator role authority requirement information;

[0035] Distributing the intermediate authorization file from the senior administrator account to the intermediate administrator account;

[0036] According to the subordinate administrator role authority requirement information, use the intermediate administrator account to set up a subordinate administrator account on the power equipment engineering simulation computing platform;

[0037] Distribute the subordinate authorization application file from the intermediate administrator account to the superior administrator account to generate a subordinate authorization file;

[0038] The superior administrator account distributes the subordinate authorization file from the superior administrator account to the subordinate administrator account through the intermediate administrator account; the superior administrator account, the intermediate administrator account and the subordinate administrator account are used to use the software in different modules in the power equipment engineering simulation computing platform according to corresponding permissions.

[0039] The above-mentioned multi-module software hierarchical authorization management method, device, computer equipment, storage medium and computer program product, in response to the operation of the superior administrator account input into the superior authority management file, matches the top-level management terminal storage information in the superior authority management file with the distributed operation terminal storage information; when the matching result is successful, according to the intermediate administrator role authority requirement information, the superior administrator account is used to set up the intermediate administrator account in the electric power equipment engineering simulation calculation platform; the intermediate authorization file is distributed from the superior administrator account to the intermediate administrator account; according to the subordinate administrator role authority requirement information, the intermediate administrator account is used to set up the subordinate administrator account in the electric power equipment engineering simulation calculation platform; the subordinate authorization application file is distributed from the intermediate administrator account to the superior administrator account to generate a subordinate authorization file; the superior administrator account distributes the subordinate authorization file from the superior administrator account to the subordinate administrator account through the intermediate administrator account; the superior administrator account, the intermediate administrator account and the subordinate administrator account are used to use the software in different modules in the electric power equipment engineering simulation calculation platform according to the corresponding permissions.

[0040] A hierarchical authorization mechanism for upper, middle, and lower-level administrators ensures secure and compliant permission control within the power equipment engineering simulation computing platform, effectively preventing the risks of unauthorized operations and abuse. The hierarchical distribution of authorization files, through the upper-level administrator account's authority setting for middle and lower-level administrator accounts, ensures transparency and traceability in permission allocation. Permissions granted at each level are based on specific permission requirements, ensuring that administrators at each level can only access and operate modules within their responsibilities. This matching and review process also provides scalability in permission management, enabling the system to flexibly adjust permissions at each level based on actual needs, avoiding operational obstacles caused by excessive or insufficient permissions. Consequently, the overall system architecture improves software usage efficiency, thereby promoting enterprise efficiency in software use and operation. It enhances system security and management efficiency, simplifies the permission management process, and ensures efficient operation and long-term stability of the system through multi-level, multi-role collaboration. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 This is an application environment diagram of a multi-module software hierarchical authorization management method according to an embodiment;

[0042] Figure 2 A flowchart of a multi-module software hierarchical authorization management method according to an embodiment;

[0043] Figure 3 A flowchart of a method for obtaining a secondary administrator account according to an embodiment;

[0044] Figure 4This is a flowchart of another embodiment of a method for obtaining a senior administrator account;

[0045] Figure 5 A flowchart of a storage information matching method according to an embodiment;

[0046] Figure 6 A flowchart of a permission change operation method according to an embodiment;

[0047] Figure 7 A flowchart of a multi-module software hierarchical authorization management method according to another embodiment;

[0048] Figure 8 This is a structural block diagram of a multi-module software hierarchical authorization management device according to an embodiment;

[0049] Figure 9 The figure is a diagram of the internal structure of a computer device according to an embodiment. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0051] The embodiment of the present application provides a multi-module software hierarchical authorization management method, which can be applied to Figure 1In the application environment shown, the terminal 102 communicates with the server 104 via a network. The data storage system can store data that the server 104 needs to process. The data storage system can be integrated on the server 104 or placed on the cloud or other network servers. In response to the operation of inputting the upper-level administrator account from the terminal 102 into the upper-level authority management file, the server 104 matches the top-level management terminal storage information in the upper-level authority management file with the distributed operation terminal storage information; if the matching result is successful, the upper-level administrator account is used to set up an intermediate administrator account in the power equipment engineering simulation computing platform according to the intermediate administrator role authority requirement information; the intermediate authorization file is distributed from the upper-level administrator account to the intermediate administrator account; according to the lower-level administrator role authority requirement information, the lower-level administrator account is used to set up the lower-level administrator account in the power equipment engineering simulation computing platform; the lower-level authorization application file is distributed from the intermediate administrator account to the upper-level administrator account to generate a lower-level authorization file; the upper-level administrator account distributes the lower-level authorization file from the upper-level administrator account to the lower-level administrator account through the intermediate administrator account; the upper-level administrator account, the intermediate administrator account, and the lower-level administrator account are used to use the software in different modules in the power equipment engineering simulation computing platform according to the corresponding permissions. Among them, the terminal 102 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices, etc. The server 104 can be implemented as a standalone server or a server cluster consisting of multiple servers.

[0052] In one embodiment, Figure 2 As shown, a multi-module software hierarchical authorization management method is provided, which is applied to Figure 1 The following steps are used as an example to illustrate the server in the example:

[0053] Step 202 : In response to the operation of inputting the upper-level administrator account into the upper-level authority management file, the top-level management terminal storage information in the upper-level authority management file is matched with the distributed operation terminal storage information.

[0054] The senior administrator account is the user account with the highest level of authority in the system, responsible for global management and control of platform operations and permission allocation. Through this account, the senior administrator can set and adjust the permissions of administrators at all levels, review authorization applications, distribute authorization documents, and oversee and maintain the operation and security of the entire system.

[0055] The superior authority management file may be a document or data file containing superior administrator authority control information, which records all key information in the system involving authority allocation, management operations, physical parameters, etc.

[0056] Among them, the top-level management terminal storage information can be the core information related to the superior administrator in the system, including the physical address stored in the top-level management terminal (computer), module availability time, company name, and the number of subordinate accounts.

[0057] The distributed operation terminal storage information can include user operations, module operating status, and other management data stored on different operation terminals in the system. Matching this information with the top-level management terminal ensures that the functions and permissions of the distributed operation terminals are consistent with the overall system security policy, ensuring data security and legitimacy.

[0058] Specifically, when the power equipment engineering simulation computing platform is first installed, the software vendor provides the software application company with a superior administrator account (i.e., a first-level administrator account) and a superior permission management file (i.e., a first-level permission management file). The superior permission management file contains top-level management terminal storage information (i.e., first storage information) and distributed operation terminal storage information (i.e., second storage information). The top-level management terminal storage information stores the physical address of the top-level management terminal (computer), module availability time, company name, and number of subordinate accounts. The distributed operation terminal storage information stores the superior administrator account and module authorization information. The superior administrator account is identified by the physical address of the terminal where it was installed, module availability time, and company name. Module authorization information is sorted by power equipment engineering simulation computing platform module, with authorized being 1 and unauthorized being 0. For example, if the engineering simulation computing platform's installed modules are software 1, software 2, software 3, ..., software n, and database 1, database 2, ..., database m, then the module authorization information will have a total of n+m bits, sorted by order. Only when the storage information of the top-level management terminal matches the storage information of the distributed operation terminal, can the upper-level administrator account be used to log in to the power equipment engineering simulation calculation platform interface.

[0059] Step 204 , when the matching result is successful, an intermediate administrator account is set up in the power equipment engineering simulation computing platform using the superior administrator account according to the intermediate administrator role authority requirement information.

[0060] The intermediate administrator role permission requirement information can include specific information describing the scope of permissions and operational permissions required by the intermediate administrator within the system. This information is typically determined by the responsibilities of the senior and intermediate administrators and is used to help senior administrators allocate permissions appropriately, enabling intermediate administrators to manage and operate the corresponding system modules within their responsibilities.

[0061] The power equipment engineering simulation computing platform can be a computing system specifically designed to simulate and emulate the operation and operation of power equipment. The platform supports multi-user and multi-role operations, allowing administrators at different levels to manage and operate different modules according to their authority requirements to perform simulation calculations, data analysis, and system debugging. Calculations involve the coupling of multiple physical fields such as electricity, magnetism, heat, force, flow, and acoustics.

[0062] The intermediate administrator account is a user account set up for intermediate administrators, used to perform operations within their authorized scope within the simulation computing platform. Intermediate administrators manage modules within the platform related to their responsibilities through this account, performing daily system operations and managing the permissions of lower-level administrators. The permissions of this account are set by higher-level administrators based on role requirements to ensure that the intermediate administrator's operational permissions are consistent with their job responsibilities.

[0063] Specifically, if the top-level management terminal storage information matches the distributed operation terminal storage information successfully, and a superior administrator account is available for logging into the power equipment engineering simulation computing platform interface, the superior administrator can use the superior administrator account to create an intermediate administrator account for use by the intermediate administrator and distribute authorization files. The intermediate administrator account created by the superior administrator also includes administrator level identifier information for the second storage information administrator account. Intermediate administrators can create and manage third-level administrator accounts.

[0064] Step 206: Distribute the intermediate authorization file from the superior administrator account to the intermediate administrator account.

[0065] The intermediate authorization file is a permission control file generated by a senior administrator and distributed to an intermediate administrator. It details the scope of the intermediate administrator's operational permissions within the intermediate administrator account. This file ensures that the intermediate administrator can only access and operate the modules and functions within their responsibilities. The file's distribution process is secure and traceable, ensuring compliance with permission allocation.

[0066] Specifically, after an intermediate administrator account is successfully created, the superior administrator generates and signs an intermediate authorization file through the system. This file contains the intermediate administrator's permission information and is securely distributed from the superior administrator account to the intermediate administrator account, ensuring that the intermediate administrator can perform operations within their authority. The system also records the distribution of the authorization file to ensure traceability of the authorization process.

[0067] Step 208: According to the authority requirement information of the subordinate administrator role, a subordinate administrator account is set up in the electric power equipment engineering simulation computing platform using the intermediate administrator account.

[0068] The subordinate administrator role permission requirements can be specific information describing the operational permissions and responsibilities required by the subordinate administrator within the system. These requirements are formulated by the mid-level administrator based on the subordinate administrator's job responsibilities and tasks, ensuring that the subordinate administrator can only access and operate modules related to their work within the system, preventing unauthorized operations.

[0069] The sub-administrator account can be a user account set up for a sub-administrator to perform basic operations in the system. The permissions of this account are assigned by the upper-level or mid-level administrator based on work requirements to ensure that the sub-administrator can complete their specific tasks, but cannot operate other modules beyond the scope of the assigned permissions to maintain system security and management efficiency.

[0070] Specifically, similar to step 204, if the intermediate administrator's account passes security verification and can be used to log in to the power equipment engineering simulation computing platform interface, the intermediate administrator can use the intermediate administrator account to create a subordinate administrator account used by the subordinate administrator and distribute authorization files. The subordinate administrator account created by the intermediate administrator can only be used and cannot create subordinate accounts.

[0071] Step 210 : Distribute the lower-level authorization application file from the intermediate administrator account to the upper-level administrator account to generate a lower-level authorization file.

[0072] The subordinate authorization application document can be generated by a mid-level administrator, recording the specific operational permissions required by the subordinate administrator and submitted to the superior administrator for review. This document serves as the basis for the subordinate administrator's application for permission. Only after approval by the superior administrator can the permission be ultimately granted to the subordinate administrator, thus ensuring the proper allocation and control of permissions.

[0073] The subordinate authorization file is a document generated after the superior administrator reviews and approves the subordinate authorization application. It specifies the subordinate administrator's specific operational permissions within the system. This document is securely transmitted and ultimately distributed by the superior administrator to the subordinate administrator's account. It is used to authorize the subordinate administrator to perform specific operations within the system, ensuring compliance and security of permission settings.

[0074] Specifically, after the intermediate administrator sets up a sub-administrator account for a subordinate administrator, they need to generate a subordinate authorization application file based on the specific responsibilities and permission requirements of the subordinate administrator's sub-administrator account. This file records the specific permissions requested by the subordinate administrator and passes it to the superior administrator for review. During this process, the intermediate administrator is responsible for clarifying the specific work tasks of the subordinate administrator and ensuring that the submitted permission application complies with the system's hierarchical permission control rules. After receiving the application, the superior administrator will review the content of the application to ensure that the scope of the requested permissions is reasonable and complies with the system's security policy.

[0075] Generally, when creating a subordinate administrator account (i.e., a level 3 administrator), an intermediate administrator (i.e., a level 2 administrator) can create an application document containing the account password and authorization file for the subordinate administrator account. The application document contains the first and second storage information corresponding to the subordinate administrator account. The application document is then passed to the superior administrator, who reads it and generates the corresponding authorization management file, which is then distributed to the intermediate administrator. This allows the superior administrator to manage and control the accounts created by the intermediate administrator's subordinates. The total number of intermediate administrators and subordinate administrators should be less than the number of subordinate accounts of the superior administrator.

[0076] In step 212 , the superior administrator account distributes the subordinate authorization file from the superior administrator account to the subordinate administrator account through the intermediate administrator account.

[0077] Specifically, after the superior administrator reviews and confirms the compliance of the subordinate authorization application, the superior administrator generates a subordinate authorization document, which details the specific operational permissions granted to the subordinate administrator. The authorization document generation process adheres to a strict permissions allocation mechanism, ensuring that subordinate administrators can only access system functions within their responsibilities. The superior administrator then transfers the intermediate administrator account clock through the superior administrator account, and further uses the intermediate administrator account to distribute the authorization document, passing the subordinate authorization document to the subordinate administrator's subordinate administrator account.

[0078] Generally, the senior administrator controls the permissions of the mid-level and lower-level administrator accounts, including software expiration dates and executable application modules. This is managed through authorization management files and administrator account information. Senior administrators can view a list of all mid-level administrators and their subordinate lower-level administrators. Senior administrators can also directly view the account information of lower-level administrators they created. Second-level administrators can only view the account information of third-level administrators they created.

[0079] In the above-mentioned multi-module software hierarchical authorization management method, the top-level management terminal storage information in the upper-level authority management file is matched with the distributed operation terminal storage information in response to the operation input into the upper-level authority management file by the upper-level administrator account; when the matching result is successful, the upper-level administrator account is used to set up the intermediate administrator account in the electric power equipment engineering simulation calculation platform according to the intermediate administrator role authority requirement information; the intermediate authorization file is distributed from the upper-level administrator account to the intermediate administrator account; according to the lower-level administrator role authority requirement information, the intermediate administrator account is used to set up the lower-level administrator account in the electric power equipment engineering simulation calculation platform; the lower-level authorization application file is distributed from the intermediate administrator account to the upper-level administrator account to generate a lower-level authorization file; the upper-level administrator account distributes the lower-level authorization file from the upper-level administrator account to the lower-level administrator account through the intermediate administrator account; the upper-level administrator account, the intermediate administrator account and the lower-level administrator account are used to use the software in different modules in the electric power equipment engineering simulation calculation platform according to the corresponding permissions.

[0080] A hierarchical authorization mechanism for upper, middle, and lower-level administrators ensures secure and compliant permission control within the power equipment engineering simulation computing platform, effectively preventing the risks of unauthorized operations and abuse. The hierarchical distribution of authorization files, through the upper-level administrator account's authority setting for middle and lower-level administrator accounts, ensures transparency and traceability in permission allocation. Permissions granted at each level are based on specific permission requirements, ensuring that administrators at each level can only access and operate modules within their responsibilities. This matching and review process also provides scalability in permission management, enabling the system to flexibly adjust permissions at each level based on actual needs, avoiding operational obstacles caused by excessive or insufficient permissions. Consequently, the overall system architecture improves software usage efficiency, thereby promoting enterprise efficiency in software use and operation. It enhances system security and management efficiency, simplifies the permission management process, and ensures efficient operation and long-term stability of the system through multi-level, multi-role collaboration.

[0081] In one embodiment, Figure 3 As shown, in the case of multiple intermediate administrator accounts, according to the intermediate administrator role permission requirements, use the superior administrator account to set the intermediate administrator account in the power equipment engineering simulation calculation platform, including:

[0082] Step 302: Use the superior administrator account to set up each initial administrator account on the power equipment engineering simulation computing platform.

[0083] The initial administrator account is a basic account created by a senior administrator in the system. It has no specific permissions assigned to it and serves only as an initial user identity. This account provides a foundation for subsequent permission assignments and is typically used to pre-define an account identity for mid-level administrators, who can then configure permissions based on role permissions.

[0084] Specifically, in the power equipment engineering simulation computing platform, when a senior administrator identifies the need to set up accounts for multiple mid-level administrators, they first create an initial administrator account for each mid-level administrator using their senior administrator's account. This step assigns each mid-level administrator a separate user identity, but these initial accounts do not have any specific permissions and exist only as basic accounts. This process ensures that each mid-level administrator in the system has a clear identity, providing a foundation for subsequent permission setting and ensuring that account creation and management comply with the system's security standards and structured processes.

[0085] Step 304 : According to the intermediate administrator role authority requirement information, the authority of each initial administrator account is set to obtain each intermediate administrator account.

[0086] Specifically, after the initial administrator account is created, the senior administrator will assign permissions to each mid-level administrator based on their role permission requirements. This step requires the senior administrator to analyze each mid-level administrator's job responsibilities in detail, including the system modules they need to access, the types of operations they need to perform, and the functional permissions they need. Based on these requirements, the senior administrator gradually defines the scope of operation permissions for each initial administrator account, ensuring that they can only perform operations within the designated modules. This process ensures precise allocation of permissions and prevents abuse of permissions, while also meeting all the functional requirements of mid-level administrators within their job responsibilities.

[0087] After permissions are set, the system officially transitions each initial administrator account to an intermediate administrator account. These accounts, with permissions assigned, now have the ability to manage and operate within their respective responsibilities. Each intermediate administrator account now has clear operational permissions, enabling them to access designated simulation computing platform modules and perform assigned tasks.

[0088] In this embodiment, the initial administrator account is set through the superior administrator account, and permissions are allocated according to the permission requirements of the intermediate administrator role, which can effectively ensure the security of the system and the accurate allocation of permissions. By first creating a basic initial administrator account and then gradually setting permissions based on specific responsibilities and needs, the system can flexibly control the operating scope of each intermediate administrator to avoid excessive concentration of permissions or unauthorized operations. This hierarchical setting method improves the transparency of management, makes permission management more controllable, and reduces safety hazards in operation, ensuring the stability and operation efficiency of the power equipment engineering simulation calculation platform.

[0089] In one embodiment, Figure 4 As shown, according to the intermediate administrator role permission requirement information, the permissions of each initial administrator account are set to obtain each intermediate administrator account, including:

[0090] Step 402 : According to the permission requirement information of the intermediate administrator role, the permissions of each initial administrator account are set to obtain each permission-limited administrator account.

[0091] Admin accounts with limited permissions can be assigned to primary administrators based on the role requirements of intermediate administrators. These accounts can access and operate system modules and functions related to their responsibilities, ensuring that each administrator can only perform tasks within their assigned permissions.

[0092] Specifically, after receiving the information about the intermediate administrator role permission requirements required by the intermediate administrator, the senior administrator carefully analyzes the specific responsibilities and task requirements of each intermediate administrator. Based on the information about the intermediate administrator role permission requirements, the senior administrator sets corresponding permissions for each initial administrator account to ensure that each intermediate administrator can only access modules and functions related to their role responsibilities. This process involves dividing the platform's operating permissions according to responsibilities, such as accessing specific data, managing certain modules, or performing certain operations. After the permission setting is completed, the initial administrator account is transformed into a permission-limited administrator account, and each account can only perform operations within a specific permission range to ensure that permissions are not abused or exceeded.

[0093] Step 404 : sort the administrator accounts with limited permissions from high to low according to permissions to obtain a sequence of administrator accounts with limited permissions.

[0094] The privileged administrator account sequence can be a list formed by sorting multiple privileged administrator accounts from highest to lowest according to their privilege scope. This sequence determines the ranking of each administrator based on the resources and functions they can access, with accounts with higher privileges ranked first and accounts with lower privileges ranked last.

[0095] Specifically, the intermediate administrator analyzes the scope of permissions for each restricted-privilege administrator account and sorts them from highest to lowest by permissions, creating a sequence of restricted-privilege administrator accounts. This order is determined by the sensitivity of the system resources each account can access and the breadth of the operational permissions granted. For example, accounts with access to more critical modules are ranked higher in the sequence, while accounts with lower permissions and limited to performing basic tasks are ranked lower. This ranking allows the system to clearly define the hierarchical position of each administrator account within the permissions structure, facilitating subsequent management and permission changes.

[0096] Step 406: Send the authority relationship of each authority-limited administrator account in the authority-limited administrator account sequence to the superior administrator account to obtain an authority setting relationship file.

[0097] The permission setting relationship file can be a document generated by a senior administrator based on the permission-limited administrator account sequence. It details the scope of permissions for each account and their hierarchical relationship within the system. This document ensures clear division of permissions between administrator accounts and standardized operation scopes. The permission setting relationship file not only provides a basis for permission allocation and management but also provides traceability, facilitating future permission review, modification, and maintenance, ensuring the compliance and security of system operations.

[0098] Specifically, based on the sequence of permission-limited administrator accounts, the system passes the relevant permission relationships to the higher-level administrator account. The higher-level administrator reviews these permission relationships to confirm their rationality and compliance with security policies. The system then generates a permission setting relationship file, detailing the scope of permissions for each permission-limited administrator account and its hierarchical relationship within the entire system. This file ensures that permission settings are traceable, facilitating future audits and adjustments. The permission setting relationship file is also a crucial document for the entire system's permission management, recording the permission distribution and hierarchical relationship of each permission-limited administrator account.

[0099] Step 408: Bind the authority-limited administrator accounts according to the authority setting relationship file to obtain intermediate administrator accounts.

[0100] Specifically, after generating the permission setting relationship file, the system performs relationship binding on the permission-limited administrator account based on the permissions and hierarchical relationships in the permission setting relationship file. This step associates the permissions of each permission-limited administrator account with its role and responsibilities in the system, ensuring that each intermediate administrator's permission-limited administrator account not only has appropriate operating permissions, but is also clearly distinguished from other administrators in the permission hierarchy. Through relationship binding, the permission-limited administrator account is officially transformed into an intermediate administrator account with actual operating permissions and the ability to enter the corresponding module to perform work tasks. The binding process ensures that the system's permission structure complies with established rules and provides a clear framework for subsequent permission management.

[0101] In this embodiment, by setting permissions, sorting, and binding relationships for the initial administrator account, accurate permission allocation and hierarchical management of intermediate administrators within the system are effectively achieved. First, by limiting the permissions of each administrator, the system can ensure that the scope of each administrator's operations meets the requirements of their role and avoid abuse of permissions. Then, permission sorting and generating permission setting relationship files make the system's permission structure clearer, making it easier for senior administrators to uniformly manage and review permission relationships. The final relationship binding ensures the coordination and controllability of the permissions of each administrator, improves the security and management efficiency of the system, reduces the risk of permission conflicts, and ensures the efficient operation of the platform.

[0102] In one embodiment, Figure 5 As shown, the top-level management terminal storage information in the upper-level authority management file is matched with the distributed operation terminal storage information, including:

[0103] Step 502: Use a hash mapping method to match the top-level management terminal storage information with the distributed operation terminal storage information to obtain a terminal storage information pairing data chain.

[0104] The terminal storage information pairing data chain is a structure used by the system to compare the storage information of the top-level management terminal with that of the distributed operation terminals. It contains the corresponding hash value pairs. This data chain is generated using a hash mapping method, where each pairing includes the hash value of the top-level management terminal and the hash value of its corresponding distributed operation terminal. By traversing this data chain, the system can compare the storage information of the two terminals item by item, verifying whether they are consistent, and ensuring data consistency and integrity across different terminals.

[0105] Specifically, the system uses a hash mapping method to hash the information stored in the top-level management terminal and the information stored in the distributed operation terminal to generate corresponding information hash values. The hash mapping method maps the original stored data into a hash value of fixed length, allowing for rapid data comparison even with large amounts of data. The system then uses these hash values ​​to generate a paired data chain, in which the hash value of each top-level management terminal's stored information corresponds one-to-one with the hash value of the corresponding distributed operation terminal's stored information. This step ensures that the system can efficiently process and initially compare the two sets of terminal storage information, achieving a fast and accurate matching process through hash mapping, and laying the foundation for subsequent verification.

[0106] Step 504: traverse each hash value in the terminal storage information pairing data chain to find matching failure data.

[0107] Match failure data can be found when traversing the terminal storage information pairing data chain and finding inconsistent hash values ​​between the top-level management terminal and the distributed operation terminal. This data indicates that the storage information between the two terminals is different, which may be caused by data modification, transmission errors, or other reasons.

[0108] Specifically, the system goes through each hash value pair in the terminal storage information pairing data chain, performing a detailed comparison. During this process, the system checks whether each pair of hash values ​​is identical. Dissimilar hash values ​​indicate a discrepancy between the storage information of the top-level management terminal and the distributed operation terminal, resulting in a match failure. The system records each data item that fails to match and marks it as "match failure data." This traversal process allows the system to thoroughly check all stored information, ensuring that no data inconsistencies are missed, providing a thorough check for data verification and security.

[0109] Step 506: When the matching failure data is an empty set, the matching result corresponding to the top-level management terminal storage information and the distributed operation terminal storage information is output.

[0110] Specifically, after the system completes the traversal, it will check the set of data that failed to match. If the set is empty, it means that in the pairing of all terminal storage information, all hash values ​​are successfully matched, which indicates that the storage information of the top-level management terminal and the distributed operation terminal are completely consistent. At this time, the system outputs the result of successful matching, confirming that there is no difference in the storage information of the two terminals, and subsequent operations can continue. If the set is not empty, it means that in the pairing of all terminal storage information, there are hash values ​​that fail to match successfully, then the importance of the information corresponding to the hash value that failed to match successfully is further judged. If the importance is lower than the threshold, subsequent operations can continue. If the importance is equal to or higher than the threshold, a warning is output. This output ensures the consistency and security of the information, proves that the data is complete and reliable, and thus ensures that the system can achieve correct and error-free operation coordination between different terminals.

[0111] In this embodiment, a hash mapping method is used to match the stored information of the top-level management terminal with the distributed operation terminals, effectively improving the speed and accuracy of data matching. By generating a paired data chain through hash mapping, the system can quickly compare large amounts of data and identify mismatches during the traversal process. If the data set for a failed match is an empty set, the information between the two is confirmed to be consistent, ensuring data integrity and security. This method reduces the time complexity and resource consumption of traditional comparison processes, while ensuring the system's efficiency and reliability in terminal information matching, improving the overall operational efficiency and security of the system.

[0112] In one embodiment, Figure 6 As shown, the superior authority management file also includes a network simulation verification condition; after the superior administrator account distributes the subordinate authorization file from the superior administrator account to the subordinate administrator account through the intermediate administrator account, the method further includes:

[0113] Step 602: Use network simulation verification conditions to determine the operation status of the intermediate administrator account and the lower-level administrator account.

[0114] The network simulation verification conditions can be pre-set rules and standards used to evaluate and monitor the operational status of each administrator account in the system. These conditions can include network performance indicators (such as latency and throughput), data transmission accuracy, resource usage, and whether the administrator's operations comply with the scope of authority.

[0115] Specifically, after the lower-level authorization file is successfully distributed to the lower-level administrator account, the system begins to continuously monitor the operation of the intermediate and lower-level administrator accounts based on the network simulation verification conditions set in the upper-level permission management file. Network simulation verification conditions may include technical indicators such as network latency, data transmission integrity, permission operation compliance, resource utilization, and operational compliance. The system uses these conditions to compare the account operations of the intermediate and lower-level administrator accounts item by item to ensure that their permission use and operational behavior are within the specified range, and to ensure that the account's operating status in the system is consistent with the simulation conditions to prevent improper operations or abnormal behavior.

[0116] In a specific embodiment, administrators at all levels can only manage the software within the scope of their authority: module availability time, number of subordinate accounts, and number of subordinate accounts. A timer is set in the power equipment engineering simulation calculation platform to record the time of the first installation of the software and the time of login, which is convenient for time verification. The superior authority management file also includes network simulation verification conditions (i.e., third storage information), which is used to record the time interval of network simulation verification of the intermediate administrator account and the subordinate administrator account (this information is set by the superior administrator when creating the account). When the interval time is reached, it is necessary to connect locally to the enterprise LAN to send a third storage information verification request. The superior administrator verifies the account information through the LAN and authorizes it to continue using it. (For example, online verification is used to control the situation where the first storage information module in the authorization management file is available for a long time, but the use of the account needs to be suspended due to special circumstances).

[0117] Step 604: When the operation status of the intermediate administrator account or the lower administrator account does not meet the network simulation verification conditions, the upper administrator account is requested to perform a permission change operation.

[0118] Specifically, if the system discovers during the monitoring process that the operation behavior or operating status of the intermediate administrator in the intermediate administrator account or the subordinate administrator in the subordinate administrator account does not meet the preset network simulation verification conditions, which may manifest as excessive use of permissions, non-compliant operation procedures, abnormal network activities or resource abuse, the system will immediately generate a warning signal to notify the superior administrator. At this time, the system will send a permission change request to the superior administrator account, reminding it that the current permission settings may have potential security risks, and recommend that the superior administrator take necessary permission change operations, such as restricting certain permissions, temporarily suspending the account, or re-examining the account's authorization documents. Alternatively, a permission change request can be submitted to the superior administrator through the intermediate administrator account or the subordinate administrator, and the superior administrator will review the changes. This mechanism ensures that the system can promptly identify and correct illegal operations and prevent the spread of potential system security vulnerabilities or non-compliant behaviors.

[0119] In this embodiment, by using network simulation verification conditions to monitor the operation of intermediate and lower-level administrator accounts in real time, the system's security and management accuracy are effectively improved. When it is discovered that the operation of an administrator account does not meet the preset network simulation verification conditions, the system will immediately notify the higher-level administrator to change the permissions, preventing potential violations or unsafe behavior. In this way, the system can quickly respond to abnormal situations and adjust permissions in a timely manner to prevent the system from being affected by unauthorized operations, ensuring the normal operation of the platform and data security. This mechanism also provides higher-level administrators with a more flexible permission management method, improving the controllability of overall operations.

[0120] In one embodiment, Figure 7 As shown, the method further includes:

[0121] Step 702: If the matching result is successful, the upper-level administrator account is used to set the intermediate administrator account and the lower-level administrator account in the power equipment engineering simulation computing platform according to the role authority requirement information of the simulation computing platform.

[0122] Specifically, when a senior administrator uses a senior administrator account to create a senior administrator account for a mid-level administrator and a junior administrator account for a junior administrator, they simultaneously create corresponding authorization management files. The accounts and authorization management files are then distributed to the corresponding administrators for installation. This authorization management file records the account information of the senior administrator using the senior administrator account and the account information of the corresponding administrator. Therefore, after the senior administrator uses the senior administrator account to create the senior administrator account for the mid-level administrator and the junior administrator account for the junior administrator, and the authorization management file, and installs them, the senior administrator can use the senior administrator account to log in to the computers installed by these individuals (with total permissions). This authorization management file includes first storage information and second storage information.

[0123] Step 704 : Distribute the intermediate authorization file from the upper-level administrator account to the intermediate administrator account, and distribute the lower-level authorization file from the upper-level administrator account to the lower-level administrator account.

[0124] Specifically, after the intermediate administrator account is created, the system needs to generate and distribute an intermediate authorization file through the superior administrator. The authorization file specifically lists the intermediate administrator's operating permissions on the simulation computing platform, including the modules that can be accessed, the management tasks that can be performed, and the operating boundaries within the system. The superior administrator uses his or her permissions to securely distribute the file to the intermediate administrator account to ensure that the intermediate administrator can only perform operations within the scope of his or her permissions when using the platform. The entire authorization file distribution process is strictly recorded by the system to ensure that the intermediate administrator can use the permissions assigned to them in compliance with regulations and will not exceed the boundaries of their permissions, thereby ensuring the safe operation of the system.

[0125] At the same time, the system generates a subordinate authorization file for the subordinate administrator, which specifies their specific permissions and accessible modules. The superior administrator securely distributes the subordinate authorization file to the subordinate administrator's account through the permissions system under their control. The subordinate authorization file defines the system components that the subordinate administrator can operate, typically with a narrower scope than that of a mid-level administrator, limiting their execution to their specific tasks. Through this authorization process, the superior administrator ensures that the subordinate administrator can perform their job duties without interfering with the work of other administrators or accessing modules outside of their responsibilities, further ensuring the system's operational compliance and hierarchical management.

[0126] In this embodiment, by accurately setting the intermediate and lower-level administrator accounts and distributing the corresponding authorization files based on the role authority requirements of the simulation computing platform under the premise of successful matching, the clarity and standardization of authority management are ensured. The superior administrator assigns authority according to the specific responsibilities of each role to ensure that each administrator can only access modules related to his or her work. This not only improves the security of the system and prevents unauthorized operations, but also simplifies the authority management process and avoids confusion and misoperation in authority allocation. In addition, the distribution of authorization files is controlled by the superior administrator, ensuring that the authority decentralization process is transparent and controllable, further enhancing the security and management efficiency of the system.

[0127] It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the flowcharts of the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0128] Based on the same inventive concept, the embodiments of the present application also provide a multi-module software hierarchical authorization management device for implementing the multi-module software hierarchical authorization management method mentioned above. The implementation solution provided by this device is similar to the implementation solution described in the above method. Therefore, the specific limitations in the embodiments of one or more multi-module software hierarchical authorization management devices provided below can be found in the above-mentioned limitations on the multi-module software hierarchical authorization management method, and will not be repeated here.

[0129] In one embodiment, Figure 8As shown, a multi-module software hierarchical authorization management device is provided, including: an information matching module 802, an account setting module 804, a permission setting module 806 and a permission application module 808, wherein:

[0130] An information matching module 802 is configured to match the top-level management terminal storage information in the upper-level authority management file with the distributed operation terminal storage information in response to an operation inputted into the upper-level authority management file by the upper-level administrator account;

[0131] The account setting module 804 is used to set up an intermediate administrator account in the power equipment engineering simulation computing platform using the upper administrator account according to the intermediate administrator role authority requirement information when the matching result is successful;

[0132] The permission setting module 806 is used to distribute the intermediate authorization file from the upper-level administrator account to the intermediate administrator account;

[0133] The account setting module 804 is further used to use the intermediate administrator account to set up a subordinate administrator account in the power equipment engineering simulation computing platform according to the subordinate administrator role authority requirement information;

[0134] The permission application module 808 is used to distribute the lower-level authorization application file from the intermediate administrator account to the upper-level administrator account to generate a lower-level authorization file;

[0135] The permission setting module 806 is also used by the superior administrator account to distribute the subordinate authorization files from the superior administrator account to the subordinate administrator account through the intermediate administrator account; the superior administrator account, the intermediate administrator account and the subordinate administrator account are used to use the software in different modules in the power equipment engineering simulation calculation platform according to the corresponding permissions.

[0136] In one embodiment, the account setting module 804 is also used to use the superior administrator account to set each initial administrator account in the power equipment engineering simulation computing platform; according to the intermediate administrator role permission requirement information, the permissions of each initial administrator account are set to obtain each intermediate administrator account.

[0137] In one embodiment, the account setting module 804 is also used to set the permissions of each initial administrator account based on the intermediate administrator role permission requirement information to obtain each permission-limited administrator account; sort each permission-limited administrator account from high to low according to the permissions to obtain a permission-limited administrator account sequence; send the permission relationship of each permission-limited administrator account in the permission-limited administrator account sequence to the superior administrator account to obtain a permission setting relationship file; and bind each permission-limited administrator account according to the permission setting relationship file to obtain each intermediate administrator account.

[0138] In one embodiment, the information matching module 802 is also used to use a hash mapping method to match the top-level management terminal storage information with the distributed operation terminal storage information to obtain a terminal storage information pairing data chain; traverse each hash value in the terminal storage information pairing data chain to find matching failure data; when the matching failure data is an empty set, output the matching result corresponding to the top-level management terminal storage information and the distributed operation terminal storage information.

[0139] In one embodiment, the permission application module 808 is also used to use network simulation verification conditions to determine the operating status of the intermediate administrator account and the subordinate administrator account; when the operating status of the intermediate administrator account or the subordinate administrator account does not meet the network simulation verification conditions, the superior administrator account is requested to perform a permission change operation.

[0140] In one embodiment, the account setting module 804 is also used to use the superior administrator account to set up the intermediate administrator account and the subordinate administrator account in the power equipment engineering simulation computing platform according to the role authority requirement information of the simulation computing platform when the matching result is successful; distribute the intermediate authorization file from the superior administrator account to the intermediate administrator account, and distribute the subordinate authorization file from the superior administrator account to the subordinate administrator account.

[0141] Each module in the multi-module hierarchical software authorization management device described above can be implemented in whole or in part through software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.

[0142] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 9 As shown. The computer device includes a processor, a memory, and a network interface connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store server data. The network interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a multi-module software hierarchical authorization management method is implemented.

[0143] Those skilled in the art will understand that Figure 9The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0144] In one embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0145] In one embodiment, a computer-readable storage medium is provided, storing a computer program, which implements the steps in the above-mentioned method embodiments when executed by a processor.

[0146] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps of each of the above-described method embodiments.

[0147] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0148] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the above-mentioned embodiments. In particular, any reference to memory, database, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), data processing logic devices based on quantum computing, and the like.

[0149] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0150] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A multi-module software hierarchical authorization management method, characterized in that: The method comprises: In response to an operation of inputting the upper-level administrator account into the upper-level authority management file, matching the top-level management terminal storage information in the upper-level authority management file with the distributed operation terminal storage information; If the matching result is successful, the intermediate administrator account is set up in the power equipment engineering simulation computing platform using the upper administrator account according to the intermediate administrator role authority requirement information; Distributing the intermediate authorization file from the senior administrator account to the intermediate administrator account; According to the subordinate administrator role authority requirement information, use the intermediate administrator account to set up a subordinate administrator account on the power equipment engineering simulation computing platform; Distribute the subordinate authorization application file from the intermediate administrator account to the superior administrator account to generate a subordinate authorization file; The superior administrator account distributes the subordinate authorization file from the superior administrator account to the subordinate administrator account through the intermediate administrator account; the superior administrator account, the intermediate administrator account and the subordinate administrator account are used to use the software in different modules in the power equipment engineering simulation computing platform according to corresponding permissions.

2. The method according to claim 1, characterized in that In the case where there are multiple intermediate administrator accounts; the intermediate administrator account is set up in the power equipment engineering simulation computing platform using the superior administrator account according to the intermediate administrator role authority requirement information, including: Use the superior administrator account to set up each initial administrator account on the electric power equipment engineering simulation computing platform; According to the intermediate administrator role authority requirement information, the authority of each initial administrator account is set to obtain each intermediate administrator account.

3. The method according to claim 2, characterized in that The process of setting permissions for each initial administrator account based on the intermediate administrator role permission requirement information to obtain each intermediate administrator account includes: According to the intermediate administrator role authority requirement information, the authority of each initial administrator account is set to obtain each authority-limited administrator account; Sort the authority-limited administrator accounts by their respective permissions from high to low to obtain an authority-limited administrator account sequence; Sending the authority relationship of each authority-limited administrator account in the authority-limited administrator account sequence to the superior administrator account to obtain an authority setting relationship file; According to the authority setting relationship file, the authority-limited administrator accounts are bound to obtain the intermediate administrator accounts.

4. The method according to claim 1, wherein The matching of the top-level management terminal storage information in the upper-level authority management file with the distributed operation terminal storage information includes: Use a hash mapping method to match the top-level management terminal storage information with the distributed operation terminal storage information to obtain a terminal storage information pairing data chain; Traversing each hash value in the terminal storage information pairing data chain to find matching failure data; In the case that the matching failure data is an empty set, the matching result corresponding to the top-level management terminal storage information and the distributed operation terminal storage information is output.

5. The method according to claim 1, wherein The superior authority management file further includes a network simulation verification condition; after the superior administrator account distributes the subordinate authorization file from the superior administrator account to the subordinate administrator account through the intermediate administrator account, the method further includes: Using the network simulation verification condition, determining the operation status of the intermediate administrator account and the subordinate administrator account; In the case that the operation status of the intermediate administrator account or the lower administrator account does not meet the network simulation verification condition, the upper administrator account is requested to perform the permission change operation.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: If the matching result is successful, the intermediate administrator account and the subordinate administrator account are set up in the power equipment engineering simulation computing platform using the superior administrator account according to the role authority requirement information of the simulation computing platform; The intermediate authorization file is distributed from the upper-level administrator account to the intermediate administrator account, and the lower-level authorization file is distributed from the upper-level administrator account to the lower-level administrator account.

7. A multi-module software hierarchical authorization management device, characterized in that: The device comprises: an information matching module for matching top-level management terminal storage information with distributed operation terminal storage information in the upper-level authority management file in response to an operation inputted into the upper-level authority management file by the upper-level administrator account; An account setting module is used to set an intermediate administrator account in the power equipment engineering simulation computing platform using the superior administrator account according to the intermediate administrator role authority requirement information when the matching result is successful; The permission setting module is used to distribute the intermediate authorization file from the upper-level administrator account to the intermediate administrator account; The account setting module is further used to use the intermediate administrator account to set a subordinate administrator account in the power equipment engineering simulation computing platform according to the subordinate administrator role authority requirement information; The permission application module is used to distribute the lower-level authorization application file from the intermediate administrator account to the upper-level administrator account to generate a lower-level authorization file; The permission setting module is also used for the superior administrator account to distribute the subordinate authorization file from the superior administrator account to the subordinate administrator account through the intermediate administrator account; the superior administrator account, the intermediate administrator account and the subordinate administrator account are used to use the software in different modules in the power equipment engineering simulation calculation platform according to the corresponding permissions.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images