Multi-tenant portal dynamic management and control method and system suitable for business plug-in

Abstract

The invention relates to the technical field of business plug-in management and control, in particular to a multi-tenant portal dynamic management and control method and system suitable for business plug-ins, and discloses a portal plug-in operation recording module, a portal plug-in management and control analysis module, a multi-tenant reference analysis module and a portal plug-in management and control execution module. By regularly analyzing the business plug-in in each tenant portal in the system, the core business plug-in of the tenant is dynamically judged, the use and operation of the tenant for all the business plug-ins in the portal are deeply analyzed, and whether the business plug-in in the current portal of the tenant meets the auxiliary matching requirement of the core business plug-in or not is accurately and comprehensively judged; when it is judged that the service plug-in in the current portal of the tenant cannot meet the auxiliary matching requirement of the core service plug-in, the tenant capable of serving as the reference of the service plug-in is quickly and accurately locked in a multi-tenant system through the two steps of primary selection and check selection, and the service plug-in needing to be recommended and downloaded to the target tenant is efficiently analyzed.

Description

Technical Field

[0001] The present invention relates to the technical field of business plugin management and control, and more specifically, it relates to a multi-tenant portal dynamic management and control method and system applicable to business plugins. Background Art

[0002] In today's digital business environment, various business applications based on software systems emerge in an endless stream. Many enterprises or organizations adopt the multi-tenant model to use these application systems to meet the needs of different user groups to carry out diversified businesses on the same platform. Multi-tenant systems usually integrate numerous business plugins with different functions. Each tenant can select and use the corresponding plugins according to its own business characteristics to build a business portal suitable for itself.

[0003] With the continuous development and change of business, the degree of dependence and usage requirements of tenants on business plugins are also in dynamic change. On the one hand, different tenants have their own unique core businesses, and business plugins, as the key tools to support the development of these core businesses, whether they can effectively cooperate with the processes and requirements of core businesses is crucial. For example, for tenants in the e-commerce industry, order management plugins, payment processing plugins, and inventory management plugins often constitute the core business plugins, and their collaborative work directly affects the smooth progress of commodity sales business; while for project management tenants, task assignment plugins, progress tracking plugins, and resource management plugins play a core role during project execution.

[0004] However, in reality, there are many problems plaguing the effective utilization of business plugins by tenants. First of all, it is often difficult for tenants themselves to comprehensively and accurately grasp the specific composition of their core business plugins at different stages. Due to the complexity of business scenarios and factors such as business expansion, the degree of dependence of core businesses on each plugin is not constant. Traditional management methods lack a regular and in-depth analysis mechanism and cannot dynamically determine which plugins are truly in a core position during a specific period, and thus it is difficult to make timely plugin configuration adjustments according to business changes.

[0005] Secondly, even if tenants can roughly determine the core business plugins, it is not easy to judge whether other business plugins in the existing portal can meet the auxiliary matching requirements of the core business plugins. Although each business plugin has its own focus in function, in the actual business process, they need to cooperate with each other and interact with data to form an organic whole to serve the core business. However, tenants lack effective analysis means in evaluating the synergy and functional complementarity between plugins, and often can only judge based on subjective experience or limited business feedback, which is likely to lead to unreasonable business plugin configurations and affect the efficient development of core businesses.

[0006] Furthermore, in a multi-tenant system environment, although numerous tenants coexist on the same platform, each tenant is like an information island, and the beneficial experiences and excellent configuration cases in the use of business plugins among tenants cannot be fully shared and utilized. Each tenant needs to spend a great deal of time and effort exploring a business plugin combination mode suitable for itself. Even if a tenant has found an efficient plugin configuration solution, it is very difficult for other tenants facing similar problems to know about and learn from it.

[0007] In view of the above-mentioned various problems, the present invention proposes a method and system for dynamically controlling business plugins in a multi-tenant portal. Summary of the Invention

[0008] Aiming at the deficiencies of the prior art, the purpose of the present invention is to provide a method and system for dynamically controlling a multi-tenant portal applicable to business plugins.

[0009] To achieve the above purpose, the present invention provides the following technical solutions: A multi-tenant portal dynamic control system applicable to business plugins, including a portal plugin operation record module, a portal plugin control analysis module, a multi-tenant reference analysis module, and a portal plugin control execution module; The portal plugin operation record module is used to generate operation logs of portal plugins for tenants in the system; The portal plugin control execution module is used to regularly determine whether it is necessary to perform portal plugin control steps on a tenant; The multi-tenant reference analysis module, when performing portal plugin control steps on a tenant, marks the tenant as a portal control tenant and selects check-reference tenants from among the multi-tenants; The portal plugin control execution module determines all non-core associated plugins included in all check-reference tenants, selects control recommended plugins from among all non-core associated plugins, determines whether the control recommended plugins have been downloaded in the portal of the portal control tenant, and if the control recommended plugins have not been downloaded in the portal of the portal control tenant, recommends to the portal control tenant to download the control recommended plugins.

[0010] Further, after a tenant in the system uses a business plugin in the portal, an operation log of the portal plugin is generated. The operation log of the portal plugin includes the name of the business plugin, the start time of use, the end time of use, operation data, and an operation complexity index; The operation complexity index of the operation log of the portal plugin is obtained as follows: Obtain the operation data of the operation log of the portal plugin, preprocess and extract features from the obtained operation data, extract operation features, obtain the name of the business plugin in the operation log of the portal plugin, obtain the plugin operation complexity analysis model of the business plugin, input the operation features into the plugin operation complexity analysis model, and output the operation complexity index.

[0011] Further, periodically determine whether it is necessary to perform portal plugin control on tenants. The steps are as follows: Set a portal dynamic control period. Every time a portal dynamic control period elapses, determine the portal plugin control index of each tenant, set a portal plugin control standard index. When the portal plugin control index of a tenant is greater than the portal plugin control standard index, perform the portal plugin control steps on that tenant.

[0012] Further, the process of determining the portal plugin control index of a tenant is as follows: Select a tenant, determine the core business plugins in the tenant's portal, and obtain the basic operation index of the business plugins of the core business plugins. , mark the remaining business plugins in the tenant's portal as non-core business plugins, compare the core business plugins with each non-core business plugin. When there is no functional association between the compared core business plugin and non-core business plugin in the business plugin function relationship diagram, increase the number of independent portal plugins by one, and mark the number of independent portal plugins as , through Calculate to obtain the portal plugin control index of this tenant. , where a4 is the fourth coefficient and a5 is the fifth coefficient; The process of determining the core business plugins in the tenant's portal is as follows: Obtain the basic operation index of each business plugin in the tenant's portal, and mark the business plugin with the largest value of the basic operation index of the business plugin as the core business plugin.

[0013] Further, the process of obtaining the basic operation index of a business plugin is as follows: Select a business plugin, obtain all portal plugin operation logs of the tenant using this business plugin in a portal dynamic control period, calculate the sum and average of the operation complexity indices of all portal plugin operation logs to obtain the average operation complexity index. , calculate the time difference between the end time and start time of the use of the portal plugin operation log to obtain the plugin operation duration, calculate the sum and average of all plugin operation durations to obtain the average plugin operation duration. , sort all portal plugin operation logs in the order of generation, calculate the time difference between the start time of the use of the adjacent subsequent portal plugin operation log and the end time of the use of the previous portal plugin operation log after sorting to obtain the plugin operation interval, calculate the sum and average of all plugin operation intervals to obtain the average plugin operation interval. , calculate the absolute difference between the operation complexity indices of two adjacent portal plugin operation logs after sorting to obtain the operation complexity fluctuation index, calculate the sum and average of all operation complexity fluctuation indices to obtain the average operation complexity fluctuation index. , through Calculate the basic operation index of the service plugin , where a1 is the first coefficient, a2 is the second coefficient, and a3 is the third coefficient.

[0014] Furthermore, select a check reference tenant among multiple tenants: determine the core service plugin of the portal management tenant, mark the remaining tenants with the same core service plugin as the portal management tenant as the primary reference tenants, obtain the tenant reference index of the primary reference tenants, set the tenant reference threshold index. When the tenant reference index of the primary reference tenant is greater than the tenant reference threshold index, mark the corresponding primary reference tenant as the check reference tenant.

[0015] Furthermore, the process of obtaining the tenant reference index of the primary reference tenant is as follows: select a primary reference tenant, obtain all non-core service plugins of the primary reference tenant, compare each non-core service plugin with the core service plugin. When there is a functional association between the core service plugin and the non-core service plugin in the service plugin function relationship diagram, mark the non-core service plugin as a non-core associated plugin, obtain the basic operation matching index of each non-core associated plugin, perform a sum and average calculation on the basic operation matching indexes of all non-core associated plugins, and calculate the tenant reference index of the primary reference tenant; The process of obtaining the basic operation matching index of the non-core associated plugin is as follows: perform an absolute difference calculation on the service plugin basic operation index of the non-core associated plugin and the service plugin basic operation index of the core service plugin to calculate the basic operation deviation , perform a sum calculation on the service plugin basic operation index of the non-core associated plugin and the service plugin basic operation index of the core service plugin to calculate the basic operation sum , and calculate the basic operation matching index of the non-core associated plugin through where a6 is the sixth coefficient and a7 is the seventh coefficient. , where a6 is the sixth coefficient and a7 is the seventh coefficient.

[0016] Furthermore, select a management recommended plugin among all non-core associated plugins: obtain the associated plugin recommendation index of each non-core associated plugin, set the associated plugin recommendation threshold index. When the associated plugin recommendation index of the non-core associated plugin is greater than the associated plugin recommendation threshold index, mark the non-core associated plugin as a management recommended plugin.

[0017] Furthermore, the process of obtaining the associated plugin recommendation index of the non-core associated plugin is as follows: select a non-core associated plugin. When a check reference tenant's portal contains the non-core associated plugin, mark the check reference tenant as an associated plugin tenant, and mark the total number of associated plugin tenants as , compare the business plug-in basic operation indexes of all associated plug-in tenants for the non-core associated plug-in in pairs, calculate the absolute difference between the two compared business plug-in basic operation indexes, and calculate the operation comparison offset index. Sum and average all operation comparison offset indices to calculate the average operation comparison offset index. ,pass Calculate the recommended index of the non-core related plug-in .

[0018] Furthermore, a multi-tenant portal dynamic management and control method applicable to business plug-ins includes the following steps: Step 1: Regularly determine whether portal plug-in management and control is required for tenants; Step 2: When performing portal plug-in management and control on a tenant, mark the tenant as a portal management tenant and select a reference tenant from the multiple tenants; Step 3: Determine all non-core-related plug-ins included in all checked reference tenants, select the control-recommended plug-in from all non-core-related plug-ins, and determine whether the control-recommended plug-in has been downloaded in the portal of the portal-controlled tenant. If the control-recommended plug-in has not been downloaded in the portal of the portal-controlled tenant, recommend the portal-controlled tenant to download the control-recommended plug-in.

[0019] Compared with the prior art, the present invention has the following beneficial effects: The system of the present invention sets up a portal plug-in operation record module and a portal plug-in management and analysis module, regularly analyzes the business plug-ins in each tenant portal in the system, dynamically determines the tenant's core business plug-in, deeply analyzes the tenant's use and operation of all business plug-ins in the portal, accurately and comprehensively determines whether the business plug-in in the tenant's current portal meets the auxiliary matching requirements of the core business plug-in, sets a multi-tenant reference analysis module and a portal plug-in management and execution module, and when it is determined that the business plug-in in the tenant's current portal cannot meet the auxiliary matching requirements of the core business plug-in, through the two steps of preliminary selection and re-selection, quickly and accurately locks the tenants who can refer to the business plug-in in the multi-tenant system, and conducts in-depth correlation and matching analysis on the portal business plug-ins of the referenced tenants, and efficiently analyzes the business plug-ins that need to be recommended to the target tenants for download. This method can assist tenants in dynamically optimizing the business plug-in configuration of their portals, better serve the development of their core businesses, and improve overall business efficiency and competitiveness. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 This is a block diagram of the principle of a multi-tenant portal dynamic management and control system applicable to business plug-ins; Figure 2 A flowchart for obtaining a tenant reference index for initial selection of reference tenants; Figure 3Method flowchart of a multi-tenant portal dynamic control method applicable to business plugins. Detailed implementation manner

[0021] Example 1: Refer to Figures 1 to 2 , a multi-tenant portal dynamic control system applicable to business plugins, including a portal plugin operation record module, a portal plugin control analysis module, a multi-tenant reference analysis module, and a portal plugin control execution module.

[0022] The portal plugin operation record module generates a portal plugin operation log after a tenant in the system uses a business plugin in the portal. The portal plugin operation log includes the name of the business plugin (business plugins include order management plugins, inventory association plugins, customer information management plugins, financial management plugins, etc.), the start time of use, the end time of use, operation data, and an operation complexity index.

[0023] In the system, each business plugin corresponds to a plugin operation complexity analysis model, and all plugin operation complexity analysis models are constructed based on a deep learning model. In this embodiment, the name of the business plugin is not specifically limited. In the embodiment, only business plugin A is used as a representative of the business plugin to disclose the construction process of the plugin operation complexity analysis model: construct a deep learning model, collect multiple operation features of business plugin A being used, train the deep learning model with the operation features, assign an operation complexity index to each operation feature, and the value range of the operation complexity index is (1.0 - 20.0). The larger the operation complexity index, the higher the operation complexity of the tenant for business plugin A. Divide the multiple operation features into a training set, a validation set, and a test set according to a set ratio of 4:2:1, and train the training set, the validation set, and the test set. After training is completed, the plugin operation complexity analysis model of business plugin A is obtained.

[0024] The operation complexity index of the portal plugin operation log is obtained as follows: obtain the operation data of the portal plugin operation log, preprocess and extract features from the obtained operation data to extract operation features, obtain the name of the business plugin of the portal plugin operation log, obtain the plugin operation complexity analysis model of the business plugin, and input the operation features into the plugin operation complexity analysis model to output the operation complexity index.

[0025] The portal plugin control execution module sets a portal dynamic control period. Every time a portal dynamic control period passes, determine the portal plugin control index of each tenant, set a portal plugin control standard index (the portal plugin control standard index is a preset index used to compare with the portal plugin control index). When the portal plugin control index of a tenant is greater than the portal plugin control standard index, perform portal plugin control steps on the tenant.

[0026] The control index of the tenant's portal plug-ins is determined as follows: Select a tenant, determine the core business plug-ins in the tenant's portal, mark the remaining business plug-ins (excluding the core business plug-ins) in the tenant's portal as non-core business plug-ins, and obtain the basic operation index of the business plug-ins of the core business plug-ins. , compare the core business plug-ins with each non-core business plug-in. When there is no functional association between the compared core business plug-in and non-core business plug-in in the business plug-in functional relationship diagram, increase the independent number of portal plug-ins by one, and mark the independent number of portal plug-ins as , and calculate the control index of the tenant's portal plug-ins through , where a4 is the fourth coefficient and a5 is the fifth coefficient. The value of a4 is 1.83 and the value of a5 is 1.27. .

[0027] The business plug-in functional relationship diagram contains all business plug-ins in the system and shows the functional associations between business plug-ins in the form of a relationship tree; for example, there is a functional association between the "order management plug-in" and the "inventory association plug-in" in the business plug-in functional relationship diagram, and there is no functional association between the "customer information management plug-in" and the "financial management plug-in" in the business plug-in functional relationship diagram.

[0028] The core business plug-ins in the tenant portal are determined as follows: Obtain the basic operation index of each business plug-in in the tenant portal, and mark the business plug-in with the largest basic operation index value as the core business plug-in.

[0029] The basic operation index of the business plug-in is obtained as follows: Select a business plug-in, obtain all portal plug-in operation logs of the tenant using this business plug-in during a portal dynamic control period, calculate the sum and average of the operation complexity indices of all portal plug-in operation logs to obtain the average operation complexity index , calculate the time difference between the end time and the start time of the use of the portal plug-in operation log to obtain the plug-in operation duration, calculate the sum and average of all plug-in operation durations to obtain the average plug-in operation duration , sort all portal plug-in operation logs in the order of generation, calculate the time difference between the start time of the use of the adjacent subsequent portal plug-in operation log and the end time of the use of the previous portal plug-in operation log after sorting to obtain the plug-in operation interval, calculate the sum and average of all plug-in operation intervals to obtain the average plug-in operation interval , calculate the absolute difference between the operation complexity indices of two adjacent portal plug-in operation logs after sorting to obtain the operation complexity turbulence index, calculate the sum and average of all operation complexity turbulence indices to obtain the average operation complexity turbulence index , through the business plug-in basic operation index of the business plug-in is calculated , where a1 is the first coefficient, a2 is the second coefficient, a3 is the third coefficient, the value of a1 is 1.48, the value of a2 is 0.92, and the value of a3 is 1.12.

[0030] Set up a portal plug-in operation record module and a portal plug-in control and analysis module to regularly analyze the business plug-ins in each tenant portal in the system, dynamically determine the core business plug-ins of the tenant, deeply analyze the use and operation of all business plug-ins in the portal by the tenant, and accurately and comprehensively determine whether the business plug-ins in the tenant's current portal meet the auxiliary matching requirements of the core business plug-ins.

[0031] Multi-tenant reference analysis module. When performing portal plug-in control steps on a tenant, mark the tenant as a portal-controlled tenant, determine the core business plug-ins of the portal-controlled tenant, mark the remaining tenants with the same core business plug-ins as the portal-controlled tenant as the primary reference tenants, obtain the tenant reference index of the primary reference tenants, set a tenant reference threshold index (the tenant reference threshold index is a preset index used to compare with the tenant reference index). When the tenant reference index of the primary reference tenant is greater than the tenant reference threshold index, mark the corresponding primary reference tenant as a secondary reference tenant.

[0032] The tenant reference index of the primary reference tenant is obtained as follows: Select a primary reference tenant, obtain all non-core business plug-ins of the primary reference tenant, compare each non-core business plug-in with the core business plug-ins. When there is a functional association between the compared core business plug-in and the non-core business plug-in in the business plug-in function relationship diagram, mark the non-core business plug-in as a non-core associated plug-in, obtain the basic operation matching index of each non-core associated plug-in, perform a sum and average calculation on the basic operation matching indexes of all non-core associated plug-ins, and calculate the tenant reference index of the primary reference tenant.

[0033] The basic operation matching index of the non-core associated plug-in is obtained as follows: Calculate the absolute difference between the business plug-in basic operation index of the non-core associated plug-in and the business plug-in basic operation index of the core business plug-in to obtain the basic operation deviation , calculate the sum value of the business plug-in basic operation index of the non-core associated plug-in and the business plug-in basic operation index of the core business plug-in to obtain the basic operation sum value , through calculate the basic operation matching index of the non-core associated plug-in , where a6 is the sixth coefficient, a7 is the seventh coefficient, the value of a6 is 2.19, and the value of a7 is 0.69.

[0034] The portal plug-in management and control execution module determines all non-core associated plug-ins included in all checked reference tenants, obtains the associated plug-in recommendation index of each non-core associated plug-in, sets the associated plug-in recommendation threshold index (the associated plug-in recommendation threshold index is a preset index used for comparison with the associated plug-in recommendation index), and when the associated plug-in recommendation index of the non-core associated plug-in is greater than the associated plug-in recommendation threshold index, marks the non-core associated plug-in as a management and control recommended plug-in, determines whether the management and control recommended plug-in has been downloaded in the portal of the portal management and control tenant, and if the management and control recommended plug-in has not been downloaded in the portal of the portal management and control tenant, recommends downloading the management and control recommended plug-in to the portal management and control tenant.

[0035] The recommended plug-in index of a non-core plug-in is obtained as follows: select a non-core plug-in, and when a selected reference tenant's portal contains the non-core plug-in, mark the selected reference tenant as the associated plug-in tenant, and mark the total number of associated plug-in tenants as , compare the business plug-in basic operation indexes of all associated plug-in tenants for the non-core associated plug-in in pairs, calculate the absolute difference between the two compared business plug-in basic operation indexes, and calculate the operation comparison offset index. Sum and average all operation comparison offset indices to calculate the average operation comparison offset index. ,pass Calculate the recommended index of the non-core related plug-in .

[0036] A multi-tenant reference analysis module and a portal plug-in management and execution module are set up. When it is determined that the business plug-ins in the tenant's current portal cannot meet the auxiliary matching requirements of the core business plug-ins, through the two steps of preliminary selection and reselection, the tenants who can be used for business plug-in reference are quickly and accurately locked in the multi-tenant system, and the portal business plug-ins of the referenced tenants are deeply analyzed for correlation and matching, and the business plug-ins that need to be recommended to the target tenants for download are efficiently analyzed.

[0037] Example 2: Reference Figure 3 The multi-tenant portal dynamic management and control method applicable to business plug-ins includes the following steps: Step 1: Regularly determine whether portal plug-in management and control is required for tenants; Step 2: When performing portal plug-in management and control on a tenant, mark the tenant as a portal management tenant and select a reference tenant from the multiple tenants; Step 3: Determine all non-core-related plug-ins included in all checked reference tenants, select the control-recommended plug-in from all non-core-related plug-ins, and determine whether the control-recommended plug-in has been downloaded in the portal of the portal-controlled tenant. If the control-recommended plug-in has not been downloaded in the portal of the portal-controlled tenant, recommend the portal-controlled tenant to download the control-recommended plug-in.

[0038] Based on the above method, assist tenants in dynamically optimizing the business plug-in configuration of their portals, better serving the development of their core businesses, and enhancing overall business efficiency and competitiveness.

[0039] The above formulas are all dimensionless and take their numerical values for calculation. The preset parameters in the formulas are set by those skilled in the art according to the actual situation.

[0040] The above embodiments can be implemented in whole or in part by software, hardware, firmware, or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired or wireless (such as infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium that the computer can access or a data storage device such as a server or data center that contains one or more collections of available media. The available media can be magnetic media (such as floppy disks, hard disks, magnetic tapes), optical media (such as DVDs), or semiconductor media. The semiconductor media can be a solid-state drive.

[0041] It should be understood that in various embodiments of the present application, the magnitudes of the serial numbers of the above processes do not mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

[0042] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Skilled professionals can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0043] Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated herein.

[0044] In several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the devices or units can be in electrical, mechanical, or other forms.

[0045] If the above-mentioned functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0046] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A multi-tenant portal dynamic control system applicable to business plugins, characterized in that, It includes a portal plugin operation record module, a portal plugin control and analysis module, a multi-tenant reference analysis module, and a portal plugin control execution module; The portal plugin operation record module is used to generate the portal plugin operation logs of tenants in the system; The portal plugin control execution module is used to periodically determine whether it is necessary to perform portal plugin control steps on a tenant; When performing portal plugin control steps on a tenant, the multi-tenant reference analysis module marks the tenant as a portal control tenant and selects check-reference tenants from the multi-tenants; The portal plugin control execution module determines all non-core associated plugins included in all check-reference tenants, selects control recommended plugins from all non-core associated plugins, determines whether the control recommended plugins have been downloaded in the portal of the portal control tenant, and if the control recommended plugins have not been downloaded in the portal of the portal control tenant, recommends to the portal control tenant to download the control recommended plugins.

2. The multi-tenant portal dynamic control system applicable to service plugins according to claim 1, characterized in that After a tenant in the system uses a business plugin in the portal, portal plugin operation logs are generated. The portal plugin operation logs include the business plugin name, the start time of use, the end time of use, operation data, and operation complexity index; The process of obtaining the operation complexity index of the portal plugin operation log is as follows: Obtain the operation data of the portal plugin operation log, preprocess and extract features from the obtained operation data to extract operation features, obtain the business plugin name of the portal plugin operation log, obtain the plugin operation complexity analysis model of the business plugin, and input the operation features into the plugin operation complexity analysis model to output the operation complexity index.

3. The multi-tenant portal dynamic control system applicable to service plugins according to claim 1, characterized in that Periodically determine whether it is necessary to perform portal plugin control steps on a tenant: Set a portal dynamic control period. Every time a portal dynamic control period passes, determine the portal plugin control index of each tenant. Set a portal plugin control standard index. When the portal plugin control index of a tenant is greater than the portal plugin control standard index, perform portal plugin control steps on the tenant.

4. The multi-tenant portal dynamic control system applicable to service plug-ins according to claim 3, characterized in that The process of determining the portal plugin control index of a tenant is as follows: Select a tenant, determine the core business plugins in the tenant's portal, obtain the business plugin basic operation index of the core business plugins, mark the remaining business plugins in the tenant's portal as non-core business plugins, compare the core business plugins with each non-core business plugin. When there is no functional association between the compared core business plugin and non-core business plugin in the business plugin functional relationship diagram, increase the portal plugin independent quantity by one. Determine the portal plugin control index of the tenant based on the business plugin basic operation index of the core business plugins and the portal plugin independent quantity; The process of determining the core business plugins in a tenant's portal is as follows: Obtain the business plugin basic operation index of each business plugin in the tenant's portal, and mark the business plugin with the largest business plugin basic operation index value as the core business plugin.

5. The multi-tenant portal dynamic control system applicable to service plugins according to claim 4, wherein The process of obtaining the basic operation index of a business plugin is as follows: Select a business plugin, obtain all the portal plugin operation logs of the tenant using this business plugin during a portal dynamic control cycle, calculate the sum and average of the operation complexity indices of all the portal plugin operation logs to obtain the average operation complexity index. Calculate the time difference between the end time and the start time of the use of the portal plugin operation logs to obtain the plugin operation duration, calculate the sum and average of all the plugin operation durations to obtain the average plugin operation duration. Sort all the portal plugin operation logs in the order of generation, calculate the time difference between the start time of the use of the adjacent subsequent portal plugin operation log and the end time of the use of the previous portal plugin operation log after sorting to obtain the plugin operation interval, calculate the sum and average of all the plugin operation intervals to obtain the average plugin operation interval. Calculate the absolute difference between the operation complexity indices of two adjacent portal plugin operation logs after sorting to obtain the operation complexity fluctuation index, calculate the sum and average of all the operation complexity fluctuation indices to obtain the average operation complexity fluctuation index. Determine the basic operation index of this business plugin based on the average operation complexity index, the average plugin operation duration, the average plugin operation interval, and the average operation complexity fluctuation index.

6. The multi-tenant portal dynamic management and control system applicable to service plugins according to claim 1, characterized in that, Select the check reference tenant in a multi-tenant environment: Determine the core business plugin of the portal control tenant, mark the remaining tenants with the same core business plugin as the portal control tenant as the primary reference tenants, obtain the tenant reference index of the primary reference tenants, set the tenant reference threshold index. When the tenant reference index of a primary reference tenant is greater than the tenant reference threshold index, mark the corresponding primary reference tenant as the check reference tenant.

7. The multi-tenant portal dynamic control system applicable to service plugins according to claim 1, characterized in that, The process of obtaining the tenant reference index of a primary reference tenant is as follows: Select a primary reference tenant, obtain all the non-core business plugins of this primary reference tenant, compare each non-core business plugin with the core business plugin. When there is a functional association between the compared core business plugin and non-core business plugin in the business plugin functional relationship diagram, mark this non-core business plugin as a non-core associated plugin. Obtain the basic operation matching index of each non-core associated plugin, calculate the sum and average of the basic operation matching indices of all the non-core associated plugins to obtain the tenant reference index of this primary reference tenant. The process of obtaining the basic operation matching index of a non-core associated plugin is as follows: Calculate the absolute difference between the basic operation index of the non-core associated plugin and the basic operation index of the core business plugin to obtain the basic operation deviation value. Calculate the sum of the basic operation index of the non-core associated plugin and the basic operation index of the core business plugin to obtain the basic operation sum value. Determine the basic operation matching index of this non-core associated plugin based on the basic operation deviation value and the basic operation sum value.

8. The multi-tenant portal dynamic control system applicable to service plugins according to claim 1, wherein Select the control recommendation plug-in from all non-nuclear associated plug-ins: obtain the associated plug-in recommendation index of each non-nuclear associated plug-in, set the associated plug-in recommendation threshold index. When the associated plug-in recommendation index of a non-nuclear associated plug-in is greater than the associated plug-in recommendation threshold index, mark this non-nuclear associated plug-in as a control recommendation plug-in.

9. The multi-tenant portal dynamic control system applicable to service plugins according to claim 8, characterized in that The process of obtaining the associated plug-in recommendation index of a non-nuclear associated plug-in is as follows: Select a non-nuclear associated plug-in. When a check reference tenant's portal contains this non-nuclear associated plug-in, mark this check reference tenant as an associated plug-in tenant. Compare the basic operation indexes of business plug-ins of all associated plug-in tenants for this non-nuclear associated plug-in in pairs, calculate the absolute difference between the two compared basic operation indexes of business plug-ins to obtain the operation comparison offset index. Calculate the sum mean of all operation comparison offset indexes to obtain the average operation comparison offset index. Determine the associated plug-in recommendation index of this non-nuclear associated plug-in based on the total number of associated plug-in tenants and the average operation comparison offset index.

10. A multi-tenant portal dynamic control method applicable to business plugins, which is applied to the multi-tenant portal dynamic control system applicable to business plugins described in any one of claims 1-9, and is characterized in that, It includes the following steps: Step 1: Regularly determine whether it is necessary to perform the portal plug-in control step for a tenant; Step 2: When performing the portal plug-in control step for a tenant, mark this tenant as a portal control tenant and select check reference tenants from multiple tenants; Step 3: Determine all non-nuclear associated plug-ins included in all check reference tenants, select the control recommendation plug-ins from all non-nuclear associated plug-ins, determine whether the control recommendation plug-ins have been downloaded in the portal of the portal control tenant. If the control recommendation plug-ins have not been downloaded in the portal of the portal control tenant, recommend downloading the control recommendation plug-ins to the portal control tenant.

Images