User equipment and methods of bearer operation for carrier aggregation

• US 10,015,805 B2
• Filed: 10/30/2014
• Issued: 07/03/2018
• Est. Priority Date: 10/31/2013
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: Zhang, Yujian, Heo, Youn Hyoung
• Primary Examiner(s): Cho, Hong
• Application Number:
  US14/917,154
• Publication Number:
  US 20160234847A1
• Time in Patent Office: 1,342 Days
• Field of Search: None
• 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 28/08 Load balancing or load distribution transferring a connection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12
• 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 a User Equipment (UE) to support dual-connectivity with a Master Evolved Node-B (MeNB) and a Secondary eNB (SeNB) are disclosed herein. The UE may receive downlink traffic packets from the MeNB and from the SeNB as part of a split data radio bearer (DRB). At least a portion of control functionality for the split DRB may be performed at each of the MeNB and the SeNB. The UE may receive an uplink eNB indicator for an uplink eNB to which the UE is to transmit uplink traffic packets as part of the split DRB. Based at least partly on the uplink eNB indicator, the UE may transmit uplink traffic packets to the uplink eNB as part of the split DRB. The uplink eNB may be selected from a group that includes the MeNB and the SeNB.

Claims

1. User Equipment (UE) to support dual-connectivity with a Master Evolved Node-B (MeNB) and a Secondary eNB (SeNB), the UE comprising hardware processing circuitry configured to:

receive downlink traffic packets from the MeNB and from the SeNB as part of a split data radio bearer (DRB), wherein at least a portion of control functionality for the split DRB is performed at each of the MeNB and the SeNB;

receive, from the MeNB, a Radio Resource Control (RRC) message that includes an uplink eNB indicator for an uplink eNB to which the UE is to transmit uplink traffic packets as part of the split DRB, wherein the uplink eNB indicator indicates a selection from a group of candidate eNBs the group of candidate eNBs including the MeNB and the SeNB;

based at least partly on the uplink eNB indicator, transmit uplink traffic packets to the indicated uplink eNB as part of the split DRB; and

exchange control messages with the MeNB on a Primary Cell (PCell) included in a Master Cell Group (MCG) supported by the MeNB;

wherein the split DRB operates as part of a Secondary Cell (SCell) included in a Secondary Cell Group (SCG) supported by the SeNB; and

wherein the uplink eNB indicator indicates whether the UE is to transmit uplink traffic packets on the SCG or the MCG.

2. The UE according to claim 1, wherein the uplink traffic packets include one or more Packet Data Convergence Protocol (PDCP) Service Data Units (SDUs).

3. The UE according to claim 1, the hardware processing circuitry further configured to exchange traffic packets with the MeNB on the PCell as part of a second, different DRB.

4. The UE according to claim 1, the hardware processing circuitry further configured to transmit, for reception at the indicated uplink eNB, a Radio Link Control (RLC) status Protocol Data Unit (PDU) that includes status information for the split DRB.

5. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors to perform operations for support, by User Equipment (UE), of dual-connectivity with a Master Evolved Node-B (MeNB) and a Secondary eNB (SeNB), the operations to configure the one or more processors to:

receive downlink traffic packets from the MeNB and from the SeNB as part of a split data radio bearer (DRB), wherein at least a portion of control functionality for the split DRB is performed at each of the MeNB and the SeNB;

receive, from the MeNB, a Radio Resource Control (RRC) message that includes an uplink eNB indicator for an uplink eNB to which the UE is to transmit uplink traffic packets as part of the split DRB, wherein the uplink eNB indicator indicates a selection from a group of candidate eNBs, the group of candidate eNBs including the MeNB and the SeNB;

based at least partly on the uplink eNB indicator, transmit uplink traffic packets to the indicated uplink eNB as part of the split DRB; and

exchange control messages with the MeNB on a Primary Cell (PCell) included in a Master Cell Group (MCG) supported by the MeNB;

wherein the split DRB operates as part of a Secondary Cell (SCell) included in a Secondary Cell Group (SCG) supported by the SeNB; and

wherein the uplink eNB indicator indicates whether the UE is to transmit uplink traffic packets on the SCG or the MCG.

6. The non-transitory computer-readable storage medium according to claim 5, wherein the uplink traffic packets include one or more Packet Data Convergence Protocol (PDCP) Service Data Units (SDUs).

7. The non-transitory computer-readable storage medium according to claim 5, wherein:

the operations further configure the one or more processors to include, in the uplink packets, a Radio Link Control (RLC) status Protocol Data Unit (PDU) that includes status information for the split DRB.

8. The non-transitory computer readable storage medium according to claim 5, wherein the operations further configure the one or more processors to include, in the uplink packets, one or more Packet Data Convergence Protocol (PDCP) Service Data Units (SDUs).

9. A method of supporting dual-connectivity with a Master Evolved Node-B (MeNB) and a Secondary eNB (SeNB) at User Equipment (UE), the method comprising:

receiving downlink traffic packets from the MeNB and from the SeNB as part of a split data radio bearer (DRB), wherein at least a portion of control functionality for the split DRB is performed at each of the MeNB and the SeNB;

receiving, from the MeNB, a Radio Resource Control (RRC) message that includes an uplink eNB indicator for an uplink eNB to which the UE is to transmit uplink traffic packets as part of the split DRB, wherein the uplink eNB indicator indicates a selection from a group of candidate eNBs, the group of candidate eNBs including the MeNB and the SeNB;

based at least partly on the uplink eNB indicator, transmitting uplink traffic packets to the indicated uplink eNB as part of the split DRB; and

exchanging control messages with the MeNB on a Primary Cell (PCell) included in a Master Cell Group (MCG) supported by the MeNB;

wherein the split DRB operates as part of a Secondary Cell (SCell) included in a Secondary Cell Group (SCG) supported by the SeNB; and

wherein the uplink eNB indicator indicates whether the UE is to transmit uplink traffic packets on the SCG or the MCG.

10. The method according to claim 9, wherein the uplink traffic packets include one or more Packet Data Convergence Protocol (PDCP) Service Data Units (SDUs).

11. The method according to claim 9, further comprising including, in the uplink packets, a Radio Link Control (RLC) status Protocol Data Unit (PDU) that includes status information for the split DRB.

12. The method according to claim 9, further comprising including, in the uplink packets, one or more Packet Data Convergence Protocol (PDCP) Service Data Units (SDUs).

13. User Equipment (UE) to support dual-connectivity with a Master Evolved Node-B (MeNB) and a Secondary eNB (SeNB), the UE comprising hardware processing circuitry configured to:

receive downlink traffic packets from the MeNB and from the SeNB as part of a split data radio bearer (DRB), wherein at least a portion of control functionality for the split DRB is performed at each of the MeNB and the SeNB;

as part of Packet Data Convergence Protocol (PDCP) layer reordering for the received downlink traffic packets, bypass a PDCP reordering timer that controls a minimum waiting period for which the UE monitors for downlink traffic packets received out of sequence.

14. The UE according to claim 13, wherein the PDCP reordering timer is set to a value of zero as part of the bypass.