Multi-module software hierarchical authorization management method and device and computer equipment

Abstract

The invention relates to a multi-module software hierarchical authorization management method and device and computer equipment. The method comprises the following steps: matching storage information of a top management terminal in a superior authority management file with storage information of a distributed operation terminal; if the matching result is successful, using the superior administrator account to set an intermediate administrator account on the electric power equipment engineering simulation calculation platform according to the intermediate administrator role authority demand information; distributing the intermediate authorization file from the superior administrator account to an intermediate administrator account; setting a subordinate administrator account by using an intermediate administrator account according to the role authority demand information of the subordinate administrator; distributing the lower-level authorization application file from the middle-level administrator account to the upper-level administrator account to generate a lower-level authorization file; and 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 software use efficiency can be improved, and then the software use and operation efficiency of an enterprise is improved.

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, device and computer equipment. Background Art

[0002] The multi-physics simulation of power equipment involves the coupling of multiple physical fields such as 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. At the same time, there are many intellectual property rights and data information such as different material parameter libraries, simulation model libraries, engineering case libraries, and corresponding standards and specifications for software applications. The existing technology usually generates authorization files for each software and encrypts the authorization files. When different users use it, the authorization files need to be reinstalled according to the permissions of the user account, and the permissions of the corresponding users need to be updated. The management process is cumbersome, and it is difficult to achieve the management of subordinate departments and user permissions, account numbers, etc. when the top-level management of the enterprise is downward, resulting in low software usage efficiency and affecting 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-mentioned 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 an upper-level administrator account into an upper-level authority management file, matching top-level management terminal storage information in the upper-level authority management file with 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 superior administrator account according to the intermediate administrator role authority requirement information;

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

[0008] According to the subordinate administrator role authority requirement information, using the intermediate administrator account to set up a subordinate administrator account on the electric 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 comprises:

[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 an upper-level administrator account;

[0013] An account setting module, 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] A permission setting module, 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 subordinate authorization application file from the intermediate administrator account to the superior administrator account to generate a subordinate 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 computing platform according to corresponding permissions.

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

[0019] In response to an operation of inputting an upper-level administrator account into an upper-level authority management file, matching top-level management terminal storage information in the upper-level authority management file with 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 superior administrator account according to the intermediate administrator role authority requirement information;

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

[0022] According to the subordinate administrator role authority requirement information, using the intermediate administrator account to set up a subordinate administrator account on the electric 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. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0026] In response to an operation of inputting an upper-level administrator account into an upper-level authority management file, matching top-level management terminal storage information in the upper-level authority management file with 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 superior administrator account according to the intermediate administrator role authority requirement information;

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

[0029] According to the subordinate administrator role authority requirement information, using the intermediate administrator account to set up a subordinate administrator account on the electric 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, and when the computer program is executed by a processor, the following steps are implemented:

[0033] In response to an operation of inputting an upper-level administrator account into an upper-level authority management file, matching top-level management terminal storage information in the upper-level authority management file with 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 superior administrator account according to the intermediate administrator role authority requirement information;

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

[0036] According to the subordinate administrator role authority requirement information, using the intermediate administrator account to set up a subordinate administrator account on the electric 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 computing 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 computing 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 computing platform according to the corresponding permissions.

[0040] Through the hierarchical authorization mechanism of upper, middle and lower administrators, the authority control of the power equipment engineering simulation computing platform is ensured to be carried out under the premise of security and compliance, effectively avoiding the risk of unauthorized operation and abuse of authority. The permission setting of the upper administrator account to the middle and lower administrator accounts and the hierarchical distribution of authorization files ensure the transparency and traceability of authority allocation. The authorization of each level is based on the corresponding authority requirements, ensuring that administrators at all levels can only access and operate modules that meet their scope of responsibility. At the same time, this matching and review process also provides the adjustability of authority management, enabling the system to flexibly adjust the authority of each level according to actual needs, avoiding operational obstacles caused by too many or too few authorities. Therefore, the overall system architecture can improve the efficiency of software use and promote the efficiency of enterprises in software use and operation, improve the security and management efficiency of the system, simplify the process of authority management, and at the same time ensure the efficient operation and long-term stability of the system under multi-level and multi-role collaboration. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0042] FIG2 is a schematic diagram of a flow chart of a multi-module software hierarchical authorization management method according to an embodiment;

[0043] FIG3 is a flow chart of a method for obtaining a secondary administrator account according to an embodiment;

[0044] FIG4 is a flow chart of another method for obtaining a senior administrator account according to an embodiment;

[0045] FIG5 is a schematic diagram of a flow chart of a storage information matching method according to an embodiment;

[0046] FIG6 is a flowchart of a permission change operation method according to an embodiment;

[0047] FIG7 is a flow chart of a multi-module software hierarchical authorization management method according to another embodiment;

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

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

[0050] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0051] A multi-module software hierarchical authorization management method provided in an embodiment of the present application can be applied in an application environment as shown in FIG1. ​​In which, the terminal 102 communicates with the server 104 through 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 it can be placed on the cloud or other network servers. The server 104 responds to the operation of inputting the upper-level administrator account from the terminal 102 into the upper-level authority management file, and matches the top-level management terminal storage information in the upper-level 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 upper-level administrator account is used to set the intermediate administrator account in the power equipment engineering simulation calculation platform; 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 the lower-level administrator account in the 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 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; 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 calculation platform according to the corresponding authority. 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 with an independent server or a server cluster composed of multiple servers.

[0052] In one embodiment, as shown in FIG2 , a multi-module software hierarchical authorization management method is provided, and the method is applied to the server in FIG1 as an example for description, including the following steps:

[0053] Step 202, in response to the 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.

[0054] The senior administrator account can be the user account with the highest authority in the system, responsible for global management and control of the platform's operations and authority allocation. The senior administrator can use this account to set and adjust the authority of administrators at all levels, review authorization applications, distribute authorization files, and supervise and maintain the operation and security of the entire system.

[0055] The superior authority management file may be a document or data file containing the superior administrator's 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 be user operations, module operation status and other management data stored on different operation terminals in the system. Matching with the information of the top-level management terminal is to ensure that the functions and permission settings of the distributed operation terminals are consistent with the overall security policy of the system, and to ensure the security and legality of the data.

[0058] Specifically, when the power equipment engineering simulation computing platform is installed for the first time, the software supplier provides a superior administrator account (i.e., the first-level administrator account) and a superior authority management file (i.e., the first-level authority management file) to the software application enterprise. The superior authority management file contains the top-level management terminal storage information (i.e., the first storage information) and the distributed operation terminal storage information (i.e., the second storage information). The top-level management terminal storage information is stored in the physical address of the top-level management terminal (computer), the module available time, the company name, and the number of subordinate accounts, and the distributed operation terminal storage information is stored in the superior administrator account and module authorization information, where the superior administrator account is identified by the physical address of the terminal installed by the account, the module available time, and the company name. The module authorization information is sorted according to the power equipment engineering simulation computing platform module, with authorization as 1 and unauthorization as 0. For example, if the engineering simulation computing platform installation modules are software 1, software 2, software 3, ..., software n and database 1, database 2, ..., database m, then the module authorization information has a total of n+m bits according to the sorting. Only when the top-level management terminal storage information matches the distributed operation terminal storage information, can the superior 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, according to the intermediate administrator role authority requirement information, use the superior administrator account to set the intermediate administrator account in the power equipment engineering simulation computing platform.

[0060] The intermediate administrator role permission requirement information may be specific content describing the scope of permissions and operation permissions required by the intermediate administrator in the system. This information is usually determined by the responsibilities of the upper and middle administrators, and is used to help the upper administrator reasonably allocate permissions so that the middle administrator can manage and operate the corresponding system modules within the scope of their responsibilities.

[0061] Among them, the power equipment engineering simulation computing platform can be a computing system specifically used to simulate and simulate 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, etc., involving multi-physics field coupling such as electricity, magnetism, heat, force, flow, and sound.

[0062] The intermediate administrator account can be a user account set up for the intermediate administrator, which is used to perform operations within the scope of authority in the simulation computing platform. The intermediate administrator performs daily system operations and authority management of subordinate administrators through the modules related to his / her responsibilities in the account management platform. The authority of the account is set by the superior administrator according to the role requirements to ensure that the operation authority of the intermediate administrator is consistent with his / her job responsibilities.

[0063] Specifically, when the top-level management terminal storage information matches the distributed operation terminal storage information, and the upper-level administrator account can be used to log in to the power equipment engineering simulation calculation platform interface, the upper-level administrator can use the upper-level administrator account to create an intermediate administrator account used by the intermediate administrator and distribute the authorization file. Among the intermediate administrators created by the upper-level administrator, the second storage information administrator account also comes with administrator level identifier information. The intermediate administrator can create and manage the third-level administrator account.

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

[0065] Among them, the intermediate authorization file can be a permission control file generated by the superior administrator and distributed to the intermediate administrator, which records in detail the scope of the intermediate administrator's operating permissions in the intermediate administrator account. This file ensures that the intermediate administrator can only access and operate the modules and functions within his or her scope of responsibility. At the same time, the distribution process of this file is secure and traceable, ensuring the compliance of permission allocation.

[0066] Specifically, after the intermediate administrator account is successfully created, the superior administrator generates and issues an intermediate authorization file through the system. This file contains the permission information of the intermediate administrator and is securely distributed from the superior administrator account to the intermediate administrator account to ensure that the intermediate administrator can perform operations within the scope of his or her authority. At the same time, the system will record the distribution of the authorization file to ensure the 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 requirement information may be specific information describing the operation permissions and responsibilities required by the subordinate administrator in the system. These requirements are formulated by the intermediate administrator based on the job responsibilities and tasks of the subordinate administrator to ensure that the subordinate administrator can only access and operate modules related to their work in the system to avoid unauthorized operations.

[0069] The subordinate administrator account can be a user account set up for the subordinate administrator to perform basic operations in the system. The authority of this account is allocated by the superior administrator or the intermediate administrator according to work requirements to ensure that the subordinate administrator can complete his specific tasks, but cannot operate other modules beyond the scope of the allocated authority to maintain the security and management efficiency of the system.

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

[0071] Step 210, distribute the subordinate authorization application file from the intermediate administrator account to the superior administrator account to generate a subordinate authorization file.

[0072] Among them, the subordinate authorization application file can be a file generated by the intermediate administrator, which records the specific operation permissions required by the subordinate administrator and is submitted to the superior administrator for review as an application. This file is the application basis for the subordinate administrator to obtain permissions. After being reviewed by the superior administrator, the permissions can be finally issued to the subordinate administrator, thereby ensuring the reasonable allocation and control of permissions.

[0073] The subordinate authorization file can be a file generated after the superior administrator reviews and approves the subordinate authorization application, which clarifies the specific operation permissions of the subordinate administrator in the system. The file is securely transmitted and finally distributed by the superior administrator to the subordinate administrator account to authorize the subordinate administrator to perform specific operations in the system, ensuring the compliance and security of the permission setting.

[0074] Specifically, when the intermediate administrator sets up the subordinate administrator's sub-administrator account, it is necessary 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 applied for by the subordinate administrator and passes it to the superior administrator for review. In 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 application content to ensure that the scope of the applied permission is reasonable and complies with the system's security policy.

[0075] Generally, an intermediate administrator (i.e., a second-level administrator) can create an application file for the account password and authorization file of a subordinate administrator account during the process of creating a subordinate administrator account (i.e., a third-level administrator account). The application file contains the first storage information and the second storage information corresponding to the subordinate administrator account. The application file is handed over to the superior administrator for reading, and the corresponding authorization management file is generated and handed over to the intermediate administrator for distribution. The advantage of this is that the superior administrator can manage and control the accounts created by the subordinates of the intermediate administrator, and the number of intermediate administrators + 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 that the application information of the subordinate authorization application document is compliant, the superior administrator generates a subordinate authorization document, which specifies in detail the specific operation permissions obtained by the subordinate administrator. The process of generating the authorization document follows a strict permission allocation mechanism to ensure that the subordinate administrator can only access the system functions within his or her scope of responsibility. Then, the superior administrator transmits 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] In general, the superior administrator controls the permissions of the intermediate and subordinate administrator accounts, including the software expiration time and the executable application modules of the software. Here, the identification management is performed through the authorization management file and the administrator account information. In addition, the superior administrator can see the account information of all intermediate administrators and their subordinates in a list. The superior administrator can also directly see the account information of the subordinate administrators he created. The second-level administrator can only see the third-level administrator information he created.

[0079] In the above-mentioned multi-module software hierarchical authorization management method, by responding to the operation of the superior administrator account input into the superior authority management file, the top-level management terminal storage information in the superior authority management file is matched 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 computing 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 computing 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 computing platform according to the corresponding permissions.

[0080] Through the hierarchical authorization mechanism of upper, middle and lower administrators, the authority control of the power equipment engineering simulation computing platform is ensured to be carried out under the premise of security and compliance, effectively avoiding the risk of unauthorized operation and abuse of authority. The permission setting of the upper administrator account to the middle and lower administrator accounts and the hierarchical distribution of authorization files ensure the transparency and traceability of authority allocation. The authorization of each level is based on the corresponding authority requirements, ensuring that administrators at all levels can only access and operate modules that meet their scope of responsibility. At the same time, this matching and review process also provides the adjustability of authority management, enabling the system to flexibly adjust the authority of each level according to actual needs, avoiding operational obstacles caused by too many or too few authorities. Therefore, the overall system architecture can improve the efficiency of software use and promote the efficiency of enterprises in software use and operation, improve the security and management efficiency of the system, simplify the process of authority management, and at the same time ensure the efficient operation and long-term stability of the system under multi-level and multi-role collaboration.

[0081] In one embodiment, as shown in FIG3 , in the case of multiple intermediate administrator accounts, according to the intermediate administrator role authority requirement information, the upper administrator account is used to set the intermediate administrator account in the power equipment engineering simulation computing platform, including:

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

[0083] The initial administrator account can be a basic account created by a senior administrator in the system. It has not yet been assigned specific permissions and is only used as an initial setting for a user identity. This account provides a basis for subsequent permission allocation and is usually used to pre-set account identities for intermediate administrators. Later, the senior administrator will configure permissions for it according to role permission requirements.

[0084] Specifically, in the power equipment engineering simulation computing platform, when the superior administrator recognizes that accounts need to be set up for multiple intermediate administrators, the initial administrator account of each intermediate administrator is first created through the superior administrator account. This step assigns an independent user identity to each intermediate administrator, but at this time these initial accounts do not have any specific permissions and only exist as basic accounts. This process ensures that each intermediate administrator in the system has a clear identity, which can provide a basis for subsequent permission settings and ensure that the creation and management of accounts meet 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 intermediate administrator based on their role permission requirements. This step requires the senior administrator to analyze the job responsibilities of each intermediate administrator in detail, including the system modules they need to access, the types of operations performed, and the functional permissions. Based on these requirements, the senior administrator gradually sets the scope of operation permissions for each initial administrator account to ensure that they can only perform operations within the specified module. This process ensures accurate allocation of permissions and avoids abuse of permissions, while meeting all functional requirements of intermediate administrators within their job responsibilities.

[0087] After the permission setting is completed, the system will officially transform each initial administrator account into an intermediate administrator account. After the permissions are assigned, these accounts have the ability to manage and operate according to their scope of responsibility. At this point, each intermediate administrator account will have clear operating permissions, can enter the specified simulation computing platform module, and perform the work tasks assigned to them.

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

[0089] In one embodiment, as shown in FIG. 4 , the permissions of each initial administrator account are set according to the permission requirement information of the intermediate administrator role, and each intermediate administrator account is obtained, 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] The permission-limited administrator account can be an account with specific permissions set based on the initial administrator account and the role requirements of the intermediate administrator. These accounts have the ability to access and operate system modules and functions related to their responsibilities, ensuring that each administrator can only perform tasks within the scope of 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 permission-limited administrator account sequence may be a list formed by sorting multiple permission-limited administrator accounts from high to low according to their permission ranges. This sequence determines the sorting position according to the resources and function ranges that each administrator can access, with accounts with higher permissions being ranked first and accounts with lower permissions being ranked later.

[0095] Specifically, the intermediate administrator analyzes the scope of authority of each limited-authority administrator account and sorts them from high to low by authority to obtain a sequence of limited-authority administrator accounts. This sorting is determined based on the sensitivity of the system resources that each account can access and the breadth of the operating authority. For example, accounts with more access rights to key modules are ranked at the front of the sequence, while accounts with lower authority and can only perform basic tasks are ranked at the back. Through this sorting, the system can clearly identify the hierarchical position of each administrator account in the authority structure, which is helpful for subsequent management and authority 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] Among them, the permission setting relationship file can be a document generated by the superior administrator based on the permission-limited administrator account sequence, which records in detail the permission scope of each account and its hierarchical relationship in the system. This file ensures that the permissions between the administrator accounts are clearly divided and the operation scope is standardized. The permission setting relationship file not only provides a basis for permission allocation and management, but also has traceability, which facilitates future permission review, modification and maintenance, and ensures the compliance and security of system operations.

[0098] Specifically, according to the sequence of permission-limited administrator accounts, the system passes its related permission relationships to the superior administrator account. The superior administrator reviews these permission relationships to confirm their rationality and compliance with security policies. Then, the system generates a permission setting relationship file, which records in detail the permission scope of each permission-limited administrator account and its hierarchical relationship in the entire system. This file ensures that the permission settings are well documented, which facilitates the audit and adjustment of permissions in the future. The permission setting relationship file is also an important document for the permission management of the entire system, recording the permission distribution of each permission-limited administrator account and its hierarchical relationship.

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

[0100] Specifically, after generating the permission setting relationship file, the system performs relationship binding on the permission-limited administrator account according to 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 in the system are effectively achieved. First, by limiting the permissions of each administrator, the system can ensure that the scope of operation of each administrator meets the requirements of their role and avoid abuse of permissions. Next, the permissions are sorted and permission setting relationship files are generated, making the system's permission structure clearer and facilitating unified management and review of permission relationships by superior administrators. 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, as shown in FIG. 5 , matching the top-level management terminal storage information in the upper-level authority management file with the distributed operation terminal storage information includes:

[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] Among them, the terminal storage information pairing data chain can be a structure in the system used to compare the storage information of the top-level management terminal and the distributed operation terminal, including the hash value pairings corresponding to the two. This data chain is generated by the hash mapping method, in which each pairing item includes a hash value of a top-level management terminal and its corresponding hash value of the distributed operation terminal. By traversing this data chain, the system can compare the storage information of the two terminals item by item, verify whether the two are consistent, and ensure the consistency and integrity of the data between different terminals.

[0105] Specifically, the system uses the hash mapping method to hash the top-level management terminal storage information and the distributed operation terminal storage information to generate corresponding information hash values. The hash mapping method maps the original storage data to a hash value of a fixed length, so that even if the data volume is large, data comparison can be performed quickly. The system then uses these hash values ​​to generate a paired data chain, in which the hash value of each top-level management terminal storage information corresponds one-to-one to the hash value of the corresponding distributed operation terminal storage information. This step ensures that the system can efficiently process and preliminarily compare the two sets of terminal storage information, achieve a fast and accurate matching process through hash mapping, and lay 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] The match failure data may be the matching items where the hash values ​​of the top-level management terminal and the distributed operation terminal are inconsistent when traversing the terminal storage information matching data chain. These data indicate that the storage information is different between the two terminals, 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 one by one and performs a detailed comparison. During this process, the system checks whether each pair of hash values ​​is exactly the same. Different hash values ​​indicate that there is a difference in the storage information between the top-level management terminal and the distributed operation terminal, which is considered a match failure. For each data item that fails to match, the system records it and marks it as "matching failed data." Through this traversal operation, the system can check all storage information one by one to ensure that any data inconsistency is found without omission, providing a detailed 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, when 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 matched successfully, 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 have not been matched successfully, then the importance of the information corresponding to the hash value that has not been successfully paired is further judged. If the importance is lower than the threshold, the subsequent operation 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, the storage information of the top-level management terminal and the distributed operation terminal is matched by using the hash mapping method, which effectively improves the speed and accuracy of data matching. By generating a pairing data chain by the hash mapping method, the system can quickly compare large-scale data and identify mismatches during the traversal process. If the matching failed data is an empty set, it is confirmed that the information of the two is consistent, ensuring the integrity and security of the data. This method reduces the time complexity and resource consumption in the traditional comparison process, while ensuring the efficiency and reliability of the system in terminal information matching, and improving the overall operation efficiency and security of the system.

[0112] In one embodiment, as shown in FIG6 , 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:

[0113] Step 602, using network simulation verification conditions to determine the operation status of the intermediate administrator account and the subordinate administrator account.

[0114] The network simulation verification conditions may be preset rules and standards for evaluating and monitoring the operating status of each administrator account in the system. These conditions may include network performance indicators (such as latency, throughput, etc.), data transmission accuracy, resource usage, and whether the administrator's operation behavior complies with the scope of authority.

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

[0116] In a specific embodiment, administrators at all levels can only manage the software within 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 (ie: 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, a local connection is required to enter 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 to use 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 condition, the upper administrator account is requested to perform a permission change operation.

[0118] Specifically, if the system finds 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 be manifested as excessive use of permissions, non-compliance with regulations for operating 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 setting 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 files. Alternatively, submit a permission change request to the superior administrator through the intermediate administrator account or the subordinate administrator, and the superior administrator will review the change. 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, the operation of the intermediate and lower-level administrator accounts is monitored in real time using network simulation verification conditions, which effectively improves the security and management accuracy of the system. When it is found that the operation of the administrator account does not meet the preset network simulation verification conditions, the system will immediately notify the superior administrator to change the permission to prevent potential violations or unsafe behaviors. In this way, the system can quickly respond to abnormal situations, adjust permissions in time, avoid the system from being affected by unauthorized operations, and ensure the normal operation of the platform and data security. This mechanism also provides a more flexible permission management method for superior administrators, improving the controllability of the overall operation.

[0120] In one embodiment, as shown in FIG7 , the method further includes:

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

[0122] Specifically, when the superior administrator uses the superior administrator account to create the intermediate administrator account of the intermediate administrator and the low-level administrator account of the low-level administrator, the corresponding authorization management files are created simultaneously, and the account and the authorization management file are distributed to the corresponding administrator identity personnel for installation. This authorization management file records the account information of the superior administrator using the superior administrator account and the account information of the corresponding administrator. Therefore, after the intermediate administrator account of the intermediate administrator and the low-level administrator account of the low-level administrator created by the superior administrator using the superior administrator account and the authorization management file are installed, the superior administrator can log in to the computer installed by these people using the superior administrator account (total authority). This authorization management file includes the first storage information and the 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 without exceeding the boundaries of their permissions, thereby ensuring the safe operation of the system.

[0125] At the same time, the system will also generate a subordinate authorization file for the subordinate administrator, which specifies the specific permissions and accessible modules of the subordinate administrator. The superior administrator will securely distribute the subordinate authorization file to the subordinate administrator account through the permission system controlled by it. The subordinate authorization file defines the part of the system that the subordinate administrator can operate, which is usually smaller than the scope of the 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 that are not their responsibilities, further ensuring the operational compliance and hierarchical management of the system.

[0126] In this embodiment, by accurately setting the intermediate and subordinate 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 to ensure 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 involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0128] Based on the same inventive concept, the embodiment of the present application also provides a multi-module software hierarchical authorization management device for implementing the multi-module software hierarchical authorization management method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the embodiments of one or more multi-module software hierarchical authorization management devices provided below can refer to the limitations of a multi-module software hierarchical authorization management method above, and will not be repeated here.

[0129] In one embodiment, as shown in FIG8 , 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] The information matching module 802 is used 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 the operation input into the upper-level authority management file by the upper-level administrator account;

[0131] The account setting module 804 is used to set the 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 administrator account to the intermediate administrator account;

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

[0134] The permission application module 808 is used to distribute the subordinate authorization application file from the intermediate administrator account to the superior administrator account to generate a subordinate authorization file;

[0135] The authority setting module 806 is also used for 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 on the 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.

[0137] In one embodiment, the account setting module 804 is also used to set the permissions of each initial administrator account according to the permission requirement information of the intermediate administrator role, and obtain each permission-limited administrator account; sort each permission-limited administrator account from high to low according to the permissions, and 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, and obtain a permission setting relationship file; according to the permission setting relationship file, bind the relationship between each permission-limited administrator account 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 conditions of the intermediate administrator account and the subordinate administrator account; when the operating conditions of the intermediate administrator account or the subordinate administrator account do 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 above-mentioned multi-module software hierarchical authorization management device can be implemented in whole or in part by software, hardware, or a combination thereof. Each of the above-mentioned modules 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 a computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0142] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG9 . 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 the 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 the structure shown in FIG. 9 is merely a block diagram of a partial 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 arrangement of components.

[0144] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, 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 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 includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps in the above-mentioned 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 can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and 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 embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium 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), magnetoresistive 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. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0149] The technical features of the above embodiments may 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 only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A multi-module software hierarchical authorization management method, characterized in that: The method comprises: In response to an operation of inputting an upper-level administrator account into an upper-level authority management file, matching top-level management terminal storage information in the upper-level authority management file with 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 superior administrator account according to the intermediate administrator role authority requirement information; Distributing the intermediate authorization file from the superior administrator account to the intermediate administrator account; According to the subordinate administrator role authority requirement information, using the intermediate administrator account to set up a subordinate administrator account on the electric 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 on 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 of the initial administrator accounts is set to obtain each of the intermediate administrator accounts.

3. The method according to claim 2, characterized in that The step of setting permissions for each of the initial administrator accounts according to the permission requirement information of the intermediate administrator role to obtain each of the intermediate administrator accounts 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 from high to low according to their authority to obtain an authority-limited administrator account sequence; Sending the authority relationship of each of the authority-limited administrator accounts 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, characterized in that 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, characterized in that 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: Using the network simulation verification condition, determining the operation status of the intermediate administrator account and the subordinate administrator account; When the operation status of the intermediate administrator account or the subordinate administrator account does not meet the network simulation verification condition, the superior administrator account is requested to perform a 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 in the electric 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 administrator account to the intermediate administrator account, and the lower authorization file is distributed from the upper administrator account to the lower 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 an upper-level administrator account; An account setting module, 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; A permission setting module, 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 subordinate authorization application file from the intermediate administrator account to the superior administrator account to generate a subordinate 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 computing platform according to 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