A multi-tenant enterprise management method based on SCRM system

Abstract

The purpose of the present invention is to provide a multi-tenant enterprise management method based on an SCRM system, the method comprising: constructing a basic application relationship model; after receiving a tenant configuration request, generating a tenant application relationship model and a multi-tenant relationship model according to the basic application relationship model; generating a tenant data isolation strategy according to the tenant application relationship model and the multi-tenant relationship model. The present invention can configure the corresponding tenant application relationship model and the multi-tenant relationship model according to the needs of each tenant, and by configuring each tenant relationship attribute and setting the corresponding data isolation strategy, so as to more effectively share and utilize these resources, reduce resource waste, minimize resource contention between different tenants, and reduce the possibility of conflict; at the same time, through reasonable data isolation strategy and resource allocation, it can be guaranteed that tenants get high-quality services when using the SCRM system.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a multi-tenant enterprise management method based on an SCRM system. Background Art

[0002] SCRM system is a social customer relationship management system, which mainly communicates and interacts with customers through social media platforms to manage potential and existing customer relationships. SCRM management system software is a customer relationship management platform that combines social media channels with traditional CRM. It is a supplement to the CRM system that relies on traditional marketing channels. It is also an adaptive optimization and upgrade of the CRM system in the context of the Internet era, when social media applications have a huge user base. SCRM increases the customer acquisition channels of enterprises, provides convenience for enterprises and users to interact and communicate anytime, anywhere, and even at will, and collects more comprehensive and real-time customer data through social media to improve customer participation, customer service and market insights. Enterprises can use the SCRM system to collect user data, track user behavior, interact with users in real time, and classify users according to user preferences, habits, transaction records, user feedback and other characteristics, so as to provide customized services, improve marketing conversion rate and ROI, maintain good customer relationships and ultimately establish user loyalty.

[0003] In the multi-tenant enterprise management method based on the SCRM system, the relationship between tenants may involve the relationship between the main tenant and the sub-tenant, the relationship between the same tenant, or the relationship between independent tenants. The existence of these relationships will bring new challenges to data sharing and security. For the relationship between the main tenant and the sub-tenant, the main tenant (such as the headquarters of a large company) may need to access and process the data of its sub-tenants (such as branches). In this case, data sharing is very important to ensure that the main tenant can obtain sufficient information for decision-making and management. At the same time, security cannot be ignored. It is necessary to ensure that only the legitimate main tenant can access the sub-tenant's data, and that the data will not be leaked to irrelevant tenants when sharing. In the multi-tenant enterprise management method based on the SCRM system, different tenant relationships have put forward new requirements for data sharing and security. While meeting the needs of data sharing to improve business efficiency and coordination, it is also necessary to fully consider data security to ensure that sensitive information will not be leaked due to data sharing. Summary of the invention

[0004] The purpose of the present invention is to provide a multi-tenant enterprise management method based on the SCRM system, which can configure the corresponding tenant application relationship model and the multi-tenant relationship model according to the needs of each tenant, and configure the relationship attributes of each tenant and set the corresponding data isolation strategy so as to more effectively share and utilize these resources, reduce resource waste, minimize resource contention between different tenants, and reduce the possibility of conflict; at the same time, through reasonable data isolation strategy and resource allocation, it can be guaranteed that tenants get high-quality services when using the SCRM system.

[0005] A multi-tenant enterprise management method based on an SCRM system, comprising:

[0006] Build a basic application relationship model;

[0007] After receiving the tenant configuration request, generating a tenant application relationship model and a multi-tenant relationship model according to the basic application relationship model;

[0008] A data isolation policy for a tenant is generated according to the tenant application relationship model and the multi-tenant relationship model.

[0009] Preferably, the basic application relationship model includes:

[0010]

[0011]

[0012]

[0013] in, Represents the basic application relationship model, Represents a basic application set, represents the basic collaborative weight set in the basic application relationship model; in the basic application relationship model, i=1,2,...,n; j=1,2,...,n; n is the number of basic applications in the basic application relationship model, and i and j both represent the numbers of the basic applications; Indicates the basic application numbered i; Represents the basic synergy weight between the basic applications numbered i and j.

[0014] Preferably, the tenant application relationship model includes:

[0015]

[0016]

[0017]

[0018] in, represents the tenant application relationship model of the k-th tenant, represents the customized application set of the kth tenant, represents the customized collaboration weight set of the kth tenant; in the tenant application relationship model, i and j are both integers between [1, m], m≤n; m is the number of customized applications in the tenant application relationship model, and i and j both represent the numbers of customized applications; Indicates the custom application numbered i of the kth tenant; Indicates the customization collaboration weight between the customized applications numbered i and j of the k-th tenant.

[0019] Preferably, generating a multi-tenant relationship model according to the basic application relationship model includes:

[0020] Generate a subordinate tenant relationship according to the basic application relationship model, and the main tenant in the subordinate relationship configures the functional application of the sub-tenant in the subordinate relationship;

[0021] Generate a peer tenant relationship according to the basic application relationship model, where the tenants in the peer relationship adopt a data sharing mechanism;

[0022] Independent tenant relationships are generated based on the basic application relationship model, and the data of each independent tenant is isolated from each other.

[0023] Preferably, generating a tenant's data isolation strategy according to the tenant application relationship model and the multi-tenant relationship model includes:

[0024] Get tenant relationship attributes according to the multi-tenant relationship model;

[0025] If the tenant relationship attribute is an independent tenant relationship, an independent database is allocated to the current tenant;

[0026] If the tenant relationship attribute is a master tenant of a subordinate tenant relationship and is not a sub-tenant, obtaining a first data sharing indicator between other master tenants having a data sharing relationship with the tenant through a tenant application relationship model;

[0027] If there is a first data sharing index higher than the first threshold, the tenant is allocated to the shared database of the main tenant with the highest first data sharing index; if there is no first data sharing index higher than the first threshold, an independent database is allocated to the tenant;

[0028] If the tenant relationship attribute is a sub-tenant of a subordinate tenant relationship, the current tenant is assigned to the shared database to which the main tenant in the subordinate tenant relationship belongs;

[0029] If the tenant relationship attribute is a peer tenant relationship and does not include a subordinate tenant relationship, obtaining a first data sharing indicator between tenants that have a peer tenant relationship with the tenant through a tenant application relationship model;

[0030] If there is a first data sharing index higher than the first threshold, the tenant is allocated to the shared database to which the tenant with the highest first data sharing index belongs; if there is no first data sharing index higher than the first threshold, an independent database is allocated to the tenant.

[0031] Preferably, if the tenant relationship attribute is a sub-tenant of a subordinate tenant relationship, assigning the current tenant to a shared database to which the main tenant in the subordinate tenant relationship belongs includes:

[0032] Get other sub-tenants that have a peer tenant relationship with the tenant;

[0033] Acquire a second data sharing indicator between the tenant and other sub-tenants through the tenant application relationship model;

[0034] If there is a second data sharing index higher than the second threshold, the tenant is allocated to a shared tablespace belonging to other sub-tenants having the highest second data sharing index;

[0035] If there is no second data sharing index higher than the second threshold, an independent table space is allocated to the tenant.

[0036] Preferably, the first data sharing indicator and the second data sharing indicator are both expressed as:

[0037]

[0038] Among them, R represents the correlation between tenant customized applications; C represents the degree of data sharing; F represents the frequency of data access, and ψ, φ and ω are all weight coefficients of data sharing indicators.

[0039] The correlation between the tenant customized applications is obtained through the tenant application relationship model, which is specifically expressed as follows:

[0040]

[0041] Among them, R represents the correlation between tenant customized applications;

[0042] Where the first term represents the custom application relevance, Weight parameters for custom application relevance; Indicates the customized application set of the tenant to be configured. represents the set of customized applications of related tenants; m is the number of customized applications in the tenant application relationship model of the tenant to be configured, The number of elements that represent the symmetric difference between the tenant to be configured and the customized application set of the related tenants. The symmetric difference belongs to But not or belongs to But not The set of elements of ;

[0043] The second term represents the custom synergy weight correlation, is the weight parameter of the customized collaborative weight correlation; n is the number of basic applications in the basic application relationship model, i and j are both integers between [1, m], m is the number of customized applications in the tenant application relationship model of the tenant to be configured, m≤n; is the customized collaboration weight between the customized applications numbered i and j of the tenants to be configured, is the customized collaboration weight between customized applications numbered i and j of related tenants; express and The difference indicator between .

[0044] A multi-tenant enterprise management system based on an SCRM system, comprising:

[0045] Initialization module, used to build the basic application relationship model;

[0046] A data processing module, configured to generate a tenant application relationship model and a multi-tenant relationship model according to the basic application relationship model after receiving a tenant configuration request;

[0047] A judgment module is used to generate a data isolation strategy for a tenant based on the tenant application relationship model and the multi-tenant relationship model.

[0048] An electronic device includes: a processor and a memory, wherein the memory is used to store computer program code, and the computer program code includes computer instructions. When the processor executes the computer instructions, the electronic device executes a multi-tenant enterprise management method based on the SCRM system.

[0049] The beneficial effects of the present invention are: 1. The present application can configure the corresponding tenant application relationship model and the multi-tenant relationship model according to the needs of each tenant, and configure the relationship attributes of each tenant and set the corresponding data isolation strategy so as to more effectively share and utilize these resources, reduce resource waste, and reduce conflicts between tenants; 2. The present application can arrange different databases for each tenant according to the level of each tenant. The data in each database is isolated from each other and does not affect each other, which can improve the data access speed of the tenant and ensure the data security of the tenant. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0051] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0052] Figure 1 A schematic diagram of a multi-tenant enterprise management method based on an SCRM system according to the present invention;

[0053] Figure 2 A schematic diagram of a process flow for generating a multi-tenant relationship model of the present invention;

[0054] Figure 3 A schematic diagram of the sub-tenant allocation process of the present invention;

[0055] Figure 4 The figure is a schematic diagram of the hardware structure of an electronic device of the present invention. DETAILED DESCRIPTION

[0056] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0057] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0058] In addition, the descriptions of "first", "second", etc. in the present invention are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0059] In the multi-tenant enterprise management method based on the SCRM system, the relationship between tenants may involve the relationship between the main tenant and the sub-tenant, the relationship between the same tenant, or the relationship between independent tenants. The existence of these relationships will bring new challenges to data sharing and security. For the relationship between the main tenant and the sub-tenant, the main tenant (such as the headquarters of a large company) may need to access and process the data of its sub-tenants (such as branches). In this case, data sharing is very important to ensure that the main tenant can obtain sufficient information for decision-making and management. At the same time, security cannot be ignored. It is necessary to ensure that only the legitimate main tenant can access the sub-tenant's data, and that the data will not be leaked to irrelevant tenants when sharing. In the multi-tenant enterprise management method based on the SCRM system, different tenant relationships have put forward new requirements for data sharing and security. While meeting the needs of data sharing to improve business efficiency and coordination, it is also necessary to fully consider data security to ensure that sensitive information will not be leaked due to data sharing.

[0060] The present application can configure the corresponding tenant application relationship model and multi-tenant relationship model according to the needs of each tenant, and configure the relationship attributes of each tenant and set the corresponding data isolation strategy to more effectively share and utilize these resources, reduce resource waste, and reduce conflicts between tenants; the present application can arrange different databases for each tenant according to the level of each tenant, and the data in each database is isolated from each other and does not affect each other, which can improve the data access speed of the tenant and ensure the data security of the tenant.

[0061] Example 1

[0062] A multi-tenant enterprise management method based on SCRM system, reference Figure 1 , including the following steps:

[0063] Step S100, constructing a basic application relationship model;

[0064] In this application, basic applications are defined as applications provided by the SaaS (Software as a Service) model. Online applications provided by the SaaS model. This type of application does not need to be installed and run on the user's personal device or the company's server. Instead, it is provided and run by the service provider on its cloud server through the Internet. Users can use any device that can connect to the Internet to access and use it through a browser or a dedicated client. In the SaaS model, all technical requirements of the application, including storage, operation, maintenance, upgrades, etc., are the responsibility of the service provider. This model can help user companies save a lot of IT hardware and operation and maintenance costs, and at the same time has good scalability and elasticity, and can be quickly changed and expanded as user needs change.

[0065] Step S200, after receiving the tenant configuration request, generating a tenant application relationship model and a multi-tenant relationship model according to the basic application relationship model;

[0066] Tenant configuration requests are initiated when a tenant first joins and uses the system, when a tenant needs to modify a custom application, when a tenant needs to adjust the parameter settings of a custom application, or when the tenant structure is adjusted, such as adding or reducing sub-tenants. The system configures the multi-tenant relationship model and the tenant application relationship model accordingly by accepting tenant configuration requests.

[0067] The tenant application relationship model is used to represent the mapping relationship between tenants and customized applications. In this application, customized applications include: Brand building and maintenance. The system provides strong data support for enterprises by analyzing the focus, discussion topics and emotional tendencies of users on social media. Based on these data, enterprises can better understand the needs and expectations of consumers and accurately formulate brand strategies. By establishing in-depth interactions with customers, enterprises can respond to user feedback in a timely manner to improve brand image and reputation. At the same time, the system can also monitor the dynamics of competitors and provide timely intelligence for enterprises to adjust their strategies. Marketing and promotion. Through in-depth mining of user behavior and interests, enterprises can formulate more targeted marketing strategies. For example, the system can accurately place advertisements based on the user's social active time and geographical location to increase the reach of advertisements. In addition, the system can also analyze user feedback on different marketing activities to help enterprises optimize advertising content and form and improve advertising effectiveness. Through the dissemination effect of social media platforms, the promotion information of enterprises can be spread more quickly and widely, achieving higher exposure. Customer service and support. By monitoring users' questions, complaints and suggestions on social media, enterprises can respond in a timely manner and provide fast and personalized solutions. The system can automatically identify keywords and emotions, classify user questions, and quickly transfer them to professional teams. This not only improves the efficiency of customer service, but also enhances customer experience. At the same time, the system can also help companies build complete customer profiles and provide customers with more personalized services. Through data analysis of customer feedback, companies can continuously improve products and services and enhance customer satisfaction. Product development and innovation, by monitoring user discussions and feedback, companies can grasp the hot spots and trends of the market and adjust product strategies in a timely manner. In addition, the system can also help companies conduct user experience testing and collect users' feelings and suggestions during use. These data provide direction for continuous product innovation and help companies maintain their leading position in the fierce market competition. Risk management and crisis public relations, the system provides companies with powerful tools for preventing crises and conducting crisis public relations by monitoring public opinion trends on social media in real time. The system can quickly discover and analyze negative information related to the company, helping companies respond quickly in the early stages of a crisis. At the same time, by monitoring and analyzing public opinion on crises, companies can better formulate crisis public relations strategies and reduce the negative impact of crises on corporate reputation. Sales and customer relationship management: By analyzing the behavior and interests of users on social media, companies can identify potential customers and conduct targeted sales promotions. The system can also help companies make sales forecasts, predicting customers' purchasing intentions based on their purchase history and behavior patterns, and improving sales hit rates. At the same time, the system helps companies better maintain customer relationships and improve customer loyalty by establishing customer profiles and continuous interaction.Talent recruitment and brand building, by analyzing the personal information, professional skills and work experience of users on social media, companies can more accurately find candidates that meet job requirements. The system can also monitor talent trends in the industry and recruitment information of competitors, providing reference for companies to formulate more competitive talent recruitment strategies. At the same time, by displaying corporate culture and employee benefits on social media, the system can also help companies shape a positive brand image and attract more outstanding talents to join. Market research and trend analysis, by monitoring the comments and discussions of users on social media, companies can have a more comprehensive understanding of the real-time dynamics of the market. The system can identify consumers' attitudes and preferences for different products and services, and provide strong support for companies to adjust their market strategies. At the same time, by tracking the development trends in the industry and the trends of competitors, companies can more keenly capture market opportunities and make timely strategic adjustments. This application can configure the required customized applications for tenants based on the configuration requests of tenants, helping tenants to better operate their businesses.

[0068] The multi-tenant relationship model is used to store the relationship attributes of each tenant. Each tenant may include one or more tenant relationships, especially in subordinate tenant relationships. There are multiple sub-tenants under a main tenant, and there are other sub-tenants under these sub-tenants. Then the tenant relationship attributes of a tenant include both the main tenant and the sub-tenant. Then the sub-tenants belonging to the same main tenant belong to the same-level tenant relationship.

[0069] Step S300: Generate a tenant's data isolation strategy based on the tenant application relationship model and the multi-tenant relationship model.

[0070] The data isolation strategy designed in this application includes three levels:

[0071] Independent database: It has the highest data isolation and security. The data of each tenant is stored in its own database without interfering with each other. At the same time, backup and recovery can be performed independently without affecting other tenants. It has strong customization of database performance requirements and management strategies. However, resource utilization is low because each tenant needs to allocate independent database resources, which easily leads to idle resources and low interaction between tenants.

[0072] Shared database independent table space: By sharing the database, resource utilization efficiency can be improved and costs can be reduced. At the same time, data can be isolated through independent table spaces to ensure a high degree of data security and isolation. A certain balance can be achieved between management complexity and resource utilization. If different tenants have different requirements for data storage, uneven resource allocation may occur. The backup and recovery process is also relatively complex and requires handling of data crossover issues.

[0073] Shared database and shared tablespace: It can maximize the use of resources and significantly reduce costs; it simplifies database management because all data is stored in one tablespace; shared data can be easily interacted and analyzed. However, data isolation is poor, and once data leakage or failure occurs, it may affect all tenants; the backup and recovery process is more complicated and needs to consider data crossover; it is limited by the shared tablespace and has poor customization, and may not meet the special needs of individual tenants.

[0074] Preferably, the basic application relationship model includes:

[0075]

[0076]

[0077]

[0078] in, Represents the basic application relationship model, Represents a basic application set, represents the basic collaborative weight set in the basic application relationship model; in the basic application relationship model, i=1,2,...,n; j=1,2,...,n; n is the number of basic applications in the basic application relationship model, and i and j both represent the numbers of the basic applications; Indicates the basic application numbered i; Represents the basic synergy weight between the basic applications numbered i and j.

[0079] The basic application relationship model connects each basic application through the basic collaboration weight to describe the collaboration degree between each basic application.

[0080] Preferably, the tenant application relationship model includes:

[0081]

[0082]

[0083]

[0084] in, represents the tenant application relationship model of the k-th tenant, represents the customized application set of the kth tenant, represents the customized collaboration weight set of the kth tenant; in the tenant application relationship model, i and j are both integers between [1, m], m≤n; m is the number of customized applications in the tenant application relationship model, and i and j both represent the numbers of customized applications; Indicates the custom application numbered i of the kth tenant; Indicates the customization collaboration weight between the customized applications numbered i and j of the k-th tenant.

[0085] Preferably, the tenant application relationship model includes a set of customized applications and a set of customized collaboration weights. The tenant application relationship model connects various customized applications through customized collaboration weights to describe the collaboration degree between various customized applications.

[0086] The custom application collection includes all custom applications required by the tenant. The number of custom applications can be increased or decreased based on the tenant's needs. Each custom application can be configured with specific parameters that vary depending on its function and purpose. For example, parameters may determine how the application works or which functions of the application can be accessed.

[0087] The custom collaboration weight set is used to describe and quantify the degree of collaboration between custom applications. Each custom collaboration weight is assigned a value, which determines the degree of collaboration between the corresponding two custom applications when processing tasks. The larger the value, the higher the degree of collaboration between the two applications, and vice versa.

[0088] For example, suppose there is a model that contains three custom applications, applications A, B, and C. The custom collaboration weight set may contain two custom collaboration weights, one weight describing the degree of collaboration between application A and application B, and one weight describing the degree of collaboration between application B and application C. The values ​​of the custom collaboration weights may be determined based on the roles of these applications in the task and the workflow between them. Combined with the tenant relationship attributes, the basic application can provide general mechanisms for handling various tenant relationships, such as data access control, permission management, etc. Customized applications specialize these mechanisms to make them more in line with the requirements of specific tenant relationships.

[0089] Preferably, step S200, generating a multi-tenant relationship model according to the basic application relationship model includes:

[0090] Step S210, generating a subordinate tenant relationship according to the basic application relationship model, and the main tenant in the subordinate relationship configures the functional application of the sub-tenant in the subordinate relationship;

[0091] Step S220, generating a peer tenant relationship according to the basic application relationship model, where the tenants in the peer relationship adopt a data sharing mechanism;

[0092] Step S230: generating independent tenant relationships according to the basic application relationship model, and the data of each independent tenant is isolated from each other.

[0093] Sub-tenant relationship: Sub-tenant relationship includes the main tenant and sub-tenant; the main tenant is usually a large enterprise or group company, and the sub-tenant is the branch or subsidiary of the enterprise or group. The main tenant usually has the authority to view and manage the data of all its subordinate sub-tenants and can control the permissions of the sub-tenants. For example, in an enterprise, the headquarters is the main tenant, and the subordinate branches or subsidiaries are sub-tenants. The headquarters can manage and control the data and permissions of all sub-tenants.

[0094] Peer tenant relationships: include relationships between tenants at the same level. These tenants need to share some data. For example, two different departments of the same company may be peer tenants. In some cases, multiple tenants need to share certain data or collaborate in the SCRM system. For example, within a large enterprise or group, there are different departments or business lines, and different departments or business lines may have different needs when using the SCRM system but need to share some data; or two companies (peer tenants) that cooperate to launch a joint marketing campaign need to share some of each other's customer data in the SCRM system.

[0095] Independent tenant relationship: means that tenants are independent in the system and there is no direct data sharing and business relationship between tenants and other tenants.

[0096] It can be understood that the tenant relationship attributes of a tenant can include both subordinate tenant relationships and peer tenant relationships. In the subordinate tenant relationship, the tenant can be both a primary tenant and a sub-tenant relative to other different tenants.

[0097] Preferably, step S300, generating a tenant's data isolation strategy according to the tenant application relationship model and the multi-tenant relationship model includes:

[0098] Step S310, obtaining tenant relationship attributes according to the multi-tenant relationship model;

[0099] Step S320A: if the tenant relationship attribute is an independent tenant relationship, an independent database is allocated to the current tenant;

[0100] Step S320B, if the tenant relationship attribute is a master tenant of a subordinate tenant relationship and is not a sub-tenant, obtaining a first data sharing indicator between other master tenants having a data sharing relationship with the tenant through a tenant application relationship model;

[0101] For example, when dealing with subordinate tenant relationships, the basic application presets the function that the main tenant can view the sub-tenant data. The customized application adds specific permission control on this basis, such as the sub-tenant can view part of the main tenant's data only with the authorization of the main tenant.

[0102] If there is a first data sharing index higher than the first threshold, the tenant is allocated to the shared database of the main tenant with the highest first data sharing index; if there is no first data sharing index higher than the first threshold, an independent database is allocated to the tenant;

[0103] There may be a need for data sharing between main tenants of the same level, so it is necessary to obtain the first data sharing index between the main tenants. If the first data sharing index is higher than the first threshold, it means that the current main tenant shares data with other main tenants very frequently and the amount of shared data is large. In this case, the current tenant needs to be assigned to the shared database of the main tenant with the highest first data sharing index. This will facilitate data sharing between the current main tenant and other main tenants and provide the current main tenant with a faster data sharing service. If the first data sharing index is lower than the first threshold, it means that the current main tenant shares less data with other main tenants. In this way, an independent database can be allocated to the current main tenant to protect the data privacy and security of the current main tenant.

[0104] Step S320C: if the tenant relationship attribute is a sub-tenant of a subordinate tenant relationship, the current tenant is assigned to a shared database to which the main tenant in the subordinate tenant relationship belongs;

[0105] Step S320D: if the tenant relationship attribute is a peer tenant relationship and does not include a subordinate tenant relationship, then obtaining a first data sharing indicator between tenants that have a peer tenant relationship with the tenant through a tenant application relationship model;

[0106] If there is a first data sharing index higher than the first threshold, the tenant is allocated to the shared database to which the tenant with the highest first data sharing index belongs; if there is no first data sharing index higher than the first threshold, an independent database is allocated to the tenant.

[0107] The first data sharing indicator reflects the degree of data sharing between the current tenant and tenants of the same level. If the first data sharing indicator is high, it means that the current tenant has a greater demand for data sharing with tenants of the same level. If the first data sharing indicator is low, it means that the current tenant has a smaller demand for data sharing with tenants of the same level. In the present application, a first threshold is established to judge whether the first data sharing indicator meets the requirement for allocating the current tenant to a shared database. If the first data sharing indicator is higher than the first threshold, it means that the current tenant's data sharing demand needs to enter the shared database to be met, so the current tenant is allocated to the shared database. If the first data sharing indicator is lower than the first threshold, an independent database can be allocated to the current tenant.

[0108] If the current tenant's demand for data sharing applications increases in the future, the current tenant can be assigned from an independent database to a shared database to which the tenant with the highest first data sharing index belongs. If the current tenant's demand for data sharing decreases in the future, but the demand for data security and confidentiality increases, the current tenant can be adjusted from a shared database to an independent database.

[0109] Preferably, reference Figure 3 , step S320C, if the tenant relationship attribute is a sub-tenant of a subordinate tenant relationship, assigning the current tenant to a shared database belonging to the main tenant in the subordinate tenant relationship includes:

[0110] Step S320C1, obtaining other sub-tenants that have a tenant relationship at the same level as the tenant;

[0111] Step S320C2, obtaining a second data sharing indicator between the tenant and other sub-tenants through the tenant application relationship model;

[0112] Step S320C3: if there is a second data sharing index higher than the second threshold, the tenant is allocated to a shared table space to which other sub-tenants with the highest second data sharing index belong;

[0113] Step S320C4: if there is no second data sharing index higher than the second threshold, an independent table space is allocated to the tenant.

[0114] Sub-tenants belonging to the same main tenant can share data as long as each sub-tenant is assigned to the shared database belonging to its main tenant. The second data sharing indicator reflects the degree of data sharing between the current sub-tenant and other sub-tenants. If the second data sharing indicator of the current sub-tenant is higher than the second threshold, it means that the current sub-tenant shares data closely with other sub-tenants, and the current tenant is assigned to the shared table space belonging to other sub-tenants with the highest second data sharing indicator. If the second data sharing indicator of the current sub-tenant is lower than the second threshold, it means that the current sub-tenant has a low demand for data sharing applications, and the current sub-tenant can be assigned to an independent table space.

[0115] If the current sub-tenant's demand for data sharing applications increases in the future, the current sub-tenant can be allocated from an independent tablespace to a shared tablespace belonging to other sub-tenants with the second highest data sharing index. If the current tenant's demand for data sharing decreases in the future and the demand for data security and confidentiality increases, the current tenant can be adjusted from a shared tablespace to an independent tablespace.

[0116] Preferably, the first data sharing indicator and the second data sharing indicator are both expressed as:

[0117]

[0118] Among them, R represents the correlation between tenant customized applications; C represents the degree of data sharing; F represents the frequency of data access, and ψ, φ and ω are all weight coefficients of data sharing indicators.

[0119] The degree of data sharing is the amount or percentage of data shared by a tenant with other tenants. It can be obtained by tracking and recording the frequency and type of data shared by each tenant. For example, the type and amount of data shared can be recorded each time data is shared and used as input to calculate the degree of data sharing, so that the degree of data sharing of each tenant can be known.

[0120] Data access frequency is the number of times a tenant accesses data in a certain period of time. This indicator can be obtained by monitoring and recording the data access behavior of each tenant. This can be achieved by recording the timestamp and the type of data accessed each time the data is accessed. In this way, the data access frequency of each tenant in a given period of time can be calculated.

[0121] The correlation between tenant customized applications is obtained through the tenant application relationship model, which is specifically expressed as follows:

[0122]

[0123] Among them, R represents the correlation between tenant customized applications;

[0124] Where the first term represents the custom application relevance, Weight parameters for custom application relevance; Indicates the customized application set of the tenant to be configured. represents the set of customized applications of related tenants; m is the number of customized applications in the tenant application relationship model of the tenant to be configured, The number of elements that represent the symmetric difference between the tenant to be configured and the customized application set of the related tenants. The symmetric difference belongs to But not or belongs to But not A set of elements of

[0125] The second term represents the custom synergy weight correlation, is the weight parameter of the customized collaborative weight correlation; n is the number of basic applications in the basic application relationship model, i and j are both integers between [1, m], m is the number of customized applications in the tenant application relationship model of the tenant to be configured, m≤n; is the customized collaboration weight between the customized applications numbered i and j of the tenants to be configured, is the customized collaboration weight between customized applications numbered i and j of related tenants; express and The difference indicator between .

[0126] The related tenants are the tenants that need to be analyzed for correlation with the tenant to be configured. In the process of allocating databases, for the main tenant whose tenant relationship attribute is a subordinate tenant relationship and is not a sub-tenant, the related tenant is one of the other main tenants that have a data sharing relationship with the tenant to be configured; for the tenant relationship attribute is a peer tenant relationship and does not include a subordinate tenant relationship, the related tenant is one of the tenants that have a peer tenant relationship with the tenant; in the process of allocating tablespaces, for the sub-tenant whose tenant relationship attribute is a subordinate tenant relationship, the related tenant is one of the other sub-tenants that have a peer tenant relationship with the tenant.

[0127] Example 2

[0128] A multi-tenant enterprise management system based on an SCRM system, comprising:

[0129] Initialization module, used to build the basic application relationship model;

[0130] A data processing module, configured to generate a tenant application relationship model and a multi-tenant relationship model according to the basic application relationship model after receiving a tenant configuration request;

[0131] The judgment module is used to generate a tenant's data isolation strategy based on the tenant application relationship model and the multi-tenant relationship model.

[0132] Example 3

[0133] An electronic device includes: a processor and a memory, the memory is used to store computer program code, the computer program code includes computer instructions, when the processor executes the computer instructions, the electronic device executes a multi-tenant enterprise management method based on the SCRM system.

[0134] refer to Figure 4 , the electronic device 2 includes a processor 21, a memory 22, an input device 23, and an output device 24. The processor 21, the memory 22, the input device 23, and the output device 24 are coupled via a connector, and the connector includes various interfaces, transmission lines, or buses, etc., which are not limited in the embodiments of the present invention. It should be understood that in various embodiments of the present invention, coupling refers to mutual connection in a specific manner, including direct connection or indirect connection through other devices, for example, through various interfaces, transmission lines, buses, etc.

[0135] The processor 21 may be one or more graphics processing units (GPUs). When the processor 21 is a GPU, the GPU may be a single-core GPU or a multi-core GPU. Optionally, the processor 21 may be a processor group consisting of multiple GPUs, and the multiple processors are coupled to each other via one or more buses. Optionally, the processor may also be other types of processors, etc., which are not limited in the embodiments of the present invention.

[0136] The memory 22 can be used to store computer program instructions and various computer program codes including program codes for executing the scheme of the present invention. Optionally, the memory includes but is not limited to random access memory (RAM), read-only memory (ROM), erasable programmable read only memory (EPROM), or portable read only memory (CD-ROM), which is used for related instructions and data.

[0137] The input device 23 is used to input data and / or signals, and the output device 24 is used to output data and / or signals. The output device 24 and the input device 23 may be independent devices or an integrated device.

[0138] The beneficial effects of the present invention are: 1. The present application can configure the corresponding tenant application relationship model and the multi-tenant relationship model according to the needs of each tenant, and configure the relationship attributes of each tenant and set the corresponding data isolation strategy so as to more effectively share and utilize these resources, reduce resource waste, and reduce conflicts between tenants; 2. The present application can arrange different databases for each tenant according to the level of each tenant. The data in each database is isolated from each other and does not affect each other, which can improve the data access speed of the tenant and ensure the data security of the tenant.

[0139] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A multi-tenant enterprise management method based on SCRM system, characterized in that: include: Build a basic application relationship model; After receiving the tenant configuration request, generating a tenant application relationship model and a multi-tenant relationship model according to the basic application relationship model; The multi-tenant relationship model is used to store the relationship attributes of each tenant; Generate a data isolation policy for a tenant according to the tenant application relationship model and the multi-tenant relationship model; The tenant application relationship model includes: ， ， ， in, represents the tenant application relationship model of the k-th tenant, represents the customized application set of the kth tenant, represents the customized collaboration weight set of the kth tenant; in the tenant application relationship model, i and j are both integers between [1, m], m≤n; m is the number of customized applications in the tenant application relationship model, and i and j both represent the numbers of customized applications; Indicates the custom application numbered i of the kth tenant; represents the custom collaboration weight between the custom applications numbered i and j of the kth tenant; Generating a tenant application relationship model and a multi-tenant relationship model according to the basic application relationship model includes the following steps: Generate a subordinate tenant relationship according to the basic application relationship model, wherein the main tenant in the subordinate tenant relationship configures the functional application of the sub-tenant in the subordinate tenant relationship; Generate a peer tenant relationship according to the basic application relationship model, wherein the tenants in the peer tenant relationship adopt a data sharing mechanism; Generate independent tenant relationships based on the basic application relationship model, and isolate the data of each independent tenant from each other; Generating a data isolation strategy for a tenant according to the tenant application relationship model and the multi-tenant relationship model includes: Get tenant relationship attributes according to the multi-tenant relationship model; If the tenant relationship attribute is an independent tenant relationship, an independent database is allocated to the current tenant; If the tenant relationship attribute is a master tenant of a subordinate tenant relationship and is not a sub-tenant, obtaining a first data sharing indicator between other master tenants having a data sharing relationship with the tenant through a tenant application relationship model; If there is a first data sharing index higher than the first threshold, the tenant is allocated to the shared database of the main tenant with the highest first data sharing index; if there is no first data sharing index higher than the first threshold, an independent database is allocated to the tenant; If the tenant relationship attribute is a sub-tenant of a subordinate tenant relationship, the current tenant is assigned to the shared database to which the main tenant in the subordinate tenant relationship belongs; If the tenant relationship attribute is a peer tenant relationship and does not include a subordinate tenant relationship, obtaining a first data sharing indicator between tenants that have a peer tenant relationship with the tenant through a tenant application relationship model; If there is a first data sharing index higher than the first threshold, the tenant is allocated to the shared database to which the tenant with the highest first data sharing index belongs; if there is no first data sharing index higher than the first threshold, an independent database is allocated to the tenant.

2. According to the multi-tenant enterprise management method based on the SCRM system of claim 1, it is characterized in that: The basic application relationship model includes: ， ， ， in, Represents the basic application relationship model, Represents a basic application set, represents the basic collaborative weight set in the basic application relationship model; in the basic application relationship model, i=1,2,...,n; j=1,2,...,n; n is the number of basic applications in the basic application relationship model, and i and j both represent the numbers of the basic applications; Indicates the basic application numbered i; Represents the basic synergy weight between the basic applications numbered i and j.

3. According to the multi-tenant enterprise management method based on the SCRM system of claim 1, it is characterized in that: If the tenant relationship attribute is a sub-tenant of a subordinate tenant relationship, the current tenant is assigned to a shared database to which the main tenant in the subordinate tenant relationship belongs, including the steps of: Get other sub-tenants that have a peer tenant relationship with the tenant; Acquire a second data sharing indicator between the tenant and other sub-tenants through the tenant application relationship model; If there is a second data sharing index higher than the second threshold, the tenant is allocated to a shared tablespace belonging to other sub-tenants having the highest second data sharing index; If there is no second data sharing index higher than the second threshold, an independent table space is allocated to the tenant.

4. A multi-tenant enterprise management method based on SCRM system according to claim 3, characterized in that: The first data sharing indicator and the second data sharing indicator are both expressed as: ； Among them, R represents the correlation between tenant customized applications; C represents the degree of data sharing; F represents the frequency of data access, and ψ, φ and ω are all weight coefficients of data sharing indicators.

5. A multi-tenant enterprise management method based on SCRM system according to claim 4, characterized in that: The correlation between the tenant customized applications is obtained through the tenant application relationship model, which is specifically expressed as follows: ； Among them, R represents the correlation between tenant customized applications; Where the first term represents the custom application relevance, Weight parameters for custom application relevance; Indicates the customized application set of the tenant to be configured. represents the set of customized applications of related tenants; m is the number of customized applications in the tenant application relationship model of the tenant to be configured, The number of elements that represent the symmetric difference between the tenant to be configured and the customized application set of the related tenants. The symmetric difference belongs to But not or belongs to But not A set of elements of The second term represents the custom synergy weight correlation, is the weight parameter of the customized collaborative weight correlation; n is the number of basic applications in the basic application relationship model, i and j are both integers between [1, m], m is the number of customized applications in the tenant application relationship model of the tenant to be configured, m≤n; is the customized collaboration weight between the customized applications numbered i and j of the tenants to be configured, is the customized collaboration weight between customized applications numbered i and j of related tenants; express and The difference indicator between .

6. A multi-tenant enterprise management system based on the SCRM system, characterized in that: A multi-tenant enterprise management method based on an SCRM system for implementing any one of claims 1 to 5, comprising: Initialization module, used to build the basic application relationship model; A data processing module, configured to generate a tenant application relationship model and a multi-tenant relationship model according to the basic application relationship model after receiving a tenant configuration request; A judgment module is used to generate a data isolation strategy for a tenant based on the tenant application relationship model and the multi-tenant relationship model.

7. An electronic device, characterized in that: include: A processor and a memory, wherein the memory is used to store computer program code, wherein the computer program code includes computer instructions. When the processor executes the computer instructions, the electronic device executes a multi-tenant enterprise management method based on an SCRM system as described in any one of claims 1 to 5.

Images