Multi-tenant platform architecture method and system, storage medium and electronic equipment
By realizing data isolation and sharing in the multi-tenant platform architecture, the problems of data silos and insufficient management in traditional multi-tenant systems are solved, the information management and decision-making efficiency of enterprise groups is improved, and the digital transformation of enterprise groups is supported.
Patent Information
- Application Number
- CN202411107954.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-13
- Publication Date
- 2024-12-06
AI Technical Summary
Traditional multi-tenant systems are difficult to achieve data sharing and integration within enterprise groups, resulting in data silos and lack of centralized management and monitoring functions, affecting decision-making efficiency.
Design a multi-tenant platform architecture, by obtaining user data and syncing it to the user pool, setting different tenant types (platform tenants, application tenants, enterprise tenants), configuring functions and services, realizing data isolation and sharing, adopting tile form and The structure setting of the tenant tree form, dynamic permission management and data synchronization mechanism ensures the secure sharing of data between different tenants.
It realizes the effective sharing and utilization of data within the enterprise group, improves the level of information management and decision-making efficiency, ensures data isolation and security, and supports the digital transformation of the enterprise group.
Smart Images

Figure CN119094536A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of data processing, and in particular, relates to a multi-tenant platform architecture method, system, storage medium and electronic device. Background Art
[0002] With the acceleration of digital transformation, enterprise groups are facing more complex and diverse information technology needs. In this context, traditional multi-tenant technology has become one of the mainstream solutions to support internal enterprise information systems. However, with the high complexity of enterprise group organizations, traditional multi-tenant technology has been unable to meet group-level needs. Traditional multi-tenant systems work well within a single organization or business entity, but there are some new challenges within enterprise groups. Among them, one of the most significant problems is the formation of data silos. In traditional multi-tenant systems, data between different tenants is often stored in isolation, making it difficult to share and integrate data. In this case, the data of various subsidiaries or departments within the enterprise group often cannot be fully shared and utilized, affecting the level of information management and decision-making efficiency.
[0003] In addition, traditional multi-tenant systems often lack centralized management and monitoring functions, making it impossible for senior management to fully query and monitor the data assets of the entire enterprise group. In this case, it is difficult for the management of the enterprise group to make accurate strategic decisions, which affects the development direction and competitiveness of the enterprise.
[0004] Therefore, how to provide a platform architecture method to solve the above-mentioned problems has become a technical problem that technical personnel in this field need to solve urgently. Summary of the invention
[0005] In view of the shortcomings of the prior art mentioned above, the purpose of the present invention is to provide a multi-tenant platform architecture, aiming to solve the problems faced by traditional multi-tenant systems when supporting large enterprise groups, such as data silos and insufficient management and monitoring, so that data can be effectively isolated between tenants and can be securely shared and collaborated.
[0006] In a first aspect, the present invention provides a multi-tenant platform architecture method, the method comprising the following steps:
[0007] Acquire user data and synchronize the acquired user data to a user pool, wherein the user data includes user unique identification information;
[0008] Setting a preset number of tenant types and configuring specific functions and services for each tenant type; wherein the tenant types include platform tenants, application tenants, and enterprise tenants;
[0009] The user service requirements are obtained, and based on the user unique identification information, the user data is synchronized to the corresponding tenant type.
[0010] In an implementation of the first aspect, setting a preset number of tenant types and configuring specific functions and services for each tenant type includes:
[0011] Providing tenant registration, tenant authentication and tenant authorization functions based on the platform tenants;
[0012] Providing specific business system functions based on the application tenant;
[0013] A business process is executed based on a specific business provided by the application tenant for the enterprise tenant to use.
[0014] In an implementation of the first aspect, the method further includes structuring the enterprise tenants in a flat format and a tenant tree format;
[0015] When the target tenant needs to share data with users outside the user pool, the tiled form is set by adding new user data;
[0016] When the target tenant needs to achieve unified business management, a tenant tree is established through sub-node settings.
[0017] In an implementation of the first aspect, the method further includes configuring independent data access rights for each tenant type and tenant form, wherein the data access rights configuration includes the following steps:
[0018] Pre-set user roles and configure corresponding attribute control rules based on the user roles;
[0019] Obtain user service requirements and perform condition matching based on the attribute control rules to implement data permission access control.
[0020] In an implementation manner of the first aspect, the method further includes setting a dynamic rights management mechanism, based on which the tenant type and the corresponding service are allowed to be dynamically adjusted according to the update of user data.
[0021] In an implementation manner of the first aspect, the method further includes setting a data isolation mechanism, and based on the data isolation mechanism, the user data is physically or logically divided into tables according to the user unique identifier.
[0022] In an implementation manner of the first aspect, the method further includes setting a data synchronization mechanism, and based on the data synchronization mechanism, the tenants realize cross-tenant data sharing through their respective permissions.
[0023] In a second aspect, the present invention provides a multi-tenant platform architecture system, the system comprising a user module, a configuration module and a business module;
[0024] The user module is used to obtain user data and synchronize the obtained user data to the user pool, wherein the user data includes user unique identification information;
[0025] The configuration module is used to set a preset number of tenant types and configure specific functions and services for each tenant type; wherein the tenant types include platform tenants, application tenants and enterprise tenants;
[0026] The business module is used to obtain user service requirements and synchronize the user data to the corresponding tenant type based on the user unique identification information.
[0027] In a third aspect, the present invention provides an electronic device, the electronic device comprising: a processor and a memory;
[0028] The memory is used to store computer programs;
[0029] The processor is used to execute the computer program stored in the memory so that the electronic device executes the above-mentioned multi-tenant platform architecture method.
[0030] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, which implements the above-mentioned multi-tenant platform architecture method when executed by an electronic device.
[0031] As described above, the multi-tenant platform architecture method, system, storage medium and electronic device of the present invention have the following features:
[0032] Beneficial effects:
[0033] The core goal of the multi-tenant platform architecture method, system, storage medium and electronic device described in the present invention is to establish a unified multi-tenant system within the enterprise group to support data sharing and resource utilization between different subsidiaries or departments, while ensuring data isolation and security between tenants. Therefore, the present invention can not only improve the level of information management within the enterprise group, promote cross-departmental collaboration and business process optimization, but also provide strong support for the digital transformation of the enterprise group. Against the backdrop of digital transformation, the emergence of group-based multi-tenant technology will lay a solid foundation for enterprise groups to maximize the utilization of information resources and create value. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] Figure 1 Shown is a flow chart of a multi-tenant platform architecture method in one embodiment of the present invention;
[0035] Figure 2 Shown is a schematic diagram of the multi-tenant platform architecture of the present invention;
[0036] Figure 3Shown is a schematic diagram of the enterprise tenant structure in the multi-tenant platform architecture of the present invention;
[0037] Figure 4 Shown is a schematic diagram of the structure of a multi-tenant platform architecture system in one embodiment of the present invention;
[0038] Figure 5 It is a schematic structural diagram of an electronic device of the present invention in one embodiment. DETAILED DESCRIPTION
[0039] The following describes the embodiments of the present invention by specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.
[0040] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.
[0041] The technical solutions in the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings in the embodiments of the present invention.
[0042] like Figure 1 As shown, in one embodiment, the multi-tenant platform architecture method of the present invention includes steps S11 to S13.
[0043] Step S11: Acquire user data, and synchronize the acquired user data to a user pool, wherein the user data includes user unique identification information.
[0044] Specifically, to obtain user data, the system collects user information through user registration, login or other interactive processes. This information can be the user's unique identifier (such as user ID, email address, mobile phone number, etc.), as well as other information related to the user's identity (such as name, contact information, role, etc.). The system sends the collected user data to the user pool. The user pool is a data storage facility used to store and manage the identity information of all users.
[0045] The synchronization process ensures the consistency and accuracy of user data, allowing the platform to effectively manage and authenticate users. The system plays the role of a passive receiver in this process. It receives and processes data from users, but does not actively collect or modify user data. This means that the system does not actively initiate data interaction with users, but responds to user behavior and requests. At the same time, users need to carefully enter their business information to ensure that the platform has a comprehensive and clear understanding of their identity and qualifications. It is worth noting that administrative organization data is special and users are not allowed to modify it by themselves. It can only be synchronized after the group's human resources data changes to ensure the accuracy and authority of the data.
[0046] Through this process, the system can effectively manage user data and provide reliable user authentication and authorization services, thereby supporting the security and availability of the platform. At the same time, the design of the user pool and the synchronization mechanism help prevent the formation of data silos and ensure data sharing and integration between different tenants.
[0047] Step S12: Set a preset number of tenant types and configure specific functions and services for each tenant type; wherein the tenant types include platform tenants, application tenants, and enterprise tenants. Figure 2 As shown, Figure 2 Shown is a schematic diagram of the multi-tenant platform architecture described in the present invention.
[0048] Specifically, setting a preset number of tenant types and configuring specific functions and services for each tenant type includes:
[0049] Providing tenant registration, tenant authentication and tenant authorization functions based on the platform tenants;
[0050] Providing specific business system functions based on the application tenant;
[0051] A business process is executed based on a specific business provided by the application tenant for the enterprise tenant to use.
[0052] In a multi-tenant system, the relationship between the platform and tenants is a relationship between a service provider and a user. The platform is a software infrastructure that provides a variety of services, tools, and resources to support the business needs of tenants.
[0053] A platform can be a cloud service platform, an application development platform, a business process management platform, etc. It provides a running environment for tenants to develop, deploy, and manage applications. A platform is usually shared by multiple tenants, but the resources of each tenant (such as computing, storage, and network resources) are isolated to ensure data security and privacy. A platform is an overall infrastructure, and tenants are entities that use the infrastructure. The platform provides services, and tenants use these services. The platform provides the services and resources required by tenants, and tenants use these services by paying fees or subscribing to services. The platform needs to ensure that the needs of tenants are met, and tenants need to abide by the rules and agreements of the platform. In a multi-tenant environment, the relationship between the platform and tenants is interdependent. The success of the platform depends on the success of tenants, and the success of tenants depends on the services and resources provided by the platform. Therefore, collaboration and communication between the platform and tenants are crucial to ensure the stable operation of the platform and the satisfaction of tenants' business needs.
[0054] Platform tenants play a key role as the functional service provider of the tenant center platform. Their responsibilities are wide-ranging and vital, covering a series of related functions on the tenant operation side. Among them, the tenant registration function provides an entry point for new tenants to join the platform, ensuring the accurate collection and entry of tenant information; the authentication function strictly verifies the identity and qualifications of tenants, laying the foundation for the security and reliability of the platform; the authorization function gives tenants specific operating permissions on the platform, allowing tenants to carry out business activities within a reasonable range. Among them, there can be multiple platform tenants.
[0055] Application tenants refer to organizations or individuals that provide application services on the platform. As important providers of business system functions, application tenants enter the platform in a unique way. They register their carefully crafted application services on the platform and provide these application services to corporate tenants and other application tenants through a rigorous authorization mechanism. This process not only enriches the service content of the platform, but also creates conditions for cooperation and communication between different types of tenants. For example, an application tenant that specializes in providing financial software services, through registration and authorization on the platform, enables many corporate tenants to conveniently use its financial processing functions and improve financial management efficiency. These applications may include various functions, such as financial management, supply chain management, customer relationship management, etc. Application tenants register their own applications on the platform through the services provided by the platform, and allow other tenants (such as corporate tenants) to use these applications through the authorization mechanism.
[0056] Enterprise tenants refer to organizations or individuals who use application services on the platform. Enterprise tenants are the main end-users of the platform. They rely on the application functions authorized by application tenants to successfully complete various related business processes. These business processes may cover multiple fields such as production management, sales operations, and human resources. For example, a manufacturing company as an enterprise tenant can optimize its raw material procurement and product distribution links by obtaining authorization for supply chain management applications, thereby improving overall operational efficiency.
[0057] In one embodiment, if Figure 3 As shown, Figure 3 Shown is a schematic diagram of the enterprise tenant structure in the multi-tenant platform architecture of the present invention. In terms of data synchronization, the group's human resources data plays an important role through efficient synchronization. On the one hand, the user data is synchronized to the platform user pool, providing accurate and timely information support for the platform's user management; on the other hand, the administrative organization data is synchronized to the enterprise tenant, helping the enterprise tenant to better understand and adapt to changes in the organizational structure. Among them, in the multi-tenant system, the administrative organization concept of the enterprise tenant refers to the organizational structure within the enterprise, including various departments, teams, positions, etc. This organizational structure is used to manage and coordinate employees' job responsibilities, reporting relationships and decision-making processes within the enterprise. In a multi-tenant system, the administrative organization data of the enterprise tenant is synchronized to the enterprise tenant, which can help the enterprise tenant better understand and adapt to changes in the organizational structure, so as to facilitate internal management and coordination of the enterprise. Specifically, the administrative organization data of the enterprise tenant is synchronized to the enterprise tenant, which can realize organizational structure management: the enterprise tenant can manage the internal organizational structure through the synchronized administrative organization data, including creating, modifying and deleting departments, teams, positions, etc. Enterprise tenants can manage employees based on synchronized administrative organization data, including creating, modifying and deleting employee accounts, and setting employee departments, teams and positions. Enterprise tenants can manage employee permissions based on synchronized administrative organization data, including setting employee access rights, roles and responsibilities. Enterprise tenants can obtain the internal organizational structure and employee information of the enterprise through synchronized administrative organization data to facilitate decision support and business analysis. Enterprise tenants can achieve collaborative work among employees through synchronized administrative organization data, including sharing work content, task allocation and progress tracking.
[0058] Through synchronized administrative organization data, enterprise tenants can better manage and coordinate internal organizational structure and employee information in a multi-tenant system to improve the operational efficiency and decision-making quality of the enterprise. At the same time, this synchronization mechanism also helps prevent the formation of data silos and ensures data sharing and integration between different tenants.
[0059] Furthermore, the method further includes structuring the enterprise tenants in a flat format and a tenant tree format;
[0060] When the target tenant needs to share data with users outside the user pool, the tiled form is set by adding new user data;
[0061] When the target tenant needs to achieve unified business management, a tenant tree is established through sub-node settings.
[0062] In a multi-tenant system, the tenant form is defined based on the tenant's organizational structure to support different types of tenant needs. In the enterprise group scenario, the tenant form can be divided into a flat form and a tenant tree form, each of which has its applicable scenarios and advantages.
[0063] First, flat tenants are relatively independent tenants in terms of organizational structure, and there is no hierarchical relationship between them. This form is suitable for partners and third-party organizations, which may not need to conduct close business collaboration with other tenants within the group. Flat tenants can optimize business processes through data sharing and business collaboration, but their data and business logic are relatively independent.
[0064] Secondly, the tenant tree form is a multi-tenant system architecture that allows the relationship between tenants to be organized in a tree structure, similar to the organizational structure of an enterprise. In the tenant tree form, the relationship between tenants is hierarchical, and each tenant can have sub-tenants, forming a tree-like hierarchical structure. This architecture helps the internal organization and management of the enterprise group and supports complex business processes and data sharing requirements. In the tenant tree form, there are usually the following key features: The root node tenant is usually the top management or headquarters of the enterprise group, responsible for the business management, decision-making and resource allocation of the entire group. The root node tenant has the highest authority and access control in the system and can access and manage the data of all sub-tenants. Sub-node tenants are usually subsidiaries or branches under the group, which have their own data storage and business logic in the system. Sub-node tenants can access and manage their own data, and can also access and manage the data of their sub-tenants. Tree node tenants are lower-level tenants under sub-node tenants, and they have their own data storage and business logic in the system. Tree node tenants can access and manage their own data, and can also access and manage the data of their sub-tenants.
[0065] The tenant tree of the present invention is designed according to the organizational hierarchy of the enterprise group, and the relationship between tenants is in a tree structure. In a group-type multi-tenant system, the tenant tree usually takes the group headquarters as the root node, the provincial company as the child node tenant, and the third-level company as the third-level tree node tenant. This form helps to achieve unified management and monitoring of the internal business of the group, and can also meet the personalized needs of companies at all levels. Through the form of the tenant tree, the group can achieve refined management of tenants at all levels while maintaining data consistency and security. Data sharing and resource utilization between various levels can be carried out under the premise of ensuring security, thereby improving the information management level and decision-making efficiency of the entire group. When designing the form of the tenant tree, the nodes are strictly limited to a maximum of three levels in order to balance the unity and personalized demands of the business. Such a design can not only ensure the overall management of the group's overall business, but also fully meet the personalized needs of companies at all levels, and realize an efficient and orderly operation mode. In the tenant tree form, data sharing and access control can be defined based on the relationship between tenants. The upper-level tenant can access and manage the data of the lower-level tenant, but the consent and authorization of the lower-level tenant is required. The tenant tree format supports complex business collaboration and processes. For example, the group headquarters can monitor and manage the business processes of its subsidiaries. Data sharing and process collaboration between tenants help improve the operational efficiency and decision-making quality of the entire group.
[0066] In one embodiment, a software development company that cooperates with a group does not need to conduct close business collaboration with other tenants within the group. As a tiled tenant, this company has independent data storage and business logic in the system. It can join the system by adding new accounts. Tile tenants can set strict permission control to limit other tenants' access to data and operation permissions. Permission control can be achieved through role definition, access tokens and authentication mechanisms.
[0067] In one embodiment, the group headquarters is the root node of the tenant tree and is responsible for the business management, decision-making and resource allocation of the entire group. Provincial companies are sub-node tenants and are responsible for the business operations and resource management of the province. They have their own data storage and business logic in the system and need to follow the unified policies and guidance of the group headquarters. Level 3 companies are third-level tree node tenants and are responsible for specific business execution and operations. They have their own data storage and business logic in the system and need to follow the policies and guidance of the group headquarters and provincial companies.
[0068] Furthermore, the method further includes configuring independent data access rights for each tenant type and tenant form, wherein the data access rights include the following steps:
[0069] Pre-set user roles and configure corresponding attribute control rules based on the user roles;
[0070] Obtain user service requirements and perform condition matching based on the attribute control rules to implement data permission access control.
[0071] Furthermore, the method also includes setting a dynamic rights management mechanism, based on which the tenant type and corresponding services are allowed to be dynamically adjusted according to the update of user data. In a multi-tenant system, the dynamic rights management mechanism is a key component, which allows the system to automatically adjust the tenant type and corresponding services according to the update of user data. This mechanism can adapt to the dynamic changes in tenant business needs and improve the flexibility and scalability of the system.
[0072] Furthermore, setting a preset number of tenant types and configuring specific functions and services for each tenant type includes configuring independent operation permissions, data access permissions and function usage rights for each tenant type and tenant form.
[0073] In modern enterprises, data security and compliance are crucial. With the popularity of multi-tenant applications, how to achieve cross-tenant data sharing and authorized access while ensuring the isolation of each tenant's data has become a challenge. The present invention adopts the attribute-based access control (ABAC) model to solve this problem, providing a flexible and fine-grained data access control mechanism.
[0074] Regarding attribute access control, for attribute control rule configuration: first define which attributes will be used for access control, such as user role, department, position, etc. Configure these rules on a centralized platform and ensure that these rules are synchronized to the Redis database of each business project for quick access and use.
[0075] Regarding query interception and rule application, when querying data, the system intercepts SQL requests and dynamically modifies SQL statements based on user attributes and preset rules to implement access control for specific rows or columns of data. Based on the user's attribute information, the system automatically adds the corresponding WHERE clause or other restriction conditions to the SQL statement to limit the scope of data access. WHERE is an SQL keyword used to specify query conditions and filter results. For example, in an SQL query, WHERE can be used to filter out records that meet specific conditions.
[0076] Regarding the granularity of permission control, row-level control can restrict users to access only specific data rows, for example, employees in a certain department can only see the data of their own department. Column-level control can restrict users from accessing certain sensitive columns, such as hiding columns containing personal privacy information.
[0077] Regarding the authorization scenario of upper and lower tenants, the authorization mode is required: the upper tenant must obtain explicit authorization consent before viewing the data of the lower tenant. The default authorization mode is that the upper tenant can view the data of the lower tenant without additional authorization. Authorization process: After authorization consent, when the upper tenant opens the business page, the query condition adds the authorized tenant information through the tenant attributes. Business data returns the business data of the required tenant and is used for display.
[0078] Regarding interface calls, when an interface containing the business data is called, the information of the authorized tenant is automatically returned. In other words, permission control is taken into consideration when designing the API to ensure that the authorization relationship between tenants can be automatically identified and processed when the interface is called.
[0079] In different tenant authorization scenarios, authorization is required by default: Under different tenant structures, one party cannot view the data of the other party by default, and an authorization process is required. Authorization process: After authorization is agreed, the data permission control mode is used to complete the data authorization review.
[0080] In terms of security control and auditing, each authorization activity is recorded based on the audit log, including who authorized, when authorized, what data was authorized to access, etc. Operation tracking is also implemented, that is, all cross-tenant data query operations are logged to ensure transparency and traceability of operations.
[0081] In terms of dynamic permission management, it allows the allocation and adjustment of permissions to be automatically performed based on real-time conditions or context. This is in contrast to static permissions, which are pre-defined and usually do not change based on runtime conditions. The allocation and revocation of dynamic permissions can change in real time based on multiple factors such as the current user status, operation context, time, location, etc. Permissions can be quickly adjusted based on organizational needs or policy changes without manually updating permission settings. User access to resources can be controlled very finely, for example, access to specific data is allowed at specific times and under specific conditions. Through attribute-based access control-ABAC is an access control strategy that uses attributes (such as user role, department, time, location, etc.) to determine access rights. The system evaluates policy rules between the attributes of the access requester and the attributes of the resource or operation to determine whether access is authorized. In addition, it can also be extended through dynamic role assignment so that roles can change based on user behavior or environmental changes. At the same time, a policy engine is used to execute complex permission logic that can be dynamically adjusted based on preset conditions or real-time data.
[0082] Through this series of measures, the present invention achieves highly secure and flexible data access control. The ABAC model not only makes data permission management efficient and accurate, but also adapts to complex multi-tenant business needs. At the same time, strict auditing and logging mechanisms ensure the security, compliance and transparency of the entire data access process.
[0083] In one embodiment, a user can become an employee of a tenant only after being invited or added by the tenant administrator. In the non-employee state, the user cannot access any functions and data under the tenant. If a user has not been formally invited or added, even if he tries to log in, the system will prevent him from entering and prompt that he does not have access rights. The operations of employees in the tenant are subject to strict permission control, and each of their access and operations will be recorded in a timely and accurate manner. For example, employee A can only operate a specific module within the scope of his granted permissions, and each of his logins, data viewing and modification will be recorded in detail in the system log.
[0084] Furthermore, the method also includes setting a data isolation mechanism, and based on the data isolation mechanism, the user data is physically or logically divided into tables according to the user unique identifier.
[0085] In one embodiment, all business data are accompanied by a tenant identification field. Based on this, all business data will be physically or logically sub-tabled according to the tenant identification, and the access to the data will be accompanied by the tenant identification by default, thereby achieving effective isolation of the data. For example, the data of tenant A and tenant B will be clearly divided and stored. When accessing the data, the system will accurately obtain the corresponding data based on the tenant identification. If a user becomes an employee under different tenants, the business data will carry detailed information related to the employee. In addition, the business data that users can see under different tenants is also isolated by employee identification by default. Assuming that a user holds positions in tenant A and tenant B respectively, he can only see the business data related to himself under the tenant in tenant A, and cannot see specific data in tenant B.
[0086] Furthermore, the method further includes setting a data synchronization mechanism, based on which the tenants can realize cross-tenant data sharing and authorized access through their respective permissions. Specifically, the method includes the following steps:
[0087] Set data sharing policies to define the scope and conditions of data that can be shared between tenants;
[0088] Provides a data sharing interface to allow tenants to exchange data according to policies;
[0089] Record data sharing logs to ensure the traceability and security of data sharing.
[0090] In one embodiment, non-tenant employees are strictly prohibited from operating the tenant's data, and any data change permissions are limited to the tenant, effectively ensuring that the data ownership belongs to the tenant. For example, unauthorized outsiders cannot modify or delete the tenant's core data.
[0091] In one embodiment, for group tenant scenarios, the upper-level tenant can access the business data of the lower-level tenant through data authorization, but this process must be initiated by the upper-level tenant and can only be accessed after obtaining the authorization and consent of the lower-level tenant. For example, if the group headquarters tenant wants to view the data of a provincial tenant, it must first initiate an application and obtain the corresponding authority after the provincial tenant agrees.
[0092] In one embodiment, in a group tenant scenario, if an employee of a higher-level tenant needs to operate the business data of a lower-level tenant, the lower-level tenant's administrator must add the employee of the higher-level tenant to the tenant before the operation is allowed. For example, the administrator of a provincial company tenant has the right to decide whether to include the employees of the group headquarters in its tenant to grant them the authority to operate business data.
[0093] Furthermore, the provision of customized services at the tenant level may include the following steps:
[0094] Allow tenants to customize interface themes, layouts, and functional modules;
[0095] Provide tenant-specific configuration parameters so that tenants can adjust system behavior according to their needs;
[0096] Supports tenant-level plug-ins and extensions to enhance tenants' business processing capabilities.
[0097] Furthermore, the method also includes setting up a notification and communication mechanism, based on which the tenants and employees within the tenants can perform targeted notification and communication based on specific circumstances.
[0098] In a multi-tenant system, since tenants and employees in different tenants are different, the system needs to be flexible and accurate in notification scenarios, and be able to select different employees for notification and communication based on the specific circumstances of the tenants. Tenant and user information: The system stores detailed information about each tenant and user, including roles, responsibilities, work areas, etc. This information can help the system determine which employees need to receive specific types of notifications. The system formulates different notification policies based on the nature and purpose of the notification. For example, for emergency notifications, it may need to be sent to all relevant employees immediately; while for general notifications, specific recipients can be set. The system provides filtering conditions, allowing administrators or users to select employees to receive notifications based on specific conditions. Conditions may include tenant type, employee role, geographic location, business department, etc. Through these implementation points, the multi-tenant system can implement a flexible notification and communication mechanism to ensure that important information can be conveyed to relevant employees in a timely and accurate manner, thereby improving the operational efficiency and responsiveness of the enterprise.
[0099] Step S13: Obtain user service requirements, and synchronize the user data to the corresponding tenant type based on the user unique identification information.
[0100] Specifically, the system collects the user's service needs through the user interface or application. Based on the user's service needs and business relationship, the tenant type to which the user belongs is determined. Tenant types may include group headquarters, subsidiaries, partners, third-party suppliers, etc. The system uses the user's unique identification information, such as user ID, email address, mobile phone number, etc., to identify the user. This unique identification information is the basis for synchronizing user data to ensure that the data is accurately associated with the correct tenant. The system associates the collected user data with the user's unique identification information and synchronizes it to the corresponding tenant type. The synchronized data may include the user's basic information, role, permissions, service preferences, etc. The system synchronizes user data regularly to reflect any changes in the user's service needs. The system also provides a mechanism to allow users or administrators to manually trigger data synchronization to update the data.
[0101] Through this process, the multi-tenant system can ensure that the user's service needs are correctly matched with the tenant type, and synchronize user data to support the corresponding services. This process helps to improve the user experience and business efficiency of the system.
[0102] Traditional multi-tenant systems are often designed for a single organization, while the present invention proposes a multi-tenant architecture for enterprise groups. By setting three types of roles, namely platform tenants, application tenants and enterprise tenants, a more complex and flexible multi-level tenant system is formed, which better meets the organizational structure and management needs of enterprise groups. The present invention can achieve a balance between data sharing and isolation: in traditional multi-tenant systems, data sharing and isolation are often difficult to balance. However, this technology not only realizes data sharing within the group, but also ensures the security of each tenant's data through an efficient data synchronization mechanism and a data isolation strategy based on tenant identification. The present invention has effective access control and authority management: the technology has carefully designed the user's access control and authority management, ensuring that the operating permissions of users with different roles and identities in the system are effectively managed, and improving the security and reliability of the system. In the group tenant scenario, the present invention implements an authorization mechanism for cross-tenant data access, allowing upper-level tenants to access their business data after obtaining authorization from lower-level tenants, while ensuring the ownership and security of the data. The present invention designs two tenant forms, namely, a flat form and a tenant tree form, for different business scenarios, which can flexibly meet the management needs of different business units and organizational levels within the group. The multi-tenant platform architecture method described in the present invention focuses on the tenant scenarios in the complex digital transformation of the group, and innovatively adopts a new tenant setting method, which can reasonably and effectively plan the construction of the system and the use of system functions by enterprise employees during the digital transformation process. Under this system, the business system connected to the platform not only has a SaaS multi-tenant system by default, but also has the ability to view sub-tenant business data in the group scenario. This innovative measure successfully resolved the data island problem caused by the traditional multi-tenant model and the long-standing problem of unclear tenant definition.
[0103] The protection scope of the multi-tenant platform architecture method described in the embodiment of the present invention is not limited to the execution order of the steps listed in this embodiment. All solutions implemented by adding, reducing or replacing steps in the prior art based on the principles of the present invention are included in the protection scope of the present invention.
[0104] An embodiment of the present invention also provides a multi-tenant platform architecture system, which can implement the multi-tenant platform architecture method described in the present invention. However, the implementation device of the multi-tenant platform architecture system described in the present invention includes but is not limited to the structure of the multi-tenant platform architecture system listed in this embodiment. All structural deformations and replacements of the prior art made according to the principles of the present invention are included in the protection scope of the present invention.
[0105] like Figure 4 As shown, in one embodiment, the multi-tenant platform architecture system of the present invention includes a user module 41, a configuration module 42, and a business module 43.
[0106] The user module 41 is used to obtain user data and synchronize the obtained user data to a user pool, wherein the user data includes user unique identification information.
[0107] The configuration module 42 is connected to the user module 41 and is used to set a preset number of tenant types and configure specific functions and services for each tenant type; wherein the tenant types include platform tenants, application tenants and enterprise tenants.
[0108] The business module 43 is connected to the configuration module 41 and is used to obtain user service requirements and synchronize the user data to the corresponding tenant type based on the user unique identification information.
[0109] In the several embodiments provided by the present invention, it should be understood that the disclosed system, device or method can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules / units is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules or units can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules or units, which can be electrical, mechanical or other forms.
[0110] The modules / units described as separate components may or may not be physically separated, and the components displayed as modules / units may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules / units may be selected according to actual needs to achieve the purpose of the embodiments of the present invention. For example, the functional modules / units in the various embodiments of the present invention may be integrated into one processing module, or each module / unit may exist physically separately, or two or more modules / units may be integrated into one module / unit.
[0111] Those of ordinary skill in the art should further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.
[0112] The embodiment of the present invention also provides a computer-readable storage medium. A person of ordinary skill in the art can understand that all or part of the steps in the method for implementing the above embodiment can be completed by instructing the processor through a program, and the program can be stored in a computer-readable storage medium, and the storage medium is a non-transitory medium, such as a random access memory, a read-only memory, a flash memory, a hard disk, a solid-state hard disk, a magnetic tape, a floppy disk, an optical disc, and any combination thereof. The above storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid-state disk (SSD)), etc.
[0113] An embodiment of the present invention further provides an electronic device, which includes a processor and a memory.
[0114] The memory is used to store computer programs.
[0115] The memory includes: ROM, RAM, disk, USB flash drive, memory card or CD and other media that can store program codes.
[0116] The processor is connected to the memory and is used to execute the computer program stored in the memory so that the electronic device executes the above-mentioned multi-tenant platform architecture method.
[0117] Preferably, the processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
[0118] like Figure 5As shown, the electronic device of the present invention is in the form of a general computing device. The components of the electronic device may include but are not limited to: one or more processors or processing units 51, a memory 52, and a bus 53 connecting different system components (including the memory 52 and the processing unit 51).
[0119] Bus 53 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.
[0120] Electronic devices typically include a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device, including volatile and non-volatile media, removable and non-removable media.
[0121] The memory 52 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 521 and / or cache memory 522. The electronic device may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 523 may be used to read and write non-removable, non-volatile magnetic media ( Figure 5 not shown, usually called a "hard drive"). Although Figure 5 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 53 via one or more data medium interfaces. The memory 52 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.
[0122] A program / utility 524 having a set (at least one) of program modules 5241 may be stored, for example, in the memory 52, such program modules 5241 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination thereof may include an implementation of a network environment. The program modules 5241 generally perform the functions and / or methods of the embodiments described herein.
[0123] The electronic device may also communicate with one or more external devices (e.g., keyboards, pointing devices, displays, etc.), one or more devices that enable a user to interact with the electronic device, and / or any device that enables the electronic device to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed via input / output (I / O) interface 54. Furthermore, the electronic device may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via network adapter 55. Figure 5 As shown, the network adapter 55 communicates with other modules of the electronic device via the bus 53. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0124] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the art may modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by a person of ordinary skill in the art without departing from the spirit and technical concept disclosed by the present invention shall still be covered by the claims of the present invention.
Claims
1. A multi-tenant platform architecture method, characterized in that: The method comprises the following steps: Acquire user data and synchronize the acquired user data to a user pool, wherein the user data includes user unique identification information; Setting a preset number of tenant types and configuring specific functions and services for each tenant type; wherein the tenant types include platform tenants, application tenants, and enterprise tenants; The user service requirements are obtained, and based on the user unique identification information, the user data is synchronized to the corresponding tenant type.
2. The multi-tenant platform architecture method according to claim 1, characterized in that: Set a preset number of tenant types and configure specific features and services for each tenant type including: Providing tenant registration, tenant authentication and tenant authorization functions based on the platform tenants; Providing specific business system functions based on the application tenant; A business process is executed based on a specific business provided by the application tenant for the enterprise tenant to use.
3. The multi-tenant platform architecture method according to claim 1, characterized in that: The method further includes structuring the enterprise tenants in a flat form and a tenant tree form; When the target tenant needs to share data with users outside the user pool, the tiled form is set by adding new user data; When the target tenant needs to achieve unified business management, a tenant tree is established through sub-node settings.
4. The multi-tenant platform architecture method according to claim 3, characterized in that: The method further includes configuring independent data access rights for each tenant type and tenant form, wherein the data access rights configuration includes the following steps: Pre-set user roles and configure corresponding attribute control rules based on the user roles; Obtain user service requirements and perform condition matching based on the attribute control rules to implement data permission access control.
5. The multi-tenant platform architecture method according to claim 1, characterized in that: The method further comprises setting a dynamic rights management mechanism, based on which the tenant type and the corresponding service are allowed to be dynamically adjusted according to the update of user data.
6. The multi-tenant platform architecture method according to claim 1, characterized in that: The method further includes setting a data isolation mechanism, and based on the data isolation mechanism, the user data is physically or logically divided into tables according to the user unique identifier.
7. The multi-tenant platform architecture method according to claim 1, characterized in that: The method further includes setting a data synchronization mechanism, based on which the tenants realize cross-tenant data sharing through their respective permissions.
8. A multi-tenant platform architecture system, characterized in that: The system includes a user module, a configuration module and a business module; The user module is used to obtain user data and synchronize the obtained user data to the user pool, wherein the user data includes user unique identification information; The configuration module is used to set a preset number of tenant types and configure specific functions and services for each tenant type; The tenant types include platform tenants, application tenants and enterprise tenants; The business module is used to obtain user service requirements and synchronize the user data to the corresponding tenant type based on the user unique identification information.
9. An electronic device, characterized in that: The electronic device comprises: a processor and a memory; The memory is used to store computer programs; The processor is used to execute the computer program stored in the memory so that the electronic device executes the multi-tenant platform architecture method according to any one of claims 1 to 7.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by an electronic device, the multi-tenant platform architecture method described in any one of claims 1 to 7 is implemented.
Citation Information
Patent Citations
Tenant management platform and tenant management method based on multi-layer parent-child structure tenants
CN111988173A
Big data multi-cluster management method and device, electronic equipment and storage medium
CN115412566A
Multi-tenant authority control method and device, computer equipment and storage medium
CN116226808A
Multi-tenant management method and system based on low-code platform
CN118211243A
Multi-industry application SaaS structure management system, method and device and readable storage medium
CN118427855A
