# US 2015/0029857 A1 · Per-class scheduling with rate limiting

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0029857 A1
- Document ID: US20150029857A1
- Status: Published application
- Kind: A1
- Application number: 14/453,784
- Filed: 2014-08-07
- Published: 2015-01-29
- Earliest claimed: 2007-01-31
- Assignees: Alcatel Lucent
- Applicants: Alcatel Lucent
- Inventors: Joseph M. Regan; Ron E. Haberman; Mike Noll
- Web page: https://patentgrep.com/patent/US20150029857A1

## CPC

- H04L 47/21: using leaky-bucket
- H04L 41/083: for increasing network speed
- H04L 47/12: Avoiding congestion; Recovering from congestion
- H04L 47/522: {Dynamic queue service slot or variable bandwidth allocation}
- H04L 47/6215: {Individual queue per QOS, rate or priority}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Providing network access is disclosed. Use of a provider equipment port via which network access is provided to two or more downstream nodes, each having one or more classes of network traffic associated with it, is scheduled on a per class basis, across the downstream nodes. The respective network traffic sent to each of at least a subset of the two or more downstream nodes is limited, on a per downstream node basis, to a corresponding rate determined at least in part by a capacity of a communication path associated with the downstream node.

## Claims

### Claim 1

A system for providing network access, comprising:
a communication port configured to send network traffic to and receive network traffic from each of two or more downstream nodes, each having one or more classes of network traffic associated with it; and
a processor coupled to the communication interface and configured to:
schedule on a per class basis, across downstream nodes, use of a provider equipment port via which access to a core provider network is provided to said two or more downstream nodes via said communication port; and
limit the respective network traffic sent to each of at least a subset of the two or more downstream nodes, on a per downstream node basis, to a corresponding rate determined at least in part by a capacity of a communication path associated with the downstream node.

### Claim 2 (depends on 1)

The system as recited in claim 1, wherein the downstream nodes comprise subscriber is hosts.

### Claim 3 (depends on 1)

The system as recited in claim 1, wherein the downstream nodes comprise digital subscriber line access multiplexers (DSLAM).

### Claim 4 (depends on 1)

The system as recited in claim 1, wherein the downstream nodes comprise access nodes, each of which has associated with it one or more subscriber hosts each of which receives directly from said access node one or more of said one or more classes of network traffic.

### Claim 5 (depends on 1)

The system as recited in claim 1, wherein said downstream nodes comprise a first level of nodes configured to provide access to a second level of nodes comprising a plurality of subscriber hosts, each associated with at least one of said first level nodes and each configured to receive via said first level node one or more of said one or more classes of network traffic.

### Claim 6 (depends on 5)

The system as recited in claim 5, wherein limiting includes applying to each of at least a subset of said first level nodes a corresponding first aggregate rate limit on traffic sent to that first level node, across subscriber hosts.

### Claim 7 (depends on 6)

The system as recited in claim 6, wherein limiting further includes applying to each of at least a subset of said subscriber hosts a corresponding second rate limit on traffic sent to that subscriber host.

### Claim 8 (depends on 1)

The system as recited in claim 1, wherein limiting to a corresponding rate includes configuring a counter or other leaky bucket mechanism to be incremented in proportion to the size of each packet sent to the downstream node and to be decremented at a rate based at least in part on said corresponding rate.

### Claim 9 (depends on 1)

The system as recited in claim 1, wherein scheduling on a per class basis includes providing for each of said one or more classes of network traffic a corresponding scheduling process.

### Claim 10 (depends on 1)

The system as recited in claim 1, wherein the processor is further configured to schedule use of said provider equipment port as between said one or more class of network traffic.

### Claim 11 (depends on 10)

The system as recited in claim 10, wherein scheduling use of said provider equipment port as between said one or more class of network traffic is performed using a fairness algorithm is that ensures equal or nearly equal access is provided for each of said one or more classes of network traffic.

### Claim 12 (depends on 10)

The system as recited in claim 10, wherein scheduling use of said provider equipment port as between said one or more class of network traffic is performed using an algorithm that affords one or more higher priority classes of network traffic greater access to the provider equipment port than one or more lower priority classes of network traffic.

### Claim 13 (depends on 1)

The system as recited in claim 1, wherein said provider equipment comprises a broadband network gateway (BNG).

### Claim 14 (depends on 1)

The system as recited in claim 1, wherein scheduling on a per class basis includes determining a next subscriber queue.

### Claim 15 (depends on 1)

The system as recited in claim 1, wherein at least one of said downstream nodes comprises a DSLAM and said communication path comprises a link between said DSLAM and an aggregation network via which the DSLAM is connected to the provider network gateway device.

### Claim 16 (depends on 1)

The system as recited in claim 1, wherein at least one of said downstream nodes comprises a subscriber host and said communication path comprises a link between said subscriber host and a DSLAM via which the subscriber host has connectivity to the provider network gateway device.

### Claim 17 (depends on 1)

The system as recited in claim 1, wherein the processor is configured to limit the respective network traffic sent to each of at least a subset of the two or more downstream nodes, on a per downstream node basis, to the corresponding rate at least in part by configuring for each downstream node for which such rate limiting is performed a counter or other leaky bucket mechanism configured to ensure that said corresponding rate is not exceeded.

### Claim 18 (depends on 1)

The system as recited in claim 1, further comprising a second communication port via which access to said core provider network is available to said provider network gateway device.

### Claim 19

A method of providing network access, comprising:
scheduling on a per class basis, across downstream nodes, use of a provider equipment port via which network access is provided to two or more downstream nodes, each having one or is more classes of network traffic associated with it; and
using a processor to limit the respective network traffic sent to each of at least a subset of the two or more downstream nodes, on a per downstream node basis, to a corresponding rate determined at least in part by a capacity of a communication path associated with the downstream node.

### Claim 20

A computer program product for providing network access, the computer program product being embodied in a non-transitory computer readable medium and comprising computer instructions for:
scheduling on a per class basis, across downstream nodes, use of a provider equipment port via which network access is provided to two or more downstream nodes, each having one or more classes of network traffic associated with it; and
limiting the respective network traffic sent to each of at least a subset of the two or more downstream nodes, on a per downstream node basis, to a corresponding rate determined at least in part by a capacity of a communication path associated with the downstream node.
