Systems and methods for dual-connectivity split-bearer packet management
Systems and methods for dual-connectivity split-bearer packet management are presented. In one embodiment, a dual-connectivity, split-bearer base station, comprises: at least one centralized unit (CU) comprising a CU-CP) and at least one CU-UP; at least one DU coupled to the at least one CU-UP, wherein the at least one DU is coupled to one or more RUs configured as a first cell group to establish a first radio link for communicating with UE within a wireless coverage area; an eNodeB coupled to the at least one CU-UP, wherein the eNodeB comprises one or more RPs configured as a second cell group to establish a second radio link for communicating with UE within the wireless coverage area; and a traffic split controller configured to selectively direct PDCP packets to either the DU or the eNodeB as a function of packet delay times associated with the DU and the eNodeB.
1 . A dual-connectivity, split-bearer base station (base station), the base station comprising:
at least one centralized unit (CU) comprising a centralized unit control-plane (CU-CP) and at least one centralized unit user-plane (CU-UP);
at least one distributed unit (DU) coupled to the at least one CU-UP, wherein the at least one DU is coupled to one or more radio units (RUs) configured as a first cell group to establish a first radio link for communicating with user equipment (UE) within a wireless coverage area;
an eNodeB coupled to the at least one CU-UP, wherein the eNodeB comprises one or more radio points (RPs) configured as a second cell group to establish a second radio link for communicating with the user equipment within the wireless coverage area;
a traffic split controller configured to selectively direct Packet Data Convergence Protocol (PDCP) packets to either the DU or the eNodeB as a function of packet delay times associated with the DU and the eNodeB; and
wherein the traffic split controller is configured to execute a traffic split algorithm,
wherein the traffic split algorithm instructs the traffic split controller to:
calculate a first packet delivery delay based on feedback received from a radio link control (RLC) entity of the eNodeB;
calculate a second packet delivery delay based on the feedback received from an RLC entity of the DU; and
selectively enqueue the PDCP packets to either an RLC Queue server of the eNodeB or an RLC Queue server of the DU based on whether the first or the second packet delivery delay is a lesser delay;
wherein calculating the first packet delivery delay and the second packet delivery delay, and selectively enquiring PDCP packets is performed by the traffic split controller comprising the traffic split algorithm executed by the CU, wherein the traffic split controller is configured to selectively direct the PDCP packets to either the DU or the eNodeB as the function of the packet delay times associated with the DU and the eNodeB.
2 . The base station of claim 1 , wherein the RLC entity of the eNodeB comprises a Long-Term-Evolution (LTE) RLC.
3 . The base station of claim 1 , wherein the RLC entity of the DU comprises a 5G New Radio (NR) RLC.
4 . The base station of claim 1 , wherein the feedback received from the RLC entity of the DU and the feedback received from the RLC entity of the eNodeB each comprise Downlink Data Delivery Status (DDDS) feedback derived from an indication of successful packet receptions by the UE.
5 . The base station of claim 1 , wherein the traffic split algorithm instructs the traffic split controller to calculate the first packet delivery delay and the second packet delivery delay in response to receiving Downlink Data Delivery Status (DDDS) updates.
6 . The base station of claim 5 , wherein the traffic split algorithm instructs the traffic split controller to:
determine a delay gap between the first packet delivery delay and the second packet delivery delay; and
close the delay gap by sending enqueued packets to either the RLC Queue server of the eNodeB or the RLC Queue server of the DU based on whether the first or the second packet delivery delay has the lesser delay.
7 . The base station of claim 6 , wherein the traffic split algorithm instructs the traffic split controller to:
determine when the delay gap is filled; and
distribute any remaining packets received prior to a next DDDS update based on a service rate ratio associated with the RLC Queue server of the eNodeB and the RLC Queue server of the DU.
8 . The base station of claim 1 , wherein the at least one CU-UP is coupled to the DU over an F1-U interface.
9 . The base station of claim 1 , wherein the at least one CU-UP is coupled to the eNodeB over an X2 interface.
10 . The base station of claim 1 , wherein the DU is coupled to the one or more RUs by a fronthaul network.
11 . The base station of claim 1 , wherein the eNodeB is coupled to the one or more RPs by a fronthaul network.
12 . The base station of claim 1 , wherein the CU is coupled to a wireless service operator core network by an S1-U interface.
13 . A method for dual-connectivity, split-bearer traffic management for a base station, wherein the base station comprises: at least one centralized unit (CU) comprising a centralized unit control-plane (CU-CP) and at least one centralized unit user-plane (CU-UP); at least one distributed unit (DU) coupled to the at least one CU-UP, wherein the at least one DU is coupled to one or more radio units (RUs) configured as a first cell group to establish a first radio link for communicating with user equipment (UE) within a wireless coverage area; and an eNodeB coupled to the at least one CU-UP, wherein the eNodeB comprises one or more radio points (RPs) configured as a second cell group to establish a second radio link for communicating with the user equipment within the wireless coverage area, the method comprising:
calculating a first packet delivery delay based on feedback received from a radio link control (RLC) entity of the eNodeB;
calculating a second packet delivery delay based on feedback received from an RLC entity of the DU; and
selectively enqueuing Packet Data Convergence Protocol (PDCP) packets to either an RLC Queue server of the eNodeB or an RLC Queue server of the DU based on whether the first or the second packet delivery delay is a lesser delay;
selectively enqueuing Packet Data Convergence Protocol (PDCP) packets to either an RLC Queue server of the eNodeB or an RLC Queue server of the DU based on whether the first or the second packet delivery delay is a lesser delay;
wherein calculating the first packet delivery delay and the second packet delivery delay, and selectively enquiring PDCP packets is performed by a traffic split controller comprising a traffic split algorithm executed by the CU, wherein the traffic split controller is configured to selectively direct the PDCP packets to either the DU or the eNodeB as a function of packet delay times associated with the DU and the eNodeB.
14 . The method of claim 13 , further comprising:
receiving the feedback received from the RLC entity of the DU and the feedback received from the RLC entity of the eNodeB each as Downlink Data Delivery Status (DDDS) feedback derived from an indication of successful packet receptions by the UE.
15 . The method of claim 14 , further comprising:
calculating the first packet delivery delay and the second packet delivery delay in response to receiving Downlink Data Delivery Status (DDDS) updates.
16 . The method of claim 15 , further comprising:
determining a delay gap between the first packet delivery delay and the second packet delivery delay; and
closing the delay gap by sending enqueued packets to either the RLC Queue server of the eNodeB or the RLC Queue server of the DU based on whether the first or the second packet delivery delay has the lesser delay.
17 . The method of claim 16 , further comprising:
determining when the delay gap is filled; and
distributing remaining packets received prior to a next DDDS update based on a service rate ratio associated with the RLC Queue server of the eNodeB and the RLC Queue server of the DU.
18 . The method of claim 13 , wherein the at least one CU-UP is coupled to the DU over an F1-U interface.
19 . The method of claim 13 , wherein the at least one CU-UP is coupled to the eNodeB over an X2 interface.
20 . The method of claim 13 , wherein the DU is coupled to the one or more RUs by a fronthaul network.
21 . The method of claim 13 , wherein the eNodeB is coupled to the one or more RPs by a fronthaul network.
22 . The method of claim 13 , wherein the CU is coupled to a wireless service operator core network by an S1-U interface.
23 . The method of claim 13 , wherein the RLC entity of the eNodeB comprises a Long-Term-Evolution (LTE) RLC.
24 . The method of claim 13 , wherein the RLC entity of the DU comprises a 5G New Radio (NR) RLC.