Subscription order generation for cloud services

• US 9,619,540 B2
• Filed: 03/15/2013
• Issued: 04/11/2017
• Est. Priority Date: 09/07/2012
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Prathipati, Anjani Kalyan, Chatterjee, Ramkrishna, Vasudevan, Ramesh, Arun, Gopalan
• Primary Examiner(s): Nguyen, Angela
• Application Number:
  US13/841,994
• Publication Number:
  US 20140143083A1
• Time in Patent Office: 1,488 Days
• Field of Search: None
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/283 Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06Q 10/06315 Needs-based resource requirements planning or analysis
• CPC Class Codes: G06Q 10/0633 Workflow analysis
• CPC Class Codes: G06Q 30/0633 Lists, e.g. purchase orders, compilation or processing
• CPC Class Codes: G06Q 30/0635 Processing of requisition or of purchase orders
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/0686 Additional information in the notification, e.g. enhancement of specific meta-data
• CPC Class Codes: H04L 41/50 Network service management, e.g. ensuring proper service fulfilment according to agreements
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 41/5064 Customer relationship management
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 47/70 : Admission control; Resource allocation
• CPC Class Codes: H04L 63/10 : for controlling access to devices or network resources
• CPC Class Codes: H04L 63/20 : for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A framework for managing service components associated with a service subscribed to by a customer in a cloud infrastructure system is disclosed. The framework generates a subscription order for the customer based upon receiving a selection of service components from the customer. The framework identifies resource metrics associated with the service components selected by the customer and generates a subscription order for the customer based upon the service components and the resource metrics.

Claims

1. A method comprising:

accessing, by a computing infrastructure system, subscription information related to a subscription order identifying a service from a set of services provided by the computing infrastructure system, the computing infrastructure system comprising one or more computing devices;

mapping, by a computing device from the one or more computing devices, the service to a set of service components associated with the service to generate a service component dependence schema, the set of service components identifying at least one mandatory service component and one or more dependent service components that depend on the mandatory service component;

displaying, by the computing device, the service component dependence schema to a customer accessing the service provided by the computing infrastructure system;

receiving, by the computing device, a selection of at least one dependent service component of the one or more dependent service components in the service component dependence schema from the customer;

identifying, by the computing device, a resource metric for the selected dependent service component, the resource metric comprising an amount of a resource to be assigned to the selected dependent service component;

determining, by the computing device, a set of rules that correlate the resource metric of the selected dependent service component to a corresponding resource metric of the mandatory service component;

updating, by the computing device, the subscription information related to the subscription order for the customer to include at least the mandatory service component and the selected dependent service component; and

provisioning, by the computing device, resources for the selected dependent service component and the mandatory service component based at least in part on the set of rules.

2. The method of claim 1 wherein mapping the service to the set of service components comprises identifying a root service component for the service.

3. The method of claim 1 wherein displaying the service component dependence schema comprises displaying the set of service components for the service to the customer, via one or more front-end interfaces provided by the computing infrastructure system.

4. The method of claim 1 further comprising receiving a selection to add or remove the one or more dependent service components identified for the service, from the customer.

5. The method of claim 1, wherein:

a first resource metric associated with a first service component of the set of service components comprises a number of users associated with a first service provided by the first service component;

a second resource metric associated with a second service component of the set of service components comprises amount of storage associated with a second service provided by the second service component;

the set of rules specify an amount of a resource to be assigned to the selected service component based at least in part on an amount of the resource assigned to the mandatory service component;

the set of rules specify a percentage of a number of users to be assigned to the selected service component based at least in part on a number of users assigned to the mandatory service component;

the set of rules correlate a change in the resource metric associated with the selected dependent service component to a change in the corresponding resource metric of the mandatory service component;

the set of rules correlate a duration of a service component to a duration of a service component from the set of service components that is dependent on the service component, the duration of the service component comprising an activation start date and an activation end date of the service component; and

the set of rules correlate a change in a renewal policy of a service component to a change in the renewal policy of a service component from the set of service components that is dependent on the service component.

6. The method of claim 2 wherein the at least one mandatory service component is automatically included in the service component dependence schema when the root component is included in the service component dependence schema.

7. A system comprising:

one or more computing devices configurable to provide one or more services;

a memory configurable to access subscription information related to a subscription order identifying a service from a set of services; and

wherein a computing device from the one or more computing devices is configurable to;

map the service to a set of service components associated with the service to generate a service component dependence schema, the set of service components identifying at least one mandatory service component and one or more dependent service components that depend on the mandatory service component;

display the service component dependence schema to a customer accessing the service;

receive a selection of at least one dependent service component of the one or more dependent service components in the service component dependence schema from the customer;

identify a resource metric for the selected dependent component, the resource metric comprising an amount of a resource to be assigned to the selected dependent service component;

determine a set of rules that correlate the resource metric of the selected dependent service component to a corresponding resource metric of the mandatory service component;

update the subscription information related to the subscription order for the customer to include at least the mandatory service component and the selected dependent service component; and

provision resources for the selected dependent service component and the mandatory service component based at least in part on the set of rules.

8. The system of claim 7 wherein the computing device is configured to map the service to the set of service components by identifying a root component for the service.

9. The system of claim 7 wherein the resource metric comprises at least one of a number of users or the amount of storage associated with the set of services provided by the set of service components.

10. The system of claim 7 wherein the computing device is configured to display the service component dependence schema by displaying the set of service components for the service to the customer, via one or more front-end interfaces provided by the computing infrastructure system.

11. The system of claim 8 wherein the computing device is configured to automatically include the at least one mandatory service component in the service component dependence schema when the root component is included in the service component dependence schema.

12. A computer-readable memory storing a plurality of instructions executable by one or more processors, the plurality of instructions comprising:

instructions that cause at least one processor from the one or more processors to access subscription information related to a subscription order identifying a service from a set of services provided by the computing infrastructure system, the computing infrastructure system comprising one or more computing devices;

instructions that cause at least one processor from the one or more processors to map the service to a set of service components associated with the service to generate a service component dependence schema, the set of service components identifying at least one mandatory service component and one or more dependent service components that depend on the mandatory service component;

instructions that cause at least one processor from the one or more processors to display the service component dependence schema to a customer accessing the service provided by the computing infrastructure system;

instructions that cause at least one processor from the one or more processors to receive a selection of at least one dependent service component of the one or more dependent service components in the service component dependence schema from the customer;

instructions that cause at least one processor from the one or more processors to identify a resource metric for the selected dependent component, the resource metric comprising an amount of a resource to be assigned to the selected dependent service component;

instructions that cause at least one processor from the one or more processors to determine a set of rules that correlate the resource metric of the selected dependent service component to a corresponding resource metric of the mandatory service component;

instructions that cause at least one processor from the one or more processors to update the subscription information related to the subscription order for the customer to include at least the mandatory service component and the selected dependent service component; and

instructions that cause at least one processor from the one or more processors to provision resources for the selected dependent service component and the mandatory service component based at least in part on the set of rules.

13. The computer-readable memory of claim 12 wherein the instructions that cause at least one processor from the one or more processors to map the service to the set of service components comprises instructions to identify a root service component for the service.

14. The computer-readable memory of claim 12 wherein the instructions include automatically including at least one mandatory service component in the service component dependence schema when the root component is included in the service component dependence schema.

15. The computer-readable memory of claim 12 wherein the instructions that cause at least one processor from the one or more processors to display the service component dependence schema comprises instructions to display the set of service components for the service to the customer, via one or more front-end interfaces provided by the computing infrastructure system.