IP Library Granted Patent US 12,634,214
Granted Patent B2
US 12,634,214 · App. 18/470,278 · Granted May 19, 2026

Quality of experience (QOE)-aware transmission over multi-transport

Inventors: Chi-Jiun Su (Rockville, MD); Lin-Nan Lee (Potomac, MD)
Assignee: HUGHES NETWORK SYSTEMS, LLC
H04L43/0805H04L43/0829H04L43/0852H04L43/0894H04L47/24
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,634,214
App. No.
18/470,278
Granted
May 19, 2026
Kind
B2
Abstract

A system and method for quality of experience (QoE)-aware transmission over multi-transport is disclosed. The system receives requests for transmitting data packets from source node to destination node in wireless communication network. Further, the system determines payload data of the data packet and n-tuple information associated with the data packet. Furthermore, the system analyzes packet level metrics associated with determined payload data of data packet. Additionally, system classifies data packets into a latency class (LC) and a Quality of Service (QoS) class based on the analyzed packet level metrics. Further, the system determines connection identifier (ID) associated with data packet. Further, the system determines appropriate multi-transport access network (MTAN) among plurality of MTANs for transmitting data packet to destination node. Furthermore, the system establishes multi-path (MP) backbone connection with destination node using determined appropriate MTAN. Additionally, the system transmits data packet to destination node through established MP backbone connection.

Claims (106)

1 . A system comprising:

a processor; and

a memory operatively coupled with the processor, wherein the memory comprises processor-executable instructions, which on execution, cause the processor to:

receive a request for transmitting a data packet from a source node to a destination node in a wireless communication network, the source node being connected to the destination node via a plurality of multi-transport access networks (MTANs);

determine payload data of the data packet and n-tuple information associated with the data packet, based on the received request;

analyze packet level metrics associated with the determined payload data of the data packet based on the determined n-tuple information;

classify the data packet into a latency class (LC) and a Quality of Service (QoS) class based on the analyzed packet level metrics;

determine an appropriate multi-transport access network (MTAN) among the plurality of MTANs and an appropriate priority traffic class for transmitting the data packet to the destination node, based on a set of parameters, wherein the set of parameters comprise at least one of a link availability value, a packet loss rate (PLR), an available bit rate (ABR), a user equipment (UE) power, a usage level, a per byte monetary cost (PBC), and system configuration parameters;

establish a multi-path (MP) backbone connection with the destination node using the determined appropriate MTAN and the appropriate priority traffic class; and

transmit the data packet to the destination node through the established MP backbone connection.

2 . The system of claim 1 , wherein the processor is to:

receive the data packet from the source node through the established MP backbone connection;

retrieve corresponding connection identifier (ID) associated with the data packet, by mapping the connection identifier (ID) with stored local connection information and established MP backbone connection information in a connection table;

determine n-tuple information, and a protocol identifier associated the established MP backbone connection based on a source node identifier, the retrieved corresponding connection ID, from the connection table; and

forward the received data packet from at least one of a performance enhancing proxy (PEP) module and a user datagram protocol (UDP) connection manager module to an application of the destination node, the PEP module or the UDP connection manager module being connected to the application of the destination node using one of a local connection and a wide area network connection.

3 . The system of claim 1 , wherein, to determine the payload data of the data packet and the n-tuple information associated with the data packet, the processor is to:

establish a local connection between an application of the source node and a performance enhancing proxy (PEP) module or a user datagram protocol (UDP) connection manager module of the source node; and

determine the n-tuple information associated with the data packet based on the received request and a type of connection established between the application of the source node and the PEP module or the UDP connection manager module, wherein the n-tuple information comprises one of a source internet protocol (IP) address, a source application protocol port number, a destination IP address, a destination application protocol port number, and a protocol type.

4 . The system of claim 1 , wherein, to analyze the packet level metrics associated with the determined payload data of the data packet, the processor is to:

monitor a bi-directional information on the payload data along with the n-tuple information for an application data flow between the application at the source node and an application at the destination node; and

analyze the packet level metrics associated with the determined payload data of the data packet based on the n-tuple information and the monitored bi-directional information, wherein the packet level metrics comprise one of a payload size, a data packet time stamp, a relative packet position in a plurality of directions and a protocol-specific information.

5 . The system of claim 1 , wherein the processor is to:

establish a multiplexed MP backbone connection with a plurality of priority levels between an application of the source node and a performance enhancing proxy (PEP) module or a user datagram protocol (UDP) connection manager module of the source node, wherein each of the selected MTAN comprises the plurality of priority levels;

assigning the data packet with a corresponding QoS class based on the plurality of priority levels;

generate a plurality of muti-path backbone protocol packets with headers based on the payload data of a plurality of data packets;

multiplex the generated plurality of muti-path backbone protocol packets with a specific QoS class over the established MP backbone connection;

determining whether the plurality of muti-path backbone protocol packets are in order for transmission;

re-ordering the plurality of muti-path backbone protocol packets upon determining that the plurality of muti-path backbone protocol packets are out of order for transmission; and

transmit the plurality of re-ordered muti-path backbone protocol packets in sequence to the traffic routing device using the established MP backbone connection, wherein the established MP backbone connection with network impairments are recovered locally and wherein the MP backbone connection queues are controlled to prevent overflow of the muti-path backbone protocol packets.

6 . The system of claim 1 , wherein, to determine the appropriate multi-transport access network (MTAN) among the plurality of MTANs, the processor is to:

obtain a latency class (LC) associated with the determined payload data based on the classification of the data packet;

determine the set of parameters comprising at least one of the link availability value, the packet loss rate (PLR), the available bit rate (ABR), the user equipment (UE) power, the usage level, the per byte monetary cost (PBC), and the system configuration parameters;

map, the set of parameters with a predefined threshold parameters; and

select respective MTAN as the appropriate MTAN among the plurality of MTANs based on the mapping of the set of parameters with the predefined threshold parameters.

7 . The system of claim 1 , wherein the processor is to:

monitor a plurality of link characteristics associated with each of the plurality of MTANs;

record a number of data bytes of the data packet transmitted over the each of the plurality of MTANs based on the monitored plurality of link characteristics;

receive estimated acknowledgment (ACK) packets from the destination node; and

modify a number of ACK packets to be transmitted over the plurality of MTANs to the source node based on the received estimated ACK packets.

8 . A method comprising:

receiving, by a processor, a request for transmitting a data packet from a source node to a destination node in a wireless communication network, the source node being connected to the destination node via a plurality of multi-transport access networks (MTANs);

determining, by the processor, payload data of the data packet and n-tuple information associated with the data packet based on the received request;

analyzing, by the processor, packet level metrics associated with the determined payload data of the data packet based on the determined n-tuple information;

classifying, by the processor, the data packet into a latency class (LC) and a Quality of Service (QoS) class based on the analyzed packet level metrics;

determining, by the processor, an appropriate multi-transport access network (MTAN) among the plurality of MTANs and an appropriate priority traffic class for transmitting the data packet to the destination node based on a set of parameters, wherein the set of parameters comprise at least one of a link availability value, a packet loss rate (PLR), an available bit rate (ABR), a user equipment (UE) power, a usage level, a per byte monetary cost (PBC), and system configuration parameters;

establishing, by the processor, a multi-path (MP) backbone connection with the destination node using the determined appropriate MTAN and the appropriate priority traffic class; and

transmitting, by the processor, the data packet to the destination node through the established MP backbone connection.

9 . The method of claim 8 , further comprising:

receiving, by the processor, the data packet from the source node through the established MP backbone connection;

retrieving, by the processor, corresponding connection identifier (ID) associated with the data packet, by mapping the connection identifier (ID) with stored local connection information and established MP backbone connection information in a connection table;

determining, by the processor, n-tuple information, and a protocol identifier associated the established MP backbone connection based on a source node identifier, the retrieved corresponding connection ID, from the connection table; and

forwarding, by the processor, the received data packet from at least one of a performance enhancing proxy (PEP) module a user datagram protocol (UDP) connection manager module to an application of the destination node, the PEP module or the UDP connection manager module being connected to the application of the destination node using one of a local connection and a wide area network connection.

10 . The method of claim 8 , wherein determining the payload data of the data packet and the n-tuple information associated with the data packet comprises:

establishing, by the processor, a local connection between an application of the source node and a performance-enhancing proxy module or a user datagram protocol (UDP) connection manager module of the source node; and

determining, by the processor, the n-tuple information associated with the data packet based on the received request and a type of connection established between the application of the source node and the performance-enhancing proxy module or a user datagram protocol (UDP) connection manager module, wherein the n-tuple information comprises one of: a source internet protocol (IP) address, a source application protocol port number, a destination IP address, a destination application protocol port number, and a protocol type.

11 . The method of claim 8 , wherein analyzing the packet level metrics associated with the determined payload data of the data packet comprises:

monitoring, by the processor, bi-directional information on the payload data along with the n-tuple information for an application data flow between the application at the source node and an application at the destination node; and

analyzing, by the processor, the packet level metrics associated with the determined payload data of the data packet based on the n-tuple information and the monitored bi-directional information, wherein the packet level metrics comprise one of a payload size, a data packet time stamp, a relative packet position in a plurality of directions and a protocol-specific information.

12 . The method of claim 8 , further comprising:

establishing, by the processor, a multiplexed MP backbone connection with a plurality of priority levels between an application of the source node and a performance enhancing proxy (PEP) module or a user datagram protocol (UDP) connection manager module of the source node, wherein each of the selected MTAN comprises the plurality of priority levels;

assigning, by the processor, the data packet with a corresponding QoS class based on the plurality of priority levels;

generating, by the processor, a plurality of muti-path backbone protocol packets with headers based on the payload data of a plurality of data packets;

multiplexing, by the processor, the generated plurality of muti-path backbone protocol packets with a specific QoS class over the established MP backbone connection;

determining, by the processor, whether the plurality of muti-path backbone protocol packets are in order for transmission;

re-ordering, by the processor, the plurality of muti-path backbone protocol packets upon determining that the plurality of muti-path backbone protocol packets are out-of order for transmission; and

transmitting, by the processor, the plurality of re-ordered muti-path backbone protocol packets in sequence to the traffic routing device using the established MP backbone connection, wherein the established MP backbone connection with network impairments are recovered locally and wherein the MP backbone connection queues are controlled to prevent overflow of the muti-path backbone protocol packets.

13 . The method of claim 8 , wherein determining the appropriate multi-transport access network (MTAN) among the plurality of MTANs comprises:

obtaining, by the processor, a latency class (LC) associated with the determined payload data based on the classification of the data packet;

determining, by the processor, the set of parameters comprising at least one of the link availability value, the packet loss rate (PLR), the available bit rate (ABR), the user equipment (UE) power, the usage level, the per byte monetary cost (PBC), and the system configuration parameters;

mapping, by the processor, the set of parameters with a predefined threshold parameters; and

selecting, by the processor, respective MTAN as the appropriate MTAN among the plurality of MTANs, based on the mapping of the set of parameters with the predefined threshold parameters.

14 . The method of claim 8 , further comprising:

monitoring, by the processor, a plurality of link characteristics associated with each of the plurality of MTANs;

recording, by the processor, a number of data bytes of the data packet transmitted over the each of the plurality of MTANs based on the monitored plurality of link characteristics;

receiving, by the processor, an estimated acknowledgement (ACK) packets from the destination node; and

modifying, by the processor, a number of ACK packets to be transmitted over the plurality of MTANs to the source node based on the received estimated ACK packets.

15 . A system comprising:

a plurality of web servers to communicate with a plurality of user equipment (UEs) using a wide area network (WAN) and multi-transport access networks (MTANs);

a traffic routing device communicatively coupled to the plurality of web servers and the plurality of UEs, the traffic routing device being connected to the plurality of web servers using the WAN, and connected to the plurality of UEs using the MTANs, the traffic routing device is to:

route a plurality of data packets between the plurality of UEs and the plurality of web servers, using MTANs and the WAN based on a set of parameters, wherein the set of parameters comprise at least one of a link availability value, a packet loss rate (PLR), an available bit rate (ABR), a user equipment (UE) power, a usage level, a per byte monetary cost (PBC), and system configuration parameters; and

the plurality of UEs communicatively coupled to the plurality of web servers via the traffic routing device, the plurality of UEs is to exchange the plurality of data packets with the plurality of web servers via the traffic routing device.

16 . The system of claim 15 , wherein the system is to:

determining multi-transport capabilities of an access traffic steering, switching, and splitting (ATSSS) protocol and a software associated with the plurality of UEs, wherein the multi-transport capabilities support quality of experience (QoE)-aware transmission;

deploy the traffic routing device as a user plane function (UPF) module within a telecommunication network based on the determined multi-transport capabilities of the ATSSS protocol and the software, the traffic routing device functions as an intermediate node between the plurality of UEs and the plurality web servers;

perform a plurality of steering functions for at least one of transmission control protocol (TCP) applications and user datagram protocol (UDP) applications within the plurality of UEs;

modify one of a data plane, a control plane, and a management plane of the telecommunication network to support the multi-transport capabilities for the quality of experience (QoE)-aware transmission; and

modify scheduling capabilities in the telecommunication network, based on the modified one of the data plane, the control plane, and the management plane.

17 . The system of claim 16 , wherein the system is to:

deploy the traffic routing device as a gateway between the telecommunication network and the plurality web servers using the WAN, based on the determined multi-transport capabilities of the ATSSS protocol and the software.

18 . The system of claim 15 , wherein the plurality of UEs comprise a Quality of Experience (QoE)-aware transmission over a multi-transport module, and the plurality of UEs function as a source node and the traffic routing device functions as a destination node, the QoE-aware transmission over a multi-transport module is to:

establish a local connection between an application within the plurality of UEs and a performance-enhancing proxy (PEP) module or a user datagram protocol (UDP) connection manager module associated with the plurality of UEs;

determine a payload data of the plurality of data packets and n-tuple information associated with the plurality of data packets;

analyze packet level metrics associated with the determined payload data of the plurality of data packets based on the determined n-tuple information;

classify the plurality of data packets into a latency class (LC) and a Quality of Service (QoS) class based on the analyzed packet level metrics;

determine an appropriate multi-transport access network (MTAN) among the plurality of MTANs and an appropriate priority traffic class for transmitting the plurality of data packets to the traffic routing system based on the set of parameters;

establish a multi-path (MP) backbone connection with the traffic routing system using the determined appropriate MTAN and the appropriate priority traffic class; and

transmit the plurality of data packets to the traffic routing device through the established MP backbone connection.

19 . The system of claim 18 , wherein to transmit the plurality of data packets to the traffic routing device using the established MP backbone connection, the QoE-aware transmission over a multi-transport module is to:

generate a plurality of muti-path backbone protocol packets with headers based on the payload data of the plurality of data packets;

multiplex the generated plurality of muti-path backbone protocol packets with a specific QoS class over the established MP backbone connection; and

transmit the plurality of multiplexed muti-path backbone protocol packets to the traffic routing device using the established MP backbone connection.

20 . The system of claim 16 , wherein the traffic routing device comprises a QoE-aware transmission over a multi-transport module, and the plurality of UEs functions as a source node and the traffic routing device functions as a destination node, the QoE-aware transmission over a multi-transport module at the traffic routing device end is to:

receive the plurality of data packets from the plurality of UEs through an established MP backbone connection;

determine a payload data, a source node identifier, and a connection ID associated with the received plurality of data packets;

extract the n-tuple information associated with the received plurality of data packets based on the determined payload data, the source node identifier, and the connection ID; and

forward the received plurality of data packets to an application of the plurality of web servers using the WAN.

Assignments (3)
SECURITY INTEREST Recorded Jul 26, 2026
From: HUGHES NETWORK SYSTEMS, LLC
To: U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION, AS TRUSTEE (FORMERLY KNOWN AS U.S. BANK NATIONAL ASSOCIATION)
Reel/Frame 075401/0515 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 20, 2023
From: SU, CHI-JIUN; LEE, LIN-NAN
To: HUGHES NETWORK SYSTEMS, LLC
Reel/Frame 065297/0058 →
SECURITY INTEREST Recorded Oct 18, 2023
From: HUGHES NETWORK SYSTEMS, LLC
To: U.S. BANK NATIONAL ASSOCIATION
Reel/Frame 065271/0695 →
Continuity (1)
Related Publication 20250097131A1 · Mar 20, 2025
References Cited (14)
US 7219158B2 · Border et al. · 2007 [cited by applicant]
US 10021034B2 · Hong et al. · 2018 [cited by applicant]
US 20020049854A1 · Cox · 2002 [cited by examiner]
US 20150195178A1 · Bhattacharya · 2015 [cited by examiner]
US 20170359272A1 · Srinivasan · 2017 [cited by examiner]
US 20210235313A1 · Devadoss · 2021 [cited by examiner]
US 20210409335A1 · Zhu et al. · 2021 [cited by applicant]
US 20220060413A1 · Joseph · 2022 [cited by examiner]
US 20220124043A1 · Zhu et al. · 2022 [cited by applicant]
US 20220386215A1 · Dillon · 2022 [cited by examiner]
US 20240267792A1 · Zhu · 2024 [cited by examiner]
3gpp.org; 3GPP TS 23.501, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18)”, Mar. 2023, 667 pages, clause … [cited by applicant]
European Patent Office, “International Search Report and Written Opinion for Application No. PCT/US2024/039177”, dated Oct. 14, 2024, 20 pages. [cited by applicant]
Kanugovi Nokia et al., “Multi-Access Management Services (MAMS)”, Internet Engineering Task Force, IETF; Standard, Internet Society (ISOC) 4, rue des Falaises CH- 1205 Geneva, Switzerland, Mar. 2020, 73 pages. [cited by applicant]