# US 2024/0179053 A1 · Continuous scheduling for automated suspension and resumption of cloud resources

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

- Number: US 2024/0179053 A1
- Document ID: US20240179053A1
- Status: Published application
- Kind: A1
- Application number: 18/059,566
- Filed: 2022-11-29
- Published: 2024-05-30
- Earliest claimed: 2022-11-29
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Clayton MOTTLEY; Loreeg TRAMBLIAN; Cameron MAYES; Amy Ann MAXWELL; Kevin HO; Torrance GRAHAM; Robert WRIGHT
- Web page: https://patentgrep.com/patent/US20240179053A1

## CPC

- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 41/0886: {Fully automatic configuration}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In some implementations, a scheduling system may receive a scheduling tag to define a custom schedule that includes one or more downtime windows for a cloud resource over a scheduling period. The scheduling system may determine a regular continuous schedule for the cloud resource that recurs over multiple scheduling periods based on the one or more downtime windows defined in the scheduling tag. The scheduling system may determine at a current scan time, whether a target state for the cloud resource is a running state or a suspended state based on the one or more uptime windows and the one or more downtime windows included in the regular continuous schedule. The scheduling system may align a current state of the cloud resource with the target state.

## Claims

### Claim 1

A system for automated suspension and resumption of cloud resources based on continuous scheduling, the system comprising:
one or more memories; and
one or more processors, coupled to the one or more memories, configured to:
receive a scheduling tag to define a custom schedule that includes at least one first window for a cloud resource over a scheduling period,
wherein the scheduling tag includes a value to express the at least one first window using a syntax that is compatible with an external metadata format supported by the cloud resource;
determine a regular continuous schedule for the cloud resource that recurs over multiple scheduling periods based on the at least one first window defined in the scheduling tag,
wherein the regular continuous schedule includes the at least one first window and at least one second window, wherein the at least one second window covers time periods during the scheduling period that are not covered by the at least one first window;
determine, at a first scan time and within a window of the at least one first window or the at least one second window, whether the cloud resource is in alignment with a target state for the cloud resource in accordance with the regular continuous schedule;
align, based at least in part on the determination at the first scan time, the cloud resource with the target state in accordance with the regular continuous schedule;
determine, at a second scan time after the first scan time and within the window corresponding to the first scan time, whether the cloud resource is in alignment with the target state for the cloud resource in accordance with the regular continuous schedule; and
align, based at least in part on the determination at the second scan time, the cloud resource with the target state in accordance with the regular continuous schedule.

### Claim 2 (depends on 1)

The system of claim 1, wherein the at least one first window comprises one or more uptime windows, and wherein the one or more processors, to align the cloud resource with the target state, are configured to:
determine that the target state for the cloud resource at the second scan time is a running state based on the second scan time being within the one or more uptime windows; and
resume the cloud resource based on determining, at the second scan time, that the cloud resource is in a suspended state.

### Claim 3 (depends on 1)

The system of claim 1, wherein the at least one second window comprises one or more downtime windows, and wherein the one or more processors, to align the cloud resource with the target state, are configured to:
determine that the target state for the cloud resource at the second scan time is a suspended state based on the second scan time being within the one or more downtime windows; and
suspend the cloud resource based on determining, at the second scan time, that the cloud resource is in a running state.

### Claim 4 (depends on 1)

The system of claim 1, wherein the one or more processors are configured to perform a point-in-time evaluation to determine the target state for the cloud resource and align a current state of the cloud resource with the target state at periodic intervals.

### Claim 5 (depends on 1)

The system of claim 1, wherein the at least one first window comprises one or more uptime windows, and wherein the value of the scheduling tag defines the one or more uptime windows according to a multi-day syntax that specifies a starting time and an ending time associated with multiple days, a single-day syntax that specifies a starting time and an ending time associated with a single day, or an overnight syntax that specifies a starting time on a first day and an ending time on a second day.

### Claim 6 (depends on 1)

The system of claim 1, wherein the one or more processors are further configured to:
receive an override to define a scheduled state for the cloud resource that takes precedence over the target state associated with the regular continuous schedule during a temporary time window specified in the override; and
align a current state of the cloud resource with the scheduled state defined in the override during the temporary time window specified in the override.

### Claim 7 (depends on 6)

The system of claim 6, wherein the override is a global override applicable to all cloud resources in a cloud infrastructure that includes the cloud resource.

### Claim 8 (depends on 6)

The system of claim 6, wherein the override is a resource-specific override applicable to only the cloud resource associated with the override.

### Claim 9 (depends on 1)

The system of claim 1, wherein the one or more processors are further configured to:
adjust the regular continuous schedule to include a buffer period that is associated with a running state of the cloud resource.

### Claim 10 (depends on 9)

The system of claim 9, wherein the buffer period has a duration that is based on an estimated time required for the cloud resource to start up.

### Claim 11

A method for continuous scheduling for cloud resources, comprising:
receiving, by a scheduling system, a scheduling tag to define a custom schedule that includes at least one first window for a cloud resource over a scheduling period,
wherein the scheduling tag includes a key indicating that the scheduling tag defines one or more downtime windows;
determining, by the scheduling system, a regular continuous schedule for the cloud resource that recurs over multiple scheduling periods based on the one or more downtime windows defined in the scheduling tag,
wherein the regular continuous schedule includes the at least one first window and at least one second window, wherein the at least one second window covers time periods during the scheduling period that are not covered by the at least one first window;
determining, by the scheduling system, at a first scan time and within a window of the at least one first window or the at least one second window, whether the cloud resource is in alignment with a target state for the cloud resource in accordance with the regular continuous schedule;
aligning, by the scheduling system and based at least in part on the determination at the first scan time, the cloud resource with the target state in accordance with the regular continuous schedule;
determining, by the scheduling system and at a second scan time after the first scan time and within the window corresponding to the first scan time, whether the cloud resource is in alignment with the target state for the cloud resource in accordance with the regular continuous schedule; and
aligning, by the scheduling system and based at least in part on the determination at the second scan time, the cloud resource with the target state in accordance with the regular continuous schedule, wherein aligning the cloud resource with the target state comprises:
resuming the cloud resource based on determining, at the second scan time, that the cloud resource is in a suspended state and that the target state for the cloud resource at the second scan time is a running state;
suspending the cloud resource based on determining, at the second scan time, that the cloud resource is in the running state and that the target state for the cloud resource at the second scan time is the suspended state; or
maintaining a current state of the cloud resource based on determining, at the second scan time, that the current state of the cloud resource matches the target state for the cloud resource.

### Claim 12 (depends on 11)

The method of claim 11, further comprising performing a point-in-time evaluation to determine the target state for the cloud resource and align the current state of the cloud resource with the target state at periodic intervals.

### Claim 13 (depends on 11)

The method of claim 11, further comprising:
receiving an override to define a scheduled state for the cloud resource that takes precedence over the target state associated with the regular continuous schedule during a temporary time window specified in the override; and
aligning the current state of the cloud resource with the scheduled state defined in the override during the temporary time window specified in the override.

### Claim 14 (depends on 13)

The method of claim 13, wherein the override is a global override applicable to all cloud resources in a cloud infrastructure that includes the cloud resource or a resource-specific override applicable to only the cloud resource associated with the override.

### Claim 15 (depends on 11)

The method of claim 11, further comprising:
adjusting the regular continuous schedule to include a buffer period that is associated with the running state.

### Claim 16

A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a scheduling system, cause the scheduling system to:
receive a scheduling tag to define a custom schedule for a cloud resource over a scheduling period,
determine a regular continuous schedule for the cloud resource that recurs over multiple scheduling periods based on the scheduling tag,
wherein the regular continuous schedule includes one or more uptime windows and one or more downtime windows that cover any time periods during the scheduling period that are not covered by the one or more uptime windows;
determine, at a first scan time and within a window of the one or more uptime windows or the one or more downtime windows, whether the cloud resource is in alignment with a target state for the cloud resource in accordance with the regular continuous schedule;
align, based at least in part on the determination at the first scan time, the cloud resource with the target state in accordance with the regular continuous schedule;
determine, at a second scan time after the first scan time and within the window corresponding to the first scan time, whether the cloud resource is in alignment with the target state for the cloud resource in accordance with the regular continuous schedule; and
align, based at least in part on the determination at the second scan time, the cloud resource with the target state in accordance with the regular continuous schedule.

### Claim 17 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the one or more instructions, that cause the scheduling system to align the cloud resource with the target state, cause the scheduling system to:
determine that the target state for the cloud resource at the second scan time is a running state based on the second scan time being within the one or more uptime windows; and
resume the cloud resource based on determining, at the second scan time, that the cloud resource is in a suspended state.

### Claim 18 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the one or more instructions, that cause the scheduling system to align the cloud resource with the target state, cause the scheduling system to:
determine that the target state for the cloud resource at the second scan time is a suspended state based on the second scan time being within the one or more downtime windows; and
suspend the cloud resource based on determining, at the second scan time, that the cloud resource is in a running state.

### Claim 19 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the one or more instructions, that cause the scheduling system to align the cloud resource with the target state, cause the scheduling system to:
maintain a current state of the cloud resource based on determining, at the second scan time, that the current state of the cloud resource matches the target state.

### Claim 20 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the one or more instructions further cause the scheduling system to:
adjust the regular continuous schedule to include, prior to a starting time of each of the one or more uptime windows, a buffer period that is associated with a running state of the cloud resource.
