IP Library Patent Application 18644203
Patent Application
App. No. 18/644,203

METHOD AND SYSTEM FOR DATA ROUTING FOR SPLIT-BEARER AT A CELLULAR BASE STATION FOR A DUAL CONNECTIVITY NETWORK ARCHITECTURE

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 None
App. No.
18/644,203
Filed
Apr 24, 2024
Art Unit
2415
USPC
370/236
Abstract

Systems and methods for updating a UL split threshold for a 4G leg and 5G leg for split Data Radio Bearers (DRBs). A dynamic splitting solution can be implemented at 5G CU-UP, 5G DU, 4G DU, or other equivalent nodes. An interleaving approach at CU-UP minimizes Packet Data Convergence Protocol (PDCP) reordering at CU-UP. A Near-RT RIC-based approach for an exchange of relevant parameters via an E2 interface can be run at a Near-RT RIC server.

Claims (82)

1 . A method comprising:

obtaining a LTE Downlink Data Delivery Status (DDDS) at a gNB node centralized unit (gNB CU) via a 4G leg from an LTE DU (MeNB DU);

obtaining a NR DDDS at the gNB CU via a 5G leg from a SgNB DU;

computing an intermediate factor for a final split factor, the intermediate factor being computed from Desired Buffer Size (DBS) parameters in the LTE DDDS message and the NR DDDS message;

computing the final split factor or a scheduling method for dynamic splitting and routing of DL Packet Data Convergence Protocol (PDCP) Protocol Data Units PDUs on a 4G leg and a 5G leg; and

routing the PDCP PDUs on the 4G leg, the 5G leg, or both based on the split factor calculation.

2 . The method of claim 1 , further comprising

setting an LTE DBS for a data radio bearer (DRB) equal to the DBS in the LTE DDDS from the 4G DU at the gNB CU;

computing the intermediate factor of a LTE DBS factor as m*a DBS weight*(the LTE Desired Buffer Size/(the LTE DBS+an NR DBS);

setting the NR DBS for a DRB equal to the DBS in the NR DDDS from the NR DU at the gNB CU;

computing the intermediate factor of an NR DBS factor as m*a DBS weight*(the NR Desired Buffer Size/(the LTE DBS+an NR DBS); and

computing the final split factor.

3 . The method of claim 2 , wherein, if there is data in a Packet Data Convergence Protocol (PDCP) Data Queue, the method further comprises:

when routing DL Packet Data Convergence Protocol (PDCP) PDUs in the 5G leg, the DBS at an SgNB CU-UP of the gNB CU for the 5G leg is updated using the last received DBS from the MeNB DU and successfully transmitted bytes from the SgNB CU-UP to the MeNB DU; and

when routing DL PDCP PDUs in an NR Leg, the DBS at the SgNB CU-UP for NR is updated using a last received DBS from a SgNB DU and the number of successfully transmitted bytes from the SgNB CU-UP to the SgNB DU.

4 . The method of claim 2 , further comprising:

computing a LTE DDR Factor ddrFactorLTE and a NR DDR factor ddrFactorNR are configured to operate on the received DDR on either or both of the 4G leg or the 5G leg.

5 . The method of claim 1 , wherein the intermediate factor is computed as the ratio of DDR received in the respective 4G leg and the 5G leg to the sum of a latest of the DDRs received in DDDS from both the 4G leg and the 5G leg.

6 . The method of claim 3 , further comprising:

when the gNB receives the LTE DDDS from the LTE DU, the DDR LTE Factor (ddrFactorLTE) is set to m*a DDR weight (WDdr) if the DDR is absent in the LTE DDDS message; and

if DDR is present in LTE DDDS message, the DDR LTE factor is set to ddrFactorLTE=m*Wddr*/(the DDR from LTE DDDS+a DDR as received from a latest NR DDDS).

7 . The method of claim 3 , further comprising:

when the gNB receives the NB DDDS from the NR DU, the DDR NR Factor (ddrFactorLTE) is set to m*a DDR weight (WDdr) if the DDR is absent in the NR DDDS message; and

if DDR is present in NR DDDS message, the DDR NR factor is set to ddrFactorLTE=m*Wddr*/(the DDR from NR DDDS+a DDR as received from a latest LTE DDDS).

8 . The method of claim 3 , further comprising: when the gNB receives the LTE DDDS from the LTE DU, the DDR LTE Factor (ddrFactorLTE) is set to m*a DDR weight (WDdr) if the DDR is absent in the LTE DDDS message; and

if DDR is present in LTE DDDS message, the DDR LTE factor is set to ddrFactorLTE=m*Wddr*/(the DDR from LTE DDDS+a DDR as received from a latest NR DDDS of the NR DDDS).

9 . The method of claim 1 , further comprising:

processing, at the gNB CU-UP or a RAN Intelligent Controller (RIC), midhaul quality parameters in the DDDS to determine the quality of the 4G leg and the 5G leg.

10 . The method of claim 9 , wherein the midhaul quality parameters further comprise:

a Number of lost NR-U Sequence Number ranges reported;

a start of lost NR-U Sequence Number range and end of lost NR-U Sequence Number range;

a Highest successfully delivered NR PDCP Sequence Number (RLC AM);

a Highest transmitted NR PDCP Sequence Number (RLC UM);

a Successfully delivered retransmitted NR PDCP Sequence Number; and

a Retransmitted NR PDCP Sequence Number.

11 . The method of claim 10 , further comprising:

when a cause report element in the DDDS message includes cause value including a Radio Link Outage, the Radio Link Outage indicating one of the a 4G leg or the 5G leg can no longer continue to transmit the DL PDCP packets, the remaining 4G leg or 5G leg that is an operative leg continues to transmit the packets from the PDCP PDU Queue, and where the gNB CU-UP is unaware of the NR UP PDCP packets that are transmitted or yet-to-be-transmitted from the DU to UE in the leg experiencing the outage, the gNB CU-UP transmits all the packets which have not been acknowledged from the leg reporting Radio Link Outage to the operative leg.

12 . The method of claim 10 , further comprising:

determining, by gNB CU-UP or the RIC, which PDCP SNs are received successfully at UE using the Highest successfully delivered NR PDCP Sequence Number parameter, the Highest transmitted NR PDCP Sequence Number parameter, or both; and

excluding PDCP SNs that are received successfully at UE when the gNB CU-UP decide which PDCP SNs are received successfully at UE and while the gNB CU-UP transmits the PDCP SNs on the operative leg.

13 . The method of claim 10 , further comprising:

transmitting all the packets on only the operative leg until the DDDS message includes cause value including a Radio Link resume.

14 . The method of claim 3 wherein the method further comprises:

computing and maintaining a final Split Factor per 4G leg and 5G leg.

15 . The method of claim 14 , comprising,

recomputing the intermediate split factors;

calculating the sum of all the intermediate factors of a given leg Li, where i takes values “LTE” and “5G NR” and the total sum of all intermediate factors of both legs is denoted as L;

computing the final split factor for a leg-i as the ratio of Li to L;

splitting the data transmission in proportion to an LTE Split Factor (SplitFcatorLTE) and a NR Split Factor (SplitFactorNR) across the 4G leg and 5G leg.

16 . A method comprising:

calculating a Routing Metric as a measure of throughput a 4G leg link or a 5G leg link can provide, wherein the routing metric includes a Routing Metric ratio for the throughput measure of the 4G leg link or the 5G leg link,

dynamically splitting, by a gNB node centralized unit user Plane (gNB CU-UP), Protocol Data Units PDUs across the 4G leg link or 5G leg link based on the Routing Metric ratio.

17 . The method of claim 16 , wherein the Routing Metric is calculated as:

Routing Metric=MCSrate(AverageCQI)×(DL Radio Quality Index)/100×F1(HARQ Failure)×F2(PL,UL Radio Quality Index).

18 . The method of claim 17 wherein if the F1(HARQ failure) is below a threshold, the value of function becomes 1; if the HARQ failure rate is higher than the threshold, the value of function reduces to zero.

19 . The method of claim 17 wherein the HARQ failure is calculated as:

F1(HARQ Failure)=1−(HARQ Failure rate)/100.

20 . The method of claim 16 wherein the gNB CU-UP or a RIC computes the Routing Metric with the a split factor, a DBS factor, a DBS weight factors, a DDR factor, and a DDR weight factor, to decide an optimal split factor splitting across the 4G leg link and 5G leg link.

21 . The method of claim 20 wherein the computation is executed in the RAN Intelligent Controller (RIC).

22 . The method of claim 21 , wherein the RIC can computation includes data from different DUs.

23 . A method comprising:

calculating a DU delay at a gNB centralized unit user Plane (gNB CU-UP) or a RAN Intelligent Controller (RIC) with one or more DL Delay counters; and

factoring DU delay for a policy to be executed by the gNB when splitting a packet transmission over a 4G leg and a 5G leg.

24 . The method of claim 23 , wherein a DU message for assistance information data includes a DL Delay DU Result to convey a DL delay at the DU to the gNB CU-UP.

25 . The method of claim 23 , further comprising:

calculating the DU delay at the gNB CU-UP, wherein a DU message to convey a DL delay at the DU is relayed from the DU to a CU-CP via an FI-C interface, and from the CU-CP to the gNB CU-UP over an E1 interface.

26 . The method of claim 23 wherein a UE CONTEXT SETUP REQUEST message and a UE CONTEXT MODIFICATION REQUEST message include Boolean parameters for “RLC Delay Required”, “Periodicity for RLC Delay”, and “RLC Delay Inclusion” for all the Signaling Radio Bearers (SRB) and Data Radio Bearers (DRB) for which RLC delay in DU is sought.

27 . The method of claim 23 wherein an FI-C message includes a DRB Stats field, which is configured to include UE gNB-CU UE F1AP ID, gNB-DU UE F1AP ID and RLC Delay for as many DRBs for which the DU agreed to send RLC delay information.

28 . The method of claim 27 wherein an E1 interface message includes an F1-C Container field which encapsulates the DRB Stats field data.

29 . The method of claim 23 further comprising

estimating, by the gNB CU-UP or the RIC, a one-way delay in the DL across the 4G leg and the 5G leg; and

factoring the estimated delay when splitting the packet transmission over 4G and 5G legs by interleaving packets based on PDCP SNs when transmitting the packets to the UE so that the of the packets arrive substantially in order at the UE.

30 . The method of claim 28 , wherein to minimize out-of-order PDCP SN arrival at a UE's Packet Data Convergence Protocol (PDCP) layer, a smaller SN is scheduled on a longer of the 4G leg or 5G leg while a larger SN is scheduled on the shorter of the 4G leg or 5G leg.

31 . The method of claim 23 , further comprising:

calculating a DU delay at the RIC with one or more DL Delay counters sent via an E2 interface;

identifying one or more policies to be execute by the gNB CU-UP; and

sending a control request from the RIC to the gNB CU-UP to execute the policy on the 4G leg, the 5G leg, or both.

32 . The method of claim 23 , wherein the policy for execution is one or more of:

Policy1: send P number of packets for next M milliseconds;

Policy2: interleave the PDCP Packets between MeNB and SgNB in M:S pattern where M packets would be transmitted in MeNB and next S Packets would be transmitted over SgNB;

Policy3: route entire packets towards SgNB for next M milliseconds; and

Policy4: route entire packets towards MeNB for next N milliseconds.

Assignments (16)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 9, 2026
From: MAVENIR US INC.
To: MAVENIR NETWORKS, INC.
Reel/Frame 073728/0678 →
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 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 →
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 →
RELEASE OF SECURITY INTERESTS (SIDECAR) Recorded Jul 29, 2025
From: JPMORGAN CHASE BANK, N.A.
To: MAVENIR SYSTEMS, INC.
Reel/Frame 072263/0041 →
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 NETWORKS, INC.
To: MAVENIR US INC.
Reel/Frame 071845/0198 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 27, 2025
From: MAVENIR NETWORKS, INC.
To: MAVENIR US, INC.
Reel/Frame 071842/0387 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 12, 2024
From: PRASAD, GIRI; TANEJA, MUKESH; KAIMALETTU, SUNIL; SAYEE, KOMPALLI CHAKRAVARTULA KALYANA RAMA SESHA
To: MAVENIR SYSTEMS, INC.
Reel/Frame 068251/0355 →
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 →