CN113271334A - Service strategy distribution method and device based on SaaS scene and electronic equipment - Google Patents
Service strategy distribution method and device based on SaaS scene and electronic equipment Download PDFInfo
- Publication number
- CN113271334A CN113271334A CN202110322973.7A CN202110322973A CN113271334A CN 113271334 A CN113271334 A CN 113271334A CN 202110322973 A CN202110322973 A CN 202110322973A CN 113271334 A CN113271334 A CN 113271334A
- Authority
- CN
- China
- Prior art keywords
- service
- tenant
- saas
- request
- service policy
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a service strategy distribution method, a device and electronic equipment based on a software as a service (SaaS) scene, wherein the method comprises the following steps: storing at least two customized business strategy logics realized by a tenant into a storage system of the SaaS software service; receiving a request of a user for acquiring a business strategy logic entity, wherein the business strategy logic entity is one of the at least two customized business strategy logics, and the user is a user for accessing the SaaS software service rented by the tenant; returning a service policy logic entity corresponding to the request; and receiving and storing result data, wherein the result data is implementation result data obtained by implementing the returned service policy logic entity based on the data input by the user. The method can meet the requirement of implementing the special business strategy of the tenant, and also avoid the problem of increasing research, development, operation and maintenance costs caused by the increase of the complexity of the SaaS software service.
Description
Technical Field
The invention belongs to the technical field of cloud computing, and particularly relates to a service strategy distribution method and device based on a software as a service (SaaS) scene and electronic equipment.
Background
Cloud computing is divided into three layers, namely Infrastructure (Infrastructure) -as-a-Service, Platform (Platform) -as-a-Service and Software (Software) -as-a-Service. Infrastructure at the bottom, platform in the middle, software at the top. SaaS is a software service, and a SaaS service provider provides software and applications through the internet. The user can order the software and then access the software through the Web or the provider API, the tenant mentioned in the present application is a user of the SaaS service provider, and the user represents an end software user who uses the software ordered by the tenant.
The SaaS software service is a general service (e.g., a financial system). After a tenant purchases software, if a special business strategy exists, the system is often required to be customized and developed by a Saas service provider, on one hand, if the Saas service is deployed on a public cloud and is connected with multiple tenants, the isolation strategy of the tenant needs to be considered by the Saas provider, the functions of other tenants cannot be affected by customizing and developing a certain tenant, which often brings about the increase of the research and development cost of the Saas provider and the complexity of the architecture of the Saas system. At present, the technical scheme which can meet the requirement of implementing special business strategies of tenants and can avoid the development and operation cost increase caused by the increase of the complexity of the SaaS software service is also lacked.
Disclosure of Invention
In order to solve the problems, the invention provides a service policy distribution method, a service policy distribution device and electronic equipment based on a SaaS scene, which can meet the requirements of implementing special service policies of tenants and avoid the problem of increased research and development and operation and maintenance costs caused by the increase of the complexity of SaaS software services.
The technical scheme adopted by the invention is as follows:
in a first aspect, the present application discloses a service policy distribution method based on a SaaS scenario, including the following steps:
storing at least two customized business strategy logics realized by a tenant into a storage system of the SaaS software service; the tenant is a tenant renting SaaS software service, and the customized business strategy logic is business strategy logic which is realized by the tenant according to the standard provided by the SaaS software service;
receiving a request of a user for acquiring a business strategy logic entity, wherein the business strategy logic entity is one of the at least two customized business strategy logics, and the user is a user for accessing the SaaS software service rented by the tenant;
returning a service policy logic entity corresponding to the request;
and receiving and storing result data, wherein the result data is implementation result data obtained by implementing the returned service policy logic entity based on the data input by the user.
As an optional technical solution, the returning the service policy logic entity corresponding to the request includes the following processes: and returning a corresponding service policy logic entity according to the tenant carried by the request and the service logic policy identification information.
In a second aspect, the present application discloses a service policy distribution apparatus based on a SaaS scenario, including:
the storage module is used for storing at least two customized business strategy logics realized by the tenant into a storage system of the SaaS software service; the tenant is a tenant renting SaaS software service, and the customized business strategy logic is business strategy logic which is realized by the tenant according to the standard provided by the SaaS software service;
a request receiving module, configured to receive a request for a user to obtain a service policy logic entity, where the service policy logic entity is one of the at least two customized service policy logics, and the user is a user accessing a SaaS software service rented by the tenant;
a return module, configured to return a service policy logic entity corresponding to the request;
and the implementation result receiving module is used for receiving and storing result data, wherein the result data is implementation result data obtained by implementing the returned business strategy logic entity based on the data input by the user.
As an optional technical solution, the return module includes: and the searching and returning unit is used for searching the corresponding service policy logic entity according to the tenant carried by the request and the service policy identification information, and returning the searched service policy logic entity.
In a third aspect, the present application discloses a service policy distribution method based on a SaaS scenario, including the following steps:
sending a request for acquiring a business strategy logic entity to a SaaS software service; the service policy logic entity is a certain customized service policy logic which is realized by a tenant and stored in the SaaS software service, the tenant is a tenant renting the SaaS software service, and the customized service policy logic is the service policy logic which is realized by the tenant according to the standard provided by the SaaS software service; the customized service strategy logic has at least two types;
receiving a service policy logic entity returned according to the request;
implementing the received service policy logic entity according to data input by a user to obtain implementation result data;
and sending the implementation result data to the SaaS software service.
As an optional technical solution, the service policy logic entity returned according to the request is: and the business strategy logic entity returns according to the tenant carried by the request and the business logic strategy identification information.
In a fourth aspect, the present application discloses a service policy distribution apparatus based on a SaaS scenario, including:
the request sending module is used for sending a request for acquiring the business strategy logic entity to the SaaS software service; the service policy logic entity is a certain customized service policy logic which is realized by a tenant and stored in the SaaS software service, the tenant is a tenant renting the SaaS software service, and the customized service policy logic is the service policy logic which is realized by the tenant according to the standard provided by the SaaS software service; the customized service strategy logic has at least two types;
an entity receiving module, configured to receive a service policy logic entity returned according to the request;
the entity implementation module is used for implementing the received business strategy logic entity according to data input by a user to obtain implementation result data;
and the implementation result sending module is used for sending the implementation result data to the SaaS software service.
As an optional technical solution, the service policy logic entity returned according to the request is: and the business strategy logic entity returns according to the tenant carried by the request and the business logic strategy identification information.
In a fifth aspect, the present application discloses an electronic device comprising: one or more processors; one or more memories; the one or more memories store one or more computer programs, the one or more computer programs comprising instructions, which when executed by the one or more processors, cause the electronic device to perform the method as disclosed in the first or third aspect above.
In a sixth aspect, the present application discloses a computer readable medium comprising a computer program which, when run on a computer, causes the computer to perform the method as disclosed in the first or third aspect above.
The invention has the beneficial effects that:
1. the product flexibility, the universality and the product competitiveness of SaaS manufacturers are improved, and the research and development cost is reduced. Because the SaaS platform does not need to develop and customize the service strategy for each tenant, an expansion capability is provided, and the service strategy can be deployed and distributed on any tenant.
2. The method and the device improve user experience, because the client application downloads the service strategy content to the local in advance, the user directly executes the service strategy locally through the client, and the execution result can be seen immediately, so that the result uncertainty caused by network request interaction is avoided.
Drawings
Fig. 1 is a schematic flow diagram of a service policy distribution method based on a SaaS scenario in an embodiment.
Fig. 2 is a schematic block diagram of a service policy distribution apparatus based on a SaaS scenario in the embodiment.
Fig. 3 is a schematic flow chart of a service policy distribution method based on a SaaS scenario in another embodiment.
Fig. 4 is a schematic block diagram of a service policy distribution apparatus based on a SaaS scenario in another embodiment.
Fig. 5 is a topological diagram in a specific usage scenario.
Fig. 6 is a business strategy distribution process diagram in a specific usage scenario.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The invention is further described with reference to the following figures and specific embodiments.
Examples
As shown in fig. 1, in a first aspect, the present application discloses a service policy distribution method based on SaaS scenario, including the following steps:
storing at least two customized business strategy logics realized by a tenant into a storage system of the SaaS software service; the tenant is a tenant renting SaaS software service, and the customized business strategy logic is business strategy logic which is realized by the tenant according to the standard provided by the SaaS software service;
receiving a request of a user for acquiring a business strategy logic entity, wherein the business strategy logic entity is one of the at least two customized business strategy logics, and the user is a user for accessing the SaaS software service rented by the tenant;
returning a service policy logic entity corresponding to the request;
and receiving and storing result data, wherein the result data is implementation result data obtained by implementing the returned service policy logic entity based on the data input by the user.
As an optional implementation manner, the returning the service policy logic entity corresponding to the request includes the following processes: and returning a corresponding service policy logic entity according to the tenant carried by the request and the service logic policy identification information.
As shown in fig. 2, in a second aspect, the present application discloses a service policy distribution apparatus based on SaaS scenario, including:
the storage module is used for storing at least two customized business strategy logics realized by the tenant into a storage system of the SaaS software service; the tenant is a tenant renting SaaS software service, and the customized business strategy logic is business strategy logic which is realized by the tenant according to the standard provided by the SaaS software service;
a request receiving module, configured to receive a request for a user to obtain a service policy logic entity, where the service policy logic entity is one of the at least two customized service policy logics, and the user is a user accessing a SaaS software service rented by the tenant;
a return module, configured to return a service policy logic entity corresponding to the request;
and the implementation result receiving module is used for receiving and storing result data, wherein the result data is implementation result data obtained by implementing the returned business strategy logic entity based on the data input by the user.
As an optional implementation, the return module includes: and the searching and returning unit is used for searching the corresponding service policy logic entity according to the tenant carried by the request and the service policy identification information, and returning the searched service policy logic entity.
As shown in fig. 3, in a third aspect, the present application discloses a service policy distribution method based on a SaaS scenario, including the following steps:
sending a request for acquiring a business strategy logic entity to a SaaS software service; the service policy logic entity is a certain customized service policy logic which is realized by a tenant and stored in the SaaS software service, the tenant is a tenant renting the SaaS software service, and the customized service policy logic is the service policy logic which is realized by the tenant according to the standard provided by the SaaS software service; the customized service strategy logic has at least two types;
receiving a service policy logic entity returned according to the request;
implementing the received service policy logic entity according to data input by a user to obtain implementation result data;
and sending the implementation result data to the SaaS software service.
As an optional implementation manner, the service policy logic entity returned according to the request is: and the business strategy logic entity returns according to the tenant carried by the request and the business logic strategy identification information.
As shown in fig. 4, in a fourth aspect, the present application discloses a service policy distribution apparatus based on SaaS scenario, including:
the request sending module is used for sending a request for acquiring the business strategy logic entity to the SaaS software service; the service policy logic entity is a certain customized service policy logic which is realized by a tenant and stored in the SaaS software service, the tenant is a tenant renting the SaaS software service, and the customized service policy logic is the service policy logic which is realized by the tenant according to the standard provided by the SaaS software service; the customized service strategy logic has at least two types;
an entity receiving module, configured to receive a service policy logic entity returned according to the request;
the entity implementation module is used for implementing the received business strategy logic entity according to data input by a user to obtain implementation result data;
and the implementation result sending module is used for sending the implementation result data to the SaaS software service.
As an optional implementation manner, the service policy logic entity returned according to the request is: and the business strategy logic entity returns according to the tenant carried by the request and the business logic strategy identification information.
In general, the method of the embodiment includes the following processes: storing customized business strategy logics realized by at least two tenants into a storage system of the SaaS software service; when a user accesses SaaS software service rented by a certain tenant through a terminal application, the terminal application requests to acquire a service policy logic entity, wherein the entity is one of customized service policy logics; after receiving the request, the SaaS software service returns a service policy logic entity corresponding to the request; the terminal application implements the returned service policy logic entity based on data input by the user and feeds back the implementation result of the service policy logic entity to the user; and the user submits data to the SaaS software service rented by the tenant based on the result fed back by the terminal application.
The embodiment provides a method for taking a tenant business strategy as an SaaS software service extension point, and the dependence of the SaaS service on the realization of the business strategy is separated. In the embodiment, the method is realized by combining Javascript programming language with JSONP technology. The advantages of this are:
1. the product flexibility, the universality and the product competitiveness of SaaS manufacturers and the research and development cost are improved. Because the SaaS platform does not need to develop and customize the service strategy for each tenant, an expansion capability is provided, and the service strategy can be deployed and distributed on any tenant.
2. The user experience is improved, because the client application downloads the service strategy content to the local in advance, the user can immediately see the execution result by directly executing the service strategy at the local through the client, and the result uncertainty caused by network request interaction is avoided.
For better understanding of the present invention, the technical solution of the present application is described below with a specific application scenario, which is: tenants 001 and 002 purchase a financial software-as-a-service that is deployed on a public cloud, supporting multi-tenant access. The overall topology is shown in fig. 5, and the specific process is shown in fig. 6, where the service policy (denoted by p 001) of tenant 001 is: the employees on business trips in non-hard areas supplement 100 yuan, and the employees on business trips in hard areas supplement 200 yuan; the business policy of tenant 002 (denoted by p 002) is 200 yuan for employees in non-hard areas and 300 yuan for employees on business in hard areas. The specific implementation process is as follows:
step 1: the tenants 001 and 002 convert the p001 and p002 into data or files according to the business strategy implementation specification provided by the SaaS service, and submit the data or files to the SaaS storage system. In the service policy implementation specification in this embodiment, a Javascript script is used to implement a service policy, and the Javascript script is uploaded to the SaaS service through an HTTP protocol, the SaaS service stores a script file in a storage system, and finally stores storage information of the script (location information of the script in the SaaS storage system), a policy id, and a tenant id as a piece of service policy information in a database of the SaaS service.
Step 2: and a user C001 of the tenant 001 accesses the SaaS financial software service by using the APP, and the APP downloads the service policy content from the SaaS software service. The specific implementation manner of the step is as follows:
2.1, the APP terminal uses an HTTP GET method to request a JSONP file, and the ur1 of the request is HTTP: com/policy/p001cal1back is setPoncy, wherein callback is a keyword of a callback function name of data returned by JSONP agreed by SaaS and APP, and after receiving a request, the SaaS service acquires the function name (setPoncy) called by APP according to the keyword "callback" when resolving url parameters.
2.2, after receiving the request of APP, the SaaS software service completes the request authentication, obtains the user identifier and the tenant identifier from the header field of the request, respectively C001 and 001, then hits and analyzes from the domain name of ur1 that the sub-path of the request is policy/p001 and callback is setPolicy, the cloud service obtains the policy script file of tenant 001 from the database according to the sub-path in combination with the user identifier and the tenant identifier, adds a Javascript statement in the script file, the statement is just the call to setPolicy, the call parameter is the function name for implementing the policy in the script file, and finally returns the modified file content to APP.
2.3, the APP runs the policy file, and after the policy file runs, the setPolicy method is executed (added to the script by the SaaS service in step 2.2), and the policy implementation function of the tenant 001 is set to the variable specified by the APP.
And 2.4, calling the policy function calculation result in the step 2.3 by the APP according to the data input by the user C001 and feeding back the result to the user in real time.
And step 3: the user C002 of tenant 002 accesses the SaaS-based financial system using APP, and the execution steps are similar to step 2, except that the policy file returned by the SaaS software service is a script file that tenant 002 implements via Javascript.
In a fifth aspect, the present application discloses an electronic device comprising: one or more processors; one or more memories; the one or more memories store one or more computer programs, the one or more computer programs comprising instructions, which when executed by the one or more processors, cause the electronic device to perform the method as disclosed in the first or third aspect above.
In a sixth aspect, the present application discloses a computer readable medium comprising a computer program which, when run on a computer, causes the computer to perform the method as disclosed in the first or third aspect above.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the apparatus, the electronic device and the computer-readable medium described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
Those skilled in the art will appreciate that the modules described above may be distributed in the apparatus according to the description of the embodiments, or may be modified accordingly in one or more apparatuses unique from the embodiments. The modules of the above embodiments may be combined into one module, or may be further split into a plurality of sub-modules (units).
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present application may be embodied in the form of a software product, which may be stored in a readable medium or on a network, and includes several instructions to enable an electronic device (which may be a personal computer, a server, a mobile terminal, or a network device) to execute the method according to the embodiments of the present application.
The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope disclosed in the present application, and all the technical solutions falling within the scope of the present invention defined by the claims fall within the scope of the present invention.
Claims (10)
1. A service strategy distribution method based on SaaS scene is characterized by comprising the following steps:
storing at least two customized business strategy logics realized by a tenant into a storage system of the SaaS software service; the tenant is a tenant renting SaaS software service, and the customized business strategy logic is business strategy logic which is realized by the tenant according to the standard provided by the SaaS software service;
receiving a request of a user for acquiring a business strategy logic entity, wherein the business strategy logic entity is one of the at least two customized business strategy logics, and the user is a user for accessing the SaaS software service rented by the tenant;
returning a service policy logic entity corresponding to the request;
and receiving and storing result data, wherein the result data is implementation result data obtained by implementing the returned service policy logic entity based on the data input by the user.
2. The service policy distribution method according to claim 1, wherein the returning the service policy logic entity corresponding to the request includes the following steps: and returning a corresponding service policy logic entity according to the tenant carried by the request and the service logic policy identification information.
3. A service strategy distribution device based on SaaS scene is characterized by comprising:
the storage module is used for storing at least two customized business strategy logics realized by the tenant into a storage system of the SaaS software service; the tenant is a tenant renting SaaS software service, and the customized business strategy logic is business strategy logic which is realized by the tenant according to the standard provided by the SaaS software service;
a request receiving module, configured to receive a request for a user to obtain a service policy logic entity, where the service policy logic entity is one of the at least two customized service policy logics, and the user is a user accessing a SaaS software service rented by the tenant;
a return module, configured to return a service policy logic entity corresponding to the request;
and the implementation result receiving module is used for receiving and storing result data, wherein the result data is implementation result data obtained by implementing the returned business strategy logic entity based on the data input by the user.
4. The service policy distribution apparatus based on SaaS scenario as claimed in claim 3, wherein the returning module comprises: and the searching and returning unit is used for searching the corresponding service policy logic entity according to the tenant carried by the request and the service policy identification information, and returning the searched service policy logic entity.
5. A service strategy distribution method based on SaaS scene is characterized by comprising the following steps:
sending a request for acquiring a business strategy logic entity to a SaaS software service; the service policy logic entity is a certain customized service policy logic which is realized by a tenant and stored in the SaaS software service, the tenant is a tenant renting the SaaS software service, and the customized service policy logic is the service policy logic which is realized by the tenant according to the standard provided by the SaaS software service; the customized service strategy logic has at least two types;
receiving a service policy logic entity returned according to the request;
implementing the received service policy logic entity according to data input by a user to obtain implementation result data;
and sending the implementation result data to the SaaS software service.
6. The service policy distribution method according to claim 5, wherein the service policy logic entity returned according to the request is: and the business strategy logic entity returns according to the tenant carried by the request and the business logic strategy identification information.
7. A service strategy distribution device based on SaaS scene is characterized by comprising:
the request sending module is used for sending a request for acquiring the business strategy logic entity to the SaaS software service; the service policy logic entity is a certain customized service policy logic which is realized by a tenant and stored in the SaaS software service, the tenant is a tenant renting the SaaS software service, and the customized service policy logic is the service policy logic which is realized by the tenant according to the standard provided by the SaaS software service; the customized service strategy logic has at least two types;
an entity receiving module, configured to receive a service policy logic entity returned according to the request;
the entity implementation module is used for implementing the received business strategy logic entity according to data input by a user to obtain implementation result data;
and the implementation result sending module is used for sending the implementation result data to the SaaS software service.
8. The service policy distribution apparatus based on SaaS scenario according to claim 7, wherein the service policy logic entity returned according to the request is: and the business strategy logic entity returns according to the tenant carried by the request and the business logic strategy identification information.
9. An electronic device, comprising: one or more processors; one or more memories; the one or more memories store one or more computer programs, the one or more computer programs comprising instructions, which when executed by the one or more processors, cause the electronic device to perform the method of any of claims 1 or 2 or 5 or 6.
10. A computer-readable medium, comprising a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 or 2 or 5 or 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110322973.7A CN113271334B (en) | 2021-03-25 | 2021-03-25 | Service policy distribution method and device based on SaaS scene and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110322973.7A CN113271334B (en) | 2021-03-25 | 2021-03-25 | Service policy distribution method and device based on SaaS scene and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113271334A true CN113271334A (en) | 2021-08-17 |
| CN113271334B CN113271334B (en) | 2023-07-21 |
Family
ID=77228254
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110322973.7A Active CN113271334B (en) | 2021-03-25 | 2021-03-25 | Service policy distribution method and device based on SaaS scene and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113271334B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116643909A (en) * | 2023-07-27 | 2023-08-25 | 北京仁科互动网络技术有限公司 | Business performance analysis method and device based on SaaS mode CRM system |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100023937A1 (en) * | 2008-07-28 | 2010-01-28 | Chetan Jagatkishore Kothari | System and method of enabling multi-tenancy for software as a service application |
| CN102981440A (en) * | 2012-11-02 | 2013-03-20 | 武汉理工大学 | Intelligent device monitoring and managing system based on software as a service (SaaS) |
| CN103780580A (en) * | 2012-10-23 | 2014-05-07 | 中国电信股份有限公司 | Method, server and system for providing capability access strategy |
| CN104216725A (en) * | 2013-06-04 | 2014-12-17 | Sap欧洲公司 | Repository layer strategy adjustment method for software solution hosting |
| US20150067126A1 (en) * | 2013-08-27 | 2015-03-05 | Connectloud, Inc. | Method and apparatus for multi-tenant service catalog for a software defined cloud |
| US20170201549A1 (en) * | 2016-01-13 | 2017-07-13 | Microsoft Technology Licensing, Llc | Restricting Access to Public Cloud SaaS Applications to a Single Organization |
| CN107409126A (en) * | 2015-02-24 | 2017-11-28 | 思科技术公司 | System and method for protecting enterprise computing environment safety |
| CN108737325A (en) * | 2017-04-13 | 2018-11-02 | 华为技术有限公司 | A kind of multi-tenant data partition method, apparatus and system |
| CN109561226A (en) * | 2017-09-26 | 2019-04-02 | 华为技术有限公司 | A kind of API mixing multi-tenant method for routing, system and API gateway |
| CN110430274A (en) * | 2019-08-09 | 2019-11-08 | 西藏宁算科技集团有限公司 | A kind of document down loading method and system based on cloud storage |
| CN111314491A (en) * | 2020-03-27 | 2020-06-19 | 北京尚医智信健康管理有限公司 | Cross-tenant data interaction method and device, server cluster and medium |
| CN112100262A (en) * | 2020-09-16 | 2020-12-18 | 南京智数云信息科技有限公司 | Method and system for quickly building and dynamically expanding multi-tenant software as a service (SaaS) platform |
| CN112118565A (en) * | 2020-08-14 | 2020-12-22 | 金蝶医疗软件科技有限公司 | Multi-tenant service gray level publishing method and device, computer equipment and storage medium |
-
2021
- 2021-03-25 CN CN202110322973.7A patent/CN113271334B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100023937A1 (en) * | 2008-07-28 | 2010-01-28 | Chetan Jagatkishore Kothari | System and method of enabling multi-tenancy for software as a service application |
| CN103780580A (en) * | 2012-10-23 | 2014-05-07 | 中国电信股份有限公司 | Method, server and system for providing capability access strategy |
| CN102981440A (en) * | 2012-11-02 | 2013-03-20 | 武汉理工大学 | Intelligent device monitoring and managing system based on software as a service (SaaS) |
| CN104216725A (en) * | 2013-06-04 | 2014-12-17 | Sap欧洲公司 | Repository layer strategy adjustment method for software solution hosting |
| US20150067126A1 (en) * | 2013-08-27 | 2015-03-05 | Connectloud, Inc. | Method and apparatus for multi-tenant service catalog for a software defined cloud |
| CN107409126A (en) * | 2015-02-24 | 2017-11-28 | 思科技术公司 | System and method for protecting enterprise computing environment safety |
| US20170201549A1 (en) * | 2016-01-13 | 2017-07-13 | Microsoft Technology Licensing, Llc | Restricting Access to Public Cloud SaaS Applications to a Single Organization |
| CN108737325A (en) * | 2017-04-13 | 2018-11-02 | 华为技术有限公司 | A kind of multi-tenant data partition method, apparatus and system |
| CN109561226A (en) * | 2017-09-26 | 2019-04-02 | 华为技术有限公司 | A kind of API mixing multi-tenant method for routing, system and API gateway |
| CN110430274A (en) * | 2019-08-09 | 2019-11-08 | 西藏宁算科技集团有限公司 | A kind of document down loading method and system based on cloud storage |
| CN111314491A (en) * | 2020-03-27 | 2020-06-19 | 北京尚医智信健康管理有限公司 | Cross-tenant data interaction method and device, server cluster and medium |
| CN112118565A (en) * | 2020-08-14 | 2020-12-22 | 金蝶医疗软件科技有限公司 | Multi-tenant service gray level publishing method and device, computer equipment and storage medium |
| CN112100262A (en) * | 2020-09-16 | 2020-12-18 | 南京智数云信息科技有限公司 | Method and system for quickly building and dynamically expanding multi-tenant software as a service (SaaS) platform |
Non-Patent Citations (3)
| Title |
|---|
| FARZANA SHAIKH,DIPTI PATIL: "Multi-tenant e-commerce based on SaaS model to minimize IT cost", 《 2014 INTERNATIONAL CONFERENCE ON ADVANCES IN ENGINEERING & TECHNOLOGY RESEARCH (ICAETR - 2014)》 * |
| 尧玉才: "基于SaaS的健身管理系统的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
| 杨天骄: "基于SAAS模式电信计费系统的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116643909A (en) * | 2023-07-27 | 2023-08-25 | 北京仁科互动网络技术有限公司 | Business performance analysis method and device based on SaaS mode CRM system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113271334B (en) | 2023-07-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11232497B2 (en) | Fulfillment of cloud service using marketplace system | |
| CN110557284B (en) | Data aggregation method and device based on client gateway | |
| CN109145201B (en) | Information management method, device, equipment and storage medium based on block chain | |
| CN113364853B (en) | Business service system, business request method and gateway equipment | |
| CN101883107B (en) | Method and related device for realizing context perception service application | |
| CN110716783A (en) | Front-end page generation and deployment method and device, storage medium and equipment | |
| CN110262851B (en) | Interface configuration method and device | |
| CN106411970B (en) | A kind of fault handling method based on service call, device and system | |
| CN111127181B (en) | Voucher accounting method and device | |
| US20140379925A1 (en) | Apparatus and method for interworking between app store servers to share application information | |
| CN111639279A (en) | Graphic code generation method, target page loading method and device | |
| US10182104B1 (en) | Automatic propagation of resource attributes in a provider network according to propagation criteria | |
| CN108932640B (en) | Method and device for processing orders | |
| CN109086414B (en) | Method, apparatus and storage medium for searching blockchain data | |
| CN113271334B (en) | Service policy distribution method and device based on SaaS scene and electronic equipment | |
| CN110245014B (en) | Data processing method and device | |
| CN113900907A (en) | Mapping construction method and system | |
| CN113821307A (en) | Method, device and equipment for quickly importing virtual machine mirror image | |
| CN113127335A (en) | System testing method and device | |
| CN114285859B (en) | Data processing method, device, equipment and storage medium for middle layer block chain service | |
| CN114885024B (en) | Routing method, device, equipment and medium of application instance | |
| US20120198039A1 (en) | Service linkage device, program, service linkage method, and service provision system | |
| CN116304403A (en) | Webpage access method and device, computer equipment and storage medium | |
| CN111953718A (en) | Page debugging method and device | |
| CN115358761A (en) | After-sale processing method and device, after-sale processing equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |