# US 2025/0168077 A1 · Congestion aware traffic optimization in communication networks

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

- Number: US 2025/0168077 A1
- Document ID: US20250168077A1
- Status: Published application
- Kind: A1
- Application number: 18/840,706
- Filed: 2023-01-18
- Published: 2025-05-22
- Earliest claimed: 2022-02-23
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Applicants: Telefonaktiebolaget LM Ericsson (publ)
- Inventors: Miguel Angel MUÑOZ DE LA TORRE ALONSO; Marcus IHLAR; Gonzalo HERNANDEZ HARO; Maria Luisa MAS ROSIQUE
- Web page: https://patentgrep.com/patent/US20250168077A1

## CPC

- H04L 41/14: Network analysis or design
- H04W 28/02: Traffic management, e.g. flow control or congestion control
- 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]
- H04W 28/06: Optimizing {the usage of the radio link}, e.g. header compression, information sizing {, discarding information (system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365)}
- H04W 76/12: Setup of transport tunnels
- 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

Methods for a network data analytics function (NWDAF) of a communication network. Such methods include receiving, from user plane function (UPF) of the communications network, a first subscription request for an analytic related to user plane (UP) traffic congestion and sending to the UPF a second subscription request for information related to traffic between the UPF and a radio access network (RAN). Such methods also include receiving the traffic-related information from the UPF, in accordance with the second subscription request, and computing the analytic related to UP traffic congestion, based on the received traffic-related information. Such methods also include sending the computed analytic to the UPF, in accordance with the first subscription request. Embodiments also include complementary methods for UPFs, as well as NWDAFs and UPFs configured to perform such methods.

## Claims

### Claim 1

A method for a network data analytics function, NWDAF, of a communication network, the method comprising:
receiving, from a user plane function, UPF, of the communication network, a first subscription request for an analytic related to user plane, UP, traffic congestion, the first subscription request including the following:
an identifier of the analytic;
an identifier of a tunnel between the UPF and a Radio Access Network, RAN, for which the analytic is requested:
identifiers of one or more user equipment, UEs, for which the analytic is requested;
one or more other filtering criteria associated with the analytic;
one or more reporting criteria associated with the analytic;
a time period associated with the analytic; and
a required confidence level for the analytic;
sending, to the UPF, a second subscription request for information related to traffic between the UPF and, the RAN, the second subscription request including an event identifier associated with the second subscription request and identifiers of one or more of the following, for which the traffic-related information is requested:
a range of tunnels between the UPF and the RAN node, indicated by a tunnel range identifier or by an identifier of the RAN node;
one or more user equipment, UEs;
one or more applications; and
one or more application types;
receiving the traffic-related information from the UPF, in accordance with the second subscription request;
computing the analytic related to UP traffic congestion, based on the received traffic-related information; and
sending the computed analytic to the UPF, in accordance with the first subscription request.

### Claim 2

(canceled)

### Claim 3

(canceled)

### Claim 4 (depends on 1)

The method of claim 1, further comprising determining the range of tunnels indicated in the second subscription request based on the identifier of the UPF tunnel in the first subscription request.

### Claim 5 (depends on 1)

The method of claim 1, wherein the traffic-related information received from the UPF includes the following:
aggregated volume of data traffic carried over the range of tunnels;
one or more key performance indicators, KPIs, for the aggregated data traffic carried over the range of tunnels; and
one or more of the following information associated with respective data flows carried over the range of tunnels: an identifier of a UE, an identifier of an application, flow data volume, flow start and stop times, flow duration, number of packets, average packet size, and other flow information relevant to congestion.

### Claim 6 (depends on 5)

The method of claim 5, wherein one or more of the following applies:
the one or more KPIs include round trip time, RTT; and
the analytic is a congestion level.

### Claim 7 (depends on 6)

The method of claim 6, wherein the congestion level is sent to the UPF according to one of the following:
based on the congestion level exceeding a reporting threshold identified in the first subscription request; or
periodically, according to a reporting period identified in the first subscription request.

### Claim 8 (depends on 6)

The method of claim 6, wherein the congestion level is sent to the UPF together with one or more of the following:
one or more suggested action for the UPF, based on the congestion level;
one or more KPIs associated with the congestion level;
one or more statistics for user data sessions;
identifiers of active ones of the UEs identified in the first subscription request; and
level of confidence associated with the congestion level.

### Claim 9 (depends on 8)

The method of claim 8, wherein the one or more suggested actions include any of the following: adaptive bit rate, ABR, shaping; large flow shaping; transmission control protocol, TCP, traffic optimization; and QUIC traffic optimization.

### Claim 10 (depends on 5)

The method of claim 5, wherein:
multiple reports of traffic-related information are received from the UPF in accordance with the second subscription request;
each report includes an aggregated volume of data traffic carried over the range of tunnels; and
computing the analytic comprises determining a congestion level based on variations in the reported aggregate volumes of data traffic.

### Claim 11

A method for a user plane function, UPF, of a communication network, the method comprising:
sending, to a network data analytics function, NWDAF, of the communication network, a first subscription request for an analytic related to user plane, UP, traffic congestion, the first subscription request including the following:
an identifier of the analytic;
an identifier of a tunnel between the UPF and a Radio Access Network, RAN, for which the analytic is requested;
identifiers of one or more user equipment, UEs, for which the analytic is requested;
one or more other filtering criteria associated with the analytic;
one or more reporting criteria associated with the analytic;
a time period associated with the analytic; and
a required confidence level for the analytic;
receiving, from the NWDAF, a second subscription request for information related to traffic between the UPF and RAN, the second subscription request including an event identifier associated with the second subscription request and identifiers of one or more of the following, for which the traffic-related information is requested:
a range of tunnels between the UPF and the RAN node, indicated by a tunnel range identifier or by an identifier of the RAN node;
one or more user equipment, UEs;
one or more applications; and
one or more application types;
sending the traffic-related information to the NWDAF, in accordance with the second subscription request; and
receiving the analytic from the NWDAF, in accordance with the first subscription request.

### Claim 12

(canceled)

### Claim 13

(canceled)

### Claim 14 (depends on 11)

The method of claim 11, wherein the traffic-related information received from the UPF includes one or more of the following:
aggregated volume of data traffic carried over the range of tunnels;
one or more key performance indicators, KPIs, for the aggregated data traffic carried over the range of tunnels; and
one or more of the following information associated with respective data flows carried over the range of tunnels: an identifier of a UE, an identifier of an application, flow data volume, flow start and stop times, flow duration, number of packets, average packet size, and other flow information relevant to congestion.

### Claim 15 (depends on 14)

The method of claim 14, wherein one or more of the following applies:
the one or more KPIs include round trip time, RTT; and
the analytic is a congestion level.

### Claim 16 (depends on 15)

The method of claim 15, wherein the congestion level is received from the NWDAF according to one of the following:
based on the congestion level exceeding a reporting threshold identified in the first subscription request; or
periodically, according to a reporting period identified in the first subscription request.

### Claim 17 (depends on 15)

The method of claim 15, wherein the congestion level is received from the NWDAF together with one or more of the following:
one or more suggested actions for the UPF, based on the congestion level;
one or more KPIs associated with the congestion level;
one or more statistics for user data sessions;
identifiers of active ones of the UEs identified in the first subscription request; and
level of confidence associated with the congestion level.

### Claim 18

(canceled)

### Claim 19 (depends on 14)

The method of claim 14, wherein:
the multiple reports of traffic-related information are sent to the NWDAF in accordance with the second subscription request;
each report includes an aggregated volume of data traffic carried over the range of tunnels; and
the congestion level is based on variations in the reported aggregate volumes of data traffic.

### Claim 20 (depends on 11)

The method of claim 11, further comprising performing one or more of the following optimization operations on traffic between the UPF and the RAN, based the analytic: adaptive bit rate, ABR, shaping; large flow shaping; transmission control protocol, TCP, traffic optimization; and QUIC traffic optimization.

### Claim 21 (depends on 11)

The method of claim 11, further comprising:
receiving, from a session management function, SMF, of the communication network, a packet forwarding control protocol, PFCP, session establishment request that indicates a congestion-aware traffic optimization, CATO, policy; and
establishing the tunnel between the UPF and the RAN, in accordance with the PCFP session establishment request,
wherein the first subscription request is sent in response to establishing the tunnel.

### Claim 22 (depends on 21)

The method of claim 21, further comprising sending to the SMF an indication that the UPF supports a CATO capability, wherein the PFCP session establishment request is received based on the indication, wherein the PFCP session establishment request indicates that the UPF should apply the CATO policy without further interaction with the SMF.

### Claim 23

(canceled)

### Claim 24 (depends on 11)

The method of claim 11, further comprising initiating collection of the traffic-related information based on detecting data traffic corresponding to the second subscription request, wherein the detected data traffic is associated with one or more of the following identified in the second subscription request: a UE, and an application.

### Claim at position 25

-27. (canceled)

### Claim 28

A network data analytics function, NWDAF configured to operate in a communication network, the NWDAF being further configured to:
receive, from a user plane function, UPF of the communication network, a first subscription request for an analytic related to user plane, UP, traffic congestion, the first subscription request including the following:
an identifier of the analytic;
an identifier of a tunnel between the UPF and a Radio Access Network, RAN, for which the analytic is requested;
identifiers of one or more user equipment, UEs, for which the analytic is requested;
one or more other filtering criteria associated with the analytic;
one or more reporting criteria associated with the analytic;
a time period associated with the analytic; and
a required confidence level for the analytic;
send, to the UPF, a second subscription request for information related to traffic between the UPF and the RAN, the second subscription request including an event identifier associated with the second subscription request and identifiers of one or more of the following, for which the traffic-related information is requested:
a range of tunnels between the UPF and the RAN node, indicated by a tunnel range identifier or by an identifier of the RAN node;
one or more user equipment, UEs;
one or more applications; and
one or more application types;
receive the traffic-related information from the UPF, in accordance with the second subscription request;
compute the analytic related to UP traffic congestion, based on the received traffic-related information; and
send the computed analytic to the UPF, in accordance with the first subscription request.

### Claim at position 27

-33. (canceled)

### Claim 34

A user plane function, UPF configured to operate in a communication network, the UPF being further configured to:
send, to a network data analytics function, NWDAF of the communication network, a first subscription request for an analytic related to user plane, UP, traffic congestion, the first subscription request including the following:
an identifier of the analytic;
an identifier of a tunnel between the UPF and a Radio Access Network, RAN, for which the analytic is requested;
identifiers of one or more user equipment, UEs, for which the analytic is requested;
one or more other filtering criteria associated with the analytic;
one or more reporting criteria associated with the analytic;
a time period associated with the analytic; and
a required confidence level for the analytic;
receive, from the NWDAF, a second subscription request for information related to traffic between the UPF and the RAN, the second subscription request including an event identifier associated with the second subscription request and identifiers of one or more of the following, for which the traffic-related information is requested:
a range of tunnels between the UPF and the RAN node, indicated by a tunnel range identifier or by an identifier of the RAN node;
one or more user equipment, UEs;
one or more applications; and
one or more application types;
send the traffic-related information to the NWDAF, in accordance with the second subscription request; and
receive the analytic from the NWDAF, in accordance with the first subscription request.

### Claim at position 29

-37. (canceled)
