TW201714136A - Service provisioning system with flexible provisioning process capable of automatically analyzing service demands and obtaining flow packaging blocks required for execution - Google Patents

Abstract

The invention provides a service provisioning system with a flexible provisioning process. A flexible provisioning process module provided in the service provisioning system is configured to analyze a service provisioning demand order to obtain a workflow category of the requested provisioning service and to configure a plurality of process packaging blocks required to be executed and an execution sequence of the process packaging blocks according to the workflow category so that a service physical resource layer is scheduled to provide the provisioning service requested by the service provisioning demand order. Accordingly, an automatic provisioning service is provided.

Description

Service supply system with flexible supply process

The invention relates to a service supply system, in particular to a service supply system with an elastic supply process.

In the current cloud service, because the user needs are different, and to provide customized services, the cloud service provider often needs to modify the content of the cloud service according to the service requirements of each user, for example, increasing the number of virtual machines. Add/delete specific functions, etc., and after modifying the service content, compile the modified service program to generate an executable program that can provide services.

Because the operating environment of the cloud industry is changeable, when the user has an urgent service modification request, or frequently requests for service modification, it often causes a serious workload for the cloud service provider. Therefore, in the case of frequent modification, the cloud service The provider provides a large amount of working time, labor costs, and system resources to meet the needs of the client.

In summary, how to provide a supply system that can analyze the needs of the user and automatically modify and set the service content is a technical problem that needs to be solved in the field.

In order to solve the problems disclosed above, the purpose of this case is to provide a service provisioning system that can analyze the service needs of users and flexibly set the supply process.

In order to achieve the above objectives, the present application proposes a service provisioning process with an elasticized supply process. The system, the flexible supply process module included in the service provisioning system is an analysis service supply demand order to know the workflow type of the requested supply service, and the plurality of executions required according to the workflow category The execution order of the process encapsulation block and the process encapsulation block is to dispatch the service entity resource layer to provide the service for the service request for the demand order.

In summary, the service provisioning system of the firm supplies the demand order through the analysis service and obtains the required process encapsulation block and its execution sequence, and automatically dispatches the service entity resource layer to provide the service request for the demand order. The provision of services can solve the technical dilemma of the prior art.

1‧‧‧Service Supply System

11‧‧‧User interface

12‧‧‧ Order Processing Module

13‧‧‧Flexible supply process module

131‧‧‧Process category control components

132‧‧‧Process step control components

133‧‧‧ process control components

134‧‧‧Supply parameter setting component

135‧‧‧ instruction components

14‧‧‧Service entity resource layer

2‧‧‧Database

FIG. 1 is a block diagram of a service supply system with an elasticized supply process in the present case.

FIG. 2 is a block diagram of the flexible supply and installation process module of the present invention.

FIG. 3 is a schematic diagram of the operation of an embodiment of the present invention.

The specific embodiments are described below to illustrate the embodiments of the invention, but are not intended to limit the scope of the invention.

Please refer to FIG. 1, which is a block diagram of a service supply system 1 having an elasticized supply process according to the present invention. The user interface 11 , the order processing module 12 , the flexible provisioning process module 13 , and the service entity resource layer 14 are sequentially connected. The internal block diagram of the foregoing elasticized supply flow module 13 is as shown in FIG. 2, and includes a process category control component 131, a process step management component 132, a secondary flow control component 133, a supply parameter setting component 134, and a command component. 135. The foregoing process step management component 132 is connected to the process category control component 131, respectively. The flow control component 133, the supply parameter setting component 134, and the command component 135.

The aforementioned interfaces, modules, components, etc. are software modules. The aforementioned software module can be implemented by ASP, C/C++/C#, JAVA, Python, PHP, Perl, etc., but the category of the programming language is not limited thereto.

The foregoing elasticized supply process module 13 analyzes the service supply demand order to know the workflow type of the requested supply service, and configures a plurality of process package blocks and process package areas to be executed according to the workflow category. The execution order of the blocks is to schedule the service entity resource layer 14 to provide the service for the service request for the demand order. The foregoing process package block is an executable package file, such as a Java Class file.

In one embodiment, the service provisioning system 1 of the present invention is applied to Infrastructure as a Service (IaaS). In this cloud service, the service provisioning system 1 of the present invention can provide a cloud service such as a virtual machine service, a firewall service, or a load balancer service, and in this embodiment, the service entity resource layer 14 is configured to be configured. The physical resource of the cloud service.

The client can select and submit the number of cloud services, specifications, and provisioning action status via the user interface 11. Next, the service provisioning system 1 transmits the user requirements to the order processing module 12 and retains its consumption records and certifications. The order processing module 12 converts the user requirements into service orders and transmits them to the flexible supply process module 13. The flexible provisioning process module 13 determines which loading procedure is initiated according to the service specification of the service supply demand order, and what kind of supply logic resources are assigned, and then transfers the order demand to the service entity resource layer 14 for installation. And the service entity resource layer 14 immediately returns the installation status to the elasticized supply process module 13, and then the elasticized supply process module 13 returns the result to the order processing module 12 and processes the order. Module 12 The results are reflected to the user interface 11 to provide a user instant query service.

Further, the process category management component 131 is used to obtain the process category of the selected service, the process step management component 132 is used to perform the work represented by the current step, and the secondary process management component 133 is used to organize all the processes included in the process category. In the order of the steps (ie, the foregoing process encapsulation block), the supply parameter setting component 134 is used to assign necessary parameters of the cloud service supply requirement, and the command component 135 is used to parse the supply service specification feature value of the order.

Based on the above organizational components, it is explained that the parameter construction process of the elasticized supply flow module 13 is as follows:

S101: Construct parameters of the process category management component 131.

S102: Construct parameters of the process step management component 132.

S103: Construct parameters of the secondary process management component 133.

The sub-flow S101 is based on the data supply library 2 setting the service provision specifications of the N kinds of cloud services that the service installation system 1 can provide after being online, where N is a positive integer and N 1. After the installation service specification is set, the plurality of supply action states provided by the service supply system 1 can be set in the database 2 according to the needs of the user terminal (for example: renting, changing, dismantling, suspending use, and multiplexing) ). The system 1 then sets the M process types that the service provisioning system 1 can provide according to the cloud service provisioning service specification and action state that has been successfully set in the database 2, where M is a positive integer and 1 M 5N.

The sub-flow S102 sets the X types of work to be executed in the supply parameter setting component 134, and then sets the corresponding X tasks in the database 2, where X is a positive integer and X 1. The instruction component 135 can write K kinds of instructions using the Reflection mechanism of the Java program to obtain the feature values of the supply service specification, where K is a positive integer and K 0, and set 5 kinds of logical operation elements, including: not equal to the operation element, equal to the operation element, include the operation element, the existence of the operation element, and the absence of the operation element. After the above work is completed, according to the cloud service content, the instruction, the logical operation element and the preset value are combined into a Y supply condition rule and set in the database 2, where Y is a positive integer and Y K , and set three kinds of boundary values, including: initial step, successful end, and error end. For each process category set in the process S101 of constructing the necessary parameters of the process category management component 131, all the process steps (process package blocks) are set in the database 2, including: 3 boundary values, 1 task, and J supply condition rules, where I X , J Y.

The sub-process S103 is to serialize all the processes defined in the sub-process S102 according to each process category set in the process S101 for constructing the necessary parameters of the process category management component 131, and according to the cloud service content and the condition value (True or False). The step (flow package block) is set in the database 2.

FIG. 3 is a sequential flow chart of an embodiment of the present invention, including the following processes:

S20: Receive service supply demand order.

S21: The process category management component 131 determines the process category to which the service belongs.

S22: The process step management component 132 determines the initial step of the service.

S23: The secondary process management component 133 determines the next step.

S231: The step of the process step management component 132 executing the boundary value type.

S232: The step of the process step management component 132 performing the task type.

S233: The process step management component 132 performs the step of loading the condition rule type.

S234: The supply parameter setting component 134 sets the supply parameter.

S235: The instruction component 135 executes the instruction program.

S24: The process step management component 132 determines that the feeding result is a successful end or an error end.

S25: The process step management component 132 verifies that the supply parameters are correct.

S251: The supply parameter setting component 134 calls the service entity resource layer 14.

S26: The process step management component 132 verifies whether the service entity resource layer 14 is successfully returned.

S27: The process step management component 132 verifies whether the execution result of the instruction is correct.

S28: Report the error message to the user interface 11.

After the service installation system 1 is online, the user terminal can submit the cloud service quantity and specification requirements through the user interface 11, and the process S20 passes the order processing module 12 to convert the foregoing quantity and specification requirements into a cloud service supply demand order and transmits The process module 13 is supplied to the elasticization. The flexible provisioning process module 13 interacts with the necessary parameters set by the parameter construction processes S101, S102, and S103, and can dynamically determine the cloud service supply process, and can instantly return the current supply state to the user interface. 11.

The decision process S21 is achieved by the process category management component 131. The process category management component 131 receives the cloud service supply demand order and parses the included service specification and action status information, and processes each process category set in the database 2 from the process S101 of the process parameter management component 131 necessary parameters. In the process, the only process category that meets the current cloud service provisioning needs is selected. If the process of obtaining the unique process category encounters an error, the process category management component 131 will execute the process S28 to report the error message to the user interface 11.

The decision process S22 is achieved by the process step management component 132. The process step management component 132 obtains the unique process category of the current cloud service provisioning requirement, and then obtains the flow process S102 of the necessary parameters of the process step management component 132 in all the process steps set by the database 2 belonging to the unique process category. The initial steps of the assembly process. If an error is encountered in the process of obtaining the initial step, the process step management component 132 will execute the process S28 to report the error message to User interface 11.

The decision process S23 is achieved by the secondary process management component 133. The secondary process management component 133 first obtains the next step of the installation process according to the initial steps of the current supply process and the association established in the database 2 by the process S103 of the necessary parameters of the secondary process management component 133. There are three types of supply process steps: boundary value, task, and supply condition rules. Each process step can only belong to one type. When the process control component 133 gets one step at a time, it will judge that this step belongs to Which type is transferred to the process step control component 132 to dynamically determine the service provider system 1 backend program that should be driven according to different types. After each time the necessary work of the current step is completed, the secondary process management component 133 will judge according to the execution result of the current step and obtain the next step. The secondary process management component 133 compares the provisioning service specification feature values presented by the cloud service provisioning demand order, and the process S102 of constructing the necessary parameters of the process step management component 132 in the feature value fields required to define the instructions, if The cloud service provisioning demand order lacks the feature value required by the process step management component 132, and an error end step is obtained, otherwise the successful end step is obtained. If an error is encountered during the acquisition step, the secondary process management component 133 will execute the process S28 to report an error message to the user interface 11.

The decision process S24 is achieved by the process step management component 132. When the current step belongs to the boundary value type, the process step management component 132 performs the process S231 to resolve whether the step is a successful end step or an error end step. If the step is a successful end step, the cloud service is successfully installed. This step is an error end step, indicating that the cloud service fails to be loaded, and the process step management component 132 will execute the process S28 to report an error message to the user interface 11.

The decision process S25 is achieved by the process step management component 132. When the current step belongs to the task type, the process step management component 132 executes the process S232 to drive the process. S234. The supply parameter setting component 134 parses the supply service specification feature value of the cloud service supply demand order, and dynamically assigns the supply logic resource corresponding to the hardware network and the computing infrastructure to complete the provisioning parameter setting. If the execution result of the supply parameter setting component 134 is transferred to the flow step management component 132, the supply parameter setting component 134 executes the flow S251 to call the service entity resource layer 14 downward, whereas the flow step management component 132 executes the flow S28. Report the error message to user interface 11.

The decision process S26 is achieved by the process step management component 132. If the execution result of the service entity resource layer 14 transmitted to the process step management component 132 is correct, it indicates that the current step has been successfully executed, so returning to the secondary process management component 133 to execute the decision process S23 again; and if the service entity resource layer 14 transmits If the execution result of the process step management component 132 is an error, the process step management component 132 will execute the process S28 to report the error message to the user interface 11.

The decision process S27 is achieved by the process step management component 132. When the current step belongs to the supply condition rule type, the process step management component 132 executes the process S233 to drive the process S235, and executes the necessary parameters of the build process step control component 132 according to the supply condition specification feature value of the cloud service supply demand order. The program of the program set in the flow S102. If the execution result of the instruction program is correct, it indicates that the current step has been successfully executed, so returning to the secondary process management component 133 to execute the decision process S23 again; and if the execution result of the instruction program is wrong, the process step management component 132 will report the error of the execution process S28. The message is to the user interface 11.

The detailed description of the preferred embodiments of the present invention is intended to be limited to the scope of the invention, and is not intended to limit the scope of the invention. The patent scope of this case.

13‧‧‧Flexible supply process module

131‧‧‧Process category control components

132‧‧‧Process step control components

133‧‧‧ process control components

134‧‧‧Supply parameter setting component

135‧‧‧ instruction components

2‧‧‧Database

Claims (10)

A service provisioning system with an elasticized supply process includes: an elasticized supply process module, an analysis service supply demand order to know the workflow type of the requested supply service, and configured according to the workflow category The plurality of process encapsulation blocks to be executed and the execution order of the process encapsulation blocks are arranged to dispatch the service entity resource layer to provide the service service requested by the service supply demand order. The service provisioning system of claim 1, wherein the process package block is an executable package file. The service provisioning system of claim 1, wherein the elasticized supply process module comprises: a process category management component, setting the workflow category to which the supply service belongs; and a process step management component, connecting the process category The control component, the process step control component is the initial step of setting the supply service; and the secondary process management component is connected to the process step control component, and the process control component is used to set the connection step of the connection service. The service loading system according to claim 3, further comprising: a parameter setting component for connecting the process step control component, the supply parameter setting component comprising a plurality of working categories; the command component connecting the process step managing component The instruction component includes a plurality of instructions for obtaining feature values of the provisioning service; wherein the work categories and the instructions further set a supply condition via a plurality of logical operation elements. The service provisioning system of claim 4, wherein the logical operation element comprises an operation element that is not equal to Equal to the operand, containing the operand, the existence of the operand, and the absence of the operand. The service provisioning system of claim 4, wherein the process step management component determines a result of the provisioning service, verifies whether the entity service resource is successfully returned, and verifies whether the instruction provided by the instruction component is correct. The service loading system of claim 1, wherein the workflow category is a supplied service and a provisioning action status thereof. The service loading system of claim 7, wherein the loading operation state further comprises at least one of a renting action state, a shift action state, a teardown action state, a pause use action state, and a multiplexing action state. The service provisioning system of claim 1, further comprising: a user interface, providing an external user to submit the request; and an order processing module connecting the user interface, the order processing module submitting the user terminal The demand is configured to supply the demand order for the service. The service provisioning system of claim 1, wherein the elasticized supply process module is electrically connected to the database to access the process package blocks.