A multi-tenant management method, a management platform and a storage medium

Abstract

The application provides a multi-tenant management method, a management platform and a storage medium. The method comprises the following steps: obtaining a multi-tenant management request, wherein the multi-tenant management request comprises resource permission information of multiple projects and project information of multiple users; constructing a tenant tree structure according to the resource permission information of the multiple projects, and configuring corresponding resource permissions for each tenant in the tenant tree structure; wherein each tenant in the tenant tree structure comprises at least one project; determining a tenant to which each user belongs according to the project information of the user, and binding the user with the tenant to which the user belongs, so that the user obtains the resource permissions of the tenant to which the user belongs. The method of the application realizes a more flexible and easy-to-operate multi-tenant management method, and meets the business requirements under the change and adjustment of administrative organizations.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a multi-tenant management method, management platform and storage medium. Background Technology

[0002] Multi-tenancy is a software architecture technique used to enable multiple users to share the same system or program components while ensuring data isolation between users. In cloud computing platforms, tenants typically act as carriers of data or resources, while users are the actual users of that data or resources within a tenant's domain.

[0003] Existing multi-tenant management architectures are usually based on corporate administrative organizations. Once the organization changes, the corresponding platform tenant system and resource allocation need to be re-planned, which adds a lot of tedious and complex work. Moreover, when a user's tenant changes, the user's corresponding resource permissions will also change. However, in many cases, although the user's position in the organization changes, it is still desirable to continue the previous resource permissions based on business needs. This requires special settings for the user, which is complicated and inconvenient.

[0004] There is an urgent need for a more flexible and easy-to-operate multi-tenant management method to meet the business needs under changes and adjustments in administrative organizations. Summary of the Invention

[0005] This application provides a multi-tenant management method, management platform, and storage medium to solve the technical problem that existing technologies, which build multi-tenant management architectures based on enterprise administrative organizations, require complex and cumbersome replanning and setting up of the multi-tenant management architecture when administrative organizations change or are adjusted.

[0006] In a first aspect, this application provides a multi-tenant management method, comprising: obtaining a multi-tenant management request, the multi-tenant management request including resource permission information of multiple projects and project information of multiple users; constructing a tenant tree structure according to the resource permission information of the multiple projects, and configuring corresponding resource permissions for each tenant in the tenant tree structure; wherein each tenant in the tenant tree structure includes at least one of the projects; determining the tenant to which the user belongs according to the project information of each user, and binding the user to the tenant to which the user belongs, so that the user can obtain the resource permissions of the tenant to which the user belongs.

[0007] Optionally, in the method described above, the step of constructing a tenant tree structure based on the resource permission information of the multiple projects includes: for each project, determining whether the resource permissions of the project are the same as those of other projects; if the resource permissions of the project are not the same as those of other projects, then the project is treated as a tenant; if the resource permissions of the project are the same as those of at least one other project, then the projects with the same resource permissions are merged to form a tenant; for each tenant, setting the tenant level according to the tenant's resource permissions to construct a tenant tree structure; wherein, the resource permissions of each level of the tenant in the tenant tree structure are greater than the resource permissions of the next level of the tenant.

[0008] Optionally, in the method described above, configuring corresponding resource permissions for each tenant in the tenant tree structure includes: for each tenant, obtaining the cloud account associated with the resource permissions of the tenant; binding the tenant to the cloud account so that the tenant can obtain the corresponding resource permissions.

[0009] Optionally, in the method described above, determining the tenant to which the user belongs based on the project information of each user includes: for each user, determining the project to which the user belongs based on the project information of the user; determining the tenant to which the project is located, thereby determining the tenant to which the user belongs.

[0010] Optionally, the method described above further includes: obtaining a tenant binding request sent by the user, the tenant binding request including a tenant identifier to be bound; sending a binding confirmation request to the tenant corresponding to the tenant identifier to be bound, and binding the user to the tenant corresponding to the tenant identifier to be bound when receiving confirmation information from the tenant, so that the user can obtain the resource permissions of the tenant.

[0011] Optionally, the method described above further includes: for each user, obtaining the user's operation permission information and querying the role corresponding to the operation permission information; binding the user to the role so that the user obtains the operation permissions corresponding to the operation permission information.

[0012] Optionally, the method described above further includes: obtaining a role binding request sent by a user, the role binding request including a role identifier to be bound; unbinding the user from its currently bound role, and binding the user to the role corresponding to the role identifier to be bound, so that the user obtains the operation permissions of the role corresponding to the role identifier to be bound.

[0013] Secondly, this application provides a multi-tenant management platform, comprising: an acquisition module for acquiring a multi-tenant management request, the multi-tenant management request including resource permission information of multiple projects and project information of multiple users; a processing module for constructing a tenant tree structure based on the resource permission information of the multiple projects, and configuring corresponding resource permissions for each tenant in the tenant tree structure; wherein each tenant in the tenant tree structure includes at least one of the projects; the processing module is further configured to determine the tenant to which the user belongs based on the project information of each user, and bind the user to the tenant to which the user belongs, so that the user can obtain the resource permissions of the tenant to which the user belongs.

[0014] Thirdly, this application provides a multi-tenant management platform, including: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the multi-tenant management method as described in the first aspect.

[0015] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the multi-tenant management method as described in the first aspect.

[0016] This application provides a multi-tenant management method, management platform, and storage medium. The method involves obtaining a multi-tenant management request, which includes resource permission information for multiple projects and project information for multiple users. Based on the resource permission information of the multiple projects, a tenant tree structure is constructed, and corresponding resource permissions are configured for each tenant in the tree structure. Each tenant in the tree structure includes at least one project. Based on each user's project information, the tenant to which the user belongs is determined, and the user is bound to their respective tenant, enabling the user to obtain the resource permissions of their tenant. Compared to existing technologies that build multi-tenant management architectures based on enterprise administrative organizational structures, this application constructs a tenant tree structure based on project resource permission information and binds users to their respective tenants, enabling users to obtain the resource permissions of their tenants. Thus, the construction of the multi-tenant management architecture is independent of organizational structure. Therefore, when the organizational structure changes, there is no need to re-plan the multi-tenant management architecture, and the user's tenant does not need to be changed, allowing the continuation of previous resource permissions and avoiding a large amount of tedious and complex work. This achieves a more flexible and easy-to-operate multi-tenant management method, meeting the business needs under changes and adjustments in administrative organizational structures. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0018] Figure 1 This is a schematic diagram of a multi-tenant management architecture in existing technologies;

[0019] Figure 2 A flowchart illustrating a multi-tenant management method according to an embodiment of this application;

[0020] Figure 3 This is a schematic diagram of a multi-tenant management architecture provided in an embodiment of this application;

[0021] Figure 4 A flowchart illustrating a second embodiment of a multi-tenant management method provided in this application;

[0022] Figure 5 A flowchart illustrating a third embodiment of a multi-tenant management method provided in this application;

[0023] Figure 6 A flowchart illustrating a fourth embodiment of a multi-tenant management method provided in this application;

[0024] Figure 7 This is a schematic diagram of the structure of a multi-tenant management platform embodiment provided in this application.

[0025] Figure 8 This is a schematic diagram of another embodiment of a multi-tenant management platform provided in this application.

[0026] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0027] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0028] 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, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0029] The specific application scenario of this application is a multi-tenant management platform. Multi-tenancy technology is a software architecture technology used to enable multiple users to share the same system or program components while ensuring data isolation between users. In cloud computing platforms, tenants typically act as carriers of data or resources, while users are the actual users of the data or resources under a tenant.

[0030] Existing multi-tenant management architectures are typically based on corporate administrative organizations. Figure 1 This is a schematic diagram of a multi-tenant management architecture in existing technologies. Figure 1 The diagram on the left shows the administrative organization of a company. The first-level organization is the group company, the second-level organizations are subsidiary A and subsidiary B, ..., the fifth-level organizations are department a and department b, and each department has multiple users. Figure 1 The diagram on the right is a multi-tenant management architecture diagram established based on the company's administrative organization. The group company is designated as the first-level tenant, subsidiary A and subsidiary B as second-level tenants A and B respectively, ..., department a and department b as fifth-level tenants a and b respectively. Users under each tenant enjoy the resource permissions of that tenant.

[0031] However, a company's administrative organization will change as the company develops. Once the organization changes, the corresponding platform tenant system and resource allocation need to be re-planned, which adds a lot of tedious and complicated work. Moreover, when a user's tenant changes, the user's corresponding resource permissions will also change. However, many times, although the user's position in the organization has changed, it is still desirable to continue the previous resource permissions based on business needs. This requires special settings for the user, which is complicated and inconvenient.

[0032] Based on the aforementioned technical problems, the technical concept of this application is: how to provide a more flexible and easy-to-operate multi-tenant management method to meet the business needs under changes and adjustments in administrative organizations.

[0033] The multi-tenant management method provided in this application aims to solve the above-mentioned technical problems of the prior art.

[0034] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0035] Figure 2 A flowchart illustrating a multi-tenant management method according to an embodiment of this application is provided. See also: Figure 2 The multi-tenant management method includes the following steps:

[0036] Step S201: Obtain a multi-tenant management request, which includes resource permission information for multiple projects and project information for multiple users.

[0037] In this embodiment, the multi-tenant management platform builds a multi-tenant management architecture based on the resource permissions of the project. For example, the project can be a business project, such as a research and development project; or it can be an organization, such as a research and development department or team. Each project can include multiple users; for example, users can be administrators and researchers.

[0038] A multi-tenant management platform can receive multi-tenant management requests, which may include resource permission information for multiple projects and project information for multiple users. Resource permission information indicates the resources that a project can use; specifically, resources may include computing resources, storage resources, and network resources. User project information indicates the project to which a user belongs.

[0039] Step S202: Based on the resource permission information of the multiple projects, construct a tenant tree structure and configure corresponding resource permissions for each tenant in the tenant tree structure.

[0040] Each tenant in this tenant tree structure includes at least one item.

[0041] In this embodiment, the multi-tenant management platform can construct a tenant tree structure based on the resource permission information of multiple projects. Figure 3 This is a schematic diagram of a multi-tenant management architecture provided in an embodiment of this application. For example, the resource permission information of multiple projects can indicate that: the resource that "R&D Team 1" can use is "Computing Resource A", the resource that "R&D Team 2" can use is "Computing Resource B", the resource that "R&D Team 3" can use is "Computing Resource A", the resource that "R&D Team 4" can use is "Computing Resource B", and the resource that "R&D Team 5" can use is "Computing Resource C".

[0042] The "R&D Team 1" and "R&D Team 3" with the same resource permissions can be merged to form "Tenant A"; "R&D Team 2" and "R&D Team 4" can be merged to form "Tenant B"; "R&D Team 5" has different resource permissions from other projects, so "R&D Team 5" can be designated as "Tenant C".

[0043] The "R&D Department" has access to all resources and can be considered a first-level tenant. The resource permissions for "R&D Project 1" are "Computing Resource A" and "Computing Resource B", therefore "R&D Project 1" is the parent tenant of "Tenant A" and "Tenant B". The resource permissions for "R&D Project 2" are "Computing Resource C" and "Computing Resource D", therefore "R&D Project 2" is the parent tenant of "Tenant C". Both "R&D Project 1" and "R&D Project 2" are second-level tenants. "Tenant A", "Tenant B", and "Tenant C" are all third-level tenants.

[0044] After constructing the tenant tree structure, corresponding resource permissions can be configured for each tenant in the tree structure. For example, resource permissions can be configured by binding tenants to cloud accounts. Each tenant's available resources correspond to a cloud account. By obtaining the cloud account associated with the tenant's resource permissions and binding the tenant to that cloud account, the corresponding resource permissions can be configured for the tenant.

[0045] Step S203: Based on each user's project information, determine the tenant to which the user belongs, and bind the user to the tenant to enable the user to obtain the resource permissions of the tenant.

[0046] In this embodiment, user information can indicate the project to which the user belongs. When the project is a business project, the user information can indicate the business project to which the user belongs, such as the aforementioned "R&D Project One" and "R&D Project Two"; when the project is an organization, the user information can indicate the organization to which the user belongs, such as the aforementioned "R&D Department" and "R&D Team 1".

[0047] After constructing the tenant tree structure, the tenant to which each user belongs can be determined based on their project information. For example, by determining the project to which a user belongs based on their project information, and then determining the tenant to which that project belongs, the tenant to which the user belongs can be identified. Binding the user to their respective tenant allows each user to access the resource permissions of their assigned tenant.

[0048] In this embodiment, the multi-tenant management platform obtains a multi-tenant management request, which includes resource permission information for multiple projects and project information for multiple users. Based on the resource permission information of the multiple projects, a tenant tree structure is constructed, and corresponding resource permissions are configured for each tenant in the tenant tree structure. Each tenant in the tenant tree structure includes at least one project. Based on each user's project information, the tenant to which the user belongs is determined, and the user is bound to their respective tenant, enabling the user to obtain the resource permissions of their tenant. Compared to existing technologies that construct multi-tenant management architectures based on enterprise administrative organizational structures, this application constructs a tenant tree structure based on project resource permission information and binds users to their respective tenants, enabling users to obtain the resource permissions of their tenants. Thus, the construction of the multi-tenant management architecture is independent of organizational structure. Therefore, when the organizational structure changes, there is no need to re-plan the multi-tenant management architecture, and the user's tenant does not need to be changed, allowing the continuation of previous resource permissions and avoiding a large amount of tedious and complex work. This implements a more flexible and easy-to-operate multi-tenant management method, meeting the business needs under changes and adjustments in administrative organizational structures.

[0049] Figure 4 A flowchart illustrating a second embodiment of a multi-tenant management method provided in this application is shown below. Figure 4 The above step S202 includes the following steps:

[0050] Step S401: For each project, determine whether the resource permissions of the project are the same as those of other projects; if not, proceed to step S402; if yes, proceed to step S403.

[0051] Step S402: If the resource permissions of this project are different from those of other projects, then this project will be treated as a tenant.

[0052] Step S403: If the resource permissions of this project are the same as those of at least one other project, then merge the projects with the same resource permissions to form a single tenant.

[0053] In this embodiment, the multi-tenant management platform can construct a tenant tree structure based on the resource permission information of multiple projects. For example, multiple projects may include organizations, such as "R&D Department", "R&D Team 1", "R&D Team 2", "R&D Team 3", "R&D Team 4" and "R&D Team 5", and may also include business projects, such as "R&D Project 1" and "R&D Project 2".

[0054] The resource permission information for each project indicates the resources it can use. For example, the "R&D Department" has access to all resources, "R&D Team 1" can use "Computing Resource A", "R&D Team 2" can use "Computing Resource B", "R&D Team 3" can use "Computing Resource A", "R&D Team 4" can use "Computing Resource B", "R&D Team 5" can use "Computing Resource C", "R&D Project 1" has resource permissions of "Computing Resource A" and "Computing Resource B", and "R&D Project 2" has resource permissions of "Computing Resource C" and "Computing Resource D".

[0055] For each project, it can be determined whether the resource permissions of the project are the same as those of other projects. If the resource permissions of the project are different from those of other projects, the project is treated as a tenant. If the resource permissions of the project are the same as those of at least one other project, the projects with the same resource permissions are merged to form a single tenant.

[0056] As mentioned in the previous example, "R&D Team 5" has different resource permissions than other projects, so "R&D Team 5" can be treated as an independent tenant "Tenant C"; "R&D Team 1" and "R&D Team 3" have the same resource permissions, so "R&D Team 1" and "R&D Team 3" can be merged to form "Tenant A"; "R&D Team 2" and "R&D Team 4" have the same resource permissions, so "R&D Team 2" and "R&D Team 4" can be merged to form "Tenant B".

[0057] Step S404: For each tenant, set the tenant level according to the tenant's resource permissions to build a tenant tree structure.

[0058] In this tenant tree structure, the resource permissions of each level of tenant are greater than the resource permissions of the next level of tenant.

[0059] In this embodiment, for each tenant, the tenant level can be set according to the tenant's resource permissions to construct a tenant tree structure, where the resource permissions of each level tenant are greater than those of the next level tenant.

[0060] As mentioned in the previous example, "R&D Department" has access to all resources and can be considered a first-level tenant; "R&D Project 1" has resource permissions for "Computing Resource A" and "Computing Resource B", therefore "R&D Project 1" is the parent tenant of "Tenant A" and "Tenant B"; "R&D Project 2" has resource permissions for "Computing Resource C" and "Computing Resource D", therefore "R&D Project 2" is the parent tenant of "Tenant C"; "R&D Project 1" and "R&D Project 2" are both second-level tenants; "Tenant A", "Tenant B", and "Tenant C" are all third-level tenants.

[0061] Step S405: For each tenant, obtain the cloud account associated with the tenant's resource permissions.

[0062] Step S406: Bind the tenant to the cloud account so that the tenant can obtain the corresponding resource permissions.

[0063] After constructing the tenant tree structure, you can configure corresponding resource permissions for each tenant in the tree structure. Specifically, resource permissions can be configured by binding tenants to cloud accounts. Each tenant's available resources correspond to a cloud account. For each tenant, you can obtain the cloud account associated with that tenant's resource permissions, bind the tenant to that cloud account, and then configure the corresponding resource permissions for that tenant.

[0064] In this embodiment, the multi-tenant management platform constructs a tenant tree structure based on the project's resource permission information and binds tenants to cloud accounts associated with resource permissions, enabling tenants to obtain the corresponding resource permissions. Thus, the construction of the multi-tenant management architecture is independent of organizational structure, eliminating the need for replanning when the organizational structure changes, and avoiding a large amount of tedious and complex work. This further realizes a more flexible and easy-to-operate multi-tenant management method, meeting the business needs under changes and adjustments in administrative organizational structures.

[0065] Figure 5 A flowchart illustrating a third embodiment of a multi-tenant management method provided in this application is shown below. Figure 5 The above step S203 specifically includes the following steps:

[0066] Step S501: For each user, determine the project to which the user belongs based on the user's project information.

[0067] Step S502: Determine the tenant to which the project belongs, in order to determine the tenant to which the user belongs.

[0068] In this embodiment, the user's project information can indicate the project to which the user belongs. For example, the user's project information can indicate that the user belongs to an organization, such as "R&D Department", "R&D Team 1", "R&D Team 2", "R&D Team 3", "R&D Team 4" and "R&D Team 5", or a business project, such as "R&D Project 1" and "R&D Project 2".

[0069] For each user, the multi-tenant management platform can determine the project to which the user belongs based on the user's project information. For example, based on the user's project information, the project to which the user belongs is determined to be "R&D Team 1".

[0070] After determining the project to which the user belongs, the tenant of that project is identified to determine the tenant to which the user belongs. As mentioned in the previous example, the tenant of the project "R&D Team 1" is "Tenant A", so the user's tenant can be determined to be "Tenant A". Binding the user to "Tenant A" will grant the user access to the resources of "Tenant A".

[0071] The multi-tenant management method of this application also supports users binding to multiple tenants. Specifically, the multi-tenant management method further includes the following steps:

[0072] Step S503: Obtain the tenant binding request sent by the user, which includes the identifier of the tenant to be bound.

[0073] Step S504: Send a binding confirmation request to the tenant corresponding to the tenant identifier to be bound, and when the confirmation information is received from the tenant, bind the user to the tenant corresponding to the tenant identifier to be bound, so that the user can obtain the resource permissions of the tenant.

[0074] In this embodiment, the multi-tenant management platform can obtain the tenant binding request sent by the user, which includes the identifier of the tenant to be bound.

[0075] The multi-tenant management platform can send a binding confirmation request to the tenant corresponding to the tenant identifier to be bound. The management terminal of the tenant corresponding to the tenant identifier to be bound can respond based on the binding confirmation request: if it accepts the user's binding, it will send a confirmation message; if it does not accept the user's binding, it will send a rejection message.

[0076] When the multi-tenant management platform receives confirmation from the tenant, it can bind the user to the tenant corresponding to the tenant identifier to be bound, so that the user can obtain the resource permissions of the tenant.

[0077] In this embodiment, the multi-tenant management platform can determine the tenant to which each user belongs based on their project information, and bind the user to that tenant. It also supports binding a user to multiple tenants, allowing the user to obtain resource permissions from multiple tenants. This flexible binding of users and tenants enables a more flexible and easy-to-operate multi-tenant management method, meeting the business needs under changes and adjustments in administrative organizational structures.

[0078] Figure 6 A flowchart illustrating a fourth embodiment of a multi-tenant management method provided in this application is shown below. Figure 5 The multi-tenant management method also includes the following steps:

[0079] Step S601: For each user, obtain the user's operation permission information and query the role corresponding to the operation permission information.

[0080] Step S602: Bind the user to the role so that the user can obtain the operation permissions corresponding to the operation permission information.

[0081] In this embodiment, each user also has operation permission information, which indicates the user's operation permissions for resources, such as "read-only" or "read-write" operation permissions.

[0082] For each user, the multi-tenant management platform can obtain that user's operation permission information and query the role corresponding to that operation permission information. Different operation permissions correspond to different roles. For example, the role "administrator" has "read and write" operation permissions, and the role "member" has "read-only" operation permissions. If the multi-tenant management platform obtains the user's operation permission information as "read and write," it can determine that the role corresponding to that operation permission information is "administrator."

[0083] The multi-tenant management platform can bind a user to a role, thereby granting the user the operation permissions corresponding to that permission information. For example, binding a user to the role "administrator" will grant the user "read and write" operation permissions.

[0084] The multi-tenant management method of this application also supports the unbinding and rebinding of users and roles. Specifically, the multi-tenant management method also includes the following steps:

[0085] Step S603: Obtain the role binding request sent by the user, which includes the identifier of the role to be bound.

[0086] Step S604: Unbind the user from its currently bound role, and bind the user to the role corresponding to the role to be bound, so that the user can obtain the operation permissions of the role corresponding to the role to be bound.

[0087] In this embodiment, the multi-tenant management platform can obtain the role binding request sent by the user, which includes the identifier of the role to be bound.

[0088] The multi-tenant management platform can first unbind the user from its currently bound role, and then bind the user to the role corresponding to the role identifier to be bound, so that the user can obtain the operation permissions of the role corresponding to the role identifier to be bound.

[0089] For example, the multi-tenant management platform receives a role binding request sent by a user. The role binding request includes a role identifier to be bound, and the role corresponding to the role to be bound is "Member," while the user's current bound role is "Administrator." The multi-tenant management platform can first unbind the user from the role "Administrator," and then bind the user to the role "Member," so that the user obtains the operation permissions of the role "Member."

[0090] In this embodiment, the multi-tenant management platform binds users to roles based on their operation permission information. It also supports unbinding and rebinding users to roles to grant users the corresponding operation permissions. After binding with a tenant and obtaining resource permissions, users further acquire operation permissions on those resources, thus realizing a more flexible and easy-to-operate multi-tenant management method that meets the business needs under changes and adjustments in administrative organizational structures.

[0091] Figure 7 This is a schematic diagram illustrating the structure of a multi-tenant management platform embodiment provided in this application. (See attached diagram.) Figure 7 As shown, the multi-tenant management platform 70 includes an acquisition module 71 and a processing module 72. The acquisition module 71 acquires multi-tenant management requests, which include resource permission information for multiple projects and project information for multiple users. The processing module 72 constructs a tenant tree structure based on the resource permission information of the multiple projects and configures corresponding resource permissions for each tenant in the tenant tree structure; each tenant in the tenant tree structure includes at least one project. The processing module 72 also determines the tenant to which each user belongs based on their project information and binds the user to their respective tenant, enabling the user to obtain the resource permissions of their tenant.

[0092] The multi-tenant management platform provided in this application embodiment can execute the technical solutions shown in the above method embodiments. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0093] In one possible implementation, the processing module 72 is specifically used to determine, for each project, whether the resource permissions of the project are the same as those of other projects; if the resource permissions of the project are different from those of other projects, then the project is treated as a tenant; if the resource permissions of the project are the same as those of at least one other project, then the projects with the same resource permissions are merged to form a tenant; for each tenant, the tenant level is set according to the tenant's resource permissions to construct a tenant tree structure; wherein, the resource permissions of each level of the tenant in the tenant tree structure are greater than the resource permissions of the next level of tenant.

[0094] In one possible implementation, the processing module 72 is specifically used to obtain, for each tenant, the cloud account associated with the resource permissions of that tenant; and bind the tenant to the cloud account so that the tenant can obtain the corresponding resource permissions.

[0095] The multi-tenant management platform provided in this application embodiment can execute the technical solutions shown in the above method embodiments. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0096] In one possible implementation, the processing module 72 is specifically used to determine, for each user, the project to which the user belongs based on the user's project information; and to determine the tenant to which the project belongs, so as to determine the tenant to which the user belongs.

[0097] In one possible implementation, the processing module 72 is further configured to obtain a tenant binding request sent by the user, the tenant binding request including a tenant identifier to be bound; send a binding confirmation request to the tenant corresponding to the tenant identifier to be bound; and bind the user to the tenant corresponding to the tenant identifier to be bound when the confirmation information is received from the tenant, so that the user can obtain the resource permissions of the tenant.

[0098] The multi-tenant management platform provided in this application embodiment can execute the technical solutions shown in the above method embodiments. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0099] In one possible implementation, the processing module 72 is further configured to obtain the operation permission information of each user, query the role corresponding to the operation permission information, and bind the user to the role so that the user can obtain the operation permissions corresponding to the operation permission information.

[0100] In one possible implementation, the processing module 72 is further configured to obtain a role binding request sent by the user, the role binding request including a role identifier to be bound; unbind the user from its currently bound role, and bind the user to the role corresponding to the role identifier to be bound, so that the user can obtain the operation permissions of the role corresponding to the role identifier to be bound.

[0101] The multi-tenant management platform provided in this application embodiment can execute the technical solutions shown in the above method embodiments. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0102] Figure 8 This is a schematic diagram of another embodiment of a multi-tenant management platform provided in this application. (See attached diagram.) Figure 8As shown, the multi-tenant management platform 80 includes: a processor 81, a memory 82 communicatively connected to the processor 81, and a communication interface 83; wherein, the memory 82 stores computer execution instructions; the processor 81 executes the computer execution instructions stored in the memory 82 to implement the technical solutions in any of the aforementioned method embodiments.

[0103] Optionally, the memory 82 can be either standalone or integrated with the processor 81.

[0104] Optionally, when the memory 82 is a device independent of the processor 81, the multi-tenant management platform 80 may further include a bus 84 for connecting the aforementioned devices.

[0105] This multi-tenant management platform is used to execute the technical solutions in any of the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be repeated here.

[0106] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the aforementioned. Figures 2 to 6 The technical solution in any of the method embodiments.

[0107] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0108] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0109] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0110] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0111] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0112] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0113] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as these combinations of technical features do not contradict each other, they should be considered within the scope of this specification.

[0114] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0115] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A multi-tenant management method, characterized in that, include: Obtain a multi-tenant management request, which includes resource permission information for multiple projects and project information for multiple users; Based on the resource permission information of the multiple projects, a tenant tree structure is constructed, and corresponding resource permissions are configured for each tenant in the tenant tree structure; wherein, each tenant in the tenant tree structure includes at least one of the projects; Based on each user's project information, determine the tenant to which the user belongs, and bind the user to the tenant to enable the user to obtain the resource permissions of the tenant to which the user belongs; The step of constructing a tenant tree structure based on the resource permission information of the multiple projects includes: For each project, determine whether the resource permissions of that project are the same as the resource permissions of other projects; If the resource permissions of the project are different from those of other projects, then the project will be treated as a tenant. If the resource permissions of the project are the same as those of at least one other project, then the projects with the same resource permissions will be merged to form a single tenant. For each tenant, a tenant level is set according to the tenant's resource permissions to construct a tenant tree structure; the resource permissions of each level of the tenant in the tenant tree structure are greater than the resource permissions of the next level of tenant.

2. The multi-tenant management method according to claim 1, characterized in that, The step of configuring corresponding resource permissions for each tenant in the tenant tree structure includes: For each tenant, obtain the cloud account associated with the tenant's resource permissions; Bind the tenant to the cloud account to enable the tenant to obtain the corresponding resource permissions.

3. The multi-tenant management method according to claim 1, characterized in that, The step of determining the tenant to which a user belongs based on each user's project information includes: For each user, the project to which the user belongs is determined based on the user's project information; Determine the tenant to which the project belongs, in order to determine the tenant to which the user belongs.

4. The multi-tenant management method according to claim 1, characterized in that, The method further includes: Obtain the tenant binding request sent by the user, wherein the tenant binding request includes the identifier of the tenant to be bound; A binding confirmation request is sent to the tenant corresponding to the tenant identifier to be bound, and upon receiving confirmation information from the tenant, the user is bound to the tenant corresponding to the tenant identifier to enable the user to obtain the resource permissions of the tenant.

5. The multi-tenant management method according to claim 1, characterized in that, The method further includes: For each user, obtain the user's operation permission information and query the role corresponding to the operation permission information; The user is bound to the role so that the user can obtain the operation permissions corresponding to the operation permission information.

6. The multi-tenant management method according to claim 5, characterized in that, The method further includes: Obtain a role binding request sent by the user, wherein the role binding request includes the identifier of the role to be bound; Unbind the user from its currently bound role, and bind the user to the role corresponding to the role to be bound, so that the user can obtain the operation permissions of the role corresponding to the role to be bound.

7. A multi-tenant management platform, characterized in that, include: The acquisition module is used to acquire multi-tenant management requests, which include resource permission information of multiple projects and project information of multiple users; The processing module is used to construct a tenant tree structure based on the resource permission information of the multiple projects, and configure corresponding resource permissions for each tenant in the tenant tree structure; wherein each tenant in the tenant tree structure includes at least one of the projects; The processing module is also used to determine the tenant to which the user belongs based on the project information of each user, and bind the user to the tenant to which the user belongs, so that the user can obtain the resource permissions of the tenant to which the user belongs; Specifically, the processing module is used to determine, for each project, whether the resource permissions of the project are the same as those of other projects; if the resource permissions of the project are different from those of other projects, then the project is treated as a tenant; if the resource permissions of the project are the same as those of at least one other project, then the projects with the same resource permissions are merged to form a tenant; for each tenant, the tenant level is set according to the tenant's resource permissions to construct a tenant tree structure; the resource permissions of each level of the tenant in the tenant tree structure are greater than the resource permissions of the next level of tenant.

8. A multi-tenant management platform, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the multi-tenant management method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the multi-tenant management method as described in any one of claims 1 to 6.

Images