IP Library Granted Patent US 10,541,855
Granted Patent B2
US 10,541,855 · App. 15/491,255 · Granted Jan 21, 2020

Resource allocation methods and apparatus

Inventors: Prince Arimpur Cheerotha Philip (Bangalore, IN); Pendyala Satya Ravi Kiran (Bangalore, IN); Kumar Saurabh (Bangalore, IN); Yasaswy Ramachandra Avasarala (Visakhapatnam, IN)
Assignee: Ribbon Communications Operating Company, Inc.
H04L29/08144G06F9/5077H04L47/70H04L67/1002H04L67/1008H04L29/06H04L67/10
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 10,541,855
App. No.
15/491,255
Granted
Jan 21, 2020
Kind
B2
Abstract

An individual session border controller in a cluster of SBCs, e.g., in a Cloud, sends a resource utilization reporting message to the current master resource manager for the cluster. In response to the received utilization reporting message from the individual SBC, the master resource manager determines a mode of operation, e.g. one of: normal, critical or overshoot, for the cluster and a resource allocation for the SBC, the resource allocation method used being different for at least two different modes. The master resource manager communicates the determined cluster mode and the determined resource allocation to the individual SBC, e.g., in a response message. The SBC controls its resource utilization reporting rate as a function of the mode. In at least one mode, e.g., normal mode, the SBC is allowed to use more resources, e.g., X % more, than the amount of resources allocated to the SBC by the master resource manager.

Claims (56)

1. A method of managing resources in a communications system, the method comprising:

operating a first resource manager, of a first session border controller, as a master resource manager for a plurality of session border controllers in a cluster of session border controllers, said first session border controller being one of the plurality of session border controllers in said cluster, operating the first resource manager including:

receiving, at the first resource manager, resource utilization reporting messages from session border controllers in said cluster, said resource utilization reporting messages including resource utilization information;

determining, at the first resource manager, from the reported resource utilization information which of a plurality of session border controller modes of operation the session border controllers are to operate in for a first resource group, said plurality of modes of session border controller operation for the first resource group including at least: i) a normal mode of operation in which session border controllers in the cluster report resource utilization for the first resource group to the first resource manager at fixed time interval spacing T and a critical mode of operation in which session border controllers in said cluster communicate resource utilization reporting messages for the first resource group to said first resource manager at a faster rate than during said normal mode of operation and during which the session border controllers reject any resource allocation requests requesting resources in the first resource group that would require a resource allocation exceeding an allocation limit assigned to an individual session border controller performing a resource allocation;

wherein said normal mode of operation is determined when the reported resource utilization for the first resource group is below or equal to a first threshold and said critical mode of operation is determined when the reported resource utilization for the first resource group is above the first threshold;

wherein during said normal mode of operation a session border controller can allocate resources above a resource allocation limit specified for the first resource group by the first resource manager for the individual session border controller performing the resource allocation; and

communicating the determined mode of operation for the first resource group to one or more session border controllers in said cluster.

2. The method of claim 1 , wherein said plurality of session border controller modes of operation further includes an overshoot mode of operation wherein session border controllers report resource utilization reporting messages to the first resource manager more frequently than during said normal mode of operation and wherein the session border controllers are controlled to reject resource allocation requests above the resource allocation assigned to the session border controller.

3. The method of claim 2 , further comprising:

operating the first resource manager to determine a resource allocation for the first resource group for a session border controller in said cluster based on the reported resource utilization information;

wherein resources which are allocated are call admission resources; and

wherein the messages reporting resource utilization include information indicating the number of active calls to which resources were allocated by the session border controller sending the resource utilization message to the first resource manager.

4. The method of claim 3 , wherein a message reporting rate used during said critical and overshoot modes is at least twice the message reporting rate used during said normal mode of session border controller operation.

5. The method of claim 3 , further comprising:

operating the first resource manager to use a first resource allocation determination method to determine resource allocations for the first resource group for individual session border controllers during said normal mode of operation; and

operating the first resource manager to use a second resource allocation determination method to determine resource allocations for the first resource group for individual session border controllers during said overshoot mode of operation.

6. The method of claim 5 , wherein both the first and second resource allocation determination methods use information indicating the total first group resources being used by the cluster to determine resource allocation limits for individual session border controllers with respect to first group resources in the cluster.

7. The method of claim 6 , wherein said second resource allocation determination method uses a factor to result in lower resource allocation limits for session border controllers for a given total resource utilization than when the first resource allocation determination method is used.

8. The method of claim 7 , wherein the first and second resource allocation determination methods allocate more first resource group resources to a session border controller in said cluster reporting a first level of first resource group resource utilization than to another session border controller in the cluster reporting a second level of first resource group resource utilization, said second level being lower than said first level.

9. The method of claim 1 , further comprising:

determining, by the first resource manager, that an overshoot condition exists for the cluster when the reported resource utilization information indicates that a maximum resource limit for the first resource group has been exceeded by the cluster of session border controllers; and

wherein said plurality of session border controller modes of operation further includes an overshoot mode of operation wherein the session border controllers report resource utilization reporting messages to the first resource manager more frequently than during said normal mode of operation and wherein the session border controllers are controlled to reject resource allocation requests above the resource allocation assigned to the session border controller, said resource allocation assigned to the session border controller being an overshoot resource allocation determined using an overshoot factor by the first resource manager after determining that an overshoot condition exists for the cluster.

10. The method of claim 9 , further comprising:

operating the first resource manager to determine a resource allocation for the first resource group for each of the session border controllers in said cluster based on the reported resource utilization information; and

operating each of the session border controllers in the cluster to receive and respond to requests for resources of the first resource group.

11. The method of claim 1 , wherein each of the session border controllers includes a resource manager, the method further comprising:

operating the session border controllers to elect one of the resource managers to operate as the master resource manager, said first resource manager having been elected to operate as the master resource manager.

12. The method of claim 11 , wherein each session border controller corresponds to one or more trunk groups, resource allocations being performed on a per trunk group and resource group basis.

13. The method of claim 1 , wherein the session border controllers in said cluster are instances of session border controllers in a cloud based system.

14. A communications system comprising:

a first session border controller comprising:

a processor; and

memory;

wherein said processor is configured to:

operate a first resource manager, of the first session border controller, as a master resource manager for a plurality of session border controllers in a cluster of session border controllers, said first session border controller being one of the plurality of session border controllers in said cluster, operating the first resource manager including:

receiving, at the first resource manager, resource utilization reporting messages from session border controllers in said cluster, said resource utilization reporting messages including resource utilization information;

determining, at the first resource manager, from the reported resource utilization information which of a plurality of session border controller modes of operation the session border controllers are to operate in for a first resource group, said plurality of modes of session border controller operation for the first resource group including at least: i) a normal mode of operation in which session border controllers in the cluster report resource utilization for the first resource group to the first resource manager at fixed time interval spacing T and ii) a critical mode of operation in which session border controllers in said cluster communicate resource utilization reporting messages for the first resource group to said first resource manager at a faster rate than during said normal mode of operation and during which the session border controllers reject any resource allocation requests requesting resources in the first resource group that would require a resource allocation exceeding an allocation limit assigned to an individual session border controller performing a resource allocation;

wherein said normal mode of operation is determined when the reported resource utilization for the first resource group is below or equal to a first threshold and said critical mode of operation is determined when the reported resource utilization for the first resource group is above the first threshold;

wherein during said normal mode of operation a session border controller can allocate resources above a resource allocation limit specified for the first resource group by the first resource manager for the individual session border controller performing the resource allocation; and

communicating the determined mode of operation for the first resource group to one or more session border controllers in said cluster.

15. The communications system of claim 14 ,

wherein the processor further operates the first resource manager to determine from the reported resource utilization information which of a plurality of session border controller modes of operation the session border controllers of the cluster are to operate in for a second resource group which is different from said first resource group, said plurality of session border controller modes of operation including a normal mode of operation for the second resource group and a critical mode of operation for the second resource group; and

wherein said normal mode of operation for the second resource group is determined when the reported resource utilization for the second resource group is below or equal to a second threshold and said critical mode of operation for the second resource group is determined when the reported resource utilization for the second resource group is above the second threshold.

16. The communications system of claim 14 , wherein said plurality of session border controller modes of operation further includes an overshoot mode of operation wherein session border controllers report resource utilization reporting messages to the first resource manager more frequently than during said normal mode of operation and wherein the session border controllers are controlled to reject resource allocation requests above the resource allocation assigned to the session border controller.

17. The communications system of claim 16 , wherein said processor is further configured to:

operate the first resource manager to determine a resource allocation for the first resource group for a session border controller in said cluster based on the reported resource utilization information.

18. The communications system of claim 17 , wherein resources which are allocated are call admission resources; and

wherein the messages reporting resource utilization include information indicating the number of active calls to which resources were allocated by the session border controller sending the resource utilization message to the first resource manager.

19. The communications system of claim 14 , wherein the session border controllers in said cluster are instances of session border controllers in a cloud based system.

20. A non-transitory machine readable medium including processor executable instructions, which when executed by a processor of a first session border controller control the first session border controller to:

operate a first resource manager, of the first session border controller, as a master resource manager for a plurality of session border controllers in a cluster of session border controllers, said first session border controller being one of the plurality of session border controllers in said cluster, operating the first resource manager including:

receive, at the first resource manager, resource utilization reporting messages from session border controllers in said cluster, said resource utilization reporting messages including resource utilization information;

determine, at the first resource manager, from the reported resource utilization information which of a plurality of session border controller modes of operation the session border controllers are to operate in for a first resource group, said plurality of modes of session border controller operation for the first resource group including at least: i) a normal mode of operation in which session border controllers in the cluster report resource utilization for the first resource group to the first resource manager at fixed time interval spacing T and ii) a critical mode of operation in which session border controllers in said cluster communicate resource utilization reporting messages for the first resource group to said first resource manager at a faster rate than during said normal mode of operation and during which the session border controllers reject any resource allocation requests requesting resources in the first resource group that would require a resource allocation exceeding an allocation limit assigned to an individual session border controller performing a resource allocation;

wherein said normal mode of operation is determined when the reported resource utilization for the first resource group is below or equal to a first threshold and said critical mode of operation is determined when the reported resource utilization for the first resource group is above the first threshold;

wherein during said normal mode of operation a session border controller can allocate resources above a resource allocation limit specified for the first resource group by the first resource manager for the individual session border controller performing the resource allocation; and

communicate the determined mode of operation for the first resource group to one or more session border controllers in said cluster.

Assignments (9)
SHORT-FORM PATENTS SECURITY AGREEMENT Recorded Sep 5, 2024
From: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
To: HPS INVESTMENT PARTNERS, LLC, AS ADMINISTRATIVE AGENT
Reel/Frame 068857/0290 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2024
From: CITIZENS BANK, N.A.
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 067822/0433 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT AT R/F 044978/0801 Recorded Dec 6, 2021
From: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 058949/0497 →
SECURITY INTEREST Recorded Mar 3, 2020
From: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
To: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 052076/0905 →
CHANGE OF NAME Recorded Jan 16, 2019
From: SONUS NETWORKS, INC.
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
Reel/Frame 048078/0036 →
SECURITY INTEREST Recorded Jan 2, 2018
From: GENBAND US LLC; SONUS NETWORKS, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 044978/0801 →
CHANGE OF NAME Recorded Dec 24, 2017
From: SONUS, INC.
To: SONUS NETWORKS, INC.
Reel/Frame 044957/0213 →
MERGER AND CHANGE OF NAME Recorded Dec 24, 2017
From: SOLSTICE SAPPHIRE, INC.; SONUS NETWORKS, INC.; SONUS NETWORKS, INC.
To: SONUS, INC.
Reel/Frame 044957/0243 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 26, 2017
From: PHILIP, PRINCE ARIMPUR CHEEROTHA; RAVI KIRAN, PENDYALA SATYA; SAURABH, KUMAR; AVASARALA, YASASWY RAMACHANDRA
To: SONUS NETWORKS, INC.
Reel/Frame 042341/0981 →
Priority Claims (1)
IN 201741004009 · Feb 3, 2017 · national
Continuity (1)
Related Publication 20180227165A1 · Aug 9, 2018