IP Library Granted Patent US 12,634,741
Granted Patent B2
US 12,634,741 · App. 18/731,498 · Granted May 19, 2026

Method for coexistence of low latency, low loss and scalable throughput (L4S) and non-L4S traffic in 5G-type networks

Inventors: Mukesh Taneja (Bangalore, IN); Moushumi Sen (Bangalore, IN)
Assignee: Mavenir Systems, Inc.
H04W28/0236H04L47/629H04W28/0268
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,741
App. No.
18/731,498
Granted
May 19, 2026
Kind
B2
Abstract

A method for optimizing coexistence of low latency, low loss and scalable throughput (L4S) traffic and non-L4S traffic in a 5G wireless system is provided, which method includes one of: a) performing one of i) a flow control between a centralized unit (CU) and a distributed unit (DU), or ii) radio resource management at the DU, to reduce latency experienced by the L4S traffic; or b) performing one of iii) a flow control between the CU and the DU to facilitate greater frequency of transmission of non-L4S traffic from CU-user plane (CU-UP) to the DU, or iv) radio resource management at the DU, to reduce a scheduling priority metric of a logical channel for the L4S traffic relative to a scheduling priority metric of a logical channel for the non-L4S traffic. To reduce latency of the L4S traffic, the L4S traffic scheduling priority is increased relative to the non-L4S traffic.

Claims (219)

1 . A method for optimizing coexistence of low latency, low loss and scalable throughput (L4S) traffic and non-L4S traffic in a 5G wireless system serving a user equipment (UE), comprising

one of:

a) performing one of i) a flow control between a centralized unit (CU) and a distributed unit (DU), or ii) radio resource management at the DU, to adjust latency experienced by the L4S traffic; or

b) performing one of iii) a flow control between the CU and the DU to facilitate greater frequency of transmission of non-L4S traffic from CU-user plane (CU-UP) to the DU, or iv) radio resource management at the DU, to adjust a scheduling priority metric of a logical channel for the L4S traffic relative to a scheduling priority metric of a logical channel for the non-LAS traffic;

wherein the scheduling priority P LC non-L4S of each non-L4S logical channel is computed using at least the following factors:

W 5QI , which is the weight of P 5QI , which is in turn a priority metric corresponding to a quality of service (QoS) class of the respective logical channel;

W GBR , which is the weight of P GBR , which is in turn a priority metric corresponding to a target bit rate of the respective logical channel;

W PDB , which is the weight of P PDB , which is in turn a priority metric corresponding to a packet delay budget at the DU for the respective logical channel, and

W PF , which is the weight of P PF , which is in turn a priority metric corresponding to a proportional fair metric of the UE;

wherein the scheduling priority P LC non-L4S of each non-L4S logical channel is computed as follows:

P

L

C

n

o

n

-

L

4

S

=

(

W

5

QI

*

P

5

Q

I

+

W

PF

*

P

P

F

)

*

maximum

(

W

GBR

*

P

G

B

R

,

W

PDB

*

P

P

D

B

n

o

n

-

L

4

S

)

;

wherein P PDB non-L4S is the priority metric corresponding to a packet delay budget at the DU for the respective non-L4S logical channel.

2 . The method of claim 1 , wherein the scheduling priority P LC L4S of each L4S logical channel is computed using at least the following factors:

W 5QI ;

W GBR ;

W PDB ;

W PF ;

WL4S 5QI , which is the weight of P 5QI for the respective L4S logical channel;

WL4S GBR , which is the weight of P GBR for the respective L4S logical channel;

WL4S PDB , which is the weight of P PDB for the respective L4S logical channel; and

WL4SPF, which is the weight of P PF for the respective L4S logical channel.

3 . The method of claim 2 , wherein the scheduling priority P LC L4S of each L4S logical channel is computed as follows:

P

L

C

L

4

S

=

(

WL

4

S

5

QI

*

W

5

QI

*

P

5

Q

I

+

W

L

4

S

PF

*

W

PF

*

P

P

F

)

*

maximum

(

WL

4

S

GBR

*

W

GBR

*

P

G

B

R

,

W

L

4

S

PDB

*

W

PDB

*

P

P

D

B

L

4

S

)

;

wherein P PDB L4S is the priority metric corresponding to a packet delay budget at the DU for the respective L4S logical channel.

4 . The method of claim 3 , wherein, to adjust the latency experienced by the L4S traffic, the radio resource management at the DU is performed to adjust the scheduling priority metric of the logical channel for the L4S traffic relative to the scheduling priority metric of the logical channel for the non-L4S traffic.

5 . The method of claim 3 , wherein at least one of the following is performed at the DU to facilitate fair coexistence of a non-L4S data radio bearer (DRB) and an L4S DRB:

i) for a non-guaranteed bit rate (non-GBR) L4S DRB, WL4S GBR is set to 0;

ii) for a non-GBR, non-L4S DRB, W GBR is set to 0;

iii) for a GBR, L4S DRB, WL4S GBR is set to be less than or equal to 1;

iv) WL4S PF is set to be greater than or equal to 1; and

v) WL4S 5QI is set to be less than or equal to 1, and WL4S PDB is set to be less than or equal to 1.

6 . The method of claim 3 , wherein at least one of the following is performed:

i) for non-L4S traffic, P PDB non-L4S is set to 1 if PDB DU is less than or equal to QDelay RLC , and P PDB non-L4S is set to 1/(PDB DU −QDelay RLC ) if PDB DU is greater than QDelay RLC , wherein PDB DU is a packet delay budget at the DU for a respective logical channel, and QDelay RLC is radio link control (RLC) queuing delay defined as a delay of the oldest RLC packet in the QoS flow that has not been scheduled yet; and

ii) for L4S traffic, P PDB L4S is set to 1 if PDB DU is less than or equal to QDelay RLC , and P PDB L4S =max[n/(PDB DU −QDelay RLC ), 1] if PDB DU is greater than QDelay RLC , wherein n is the number of packets which have been in the RLC queue for a specified time interval.

7 . The method of claim 3 , wherein at least one of the following is performed:

i) for non-L4S traffic, P PDB non-L4S is set to 1 if PDB DU is less than or equal to QDelay RLC , and P PDB non-L4S is set to 1/(PDB DU −QDelay RLC ) if PDB DU is greater than QDelay RLC , wherein PDB DU is a packet delay budget at the DU for a respective logical channel, and QDelay RLC is radio link control (RLC) queuing delay defined as a delay of the oldest RLC packet in the QoS flow that has not been scheduled yet; and

ii) for L4S traffic, Pppp is set to 1 if PDB DU is less than or equal to QDelay RLC , and P PDB L4S =1/[(PDB DU −QDelay RLC )*(PDB DU −QDelay RLC,2 )] if PDB DU >QDelay RLC and the RLC queue has at least two packets, wherein QDelay RLC,2 is the delay of the second oldest RLC packet in the QoS flow that has not been scheduled yet.

8 . The method of claim 1 , wherein, for non-L4S data radio bearers (DRBs) and L4S DRBs that are mapped to radio link control Unacknowledged Mode (RLC UM), the following are performed:

for non-L4S traffic, expiration of a first periodic timer having a first duration is used as a trigger for sending downlink data delivery status (DDDS) message from the DU to the CU-UP; and

for non-L4S traffic, expiration of a second periodic timer having a second duration different from the first duration is used as a trigger for sending downlink data delivery status (DDDS) message from the DU to the CU-UP.

9 . The method of claim 8 , wherein the first duration is greater than the second duration.

10 . The method of claim 8 , wherein the second duration is greater than the first duration.

11 . The method of claim 1 , wherein, for non-L4S data radio bearers (DRBs) and L4S DRBs that are mapped to radio link control Acknowledged Mode (RLC UM), the following are performed:

for non-L4S traffic, sending of downlink data delivery status (DDDS) message from the DU to the CU-UP is triggered at the expiration of a first periodic timer having a first duration or upon receipt of RLC status Protocol Data Unit (PDU), whichever occurs first; and

for L4S traffic, sending of DDDS message from the DU to the CU-UP is triggered at the expiration of a second periodic timer having a second duration different from the first duration or upon receipt of RLC status PDU, whichever occurs first.

12 . The method of claim 11 , wherein the first duration is greater than the second duration.

13 . The method of claim 11 , wherein the second duration is greater than the first duration.

14 . The method of claim 4 , wherein at least one of the following is performed at the DU to facilitate fair coexistence of a non-L4S data radio bearer (DRB) and an L4S DRB:

i) for a non-guaranteed bit rate (non-GBR) L4S DRB, WL4S GBR is set to 0;

ii) for a non-GBR, non-L4S DRB, W GBR is set to 0;

iii) for a GBR, L4S DRB, WL4S GBR is set to be less than or equal to 1;

iv) WL4S PF is set to be greater than or equal to 1; and

v) WL4S 5QI is set to be less than or equal to 1, and WL4S PDB is set to be less than or equal to 1.

Assignments (16)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 9, 2026
From: MAVENIR US INC.
To: MAVENIR SYSTEMS, INC.
Reel/Frame 073728/0534 →
RELEASE OF SECURITY INTEREST IN ADDITIONAL COLLATERAL RECORDED AT REEL 068462 AND FRAME 0603 Recorded Jul 31, 2025
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072308/0708 →
RELEASE OF SECURITY INTEREST IN COLLATERAL RECORDED AT REEL 069113 AND FRAME 0558 Recorded Jul 31, 2025
From: GLAS USA LLC
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072308/0172 →
RELEASE OF SECURITY INTERESTS (SIDECAR) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072263/0041 →
GRANT OF SECURITY INTEREST - PATENTS Recorded Jul 29, 2025
From: MAVENIR NETWORKS, INC.; MAVENIR SYSTEMS, INC.; ARGYLE DATA, INC.; MAVENIR, INC.; AQUTO CORPORATION; MAVENIR IPA UK LIMITED; MAVENIR SYSTEMS UK LIMITED; MAVENIR LTD.; MAVENIR US INC.
To: GLAS USA LLC
Reel/Frame 072245/0764 →
RELEASE OF SECURITY INTERESTS (SYNDICATED) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072263/0121 →
SECURITY INTEREST Recorded Jul 28, 2025
From: MAVENIR NETWORKS, INC.; MAVENIR SYSTEMS, INC.; ARGYLE DATA, INC.; MAVENIR, INC.; AQUTO CORPORATION; MAVENIR IPA UK LIMITED; MAVENIR SYSTEMS UK LIMITED; MAVENIR LTD.; MAVENIR US INC.
To: BLUE TORCH FINANCE LLC
Reel/Frame 072268/0439 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 28, 2025
From: MAVENIR SYSTEMS, INC.
To: MAVENIR US INC.
Reel/Frame 072245/0580 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 27, 2025
From: MAVENIR SYSTEMS, INC.
To: MAVENIR US, INC.
Reel/Frame 072245/0419 →
RELEASE OF SECURITY INTEREST Recorded Oct 4, 2024
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MAVENIR SYSTEMS, INC.
Reel/Frame 069113/0596 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Oct 4, 2024
From: MAVENIR SYSTEMS, INC.
To: GLAS USA LLC
Reel/Frame 069113/0558 →
SECURITY INTEREST Recorded Aug 30, 2024
From: MAVENIR SYSTEMS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 068822/0966 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT SUPPLEMENT Recorded Jul 19, 2024
From: MAVENIR SYSTEMS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB, AS COLLATERAL AGENT
Reel/Frame 068462/0603 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT SUPPLEMENT Recorded Jul 18, 2024
From: MAVENIR SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 068425/0209 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT SUPPLEMENT Recorded Jul 18, 2024
From: MAVENIR SYSTEMS, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 068425/0126 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 19, 2024
From: TANEJA, MUKESH; SEN, MOUSHUMI
To: MAVENIR SYSTEMS, INC.
Reel/Frame 067770/0731 →
Priority Claims (1)
IN 202321039516 · Jun 9, 2023 · national
Continuity (1)
Related Publication 20240414582A1 · Dec 12, 2024
References Cited (18)
US 10334594B2 · Sundararajan · 2019 [cited by examiner]
US 10785674B2 · Cakulev et al. · 2020 [cited by applicant]
US 20230142425A1 · Nádas · 2023 [cited by examiner]
US 20240314636A1 · Liu · 2024 [cited by examiner]
WO 2022005344A1 · 2022 [cited by applicant]
WO 2022153105A1 · 2022 [cited by applicant]
3rd Generation Partnership Project (3GPP) TS 36.300 v17.4 “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universa… [cited by applicant]
3rd Generation Partnership Project (3GPP) TS 38.300 V 17.4.0 “Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 17)” Mar. 2023; 3rd Generation Partnership Projec… [cited by applicant]
3rd Generation Partnership Project (3GPP) TS 23.501 V 18.1.0 “Technical Specification Group Services and System Aspects; System Architecture for the 5G System (5GS); Stage 2 (Release 18)” Mar. 2023; 3rd Generation Partn… [cited by applicant]
3rd Generation Partnership Project (3GPP ) TS 38.401 V 17.4.0 “Technical Specification Group Radio Access Network; NG-RAN; Architecture Description; (Release 17)” Mar. 2023; 3rd Generation Partnership Project, Valbonne,… [cited by applicant]
3rd Generation Partnership Project (3GPP) TS 38.425 17.3.0,“Technical Specification Group Radio Access Network; NG-RAN; NR user plane protocol; (Release 17)” Mar. 2023; 3rd Generation Partnership Project, Valbonne, Fran… [cited by applicant]
3rd Generation Partnership Project (3GPP) TS 38.323 V 17.4.0 Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification (Release 17) Mar. 2023; 3rd Generation Partnersh… [cited by applicant]
DeSchepper et al “RFC 9332: Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)” Internet Engineering Task Force (IETF); Jan. 2023. [cited by applicant]
Briscoe et al “RFC 9330: Low Latency, Low Loss and Scalable Throughout (L4S) Internet Service: Architecture” Internet Engineering Task Force (IETF); Jan. 2023. [cited by applicant]
Deschepper et al “RFC 9331: The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss and Scalable Throughput (L4S)” Internet Engineering Task Force (IETF); Jan. 2023. [cited by applicant]
Alvestrand “RFC 8825 Overview: Real-Time Protocols for Browser-Based Applications” Internet Engineering Task Force (IETF); Jan. 2021. [cited by applicant]
Extended European search report for corresponding European patent application No. 24180406, 8 pages, dated Oct. 21, 2024. [cited by applicant]
Ericcson “L4S Support in 5 G” 3rd Generation Partnership Project (3GPP) draft, R2191-0724; 3GPP TSG-RAN; WG2-#107; Aug. 26-30, 2019. [cited by applicant]