Radio link failure handling for dual connectivity

• US 9,674,852 B2
• Filed: 09/19/2014
• Issued: 06/06/2017
• Est. Priority Date: 10/31/2013
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: Zhang, Yujian, Heo, Youn Hyoung
• Primary Examiner(s): O CONNOR, BRIAN T
• Application Number:
  US14/491,639
• Publication Number:
  US 20150117183A1
• Time in Patent Office: 991 Days
• CPC Class Codes: H04B 17/17 Detection of non-compliance or faulty performance, e.g. response deviations H04B17/18 takes precedence
• CPC Class Codes: H04B 17/318 Received signal strength
• CPC Class Codes: H04B 7/0413 MIMO systems
• CPC Class Codes: H04J 3/1694 Allocation of channels in TDM/TDMA networks, e.g. distributed multiplexers Passive Optical Networks H04Q11/0062
• CPC Class Codes: H04L 5/0007 the frequencies being orthogonal, e.g. OFDM(A), DMT
• CPC Class Codes: H04L 5/001 the frequencies being arranged in component carriers
• CPC Class Codes: H04L 5/0098 Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
• CPC Class Codes: H04W 24/10 Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 28/0215 based on user or device properties, e.g. MTC-capable devices services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51
• CPC Class Codes: H04W 36/0069 in case of dual connectivity, e.g. decoupled uplink/downlink
• CPC Class Codes: H04W 36/00692 using simultaneous multiple data streams, e.g. cooperative multipoint [CoMP], carrier aggregation [CA] or multiple input multiple output [MIMO] allocation of physical resources in CoMP or in CA H04L5/0035
• CPC Class Codes: H04W 36/305 Handover due to radio link failure control signalling for hand-off failure H04W36/0079
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/023 using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 4/90 Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
• CPC Class Codes: H04W 48/06 based on traffic conditions
• CPC Class Codes: H04W 48/08 Access restriction or access information delivery, e.g. discovery data delivery signalling during connection H04W76/00
• CPC Class Codes: H04W 48/12 : using downlink control channel
• CPC Class Codes: H04W 48/18 : Selecting a network or a communication service
• CPC Class Codes: H04W 52/346 : distributing total power among users or channels
• CPC Class Codes: H04W 56/001 : Synchronization between nodes
• CPC Class Codes: H04W 56/002 : Mutual synchronization
• CPC Class Codes: H04W 60/00 : Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 60/02 : by periodical registration
• CPC Class Codes: H04W 72/0453 : Resources in frequency domain, e.g. a carrier in FDMA
• CPC Class Codes: H04W 72/51 : based on terminal or device properties
• CPC Class Codes: H04W 72/52 : based on load
• CPC Class Codes: H04W 72/542 : using measured or perceived quality
• CPC Class Codes: H04W 72/56 : based on priority criteria
• CPC Class Codes: H04W 74/004 : in the uplink, i.e. towards network
• CPC Class Codes: H04W 74/0833 : Random access procedures, e.g. with 4-step access
• CPC Class Codes: H04W 76/10 : Connection setup
• CPC Class Codes: H04W 76/14 : Direct-mode setup
• CPC Class Codes: H04W 76/15 : Setup of multiple wireless link connections
• CPC Class Codes: H04W 76/18 : Management of setup rejection or failure
• CPC Class Codes: H04W 76/19 : Connection re-establishment
• CPC Class Codes: H04W 8/005 : Discovery of network devices, e.g. terminals
• CPC Class Codes: H04W 8/04 : Registration at HLR or HSS [Home Subscriber Server]
• CPC Class Codes: H04W 8/06 : Registration at serving network Location Register, VLR or user mobility server
• CPC Class Codes: H04W 8/183 : Processing at user equipment or user record carrier
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: H04W 88/08 : Access point devices
• CPC Class Codes: H04W 88/16 : Gateway arrangements
• CPC Class Codes: H04W 88/18 : Service support devices; Network management devices
• CPC Class Codes: H04W 92/20 : between access points
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Embodiments of an evolved Node B (eNB) and methods for radio link failure handling for dual connectivity are generally described herein. A method performed by circuitry of a User Equipment (UE) may include connecting, at a UE, to a Master eNB (MeNB) and connecting to a Secondary eNB (SeNB). The method may include determining, at the UE, that one of the connections has a Radio Link Failure and determining at the UE, that the other of the connections remains connected to the UE. The method may include refraining from initiating a Radio Resource Control (RRC) re-establishment procedure while at least one of the connections does not have a radio link failure.

Claims

1. A first evolved Node B (eNB), the first eNB connected to a User Equipment (UE), the first eNB comprising:

hardware processing circuitry arranged to;

receive, from the UE, an indication of a Radio Link Failure at a second eNB, the UE in a dual connectivity state with the first eNB and the second eNB, wherein the indication indicates that the UE is to refrain from initiating a Radio Resource Control (RRC) re-establishment procedure between the UE and the second eNB; and

communicate to the second eNB a command to suspend at least one radio bearer, the at least one radio bearer used prior to being suspended by the second eNB to communicate with the UE.

2. The first eNB of claim 1, wherein the first eNB is a Master eNB (MeNB) and the second eNB is a Secondary eNB (SeNB), and wherein the MeNB is associated with a Primary Cell (PCell) and the SeNB is associated with a Secondary Cell (SCell).

3. The first eNB of claim 2, wherein operations to suspend the at least one radio bearer used by the second eNB include operations to suspend all radio bearers used by the SeNB.

4. The first eNB of claim 2, wherein the hardware processing circuitry of the MeNB is further arranged to transmit a Radio Resource Control reconfiguration message to the UE to remove the SCell from a set of cells serving the UE.

5. The first eNB of claim 1, wherein the first eNB is a Secondary eNB (SeNB) and the second eNB is a Master eNB (MeNB), and wherein the MeNB is associated with a Primary Cell (PCell) and the SeNB is associated with a Secondary Cell (SCell).

6. The first eNB of claim 5, wherein operations to suspend at least one radio bearer used by the second eNB include operations to suspend a Signaling Radio Bearer 1 (SRB1) and a Signaling Radio Bearer 2 (SRB2) used by the MeNB.

7. The first eNB of claim 5, wherein the hardware processing circuitry of the SeNB is further arranged to relay a Radio Resource Control reconfiguration message from the MeNB to the UE to suspend the at, least one radio bearer.

8. The first eNB of claim 5, wherein the hardware processing circuitry of the SeNB is further arranged to receive instructions to initiate a handover from the MeNB to suspend the at least one radio bearer.

9. The first eNB of claim 5, wherein the hardware processing circuitry of the SeNB is further arranged to use a UE context for the UE, the UE context maintained by the MeNB.

10. The first eNB of claim 5, wherein the hardware processing circuitry of the SeNB is further arranged to receive the Radio Link Failure indication over a logical channel.

11. The first eNB of claim 5, wherein the MeNB is further arranged to receive an indication of a random access problem from the UE.

12. The first eNB of claim 11, wherein the indication is received by the MeNB using a Radio Resource Control (RRC) message.

13. The first eNB of claim 11, wherein the indication is received by the MeNB using a MAC control element, and wherein the MAC control element has zero bytes or the MAC control element includes information indicating:

a random access problem in the SeNB, a radio link control error in the SeNB, or a radio link monitoring error in the SeNB.

14. User Equipment (UE) adapted for communication with an evolved Node B (eNB), the UE comprising:

a transceiver arranged to transmit and receive communication with a Master eNB (MeNB) and a Secondary eNB (SeNB) in a dual connectivity state; and

a processor, coupled to the transceiver, arranged to;

determine that one of a connection to the MeNB and a connection SeNB has a Radio Link Failure;

determine that the other one of the connection to the MeNB and the connection to the SeNB does not have a Radio Link Failure; and

prevent initiation, by the UE, of a Radio Resource Control (RRC) re-establishment procedure between the UE and the one of the connection to the MeNB and the connection to the SeNB that has the Radio Link Failure while the other one of the connection to the MeNB and the connection to the SeNB does not have a Radio Link Failure and remains connected to the UE.

15. The UE of claim 14, wherein the connection that has a Radio Link Failure is the MeNB and the connection that remains connected is the SeNB, and wherein the MeNB is associated with a Primary Cell (PCell) and the SeNB is associated with a Secondary Cell (SCell), and wherein the UE is further arranged to transmit a Radio Resource Control (RRC) message to the MeNB indicating that the SeNB has a Radio Link Failure.

16. The UE of claim 14, wherein the connection that has a Radio Link Failure is the SeNB and the connection that remains connected is the MeNB, and wherein the MeNB is associated with a Primary Cell (PCell) and the SeNB is associated with a Secondary Cell (SCell).

17. The UE of claim 16, wherein the UE is further arranged to receive a Radio Resource Control reconfiguration message originating from the MeNB sent through the SeNB.

18. The UE of claim 16, wherein the UE is further arranged to receive a handover command message originating from the MeNB through the SeNB.

19. The UE of claim 16, wherein the UE is further arranged to receive a handover command message originating from the MeNB through a new cell, wherein the new cell is not the PCell or the SCell.

20. The UE of claim 16, wherein the UE is further arranged to reconnect to the MeNB when a MeNB channel condition exceeds a threshold.

21. At least one non-transitory machine-readable medium including instructions for operation of a computing system, which when executed by a machine, cause the machine to:

connect, at a User Equipment (UE), to a Master evolved Node B (MeNB);

connect, at the UE, to a Secondary eNB (SeNB), in a dual connectivity state;

determine, at the UE, that one of the connections has a Radio Link Failure;

determine, at the UE, that the other of the connections does not have a Radio Link Failure; and

refrain, at the UE, from initiating a Radio Resource Control (RRC) re-establishment procedure between the UE and the one of the connections that has the Radio Link Failure while the other of the connections does not have a Radio Link Failure and remains connected to the UE.

22. The at least one machine-readable medium of claim 21, wherein the connection that has a Radio Link Failure is the SeNB and the connection that remains connected is the MeNB, and wherein the MeNB is associated with a Primary Cell (PCell) and the SeNB is associated with a Secondary Cell (SCell).

23. The at least one machine-readable medium of claim 22, further comprising, operations to receive, at the UE, a Radio Resource Control (RRC) reconfiguration message originating from the MeNB sent through the SeNB.

24. User Equipment (UE) adapted for communication with an evolved Node B (eNB), the UE comprising:

a transceiver arranged o transmit and receive communication with a Master eNB (MeNB) and a Secondary eNB (SeNB), in a dual connectivity state; and

a processor, coupled to the transceiver, arranged to perform operations in connection with a connection to a .MeNB and a connection. to a SeNB;

determine that one of a connection to the MeNB and a connection to the SeNB has a Radio Link Failure;

determine that the other one of the connection to the MeNB and the connection to the SeNB does not have a Radio Link Failure; and

communicate indirectly to the one of the connection to the MeNB and the connection to the SeNB to suspend at least one radio bearer used by the one of the connection to the MeNB and the connection to the SeNB, the at least one radio bearer used to communicate with the UE by the one of the connection to the MeNB and the connection to the SeNB prior to being suspended, wherein to communicate includes to communicate via the other one of the connection to the MeNB and the connection to the SeNB that does not have a Radio Link Failure and remains connected to the UE.

25. The UE of claim 24, wherein the one of the connection to the MeNB and the connection to the SeNB that has the Radio Link Failure is the connection to the MeNB and the other one of the connection to the MeNB and the connection to the SeNB that does not have the Radio Link Failure is the connection to the SeNB, and wherein the MeNB is associated with a Primary Cell (PCell) and the SeNB is associated with a Secondary Cell (SCell).