Method for bandwidth management by resizing pipes

• US 6,999,474 B1
• Filed: 07/21/2004
• Issued: 02/14/2006
• Est. Priority Date: 12/16/1998
• Status: Expired due to Term

• Current Assignee: Fernham Technologies LLC (Intellectual Ventures LLC)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Goyal, Pawan, Greenberg, Albert Gordon, Mishra, Partho Pratim, Ramakrishnan, Kadangode K.
• Primary Examiner(s): HO, DUC CHI
• Application Number:
  US10/895,931
• Time in Patent Office: 573 Days
• Field of Search: None
• US Class Current: 370/468
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/724 at intermediate nodes, e.g. resource reservation protocol [RSVP]
• CPC Class Codes: H04L 47/762 triggered by the network
• CPC Class Codes: H04L 47/801 Real time traffic
• CPC Class Codes: H04L 47/822 Collecting or measuring resource availability data

Abstract

Signaling messages are exchanged for a call between a calling party to a called party. A setup message for the call is exchanged through at least one gate controller. Network resources are reserved for the call based on the exchanged setup messages. An end-to-end message for the call is exchanged without the end-to-end message being routed through the at least one gate controller.

Claims

1. A method for allocating network resources for a plurality of calls between calling parties and called parties comprising:

aggregating call flows into a single queue;

partitioning network bandwidth between the call flows and other classes of traffic; and

scheduling the call flows with priority over the other classes of traffic

wherein the call flows are aggregated into a pipe across a backbone of the network; and

wherein the pipe is resized on a periodic basis.

2. A method for allocating network resources for a call between a calling party and a called party comprising:

receiving a reservation request for the call flow at an ingress aggregation router connected to an egress router by a pipe across a plurality of core routers in a core network; and

requesting bandwidth for the call flow to an egress aggregation router;

wherein the requesting bandwidth step further comprises the steps of;

modifying the reservation request to hide it from core routers;

forwarding the reservation request across the core network to the egress router.

3. The method of claim 2, wherein the requesting bandwidth step further comprises forwarding a message through the core routers without the message being interpreted by the core routers.

4. A method for allocating network resources for a call between a calling party and a called party comprising:

receiving a reservation request for the call flow at an ingress aggregation router connected to an egress router by a pipe across a plurality of core routers in a core network; and

requesting bandwidth for the call flow to an egress aggregation router the request being transmitted on a same path as the call flow;

wherein the requesting bandwidth step further comprises the steps of;

modifying the reservation request to hide it from core routers;

forwarding the reservation request across the core network to the aggregation network.

5. The method of claim 4 wherein the requesting bandwidth step further comprises the steps of:

receiving the reservation request at an egress aggregation router;

checking to see if the flow can be accommodated on the pipe between the ingress aggregation router and the egress aggregation router.

6. A method for allocating network resources for a call between a calling party and a called party comprising:

receiving a reservation request for the call flow at an ingress aggregation router connected to an egress router by a pipe across a plurality of core routers in a core network; and

requesting bandwidth for the call flow to an egress aggregation router, the request being transmitted on a same path as the call flow;

wherein the requesting bandwidth step further comprises forwarding a message through the core routers without the message being interpreted by the core routers.