Selection of acknowledgment timing in wireless communications

• US 10,079,669 B2
• Filed: 12/21/2017
• Issued: 09/18/2018
• Est. Priority Date: 11/04/2011
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel Corporation
• Inventors: He, Hong, Fwu, Jong-Kae
• Primary Examiner(s): Towfighi, Afshawn M
• Application Number:
  US15/851,345
• Publication Number:
  US 20180167190A1
• Time in Patent Office: 271 Days
• CPC Class Codes: H04B 7/024 Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
• CPC Class Codes: H04B 7/0456 Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
• CPC Class Codes: H04B 7/0626 Channel coefficients, e.g. channel state information [CSI]
• CPC Class Codes: H04J 11/00 Orthogonal multiplex systems, e.g. using WALSH codesH04J13/00 takes precedence
• CPC Class Codes: H04J 3/12 Arrangements providing for calling or supervisory signals
• CPC Class Codes: H04L 1/0026 Transmission of channel quality indication
• CPC Class Codes: H04L 1/0077 Cooperative coding
• CPC Class Codes: H04L 1/1812 Hybrid protocols; Hybrid automatic repeat request [HARQ]
• CPC Class Codes: H04L 27/2646 using feedback from receiver for adjusting OFDM transmission parameters, e.g. transmission timing or guard interval length
• CPC Class Codes: H04L 27/2662 Symbol synchronisation
• CPC Class Codes: H04L 27/2675 Pilot or known symbols
• CPC Class Codes: H04L 5/0035 Resource allocation in a cooperative multipoint environment
• CPC Class Codes: H04L 5/0053 Allocation of signaling, i.e. of overhead other than pilot signals
• CPC Class Codes: H04L 5/0055 Physical resource allocation for ACK/NACK for physical mapping arrangements in ARQ protocols H04L1/1861
• CPC Class Codes: H04L 5/0078 Timing of allocation
• CPC Class Codes: H04L 5/14 Two-way operation using the same type of signal, i.e. duplex
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 4/06 Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 52/0206 in access points, e.g. base stations access point devices per se H04W88/08
• CPC Class Codes: H04W 52/146 : Uplink power control
• CPC Class Codes: H04W 52/242 : taking into account path loss
• CPC Class Codes: H04W 52/244 : Interferences in heterogeneous networks, e.g. among macro and femto or pico cells or other sector / system interference [OSI]
• CPC Class Codes: H04W 52/34 : TPC management, i.e. sharing limited amount of power among users or channels or data types, e.g. cell loading
• CPC Class Codes: H04W 56/0015 : one node acting as a reference for the others
• CPC Class Codes: H04W 68/02 : Arrangements for increasing efficiency of notification or paging channel
• CPC Class Codes: H04W 72/02 : Selection of wireless resources by user or terminal
• CPC Class Codes: H04W 72/0446 : Resources in time domain, e.g. slots or frames
• CPC Class Codes: H04W 72/12 : Wireless traffic scheduling
• CPC Class Codes: H04W 72/21 : in the uplink direction of a wireless link, i.e. towards the network
• CPC Class Codes: H04W 72/23 : in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 72/542 : using measured or perceived quality
• CPC Class Codes: H04W 76/11 : Allocation or use of connection identifiers
• CPC Class Codes: H04W 76/40 : for selective distribution or broadcast
• CPC Class Codes: H04W 84/14 : WLL [Wireless Local Loop]; RLL [Radio Local Loop]
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: H04W 88/08 : Access point devices
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Disclosed is a method including communicating, by a mobile device, with a base station via first and second component carriers having different frequency bands and time division duplexing (TDD) configurations. The method may include receiving one or more downlink transmissions via the second component carrier. The method may include selecting a hybrid automatic repeat request (HARQ) timing sequence based on the TDD configurations of the first and second component carriers. The method may include transmitting one or more positive acknowledgment and/or negative acknowledgement (ACK/NACK) signals, associated with the one or more downlink transmissions, according to the selected HARQ timing sequence. Other embodiments may be described and claimed.

Claims

1. A method comprising:

identifying a reference time division duplex (TDD) configuration based on a first TDD configuration of a primary serving cell (PCell) and a second TDD configuration of a secondary serving cell (SCell); and

transmitting a hybrid automatic repeat request acknowledgement (HARQ-ACK) signal associated with downlink data received through the SCell according to a HARQ timing of the reference TDD configuration, wherein;

only HARQ-ACK signals associated with the downlink data of the SCell are to be transmitted according to the HARQ timing of the reference TDD configuration; and

HARQ-ACK signals associated with downlink data of the PCell are to be transmitted only according to the HARQ timing of the first TDD configuration.

2. The method of claim 1, wherein the reference TDD configuration is different from the second TDD configuration.

3. The method of claim 2, wherein the second TDD configuration is indicated by a System Information Block 1 (SIB1) of the SCell.

4. The method of claim 1, wherein the first TDD configuration is indicated by a System Information Block 1 (SIB1) of the PCell.

5. The method of claim 1, further comprising:

identifying uplink subframes common between the first TDD configuration and the second TDD configuration; and

identifying the reference TDD configuration based on the determined uplink subframes common between the first TDD configuration and the second TDD configuration.

6. The method of claim 5, further comprising:

identifying the uplink subframes common between the first TDD configuration and the second TDD configuration; and

identifying the reference TDD configuration based on a determination that uplink subframes of the reference TDD configuration are the same as the common uplink subframes between the first TDD configuration and the second TDD configuration.

7. The method of claim 1, further comprising:

identifying the first TDD configuration as the reference TDD configuration if downlink subframes of the second TDD configuration are a subset of downlink subframes of the first TDD configuration; and

identifying the second TDD configuration as the reference TDD configuration if downlink subframes of the second TDD configuration are a superset of downlink subframes of the first TDD configuration.

8. The method of claim 1, further comprising:

identifying the reference TDD configuration as TDD downlink/uplink (DL/UL) configuration 4, if the first TDD configuration is TDD DL/UL configuration 1 and the second TDD configuration is TDD DL/UL configuration 3;

identifying the reference TDD configuration as TDD DL/UL configuration 5, if the first TDD configuration is TDD DL/UL configuration 2 and the second TDD configuration is TDD DL/UL configuration 3; and

identifying the reference TDD configuration as TDD DL/UL configuration 5, if the first TDD configuration is TDD DL/UL configuration 2 and the second TDD configuration is TDD DL/UL configuration 4.

9. The method of claim 1, further comprising:

identifying the reference TDD configuration as TDD downlink/uplink (DL/UL) configuration 4, if the first TDD configuration is TDD DL/UL configuration 3 and the second TDD configuration is TDD DL/UL configuration 1;

identifying the reference TDD configuration as TDD DL/UL configuration 5, if the first TDD configuration is TDD DL/UL configuration 3 and the second TDD configuration is TDD DL/UL configuration 2; and

identifying the reference TDD configuration as TDD DL/UL configuration 5, if the first TDD configuration is TDD DL/UL configuration 4 and the second TDD configuration is TDD DL/UL configuration 2.

10. The method of claim 1, further comprising transmitting a positive or negative acknowledgement according to the HARQ timing of the reference TDD configuration through at least one uplink subframe.

11. One or more non-transitory computer-readable media comprising instructions that, upon execution by a processor, are to cause the processor to:

identify a reference time division duplex (TDD) configuration based on a first TDD configuration of a primary serving cell (PCell) and a second TDD configuration of a secondary serving cell (SCell); and

transmit a hybrid automatic repeat request acknowledgement (HARQ-ACK) signal associated with downlink data received through the SCell according to a HARQ timing of the reference TDD configuration, wherein;

only HARQ-ACK signals associated with the downlink data of the SCell are to be transmitted according to the HARQ timing of the reference TDD configuration; and

HARQ-ACK signals associated with downlink data of the PCell are to be transmitted only according to the HARQ timing of the first TDD configuration.

12. The one or more non-transitory computer-readable media of claim 11, wherein the reference TDD configuration is different from the second TDD configuration.

13. The one or more non-transitory computer-readable media of claim 12, wherein the second TDD configuration is indicated by a System Information Block 1 (SIB1) of the SCell.

14. The one or more non-transitory computer-readable media of claim 11, wherein the first TDD configuration is indicated by a System Information Block 1 (SIB1) of the PCell.

15. The one or more non-transitory computer-readable media of claim 11, wherein the instructions are further to:

identify uplink subframes common between the first TDD configuration and the second TDD configuration; and

identify the reference TDD configuration based on the determined uplink subframes common between the first TDD configuration and the second TDD configuration.

16. The one or more non-transitory computer-readable media of claim 15, wherein the instructions are further to:

identify the uplink subframes common between the first TDD configuration and the second TDD configuration; and

identify the reference TDD configuration based on a determination that uplink subframes of the reference TDD configuration are the same as the common uplink subframes between the first TDD configuration and the second TDD configuration.

17. The one or more non-transitory computer-readable media of claim 11, wherein the instructions are further to:

identify the first TDD configuration as the reference TDD configuration if downlink subframes of the second TDD configuration are a subset of downlink subframes of the first TDD configuration; and

identify the second TDD configuration as the reference TDD configuration if downlink subframes of the second TDD configuration are a superset of downlink subframes of the first TDD configuration.

18. The one or more non-transitory computer-readable media of claim 11, wherein the instructions are further to:

identify the reference TDD configuration as TDD downlink/uplink (DL/UL) configuration 4, if the first TDD configuration is TDD DL/UL configuration 1 and the second TDD configuration is TDD DL/UL configuration 3;

identify the reference TDD configuration as TDD DL/UL configuration 5, if the first TDD configuration is TDD DL/UL configuration 2 and the second TDD configuration is TDD DL/UL configuration 3; and

identify the reference TDD configuration as TDD DL/UL configuration 5, if the first TDD configuration is TDD DL/UL configuration 2 and the second TDD configuration is TDD DL/UL configuration 4.

19. The one or more non-transitory computer-readable media of claim 11, wherein the instructions are further to:

identify the reference TDD configuration as TDD downlink/uplink (DL/UL) configuration 4, if the first TDD configuration is TDD DL/UL configuration 3 and the second TDD configuration is TDD DL/UL configuration 1;

identify the reference TDD configuration as TDD DL/UL configuration 5, if the first TDD configuration is TDD DL/UL configuration 3 and the second TDD configuration is TDD DL/UL configuration 2; and

identify the reference TDD configuration as TDD DL/UL configuration 5, if the first TDD configuration is TDD DL/UL configuration 4 and the second TDD configuration is TDD DL/UL configuration 2.

20. The one or more non-transitory computer-readable media of claim 11, wherein the instructions are further to transmit a positive or negative acknowledgement according to the HARQ timing of the reference TDD configuration through at least one uplink subframe.

21. One or more non-transitory computer-readable media comprising instructions that, upon execution by a processor in mobile device, are to cause the mobile device to:

establish communication with one or more base stations through a primary serving cell (PCell) and a secondary serving (SCell), the PCell associated with a first component carrier established with a first time-division duplexing (TDD) configuration, the SCell including a second component carrier established with a second TDD configuration;

receive downlink data through the SCell;

select a reference TDD configuration based on the first and second TDD configurations; and

transmit acknowledgement information to be associated with the downlink data according to a hybrid automatic repeat request (HARQ) timing of the reference TDD configuration,

wherein the instructions further causes the mobile device to;

select the first TDD configuration as the reference TDD configuration if downlink subframes of the second TDD configuration are a subset of downlink subframes of the first TDD configuration unless;

the first TDD configuration is TDD downlink/uplink (DL/UL) configuration 1 and the second TDD configuration is TDD DL/UL configuration 3;

the first TDD configuration is TDD DL/UL configuration 2 and the second TDD configuration is TDD DL/UL configuration 3 or 4;

the first TDD configuration is TDD DL/UL configuration 3 and the second TDD configuration is TDD DL/UL configuration 1 or TDD DL/UL configuration 2;

or

the first TDD configuration is TDD DL/UL configuration 4 and the second TDD configuration is TDD DL/UL configuration 2; and

select the second TDD configuration as the reference TDD configuration if downlink subframes of the second TDD configuration are a superset of downlink subframes of the first TDD configuration unless;

the first TDD configuration is TDD DL/UL configuration 1 and the second TDD configuration is TDD DL/UL configuration 3;

the first TDD configuration is TDD DL/UL configuration 2 and the second TDD configuration is TDD DL/UL configuration 3 or 4;

the first TDD configuration is TDD DL/UL configuration 3 and the second TDD configuration is TDD DL/UL configuration 1 or 2;

or

the first TDD configuration is TDD DL/UL configuration 4 and the second TDD configuration is TDD DL/UL configuration 2.

22. The one or more non-transitory computer-readable media of claim 21, wherein the reference TDD configuration is different from a TDD configuration indicated by a system information block of the SCell.

23. The one or more non-transitory computer-readable media of claim 22, wherein the system information block is System Information Block 1 (SIB1).

24. The one or more non-transitory computer-readable media of claim 21, wherein:

the first TDD configuration is indicated by System Information Block 1 (SIB1) of the PCell; and

the second TDD configuration is indicated by SIB1 of the SCell.

25. The one or more non-transitory computer-readable media of claim 21, wherein the processor causes the mobile device to:

select the reference TDD configuration whose uplink subframes are the same as uplink subframes common between the first TDD configuration and the second TDD configuration.

26. The one or more non-transitory computer-readable media of claim 21, wherein the processor causes the mobile device to:

select TDD DL/UL configuration 4 as the reference TDD configuration, if the first TDD configuration is TDD DL/UL configuration 1 and the second TDD configuration is TDD DL/UL configuration 3;

select TDD DL/UL configuration 5 as the reference TDD configuration, if the first TDD configuration is TDD DL/UL configuration 2 and the second TDD configuration is TDD DL/UL configuration 3; and

select TDD DL/UL configuration 5 as the reference TDD configuration, if the first TDD configuration is TDD DL/UL configuration 2 and the second TDD configuration is TDD DL/UL configuration 4.

27. The one or more non-transitory computer-readable media of claim 21, wherein the processor causes the mobile device to:

select TDD downlink/uplink (DL/UL) configuration 4 as the reference TDD configuration, if the first TDD configuration is TDD DL/UL configuration 3 and the second TDD configuration is TDD DL/UL configuration 1;

select TDD DL/UL configuration 5 as the reference TDD configuration, if the first TDD configuration is TDD DL/UL configuration 3 and the second TDD configuration is TDD DL/UL configuration 2; and

select TDD DL/UL configuration 5 as the reference TDD configuration, if the first TDD configuration is TDD DL/UL configuration 4 and the second TDD configuration is TDD DL/UL configuration 2.

28. The one or more non-transitory computer-readable media of claim 21, wherein the processor causes the mobile device to:

transmit a positive or negative acknowledgement according to the HARQ timing of the reference TDD configuration through at least one uplink subframe.

29. The one or more non-transitory computer-readable media of claim 21, wherein each of the first, second, and reference TDD configurations include at least one of TDD downlink/uplink (DL/UL) configurations 0-6.