# US 2025/0373530 A1 · Systems and methods for monitoring performance of a network slice and mitigating load on the network slice

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

- Number: US 2025/0373530 A1
- Document ID: US20250373530A1
- Status: Published application
- Kind: A1
- Application number: 19/252,714
- Filed: 2025-06-27
- Published: 2025-12-04
- Earliest claimed: 2022-06-27
- Assignees: Verizon Patent and Licensing Inc.
- Applicants: Verizon Patent and Licensing Inc.
- Inventors: James MATHEW; Peretz FEDER; Mourad B. TAKLA; Sachin VARGANTWAR
- Web page: https://patentgrep.com/patent/US20250373530A1

## CPC

- H04L 43/087: Jitter
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 43/0835: {One way packet loss}
- H04L 43/0858: {One way delays}
- H04L 43/0888: Throughput
- H04L 43/16: Threshold monitoring
- H04L 47/125: by balancing the load, e.g. traffic engineering
- H04L 47/28: in relation to timing considerations
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- H04L 41/145: {involving simulating, designing, planning or modelling of a network}
- H04L 41/147: for predicting network behaviour
- H04L 41/16: using machine learning or artificial intelligence
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A device may receive network data identifying uplink/downlink packet loss percentage, uplink/downlink jitter, uplink/downlink latency, and uplink/downlink packet throughput associated with a slice of a network, and may set an uplink value for each of the uplink packet loss percentage, the uplink jitter, the uplink latency, and the uplink packet throughput. The device may multiply the uplink values by corresponding uplink weights to calculate an uplink cost, and may set a downlink value for each of the downlink packet loss percentage, the downlink jitter, the downlink latency, and the downlink packet throughput. The device may multiply the downlink values by corresponding downlink weights to calculate a downlink cost, and may calculate a total cost based on the uplink cost and the downlink cost. The device may cause another slice, with the same attributes as the slice, to be instantiated when the total cost satisfies a threshold for a time period.

## Claims

### Claim 1

A method, comprising:
receiving, by a device, network data identifying one or more uplink metrics and one or more downlink metrics associated with a slice of a network;
processing, by the device, the network data to generate a set of uplink values corresponding to the one or more uplink metrics and a set of downlink values corresponding to the one or more downlink metrics;
calculating, by the device, an uplink cost based on the set of uplink values and a downlink cost based on the set of downlink values;
calculating, by the device, a total cost based on the uplink cost and the downlink cost;
determining, by the device, whether the total cost satisfies a threshold; and
instantiating, by the device, another slice or a slice instance, with the same set of uplink values and the same set of downlink values, based on the total cost satisfying the threshold.

### Claim 2 (depends on 1)

The method of claim 1, wherein the network data is received periodically or continuously over a predetermined time period.

### Claim 3 (depends on 1)

The method of claim 1, wherein calculating the uplink cost and the downlink cost comprises:
applying a set of respective weights to the set of uplink values and the set of downlink values.

### Claim 4 (depends on 1)

The method of claim 1, wherein the uplink cost is calculated based on historical network performance data.

### Claim 5 (depends on 1)

The method of claim 1, wherein the downlink cost is calculated based on historical network performance data.

### Claim 6 (depends on 1)

The method of claim 1, wherein instantiating the other slice or the slice instance comprises:
instantiating the other slice or the slice instance in a different physical or virtual network environment.

### Claim 7 (depends on 1)

The method of claim 1, wherein the one or more uplink metrics and the one or more downlink metrics comprise at least one of:
a metric associated with packet loss percentage,
a metric associated with jitter,
a metric associated with latency, or
a metric associated with packet throughput.

### Claim 8

A device, comprising:
one or more processors configured to:
receive network data identifying one or more performance metrics associated with a slice of a network;
process the network data to generate a set of uplink values corresponding to the one or more performance metrics and a set of downlink values corresponding to the one or more performance metrics;
calculate an uplink cost based on the set of uplink values and a downlink cost based on the set of downlink values;
calculate a total cost based on the uplink cost and the downlink cost;
determine whether the total cost satisfies a threshold; and
instantiate another slice or a slice instance, with the same set of uplink values and the same set of downlink values, based on the total cost satisfying the threshold.

### Claim 9 (depends on 8)

The device of claim 8, wherein the network data is received periodically or continuously over a predetermined time period.

### Claim 10 (depends on 8)

The device of claim 8, wherein the one or more processors, to calculate the uplink cost and the downlink cost, are configured to:
apply a set of respective weights to the set of uplink values and the set of downlink values.

### Claim 11 (depends on 8)

The device of claim 8, wherein the uplink cost is calculated based on historical network performance data.

### Claim 12 (depends on 8)

The device of claim 8, wherein the downlink cost is calculated based on historical network performance data.

### Claim 13 (depends on 8)

The device of claim 8, wherein the one or more processors, to instantiate the other slice or the slice instance, are configured to:
instantiate the other slice or the slice instance in a different physical or virtual network environment.

### Claim 14 (depends on 8)

The device of claim 8, wherein the one or more performance metrics comprise at least one of:
a metric associated with packet loss percentage,
a metric associated with jitter,
a metric associated with latency, or
a metric associated with packet throughput.

### Claim 15

A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a device, cause the device to:
receive network data identifying one or more performance metrics associated with a slice of a network;
process the network data to generate a set of uplink values corresponding to the one or more performance metrics and a set of downlink values corresponding to the one or more performance metrics;
calculate an uplink cost based on the set of uplink values and a downlink cost based on the set of downlink values;
calculate a total cost based on the uplink cost and the downlink cost;
determine whether the total cost satisfies a threshold; and
instantiate another slice or a slice instance, with the same set of uplink values and the same set of downlink values, based on the total cost satisfying the threshold.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the network data is received periodically or continuously over a predetermined time period.

### Claim 17 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the device to calculate the uplink cost and the downlink cost, further cause the device to:
apply a set of respective weights to the set of uplink values and the set of downlink values.

### Claim 18 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the uplink cost is calculated based on historical network performance data.

### Claim 19 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the downlink cost is calculated based on historical network performance data.

### Claim 20 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the device to instantiate the other slice or the slice instance, further cause the device to:
instantiate the other slice or the slice instance in a different physical or virtual network environment.
