IP Library › Granted Patent US 8,782,240
Granted Patent B2
US 8,782,240 · App. 13/079,593 · Granted Jul 15, 2014

Resource allocation using shared resource pools

Inventors: James Douglas Free (Thornton, CO); Kenneth Owen Michie (Thornton, CO); Chandra Mouli Ravipati (Thornton, CO)
Assignee: Avaya Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,782,240
App. No.
13/079,593
Filed
Apr 4, 2011
Granted
Jul 15, 2014
Kind
B2
Art Unit
2457
USPC
709/226
Abstract

The present disclosure describes methods and systems for managing resources, for example in connection with call admission control or other communications or transactions in a system. In particular, a plurality of resource pools are established. At least a first or priority resource is associated with a minimum resource amount, while at least a second or normal resource pool is associated with a maximum resource amount. From the system resource pools, allocations are made to each of a plurality of system servers. If a server receives a request for priority resources that cannot be satisfied from the allocation of priority resources made to that server, that server may borrow from an allocation of normal resources. Resources can also be shared between servers. Accordingly, if required resources are not available from an allocation made to a server receiving the request for resources, that server can request resources from another server. In responding to a request to share resources, a server can attempt to fill the request as if the request had originally been made to that server.

Claims (53)

1. A method for allocating resources, comprising:

defining a plurality of resource pools, wherein a first resource pool in the plurality of resource pools is a priority resource pool, wherein the priority resource pool has a first maximum pool size, wherein a second resource pool in the plurality of resource pools is a normal resource pool, wherein the normal resource pool has a second maximum pool size, and wherein the first maximum pool size is greater than the second maximum pool size;

assigning an initial resource allocation from the plurality of resource pools to each of a plurality of servers;

receiving a request for resources at a first server included in the plurality of servers;

identifying a first one of the first or second resource pools associated with the request;

in response to determining that the first server does not have resources currently allocated from the resource pool associated with the request available, perform at least one of:

reallocating at least some of the requested resources from one of the first or second resource pools to the other of the first and second resource pools; and

requesting at least some of the requested resources from a second server included in the plurality of servers; and

in response to determining that the request cannot be satisfied from resources currently allocated to the first server:

sending a first request for shared resources to a third server included in the plurality of servers;

wherein the request for shared resources includes a maximum amount of priority resources that the first server could use, a maximum amount of normal resources that the first server could use, and a maximum amount of borrowed resources that the first server could use.

2. The method of claim 1 , wherein in response to determining that the first server does not have resources allocated from the resource pool associated with the request available the method includes:

reallocating the requested resources from another resource pool.

3. The method of claim 2 , wherein reallocating the requested resources from another resource pool includes:

determining that the resource pool associated with the request is the priority resource pool;

determining that resources from the allocation made to the first server from the normal resource pool is available;

incrementing a priority resource count associated with the first server;

incrementing a borrowed resource count associated with the first server; and

decrementing a normal resource count associated with the first server.

4. The method of claim 2 , wherein reallocating the requested resource from the another resource pool includes:

determining that the resource pool associated with the request is the normal resource pool;

determining that a borrowed resource count associated with the first server is greater than zero;

determining that an available priority resource count for the first server is greater than zero;

decrementing the borrowed resource count for the first server;

decrementing an available priority resource count for the first server; and

incrementing a total normal resource count for the first server, wherein resources are reallocated from the priority resource allocation for the first server to the normal resource allocation for the first server.

5. The method of claim 1 , further comprising:

in response to receiving the first request for shared resources, the third server releasing unused resources to the first server, wherein resources are reallocated between the first and the third servers.

6. The method of claim 5 , wherein the priority resource pool has a minimum pool size, wherein a sum of the minimum pool size of the priority resource pool and the maximum pool size of the normal resource pool equals total system resources, and wherein the reallocation of resources between the first and the third servers does not change the total system resources.

7. The method of claim 6 , wherein the third server reallocating unused resources to the first server includes the third server:

determining an amount of requested normal resources that can be reallocated to the first server;

determining an amount of requested borrowed resources that can be reallocated to the first server;

determining an amount of requested priority resources that can be reallocated to the first server.

8. The method of claim 7 , further comprising:

in response to receiving reallocated resources from the third server, the first server applying the reallocated resources.

9. The method of claim 8 , further comprising:

in response to the received allocated resources being insufficient to satisfy the request for resources made to the first server, the first server sending a second request for shared resources to a fourth server.

10. The method of claim 1 , wherein the request for resources received at the first server is for priority resources, wherein the first request for shared resources sent to the third server by the first server requests zero normal resources.

11. The method of claim 1 , further comprising:

the first server assigning the requested resources to satisfy the request.

12. The method of claim 1 , wherein the plurality of resource pools are resource pools of electrical power.

13. The method of claim 12 , wherein the first resource pool is a resource pool of renewable energy resources and the second resource pool is a resource pool of non-renewable resources.

14. A system for administering resources, comprising:

at least a first network;

two or more branches;

a plurality of servers, wherein each server is associated with one of the branches, and wherein the servers are in communication with one another and are interconnected to the first network, each server including:

data storage, including:

a control table, wherein the control table defines a plurality of resource pools, wherein a first resource pool in the plurality of resource pools is a priority resource pool, wherein the priority resource pool has a first maximum pool size, wherein a second resource pool in the plurality of resource pools is a normal resource pool, wherein the normal resource pool has a second maximum pool size, and wherein the first maximum pool size is greater than the second maximum pool size;

a resource allocation application, wherein the resource allocation assigns an initial resource allocation from the plurality of resource pools to each of the plurality of servers, receives a request for resources at a first server included in the plurality of servers, identifies a first one of the first or second resource pools associated with the request, and in response to determining that the first server does not have resources allocated from the resource pool associated with the request available, the resource allocation application perform at least one of:

reallocates at least some of the requested resources from one of the first or second resource pools to the other of the first or second resource pools; and

requests at least some of the requested resources from a second server included in the plurality of servers; and

a resource application in the first server of the plurality of servers that, in response to determining that a request cannot currently be satisfied from resources allocated to the first server, sends a request message over the first network to a third server, and wherein the request message includes a maximum amount of priority resources that the first server could use, a maximum amount of normal resources that the first server could use, and a maximum amount of borrowed resources that the first server could use.

15. The system of claim 14 , wherein total system resources are held constant.

Assignments (21)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 14, 2026
From: AVAYA LLC
To: PULSELINK SYSTEMS LLC
Reel/Frame 074909/0627 →
INTELLECTUAL PROPERTY PARTIAL RELEASE AND REASSIGNMENT Recorded Feb 4, 2026
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: AVAYA LLC (F/K/A AVAYA INC.); AVAYA MANAGEMENT L.P.
Reel/Frame 074981/0940 →
INTELLECTUAL PROPERTY PARTIAL RELEASE AND REASSIGNMENT Recorded Feb 4, 2026
From: CITIBANK, N.A.
To: AVAYA LLC (F/K/A AVAYA INC.); AVAYA MANAGEMENT L.P.
Reel/Frame 074944/0573 →
(SECURITY INTEREST) GRANTOR'S NAME CHANGE Recorded Sep 21, 2023
From: AVAYA INC.
To: AVAYA LLC
Reel/Frame 065019/0231 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 4, 2023
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 063542/0662 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 3, 2023
From: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; KNOAHSOFT INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB [COLLATERAL AGENT]
Reel/Frame 063742/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 029608/0256 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 044891/0801 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 045012/0666 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
SECURITY AGREEMENT Recorded Mar 13, 2013
From: AVAYA, INC.
To: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE
Reel/Frame 030083/0639 →
SECURITY AGREEMENT Recorded Jan 10, 2013
From: AVAYA, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 029608/0256 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 26, 2011
From: FREE, JAMES DOUGLAS; MICHIE, KENNETH OWEN; RAVIPATI, CHANDRA MOULI
To: AVAYA INC.
Reel/Frame 026180/0243 →
Continuity (2)
Provisional Application 61394025 · Oct 18, 2010
Related Publication 20120096167A1 · Apr 19, 2012