US 2025/0086012 A1Published application

Resource allocation using proactive pause

AssigneeMicrosoft Technology Licensing, LLC

InventorsOlga POPPE, Qun GUO, Willis LANG, Pankaj ARORA, Ajay KALHAN

Life of this patent

Estimating the term…

Loading patent…

Abstract

A proactive resource allocator in a database management system is configured to make database resource allocation decisions for users accessing a database, including proactively pausing resources allocated to a user for accessing a database. To determine whether to proactively pause resources that are allocated to a user who has logged out, the proactive resource allocator accesses historical data to predict a next time the user with log back in. If the predicted next time of user login is relatively soon, the proactive resource allocator maintains the allocation of the resources to the user. If the predicted next time of user login is relatively far away, the proactive resource allocator pauses the resources. The proactive resource allocator may logically pause the resources or may physically pause the resources.

Claims20

Dependent claims

A system, comprising:

a processor;
and
a memory device that stores program code structured to cause the processor to:
allocate resources to a user in response to the user logging into a database;
determine the user logged out of the database subsequent to the user logging in;
determine a plurality of login patterns for the user from historical data of user interactions with the database, each login pattern of the login patterns corresponding to a respective time window of a plurality of time windows having a same start of predicted activity;
calculate a plurality of probabilities corresponding to the determined login patterns for the time windows, each calculated probability indicative of a likelihood that the user will log into the database during the corresponding time window of the time windows;
in response to a set of the calculated probabilities being determined to have a predetermined relationship with a confidence threshold:
select from the set the probability having a greatest likelihood;
and
determine whether a time of predicted activity in the time window associated with the selected probability is within an upcoming predetermined length of time;
and
in response to the time of predicted activity being determined to be within the upcoming predetermined length of time, maintain the allocation of the resources to the user.

10 more elements

A method, comprising:

allocating resources to a user in response to the user logging into a database;
determining the user logged out of the database subsequent to the user logging in;
determining a plurality of login patterns for the user from historical data of user interactions with the database, each login pattern of the login patterns corresponding to a respective time window of a plurality of time windows having a same start of predicted activity;
calculating a plurality of probabilities corresponding to the determined login patterns for the time windows, each calculated probability indicative of a likelihood that the user will log into the database during the corresponding time window of the time windows;
in response to a set of the calculated probabilities being determined to have a predetermined relationship with a confidence threshold:
selecting from the set the probability having a greatest likelihood;
and
determining whether a time of predicted activity in the time window associated with the selected probability is within an upcoming predetermined length of time;
and
in response to determining the time of predicted activity to be within the upcoming predetermined length of time, maintaining the allocation of the resources to the user.

7 more elements

A computer-readable storage device encoded with program instructions that, when executed by a processor circuit, perform a method comprising:

allocating resources to a user in response to the user logging into a database;
determining the user logged out of the database subsequent to the user logging in;
determining a plurality of login patterns for the user from historical data of user interactions with the database, each login pattern of the login patterns corresponding to a respective time window of a plurality of time windows having a same start of predicted activity;
calculating a plurality of probabilities corresponding to the determined login patterns for the time windows, each calculated probability indicative of a likelihood that the user will log into the database during the corresponding time window of the time windows;
in response to a set of the calculated probabilities being determined to have a predetermined relationship with a confidence threshold:
selecting from the set the probability having a greatest likelihood;
and
determining whether a time of predicted activity in the time window associated with the selected probability is within an upcoming predetermined length of time;
and
in response to determining the time of predicted activity to be within the upcoming predetermined length of time, maintaining the allocation of the resources to the user.

7 more elements

Dependencies are inferred from the claim text.

Facts

Application: 18/484,861Filed 11 Oct 2023
Priority: 8 Sep 2023
Published: 13 Mar 2025
Term ends: Not estimatedThe source records don’t support an estimate.

Classification15 codes

G06F 11/3423
By assessing time: where the assessed time is active or idle time
G06F 11/3438
Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of…:…
G06F 9/5005
Allocation of resources, e.g. of the central processing unit [CPU]: to service a request
G06F 9/5022
The resources being hardware resources other than CPUs, Servers and Terminals: mechanisms to release resources

Family

Application63/581,495Us provisional application · filed 8 Sep 2023
US 2025/0086012 A1This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key