Packet data convergence protocol (PDCP) enhancements in dual-connectivity networks
In embodiments, apparatuses, methods, and storage media may be described for identifying, by a master evolved NodeB (MeNB), one or more packet data convergence protocol (PDCP) packets that were previously scheduled to be transmitted to a user equipment (UE) by a secondary eNB (SeNB). The PDCP packets that are identified by the MeNB may then be transmitted, or retransmitted, to the UE. Additionally, embodiments may include apparatuses, methods, and storage media for allowing the UE to identify one or more parameters related to a PDCP reordering process to be performed by the UE. Other embodiments may be claimed.
1. A Master evolved NodeB (MeNB) of a dual connectivity network, the MeNB comprising:
a buffer to store a plurality of packet data convergence protocol (PDCP) packets transmitted by the MeNB to a secondary eNB (SeNB) of the dual connectivity network for delivery to a user equipment (UE) by a radio link control (RLC) of the SeNB; and
packet data convergence protocol (PDCP) circuitry coupled with the buffer, the PDCP circuitry to:
identify, based on a status report from the SeNB, successful delivery of a first PDCP packet of the plurality of PDCP packets to the UE; and
cause the first PDCP packet to be removed from the buffer based on said identification of the successful delivery of the PDCP packet;
wherein:
the UE is to simultaneously communicatively couple with the MeNB and the SeNB; the MeNB is to control a transmission of the SeNB;
the PDCP circuitry is to identify an unsuccessful delivery of a second PDCP packet of the plurality of PDCP packets to the UE based on the status report or another status report received from the SeNB and cause an RLC of the MeNB to attempt to deliver the second PDCP packet to the UE; and
the status report is a periodic status report, an event-based status report, or a trigger-based status report.
2. The MeNB of claim 1 , wherein the status report is a periodic status report or a trigger-based status report.
3. The MeNB of claim 1 , wherein the status report is to be received in flow control signaling over an X2 interface.
4. The MeNB of claim 1 , wherein a plurality of status reports are to be received while the UE is simultaneously communicatively coupled with the MeNB and the SeNB.
5. The MeNB of claim 1 , wherein the PDCP circuitry is further to cause transmission of a request for the status report to the SeNB.
6. One or more non-transitory, computer-readable media having instructions that, when executed by one or more processors, cause a master evolved node B (MeNB) of a dual connectivity network to:
transmit a plurality of packet data convergence protocol (PDCP) packets to a secondary eNB (SeNB) of the dual connectivity network for delivery to a user equipment (UE) by a radio link control (RLC) of the SeNB;
store the plurality of PDCP packets in a buffer;
identify, based on a status report from the SeNB, successful delivery of a first PDCP packet of the plurality of PDCP packets;
remove the PDCP packet from the buffer based on said identification of the successful delivery of the PDCP packet;
identify an unsuccessful delivery of a second PDCP packet of the plurality of PDCP packets to the UE based on the status report or another status report from the SeNB; and
cause an RLC of the MeNB to attempt to deliver the second PDCP packet to the UE based on identification of the unsuccessful delivery,
wherein the status report is a periodic status report, an event-based status report, or a trigger-based status report.
7. The one or more non-transitory, computer-readable media of claim 6 , wherein the status report is a periodic status report or a trigger-based status report.
8. The one or more non-transitory, computer-readable media of claim 6 , wherein the status report is to be received in flow control signaling over an X2 interface.
9. The one or more non-transitory, computer-readable media of claim 6 , wherein a plurality of status reports are to be received while the UE is simultaneously communicatively coupled with the MeNB and the SeNB.
10. The one or more non-transitory, computer-readable media of claim 6 , wherein the instructions, when executed, further cause the MeNB to transmit a request for the status report to the SeNB.