# US 12,120,012 B2 · Dynamic quality of service in edge cloud architectures

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

- Number: US 12,120,012 B2
- Document ID: US12120012B2
- Status: Granted
- Kind: B2
- Application number: 17/406,270
- Filed: 2021-08-19
- Published: 2022-02-10
- Granted: 2024-10-15
- Earliest claimed: 2018-12-28
- Assignees: Intel Corporation
- Applicants: Intel Corporation
- Inventors: Francesc Guim Bernat; Andrew J. Herdrich; Karthik Kumar; Felipe Pastor Beneyto; Edwin Verplanke; Rashmin Patel; Monica Kenguva; Brinda Ganesh; Alexander Vul; Ned M. Smith
- Web page: https://patentgrep.com/patent/US12120012B2

## CPC

- H04L 43/16: Threshold monitoring
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 41/5006: Creating or negotiating SLA contracts, guarantees or penalties
- H04L 43/08: Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L 43/20: the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
- H04L 45/125: based on throughput or bandwidth
- H04L 47/2408: for supporting different services, e.g. a differentiated services [DiffServ] type of service
- H04L 47/2425: for supporting services specification, e.g. SLA
- H04L 41/5019: Ensuring fulfilment of SLA
- H04L 43/0852: Delays
- H04L 43/0888: Throughput
- H04W 28/0268: {using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A device of a service coordinating entity includes communications circuitry to communicate with a plurality of access networks via a corresponding plurality of network function virtualization (NFV) instances, processing circuitry, and a memory device. The processing circuitry is to perform operations to monitor stored performance metrics for the plurality of NFV instances. Each of the NFV instances is instantiated by a corresponding scheduler of a plurality of schedulers on a virtualization infrastructure of the service coordinating entity. A plurality of stored threshold metrics is retrieved, indicating a desired level for each of the plurality of performance metrics. A threshold condition is detected for at least one of the performance metrics for an NF V instance of the plurality of NFV instances, based on the retrieved plurality of threshold metrics. A hardware resource used by the NFV instance to communicate with an access network is adjusted based on the detected threshold condition.

## Claims

### Claim 1

A computing node to implement a service coordinating entity in a wireless network, the computing node comprising:
a memory device;
communications circuitry; and
processing circuitry coupled to the communications circuitry and the memory device, the processing circuitry configured to:
monitor quality of service (QOS) metrics for a plurality of network function virtualization (NFV) instances, each of the plurality of NFV instances instantiated on a virtualization infrastructure by a corresponding scheduler of a plurality of schedulers of the service coordinating entity;
retrieve a plurality of threshold metrics, the plurality of threshold metrics associated with a network traffic type of a plurality of network traffic types processed by the plurality of NFV instances and indicating a minimum level for each of the QoS metrics, the plurality of network traffic types associated with a corresponding plurality of wireless communication technologies;
detect that at least one QoS metric of the QoS metrics for an NFV instance of the plurality of NFV instances is below a corresponding threshold metric of the plurality of threshold metrics; and
adjust a hardware resource used by the NFV instance to establish a communication session with at least a second computing node in the wireless network based on detecting that the at least one QoS metric is below the corresponding threshold metric and further based on a prediction for hardware resource utilization by the NFV instance.

### Claim 2 (depends on 1)

The computing node of claim 1, wherein each NFV instance of the plurality of NFV instances is provided by a respective Multi-Access Edge Computing (MEC) application executing on the virtualization infrastructure of the service coordinating entity.

### Claim 3 (depends on 1)

The computing node of claim 1, wherein the service coordinating entity is a Multi-Access Edge Computing (MEC) host executing the plurality of NFV instances as respective MEC applications instantiated on the virtualization infrastructure.

### Claim 4 (depends on 3)

The computing node of claim 3, wherein the MEC host is configured to operate according to a standard from a European Telecommunications Standards Institute (ETSI) MEC standards family or ETSI NFV standards family.

### Claim 5 (depends on 1)

The computing node of claim 1, wherein a QoS metric of QoS metrics comprises at least one of:
communication throughput for at least one of the plurality of NFV instances;
latency for the at least one of the plurality of NFV instances;
bandwidth of a communication link between two NFV instances of the plurality of NFV instances;
reliability for the at least one of the plurality of NFV instances; and
power consumption of a hardware resource used by the at least one of the plurality of NFV instances.

### Claim 6 (depends on 5)

The computing node of claim 5, wherein the communications circuitry is configured to:
receive the QoS metrics for storing as Service Level Agreement (SLA) objectives.

### Claim 7 (depends on 1)

The computing node of claim 1, wherein the processing circuitry is further configured to:
determine a plurality of Top-down Microarchitecture Analysis Method (TMAM) metrics for the plurality of NFV instances; and
select, based on the plurality of TMAM metrics, the hardware resource from a plurality of available hardware resources for adjustment.

### Claim 8 (depends on 7)

The computing node of claim 7, wherein the plurality of available hardware resources includes allocated processing power, allocated memory, and allocated communication bandwidth.

### Claim 9 (depends on 7)

The computing node of claim 7, wherein the TMAM metrics include one or more of the following:
metrics indicating a memory bound condition;
metrics indicating a processing core bound condition;
metrics indicating a frontend latency condition; and
metrics indicating a processing misprediction condition.

### Claim 10 (depends on 7)

The computing node of claim 7, wherein the processing circuitry is further configured to:
generate the prediction for hardware resource utilization by the NFV instance based at least on the TMAM metrics; and
adjust the hardware resource used by the NFV instance to communicate with the wireless network further based on the generated prediction.

### Claim 11 (depends on 1)

The computing node of claim 1, wherein the processing circuitry is further configured to:
allocate at least a portion of the memory device to store Class of Service (CloS) information for the wireless network.

### Claim 12 (depends on 11)

The computing node of claim 11, wherein the CloS information includes:
an identifier of at least one of the network traffic types associated with the wireless network; and
a second plurality of threshold metrics associated with the at least one of the plurality of network traffic types.

### Claim 13 (depends on 12)

The computing node of claim 12, wherein the NFV instance is configured to communicate with the wireless network via the at least one of the plurality of network traffic types, and wherein the processing circuitry is further configured to:
detect the at least one QoS metric for the NFV instance is below a threshold metric of the second plurality of threshold metrics; and
adjust the hardware resource used by the NFV instance to communicate with the wireless network based on detecting the at least one QoS metric is below the threshold metric of the second plurality of threshold metrics.

### Claim 14

At least one non-transitory machine-readable storage medium including instructions, wherein the instructions, when executed by a processing circuitry of a service coordinating entity in a wireless network, cause the processing circuitry to perform operations comprising:
monitoring quality of service (QOS) metrics for a plurality of network function virtualization (NFV) instances, each of the plurality of NFV instances instantiated on a virtualization infrastructure by a corresponding scheduler of a plurality of schedulers of the service coordinating entity;
retrieving a plurality of threshold metrics, the plurality of threshold metrics associated with a network traffic type of a plurality of network traffic types processed by the plurality of NFV instances and indicating a minimum level for each of the QoS metrics, the plurality of network traffic types associated with a corresponding plurality of wireless communication technologies;
detecting that at least one QoS metric of the QoS metrics for an NFV instance of the plurality of NFV instances is below a corresponding threshold metric of the plurality of threshold metrics; and
adjusting a hardware resource used by the NFV instance to establish a communication session with at least a second computing node in the wireless network based on detecting that the at least one QoS metric is below the corresponding threshold metric and further based on a prediction for hardware resource utilization by the NFV instance.

### Claim 15 (depends on 14)

The at least one non-transitory machine-readable storage medium of claim 14, wherein the service coordinating entity is a Multi-Access Edge Computing (MEC) host executing the plurality of NFV instances as respective MEC applications instantiated on the virtualization infrastructure.

### Claim 16 (depends on 15)

The at least one non-transitory machine-readable storage medium of claim 15, wherein the MEC host is configured to operate according to a standard from a European Telecommunications Standards Institute (ETSI) MEC standards family or ETSI NFV standards family.

### Claim 17 (depends on 14)

The at least one non-transitory machine-readable storage medium of claim 14, wherein a QoS metric of QOS metrics comprises at least one of:
communication throughput for at least one of the plurality of NFV instances;
latency for the at least one of the plurality of NFV instances;
bandwidth of a communication link between two NFV instances of the plurality of NFV instances;
reliability for the at least one of the plurality of NFV instances; and
power consumption of a hardware resource used by the at least one of the plurality of NFV instances.

### Claim 18 (depends on 17)

The at least one non-transitory machine-readable storage medium of claim 17, the operations further comprising:
receiving the QoS metrics for storing as Service Level Agreement (SLA) objectives.

### Claim 19 (depends on 14)

The at least one non-transitory machine-readable storage medium of claim 14, the operations further comprising:
determining a plurality of Top-down Microarchitecture Analysis Method (TMAM) metrics for the plurality of NFV instances; and
selecting, based on the plurality of TMAM metrics, the hardware resource from a plurality of available hardware resources for adjustment.

### Claim 20 (depends on 19)

The at least one non-transitory machine-readable storage medium of claim 19, wherein the plurality of available hardware resources includes allocated processing power, allocated memory, and allocated communication bandwidth.

### Claim 21 (depends on 19)

The at least one non-transitory machine-readable storage medium of claim 19, the operations further comprising:
generating the prediction for hardware resource utilization by the NFV instance based at least on the TMAM metrics; and
adjusting the hardware resource used by the NFV instance to communicate with the wireless network further based on the generated prediction.

### Claim 22

An apparatus of a service coordinating entity in a wireless network, the apparatus comprising:
means for monitoring quality of service (QOS) metrics for a plurality of network function virtualization (NFV) instances, each of the plurality of NFV instances instantiated on a virtualization infrastructure by a corresponding scheduler of a plurality of schedulers of the service coordinating entity;
means for retrieving a plurality of threshold metrics, the plurality of threshold metrics associated with a network traffic type of a plurality of network traffic types processed by the plurality of NFV instances and indicating a minimum level for each of the QoS metrics, the plurality of network traffic types associated with a corresponding plurality of wireless communication technologies;
means for detecting that at least one QoS metric of the QoS metrics for an NFV instance of the plurality of NFV instances is below a corresponding threshold metric of the plurality of threshold metrics; and
means for adjusting a hardware resource used by the NFV instance to establish a communication session with at least a second computing node in the wireless network based on detecting that the at least one QoS metric is below the corresponding threshold metric and further based on a prediction for hardware resource utilization by the NFV instance.

### Claim 23 (depends on 22)

The apparatus of claim 22, wherein a QoS metric of QOS metrics comprises at least one of:
communication throughput for at least one of the plurality of NFV instances;
latency for the at least one of the plurality of NFV instances;
bandwidth of a communication link between two NFV instances of the plurality of NFV instances;
reliability for the at least one of the plurality of NFV instances; and
power consumption of a hardware resource used by the at least one of the plurality of NFV instances.

### Claim 24 (depends on 23)

The apparatus of claim 23, further comprising:
means for receiving the QoS metrics for storing as Service Level Agreement (SLA) objectives.

### Claim 25 (depends on 22)

The apparatus of claim 22, further comprising:
means for determining a plurality of Top-down Microarchitecture Analysis Method (TMAM) metrics for the plurality of NFV instances; and
means for selecting, based on the plurality of TMAM metrics, the hardware resource from a plurality of available hardware resources for adjustment.
