Method and apparatus for providing saas service based on automatic authorization

Abstract

The application relates to a method for providing a SaaS service based on automatic authorization, which is executed by a server side and comprises the following steps: dividing functions of the SaaS service into at least one MVP module, wherein each MVP module contains at least one SaaS service function; performing pre-authorization processing on each MVP module to configure pre-authorization permissions of each MVP module; receiving information about one or more MVP modules purchased by a user, determining pre-authorization permissions corresponding to the MVP modules purchased by the user according to the information about the MVP modules purchased by the user; and generating a permission token of the user according to the pre-authorization permissions corresponding to the MVP modules purchased by the user, and sending the permission token to a client. The technical scheme can improve the flexibility of a SaaS service providing process, improve response speed, reduce cost and improve user experience.

Description

Technical Field

[0001] This application generally relates to the field of communication technology, and more particularly to a method and apparatus for providing SaaS services based on automatic authorization. Background Technology

[0002] SaaS (Software as a Service) means that software is provided via the internet. SaaS platform providers deploy application software on their servers, and customers can order the application software services they need from the provider via the internet based on their actual work requirements. They pay the provider according to the amount of service ordered and the duration of the service, and receive the services provided by the SaaS platform provider via the internet.

[0003] Currently, most SaaS services on the market follow the same process in terms of selection, payment and authorization, implementation, and after-sales service and maintenance: First, users who wish to purchase or upgrade a SaaS service contact the SaaS service provider's pre-sales customer service, communicate with the pre-sales customer service to select the SaaS service to purchase or upgrade, and make payment according to the payment account provided by the service provider; then, the SaaS service provider authorizes and allocates functions, and implements the SaaS service purchased or upgraded by the user on-site, thus completing the SaaS service delivery process.

[0004] The aforementioned SaaS service delivery process suffers from drawbacks such as poor flexibility, slow response, high costs, and poor user experience: In the selection phase, most SaaS providers only offer the SaaS service as a whole, forcing users to choose only all its features, resulting in poor flexibility. In the payment and authorization phase, after selecting the desired SaaS service, users must communicate with the provider to confirm their purchase intention, sign a contract, make offline payments, and confirm relevant details before the provider grants the user the necessary permissions, leading to lengthy communication cycles and slow responses. In the implementation phase, traditional SaaS service delivery processes may require various operations such as service content allocation, permission token distribution, on-site environment setup, and user training, many of which require on-site implementation, resulting in high costs. In the after-sales and maintenance phase, if renewal is required upon expiration of the traditional SaaS service, users must repeat the above steps, a cumbersome and time-consuming process that leads to a poor user experience. Summary of the Invention

[0005] In view of the above-mentioned shortcomings of the prior art, this application provides a method and apparatus for providing SaaS services based on automatic authorization, so as to improve the flexibility of the SaaS service provision process, increase response speed, reduce costs and enhance user experience.

[0006] According to a first aspect of this application, a method for providing SaaS services based on automatic authorization is provided, executed by a server, comprising: dividing the functionality of the SaaS service into at least one MVP module, wherein each MVP module contains at least one SaaS service function; performing pre-authorization processing on each MVP module to configure the pre-authorization limit of each MVP module; receiving information about one or more MVP modules purchased by a user, determining the pre-authorization limit corresponding to the MVP module based on the information about the MVP module purchased by the user; generating a permission token for the user based on the pre-authorization limit corresponding to the MVP module purchased by the user, and sending the permission token to a client.

[0007] In one embodiment, the method further includes: combining the MVP modules into at least one MVP module combination based on the correlation between the MVP modules, wherein each MVP module combination contains at least one MVP module.

[0008] In one embodiment, the method further includes setting description information, pricing information, and application scenario information for each MVP module and each combination of MVP modules.

[0009] In one embodiment, the pre-licensing limits of the MVP module combination are determined based on the pre-licensing limits of the MVP modules included in the MVP module combination.

[0010] In one embodiment, the pre-authorization processing for each MVP module to configure the pre-authorization limits for each MVP module includes: obtaining the permission information corresponding to the MVP module based on the association between each MVP module and permission information; and performing pre-authorization processing on the MVP module based on the permission information corresponding to the MVP module to configure the pre-authorization limits for the MVP module.

[0011] In one embodiment, the method further includes obtaining relevant information about the user, wherein generating the user's permission token based on the pre-authorization limit corresponding to the MVP module purchased by the user includes: generating the user's permission token based on the pre-authorization limit corresponding to the MVP module purchased by the user and the user's relevant information.

[0012] In one embodiment, the relevant information of the user includes the user's authentication information, payment information, deployment mode, and access mode.

[0013] In one embodiment, the user's deployment mode includes a cloud deployment mode and a private deployment mode.

[0014] In one embodiment, when the user's deployment mode is the private deployment mode, the permission token is stored as a token file for the client to download.

[0015] According to a second aspect of this application, an apparatus for providing SaaS services based on automatic authorization is provided, including a memory and a processor, wherein the memory stores computer-executable instructions, which, when executed by the processor, implement the method for providing SaaS services based on automatic authorization according to the first aspect of this application.

[0016] According to the above technical solution of this application, by dividing the functions of SaaS services into MVP modules and combining related MVP modules into MVP module combinations, users can flexibly select the required SaaS service functions as needed, thereby improving the flexibility of selecting SaaS service functions; by pre-authorizing MVP modules, generating the user's permission token based on the pre-authorization limit of the MVP modules purchased by the user, and automatically deploying SaaS service functions based on the permission token, the entire SaaS service provision process, including selection, payment and authorization, implementation, and after-sales and maintenance, can be completed online automatically, thereby improving response speed, reducing costs, and enhancing user experience. Attached Figure Description

[0017] The above and other objects, features, and advantages of exemplary embodiments of this application will become readily understood by reading the following detailed description with reference to the accompanying drawings. In the drawings, several embodiments of this application are illustrated by way of example and not limitation, and the same or corresponding reference numerals denote the same or corresponding parts, wherein:

[0018] Figure 1 This is a flowchart of a method for providing SaaS services based on automatic authorization, executed by a server according to an embodiment of this application;

[0019] Figure 2 This is a flowchart illustrating a method for deploying a SaaS service executed by a client and / or a private server according to an embodiment of this application.

[0020] Figure 3 This is a schematic diagram illustrating the communication between a client and / or a private server and a remote server according to embodiments of this application.

[0021] Figure 4 This is a schematic diagram of a device for providing SaaS services based on automatic authorization, arranged on a server side according to an embodiment of this application. Detailed Implementation

[0022] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0023] It should be understood that when the terms "first," "second," etc., are used in the claims, description, and drawings of this application, they are only used to distinguish different objects and not to describe a specific order. The terms "comprising" and "including" used in the description and claims of this application indicate the presence of the described features, integrals, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or collections thereof.

[0024] According to a first aspect of this application, this application provides a method for providing SaaS services based on automatic authorization, which is executed by the server side.

[0025] Figure 1 A flowchart illustrating a method for providing SaaS services based on automatic authorization, executed by a server according to an embodiment of this application, is shown. The method for providing SaaS services based on automatic authorization includes steps S102 to S108, which are described in detail below.

[0026] S102, divide the functionality of the SaaS service into at least one MVP module, where each MVP module contains at least one SaaS service function.

[0027] The SaaS service includes multiple functions, some of which are configured to run independently and are called independent functions, while others cannot run independently and must be combined with one or more other functions to function; these are called combined functions. For example, the SaaS service S includes five functions: a, b, c, d, and e. Functions a, b, and c can run independently and are called independent functions, while functions d and e cannot run independently and are called combined functions.

[0028] An MVP (Minimum Viable Product) module is a minimal set of independently operable functionalities that can meet a user's basic needs. For example, an MVP module may include at least one standalone function and at least one combined function, such as a, a+c, b+e, a+c+d, a+b+c+d, etc.

[0029] In one embodiment, dividing the functionality of the SaaS service into at least one MVP module includes: determining the boundaries and scope of the MVP module based on the characteristics of each function of the SaaS service, the interrelationships between the functions, and the operating conditions of each MVP module; and generating the at least one MVP module based on the boundaries and scope of the MVP module.

[0030] As an example, the inherent characteristics of each function in the SaaS service include its purpose and whether it can run independently. If it cannot run independently, it cannot be divided into a single MVP module, but must be combined with one or more other related functions and divided into an MVP module. The operating condition of each MVP module means that each MVP module must be able to run independently and meet the user's basic needs. For example, the combination of a, b+e, and c+d can meet the user's basic needs. Therefore, the SaaS function S is divided into three MVP modules: the first MVP module, containing function a; the second MVP module, containing the combination of functions b+e; and the third MVP module, containing the combination of functions c+d, as shown in Table 1. The boundaries and scope of the MVP modules refer to the scope of the function set of each MVP module.

[0031] Table 1 Example of MVP module partitioning

[0032] First MVP Module a Second MVP module b+e Third MVP Module c+d

[0033] The functional division of the SaaS service can also be based on other standards, as long as at least one MVP module can be generated in the end. This application does not impose any special restrictions on this.

[0034] In one embodiment, the method further includes:

[0035] S103, based on the correlation between the MVP modules, the MVP modules are combined into at least one MVP module combination, wherein each MVP module combination contains at least one MVP module.

[0036] The correlation between the MVP modules can include functional correlation, predetermined correlation based on the needs of most users, or custom correlation based on specific user needs. For example, the first and second MVP modules of the aforementioned SaaS functionality can be combined into a first MVP module combination, containing functional combination a+(b+e); the first and third MVP modules can be combined into a second MVP module combination, containing functional combination a+(c+d); and the second and third MVP modules can be combined into a third MVP module combination, containing functional combination (b+e)+(c+d), as shown in Table 2. By combining the MVP modules into at least one MVP module combination, the selection of MVP modules is made more convenient and efficient for users.

[0037] Table 2 Examples of MVP Module Combinations

[0038]

[0039] In one embodiment, the method further includes: setting description information, pricing information, and application scenario information for each MVP module and each combination of MVP modules. The description information includes a detailed introduction to each MVP module and each combination of MVP modules, its corresponding functions, and the problems it solves. Setting this information provides users with a reference when making a purchase, thereby facilitating users to carefully select MVP modules or combinations of MVP modules that meet their needs based on their own circumstances.

[0040] S104 performs pre-authorization processing on each MVP module to configure the pre-authorization limits for each MVP module.

[0041] To address the issues of incomplete authorization and confusing cross-authorization in the later stages, and to make the deployment and implementation of subsequent MVP modules faster and more efficient, pre-authorization processing is performed on each MVP module, and pre-authorization limits are configured for each MVP module.

[0042] In one embodiment, the step includes: obtaining permission information corresponding to each MVP module based on the association between each MVP module and permission information; and performing pre-authorization processing on the MVP module based on the permission information corresponding to the MVP module to configure the pre-authorization limit of the MVP module.

[0043] Specifically, the association between each MVP module and permission information can be provided in the form of a permission list. This permission list includes various permissions corresponding to each MVP module, such as access permissions to external interfaces of the SaaS function and internal interfaces of other MVP modules within the SaaS function. This application does not specifically limit the form of the permission information corresponding to each MVP module or the category of the corresponding permissions. After obtaining the permission information corresponding to the MVP module based on the permission list, pre-authorization processing is performed on the MVP module according to the permission information to configure the pre-authorization limits of the MVP module. The pre-authorization processing can be implemented using an automatic authorization algorithm. As an example, the automatic authorization algorithm can be a rule-based automatic authorization algorithm or other automatic authorization algorithms known in the art; this application does not specifically limit this.

[0044] The MVP module that has been pre-authorized through this step already carries the permission information. Users can implement the corresponding MVP module immediately without having to grant permissions again through the authorization service, making the subsequent deployment and implementation of the MVP module faster and more convenient.

[0045] S106, Receive information about one or more MVP modules purchased by the user, and determine the pre-licensing limit corresponding to the MVP module based on the information about the MVP modules purchased by the user.

[0046] Specifically, the user can purchase one or more independent MVP modules, or a combination of the aforementioned MVP modules, or simultaneously purchase one or more independent MVP modules and a combination of MVP modules.

[0047] The pre-license limits corresponding to the MVP modules are determined in step S104. The pre-license limits of the MVP module combination are determined based on the pre-license limits of the MVP modules included in the MVP module combination. Specifically, the pre-license limits of the MVP module combination can inherit the pre-license limits of the MVP modules it contains. Regarding the inheritance method, the pre-license limits of each MVP module included in the MVP module combination can be considered as a set. The pre-license limits of the MVP module combination can be a simple sum of the sets of pre-license limits of each MVP module, or it can be their union. This application does not impose any particular limitation on the method of determining the pre-license limits of the MVP module combination based on the pre-license limits of the MVP modules included in the MVP module combination, as long as the determined pre-license limits of the MVP module combination enable each MVP module therein to operate normally and perform its set functions.

[0048] S108, Based on the pre-authorization limit corresponding to the MVP module purchased by the user, generate the user's permission token and send the permission token to the client.

[0049] The permission token is a string generated by the server that contains the user's identity and permission information, used to verify the user's identity and permissions on the client side, thereby enabling the user to view or operate the corresponding SaaS resources.

[0050] In one embodiment, in step S106, receiving information about one or more MVP modules purchased by the user further includes receiving relevant information about the user. This relevant information includes one or more of the user's authentication information, payment information, deployment mode, and access mode. The authentication information refers to the user's identity authentication information; the payment information refers to the user's MVP module purchase information; the deployment mode refers to the deployment method of the SaaS functionality included in the purchased MVP module, including cloud deployment mode and private deployment mode; and the access mode refers to the user's access method to the SaaS functionality included in the MVP module, including local access and remote access.

[0051] Accordingly, generating the user's permission token includes: generating the user's permission token based on the pre-authorization limit corresponding to the MVP module and the user's relevant information.

[0052] Specifically, a permission token for the user is automatically generated using a permission token generation algorithm. Regarding validity, the permission token can be either a permanent token or a temporary token. A permanent token is valid indefinitely once generated to facilitate user access, while a temporary token is only valid for a predetermined period after generation and expires, thus improving the security of the SaaS service. In terms of permission completeness, the permission token can be either a full permission token or a partial permission token. The former includes all permissions to SaaS resources, while the latter only includes partial permissions, such as excluding the deletion permission for basic SaaS resources shared by all MVP modules, further enhancing the security of the SaaS service. The permission token may also include access restriction information, including global restrictions and interface restrictions, to limit the access time and frequency to MVP modules and related internal and external interfaces, thereby further improving the security of the SaaS service.

[0053] The permission token generation algorithm may include permission token generation algorithms known in the art, such as HMACs algorithm, ECDSA algorithm, SHA algorithm, etc., or a new dedicated permission token generation algorithm may be used. This application does not make any special limitation in this regard.

[0054] After generating the permission token, the permission token is sent to the client for subsequent deployment of SaaS functionality from one or more MVP modules or a combination of MVP modules purchased by the user. When the user's deployment mode is the private deployment mode, the permission token is stored as a token file for the client to download; for example, the token file can be stored in a predetermined storage space.

[0055] At this point, the process of providing SaaS services on the server side is basically complete.

[0056] According to the above-mentioned technical solution of the first aspect of this application, by dividing the functions of SaaS services into MVP modules and combining related MVP modules into MVP module combinations, users can flexibly select the required SaaS service functions as needed, thereby improving the flexibility of selecting SaaS service functions; by pre-authorizing MVP modules and generating the user's permission token based on the pre-authorization limit of the MVP modules purchased by the user, the purchase, payment and authorization links in the SaaS service provision process can be completed online automatically, thereby improving response speed, reducing costs and enhancing user experience.

[0057] To more completely describe the technical solution of this application, so that those skilled in the art can more clearly understand the content and principle of the technical solution of this application, the following describes the method flow for deploying SaaS functions by generating permission tokens based on the method of providing SaaS services with automatic authorization according to the first aspect of this application.

[0058] Figure 2 A flowchart illustrating a method for deploying a SaaS service executed by a client and / or a private server according to an embodiment of this application is shown. The method for deploying the SaaS service includes steps S202 to S206, which are described in detail below.

[0059] Figure 3 A schematic diagram illustrating the communication between the client and / or private server and the remote server is shown. For example... Figure 3 As shown, the client device and the private server are communicatively connected to form a local area network (LAN), which communicates with a remote server. The remote server can be any of the servers described in the first aspect of this application.

[0060] S202, obtain information about one or more MVP modules purchased by the user, and send the information about the MVP modules purchased by the user to the server.

[0061] Specifically, the information on one or more MVP modules purchased by the user can be obtained by the client through obtaining the MVP module purchase information input by the user, or it can be obtained through other means, which are not particularly limited in this application.

[0062] After obtaining the information about the MVP module purchased by the user, the information about the MVP module purchased by the user is sent to the remote server, for example, via wired or wireless communication.

[0063] S204, Receive the user's permission token sent by the server.

[0064] Specifically, the user's permission token is generated by the remote server in response to receiving information about the user's purchase of one or more MVP modules, through step S106 of the method for providing SaaS services based on automatic authorization executed by the server in the first aspect of this application. The specific process and method will not be described in detail here.

[0065] S206, Based on the user's permission token, deploy the corresponding SaaS functions of the MVP module purchased by the user. Depending on the user's different requirements for SaaS functions, there are two scenarios: cloud deployment mode and private deployment mode.

[0066] Specifically, in one embodiment, when the user's deployment mode is cloud deployment mode, deploying the corresponding SaaS function of the MVP module purchased by the user includes: executing the user's permission token on the client to deploy the corresponding function of the MVP module purchased by the user on the client.

[0067] In another embodiment, when the user's deployment mode is a private deployment mode, deploying the corresponding functions of the MVP module purchased by the user includes: downloading the user's token file stored on the server side based on the user's permission token on the client side; and executing the token file on the private server side to deploy the corresponding functions of the MVP module purchased by the user on the private server side. Compared to the cloud deployment mode described above, storing the permission token as a token file and having the user download the generated token file to the private server for installation allows the user to execute the token file with a single click on the private server side for SaaS function deployment.

[0068] In one embodiment, the method further includes: notifying the user after completing the deployment of the corresponding functionality of the MVP module purchased by the user.

[0069] Furthermore, after the SaaS functionality is deployed on the client side, when upgrades and maintenance of the SaaS functionality are required, one or more of the above steps of the method for providing SaaS services based on automatic authorization according to any embodiment of this application can be executed, depending on the specific circumstances. For example, if the user needs to add an MVP module based on the MVP module already purchased and used, steps S102 to S108 and steps S202 to S206 above are executed completely. For example, if the user has already purchased and used a first MVP module and wants to add a second MVP module, the user's existing permission token can be upgraded to the permission token corresponding to the first MVP module combination, and the corresponding function a+(b+e) can be deployed for the user. If the user needs to deactivate the original MVP module and purchase other MVP modules, the original MVP module is first deactivated, and then steps S102 to S108 and steps S202 to S206 above are executed to deploy and implement the SaaS functionality in the other MVP modules. For example, if a user has purchased and used the first MVP module and wants to deactivate it and switch to the second MVP module, then firstly, the first MVP module is deactivated, the user's existing permission token is upgraded to the permission token corresponding to the second MVP module, and the function b+e corresponding to the second MVP module is deployed for the user.

[0070] According to the technical solutions of the above embodiments of this application, by obtaining information about the MVP module purchased by the user, and receiving and executing the user's permission token generated by the server based on the MVP module information, the corresponding functions of the MVP module purchased by the user are deployed for the user. This simple operation of executing the permission token replaces the original lengthy and cumbersome series of implementation actions, enabling the deployment stage in the SaaS service delivery process to be completed automatically online. Furthermore, combined with the above technical solutions according to the first aspect of this application, after-sales maintenance can also be completed online. This allows the entire SaaS service delivery process—including selection, payment and authorization, implementation, and after-sales and maintenance—to be completed automatically online, thereby improving response speed, reducing costs, and enhancing user experience.

[0071] According to a second aspect of this application, this application also provides an apparatus 400 for providing SaaS services based on automatic authorization. For example, the apparatus may be a server-side device, such as... Figure 4As shown, the device 400 includes a memory and a processor. The memory stores computer-executable instructions, which, when executed by the processor, enable the server-side method for providing SaaS services based on automatic authorization, as described in any embodiment of the first aspect of this application. The method for providing SaaS services based on automatic authorization has been described in detail above; further details will not be repeated here, but can be found in the relevant content of the first aspect of this application.

[0072] The apparatus according to the second aspect of this application also includes other components well known to those skilled in the art, such as a communication bus and a communication interface, the setup and function of which are known in the art and therefore will not be described in detail here.

[0073] To make the technical solution of this application easier to understand, the following example is used to describe in detail the specific method and process of providing SaaS services based on automatic authorization, including the following steps S1 to S3.

[0074] S1, users purchase / upgrade one or more MVP modules and / or combinations of MVP modules on the client.

[0075] S2, the server obtains the corresponding pre-authorization information based on the MVP module and / or combination of MVP modules purchased by the user, and automatically generates an authorization token based on the pre-authorization information.

[0076] S3, the client and / or private server deploy the SaaS functionality included in the MVP module and / or the combination of MVP modules according to the user's deployment mode (cloud deployment mode or private deployment mode):

[0077] S3.1 If the user's deployment mode is cloud deployment mode, the client automatically executes the permission token, deploys the SaaS functions contained in the MVP module and / or the combination of MVP modules on the client, and notifies the user after the implementation is completed;

[0078] S3.2 If the user's deployment mode is a private deployment mode, the server will store the permission token as the user's token file. After the client downloads the token file, it will execute the token file on the private server to deploy the MVP module and / or the SaaS functions contained in the MVP module combination on the private server, and notify the user after the implementation is completed.

[0079] The above examples detail the specific methods and processes for providing SaaS services based on automatic authorization in this application. Through the technical solution in this example, the entire process of SaaS service provision—including consultation, selection, payment, authorization, and implementation—is completed online, resulting in rapid response, short response cycles, and a good customer experience. Subsequent service upgrades and maintenance are all completed online, saving significant implementation costs and shortening after-sales integration and testing timelines.

[0080] Based on the above description in this specification, those skilled in the art will also understand that the terms used, such as "upper" and "lower," which indicate orientation or positional relationship, are based on the orientation or positional relationship shown in the accompanying drawings of this specification. They are only for the purpose of facilitating the explanation of the present application and simplifying the description, and do not imply that the device or element involved must have the specific orientation, or be constructed and operated in a specific orientation. Therefore, the above-mentioned orientation or positional relationship terms should not be understood or interpreted as a limitation on the present application.

[0081] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0082] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method for providing SaaS services based on automatic authorization, executed by the server side, characterized in that, include: The functionality of the SaaS service is divided into at least one MVP module, where each MVP module contains at least one SaaS service function; Perform pre-authorization processing on each MVP module to configure the pre-authorization limits for each MVP module; Receive information about one or more MVP modules purchased by a user, and determine the pre-licensing limit corresponding to the MVP module based on the information about the MVP modules purchased by the user; The pre-authorization process for each MVP module to configure the pre-authorization limits for each MVP module includes: obtaining the permission information corresponding to each MVP module based on the association between each MVP module and permission information; Based on the permission information corresponding to the MVP module, pre-authorization processing is performed on the MVP module to configure the pre-authorization limit of the MVP module; Based on the pre-authorization limit corresponding to the MVP module purchased by the user, generate the user's permission token and send the permission token to the client; The method further includes obtaining relevant information about the user, wherein generating the user's permission token based on the pre-authorization limit corresponding to the MVP module purchased by the user includes: generating the user's permission token based on the pre-authorization limit corresponding to the MVP module purchased by the user and the user's relevant information; The relevant information of the user includes the user's authentication information, payment information, deployment mode, and access mode; The association between each MVP module and permission information can be provided in the form of a permission list, which lists various permissions corresponding to each MVP module, including access permissions to the external interfaces of the SaaS function and the internal interfaces of other MVP modules of the SaaS function.

2. The method for providing SaaS services based on automatic authorization according to claim 1, characterized in that, The method further includes: combining the MVP modules into at least one MVP module combination based on the correlation between the MVP modules, wherein each MVP module combination contains at least one MVP module.

3. The method for providing SaaS services based on automatic authorization according to claim 2, characterized in that, The method also includes setting description information, pricing information, and application scenario information for each MVP module and each combination of MVP modules.

4. The method for providing SaaS services based on automatic authorization according to claim 2 or 3, characterized in that, The pre-license limits of the MVP module combination are determined based on the pre-license limits of the MVP modules included in the MVP module combination.

5. The method for providing SaaS services based on automatic authorization according to claim 1, characterized in that, The user's deployment mode includes cloud deployment mode and private deployment mode.

6. The method for providing SaaS services based on automatic authorization according to claim 5, characterized in that, When the user's deployment mode is the private deployment mode, the permission token is stored as a token file for the client to download.

7. An apparatus for providing SaaS services based on automatic authorization, comprising a memory and a processor, wherein the memory stores computer-executable instructions, characterized in that, When the computer-executable instructions are executed by the processor, they implement the method for providing SaaS services based on automatic authorization according to any one of claims 1 to 6.

Images