TWI631519B - Scalable multi-dimensional service strategy management system - Google Patents

Abstract

The invention provides a scalable multi-dimensional service policy management system. The aforementioned system includes a server application layer, an order management and control module, a service management and control module, and a service strategy management and control module. The aforementioned server application layer is used to receive service requests from user devices held by external users. The aforementioned service policy management and control module configures a cloud service corresponding to a service request according to a service policy management model. Among them, the service policy management model further includes a multi-level data model of service policies, policy rules, and rule descriptions. Service policies define the cloud services that users can apply for, policy rules define the cloud service management model, and rules are described as an attribute item. Correspondence with the value.

Description

Scalable multi-dimensional service strategy management system

The invention relates to a cloud service system, in particular to a cloud service system managed through a scalable multi-dimensional service strategy.

The current cloud service system considers the convenience of operation, and generally provides a single service and a single specification of cloud services to users. However, there are many user requirements and types. Therefore, in actual operation, it is necessary to provide customers with different categories and attributes. List of customized services and project specifications.

In order to achieve the above-mentioned goals, the current cloud service providers are mostly customized by engineers for each customer. When the number of users gradually increases, the aforementioned work mode will cause a great workload for the cloud service providers.

In summary, how to provide a cloud service system that can be built automatically to solve the aforementioned problems is a technical problem that needs to be solved urgently in this field.

In order to solve the problem of previous disclosure, the object of the present invention is to provide a technical solution for extended multi-dimensional service policy management.

To achieve the above object, the present invention proposes a scalable multi-dimensional service policy management system. The aforementioned system includes a server application layer, an order management and control module, a service management and control module, and And service strategy control module. The aforementioned server application layer is used to receive service requests from user devices held by external users. The aforementioned order management and control module and service management and control module are connected to the server application layer. The aforementioned service policy management and control module is connected to the order management and control module and the service management and control module. The service policy management and control module configures the cloud service corresponding to the service request according to the service policy management model. Among them, the service policy management model further includes a multi-level data model of service policies, policy rules, and rule descriptions. Service policies define the cloud services that users can apply for, policy rules define the cloud service management model, and rules are described as an attribute item. Correspondence with the value.

In summary, the extensible multi-dimensional service policy management system of the present invention configures corresponding cloud services through the service policy management model, which can effectively improve the automation degree of the cloud service system.

1‧‧‧ Scalable Multi-Dimensional Service Strategy Management System

11‧‧‧Server Application Layer

12‧‧‧Order Management Module

13‧‧‧Service Management Module

14‧‧‧Service Strategy Management Module

2‧‧‧ users

21‧‧‧User Group

22‧‧‧user device

3‧‧‧Service Strategy Management Model

31‧‧‧Service Strategy

31A‧‧‧General Policy

32‧‧‧Strategic Rules

32A‧‧‧Subsidiary Strategy Rules

33‧‧‧ Rule description

4‧‧‧ Cloud Service

41‧‧‧ Cloud Service Category

FIG. 1 is a system block diagram of an extensible multi-dimensional service policy management system according to an embodiment of the present invention.

FIG. 2 is a schematic diagram of a data model of the service policy management mechanism of the present invention.

FIG. 3 is a corresponding relationship diagram between users and service strategies of the present invention.

FIG. 4 is a correspondence diagram of policy rules and services according to the present invention.

5 to 6 are schematic diagrams of preset scenarios of the service strategy data model of the present invention.

FIG. 7 is a flowchart of a service inquiry performed by a user of the present invention.

FIG. 8 is a flowchart of querying service specifications by a user of the present invention.

FIG. 9 is a flowchart of a service application by a user of the present invention.

FIG. 10 is a flowchart of a service for renting back a user of the present invention.

The following describes specific embodiments to illustrate the implementation of the present invention, but it is not intended to limit the scope of the present invention.

Please refer to FIG. 1, which is a system block diagram of an extensible multi-dimensional service policy management system 1 according to an embodiment of the present invention. The aforementioned system includes a server application layer 11, an order management and control module 12, a service management and control module 13, and a service strategy management and control module 14. The server application layer 11 is used to receive a service request from a user device 22 held by an external user 2. The aforementioned order management and control module 12 and service management and control module 13 are connected to the server application layer 11. The aforementioned service policy management and control module 14 is connected to the order management and control module 12 and the service management and control module 13. The service policy management and control module 14 configures the cloud service corresponding to the service request according to the service policy management model 3 (FIG. 2). Among them, the service policy management model 3 further includes a multi-level data model of the service policy 31 (Figure 2), the policy rule 32 (Figure 2), and the rule description 33 (Figure 2). The service policy 31 defines the user 2 can apply for Cloud service 4 (Figure 4), policy rule 32 defines the management mode of cloud service 4, and rule description 33 is the correspondence between an attribute item and a value.

In another embodiment, the aforementioned service policy 31 further includes a user 2 service policy 31, a group service policy 31, and a service policy general rule 31A (FIG. 3). In another embodiment, when the aforementioned user 2 service policy 31, group service policy 31, and service policy general rule 31A are established, the execution priority order is user 2 service policy 31, group service policy 31, and service policy. General Rule 31A.

In another embodiment, the aforementioned policy rule 32 and the cloud service 4 are associated one-to-one or one-to-many. In another embodiment, the aforementioned service policy 31 is a set of a plurality of policy rules 32. In another embodiment, the aforementioned policy rule 32 is a set of a plurality of rule descriptions 33.

In another embodiment, when the server application layer 11 receives a service request, The order management and control module 12 series releases the available cloud service 4 (Figure 4), and calls the service strategy management and control module 14 to check the acceptability of the cloud service 4. In another embodiment, the aforementioned order management and control module 12 further checks whether the cloud service 4 reaches the upper limit of acceptance to determine whether to provide an error message. In another embodiment, the aforementioned order management and control module 12 further checks whether the cloud service 4 reaches the acceptance lower limit quantity to determine whether to perform a rent-off operation.

In another embodiment, when the aforementioned server application layer 11 receives a service request, the service management and control module 13 serializes the available specifications of the cloud service 4 and calls the service policy management and control module 14 to check the availability of the specifications of the cloud service 4.

Please refer to FIG. 2 again, which is a schematic diagram of a data model of a service policy management mechanism. The data model of the service policy 31 management mechanism is a multi-level data structure that includes three entities: service policy 31, policy rule 32, and rule description 33. Service policy 31 is the main body of the data structure. It defines cloud service 4 that user 2 can apply for. It corresponds to multiple policy rules 32 below, which is a collection of policy rules 32. Policy rule 32 corresponds to cloud service 4 and defines this service. For the control method, each policy rule 32 will include more than one rule description 33; the rule description 33 is a correspondence between an attribute item and a value, and is used to describe the details of the control method.

Please refer to FIG. 3, which is a corresponding relationship diagram between the user 2 and the service policy 31 of the present invention. The user 2 and the service strategy 31 have a many-to-one correspondence relationship, and each user 2 obtains relevant information of the cloud service 4 through its corresponding service strategy 31. In addition, this case also defines a general service policy 31, which is called service policy general rule 31A. When user 2 does not have a corresponding service policy 31, this general rule is applied. If the user 2 management module supports the user group function, the service policy 31 may also be mapped to the user group 21. When user 2, group and general service policy 31 are established, their priority is: user 2 service policy 31, group service policy 31, service General Policy 31A. There are two ways to implement this: (1) apply only the service policies with high priority 31, (2) apply the policy rules 32 in order from low to high priority, if the rules conflict, the low priority part Will be overwritten.

Please refer to FIG. 4, which is a corresponding diagram of the policy rule 32 and the service of the present invention. The corresponding relationship between the policy rule 32 and the cloud service 4 is one-to-one or one-to-many. Each policy rule 32 must correspond to a cloud service 4 or a cloud service category 41. Cloud service 4 often has a subordinate relationship, of which the service that can exist independently is called "main service", and the attached service is called "sub service". If you want to formulate a policy rule 32 that is a sub-service for a specific main service, it is difficult to achieve it with a single policy rule 32. Therefore, in this case, the existing data structure of policy rule 32, and the corresponding relationship with other policy rules 32, is called "subordinate policy rule 32A", which is used to define the policy rule 32 of the sub-services of the main service.

The policy rule 32 corresponds to the cloud service 4, and the rule description 33 below is used to explain the management method corresponding to this (class) cloud service 4. Rule description 33 is a corresponding relationship between an attribute item and a value. The attribute item includes the following four categories: (1) admissibility, (2) the maximum number of acceptances, (3) the minimum number of acceptances, and (4) service specification restrictions. The service policy management and control module 14 performs service management and control according to the actions of the user 2 and the settings of the rule description 33. Because the rule description 33 has a simple structure and is easy to expand, if there is a new rule description 33 in the future, developers need only add new logical judgments to the service policy management and control module 14 without having to change the relevant data structure of the service policy 31. It has good scalability .

Please refer to FIG. 5 and FIG. 6, which are schematic diagrams of preset scenarios of the service strategy 31 data model of the present invention. In this scenario, general user 2 / user group 22 corresponds to service policy 31 / service policy general rule 31A, and can apply for virtual machine type A, virtual machine type B, virtual machine type C, and storage Storage space service. This case establishes a service policy 31 for user 2 and the underlying policy rules 32 correspond to virtual machine D-type and storage space services, respectively. Among them, the virtual machine D-type policy rule 32 adds the product acceptance upper limit and product acceptance lower limit rule description 33, and adds two subsidiary policy rules 32A, which prohibit the acceptance of two sub-services of CPU value-added and RAM value-added; in addition, This case adds specifications to the storage space service, and only allows user 2 to apply for a storage space service with a capacity below 200GB.

In the following, the extensible multi-dimensional service policy management system 1 is operated in a cloud system as an example. The order management module 12 of the extensible multi-dimensional service strategy management system 1 is responsible for the acceptance of orders by user 2; the service management module 13 is responsible for the management of cloud service 4. If user 2 wants to operate the cloud system, he must use the user device 22 sends a request to the server application layer 11, and then calls different modules according to the request type. After the service policy management module 14 is added, there is no need to make much changes. In this case, a set of internal interfaces is implemented in the service policy management and control module 14. When the user 2 sends a request, the order management and control module 12 and the service management and control module 13 will call the internal interface of the service policy management and control module 14 to perform strategy rule 32. verification. The actual process is slightly different depending on the execution actions, which are explained separately below.

Please refer to FIG. 7, which is a flowchart of service inquiry performed by user 2 of the present invention. After user 2 calls the server application layer 11 and sends a service query (S101), the service management and control module 13 will list all available services (S102), and then calls the service policy management and control module 14 to check the service " "Acceptability" (S104), after removing the services set as unacceptable, the service list is returned to the user device 22 (S105).

Please refer to FIG. 8, which is a flowchart of querying service specifications by user 2 of the present invention. After user 2 calls the server application layer 11 and sends the specification query (S201), the service manager The control module 13 will list the available specifications of the query service (S202), and then call the service policy management control module 14 to check the "specification availability" of the service (S203), remove the specifications that cannot be accepted, and then return the specification list to User interface of the user device 22 (S204).

Please refer to FIG. 9, which is a flowchart of service application by the user 2 of the present invention. After user 2 calls the server application layer 11 and submits a service application (S301), the order management and control module 12 first calls the service policy management and control module 14 to prepare to receive the required information for inspection (S302, S303). "Acceptability", "Specification availability", and then check the "Maximum number of acceptances" (S304 ~ S306) of the service. If the service meets the above verification, continue the order acceptance process (S307). , An error message is returned to the user device 22 (S308).

Please refer to FIG. 10, which is a flowchart of the service 2 renting back by the user 2 of the present invention. After user 2 calls the server application layer 11 and submits a cancellation request (S401), the order management and control module 12 will call the order management and control module 13 and the service strategy management and control module 14 to query the required information (S402 ~ S403). Check if the number of services under the "Lower Acceptance Number" is greater than the lower acceptance limit? If it is, then the order cancellation process is performed (S405); if the lower limit has been reached, an error message is returned to the user device 22 (S406).

The above detailed description is a specific description of a feasible embodiment of the present invention, but this embodiment is not intended to limit the patent scope of the present invention. Any equivalent implementation or change that does not depart from the technical spirit of the present invention should be included in Within the scope of the patent in this case.

Claims (8)

An extensible multi-dimensional service policy management system includes: a server application layer for receiving service requests from user devices held by external users; an order management and control module connected to the server application layer; and a service management and control module To connect to the server application layer; and a service policy management module to connect the order management module and the service management module, wherein the service policy management module configures the cloud service corresponding to the service request according to the service policy management model ; The service policy management model further includes a multi-level data model of service policies, policy rules, and rule descriptions. The service policy defines the cloud service that users can apply for, and the policy rule defines the management mode of the cloud service. The rule is described as a correspondence between an attribute item and a value. The service policy further includes a user service policy, a group service policy, and a service policy general rule, and the user service policy, the group service policy, and the service policy general rule. When created, execution priority is sequentially for the user Business strategy, the group service strategy, service strategy General. The extensible multi-dimensional service policy management system according to claim 1, wherein the policy rule is associated with the cloud service on a one-to-one or one-to-many basis. The scalable multi-dimensional service policy management system according to claim 1, wherein the service policy is a collection of a plurality of policy rules. The scalable multi-dimensional service policy management system according to claim 3, wherein the policy rule is a plurality of sets described by the rule. The extensible multi-dimensional service policy management system according to claim 1, wherein when the server application layer receives the service request, the order management module series outputs the cloud service that can be used, and calls the service policy management module Group to check the admissibility of the cloud service. The scalable multi-dimensional service policy management system according to claim 5, wherein the order management and control module further checks whether the cloud service reaches the acceptance limit number to determine whether to provide an error message. The scalable multi-dimensional service policy management system according to claim 5, wherein the order management and control module further checks whether the cloud service reaches the acceptance lower limit quantity to determine whether to perform a rent-off operation. The scalable multi-dimensional service policy management system as described in claim 1, wherein when the server application layer receives the service request, the service management module serializes the available specifications of the cloud service and calls the service policy management module To check the availability of the specifications of the cloud service.