HARQ timing design for a TDD system

• US 9,331,759 B2
• Filed: 12/26/2013
• Issued: 05/03/2016
• Est. Priority Date: 03/29/2013
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: He, Hong, Fwu, Jong-Kae, Khoryaev, Alexey, Han, Seunghee
• Primary Examiner(s): Abelson, Ronald B
• Application Number:
  US14/141,265
• Publication Number:
  US 20140293842A1
• Time in Patent Office: 859 Days
• Field of Search: 370/280, 370/328, 370/329, 370/336, 370/337
• US Class Current: 1/1
• CPC Class Codes: H04B 1/56 with provision for simultaneous communication in two directions
• CPC Class Codes: H04B 7/0417 Feedback systems
• CPC Class Codes: H04B 7/0452 Multi-user MIMO systems
• CPC Class Codes: H04B 7/0617 for beam forming
• CPC Class Codes: H04B 7/0619 using feedback from receiving side feedback signaling for adaptive modulation/coding H04L1/0001
• CPC Class Codes: H04B 7/063 Parameters other than those covered in groups H04B7/0623 - H04B7/0634, e.g. channel matrix rank or transmit mode selection
• CPC Class Codes: H04B 7/0695 using beam selection
• CPC Class Codes: H04B 7/088 using beam selection
• CPC Class Codes: H04L 1/1864 ARQ related signaling H04L1/1607 takes precedence
• CPC Class Codes: H04L 2025/03426 transmission using multiple-input and multiple-output channels
• CPC Class Codes: H04L 25/0204 of multiple channels
• CPC Class Codes: H04L 25/03305 Joint sequence estimation and interference removal joint detection of several desired signals H04L25/03331
• CPC Class Codes: H04L 47/803 Application aware
• CPC Class Codes: H04L 47/83 based on usage prediction
• CPC Class Codes: H04L 5/0007 the frequencies being orthogonal, e.g. OFDM(A), DMT
• CPC Class Codes: H04L 5/0048 Allocation of pilot signals, i.e. of signals known to the receiver
• CPC Class Codes: H04L 5/0051 of dedicated pilots, i.e. pilots destined for a single user or terminal
• 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/0057 Physical resource allocation for CQI
• CPC Class Codes: H04L 5/0085 : when channel conditions change
• CPC Class Codes: H04L 5/1469 : using time-sharing
• CPC Class Codes: H04L 65/613 : for the control of the source by the destination control signals issued by the client directed to the server or network components specially adapted for selective content distribution H04N21/637
• CPC Class Codes: H04L 65/65 : Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 65/70 : Media network packetisation
• CPC Class Codes: H04L 65/75 : Media network packet handling
• CPC Class Codes: H04L 65/752 : adapting media to network capabilities
• CPC Class Codes: H04L 65/756 : adapting media to device capabilities
• CPC Class Codes: H04L 65/762 : at the source reformatting of additional data in video distribution servers H04N21/2355
• CPC Class Codes: H04L 65/764 : at the destination reformatting of additional data in video clients H04N21/4355
• CPC Class Codes: H04L 65/80 : Responding to QoS
• CPC Class Codes: H04M 1/72457 : according to geographic location
• CPC Class Codes: H04N 21/2402 : Monitoring of the downstream path of the transmission network, e.g. bandwidth available traffic monitoring in data switching networks H04L43/00; monitoring data switching networks utilization H04L43/0876
• CPC Class Codes: H04N 21/8456 : by decomposing the content in the time domain, e.g. in time segments
• CPC Class Codes: H04N 21/8543 : using a description language, e.g. Multimedia and Hypermedia information coding Expert Group [MHEG], eXtensible Markup Language [XML] information retrieval of semistructured data, the underlying structure being taken into account, e.g. mark-up language structure data G06F16/80
• CPC Class Codes: H04W 24/00 : Supervisory, monitoring or testing arrangements
• CPC Class Codes: H04W 24/02 : Arrangements for optimising operational condition
• CPC Class Codes: H04W 28/02 : Traffic management, e.g. flow control or congestion control
• CPC Class Codes: H04W 28/0226 : based on location or mobility handoff or reselection H04W36/00; mobile application services making use of the location of users or terminals H04W4/02
• CPC Class Codes: H04W 28/0289 : Congestion control load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 28/082 : among bearers or channels
• CPC Class Codes: H04W 28/20 : Negotiating bandwidth
• CPC Class Codes: H04W 36/0011 : for data sessions of end-to-end connection
• CPC Class Codes: H04W 36/0022 : for transferring data sessions between adjacent core network technologies
• CPC Class Codes: H04W 36/0072 : of resource information of target access point
• CPC Class Codes: H04W 36/08 : Reselecting an access point
• CPC Class Codes: H04W 36/125 : involving different types of service backbones
• CPC Class Codes: H04W 36/22 : for handling the traffic
• CPC Class Codes: H04W 36/26 : by agreed or negotiated communication parameters
• CPC Class Codes: H04W 4/021 : Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 48/06 : based on traffic conditions
• CPC Class Codes: H04W 48/12 : using downlink control channel
• CPC Class Codes: H04W 48/16 : Discovering, processing access restriction or access information
• CPC Class Codes: H04W 48/18 : Selecting a network or a communication service
• CPC Class Codes: H04W 56/001 : Synchronization between nodes
• CPC Class Codes: H04W 72/0446 : Resources in time domain, e.g. slots or frames
• CPC Class Codes: H04W 72/046 : the resource being in the space domain, e.g. beams
• CPC Class Codes: H04W 72/541 : using the level of interference
• CPC Class Codes: H04W 76/15 : Setup of multiple wireless link connections
• CPC Class Codes: H04W 8/02 : Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
• CPC Class Codes: H04W 8/06 : Registration at serving network Location Register, VLR or user mobility server
• CPC Class Codes: H04W 8/082 : for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
• CPC Class Codes: H04W 84/042 : Public Land Mobile systems, e.g. cellular systems
• CPC Class Codes: H04W 84/045 : using private Base Stations, e.g. femto Base Stations, home Node B
• 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/10 : adapted for operation in multiple networks, e.g. multi-mode access points
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Disclosed are methods and apparatuses related to receiving one or more indications of time division duplex (TDD) uplink/downlink (UL/DL) configurations for two consecutive radio frames. Based on the indications of the TDD UL/DL configurations, a reference TDD UL/DL configuration may be identified for one or more Hybrid Automatic Repeat reQuest (HARQ) processes.

Claims

1. A user equipment (UE) comprising:

receiver circuitry to receive, from an eNodeB (eNB), a first indication of a first time division duplex (TDD) uplink/downlink (UL/DL) configuration for a first radio frame and a second indication of a second TDD UL/DL configuration that is same or different than the first TDD UL/DL configuration for a second radio frame that immediately follows the first radio frame; and

Hybrid Automatic Repeat reQuest (HARQ) circuitry to;

identify, based at least in part on the first and second indications, a first HARQ timing for a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH) in the first radio frame; and

identify, based at least in part on the second indication, a second HARQ timing for a PDSCH or a PUSCH in the second radio frame that immediately follows the first radio frame.

2. The UE of claim 1, wherein the first indication or the second indication is a Downlink Control Information (DCI) message.

3. The UE of claim 1, wherein the first indication is received in a first subframe or a first set of subframes of the first radio frame and the second indication is received in a second subframe or a second set of subframes of the second radio frame.

4. The UE of claim 1, wherein the first indication is received in a first subframe or a first set of subframes of a third radio frame that immediately precedes the first radio frame, and the second indication is received in a second subframe or a second set of subframes of the first radio frame.

5. The UE of claim 1, wherein the first indication or the second indication are received in a DL subframe or a set of DL subframes of a TDD UL/DL configuration indicated in a SystemInformationBlockType1 (SIB1) message.

6. The UE of claim 5, wherein the first indication or the second indication are received in subframe 0, subframe 1, subframe 5, or subframe 6 of the TDD UL/DL configuration.

7. A user equipment (UE) comprising:

receiver circuitry to receive, from an eNodeB (eNB), a first indication of a first time division duplex (TDD) uplink/downlink (UL/DL) configuration for a first radio frame and a second indication of a second TDD UL/DL configuration that is same or different than the first TDD UL/DL configuration for a second radio frame that immediately follows the first radio frame; and

Hybrid Automatic Repeat reQuest (HARQ) circuitry to;

identify based at least in t on the first and second indication, a first HARQ timing for a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH) in the first radio frame; and

identify, based at least in part on the second indication, a second HARQ timing a PDSCH or a PUSCH in the second radio frame that immediately follows the first radio frame,

wherein the first indication is received in a first subframe or first set of subframes of the first radio frame or a second subframe or a second set of subframes of a third radio frame immediately preceding the first radio frame, and the second indication is received in a third subframe or third set of subframes of the first radio frame or a fourth subframe or fourth set of subframes of the second radio frame.

8. A method comprising:

receiving, by a user equipment (UE) from an eNodeB (eNB), a first indication of a first time division duplex (TDD) uplink/downlink (UL/DL) configuration for a first radio frame;

receiving, by the UE, a second indication of a second TDD UL/DL configuration for a second radio frame immediately following the first radio frame; and

identifying, by the UE and based at least in part on the first indication and the second indication, a reference TDD UL/DL configuration for Hybrid Automatic Repeat reQuest (HARQ) timing determination associated with a first subframe in the first radio frame.

9. The method of claim 8, further comprising identifying, by the UE, the reference TDD UL/DL configuration based at least in part on whether a HARQ acknowledgement signal associated with a data received in the first subframe is to be transmitted by the UE in the first radio frame or the second radio frame in accordance with the first TDD UL/DL configuration.

10. The method of claim 8, wherein the reference TDD UL/DL configuration is the second TDD UL/DL configuration if DL subframes in the first TDD UL/DL configuration of the first radio frame are a subset of DL subframes in the second TDD UL/DL configuration of the second radio frame.

11. The method of claim 8, wherein the reference TDD UL/DL configuration is the first TDD UL/DL configuration if DL subframes in the first TDD UL/DL configuration of the first radio frame are a superset of DL subframes in the second TDD UL/DL configuration of the second radio frame.

12. The method of claim 8, wherein the first TDD UL/DL configuration has a first configuration of UL subframes and the second TDD UL/DL configuration has a second configuration of UL subframes;

wherein at least a portion of the UL subframes in the first TDD UL/DL are UL subframes in the second TDD UL/DL configuration; and

wherein the reference TDD UL/DL configuration is a third TDD UL/DL configuration having a configuration of UL subframes that only includes the portion of UL subframes.

13. The method of claim 12, wherein the reference TDD UL/DL configuration is TDD UL/DL configuration 4 if the first TDD UL/DL configuration is TDD UL/DL configuration 3 and the second TDD UL/DL configuration is TDD UL/DL configuration 1;

wherein the reference TDD UL/DL configuration is TDD UL/DL configuration 4 if the first TDD UL/DL configuration is TDD UL/DL configuration 1 and the second TDD UL/DL configuration is TDD UL/DL configuration 1;

wherein the reference TDD UL/DL configuration is TDD UL/DL configuration 5 if the first TDD UL/DL configuration is TDD UL/DL configuration 3 or TDD UL/DL configuration 4, and the second TDD UL/DL configuration is TDD UL/DL configuration 2; and

wherein the reference TDD UL/DL configuration is TDD UL/DL configuration 5 if the first TDD UL/DL configuration is TDD UL/DL configuration 2, and the second TDD UL/DL configuration is TDD UL/DL configuration 3 or TDD UL/DL configuration 4.

14. The method of claim 12, wherein the reference TDD UL/DL configuration is TDD UL/DL configuration 0 if the first TDD UL/DL configuration is TDD UL/DL configuration 0;

wherein the reference TDD UL/DL configuration is TDD UL/DL configuration 6 if the first TDD UL/DL configuration is TDD UL/DL configuration 6, and the second TDD UL/DL configuration is TDD UL/DL configuration 3; and

wherein the reference TDD UL/DL configuration is the TDD UL/DL configuration 3 if the first TDD UL/DL configuration is TDD UL/DL configuration 2, and the second TDD UL/DL configuration is TDD UL/DL configuration 3.

15. The method of claim 12, further comprising transmitting, by the UE, a HARQ acknowledgement signal from the UE in accordance with the reference TDD UL/DL configuration.

16. The method of claim 15, further comprising transmitting, by the UE, the HARQ acknowledgement signal on a third generation partnership project (3GPP) physical uplink control channel (PUCCH) or a Physical Uplink Shared Channel (PUSCH).

17. One or more non-transitory computer readable storage media comprising instructions to cause a user equipment (UE), upon execution of the instructions by a processor of the UE, to:

receive a first indication of a time division duplex (TDD) uplink/downlink (UL/DL) configuration for a first radio frame;

receive, from an eNodeB (eNB), a second indication of a second TDD UL/DL configuration for a second radio frame immediately following the first radio frame;

identify, by the UE and based at least in part on the first TDD UL/DL configuration and the second TDD UL/DL configuration, a reference TDD UL/DL configuration for a Hybrid Automatic Repeat reQuest (HARQ) timing in the first radio frame; and

transmit, by the UE, a UL HARQ acknowledgement (HARQ-ACK) message or a physical uplink shared channel (PUSCH) message based at least in part on the reference TDD UL/DL configuration.

18. The one or more computer readable storage media of claim 17, wherein the instructions further include instructions to receive a HARQ feedback associated with a PUSCH message in the first radio frame based at least in part on the reference TDD UL/DL configuration.

19. The one or more computer readable storage media of claim 17, wherein the reference TDD UL/DL configuration is equal to the first TDD UL/DL configuration.

20. The one or more computer readable storage media of claim 17, wherein the reference TDD UL/DL configuration is equal to the second TDD UL/DL configuration.

21. The one or more computer readable storage media of claim 17, wherein the reference TDD UL/DL configuration is not equal to the first TDD UL/DL configuration or the second TDD UL/DL configuration.

22. The one or more computer readable storage media of claim 17, wherein the indication is a downlink control information (DCI) message.

23. The one or more computer readable storage media of claim 17, wherein the UL HARQ-ACK message is a message on a third generation partnership project (3GPP) physical uplink shared channel (PUSCH) or a 3GPP physical uplink control channel (PUCCH).