Method for applying cloud service resources based on cloud application market and process platform
By integrating the cloud application marketplace and the process platform, a unified entry point for applying for cloud service resources is provided, which solves the problem of scattered subscription pages in private clouds, improves user experience and operational efficiency, and simplifies resource management.
Patent Information
- Application Number
- CN202411144763.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-20
- Publication Date
- 2024-11-15
AI Technical Summary
In private clouds, the subscription pages and application processes for various cloud services are scattered, resulting in inconsistent interface styles, high operational and maintenance difficulties, and complex resource management, which is especially evident when services are provided by multiple software vendors.
By integrating service subscription forms through the cloud application marketplace and process platform, a unified service application portal is provided. The process platform is used for unified management of approval processes, and cloud service resource management APIs are called for operations.
It has enabled a unified entry point and process for cloud service resource applications, improved user experience, simplified operation and maintenance management, reduced operation and maintenance difficulty and resource management costs, and improved the efficiency of resource changes.
Smart Images

Figure CN118964034A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to cloud computing, and in particular to a method for applying for cloud service resources based on a cloud application market and a process middle platform. Background Art
[0002] With the rapid development of information technology, cloud computing, as a new IT resource delivery model, is being widely used around the world. In the field of cloud computing, cloud services are usually provided in the form of IaaS (Infrastructure as a Service), PaaS (Platform as a Service) and SaaS (Software as a Service). Among them, IaaS provides virtualized computing resources, including virtual machines (VMs), storage, networks and operating systems. It is a delivery model that provides infrastructure as a service to users; PaaS provides a software tool platform for users to develop, test, deploy and manage applications. It is a delivery model that provides the platform as a service to users; SaaS is a delivery model that provides applications as a service to users. In the SaaS model, users do not need to purchase and maintain applications, but only need to access applications through the network to use them.
[0003] When a service applicant subscribes to a service, the current mainstream cloud vendors provide a service subscription page and application process for each service. The service applicant can enter the subscription page of the service to apply for resource creation, resource modification, resource deletion, etc. Take a certain type of database service as an example: there is an entrance to this type of database service on the cloud portal; after entering the database resource subscription page through the service entrance, you can apply to create, modify, and delete this type of database.
[0004] Each service provides its own service subscription page, which gives each service greater freedom and allows them to freely define the style, style and application process of the service subscription page. However, this approach also has certain disadvantages, especially in private clouds. This is mainly because the operating models of private clouds and public clouds are different: when applying for public cloud services, generally, you only need to pre-deposit enough money to automatically change resources; when applying for private cloud services, the overall resources of the private cloud are uniformly planned by the private cloud manager and operation and maintenance personnel, and resources are generally allocated in the form of process approval. Therefore, the scattered subscription entrances will lead to the following problems: First, subscriptions to different services usually have the same process, and each service should not implement a set of processes on its own; second, the subscription page is implemented by each service itself, and there may be inconsistencies in the interface style, resulting in a poor experience; third, the lack of a unified service application entrance increases the difficulty of operation and maintenance from the perspective of unified operation and maintenance; in addition, each service is responsible for its own subscription resource management, and additional manpower and material resources are required to summarize and allocate all service resource usage. Especially in the process of building a private cloud, since private clouds are usually provided with different services by multiple software vendors, problems such as inconsistent styles of service subscription pages, inconsistent subscription processes, difficulty in operation and maintenance, and difficulty in resource management are particularly obvious. Summary of the invention
[0005] In order to solve the above technical problems, the present invention provides a method for applying for cloud service resources based on a cloud application market and a process middle platform, the method comprising: Step S1, receiving a subscription application for a cloud service from a service applicant through the cloud application market, where the application type includes creating resources, modifying resources or deleting resources. The cloud application market integrates the process middle platform and implements the service subscription form of each cloud service, where the service subscription form includes the resource operation type, service specification and contact information for creating, modifying and deleting service resources. When the service applicant creates, modifies or deletes resources, he logs in to the cloud application market, selects the corresponding cloud service in the cloud application market, fills in the subscription form of the cloud service and submits the application; Step S2, the cloud application market calls the approval process initiation API provided by the process center, and uses the filled content of the service subscription form as an API parameter to send the application to the process center of the process center for approval; Step S3: The process center presets the approval process model for creating, modifying, and deleting resources that is common to all services. After receiving the request to initiate the approval process API, the process center notifies the cloud system administrator to enter the process center of the process center for approval, and presents the resource operation type and service specifications in the API to the cloud system administrator through a page. After reviewing, the cloud system administrator agrees or rejects the application and returns the approval result to the cloud application market. Step S4: The cloud application market receives the resource application approval result returned by the process center. When the approval result is approval, the cloud application market calls the resource management API provided by the applied service according to the request type of the service subscription application, and uses the resource operation type and service specification filled in the service subscription form as API parameters to pass the API request to the cloud service. Step S5, the cloud service receives the resource management API request initiated by the cloud application market, and performs corresponding operations according to the API parameters in the resource management API request; the corresponding operations include: when the resource operation type is to create a resource, the resource share applied for by the user is reserved; when the resource operation type is to modify a resource, the resource share reserved for the user is modified to the resource share after the application change; when the resource operation type is to delete a resource, all resources reserved for the user are released; Step S6, after the cloud service completes the operation, it returns the result of the operation to the cloud application market through the resource management API. The cloud application market displays the execution result of the application to the service applicant and notifies the service applicant via SMS or email according to the contact information filled in the service subscription form.
[0006] Compared with the prior art, the present invention has the following beneficial effects: 1. The present invention discloses a method for applying for cloud service resources based on a cloud application market and a process middle platform. The method requires each service to use the cloud application market as a unified service application portal, and provide online activation and change capabilities for various types of services such as cloud platform infrastructure resources (IaaS) and middle platform services (PaaS), business applications (SaaS), etc. in a self-service form, to ensure consistency of user experience and improve user satisfaction.
[0007] 2. The present invention requires that each service use the cloud application market for resource creation, modification, deletion and other operations, and use a unified process model to ensure the consistency of approval operations by each service administrator, thereby speeding up the response speed, shortening the service change cycle, and improving the efficiency of service changes.
[0008] 3. The present invention requires that each service use the cloud application market as a unified entrance for resource creation, modification, deletion and other operations, which is convenient for operation and maintenance personnel to maintain the system, while reducing the technical capability requirements for operation and maintenance management, and is also convenient for auditors to audit service resource allocation operations.
[0009] 4. Apply for and distribute resources for various services through the cloud application market, which facilitates the unified management and statistics of cloud software and hardware resources, and enables real-time monitoring of cloud resource usage. When cloud resource surplus is insufficient, it can be discovered in time and corresponding resource expansion can be carried out.
[0010] 5. The present invention requires that each service use a unified process platform for resource creation, modification, deletion and other operations. Each service does not need to repeatedly build process-related capabilities, thereby reducing service construction costs and resource requirements.
[0011] 6. From the perspective of cloud service developers and cloud operators, the cloud application market is an excellent channel and window for application promotion and service monetization. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Figure 1 It is a flow chart of a method for applying for cloud service resources based on a cloud application market and a process middle platform in an embodiment of the present invention; Figure 2 This is a use case diagram of a method for applying for cloud service resources based on a cloud application market and a process middle platform in an embodiment of the present invention. DETAILED DESCRIPTION
[0013] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms, and the present disclosure should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.
[0014] Figure 1 The present invention is a flowchart of a method for applying for cloud service resources based on a cloud application market and a process middle platform in an embodiment of the present invention. Figure 2 This is a use case diagram of a method for applying for cloud service resources based on a cloud application market and a process middle platform in an embodiment of the present invention. Figure 1 and Figure 2 The method of the embodiment of the present invention is described. Figure 1 As shown, the method includes: Step S1, receiving a service subscription application for a certain cloud service from a service applicant through the cloud application market, where the application type includes creating resources, modifying resources or deleting resources. The cloud application market integrates the process middle platform and implements the service subscription form of each cloud service, where the service subscription form contains information such as resource operation types such as creating, modifying, and deleting service resources, service specifications, and contact information; when the service applicant creates, modifies, or deletes resources, he logs in to the cloud application market, selects the corresponding cloud service in the cloud application market, fills in the subscription form of the cloud service, and submits the application.
[0015] According to the technical solution of the embodiment of the present invention, the cloud application market is integrated with the process middle platform and the service subscription form of each cloud service is implemented. The application request of the service applicant is received through the cloud application market, instead of each cloud service independently providing a subscription form. This can avoid the confusion caused by the inconsistency of the application pages and processes of each service resource, thereby improving the response speed, shortening the service resource change cycle, and improving the efficiency of service resource changes.
[0016] In step S2, the cloud application market calls the application programming interface (API) for initiating the approval process provided by the process center, and uses the filled-in content of the service subscription form as an API parameter to send the application to the process center of the process center for approval.
[0017] Step S3, the process center presets the approval process model for creating, modifying, and deleting resources that is common to all services; after receiving the request to initiate the approval process API, the process center notifies the cloud system administrator to enter the process center of the process center for approval, and presents the resource operation type and service specifications and other parameters in the API to the cloud system administrator through a page; the cloud system administrator approves or rejects the application after review, and returns the approval result to the cloud application market.
[0018] In step S4, the cloud application market receives the resource application approval result returned by the process center. When the approval result is agreed, the cloud application market calls the resource management API provided by the applied service according to the request type of the service subscription application, and uses the resource operation type, service specifications and other information filled in the service subscription form as API parameters, and passes the API request to the cloud service.
[0019] Step S5, the cloud service receives the resource management API request initiated by the cloud application market, and performs corresponding operations according to the API parameters in the resource management API request. The corresponding operations include: when the resource operation type is to create resources, it means that the user applies for new service resources, and the resource share applied for needs to be reserved for the user, so as to achieve the purpose of creating resources; when the resource operation type is to modify resources, it means that the user has applied for the cloud service resource before, and the existing resource share is applied for change this time, and the resource share reserved for the user needs to be modified to the resource share after the application change, so as to achieve the purpose of modifying resources for the service applicant; when the resource operation type is to delete resources, it means that the user has applied for the cloud service resource before, and the existing resource share is applied for deletion this time, and all resources reserved for the user need to be released, so as to achieve the purpose of deleting resources for the service applicant.
[0020] Step S6, after the cloud service completes the operation, it returns the result of the operation to the cloud application market through the resource management API. The cloud application market displays the execution result of the application to the service applicant and notifies the service applicant through SMS, email and other methods according to the contact information filled in the service subscription form.
[0021] The above step S1 mentioned that the cloud application market integrates the process middle platform and implements the service subscription form of each cloud service. When the service applicant creates, modifies or deletes resources, he logs in to the cloud application market, selects the corresponding cloud service in the cloud application market, enters the service subscription form of the cloud service, fills in information such as resource operation type and service specifications, and submits the application. This is further described in detail below.
[0022] In one embodiment, the cloud application market is integrated with the process platform, and the approval process is initiated and the process approval result is received through the process platform. The cloud application market can also be integrated with the managed cloud service to implement resource management of the cloud service by implementing its service subscription form and calling the resource management API. The service subscription form and resource management API include: 1. Create a service subscription form and resource creation API for service resources; 2. Modify the service subscription form and resource modification API of service resources; 3. Delete the service subscription form and resource deletion API for service resources.
[0023] Accordingly, each service subscription form can contain the following information: 1. Use the resource creation form to create service resources, including tenant / user information (read-only), applied resource quota, contact information, etc.; 2. Use the resource modification form to modify service resources, including tenant / user information (read-only), allocated resource quotas (read-only), new resource quotas, contact information, etc.; 3. Use the resource deletion form to delete service resources, including tenant / user information (read-only), allocated resource quota (read-only), contact information, etc.
[0024] The specifications of cloud services vary according to the delivery type, for example: 1. Cloud services are IaaS services, and specifications are resource combinations at the IaaS level. Taking virtual machine services as an example, specifications include information such as CPU type, number of CPU cores, memory size, disk type and size, etc. 2. Cloud services are PaaS-type services, and specifications are resource combinations at the PaaS level. Taking cloud database services as an example, specifications include database type, number of CPU cores, memory size, storage size, data throughput, whether master-slave deployment is required, and other information. 3. Cloud service is a SaaS-type service, and the specification is a resource combination at the SaaS level. Taking cloud enterprise resource planning (ERP) service as an example, the specification includes the name of the ERP module to be subscribed, the number of users and other information.
[0025] In one embodiment, in the above step S1, when a service applicant creates, modifies or deletes a resource, he logs into the cloud application market, selects a corresponding cloud service in the cloud application market, enters the service subscription form of the cloud service, fills in information such as the operation type and service specifications, and submits the application. The preconditions include: 1. Service applicants must register in the cloud application market in advance and be able to log in to the cloud application market; 2. Service applicants must be granted sufficient permissions to submit applications for creation, modification, deletion, and other operations of cloud service resources in the cloud application market.
[0026] In one embodiment, in the above step S3, the cloud application market receives the approval result of the process center, and further includes: When the approval result is a rejection of the application, the cloud application market will notify the service applicant of the rejection of the request through SMS, email, etc. based on the contact information filled in the application form.
[0027] Step S4, the cloud application market receives the approval result of the process center. When the approval result is approval, the cloud application market calls the resource management API provided by the applied cloud service according to the request type of the service subscription application, and uses the resource operation type, service specification and other information filled in the service subscription form as API parameters, and passes the API request to the cloud service, which also includes: The cloud application market defines a standard resource management API abstract interface. In addition to standard parameters such as resource operation types, the API parameters also reserve dynamic data structure parameters to adapt to the different service specifications of each cloud service. All cloud services that manage service subscriptions through the cloud application market must be implemented accordingly according to the standard abstract interface definition.
[0028] In one embodiment, in the above step S5, the cloud service receives the resource management API request initiated by the cloud application market, and performs corresponding operations according to the API request type and parameters. The cloud application market is responsible for initiating an application to the cloud service to create, modify or delete resources, and the cloud service performs the specific operations. The subscription interface of the cloud service itself should be blocked or deleted to ensure that the cloud application market is the only entrance.
[0029] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.
[0030] Although the present invention has been described according to a limited number of embodiments, it will be apparent to those skilled in the art, with the benefit of the above description, that other embodiments may be envisioned within the scope of the invention thus described. In addition, it should be noted that the language used in this specification is primarily selected for readability and instructional purposes, rather than for the purpose of explaining or limiting the subject matter of the present invention.
Claims
1. A method for applying for cloud service resources based on a cloud application market and a process middle platform, It is characterized in that include: Step S1, receiving a subscription application for a cloud service from a service applicant through the cloud application market, where the application type includes creating resources, modifying resources or deleting resources. The cloud application market integrates the process middle platform and implements the service subscription form of each cloud service, where the service subscription form includes the resource operation type, service specification and contact information for creating, modifying and deleting service resources. When the service applicant creates, modifies or deletes resources, he logs in to the cloud application market, selects the corresponding cloud service in the cloud application market, fills in the subscription form of the cloud service and submits the application; Step S2, the cloud application market calls the approval process initiation API provided by the process center, and uses the filled content of the service subscription form as an API parameter to send the application to the process center of the process center for approval; Step S3: The process center presets the approval process model for creating, modifying, and deleting resources that is common to all services. After receiving the request to initiate the approval process API, the process center notifies the cloud system administrator to enter the process center of the process center for approval, and presents the resource operation type and service specifications in the API to the cloud system administrator through a page. After reviewing, the cloud system administrator agrees or rejects the application and returns the approval result to the cloud application market. Step S4: The cloud application market receives the resource application approval result returned by the process center. When the approval result is approval, the cloud application market calls the resource management API provided by the applied service according to the request type of the service subscription application, and uses the resource operation type and service specification filled in the service subscription form as API parameters to pass the API request to the cloud service. Step S5, the cloud service receives the resource management API request initiated by the cloud application market, and performs corresponding operations according to the API parameters in the resource management API request; the corresponding operations include: when the resource operation type is to create a resource, the resource share applied for by the user is reserved; When the resource operation type is to modify resources, the resource share reserved for the user will be modified to the resource share after the change application; when the resource operation type is to delete resources, all resources reserved for the user will be released; Step S6, after the cloud service completes the operation, it returns the result of the operation to the cloud application market through the resource management API. The cloud application market displays the execution result of the application to the service applicant and notifies the service applicant via SMS or email according to the contact information filled in the service subscription form.
2. The method for applying for cloud service resources based on the cloud application market and process platform according to claim 1, It is characterized in that The cloud application market is integrated with the process middle platform, which initiates the service resource approval process and receives the approval results through the process middle platform. The cloud application market is also integrated with various cloud services to manage cloud service resources by implementing the service subscription form of the cloud service and calling the resource management API provided by the cloud service.
3. The method for applying for cloud service resources based on the cloud application market and process middle platform according to claim 1, It is characterized in that Different types of cloud services have different service specifications: In the case of IaaS-type cloud services, the specifications are resource combinations at the IaaS level; In the case where the cloud service is a PaaS-type service, the specification is the resource combination at the PaaS level; When the cloud service is a SaaS-type service, the specification is the resource combination at the SaaS level.
4. The method for applying for cloud service resources based on the cloud application market and process middle platform according to claim 1, It is characterized in that Step S4, the cloud application market receives the resource application approval result returned by the process center. When the approval result is approval, the cloud application market calls the resource management API provided by the applied service according to the request type of the service subscription application, and uses the resource operation type and service specification filled in the service subscription form as API parameters to pass the API request to the cloud service, which also includes: The cloud application market defines a standard resource management API abstract interface. In addition to the resource operation type, service specifications and contact information, the API parameters also reserve dynamic data structure parameters to adapt to the different service specifications of each cloud service. All cloud services that manage service subscriptions through the cloud application market are implemented accordingly according to the standard abstract interface definition.
5. The method for applying for cloud service resources based on the cloud application market and process middle platform according to claim 1, It is characterized in that In the above step S5, the cloud service receives the resource management API request initiated by the cloud application market, and performs corresponding operations according to the API parameters in the resource management API request. The cloud application market initiates an application to create, modify or delete resources to the cloud service, and the cloud service executes the operation. The subscription interface of the cloud service itself is blocked or deleted. The cloud application market is the only entrance to initiate applications to the cloud service.
