# US 2022/0067607 A1 · Cloud resources allocation system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0067607 A1
- Document ID: US20220067607A1
- Status: Published application
- Kind: A1
- Application number: 17/003,412
- Filed: 2020-08-26
- Published: 2022-03-03
- Earliest claimed: 2020-08-26
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: ASHISH KUMAR; Kishan PATEL; Travis HUGHES; Mathew VERGHESE; Saugata MONDAL; Pradeep KHANDELWAL
- Web page: https://patentgrep.com/patent/US20220067607A1

## CPC

- G06Q 30/08: Auctions
- G06F 9/5072: {Grid computing}
- G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)}
- G06Q 10/06312: {Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling}
- G06Q 10/06315: {Needs-based resource requirements planning or analysis}
- G06Q 20/085: {involving remote charge determination or related payment systems}
- H04L 47/70: Admission control; Resource allocation
- H04L 47/76: using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
- H04L 47/781: {Centralised allocation of resources}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- G06Q 20/145: {Payments according to the detected use or quantity}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Disclosed herein are various embodiments for a cloud resources allocation system. An embodiment operates by determining that an application requests a plurality of instances to execute across one or more processors of a cloud services platform. One or more spare instances are requested to fulfill at least a portion of the plurality of instances, and an allocation of at least a subset of the requested one or more spare instances is received. An execution of the application is directed to the allocated subset of the one or more spare instances, including a first spare instance. A notification is received from the cloud services platform that the first spare instance is to be reallocated to a different process. A subsequent execution of the application is redirected to an on demand instance of the cloud services platform.

## Claims

### Claim 1

A computer-implemented method for efficient utilization of cloud computing services, comprising:
determining that an application requests a plurality of instances to execute across one or more processors of a cloud services platform;
requesting, from the cloud services platform, one or more spare instances to fulfill at least a portion of the plurality of instances, wherein each spare instance comprises an unused processing capacity of the cloud services platform that is available for allocation such that the cloud services platform reserves a right to reallocate the spare instance;
receiving an allocation of at least a subset of the requested one or more spare instances;
directing an execution of the application to the allocated subset of the one or more spare instances, including a first spare instance;
receiving a notification from the cloud services platform that the first spare instance is to be reallocated to a different process; and
redirecting a subsequent execution of the application to an on demand instance of the cloud services platform, that was allocated for the application prior to the determining, instead of the first spare instance.

### Claim 2 (depends on 1)

The method of claim 1, wherein the cloud services platform charges a greater price for executing the application using the on demand instance than using the first spare instance, wherein the on demand instance includes service guarantee from the cloud services platform that is not provided with the first spare instance.

### Claim 3 (depends on 2)

The method of claim 2, wherein the requesting comprises:
identifying, by a processor, a cost of the first spare instance;
automatically submitting, by the processor, a bid for the first spare instance based on the cost; and
determining, by the processor, that the bid was accepted and the first spare instance was allocated for use by the application by the cloud services platform.

### Claim 4 (depends on 3)

The method of claim 3, wherein the identifying the cost comprises:
determining that the cloud services platform includes a plurality of different availability zones, wherein each availability zone includes spare instance capacity for a particular price;
identifying a cost of the spare instances in each availability zone; and
selecting, by the processor, the first spare instance in the availability zone with the lowest cost, wherein the bid is submitted on the selected first spare instance.

### Claim 5 (depends on 2)

The method of claim 2, wherein at least one on demand instance is maintained for executing the application on the cloud services platform.

### Claim 6 (depends on 5)

The method of claim 5, wherein the requesting comprises:
identifying a cost of the first spare instance;
submitting a bid for the first spare instance based on the cost;
determining by the processor, that the bid was rejected; and
executing the application on the at least one maintained on demand instance until a subsequent spare instance bid is accepted.

### Claim 7 (depends on 1)

The method of claim 1, wherein the notification indicates a timeout period before the first spare instance is to be deallocated by the cloud services platform, and wherein the application is stateless.

### Claim 8

A system for efficient utilization of cloud computing services, comprising:
a memory; and
at least one processor coupled to the memory and configured to perform operations comprising:
determining that an application requests a plurality of instances to execute across one or more processors of a cloud services platform;
requesting, from the cloud services platform, one or more spare instances to fulfill at least a portion of the plurality of instances, wherein each spare instance comprises an unused processing capacity of the cloud services platform that is available for allocation such that the cloud services platform reserves a right to reallocate the spare instance;
receiving an allocation of at least a subset of the requested one or more spare instances;
directing an execution of the application to the allocated subset of the one or more spare instances, including a first spare instance;
receiving a notification from the cloud services platform that the first spare instance is to be reallocated to a different process; and
redirecting a subsequent execution of the application to an on demand instance of the cloud services platform, that was allocated for the application prior to the determining, instead of the first spare instance.

### Claim 9 (depends on 8)

The system of claim 8, wherein the cloud services platform charges a greater price for executing the application using the on demand instance than using the first spare instance, wherein the on demand instance includes service guarantee from the cloud services platform that is not provided with the first spare instance.

### Claim 10 (depends on 9)

The system of claim 9, wherein the requesting operations comprise:
identifying, by a processor, a cost of the first spare instance;
automatically submitting, by the processor, a bid for the first spare instance based on the cost; and
determining, by the processor, that the bid was accepted and the first spare instance was allocated for use by the application by the cloud services platform.

### Claim 11 (depends on 10)

The system of claim 10, wherein the identifying the cost operations comprise:
determining that the cloud services platform includes a plurality of different availability zones, wherein each availability zone includes spare instance capacity for a particular price;
identifying a cost of the spare instances in each availability zone; and
selecting, by the processor, the first spare instance in the availability zone with the lowest cost, wherein the bid is submitted on the selected first spare instance.

### Claim 12 (depends on 9)

The system of claim 9, wherein at least one on demand instance is maintained for executing the application on the cloud services platform.

### Claim 13 (depends on 12)

The system of claim 12, wherein the requesting operations comprise:
identifying a cost of the first spare instance;
submitting a bid for the first spare instance based on the cost;
determining by the processor, that the bid was rejected; and
executing the application on the at least one maintained on demand instance until a subsequent spare instance bid is accepted.

### Claim 14 (depends on 8)

The system of claim 8, wherein the notification indicates a timeout period before the first spare instance is to be deallocated by the cloud services platform, and wherein the application is stateless.

### Claim 15

A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations for efficient utilization of cloud computing services, the operations comprising:
determining that an application requests a plurality of instances to execute across one or more processors of a cloud services platform;
requesting, from the cloud services platform, one or more spare instances to fulfill at least a portion of the plurality of instances, wherein each spare instance comprises an unused processing capacity of the cloud services platform that is available for allocation such that the cloud services platform reserves a right to reallocate the spare instance;
receiving an allocation of at least a subset of the requested one or more spare instances;
directing an execution of the application to the allocated subset of the one or more spare instances, including a first spare instance;
receiving a notification from the cloud services platform that the first spare instance is to be reallocated to a different process; and
redirecting a subsequent execution of the application to an on demand instance of the cloud services platform, that was allocated for the application prior to the determining, instead of the first spare instance.

### Claim 16 (depends on 15)

The device of claim 15, wherein the cloud services platform charges a greater price for executing the application using the on demand instance than using the first spare instance, wherein the on demand instance includes service guarantee from the cloud services platform that is not provided with the first spare instance.

### Claim 17 (depends on 16)

The device of claim 16, wherein the requesting operations comprise:
identifying, by a processor, a cost of the first spare instance;
automatically submitting, by the processor, a bid for the first spare instance based on the cost; and
determining, by the processor, that the bid was accepted and the first spare instance was allocated for use by the application by the cloud services platform.

### Claim 18 (depends on 17)

The device of claim 17, wherein the identifying the cost operations comprise:
determining that the cloud services platform includes a plurality of different availability zones, wherein each availability zone includes spare instance capacity for a particular price;
identifying a cost of the spare instances in each availability zone; and
selecting, by the processor, the first spare instance in the availability zone with the lowest cost, wherein the bid is submitted on the selected first spare instance.

### Claim 19 (depends on 16)

The device of claim 16, wherein at least one on demand instance is maintained for executing the application on the cloud services platform.

### Claim 20 (depends on 19)

The device of claim 19, wherein the requesting operations comprise:
identifying a cost of the first spare instance;
submitting a bid for the first spare instance based on the cost;
determining by the processor, that the bid was rejected; and
executing the application on the at least one maintained on demand instance until a subsequent spare instance bid is accepted.
