# US 2024/0406755 A1 · Traffic signature-based network slice policy actions

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

- Number: US 2024/0406755 A1
- Document ID: US20240406755A1
- Status: Published application
- Kind: A1
- Application number: 18/325,460
- Filed: 2023-05-30
- Published: 2024-12-05
- Earliest claimed: 2023-05-30
- Assignees: Verizon Patent and Licensing Inc.
- Applicants: Verizon Patent and Licensing Inc.
- Inventors: Ravi Potluri; Kalyani Bogineni; Sudhakar Reddy Patil; Jude M. Munn
- Web page: https://patentgrep.com/patent/US20240406755A1

## CPC

- H04W 24/02: Arrangements for optimising operational condition
- H04W 24/08: Testing, {supervising or monitoring} using real traffic
- H04W 28/0226: {based on location or mobility (handoff or reselection H04W36/00; mobile application services making use of the location of users or terminals H04W4/02)}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A network device monitors traffic associated with a network slice in a mobile network and applies machine learning to the monitored first traffic to determine at least one metric for detecting traffic anomalies in the network slice. The network device triggers, based on the determined at least one metric, at least one of: applying policy rules to second traffic in the network slice, or updating the policy rules for the network slice.

## Claims

### Claim 1

A method, comprising:
monitoring first traffic associated with a network slice in a mobile network;
applying machine learning to the monitored first traffic to determine at least one metric for detecting traffic anomalies in the network slice; and
triggering, based on the determined at least one metric, at least one of:
applying policy rules to second traffic in the network slice, or
updating the policy rules for the network slice.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
monitoring third traffic associated with the network slice;
applying the machine learning to learn traffic patterns of the network slice; and
determining traffic signatures for the network slice based on the learned traffic patterns,
wherein the at least one metric comprises at least one distance metric, and wherein applying the machine learning further determines the at least one distance metric relative to the determine traffic signatures.

### Claim 3 (depends on 2)

The method of claim 2, wherein the third traffic comprises training data sent over the network slice.

### Claim 4 (depends on 2)

The method of claim 2, wherein, when learning the traffic patterns, the machine learning comprises a Random Cut Forest (RCF) technique.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
generating at least one anomaly score based on the determined at least one metric,
wherein the triggering is further based on the at least one anomaly score.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
determining, based on the monitored first traffic and the at least one anomaly score, a need for changes to the network slice; and
triggering changes to the network slice based on the determined need for changes.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
receiving configuration data associated with performing traffic management functions for the network slice,
wherein monitoring the first traffic is based on the received configuration data.

### Claim 8 (depends on 7)

The method of claim 7, wherein the configuration data comprises at least one of:
data that identifies traffic attributes to collect for the network slice;
data that identifies monitoring thresholds for the network slice; or
data that identifies thresholds associated with the determined at least one metric.

### Claim 9 (depends on 2)

The method of claim 2, wherein determining the traffic signatures for the network slice comprises:
storing certain of the learned traffic patterns as the traffic signatures in a traffic signature repository.

### Claim 10 (depends on 1)

The method of claim 1, wherein monitoring the first traffic comprises:
monitoring traffic attributes of control plane (CP) and User Plane (UP) traffic associated with the network slice.

### Claim 11

A network device, comprising:
at least one communication interface configured to communicate via a network; and
at least one processor configured to:
monitor first traffic associated with a network slice in a mobile network,
apply machine learning to the monitored first traffic to determine at least one metric for detecting traffic anomalies in the network slice, and
trigger, based on the determined at least one metric, at least one of:
apply policy rules to second traffic in the network slice, or
update the policy rules for the network slice.

### Claim 12 (depends on 11)

The network device of claim 11, wherein the at least one processor is further configured to:
monitor third traffic associated with the network slice;
apply the machine learning to learn traffic patterns of the network slice; and
determine traffic signatures for the network slice based on the learned traffic patterns,
wherein the at least one metric comprises at least one distance metric, and wherein applying the machine learning further determines the at least one distance metric relative to the determine traffic signatures.

### Claim 13 (depends on 12)

The network device of claim 12, wherein, when learning the traffic patterns, the machine learning comprises a Random Cut Forest (RCF) technique.

### Claim 14 (depends on 11)

The network device of claim 11, wherein the at least one processor is further configured to:
generate at least one anomaly score based on the determined at least one metric,
wherein the triggering is further based on the at least one anomaly score.

### Claim 15 (depends on 14)

The network device of claim 14, wherein the at least one processor is further configured to:
determine, based on the monitored first traffic and the at least one anomaly score, a need for changes to the network slice; and
trigger changes to the network slice based on the determined need for changes.

### Claim 16 (depends on 11)

The network device of claim 11, wherein the at least one processor is further configured to:
receive configuration data associated with performing traffic management functions for the network slice,
wherein monitoring the first traffic is based on the received configuration data, and
wherein the configuration data comprises at least one of:
data that identifies traffic attributes to collect for the network slice,
data that identifies monitoring thresholds for the network slice, or
data that identifies thresholds associated with the determined at least one metric.

### Claim 17

A non-transitory storage medium storing instructions executable by a network device, wherein the instructions comprise instructions to cause the network device to:
monitor first traffic associated with a network slice in a mobile network;
apply machine learning to the monitored first traffic to determine at least one metric for detecting traffic anomalies in the network slice; and
trigger, based on the determined at least one metric, at least one of:
applying policy rules to second traffic in the network slice, or
updating the policy rules for the network slice.

### Claim 18 (depends on 17)

The non-transitory storage medium of claim 17, wherein the instructions further comprise instructions to cause the network device to:
monitor third traffic associated with the network slice;
apply the machine learning to learn traffic patterns of the network slice; and
determine traffic signatures for the network slice based on the learned traffic patterns,
wherein the at least one metric comprises at least one distance metric, and wherein applying the machine learning further determines the at least one distance metric relative to the determine traffic signatures.

### Claim 19 (depends on 17)

The non-transitory storage medium of claim 17, wherein the instructions further comprise instructions to cause the network device to:
generate at least one anomaly score based on the determined at least one metric,
wherein the triggering is further based on the at least one anomaly score.

### Claim 20 (depends on 19)

The non-transitory storage medium of claim 19, wherein the instructions further comprise instructions to cause the network device to:
determine, based on the monitored first traffic and the at least one anomaly score, a need for changes to the network slice; and
trigger changes to the network slice based on the determined need for changes.
