JP6541694B2 - Providing subscriptions for services using existing subscriptions - Google Patents

Description

This application is related to the following applications, the entire contents of which are incorporated herein by reference for all purposes.

(1) US Provisional Application No. 61 / 698,413, filed on September 7, 2012 and entitled "Tenant Automation System" (2) filed on September 7, 2012, entitled "Service Development Infrastructure" US Provisional Application No. 61 / 698,459 (3) US Provisional Patent Application No. 61 / 785,299, filed March 14, 2013 and entitled "Cloud Infrastructure" (4) 2013 3 US Provisional Application No. 61 / 794,427 filed on May 15, entitled "Cloud Infrastructure" (5) US Provisional Application No. 61, filed on March 15, 2013, entitled "Service Association Model" This application claims the benefit of US Provisional Application No. 61 / 698,463, filed Sep. 7, 2012, entitled "Shared Identify Management Architecture", which is hereby incorporated by reference in its entirety for all purposes. To quote Ri is incorporated.

  This application claims the priority and benefit of US Provisional Application No. 62 / 010,617 filed on June 11, 2014 and entitled "REUSABLE ANONYMOUS SUBSCRIPTION", filed on February 17, 2015 Claim priority and benefit under US Non Provisional Application No. 14 / 624,364 entitled REUSABLE ANONYMOUS SUBSCRIPTION.

  The present application is filed on February 7, 2015 claiming priority and benefit based on US Provisional Application No. 62 / 011,400, filed on June 12, 2014 and entitled "RULE BASED SUBSCRIPTION CLONING". Claim priority and benefit based on US Non-Provisional Application No. 14 / 624,356 entitled "RULE BASED SUBSCRIPTION CLONING".

  The entire contents of the above non-provisional and provisional patent applications are incorporated herein by reference for all purposes.

BACKGROUND The present disclosure relates to computer systems and software, and more particularly, to techniques for facilitating and automating service provisioning in cloud environments.

  Cloud computing is a model that allows easy on-demand network access to a shared pool of configurable computing resources (eg, networks, servers, storage devices, applications, and services). Services provided or accessed through the cloud (or network) are called cloud services. A cloud service provider needs to perform a lot of processing to make the cloud service available to contracted customers. Because of its complexity, much of this process is still done manually. For example, provisioning resources to provide such cloud services can be a labor intensive process.

  Consumers and businesses expect the order and start of use of computer network cloud based services to be seamless. However, many cloud services require provisioning of resources that can be shared, making startup difficult. For example, a server in a server farm may perform cloud services for a large number of customers at once, and resources may need to be transferred to add another customer. The service that the user wishes to use may vary from user to user. For example, some users may only want raw storage on the cloud, while others may want to use advanced database storage. There are also other users who want to use graphical user interface (GUI) software running on the cloud for their employees or customers.

  In some cases, an operator may wish to try out new features or components using an existing computing environment (e.g., a production system). However, these business owners may not be able to test new features by implementing another environment using an existing computing environment. As a result, an operator may consume resources to implement another environment that includes additional configuration and computing resources. In addition, the implementation of the additional system may involve management procedures to contract with the service provider for more computing resources. The construction of the additional calculation environment may require exorbitant costs and a large amount of time depending on the business operator.

  Some operators want to try a cloud-based service to determine if they meet their needs. However, the operator may not want to test the service. Because establishing a regular subscription to the service may require additional heavyweight processes, including configuring resources, before the subscription allows access to the service. It is from. If you purchase a full subscription, this additional process can cause delays when the operator attempts to use this service further. Furthermore, customer data created during testing of a service may not be retained for subsequent use of the service by a regular subscription after testing of the service. Operators may bear the burden of spending time and money regenerating customer data for subsequent use based on legitimate subscriptions by testing the service while realizing the environment of use . Because of these issues, some operators may not be given the flexibility to try out the service before purchasing a subscription for the service. Cloud service providers may lose the opportunity to gain other customers reluctant to try this service before subscribing to the service. The provider may be tasked with reprovisioning the resources for the service each time another provider wishes to try the service. Customers and service providers will benefit from technology that enables services and reduces the time it takes to provision resources to maintain customer data related to the use of these services.

  There is a need in the art for cloud-based computer systems that are faster, less expensive, and easier to use.

SUMMARY In general, aspects of the present disclosure relate to techniques for providing access to services to users using existing services provisioned by a cloud infrastructure system. More specifically, subscriptions for access to services may be provided to users based on existing subscriptions. Examples of service types are: Software as a Service (SaaS) category, Platform as a Service (PaaS) category, Infrastructure as a Service (IaaS) Including, but not limited to) categories, or other categories of services, including hybrid services.

  The cloud infrastructure system may provide users with access to services based on existing services using the various techniques described herein. Such techniques may improve processing efficiency in providing access to services to customers by reducing the processing time required to provision resources for the requested service. The cloud infrastructure system can determine the type of service based on the request from the user, and provide a subscription that allows access to the service using the determined provisioning for the existing service be able to.

  In some embodiments, the cloud infrastructure system creates a subscription (eg, a "clone subscription") based on an existing subscription (eg, a base subscription) to existing services provided by the cloud infrastructure system. Can provide the service to the user. Clone subscriptions provide users with access to services based on existing services. Multiple clone subscriptions may be created based on the base subscription, and each clone subscription provides a subscription to a service based on the existing services of the base subscription. A clone subscription may be associated with the subscription from which the creation of this clone subscription was based. When a clone subscription is associated with the subscription on which this clone subscription was created, the lifecycle of this subscription and the clone subscription will be associated with each other.

  In at least one illustrative example, access to the services provided by the clone subscription may be provided to support additional environments for one type of use indicated by the user. The type of use that this additional environment supports may be different from the type of use that corresponds to the existing subscription from which the clone subscription was established. For example, a user may request a clone subscription of a production environment provided by a base subscription. By doing so, a test environment based on this production environment (for example, a clone of this production environment) is established. The test environment for this clone subscription may be required to be able to test in the clone environment before deploying new features into the production environment.

  In some embodiments, the cloud infrastructure system may implement technology that allows various users to anonymously reuse the services provisioned by the cloud infrastructure system. The system may configure a subscription called "reusable anonymous subscription" (RAS). The RAS may provide the user with access to this service provided by the system prior to obtaining a qualifying subscription for the service. The services that RAS can access may already be provisioned. The cloud infrastructure system may configure one or more pools of RAS. Each RAS provides reusable subscriptions to pre-provisioned services. When a service is requested by a user, a RAS for this service may be assigned from the pool to the user so that the service can be accessed.

  If the user decides not to convert the RAS to a full subscription, then return the RAS back to the pool for reuse of the services provisioned for this RAS. The service provisioned for this RAS keeps provisioned even when the RAS is returned to the pool, thereby minimizing the time required to provision new resources for this service and maximizing resource usage. Make it The RAS may be reassigned to another user if the previous user does not convert the RAS to a regular subscription.

  If the user decides to convert the RAS to a regular subscription, the RAS does not have to be returned to the pool. The RAS may be converted to a regular subscription using a lightweight conversion process. Because the services provided by RAS are already provisioned, the conversion process is lightweight and services will not need to be re-provisioned. The conversion process may establish an account assigned a periodic subscription for use of the service already provisioned to the RAS. In some embodiments, customer-specific data generated during use of a service provided by the RAS may be separated from data-specific data associated with the service. When the RAS is converted to a regular subscription, data for a specific customer may be held and associated with the regular subscription. Thus, a user who is provided a legitimate subscription may continue to use the service with existing customer-specific data created during use of the service through RAS.

  In at least one embodiment, techniques for providing access to services to users using existing services provisioned by the cloud infrastructure system are disclosed. One technique is a method that can be implemented by a computing system. This computing system may be included in a service infrastructure system. The service infrastructure system may be realized by a cloud infrastructure system. The service infrastructure system may include a multi-tenant environment. The method may include providing a plurality of services to a service infrastructure system. The services may include Java® services, customer relationship management (CRM) services, or human capital management (HCM) services. Each service of these services may be associated with data for specific service. The application specific service corresponding to a service may indicate the configuration of this service, which may include one or more resources assigned to provide this service. The method may include providing a plurality of services to a service infrastructure system. The method may include receiving from the first customer a request for access to a service provided by the service infrastructure system. The method may include determining a type of subscription based on the service requested by the first customer. The type of subscription may be either a clone subscription or a reusable subscription. The method may include providing the first customer with a subscription to access the service. The subscription may be provided based on the type of subscription, and may be provided using a first of the plurality of services. The method may include managing a subscription provided to the first customer.

  In some embodiments, the first customer request may indicate the type of use of the service by the customer, and the type of subscription may be determined based on the type of use indicated by the request. Good.

  In some embodiments, when the type of subscription is a clone subscription, providing the subscription to the first customer is a first clone subscription based on the first subscription to the first service. The first clone subscription is provided as a subscription to the first customer, and providing the subscription to the first customer is based on a set of rules. And C. matching a clone subscription to the first subscription.

  In some embodiments, when the type of subscription is a clone subscription, associating the first clone subscription with the first subscription is a first subscription with the first clone subscription life cycle. May be associated with the life cycle of the The clone subscription may provide access to the second service, and the access to the second service by the customer may end when the access to the first service by the customer is finished. When the type of subscription is a clone subscription, the method further comprises updating access to the first service based on a request from the customer and based on updated access to the first service. And modifying access to the second service.

  In some embodiments, when the type of subscription is a clone subscription, the first clone subscription may provide access to a second service, and the set of rules comprises: It may also indicate the use of a second service as a clone of the service. One set of rules may indicate the duration of access to the second service. The set of rules may indicate the number of users authorized to access the second service, the number of users authorized to access the second service being the access to the first service May be different from the number of authorized users. The set of rules may indicate the configuration of the second service, and the configuration of the second service may be different from the configuration of the first service.

  In some embodiments, when the type of subscription is a clone subscription, managing the subscription determines access to the requested service by the subscription in response to the change of the first service. Can be included. Access to the requested service may be determined using a set of rules.

  In some embodiments, providing the subscription to the first customer when the type of subscription is a reusable subscription is provision of the first service in a service pool in the service infrastructure system. Provisioning the first service for the first subscription in the service pool, and determining that the first service for the subscription is not provisioned in the service pool, and Assigning a first subscription for the one service to the customer as a subscription for the service. Assigning a first subscription may include assigning a first service from a service pool to a customer. Assigning the first service to the customer may include removing the first service from the service pool.

  In some embodiments, when the type of subscription is a reusable subscription, the method may include associating customer-specific data with service-specific data corresponding to the first service. Specific-customer data associated with the first customer may include data related to the use of the first service by the customer. When the type of subscription is a reusable subscription, managing the subscription to access the service may include assigning a first service to the service pool when the subscription is terminated. Assigning the first service may include releasing the correspondence between the data for specific customer and the data for specific service corresponding to the first service. The first service may be able to be reassigned from the service pool to one or more other customers. In some embodiments, when the type of subscription is a reusable subscription, the method receives a request by a second customer for access to a second service of the plurality of services. Determining that the second service is available in the service pool based on determining that the second service is similar to the first service, and determining the first subscription in the service pool. Assigning a first subscription to a second customer, including assigning to a second customer, includes removing the first subscription from the service pool, and the method further comprises: And associating the data for specific customer corresponding to the data for specific service corresponding to the first service.

  In some embodiments, providing the service may include provisioning the service in the cloud infrastructure system prior to receiving a request from the first customer. Services may be provisioned based on one or more metrics associated with the demand for services. Services may be provisioned based on one or more metrics associated with the type of service.

  In at least one embodiment, techniques are disclosed for providing access to services to users using existing services provisioned by the cloud infrastructure system. One technique is a system that includes at least one processor and a memory operatively coupled to the at least one processor. This system may be included in a service infrastructure system. The service infrastructure system may include a multi-tenant environment. The memory may store computer code. Computer code may be executed by the at least one processor of the system to provide a plurality of services to a service infrastructure system. The services may include Java services, customer relationship management (CRM) services, or human resource management (HCM) services. Each service of these services may be associated with data for a specific service. The service-specific data corresponding to the service may indicate a configuration for the service, and the configuration may include one or more resources assigned to provide the service.

  The at least one processor receives a request by a first customer for access to services provided by the service infrastructure system by executing computer code stored in memory. The at least one processor executes the computer code stored in the memory to determine the type of subscription based on the service requested by the first customer. The type of subscription may be either a clone subscription or a reusable subscription. The at least one processor executes the computer code stored in the memory to provide the first customer with a subscription for accessing the service. The subscription may be provided based on the type of subscription, and may be provided using a first of the plurality of services. The at least one processor manages subscriptions provided to a first customer by executing computer code stored in a memory.

  In some embodiments, the first customer request may indicate the type of use of the service by the customer, and the type of subscription may be determined based on the type of use indicated by the request. .

  In some embodiments, when the type of subscription is a clone subscription, providing the subscription to the first customer is a first clone subscription based on the first subscription to the first service. Providing the first clone subscription as a subscription to the first customer, and providing the subscription to the first customer is a first clone based on a set of rules. Including associating the subscription with a first subscription.

  In some embodiments, when the type of subscription is a clone subscription, associating the first clone subscription with the first subscription is a first subscription with the first clone subscription life cycle. May be associated with the life cycle of the The clone subscription may provide access to the second service, and the customer's access to the second service may end when the customer's access to the first service is finished. When the type of subscription is a clone subscription, the at least one processor updates the access to the first service based on the request from the customer by executing computer code stored in the memory. , Modify access to the second service based on access to the updated first service.

  In some embodiments, when the type of subscription is a clone subscription, the first clone subscription may provide access to a second service, and the set of rules comprises a second service May be shown to be used as a clone of the first service. One set of rules may indicate the duration of access to the second service. The set of rules may indicate the number of users authorized to access the second service, the number of users authorized to access the second service being the access to the first service May be different from the number of authorized users. The set of rules may indicate the configuration of the second service, and the configuration of the second service may be different from the configuration of the first service.

  In some embodiments, when the type of subscription is a clone subscription, managing the subscription determines access to the requested service by the subscription in response to the change of the first service. Can be included. Access to the requested service may be determined using a set of rules.

  In some embodiments, providing the subscription to the first customer when the type of subscription is a reusable subscription is provision of the first service in a service pool in the service infrastructure system. Determining that the first service for the subscription has not been provisioned in the service pool, provisioning the first service for the first subscription in the service pool, and Assigning a first subscription to the service of the customer to the customer as a subscription to the service. Assigning a first subscription may include assigning a first service from a service pool to a customer. Assigning the first service to the customer may include removing the first service from the service pool.

  In some embodiments, when the type of subscription is a reusable subscription, the at least one processor executes customer-specific data by executing computer code stored in memory, Correspond to the data for specific service corresponding to the service of 1. The data for specific customer is associated with the customer of the first service. Specific-customer data associated with the first customer may include data related to the use of the first service by the customer. When the type of subscription is a reusable subscription, managing the subscription to access the service includes assigning the first service from the customer to the service pool when the subscription is terminated obtain. Assigning the first service may include releasing the correspondence between the data for specific customer and the data for specific service corresponding to the first service. The first service may be able to be reassigned from the service pool to one or more other customers. In some embodiments, when the type of subscription is a reusable subscription, the at least one processor executes a computer code stored in the memory to execute a third of the plurality of services. A second service is available in the service pool based on the determination by the second customer of access to the two services that the second service is similar to the first service Determining, assigning a second subscription in the second pool to a second customer, and assigning a first subscription to a second customer, removing the first subscription from the service pool Data for specific customer corresponding to the second customer, and data for specific service corresponding to the first service. Associate with.

  In some embodiments, providing the service may include provisioning the service in the cloud infrastructure system prior to receiving a request from the first customer. Services may be provisioned based on one or more metrics associated with the operation of the service infrastructure system. Providing the service may include provisioning the service prior to receiving a request from the first customer. Services may be provisioned based on one or more metrics associated with the demand for services.

  In at least one embodiment, techniques are disclosed for providing access to services to users using existing services provisioned by the cloud infrastructure system. One technology is a non-transitory computer readable medium that stores instructions executable by a processor of a computer system. This non-transitory computer readable medium may be included in a service infrastructure system. The service infrastructure system may include a multi-tenant environment. The instructions stored on the non-transitory computer readable medium are executable by the processor to provide the plurality of services to the service infrastructure system. The services may include Java services, customer relationship management (CRM) services, or human resource management (HCM) services. Each service of these services may be associated with data for a specific service. The service-specific data corresponding to the service may indicate a configuration for the service, and the configuration may include one or more resources assigned to provide the service.

  The processor may execute instructions stored in the non-transitory computer readable medium to receive a request by a first customer for access to a service provided by the service infrastructure system. The processor executes the instructions stored in the non-transitory computer readable medium to determine the type of subscription based on the service requested by the first customer. The type of subscription may be either a clone subscription or a reusable subscription. The processor may execute the instructions stored by the non-transitory computer readable medium to provide the first customer with a subscription for accessing the service. The subscription may be provided based on the type of subscription, or may be provided using a first of a plurality of services. The processor may execute instructions stored in the non-transitory computer readable medium to manage the subscription provided to the first customer.

  In some embodiments, the first customer request may indicate the type of usage of the service by the customer, and the type of subscription may be determined based on the type of usage indicated by the request.

  In some embodiments, when the type of subscription is a clone subscription, providing the subscription to the first customer is a first clone subscription based on the first subscription to the first service. The first clone subscription is provided as a subscription to the first customer, and providing the subscription to the first customer is performed based on the set of rules. Including associating the clone subscription with the first subscription.

  In some embodiments, when the type of subscription is a clone subscription, associating the first clone subscription with the first subscription is a first subscription with the first clone subscription life cycle. May be associated with the life cycle of the The clone subscription may provide access to the second service, and the customer's access to the second service may end when the customer's access to the first service is finished. When the type of subscription is a clone subscription, the processor executes instructions stored in the non-transitory computer readable medium to update the access to the first service based on the request from the customer. , Modify access to the second service based on access to the updated first service.

  In some embodiments, when the type of subscription is a clone subscription, the first clone subscription may provide access to a second service, and the set of rules comprises a second service May be shown to be used as a clone of the first service. One set of rules may indicate the duration of access to the second service. The set of rules may indicate the number of users authorized to access the second service, the number of users authorized to access the second service being the access to the first service May be different from the number of authorized users. The set of rules may indicate the configuration of the second service, and the configuration of the second service may be different from the configuration of the first service.

  In some embodiments, when the type of subscription is a clone subscription, managing the subscription determines access to the requested service by the subscription in response to the change of the first service. Can be included. Access to the requested service may be determined using a set of rules.

  In some embodiments, providing the subscription to the first customer when the type of subscription is a reusable subscription is provision of the first service in a service pool in the service infrastructure system. Determining that the first service for the subscription has not been provisioned in the service pool, provisioning the first service for the first subscription in the service pool, and Assigning a first subscription to a service to the customer as a subscription to the service. Assigning a first subscription may include assigning a first service from a service pool to a customer. Assigning the first service to the customer may include removing the first service from the service pool.

  In some embodiments, when the type of subscription is a reusable subscription, the processor executes instructions stored in the non-transitory computer readable medium to store customer specific data, Correspond to the data for specific service corresponding to the service of 1. The data for specific customer is associated with the customer of the first service. Specific-customer data associated with the first customer may include data related to the use of the first service by the customer. When the type of subscription is a reusable subscription, managing the subscription to access the service includes assigning the first service from the customer to the service pool when the subscription is terminated obtain. Assigning the first service may include releasing the correspondence between the data for specific customer and the data for specific service corresponding to the first service. The first service may be able to be reassigned from the service pool to one or more other customers. In some embodiments, when the type of subscription is a reusable subscription, the processor executes instructions stored in the non-transitory computer readable medium to cause the first of the plurality of services to be executed. A second service is available in the service pool based on the determination by the second customer of access to the two services that the second service is similar to the first service Determining and assigning a second subscription in the second pool to the second customer and assigning the first subscription to the second customer includes deleting the first subscription from the service pool , Corresponding to the data for specific service corresponding to the first service, the data for specific customer corresponding to the second customer Kick.

  In some embodiments, providing the service may include provisioning the service in the cloud infrastructure system prior to receiving a request from the first customer. Services may be provisioned based on one or more metrics associated with the operation of the service infrastructure system. Providing the service may include provisioning the service prior to receiving a request from the first customer. Services may be provisioned based on one or more metrics associated with the demand for services.

  Still other embodiments relate to system and machine readable tangible storage media that use or store instructions and / or code to perform the operations to implement the techniques described herein.

  The above summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used solely to determine the scope of the claimed subject matter . The subject matter should be understood with reference to the entire specification of this patent, any or all of the drawings, and appropriate parts of each of the claims.

  A more complete understanding of the nature and advantages of the present invention will be obtained by the following detailed description and the accompanying drawings.

  Embodiments for explaining the present invention will be described in detail below with reference to the attached drawings.

FIG. 1 is a logic diagram of a cloud infrastructure system in accordance with an embodiment of the present invention. FIG. 2 is a simplified block diagram of a hardware / software stack that may be used to implement a cloud infrastructure system in accordance with an embodiment of the present invention. FIG. 2 is a simplified block diagram of a system environment for implementing the cloud infrastructure system shown in FIG. 1A. FIG. 6 shows a simplified flowchart 300 illustrating the processing that a TAS module may perform in a cloud infrastructure system in accordance with an embodiment of the present invention. FIG. 6 shows a simplified high level diagram of one or more sub-modules in a TAS module in a cloud infrastructure system in accordance with an embodiment of the present invention. 1 illustrates an exemplary distributed deployment of TAS components in accordance with an embodiment of the present invention. FIG. 5 is a simplified block diagram illustrating the interaction of an SDI module with one or more modules in a cloud infrastructure system in accordance with an embodiment of the present invention. FIG. 5 shows a simplified high level view of sub modules of an SDI module according to an embodiment of the present invention. Fig. 6 shows a simplified flow chart illustrating the processing that an SDI component may perform in a cloud infrastructure system according to an embodiment of the present invention. FIG. 10 shows a simplified block diagram illustrating the high level architecture of Nuviaq system 710 and the relationship of this system to other cloud infrastructure components in accordance with an embodiment of the present invention. FIG. 6 shows an exemplary sequence diagram illustrating steps of a provisioning process using a Nuviaq system according to an embodiment of the present invention. FIG. 6 shows an exemplary sequence diagram illustrating the steps of a deployment process using the Nuviaq system according to an embodiment of the present invention. Fig. 6 shows an example of a database instance provisioned for a database service according to an embodiment of the present invention. FIG. 1 shows a simplified block diagram of a system environment for providing reusable anonymous subscriptions in accordance with some embodiments of the present invention. 7 illustrates an example data structure for implementing reusable anonymous subscriptions in accordance with some embodiments of the present invention. 7 is a flowchart of a process for managing the life cycle of reusable anonymous subscriptions in accordance with various embodiments. FIG. 1 shows a simplified block diagram of a system environment for providing clone subscriptions in accordance with some embodiments of the present invention. 7 illustrates an example of a subscription data structure in accordance with some embodiments of the present invention. 7 illustrates exemplary rules for managing clone subscriptions in accordance with various embodiments. 5 is a flowchart of a process for managing the life cycle of a clone subscription in accordance with various embodiments. 7 is a flowchart of a process for cloning a subscription in accordance with various embodiments. 7 is a flowchart of a process for providing a subscription for a service using existing subscriptions in accordance with various embodiments. FIG. 5 illustrates a high level overview of various interactions involved in providing a tenant environment in accordance with an embodiment of the present invention. FIG. 1 shows a simplified diagram of a distributed system for implementing an embodiment. 1 illustrates a typical computer system that may be used to implement an embodiment of the present invention. 1 illustrates an exemplary service infrastructure system that may be used to implement certain embodiments of the present invention.

DETAILED DESCRIPTION In the following description, for purposes of explanation, specific details are set forth in order to provide a thorough understanding of the embodiments of the present invention. However, it will be apparent that various embodiments may be practiced without these specific details. The drawings and descriptions are not intended to be limiting.

  Certain embodiments of the present invention provide techniques for automating provisioning, management, and tracking of services provided by a cloud infrastructure system.

Introduction In a specific embodiment, the cloud infrastructure system is a set of applications that are provided to customers in a self-service, subscription-based, flexible, scalable, secure, highly available, and secure manner. It may include middleware and database service offerings. An example of such a cloud infrastructure system is the Oracle Public Cloud provided by the assignee of the present application.

  Cloud infrastructure systems provision, manage and track customer subscriptions of services and resources within the cloud infrastructure system, and provide predictable business costs to customers utilizing services within the cloud infrastructure system Providing robust identity domain separation and protection of customer data within the cloud infrastructure system, providing the customer with transparent architecture and control of the cloud infrastructure system design, reliable data protection and data privacy Providing customers with compliance with standards and regulations, integrated development experience for building and deploying services in cloud infrastructure systems Providing a large number of functions including, but not limited to, providing customers, and providing customers seamless integration between business software, middleware, databases and infrastructure services in cloud infrastructure systems obtain.

  In particular embodiments, the services provided by the cloud infrastructure system may include a number of services that are made available to users of the cloud infrastructure system on demand. These services include online data storage and backup solutions, web-based email services, hosted office software packages and document collaboration services, database processing, managed technical support services, and more. The services provided by the cloud infrastructure system can be dynamically adjusted to meet the needs of its users. What embodies the service provided by the cloud infrastructure system is referred to herein as a service instance. Generally, a service that is made available to users from a cloud service provider's system via a communication network such as the Internet is called a cloud service. Typically, in a public cloud environment, the servers and systems that make up the cloud service provider's system are different from the customer's own on-premises servers and systems. For example, a cloud service provider's system may host an application, and a user can order and use the application on demand via a communication network such as the Internet.

  Services in the computer network cloud infrastructure may include protected computer network access to storage, hosted databases, hosted web servers, software applications, or other services provided to users from cloud vendors, or the like. Includes other services well known in the art. For example, the service may include password protected access to remote storage on the cloud through the Internet. As another example, the service may include a web service based hosted relational database and scripting language middleware engine for private use of networked developers. As another example, the service may include access to an email software application hosted on the cloud vendor's website.

  FIG. 1A is a logic diagram of a cloud infrastructure system in accordance with an embodiment of the present invention. Cloud infrastructure system 100 may provide various services via a cloud or networked environment. These services may be provided in the Software as a Service (SaaS) category, Platform as a Service (PaaS) category, Infrastructure as a Service (IaaS) category, or other categories of services including hybrid services Service may be included. The customer may order one or more services provided by the cloud infrastructure system 100 via a subscription order. In that case, the cloud infrastructure system 100 performs processing to provide a service for the customer's subscription order.

  Cloud infrastructure system 100 may provide cloud services through various deployment models. For example, services may be provided in a public cloud model. In the public cloud model, the cloud infrastructure system 100 is owned by an organization sales cloud service (for example, owned by Oracle Corporation), and the service is made available to general public or companies in various industries. As another example, services may be provided in a private cloud model. In the private cloud model, the cloud infrastructure system 100 can be operated for only one organization, and services can be provided to one or more entities in the organization. Cloud services can also be provided by the community cloud model. In the community cloud model, the cloud infrastructure system 100 and the services provided by this system are shared by several organizations in the related community. Cloud services may also be provided by a hybrid cloud model, which is a combination of two or more different models.

  As shown in FIG. 1A, cloud infrastructure system 100 may include multiple components that work together to enable provisioning of services provided by cloud infrastructure system 100. In the embodiment illustrated in FIG. 1A, cloud infrastructure system 100 includes SaaS platform 102, PaaS platform 104, IaaS platform 110, infrastructure resources 106, and cloud management function 108. The components of this may be realized by hardware or software or a combination thereof.

  The SaaS platform 102 is configured to provide cloud services included in the SaaS category. For example, SaaS platform 102 may provide the ability to build and deliver a set of on-demand applications on an integrated development and deployment platform. The SaaS platform 102 can manage and control the underlying software and infrastructure in providing the SaaS service. By using the service provided by the SaaS platform 102, the customer can use an application executed on the cloud infrastructure system 100. Customers can obtain application services without purchasing separate licenses and support.

  It can provide various different SaaS services. Examples include, but are not limited to, services that provide solutions for sales performance management, enterprise integration for large organizations, business versatility, and the like. In one embodiment, the SaaS service may include a customer relationship management (CRM) service 110 (eg, a fusion CRM service provided by Oracle Cloud), human resource management (HCM) / human resource management service 112, and the like. CRM service 110 may include services directed to reporting and managing sales activity cycles for customers. HCM / Human Resources Services 112 may include services directed to providing clients with global workforce lifecycle management and human resources management services.

  A variety of different PaaS services may be provided by the PaaS platform 104 in a standardized, shared and flexible and scalable application development and deployment platform. The PaaS service example builds a service that allows organizations (such as Oracle) to merge existing applications on a shared common architecture and a new application that enhances the shared services provided by this platform It may include functions but is not limited to them. The PaaS platform 104 can manage and control the underlying software and infrastructure in providing PaaS services. Customers can obtain PaaS services provided by the cloud infrastructure system 100 without purchasing separate licenses and support. Examples of PaaS services include, but are not limited to, Oracle Java Cloud Service (JCS), Oracle Database Cloud Service (DBCS), and others.

  By utilizing the services provided by the PaaS platform 104, customers can utilize programming languages and tools supported by the cloud infrastructure system 100, and can also control deployed services. In some embodiments, the PaaS service provided by cloud infrastructure system 100 may include database cloud service 114, middleware cloud service (eg, Oracle Fusion middleware service) 116, and Java cloud service 117. . In one embodiment, the database cloud service 114 may support a shared service deployment model that enables organizations to pool database resources and provide database as a service to customers in the form of a database cloud. Middleware cloud service 116 provides a platform for customers to develop and deploy various business applications, and Java cloud service 117 provides a platform for customers to deploy Java applications in cloud infrastructure system 100. Do. The components in the SaaS platform 102 and the PaaS platform 104 shown in FIG. 1A are shown for illustrative purposes only and are not intended to limit the scope of the embodiments of the present invention. In alternative embodiments, the SaaS platform 102 and the PaaS platform 104 may include additional components to provide additional services to customers of the cloud infrastructure system 100.

  A variety of different IaaS services may be provided by the IaaS platform 110. The IaaS service facilitates management and control of basic computing resources, such as storage, networks and other basic computing resources, for customers utilizing the services provided by the SaaS and PaaS platforms.

  In particular embodiments, cloud infrastructure system 100 includes infrastructure resources 106 for providing resources used to provide various services to customers of cloud infrastructure system 100. In one embodiment, the infrastructure resources 106 are pre-integrated, optimized combinations of hardware such as servers, storage and networking resources to perform the services provided by the PaaS platform and the SaaS platform. Including.

  In particular embodiments, cloud management function 108 provides comprehensive management of cloud services (eg, SaaS, PaaS, IaaS services) in cloud infrastructure system 100. In one embodiment, cloud management functionality 108 includes functionality for provisioning, managing and tracking customer subscriptions received by cloud infrastructure system 100, and the like.

  FIG. 1B is a simplified block diagram of a hardware / software stack that may be used to implement cloud infrastructure system 100 according to an embodiment of the present invention. It should be understood that the implementation shown in FIG. 1B may have other components besides those shown in FIG. 1B. Furthermore, the embodiment shown in FIG. 1B is only one example of a cloud infrastructure system that can incorporate embodiments of the present invention. In some other embodiments, cloud infrastructure system 100 may have more or less components than those shown in FIG. 1B, or may combine two or more components, or It may have different configurations or arrangements of components. In certain embodiments, hardware and software components are stacked to provide vertical integration that provides optimal performance.

  Various types of users may interact with cloud infrastructure system 100. These users may include, for example, end users 150 who may interact with the cloud infrastructure system 100 using various client devices such as desktops, mobile devices, tablets and the like. Also, users can use command line interface (CLI), application programming interface (application programming interface): through various integrated development environment (IDE) and through other applications. The developer / programmer 152 may interact with the cloud infrastructure system 100 using the API). The user may also include operations staff 154. These may include the staff of the cloud service provider or the staff of other users.

  Application services layer 156 identifies various cloud services that may be provided by cloud infrastructure system 100. These services may be mapped to their respective software components 160 (eg, an Oracle web logic server for providing Java services, an Oracle database for providing database services, etc.) via service integration and connectivity layer 158, or Or may be associated.

  In particular embodiments, several internal services 162 shared by various components or modules of cloud infrastructure system 100 and services provided by cloud infrastructure system 100 may be provided. These internal shared services include security and identity services, integrated services, enterprise repository services, enterprise manager services, virus scan and white list services, high availability, backup and recovery services, services to enable cloud support in IDEs, It may include, but is not limited to, email services, notification services, file transfer services, and the like.

  The runtime infrastructure layer 164 represents the hardware layer on which various other layers and components are built. In particular embodiments, runtime infrastructure layer 164 may comprise one Oracle Exadata machine to provide storage, processing and networking resources. The Exadata machine may be comprised of various database servers, storage servers, networking resources, and other components for hosting cloud service related software layers. In particular embodiments, Exadata machines may be designed to work with Oracle Exalogic, an engineered system that provides a collection of storage, computing, network and software resources. The combination of Exadata and Exalogic provides a complete hardware and software engineered solution that provides a high performance, high availability, scalable, secure, managed platform for delivering cloud services.

  FIG. 2 is a simplified block diagram of a system environment for implementing the cloud infrastructure system shown in FIG. 1A according to an embodiment of the present invention. In the illustrated embodiment, system environment 230 includes one or more client computing devices 224, 226 and 228 that may be used by a user to interact with cloud infrastructure system 100. The client device may be a web browser, a proprietary client application (e.g., Oracle Forms) or a client application that may be used by the client device user to interact with the cloud infrastructure system 100 to utilize services provided by the cloud infrastructure system 100. It may be configured to run client applications, such as other applications.

  It should be understood that the cloud infrastructure system 100 shown in FIG. 2 may have other components besides those shown in FIG. Furthermore, the embodiment shown in FIG. 2 is only one example of a cloud infrastructure system that can incorporate embodiments of the present invention. In some other embodiments, the cloud infrastructure system 100 may have more or less components than those shown in FIG. 2, and may combine two or more components, or It may have different configurations or arrangements of components.

  The client computing devices 224, 226 and 228 may be general purpose personal computers (including, by way of example, personal computers and / or laptop computers running various versions of Microsoft Windows® and / or Apple Macintosh operating systems), Runs software such as Microsoft Windows Mobile and is Internet, email, SMS, Blackberry or any other communication protocol available) mobile phone or PDA, various commercially available UNIX or UNIX-like operating system Any system (including but not limited to various GNU / Linux (R) operating systems) Or workstation computers running or may be another computing device. For example, client computing devices 224, 226 and 228 may be thin client computers capable of communicating over a network, gaming devices capable of connecting to the Internet, and / or other electronic devices such as personal messaging devices. Good. Although the exemplary system environment 230 is shown with three client computing devices, any number of client computing devices may be supported. Other devices, such as devices with sensors, may interact with the cloud infrastructure system 100.

  Network 232 may facilitate communication and exchange of data between clients 224, 226 and 228 and cloud infrastructure system 100. Network 232 may support data communication using any of a variety of commercially available protocols, including but not limited to TCP / IP, SNA, IPX, Apple Talk, etc., as is well known to those skilled in the art It may be any type of network. By way of example only, networks 232 include but are limited to Ethernet networks, local area networks (LANs) such as token ring networks, wide area networks, and virtual private networks (VPNs). Virtual networks, the Internet, intranets, extranets, public switched telephone networks (PSTNs), infrared networks, wireless networks (eg IEEE 802.1X protocol series, Bluetooth known in the art) Networks operating under any of (registered trademark) protocols and / or other wireless protocols, and / or these and / or other networks It may be any combination of work.

  The cloud infrastructure system 100 may be a general-purpose computer, a dedicated server computer (including, for example, a PC server, a UNIX server, a midrange server, a mainframe computer, a rack mount server, etc.), a server farm, a server cluster, or any other One or more computers and / or servers may be provided, which may be of any suitable configuration and / or combination. The computing devices that make up cloud infrastructure system 100 execute either the operating system or any of a variety of additional server applications and / or middle tier applications, including HTTP servers, FTP servers, CGI servers, Java servers, database servers, etc. It can. Representative database servers include, but are not limited to, those commercially available from Oracle, Microsoft, Sybase, IBM, and the like.

  In various embodiments, cloud infrastructure system 100 may be adapted to automatically provision, manage and track customer subscriptions to services provided by cloud infrastructure system 100. In one embodiment, as shown in FIG. 2, the components in the cloud infrastructure system 100 include an Identity Management (IDM) module 200, a service module 202, and a Tenant Automation System (TAS) module. 204, Service Deployment Infrastructure (SDI) module 206, Enterprise Manager (EM) module 208, store user interface (UI) 210, cloud user interface (UI) 212 and support One or more front end web interfaces, such as a user interface (UI) 216, and an order management module 214 , Including the sales staff 218, the operator staff 220, and the order database 222. These modules may include one or more computers and / or servers, which may be general purpose computers, specialized server computers, server farms, server clusters, or any other suitable arrangement and / or combination. Or may be provided using them. In one embodiment, one or more of these modules may be provided by cloud management function 108 or IaaS platform 110 in cloud infrastructure system 100. The various modules of cloud infrastructure system 100 shown in FIG. 2 are shown for illustrative purposes only and are not intended to limit the scope of the embodiments of the present invention. Alternative embodiments may include more or less modules than those shown in FIG.

  In exemplary operations, in (1), a customer using a client device, such as client device 224 or 226, browses and provides various services provided by cloud infrastructure system 100. It may interact with the cloud infrastructure system 100 by ordering subscriptions for one or more services. In particular embodiments, a customer may access the store UI 210 or cloud UI 212 and place a subscription order via these user interfaces.

  The order information received by the cloud infrastructure system 100 in response to the customer placing an order comprises the customer and one or more services provided by the cloud infrastructure system 100 to which the customer is to subscribe. It may contain identifying information. A single order may include multiple service orders. For example, a customer may login to the cloud UI 212 to request subscriptions for CRM service and Java cloud service in the same order.

  Further, the order may also include one or more service levels for the ordered service. As used herein and described in more detail below, service levels for services include services requested in the context of subscriptions, such as the amount of storage, the amount of computing resources, data transfer equipment, etc. Determine the amount of resources allocated to provide. For example, basic service levels may provide a minimal level of storage, data transmission or number of users, and higher service levels may include additional resources.

  Also, in some examples, the order information received by the cloud infrastructure system 100 may include information indicating customer level and the time period for which the service is required. The customer level defines the priority of the customer making the subscription request. In one example, the service that the cloud infrastructure system 100 guarantees or promises to the customer as defined by the Service Level Agreement (SLA) agreed upon between the customer and the provider of the cloud service. It can be determined based on the quality of In one example, various customer levels include basic levels, silver levels and gold levels. The period of service may define the start date and time of the service and the period in which the service is required (for example, the end date and time of service may be defined).

  In one embodiment, the customer may request a new subscription via the store UI 210 or may request a trial subscription via the cloud UI 212. In particular embodiments, store UI 210 may correspond to a service provider's e-commerce storefront (eg, www.oracle.com/store for Oracle Cloud Services). Cloud UI 212 may correspond to a business interface for a service provider. The customer can investigate available services and sign up for services of interest via the cloud UI 212. Cloud UI 212 captures the user input necessary to order a trial subscription provided by cloud infrastructure system 100. Also, the cloud UI 212 may be used to view account functions and configure a runtime environment located within the cloud infrastructure system 100. In addition to ordering new subscriptions, the store UI 210 can also change subscription service levels, extend subscription terms, improve subscription service levels, and terminate existing subscriptions It may also allow customers to perform subscription related tasks.

  After the order is made per (1), the order information received via either the store UI 210 or the cloud UI 212 is stored in the order database 222 in (2), and the order database 222 is stored in the cloud infrastructure system 100. May be one of several databases operated by and used in conjunction with other system elements. Although the order database 222 is logically illustrated in FIG. 2 as a single database, in an actual implementation it may comprise one or more databases.

  At (3), the order is sent to the order management module 214. The order management module 214 is configured to perform billing and accounting functions associated with the order, such as order verification and order reservation upon verification. In particular embodiments, order management module 214 may include a contract management module and an installation base module. The contract management module may store contract information associated with a customer's subscription order, such as a customer's service level agreement (SLA) with the cloud infrastructure system 100. The installed base module may include a detailed description of the service in the customer's subscription order. In addition to order information, the installed base module may track installation details associated with the service, product status and support service history associated with the service. When a customer orders a new service or upgrades an existing one, the installed base module may automatically add new order information.

  At (4), information regarding the order is communicated to the TAS module 204. In one embodiment, the TAS module 204 utilizes order information to orchestrate service and resource provisioning for orders placed by customers. In (5), the TAS component 204 orchestrates the provisioning of resources to support subscribed services using the services of the SDI module 206. At (6), the TAS module 204 provides the service module 202 with information related to the provisioned order received from the SDI module 206. In (7), in some embodiments, the SDI module 206 may also use the services provided by the service module 202 to allocate and configure the resources necessary to fulfill the customer's subscription order. .

  At (8), service module 202 sends a notification on the status of the order to the customer on client devices 224, 226 and 228.

  In particular embodiments, the TAS module 204 acts as an orchestration component that manages the business processes associated with one another and applies business logic to determine whether to proceed with provisioning an order. In one embodiment, upon receiving a new subscription order, the TAS module 204 requests the SDI module 206 to allocate resources and configure those resources necessary to fulfill the subscription order. Send The SDI module 206 enables allocation of resources for services ordered by the customer. The SDI module 206 provides a level of abstraction between the cloud services provided by the cloud infrastructure system 100 and the physical implementation layer used to provision the resources to provide the requested service. Do. Thus, the TAS module 204 can be decoupled from implementation details such as whether services and resources are actually provisioned on the fly, or whether they are pre-provisioned and simply allocated / assigned on demand.

  In particular embodiments, a user may interact directly with the order management module 214 to use the store UI 210 to perform billing and accounting related functions such as order validation and order booking upon validation. In some embodiments, instead of the customer placing an order, at (9) the order may instead be placed by the sales staff 218 representative of the customer, such as a customer service representative or sales representative. . Sales staff 218 may interact directly with order management module 214 via a user interface (not shown in FIG. 2) provided by order management module 214 to place an order or provide a quote to the customer. . For example, this may be done for large customers where orders may be made by a customer sales representative via order management module 214. The sales representative may prepare a subscription on behalf of the customer.

  The EM module 208 is configured to monitor activities associated with managing and tracking customer subscriptions in the cloud infrastructure system 100. The EM module 208 collects usage statistics for services in subscription orders, such as the amount of storage used, the amount of data transferred, the number of users, the amount of system up time and system down time. In (10), the host operator staff 220, who may be an employee of the provider of the cloud infrastructure system 100, is an enterprise manager user to manage systems and resources for which services are provisioned within the cloud infrastructure system 100. It may interact with the EM module 208 via an interface (not shown in FIG. 2).

  Identity management (IDM) module 200 is configured to provide identity services, such as access management and authorization services, in cloud infrastructure system 100. In one embodiment, the IDM module 200 controls information about customers who want to use the services provided by the cloud infrastructure system 100. Such information is information that authenticates the identity of such customers, and what actions they perform against various system resources (eg, files, directories, applications, communication ports, memory segments, etc.) It may contain information that indicates whether it is authorized. Also, the IDM module 200 may include management of descriptive information about each customer and descriptive information about how the descriptive information may be accessed and modified by whom.

  In one embodiment, the information managed by identity management module 200 can be split to create separate identity domains. Information belonging to a particular identity domain can be decoupled from all other identity domains. Also, an identity domain can be shared by multiple distinct tenants. Each such tenant may be a customer subscribing to a service in the cloud infrastructure system 100. In some embodiments, a customer can have one or more identity domains, and each identity domain can be associated with one or more subscriptions, and each subscription can be one or more. Have a service. For example, a single customer may represent a large enterprise, and an identity domain may be created for the departments / departments within this large enterprise. Additionally, the EM module 208 and the IDM module 200 may interact with the order management module 214 at (11) and (12), respectively, to manage and track customer subscriptions in the cloud infrastructure system 100.

  In one embodiment, at (13), support services may also be provided to the customer via the support UI 216. In one embodiment, the support UI 216 allows support staff to interact with the order management module 214 via the support backend system to perform support services at (14). Support staff and customers in the cloud infrastructure system 100 can submit bug reports and check the status of these reports via the support UI 216.

  Other interfaces not illustrated in FIG. 2 may also be provided by the cloud infrastructure system 100. For example, an identity domain administrator may use a user interface to the IDM module 200 to configure domain and user identity. Also, customers can log in to a separate interface for each service they want to use. In particular embodiments, customers who wish to subscribe to one or more services provided by cloud infrastructure system 100 may also be assigned various roles and assignments. In one embodiment, the various roles and duties that may be assigned to customers may be: buyers, account administrators, service administrators, identity domain administrators, or users of services and resources provided by the cloud infrastructure system It may include roles and missions. The various roles and missions are more fully illustrated in FIG. 4 below.

  FIG. 3A shows a simplified flowchart 300 that illustrates the processing that may be performed by the TAS module in a cloud infrastructure system according to an embodiment of the present invention. The processing illustrated in FIG. 3A may be implemented in software (eg, code, instructions, program) executed by one or more processors, hardware, or a combination thereof. The software may be stored in memory (eg, on a memory device, non-transitory computer readable storage medium). The specific sequence of process steps shown in FIG. 3A is not intended to be limiting. Other sequences of steps may also be performed according to alternative embodiments. For example, alternative embodiments of the invention may perform the above steps in a different order. Furthermore, the individual steps shown in FIG. 3A may include multiple sub-steps that may be performed in various sequences as appropriate to the individual steps. In addition, further steps may be added or deleted depending on the particular application. One of ordinary skill in the art would recognize many variations, modifications, and alternatives. In one embodiment, the process shown in FIG. 3A may be performed by one or more components in TAS component 204, as shown in detail in FIG. 3B.

  At 302, a customer's subscription order is processed. The process may include, in one example, authentication of the order. The authentication of the order guarantees that the customer has paid for the subscription and that the customer does not yet have a subscription with the same name, or Including guaranteeing that the customer has not attempted to create multiple subscriptions of the same type in the same identity domain for unauthorized subscription types etc. The processing may also include tracking the status of the order for each order being processed by the cloud infrastructure system 100.

  At 304, the business process associated with the order is identified. In some examples, multiple business processes may be identified for an order. Each business process identifies a series of steps to process various aspects of the order. As an example, a first business process may identify one or more steps associated with provisioning of physical resources for an order, and a second business process creates an identity domain with a customer identity for the order The third business process may relate to performing back office functions such as creating customer records for the user, performing accounting functions related to the order, etc., which may identify one or more steps related to One or more steps may be identified. In particular embodiments, different business processes may also be identified to process different services in the order. For example, various business processes may be identified to process CRM services and database services.

  At 306, the business process identified for the order at 304 is performed. Execution of the business process associated with the order may include an orchestration of a series of steps associated with the business process identified in step 304. For example, the execution of business processes related to provisioning of physical resources for an order sends a request to the SDI module 206 to allocate resources and configure those resources necessary to fulfill a subscription order May be included.

  At 308, a notification regarding the status of the provisioned order is sent to the customer. Further discussion related to the implementation of steps 302, 304, 306 and 308 is described in detail in FIG. 3B.

  FIG. 3B shows a simplified high level diagram of one or more submodules in a TAS module in a cloud infrastructure system according to an embodiment of the present invention. In one embodiment, the module shown in FIG. 3B performs the processing described in steps 302-308 shown in FIG. 3A. In the illustrated embodiment, the TAS module 204 includes an order processing module 310, a business process identifier 312, a business process executer 316, an excess framework 322, a workflow identification module 324 and a bundled subscription generation module 326. And These modules may be realized in hardware or software or a combination thereof. The various modules of the TAS module shown in FIG. 3B are shown for illustrative purposes only and are not intended to limit the scope of the embodiments of the present invention. Alternative embodiments may include more or less modules than those shown in FIG. 3B.

  In one embodiment, order processing module 310 receives an order from a customer from one or more input sources 321. For example, order processing module 310 may receive orders directly via cloud UI 212 or store UI 210 in one embodiment. Alternatively, order processing module 310 may receive orders from order management module 214 or order database 222. The order processing module 310 then processes the order. In a particular embodiment, processing of the order comprises of customer records including information about the order, such as service type, service level, customer level, type of resource, type of resource allocated to service instance, and time period for which service is sought. Includes generation. As part of processing, order processing module 310 also determines whether the order is a valid order. This is to ensure that the customer does not yet have a subscription with the same name, or (in the case of a fusion CRM service) multiples of the same type in the same identity domain for subscription types not allowed Including guaranteeing that the customer is not trying to create a subscription.

  Also, order processing module 310 may perform further processing on the order. The processing may include tracking the status of the order for each order being processed by the cloud infrastructure system 100. In one embodiment, order processing module 310 may process each order to identify several states associated with the order. In one example, the various states of an order may be an initialization state, a provisioning state, an active state, a state requiring management, an error state, and the like. The initialization state refers to the state of the new order, and the provisioning state refers to the state of the service for the order and the order when the resources were provisioned. Once the order is processed by the TAS module 204 and a notification to that effect is given to the customer, the order is active. Orders need to be managed if manager intervention is required to solve the problem. If the order can not be processed, the order is in error. In addition to maintaining order progress, order processing module 310 maintains detailed information about any failures encountered during the execution of the process. In other embodiments, as described in more detail below, the additional processing performed by the order processing module 310 includes: changing the service level of the service in the subscription, changing the service included in the subscription, the subscription It may also include the extension of time periods and cancellation of subscriptions or specification of different service levels over different time periods in subscription.

  After the order is processed by order processing module 310, business logic is applied to determine whether the order should proceed to provisioning. In one embodiment, as part of the orchestration of an order, the business process identifier 312 receives the processed order from the order processing module 310, applies business logic, and identifies the to be used in the order being processed. Identify the business processes of In one embodiment, business process identifier 312 may utilize information stored in service catalog 314 to determine the particular business process to be used in the order. In one embodiment, as shown in FIG. 3A, multiple business processes may be identified for an order, each business process identifying a series of steps to process various aspects of the order. In another embodiment, different business processes may be defined for different types of services or service combinations, such as CRM services or database services, as described above. In one embodiment, service catalog 314 may store information that maps orders to particular types of business processes. Business process identifier 312 may use this information to identify a particular business process for the order being processed.

  Once the business process is identified, business process identifier 312 communicates to business process executer 316 the particular business process to be performed. The business process executable 316 then executes the identified business process steps by operating in conjunction with one or more modules in the cloud infrastructure system 100. In some embodiments, Business Process Executor 316 acts as an orchestrator to perform the steps associated with the business process. For example, an order processing module such that the business process exporter identifies the workflow associated with the order to determine the excess of service in the order, or performs the steps in the business process identifying the service components associated with the order. It can interact with 310.

  In one example, the business process exporter 316 interacts with the SDI module 206 to perform the steps in the business process to allocate and provision resources for the service requested in the subscription order. In this example, at each step in the business process, the business process exporter 316 may send a request to the SDI component 206 to allocate resources and configure the resources needed to realize the particular step. The SDI component 206 is responsible for the actual allocation of resources. Once all steps of the order's business process have been performed, the business process executer 316 can send notification of the processed order to the customer by utilizing the services of the service component 202. The notification may include sending an email notification with the details of the processed order to the customer. The email notification may also include deployment information associated with the order to enable the customer to access the subscribed service.

  In particular embodiments, the TAS module 204 interacts with other modules in the cloud infrastructure system 100 and allows one or more TAS application programs to interact with the TAS module 204. An interface (Application Programming Interface: API) 318 may be provided. For example, the TAS API interacts with the SDI module 206 via an asynchronous Simple Object Access Protocol (SOAP) based web service call to provision resources for a customer's subscription order. System provisioning API may be included. In one embodiment, the TAS module 204 may also utilize the system provisioning API to accomplish system and service instance creation and deletion, switch service instances to enhanced service levels, and associate service instances. An example of this is the association of a Java service instance to a fusion application service instance to enable secure web service communication. The TAS API may also include a notification API that interacts with the service module 202 to notify the customer of the processed order. In particular embodiments, the TAS module 204 also periodically informs the service component 202 of subscription information, outages and notifications (eg, planned downtime).

  In a particular embodiment, the TAS module 204 uses for each of the provisioned services such as the amount of storage used, the amount of data transferred, the number of users, and the amount of system up time and system down time Statistics are periodically received from the EM module 208. The excess framework 322 uses this usage statistics to order whether this information is used to determine if overuse of the service has occurred, and if so, how much to charge for the excess. It is provided to the management module 214.

  In particular embodiments, the TAS module 204 includes an order workflow identification module 324 configured to identify one or more workflows associated with processing a customer's subscription order. In particular embodiments, the TAS module 204 may generate a subscription order for a customer when the customer places a subscription order for one or more services provided by the cloud infrastructure system 100. A generation framework 326 may be included. In one embodiment, the subscription order includes one or more service components responsible for providing the services requested by the customer in the subscription order.

  In addition, the TAS module 204 can provide a tenant information system to enable provisioning of resources for one or more services subscribed by a customer, taking into account historical information available to the customer, if any. It may also interact with one or more additional databases, such as a Tenant Information System (TIS) database 320. The TIS database 320 may include historical order information and historical usage information related to the orders subscribed by the customer.

  The TAS module 204 may be deployed using various deployment models. In particular embodiments, a deployment includes a central component that interacts with one or more distributed components. The distributed components may be deployed, for example, as various data centers, and may therefore also be referred to as data center components. The central component includes functionality to process orders and organize services in the cloud infrastructure system 100, and the data center component is operable to provision and operate a runtime system that provides resources to subscribed services. I will provide a.

  FIG. 4 illustrates an exemplary distributed deployment of a TAS module according to an embodiment of the present invention. In the embodiment shown in FIG. 4, the distributed deployment of the TAS module 204 includes a TAS central component 400 and one or more TAS data center (DC) components 402, 404 and 406. These components may be realized in hardware or software or a combination thereof.

  In one embodiment, the task of TAS-centric component 400 is to receive customer orders and create new subscriptions, change service levels of services in subscriptions, change in services included in subscriptions, and duration of subscriptions. Including providing a centralized component for performing order-related business operations, such as, extension of, or cancellation of subscriptions, but is not limited thereto. Also, the task of the TAS core component 400 is to maintain and provide subscription data required by the cloud infrastructure system 100, and an order management module 214, support UI 216, to handle all back office interactions. Interchanging with the cloud UI 212 and the store UI 210 may also be included.

  In one embodiment, the duties of TAS DCs 402, 404 and 406 include performing runtime operations to orchestrate the provisioning of resources for one or more services subscribed by the customer, including It is not limited. TAS DCs 402, 404 and 406 also perform operations such as locking, unlocking, enabling or disabling subscription order, collecting metrics related to the order, determining the status of the order, and sending notification events related to the order. Also includes functions for performing

  In the exemplary operation of the distributed TAS system shown in FIG. 4, the TAS central component 400 is initially via the cloud UI 212, store UI 210, via the order management system 214, or via the order database 222. Receive an order from a customer. In one embodiment, the customer corresponds to a buyer with the authority to order and / or modify financial information and subscriptions. In one embodiment, the order information includes information identifying the customer, the type of service the customer wants to subscribe to, and an account administrator who is responsible for handling the request. In particular embodiments, an account administrator may be appointed by a customer when the customer places an order for a subscription to one or more services provided by the cloud infrastructure system 100. Based on the order information, the TAS central component 400 generates a global data area, such as the U.S., EMEA or Asia-Pacific, where the order originates, and the specific TAS DC deployed to provision the order (e.g. 402, 404 or 406). Identify). In one embodiment, the particular TAS DC (eg, from among DCs 402, 404 or 406) deployed to provision the order is determined based on the geographic data region where the request originated.

  The TAS core component 400 then sends the order request to a particular TAS DC to provision services for the order request. In one embodiment, TAS DCs 402, 404, or 406 identify a service administrator and an identity domain administrator responsible for processing order requests in a particular TAS DC. Service Administrators and Identity Administrators may be appointed by the Account Administrator identified in the subscription order. The TAS DCs 402, 404 or 406 communicate with the SDI module 204 to orchestrate the provisioning of physical resources for ordering. The SDI component 206 in each TAS DC 402, 404 or 406 allocates resources and configures those resources necessary to fulfill the subscription order.

  In particular embodiments, TAS DCs 402, 404 or 406 identify an identity domain associated with the subscription. The SDI component 206 may provide identity domain information to the IDM component 200 (shown in FIG. 2) for identification of an existing identity domain or creation of a new identity domain. Once the order is provisioned by the SDI module in each TAS DC 402, 404 or 406, the TAS central component 400 may deploy information regarding the provisioned resources in the support system via the support UI 216. The information may include, for example, an indication of resource metrics associated with the service and usage statistics of the service.

  In operation, at each data center, the EM module 208 determines, for each of the provisioned services provisioned at the data center, the amount of storage used, the amount of data transferred, the number of users, and the system up time And regularly collect usage statistics, such as the amount of system downtime. These statistics are provided to the TAS DC local to the EM module 208 (ie, at the same data center). In an embodiment, the TAS DC uses usage statistics to determine if overuse of the service has occurred, and if so, how much will be charged for the excess, and the charging information It may be provided to the order management system 214.

  FIG. 5 is a simplified block diagram illustrating the interaction of an SDI module with one or more modules in a cloud infrastructure system according to an embodiment of the present invention. In one embodiment, SDI module 206 interacts with TAS module 204 to provision resources for services in the subscription order received by TAS module 204. In particular embodiments, one or more of the modules shown in FIG. 5 may be modules within cloud infrastructure system 100. In other embodiments, one or more of the modules that interact with SDI module 206 may be outside of cloud infrastructure system 100. Also, alternative embodiments may have more or less modules than those shown in FIG. These modules may be realized in hardware or software or a combination thereof.

  In one embodiment, the modules in SDI module 206 may include SaaS platform 102 in cloud infrastructure system 100 and one or more modules in PaaS platform 104. To provision resources for various services, SDI module 206 may interact with various other modules that are each customized to help provision resources for particular types of services. For example, as shown in FIG. 5, SDI module 206 may interact with Java service provisioning control module 500 to provision Java cloud services. In one embodiment, Java service provisioning control component 500 deploys a Java Cloud Service (JCS) assembly defined by SDI module 206 that includes a set of tasks performed to provision Java cloud services. It can. Infrastructure resources 106 then determine the resources needed to provision the Java cloud service.

  As another example, the SDI module 206 can be a Virtual Assembly Builder (VAB) module 502, an Application Express (APEX) deployer module 504, a Virtual Machine (VM) module 506, an IDM. It may interact with one or more modules, such as module 200 and database machine module 118. The VAB module 502 includes functionality to configure and provision a complete multi-tier application environment. In one embodiment, the VAB module 502 uses the MW service defined by the SDI module 206 to provision middleware (MW) services in the cloud infrastructure system 100 using the services provided by the VM module 506. Deploy the assembly APEX deployer module 504 includes functionality for configuring and provisioning database services. In one embodiment, the APEX deployer module 504 deploys the database service assembly defined by the SDI module 206 to provision database services in the cloud infrastructure system 100 using resources provided by the infrastructure resource 106. Do. The SDI module 206 interacts with the IDM module 200 to provide identity services such as access management across applications in the cloud infrastructure system 100.

  FIG. 6 shows a simplified high level diagram of the submodules of the SDI module according to an embodiment of the present invention. In the embodiment shown in FIG. 6, the SDI module 206 includes an SDI-Web Service (Web Service) module 600, an SDI request controller module 602, an SDI task manager module 604, an SDI monitoring module 606, and SDI data. An access module 608, an SDI common library module 610, and an SDI connector module 612 are included. These modules may be realized in hardware or software or a combination thereof. The SDI module 206 and its various modules shown in FIG. 6 are shown for illustrative purposes only and are not intended to limit the scope of embodiments of the present invention. Alternative embodiments may have more or less modules than those shown in FIG. These modules and their functions are described in detail below.

  The SDI-WS module 600 includes functionality from the Business Process Executor 316 of the TAS component 204 to receive steps in the business associated with the order. In one embodiment, the SDI-WS module 600 parses each step of the business process and converts the step to an internal representation used by the SDI module 206. In one embodiment, each step of the business process associated with the order is in the form of a SOAP request to the SDI-WS module 600 via the web service processing layer (eg via the system provisioning API shown in FIG. 3B) )arrive.

  The SDI request controller module 602 is an internal request processing engine in the SDI module 206 and functions to perform asynchronous request processing, simultaneous request processing, simultaneous task processing, fault tolerant recovery and plug-in support related to order requests. including. In one embodiment, the SDI request controller module 602 accepts each step of the business process associated with the order from the SDI-WS module 600 and submits the steps to the SDI task manager module 604.

  The SDI task manager module 604 translates each step defined in the business process into a series of tasks for provisioning a particular step. Once a set of tasks for a particular step has been provisioned, the SDI task manager module 604, with the operation result including an order payload with details of the resources provisioned to realize the particular step, causes the TAS module 204 to In response to the business process executor 316 in The SDI task manager module 604 repeats this process until all steps of the particular business process associated with the order are complete.

  In particular embodiments, SDI task manager module 604 translates each step defined in the business process into a series of tasks by utilizing the services of SDI connector module 612. The SDI connector module 612 includes one or more connectors to handle the deployment of tasks defined by the SDI task manager module 604 to provision one or more services related to the order request. In particular embodiments, one or more of the connectors may handle tasks specific to a particular service type, and other connectors may handle common tasks across various service types. In one embodiment, the SDI connector module 612 interacts with one or more of the external modules (shown in FIG. 5) in the cloud infrastructure system 100 to provision services and resources associated with the order request. Includes connector (wrapper API). For example, application express (APEX) connector 614 interacts with APEX deployer module 504 to provision database services. A web center connector 616 (Web Center Connector: WCC) interacts with a web center module in the cloud infrastructure system 100 to provision web services. The web center module is a user engagement platform and includes functions for providing connectivity between people and information in the cloud infrastructure system 100.

  In particular embodiments, the middleware application (MA) connector 618 interacts with the VAB module 502 in the cloud infrastructure system 100 to provision middleware application services. The NUVIAQ connector 620 interacts with the VAB module 502 to provision Java services. The IDM connector 622 interacts with the IDM module 200 to provide identity and access management to users subscribing to services and resources in the cloud infrastructure system 100. A virtual assembly builder (VAB) connector 624 interacts with the VAB module 502 in the cloud infrastructure system 100 to configure and provision a complete multi-tier application environment. The plug-in connector 626 interacts with the EM module 208 to manage and monitor components in the cloud infrastructure system 100. The HTTP server connector 628 interacts with one or more web servers in the PaaS platform to provide connectivity services to users in the cloud infrastructure system 100.

  The SDI monitoring module 606 in the SDI module 206 provides an inbound interface for receiving Java Management Extensions (JMX) requests. The SDI monitoring module 606 also provides tools for managing and monitoring applications, system objects and devices in the cloud infrastructure system 100. The SDI data access module 608 provides an inbound interface for receiving Java Database Connectivity (JDBC) requests. The SDI data access module 608 supports data access in the cloud infrastructure system 100 and provides object relationship mapping, java transaction API services, data access objects and connection pooling. The SDI common library module 610 provides configuration support for the modules in the SDI module 206.

  The embodiment of FIG. 6 above describes a module in an SDI module according to an embodiment of the present invention. FIG. 7A shows a simplified flowchart 700 that illustrates the processing that may be performed by the modules of the SDI module in the cloud infrastructure system according to an embodiment of the present invention. The process illustrated in FIG. 7A may be implemented by software (eg, code, instructions, program) executed by one or more processors, hardware, or a combination thereof. The software may be stored in memory (eg, on a memory device, non-transitory computer readable storage medium). The particular sequence of process steps shown in FIG. 7A is not intended to be limiting. Other sequences of steps may also be performed according to alternative embodiments. For example, alternative embodiments of the invention may perform the above steps in a different order. Furthermore, the individual steps shown in FIG. 7A may include multiple sub-steps that may be performed in various sequences as appropriate to the individual steps. In addition, further steps may be added or deleted depending on the particular application. One of ordinary skill in the art would recognize many variations, modifications, and alternatives. In one embodiment, the process shown in FIG. 7A may be performed by one or more modules in SDI module 206 shown in detail in FIG.

  At 702, the business process associated with the subscription order is received. In one embodiment, the SDI-WS module 600 in the SDI module 206 receives one or more steps in the business process associated with the subscription order from the business process executer 316. At 704, each step in the business process is converted into a series of tasks for provisioning resources for a subscription order. In one embodiment, the SDI task manager module 604 in the SDI module 206 converts each step defined in the business process into a series of tasks by utilizing the services of the SDI connector module 612. At 706, subscription orders are provisioned based on a series of tasks. In one embodiment, as shown in FIG. 6, the SDI connector module 612 handles the deployment of tasks defined by the SDI task manager module 604 to provision resources for services in subscription orders. Including one or more connectors.

  As described above with respect to FIG. 6, the SDI task manager module 604 translates each step defined in the business process into a series of tasks by utilizing the services of the SDI connector module 612, and the SDI connector module 612 orders One or more connectors may be included to handle the deployment of tasks defined by the SDI task manager module 604 to provision one or more services associated with the request. One or more of the connectors can handle tasks specific to a particular service type, and other connectors can handle common tasks across different service types. In one embodiment, the SDI connector module 612 interacts with one or more of the external modules (shown in FIG. 5) in the cloud infrastructure system 100 to provision services and resources associated with the order request. Includes connector (wrapper API). For example, the NUVIAQ connector 620 interacts with the VAB module 502 to provision Java services.

  FIG. 7B shows a simplified block diagram illustrating a high level architecture of Nuviaq system 710 and its relationship with other cloud infrastructure systems according to an embodiment of the present invention. It should be understood that the Nuviaq system 710 shown in FIG. 7B may have other components besides those shown in FIG. 7B. Furthermore, the embodiment shown in FIG. 7B is only one example of a cloud infrastructure system that can incorporate an embodiment of the present invention. In some other embodiments, Nuviaq system 710 may have more or less components than those shown in FIG. 7B, may combine two or more components, or It may have different configurations or arrangements.

  In particular embodiments, Nuviaq system 710 may be configured to provide a run-time engine for orchestrating PaaS operations. The Nuviaq system 710 may provide a web service API to facilitate integration with other products and services. The Nuviaq system 710 also provides support for complex workflows in system provisioning, application deployment and associated lifecycle operations, and integrates with management and monitoring solutions.

  In the embodiment shown in FIG. 7B, the Nuviaq system 710 comprises a Nuviaq proxy 712, a Nuviaq manager 714, and a Nuviaq database 716. In particular embodiments, Nuviaq manager 714 provides an entry point to Nuviaq system 710 and provides secure access to PaaS operations via a web services API. Internally, the Nuviaq manager 714 tracks system state in the database and controls the execution of jobs on the workflow engine. In the public cloud, the Nuviaq manager 714 can be accessed by the tenant provisioning system (SDI 206) and the tenant console to drive provisioning and deployment operations, respectively.

  In one embodiment, Nuviaq manager 714 executes jobs asynchronously through the internal workflow engine. The job may be a sequence of actions specific to a given PaaS workflow. The actions may be performed sequentially, and failure at any step results in failure of the entire job. Many workflow actions delegate authority to external systems related to workflow, such as the EM command line interface (cli). In one implementation, the Nuviaq manager 714 application may be hosted in a two-node web logic cluster with an associated HTTP server (eg, an Oracle HTTP server or OHS) instance running within a firewall.

  In particular embodiments, Nuviaq proxy 712 is a public access point to the Nuviaq API. In one embodiment, only public APIs may be published here. The request received by proxy 712 may be sent to Nuviaq manager 714. In one embodiment, Nuviaq proxy 712 runs outside the firewall while manager 714 runs inside the firewall. In one implementation, the Nuviaq proxy 712 application is run on a web logic cluster that runs outside the firewall.

  In particular embodiments, the Nuviaq database 716 tracks various domain entities such as, but not limited to, platform instances, deployment plans, applications, web logic domains, jobs, alerts and the like. Primary keys may be aligned with the service database, if desired.

  In one embodiment, platform instance 718 may include all the resources needed for the web logic service for a given tenant.

  The Nuviaq system 710 may rely on additional systems of the cloud infrastructure system 100 to perform the workflows used by the web logic cloud service. These dependencies may include dependencies on SDI 206, IDM 200, virus scanning systems, service databases, CRM instances, etc. For example, Nuviaq system 710 may rely on the functions performed by the assembly deployer at SDI 206. In one embodiment, the assembly deployer is a system for managing interactions with the Oracle Virtual Assembly Builder (OVAB) and the Oracle Virtual Machine (OVM). The functions of the assembly deployer used by the Nuviaq system 710 may include functions for deploying an assembly, functions for undeploying an assembly, functions for describing an assembly deployment, functions for scaling an appliance, etc. However, it is not limited to these. In one implementation, Nuviaq system 710 accesses the assembly deployer via a web service API.

  In certain embodiments, security policies may require that certain artifacts be virus scanned before being deployed to an application. Cloud infrastructure system 100 may provide a virus scanning system for this purpose, providing scanning as a service for multiple components of a public cloud.

  In particular embodiments, the public cloud infrastructure may maintain a services database that includes information about tenants (eg, customers) and their service subscriptions. The Nuviaq workflow can access this data to properly configure the weblogic service as a client to other services that also subscribe to the tenant.

  Nuviaq system 710 may rely on IDM 200 for its security integration. In particular embodiments, a Java service instance may be associated with a CRM instance. The association allows the user application deployed to the Java service instance to access the CRM instance via the web service call.

  Various entities may use the services provided by the Nuviaq system 710. These clients of Nuviaq system 710 have access to application life cycle management operations, tenant consoles, which are management server (eg Oracle management server) based user interfaces that customers can access to manage applications on platform instances. Some IDEs, such as the Oracle IDE (JDeveloper, NetBeans and OEPE), which has been extended to provide an API, and one or more command line interfaces (Command Line) available to access lifecycle operations on platform instances Interface: CLI) may be included.

The provisioning use case for Nuviaq system 710, ie, the use case of a provisioning platform instance, is realized by the creation platform instance operation of the Nuviaq API. In the context of cloud infrastructure system 100, the service instance for the Nuviaq system corresponds to the Nuviaq platform instance. The platform instance is assigned a unique identifier that is used on all subsequent operations associated with this instance. The platform deployment descriptor provided in the create platform instance action allows to set properties that modify the configuration of the platform instance to meet the tenant's subscription requirements. These properties may include, for example:
Property # 1 : oracle.cloud.service.weblogic.size
Values: Basic, Standard, Enterprise Description: Defines the subscription type. This affects the number of servers, database limits and quality of service settings.

Property # 2 : oracle.cloud.service.weblogic.trial
Values: True, False Description: Indicates whether this is a trial subscription.

Property # 3 : oracle.cloud.service.weblogic.crm
Value: CRM Service ID
Description: Identifies the CRM service to be associated with this web logic service instance.

  FIG. 7C shows an exemplary sequence diagram showing steps of a provisioning process using the Nuviaq system according to an embodiment of the present invention. The sequence diagram shown in FIG. 7C is merely an example and is not intended to be limiting.

The install / update application use case, i.e. install application operation, deploys the application to a running weblogic server after confirming that the application archive meets the public cloud security requirements. In one embodiment, the application deployment descriptor provided in the install application action can set properties that modify the configuration of the application to meet the subscription requirements of the tenant. These properties may include, for example:
Property : oracle.cloud.service.weblogic.state
Values: Execution, Stop Description: Defines the initial state of the application after deployment.

  FIG. 7D shows an exemplary sequence diagram showing steps of a deployment process using the Nuviaq system according to an embodiment of the present invention. The sequence diagram shown in FIG. 7D is merely an example and is not intended to be limiting.

Returning to FIG. 2, in certain embodiments, the cooperating TAS 204 and SDI 206 may be for one or more services ordered by a customer from a set of services provided by the cloud infrastructure system 100. Responsible for provisioning resources. For example, in one embodiment, to provision a database service, the automated provisioning flow may be as follows for a paid subscription:
(1) The customer places an order for a paid subscription of the service via the store UI 210.

(2) TAS 204 receives a subscription order.
(3) When the service is available, the TAS 204 starts provisioning by using the service of the SDI 206. The TAS 204 may perform business process orchestration, and execute related business processes to complete the provisioning phase of the order. In one embodiment, TAS 204 may use a BPEL (Business Process Execution Language) process manager to orchestrate the steps involved in provisioning and to handle life cycle operations.

  (4) In one embodiment, to provision a database service, SDI 206 may call the PLSQL API in CLOUD_UI to associate a schema with the requesting customer.

  (5) After successfully associating the schema with the customer, SDI informs TAS, which sends a notification to the customer that the database service is currently available for use by the customer.

  (6) The customer may log into the cloud infrastructure system 100 (eg, using a URAL such as cloud.oracle.com) and launch the service.

  In some embodiments, customers may also be authorized to subscribe to services on a trial basis. For example, such trial orders may be received via the cloud UI 212 (eg, using cloud.oracle.com).

  In particular embodiments, cloud infrastructure system 100 enables basic hardware and service instances to be shared among customers or tenants. For example, a database service may be provisioned in one embodiment as shown in FIG. 7E. FIG. 7E shows a plurality of Exadata compute nodes 730 and 732, each of compute nodes 730 and 732 providing a database instance provisioned for database service. For example, computing node 730 provides database instance 734 for a database service. Each Exadata operation node may have multiple database instances.

  In particular embodiments, each database instance may comprise multiple schemas, which may be associated with different customers or tenants. For example, in FIG. 7E, database instance 734 provides two schemas 736 and 738, each of schemas 736 and 738 having its own table. The schema 736 can be associated with a first customer or tenant subscribing to a database service, and the schema 738 can be associated with a second customer or tenant subscribing to a database service. Each tenant gets a completely disconnected schema. Each schema acts like a container that can manage database objects, including tables, views, stored procedures, triggers, etc. for associated tenants. Each schema may have one dedicated tablespace, and each tablespace has one data file.

  Thus, a single database instance can provide database services to multiple tenants. This enables not only sharing of basic hardware resources but also sharing of service instances between tenants.

  In certain embodiments, such a multi-tenancy system is facilitated by the IDM 200, whereby hardware and multiple separate customers, each with its own separate identity domain, are shared in the cloud It is advantageously possible to use software. As a result, each customer does not have to have their own dedicated hardware or software resources, and in some cases, resources not used by some customers at a particular time may be made available to other customers. It prevents their resources from being wasted. For example, as shown in FIG. 7E, database instances can be provisioned to multiple customers, each having a respective identity domain. Each such database service instance may be a separate abstraction or view of a single physical multi-tenant database system shared among many separate identity domains, but each such database Service instances can have schemas that are different and possibly different from those that each other database service instance has. Thus, the multi-tenant database system may store mappings between customer-specified database schemas and the identity domains to which those database schemas relate. The multi-tenant database system may cause database service instances for a particular identity domain to use a schema that is mapped to that particular identity domain.

  Also, multi-tenancy can be extended to other services, such as Java services. For example, multiple customers may have JAVA service instances located within their respective identity domains. Each such identity domain may have a JAVA virtual machine that can be considered as a virtual "slice" of hardware. In one embodiment, the job monitoring service (e.g., Hudson) allows JAVA in the cloud to allow each distinct identity domain to have its own distinct virtual "slice" of the JAVA enterprise edition platform. It may be combined with an enterprise version platform (eg Oracle Web Logic). Such job monitoring services may monitor the execution of recurring jobs, such as the construction of software projects or jobs performed by, for example, a time-based job scheduler of the operating system. Such repeated jobs may include continuous construction and / or testing of the software project. Additionally or alternatively, such repeated jobs may include monitoring of the execution of operating system launch jobs that are executed on a machine remote from the machine on which the job monitoring service is performed.

Reusable Anonymous Subscription (RAS)
In certain embodiments, the cloud infrastructure system 100 not only allows underlying hardware and service instances to be shared among customers or tenants, but also does not fully provision new resources. Allows other customers or tenants to reuse existing subscriptions. In one aspect, Reusable Anonymous Subscription (RAS) is a type of subscription that allows customers to access this service, which has already been provisioned prior to requesting access to the service. In some embodiments, the RAS may have been used by other customers to access the service. The RAS may be reassigned to another customer after being used for access to the service. The resources of services accessible using RAS may remain provisioned for this RAS for reuse by other customers given the RAS.

  In some embodiments, RAS allows customers to use this service before purchasing a subscription for the service (eg, a full subscription). The access provided by the service to the RAS may be different (eg, may be restricted) than the access provided by the service to the regular subscription. For example, the RAS may allow the customer to access the service as a guest for temporary use (eg, testing or trial use) prior to purchase of a subscription for the service. RAS will help enable customers to try out the service without actually paying for it.

  In some aspects, the RAS may be configured to be different than a regular subscription, such that the purpose of using the RAS is to try a service. In some embodiments, the RAS may not provide all of the features available to customers who have regular subscriptions assigned. In one example, operation updates and extensions may not be supported for RAS. That is, the customer can not add new features or increase the size of the RAS (eg, number of users). On the other hand, customers who have been assigned regular subscriptions may have access to some or all of these features. In another example, a customer assigned a RAS may not be able to utilize support such as high availability and disaster recovery features (eg, such support may be disabled). In another example, the RAS may not allow the gradual deployment of services accessed by customers of the RAS. In staged deployment, the configuration of subscriptions is changed based on a predefined deployment plan. In another example, customers of RAS may not be allowed to incur an excess. In another example, a customer assigned a RAS may not be able to use notifications, such as alerts associated with usage.

  If the customer decides not to convert the RAS to a full subscription, the RAS can be reassigned to another customer for reuse of this RAS. The service provisioned for this RAS will remain provisioned when the customer returns the RAS. In this way, the time taken to provision new resources for the service is minimized and resource usage is maximized.

  If the customer agrees to obtain a regular subscription for a service accessed using RAS, the cloud infrastructure system 100 may convert the RAS into a regular subscription. In various embodiments, cloud infrastructure system 100 may implement a conversion process (e.g., a lightweight personality injection process) for converting a RAS to a regular subscription. The conversion process keeps the resources of the service provided by the RAS from being re-provisioned by keeping the resources provisioned to the RAS. As such, RAS can be very useful for complex products (eg, CRM systems) that are provisioned using a weight process. The conversion process may maintain customer generated data using services accessed via RAS. The customer data held may be used by customers of the service accessed by the regular subscription. By retaining the customer data, the customer can save time and resources required to regenerate the customer data based on the customer's use of the service.

  In another aspect, customer-specific data generated during use of a service provided by the RAS may be separated from data for service-related in relation to the service provided by the RAS. In some embodiments, if the RAS is not converted to a regular subscription, then the data for a particular service about the service provided by this RAS may be maintained in association with the RAS, and the data for a particular customer may be The correspondence relationship of may be cancelled. When RAS is converted to a regular subscription, data for a specific customer may be held and mapped to the regular subscription. Thus, a user who has been provided a regular subscription can continue using the service with existing customer-specific data generated when accessing the service using RAS. RAS can be distinguished from trial subscriptions, which are usually not reusable by different customers. The trial subscription is released at the end of the trial period.

  Referring now to Figures 8A-8C, various embodiments for providing a customer with a RAS in accordance with some embodiments of the present embodiments are shown. FIG. 8A shows a simplified block diagram of a system environment 800 for providing reusable anonymous subscriptions in accordance with some embodiments of the present invention. FIG. 8B illustrates an example data structure for implementing reusable anonymous subscriptions in accordance with some embodiments of the present invention. FIG. 8C is a flowchart of a process for managing the life cycle of reusable anonymous subscriptions in accordance with various embodiments.

  In FIG. 8A, several customers, such as customer 1, customer 2, and customer 3, are associated with client device 224, client device 226, and client device 228, respectively, for communication with cloud infrastructure system 100. In addition, a system environment 800 is shown. Cloud infrastructure system 100 may manage one or more service pools (eg, service pool 810) of RAS subscriptions for customers. Service pool 810 may include one or more RASs, such as RAS 812 (“RAS1”), RAS 814 (“RAS 2”), and RAS 816 (“RAS 3”), each available for assignment to a customer. In some embodiments, one or more service pools (eg, RAS pools) may be created to provide RAS to allow access to services that have already been provisioned.

  In various embodiments, service pools may be constructed based on configurations or templates (eg, product templates). For example, service pools may be built and maintained for specific product configurations. If the customer needs a RAS for a product configuration that does not have a RAS pool, create a new service for this product configuration and add a new RAS to this service pool. If one or more additional RASs are created for the same product configuration in the future, these RASs may also be added to the above service pool. The template may incorporate resource constraints (e.g., limitations on the number of users, limitations on storage, etc.) imposed on access to the product (e.g., service). For example, one service pool may be configured based on a product configuration template for a database as a service (DBAAS) product, and another service pool based on a product configuration template for a CRM service product It may be configured. In some embodiments, the service pool may include other pools, each of which is further defined based on a category. In the previous example, the service pools for the DBAAS service pool may have separate service pools, each providing different types of RAS for the DBAAS, such as DBAAS Basic, DBAAS Standard, and DBAAS Enterprise. Alternatively, separate pools may be created for different types of subscriptions, either for the same product or different products.

  In some embodiments, service pools may be mapped or classified based on one or more criteria. This criterion may indicate the template used to configure the service pool. The template may be based on the type of service, the resources provisioned for the service made available by the service pool, the type of subscription, the number of subscriptions, the availability of resources, etc. A service corresponding to each RAS in the service pool may be provisioned before a subscription order for services in the service pool is processed.

  In one aspect, the templates used to define the service pool may be determined based on feedback provided by various components of the cloud infrastructure system 100. For example, it may be used to determine the rate at which customers place orders and to reflect on the number of subscriptions assigned to the pool. In another example, the type of service may be used to allocate X subscriptions for the first type and a different number of subscriptions for the second type. Other performance, marketing, and customer related metrics can be used to determine the number of available subscriptions and to determine how to reassign these subscriptions. Further, the cloud infrastructure system 100 can dynamically increase or decrease the number of available RAS in the service pool based on analysis of feedback determined by the cloud infrastructure system 100.

  In some embodiments, RAS can also be created based on customer-specific product templates configured based on customer needs. The customer-specific RAS may be stored in a service pool designated for one or more customers. In some embodiments, the customer-specific RAS may be reused by other customers who have a need to be met by the customer-specific RAS. In some embodiments, service pools may be created for services configured as a customer-specific RAS. Another RAS created as a customer-specific RAS in a similar configuration may be added to the service pool. The customer-specific RAS may be stored in a service pool designed for the customer who has configured this customer-specific RAS.

  As described above, the TAS module 204 of the cloud infrastructure system 100 manages the business process associated with each subscription order and applies business logic to determine whether the subscription order should proceed to provisioning. Act as an orchestration component. The TAS module 204 handles the processing for processing subscription orders based on customer requirements for services. In some embodiments, the TAS module 204 can determine whether a request for service (eg, request 802) to which the RAS can provide access has been made. The TAS module 204 may build an environment for the requested service based on the type of use indicated by the customer request. The TAS module 204 can determine that a RAS has been requested based on the specified request for the RAS indicated by the request received from the customer.

  A request for service (eg, request 802) from cloud infrastructure system 100 may include information that may be used to provide the service. Specifically, the request may include information (e.g., order information) that enables cloud infrastructure system 100 to determine which RAS to provide the customer for the requested service. In some embodiments, the request may indicate the type of service or type of intended use for the requested service. Types of use include, but are not limited to, development, testing, training, prototyping, load balancing, marketing, sales, design, production, and the like.

  In some embodiments, the request may indicate one or more requirements for the requested service. This requirement may include: rate restrictions (eg minimum and / or maximum charges), time restrictions on the use of the requested service, the amount of users using this service, the type of service support desired, other related to the use of the service Requirements, or combinations of these. The cloud infrastructure system 100 may determine the subscriptions provided to the customer to enable access to the requested service based on the requirements indicated by the request from the customer. At least one example of a subscription provided to a customer may be RAS.

  The TAS module 204 may implement operations to establish a RAS that allows access to the requested service. In the example shown in FIG. 8A, cloud infrastructure system 100 may determine whether the requested service has been provisioned for RAS in one or more service pools (eg, service pool 810). Whether the available subscriptions provide access to the requested service by analyzing the available subscriptions (eg RAS) in one or more service pools by performing the process You may judge. The service pool may include multiple RASs. Each RAS can be assigned to a customer when this RAS is available. By examining each RAS, the resources and / or services provided by this RAS may be determined. Subscriptions such as RAS are based in part on the information determined from the request (eg, the type of subscription requested by the customer, the type of use of the requested service, the duration of the requested service, or a combination of these). May be identified within the service pool.

  In some embodiments, service pools may be constructed for specific geographic locations (e.g., geographic regions). The geographical position may be determined based on the geographical position of the data center. Service pools may be built for geographic locations for legal and / or compliance reasons. A service pool may be constructed for a geographic location if the service pool is not built for this geographic location. In some embodiments, service pools built at certain geographic locations may be further defined based on product configuration. For example, service pools may be built for certain geographic locations for RAS with specific product configurations. In such an embodiment, if there is no existing service pool in the geographic location defined for this new RAS product configuration for the new RAS, then there is no service pool for that geographic location. You may create it.

  When it is not possible to find a RAS that matches the customer's request, a new RAS can be provisioned based on the customer's request. Add the newly provisioned RAS to the appropriate service pool. The service pool may be expanded to include a new RAS to meet customer needs. The new RAS can then be assigned to the customer.

  In some embodiments, provisioned RAS may not be added to an existing service pool. For example, the RAS may not be added to the service pool when the existing service pool is full due to resource capacity. In some embodiments, the RAS may not be added to the service pool when the provisioned RAS product configuration does not fit into the service pool classification. The RAS in the existing service pool may be configured for a subscription type or usage type that does not match the new RAS configuration, in one example, provisioned RAS, RAS product configuration If the application does not match the product configuration of the existing service pool, it may not be assigned to the existing service pool. In some embodiments, the newly created RAS product configuration is existing because the product configuration of this new RAS is different from the product configuration of each of the existing service pools. It may not match the product configuration of each service pool. In such a case, a new service pool may be constructed on demand.

  In some embodiments, the service pool may be for a specific customer, and the service pool may include RAS configured according to a custom template for a customer. In this embodiment, RASs in such a service pool may be assigned only to specific customers designated for this service pool.

  In some embodiments, determining whether the requested service has been provisioned may include determining a service pool corresponding to a type of service pool. The type of service pool may be identified based on the information indicated by the request from the customer. For example, the type of service pool may include the requested service, the type of subscription requested by the customer (eg, RAS subscription), the type of use of the requested service, or a combination of these. The request may indicate any or all of these.

  In one example shown in FIG. 8A, the TAS module 204 may send one or more RAS in the service pool 810, eg, RAS2 814 and RAS3 816, to a customer (eg, customer 1) for one or more requested services. It may be determined whether it can be used for allocation. The TAS module 204 assigns 822 the first RAS (eg RAS2 814) to the first service for the first service and operation 824 for assigning the second RAS (eg RAS3 816) to the customer 1 for the second service. It can be realized. Subscriptions assigned to a customer, such as subscription 830 ("Customer 1 Subscription") may be held in storage associated with this customer. In some embodiments, data for a specific customer associated with a service accessed using RAS may be stored in association with data related to the service (for example, data for a specific service). An example data structure for storing subscriptions is described with reference to FIG. 8B.

  The RAS may be returned to the service pool when the customer has finished using this RAS. In some embodiments, the RAS may be mapped to one or more requirements associated with the use of this RAS. For example, this requirement may relate to the use of resources enabled for RAS or to a time period to enable access to services. The RAS may be returned to the service pool when the requirements of the RAS are met. For example, RAS3 816 may be returned 826 to service pool 810. The data for specific service associated with RAS3 816 may be stored in the storage area, while the data for specific customer generated by customer 1 using RAS3 816 may be discarded. Reverting the RAS may include assigning the RAS to a service pool. In some embodiments, the RAS may be returned to the service pool that acquired the RAS. However, the RAS may revert to a different service pool based on the assignment of the RAS to the service pool.

  Cloud infrastructure system 100 may convert the assigned RAS into a regular subscription (RS). The RAS may not be returned to the service pool if this RAS is converted to RS. The RAS may be converted to RS based on the input received from the client device operated by the customer. In some embodiments, the cloud infrastructure system 100 may send information to the client device so that the client device gives the client the priority to prompt the customer to convert the RAS to RS. The RS may allow the customer to continue using the services accessed using the RAS. In one example shown in FIG. 8A, RAS2 814 may be converted to RS1 838 based on input received from a client device operated by customer 1. Conversion of the assigned RAS to RS is further described below with reference to FIGS. 8B and 8C.

  The RAS assigned to the customer and returned to the service pool may be assigned to the customer for the requested service. The customer may be the same or a different customer than the one to whom RAS was previously assigned. As described in the previous example described with reference to FIG. 8A, once RAS3 816 is returned to service pool 810, RAS3 816 may be assigned 828 to another customer (e.g., customer 2). The subscriptions assigned to customer 2 such as subscription 850 (“customer 2 subscription”) may be held in the storage area associated with this customer. The data for specific service associated with RAS 3 816 is It may be held after RAS3 816 is returned to service pool 810 and assigned to customer 2. Data for a specific customer generated based on access to a service using RAS 3 816 is mapped to RAS 3 816. It may be stored in association with data for a specific service, RAS3 816 may be returned to the service pool 816, or may be converted to RS In the example of FIG. 854. In this case, RAS3 816 is returned to service pool 810 It is not possible to use RAS3 816 to reassign customers to customers, and by converting RAS3 816 to RS1 856, the customer-specific data generated by customer 2 is retained for use with RS1 856. It is also good.

  Referring now to FIG. 8B, an example of a data structure for implementing reusable anonymous subscriptions in accordance with some embodiments of the present invention is shown. Data associated with the subscription may be stored by implementing one or more data structures with the cloud infrastructure system 100. Examples of data structures include, but are not limited to, linked lists, tables, arrays, hash tables, graphs, and the like.

  The RAS 870 is an example of a data structure that can store information related to the RAS. The RAS 870 may be stored in memory allocated for the service pool. In the example of FIG. 8B, RAS 870 is shown with data for one RAS. However, RAS 870 can store information regarding one or more RAS. The modular implementation of one or more data structures for the RAS may facilitate a lightweight transformation process that allows multiple customers to use the RAS.

  The RAS 870 may include data corresponding to the service provisioned for the RAS (eg, data for a specific service 872). The service-specific data 872 may include data related to the provision of services enabled for the RAS. The data for specific service 872 may be customer-neutral so that various customers can reuse it. For example, the service-specific data 872 may include product-specific metadata associated with a product (eg, a service or a component) provided by the RAS corresponding to the RAS 870.

  In some embodiments, the service-specific data 872 may indicate the configuration of services provided to the subscription (eg, physical configuration of resources). The configuration may indicate resource constraints, such as one or more components (eg, features) that are enabled or disabled for the service. The configuration may be determined based on the service or a template regarding the type of product associated with the service. In some embodiments, this configuration may be based on a generic product template as opposed to a regular subscription configuration (eg, purchased configuration) that may be based on customer preferences.

  In some embodiments, the service-specific data 872 may include information related to the RAS. Among other information, the service-specific data 872 may identify the subscription, such as the name of the subscription and / or the identifier of the subscription. The service-specific data 872 may include customer information associated with the anonymous user. For example, the service-specific data 872 may include a reference to a data structure (eg, a guest customer identity object 864) that includes information about the guest assigned the RAS 870. The data for specific service 872 may include contract information. The RAS may not have an effective start date and / or an end date so that multiple customers can reuse it. On the other hand, the regular subscription may be assigned an effective start date and / or an end date at which the customer purchased the regular subscription.

  Customer-specific data 872 may indicate the type of support for RAS. RAS may enable different levels of support than regular subscriptions, as RAS may be used in limited capacity until converted to regular subscriptions. For example, a customer assigned a RAS may be provided with a comprehensive level of support, while a customer who has purchased a full subscription may be provided with a premium level of support.

  In some embodiments, the service-specific data 872 may indicate operations that may be performed using the RAS. For example, the service-specific data 872 may indicate that the service provided by the RAS can be used to support the customer's workflow by performing a test using the RAS. Additionally or alternatively, the RAS allows other applications, such as allowing the customer to demonstrate the service and / or to compare the service to a similar service provided by one or more competitors. May be provided.

  Once the RAS 870 is assigned 840 to the customer, the cloud infrastructure system 100 may maintain the data structure 874 (assigned RAS). The RAS 870 may be stored as an assigned RAS 874. Assigning the RAS may include moving the location of the RAS 870 to a new location in storage associated with the customer. Alternatively, assigned RAS 874 may include a reference to RAS 870 in storage. In some embodiments, assigned RAS 874 may be implemented as a different data structure, including data in RAS 870. In some embodiments, a data structure (eg, a mapping table or hash table) may be implemented in addition to RAS 874 to store a reference to each assigned RAS 874 associated with a customer.

  The customer-specific data 872 assigned to the customer but assigned in the RAS 870 may include an anonymous customer identity as the RAS subscription has not yet been converted. For example, the service-specific data 872 may indicate a reference (guest customer identity object) to a data structure 864 storing identity information about the guest. In some embodiments, guest customer identity object 864 may include information about the guest such as the guest's name, contact information, and the like.

  The assigned RAS 874 may be modified to store customer specific data 876 for the customer to which the RAS 870 has been assigned. Customer-specific data 876 may include data corresponding to the use of a service accessed using RAS corresponding to RAS 870. Customer-specific data 876 may be based on the application used to access the service. For example, customer-specific data 876 may include a customer mailbox corresponding to a sales cloud service accessed by a subscription for a service. In another example, customer-specific data 876 may include a table generated by use of a database service. In another example, customer-specific data 876 may include storage objects for object storage services accessed using RAS. In some embodiments, actual customer-specific data may be stored in another customer-specific repository, and customer-specific data 876 stores a reference to customer-specific data stored in the customer-specific repository. You may

  Cloud infrastructure system 100 may implement a conversion process 842 (eg, a lightweight personality injection process) that converts the RAS to a regular subscription (RS). For example, the RAS corresponding to RAS 874 may be converted to the RS represented by data structure 878. The conversion process 842 may include changing the type of subscription corresponding to the assigned RAS 874. For example, RS 878 indicates access to the same service provided by the assigned RAS 874 except for the duration of the RAS as corresponding to the assigned RAS 874 and the period as a regular subscription (eg, an extended period) It may be The conversion process 842 may store the information in the assigned RAS 874 in the RS 878. In some embodiments, the storage of assigned RAS 874 may be updated to indicate that the assigned RAS 874 is RS, eg, RS 878.

  The conversion process 842 may include determining account information (e.g., an account footprint) of the subscription (e.g., a regular subscription) that has converted the subscription assigned to the customer. For example, order management module 214 of cloud infrastructure system 100 may determine customer account information. Determining account information may include creating a customer account. An account may be created when an existing account is not found based on the customer's identity information. When an existing account is found, the existing account may be updated to allow access to the converted subscription. Thus, the service-specific data 872 in the RS 878 may be updated using the account information corresponding to the converted subscription.

  The conversion process 842 may include storing customer information in association with the RS 878 (eg, injecting personality information). The RS 878 may be associated with the customer's customer identity information associated with the assigned RAS 874 and may refer to it. In cloud infrastructure system 100, information regarding the identity of the customer may be stored in data structure 866 (customer identity object). In the example shown in FIG. 8B, RS 878 may indicate a reference to a customer identity object 866 that identifies the customer associated with the assigned RAS 874. Other subscriptions associated with the customer (eg, other RAS) may store a reference to the customer identity object 866. The customer identity object (eg, customer identity object 866) may include data indicative of information regarding the customer. This data may indicate the customer's identity (e.g., name or user identifier), customer's contact information, customer's billing information, other customer-related information, or a combination of these.

  In some embodiments, conversion process 842 may include updating guest customer identity object 864 with information in customer identity object 866. Information on the identity of the customer may be stored symbolically by using a reference to the object to reduce the processing time required to convert from RAS to RS. Alternatively, the reference to the customer identity object 866 may be shown by updating the reference to the guest customer identity object 864 from the service specific data 872.

  Conversion process 842 may include determining, for the customer, a contract for a regular subscription (eg, RS 878) converted from RAS (eg, assigned RAS 874). For example, the order management module 214 may perform processing to determine a contract for the type of subscription provided by the RS 878. Determining the contract may include determining qualification information regarding the subscription period and one or more qualifications that RS 878 provides. This contract may cause the customer to comply with terms and conditions that can be associated with a regular subscription, such as enforcing the customer with qualifying product support. The above conditions may indicate the usage period of the service matching the paid subscription. Regular subscriptions converted from RAS may provide customers with usage quotas that are larger than the quotas provided by RAS.

  The conversion process 842 may further include building support information within the support system 217 of the cloud infrastructure system 100. Providing the support system with account information on the regular subscription (eg, RS 878) assigned to the customer may allow the customer to receive the support (eg, regular product support) provided by the regular subscription.

  In some embodiments, conversion process 842 may include injecting customer account information into TAS 204 and the physical provisioning layer. For example, RAS 204 tags the subscription footprint and identity domain with a customer account number.

  FIG. 8C is a flowchart 880 of a process of managing the life cycle of reusable anonymous subscriptions in accordance with various embodiments. In some embodiments, the process illustrated by flowchart 880 may be implemented by all or part of a service infrastructure system (eg, cloud infrastructure system 100).

  The process described with reference to FIG. 8C may be implemented by software (eg, code, instructions, programs) executed by one or more processors, hardware, or a combination thereof. The software may be stored in memory (eg, on a memory device, non-transitory computer readable storage medium). The particular sequence of process steps shown in FIG. 8C is not intended to be limiting. Other sequences of steps may be performed according to alternative embodiments. For example, alternative embodiments of the present invention may perform the steps outlined above in other orders. In addition, the individual steps shown in FIG. 8C may include a plurality of sub-steps that may be performed in various sequences as appropriate depending on the individual step. In addition, other steps may be added or deleted depending on the particular application. One of ordinary skill in the art would recognize many variations, modifications, and alternatives. The process shown in flowchart 880 begins at block 882.

  At block 882, one or more services are provided to a service infrastructure system (eg, cloud infrastructure system 100 of FIG. 1). The service infrastructure system may include or implement a multi-tenant environment. Examples of services may include CRM services, HCM services, Java services, or other computing services.

  Data for specific service (for example, data for specific service 872 in FIG. 8B) may be associated with each service of the provisioned services. The data for specific service corresponding to a certain service may indicate the configuration of this service. This configuration may include one or more resources assigned to provide services.

  In some embodiments, providing one or more services provisions one or more of the services in the service infrastructure system prior to receiving a request for access to one of the services from the customer. Including. Services may be provisioned based on one or more criteria. For example, services may be provisioned based on one or more metrics associated with the operation of the service infrastructure system. In another example, services may be provisioned based on one or more metrics associated with the demand for services. In another example, services may be provisioned based on one or more metrics associated with the type of service.

  In some embodiments, creating one or more service pools may provide access to services that have already been provisioned. As described above, a service infrastructure system may maintain multiple service pools. One service pool may include multiple subscriptions. Each of the plurality of subscriptions may be associated with at least one service provided by the service infrastructure system. In one example, a service pool may provide multiple RAS subscriptions. In some embodiments, the service pool may be associated or classified based on the type of service, the resources provisioned for the service made available by the service pool, the type of subscription, etc. It is also good. The services corresponding to the subscriptions in the service pool may have already been provisioned by the service infrastructure system before this service request is made.

  A request for access to a service by a customer is received at block 884. For example, request 802 may be received from client device 224. The request may indicate the requirements of the service being requested. For example, the request may include information indicating the type of use of the service being requested. The service infrastructure system may use the type of use to determine the service that the customer requires.

  In various aspects, various options can be presented to the client at the client device user interface when the customer requests a service. One option may include the choice of whether to provision all or part of the requested service. Another option may include the type of subscription (eg, RAS subscription or production subscription) desired for the requested service.

  At block 886, execution of the process determines whether the requested service is provisioned for a subscription in a service infrastructure system's service pool (eg, service pool 810). By performing processing, analyze available subscriptions (eg, RAS) in one or more service pools and determine whether the available subscriptions provide access to the requested service. It is also good. As mentioned above, a service pool may include multiple RASs. Each RAS can be assigned to a customer when this RAS is available. By examining each RAS, the resources and / or services provided by this RAS may be determined. Subscriptions, such as RAS, are subject to information determined from the request (for example, the type of subscription requested by the customer, the type of use of the requested service, the duration of the requested service, or a combination of these). Can be identified within the service pool based in part. By processing service-specific data corresponding to each subscription in the service pool, a subscription of the type of subscription (eg, RAS subscription) for the service requested by the customer may be identified.

  Determining that the requested service has been provisioned can include determining a service pool from a plurality of service pools that provide and subscribe to the service, such as the requested service. In some embodiments, specifying a service pool may provide one or more subscriptions (eg, one or more RASs) for certain types of services. Thus, determining the service pool may include identifying a service pool that may provide a RAS for accessing the requested service. By examining the identified service pools, it may be determined whether any RAS in these service pools will enable access to the requested service.

  In some embodiments, determining one service pool from a plurality of service pools may be based on the availability within at least one service pool of a subscription for the service requested by the user. For example, one service pool may be determined from a plurality of service pools based on the type of service pool. The type of service pool may be determined based on the information indicated by the request from the customer (eg, the request received at block 884). For example, the type of service pool may be determined based on the requested service, the type of subscription requested by the customer (eg, RAS subscription), the type of use of the requested service, or a combination of these. The request may indicate any or all of these.

  At block 888, a subscription for access to the requested service may be assigned to the customer from the service pool (eg, the service pool determined at block 886). For example, RAS3 816 of FIG. 8A may be assigned to customer 1 824. When a subscription such as a RAS subscription is assigned to a customer, data associated with the subscription, for example, data for a specific service included in the RAS, is stored in association with information on the subscription assigned to the customer. May be For example, RAS 870 of FIG. 8B may be assigned to customers assigned RAS 874. In this example, the service-specific data 872 may be stored with the assigned RAS 874 stored for the assigned RAS subscription. Assigning the subscription for the requested service from the service pool to the customer may include removing the subscription from the service pool.

  In some embodiments, the availability of subscriptions (eg, RAS subscriptions) in a service pool may be changed based on demand from customers. Thus, a subscription for access to the requested service (e.g., a RAS subscription) may not be available when the request is received. In some embodiments, when a service requested by a customer is returned to the service pool with a subscription for access to this service (eg, a subscription for a service is reassigned from the customer to the service pool) May be assigned to customers from the determined service pool).

  At block 890, data for a particular customer corresponding to a customer (e.g., the customer who requested the service) may be associated with data for a particular service corresponding to the requested service. As mentioned above, customer-specific data includes data generated by the use of a service (eg, a service provided by a subscription). The customer-specific data, when generated, may be stored in association with the data-specific data for a subscription that provides access to the service used to generate the data. In at least one example, customer-specific data 876 related to the use of the service provided by the subscription corresponding to the assigned RAS 874 may be stored in association with the data for service-specific in the assigned RAS 874 .

  By storing data for specific customer in association with data for specific service for RAS, the data for specific customer is stored for the service provided by RAS when RAS is converted to a regular subscription. It is also good. Furthermore, the data for specific customer may be associated with the data for specific service to prevent the loss of data for specific customer when the access to the RAS service is modified. Customer-specific data may be maintained as this RAS subscription is converted to extend access to different subscriptions from RAS subscription to regular subscription (eg, production subscription).

  By performing the process, it is determined whether to convert a subscription for the customer (e.g., a RAS subscription). The subscriptions may be converted by a conversion process (eg, a lightweight personality injection process), such as the conversion process 842 described with reference to FIG. 8B. This conversion process may include changing the type of subscription that is assigned to the customer to access services previously provided by the subscription (e.g., the subscription assigned at block 888). For example, the subscription may be converted to a regular subscription. The regular subscription is a subscription that can provide access to the service under conditions different from the conditions of the subscription allocated from the service pool.

  There may be many reasons to convert a subscription. For example, a customer may indicate that they want to purchase a subscription to use the service for a period of time. In another example, a customer may express that they would like to get more support for a service than a comprehensive level of service support. Thus, in this case, the customer may convert the subscription to one that provides premium support for the service.

  In some embodiments, determining whether to convert a subscription to a customer may be based on input received from the customer. For example, cloud infrastructure system 100 may request input from a customer indicating a decision on whether to convert a subscription. The customer may provide an input stating whether to convert the subscription. This input may indicate one or more criteria for converting the subscription. This criterion may indicate the duration of the subscription after converting the subscription. The criteria may indicate other choices for the subscription, such as fees, type of service, type of support, or other criteria related to the type of subscription. In some embodiments, the customer may have entered the request received at block 884. In this request, the customer may indicate when and how to convert the subscription.

  In some embodiments, the service infrastructure system may make a determination of whether to convert a subscription for a customer. The service infrastructure system may determine whether to convert the subscriptions into other types of subscriptions based on the information determined by the service infrastructure system. In some embodiments, the customer may provide one or more rules that indicate when and how to convert the subscription. For example, this determination may be made based on various factors. These factors may be metrics associated with the operation of the service infrastructure system for the service, one or more metrics associated with the demand for the service, one or more metrics associated with the type of service, or Although the thing which combined these is included, it is not limited to these. The metrics may be defined by the rules provided by the customer.

  If it is determined to convert the subscription to the customer, the process may proceed to 894. If it is determined not to convert the subscription to the customer, the process may proceed to 896.

  At block 894, the subscription to the customer (eg, the subscription assigned to the customer at block 888) may be converted. At block 898, the process illustrated by flowchart 888 ends.

  In at least one embodiment, a subscription to a customer may be converted by changing the type of subscription assigned to the customer for access to the services previously provided by the subscription. For example, if the subscription is a RAS subscription that has a period of service (eg, trial period), then the type of subscription for this service may be different from the type of subscription assigned at block 888, with a different service period (Eg, regular subscription). By converting the subscriptions to different types of subscriptions, the customer can access longer or shorter periods of service, depending on the needs for the service. In one example, when the subscription is a RAS subscription defined by a trial period, the customer may want to convert the RAS subscription to a full subscription (eg, a production subscription). With regular subscriptions, customers will be able to realize a production environment.

  As described above, subscriptions may be transformed by the transformation process. When provided by the customer, the subscription may be transformed using the criteria provided by the customer. For example, the type of subscription may be selected based on input from the customer. In some embodiments, the type of subscription may be selected based on the information determined by the service infrastructure system.

  When the conversion process is complete, delete the assigned subscription from the service pool from the service pool. By removing the subscription from the service pool, the subscription will not be assigned to another customer.

  Next, returning to block 892, if it is decided not to convert the subscription for the customer, then at block 896, the subscription (eg, the subscription assigned to the customer at block 888) may be returned to the service pool. The subscription may be returned to the service pool by assigning a subscription from the customer to the service pool. For example, subscriptions may be returned to the service pool, this time by assigning the subscriptions assigned to the customer at block 888 to the service pool. For example, RAS3 816 of FIG. 8A may be assigned 826 from customer 1 to service pool 810 as RAS3 816. When the subscription is returned to the service pool, the subscription may again be assigned to one or more other customers (e.g. the same customer or another customer).

  Reverting the subscription to the service pool may include resolving the correspondence between the data for specific customer and the data for specific service corresponding to the service accessible by the subscription. In one illustrative example, if the customer decides not to purchase the services offered by the assigned subscription, then data for the particular customer is removed from the subscription prior to assigning the subscription to the service pool. By deleting customer-specific data from this subscription prior to assigning the subscription to the service pool, this subscription can be reassigned and hence reused by other customers. In some embodiments, customer-specific data may be stored in association with the customer's identity. By storing the data for specific customer in association with the identity of the customer, the data for specific customer can be easily deleted before returning the RAS to the service pool.

  Returning the subscription to the service pool may include implementing the deallocation process. The deallocation process may be performed based on the type of service offered by the subscription. In one example, the deallocation process for the provided service, which is a database as a service (DBAAS), may include deleting one or more users created by the customer of the service provided by the subscription assigned at block 888. In another example, the process of deassigning a service that is an object storage service may include deleting a storage object created by a customer if the subscription is a RAS subscription. In some embodiments, the deallocation process re-initializes resource usage statistics of the subscription (eg, RAS subscription) so that another customer to which the subscription is assigned is offered for this subscription. It may include making available the resources of the quota.

At block 898, the process illustrated by flowchart 880 ends.
Cloning of Subscriptions In certain embodiments, cloud infrastructure system 100 may enable other instance provisioning. Other instance provisioning may build services that provide other environments for customers to use. Examples of types of services include software as a service (SaaS) category, platform as a service (PaaS) category, infrastructure as a service (IaaS) category, or other service categories including hybrid services. It is not limited to

  In one aspect, cloud infrastructure system 100 can provide users with access to services based on existing services (eg, cloning existing services). Services based on existing services may be provided by creating subscriptions (eg "clone subscriptions") based on existing subscriptions (eg base subscriptions) for existing services. Clone subscriptions can be used by customers as an additional environment ("clone environment"). In another aspect, multiple clone subscriptions may be created based on the base subscription, each clone subscription providing a subscription for a service based on the existing services of the base subscription. The services provided by the clone subscription may provide an additional computing environment for the customer that is separate from the computing environment provided by the base subscription.

  A clone subscription may specify or be intended for a type of use that may be different from the type of use corresponding to the service provided by the base subscription. Customers can enjoy many benefits by being able to use the cloned environment for different purposes than the intended use of the environment associated with the base subscription. For example, clone subscriptions may be used for testing, customer / employee training, customer / employee demonstrations, prototyping for customer / development, development, load balancing, base subscriptions, production etc. May be used for other purposes. The types of uses disclosed herein are described for illustrative purposes. The type of use of clone subscriptions and base subscriptions can vary depending on the needs of the customer.

  In one example, a customer may require a clone subscription to implement a clone environment in a production environment to test or prototyping new features in the clone environment prior to deploying the feature in the production environment. . The ability to test or prototype new features in a cloning environment prior to application to production would allow customers to test and realize the product. By prototyping, the customer is able to provide feedback on the proposed products / features by using the services provided by the base subscription by hosting them using the provided environment for clone subscriptions. It can be received without affecting the production environment of the The features to be prototyped and tested in a cloning environment may be different from the production environment. Because customers will not want to realize these features in a production environment until they are ready.

  In another example, clone subscriptions may be used for load balancing. Non-mission critical workflows can be offloaded to a clone environment, and only mission critical workflows can be run in a production environment. This reduces the load on the production environment and can improve the performance of mission critical workflows.

  In another example, the environment provided by the clone subscription may allow the customer to perform tasks such as demonstrations and training, and the environment provided by the base subscription may be used as a production environment. For example, clone subscriptions can be used to train internal employees (e.g., marketing and sales representatives) or to demonstrate product features to customers. It would be desirable to perform such tasks in an environment different from the production environment. Production environments can be affected by such applications. In this way, the clone environment provides the customer with an additional environment that is automatically configured for different purposes without having to configure and realize a completely new environment from the beginning.

  The ability to create one or more cloned subscriptions based on existing subscriptions allows customers to reduce the cost of creating a similar environment, even if not replicated. In some embodiments, the cost to obtain a clone subscription will be much less than the cost of the base subscription. Clone subscriptions can be provisioned based on existing services, thus reducing the cost of implementing clone services. In this way, the customer enjoys the benefit of reduced costs for clone subscriptions. However, in return for cost reduction, the features provided for clone subscriptions may be different than base subscriptions. For example, the level of recovery service (eg, high availability and disaster recovery) provided to a customer for a clone subscription may be different than the service provided to this customer for a base subscription. In another example, the latency of replication of clone subscriptions will be greater than base subscriptions.

  A clone subscription may be associated with the subscription from which this clone subscription was created. When a clone subscription is associated with the subscription from which this clone subscription is created, the lifecycle of the subscription and the lifecycle of the clone subscription may be mapped to each other. In some embodiments, when associating a clone subscription with a base subscription, changes made to the base subscription may be reflected in the associated clone subscription. This change may be applied based on one or more rules. An example of the management of clone subscriptions is described below with reference to FIGS. 9A-9C and FIG.

  The configuration of the service provided by the clone subscription may be adjusted separately from the service provided by the base subscription. An example of adjusting the configuration of a clone subscription is adjusting the user count, which is the number of users that can be accessed using this clone subscription, adjusting the components to be enabled / disabled for this service, and / or the clone subscription Adjustment of the period of Changes in clone configuration may be requested at the time of creation of the clone, or may be requested later through operations on the configuration of the clone subscription. An example of changing the clone configuration is described with reference to FIGS. 9C and 10.

  Referring now to FIGS. 9A-9C, various embodiments for providing a clone subscription in accordance with some embodiments of the present embodiments are shown. FIG. 9A shows a simplified block diagram of a system environment for providing clone subscriptions in accordance with some embodiments. FIG. 9B shows an example of a subscription data structure in accordance with some embodiments. FIG. 9C shows an example of the rules for managing clone subscriptions accordingly. The clone subscription may be managed based on the correspondence with the subscription according to the rules.

  In FIG. 9A, several customers, such as customer 1, customer 2, and customer 3 are associated with client device 224, client device 226, and client device 228, respectively, for communication with cloud infrastructure system 100. In addition, a system environment 900 is shown. Cloud infrastructure system 100 may manage one or more subscriptions to customers (eg, subscription 910). The subscription 910 may include data corresponding to one or more subscriptions created for access to one or more services provided by the cloud infrastructure system 100. Subscription 910 may include a base subscription. For example, subscription 910 may include subscription 912 ("S1"), subscription 914 ("S2"), and subscription 916 ("S3"). Cloud infrastructure system 100 may have assigned one of subscriptions 910 to one or more customers. In the example shown in FIG. 9A, S2 914 and S3 916 are assigned to customer 1 as subscription S2 932 and subscription S3 934, respectively. Thus, S2 932 and S3 934 are existing base subscriptions. Subscriptions assigned to a customer, such as subscription 930 ("Customer 1 Subscription"), may be maintained in storage associated with this customer. An example data structure for storing subscriptions is described with reference to FIG. 9B.

  In at least one example, a customer (“Customer 1”) may obtain service 904 from cloud infrastructure system 100. Services 904 may include clone services. Access to the clone service (eg, service 904) may be provided by a clone subscription established by the cloud infrastructure system 100. Service 904 may be provided to customer 1 based on a request 902 by customer 1 operating client device 224. In various aspects, the customer can be presented with different options when ordering the service. The customer may choose to fully provision or partially provision each part of the order. The customer may select one or more clone subscriptions to gain access to the service. The following further describes the process of providing a clone subscription.

  As described above, the TAS module 204 of the cloud infrastructure system 100 manages the business process associated with each subscription order, and applies business logic to proceed with the provisioning order or not. Act as an orchestration component to judge. The TAS module 204 handles the process of processing subscription orders based on service requests from customers. In some embodiments, TAS module 204 can determine whether a request for clone service (eg, request 902) has been made based on an existing subscription. The TAS module 204 may build a clone environment for clone services based on the type of use indicated by the customer request. The TAS module 204 can determine that a clone subscription has been requested based on the request explicitly made for the clone subscription.

  A request for service (eg, request 902) from a customer to cloud infrastructure system 100 may include information that may be used to provide this service. Specifically, the request may include information (e.g., order information) that enables cloud infrastructure system 100 to determine a clone subscription to provide to the customer for the requested service. In some embodiments, the request may indicate the type of service or the type of intended use for the requested service. Examples of types of use may include, but are not limited to, development, testing, training, prototyping, load balancing, marketing, sales, design, production, and the like. In some embodiments, the request for cloud infrastructure system 100 may indicate the type of subscription desired by the customer, eg, a clone subscription or a regular subscription. In some embodiments, the request may indicate one or more requirements for the requested service. This requirement may include: rate restrictions (eg minimum and / or maximum charges), time restrictions on the use of the requested service, the amount of users using this service, the type of service support desired, other related to the use of the service Requirements, or combinations of these. Cloud infrastructure system 100 may determine a clone subscription to provide to the customer to enable access to the requested service based on the customer's conditions. Subscriptions may be provided based on existing subscriptions (e.g., base subscriptions).

  Upon determining that a request for a clone subscription has been received, the TAS module 204 may implement operations for the cloning process to establish a clone subscription. In the example shown in FIG. 9A, the cloud infrastructure system 100 may provision one or more clone services associated with the clone subscription order based on the request 902 from the customer 1. For example, clone subscription 940 (“C1”) and clone subscription 942 (“C2”) may be established by implementing cloning process 936 and cloning process 938 using base subscription S3 934, respectively.

  The operations for the cloning process may include processing subscription orders to establish C1 940 and C2 942 by performing the steps described with reference to FIGS. 3A and 3B. Processing the subscription order may include determining a charge associated with the clone subscription. The fee for clone subscription can be based on various criteria. These criteria include, but are not limited to, the type of use intended for the clone service provided for the clone subscription and the duration of the base subscription. In some embodiments, the fee may depend on the additional type of service requested in connection with the clone subscription. In some embodiments, the fee for clone subscriptions may be based on the configuration of clone subscriptions, and the fee may be adjusted based on changes in clone subscriptions. In the example shown in FIG. 9A, C1 940 and C2 942 may be established based on the information contained in the request 902.

  Having established the clone subscription, the TAS module 204 may send a request for provisioning clone service for each of the clone subscriptions C1 940 and C2 942 to the SDI module 206. Provisioning a clone service may include allocating resources and providing the clone service by configuring these resources necessary to fulfill the subscription order. The cloning process may include replicating resources provisioned for services enabled for base subscriptions. The cloning process may include configuring the clone service to resemble (e.g., clone) the configuration of the service provided for the base subscription. For the example of FIG. 9A, the clone service for C1 940 and C2 942 may be provisioned as a clone based on the provisioned service for base subscription S3 934.

  FIG. 9B shows an example of a subscription data structure in accordance with some embodiments of the present invention. Data associated with the subscription may be stored by the cloud infrastructure system 100 implementing one or more data structures. Examples of data structures include, but are not limited to, linked lists, tables, arrays, hash tables, graphs, and the like.

  The subscription 944 is an example of a data structure for storing information related to a subscription ("base subscription") established by the cloud infrastructure system 100. In the example of FIG. 9B, subscription 944 is shown with data corresponding to one subscription for the customer. However, the subscription data structure may store information regarding one or more subscriptions corresponding to any number of customers.

  The subscription 944 may include data corresponding to a customer (eg, data for a specific customer 952). Customer-specific data 952 may include data corresponding to the use of a service accessed with a base subscription corresponding to subscription 944. For example, the data for specific customer 952 may include a customer mailbox corresponding to a sales cloud service accessed by a subscription for the service. In another example, the customer-specific data 952 may include a table generated by use of a database service.

  The subscription 944 may include data (eg, data for specific service 954) corresponding to a service to which the base subscription corresponding to the subscription 944 can access. The service-specific data 954 may include data related to providing a service enabled for the subscription. For example, the service-specific data 954 may include product-specific metadata associated with a product (eg, service or component) provided by the base subscription corresponding to the subscription 944. In some embodiments, the service-specific data 954 may indicate the configuration of services provided to the base subscription (eg, physical configuration of resources). The configuration may indicate resource constraints, such as one or more components (eg, features) that are enabled or disabled for the service.

  Subscription 944 may include subscription data 956 associated with one or more subscriptions provided to the customer. In some embodiments, all or part of the subscription data 956 may be included in the data for service 954. The subscription data 956 may include account information of the account established for the subscription corresponding to the subscription 944. Account information may be associated with a customer identity. Information regarding the customer identity (e.g., user identity, password, contact information, etc.) may be stored in a customer identity data structure (e.g., a customer identity object). Subscription data 944 may include subscription contract information regarding the contract associated with the subscription and the entitlements granted by this contract. Subscription data 944 may include subscription support information associated with the subscription.

  Subscription data 944 may include clone subscription data 958 indicating information regarding one or more clone subscriptions associated with the subscription identified by subscription data 956. Clone subscription data 958 may include information indicating a correspondence between a base subscription corresponding to subscription 944 and one or more clone subscriptions. For example, clone subscription 958 may show correspondence 982 between a base subscription and a clone subscription corresponding to data structure 960 (e.g., "clone subscription 1") In another example, clone subscription 958 is It may occupy correspondence 984 between a base subscription corresponding to subscription 944 and a clone subscription ("clone subscription 2") corresponding to data structure 970. Both clone subscriptions 1 and 2 are subscriptions 944. May be established based on the corresponding base subscription.

  The life cycle of the base subscription (eg, the base subscription corresponding to the subscription 944) and the life cycle of the clone subscription (eg, clone subscription 1 or clone subscription 2) may be associated with each other. When the life cycles of the base subscription and the clone subscription are associated with each other, a change or update of the configuration or operation of the service provided for the base subscription is propagated to the clone service provided by the clone subscription. It is also good. For example, configuration changes stored in the service-specific data 954 may be applied to the configuration of clone subscription 1 and clone subscription 2 associated with the base subscription.

  In some embodiments, the correspondence between the base subscription life cycle and the clone subscription life cycle may be based on one or more rules. Rules may be based on base subscriptions. Subscription 944 may include rule data 972 indicating one or more rules for managing the life cycles of correspondences 982 and 984 with clone subscription 1 and clone subscription 2 respectively. Examples of rules are described below with reference to FIG. 9C. In some embodiments, access to the service provided by the clone subscription and access to the service provided by the base subscription may be managed by rules based on the correspondence between the clone subscription and the base subscription. Good.

  Clone subscription 960 and clone subscription 970 are examples of data structures for storing information related to clone subscriptions established by cloud infrastructure system 100. In the example of FIG. 9B, clone subscription 960 and clone subscription 970 are each one clone subscription for the customer, clone subscription 1 (eg, C1 940 of FIG. 9A) and clone subscription 2 (eg, C2 942). And the corresponding data. A data structure for a clone subscription may store information regarding one or more clone subscriptions corresponding to any number of customers.

  The clone subscription data structure (eg, clone subscription 960 or clone subscription 970) may include data for a particular customer (eg, data for a particular customer 962). Customer-specific data for clone subscriptions may include data corresponding to the use of services accessed using clone subscriptions.

  The clone subscription data structure may include data for a particular service (eg, data for a particular service 964). The service-specific data for a clone subscription may indicate information about the clone subscription, such as one or more attributes of the service provided for this clone subscription. The service-specific data may include product-specific metadata about the product (eg, service or component). The service-specific data may indicate the configuration (for example, physical configuration of resources) of the clone service provided for the clone subscription. The configuration may indicate resource constraints, such as one or more components (eg, features) to be enabled or disabled for the clone service. Customers of clone subscriptions established based on base subscriptions may not be provided with all features or components of base subscriptions.

  The customer may choose to change the configuration of the clone subscription (eg, clone configuration) from the configuration of the base subscription (eg, base configuration). The customer can define the clone configuration when the clone subscription is requested or after the clone subscription is provisioned. The cloning process can be implemented using base configuration and clone configuration. If the clone configuration is different from the base configuration, the cloning process may configure the clone subscription according to the clone configuration for differences from the base configuration. Thus, the clone service may be provisioned differently to the service for base subscription when the clone configuration is different from the base configuration.

  In some embodiments, the clone configuration for a clone subscription, unlike the base subscription configuration, indicates that one or more components are enabled / disabled for this clone subscription. It is also good. In one example, infrastructure service components associated with security or storage may be disabled. In another example, service components enabled for base subscription (eg, activity stream cloud component or sales forecasting component) may be enabled for clone subscriptions. In another example, performance features such as large indexes may not be enabled for clone subscriptions.

  In some embodiments, the clone configuration can be adjusted to a different amount than the base subscription according to size metrics such as user count. Size metrics may be adjusted for different uses of the clone subscription.

  In some embodiments, a clone subscription may be configured such that its duration is shorter than the duration of the base subscription. For example, a three year period may be required for base subscriptions and a one year period for clone subscriptions. Customers may select this to support development / test activities that are expected to be only for one year.

  Clone subscriptions may be provisioned based on the adjustment of the clone configuration in comparison to the base configuration. The clone configuration may be adjusted after provisioning based on the changing needs of the customer to which the clone subscription is assigned.

  In some embodiments, clone subscriptions may be configured based on one or more rules that indicate clone configuration. This rule can be determined based on rule data (eg, rule data 966) stored for a clone subscription, or stored for a base subscription from which a clone subscription was established. It can be determined based on the rule data (e.g., rule data 972).

  The clone configurations corresponding to each of a plurality of clone subscriptions (eg, C1 940 and C2 942) may be modified independently of one another. Clone subscriptions may be configured differently from one another. The configuration for clone subscription can be changed when the customer intends to use each clone subscription for different purposes. For example, the C1 940 clone configuration may be modified for testing. The clone configuration of C2 942 is left unchanged without modification, and the base configuration of base subscription S3 934 to implement features in a production environment similar to the product environment realized with base subscription. (Eg, clone base configuration).

  In some embodiments, schemas may be created to build clone configurations for clone subscriptions from base subscriptions. A schema can be defined for service types, specific services, specific product products, other types of categories for subscriptions to services, or a combination of these. Thus, the schema may indicate rules such as rules 990 that can be used to determine a clone subscription based on this schema.

  The clone subscription data structure includes rule data 966 indicating one or more rules for managing the life cycle of the correspondence (for example, correspondence 982) between the clone subscription (for example, clone subscription 1) and the base subscription. May be included. An example of rule data is described below with reference to FIG. 9C.

  The subscription data (eg, subscription data 968) included in the clone subscription data structure may include subscription information for the clone subscription (eg, clone subscription 1). The subscription data may indicate identification information regarding the subscription (e.g. subscription identifier or name of the subscription), subscription period, and identity information of the user (e.g. administrator and non-administrator). In some embodiments, subscription data for a clone subscription may include a parent subscription identifier that identifies the base subscription from which the clone subscription is established. For example, subscription data 968 may include a parent subscription ID that identifies the base subscription corresponding to the base subscription 944 from which clone subscription 1 was established. The parent subscription ID may indicate a reference to a base subscription data structure (eg, base subscription 944) corresponding to the base subscription from which the clone subscription (eg, clone subscription 1) was created. The reference can be used to identify data corresponding to a clone subscription generated based on the base subscription.

  FIG. 9C shows an example of rules 990 for managing clone subscriptions in accordance with various embodiments. The rules 990 may include information corresponding to one or more rules, such as a set of rules. The rule 990 may be predetermined by the cloud infrastructure system, may be defined by the customer, or may be a combination of these. The rules 990 may be defined in a data file (eg, an Extensible Markup Language (XML) file) or may be based on input received from a customer via a client device.

  The customer may define rules at the customer level or at the subscription level. Customer level rules may be defined on the basis of customer created subscriptions (eg, clone subscriptions). In some embodiments, customer level rules may be defined on the basis of a clone of a particular product created by the customer. The subscription level rules may be defined such that the subscription level rules apply to a clone subscription established from a base subscription for which the rules are defined, on the basis of the base subscription. These types of rules may be applied at the start of the subscription and may be applied later when the subscription is changed.

  Rule 990 may be used to manage the correspondence between the base subscription and one or more clone subscriptions (eg, clone subscription 1 and clone subscription 2). Changes to a base subscription (eg, base subscription 944) may be applied to clone subscriptions based on rule 990. For example, a change in the configuration of a base subscription may be applied as a change in the clone configuration of a clone subscription created based on the base subscription. As described above, the clone configuration may be changed from the base configuration.

The following are some examples of such rules.
The clone created from the base subscription must initially have the same configuration as the base subscription, but the duration of the clone may be shorter than that of the base subscription.

  -All functional changes made to the base subscription, such as enabling / disabling components, can be applied to the clone associated with the base subscription but increase / decrease the user count Such resizing should not be applied to clones.

  When updating a base subscription, all clones currently associated with the base subscription must also be updated over their respective current period.

  When terminating a base subscription, all clones associated with the base subscription must also be terminated.

  In at least one example, rules 990 may be based on one or more conditions 992. Condition 992 can be determined based on one or more criteria. For example, condition 992 is based on one or more metrics (eg, metrics associated with operations in cloud infrastructure system 100). Examples of metrics include, but are not limited to, system metrics, product metrics, component metrics, customer metrics, and the like. The conditions may also be based on the operation being performed on the base subscription. Examples of base subscription operations are "On-Board Clone" (eg, Clone Subscription created based on Base Subscription), "Add Component", "Delete Component", "User Count Increase", and "User Count" But not limited thereto. In some embodiments, the condition is a logical relationship with a logical operator such as disjunction, conjunction, negation (eg, "user's clone subscription count" <100 AND based subscription operations = "add component"). It can be expressed as A rule may be satisfied when each of the conditions of the rule is satisfied.

  In another example, rule 990 may include one or more procedures 994. For example, procedure 994 may be based on one or more classes 996. Class 996 may be a type of operand applied to a clone subscription. Examples of operand types are those described above for the direct operations performed on a base subscription. In another example, the operands may correspond to operations such as "on-board clones" (ie, clone based on parent subscriptions). Other operands may include "extension", "update", "end" and "extension". Extensions may include operations such as increasing and decreasing user counts. The termination may include operations such as termination of the clone subscription. An update may include operations such as adding or deleting one or more components to a clone subscription. The extension may include an operation such as extending the period of the clone subscription. If the rules are fulfilled, the clone configuration may be modified based on this rule.

  In another example, procedure 994 may be based on one or more actions. Action 998 can be defined based on one or more operations ("clone subscription operations") that can be performed on the clone subscription. Some examples of clone subscription operations are "Cloning All Data", "Do not Clone Data", "Cloning Selected Data", "Add Components", "If Specified List" Add Component, Remove Component, and Remove Component if Specified List. The clone subscription may be modified based on the class of operands of class 966 and the specified operation of action 998.

  In some embodiments, rules may be defined by one or more conditions 992, one or more procedures 994, one or more actions 998, or a combination thereof. A rule may be satisfied by the fulfillment of one or more criteria defined for that rule. Once the rules are met, the clone configuration may be changed based on the changes indicated by the rules.

  FIG. 10 is a flow chart of a process for managing the life cycle of a clone subscription in accordance with various embodiments. In particular, the process illustrated by flowchart 1000 can provide a customer with a clone subscription of a service, and manage the clone subscription life cycle based on a set of rules (eg, rule 990) Can. In some embodiments, the process illustrated by flowchart 1000 may be implemented by all or part of a service infrastructure system (eg, cloud infrastructure system 100).

  The process described with reference to FIG. 19 may be implemented by software (eg, code, instructions, programs) executed by one or more processors, hardware, or a combination of these. The software may be stored in memory (eg, on a memory device, non-transitory computer readable storage medium). The particular sequence of process steps shown in FIG. 10 is not intended to be limiting. Other sequences of steps may be performed according to alternative embodiments. For example, alternative embodiments of the present invention may perform the steps outlined above in other orders. In addition, the individual steps illustrated in FIG. 10 may include multiple sub-steps that may be performed in various sequences as appropriate depending on the individual step. In addition, other steps may be added or deleted depending on the particular application. One of ordinary skill in the art would recognize many variations, modifications, and alternatives. The process shown in flowchart 1000 begins at block 1002.

  At block 1002, one or more services are provided to a service infrastructure system (eg, cloud infrastructure system 100 of FIG. 1). The service infrastructure system may include or implement a multi-tenant environment. Examples of services may include CRM services, HCM services, Java services, or other computing services.

  In some embodiments, providing one or more services provisions one or more of the services in the service infrastructure system prior to receiving a request for access to one of the services from the customer. Including. Services may be provisioned based on one or more criteria. For example, services may be provisioned based on one or more metrics associated with the operation of the service infrastructure system. In another example, services may be provisioned based on one or more metrics associated with the demand for services. In another example, services may be provisioned based on one or more metrics associated with the type of service.

  At block 1004, the customer may be able to access the service. Providing access to a service may include providing a subscription (eg, a base subscription) to a user. For example, referring to FIG. 9A, a customer (“customer 1”) may be provided with subscription S2 932 and subscription S3 934. The subscription may indicate the access granted to the service. In some embodiments, a client device (eg, any one of client devices 224, 226, 228) may allow a user to access services by providing a user interface. Information regarding the subscription that allows access to the service may be shown to the customer via the user interface.

  A request from a customer is received at block 1006. For example, request 902 may be received from client device 224. The request may be to access other services as a clone (e.g., a clone service) based on the service enabled for the customer at block 1004. In some embodiments, the other services may be requested by the customer for an application different from that of the service enabled at block 1004. For example, the other features described above may be used to test new features before enabling them on a production system. On the other hand, the services enabled at block 904 may be used to implement a production system. The other service may be similar to or associated with the service enabled for the customer at block 1004, or the other service may be different from this service.

  At block 1008, the other service may be constructed as a clone of the service enabled at block 1004. Building a clone of the service may include determining a subscription (eg, a clone subscription) for the clone service. The clone subscription may be determined based on the cloning of the subscription corresponding to the service. These other services may be provided to the customer by subscription ("clone subscription") as a clone of the subscription corresponding to the service enabled at block 1004 ("clone subscription"). For example, subscription C1 940 may be generated 936 as a clone based on subscription S3 934 of FIG. 9A. In this example, C1 940 may provide clone services based on the services provided by S3 934. Thus, a clone subscription may be created to build a clone of the service. Clone subscriptions can provide access to "cloned" services.

  At block 1010, the service enabled at block 1004 may be associated with the service enabled at block 1008 ("clone service"). The two services may be associated with each other based on the correspondence between subscriptions corresponding to these services. For example, clone subscription 1 960 for a clone service may be associated with a subscription 944 (eg, a base subscription) for a service (eg, correspondence 982).

  In some embodiments, associating a base subscription corresponding to a service with a clone subscription corresponding to a clone service may include associating a subscription life cycle with a clone subscription life cycle. In this way, the life cycle of the base subscription and the life cycle of the clone subscription are related. In some embodiments, associating the services enabled for the base subscription with the clone services built for the clone subscription may include associating the life cycles of these services. As described above, when associating two subscriptions with each other, changes to the base subscription may be reflected in the clone subscription. For example, when the service corresponding to the base subscription is terminated, the access to the clone service by the customer is terminated. In another example, when access to the service corresponding to the base subscription is updated, access to the clone service may be updated based on the updated access for the base subscription.

  In some embodiments, the correspondence between subscriptions (eg, base subscriptions and clone subscriptions) may be based on a set of rules (eg, rule 990 of FIG. 9C). All or part of the set of rules may be predetermined or may be based on a default according to the subscription. For example, the set of rules may be based on the products (eg, services) provided by the base subscription. The customer provides input to modify a predetermined set of rules or create a new set of rules.

  At block 1012, access to other or clone services may be managed based on a set of rules. For example, access to the clone service provided for clone subscription 1 960 of FIG. 9B may be managed based on a set of rules, eg, 990 of FIG. 9C. The flowchart 100 ends at block 1014.

  In various embodiments, the rules used to manage the clone service define one or more conditions and one or more actions. If one or more conditions are met, one or more actions are performed on the associated clone subscription. The one or more actions may correspond to direct actions that the customer may perform on the clone subscription as described above.

  In some embodiments, when a clone service is associated with a base service, access to the clone service may be managed by a set of rules (eg, rule 990). Access to the clone service may be managed using rules in response to changes to the base service. As described above with reference to FIG. 9C, one or more rules may also be used to manage the lifecycle of the clone subscription and thus access to the clone service provided to the clone subscription. Good. For example, access to the clone service may end when the base service associated with the clone service is terminated.

  In some embodiments, access to the clone service may be managed by performing one or more actions associated with one type of procedure performed for the clone service. The one type of procedure may be determined based on one or more criteria. For example, one type of procedure may be determined based on one or more metrics of the base service (eg, the performance of this service) associated with the clone service. Another criterion may be the operations performed on the base service based on changes to the base service. In some embodiments, one type of procedure may be associated with an action, and some of these actions may belong to other rules. For example, in one rule, one type of procedure may be "update" and the action may be "add component", and in another rule, one type of procedure may be "update" but the action is "component delete" It may be

  FIG. 11 is a flowchart 1100 of a process of cloning a subscription in accordance with various embodiments. In some embodiments, all or part of a service infrastructure system (eg, cloud infrastructure system 100 of FIG. 1) may implement the process shown in FIG.

  The process described with reference to FIG. 11 allows the customer to modify the clone subscription based on the subscription from which the clone subscription was established. Modifications may be requested at the time of creation of the clone subscription or may be requested later by direct operation on the clone subscription. As described above, the modification of the clone subscription may include the modification of the configuration related to the service provided for the clone subscription, and may include the modification of the configuration of the subscription. Good.

  The processing illustrated in FIG. 11 may be implemented by software (eg, code, instructions, programs) executed by one or more processors, hardware, or a combination of these. The software may be stored in memory (eg, on a memory device, non-transitory computer readable storage medium). The particular sequence of process steps shown in FIG. 11 is not intended to be limiting. Other sequences of steps may be performed according to alternative embodiments. For example, alternative embodiments of the present invention may perform the steps outlined above in other orders. In addition, the individual steps shown in FIG. 11 may include multiple sub-steps that may be performed in various sequences as appropriate depending on the individual step. In addition, other steps may be added or deleted depending on the particular application. One of ordinary skill in the art would recognize many variations, modifications, and alternatives. The process shown in flowchart 1100 begins at block 1102.

  At block 1102, a subscription (eg, a base subscription) for the service may be provided to the customer. For example, service 904 may be provided to customer 1 of client device 224. Providing a service may include provisioning a service. Services may be provisioned according to the configuration indicated by the customer. Providing a service may include determining a subscription to the service and enabling access to the service based on the subscription. In various embodiments, a list of valid subscriptions may be provided to the client device. The customer may select one of these subscriptions.

  At block 1104, a configuration (eg, a clone configuration) for cloning the subscription (eg, the subscription provided at block 1102) may be determined. As described above, the clone configuration may indicate one or more criteria for configuring a subscription to be cloned based on an existing subscription. For example, the clone configuration may indicate the usage period of the clone service (for example, shorter than the period of service corresponding to the base subscription). In another example, the clone configuration may indicate components to enable / disable for services provided to the clone subscription.

  The clone configuration can be determined using various methods. In some embodiments, the clone configuration may be determined based on the input received from the customer. This input may indicate the intended use or requirement of the clone subscription. The clone configuration may be determined based on input from the customer. For example, a customer operating a client device may provide information to a service infrastructure system (e.g., cloud infrastructure system 110). This information may indicate the clone configuration (eg, clone variation).

  In some embodiments, the clone configuration may be determined based on analysis information determined by the service infrastructure system. The analysis information may include metric information related to operations performed by the service infrastructure system for the customer. The analysis information may include information regarding the operations performed by the customer using the services provided by the service infrastructure system.

  At block 1106, a clone subscription may be created based on the clone configuration (eg, the configuration determined at block 1104). Clone subscriptions may be created based on the subscription (eg, the subscription provided at block 1102) and the clone configuration. Clone subscriptions may be created based on customer preferences, predefined rules, and other criteria described with reference to FIG. 9C, as described above.

  At block 1108, a clone subscription (eg, the clone subscription created at block 1106) may be managed by performing one or more operations. This (these) operations may be performed during the clone subscription's life cycle. By performing the operation directly on the clone subscription, the clone service provided for the clone subscription can be modified. The flowchart 1100 ends at block 1110.

  In some embodiments, direct operation may include modifying the clone configuration corresponding to the clone subscription. The clone configuration may be modified based on the input received from the customer or may be modified based on information determined by the service infrastructure system. It would be useful to allow customers to modify clone subscriptions based on their needs. Direct operations may include, but are not limited to, operations performed on clone services corresponding to clone subscriptions. This operation may enable / disable components provided for the clone service, or adjust resizing of users authorized to access the clone service (eg, increase / decrease user count) May be included.

Providing Subscriptions Based on Existing Services In certain embodiments, the cloud infrastructure system 100 provides users with access to services based on existing services using the various techniques described herein. be able to. Such techniques can reduce processing time when provisioning resources for requested services, which can improve processing efficiency in providing access to services to customers. . The cloud infrastructure system 100 can determine the type of service based on the request from the user, and provide a subscription that enables access to the service using provisioning based on the existing service. it can.

  In one aspect, the cloud infrastructure system 100 can enable provisioned resources (eg, hardware and service instances) for services shared among customers. The cloud infrastructure system 100 may not need to re-provision these resources for each customer accessing the service. For example, by defining RAS, customers can be able to share access to services. This RAS can be assigned to customers when it is available and available in the service pool. Resources for services accessible using the RAS may remain provisioned for the RAS so that customers assigned the RAS can reuse it.

  The service accessible using RAS allows the customer to try this service before purchasing a full subscription for the service. Thus, customers can avoid delays in provisioning resources for subscriptions to services. The RAS may be converted to a regular subscription if the customer decides to purchase a subscription for the RAS. It can improve the efficiency of the process for providing regular subscriptions. This is because RAS can be transformed using a process that reduces the time taken to provision resources for subscriptions. Resources and data for RAS can be kept for regular subscriptions.

  In another aspect, cloud infrastructure system 100 can provide customers with access to cloud services based on existing services. Services based on existing services may be provided by creating subscriptions (eg, “clone subscriptions”) based on existing subscriptions (eg, base subscriptions) for existing services. Cloud infrastructure system 100 may prepare cloud services based on the configuration of services provided by the base subscription. In this way, the processing time required to establish a subscription for the requested service can be reduced by configuring the clone service according to the configuration of the base subscription. Customers may use the clone service as an additional environment apart from the computing environment provided by the base subscription. As discussed above, a clone subscription may specify or be intended for a type of use that may be different from the type of use corresponding to the service provided by the base subscription.

  FIG. 12 is a flowchart 1200 of a process for providing a subscription for a service with existing subscriptions in accordance with various embodiments. In particular, the process illustrated by flowchart 1200 may provide a subscription to a customer based on a service that has already been provisioned. The subscription may be either a reusable anonymous subscription or a cloned subscription to access the service requested by the customer. In some embodiments, the process illustrated by flowchart 1200 may be implemented by all or part of a service infrastructure system (eg, cloud infrastructure system 100).

  The processes described with reference to FIG. 12 may be implemented by software (eg, code, instructions, programs) executed by one or more processors, hardware, or a combination of these. The software may be stored in memory (eg, on a memory device, non-transitory computer readable storage medium). The particular sequence of process steps shown in FIG. 12 is not intended to be limiting. Other sequences of steps may be performed according to alternative embodiments. For example, alternative embodiments of the present invention may perform the steps outlined above in other orders. In addition, the individual steps shown in FIG. 12 may include a plurality of sub-steps that may be performed in various sequences as appropriate depending on the individual step. In addition, other steps may be added or deleted depending on the particular application. One of ordinary skill in the art would recognize many variations, modifications, and alternatives. The process shown in flowchart 1200 begins at block 1202.

  At block 1202, one or more services are provided to a service infrastructure system (eg, cloud infrastructure system 100 of FIG. 1). The service infrastructure system may include or implement a multi-tenant environment. Examples of services may include CRM services, HCM services, Java services, or other computing services.

  In some embodiments, providing one or more services may be performed by the service infrastructure system prior to receiving a request for access to one of the services from the customer. Including provisioning more. Services may be provisioned based on one or more criteria. For example, services may be provisioned based on one or more metrics associated with the operation of the service infrastructure system. In another example, services may be provisioned based on one or more metrics associated with the demand for services. In another example, services may be provisioned based on one or more metrics associated with the type of service.

  At block 1204, a request is received from a customer for access to a service provided by the service infrastructure system. For example, request 802 or request 902 may be received from client device 224. The customer request may indicate the type of use of the service requested by the customer. Examples of types of use include, but are not limited to, testing, development, load balancing, production, training, marketing, or combinations thereof. In some embodiments, the customer request may indicate the type of subscription desired by the customer. The type of subscription may indicate a reusable subscription (eg, RAS) or a clone subscription.

  In some embodiments, the request may indicate one or more requirements for the requested service. This requirement may include: rate restrictions (eg minimum and / or maximum charges), time restrictions on the use of the requested service, the amount of users using this service, the type of service support desired, other related to the use of the service Requirements, or combinations of these.

  At block 1206, processing is performed to determine the type of subscription based on the service requested by the customer. The type of subscription is either a clone subscription or a reusable subscription (eg RAS). The type of subscription may be determined based on the information in the request, such as the type of subscription, the type of use, and / or one or more requirements. The type of subscription determined for the requested service can be used to determine the subscriptions provided to the customer to enable access to the requested service.

  At 1208, the customer is provided with a subscription to access the first service (eg, the service requested at 1204). This subscription is provided based on the type of subscription determined at 1206. The first service may be provided using one of the services provided by the service infrastructure system (eg, the service provided at block 1202).

  In one example, when the request indicates a type of use, such as testing or developing new features of the production environment, a clone subscription may be provided to the customer to access the first service. In this example, the reason why the clone subscription can be selected is that the base subscription used for establishing the clone subscription may already be configured according to the specification by the customer, and the clone subscription is configured of the base subscription Because it is cloned based on the Reusable subscriptions may not be provided. This is because other configurations may be needed for services provided by reusable subscriptions. Clone subscriptions can reduce the processing time required to build the requested service. This is because the customer does not have to provide the information to configure the clone subscription. By selecting clone subscriptions rather than reusable subscriptions, the additional processing performed for managing clone subscriptions may be reduced. For example, the clone subscription life cycle is associated with the base subscription life cycle to automatically manage (eg, renew or terminate) the clone subscription based on the operations performed to manage the base subscription. May be

  In another example, a reusable subscription may be provided to the customer when the request for the first service indicates a test as a type of use and indicates a time limit of use of the requesting service. In this example, the reason why a reusable subscription can be provided rather than a clone subscription may be that the customer does not yet have a base subscription that can be the basis of creating a clone subscription . Reusable subscriptions may be desirable for providing to customers. Because resources for reusable subscriptions will already be provisioned. In addition, reusable subscriptions may be reassigned to other customers when the current customer has finished using the reusable subscription. Reusable subscriptions may be provided to the customer when the customer does not require additional configuration.

  In some embodiments, when the type of subscription is a clone subscription, providing the subscription to the customer is determined based on the first subscription to the first service (eg, an existing service). Establishing a clone subscription and associating the first clone subscription with the first subscription based on a set of rules. The first clone subscription may provide access to a second service. The first clone subscription may be provided to the customer as a subscription.

  Associating the first clone subscription with the first subscription may include associating the first clone subscription life cycle with the first subscription life cycle. The access to the second service may end when the access to the first service is terminated based on the correspondence between the first clone subscription and the life cycle of the first subscription. In some embodiments, when the life cycle of the first clone subscription and the life cycle of the first subscription are associated with each other, access to the second service is based on a request from the customer. It may be corrected based on the update of access to one service.

  In some embodiments, the correspondence between the first clone subscription and the first subscription may be managed by using a set of rules. The set of rules may indicate the use of the second service as a clone of the first service. One set of rules may indicate the duration of access to the second service. One set of rules may indicate the number of users authorized to access the second service. The number of users authorized to access the second service may be different from the number of users authorized to access the first service. One set of rules may indicate the configuration of the second service. The configuration of the second service may be different from the configuration of the first service.

  In some embodiments, providing the subscription to the first customer when the type of subscription is a reusable subscription is provision of the first service in a service pool in the service infrastructure system. Determining that it has been done and assigning the first subscription for the first service to the customer as a subscription for the service. Assigning the first subscription may include assigning the first service to the customer from the service pool. Assigning the first service to the customer may include removing the first service from the service pool. For the first service, data for a specific customer may be associated with the customer. The data for specific customer may be associated with the data for specific service corresponding to the first service.

  At block 1210, subscriptions provided to the first customer may be managed. When the type of subscription is a clone subscription, managing the subscription may include, in response to a change of the first service, determining access to the requested service by the subscription. Access to services may be determined using a set of rules. When the type of subscription is a reusable subscription, managing the subscription may include assigning a first service from the customer to the service pool when the subscription is terminated. Assigning the first service to the service pool may include resolving the correspondence between the data for specific customer and the data for specific service corresponding to the first service. Once the first service is returned to the service pool, the first service may be reassigned from the service pool to one or more other customers.

The flowchart 1200 ends at block 1212.
FIG. 13 shows a high level overview of various interactions involved in providing a tenant environment, in accordance with an embodiment of the present invention.

  At (1), a tenant request for a Java service is sent from TAS 204 to SDI 206. The SDI 206 provisions the requested Java service from the pool of reusable anonymous subscriptions. SDI 206 includes an SDI connector 612. SDI connector 612 includes Nuviaq connector 620, IDM connector 622, DB connector 614, and assembly builder 624.

  As noted above, before receiving a tenant request, SDI 206 provisions one or more pools of one or more reusable anonymous subscriptions. For example, when the SDI 206 requires provisioning of a new Java subscription, at (2), a request for anonymous assembly is sent from the assembly builder connector 624 of the SDI connector 612 to the assembly builder 502. At (3), the anonymous assembly is deployed by the assembly builder 502 through the virtual machine OVM 1302. At (4), the assembly builder 502 returns the result of the anonymous assembly to the assembly builder connector 624.

  At (5), an IDM slice creation command is sent from the IDM connector 622 to the IDM 200. At (6), the IDM coordinates are returned from the IDM 200 to the IDM connector 622. At (7), the DB connector 614 instructs creation of a DB slice through the DB 504. At (8), the DB coordination is returned from the DB 504 to the DB connector 614.

  At (9), a request for configuration of Java services with given IDM, DB, and EM agent (if applicable) coordination is sent from Nuviaq connector 620 to Nuviaq database application 1304. At (10), the Nuviaq database application 1304 stores all service instance data. In (11), a Java service instance including activation of the EM agent is configured. Lightweight directory access protocol (LDAP) ATN credentials, node manager password, and embedded LDAP password can be configured in the advanced encryption standard (AES) available to the OVM 1302 It is stored in .xml file. Other services besides Java services, including services of different types, can be created using the SDI module.

  A computer network cloud infrastructure system can provide multiple services. Such services may include simple infrastructure as services (IAAS) services, platform as services (PAAS) services, and software as services (SAAS) services. IAAS, PAAS, and SAAS services are different types of services.

  The IAAS service may include a simple storage solution. The storage solution may include a remote set of disk drives accessible from the Internet or other memory devices. These may also include file transfer protocol (FTP), virtual private network (VPN), or other services for uploading, downloading, and tracking data stored on disk drives. IAAS storage solutions may include functionality beyond mere storage, such as redundancy and backup services. IAAS services may also include processing power, bandwidth to other parts of the earth, and other computer resources.

  PAAS services may include database cloud services, middleware cloud services, Java cloud services, and other services commonly provided as software platforms. Database services may include access to relational database engines such as SQL database engines. Tables and other database schemas can be designed and implemented by the user on the cloud, and the database management engine can be used by the user to input and export data from the database. Similarly, a user can create a custom application on the cloud system using Java or other programming language and then execute it on the cloud system. Users at a distance from the cloud server can design and execute other middleware applications that support custom user interfaces and data structures.

  SAAS services may include customer relationship management (CRM) services. These services can help salespeople track leads, help employees maintain customer accounts, and help customers view their own accounts can do. Human resource management (HCM) and human resources services can help employers store information about employees and independent contractors. Such services can provide working time tracking, asset inspection, and employee directory tracking and payment.

  Provisioning of cloud resources for services may occur asynchronously. For example, a method or function can be invoked through an application programming interface (API) using argument variables including a callback address. Rather than waiting for the called method to finish before the called method continues, the called method can send a message to the module upon exit. The invoked method can also send status updates to the module. Because provisioning for some services, such as SAAS services, can take hours or days, and provisioning time for other services, such as IAAS services, can be several minutes, Asynchronous API calls may help to ensure that the minimum activation period service is provisioned first rather than later, even when it is provisioned with other services with longer activation times.

Conclusion FIG. 14 shows a simplified diagram of a distributed system 1400 for implementing certain embodiments. In the illustrated embodiment, distributed system 1400 is configured to execute and manipulate client applications, such as web browsers, proprietary clients (eg, Oracle Forms), etc., on one or more networks 1410. Arithmetic units 1402, 1404, 1406 and 1408 are included. Server 1412 may be communicatively coupled to remote client computing devices 1402, 1404, 1406, and 1408 via network 1410.

  In various embodiments, server 1412 executes one or more services or software applications such as services and applications to provide users with access to services using existing services provisioned by the cloud infrastructure system. Can be configured to In particular embodiments, server 1412 may also provide other services or software applications that may include non-virtual and virtual environments. In some embodiments, these services may be based on a software (SaaS) model as a web-based or as a cloud service or as a service to users of client computing devices 1402, 1404, 1406, and / or 1408. Can be provided by A user operating client computing devices 1402, 1404, 1406, and / or 1408 may utilize services provided by these components by interacting with server 1412 utilizing one or more client applications.

  In the configuration shown in FIG. 14, software components 1418, 1420, and 1422 of system 1400 are shown as being implemented on server 1412. In other embodiments, one or more of the above components of system 1400 and / or the services provided by these components are implemented by one or more of client computing devices 1402, 1404, 1406, and / or 1408. It may be done. Then, a user operating the client computing device can use one or more of the client applications to use the service provided by these components. These components may be implemented in hardware, firmware, software, or a combination of these. Note that a wide variety of system configurations are possible, which may differ from the distributed system 1400. The embodiment shown in FIG. 14 is thus a distributed system for implementing the system of an embodiment and is not intended to be limiting.

  Client computing devices 1402, 1404, 1406, and / or 1408 may include various types of computing systems. For example, the client device runs software such as Microsoft Windows Mobile® and / or various mobile operating systems such as iOS, Windows Phone, Android®, BlackBerry® 10, Palm OS, etc. , Portable handheld devices (e.g., iPhone (R), mobile phones, iPad (R), computing tablets, personal digital assistants (PDAs)) or wearable devices (e.g., Google Glass (R) head mounted display). These devices may support various applications such as various Internet related applications, email, short message service (SMS) applications, and may use various other communication protocols. Also, client computing devices include, by way of example, personal computers and / or laptop computers running various versions of Microsoft Windows®, Apple Macintosh® and / or Linux® operating systems. , A general purpose personal computer. The client computing device may run any of a variety of commercially available operating systems, such as, but not limited to, various GNU / Linux operating systems, such as the Google Chrome OS It may be a workstation computer. In addition, the client computing device may be a thin client computer capable of communicating on the network 1410, an Internet connectable gaming system (e.g., a Microsoft Xbox gaming machine with or without a Kinect.RTM. Gesture input device), and / or Or may include an electronic device such as a personal messaging device.

  Although distributed system 1400 of FIG. 14 is shown with four client computing devices, it may support any number of client computing devices. Other devices, such as devices having sensors or the like may interact with server 1412.

  A variety of networks 1410 in distributed system 1400 may be used, including but not limited to TCP / IP (Transmission Control Protocol / Internet Protocol), SNA (Systems Network Architecture), IPX (Internet Packet Switching), Apple Talk, etc. Any type of network well known to those skilled in the art that can support data communication using any of the above protocols. By way of example only, network 1410 may be a local area network (LAN), Ethernet based network, token ring, wide area network, Internet, virtual network, virtual private network (VPN), intranet, extranet, public switched telephone Network (PSTN), infrared network, wireless network (eg, one of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 protocol suite, Bluetooth, and / or any other wireless protocol) And / or combinations thereof and / or other networks.

  The server 1412 includes one or more general-purpose computers, a dedicated server computer (for example, a PC (personal computer) server, a UNIX (registered trademark) server, a midrange server, a mainframe computer, a rack mount server, etc.), a server It may be configured with a farm, server cluster, or any other suitable configuration and / or combination. Server 1412 may include one or more virtual machines running virtual operating systems or other computing architectures with virtualization. By virtualizing one or more flexible pools of logical storage, virtual storage for the server can be maintained. The virtual network can be controlled by server 1412 using software defined networking. In various embodiments, server 1412 may be configured to execute one or more services or software applications described in the previous disclosures. For example, server 1412 may correspond to a server for performing the above-described processing in accordance with certain embodiments of the present disclosure.

  The server 1412 may execute an operating system including any of the above and any commercially available server operating system. Server 1412 may also include various other server applications, including HTTP (hypertext transport protocol) servers, FTP (file transfer protocol) servers, CGI (common gateway interface) servers, JAVA servers, database servers, etc. And / or any of the mid-tier applications may be run. Representative database servers include, but are not limited to, those commercially available from Oracle, Microsoft, Sybase, IBM (International Business Machines) and the like.

  In some implementations, server 1412 may include one or more applications for analyzing and integrating data feeds and / or event updates received from users of client computing devices 1402, 1404, 1406, and 1408. As an example, data feeds and / or event updates may be real-time events related to sensor data applications, stock tickers, network performance measurement tools (eg network monitoring and traffic management applications), clickstream analysis tools, automotive traffic monitoring etc. , Including, but not limited to, Twitter® feeds, Facebook® updates, or real-time updates, received from one or more third party sources and continuous data streams, which may include, Also, server 1412 may include one or more applications for displaying data feeds and / or real-time events via one or more displays of client computing devices 1402, 1404, 1406, and 1408.

  Distributed system 1400 may also include one or more databases 1414 and 1416. These databases may provide a mechanism for storing information such as user interaction information, usage pattern information, conformance rule information, and other information used by embodiments of the present invention. Databases 1414 and 1416 may exist in various places. As an example, one or more of databases 1414 and 1416 may reside on non-transitory storage media local to (and / or present at) server 1412. Alternatively, databases 1414 and 1416 may be remote from server 1412 and communicate with server 1412 via a network-based or dedicated connection. In one set of embodiments, databases 1414 and 1416 may be in a storage area network (SAN). Similarly, files needed to perform functions originating from server 1412 may optionally be stored locally at server 1412 and / or stored remotely. In one set of embodiments, databases 1414 and 1416 may include a relational database, such as an Oracle-provided database, configured to store, update, and retrieve data in response to commands in SQL format.

  FIG. 15 shows an exemplary computer system 1500 that may be used to implement an embodiment of the present invention. In some embodiments, computer system 1500 may be used to implement any of the various servers and computer systems described above. As shown in FIG. 15, computer system 1500 includes various subsystems including processing unit 1504 that communicates with a number of peripheral subsystems via bus subsystem 1502. These peripheral subsystems may include processing acceleration unit 1506, I / O subsystem 1508, storage subsystem 1518, and communication subsystem 1524. Storage subsystem 1518 may include tangible computer readable storage media 1522 and system memory 1510.

  Bus subsystem 1502 provides a mechanism for letting the various components and subsystems of computer system 1500 communicate with one another as desired. Although bus subsystem 1502 is schematically illustrated as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses. Bus subsystem 1502 may be any of various types of bus structures, including a memory bus or memory controller, a peripheral bus, and a local bus, using any of a variety of bus architectures. For example, such an architecture may be implemented as an industry standard architecture (ISA) bus, a microchannel architecture (MCA) bus, an enhanced ISA (EISA) bus, which may be implemented as a Mezzanine bus etc. manufactured according to the IEEE P1386.1 standard. It may include a Video Electronics Standards Association (VESA) local bus, and a peripheral component interconnect (PCI) bus.

  Processing subsystem 1504 controls the operation of computer system 1500 and may include one or more processing units 1532 1534, and so on. The processing unit may include one or more processors, including single or multi-core processors, one or more cores of processors, or a combination thereof. In some embodiments, processing subsystem 1504 may include one or more dedicated co-processors, such as graphic processors, digital signal processors (DSPs), and the like. In some embodiments, some or all of the processing units of processing subsystem 1504 are implemented using customized circuits such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). May be

  In some embodiments, a processing unit within processing subsystem 1504 can execute instructions stored in system memory 1510 or on computer readable storage medium 1522. In various embodiments, a processing unit may execute various program or code instructions and may maintain multiple programs or processes executing simultaneously. At a given time, some or all of the program code to be executed may be in system memory 1510 and / or on computer readable storage medium 1522, possibly including one or more storage devices. Through appropriate programming, the processing subsystem 1504 can provide the various capabilities described above to provide users with access to services using existing services provisioned by the cloud infrastructure system.

  In particular embodiments, to accelerate the overall process performed by computer system 1500, to perform a customized process, or to offload some of the processes performed by processing subsystem 1504. A processing acceleration unit 1506 may be provided.

  I / O subsystem 1508 may include devices and mechanisms for entering information into computer system 1500 and / or outputting information from or through computer system 1500. In general, use of the term “input device” is intended to include all possible types of devices and mechanisms for inputting information into computer system 1500. The user interface input device may be, for example, a keyboard, a pointing device such as a mouse or a trackball, a touch pad or touch screen incorporated in a display, a scroll wheel, a click wheel, a dial, a button, a switch, a keypad, a voice command recognition system It may include a built-in voice input device, a microphone, and other types of input devices. The user interface input device also allows the user to control the input device and interact with the input device Microsoft Kinect® motion sensor, Microsoft Xbox® 360 game controller, input using gestures and speech commands A motion sensing and / or gesture recognition device may be included, such as a device providing an interface to receive. The user interface input device may also receive eye movements from the user (e.g. "blink" when taking a picture and / or when selecting a menu) and input eye gestures as input to the input device (e.g. Google Glass (R)) It may include an eye gesture recognizer such as a Google Glass® blink detector to convert. In addition, the user interface input device may include a speech recognition detection device that allows the user to interact with the speech recognition system (eg, Siri® navigator) through speech commands.

  Other examples of user interface input devices are three-dimensional (3D) mice, joysticks or pointing sticks, game pads and graphic tablets, and speakers, digital cameras, digital camcorders, portable media players, webcams, image scanners, fingerprint scanners And audio / visual devices such as, but not limited to, barcode readers 3D scanners, 3D printers, laser range finders, and eye tracking devices. In addition, the user interface input device may include, for example, medical imaging input devices such as computed tomography, magnetic resonance imaging, positron emission tomography, echography and the like. The user interface input device may also include an audio input device such as, for example, a MIDI keyboard, digital music equipment, and the like.

  The user interface output device may include a display subsystem, an indicator light, or a non-visual display such as an audio output device. The display subsystem may be a cathode ray tube (CRT), eg a flat panel device using a liquid crystal display (LCD) or a plasma display, a projection device, a touch screen etc. In general, use of the term "output device" is intended to include all possible types of devices and mechanisms for outputting information from computer system 1500 to a user or other computer. For example, user interface output devices include various display devices that visually convey text, graphic and audio / video information, such as monitors, printers, speakers, headphones, car navigation systems, plotters, audio output devices, and modems. But not limited thereto.

  Storage subsystem 1518 provides a repository or data storage device for storing information for use by computer system 1500. Storage subsystem 1518 provides a tangible non-transitory computer readable storage medium for storing basic programming and data structures that provide the functionality of some embodiments. Software (programs, code modules, instructions) that provide the above functionality when executed by processing subsystem 1504 may be stored in storage subsystem 1518. The software may be executed by one or more processing units of processing subsystem 1504. Storage subsystem 1518 may also provide a repository for storing data used in accordance with the present invention.

  Storage subsystem 1518 may include one or more non-transitory memory devices, including volatile and non-volatile memory devices. As shown in FIG. 15, storage subsystem 1518 includes system memory 1510 and computer readable storage media 1522. The system memory 1510 includes a number of volatile main random access memory (RAM) for storing instructions and data during program execution and a non-volatile read only memory (ROM) or flash memory where fixed instructions are stored. It may include memory. In some implementations, for example, a basic input / output system (BIOS), which includes basic routines to assist information transfer between elements within the booting computer system 1500, is generally stored in ROM. Ru. The RAM typically includes data and / or program modules that the processing subsystem 1504 is currently operating and executing. In some implementations, system memory 1510 may include multiple memories of different types, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

  By way of example and not limitation, as shown in FIG. 15, system memory 1510 may include an application program 1512 that may include a client application, a web browser, a mid-tier application, a Relationalator-based management system (RDBMS), etc. , Operating system 1516 may be stored. As an example, operating system 1516 may be various versions of Microsoft Windows®, Apple Macintosh®, and / or Linux® operating systems, various commercial UNIX® or UNIX-like. Operating systems (including but not limited to various GNU / Linux operating systems, Google Chrome (R) OS etc) and / or iOS, Windows (R) Phone, Android (R) Various mobile operating systems may be included, such as OS, BlackBerry® 10 OS, and Palm® OS operating system.

  Computer readable storage medium 1522 may store programming and data structures that provide the functionality of some embodiments. Software (programs, code modules, instructions) that provide the above functionality when executed by the processor of processing subsystem 1504 may be stored in storage subsystem 1518. By way of example, computer readable storage medium 1522 may include non-volatile memory such as an optical disk drive such as a hard disk drive, a magnetic disk drive, a CD ROM, a DVD, a Blu-Ray® disk, or other optical media. . Computer readable storage media 1522 may include, but is not limited to, Zip® drive, flash memory card, Universal Serial Bus (USB) flash drive, Secure Digital (SD) card, DVD disc, digital video tape, etc. It is not something to be done. The computer readable storage medium 1522 may also be volatile memory such as solid state drive (SSD) based on non-volatile memory such as flash memory based SSD, enterprise flash drive, solid state ROM etc, solid state RAM, dynamic RAM, static RAM etc , A DRAM based SSD, a magnetoresistive RAM (MRAM) SSD, and a hybrid SSD, using a combination of SSD based, DRAM combined with flash memory based SSD. Computer readable media 1522 may provide storage for computer readable instructions, data structures, program modules, and other data for computer system 1500.

  In particular embodiments, storage subsystem 1500 may also include a computer readable storage medium reader 1520 that may be further connected to computer readable storage medium 1522. Computer readable storage medium 1522, in conjunction with, and optionally in combination with, system memory 1510 is remote, local, fixed and / or removable storage plus storage for storing computer readable information. The medium can be represented generically.

  In particular embodiments, computer system 1500 may provide support for running one or more virtual machines. Computer system 1500 may execute programs, such as a hypervisor, to facilitate configuration and management of virtual machines. Each virtual machine may be assigned memory, computing (e.g., processor, core), I / O, and networking resources. Each virtual machine typically runs its own operating system, which may be the same as or different from the operating systems run by other virtual machines that computer system 1500 executes. Thus, in some cases, multiple operating systems may be concurrently executed by computer system 1500. In general, each virtual machine runs independently of the other virtual machines.

  Communications subsystem 1524 provides an interface to other computer systems and networks. Communication subsystem 1524 serves as an interface for receiving data from systems other than computer system 1500 and transmitting data to systems other than computer system 1500. For example, communication subsystem 1524 allows computer system 1500 to establish a communication channel over the Internet to one or more client devices to receive information from the client device and transmit information to the client device. Will.

  Communication subsystem 1524 may support both wired and / or wireless communication protocols. For example, in particular embodiments, communications subsystem 1524 may be an advanced data network technology (eg, cellular technology, 3G, 4G or EDGE (Global Evolved High Data Rate), WiFi (IEEE 802.11 family standard, or others), etc. Mobile radio technology (or any combination thereof)) radio frequency (RF) transceiver components for accessing wireless voice and / or data networks, global positioning system (GPS) receiver components, and / or other Components of the The communications subsystem 1524 of some embodiments may provide a wired network connection (eg, Ethernet) in addition to or in place of the wireless interface.

  Communications subsystem 1524 can receive and transmit various forms of data. For example, in some embodiments, communications subsystem 1524 may receive input communications in the form of structured and / or unstructured data feeds 1526, event streams 1528, event updates 1530, etc. For example, the communication subsystem 1524 may be a web feed such as Twitter (R) feed, Facebook (R) update, rich site summary (RSS) feed, etc. in real time from users of social media networks and / or other communication services. And / or may be configured to receive (or transmit) data feeds 1526, such as real-time updates from one or more third party sources.

  In particular embodiments, communications subsystem 1524 may include continuous streams of real-time events, which may be event streams 1528 and / or event updates 1530, which may be essentially continuous or infinite and without a definite end. It may be configured to receive data in the form of a stream. Examples of applications that generate continuous data may include, for example, sensor data applications, stock tickers, network performance measurement tools (eg, network monitoring and traffic management applications), click stream analysis tools, automotive traffic monitoring, etc.

  Communications subsystem 1524 may also include structured and / or unstructured data feeds 1526, event streams 1528, event updates 1530, etc., with one or more streaming data source computers coupled to computer system 1500. It may be configured to output to one or more databases that may communicate.

  Computer system 1500 may be a handheld portable device (e.g., an iPhone mobile phone, an iPad® computing tablet, a PDA), a wearable device (e.g., a Google Glass® head mounted display), a personal computer, a workstation, It may be one of a variety of types, including mainframes, kiosks, server racks, or other data processing systems.

  Because computers and networks are of a constantly changing nature, the description of computer system 1500 shown in FIG. 15 is intended for the specific example only. Many other configurations are possible, with more or fewer components than the system shown in FIG. Based on the disclosures and teachings provided herein, one of ordinary skill in the art will understand other ways and / or methods of implementing various embodiments.

FIG. 16 shows an exemplary service infrastructure system 1600 that may be used to implement an embodiment of the present invention. As shown in FIG. 16, service infrastructure system 1600 includes a processing subsystem 1602 and a communication subsystem 1604. For example, processing subsystem 1602 and communication subsystem 1604 may be processing subsystem 1504 and communication subsystem 1524 shown in FIG. 15, respectively. The processing subsystem 1602 is configured to provide a plurality of services to the service infrastructure system, and the communication subsystem 1604 receives a request by the first customer for access to the service provided by the service infrastructure system. Configured Further, processing subsystem 1602
Configured to determine the type of subscription based on the service requested by the first customer, the type of subscription being either a clone subscription or a reusable subscription,
A subscription for accessing the service is configured to be provided to a first customer, the subscription being provided based on the type of subscription and provided using a first service of the plurality of services And
It is configured to manage the subscription provided to the first customer.

  In certain embodiments, the first customer request indicates the type of use of the service by the customer, and the type of subscription is determined based on the type of use indicated by the request.

In certain embodiments, providing the subscription to the first customer when the type of subscription is a clone subscription is:
Establishing a first clone subscription based on a first subscription to a first service, the first clone subscription being provided as a subscription to a first customer,
Including associating the first clone subscription with the first subscription based on a set of rules.

  In certain embodiments, associating the first clone subscription with the first subscription includes associating the first clone subscription life cycle with the first subscription life cycle.

  In certain embodiments, the first clone subscription provides access to the second service, and access by the customer to the second service is when the customer has finished accessing the first service. finish.

  In certain embodiments, the processing subsystem 1602 is further configured to update access to the first service based on a request from the customer, and based on the updated access to the first service. Configured to correct access to the service of.

  In certain embodiments, the first clone subscription provides access to a second service, and the set of rules indicates the use of the second service as a clone of the first service.

In certain embodiments, a set of rules indicates a duration of access to a second service.
In a particular embodiment, the set of rules indicates the number of users authorized to access the second service, and the number of users authorized to access the second service is the number of users to the first service. Different from the number of users authorized to access.

  In a particular embodiment, the set of rules indicates the configuration of the second service, and the configuration of the second service is different than the configuration of the first service.

  In certain embodiments, managing the subscription comprises determining access to the requested service by the subscription in response to the change of the first service, wherein access to the requested service is: It is determined using a set of rules.

In certain embodiments, providing the subscription to the first customer when the subscription type is a reusable subscription is:
Determining that a first service is provisioned in a service pool in the service infrastructure system;
Provisioning the first service for the first subscription in the service pool when it is determined that the first service for the subscription is not provisioned in the service pool;
Assigning a first subscription for the first service to the customer as a subscription for the service, and assigning the first subscription comprises assigning the first service to the customer from the service pool Assigning the first service to the customer includes deleting the first service from the service pool.

  In particular embodiments, processing subsystem 1602 is further configured to associate customer-specific data with service-specific data corresponding to the first service, wherein customer-specific data is transmitted to the customer for the first service. It is matched.

  In certain embodiments, managing a subscription for accessing a service includes assigning a first service from a customer to a service pool when the subscription is terminated, assigning the first service , Removing the correspondence between the data for specific customer and the data for specific service corresponding to the first service, wherein the first service can be reassigned from the service pool to one or more other customers. .

In particular embodiments, communication subsystem 1604 is further configured to receive a request by a second customer of access to a second service of the plurality of services, and processing subsystem 1602 is further configured to:
Configured to determine that the second service is available in the service pool based on the determination that the second service is similar to the first service,
Assigning a first subscription in the service pool to a second customer, and assigning the first subscription to a second customer includes deleting the first subscription from the service pool ,
The data for specific customer corresponding to the second customer is configured to correspond to the data for specific service corresponding to the first service.

  In particular embodiments, the customer-specific data associated with the first customer includes data related to the use of the first service by the customer.

  In particular embodiments, each service of the plurality of services is associated with data for a particular service, the data for a particular service corresponding to the service indicates the configuration of the service, and the configuration provides the service. Include one or more resources assigned to

  In certain embodiments, providing the service includes provisioning the service in the cloud infrastructure system prior to receiving a request from the first customer, the service being associated with the operation of the service infrastructure system Provisioned based on one or more metrics.

  In certain embodiments, providing the service includes provisioning the service prior to receiving a request by the first customer, the service being based on one or more metrics associated with the demand for the service. Provisioned

  In certain embodiments, providing the service includes provisioning the service prior to receiving a request by the first customer, the service being based on one or more metrics associated with the type of service. Provisioned

  In particular embodiments, service infrastructure system 1600 includes a multi-tenant environment.

  In particular embodiments, services include Java services, customer relationship management (CRM) services, or human resource management (HCM) services.

  While particular embodiments of the present invention have been described, various alternatives, modifications, alternative constructions and equivalents are also included within the scope of the present invention. Embodiments of the present invention are not limited to operating within a particular specific data processing environment, but can operate freely within multiple data processing environments. Furthermore, while the embodiments of the invention have been described using a particular set of transactions and steps, it is to be understood that the scope of the present invention is not limited to the set of transactions and steps described. It should be clear to the trader.

  Furthermore, while specific embodiments of the invention have been described using a specific combination of hardware and software, it should be appreciated that other combinations of hardware and software are within the scope of the invention. is there. Embodiments of the present invention may be implemented in hardware only, software only, or a combination thereof. The various processes described herein may be implemented on the same processor or on various processors in any combination. Thus, although the component or module is described as being configured to perform some operations, such an arrangement may operate, for example, by designing an electronic circuit to perform the operations. This can be accomplished by programming an electronic circuit (such as a microprocessor) that is programmable to run, or by combining these. The processes may communicate using various techniques, including but not limited to conventional techniques for inter-process communication, and different pairs of processes may use different techniques or the same pair of The process may use different techniques at different times.

  Therefore, the specification and drawings should be considered in an illustrative rather than a restrictive sense. However, it will be apparent that additions, reductions, deletions and other variations and modifications may be made thereto without departing from the broader spirit and scope as set forth in the claims. Thus, although specific inventive embodiments have been described, these are not intended to be limiting. Various modifications and equivalents are within the scope of the following claims.

Claims (24)

A computer-implemented method,
Providing multiple services to the service infrastructure system;
The service infrastructure system receives a request by a first customer of access to a service provided by the service infrastructure system;
The service infrastructure system determining, based on the request, a type of use of the service for which access is requested;
The service infrastructure system determines the type of subscription based on the type of use of the service requested by the first customer, the type of subscription being a clone subscription or reusable One of the subscriptions, wherein the type of subscription enables access to the service based on one of the plurality of services provisioned before the service is requested The first service is one of the plurality of services, and the reusable subscription is configured to access the service, the service of the one of the plurality of services, and the first service. Be configured as a service requested by the customer Based on possible, the clones subscription access to the service, to allow on the basis that provision the service in accordance with the configuration of provisioned said one service before the service is requested,
The service infrastructure system identifies the first service of the plurality of services that is configurable to provide the requested service of the type of use based on the type of subscription. Step and
The service infrastructure system provides the first customer with a subscription for accessing the service, wherein the subscription for accessing the service is such that the type of subscription is reusable Provided by configuring the first service as the service based on the determination that it is a subscription, and for accessing the service based on the determination that the type of the subscription is the clone subscription Subscription is provided by provisioning one or more resources for the service and configuring the service according to the configuration of the first service,
A method wherein the service infrastructure system manages the subscription provided to the first customer.   The computer-implemented method of claim 1, wherein the first service of the plurality of services is identified as already provisioned in a service pool by the service infrastructure system. Providing the subscription to the first customer when the type of subscription is the clone subscription:
Establishing a first clone subscription based on a first subscription to the first service, the first clone subscription being provided as a subscription to the first customer,
The computer-implemented method of claim 1 or 2, including the step of associating the first clone subscription with the first subscription based on a set of rules.   The method according to claim 3, wherein the step of associating the first clone subscription with the first subscription includes the step of associating the life cycle of the first clone subscription with the life cycle of the first subscription. Computer-implemented method.   The service enabled by the first clone subscription is a second service different from the first service, the second service is one of the plurality of services, the first 5. The computer-implemented method of claim 4, wherein access to the second service by a customer of is terminated when access to the first service by the first customer is terminated. Updating access to the first service based on a request from the first customer;
6. The computer-implemented method of claim 5, further comprising: modifying access to the second service based on the updated access to the first service.   The first clone subscription provides access to a second service, the second service is one of the plurality of services, and the set of rules includes the first service. The computer-implemented method of claim 3, which illustrates the use of the second service as a clone of. The first service of the plurality of services is identified as already provisioned in a service pool by the service infrastructure system,
Receiving a request by a second customer of access to the second service of the plurality of services;
Determining that the second service is available in the service pool based on the determination that the second service is similar to the first service;
Assigning the first subscription in the service pool to the second customer, the step of assigning the first subscription to the second customer comprising the step of assigning the first subscription to the service. Including the step of removing from the pool,
The computer-implemented method according to claim 5 or 7, including the step of associating specific customer data corresponding to the second customer with specific service data corresponding to the first service.   The computer-implemented method of claim 7, wherein the set of rules indicates a duration of access to the second service.   The set of rules indicates the number of users authorized to access the second service, and the number of users authorized to access the second service is the access to the first service The computer-implemented method of claim 7, wherein is different from the number of authorized users.   The computer-implemented computer program of claim 7, wherein the set of rules indicates a configuration of the second service, and the configuration of the second service is different than the configuration of the first service. Method.   The step of managing the subscription includes determining access to the requested service by the subscription in response to a change of the first service, the access to the requested service comprising: The computer-implemented method of claim 3, wherein the method is determined using a set of rules. Providing the subscription to the first customer when the type of subscription is the reusable subscription:
Determining that the first service is provisioned in a service pool in the service infrastructure system;
Assigning a first subscription for the first service to the first customer as a subscription for the service, the step of assigning the first subscription comprising: Assigning the first service to the first customer from the service pool, and assigning the first service to the first customer includes deleting the first service from the service pool. the method implemented by a computer according to any one of 1 to 12.   The method according to claim 1, further comprising the step of associating data for specific customer with data for specific service corresponding to the first service, wherein the data for specific customer is corresponded to the first customer of the first service. The computer-implemented method according to claim 13.   Managing the subscription for accessing the service includes assigning the first service from the first customer to the service pool when the subscription is terminated, the first service The step of assigning a request includes releasing the correspondence between the data for specific customer and the data for specific service corresponding to the first service, wherein the first service includes at least one other from the service pool. The computer-implemented method of claim 14, wherein the computer-implemented method is reassignable to a customer of The specific customer data associated with the first customer, including data relating to use of the first service by the first customer is realized by a computer according to claim 14 or 15 Method.   Each service of the plurality of services is associated with data for specific service, the data for specific service corresponding to the service indicates a configuration of the service, and the configuration is for providing the service. A computer-implemented method according to any one of the preceding claims, comprising one or more allocated resources.   The step of providing the service includes the step of provisioning a service in the service infrastructure system before receiving a request from the first customer, wherein the service is associated with the operation of the service infrastructure system 18. The computer-implemented method of any of the preceding claims, wherein the method is provisioned based on one or more metrics.   Providing the service includes provisioning the service prior to receiving a request from the first customer, wherein the service is provisioned based on one or more metrics associated with the demand for the service. A computer-implemented method according to any one of the preceding claims.   Providing the service includes provisioning the service before receiving a request from the first customer, the service being provisioned based on one or more metrics associated with the type of service A computer-implemented method according to any one of the preceding claims.   The computer-implemented method of any one of the preceding claims, wherein the service infrastructure system comprises a multi-tenant environment.   22. The computer-implemented method of any of the preceding claims, wherein the service comprises a Java service, a customer relationship management (CRM) service, or a human resource management (HCM) service. . A system,
At least one processor,
A memory operatively coupled to the at least one processor, the at least one processor executing computer code stored in the memory;
Provide multiple services to the service infrastructure system,
Receiving a request by a first customer of access to services provided by the service infrastructure system,
Determine the type of use of the service for which access is requested, based on the request;
Determining a type of subscription based on the type of use of the service requested by the first customer, the type of subscription being one of a clone subscription or a reusable subscription, The type of subscription enables access to the service based on a service of the plurality of services provisioned before the service is requested, a first service being the plurality of services Wherein the reusable subscription configures access to the service as a service requested by the first customer from one of the plurality of services. Enabling the clone subscription based on the Access to screws allows based on provisioning a service in accordance with configuration of provisioned said one service before the service is requested,
Identifying the first service of the plurality of services configurable based on the type of subscription to provide the requested service of the type of use;
Providing the first customer with a subscription for accessing the service, the subscription for accessing the service being based on the determination that the type of subscription is the reusable subscription A subscription for accessing the service based on the determination that the first service is configured as the service, and the type of subscription is the clone subscription; Provisioning one or more resources and configuring the service according to the configuration of the first service,
A system for managing the subscription provided to the first customer.   A program for causing a computer to execute the method according to any one of claims 1 to 22.