GB2520923A - Bearer reconfiguration - Google Patents

Abstract

A data transmission method of a User Equipment (UE) in a Long Term Evolution (LTE) compliant mobile communications network comprises detecting reconfiguration of a bearer from a split bearer, in which uplink Packet Data Convergence Protocol Protocol Data Units, PDCP PDUs, are transmitted to both a Master eNB (MeNB) and to a Secondary Enb (SeNB), to non-split bearer in which uplink PDCP PDUs are transmitted only to the MeNB. If reconfiguration of a bearer from a split bearer to a non-split bearer is detected, the method further comprises initiating retransmission of PDCP Service Data Units, SDUs, from the first PDCP SDU for which transmission of the corresponding PDCP PDU was attempted via the SeNB and for which there has been no confirmation of successful delivery by a protocol layer below the PDCP layer within the UE. The method further comprises retransmitting only PDCP SDUs for which transmission of the corresponding PDCP PDU was attempted via the SeNB. PDCP PDUs sent via the MeNB are not re-transmitted. The method avoids unnecessary re-transmissions.

Description

BEARER RECONFIGURATION

FIELD OF THE INVENTION

[0001] The present invention relates to bearer reconfiguration. In particular, certain embodiments of the present invention relate to reconfiguration of a split bearer to a non-split bearer, or vice versa, in a 3rd Generation Partnership Project (3GPP) Long Term Evolution (LIE) or LTE Advanced compliant mobile communications network comprising a mobile terminal (also referred to herein as the User Equipment, UE) and network equipment. The present invention relates to determining which Packet Data Convergence Protocol, PDCP, Service Data Units (SDU5) the UE should retransmit following bearer reconfiguration.

BACKGROUND OF THE INVENTION

[0002] Wireless or mobile (cellular) communications networks in which a mobile terminal (UE, such as a mobile handset) communicates via a radio link to a network of base is stations (eNBs) or other wireless access points connected to a telecommunications network, have undergone rapid development through a number of generations. The initial deployment of systems using analogue signalling has been superseded by Second Generation (2G) digital systems such as Global System for Mobile communications (GSM), which typically use a radio access technology known as GSM Enhanced Data rates for GSM Evolution Radio Access Network (GERAN), combined with an improved core network.

[0003] Second generation systems have themselves been largely replaced by or augmented by Third Generation (3G) digital systems such as the Universal Mobile Telecommunications System (UMTS), which uses a Universal Terrestrial Radio Access Network (UTRAN) radio access technology and a similar core network to GSM. UMTS is specified in standards produced by 3GPP. Third generation standards provide for a greater throughput of data than is provided by second generation systems. This trend is continued with the move towards Fourth Generation (4G) systems.

[0004] 3GPP design, specify and standardise technologies for mobile wireless communications networks. Specifically, 3GPP produces a series of Technical Reports (IR) and Technical Specifications (TS) that define 3GPP technologies. The focus of 3GPP is currently the specification of standards beyond 3G, and in particular an Evolved Packet System (EPS) offering enhancements over 3G networks, including higher data rates. The set of specifications for the EPS comprises two work items: Systems Architecture Evolution (SAE, concerning the core network) and LTE concerning the air interface. The first set of EPS specifications were released as 3GPP Release 8 in December 2008. LTE uses an improved radio access technology known as Evolved UTRAN (E-UTRAN), which offers potentially greater capacity and additional features compared with previous standards. SAE provides an improved core network technology referred to as the Evolved Packet Core (EPC). Despite LTE strictly referring only to the air interface, LIE is commonly used to refer to the whole of the EPS, including by 3GPP themselves. LIE is used in this sense in the remainder of this specification, including when referring to LTE enhancements, such as LTE Advanced. LTE is an evolution of UMTS and shares certain high level components and protocols with UMTS. LTE Advanced offers still higher data rates compared to LIE and is defined by 3GPP standards releases from 3GPP Release 10 up to and including 3GPP Release 12. LTE Advanced is considered to be a 4G mobile communication system by the International Telecommunication Union (ITU).

[0005] The present invention is implemented within an LTE mobile network. Therefore, an overview of an LTE network is shown in Figure 1. The LTE system comprises three high level components: at least one UE 102, the E-UTRAN 104 and the EPC 106. The EPC 106 communicates with Packet Data Networks (PDNs) and servers 108 in the outside world. Figure 1 shows the key component parts of the EPC 106. It will be appreciated that Figure 1 is a simplification and a typical implementation of LTE will include further components. In Figure 1 interfaces between different pads of the LTE system are shown.

The double ended arrow indicates the air interface between the UE 102 and the E-UTRAN 104. For the remaining interfaces user data is represented by solid lines and signalling is represented by dashed lines.

[0006] The E-UTRAN 104 comprises a single type of component: an eNB (E-UIRAN Node B) which is responsible for handling radio communications between the UE 102 and the EPC 106 across the air interface. An eNB controls UEs 102 in one or more cell. LTE is a cellular system in which the eNBs provide coverage over one or more cells. Typically there is a plurality of eNBs within an LIE system. In general, a UE in LTE communicates with one eNB through one cell at a time.

[0007] Key components of the EPC 106 are shown in Figure 1. It will be appreciated that in an LTE network there may be more than one of each component according to the number of UE5 102, the geographical area of the network and the volume of data to be transported across the network. Data traffic is passed between each eNB and a corresponding Serving Gateway (S-GW) 110 which routes data between the eNB and a PDN Gateway (P-GW) 112. The P-GW 112 is responsible for connecting a UE to one or more servers or PDNs 108 in the outside world. The Mobility Management Entity (MME) 114 controls the high-level operation of the U E 102 through signalling messages exchanged with the UE 102 through the E-UTRAN 104. Each UE is registered with a single MME. There is no direct signalling pathway between the MME 114 and the UE 102 (communication with the UE 102 being across the air interface via the E-UTRAN 104).

Signalling messages between the MME 114 and the UE 102 comprise EPS Session Management (ESM) protocol messages controlling the flow of data from the UE to the outside world and EPS Mobility Management (EMM) protocol messages controlling the rerouting of signalling and data flows when the UE 102 moves between eNBs within the E-UTRAN. The MME 114 exchanges signalling traffic with the S-GW 110 to assist with routing data traffic. The MME 114 also communicates with a Home Subscriber Server (HSS) 116 which stores information about users registered with the network.

[0008] Within an LTE network, data is transferred between different components of the network using bearers. An EPS bearer serves to transfer data between a UE and a P-GW.

The data flow is bi-directional. Data carried by an EPS bearer comprises one or more service data flows carrying data for a particular service, for instance streamed media.

Each service data flow comprises one or more packet flows.

[0009] 3GPP Radio Access Network (RAN) workgroups are current working on a Study Item (SI) called "Small Cell Enhancements". The technical outcome of this SI is documented in 3GPP TR 36.842 Evolved Universal Terrestrial Radio Access (E-UTRA)"; Study on Small Cell enhancements for E-UTRA and E-UTRAN -Higher layer aspects (Release 12); vO.4.0. 3GPP TR 36.842 concerns the radio access aspects of the SI and impacts upon both the UE and the eNB. Small cell enhancements are applicable, for instance, where there is a macro cell and a small cell (within the coverage area of the macro cell) operating on the same carrier frequency.

[0010] It is currently proposed that the RAN will support so called "dual connectivity" functionality. Dual connectivity refers to an operation where a given UE consumes radio resources provided by at least two different network points (Master and Secondary eNBs) connected with non-ideal backhaul while the UE is active within the network (in an RRC CONNECTED (Radio Resource Control Connected) state. Dual connectivity permits a greater data rate to be achieved between the UE and the eNB. To achieve dual connectivity, it is proposed that the RAN will support "bearer split" functionality. In dual connectivity, bearer split refers to the ability to split a bearer over multiple eNBs. A Master eNB (MeNB, usually the macro cell eNB) is the eNB which terminates at least S1-MME interface (the interface between the eNB and the MME) and therefore act as mobility anchor towards the Core Network (CN). A Secondary eNB (SeNB) is an eNB providing additional radio resources for the UE, which is not the MeNB.

[0011] Referring to Figure 2, this shows option 3 of Figure 8.1.1-1 of TS 36.842, which 33 illustrates one bearer split option, taking the downlink direction as an example. It can be seen that there is a first EPS bearer (#1: solid arrows) communicating directly from a P-GW (not shown) via the S-GW and the MeNB to the UE. A second EPS bearer (#2: dashed arrows) passes from the MeNB to the UE via the SeNB as well as directly between the MeNB and the UE. The second EPS bearer is split across the RAN.

[0012] To achieve a split bearer it is necessary to modify the existing user plane architecture shown in Figure 6-i of 3GPP TS 36.300 Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN)"; Overall description; Stage 2 (Release 11); vii.7.0 (not reproduced in the present specification. At an eNB, for communicating with the UE across the air interface to, the eNB comprises a protocol stack having a PDCP layer, a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer. Collectively, these protocol layers form the data link layer: layer two of the standard Open Systems Interconnection (OSI) model. The MAC layer carries out low-level control of the physical layer (layer i of the OSI model, and outside of the scope of the present specification), including scheduling data transmissions between the mobile and the base station. The RLC layer maintains the data link between the UE and the eNB, and handles the acknowledgement of receipt of data packets, when required. The PDCP layer carries out higher-level transport functions including header compression and security. At each layer of the protocol stack the protocol receives a data packet from the protocol above in the form of a Service Data Unit (SDU), processes the packets and adds a header to form a Protocol Data Unit (PDU). The PDU becomes the incoming SDU of the next layer down the stack.

[0013] In a bearer split architecture such as is shown in Figure 2 the layer 2 protocol stack at the eNB is split between the MeNB and the SeNB. Specifically! a split radio bearer uses two RLC entities as shown in Figure 3, which reproduces Figure 8.1.1.8-1 from 3GPP TR 36.842. Figure 3 shows a first non-split bearer protocol stack at the MeNB (solid boxes). Figure 3 shows data being received from the S-GW across the Si interface.

Figure 3 further shows a second split radio bearer (dashed boxes and dashed arrows).

For the split bearer there is a single PDCP entity at the MeNB and duplicated RLC/MAC protocol stack entities for the split bearer in both the MeNB and the SeNB. Data is sent between the single PDCP entity in the MeNB and the RCLIMAC entities in the SeNB across the Xn interface (alternatively referred to as the X2 interface). Although not shown in Figure 3, at the UE side there would be corresponding MAC/RLC/PDCP entities, and specifically a single UE PDCP entity and duplicated UE MAC/RLC entities.

[0014] In certain scenarios, part or the whole of the radio bearer protocol stack may be moved from one termination point to another termination point, for instance from one eNB to another eNB. For non-split radio bearers this may be due to the UE roaming between cells controlled by separate eNBs. In this case some of the on-going transmissions in the discontinued user plane stack will be terminated before successful delivery of the corresponding PDCP SDUs has been ensured. To overcome the loss that would be the iesult of this termination, PDCP SDU retiansmissions may be initiated after the radio bearer protocol stack move. So far, 3GPP RAN2 specifications have only specified how PDCP SDU retransmissions are handled for non-split bearers (that is, how PDCP SDU ietransmissions aie to be handled when the complete RAN protocol stack is moved). If it is required to ieconfiguie a split bearer as a non-split bearer, for instance due to the UE moving out of the coverage area of the small cell, while remaining in the coverage area of the macro cell, then this also requires at least the pad of the radio bearer protocol stack within the SeNB to be moved. Applying the same retransmission techniques when ieconfiguring a split bearer to a non-split bearer will lead to inefficient retransmission, as is described in greater detail below.

BRIEF SUMMARY OF THE DISCLOSURE

[0015] It is an aim of certain embodiments of the present invention to improve the efficiency of PDCP SDU retransmission when reconfiguring a split bearer as a non-split beaiei. Certain embodiments relate specifically to retransmissions of POOP SDUs from the UE to the network. Certain embodiments of the present invention aie specifically concerned with the case that a split bearer is reconfigured to a non-split bearer while keeping the same POOP entity in the network. In this case the part of the user plane stack in the SeNB is terminated and transmissions on-going in that part may be lost. Certain embodiments of the invention are concerned specifically with bearers configured for reliable transport, for instance using RLC-Acknowledged Mode. In RLC-Acknowledged Mode the transmitter sends PDUs and stores the POUs in a retransmission buffer until an acknowledgement of receipt is received. The transmittei regularly polls the receivel to return a status PDU listing the received PDUs. The transmitter may then delete the received PDUs from the buffer and re-transmit the remaining PDUs.

[0016] According to a first aspect of the present invention there is provided a data transmission method of a User Equipment! UE, in a Long Term Evolution, LTE. compliant mobile communications network, the method comprising: detecting reconfiguration of a bearer from a split bearer in which uplink Packet Data Convergence Protocol, PDCP, Protocol Oata Units, POUs, are transmitted to both a Master eNB, MeNB, and to a Secondaiy eNB, SeNB, to non-split bearer in which uplink PDCP POUs aie tiansmitted only to the MeNB; and if reconfiguration of a bearer from a split bearer to a non-split bearer is detected: initiating retransmission of PDCP Service Data Units, SDUs, from the first PDCP SOU for which transmission of the corresponding POOP PDU was attempted via the SeNB and for which theie has been no confiimation of successful deliveiy by a protocol layer below the PDCP layer within the UE; and retransmitting only PDCP SDUs for which transmission of the corresponding PDCP PDU was attempted via the SeNB.

[0017] The retransmission of PDCP SDUs may be in ascending order of count values assigned to the PDCP SDUs prior to the reconfiguration of the bearer.

[0018] The method may further comprise: receiving a PDCP status report from the MeNB; and determining that PDCP SDUs that are indicated in the PDCP status report as received need not be retransmitted.

[0019] The UE may be configured to use only bearers for which successful delivery of PDCP PDUs is acknowledged by the eNB at a protocol layer below the FDCP layer.

[0020] The UE may be configured to use only bearers using Radio Link Control Acknowledged Mode, RLC-Acknowledged Mode.

[0021] Successful delivery of a PDCP PDU may be confirmed by the Radio Link Control, RLC, layer or the Medium Access Control, MAC, layer.

[0022] The method may further comprise: determining whether, following reconfiguration of the bearer from a split bearer to a non-split bearer, PDCP transmissions are to be terminated within the MeNB or the SeNB; wherein the steps of initiating retransmission of PDCP SDUs from the first PDCP SDU for which transmission of the corresponding PDCP PDU was attempted via the SeNB and for which there has been no confirmation of successful delivery by a protocol layer below the PDCP layer within the UE, and retransmitting only PDCF SDUs for which transmission of the corresponding PDCP PDU was attempted via the SeNB are only performed if it is determined that PDCP transmissions are to be terminated within the MeNB.

[0023] If it is determined that PDCP transmissions are to be terminated within the SeNB then the method may further comprise: retransmitting of PDCP SDUs from the first PDCP SDU for which there is no confirmation of successful delivery of a corresponding FDCP PDU by a protocol layer below the PDCP layer within the UE; and retransmitting all PDCP SDUs from the first PDCP SDU.

[0024] The method may further comprise: detecting reconfiguration of a bearer from a non-split bearer to split bearer; and if reconfiguration of a bearer from a non-split bearer to a split bearer is detected: determining whether, before reconfiguration of the bearer from a split bearer to a non-split bearer, PDCP transmission were terminated within the MeNB or the SeNB; wherein if it is determined that PDCP transmissions were terminated within the MeNB then the method further comprises determining that no PDCP SDU retransmissions are required.

[0025] If it is determined that PDCP transmissions were terminated within the SeNB then the method further comprises: retransmitting PDCP SOUs from the first POOP SOU for which there is no confirmation of successful delivery of a corresponding PDCP POU by a protocol layer below the PDCP layer within the UE; and retransmitting all PDCP SDUs from the first PDCP SDU.

[0026] If reconfiguration of a bearer from a split bearer to a non-split bearer is detected, the method may further comprise: determining whether before reconfiguration POOP SOU transmissions from the UE were restricted to transmissions to just the MeNB or just the SeNB; wherein if it is determined whether POCP SDU transmissions from the UE were restricted to transmissions to just the MeNB then the method further comprises determining that no PDCP SDU retransmissions are required; and wherein if it is determined whether PDCP SOU transmissions from the UE were restricted to transmissions to just the MeNB then the method further comprises: retransmitting POCP SDUs from the first PDCP SDU for which there is no confirmation of successful delivery of a corresponding PDCP PDU by a protocol layer below the PDCP layer within the UE; and retransmitting all PDCP SOUs from the first POOP SDU.

[0027] According to a second aspect of the present invention there is provided a User Equipment, UE, in a Long Term Evolution, LTE, compliant mobile communications network, wherein the UE is arranged to: detect reconfiguration of a bearer from a split bearer in which uplink Packet Oata Convergence Protocol, POOP, Protocol Oata Units, POUs, are transmitted to both a Master eNB, MeNB, and to a Secondary eNB, SeNB, to non-split bearer in which uplink POOP POUs are transmitted only to the MeNB; if reconfiguration of a bearer from a split bearer to a non-split bearer is detected, initiate retransmission of POOP Service Oata Units, SOUs, from the first POOP SOU for which transmission of the corresponding POCP PDU was attempted via the SeNB and for which there has been no confirmation of successful delivery by a protocol layer below the POOP layer within the UE; and retransmit only PDCP SDU5 for which transmission of the corresponding POOP POU was attempted via the SeNB.

[0028] The UE may be further arranged to implement the above described method.

[0029] Another aspect of the invention provides a computer program comprising instructions arranged, when executed, to implement a method and/or apparatus in accordance with any one of the above-described aspects. A further aspect provides machine-readable storage storing such a program.

BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Embodiments of the invention are further described hereinafter with reference to the accompanying drawings, in which: (S Figure 1 schematically illustrates an overview of an LTE mobile communication network; Figure 2 illustrates a split bearer; Figure 3 illustrates a RAN protocol stack at a MeNb and a SeNB for the split bearer of Figure 2; Figure 4 illustrates a message flow during an X2 handover of a non-split bearer between a source eNB and a target eNB; Figure 5 illustrates the format of a PDCP status report; Figure 6 illustrates the delivery situation for a non-split radio bearer immediately before an X2 handover from a source eNB to a target eNB; Figure 7 illustrates PDCP SDU retransmissions for the delivery situation of Figure 6 upon the X2 handover, according to a first network option; Figure 8 illustrates PDCP SDU retransmissions for the delivery situation of Figure 6 upon the X2 handover, according to a second network option; Figure 9 illustrates the delivery situation for a split radio bearer immediately before reconfiguration to a non-split radio bearer; Figures 10 to 14 illustrates PDCP SDU retransmissions for the delivery situation of Figure 9 following reconfiguration to a non-split bearer, according to a first to fifth options; Figure 15 illustrates PDCP SDU retransmissions for the delivery situation of Figure 9 following reconfiguration to a non-split bearer, according to a first embodiment of the present invention; Figure 16 illustrates PDCP SDU retransmissions for the delivery situation of Figure 9 following reconfiguration to a non-split bearer, according to a second embodiment of the present invention; Figure 17 illustrates a message flow during reconfiguration of a bearer according an embodiment of the invention; and Figure 18 is a flowchart illustrating a method of reconfiguring a bearer according to an embodiment of the invention.

DETAILED DESCRIPTION

[0031] Embodiments of the invention will now be described in the context of an LTE compliant mobile wireless communications network operating in accordance with Release- 11 and beyond of the 3GPP LIE standards. However, it will be understood that this is by way of example only and that other embodiments may involve other wireless networks, operating at least partially in compliance with other releases and other standards.

[0032] Referring to Figure 4, this shows the message sequence chart for an X2 handover' from 3GPP TS 36.300 (Figure 10.1.2.1.1-1). Specifically, this shows an X2 handover of a UE in RRC_CONNECTED mode in which a non-split bearer is reconfigured such that it is terminated at a target eNB in place of a source eNB. At steps ito 3 the source eNB determines whether to handover. Steps 4 to 7 concern handover preparation during which the source eNB passes all necessary information to the target eNB for effecting the handover. Steps 8 to ii comprise handover execution. Steps 12 to 18 comprise handover execution. A more detailed explanation of Figure 4 is provided in section 10.1.2.1.1 of 3GPP TS 36.300, but is not needed for explanation of the present invention.

[0033] In the context of the present invention a first key step is the "Data Forwarding" over user data from the source eNB to the target eNB after step 8 (during handover execution). Importantly, it is at the discretion of the source eNB whether or not uplink PDCP SDUs that are received out of sequence are forwarded to the target eNB. As a first option, the source eNB may discard all such out of sequence PDCP SDUs and rely on the UE retransmitting all PDCP SDU's from the first non-delivered PDCP SDU to the target eNB. Alternatively, as a second option the source eNB may forward all such out of sequence PDCP SDU5 and ask the UE to only retransmit the missing PDCP SDU5 to the target eNB.

[0034] This behaviour is captured in 3GPP TS 36.300 section 10.1.2.3.1: Then the source eNB shall either: -discard the uplink PDCP SDUs received out of sequence if the source eNB has not accepted the request from the target eNB for up/ink forwarding or if the target eNB has not requested up/ink forwarding for the bearer during the Handover Preparation procedure, -forward to the target eNS the uplink PDCP SDUs received out of sequence if the source eNS has accepted the request from the target eNS for uplink forwarding for the bearer during the Handover Preparation procedure.

[0035] As further set out in 3GPP TS 36.300 section 10.1.2.3.1, the source eNB is further responsible for forwarding unacknowledged downlink PDCP SDUs to the target eNB, forwarding successively received uplink PDCP SDUs to the S-GW though this is outside of

the scope of the present specification.

[0036] This optional behaviour for handling out of sequence uplink PDCP SDUs has consequences for later steps in Figure 4. A second key step is the "packet data" delivery of user data between the UE and the target eNB after step 11. The UE retransmits all PDCP SDUs for which successful delivery of corresponding PDCP PDU has not been confirmed by lower layers as documented in 3GPP TS 36.323 "Evolved Universal Terrestrial Radio Access (E-UTRA)"; Packet Data Convergence Protocol (PDCP) specification (Release 11); vii.2.0 section 5.2.1.1: -from the f/rst PDCP SDU for which the successful delivery of the corresponding PDCP PDU has not been confirmed by lower layers, perform retransmission or transmission of all the PDCP SDUs already associated with PDCP SNs in ascending order of the COUNT values associated to the PDCP SDU prior to the PDCP re-establishment as spec/fled below: II partly omitted/I -submit the resulting PDCP Data PDU to lower layer.

[0037] If the source eNB is configured to the option of not forwarding out of sequence PDCP SDUs, then the retransmission by the UE of all PDCP SDUs from the first PDCP SDU for which there is not lower layer confirmation of successful delivery is fine and no further action is required.

[0038] If the source eNB is configured to forward out of sequence received PDCP SDUs to the target eNB, then the specifications allow the target eNB to inform the UE about the already received PDCP SDUs with a PDCP status report as described in 3GPP TS 36.323 section 6.2.& Figure 4 does not show a PDCP status report message, though this would be provided after the data forwarding following step 8 and before the packet data transmission following step 11. Figure 5 reproduces Figure 6.2.6.1 of 3GPP TS 36.323 and shows the format of a PDCP Control PDU carrying one PDCP status report when a 12 bit sequence number length is used. The field FMS identifies the first missing PDCP serial number. If there are received out of sequence PDCP SDUs then the bitmap field indicates missing PDCP SDUs from the first missing PDCP SDU. The bitmap field is of length in bits equal to the number of PDCP sequence numbers from, but not including the first missing PDCP SDU and up to and including the last received out of sequence PDCP SDU, rounded to the next multiple of 8 bits. For each position in the bitmap a zero indicates a PDCP SDU sequence number which is not reported to have been received by the lower layers. A one in the bitmap indicates a received PDCP SDU.

[0039] If the UE receives a PDCP status report, the UE may omit retransmissions of any PDCP SDU5 which have been received by the source eNB. This behaviour is documented in section 5.4 of 3GPP TS 36.323: When the discard Timer expires for a PDCP SDU, or the successful delivery of a PDCP SDU is confirmed by PDCP status report, the UE shall discard the PDCP SDU along with the corresponding PDCP PDU. If the corresponding PDCP PDU has already been submitted to lower layers the discard is indicated to lower layers. ii

[0040] The currently specified solution works fine for an X2 handover when moving a non-split bearer. To illustrate the conventional retransmission of PDCP SDUs from a UE to a target eNB during such a handover, both with and without forwarding by the source PDCP, reference is now made to Figures 6 to 8.

[0041] Figure 6 shows a possible delivery situation tor a non-split radio bearer just before an X2 handover. Figure 6 shows PDCP and RLC entities at both a UE and a source eNB (MAC entities are omitted for clarity). This split between the network and the UE is shown.

The UE PDCP entity shows six PDCP PDUs for transmission to the source eNB PDCP entities. In this example, PDCP PDU 1 is the last PDCP PDU delivered in sequence to the eNB PDCF entity. PDCP POUs 2 and 4 failed at during their first transmission at lower layers and will have to be retransmitted by the UE RLC entity. This is indicated by the arrows from those PDUs not reaching across the network line to the source eNB RLC entity. PDUs 3 and 5 have been delivered to the RLC entity at the eNB, but since the RLC entity only delivers PDCP PDU's in sequence to PDCP, these PDCP PDU's are still buffered at the source eNB RLC entity. Receipt of the PDU5 3 and 5 will have been acknowledged by the source eNB RLC entity to the UE RLC entity.

[0042] Figure 7 shows what happens after X2 handover to a target eNB if the network implements the first option in which the source eNB discards out of sequence SDUs. At handover the source eNB RLC entity delivers out of sequence delivered PDCP PDUs (PDU5 3 and 5) to the PDCP entity due to a re-establishment of the RLC entity in the source eNB. However, the source PDCP entity will discard these PDUs, indicated by PDUs 3 and 5 being crossed out. During handover completion the UE retransmits all PDUs from the first non-delivery-confirmed PDCP PDU (PDCP PDU 2 in this example).

Consequently, the UE must retransmit PDCP PDUs 2 to 6 (indicated by the arrows between the UE PDCP entity and the target eNB PDCP entity), even though PDUs 3 and 5 were successfully delivered to the network.

[0043] Figure 8 shows what happens after X2 handover to a target eNB if the network implements the second option in which the source eNB forwards out of sequence SDUs.

Again PDCP PDUs 3 and 5 are delivered to the source eNB PDCP entity due to a re-establishment of the RLC entity in the source eNB. However, this time PDCP PDUs 3 and are forwarded to the target eNB PDCP entity. Based on a PDCP status report as described above in connection with Figure 5, the UE knows that these PDCP PDUs do not longer have to be transmitted in the target eNB, thus saving resources in the UE and the target eNB. Consequently, the UE need only retransmit PDCP PDUs 2, 4 and 6 (indicated by the arrows between the UE PDCP entity and the target eNB PDCP entity).

[0044] To implement similar functionality during reconfiguration of a split bearer, the same techniques described above for an X2 handover of a non-split bearer may be reapplied. However, as will now be demonstrated, the result is a significant reduction in efficiency caused by retransmission of data unnecessarily. The following cases relate to the reconfiguration of a split bearer to a non-split bearer in which the PDCP entity within a MeNB remains following the reconfiguration and the PLC/MAC entities within a SeNB are removed.

[0045] Before illustrating specific examples, it is first clarified that it is assumed that also for a split bearer, PLC entities will in normal situations (other than for re-establishment) only deliver in sequence PDCF PDUs to the PDCP entity. However, since each PLC entity is only handling part of the PDCP PDUs, this do not necessarily need to be consecutive PDCP PDUs such that there could be gaps in the PDCP PDUs delivered by each PLC entity to a PDCP entity for a split bearer. At the PLC layer, in PLC Acknowledged Mode, for the uplink in the UE each PLC entity (one each for transmissions is to eNBi and eNB2) each PDCP PDU allocated for transmission to that eNB is numbered sequentially to form PLC PDUs, such that while there may be gaps in the numbering of FDCP PDUs sent to each eNB, there are no gaps for the PLC PDUs. At each eNB the PLC entity does not pass received PLC PDUs to the PDCP entity out of sequence.

[0046] Figure 9 shows a possible delivery situation for a split radio bearer just before reconfiguration from a split bearer to a non-split bearer. PDCP PDU 1 is the last in sequence PDCP PDU delivered via eNB1 PLC (the MeNB PLC entity) to the PDCP entity.

FDCP PDU 4 is the last in PDCP FDU delivered via eNB2 PLC (the SeNB PLC entity).

The UE is aware that PDCP PDUs 1 and 4 have successfully transmitted based on lower layer confirmation. Transmission was also successful for PDCP PDUs 3, 5, 7 and 8 to the eNB PLC entities but all these PDUs remain buffered in the receiving PLC entity due to out of sequence reception (that is, the received PLC PDUs are out of sequence). PDCP PDU5 2 and 6 still need to be retransmitted by the UE though these have not necessarily failed transmissions. Since transmissions in eNB2 are discontinued, PDCP PDU6 cannot be received by the network PDCP entity unless there is a new retransmission from the UF.

PDCP PDU2 will be delivered by the PLC/lower layers in eNB1 if these layers are not re-established.

[0047] The amount of unnecessary retransmissions resulting from the current UE behaviour will depend on the network behaviour, as will now be set out via several example cases. The description of the following cases is not exhaustive of all possible scenarios for current UE behaviour and current network behaviour. The following example cases vary according to whether the eNB1 PLC is re-established, whether there is forwarding from the enBl (SeNB) to the eNB2 (MeNB) and whether the PDCP entity sends a PDCP status report. If the eNB1 RLC is not re-established then on-going transmissions (PDUs 2, 3 and 5) will continue and eventually these PDCP PDUs will be delivered to the PDCP entity (unless of course they later fail and no acknowledgement of receipt is received by the UE before the normal acknowledgement timer expires, in which case they would be retransmitted conventionally).

[00481 Case la: No eNB1 RLC re-establishment: Noforwardinci ofoutofseciuence PDCP PDUs from eNB2 RLC: No PDCP status rer)ort [0049] The resulting UE retransmissions following reconfiguration from a split bearer to a non-split bearer is shown in figure 10.

[0050] With the current UE behaviour the UE will restart transmissions from PDCP PDU 2 (the first PDCP PDU for which there is no confirmation of receipt by the lower level layers) and only skip PDCP PDU 4. PDCP PDUs 2, 3 and 5 are unnecessarily retransmitted by the UE, and retransmission of PDCP SDU's 7 and 8 could have been avoided if eNB2 had forwarded out of sequence received PDUs.

[0051] Case ib: No eNB1 RLC re-establishment: Noforwardinci of out of sequence PDCP PDUs from eNB2 RLC; PDCP status reort [0052] This case differs from Case la only in the fact that the PDCP entity sends a PDCP status report during bearer reconfiguration. It is clear that in this case the PDCP status report will indicate that PDCP PDUs 1 and 4 do not need to be retransmitted. It is questionable what the PDCP status report would say for PDCP PDUs 2, 3 and 5. Since these PDCP PDUs are not received by the PDCP entity, it is probable that the only thing the PDCP entity can say is that these PDCP PDUs need to be retransmitted.

Consequently, the resulting UE retransmissions are identical to those shown in Figure 10.

[0053] With the current UE behaviour the UE will restart transmissions from PDCP PDU 2 and only skip PDCP PDU 4. PDCP PDUs 2, 3 and 5 are unnecessarily retransmitted by the UE, and retransmission of PDCP SDU's 7 and 8 could have been avoided if eNB2 had forwarded out of sequence received PDUs.

[0054] Case 2a: No eNB1 RLC re-establishment; Forwarding of out of sequence PDCP PDUs from eNB2 RLC; No PDCP status report [0055] This case differs from Case la only in that there is forwarding from eNB2 RLC.

The resulting UE retransmissions following reconfiguration from a split bearer to a non-split bearer is shown in Figure 11.

[0056] With the current UE behaviour the UE will restart transmissions from PDCP PDU 2 and only skip PDCP PDU 4. PDCP PDUs 2, 3, 5, 7 and 8 are unnecessarily ietransmitted by the UE.

[0057] Case 2b: No eNBl RLC rn-establishment; Forwarding of out of sequence PDCP PDUs from eNB2 RLC; PDCF status report [0058] This case differs from Case lb only in that there is forwarding from eNB2 RLC.

As for Case ib, it is probable that the PDCP status report will not indicate that PDCP PDUs 2, 3 and 5 have been received. However, differing from Case ib, the PDCP status report will indicate that PDCP PDUs 7 and 8 (in addition to PDCP PDUs 1 and 4) do not need to be retransmitted.

[0059] The resulting UE retransmissions following reconfiguration from a split bearer to a non-split beaiei is shown in Figure 12.

[0060] With the curient UE behaviour the UE will lestart transmissions from PDCP PDU 2 and only skip PDCP FDUs 4, 7 and 8. FDCP PDUs 2, 3 and 5 are unnecessarily retransmitted by the UE.

[0061] Case 3a: eNB1 RLC re-establishment; Forwarding of out of sequence PDCP PDUs from eNB2 RLC; No PDCP status reçort [0062] This case differs from Case 2a only in that the eNB1 RLC is re-established along with the corresponding UE RLC1 entity.

[0063] The resulting UE retransmissions following reconfiguration from a split bearer to a non-split beaiei is shown in Figure 12.

[0064] With the UE current behaviour the UE will restart transmissions from PDCP PDU 2 and only skip PDCP PDU 4. PDCP PDUs 3, 5, 7 and 8 are unnecessarily retransmitted by the UE. PDCP PDU2 may also be unnecessarily retransmitted depending on whether already some part of the PDCP PDU 2 was received in the eNB1 RLC.

[0065] Case 3b: eNB1 RLC re-establishment: Forwarding of out of sequence PDCP PDUs from eNB2 RLC; PDCP status report [0066] This case differs from Case 2a only in that the eNB1 RLC is re-established along with the corresponding UE RLC1 entity.

[0067] Due to the re-establishment of the eNB1 RLC entity, in this case PDCP PDUs 3 and 5, which weie buffered in the eNB1 RLC, will be delivered to the eNB PDCP entity.

Since PDCP PDUs 7 and 8 were also forwarded from the of the eNB2 RLC entity, and PDCP PDU5 1 and 4 were already delivered, the PDCP status report can indicated that PDCP PDU's 1, 3,4, 5,7 and 8 do not need to be retransmitted. The corresponding retransmission situation is shown in Figure 14.

[0068] With the current UE behaviour the UE will restart transmissions from PDCP PDU 2. Assuming that the PDCP status report is received in time, only the UE only retransmits PDCP PDUs 2 and 6. PDCP FDU2 may be unnecessarily retransmitted depending on whether already some part of the PDCP PDU 2 was received in the eNB1 RLC.

[0069] The unnecessary retransmission of PDCP PDUs for the above cases la to 3b is shown in Table 1 below: eN B RLC1 Forwarding PDCP Unnecessarily Comment re-establish from eNB2 status retransmitted report PDCP PDU ____ ___________ ___________ ___________ 2 3/3 4 6 7/8 ________________________ la No No(A) No x x x ______________ lb No No(A) Yes x x x _________________ No Yes(B) No x x x __________________ 2h No Yes (B) Yes x x _____ __________________________ 3a Yes Yes (B) No x x x PDCP PDU2 possibly _____________ _____________ _____________ _____ _____ unnecessarily retransmitted 3h Yes Yes (B) Yes x PDP PDU2 possibly ______________ ______________ ______________ ______ ______ unnecessarily retransmitted Table 1: Unnecessary retransmissions with currently specified UE behaviour.

[0070] As we can see from Table 1, although usage of a PDCP status report improves the situation, especially if combined with forwarding between eNB2 and eNB1 and re-establishing eNB1 RLC, in none of the cases are all unnecessary retransmissions are avoided. That is, according to currently specified UE and network behaviour, it is not possible to fully eliminate all possible inefficient use of UE and eNB resources.

[0071] In accordance with certain embodiments of the present invention, in the event of reconfiguring a split bearer to a non-split bearer, the UE retransmission behaviour is changed relative to the current 3GPP specified behaviour. In place of having the UE restart transmissions of all PDCP SDUs from the first PDCP SDU for which the successful delivery of the corresponding FDCF PDU has not been confirmed by lower layers, the UE: [0072] 1) Restarts transmissions for PDCP SDU5 from the first PDCP SDU for which transmission was attempted via the discontinued lower layer protocol stack part (at the SeNB) and for which the successful delivery of the corresponding PDCP PDU has not been confirmed by lower layers.

[0073] 2) Furthermore, the UE only retransmits PDCP SDUs for which transmission of the corresponding PDCP PDU was attempted! performed via the discontinued lower layer protocol stack part.

[0074] That is, in accordance with certain embodiments of the present invention, there is no retransmission of POOP SDUs for which a PDCP PDU has already been provided to the lower layer protocol stack part that is not discontinued (at the MeN B).

[0075] As a consequence, in accordance with certain embodiments of the piesent invention! even if the UE receives a PDCP status report in this case indicating that certain PDCP PDUs are missing, this does not trigger retransmissions of PDCP PDUs already sent via the MeNB. Should those PDCP PDUs truly be missing then normal retransmission is initiated following expiry of a retransmission timer.

[0076] To illustrate this embodiment of the present invention, two further example cases aie highlighted based upon the same delivery situation for a split iadio bearei just befoie ieconfiguration from a split bearer to a non-split bearer shown in Figure 9.

[0077] Case 4a: no eNB1 RLC re-establishment; No foiwardinci of out of sequence PDCP PDUs from eNB2 RLC; No PDCP status reQort [0078] The resulting UE retransmissions situation is shown in Figure 15.

[0079] Since the UE will not considei PDCF PDUs transmitted via eNB1 foi retransmission, retransmission for PDCP PDUs 2, 3 and 5 will not be triggered. Assuming that PDCP PDU 4 transmission was confirmed by lower layers of UE RLC2, the UE will only start retransmission from PDCP PDU6 and retransmit PDU5 6, 7 and 8.

[0080] If we compare this solution with Case la (as shown in Table 2 below), it can be seen that there is a clear reduction in the number of retransmitted FDCP PDUs.

cNB RLC1 Forwarding PDCP Unnecessarily Comment re-establish from eNB2 status retransmitted report PDCP PDU ___________ ___________ ___________ 2 3/5 4 6 7/8 ________________________ la No No(A) No x x x ___________________ 4a No No(A) No x ____________________ Table 2: First comparison of embodiment of the invention to cuiient UE behaviour.

[0081] Oase 4b: no eNB1 RLC re-establishment: Forwarding of out of sequence POOP PDUs from eNB2 RLC; PDCP status leport [0082] The resulting UE retransmissions situation is shown in figure 16.

[0083] Since the UE will not consider PDCP PDUs transmitted via eNB1 for retransmission, retransmission for PDCP PDUs 2, 3 and 5 will not be triggered. Since the PDCP status report confirms that PDCP PDUs 4, 7 and 8 no longer need to be retransmifted, in the end only PDCP PDU 6 will be retransmitted.

[0084] If we compare this solution with Case 2b (as shown in Table 3 below), it can be seen that again there is a clear reduction in the number of retransmitted PDCP PDUs.

eN B RLC1 Forwarding PDC[' Unnecessarily Comment re-establish from eNB2 status retransmitted report PDCP PDU ___________ ___________ ___________ 2 3/3 4 6 7/8 ________________________ 2b No Yes(B) Yes x x ___________________ 4±, No Yes (B) Yes ________________________ __________________________ Table 3: Second comparison of embodiment of the invention to current UE behaviour.

[0085] Advantageously! the embodiments of the present invention described above in connection with Case 4a and Case 4b are not reliant upon processing a PDCP status report to determine which PDCP PDUs to retransmit. A PDCP status report based approach might result in the UE having started certain PDCP PDU transmissions before receiving the PDCP status report (a race condition). If the UE has already started to retransmit unnecessary PDCF PDUs when the PDCP status report is received then this can result in a loss of efficiency.

[0086] Referring now to Figure 17, this shows an example full sequence message flow in accordance with certain embodiments of the present invention for deletion of the last cell in an SCG resulting also in the reconfiguration a split bearer to a non-split bearer. Figure 17 shows messages transferred between the UE, the MeNB, the SeNB and the CN. Prior to release of the last cell in the SCG, at least one radio bearer serving the UE is split between the MeNB and the SeNB as described above in connection with Figure 3.

[0087] At step 1 the MeNB obtains measurement information from the UE and I or status information from the SeN B. The measurement information or status information may be the trigger that causes the MeNB to decide to release the last cell in the SCG. There may be other triggers. Alternatively, the trigger may be some other status report. At step 2 the MeNB determines that release of the last cell in the SCG is required. The SeNB is instructed to release the last cell in the SCG at step 3 (the MeNB commands the SeNB to remove the SCG part of the bearer) and acknowledges this at step 4. Specifically, at step 4 the SeNB makes a new SeNB configuration to be sent to the UE and forwards this to the MeNB. At step 5a the SeNB forwards out of sequence uplink PDCP POUs (though it is noted that the present invention functions correctly as in Case 4a described above even if there is no forwarding). At step 5b the SeNB forwards undelivered downlink F'DCP PDU5 to the MeNB. The PDUs are buffered by the MeNB at step 6.

[0088] At step 7 the MeNB instructs the UE to release the last cell in the SCG. At step 7 the MeNB sends the new SeNB configuration to the UE. At step B the UE begins to reorder received downlink PDCP PDUs. At step 9, in accordance with certain embodiments of the present invention the UE determines which uplink PDCP PDUs to retransmit as described above in connection with Case 4a and Case 4b. That is, only PDCP PDUs transmitted to the discontinued eNB protocol stack (at the SeNB), and for which no lower layer acknowledgement of receipt has been received, will be retransmitted.

[0089] At step 10 the UE signals to the MeNB that the release of the last cell in the SCO is complete and at step 12a the UE sends a PDCP status report including a bitmap indicating received and missing downlink PDCP FDUs. At step 12b, in accordance with the 3GPP specifications, the MeNB sends a PDCP status report indicating what retransmissions to make including a bitmap indicating received and missing uplink PDCP PDUs. However, in accordance with certain embodiments of the present invention, this PDCP status report is partially ignored and does not trigger retransmission of PDCP POUs transmitted directly to the MeNB.

[0090] Steps 13, 14 and 15 relate to the release of radio resources by the SeNB. At step 13 the MeNB informs the SeNB about the UE response, and at step 14 the SeNB informs the MeNB that reconfiguration has been completed. At steps 16a and 16b the UE and the MeNB (which from now on may be simply referred to as the eNB) continue to operate in a "normal mode" in which a non-split bearer is used.

[0091] The modified retransmission behaviour of the UE described above in connection with certain embodiments of the invention could be captured within a modification to the relevant 3GPP specification (3GPP IS 36.323) as follows, with changes indicated by underlining.

5.2.1.1 Procedures for ORBs mapped on RLC AM When upper layers reguest a PDCP re-establishment due to reconfiguration of the radio bearer from a split bearer to a non-split bearer handled by the PCG. the UE shall: -from the first PDCP SDU transmitted via the SCG for which the successful deliver'' of the corresponding PDCP PDU has not been confirmed by lower layers, perform retransmission of all PDCP SDUs for which initial transmission was performed via the SCG, in ascending order of the COUNT values associated to the PDCP SDU prior to the PDCP re-establishment as specified below: -perform header compression ot the PDCP SOU (if configured') as specified in the subclause 5.5.4; -if connected as an RN, perform integrity protection (if configured) of the PDCP SDU using the COUNT value associated with this PDCP SDU as specified in the subclause 5.7: -ijerform ciphering of the PDCP SDU using the COUNT value associated with this PDCP SDU as specified in the subclause 5.6; -submit the resulting PDCP Data PDU to lower layer.

When upper layers request a PDCP re-establishment for other reasons, the UE shall: -reset the header compression protocol for uplink and start with an IR state in U-mode (if configured) [9] [11]; -if connected as an RN, apply the integrity protection algorithm and key provided by upper layers (if configured) during the re-establishment procedure; -apply the ciphering algorithm and key provided by upper layers during the re-establishment procedure; -from the first PDCP SDU for which the successful delivery of the corresponding FDCP PDU has not been confirmed by lower layers, perform retransmission or transmission of all the PDCP SDUs already associated with PDCP SNs in ascending order of the COUNT values associated to the PDCP SDU prior to the PDCP re-establishment as specified below: -perform header compression of the PDCP SDU (if configured) as specified in the subclause 5.5.4; -if connected as an RN, perform integrity protection (if configured) of the PDCP SDU using the COUNT value associated with this PDCP SDU as specified in the subclause 5.7; -perform ciphering of the PDCP SDU using the COUNT value associated with this PDCP SDU as specified in the subclause 5.6; -submit the resulting PDCP Data PDU to lower layer.

[0092] It is noted that in this revised section of 3GPP TS 36.323 references to header compression, integrity protection and ciphering are unchanged from the case for PDCP re-establishment for other reasons, except that the header compression entity might not need to be reset. PCG stands for "primary cell group" and corresponds to cells in the MeNB, and SCG stands for "secondary cell group" and corresponds to cells in the SeNB.

[0093] In accordance with certain embodiments of the invention consideration of how UE retransmission behaviour may be improved to increase efficiency is extended to considering a reconfiguration of an uplink non-split bearer to an uplink split bearer (the reverse situation to that described above).

[0094] Referring now Figure 18, this shows a flow chart illustrating retransmission behaviour at the UE. At step 181 the UE determines that reconfiguration of an uplink bearer termination is required. That is, the UE determines whether as a result of a re-establishment process retransmission of PDCP SDUs is required. At step 182 a determination is made whether the reconfiguration is from a split bearer to a non-split bearer. If it is determined that the reconfiguration is from a split bearer to a non-split bearer then at step 183 a determination is made where the uplink configuration is to be located after the reconfiguration to a non-split bearer. That is, it is determined where the PDCP entity is to be located at the network side after reconfiguration. Alternatively, step 183 may be viewed as determining for which eNB uplink PDU transmission is to be configured. As a further alternative, step 183 may be viewed as determining whether PDCP PDU transmission is to be allowed only in in the Macro Cell Group (MCG) or only in the Small Cell Group (SCG).

[0095] If at step 183 it is determined that the PDCP entity will reside in the MeNB after is reconfiguration then at step 184 the UE performs retransmission according to the embodiments of the present invention described above in connection with Case 4a and Case 4b. That is, only FDCP SDUs for which the corresponding PDCP FDUs were transmifted via the SeNB, and which have not been confirmed as delivered, are retransmitted.

[0096] If at step 183 it is determined that the PDCP entity will reside in the SeNB then at step 185 the UE performs retransmission according to the existing 3GPP specified behaviour (all PDCP SDUs are retransmitted if there has been no acknowledgement of delivery via lower layers).

[0097] Alternatively, if at step 182 it is determined that the reconfiguration is not from a split bearer to a non-split bearer then at step 186 a determination is made whether the reconfiguration is from a non-split bearer to a split bearer. If it is determined that the reconfiguration is not from a non-split bearer to a split bearer then the flow passes to step and the UE performs retransmission according to the existing 3GPP specified behaviour.

[0098] If at step 186 it is determined that the reconfiguration is from a non-split bearer to a split bearer then at step 187 a determination is made where the uplink configuration was located before the reconfiguration to a split bearer. That is, it is determined where the PDCP entity was located at the network side before reconfiguration. Alternatively, step 187 may be viewed as determining for which eNB uplink PDU transmission was previously located configured. As a further alternative, step 187 may be viewed as determining whether PDCP PDU transmission was previously only in in the Macro Cell Group (MCG) or only in the Small Cell Group (SCG).

[0099] If at step 187 it is determined that the PDCP entity previously resided in the SeNB then at step 185 the UE performs retransmission according to the existing 3GPP specified behaviour. Alternatively, if at step 187 it is determined that before reconfiguration the PDCP entity resided in the MeNB then at step 188 in accordance with certain embodiments of the invention no PDCP SDU retransmissions are required. This may include if the MeNB sends a PDCP status report indicating that certain corresponding PDCP PDUs have not been received.

[00100] Figure 18 illustrates the behaviour of the UE when a reconfiguration of a radio bearer is commanded between first and second configurations. The first configuration is where a radio bearer is configured with two bi-directional RLC entities (at a MeNB and a SeNB, and also duplicated at the UE). The second configuration is where a radio bearer is configured with one bi-directional RLC entity (at an eNB, and also duplicated at the UE).

While noting that bearers are bi-directional (and both "paths" are typically used in a split bearer for the downlink), for the uplink in a split bearer the UE could be restricted to only transmitting PDCP PDUs via a single "path" (to an RLC entity at only the MeNB or the SeNB). In such a situation then if PDCP PDUs have been transmitted only to the MeNB, upon reconfiguring the bearer from the first configuration to the second configuration then in accordance with certain embodiments of the present invention no PDCP retransmissions may be required. Specifically, when bearer reconfiguration is commanded, the UE checks if reconfiguration of a bearer is from configuration 1 (split) to configuration 2 (non-split). If so, the UE checks whether in configuration 1 PDCP PDU transmission was allowed only to the SeNB (or only on SCG serving cells) or only to the MeNB. If PDCP PDU transmission was allowed only to the SeNB (only via SCG serving cells) then PDCP SDU retransmissions need to be performed in accordance with the current 3GPP standards, that is according to step 185. If, however, PDCP PDU transmission was allowed only to the MeNB then no retransmission is required, that is according to step 188. However, for simplicity, this UE behaviour is not included in Figure 18, and it is assumed in Figure 18 that when in the first configuration (split bearer) PDCP PDUs are transmitted via both paths.

[00101] Certain embodiments of the present invention described above are based upon modifications only to the way in which the UE responds to a bearer reconfiguration, and in particular how the UE determines which PDCP SDUs to retransmit to maximise resource efficiency. However, two further options in accordance with further embodiments of the invention for increasing resource efficiency during reconfiguration from a split bearer to a non-split bearer are now presented.

[00102] As a first option, and as described above in connection with Case 3b, the eNB1 RLC entity may be re-established when removing the eNB2 protocol stack part and a PDCP status report may be sent from eNB1 to the UE. If the network re-establishes the eNB1 PLC entity when deleting the protocol stack part in eNB2, out of sequence PDCP PDUs will be delivered to the PDPC entity which will improve the contents of the PDCP status report (no longer asking retransmission of PDCP PDUs 3 and 5 unnecessarily in the example of Case 3b). The UE behaviour may be that currently specified in the 3GPP standards, with the improvements in resource efficiency arising through appropriate configuration of the eNB1 behaviour. As discussed above in connection with Case 3b, partly received PDCP PDUs (for instance PDCP PDU 2) will be dropped by the RLC entity in eNB1, which may cause them to be at least partly unnecessarily retransmitted.

[00103] As a second option, rather than re-establishing the RLC entity in eNB1, the eNB1 PLC entity informs the PDCP entity about the reception status or PDCP PDUs. Again, this results in a more accurate PDCP status report. In accordance with the second option the transmission of PDCP PDU 2 to the eNB1 will continue, and PDCP PDU 2 will be retransmitted. It is noted that the second option requires modification to the 3GPP standards concerning the behaviour of the eNB PLC upon a change in a PDCP termination.

[00104] It will be appreciated that embodiments of the present invention can be realized in the form of hardware, software or a combination of hardware and software. Any such software may be stored in the form of volatile or non-volatile storage, for example, a storage device like a ROM, whether erasable or rewritable or not, or in the form of memory, for example, RAM, memory chips, device or integrated circuits or on an optically or magnetically readable medium, for example, a CD, DVD, magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are embodiments of machine-readable storage that are suitable for storing a program or programs comprising instructions that, when executed, implement embodiments of the present invention. Accordingly, embodiments provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a machine-readable storage storing such a program. Still further, such programs may be conveyed electronically via any medium including a communication signal carried over a wired orwireless connection and embodiments suitably encompass the same.

[00105] Throughout the description and claims of this specification, the words comprise" and "contain" and variations of them mean "including but not limited to", and they are not intended to (and do not) exclude other components, integers or steps. Throughout the description and claims of this specification, the singular encompasses the plural unless the context otherwise requires. In particular, where the indefinite article is used, the specification is to be understood as contemplating plurality as well as singularity, unless the context requires otherwise.

[00106] Features, integers or characteristics described in conjunction with a particular aspect, embodiment or example of the invention are to be understood to be applicable to any other aspect, embodiment or example described herein unless incompatible therewith.

All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and/or all of the steps of any method or process so disclosed, may be combined in any combination, except combinations where at least some of such features and/or steps are mutually exclusive. The invention is not restricted to the details of any foregoing embodiments. The invention extends to any novel one, or any novel combination, of the features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel one, or any novel combination, of the steps of any method or process so disclosed. It will be also be appreciated that, throughout the description and claims of this specification, language in the general form of "X for Y" (where Y is some action, activity or step and X is some means for carrying out that action, activity or step) encompasses means X adapted or arranged specifically, but not exclusively, to do Y. [00107] The reader's attention is directed to all papers and documents which are filed concurrently with or previous to this specification in connection with this application and which are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference...

[00108] The above embodiments are to be understood as illustrative examples of the invention. Further embodiments of the invention are envisaged. It is to be understood that any feature described in relation to any one embodiment may be used alone, or in combination with other features described, and may also be used in combination with one or more features of any other of the embodiments, or any combination of any other of the embodiments. Furthermore, equivalents and modifications not described above may also be employed without departing from the scope of the invention, which is defined in the accompanying claims.

Claims (13)

1. CLAIMS: 1. A data transmission method of a User Equipment, UE, in a Long Term Evolution, LTE, compliant mobile communications network, the method comprising: detecting reconfiguration of a bearer from a split bearer in which uplink Packet Data Convergence Protocol, PDCP, Protocol Data Units, PDUs, are transmitted to both a Master eNB, MeNB, and to a Secondary eNB, SeNB, to non-split bearer in which uplink PDCP PDUs are transmitted only to the MeNB; and if reconfiguration of a bearer from a split bearer to a non-split bearer is detected: initiating retransmission of PDCP Service Data Units, SDU5, from the first PDCP SDU for which transmission of the corresponding PDCP PDU was attempted via the SeNB and for which there has been no confirmation of successful delivery by a protocol layer below the PDCP layer within the UE; and retransmitting only PDCP SDUs for which transmission of the corresponding PDCP PDU was attempted via the SeNB.
2. 2. The method of claim 1, wherein the retransmission of PDCP SDU5 is in ascending order of count values assigned to the PDCP SDUs prior to the reconfiguration of the bearer.
3. 3. The method of claim 1 or claim 2, further comprising: receiving a PDCP status report from the MeNB; and determining that FDCP SDUs that are indicated in the FDCF status report as received need not be retransmitted.
4. 4. The method of any one of the preceding claims, wherein the UE is configured to use only bearers for which successful delivery of PDCP PDUs is acknowledged by the eNB at a protocol layer below the PDCP layer.
5. 5. The method of claim 4, wherein the UE is configured to use only bearers using Radio Link Control Acknowledged Mode, RLC-Acknowledged Mode.
6. 6. The method of any one of the preceding claims, wherein successful delivery of a PDCP PDU is confirmed by the Radio Link Control, RLC, layer or the Medium Access Control, MAC, layer.
7. 7. The method of any one of the preceding claims, further comprising: determining whether, following reconfiguration of the bearer from a split bearer to a non-split bearer, PDOP transmissions are to be terminated within the MeNB or the SeN B; wherein the steps of initiating retransmission of PDCP SDUs from the first PDCP SDU for which transmission of the corresponding PDCP PDU was attempted via the SeNB and for which there has been no confirmation of successful delivery by a protocol layer below the PDCP layer within the UE, and retransmitting only PDCP SDUs for which transmission of the corresponding POOP PDU was attempted via the SeNB are only performed if it is determined that PDCP transmissions are to be terminated within the MeNB.
8. 8. The method of claim 7, wherein if it is determined that PDCF transmissions are to be terminated within the SeNB then the method further comprises: retransmitting of PDCP SDUs from the first PDCP SDU for which there is no confirmation of successful delivery of a corresponding PDCP PDU by a protocol layer below the POOP layer within the UE; and retransmitting all PDCP SDU5 from the first POOP SDU.
9. 9. The method of any one of the preceding claims, further comprising: detecting reconfiguration of a bearer from a non-split bearer to split bearer; and if reconfiguration of a bearer from a non-split bearer to a split bearer is detected: determining whether, before reconfiguration of the bearer from a split bearer to a non-split bearer, PDCP transmission were terminated within the MeNB or the SeNB; wherein if it is determined that PDCP transmissions were terminated within the MeNB then the method further comprises determining that no PDCP SDU retransmissions are required.
10. 10. The method of claim 9, wherein if it is determined that PDCP transmissions were terminated within the SeNB then the method further comprises: retransmitting PDCP SOUs from the first POOP SDU for which there is no confirmation of successful delivery of a corresponding PDCP PDU by a protocol layer below the PDCP layer within the UE; and retransmitting all POOP SOUs from the first POOP SOU.
11. 11. The method of any one of the preceding claims, wherein if reconfiguration of a bearer from a split bearer to a non-split bearer is detected, the method further comprises: determining whether before reconfiguration PDCP SDU transmissions from the UE were restricted to transmissions to just the MeNB or just the SeNB; wherein if it is determined whether POOP SOU transmissions from the UE were restricted to transmissions to just the MeNB then the method further comprises determining that no PDCP SDU retransmissions are required; and wherein if it is determined whether POOP SOU transmissions from the UE were restricted to transmissions to just the MeNB then the method further comprises: retransmitting PDCP SOUs from the first PDCP SDU for which there is no confirmation of successful delivery of a corresponding PDCP PDU by a protocol layer below the PDCP layerwithin the UE; and retransmitting all POOP SOUs from the first POOP SDU.
12. 12. A User Equipment, UE, in a Long Term Evolution, LTE, compliant mobile communications network, wherein the UE is arranged to: detect reconfiguration of a bearer from a split bearer in which uplink Packet Oata Convergence Protocol, POOP, Protocol Data Units, PDUs, are transmitted to both a Master eNB, MeNB, and to a Secondary eNB, SeNB, to non-split bearer in which uplink POOP POUs are transmitted only to the MeNB; if reconfiguration of a bearer from a split bearer to a non-split bearer is detected, initiate retransmission of POOP Service Data Units, SOUs, from the first PDCP SDU for which transmission of the corresponding POOP PDU was attempted via the SeNB and for which there has been no confirmation of successful delivery by a protocol layer below the PDCP layer within the UE; and retransmit only POOP SDUs for which transmission of the corresponding POOP POU was attempted via the SeNB.
13. 13. A UE according to claim 12, wherein the UE is further arranged to implement the method of any one of claims 2 to 11.AMENDMENTS TO THE CLAIMS HAVE BEEN FtLED AS FOLLOWS:- 1. A data transmission method of a User Equipment, UE, in a Long Term Evolution, LTE, compliant mobile communications network, the method comprising: detecting reconfiguration of a bearer from a split bearer in which uplink Packet Data Convergence Protocol, PDCP, Protocol Data Units, PDUs, are transmitted to both a Master eNB, MeNB, and to a Secondary eNB, SeNB, to a non-split bearer in which uplink PDCP PDUs are transmitted only to the MeNB; and if reconfiguration of a bearer from a split bearer to a non-split bearer in which uplink PDCP PDU5 are transmitted to the MeNB is detected: initiating retransmission of PDCP Service Data Units, SDUs, from the first PDCP SDU for which transmission of the corresponding PDCP PDU was attempted via the SeNB and for which there has been no confirmation of successful delivery by a protocol layer below the PDCP layer within the UE; and retransmitting only PDCP SDUs for which transmission of the corresponding PDCP PDU was attempted via the SeN B. 2. The method of claim 1, wherein the retransmission of PDCP SDUs is in (0 ascending order of count values assigned to the PDCP SDUs prior to the reconfiguration of the bearer.CC\i 3. The method of claim 1 or claim 2, further comprising: receiving a PDCP status report from the MeNB; and determining that PDCF SDUs that are indicated in the PDCP status report as received need not be retransmitted.4. The method of any one of the preceding claims, wherein the UE is configured to use only bearers for which successful delivery of PDCP PDUs is acknowledged by the eNB at a protocol layer below the PDCP layer.5. The method of claim 4, wherein the UE is configured to use only bearers using Radio Link Control Acknowledged Mode, RLC-Acknowledged Mode.6. The method of any one of the preceding claims, wherein successful delivery of a PDCP PDU is confirmed by the Radio Link Control, RLC, layer or the Medium Access Control, MAC, layer.7. The method of any one of the preceding claims, further comprising: detecting reconfiguration of a bearer from a split bearer in which uplink Packet Data Convergence Protocol, PDCP, Protocol Data Units, PDUs, are transmitted to both a Master eNB, MeNB, and to a Secondary eNB, SeNB, to a non-split bearer in which uplink PDCP PDU5 are transmitted to the SeNB; and if reconfiguration of a bearer from a split bearer to a non-split bearer in which uplink PDCP PDUs are transmitted only to the SeNB is detected: initiating retransmission of PDCF SDUs from the first FDCF SDU for which there is no confirmation of successful delivery of a corresponding PDCP PDU by a protocol layer below the PDCP layer within the UE; and retransmitting all PDCP SDUs from the first PDCP SDU.8. The method of any one of the preceding claims, further comprising: detecting reconfiguration of a bearer from a non-split bearer to split bearer; and if reconfiguration of a bearer from a non-split bearer to a split bearer is detected: determining whether, before reconfiguration of the bearer from a split bearer to a non-split bearer, PDCP transmission were terminated within the MeNB or the ct SeNB; wherein if it is determined that PDCP transmissions were terminated within the MeNB then the method further comprises determining that no PDCP SDU retransmissions are required.CC\J 9. The method of claim 8, wherein if it is determined that PDCP transmissions were terminated within the SeNB then the method further comprises: initiating retransmission of PDCF SDUs from the first FDCF SDU for which there is no confirmation of successful delivery of a corresponding PDCP PDU by a protocol layer below the PDCP layer within the UE; and retransmitting all PDCP SDU5 from the first PDCP SDU.10. The method of any one of the preceding claims, further comprising: detecting reconfiguration of a bearer from a split bearer in which uplink PDCP PDUs are transmitted to only one of a MeNB and a SeNB to a non-split bearer in which uplink PDCP PDU5 are transmitted to the MeNB; determining whether before reconfiguration PDCP PDU transmissions from the UE were restricted to transmissions to just the MeNB or just the SeNB; wherein if it is determined that PDCP PDU transmissions from the UE were restricted to transmissions to just the MeNB then the method further comprises determining that no PDCP SDU retransmissions are required; and wherein if it is determined that PDCP PDU transmissions from the UE were restricted to transmissions to just the SeNB then the method further comprises: initiating retransmission of PDCP SDUs from the first PDCP SDU for which there is no confirmation of successful delivery of a corresponding PDCP PDU by a protocol layer below the PDCP layer within the UE; and retransmitting all PDCP SDUs from the first PDCP SDU.11. A User Equipment, UE, in a Long Term Evolution, LTE, compliant mobile communications network, wherein the UE is arranged to: detect reconfiguration of a bearer from a split bearer in which uplink Packet Data Convergence Protocol, PDCP, Protocol Data Units, PDU5, are transmitted to both a Master eNB, MeNB, and to a Secondary eNB, SeNB, to a non-split bearer in which uplink PDCP PDU5 are transmitted only to the MeNB; if reconfiguration of a bearer from a split bearer to a non-split bearer in which uplink PDCP PDU5 are transmitted to the MeNB is detected, initiate retransmission of PDCP Service Data Units, SDUs, from the first PDCP SDU for which transmission of the corresponding PDCP PDU was attempted via the SeNB and for which there has been no confirmation of successful delivery by a protocol layer below the PDCP layer within the UE; and retransmit only PDCP SDUs for which transmission of the corresponding PDCP 0 PDU was attempted via the SeN B. 12. A UE according to claim 12, wherein the UE is further arranged to implement the method of any one of claims 2 to 10.