SIGNALING IN DUAL CONNECTIVITY MOBILE COMMUNICATION NETWORKS

Abstract

There is disclosed a method of a User Equipment, UE, in a 3rd Generation Partnership Project, 3GPP, compliant mobile communications network supporting dual connectivity, and a corresponding UE. The method comprises detecting a signalled reconfiguration procedure of a Data Radio Bearer, DRB, having or changing to a DRB type in which downlink, DL, data is received from only serving cells of a Secondary Cell Group, SCG, connected to a Secondary eNB, SeNB, via an SCG DRB, or in which DL data is received from a SCG and also from serving cells of a Master Cell Group, MCG, connected to a Master eNB, MeNB, via a split DRB. If a DRB reconfiguration procedure type including one or more of: a handover; an SCG change; and DRB type change; is detected, the method further comprises: deciding one or more required layer 2 DRB-related actions resulting from the DRB reconfiguration based on: the initial DRB configuration; the final DRB configuration; and relevant DRB reconfiguration procedure types; and performing said decided layer 2 DRB-related actions.

Claims

1. A method for controlling a bearer by a first base station, the method comprising: transmitting, to a second base station, a first message to modify the bearer; receiving, from the second base station, a second message including first information associated with the bearer for the second base station; generating configuration information including the first information and second information; and transmitting the configuration information to a terminal.

2. The method of claim 1, wherein the first information includes at least one parameter to modify a data radio bearer for the second base station, and wherein the second information includes at least one parameter used to generate a security key.

3. (canceled)

4. The method of claim 1, wherein the configuration information includes information changed compared to current bearer information.

5. A method for controlling a bearer by a second base station, the method comprising: receiving, from a first base station, a first message to modify the bearer; and transmitting, to the first base station, a second message including first information associated with the bearer for the second base station, wherein configuration information including the first information and second information is transmitted by the first base station to the terminal.

6. The method of claim 5, wherein the first information includes at least one parameter to modify a data radio bearer for the second base station, and wherein the second information includes at least one parameter used to generate a security key.

7. (canceled)

8. The method of claim 5, wherein the configuration information includes information changed compared to current bearer information.

9. A method for controlling a bearer by a terminal, the method comprising: receiving, from a first base station, configuration information including first information associated with the bearer for a second base station and second information; and modifying information associated with the bearer based on the configuration information, wherein the first information is transmitted from the second base station to the first base station.

10. The method of claim 9, wherein the first information includes at least one parameter to modify a data radio bearer for the second base station, and wherein the second information includes at least one parameter used to generate a security key.

11. (canceled)

12. The method of claim 9, wherein the configuration information includes information changed compared to current bearer information.

13. A first base station for controlling a bearer, the first base station comprising: a transceiver for receiving and transmitting signal; and a controller configured to: transmit, to a second base station, a first message to modify the bearer, receive, from the second base station, a second message including first information associated with the bearer for the second base station, generate configuration information including the first information and second information, and transmit the configuration information to a terminal.

14. The first base station of claim 13, wherein the first information includes at least one parameter to modify a data radio bearer for the second base station, and wherein the second information includes at least one parameter used to generate a security key.

15. (canceled)

16. The first base station of claim 13, wherein the configuration information includes information changed compared to current bearer information.

17. A second base station for controlling a bearer, the second base station comprising: a transceiver for receiving and transmitting a signal; and a controller configured to: receive, from a first base station, a first message to modify the bearer, and transmit, to the first base station, a second message including first information associated with the bearer for the second base station, wherein configuration information including the first information and second information is transmitted by the first base station to the terminal.

18. The first base station of claim 17, wherein the first information includes at least one parameter to modify a data radio bearer for the second base station, and wherein the second information includes at least one parameter used to generate a security key.

19. The first base station of claim 17, wherein the second information includes at least one parameter used to generate security key.

20. The first base station of claim 17, wherein the configuration information includes information changed compared to current bearer information.

21. A terminal for controlling a bearer by a terminal, the terminal comprising: a transceiver for receiving and transmitting a signal; and a controller configured to: receive, from a first base station, configuration information including first information associated with the bearer for a second base station and second information, and modify information associated with the bearer based on the configuration information, wherein the first information is transmitted from the second base station to the first base station.

22. The terminal of claim 21, wherein the first information includes at least one parameter to modify a data radio bearer for the second base station.

23. The terminal of claim 21, wherein the second information includes at least one parameter used to generate security key.

24. The terminal of claim 21, wherein the configuration information includes information changed compared to current bearer information.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0129] Embodiments of the invention are further described hereinafter with reference to the accompanying drawings, in which:

[0130] FIG. 1 schematically illustrates an overview of an LTE mobile communication network;

[0131] FIG. 2 illustrates inter-node radio resource allocation in dual connectivity;

[0132] FIG. 3A illustrates a supported arrangement of a bearer for splitting user plane downlink data at the CN;

[0133] FIG. 3B illustrates another supported arrangement of a split bearer for splitting user plane downlink data at the RAN;

[0134] FIG. 4 illustrates a control plane architecture for dual connectivity;

[0135] FIG. 5A illustrates a RAN protocol stack at a MeNB and a SeNB for the split bearer of FIG. 3A;

[0136] FIG. 5B illustrates a RAN protocol stack at a MeNB and a SeNB for the split bearer of FIG. 3B;

[0137] FIG. 6 shows a block diagram illustrating selected components of a UE foe use in a wireless communication network as shown in FIGS. 1 and 2;

[0138] FIG. 7 is a flowchart illustrating a method of a UE for taking action on DRB reconfiguration and/or DRB type change in DC;

[0139] FIG. 8 is a message sequence chart showing an SeNB change procedure implementing delta signalling;

[0140] FIG. 9 is a flowchart illustrating a method of a UE for supporting delta signalling on SCG change and DRB type change;

[0141] FIG. 10 is a flowchart illustrating a method of an eNB;

MODE FOR THE INVENTION

[0142] Embodiments of the invention will now be described in the context of an LTE compliant mobile wireless communications network operating in accordance with the 3GPP LTE standards up to Release-12 and beyond. 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.

[0143] FIG. 6 shows a block diagram illustrating some example components comprised in an example UE 600 that can be used in the LTE-enabled wireless network as shown in FIG. 1. The UE 600 may be a wireless device and its associated Universal Integrated Circuit Card (UICC) that includes a Subscriber Identity Module (SIM) application, a Universal Subscriber Identity Module (USIM) application, or a Removable User Identity Module (R-UIM) application or the UE 600 might be the device itself without such a card.

[0144] UE 600 includes multiple components linked by a communications bus 601. A processor 602 controls the overall operation of the UE 600. Communication functions, including data and voice communications, are performed through a communication subsystem 604. The communication subsystem 604 may take the form of modems, modem banks, Ethernet devices, universal serial bus (USB) interface devices, serial interfaces, token ring devices, fiber distributed data interface (FDDI) devices, wireless local area network (WLAN) devices, radio transceiver devices such as code division multiple access (CDMA) devices, global system for mobile communications (GSM) radio transceiver devices, worldwide interoperability for microwave access (WiMAX) devices, and/or other well-known devices for connecting to networks. The communication subsystem 604 may enable the processor 602 to communicate with the Internet or one or more telecommunications networks or other networks from which the processor 602 might receive information or to which the processor 602 might output information.

[0145] In the context of FIG. 1, the communication subsystem 604 receives messages from and sends messages to wireless network 606 which may be the E-UTRAN 104 shown in FIG. 1 for voice communications or data communications or both.

[0146] A power source 608, such as one or more rechargeable batteries or a port to an external power supply, powers the UE 600.

[0147] The processor 602 interacts with other components of the electronic device including Random Access Memory (RAM) 610, mass storage 612 (including but not limited to magnetic and optical disks, magnetic tape, solid state drives or RAID arrays), Read Only Memory (ROM) 614 and display screen 616, which may be, for example, a Liquid Crystal Display (LCD). An i/o controller 618 sends and receives signals relative to one or more user control devices, such as a touch sensitive overlay on the display screen 616 to enable user interaction with the UE 600.

[0148] The processor 602 executes instructions, code, software or computer programs it may access from communications subsystem 604, RAM 610, mass storage 612 or ROM 614. The processor 602 may comprise one or more data processing units or CPU chips. The processor 602 may execute the instructions solely by itself, or in concert with other locally or remotely provided data processing components or other components not shown in FIG. 6. In particular, the processor 602 is capable of carrying out instructions such that the UE 600 is operable to perform wireless communications in an LTE network in accordance with the disclosure set out below.

[0149] For example, the processor 602 may carry out instructions to instantiate and maintain a communications manager in RAM 610 that in use operates the communications subsystem 604 to perform signalling to interact with E-UTRAN 104.

[0150] The communications manager may instantiate, for example in the RAM 610 of UE 600, an LTE protocol stack to provide as described above in relation to FIGS. 5A and 5B, at the Access Stratum layers of LTE, one or more of a Radio Resource Control (RRC) signalling layer that is typically responsible for the control of radio related functions, a Packet Data Convergence Control (PDCP) signalling layer that is typically responsible for header compression and security, a Radio Link Control (RLC) signalling layer that is typically responsible for the retransmission of lost data, a Medium Access Control (MAC) signalling layer that is typically responsible for controlling access to the Physical Layer (PHY). Of course, layers of the protocol stack may be implemented elsewhere, for example the MAC and PHY signalling may be provided in the UE by firmware or hardware and so not maintained in RAM 610. Indeed, the implementation of the protocol stack in the RAM 610 UE described above is only one example of many possibilities within the scope of the present disclosure, and is provided for explanatory purposes only.

[0151] As mentioned above, the LTE system includes protocols such as a Radio Resource Control (RRC) protocol, which is responsible for the assignment, configuration and release of connections and radio resources between the UE 102 and the eNBs of the E-UTRAN 104 or other access or LTE equipment. These protocols will have to define signalling and operations at the UE, the MeNB of the MCG and the SeNB of the SCG in order to govern how these components of the wireless communications network operate and interact to support dual connectivity.

[0152] In order to reduce unnecessary repetition of UE actions on reconfiguration of the DRB and/or on DRB type change, the present application provides a method in which a UE determines layer 2 actions to be taken based on the target DRB type and configuration, rather than on individual fields of the signalled reconfiguration. This will now be described in more detail with reference to FIG. 7.

[0153] According to the LTE standard, the UE modifies the radio configuration (including the layer 2 user plane configuration comprising one main MAC configuration and a logical channels, RLC and PDCP configuration per radio bearer) either:

[0154] a. Upon receiving (from the MeNB) a reconfiguration message including configuration parameters

[0155] b. Upon receiving a message triggering a specific action e.g. upon handover, the UE first resets MAC, re-establishes PDCP and RLC for every DRB that is established

[0156] c. Upon occurrence of a specific event e.g. when the UE initiates connection re-establishment, it releases the Secondary Cells (SCells)

[0157] The configuration parameters that are signalled to the UE by the MeNB, can either concern [0158] Delta signalling: Changes compared to the configuration/the configuration at the time the signalled parameters are processed (i.e. before the UE processes the configuration parameters received, the UE may trigger actions resulting in a change of the configuration e.g. upon handover). As will be understood from the description below, currently delta signalling is supported in LTE on normal reconfiguration and on handover. [0159] Full signalling: the entire configuration the UE shall apply, irrespective of the current configuration

[0160] For Dual Connectivity, it has been agreed through 3GPP working group discussions that: [0161] An SCG change procedure is to be specified i.e. a reconfiguration message including release of the current SCG as well as the addition of an SCG. The newly added SCG may include cells that were present of the former SCG, in which case the new SCG is handled by the same SeNB [0162] Upon handover, the SCG is either released or, if the MeNB wants to continue DC, it can perform an SCG change as part of the handover [0163] No constraints were agreed regarding the SCG change procedure e.g. that it or some specific cases can only be done in combination with handover [0164] In case of a change of DRB type from a split DRB to MCG DRB, the MCG-RLC is not re-established i.e. the UE merely releases SCG-RLC

[0165] A proposal submitted to the 3GPP working group on small cell enhancements as document R2-141940 largely covers the PDCP operation in DC to be performed in cases involving: change of DRB type, SCG addition/change/release, reconfiguration of UL path of split DRB. In summary the paper indicates that:

[0166] a. Upon change of an MCG DRB to a split DRB, there is no need for any specific PDCP actions other than configuring the UL data path (i.e. which CG the UE shall apply for UL data)

[0167] b. Upon move of the PDCP entity between MeNB and SeNB, the UE performs a PDCP re-establishment alike upon HO without DC

[0168] c. Upon SCG change, the UE performs a PDCP re-establishment for SCG DRBs alike upon HO without DC

[0169] d. Upon change of a split DRB to an MCG DRB, the UE performs a partial PDCP re-establishment (merely of the SCG part)

[0170] e. Upon SCG change, the UE performs a partial PDCP re-establishment for split DRBs

[0171] The above list shows that there are multiple triggers for a (partial) PDCP re-establishment. Moreover, a single reconfiguration message received by the UE may result in multiple triggers e.g: [0172] If a reconfiguration message including SCG change is also used to change DRB type of an SCG DRB to an MCG DRB e.g. because the target SeNB is somewhat loaded, the UE detects both trigger (b) and (c) for the concerned SCG DRB [0173] If a reconfiguration message including SCG change is also used to change DRB type of a split DRB to an MCG DRB (for similar reasons), the UE detects both trigger (d) and (e) for the concerned split DRB [0174] A handover message including SCR release may also include change of DRB type of an SCG DRB to an MCG DRB (or it might be performed autonomously by the UE, as in B.7), the UE may again detect multiple triggers for PDCP re-establishment

[0175] As indicated in the previous, SCG change is assumed to be signaled by release of the current SCG and addition of a possibly different SCG. In such cases, on the basis of the current specification, the UE would normally first take action based on a field indicating release of the SCG and subsequently take action based on another field indicating addition of a new SCG.

[0176] It is undesirable if a single reconfiguration message would result in the UE to trigger, for example, PDCP re-establishment more than once as it could even result in the UE transmitting multiple PDCP status reports. It might even be so that a reconfiguration message includes a first reconfiguration that alone would trigger a certain action, but in combination with another reconfiguration should result in no or a different action.

[0177] To avoid unnecessary repetition by the UE of certain actions, which would lead to increased signaling and decreased performance, in accordance with the present disclosure the UE should be configured to not take action immediately upon detecting an individual trigger, but should instead take into account the complete initial and the complete final configuration, as well as any relevant reconfiguration procedure types of the DRB.

[0178] Thus, referring to FIG. 7, which shows a flowchart illustrating a method of a UE for taking action on DRB reconfiguration and/or DRB type change in DC, the UE is configured at step 701 to detect a signalled reconfiguration procedure of a DRB having or changing to a SCG DRB or an split DRB type. That is, the DRB type change or DRB reconfiguration is to change from or to a DRB in which downlink, DL, data is received from only serving cells of a Secondary Cell Group, SCG, connected to a Secondary eNB, SeNB, via an SCG DRB, or in which DL data is received from a SCG and also from serving cells of a Master Cell Group, MCG, connected to a Master eNB, MeNB, via a split DRB. At step 702, the UE determines if a DRB reconfiguration procedure type including one or more of: a handover; an SCG change; and DRB type change; is detected. If the answer at the decision point in step 702 is yes, then at step 703 the UE decides one or more required layer 2 DRB-related actions resulting from the DRB reconfiguration based on: the initial DRB configuration; the final DRB configuration; and relevant DRB reconfiguration procedure types. At step 704, the UE then performing said decided layer 2 DRB-related actions.

[0179] If the answer at the decision point in step 702 is no, then at step 705 the UE continues as per the current specification. I.e. the reconfiguration may include other configuration changes that the UE still needs to perform as per the current specification. FIG. 7 focuses on the additional layer 2 DRB-related actions upon DRB type reconfiguration as well as handover and/or SCG establishment/change/release.

[0180] It is noted that more generally, the present application provides that the resulting layer 2 DRB-related actions performed by the UE depend on the (reconfiguration) procedure type and the DRB type reconfiguration. Here, (reconfiguration) procedure type is defined as generalised term for the combination of {normal reconfiguration, handover} and {SCG establishment, SCG change, SCG release} procedures.

[0181] In accordance with the above-described method, if when deciding one or more required layer 2 DRB-related actions resulting from the DRB reconfiguration, multiple triggers for an action are generated, the method may enable the UE to decide to perform the action only once. For example, when the required layer 2 DRB-related actions include a Packet Data Convergence Protocol, PDCP, re-establishment action, and if when deciding one or more required actions resulting from the DRB reconfiguration, multiple triggers for the same PDCP re-establishment action are generated, the UE may decide to perform the PDCP re-establishment action only once.

[0182] The L2 flush operations currently in LTE are performed upon handover, in which case delta signalling is used. However, as will be shown below, the present application provides that the use of delta signalling should be supported not just on HO, but also on SCG change and on DRB type change i.e. the other cases in which such L2 flush operations are performed.

[0183] The following analysis involved an in depth consideration of the details of how to specify the behaviour of a UE configured with DC upon receiving a reconfiguration message including handover, SCG change and/or change of DRB type. The analysis was not limited to PDCP, but also covered MAC and RLC.

[0184] As indicated above, upon SCG change, the reconfiguration message sent from the RAN includes a release and addition of the SCG meaning that all SCG configuration parameters are signalled. As indicated in the previous, the PDCP operation is the same as performed upon handover. In case of handover, E-UTRAN does normally however only signal the changes compared to the current configuration (i.e. delta signalling). The protocol does however also include an option to provide the full configuration upon handover, targeted to address the case the target eNB is does not comprehend the current configuration as it supports a lower release of the protocol. Table 1 below summarises the action currently specified upon handover (without/with fullConfig), listed in sequential order.

TABLE-US-00001 TABLE 1 Handover/delta Handover/fullConfig Reset MAC Re-establish PDCP for all RBs that are established Re-establish RLC for all RBs that are established Consider SCells to be deactivated Apply the received CRNTI, Release the current configuration (common if resourceConfigDed & mobilityControlInfo included) mobilityControlInfo Apply the default configuration (Phy, SPS, MAC main), logical channel and RLC for SRB1/2 For EPS included in drb-ToAddModList (i.e. continueing): release PDCP/RLC/DTCH entities & DRB identity For other EPS bearers: same, but also inform upper layers about the release Reconfigure security Apply other configurations received (SCells, measConfig, otherConfig) If RA success, consider procedure completed successfully

[0185] Table 1. Actions currently specified on handover for delta and full signaling

[0186] Some further remarks on the above specification for HO are as follows: [0187] In case of fullConfig, the UE still performs reset/re-establishment of L2 before it releases the entities, which seems redundant [0188] The reset of MAC that is performed upon handover is considered to be functionally equivalent to release+addition of the MAC entity, as would be performed upon release and addition of the SCG [0189] The reset of RLC that is performed upon handover is considered to be not entirely functionally equivalent to release+addition of the RLC entity. I.e. for release of an RLC entity the specification does not explicitly state/mandate reassembly of RLC SDUs and their forwarding to upper layers (as is done upon RLC re-establishment). It seems that the UE should however preferably perform this operation upon RLC release also (even though currently not mandated)

[0190] From the above, turning now to consider, an SCG change procedure when using release and addition upon SCG change (i.e. no delta signalling): [0191] the UE operation to be performed at RLC and MAC layers does not seem to require any specification as it automatically follows from the release and addition of the concerned entity [0192] The UE operation to be performed at PDCP is however different from a simple release and addition of the concerned entity i.e. the PDCP entity really needs to continue and perform some actions to avoid data loss. It is however possible to model this operation, but it means the UE cannot process the received fields drbToReleaseList and drbToAddModList independently, but has to recognise that the DRB actually continues [0193] In the previous, it was indicated that the UE not just needs to consider SCG change but also DRB type change and thus anyhow needs to analyse both fields to decide the required action

[0194] If delta signalling were supported upon SCG change, however, the analysis undertaken has shown that: [0195] The UE operation to be performed at RLC and MAC layers would require statements similar to the ones for handover [0196] The UE operation at PDCP can be specified similar to handover. If the operation is needed for cases not involving handover (i.e. where SCG change is performed not as part of handover), a separate field would need to be introduced to trigger this

[0197] The analysis has shown that the same applies were delta signalling supported upon DRB type change even when it involves a move of PDCP from MCG to SCG configuration (i.e. a change of DRB type from MCG or split to SCG DRB) or vice versa. It has been found that in this case delta signalling would have the advantage that we can align the PDCP, RLC and MAC operation with the behaviour as performed upon handover.

[0198] It is recognised that the supporting of delta signalling on DRB type change implies that the reference for the delta configuration signalling differs depending on the case, i.e: [0199] In case the reconfiguration does not involve a move of PDCP: the reference PDCP configuration is part of the configuration of the Cell Group (CG) including PDCP (i.e. intra-CG) [0200] In case the reconfiguration involves a move of PDCP: the reference is the PDCP configuration is part of the configuration of the Cell Group (CG) currently including PDCP (i.e. inter-CG) [0201] However, there is one PDCP configuration per DRB and even though it moves between cell groups one can regard that in both cases the current PDCP configuration is the reference

[0202] As indicated in the previous, upon SCG change (as well as upon DRB type change) the PDCP cannot be released and added/created again because this would involve unacceptable data loss. This requires the PDCP internal state/context to be maintained. Still, the UE needs to take into account the PDCP configuration that is signalled by E-UTRAN. As the PDCP existing entity continues, if full signalling were used rather than delta signalling, one way to do this would be for the UE to itself derive the delta to the current configuration even though E-UTRAN signals the full configuration. The UE can do this by comparing the received full configuration with the current configuration.

[0203] An example of this proposed PDCP configuration handling by the UE on full signalling and delta signalling on an SCG change procedure is as follows. Suppose that: the PDCP configuration includes 5 optional fields (configurationparameters) i.e. field1 to field5; and that the UE is currently configured with field1, field3 and field4.

[0204] Full signalling: If the E-UTRAN wants to configure the UE with field1, field2 and field4, and it wants to modify the value of field1 and it applies full config, and thus signals (besides the field indicating the UE shall release the current config i.e. fullConfigSCG), the complete new configuration in SCG-ConFIG. I.e. it would include field1, field2 and field4.

[0205] The UE however, would not release the current PDCP configuration, but it instead compares the received full configuration with the current configuration and determines the differences (i.e. the delta) and the corresponding changes which in this case would be: modification of field1 (as the received value differs), addition of field2 (as this is currently not configured) and release of field3.

[0206] Delta signalling: If the E-UTRAN wants to configure the UE with field1, field2 and field4, and it wants to modify the value of field1 and it applies delta signalling, it thus signals (besides the field indicating the SCG change procedure i.e. that UE shall perform a L2 flush), the changes compared to the current SCG configuration i.e. it would include field1 (to indicate the new value), field2 (as currently not configured) and an indication the UE shall release field3. The UE would apply these changes to the SCG configuration and continue the PDCP entity.

[0207] Both approaches (use of delta signalling and full signalling of DRB configuration parameters on SCG change and DRB type change) seem to be possible, and merely result in different conditions to trigger the same/similar UE behaviour.

[0208] Introducing support for delta signalling on SCG change and DRB type change would not seem to introduce much additional complexity, we could consider to allow delta signalling upon SCG change. However, the UE and the eNBs operating as the MeNB and the SeNBs need to be configured to support delta signalling.

[0209] FIG. 8 is a message sequence chart showing an SeNB change procedure supporting delta signalling. At step 1, the MeNB sends an SeNB Addition Request message to the target SeNG (T-SeNB) as an AP message over X2 interface. The SeNB Addition Request is modified to include the SCG-Configuration set according to the configuration currently assigned to the UE. This may be included in the RRC Inter-node message SCGConfigInfo included in the X2 AP message.

[0210] At step 2 the T-SeNB sends an SeNB Addition Request Acknowledge message to the MeNB as an AP message over the X2 interface. The X2 AP message SeNB Addition Request Acknowledge is modified to include a field to indicate that the UE should perform the operations defined for SCG-Change i.e. to reset/release MAC, to re-establish/release RLC and to re-establish PDCP. This may be included in the RRC Inter-node message SCGConfig(uration) included in the X2 AP message. The T-SeNB sets the/an fullConfigSCG field indicating whether the UE should release the entire SCG-Configuration before applying the signaled SCG-configuration i.e. indicating to not apply delta signalling. This is included in the RRC Inter-node message SCGConfig(uration) included in the X2 AP message SeNB Addition Request Acknowledge

[0211] At step 3, the MeNB sends an SeNB Release Request Message to the source SeNB (S-SeNB) and at step 4 the MeNB sends an RRC Connection Reconfiguration Message to the UE over the Uu air interface. The RRC message RRCConnectionReconfiguration is modified to include a field to indicate that the UE should perform the operations defined for SCG-Change i.e. to reset/release MAC, to re-establish/release RLC and to re-establish PDCP. This may be included in the RRC IE SCG-Configuration that may be included in this RRC message. Here the SGC configuration includes a delta configuration that the UE applies to the current PDCP configuration for the PDCP entity that continues. If delta signalling is not indicated and instead the RRCConnectionReconfiguration indicates an SCG release and add, the UE, instead of releasing the SCG Configuration itself determines the delta from the fully signalled configuration parameters, and the UE applies this derived delta to the current PDCP configuration for the PDCP entity that continues.

[0212] At step 5 the UE sends an RRC Connection Reconfiguration Complete message to the MeNB over the Uu air interface. Thereafter the MeNB sends an SeNB Reconfiguration Complete message to the T-SeNB over the X2 interface and in step 7 the UE then performs a Random Access Procedure with the T-SeNB to synchronise with and gain access to the SeNB.

[0213] Thus, to enable a UE to support delta signalling on SCG change and DRB type change, the present application provides a method of a UE as shown in the flow chart of FIG. 9. Here, in step 901, the UE detects a signalled DRB reconfiguration including an SCG change procedure or DRB type change not including handover. This may be by an SCG change or DRB type change is indicated in the RRC Connection Reconfiguration message. For example, the mobilityControlInfoSCG field of the RRC Connection Reconfiguration message may indicate an SCG change procedure. At step 902, it is determined if delta signalling is used of if full signalling is used. If delta signalling is used, at step 903 the UE applies received signalled changes compared to the current SCG configuration parameters to update the stored SCG parameters. The method further comprises: flushing the layer 2 of Service Data Units, SDUs; releasing and adding the SCG-MAC entity; re-establishing the SCG-RLC entity; and continuing and re-establishing the PDCP entity for the SCG DRB that is established.

[0214] Alternatively, if at step 902 it is determined that full SCG configuration signalling is received upon an SCG change procedure or DRB type change not including handover (for example by receipt of an SCG release and add instruction by virtue of a fullConfigSCG field of the DRB reconfiguration message), at step 904 the UE continues and re-establishes the PDCP entity for the SCG DRB that is established. At step 905 the UE determines, from the signalled full SCG configuration, the delta (i.e. the changes) to the current PDCP configuration necessary to reconfigure the PDCP. At step 906 the UE applies the determined changes.

[0215] Similarly, to enable an eNB acting as an MeNB to support delta signalling on SCG change and DRB type change, the present application provides a method of an eNB. Here, the eNB transmits signalling of a reconfiguration procedure of a DRB on SCG change or DRB type change. If the eNB and target SeNB support delta signalling on SCG change or DRB type change not including handover, the eNB signalling indicates an SCG change procedure or DRB type change not including handover and the eNB signals the delta (i.e. changes) compared to the current SCG configuration parameters. The eNB itself derives the delta. The indication for the UE to perform the operations defined for SCG change (i.e. to reset/release MAC, to re-establish/release RLC and to re-establish PDCP) may comprise using the mobilityControlInfoSCG field of the RRC connection reconfiguration message.

[0216] If the eNB and target SeNB do not support delta signalling on SCG change or DRB type change not including handover, the eNB may signal a full SCG configuration and an indication that an existing SCG configuration should be released before applying the signalled SCG configuration. For example, the fullConfigSCG field can be used to indicate for the UE to release the entire SCG configuration before applying a signalled SCG configuration. The indication for the UE to release the entire SCG configuration before applying a signalled SCG configuration can be received from and/or generated by an SeNB.

[0217] The MeNB may further transmit to a target SeNB the SCG configuration upon inter-SeNB SCG change (i.e. within the SeNB addition Request message it sends to the target SeNB).

[0218] Upon a change of MeNB, the MeNB may further transmit to a target MeNB the SCG configuration upon inter-MeNB handover (i.e. within the X2 AP message Handover Request that it sends to the target MeNB. This would be included in the RRC inter-node message HandoverPreparationInformation that is contained in this X2 AP message).

[0219] It should be noted that the fullConfig parameter was introduced to support mobility towards a node supporting the ASN.1 of a lower protocol version. Such a node namely receives a configuration including extension that it does not comprehend. As the node does can not generate the normal signalling used to release the functionality associated with such extensions, a field was introduced merely indicating the UE shall release the entire configuration (fullConfig). In case of handover towards from an SeNB supporting a late protocol version to an SeNB supporting an early version (i.e. REL-12) a similar solution is can be used i.e. that the target SeNB can decide that the UE should release the entire SCG configuration. Thus when delta signalling is supported upon SCG change, the SeNB is assumed to be the proper node to decide the fullConfigSCG parameter, as described above.

[0220] Currently three different SCG reconfiguration procedures are defined a) normal SCG reconfiguration, b) synchronous SCG reconfiguration i.e. a field is included indicating the UE should perform Random Access (RA) towards the PSCell, c) SCG change i.e. a procedure involving release and addition of the SCG i.e. including flushing of the layer 2 (and also involving RA towards PSCell). As for the MCG there is no option to perform an RA without doing flushing of layer 2, one could debate the need to support option b). In case this option is removed, the field that is currently assumed to indicate the UE should perform RA i.e. mobilityControlInfoSCG, could actually be used to indicate the UE should perform SCG change, as described above.

[0221] An analysis determining the complete UE behaviour upon handover, SCG change and/or DRB type change has been performed and is set out in Table 2 below. It should be noted that the table describes the UE actions only and is based on the assumption that upon release of an RLC entity the UE flushes to upper layers. Importantly, it should also be noted Table 2 covers the case where full signalling is used upon SCG change as well as upon DRB type changes. Some remarks about additional statements that would need to be introduced to if delta signalling were used are set out below.

[0222] In case there is UE operation applicable in every cell of a row/column, this behaviour is included in the edge cell i.e. the leftmost/top cell respectively.

TABLE-US-00002 TABLE 2 Setting out complete UE behaviour 2. Handover with SCG change Handover with 5. SCG MCG-MAC: reset SCG release 3. SCG change establishment 1. Normal SCG-MAC: MCG-MAC: reset SCG-MAC: 4. SCG release SCG-MAC: reconfiguration rel + add SCG-MAC: rel rel + add SCG-MAC: rel add a. MCG None PDCP: reestablish PDCP: reestablish None None None (no DRB MCG-RLC: reestablish MCG-RLC: reestablish type change) b. Split None PDCP: reestablish Not possible PDCP: partial Not possible Not possible (no DRB MCG-RLC: reestablish reestablish type change) SCG-RLC: rel + add SCG-RLC: rel + add c. SCG None PDCP: reestablish Not possible PDCP: reestablish Not possible Not possible (no DRB SCG-RLC: rel + add SCG-RLC: rel + add type change) d. MCG None PDCP: reestablish Not possible None Not possible None .fwdarw.Split MCG-RLC: reestablish (not essential) PDCP: (not essential) UL route SCG-RLC: add e. MCG PDCP: reestablish PDCP: reestablish Not possible PDCP: reestablish Not possible PDCP: reestablish .fwdarw.SCG (not essential) (not essential) MCG-RLC: rel SCG-RLC: add f. Split Not possible PDCP: reestablish Not possible PDCP: reestablish Not possible Not possible .fwdarw.SCG (not needed (not needed MCG-RLC: rel in Rel-12) in Rel-12) SCG-RLC: rel + add g. SCG Not possible PDCP: reestablish Not possible PDCP: reestablish Not possible Not possible .fwdarw. split (not needed (not needed MCG-RLC: add in Rel-12) in Rel-12) SCG-RLC: rel + add h. SCG PDCP: reestablish PDCP: reestablish PDCP: reestablish PDCP: reestablish PDCP: reestablish Not possible .fwdarw.MCG MCG-RLC: add SCG-RLC: rel i. Split PDCP: Partial PDCP: Reestablish PDCP: reestablish PDCP: Partial PDCP: Partial Not possible .fwdarw.MCG reestablish MCG-RLC: reestablish MCG-RLC: reestablish reestablish reestablish SCG-RLC: rel

[0223] There does not seem to be a real need to move traffic towards SCG immediately upon handover, while moving traffic in the other direction seems important to support (as the target SeNB may not be able to admit the same DRBs). The latter could also be debated as RAN2 earlier agreed that inter-SeNB SCG change upon handover is not really essential for REL-12.

[0224] As a result, all cases in the table need to be supported for DC, with the following exceptions. The cells that are shaded out correspond to cases that do not exist. The cases where an SCG establishment is performed in which the DRB type changes from MCG to SCG or split might need to be supported e.g. if we want to avoid an SCG without DRB. The cases where an SCG change is performed (as part of a handover or otherwise) in which the DRB type changes from MCG to SCG or split do not seem essential to support, but could be supported if they do not introduce additional complexity. The cases where an SCG change is performed (as part of a handover or otherwise) in which the DRB type changes between SCG and split need not be supported in Rel-12.

[0225] Referring to Table 2, it can be seen that the ‘cell-specific’ action (i.e. the action not commonly applicable for all concerned row/column cells) only includes the following items: [0226] PDCP re-establishment, Partial PDCP re-establishment [0227] MCG-RLC re-establishment (although it is not needed this operation could actually always be done upon handover i.e. when the MCG-RLC entity is released, without a significant detrimental effect) [0228] Release/addition of SCG-RLC entity upon SCG change (with/without handover) obviously applies only in case the current configuration includes an SCG-RLC entity (i.e. not for MCG DRB). This could be reflected in the top row

[0229] Taking this into account, the table of complete UE behaviour can be simplified, as shown in Table 3.

TABLE-US-00003 TABLE 3 Simplified table setting out complete UE behaviour 2. Handover with SCG change PDCP: reestablish MCG-MAC: reset Handover with SCG MCG-RLC: reestablish release PDCP: re- SCG-MAC: rel + add establish MCG-MAC: 3. SCG change SCG-MAC: SCG-RLC: rel + add, reset MCG-RLC: rel + add SCG-RLC: 5. SCG 1. Normal if split/SCG DRB (source reestablish SCG-MAC: rel + add, if split/ 4. SCG release establishment reconfiguration config) rel SCG DRB (source config) SCG-MAC: rel SCG-MAC: add a. MCG None None None None None None (no DRB type change) b. Split None None Not possible PDCP: Not possible Not possible (no DRB Partial type change) reestablish c. SCG None  None Not possible PDCP: reestablish Not possible Not possible (no DRB type change) d. None None Not possible None Not possible None MCG.fwdarw.Split (not essential) (not essential) PDCP: UL route SCG-RLC: add e. MCG None None Not possible None Not possible None .fwdarw.SCG (not essential) (not essential) PDCP re- establish MCG-RLC: rel SCG-RLC: add f. Split Not possible None Not possible None Not possible Not possible .fwdarw.SCG (not needed (not needed PDCP re- in Rel-12) in Rel-12) establish MCG-RLC: rel SCG-RLC: rel + add g. SCG Not possible None Not possible None Not possible Not possible .fwdarw.split (not needed  (not needed PDCP re- in Rel-12) in Rel-12) establish MCG-RLC: add SCG-RLC: rel + add h. SCG None None None None None Not possible .fwdarw.MCG PDCP re- establish MCG-RLC: add SCG-RLC: rel i. Split PDCP: None None PDCP: PDCP: Not possible .fwdarw.MCG Partial Partial Partial SCG- reestablish reestablish reestablish RLC: rel

[0230] Several actions performed upon handover are already covered by the current procedural specification, i.e. PDCP: re-establish, MCG-MAC: reset, MCG-RLC: re-establish.

[0231] Several actions indicated in the table are the normal actions performed upon receiving the field indicating the concerned action (meaning that in the procedural specification this is implicitly already covered by the procedural specification): XCG-MAC rel/add, XCG-RLC rel/add, PDCP UL route (data path). Whether this is the case for release of MCG-RLC upon DRB type change depends on the actual signalling details. Let's assume that upon change from Split to SCG-DRB, the signalling indicates release of the SCG-RLC. In case delta signalling would be used upon SCG change (meaning the RLC and MAC fields are not released and added), statements need to be introduced to reflect SCG-MAC is reset and SCG-RLC is re-established

[0232] Taking into account the above means that the procedural specification merely needs to additionally cover the UE actions underlined in the Simplified Table 3 above. That the UE shall perform (assuming full signalling on SCG change and DRB type change): [0233] PDCP re-establishment upon DRB type change MCG⇄SCG, split⇄SCG, as well as of SCG DRB upon SCG change [0234] Partial PDCP re-establishment upon DRB type change split.fwdarw.MCG upon reconfiguration other than HO, as well as of split DRB upon SCG change

[0235] Thus, the present application provides a method of a UE having additional specified actions to completely specify the UE actions required to perform DRB reconfiguration procedures and DRB type changes in DC. That is, the UE, on detecting reconfiguration of a DRB having or changing to a split DRB or SCG DRB type, if the reconfiguration includes: a reconfiguration procedure type not including handover for DRBs in which the DRB type changes between (a) a split DRB or an MCG DRB; and (b) an SCG DRB; or an SCG change procedure for an SCG DRB; the UE re-establishes the PDCP entity for the concerned DRB. Alternatively, or in addition, the UE, on detecting reconfiguration of a DRB having or changing to a split DRB or SCG DRB type, if the reconfiguration includes: a reconfiguration procedure type not including handover for DRBs in which the DRB type changes from a split DRB to an MCG DRB in which DL data is received only from serving cells of a MCG; or an SCG change procedure for a split DRB; the UE partially re-establishes the PDCP entity for the concerned DRB.

[0236] The partial PDCP re-establishment operation that has been identified as being needed may actually be unnecessary. It has been realised that it may actually be better to avoid the additional complexity of introducing this partial PDCP re-establishment and instead always trigger a complete PDCP re-establishment in the cases currently assumed to trigger a partial PDCP re-establishment. This can be achieved if a UE configured with a split DRB performs a regular PDCP re-establishment (alike in case of HO without DC) when the DRB is changed to MCG DRB, as well as upon SCG change. In fact, in these cases, if reconfiguration including: a reconfiguration procedure type not including handover for DRBs in which the DRB type changes from a split DRB to an MCG DRB in which DL data is received only from serving cells of a MCG; or an SCG change procedure for a split DRB; occurs, the MeNB may initiate handover procedures and signal the UE appropriately (e.g. by including field mobilityControlInfo field in the RRC Connection Reconfiguration message).

[0237] Thus the present application provides an alternative to partial PDCP re-establishment, in that a UE is configured such that if reconfiguration including: a reconfiguration procedure type not including handover for DRBs in which the DRB type changes from a split DRB to an MCG DRB; or an SCG change procedure for a split DRB; occurs and signalling indicating handover procedures is received; then the UE performs the procedures indicated for handover.

[0238] Given the above signalling and procedures needed for configuring and reconfiguring a UE with DC, an efficient signalling mechanism between the E-UTRAN and the UE is desirable. In case E-UTRA configures a UE with Dual Connectivity, the dedicated UE radio configuration comprises 2 parts: an MCG configuration and an SCG configuration. The MeNB has overall responsibility for setting the UE configuration parameters, and in particular solely controls the MCG configuration. The SeNB generally decides the values of the SCG configuration parameters, but the MeNB may specify some constraints/limitations to be observed by SeNB in order to ensure that the combination of MCG and SCG configuration does not exceed the capabilities of the UE. Generally, the SCG configuration as signalled to the UE is generated by the SeNB. However, there are some exceptions where SCG configuration as signalled is generated by the MeNB. For example: [0239] The MeNB may generate a field indicating that the UE shall release the entire SCG. [0240] The MeNB signals the Small Cell Counter (SCC) that the UE uses when deriving the security key associated with the SCG (i.e. the S-KeNB) from the security key associated with the MCC/MeNB [0241] The MeNB may decide to release a split DRB, in which case both the MCG and SCG parts of the DRB configuration need to be released. It is not entirely clear which node would generate the release of the SCG configuration part in such a case, but it could be beneficial if the MeNB would be able to do this

[0242] One signalling option that has been identified would be for the MeNB to update fields in SCG-Configuration received from SeNB In this option, SeNB would send the SCG configuration parameters (referred to as Information Element (IE) SCG-Configuration) in a container over X2 (e.g. in an octet string) to the MeNB. The IE SCG-Configuration includes parameters that are set by MeNB e.g. the SCC, fullConfigSCG. The SeNB does not set these parameters, or sets them to a dummy value. This parameter is in the original REL-12 part of the IE SCG-Configuration. This means, that any MeNB supporting Dual-Connectivity can set the parameter even if the SeNB would add extensions to the IE SCG-Configuration. The MeNB includes the received IE SCG-Configuration in a container (e.g. in an octet string) over the Uu interface towards the UE (i.e. in the in a RRCConnectionReconfiguration message). Use of this container makes it possible for MeNB to forward any extensions the SeNB included, even if MeNB does not comprehend them. MeNB sets the SCG parameters in this SCG-Configuration that it decides e.g. the SCC, fullConfigSCG. The following ASN.1 specifies this approach.

TABLE-US-00004 -- ASN1START  RRCConnectionReconfiguration-v12xy-IEs ::= SEQUENCE (  .fwdarw. scg-Configuration-r12.fwdarw. .fwdarw. .fwdarw. .fwdarw. OCTET STRING (SCG-Configuration-r12) OPTIONAL, .fwdarw. -- Need ON  .fwdarw. nonCriticalExtension .fwdarw. .fwdarw. .fwdarw. .fwdarw. SEQUENCE { } .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. OPTIONAL  )  SCG-Configuration-r12 ::= .fwdarw. .fwdarw. .fwdarw. CHOICE (  .fwdarw. release .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. NULL, .fwdarw. setup .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. SEQUENCE (  .fwdarw. .fwdarw. -- FFS how to indicate release and addition in single reconfiguration (i.e. change of SeNS)  .fwdarw. .fwdarw. fullConfigSCG-r12.fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. ENUMERATED (true).fwdarw. .fwdarw. .fwdarw. OPTIONAL, -- Cond SCG-Cha  .fwdarw. .fwdarw. securityConfigSCG-r12.fwdarw. .fwdarw. .fwdarw. .fwdarw. SecurityConfigSCG-r12.fwdarw. .fwdarw. OPTIONAL, -- Cond SCG-Est  .fwdarw. .fwdarw. radioResourceConfigDedicatedSCG-r12.fwdarw.RadioResourceConfigDedicatedSCG-r12 OPTIONAL,-- Cond SCG-Est  .fwdarw. .fwdarw. -- FFS is there is a need for sCellToReleaseListSCG or whether this is done by MCG config  .fwdarw. .fwdarw. sCellToReleaseListSCG-r12 .fwdarw. .fwdarw. .fwdarw. SCellToReleaseList-r10.fwdarw. .fwdarw. OPTIONAL, -- Need ON  .fwdarw. .fwdarw. sCellToAddModListSCG-r12 .fwdarw. .fwdarw. .fwdarw. SCellToAddModList-r10.fwdarw. .fwdarw. OPTIONAL, -- Cond SCG-Est  .fwdarw. .fwdarw. -- FFS how to indicate UE shall apply RA in SCG and what to signal  .fwdarw. .fwdarw. mobilityControlInfoSCG-r12.fwdarw. .fwdarw. .fwdarw. MobilityControlInfoSCG-r12 OPTIONAL -- Cond SCG-Est  .fwdarw. )  )  SecurityConfigSCG-r12 ::= .fwdarw. .fwdarw. .fwdarw. .fwdarw. SEQUENCE {  .fwdarw. scg-Count-r12 .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. INTEGER (0.. 65535),  .fwdarw. cipheringAlgorithmSCG-r12 .fwdarw. .fwdarw. .fwdarw. CipheringAlgorithm-r12,  .fwdarw. ...  )  indicates data missing or illegible when filed

[0243] However, as, in this Uu signalling approach, the SeNB should treat some of the fields (e.g. fullConfigSCG and scg-Count) more or less as dummy fields, the MeNB can not transparently forward the information received by SeNB, but needs to decode and re-code the information received from SeNB before signalling it to the UE.

[0244] An alternative approach would be that the MeNB forwards the SCG configuration parameters that it decides to the SeNB, which subsequently includes them in the SCG-Configuration. The latter variant enable the MeNB to transparently forward the SCG configuration information received from SeNB.

[0245] In some cases it may be actually be up to the SeNB to set fullConfigSCG i.e. when delta signalling would be supported upon SCG change. In such cases, the SeNB may actually decide, e.g. when on the received SCG configuration includes non-comprehended extensions, to apply full instead of delta signalling (i.e. for the same reasons as for the regular fullConfig).

[0246] In view of the above, an alternative signalling option is herein disclosed that enables simple transparent forwarding by the MeNB of the SCG configuration parameters received from the SeNB would be one where it can add additional IEs in the message to the UE. In this Uu signalling option, the SeNB sends the SCG configuration parameters (referred to as Information Element SCG-Configuration) in a container over X2 (e.g. in an octet string). The IE SCG-Configuration sent to the UE consists of two parts i.e. a first part that is set by MeNB and a second part represented by field scg-ConfigurationPart2, containing the parameters set by SeNB.

[0247] In this approach, only the second part is carried in a container, and the MeNB can forward this part of the SCG configuration that is received from SeNB transparently to the UE. The following ASN.1 specifies this two-part signalling approach.

TABLE-US-00005 -- ASN1START  RRCConnectionReconfiguration-v12xy-IEs ::= SEQUENCE (  .fwdarw. scg-Configuration-r12.fwdarw. .fwdarw. .fwdarw. .fwdarw. OCTET STRING OPTIONAL, .fwdarw. -- Need ON  (SCG-Configuration-r12).fwdarw. .fwdarw. nonCriticalExtension .fwdarw. .fwdarw. .fwdarw. .fwdarw. SEQUENCE { } .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. OPTIONAL  )  SCG-Configuration-r12 ::=.fwdarw. .fwdarw. .fwdarw. CHOICE (  .fwdarw. release .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. NULL, .fwdarw. setup .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. SEQUENCE (  .fwdarw. .fwdarw. scg-ConfigPart1-r12 .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. SEQUENCE (  .fwdarw. .fwdarw. .fwdarw. fullConfigSCG-r12.fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. ENUMERATED (true).fwdarw. .fwdarw. .fwdarw. OPTIONAL, -- Cond SCG- Cha  .fwdarw. .fwdarw. .fwdarw. securityConfigSCG-r12.fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. SecurityConfigSCG-Part1-r12 OPTIONAL, -- Cond SCG- Est  )  .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. OPTIONAL, -- Need- ON,  .fwdarw. .fwdarw. scg-ConfigPart2-r12 .fwdarw. .fwdarw. .fwdarw. .fwdarw. OCTET STRING (SCG-ConfigurationPart2-r12) OPTIONAL, -- Need ON .fwdarw.  .fwdarw. )  )  SCG-ConfigurationPart2-r12 ::=.fwdarw. .fwdarw. .fwdarw. SEQUENCE (  .fwdarw. -- FFS how to indicate release and addition in single reconfiguration (i.e. change of SeNB)  .fwdarw. securityConfigSCG-r12.fwdarw. .fwdarw. .fwdarw. .fwdarw. SecurityConfigSCG-Part2-r12  .fwdarw. OPTIONAL, -- Cond SCG-Est  .fwdarw. radioResourceConfigDedicatedSCG-r12.fwdarw.RadioResourceConfigDedicatedSCG-r12.fwdarw.OPTIONAL, -- Cond SCG-Est  .fwdarw. -- FFS is there is a need for sCellToReleaseListSCG or whether this is done by MCG config  .fwdarw. sCellToReleaseListSCG-r12 .fwdarw. .fwdarw. .fwdarw. SCellToReleaseList-r10.fwdarw. .fwdarw. OPTIONAL, -- Need ON  .fwdarw. sCellToAddModListSCG-r12 .fwdarw. .fwdarw. .fwdarw. SCellToAddModList-r10.fwdarw. .fwdarw. OPTIONAL, -- Cond SCG-Est  .fwdarw. -- FFS how to indicate UE shall apply RA in SCG and what to signal  .fwdarw. mobilityControlInfoSCG-r12.fwdarw. .fwdarw. .fwdarw. MobilityControlInfoSCG-r12 OPTIONAL.fwdarw.-- Cond SCG-Est  )  SecurityConfigSCG-Part1-r12 ::=.fwdarw. .fwdarw. .fwdarw. SEQUENCE (  .fwdarw. scg-Count-r12 .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. .fwdarw. INTEGER (0.. 65535) ,  .fwdarw. ...  )  SecurityConfigSCG-Part2-r12 ::= .fwdarw. .fwdarw. SEQUENCE (  .fwdarw. cipheringAlgorithmSCG-r12 .fwdarw. .fwdarw. .fwdarw. CipheringAlgorithm-r12,  .fwdarw. ...  indicates data missing or illegible when filed

[0248] The ASN.1 above illustrates that with both Uu signalling approaches, all SCG configuration parameters are signalled together in a structure, which would make it easy to release all parameters in one go.

[0249] With both approaches, the use of containers enables the receiving node to forward the information received from originating eNB without having to comprehend the complete information (i.e. including all extensions introduced in later versions) generated by the originating node.

[0250] The first Uu signalling approach does however imply the MeNB needs to decode and re-code the information received from the SeNB which is a drawback. An advantage of second Uu signalling approach in which two parts are used is that it is possible to transparently forward the information received from the SeNB. Further, with the second approach the information sent to the UE is partitioned according to the network node that sets the information.

[0251] Thus to enable the E-UTRAN to configure the UE with DC in which the MeNB can efficiently transparently forward SCG configuration parameters received from the SeNB, the present application provides a method of a UE including receiving signalling of a DRB configuration including SCG configuration parameters provided together in a single information structure comprising two parts: a first part including SCG configuration parameters generated by the MeNB; and a second part including SCG configuration parameters generated by the SeNB. A container (such as an octet string) is provided around the parameters of the first and second parts or a container is provided around only the parameters of the second part.

[0252] The present application also provides a method of an eNB, acting as the MeNB, including transmitting signalling of a configuration of a DRB, the signalled DRB configuration including SCG configuration parameters provided together in a single information structure comprising two parts: a first part including SCG configuration parameters generated by the MeNB; and a second part including SCG configuration parameters generated by the SeNB. The two parts of the transmitted SCG configuration parameters are provided together in a single information structure. The MeNB sets the first part of the SCG configuration parameters and receives the second part of the SCG configuration parameters from the SeNB, and transmits to the UE the SCG configuration parameters provided in a single information structure comprising the two parts.

[0253] In one embodiment, a container is provided around the parameters of the first and second parts. Here, the MeNB transmits the first part of the SCG configuration parameters to the SeNB, and receives from the SeNB and transparently forwards to the UE the SCG configuration parameters provided in a single information structure comprising the two parts. Alternatively, the MeNB may decode the SCG configuration parameters of the second part and recode the SCG configuration parameters of the first and second parts, placing them together in a container before transmitting the SCG configuration parameters to the UE.

[0254] In another embodiment, a container is provided around only the parameters of the second part. In this embodiment, the MeNB receives the second part of the SCG configuration parameters from the SeNB, and transparently forwards them to the UE, placed within a container and which together with the first part of the SCG configuration parameters is provided in a single information structure comprising the two parts.

[0255] Additionally, the present application provides an eNB acting as an SeNB including transmitting configuration parameters, for use in signalling of a configuration of a DRB, the transmitted DRB configuration parameters comprising SCG configuration parameters generated by the SeNB. The DRB configuration parameters are transmitted to the MeNB over the X2 interface. The SeNB receives SCG configuration parameters generated by the MeNB and provides the transmitted DRB configuration parameters together in a single information structure comprising two parts: a first part including the SCG configuration parameters generated by the MeNB; and a second part including the SCG configuration parameters generated by the SeNB.

[0256] Another aspect of dual connectivity in which the present application provides a proposed alteration to UE behaviour is to avoid transfer delays on detection of Radio Link Failure (RFL) or release of an SCG DRB, as will be explained below.

[0257] When detecting RLF of an SCG (SCG SCG-RLF), data communication via the SCG is impossible as the UE suspends uplink transmission via the SCG. The UE furthermore reports the problem to the MeNB. Currently, until the MeNB has resolved the issue, packets transferred via DRBs for which data is (partially) transferred via the SCG will thus suffer from increased transfer delay. To avoid this, upon detecting SCG-RLF or SCG release, the UE initiates autonomous reconfiguration of the DRBs which data is (partially) transferred via the SCG. For example, upon detecting SCG-RLF, the UE autonomously reconfigures the one or more split DRB to MCG DRB by releasing the associated SCG-RLC entity and associated the SCG logical channel. In another example, upon detecting SCG-RLF, the UE autonomously reconfigures one or more SCG DRB to MCG DRB by releasing the associated SCG-RLC entity and the associated SCG logical channel while establishing a new MCG entities with a default configuration. The associated PDCP is re-established (alike upon handover) and reconfigured to a default configuration. The default configuration could either be a configuration specified in the standard, or the configuration that was used in the SCG, or the configuration last used in the MCG for the same EPS bearer (i.e. before it was changed to SCG DRB).

[0258] On the other hand, the default configuration could be different for different protocol parts (PDCP, RLC, Logical channel).

[0259] For example, Table 4 below shows an illustration that for different protocol parts a different default could be used.

TABLE-US-00006 TABLE 4 Example default configuration per protocol part on autonomous reconfiguration New baseline New baseline configuration of MCG configuration of MCG DRB that was SCG DRB that was split DRB (when autono- DRB (when autono- Protocol part mously reconfigured) mously reconfigured) PDCP config PDCP config used in SCG RLC config RLC config used in SCG LogicalChannel Logical channel identity used identity in MCG before it was changed to SCG DRB (for the same EPS bearer) Logical Logical channel config used in channel MCG before it was changed to config SCG DRB (for the same EPS bearer)

[0260] To use the configuration used in the SCG as default, the MeNB needs to know the current SCG configuration. As the SeNB always signals this via MeNB, the MeNB should always have the latest SCG-Configuration. It could however be that the SeNB configures extensions not comprehended by the MeNB. If this is the case, the MeNB can either decide to use another default e.g. the default specified in the standard or it could indicate that the UE should release all extension beyond a particular protocol release. As the objective of the autonomous UE actions is to avoid increased transfer delays, this should be configured prior to SCG-RLF being detected (i.e. if it were in a message by which the MeNB indicates the UE is allowed to resume data transfer across the former SCG DRBs, the main objective would be defeated). Thus the MeNB should indicate which default configuration the UE shall apply, which is done in advance of the SCG-RLF or SCG release. When the MeNB indicates that the configuration used in the SCG is the default, it may additionally indicate that, when applying this default, the UE shall release all extensions beyond a particular protocol release, if configured.

[0261] In case E-UTRAN releases the SCG, the UE could perform the same autonomous reconfiguration operations as defined for detection of SCG-RLF. This would mean the network would only need to configure any changes compared to the (default) configurations resulting from the UE autonomous reconfigurations. This may reduce the signaling upon SCG release as the MeNB may just signal the new configuration when releasing the SCG.

[0262] 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 or wireless connection and embodiments suitably encompass the same.

[0263] 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.

[0264] 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.

[0265] 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.

[0266] 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.