# US 2013/0159479 A1 · Quality of service (qos) configuration in low-power and lossy networks

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

- Number: US 2013/0159479 A1
- Document ID: US20130159479A1
- Status: Published application
- Kind: A1
- Application number: 13/331,890
- Filed: 2011-12-20
- Published: 2013-06-20
- Earliest claimed: 2011-12-20
- Assignees: Cisco Technology, Inc.
- Inventors: Jean-Philippe Vasseur
- Web page: https://patentgrep.com/patent/US20130159479A1

## CPC

- H04L 47/10: Flow control; Congestion control
- H04L 45/302: Route determination based on requested QoS
- H04L 45/38: {Flow based routing}
- H04L 49/205: {Quality of Service based}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one embodiment, a distributed intelligence agent (DIA) in a computer network performs deep packet inspection on received packets to determine packet flows, and calculates per-flow service level agreement (SLA) metrics for the packets based on timestamp values placed in the packets by respective origin devices in the computer network. By comparing the SLA metrics to respective SLAs to determine whether the respective SLAs are met, then in response to a particular SLA not being met for a particular flow, the DIA may download determined quality of service (QoS) configuration parameters to one or more visited devices along n calculated paths from a corresponding origin device for the particular flow to the DIA. In addition, in one or more embodiments, the QoS configuration parameters may be adjusted or de-configured based on whether they were successful.

## Claims

### Claim 1

A method, comprising:
performing deep packet inspection on received packets at a distributed intelligence agent (DIA) in a computer network to determine packet flows;
calculating per-flow service level agreement (SLA) metrics for the packets based on timestamp values placed in the packets by respective origin devices in the computer network;
comparing the SLA metrics to respective SLAs to determine whether the respective SLAs are met; and
in response to a particular SLA not being met for a particular flow, downloading determined quality of service (QoS) configuration parameters to one or more visited devices along n calculated paths from a corresponding origin device for the particular flow to the DIA.

### Claim 2 (depends on 1)

The method as in claim 1, wherein the SLA metrics are selected from delay and jitter.

### Claim 3 (depends on 1)

The method as in claim 1, further comprising:
in response to the particular SLA not being met for the particular flow, downloading a classification rule to the corresponding origin device in order to mark the packets of the flow;
monitoring marked packets at the DIA; and
re-determining whether the particular SLA is met based on the monitored marked packets.

### Claim 4 (depends on 3)

The method as in claim 3, further comprising:
in response to the particular SLA still not being met for the particular flow based on the monitored marked packets, adjusting the QoS configuration parameters on the visited devices by the DIA.

### Claim 5 (depends on 3)

The method as in claim 3, further comprising:
in response to the particular SLA being met for the particular flow based on the monitored marked packets, de-configuring the QoS configuration parameters on the visited devices by the DIA.

### Claim 6 (depends on 1)

The method as in claim 1, wherein determined QoS configuration parameters comprise an increased bandwidth allotment specific to a traffic type of the particular flow.

### Claim 7 (depends on 1)

The method as in claim 1, wherein determining that the particular SLA is not being met for the particular flow is based on a pre-breach threshold of the particular SLA.

### Claim 8 (depends on 7)

The method as in claim 7, wherein the pre-breach threshold is a rate of change of the corresponding SLA metrics.

### Claim 9 (depends on 1)

The method as in claim 1, further comprising:
determining historical SLA metrics;
determining traffic patterns based on the historical SLA metrics; and
proactively configuring QoS configuration parameters in the computer network by the DIA based on the traffic patterns.

### Claim 10 (depends on 1)

The method as in claim 1, wherein n=1, the method further comprising:
in response to a particular number of packets for the flow having been flagged as utilizing an alternate path from the origin device to the DIA, increasing the value of n.

### Claim 11 (depends on 1)

The method as in claim 1, further comprising:
receiving the respective SLAs at the DIA from a central intelligence controller (CIC) in the computer network.

### Claim 12 (depends on 1)

The method as in claim 1, wherein the visited devices are minimalistic connected objects (MCOs).

### Claim 13

An apparatus, comprising:
one or more network interfaces to communicate in a computer network;
a processor coupled to the network interfaces and adapted to execute one or more processes; and
a memory configured to store a process executable by the processor, the process when executed operable to:
perform deep packet inspection on received packets at the apparatus to determine packet flows;
calculate per-flow service level agreement (SLA) metrics for the packets based on timestamp values placed in the packets by respective origin devices in the computer network;
compare the SLA metrics to respective SLAs to determine whether the respective SLAs are met; and
in response to a particular SLA not being met for a particular flow, is download determined quality of service (QoS) configuration parameters to one or more visited devices along n calculated paths from a corresponding origin device for the particular flow to the apparatus.

### Claim 14 (depends on 13)

The apparatus as in claim 13, wherein the SLA metrics are selected from delay and jitter.

### Claim 15 (depends on 13)

The apparatus as in claim 13, wherein the process when executed is further operable to:
in response to the particular SLA not being met for the particular flow, download a classification rule to the corresponding origin device in order to mark the packets of the flow;
monitor marked packets; and
re-determine whether the particular SLA is met based on the monitored marked packets.

### Claim 16 (depends on 15)

The apparatus as in claim 15, wherein the process when executed is further operable to:
in response to the particular SLA still not being met for the particular flow based on the monitored marked packets, adjust the QoS configuration parameters on the visited devices.

### Claim 17 (depends on 15)

The apparatus as in claim 15, wherein the process when executed is further operable to:
in response to the particular SLA being met for the particular flow based on the monitored marked packets, de-configure the QoS configuration parameters on the visited devices.

### Claim 18 (depends on 13)

The apparatus as in claim 13, wherein the process when executed is further operable to:
determine that the particular SLA is not being met for the particular flow based on a pre-breach threshold of the particular SLA.

### Claim 19 (depends on 13)

The apparatus as in claim 13, wherein the process when executed is further operable to:
determine historical SLA metrics;
determine traffic patterns based on the historical SLA metrics; and
proactively configure QoS configuration parameters in the computer network based on the traffic patterns.

### Claim 20

A tangible, non-transitory, computer-readable media having software encoded thereon, the software when executed by a processor operable to:
perform deep packet inspection on received packets at a distributed intelligence agent (DIA) in a computer network to determine packet flows;
calculate per-flow service level agreement (SLA) metrics for the packets based on timestamp values placed in the packets by respective origin devices in the computer network;
compare the SLA metrics to respective SLAs to determine whether the respective SLAs are met; and
in response to a particular SLA not being met for a particular flow, download determined quality of service (QoS) configuration parameters to one or more visited devices along n calculated paths from a corresponding origin device for the particular flow to the DIA.

### Claim 21 (depends on 20)

The computer-readable media as in claim 20, wherein the software when executed is further operable to:
in response to the particular SLA not being met for the particular flow, download a classification rule to the corresponding origin device in order to mark the packets of the flow;
monitor marked packets at the DIA;
re-determine whether the particular SLA is met based on the monitored marked packets;
in response to the particular SLA still not being met for the particular flow based on the monitored marked packets, adjusting the QoS configuration parameters on the visited devices by the DIA; and
in response to the particular SLA being met for the particular flow based on the monitored marked packets, de-configuring the QoS configuration parameters on the visited devices by the DIA.

### Claim 22

A method, comprising:
receiving one or more timestamped packets at a minimalistic connected object (MCO) as a visited device along a path between an origin device of the packets and a distributed intelligence agent (DIA);
forwarding the packets from the MCO without applying any deep packet inspection or quality of service (QoS) mechanisms to the packets;
receiving downloaded QoS configuration parameters at the MCO from the DIA in response to a particular flow associated with the packets not meeting a corresponding service level agreement (SLA) according to the DIA, the QoS configuration parameters for future packets; and
in response to receiving future packets at the MCO, applying the QoS configuration parameters according to the QoS configuration parameters from the DIA.

### Claim 23 (depends on 22)

The method as in claim 22, further comprising:
receiving adjusted QoS configuration parameters at the MCO from the DIA.

### Claim 24 (depends on 22)

The method as in claim 22, further comprising:
receiving instructions from the DIA to de-configure the QoS configuration parameters on the MCO.
