# US 2015/0103652 A1 · Configuring traffic allocations in a router

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

- Number: US 2015/0103652 A1
- Document ID: US20150103652A1
- Status: Published application
- Kind: A1
- Application number: 14/477,162
- Filed: 2014-09-04
- Published: 2015-04-16
- Earliest claimed: 2010-08-30
- Assignees: Tellabs Operations, Inc.
- Applicants: Tellabs Operations, Inc.
- Inventors: Leo S. Lee; Timothy E. Blair; David H. Liu
- Web page: https://patentgrep.com/patent/US20150103652A1

## CPC

- H04L 43/16: Threshold monitoring
- H04L 43/028: by filtering
- H04L 45/00: Routing or path finding of packets in data switching networks (routing or path finding in wireless networks H04W40/00)
- H04L 45/302: Route determination based on requested QoS
- H04L 47/2425: for supporting services specification, e.g. SLA
- H04L 43/0894: Packet rate
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Disclosed herein are methods and calculators for configuring traffic allocations for service classes with different Quality of Service (QoS) in a router. Example embodiments involve setting allocations at a router based on traffic rate values and/or traffic weight values provided by a user. The router may monitor actual traffic rates to ensure that traffic is not being dropped due to improper rate allocations and to provide historical data for optimizing traffic allocations. In addition, the router may automatically adjust traffic allocations to avoid dropping high(er) priority traffic. The router may also transmit alarms to the user and/or to other network devices to prompt traffic re-routing and/or re-allocation of traffic rates. Example methods and apparatus ensure appropriate traffic allocation to meet certain QoS metrics

## Claims

### Claim at position 1

1-26. (canceled)

### Claim 27

A method of configuring traffic allocations for a router, the method comprising:
determining a traffic weight value for each of a plurality of traffic rate values, each traffic rate value indicating a percentage of interface bandwidth of a router allocated to a respective class of service, the traffic weight value indicating a share of a subset of the interface bandwidth;
setting traffic allocations for a plurality of classes of service on the router based on the respective traffic weight value; and
dropping one or more packets in a given class of service at the router if a projected traffic rate associated with the given class of service exceeds the traffic allocation for the given class of service.

### Claim 28 (depends on 27)

The method of claim 27, further including:
monitoring traffic rates at the router as a function of class of service; and
automatically adjusting traffic allocations based on changes in actual traffic rates from projected traffic rates.

### Claim 29 (depends on 27)

The method of claim 27, further including:
monitoring traffic rates at the router as a function of class of service; and
emitting an alarm when actual traffic rates deviate from projected traffic rates.

### Claim 30 (depends on 29)

The method of claim 29, further including:
transmitting the alarm to a device connected to the router; and
changing traffic allocations at the device.

### Claim 31 (depends on 27)

The method of claim 27, further including:
performing deep packet inspection on packets transmitted or received by the router;
generating trend analysis based on the deep packet inspection; and
presenting results of the trend analysis to a user.

### Claim 32

A method of configuring traffic allocations for a router, the method comprising:
determining a traffic rate value for each of a plurality of traffic weight values, the traffic rate value indicating a percentage of interface bandwidth of a router allocated to a respective class of service, each traffic weight value indicating a share of a subset of the interface bandwidth;
setting traffic allocations for a plurality of classes of service on the router based on the respective traffic rate value; and
dropping one or more packets in a given class of service at the router if a projected traffic rate associated with the given class of service exceeds the traffic allocation for the given class of service.

### Claim 33 (depends on 32)

The method of claim 32, further including:
monitoring traffic rates at the router as a function of class of service; and
automatically adjusting traffic allocations based on changes in actual traffic rates from projected traffic rates.

### Claim 34 (depends on 32)

The method of claim 32, further including:
monitoring traffic rates at the router as a function of class of service; and
emitting an alarm when actual traffic rates deviate from projected traffic rates.

### Claim 35 (depends on 34)

The method of claim 34, further including:
transmitting the alarm to a device connected to the router; and
changing traffic allocations at the device.

### Claim 36 (depends on 32)

The method of claim 32, further including:
performing deep packet inspection on packets transmitted or received by the router;
generating trend analysis based on the deep packet inspection; and
presenting results of the trend analysis to a user.

### Claim 37

An apparatus to configure traffic allocations for a router, the apparatus includes a processor for executing instructions stored in a memory, the processor executing:
a determination module, the determination module configured to determine a traffic weight value for each of a plurality of traffic rate values, each traffic rate value indicating a percentage of interface bandwidth of a router allocated to a respective class of service, the traffic weight value indicating a share of a subset of the interface bandwidth; and
a traffic allocation module, communicatively coupled to the determination module, to set traffic allocations for a plurality of classes of service on the router based on the respective traffic weight value.

### Claim 38 (depends on 37)

The apparatus of claim 37, further comprising a packet dropping module communicatively coupled to the traffic allocation module, the packet dropping module configured to drop one or more packets in a given class of service at the router if a projected traffic rate associated with the given class of service exceeds the traffic allocation for the given class of service.

### Claim 39 (depends on 37)

The apparatus of claim 37, further comprising:
a monitoring module configured to monitor traffic rates at the router as a function of class of service; and
an adjusting module, communicatively coupled to the monitoring module, to adjust traffic allocations automatically based on changes in actual traffic rates from projected traffic rates.

### Claim 40 (depends on 37)

The apparatus of claim 37, further comprising:
a monitoring module to monitor traffic rates at the router as a function of class of service; and
an alarm module, communicatively coupled to the monitoring module, to emit an alarm when actual traffic rates deviate from projected traffic rates.

### Claim 41 (depends on 40)

The apparatus of claim 40, wherein the alarm module further transmits the alarm to a device connected to the router and changes traffic allocations at the device.

### Claim 42 (depends on 37)

The apparatus of claim 37, further comprising:
an inspection module to perform deep packet inspection on packets transmitted or received by the router;
an analysis module, communicatively coupled to the inspection module, to generate trend analysis based on the deep packet inspection; and
a presentation module, communicatively coupled to the analysis module, to present results of the trend analysis to a user.
