# US 2025/0168084 A1 · Edge Device for a Distributed Traffic Engineering System With Quality of Service Control of a Plurality of Flow Groups

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

- Number: US 2025/0168084 A1
- Document ID: US20250168084A1
- Status: Published application
- Kind: A1
- Application number: 19/027,242
- Filed: 2025-01-17
- Published: 2025-05-22
- Earliest claimed: 2022-07-27
- Assignees: Huawei Technologies Co., Ltd.
- Applicants: Huawei Technologies Co., Ltd.
- Inventors: Tran Anh Quang Pham; Youcef Magnouche; Jeremie Leguay; Xu Gong
- Web page: https://patentgrep.com/patent/US20250168084A1

## CPC

- H04L 41/5025: by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
- H04L 41/5009: Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
- H04L 41/5019: Ensuring fulfilment of SLA
- H04L 47/2425: for supporting services specification, e.g. SLA
- H04L 41/046: comprising network management agents or mobile agents therefor
- H04L 41/142: using statistical or mathematical methods
- H04L 41/147: for predicting network behaviour
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An edge device is for a distributed traffic engineering system with quality of service control of a plurality of flow groups routed over a set of overlay links. The edge device is configured to receive one or more service-level agreement requirements for the plurality of flow groups from a network controller, receive first control information from one or more other edge devices in the distributed traffic engineering system, obtain monitoring information for the plurality of flow groups and the set of overlay links, and adjust a plurality of queuing parameters for the plurality of flow groups based on at least one of the first control information, the monitoring information, or the one or more SLA requirements.

## Claims

### Claim 1

An edge device for a distributed traffic engineering system with quality of service (QoS) control of a plurality of flow groups routed over a set of overlay links, wherein the edge device comprises:
a memory configured to store instructions; and
one or more processors coupled to the memory and configured to execute the instructions to cause the edge device to:
receive one or more service-level agreement (SLA) requirements for the plurality of flow groups from a network controller;
receive first control information from one or more other edge devices in the distributed traffic engineering system;
obtain monitoring information for the plurality of flow groups and the set of overlay links; and
adjust a plurality of queuing parameters for the plurality of flow groups based on at least one of the first control information, the monitoring information, or the one or more SLA requirements to obtain a plurality of adjusted queuing parameters.

### Claim 2 (depends on 1)

The edge device of claim 1, wherein the instructions, when executed by the one or more processors, further cause the edge device to:
determine if a help request is required based on the monitoring information and the one or more SLA requirements; and
send, when the help request is required, the help request to the network controller.

### Claim 3 (depends on 2)

The edge device of claim 2, wherein the instructions, when executed by the one or more processors, further cause the edge device to receive, after sending the help request, a routing policy from the network controller.

### Claim 4 (depends on 1)

The edge device of claim 1, wherein the instructions, when executed by the one or more processors, further cause the edge device to:
determine second control information based on the plurality of adjusted queuing parameters or the monitoring information; and
provide the second control information to the one or more other edge devices.

### Claim 5 (depends on 2)

The edge device of claim 2, wherein the instructions, when executed by the one or more processors, further cause the edge device to receive, from the network controller, one or more end points for the help request.

### Claim 6 (depends on 1)

The edge device of claim 1, wherein the instructions, when executed by the one or more processors, further cause the edge device to further adjust the plurality of queuing parameters based on an SLA prediction model.

### Claim 7 (depends on 1)

The edge device of claim 1, wherein the instructions, when executed by the one or more processors, further cause the edge device to forward traffic of each flow group of the plurality of flow groups over the set of overlay links.

### Claim 8 (depends on 2)

The edge device of claim 2, wherein the instructions, when executed by the one or more processors, further cause the edge device to further determine if the help request is required based on an SLA prediction model or based on whether the one or more SLA requirements are met.

### Claim 9 (depends on 1)

The edge device of claim 1, wherein the monitoring information comprises a measured throughput for each flow group of the plurality of flow groups or for each overlay link in the set of overlay links, and wherein the one or more processors execute the instructions to further cause the edge device to:
compare the measured throughput of each flow group with the one or more SLA requirements or with a plurality of rate allocations; and
send, when the measured throughput is not high enough to satisfy at least one of the one or more SLA requirements, a help request.

### Claim 10 (depends on 1)

The edge device of claim 1, wherein the instructions, when executed by the one or more processors, further cause the edge device to further adjust the plurality of queuing parameters based on a class-based queuing (CBQ) architecture.

### Claim 11 (depends on 1)

The edge device of claim 1, wherein the instructions, when executed by the one or more processors, further cause the edge device to determine a plurality of rate allocations based on a QoS optimization model.

### Claim 12 (depends on 11)

The edge device of claim 11, wherein the QoS optimization model includes at least one of the following constraints:
capacities of each overlay link of the set of overlay links is satisfied,
an objective for fairness of rate allocations, or
SLA violations, rate allocations, or rate violations.

### Claim 13 (depends on 11)

The edge device of claim 11, wherein the QoS optimization model includes at least one of the following inputs:
one or more flow groups in the plurality of flow groups,
one or more tunnels, wherein each of the one or more tunnels is defined by a first origin and a first destination,
the plurality of flow groups, wherein each flow group in the plurality of flow groups is defined by a class of traffic, a second origin, and a second destination,
a traffic demand of each flow group on each overlay link,
an SLA prediction model for each flow group on each overlay link,
an SLA requirement of each flow group, or
a penalty of demand violation of each flow group, or
wherein the QoS optimization model includes at least one of the following outputs:
a rate allocation of each flow group on each overlay link,
an SLA violation of each flow group on each overlay link,
a rate violation of each flow group on each overlay link, or
an intermediate variable of each flow group on each overlay link to optimize fairness according to a fairness objective.

### Claim 14

A network controller for a distributed traffic engineering system with quality of service (QoS) control of a plurality of flow groups routed over a set of overlay links, wherein the network controller comprises:
memory configured to store instructions; and
one or more processors configured to execute the instructions to cause the network controller to:
send service level agreement (SLA) requirements for each flow group of the plurality of flow groups to two or more edge devices of the distributed traffic engineering system;
receive a help request from at least one edge device of the two or more edge devices in response to the SLA requirements; and
send a routing policy to the at least one edge device in response to the help request.

### Claim 15

A method of operating an edge device for a distributed traffic engineering system with Quality of Service (QoS) control of a plurality of flow groups routed over a set of overlay links, wherein the method comprises:
receiving one or more Service Level Agreement (SLA) requirements for the plurality of flow groups from a network controller;
receiving first control information from one or more other edge devices in the distributed traffic engineering system;
obtaining monitoring information for the plurality of flow groups and the set of overlay links; and
adjusting a plurality of queuing parameters for the plurality of flow groups based on the first control information, the monitoring information, and the one or more SLA requirements to obtain a plurality of adjusted queuing parameters.

### Claim 16 (depends on 15)

The method of claim 15, further comprising:
determining if a help request is required based on the monitoring information and the one or more SLA requirements; and
sending, if a help request is required, a help request to the network controller.

### Claim 17 (depends on 16)

The method of claim 16, further comprising receiving, after sending the help request, a routing policy from the network controller.

### Claim 18 (depends on 15)

The method of claim 15, further comprising:
determining second control information based on the plurality of adjusted queuing parameters or the monitoring information; and
sending the second control information to the one or more other edge devices.

### Claim 19 (depends on 15)

The method of claim 15, further comprising further adjusting the plurality of queuing parameters based on an SLA prediction model.

### Claim 20 (depends on 16)

The method of claim 16, further comprising further determining if the help request is required based on an SLA prediction model, or based on whether the one or more SLA requirements are met.
