A method for deploying and using multiple SaaS applications in a single organization

By adopting multi-SaaS and application deployment methods on the SaaS platform, the problem of low work efficiency of the administrative system of traditional agencies and units is solved, cost reduction, security improvement and application collaborative use are achieved, and functional needs in different scenarios are met.

CN115509548BActive Publication Date: 2024-12-03GUANGZHOU MINSTONE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202211360080.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-11-02
Publication Date
2024-12-03
Estimated Expiration
2042-11-02

AI Technical Summary

Technical Problem

The administrative system of traditional agencies and units is inefficient in their work, and requires the development and deployment of system software and hardware. The maintenance costs are high and the security is insufficient. The application collaborative use cannot be fully utilized, and it cannot efficiently serve local urban construction and social and economic construction.

Method used

Using a single organization's multi-SaaS and application deployment method, including application component layer, combined service layer and SaaS platform application center layer, hierarchical components are constructed through tenant business requirements and application hierarchical models, and tenant applications are constructed based on functional data division rules. Deploy service stations to support role permission division and business function requirements, and realize the reconstruction and sharing of functional data.

Benefits of technology

Reduce the application deployment and maintenance costs of each unit, improve work efficiency, and realize the functional support of different user objects in different scenarios. Through the division of role permissions and business function requirements, some functional data sharing and personalized functional data independence are realized. , meets the business needs of multiple units.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115509548B_ABST
    Figure CN115509548B_ABST
Patent Text Reader

Abstract

The present invention discloses a method for deploying and using multiple SaaS applications in a single organization, including: an application component layer, a composite service layer, and a SaaS platform application center layer; the application component layer is used to construct a number of layered components based on tenant business requirements and an application layering model; the composite service layer is used to construct a tenant application deployment service station based on a functional data division rule; the SaaS platform application center layer is used to reconstruct functional data of a number of layered components based on the tenant application deployment service station by dividing the functional data through business functional requirements, and obtain new application data between units, wherein there are multiple units in a tenant, and the multiple units process personalized requirements between units through configuration. Thus, the functions used by different users in the same and different scenarios are met, and the use of multiple identical applications within a set of organizations and units is supported.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of application deployment technology, and in particular to a method for deploying and using multiple SaaS-based applications of a single organization. Background Art

[0002] For regional-level government agencies, the traditional administrative systems of government agencies have low work efficiency. Each agency not only needs to develop system software and deploy hardware equipment, but also requires professional IT personnel to maintain the system software and hardware. This is costly and insecure, and it is impossible to give full play to the collaborative use of applications of various units. The application software of each unit cannot effectively serve local urban construction and social and economic development.

[0003] There is an urgent need for a deployment that supports the existence of multiple identical applications in the SaaS platform application center, where the functions of the same application are differentiated to meet the needs of different users in the same and different scenarios, and to support the use of multiple identical applications within an organization or unit, with role authority division, partial function data sharing, and individual function data independence. Summary of the invention

[0004] The present invention provides a method for deploying and using multiple SaaS applications in a single organization to solve the problems in the prior art that the administrative system of traditional regional-level agencies and units is inefficient. Each unit not only needs to develop system software and deploy hardware equipment, but also needs professional IT personnel to maintain the system software and hardware, which is costly and insecure. It is impossible to give full play to the collaborative use of applications of various units, and the application software of various units cannot efficiently serve local urban construction and social and economic construction. There is an urgent need for a deployment that supports the existence of multiple identical applications in the SaaS platform application center, in which the functions of the same application are differentiated to meet the functions used by different users in the same and different scenarios, and supports the use of multiple identical applications within a set of organizations and units, through role authority division, partial function data sharing, and individual function data independence.

[0005] In order to achieve the above object, the present invention provides the following technical solutions:

[0006] A single organization's multi-SaaS same-application deployment, including: application component layer, composite service layer and SaaS platform application center layer;

[0007] The application component layer is used to build several layered components based on tenant business requirements and application layered models;

[0008] The combined service layer is used to build a tenant application deployment service station based on the functional data partitioning rules;

[0009] The application center layer of the SaaS platform is used to deploy service stations based on tenant applications, reconstruct functional data of several layered components according to business function requirements, and obtain new application data of each unit. Among them, the tenant has multiple units, and multiple units perform updated business demand processing between units.

[0010] Wherein, the application component layer includes: an application division unit, a relationship determination unit and a component construction unit;

[0011] The application division unit is used to perform business demand analysis on applications of different units and obtain service components to be developed according to the business demand analysis results;

[0012] The relationship determination unit is used to analyze the dependency relationship between the service component to be developed and the service of the application layer model, and determine the level of the service component to be developed in the application layer model;

[0013] The component construction unit is used to divide the components into a number of hierarchical components according to the dependency relationship between the unit application components, store the several hierarchical components in the component library, and update the corresponding application hierarchical model at the same time.

[0014] Wherein, the composite service layer includes: a business service unit, a service matching unit and a configuration metadata unit;

[0015] The business service unit is used to perform service analysis on a number of layered components, extract a business function group of an abstract application to be constructed from the service analysis, and perform semantic description on the business function group;

[0016] The service matching unit is used to obtain the business function description of the same semantics of the business function group and the layered component according to the semantic description of the business function group, and construct an abstract application according to the business function description;

[0017] The configuration metadata unit is used to configure the metadata of the application based on the functional data division rules, starting from building an abstract application, under the framework of the abstract application, to build a tenant application deployment service station.

[0018] The multi-SaaS application deployment layer includes: a building hierarchy unit, a configuration unit and a deployment unit;

[0019] The layer construction unit is used to analyze the application business abstraction layer to be constructed based on the tenant application deployment service station and obtain the corresponding analysis result;

[0020] The configuration unit is used to select an abstract application, configure unit metadata, match existing abstract applications with the business needs of each unit, and select an abstract application that matches the unit needs;

[0021] The deployment unit is used to drive metadata based on role authority division and business function requirement division to generate SaaS applications for each unit to replace the original unit applications.

[0022] Wherein, the deployment unit includes: an agreement signing subunit;

[0023] After obtaining the SaaS applications of each unit, the applications are registered and metadata information is further configured; based on the requirements of each unit for component performance, a tenant level agreement is signed based on the signed agreement sub-unit, and each unit selects the corresponding service level for each service in the application; after the tenant level agreement is signed, each service component in the application of each unit is called, among which, among multiple deployed service components that provide the same function, a service component that meets the corresponding performance requirements and the lower-level service components that the service component depends on are selected according to the signed tenant level agreement to provide business services for the corresponding unit.

[0024] A method for using multiple SaaS-based applications in a single organization, comprising:

[0025] S101: Build several layered components based on tenant business requirements and application layered models;

[0026] S102: Building a tenant application deployment service station based on functional data division rules;

[0027] S103: Based on the tenant application deployment service station, several layered components are divided and constructed into functional data according to business function requirements, and new application data of each unit is obtained. Among them, the tenant has multiple units, and multiple units perform updated business demand processing between units.

[0028] Wherein, the step S101 includes:

[0029] S1011: Analyze the business requirements of applications of different units and obtain the service components to be developed based on the results of the business requirements analysis;

[0030] S1012: Analyze the dependency between the service component to be developed and the service of the application layer model, and determine the layer of the service component to be developed in the application layer model;

[0031] S1013: Divide the application components of each unit into a number of hierarchical components according to the dependency relationship between the components, store the several hierarchical components in a component library, and update the corresponding application hierarchical model at the same time.

[0032] Wherein, the step S102 includes:

[0033] S1021: Perform service analysis on several layered components, extract a business function group of an abstract application to be constructed from the service analysis, and perform semantic description on the business function group;

[0034] S1022: Obtain business function descriptions of the same semantics of the business function group and the layered component according to the semantic description of the business function group, and construct an abstract application according to the business function description;

[0035] S1023: Based on the functional data division rules, starting from building an abstract application, configuring the application metadata under the framework of the abstract application, and building a tenant application deployment service station.

[0036] Wherein, the step S103 includes:

[0037] S1031: Analyze the application business abstraction level to be constructed based on the tenant application deployment service station, and obtain corresponding analysis results;

[0038] S1032: Select an abstract application according to the corresponding analysis result, configure unit metadata, match the business needs of each unit with the existing abstract applications, and select an abstract application that matches the unit needs;

[0039] S1033: Based on the division of role permissions and business function requirements, metadata is driven to generate SaaS applications for each unit to replace the original unit applications.

[0040] Wherein, the step S1033 includes:

[0041] After obtaining the SaaS applications of each unit, the applications are registered and metadata information is further configured; based on the requirements of each unit for component performance, a tenant level agreement is signed based on the signed agreement sub-unit, and each unit selects the corresponding service level for each service in the application; after the tenant level agreement is signed, each service component in the application of each unit is called, among which, among multiple deployed service components that provide the same function, a service component that meets the corresponding performance requirements and the lower-level service components that the service component depends on are selected according to the signed tenant level agreement to provide business services for the corresponding unit.

[0042] Compared with the prior art, the present invention has the following advantages:

[0043] A multi-SaaS same-application deployment of a single organization, comprising: an application component layer, a composite service layer, and a SaaS platform application center layer; the application component layer is used to construct a number of layered components based on tenant business requirements and application layering models; the composite service layer is used to construct a tenant application deployment service station based on functional data division rules; the SaaS platform application center layer is used to reconstruct functional data of a number of layered components based on the tenant application deployment service station through business function requirements and role authority division, and obtain new application data of each unit, wherein the tenant has multiple units, and multiple units perform updated inter-unit business demand processing. Thus, the functions used by different users in the same and different scenarios are met, and multiple identical applications are supported within a set of organizations and units, and the functions of partial functional data sharing and individual functional data independence are realized through business function requirement division and role authority division.

[0044] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the written description, claims, and drawings.

[0045] The technical solution of the present invention is further described in detail below through the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation of the present invention. In the accompanying drawings:

[0047] Figure 1 This is a structural diagram of multi-SaaS same-application deployment for a single organization in an embodiment of the present invention;

[0048] Figure 2 This is an application component layer structure diagram of a single organization's multi-SaaS same-application deployment in an embodiment of the present invention;

[0049] Figure 3 This is a diagram of a combined service layer structure of multiple SaaS applications deployed in a single organization in an embodiment of the present invention. DETAILED DESCRIPTION

[0050] The preferred embodiments of the present invention are described below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present invention, and are not used to limit the present invention.

[0051] The embodiment of the present invention provides a multi-SaaS same-application deployment for a single organization, including: an application component layer, a combined service layer, and a SaaS platform application center layer;

[0052] The application component layer is used to build several layered components based on tenant business requirements and application layered models;

[0053] The combined service layer is used to build a tenant application deployment service station based on the functional data partitioning rules;

[0054] The application center layer of the SaaS platform is used to deploy service stations based on tenant applications, reconstruct functional data of several layered components through business function requirements and role authority division, and obtain new application data of each unit. Among them, the tenant has multiple units, and multiple units perform updated inter-unit business demand processing.

[0055] The working principle of the above technical solution is as follows: the application component layer is used to construct several layered components based on tenant business requirements and application layered models; the combined service layer is used to construct a tenant application deployment service station based on functional data division rules; the SaaS platform application center layer is used to reconstruct functional data of several layered components based on the tenant application deployment service station through business function requirement division and role authority division, and obtain new application data of each unit, wherein the tenant has multiple units, and multiple units perform updated inter-unit business demand processing. This satisfies the functions used by different users in the same and different scenarios, and supports the use of multiple identical applications within a set of organizations and units, and realizes the functions of partial functional data sharing and individual functional data independence through business function requirement division and role authority division.

[0056] Among them, obtaining new application data from each unit is to isolate applications at different sites in a tenant manner. There can be multiple units in a tenant, and then multiple units can handle personalized needs between units through configuration.

[0057] The beneficial effects of the above technical solution are as follows: the application component layer is used to construct several layered components based on tenant business needs and application layered models; the combined service layer is used to construct a tenant application deployment service station based on functional data division rules; the SaaS platform application center layer is used to reconstruct functional data of several layered components based on the tenant application deployment service station through role permissions and business function requirements, and obtain new application data of each unit, wherein the tenant has multiple units, and multiple units perform updated inter-unit business demand processing. This satisfies the functions used by different users in the same and different scenarios, and supports the use of multiple identical applications within a set of organizations and units, and realizes the functions of partial functional data sharing and individual functional data independence through business function requirement division and role permission division.

[0058] In another embodiment, the application component layer includes: an application partitioning unit, a relationship determination unit, and a component construction unit;

[0059] The application division unit is used to perform business demand analysis on applications of different units and obtain service components to be developed according to the business demand analysis results;

[0060] The relationship determination unit is used to analyze the dependency relationship between the service component to be developed and the service of the application layer model, and determine the level of the service component to be developed in the application layer model;

[0061] The component construction unit is used to divide the components into a number of hierarchical components according to the dependency relationship between the unit application components, store the several hierarchical components in the component library, and update the corresponding application hierarchical model at the same time.

[0062] The working principle of the above technical solution is as follows: the application division unit is used to perform business demand analysis on applications of different units, and obtain the service components to be developed according to the business demand analysis results; the relationship determination unit is used to analyze the dependency relationship between the service components to be developed and the services of the application layered model, and determine the level of the service components to be developed in the application layered model; the component construction unit is used to divide the application components of each unit into several layered components according to the dependency relationship between the application components, store the several layered components in the component library, and update the corresponding application layered model at the same time.

[0063] The beneficial effects of the above technical solution are as follows: the application division unit is used to analyze the business needs of applications of different units, and obtain the service components to be developed according to the business needs analysis results; the relationship determination unit is used to analyze the dependency relationship between the service components to be developed and the services of the application layered model, and determine the level of the service components to be developed in the application layered model; the component construction unit is used to divide the application components of each unit into several layered components according to the dependency relationship between the application components of each unit, store the several layered components in the component library, and update the corresponding application layered model at the same time. This reduces the impact of the hierarchical relationship on service resource consumption and service quality when various services are at the same level or different levels.

[0064] In another embodiment, the composite service layer includes: a business service unit, a service matching unit, and a configuration metadata unit;

[0065] The business service unit is used to perform service analysis on a number of layered components, extract a business function group of an abstract application to be constructed from the service analysis, and perform semantic description on the business function group;

[0066] The service matching unit is used to obtain the business function description of the same semantics of the business function group and the layered component according to the semantic description of the business function group, and construct an abstract application according to the business function description;

[0067] The configuration metadata unit is used to configure the metadata of the application based on the functional data division rules, starting from building an abstract application, under the framework of the abstract application, to build a tenant application deployment service station.

[0068] The working principle of the above technical solution is as follows: the business service unit is used to perform service analysis on several hierarchical components, extract the business function group of the abstract application to be constructed from the service analysis, and perform semantic description on the business function group; the service matching unit is used to obtain the business function description of the same semantics of the business function group and the hierarchical component according to the semantic description of the business function group, and construct the abstract application according to the business function description; the configuration metadata unit is used to configure the metadata of the application based on the functional data division rules, starting from the construction of the abstract application, and within the framework of the abstract application, to construct a tenant application deployment service station.

[0069] The beneficial effects of the above technical solution are as follows: the business service unit is used to perform service analysis on several hierarchical components, extract the business function group of the abstract application to be constructed from the service analysis, and perform semantic description on the business function group; the service matching unit is used to obtain the business function description of the same semantics of the business function group and the hierarchical component according to the semantic description of the business function group, and construct the abstract application according to the business function description; the configuration metadata unit is used to configure the metadata of the application based on the functional data division rule, starting from the construction of the abstract application, and under the framework of the abstract application, to construct the tenant application deployment service station. The security of SaaS services can be ensured, and at the same time, there is a calling relationship between services within the same layer.

[0070] In another embodiment, the multi-SaaS application deployment layer includes: a construction hierarchy unit, a configuration unit, and a deployment unit;

[0071] The layer construction unit is used to analyze the application business abstraction layer to be constructed based on the tenant application deployment service station and obtain the corresponding analysis result;

[0072] The configuration unit is used to select an abstract application, configure unit metadata, match existing abstract applications with the business needs of each unit, and select an abstract application that matches the unit needs;

[0073] The deployment unit is used to drive metadata based on role authority division and business function requirement division to generate SaaS applications for each unit to replace the original unit applications.

[0074] The working principle of the above technical solution is: the construction hierarchy unit is used to analyze the application business abstraction hierarchy that needs to be constructed based on the tenant application deployment service station to obtain the corresponding analysis results; the configuration unit is used to select abstract applications, configure unit metadata, match the existing abstract applications according to the business needs of each unit, and select abstract applications that match the unit needs; the deployment unit is used to drive metadata based on role authority division and business function requirement division, generate SaaS applications for each unit, and replace the original unit applications.

[0075] The beneficial effects of the above technical solution are as follows: the construction level unit is used to analyze the application business abstraction level to be constructed based on the tenant application deployment service station and obtain the corresponding analysis results; the configuration unit is used to select abstract applications, configure unit metadata, match the existing abstract applications according to the business needs of each unit, and select abstract applications that match the unit needs; the deployment unit is used to drive metadata based on the role authority division and business function requirement division, generate SaaS applications for each unit, and replace the original unit applications. The metadata of each unit is used to ensure the configurability and isolation of the application, and the application at the logical level is turned into a truly executable application through service deployment.

[0076] In another embodiment, the deployment unit includes: a signing agreement subunit;

[0077] After obtaining the SaaS applications of each unit, the applications are registered and metadata information is further configured; based on the requirements of each unit for component performance, a tenant level agreement is signed based on the signed agreement sub-unit, and each unit selects the corresponding service level for each service in the application; after the tenant level agreement is signed, each service component in the application of each unit is called, among which, among multiple deployed service components that provide the same function, a service component that meets the corresponding performance requirements and the lower-level service components that the service component depends on are selected according to the signed tenant level agreement to provide business services for the corresponding unit.

[0078] The working principle of the above technical solution is: after obtaining the SaaS application of each unit, the application is registered and metadata information is further configured; according to the requirements of each unit for component performance, a tenant level agreement is signed based on the signing of the agreement sub-unit, and each unit selects the corresponding service level for each service in the application; after the tenant level agreement is signed, each service component in the application of each unit is called, among which, among multiple deployed service components that provide the same function, a service component that meets the corresponding performance requirements and the lower-level service components that the service component depends on are selected according to the signed tenant level agreement to provide business services for the corresponding unit.

[0079] The beneficial effects of the above technical solution are: after obtaining the SaaS application of each unit, register the application and further configure the metadata information; according to the requirements of each unit for component performance, a tenant level agreement is signed based on the signed agreement sub-unit, and each unit selects the corresponding service level for each service in the application; after the tenant level agreement is signed, each service component in the application of each unit is called, wherein, among multiple deployed service components providing the same function, a service component that meets the corresponding performance requirements and the lower-level service component that the service component depends on are selected according to the signed tenant level agreement to provide business services for the corresponding unit. In this way, the functions used by different users in the same and different scenarios are met, and multiple identical applications are supported within a set of organizations and units, and the functions of partial function data sharing and individual function data independence are realized through role authority division.

[0080] In another embodiment, a method for using multiple SaaS-based applications of a single organization includes:

[0081] S101: Build several layered components based on tenant business requirements and application layered models;

[0082] S102: Building a tenant application deployment service station based on functional data division rules;

[0083] S103: Based on the tenant application deployment service station, several layered components are divided and constructed into functional data according to business function requirements, and new application data of each unit is obtained. Among them, the tenant has multiple units, and multiple units perform updated business demand processing between units.

[0084] The working principle of the above technical solution is: construct several layered components based on tenant business needs and application layered models; construct a tenant application deployment service station based on functional data division rules; based on the tenant application deployment service station, reconstruct the functional data of several layered components according to business functional requirements, and obtain new application data for each unit, where the tenant has multiple units, and multiple units perform updated business demand processing between units.

[0085] Among them, tenant applications use services in the composite service layer without knowing the specific implementation of the services; the services in the composite service layer are operated through the services in the application component layer; the services in the application center layer of the SaaS platform implement business processes by accepting calls from services in the composite service layer. At the same time, there are also call relationships between services within the same layer. In addition, there are multiple dependencies between services at different levels and between services at the same level.

[0086] The beneficial effects of the above technical solution are: constructing several hierarchical components based on tenant business requirements and application hierarchical models; constructing tenant application deployment service stations based on functional data division rules; based on tenant application deployment service stations, reconstructing functional data of several hierarchical components by business functional requirements division, and obtaining new application data of each unit, wherein the tenant has multiple units, and multiple units perform updated business requirements processing between units. This reduces the impact of hierarchical relationships on service resource consumption and service quality when various services are at the same level or different levels.

[0087] In another embodiment, the step S101 includes:

[0088] S1011: Analyze the business requirements of applications of different units and obtain the service components to be developed based on the results of the business requirements analysis;

[0089] S1012: Analyze the dependency between the service component to be developed and the service of the application layer model, and determine the layer of the service component to be developed in the application layer model;

[0090] S1013: Divide the application components of each unit into a number of hierarchical components according to the dependency relationship between the components, store the several hierarchical components in a component library, and update the corresponding application hierarchical model at the same time.

[0091] The working principle of the above technical solution is: conduct business demand analysis on applications of different units, and obtain the service components to be developed based on the results of the business demand analysis; analyze the dependency relationship between the service components to be developed and the services of the application layered model, and determine the level of the service components to be developed in the application layered model; divide the application components of each unit into several layered components according to the dependency relationship between the components, store the several layered components in the component library, and update the corresponding application layered model at the same time.

[0092] The beneficial effects of the above technical solution are: business demand analysis of applications of different units, obtaining the service components to be developed based on the results of the business demand analysis; analyzing the dependency relationship between the service components to be developed and the services of the application layered model, determining the level of the service components to be developed in the application layered model; dividing the application components of each unit into several layered components according to the dependency relationship, storing the several layered components in the component library, and updating the corresponding application layered model at the same time. This satisfies the functions used by different users in the same and different scenarios, and supports the use of multiple identical applications within a set of organizations and units, and realizes the functions of partial function data sharing and individual function data independence through role authority division.

[0093] In another embodiment, the step S102 includes:

[0094] S1021: Perform service analysis on several layered components, extract a business function group of an abstract application to be constructed from the service analysis, and perform semantic description on the business function group;

[0095] S1022: Obtain business function descriptions of the same semantics of the business function group and the layered component according to the semantic description of the business function group, and construct an abstract application according to the business function description;

[0096] S1023: Based on the functional data division rules, starting from building an abstract application, configuring the application metadata under the framework of the abstract application, and building a tenant application deployment service station.

[0097] The working principle of the above technical solution is: perform service analysis on several layered components, extract the business function group to be built of the abstract application from the service analysis, and perform semantic description on the business function group; obtain the business function description of the same semantics of the business function group and the layered component according to the semantic description of the business function group, and build the abstract application according to the business function description; based on the functional data division rules, take the construction of the abstract application as the starting point, configure the metadata of the application under the framework of the abstract application, and build a tenant application deployment service station.

[0098] The beneficial effects of the above technical solution are: perform service analysis on several layered components, extract the business function group of the abstract application to be constructed from the service analysis, and perform semantic description on the business function group; obtain the business function description of the same semantics of the business function group and the layered component according to the semantic description of the business function group, and construct the abstract application according to the business function description; based on the functional data division rule, take the construction of the abstract application as the starting point, configure the metadata of the application under the framework of the abstract application, and build a tenant application deployment service station. The security of SaaS services can be ensured, and at the same time, there is a calling relationship between services within the same layer.

[0099] In another embodiment, the step S103 includes:

[0100] S1031: Analyze the application business abstraction level to be constructed based on the tenant application deployment service station, and obtain corresponding analysis results;

[0101] S1032: Select an abstract application according to the corresponding analysis result, configure unit metadata, match the business needs of each unit with the existing abstract applications, and select an abstract application that matches the unit needs;

[0102] S1033: Based on the division of role permissions and business function requirements, metadata is driven to generate SaaS applications for each unit to replace the original unit applications.

[0103] The working principle of the above technical solution is: based on the tenant application deployment service station, the application business abstraction level to be constructed is analyzed to obtain the corresponding analysis results; according to the corresponding analysis results, the abstract application is selected, the unit metadata is configured, and the business needs of each unit are matched with the existing abstract applications, and the abstract application that matches the unit needs is selected; based on the division of role permissions and the division of business function requirements, the metadata is driven to generate SaaS applications for each unit to replace the original unit applications.

[0104] Among them, abstract applications that meet business needs are selected from the SaaS applications of each unit, and after obtaining the abstract applications, the corresponding unit needs are analyzed to build new abstract applications; the selected abstract applications are deployed based on the relevant service instances in the application layering model; various functional and non-functional requirements of the unit are analyzed, and the variable points in the abstract applications are configured, and the variable points are described through metadata, including: UI metadata, service metadata, data metadata, permission metadata and functional metadata; metadata is used to drive the operation of each unit application.

[0105] The SaaS services provided by the tenant application deployment service station include m different types of multi-unit SaaS applications, and the number of instances of each type of SaaS application is determined according to the unit service; t unit services, each unit service involves different SaaS applications; n types of resources are available, and the type and number of services used in the end are related to the deployment strategy; SaaS applications are combined and optimized through the optimization deployment plan, and the formula for the combination optimization is:

[0106]

[0107] Where F(m) represents the combined optimization fitness function; V(m) represents the unit metadata set used by individual m; v represents the element in the unit metadata set; e g(v) Represents the corresponding cost value of type g(v); Indicates the highest cost value in the current j-th generation data set; Indicates the lowest cost value in the current j-th generation data set;

[0108] By obtaining the combined optimization fitness function, the consumption of server node resources by SaaS applications is obtained, and the deployment strategy is combined and optimized according to the resource consumption, so as to meet the business needs of various government units for application software.

[0109] The beneficial effects of the above technical solution are: based on the tenant application deployment service station, the application business abstraction level to be constructed is analyzed to obtain the corresponding analysis results; according to the corresponding analysis results, the abstract application is selected, the unit metadata is configured, and the business needs of each unit are matched with the existing abstract application, and the abstract application matching the unit needs is selected; based on the role authority division and the business function requirement division, the metadata is driven to generate the SaaS application of each unit to replace the original unit application. The metadata of each unit is used to ensure the configurability and isolation of the application, and the application at the logical level is turned into a truly executable application through service deployment.

[0110] In another embodiment, the step S1033 includes:

[0111] After obtaining the SaaS applications of each unit, the applications are registered and metadata information is further configured; based on the requirements of each unit for component performance, a tenant level agreement is signed based on the signed agreement sub-unit, and each unit selects the corresponding service level for each service in the application; after the tenant level agreement is signed, each service component in the application of each unit is called, among which, among multiple deployed service components that provide the same function, a service component that meets the corresponding performance requirements and the lower-level service components that the service component depends on are selected according to the signed tenant level agreement to provide business services for the corresponding unit.

[0112] The working principle of the above technical solution is: according to the business needs of each unit, business matching is performed in the corresponding abstract application, an abstract application is selected, registered in the abstract application system, and relevant information corresponding to the unit is filled in, and the relevant information is processed to form partial metadata information;

[0113] After obtaining the SaaS applications of each unit, register the applications and further configure metadata information; based on the requirements of each unit for component performance, sign a tenant level agreement based on the signing agreement subunit, and each unit selects the corresponding service level for each service in the application; after the tenant level agreement is signed, call each service component in the application of each unit, where, among multiple deployed service components that provide the same function, select a service component that meets the corresponding performance requirements and the lower-level service components that the service component depends on according to the signed tenant level agreement to provide business services for the corresponding unit;

[0114] The SaaS application of each unit starts with an abstract application and is driven by unit metadata. The abstract application extracts the business framework of the application, and the specific differences between each unit are described using metadata. The metadata types used to describe the applications of each unit include: functional metadata, page metadata, and style metadata.

[0115] The beneficial effects of the above technical solution are as follows: after obtaining the SaaS application of each unit, the application is registered and metadata information is further configured; according to the requirements of each unit for component performance, a tenant level agreement is signed based on the signed agreement subunit, and each unit selects the corresponding service level for each service in the application; after the tenant level agreement is signed, each service component in the application of each unit is called, wherein, among multiple deployed service components providing the same function, a service component that meets the corresponding performance requirements and the lower-level service components that the service component depends on are selected according to the signed tenant level agreement to provide business services for the corresponding unit. The metadata of each unit is used to ensure the configurability and isolation of the application, and the application at the logical level is turned into a truly executable application through service deployment.

[0116] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A multi-SaaS same-application deployment for a single organization, characterized in that: include: Application component layer, composite service layer and SaaS platform application center layer; The application component layer is used to build several layered components based on tenant business requirements and application layered models; The combined service layer is used to build a tenant application deployment service station based on the functional data partitioning rules; The SaaS platform application center layer is used to deploy service stations based on tenant applications, reconstruct functional data by dividing several layered components according to business function requirements, and obtain new application data between units, wherein a tenant has multiple units, and multiple units process business requirements between units through configuration; The composite service layer includes: a business service unit, a service matching unit and a configuration metadata unit; The business service unit is used to perform service analysis on a number of layered components, extract a business function group of an abstract application to be constructed from the service analysis, and perform semantic description on the business function group; The service matching unit is used to obtain the business function description of the same semantics of the business function group and the layered component according to the semantic description of the business function group, and construct an abstract application according to the business function description; The configuration metadata unit is used to configure the metadata of the application based on the functional data division rule, starting from building an abstract application, under the framework of the abstract application, to build a tenant application deployment service station; The SaaS platform application center layer includes: a building hierarchy unit, a configuration unit and a deployment unit; The layer construction unit is used to analyze the application business abstraction layer to be constructed based on the tenant application deployment service station and obtain the corresponding analysis result; The configuration unit is used to select an abstract application, configure unit metadata, match existing abstract applications with the business needs of each unit, and select an abstract application that matches the unit needs; The deployment unit is used to drive metadata based on role authority division and business function requirement division to generate SaaS applications for each unit to replace the original unit applications; Among them, select abstract applications that meet business needs from the SaaS applications of each unit, analyze the corresponding unit needs after obtaining the abstract applications, and build new abstract applications; deploy the selected abstract applications based on the relevant service instances in the application layering model; analyze the various functional and non-functional requirements of the unit, configure the variable points in the abstract application, and describe the variable points through metadata, including: UI metadata, service metadata, data metadata, permission metadata and function metadata; use metadata to drive the operation of each unit application; The SaaS services provided by the tenant application deployment service station include several different types of multi-unit SaaS applications. The number of instances of each type of SaaS application is determined by the unit service; t unit services, each unit service involves different SaaS applications; n types of resource selection, the type and number of services used in the end are related to the deployment strategy; SaaS applications are combined and optimized through the optimization deployment plan, and the formula for the combination optimization is: in, represents the fitness function of the combined optimization; Represents the unit metadata set used by individual m; Represents an element in a unit metadata collection; Representation Type The corresponding cost value of Indicates the highest cost value in the current j-th generation data set; Indicates the lowest cost value in the current j-th generation data set; The consumption of server node resources by SaaS applications is obtained by obtaining the combined optimization fitness function, and the deployment strategy is combined and optimized according to the resource consumption; The deployment unit includes: a signing agreement subunit; After obtaining the SaaS applications of each unit, the applications are registered and metadata information is further configured; based on the requirements of each unit for component performance, a tenant level agreement is signed based on the signed agreement sub-unit, and each unit selects the corresponding service level for each service in the application; after the tenant level agreement is signed, each service component in the application of each unit is called, among which, among multiple deployed service components that provide the same function, a service component that meets the corresponding performance requirements and the lower-level service components that the service component depends on are selected according to the signed tenant level agreement to provide business services for the corresponding unit.

2. The multi-SaaS same-application deployment of a single organization according to claim 1, characterized in that: The application component layer includes: an application division unit, a relationship determination unit and a component construction unit; The application division unit is used to perform tenant business demand analysis on applications of different units, and obtain service components to be developed according to the business demand analysis results; The relationship determination unit is used to analyze the dependency relationship between the service component to be developed and the service of the application layer model, and determine the level of the service component to be developed in the application layer model; The component construction unit is used to divide the components into a number of hierarchical components according to the dependency relationship between the unit application components, store the several hierarchical components in the component library, and update the corresponding application hierarchical model at the same time.

3. A method for using multiple SaaS applications in a single organization, characterized in that: include: S101: Build several layered components based on tenant business requirements and application layered models; S102: Building a tenant application deployment service station based on functional data division rules; S103: Based on the tenant application deployment service station, several layered components are divided and constructed into functional data according to business function requirements, and new application data of each unit is obtained, wherein the tenant has multiple units, and multiple units perform updated inter-unit business requirements processing; The step S102 includes: S1021: Perform service analysis on several layered components, extract a business function group of an abstract application to be constructed from the service analysis, and perform semantic description on the business function group; S1022: Obtain business function descriptions of the same semantics of the business function group and the layered component according to the semantic description of the business function group, and construct an abstract application according to the business function description; S1023: Based on the functional data division rule, starting from building an abstract application, configuring the metadata of the application under the framework of the abstract application, and building a tenant application deployment service station; The step S103 includes: S1031: Analyze the application business abstraction level to be constructed based on the tenant application deployment service station, and obtain corresponding analysis results; S1032: Select an abstract application according to the corresponding analysis result, configure unit metadata, match the business needs of each unit with the existing abstract applications, and select an abstract application that matches the unit needs; S1033: Based on the division of role permissions and business function requirements, metadata is driven to generate SaaS applications for each unit to replace the original unit applications; Among them, select abstract applications that meet business needs from the SaaS applications of each unit, analyze the corresponding unit needs after obtaining the abstract applications, and build new abstract applications; deploy the selected abstract applications based on the relevant service instances in the application layering model; analyze the various functional and non-functional requirements of the unit, configure the variable points in the abstract application, and describe the variable points through metadata, including: UI metadata, service metadata, data metadata, permission metadata and function metadata; use metadata to drive the operation of each unit application; The SaaS services provided by the tenant application deployment service station include several different types of multi-unit SaaS applications. The number of instances of each type of SaaS application is determined by the unit service; t unit services, each unit service involves different SaaS applications; n types of resource selection, the type and number of services used in the end are related to the deployment strategy; SaaS applications are combined and optimized through the optimization deployment plan, and the formula for the combination optimization is: in, represents the fitness function of the combined optimization; Represents the unit metadata set used by individual m; Represents an element in a unit metadata collection; Representation Type The corresponding cost value of Represents the highest cost value in the current j-th generation data set; Indicates the lowest cost value in the current j-th generation data set; The consumption of server node resources by SaaS applications is obtained by obtaining the combined optimization fitness function, and the deployment strategy is combined and optimized according to the resource consumption; The step S1033 includes: After obtaining the SaaS applications of each unit, the applications are registered and metadata information is further configured; based on the requirements of each unit for component performance, a tenant level agreement is signed based on the signed agreement sub-unit, and each unit selects the corresponding service level for each service in the application; after the tenant level agreement is signed, each service component in the application of each unit is called, among which, among multiple deployed service components that provide the same function, a service component that meets the corresponding performance requirements and the lower-level service components that the service component depends on are selected according to the signed tenant level agreement to provide business services for the corresponding unit.

4. The method for using multiple SaaS applications in a single organization according to claim 3, characterized in that: The step S101 includes: S1011: Analyze the business requirements of applications of different units and obtain the service components to be developed based on the results of the business requirements analysis; S1012: Analyze the dependency between the service component to be developed and the service of the application layer model, and determine the layer of the service component to be developed in the application layer model; S1013: Divide the application components of each unit into a number of hierarchical components according to the dependency relationship between the components, store the several hierarchical components in a component library, and update the corresponding application hierarchical model at the same time.