Methods and apparatus for controlling call admission to a network based on network resources

US10171513B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10171513-B2
Application numberUS-42722006-A
CountryUS
Kind codeB2
Filing dateJun 28, 2006
Priority dateDec 31, 2004
Publication dateJan 1, 2019
Grant dateJan 1, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A session controller coupled to a database and configured to receive an indication associated with an ingress call is disclosed. The disclosed session controller is further configured to compare at least one of a network capacity, a call-peer bandwidth, or a number of active call-legs associated with the ingress call session against a respective threshold, and to reject the ingress call when a respective threshold is exceeded.

First claim

Opening claim text (preview).

We claim: 1. An apparatus comprising: a session controller coupled to a database and configured to receive an indication associated with an ingress call, wherein the ingress call is one of a group of calls associated with an ingress call peer, wherein the group of calls is associated with the same session initiation protocol (SIP) address-of-record information, wherein the ingress call peer represents the group of calls and indicates a signaling entity associated with the same SIP address-of-record information, wherein the signaling entity is associated with processing the ingress call; the session controller being further configured to compare a number of active call-legs associated with the ingress call against a call-leg threshold associated with the ingress call peer, wherein the call-leg threshold indicates the limit for active call-legs associated with the ingress call peer; and the session controller being further configured to reject the ingress call when the call-leg threshold is exceeded, wherein the session controller is further configured to reject the ingress call based on an indication of a best-effort service level, an indication of a call-load balance, or when the ingress call exceeds a provisioned service-level assurance threshold. 2. A method, comprising: receiving an indication of an ingress call at a session controller, wherein the ingress call is one of a group of calls associated with an ingress call peer, wherein the group of calls is associated with the same session initiation protocol (SIP) address-of-record information, wherein the ingress call peer represents the group of calls and indicates a signaling entity associated with the same SIP address-of-record information, wherein the signaling entity is associated with processing the ingress call; comparing a number of active call-legs associated with the ingress call against a call-leg threshold associated with the ingress call peer, wherein the call-leg threshold indicates the limit for active call-legs associated with the ingress call peer; and when the call-leg threshold is exceeded, rejecting the ingress call, wherein the session controller is further configured to reject the ingress call based on an indication of a best-effort service level, an indication of a call-load balance, or when the ingress call exceeds a provisioned service-level assurance threshold. 3. A computer program stored on a non-transitory computer-readable medium, the computer program comprising: a receiving instruction to receive an ingress call indicator associated with an ingress call, wherein the ingress call is one of a group of calls associated with an ingress call peer, wherein the group of calls is associated with the same session initiation protocol (SIP) address-of-record information, wherein the ingress call peer represents the group of calls and indicates a signaling entity associated with the same SIP address-of-record information, wherein the signaling entity is associated with processing the ingress call; a comparison instruction to compare a number of active call-legs associated with the ingress call against a call-leg threshold associated with the ingress call peer, wherein the call-leg threshold indicates the limit for active call-legs associated with the ingress call peer; and a rejection instruction to reject the ingress call when the call-leg threshold is exceeded, wherein the rejection instruction is further to reject the ingress call based on an indication of a best-effort service level, an indication of a call-load balance, or when the ingress call exceeds a provisioned service-level assurance threshold. 4. An apparatus comprising: a session controller including at least one processor and being coupled to a database and configured to receive an indication associated with an egress call, wherein the egress call is one of a group of calls associated with an egress call peer, wherein the group of calls is associated with the same session initiation protocol (SIP) address-of-record information, wherein the egress call peer represents the group of calls and indicates a signaling entity associated with the same SIP address-of-record information, wherein the signaling entity is associated with processing the egress call; the session controller being further configured to compare a number of active call-legs associated with the egress call against a call-leg threshold associated with the egress call peer, wherein the call-leg threshold indicates the limit for active call-legs associated with the egress call peer; and the session controller being further configured to reject the egress call when the call-leg threshold is exceeded, wherein the session controller is further configured to reject the egress call based on an indication of a best-effort service level, an indication of a call-load balance, or when the egress call exceeds a provisioned service-level assurance threshold. 5. A method, comprising: receiving an indication of an egress call at a session controller, wherein the egress call is one of a group of calls associated with an egress call peer, wherein the group of calls is associated with the same session initiation protocol (SIP) address-of-record information, wherein the egress call peer represents the group of calls and indicates a signaling entity associated with the same SIP address-of-record information, wherein the signaling entity is associated with processing the egress call; comparing a number of active call-legs associated with the egress call against a call-leg threshold associated with the egress call peer, wherein the call-leg threshold indicates the limit for active call-legs associated with the egress call peer; and when the call-leg threshold is exceeded, rejecting the egress call, wherein the session controller is further configured to reject the egress call based on an indication of a best-effort service level, an indication of a call-load balance, or when the egress call exceeds a provisioned service-level assurance threshold. 6. A computer program stored on a non-transitory computer-readable medium, the computer program comprising: a receiving instruction to receive an egress call indicator associated with an egress call, wherein the egress call is one of a group of calls associated with an egress call peer, wherein the group of calls is associated with the same session initiation protocol (SIP) address-of-record information, wherein the egress call peer represents the group of calls and indicates a signaling entity associated with the same SIP address-of-record information, wherein the signaling entity is associated with processing the egress call; a comparison instruction to compare a number of active call-legs associated with the egress call against a call-leg threshold associated with the egress call peer, wherein the call-leg threshold indicates the limit for active call-legs associated with the egress call peer; and a rejection instruction to reject the egress call when the call-leg threshold is exceeded, wherein the rejection instruction is further to reject the egress call based on an indication of a best-effort service level, an indication of a call-load balance, or when the egress call exceeds a provisioned service-level assurance threshold.

Assignees

Inventors

Classifications

  • Responding to QoS · CPC title

  • Assignment of logical groups to network elements · CPC title

  • Discovery involving ranked list compilation of candidate peers · CPC title

  • Interworking of session control protocols · CPC title

  • Traffic control in data switching networks (arrangements for detecting or preventing errors in the information received H04L1/00) · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10171513B2 cover?
A session controller coupled to a database and configured to receive an indication associated with an ingress call is disclosed. The disclosed session controller is further configured to compare at least one of a network capacity, a call-peer bandwidth, or a number of active call-legs associated with the ingress call session against a respective threshold, and to reject the ingress call when a …
Who is the assignee on this patent?
Ramachandran Sridhar, Tyagi Paritosh, Mallesan Saravanan, and 5 more
What technology area does this patent fall under?
Primary CPC classification H04L65/1046. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jan 01 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 3 related publications on this page (citations in our corpus or others sharing the same primary CPC).