[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2014153688A1 - Conception de gestion des temps harq pour frontière de reconfiguration en eimta - Google Patents

Conception de gestion des temps harq pour frontière de reconfiguration en eimta Download PDF

Info

Publication number
WO2014153688A1
WO2014153688A1 PCT/CN2013/000367 CN2013000367W WO2014153688A1 WO 2014153688 A1 WO2014153688 A1 WO 2014153688A1 CN 2013000367 W CN2013000367 W CN 2013000367W WO 2014153688 A1 WO2014153688 A1 WO 2014153688A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
subframe
tdd
tdd configuration
configuration
Prior art date
Application number
PCT/CN2013/000367
Other languages
English (en)
Inventor
Minghai Feng
Chao Wei
Neng Wang
Jilei Hou
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2013/000367 priority Critical patent/WO2014153688A1/fr
Publication of WO2014153688A1 publication Critical patent/WO2014153688A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1887—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0093—Point-to-multipoint

Definitions

  • Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, and the like. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources.
  • a wireless communication network may include a number of base stations that can support communication for a number of mobile devices.
  • a mobile device may communicate with a base station via downlink (DL) and uplink (UL) transmissions.
  • the downlink (or forward link) refers to the communication link from the base station to the mobile device
  • the uplink (or reverse link) refers to the communication link from the mobile device to the base station.
  • Multiple access technologies may use Frequency Division Duplexing (FDD) or Time Division Duplexing (TDD) to provide uplink and downlink communications over one or more carriers.
  • FDD Frequency Division Duplexing
  • TDD Time Division Duplexing
  • TDD formats include transmission of frames of data, each including a number of different subframes in which different subframes may be uplink or downlink subframes.
  • different formats may be used in which uplink and downlink communications may be asymmetric.
  • TDD configuration provides efficient ways to use unpaired spectrum resources and TDD configuration may be adaptive based on traffic conditions (e.g., UL/DL loading at the base station and/or mobile device).
  • traffic conditions e.g., UL/DL loading at the base station and/or mobile device.
  • flexible TDD configuration may create challenges for data error control and retransmission processes that span different TDD configurations.
  • HARQ processes with data transmissions occurring prior to TDD reconfiguration may use transitional HARQ indicator timing.
  • the transitional HA Q indicator timing may be based on HARQ indicator timing for one of the initial or post-reconfiguration TDD configuration, or may be based on a predetermined reference configuration.
  • cross-boundary HARQ processes may use transitional HARQ retransmission timing.
  • the transitional HARQ retransmission timing may be determined by new synchronous retransmission offset values for cross-boundary synchronous HARQ processes.
  • the new synchronous retransmission offset values may supplement the existing synchronous retransmission offset values.
  • the transitional HARQ retransmission timing may define synchronous HARQ retransmission timing for each subframe having DL resources.
  • the transitional HARQ retransmission timing for TDD reconfigurations may be determined according to the post-reconfiguration TDD configuration.
  • retransmission collisions for cross-boundary HARQ processes may be avoided by suspending HARQ retransmission and/or adaptive UL HARQ techniques.
  • a serving base station may suspend a HARQ process with a retransmission collision by transmitting an ACK even where the data associated with the HARQ process is not received correctly at the serving base station.
  • the serving base station may resume the suspended HARQ process on resources not colliding with other HARQ processes.
  • Adaptive UL HARQ may be used in retransmission collisions between HARQ processes in different devices by modifying UL transmission resources for one of the devices within the subframe subject to the collision.
  • Embodiments are directed to a method performed by a user equipment (UE) in communication with a base station over a TDD carrier.
  • the method may include determining a TDD configuration transition from a first TDD configuration during a first frame to a second TDD configuration during a second frame, transmitting a first uplink data
  • the method includes determining the HARQ reference configuration corresponds to one of the first TDD configuration or the second TDD configuration.
  • the HARQ reference configuration may correspond to the configuration of the first TDD configuration or the second TDD configuration that has the highest number of uplink sub frames.
  • the HARQ reference configuration may correspond to a predetermined TDD configuration from a limited set of TDD configurations. For example, the
  • predetermined TDD configuration may be the configuration of the limited set of TDD configurations having the highest number of uplink sub frames.
  • the second TDD configuration is associated with HARQ retransmission information comprising synchronous retransmission offset values
  • the method may include determining a third subframe for a second uplink transmission associated with the HARQ process based on transitional HARQ retransmission information.
  • the transitional HARQ retransmission information may be used, for example, for HARQ retransmission timing after TDD reconfiguration instead of the HARQ retransmission information for the second TDD configuration.
  • the transitional HARQ retransmission information may include HARQ
  • the method may include remapping the third subframe iteratively until the third subframe corresponds to an UL subframe for the second TDD configuration.
  • the remapping may be performed incrementally or based on remapping rules associated with the predetermined TDD configuration.
  • the transitional HARQ retransmission information may be associated with the second TDD configuration, and the transitional HARQ retransmission information may include synchronous retransmission offset values corresponding to each subframe index having downlink resources.
  • the transitional HARQ retransmission information may be used for TDD configuration transitions to the second TDD configuration irrespective of the TDD configuration prior to the TDD configuration transition.
  • Some embodiments are directed to a method performed by a base station in communication with a UE over a TDD carrier.
  • the method may include determining, for the TDD carrier, a TDD configuration transition from a first TDD configuration during a first frame to a second TDD configuration during a second frame, receiving a first uplink data transmission associated with a first hybrid automatic repeat request (HARQ) process on the TDD carrier during a first subframe of the first frame, determining a second subframe based on HARQ indicator timing for a HARQ reference configuration, and transmitting downlink resources on the second subframe, the downlink resources comprising
  • HARQ hybrid automatic repeat request
  • acknowledgement/negative acknowledgement (ACK/NACK) information associated with the first HARQ process.
  • the second TDD configuration may be associated with HARQ retransmission information comprising synchronous retransmission offset values corresponding to a set of subframe indices.
  • the second subframe may not be within the set of subframe indices of the HARQ retransmission information for the second TDD configuration.
  • the method may include determining a third subframe comprising uplink resources for receiving a second uplink data transmission associated with the first HARQ process based on transitional HARQ retransmission information.
  • the method may include determining that the third subframe conflicts with an uplink data transmission associated with a second HARQ process.
  • the first HARQ process may be suspendeed responsive to determining that the third subframe conflicts with the uplink data transmission of the second HARQ process.
  • Suspending the first HARQ process may include transmitting an ACK message associated with the first uplink data transmission for the first HARQ process in the second subframe of the second frame. The ACK message may be transmitted, for example, even when the first uplink data transmission is not received correctly at the base station.
  • the method may include determining that the third subframe conflicts with an uplink transmission associated with a second HARQ process of a second UE.
  • the second UE may, for example, have a different uplink transmission bandwidth for the TDD carrier than the first UE.
  • the base station may transmit downlink control information to the first UE including an uplink resource block assignment shift for the second uplink data transmission.
  • a second UE may be in communication with the base station using the TDD carrier.
  • the first UE may be a non-legacy UE configured according to dynamic TDD reconfiguration messaging and the second UE may be a legacy UE configured according to semi-static TDD reconfiguration messaging.
  • the method may include configuring the first UE to use the first TDD configuration for the first frame and the second TDD configuration for the second frame using the dynamic TDD reconfiguration messaging, and configuring the second UE to use a predetermined TDD configuration for the first and second frames using the semi-static TDD reconfiguration messaging.
  • the semi-static TDD reconfiguration messaging may be a system information block (SIB) message
  • the dynamic TDD reconfiguration messaging may be, for example, paging signaling, radio resource control (RRC) signaling, medium access control (MAC) signaling, or physical layer signaling.
  • Some embodiments are directed to a user equipment apparatus configured for communication with a base station over a TDD carrier.
  • the user equipment apparatus may include means for determining a TDD configuration transition from a first TDD configuration during a first frame to a second TDD configuration during a second frame for the TDD carrier, means for transmitting a first uplink data transmission during a first subframe in the first frame, the first uplink data transmission being associated with a HARQ process, means for determining a second subframe based on HARQ indicator timing for a HARQ reference configuration, and means for receiving downlink resources on the second subframe, the downlink resources comprising ACK/NACK information associated with the HARQ process.
  • the second TDD configuration may be associated with HARQ retransmission information comprising synchronous retransmission offset values corresponding to a set of subframe indices.
  • the second subframe may not be within the set of subframe indices of the HARQ retransmission information for the second TDD configuration.
  • the apparatus may include means for receiving a NACK message associated with the HARQ process in the second subframe of the second frame, and means for determining a third subframe for a second uplink transmission associated with the HARQ process based on transitional HARQ retransmission information.
  • the transitional HARQ retransmission information may include HARQ
  • the apparatus may include means for remapping the third subframe iteratively until the third subframe corresponds to an UL subframe for the second TDD configuration.
  • the remapping may be performed performed incrementally or based on remapping rules associated with the predetermined TDD configuration.
  • the transitional HARQ retransmission information may be associated with the second TDD configuration.
  • the transitional HARQ retransmission information may include synchronous retransmission offset values corresponding to each subframe index having downlink resources.
  • Some embodiments are directed to a base station apparatus for communication with a UE over a TDD carrier.
  • the base station apparatus may include means for determining a TDD configuration transition from a first TDD configuration during a first frame to a second TDD configuration during a second frame for the TDD carrier, means for receiving a first uplink data transmission associated with a first HARQ process on the TDD carrier during a first subframe of the first frame, means for determining a second subframe based on HARQ indicator timing for a HARQ reference configuration, and means for transmitting downlink resources on the second subframe, the downlink resources comprising ACK/NACK information associated with the first HARQ process.
  • the second TDD configuration may be associated with HARQ retransmission information comprising synchronous retransmission offset values corresponding to a set of subframe indices. In some instances, the second subframe may not be within the set of subframe indices of the HARQ retransmission information for the second TDD configuration.
  • the apparatus may include means for determining a third subframe comprising uplink resources for receiving a second uplink data transmission associated with the first HARQ process based on transitional HARQ retransmission information. [0023] The apparatus may include means for determining that the third subframe conflicts with an uplink data transmission associated with a second HARQ process.
  • the apparatus includes means for suspending the first HARQ process responsive to determining that the third subframe conflicts with the uplink data transmission of the second HARQ process.
  • the second HARQ process may be associated with a second UE.
  • the second UE may have a different uplink transmission bandwidth for the TDD carrier than the first UE.
  • the apparatus may include means for transmitting downlink control information to the first UE comprising an uplink resource block assignment shift for the second uplink data transmission.
  • the apparatus may include means for determining that a second UE is in communication with the base station using the TDD carrier.
  • the first UE may be a non- legacy UE that is configured according to dynamic TDD reconfiguration messaging and the second UE may be a legacy-UE configured according to semi-static TDD reconfiguration messaging.
  • the apparatus may include means for configuring the first UE to use the first TDD configuration for the first frame and the second TDD configuration for the second frame using the dynamic TDD reconfiguration messaging, and means for configuring the second UE to use a predetermined TDD configuration for the first and second frames using the semi-static TDD reconfiguration messaging.
  • Some embodiments are directed to a user equipment apparatus configured for communication with a base station over a TDD carrier.
  • the user equipment apparatus may include at least one processor configured to determine a TDD configuration transition from a first TDD configuration during a first frame to a second TDD configuration during a second frame for a TDD carrier; transmit a first uplink data transmission during a first subframe in the first frame, the first uplink data transmission being associated with a HARQ process; determine a second subframe based on HARQ indicator timing for a HARQ reference configuration, and receive downlink resources on the second subframe, the downlink resources may include ACK/NACK information associated with the HARQ process, and a memory coupled to the at least one processor
  • the second TDD configuration may be associated with HARQ retransmission information comprising synchronous retransmission offset values corresponding to a set of subframe indices.
  • the second subframe may not be within the set of subframe indices of the HARQ retransmission information for the second TDD configuration.
  • the at least one processor may be further configured to receive a NACK message associated with the HARQ process in the second subframe, and determine a third subframe for a second uplink transmission associated with the HARQ process based on transitional HARQ retransmission information.
  • the transitional HARQ retransmission information may include HARQ
  • the at least one processor may be further configured to remap the third subframe iteratively until the third subframe corresponds to an UL subframe for the second TDD configuration, the remapping performed incrementally or based on remapping rules associated with the predetermined TDD configuration.
  • the transitional HARQ retransmission information may be associated with the second TDD configuration.
  • the transitional HARQ retransmission information may include synchronous retransmission offset values corresponding to each subframe index having downlink resources.
  • Some embodiments are directed to a base station apparatus for communication with a UE over a TDD carrier.
  • the base station apparatus may include at least one processor configured to determine, for the TDD carrier, a TDD configuration transition from a first TDD configuration during a first frame to a second TDD configuration during a second frame, receive a first uplink data transmission associated with a first HARQ process on the TDD carrier during a first subframe of the first frame, determine a second subframe based on HARQ indicator timing for a HARQ reference configuration, and transmit downlink resources on the second subframe, the downlink resources comprising ACK/NACK information associated with the first HARQ process, and a memory coupled to the at least one processor.
  • the second TDD configuration may be associated with HARQ retransmission information comprising synchronous retransmission offset values corresponding to a set of subframe indices.
  • the second subframe may not be within the set of subframe indices of the HARQ retransmission information for the second TDD configuration.
  • the at least one processor may be further configured to determine a third subframe comprising uplink resources for receiving a second uplink data transmission associated with the first HARQ process based on transitional HARQ retransmission information.
  • the at least one processor may be further configured to determine that the third subframe conflicts with an uplink data transmission associated with a second HARQ process. In some embodiments, the at least one processor is configured to suspend the first HARQ process responsive to determining that the third subframe conflicts with the uplink data transmission of the second HARQ process. In some instances, the second HARQ process may be associated with a second UE. The second UE may, for example, have a different uplink transmission bandwidth for the TDD carrier than the first UE. In some embodiments, the at least one processor is configured to transmit downlink control information to the first UE that includes an uplink resource block assignment shift for the second uplink data transmission.
  • the at least one processor is configured to determine that a second UE is in communication with the base station using the TDD carrier.
  • the first UE may be a non-legacy UE configured according to dynamic TDD reconfiguration messaging while the second UE is a legacy UE configured according to semi- static TDD reconfiguration messaging.
  • the at least one processor may be configured to configure the first UE to use the first TDD configuration for the first frame and the second TDD configuration for the second frame using the dynamic TDD reconfiguration messaging and to configure the second UE to use a predetermined TDD configuration for the first and second frames using the semi-static TDD reconfiguration messaging.
  • Some embodiments are directed to a computer program product for wireless communications by a UE configured for communication with a base station over a TDD carrier.
  • the computer program product may include a non-transitory computer-readable medium that includes code for determining a TDD configuration transition from a first TDD configuration during a first frame to a second TDD configuration during a second frame for the TDD carrier, transmitting a first uplink data transmission during a first subframe in the first frame, the first uplink data transmission being associated with a HARQ process, determining a second subframe based on HARQ indicator timing for a HARQ reference configuration, and receiving downlink resources on the second subframe, the downlink resources comprising ACK/NACK information associated with the HARQ process.
  • the second TDD configuration may be associated with HARQ retransmission information comprising synchronous retransmission offset values corresponding to a set of subframe indices.
  • the second subframe may not be within the set of subframe indices of the HARQ retransmission information for the second TDD configuration.
  • the non-transitory computer-readable medium may include code for receiving a NACK message associated with the HARQ process in the second subframe of the second frame, and determining a third subframe for a second uplink transmission associated with the HARQ process based on transitional HARQ retransmission information.
  • the transitional HARQ retransmission information may include HARQ retransmission information corresponding to a predetermined TDD configuration of a limited set of TDD configurations.
  • the non-transitory computer-readable medium may include code for: remapping the third subframe iteratively until the third subframe corresponds to an UL subframe for the second TDD configuration. The remapping may be performed
  • transitional HARQ retransmission information may be associated with the second TDD configuration, and may include synchronous retransmission offset values corresponding to each subframe index having downlink resources.
  • Some embodiments are directed to a computer program product for wireless communications by a base station apparatus configured for communication with a UE over a TDD carrier.
  • the computer program product may include a non-transitory computer- readable medium including code for determining a TDD configuration transition from a first TDD configuration during a first frame to a second TDD configuration during a second frame for the TDD carrier, receiving a first uplink data transmission associated with a first HARQ process on the TDD carrier during a first subframe of the first frame, determining a second subframe based on HARQ indicator timing for a HARQ reference configuration, and transmitting downlink resources on the second subframe, the downlink resources comprising ACK/NACK information associated with the first HARQ process.
  • the second TDD configuration may be associated with HARQ retransmission information comprising synchronous retransmission offset values corresponding to a set of subframe indices.
  • the second subframe may not be within the set of subframe indices of the HARQ retransmission information for the second TDD configuration.
  • the non-transitory computer-readable medium may include code for determining a third subframe comprising uplink resources for receiving a second uplink data transmission associated with the first HARQ process based on transitional HARQ retransmission information.
  • the non-transitory computer-readable medium may include code for determining that the third subframe conflicts with an uplink data transmission associated with a second HARQ process.
  • the non-transitory computer-readable medium includes code for suspending the first HARQ process responsive to determining that the third sub frame conflicts with the uplink data transmission of the second HARQ process.
  • the second HARQ process may be associated with a second UE. The second UE may, for example, have a different uplink transmission bandwidth for the TDD carrier than the first UE.
  • the non-transitory computer-readable medium includes code for transmitting downlink control information to the first UE comprising an uplink resource block assignment shift for the second uplink data transmission.
  • a second UE may be in communication with the base station using the TDD carrier.
  • the first UE may be a non-legacy UE configured according to dynamic TDD reconfiguration messaging while the second UE may be a legacy UE configured according to semi-static TDD reconfiguration messaging.
  • the non-transitory computer-readable medium may include code for configuring the first UE to use the first TDD configuration for the first frame and the second TDD configuration for the second frame using the dynamic TDD reconfiguration messaging, and code for configuring the second UE to use a predetermined TDD configuration for the first and second frames using the semi-static TDD reconfiguration messaging.
  • FIG. 1 is a diagram illustrating an example of a wireless communications system in accordance with various embodiments
  • FIG. 2 is a timing diagram illustrating dynamic TDD reconfiguration based on DL and UL traffic loading in accordance with various embodiments
  • FIG. 3 is a timing diagram illustrating TDD reconfiguration with cross
  • FIG. 4A is a timing diagram 400 illustrating TDD reconfiguration using a predetermined reference configuration for transitional HARQ indicator timing in accordance with various embodiments;
  • FIG. 4B is a timing diagram illustrating TDD reconfiguration using the more UL- heavy of the initial and post-reconfiguration configurations as a reference configuration for transitional HARQ indicator timing in accordance with various embodiments;
  • FIG. 5 is a timing diagram illustrating example HARQ retransmission timing for TDD reconfiguration in accordance with various embodiments
  • FIG. 6 is a timing diagram illustrating TDD reconfiguration using a reference configuration for HARQ retransmission timing in accordance with various embodiments
  • FIG. 7 is a process flow for determining transitional HARQ retransmission information based on a reference configuration and subframe remapping in accordance with various embodiments
  • FIGS. 8 A and 8B illustrate tables showing synchronous retransmission offset values for transitional HARQ retransmission timing in accordance with various embodiments
  • FIG. 9 is a timing diagram illustrating TDD reconfiguration using transitional HARQ retransmission timing in accordance with various embodiments.
  • FIG. 10 is a timing diagram illustrating TDD reconfiguration using a reference configuration for transitional HARQ retransmission timing in accordance with various embodiments
  • FIGS. 11 A and 1 IB illustrate methods for transitional HARQ indicator timing in TDD reconfiguration in accordance with various embodiments
  • FIGS. 12A and 12B illustrate methods for HARQ retransmission timing in TDD reconfiguration in accordance with various embodiments
  • FIG. 13 illustrates a method for HARQ timing in TDD reconfiguration in accordance with various embodiments
  • FIG. 14 shows a block diagram of a device for transitional HARQ indicator timing in TDD reconfiguration in accordance with various embodiments
  • FIG. 15 shows a block diagram of a device for transitional HARQ indicator and retransmission timing in TDD reconfiguration in accordance with various embodiments
  • FIG. 16 shows a block diagram of a device for transitional HARQ indicator and retransmission timing in TDD reconfiguration in accordance with various embodiments
  • FIG. 17 is a block diagram of a mobile device configured for transitional HARQ indicator and retransmission timing in TDD reconfiguration in accordance with various embodiments.
  • FIG. 18 shows a block diagram of a communications system that may be configured for transitional HARQ indicator and retransmission timing for TDD reconfiguration in accordance with various embodiments
  • Described embodiments are directed to systems and methods for resolving timing issues in TDD reconfiguration for synchronous HARQ by using transitional HARQ timing (HARQ indicator timing and/or synchronous HARQ retransmission timing).
  • transitional HARQ timing HARQ indicator timing and/or synchronous HARQ retransmission timing.
  • HARQ processes with data transmissions occurring prior to TDD
  • transitional HARQ indicator timing may be based on HARQ indicator timing for one of the initial or post- reconfiguration TDD configuration, or may be based on a predetermined reference configuration.
  • cross-boundary HARQ processes may use transitional HARQ retransmission timing.
  • the transitional HARQ retransmission timing may be determined by new synchronous retransmission offset values for cross-boundary synchronous HARQ processes.
  • the new synchronous retransmission offset values may supplement the existing synchronous retransmission offset values.
  • the transitional HARQ retransmission timing may define synchronous HARQ retransmission timing for each subframe having DL resources.
  • the transitional HARQ retransmission timing for TDD reconfigurations may be determined according to the post-reconfiguration TDD configuration.
  • retransmission collisions for cross-boundary HARQ processes may be avoided by suspending HARQ retransmission and/or adaptive UL HARQ techniques.
  • a serving base station may suspend a HARQ process with a retransmission collision by transmitting an ACK even where the data associated with the HARQ process is not received correctly at the serving base station.
  • the serving base station may resume the suspended HARQ process on resources not colliding with other HARQ processes.
  • Adaptive UL HARQ may be used in retransmission collisions between HARQ processes in different devices by modifying UL transmission resources for one of the devices within the subframe subject to the collision.
  • Techniques described herein may be used for various wireless communications systems such as cellular wireless systems, Peer-to-Peer wireless communications, wireless local access networks (WLANs), ad hoc networks, satellite communications systems, and other systems.
  • WLANs wireless local access networks
  • system and “network” are often used interchangeably.
  • These wireless communications systems may employ a variety of radio communication
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal FDMA
  • Radio Access Technologies employing CDMA techniques include
  • CDMA2000 Universal Terrestrial Radio Access (UTRA), etc.
  • CDMA2000 covers IS-2000, IS-95, and IS-856 standards.
  • IS-2000 Releases 0 and A are commonly referred to as
  • IS-856 (TIA-856) is commonly referred to as CDMA2000 lxEV- DO, High Rate Packet Data (HRPD), etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. Examples of TDMA systems include various implementations of Global System for Mobile Communications (GSM). Examples of Radio Access
  • UMB Ultra Mobile Broadband
  • E-UTRA Evolved UTRA
  • Wi-Fi IEEE 802.11
  • WiMAX IEEE 802.16
  • Flash-OFDM Flash-OFDM
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS).
  • 3 GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3 GPP).
  • CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • FIG. 1 a diagram illustrates an example of a wireless
  • the system 100 includes base stations (or cells) 105, communication devices 1 15, and a core network 130.
  • the base stations 105 may be base stations (or cells) 105, communication devices 1 15, and a core network 130.
  • the base stations 105 may
  • Base stations 105 may communicate control information and/or user data with the core network 130 through backhaul links 132.
  • Backhaul links 132 may be wired backhaul links (e.g., copper, fiber, etc.) and/or wireless backhaul links (e.g., microwave, etc.).
  • the base stations 105 may communicate, either directly or indirectly, with each other over backhaul links 134, which may be wired or wireless communication links.
  • the system 100 may support operation on multiple carriers (waveform signals of different frequencies). Multi-carrier transmitters can transmit modulated signals simultaneously on the multiple carriers.
  • each communication link 125 may be a multi-carrier signal modulated according to the various radio technologies described above.
  • Each modulated signal may be sent on a different carrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, data, etc.
  • the base stations 105 may wirelessly communicate with the devices 1 15 via one or more base station antennas. Each of the base station 105 sites may provide communication coverage for a respective coverage area 110.
  • base stations 105 may be referred to as a base transceiver station, a radio base station, an access point, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a NodeB, eNodeB (eNB), Home NodeB, a Home eNodeB, or some other suitable terminology.
  • the coverage area 1 10 for a base station may be divided into sectors making up only a portion of the coverage area (not shown).
  • the system 100 may include base stations 105 of different types (e.g., macro, micro, and/or pico base stations). There may be overlapping coverage areas for different technologies.
  • the communication devices 1 15 are dispersed throughout the wireless network 100, and each device may be stationary or mobile.
  • a communication device 1 15 may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a user equipment, a mobile client, a client, or some other suitable terminology.
  • a communication device 1 15 may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, or the like.
  • a communication device may be able to communicate with macro base stations, pico base stations, femto base stations, relay base stations, and the like.
  • the transmission links 125 shown in network 100 may include uplink (UL) transmissions from a mobile device 1 15 to a base station 105, and/or downlink (DL) transmissions, from a base station 105 to a mobile device 1 15.
  • the downlink transmissions may also be called forward link transmissions while the uplink transmissions may also be called reverse link transmissions.
  • the transmission links 125 are TDD carriers carrying bidirectional traffic within traffic frames.
  • the system 100 is an LTE/LTE-A network.
  • LTE/LTE-A networks the terms evolved Node B (eNB) and user equipment (UE) may be generally used to describe the base stations 105 and communication devices 1 15, respectively.
  • the system 100 may be a Heterogeneous LTE/LTE-A network in which different types of eNBs provide coverage for various geographical regions.
  • each eNB 105 may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider.
  • a pico cell would generally cover a relatively smaller geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider.
  • a femto cell would also generally cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, and the like).
  • An eNB for a macro cell may be referred to as a macro eNB.
  • An eNB for a pico cell may be referred to as a pico eNB.
  • an eNB for a femto cell may be referred to as a femto eNB or a home eNB.
  • An eNB may support one or multiple (e.g., two, three, four, and the like) cells.
  • the communications system 100 may be referred to as an Evolved Packet System (EPS) 100.
  • the EPS 100 may include one or more UEs 1 15, an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), an Evolved Packet Core (EPC) 130 (e.g., core network 130), a Home Subscriber Server (HSS), and an Operator's IP Services.
  • E-UTRAN Evolved UMTS Terrestrial Radio Access Network
  • EPC Evolved Packet Core
  • HSS Home Subscriber Server
  • the EPS may interconnect with other access networks using other Radio Access Technologies.
  • EPS 100 may interconnect with a UTRAN- based network and/or a CDMA-based network via one or more Serving GPRS Support Nodes (SGSNs).
  • SGSNs Serving GPRS Support Nodes
  • EPS 100 may support handover of UEs 1 15 between a source eNB 105 and a target eNB 105.
  • EPS 100 may support intra-RAT handover between eNBs 105 and/or base stations of the same RAT (e.g., other E-UTRAN networks), and inter-RAT handovers between eNBs and/or base stations of different RATs (e.g., E-UTRAN to CDMA, etc.).
  • the EPS 100 may provide packet-switched services, however, as those skilled in the art will readily appreciate, the various concepts presented throughout this disclosure may be extended to networks providing circuit-switched services.
  • the E-UTRAN may include the eNBs 105 and may provide user plane and control plane protocol terminations toward the UEs 1 15.
  • the eNBs 105 may be connected to other eNBs 105 via backhaul link 134 (e.g., an X2 interface, and the like).
  • the eNBs 105 may provide an access point to the EPC 130 for the UEs 1 15.
  • the eNBs 105 may be connected by backhaul link 132 (e.g., an S I interface, and the like) to the EPC 130.
  • Logical nodes within EPC 130 may include one or more Mobility Management Entities (MMEs), one or more Serving Gateways, and one or more Packet Data Network (PDN) Gateways (not shown).
  • MMEs Mobility Management Entities
  • PDN Packet Data Network Gateways
  • the MME may provide bearer and connection management. All user IP packets may be transferred through the Serving Gateway, which itself may be connected to the PDN Gateway.
  • the PDN Gateway may provide UE IP address allocation as well as other functions.
  • the PDN Gateway may be connected to IP networks and/or the operator's IP
  • the IP Networks/Operator's IP Services may include the Internet, an Intranet, an IP Multimedia Subsystem (IMS), and/or a Packet- Switched (PS) Streaming Service (PSS).
  • IMS IP Multimedia Subsystem
  • PS Packet- Switched
  • PSS Packet- Switched
  • the UEs 115 may be configured to collaboratively communicate with multiple eNBs 105 through, for example, Multiple Input Multiple Output (MIMO), Coordinated Multi-Point (CoMP), or other schemes. MIMO techniques use multiple antennas on the base stations and/or multiple antennas on the UE to take advantage of multipath environments to transmit multiple data streams.
  • MIMO Multiple Input Multiple Output
  • CoMP Coordinated Multi-Point
  • CoMP includes techniques for dynamic coordination of transmission and reception by a number of eNBs to improve overall transmission quality for UEs as well as increasing network and spectrum utilization.
  • CoMP techniques utilize backhaul links 132 and/or 134 for communication between base stations 105 to coordinate control plane and user plane communications for the UEs 115.
  • the communication networks may be packet-based networks that operate according to a layered protocol stack.
  • communications at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP -based.
  • PDCP Packet Data Convergence Protocol
  • a Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels.
  • RLC Radio Link Control
  • the MAC layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer may also use hybrid automatic repeat request (HARQ) techniques to provide retransmission at the MAC layer to ensure reliable data transmission.
  • the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between the UE and the network used for the user plane data.
  • the transport channels may be mapped to Physical channels.
  • the downlink physical channels may include at least one of a physical downlink control channel (PDCCH), a physical HA Q indicator channel (PHICH), and a physical downlink shared channel (PDSCH).
  • PDCCH physical downlink control channel
  • PHICH physical HA Q indicator channel
  • PDSCH physical downlink shared channel
  • the uplink physical channels may include at least one of a physical uplink control channel (PUCCH) and a physical uplink shared channel (PUSCH).
  • the PDCCH may carry downlink control information (DCI), which may indicate data transmissions for UEs on the PDSCH as well as provide UL resource grants to UEs for the PUSCH.
  • DCI downlink control information
  • the UE may transmit control information in the PUCCH on the assigned resource blocks in the control section.
  • the UE may transmit only data or both data and control information in the PUSCH on the assigned resource blocks in the data section.
  • LTE/LTE-A utilizes orthogonal frequency division multiple-access (OFDMA) on the downlink and single-carrier frequency division multiple-access (SC-FDMA) on the uplink.
  • OFDMA orthogonal frequency division multiple-access
  • SC-FDMA single-carrier frequency division multiple-access
  • An OFDMA and/or SC-FDMA carrier may be partitioned into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, or the like. Each subcarrier may be modulated with data.
  • the spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth.
  • K may be equal to 72, 180, 300, 600, 900, or 1200 with a subcarrier spacing of 15 kilohertz (KHz) for a corresponding system bandwidth (with guardband) of 1.4, 3, 5, 10, 15, or 20 megahertz (MHz), respectively.
  • the system bandwidth may also be partitioned into sub-bands. For example, a sub-band may cover 1.08 MHz, and there may be 1 , 2, 4, 8 or 16 sub-bands.
  • the carriers may transmit bidirectional communications using FDD (e.g. , using paired spectrum resources) or TDD operation (e.g., using unpaired spectrum resources).
  • FDD e.g. , using paired spectrum resources
  • TDD operation e.g., using unpaired spectrum resources.
  • Frame structures for FDD (e.g., frame structure type 1) and TDD (e.g., frame structure type 2) may be defined.
  • each subframe may carry UL or DL traffic, and special sub frames ("S") may be used to switch between DL to UL transmission.
  • S special sub frames
  • Allocation of UL and DL subframes within radio frames may be symmetric or asymmetric and may be reconfigured semi-statically (e.g., via backhaul messaging over SI and/or X2 interfaces, etc.).
  • Special sub frames may carry some DL and/or UL traffic and may include a Guard Period (GP) between DL and UL traffic. Switching from UL to DL traffic may be achieved by setting timing advance at the UEs without the use of Special subframes or a guard period between UL and DL subframes.
  • GP Guard Period
  • TDD configurations with switch-point periodicity equal to the frame period (e.g., 10 ms) or half of the frame period (e.g., 5 ms) may be supported.
  • TDD frames may include one or more Special frames, and the period between Special frames may determine the TDD DL-to-UL switch-point periodicity for the frame.
  • LTE/LTE-A uses asynchronous HARQ transmission on the downlink and synchronous HARQ transmission on the uplink.
  • synchronous UL HARQ upon transmitting on the PUSCH during a subframe n, the UE may determine a PHICH subframe n+kpHicH for receiving ACK/NACK information associated with the PUSCH transmission, where kp H icn is given in Table 2.
  • the UE may automatically ⁇ e.g., no explicit grant is required) retransmit on PUSCH resources.
  • the UE may determine a PUSCH subframe n+kpusc H for retransmission, where kpuscn is given in Table 3.
  • Retransmission may be assigned the same MCS and coding rate as the initial transmission.
  • rapidly changing traffic conditions may be accommodated through flexible TDD reconfiguration for TDD carriers.
  • Such flexible TDD reconfiguration may occur semi-statically (e.g., transmitted in system information, paging messages, C signaling, etc.) or dynamically (e.g., MAC layer signaling, PHY layer signaling, etc.).
  • Dynamic TDD reconfiguration may occur on the order of a single frame or several frames (e.g., 10 ms, 50 ms, etc.). These and other techniques for flexible TDD reconfiguration may be included in "enhanced Interference Management and Traffic Adaptation” (elMTA), which may be implemented in some networks.
  • elMTA enhanced Interference Management and Traffic Adaptation
  • UEs that are capable of operating according to elMTA are referred to herein as non- legacy UEs, and UEs that are not capable of operating according to elMTA are referred to herein as legacy UEs.
  • an eNB may be in communication with both legacy UEs and non-legacy UEs, and thus signaling between the UEs and eNB must be provided to allow the legacy UEs to operate properly while also allowing dynamic reconfiguration for non-legacy UEs as well as other related signaling, such as HARQ acknowledgements, to be carried out between the UEs and an eNB.
  • a downlink sub frame in an established TDD configuration such as indicated in System Information Block 1 (SIB1), cannot be changed to an uplink subframe, as such a change may result in a Radio Resource Management (RRM) measurement and/or periodic Channel State Information (CSI) reporting problem.
  • RRM Radio Resource Management
  • CSI Channel State Information
  • An eNB operating according to elMTA may, however, modify scheduling information for legacy UEs and configure resources to certain uplink subframes in order to "blank" UL subframes that are reconfigured to be downlink subframes in non-legacy UEs.
  • FIG. 2 is a timing diagram 200 illustrating dynamic TDD reconfiguration based on DL and UL traffic loading in accordance with various embodiments.
  • Timing diagram 200 shows several frames 210 for a TDD carrier 205.
  • traffic loading may be heavier for DL transmissions and the TDD carrier 205 may be configured in frames 210-a and 210-b for a TDD configuration that favors DL traffic flow over UL traffic flow (e.g., TDD configuration 2, etc.).
  • the traffic loading may change and UL loading may be heavier than UL loading in frame 210-a, or even heavier than DL loading.
  • TDD reconfiguration 215 illustrates that the eNB 105 may reconfigure TDD carrier 205 for TDD configuration 0 in frame 210-c.
  • TDD carrier 205 may remain configured in TDD configuration 0 for frame 210-d while DL loading has now increased again to warrant TDD reconfiguration 220 back to TDD configuration 2 for frames 210-e and 210-f.
  • the expected PHICH resources for a HARQ process associated with a transmission (or retransmission) in an initial TDD configuration may be mapped (e.g., based on kpnic H for the initial TDD configuration, etc.) to an UL subframe in the post-reconfiguration TDD configuration.
  • the expected PHICH resources for the cross-boundary HARQ process fall in a DL subframe in the post-reconfiguration TDD configuration
  • the DL subframe may not be defined for PHICH in the post-reconfiguration TDD configuration and therefore synchronous HARQ retransmission behavior may be indeterminate.
  • the different aspects of system 100 such as the eNBs 105 and UEs 1 15, may be configured to resolve timing issues in TDD reconfiguration for synchronous HARQ by using transitional HARQ timing (HARQ indicator timing and/or synchronous HARQ retransmission timing).
  • transitional HARQ timing HARQ indicator timing and/or synchronous HARQ retransmission timing.
  • HARQ processes with data transmissions occurring prior to TDD reconfiguration may use transitional HARQ indicator timing.
  • the transitional HARQ indicator timing may be based on HARQ indicator timing for one of the initial or post-reconfiguration TDD configuration, or may be based on a predetermined reference configuration.
  • cross-boundary HARQ processes may use transitional HARQ retransmission timing.
  • the transitional HARQ retransmission timing may be determined by new synchronous retransmission offset values for cross-boundary synchronous HARQ processes.
  • the new synchronous retransmission offset values may supplement the existing synchronous retransmission offset values.
  • the transitional HARQ retransmission timing may define synchronous HARQ retransmission timing for each subframe having DL resources.
  • the transitional HARQ retransmission timing for TDD reconfigurations may be determined according to the post-reconfiguration TDD configuration.
  • retransmission collisions for cross-boundary HARQ processes may be avoided by suspending HARQ retransmission and/or adaptive UL HARQ techniques.
  • a serving base station may suspend a HARQ process with a retransmission collision by transmitting an ACK even where the data associated with the HARQ process is not received correctly at the serving base station.
  • the serving base station may resume the suspended HARQ process on resources not colliding with other HARQ processes.
  • Adaptive UL HARQ may be used in retransmission collisions between HARQ processes in different devices by modifying UL transmission resources for one of the devices within the subframe subject to the collision.
  • FIG. 3 is a timing diagram 300 illustrating TDD reconfiguration with cross configuration boundary HARQ processes in accordance with various embodiments.
  • a TDD carrier 305 is configured in TDD configuration 2 in a first frame 310-a and is reconfigured to TDD configuration 1 in a second frame 310-b.
  • Timing diagram 300 illustrates two HARQ processes 320-a and 320-b, each transmitting UL data on PUSCH resources during frame 310-a.
  • PUSCH transmission 325-a for HARQ process 320-a occurs in subframe 2 of frame 310-a and ACK/NACK information 330-a is received (according to HARQ indicator timing 340 for TDD configuration 2) in subframe 8 of frame 310-a.
  • PUSCH transmission 325-b occurs in subframe 7 of frame 310-a.
  • ACK/NACK information 330-b should be received in subframe 3 of frame 310-b.
  • subframe 3 of TDD configuration 1 is an UL subframe where the eNB 105 does not transmit PHICH resources.
  • HARQ indicator timing for TDD reconfiguration may use a reference configuration to map ACK/NACK information to PHICH resources on DL subframes.
  • the reference configuration may be a predetermined reference configuration for all TDD reconfiguration combinations or may be determined from one of the pre- and post- reconfiguration TDD configurations.
  • FIG. 4A is a timing diagram 400-a illustrating TDD reconfiguration using a predetermined reference configuration for transitional HARQ indicator timing in accordance with various embodiments. Similarly to FIG. 3, FIG. 4A illustrates TDD reconfiguration from TDD configuration 2 in a first frame 410-a to TDD configuration 1 in a second frame 410-b for a TDD carrier 405-a. In FIG. 4A, HARQ indicator timing for PUSCH
  • transmissions (or retransmissions) in frame 410-a is based on kpnic H for a reference configuration.
  • the reference configuration may be, for example, the TDD configuration with the highest number of UL sub frames ⁇ e.g., TDD configuration 0).
  • PUSCH transmission 425-a for HARQ process 420-a occurs in subframe 2 of frame 410-a and ACK/NACK information 430-a is received (according to HARQ indicator timing 440-a for TDD configuration 0) in subframe 6 of frame 410-a.
  • PUSCH transmission 425-b occurs in subframe 7 of frame 410-a and ACK/NACK information 430-b is received in subframe 1 of frame 410-b.
  • HARQ processes 420-a and 420-b both schedule ACK/NACK information 430 for DL or special subframes for which the eNB can transmit the ACK/NACK information via PHICH resources. Because kpnic H for TDD configuration 0 maps all PHICH transmissions for all UL subframes of the available TDD configurations to common DL subframes, this reference configuration may be used for all combinations of TDD reconfiguration to map PHICH transmissions to DL subframes.
  • FIG. 4B is a timing diagram 400-b illustrating TDD reconfiguration using the more UL-heavy of the initial and post-reconfiguration configurations as a reference configuration for transitional HARQ indicator timing in accordance with various embodiments.
  • HARQ indicator timing for PUSCH transmissions (or retransmissions) in frame 410-c is based on kpnicH for the more UL-heavy of the pre- (TDD configuration 2 for frame 410-c) and the post-reconfiguration configurations (TDD configuration 1 for frame 410-d) for the TDD carrier 405 -b.
  • Timing diagram 400-b results in similar HARQ indicator timing as timing diagram 400-a, with PUSCH transmission 425-c for HARQ process 420-c in subframe 2 of frame 410-c and ACK/NACK information 430-c received (according to HARQ indicator timing 440-b for TDD configuration 1) in subframe 6 of frame 410-c.
  • PUSCH transmission 425-d occurs in subframe 7 of frame 410-c and ACK/NACK information 430-d is received in subframe 1 of frame 410-d.
  • Other options for transitional HARQ indicator timing include various combinations of reference configurations and/or the pre- and post-reconfiguration configurations.
  • HARQ indicator timing may be based on kpHicn for the more UL-heavy TDD configuration, with kpnic H for subframes that are UL subframes in the first configuration but DL subframes in the second configuration determined by kpHicn for the first configuration.
  • HARQ indicator timing may be based on kpnic H for the more UL-heavy TDD configuration for reconfigurations with both first and second configurations having the same TDD period, and based on TDD configuration 0 for other reconfiguration combinations.
  • synchronous HARQ processes automatically retransmit on UL resources determined by an offset value from the sub frame in which ACK/NACK
  • FIG. 5 is a timing diagram 500 illustrating example HARQ retransmission timing for TDD reconfiguration in accordance with various embodiments.
  • TDD carrier 505 is reconfigured from TDD configuration 1 in a first frame 510-a to TDD configuration 2 in a second frame 510-b.
  • HARQ indicator timing for PUSCH transmissions or
  • transitional HARQ indicator timing 540 ⁇ e.g., kpnic H for reference TDD
  • PUSCH transmission 525-b for HARQ process 520-b may occur in subframe 3 of frame 510-a and ACK/NACK information 530-b may be received in subframe 0 of frame 510-b.
  • subframe 0 does not have an associated kpuscn timing offset value for HARQ
  • HARQ retransmission timing is mapped according to transitional HARQ indicator timing 540, that fall on subframe indexes of frame 510-b without defined kpuscn timing offset values for HARQ retransmissions.
  • a reference configuration may be used to define transitional HARQ retransmission timing. It can be appreciated that using the same reference
  • transitional HARQ indicator timing and transitional HARQ retransmission timing will result in ACK/NACK information mapping to subframe indexes with defined HARQ retransmission timing for the reference configuration.
  • using a reference configuration for transitional HARQ retransmission timing may result in throughput loss as some retransmission mappings from the reference configuration may fall on DL subframes of the post-reconfiguration TDD configuration.
  • FIG. 6 is a timing diagram 600 illustrating TDD reconfiguration using a reference configuration for HARQ retransmission timing in accordance with various embodiments.
  • TDD carrier 605 is reconfigured from TDD configuration 1 in a first frame 610-a to TDD configuration 2 in a second frame 610-b.
  • HARQ indicator timing for PUSCH transmissions (or retransmissions) for HARQ processes 620-a, 620-b, 620-c, and/or 620-d in frame 610-a is based on transitional HARQ indicator timing 640 (e.g., kp H icn for reference TDD configuration 0).
  • PUSCH transmission 625-a for HARQ process 620-a may occur in subframe 2 of frame 610-a and ACK/NACK information 630-a may be received in subframe 6 of frame 610-a.
  • transitional HARQ retransmission timing 650 e.g., kpuscn for reference TDD configuration 0
  • PUSCH retransmission 635-a may be scheduled for subframe 2 of frame 610-b.
  • PUSCH transmission 625-b may occur in subframe 3 of frame 610-a, while ACK/NACK information 630-b may be received in subframe 0 of frame 610-b.
  • transitional HARQ retransmission timing 650 e.g., kpuscn for reference TDD configuration 0
  • PUSCH retransmission 635-a may be scheduled for subframe 2 of frame 610-b.
  • PUSCH transmission 625-b may occur in subframe 3 of frame 610-a
  • retransmission 635 -b may be scheduled for subframe 4 of frame 610-b.
  • subframe 4 of frame 610-b is a DL subframe for TDD configuration 2.
  • HARQ process 620-b may need to be dropped because of unsuccessful scheduling of PUSCH retransmission 635-b. Similar issues may occur to HARQ process 620-d.
  • the throughput loss for cross- boundary HARQ timing for TDD reconfiguration from TDD configuration 1 to TDD configuration 2 may be 50%, as illustrated in FIG. 6.
  • TDD reconfiguration may experience similar throughput losses using TDD configuration 0 as a reference configuration transitional HARQ
  • reconfiguration from TDD configuration 4 to TDD configuration 5 may result in a throughput loss of 50%
  • reconfiguration from TDD configuration 1 to TDD configuration 4 may result in a throughput loss of 75%.
  • transitional HARQ retransmission timing may be based on a reference configuration and remapped to UL subframes.
  • FIG. 7 is a process flow 700 for determining transitional HARQ retransmission information based on a reference
  • Process flow 700 may be used, for example, by the UEs 115 and/or eNBs 105 illustrated in FIG. 1. Process flow 700 may be used for TDD reconfiguration between any combination of TDD configurations.
  • Process flow 700 begins at block 705 which may correspond to receiving or transmitting ACK/NACK information for a cross-boundary HARQ process.
  • a subframe for UL HARQ retransmission for the HARQ process is determined based on a reference configuration.
  • the reference configuration may be, for example, TDD configuration 0 or TDD configuration 6.
  • the UE 115 and/or eNB 105 determine whether the subframe conflicts with a DL subframe. If the subframe selected for UL HARQ retransmission conflicts with a DL subframe, the subframe may be remapped to the next subframe at block 720. Remapping of the subframe at block 720 may be performed incrementally or according to remapping rules. For rules-based remapping, a subframe index n may be remapped to a subframe index m according to rules for each reference configuration.
  • the rules may remap subframe index n to subframe index m according to n ⁇ m : ⁇ 2 ⁇ 3, 3 ⁇ 4, 4 ⁇ 7, 7 ⁇ 8, 8 ⁇ 9, 9 ⁇ 2 ⁇ .
  • the rules may specify remappings according to n ⁇ m : ⁇ 2 ⁇ 3, 3 ⁇ 4, 4 ⁇ 7, 7 ⁇ 8, 8 ⁇ 2 ⁇ .
  • Blocks 715 and 720 may be performed iteratively until the subframe maps to an UL subframe.
  • the HARQ retransmission may be scheduled on the PUSCH for the subframe (with or without remapping in blocks 715 and 720) and the process may complete at block 730.
  • transitional HARQ retransmission timing may be based on newly defined synchronous retransmission offset values.
  • FIG. 8A illustrates a table 800-a showing synchronous retransmission offset values for transitional HARQ retransmission timing in accordance with various embodiments.
  • table 800-a existing synchronous retransmission offset values 805 (no shading) are supplemented with newly defined synchronous retransmission offset values 810 (shaded).
  • table 800-a may define kpusc H for transitional HARQ retransmission timing and may eliminate throughput loss due to UL HARQ retransmission mapping to DL subframes as can occur with use of a reference configuration.
  • Table 800-a includes several options for ACK/NACK information received in some subframe indexes and transitional HARQ retransmission timing may be defined according to any of various combinations of the options provided.
  • any of the above synchronous retransmission offset values 805, 810 may be offset by one or more frames (e.g. , 10 subframes, etc.) to reduce the chance of PUSCH collisions.
  • FIG. 8B illustrates a table 800-b showing alternative synchronous retransmission offset values for transitional HARQ retransmission timing in accordance with various embodiments.
  • synchronous retransmission offset values 810-a, 810-b, and/or 810-c may be offset by an additional frame to reduce PUSCH collision probability with other HARQ processes.
  • FIG. 9 is a timing diagram 900 illustrating TDD reconfiguration using transitional HARQ retransmission timing in accordance with various embodiments.
  • TDD carrier 905 is reconfigured from TDD configuration 1 in a first frame 910-a to TDD configuration 2 in second and third frames 910-b and 910-c .
  • HARQ indicator timing for PUSCH transmissions (or retransmissions) for HARQ processes 920-a, 920-b, 920-c, and/or 920-d in frame 910-a is based on transitional HARQ indicator timing 940 (e.g. , kp H icn for reference TDD configuration 0).
  • HARQ retransmission timing 950 for HARQ processes 920-a, 920-b, 920-c, and/or 920-d is based on k PU sc H _TR for the post- reconfiguration TDD configuration (e.g., TDD configuration 2 in FIG. 9).
  • PUSCH transmission 925-b for HARQ process 920-b may occur in subframe 3 of frame 910-a and ACK/NACK information 930-b may be received in subframe 0 of frame 910-b.
  • transitional HARQ retransmission timing 950 e.g., kpusc H for TDD configuration 2
  • PUSCH retransmission 935-b may be scheduled for subframe 7 of frame 910-b.
  • HARQ processes 920-a, 920-c, and/or 920-d may have synchronous HARQ retransmissions scheduled according to transitional HARQ retransmission timing 950.
  • transitional HARQ retransmission timing according to the techniques illustrated in FIGS. 8A, 8B, and/or 9 can be used in combination with other techniques for mapping HARQ indicator information.
  • the techniques described with reference to FIG. 8A, FIG. 8B, and/or FIG. 9 may be used in combination with using the more UL-heavy of the pre- and post-transition
  • FIG. 10 is a timing diagram 1000 illustrating TDD reconfiguration using a reference configuration for transitional HARQ retransmission timing in accordance with various embodiments.
  • TDD carrier 1005 is reconfigured from TDD configuration 1 in a first frame 1010-a to TDD configuration 2 in second and third frames 1010-b and 1010-c.
  • HARQ indicator timing for PUSCH transmissions (or retransmissions) for HARQ processes 1020-a, 1020-b, 1020-c, and/or 1020-d in frame 1010-a is based on transitional HARQ indicator timing 1040 (e.g., kp H icn for reference TDD configuration 0).
  • Transitional HARQ retransmission timing 1050 may be based on kpuscn for TDD configuration 6, using the remapping techniques described above with reference to FIG. 7.
  • PUSCH retransmissions 1035-a and 1035-b for HARQ processes 1020-a and 1020-b may both be scheduled for subframe 7 of frame 1010-b.
  • PUSCH retransmissions 1035-c and 1035-d for HARQ processes 1020-c and 1020-d may both be scheduled for subframe 2 of frame 1010-c.
  • eNBs 105 may be configured to avoid PUSCH collisions by suspending HARQ processes or using PDCCH based adaptive HARQ techniques.
  • UL HARQ processes may be suspended by the eNB 105 by transmitting an ACK (e.g., even when the data transmission is not decoded correctly). Because data in buffers at the UE for HARQ processes is maintained until allocation of a grant for a new set of data (e.g., new transport block, etc.) The HARQ process may be resumed by an appropriate UL resource grant (e.g., using the new data indicator field of an uplink resource grant).
  • PDDCH based adaptive HA Q may be used to avoid the PUSCH collision.
  • one or both UEs with a PUSCH collision may be sent an UL resource grant for the collision subframe specifying a different resource allocation (e.g., different resource blocks, etc.).
  • a different resource allocation e.g., different resource blocks, etc.
  • this technique may be applied where resource allocations for each UE are relatively narrow bandwidth allocations (e.g., less than half of available resource blocks, etc.).
  • elMTA networks may support, over the same TDD carrier as non-legacy UEs, legacy UEs that do not receive signaling and/or messaging that dynamically reconfigures the TDD carrier.
  • the eNB may dynamically reconfigure TDD operation for the non-legacy UEs while signaling a default configuration to the legacy UEs using system information (e.g., SIB1).
  • SIB1 system information
  • PHICH resources may be backward compatible for TDD configuration 0
  • legacy UEs may be signaled in this TDD configuration while TDD operation for non-legacy UEs may be dynamically reconfigured and the techniques described above applied for HARQ timing in non-legacy UEs.
  • FIG. 11A illustrates a method 1 100-a for transitional HARQ indicator timing in TDD reconfiguration in accordance with various embodiments.
  • Method 1 100-a may be used, for example, by UEs 1 15 (or individual HARQ processes in UEs 1 15) in system 100 illustrated in FIG. 1.
  • Method 1 100-a may be performed, for example, by each UL HARQ process of the UEs 1 15.
  • the UE 1 15 may determine a TDD reconfiguration for a TDD carrier used for communication with an eNB 105. For example, a semi-static or dynamic
  • the reconfiguration message may reconfigure the TDD carrier from a first TDD configuration in a first frame to a second TDD configuration in a second frame.
  • the UE 1 15 may transmit data on a first subframe of the first frame for a HARQ process at block 1 1 10.
  • the transmission may be, for example, transmission of new data (e.g., a new transport block) or a HARQ retransmission based on receiving a NACK for a previous transmission.
  • the UE 1 15 may determine scheduling of a second subframe for receiving ACK/NACK information for the HARQ process based on transitional HARQ indicator information.
  • the transitional HARQ indicator information may be, for example, HARQ indicator information from a reference configuration or from the more UL-heavy configuration of the pre- and post-reconfiguration TDD configurations as described above with reference to FIGS 4 A and 4B.
  • the UE may receive ACK/NACK information for the HARQ process in the second sub frame at block 1 120.
  • the ACK/NACK information may indicate, for example, that a retransmission is necessary (e.g., NACK) for the HARQ process or that the data has been received and decoded correctly (e.g., ACK).
  • FIG. 11B illustrates a method 1 100-b for performing transitional HARQ indicator timing in TDD reconfiguration in accordance with various embodiments.
  • Method 1 100-b may be used, for example, by eNBs 105 (or individual HARQ processes in eNBs 105) in system 100 illustrated in FIG. 1.
  • Method 1 100-b may be performed, for example, by each UL HARQ process of the eNBs 105.
  • the eNB 105 may determine a TDD reconfiguration for a TDD carrier used for communication with one or more UEs 1 15. For example, the eNB 105 may determine a reconfiguration of the TDD carrier from a first TDD configuration in a first frame to a second TDD configuration in a second frame. The eNB 105 may send the reconfiguration to the one or more UEs 115 (e.g., system information signaling, RRC layer signaling, MAC layer signaling, PHY layer signaling, etc.).
  • the one or more UEs 115 e.g., system information signaling, RRC layer signaling, MAC layer signaling, PHY layer signaling, etc.
  • the eNB 105 may receive data on a first subframe of the first frame for a HARQ process at block 1 130.
  • the received data may be, for example, new data (e.g., a new transport block) or a HARQ retransmission based on transmission by the eNB of a NACK for a previous transmission.
  • the eNB 105 may determine scheduling of a second subframe for transmitting ACK/NACK information for the HARQ process based on transitional HARQ indicator information.
  • the transitional HARQ indicator information may be, for example, HARQ indicator information from a reference configuration or from the more UL-heavy configuration of the pre- and post-reconfiguration TDD configurations as described above with reference to FIGS 4 A and 4B.
  • the eNB may transmit ACK/NACK information for the HA Q process in the second sub frame at block 1 140.
  • the ACK/NACK information may indicate, for example, whether the data received at block 1 130 was received and decoded correctly.
  • FIG. 12A illustrates a method 1200-a for HARQ retransmission timing in TDD reconfiguration in accordance with various embodiments.
  • Method 1200-a may be used, for example, by UEs 1 15 (or individual HARQ processes in UEs 1 15) in system 100 illustrated in FIG. 1.
  • Method 1200-a may be performed, for example, by each UL HARQ process of the UEs 1 15.
  • the UE 1 15 may determine a TDD reconfiguration for a TDD carrier used for communication with an eNB 105. For example, the UE 1 15 may receive a semi-static or dynamic reconfiguration message that reconfigures the TDD carrier from a first TDD configuration in a first frame to a second TDD configuration in a second frame.
  • the UE may receive a NACK from the eNB 105 associated with a first data transmission for a HARQ process at block 1210.
  • the UE determines scheduling of a subframe for retransmission for the HARQ process based on transitional HARQ retransmission information.
  • the UE determines scheduling of the subframe based on HARQ retransmission timing for a reference configuration (e.g. , TDD configuration 0, etc.).
  • the HARQ retransmission timing for the reference configuration is remapped to UL subframes using incremental remapping or rules-based remapping as described above with reference to FIG. 7.
  • the UE determines scheduling of the subframe based on transitional HARQ retransmission timing defined according to the post-reconfiguration TDD configuration. For example, the UE may determine the scheduling for the subframe based on tables 800-a and/or 800-b of FIGS. 8A and/or 8B.
  • the UE transmits the second data transmission for the HARQ process on the subframe at block 1220.
  • FIG. 12B illustrates a method 1200-b for HARQ retransmission timing in TDD reconfiguration in accordance with various embodiments.
  • Method 1200-b may be used, for example, by eNBs 105 (or individual HARQ processes in eNBs 105) in system 100 illustrated in FIG. 1.
  • Method 1200-b may be performed, for example, by each UL HARQ process of the eNBs 105.
  • the eNB 105 may determine a TDD reconfiguration for a TDD carrier used for communication with one or more UEs 1 15.
  • the eNB 105 may determine a reconfiguration of the TDD carrier from a first TDD configuration in a first frame to a second TDD configuration in a second frame.
  • the eNB 105 may send the reconfiguration to the one or more UEs 115 (e.g., system information signaling, RRC layer signaling, MAC layer signaling, PHY layer signaling, etc.).
  • the eNB 105 may transmit a NACK associated with a first data transmission for a HARQ process at block 1230.
  • the eNB 105 determines scheduling of a sub frame for retransmission for the HARQ process by the UE 1 15 based on transitional HARQ retransmission information.
  • the eNB 105 determines scheduling of the sub frame based on HARQ retransmission timing for a reference configuration (e.g. , TDD configuration 0, etc.).
  • the HARQ retransmission timing for the reference configuration is remapped to UL subframes using incremental remapping or rules-based remapping as described above with reference to FIG. 7.
  • the eNB 105 determines scheduling of the sub frame based on transitional HARQ retransmission timing defined according to the post-reconfiguration TDD configuration. For example, the eNB 105 may determine the scheduling for the subframe based on tables 800-a and/or 800-b of FIGS. 8 A and/or 8B. The eNB receives the second data transmission for the HARQ process in the subframe at block 1240.
  • FIG. 13 illustrates a method 1300 for HARQ timing in TDD reconfiguration in accordance with various embodiments. Method 1300 may be used, for example, by eNBs 105 (or individual HARQ processes in eNBs 105) in system 100 illustrated in FIG. 1. Method 1300 may be performed, for example, by each UL HARQ process of the eNBs 105.
  • the eNB 105 may determine a TDD reconfiguration for a TDD carrier used for communication with one or more UEs 1 15. For example, the eNB 105 may determine a reconfiguration of the TDD carrier from a first TDD configuration in a first frame to a second TDD configuration in a second frame. The eNB 105 may send the reconfiguration to the one or more UEs 115 (e.g., system information, RRC layer signaling, MAC layer signaling, PHY layer signaling, etc.). [0135] The eNB 105 may receive data on a first subframe of the first frame for a HARQ process at block 1310. The received data may be, for example, new data (e.g., a new transport block) or a HARQ retransmission based on transmission by the eNB of a NACK for a previous transmission.
  • new data e.g., a new transport block
  • a HARQ retransmission based on transmission by the eNB of a N
  • the eNB 105 may determine that the data received at block 1310 has failed to decode (e.g., CRC fail, etc.).
  • the eNB 105 may determine scheduling of a second subframe for transmitting ACK/NACK information for the HARQ process based on transitional HARQ indicator information.
  • the transitional HARQ indicator information may be, for example, HARQ indicator information from a reference configuration or from the more UL-heavy configuration of the pre- and post-reconfiguration TDD configurations as described above with reference to FIGS. 4A and 4B.
  • the eNB 105 determines scheduling of a third subframe for retransmission for the HARQ process by the UE 1 15 based on transitional HARQ
  • the transitional HARQ retransmission information may be a reference configuration (with or without re-mapping to UL subframes) or based on tables (e.g., table 800-a and/or 800-b, etc.) according to the post-reconfiguration TDD
  • the eNB 105 may determine if the third subframe will have a PUSCH collision with other PUSCH transmissions (e.g., other HARQ processes of the same UE or HARQ processes of other UEs). If the PUSCH transmission has a collision with another HARQ process at block 1330, the eNB may use techniques in one of the alternative paths of execution of method 1300 illustrated in dashed outline. In one technique, the eNB may suspend the HARQ process at block 1335 to avoid the PUSCH transmission collision. Suspending the HARQ process may include transmitting an ACK on the second subframe even though the data transmission failed decode at block 1315.
  • other HARQ processes of the same UE or HARQ processes of other UEs may use techniques in one of the alternative paths of execution of method 1300 illustrated in dashed outline. In one technique, the eNB may suspend the HARQ process at block 1335 to avoid the PUSCH transmission collision. Suspending the HARQ process may include transmitting an ACK on the second
  • the eNB may resume the HARQ process on open PUSCH resources (e.g., using an appropriate UL resource grant, etc.) at block 1340.
  • the eNB may use PDCCH based adaptive HARQ techniques at block 1345 to avoid the PUSCH transmission collision.
  • the eNB 105 may transmit an UL resource grant to the UE 1 15 to modify or shift the resource blocks used by the UE for retransmission for the HARQ process.
  • FIG. 14 shows a block diagram of a device 1400 for transitional HARQ indicator timing in TDD reconfiguration in accordance with various embodiments.
  • Device 1400 may illustrate, for example, aspects of UEs 1 15 illustrated in FIG. 1.
  • Device 1400 may include TDD configuration transition module 1410, UL HARQ transmitter 1420, UL HARQ
  • TDD configuration transition module 1410 may determine a TDD reconfiguration for a TDD carrier used for communication between, for example, the device 1400 and an eNB 105.
  • the TDD configuration transition module 1410 may determine the TDD reconfiguration based on signaling from the eNB 105 (e.g. , system information signaling, RRC layer signaling, MAC layer signaling, PHY layer signaling, etc.).
  • the TDD reconfiguration may reconfigure the TDD carrier from a first TDD configuration in a first frame to a second TDD configuration in a second frame.
  • the TDD reconfiguration may be semi-static or dynamic.
  • UL HARQ transmitter 1420 may transmit data on a first subframe of the first frame for a HARQ process.
  • the transmission may be, for example, transmission of new data (e.g., a new transport block) or a HARQ retransmission based on receiving a NACK for a previous transmission.
  • UL HARQ indicator scheduling module 1440 may determine scheduling of a second subframe for receiving ACK/NACK information for the HARQ process based on transitional HARQ indicator information.
  • the transitional HARQ indicator information may be, for example, HARQ indicator information from a reference configuration or from the more UL-heavy configuration of the pre- and post-reconfiguration TDD configurations as described above with reference to FIGS 4 A and 4B.
  • UL HARQ ACK/NACK receiver 1430 may receive ACK/NACK information for the HARQ process in the second subframe.
  • the ACK/NACK information may indicate, for example, that a retransmission is necessary (e.g. , NACK) for the HARQ process or that the data has been received and decoded correctly (e.g., ACK).
  • FIG. 15 shows a block diagram of a device 1500 for transitional HARQ indicator and retransmission timing in TDD reconfiguration in accordance with various embodiments.
  • Device 1500 may illustrate, for example, aspects of UEs 1 15 illustrated in FIG. 1.
  • Device 1500 may include TDD configuration transition module 1410-a, UL HARQ transmitter 1420-a, UL HARQ ACK/NACK receiver 1430-a, UL HARQ indicator scheduling module 1440-a, and/or UL HARQ Retransmission Scheduling Module 1550. Each of these components may be in communication with each other.
  • the TDD configuration transition module 1410-a, UL HARQ transmitter 1420-a, UL HARQ ACK/NACK receiver 1430-a, and UL HARQ indicator scheduling module 1440-a may perform the functions of the TDD configuration transition module 1410, UL HARQ transmitter 1420, UL HARQ ACK/NACK receiver 1430, and UL HARQ indicator scheduling module 1440 described above.
  • the UL HARQ Retransmission Scheduling Module 1550 may, upon receipt by the UL HARQ ACK/NACK receiver 1430-a of a NACK from the eNB 105 associated with a first data transmission for a HARQ process, determine scheduling of a subframe for retransmission for the HARQ process based on transitional HARQ retransmission
  • the UL HARQ Retransmission Scheduling Module 1550 determines scheduling of the subframe based on HARQ retransmission timing for a reference configuration (e.g., TDD configuration 0, etc.). In embodiments, the HARQ retransmission timing for the reference configuration is remapped to UL subframes using incremental remapping or rules-based remapping as described above with reference to FIG. 7. In embodiments, the UL HARQ Retransmission Scheduling Module 1550 determines scheduling of the subframe based on transitional HARQ retransmission timing defined according to the post-reconfiguration TDD configuration.
  • a reference configuration e.g., TDD configuration 0, etc.
  • the HARQ retransmission timing for the reference configuration is remapped to UL subframes using incremental remapping or rules-based remapping as described above with reference to FIG. 7.
  • the UL HARQ Retransmission Scheduling Module 1550 determines scheduling of the subframe based on transitional HAR
  • the UL HARQ Retransmission Scheduling Module 1550 may determine the scheduling for the subframe based on tables 800-a and/or 800-b of FIGS. 8A and/or 8B.
  • the UL HARQ transmitter 1420- a may transmit the second data transmission for the HARQ process on the subframe.
  • FIG. 16 shows a block diagram of a device 1600 for transitional HARQ indicator and retransmission timing in TDD reconfiguration in accordance with various embodiments.
  • Device 1600 may illustrate, for example, aspects of eNBs 105 illustrated in FIG. 1.
  • Device 1600 may include TDD configuration transition module 1610, UL HARQ receiver 1620, UL HARQ indicator scheduling module 1630, UL HARQ ACK/NACK transmitter 1640, UL HARQ retransmission scheduling module 1650, UL decoder 1660, and/or UL HARQ retransmission collision avoidance module 1670. Each of these components may be in communication with each other.
  • TDD configuration transition module 1610 may determine a TDD reconfiguration for a TDD carrier used for communication with one or more UEs 1 15. For example, the TDD configuration transition module 1610 may determine a reconfiguration of the TDD carrier from a first TDD configuration in a first frame to a second TDD configuration in a second frame. The device 1600 may send the reconfiguration to the one or more UEs 1 15 (e.g., system information signaling, RRC layer signaling, MAC layer signaling, PHY layer signaling, etc.).
  • the one or more UEs 1 15 e.g., system information signaling, RRC layer signaling, MAC layer signaling, PHY layer signaling, etc.
  • UL HARQ receiver 1620 may receive data on a first subframe of the first frame for a HARQ process.
  • the received data may be, for example, new data (e.g. , a new transport block) or a HARQ retransmission based on transmission by the eNB of a NACK for a previous transmission.
  • UL HARQ indicator scheduling module 1630 may determine scheduling of a second subframe for transmitting ACK/NACK information for the HARQ process based on transitional HARQ indicator information.
  • the transitional HARQ indicator information may be, for example, HARQ indicator information from a reference configuration or from the more UL-heavy configuration of the pre- and post-reconfiguration TDD configurations as described above with reference to FIGS. 4A and 4B.
  • UL HARQ ACK/NACK transmitter 1640 may transmit ACK/NACK information for the HARQ process in the second subframe.
  • the ACK/NACK information may indicate, for example, whether the data was received and decoded correctly by UL decoder 1660.
  • UL HARQ retransmission scheduling module 1650 may, if UL decoder 1660 determines that the data was not received correctly, determine scheduling of a subframe for retransmission for the HARQ process based on transitional HARQ retransmission information.
  • the UL HARQ retransmission scheduling module 1650 determines scheduling of the subframe based on HARQ retransmission timing for a reference configuration (e.g., TDD configuration 0, etc.). In embodiments, the HARQ retransmission timing for the reference configuration is remapped to UL subframes using incremental remapping or rules-based remapping as described above with reference to FIG. 7. In embodiments, the UL HARQ retransmission scheduling module 1650 determines scheduling of the subframe based on transitional HARQ retransmission timing defined according to the post-reconfiguration TDD configuration.
  • a reference configuration e.g., TDD configuration 0, etc.
  • the HARQ retransmission timing for the reference configuration is remapped to UL subframes using incremental remapping or rules-based remapping as described above with reference to FIG. 7.
  • the UL HARQ retransmission scheduling module 1650 determines scheduling of the subframe based on transitional HARQ re
  • the UL HARQ retransmission scheduling module 1650 may determine the scheduling for the subframe based on tables 800- a and/or 800-b of FIGS. 8A and/or 8B.
  • the UL HARQ receiver 1620 may receive the second data transmission for the HARQ process on the subframe.
  • UL HARQ retransmission collision avoidance module 1670 may avoid scheduling collisions on the PUSCH by suspending HARQ processes or using PDCCH based adaptive HARQ techniques.
  • UL HARQ processes may be suspended by the eNB 105 by transmitting an ACK (e.g., even when the data transmission is not decoded correctly).
  • PDDCH based adaptive HARQ may be used to avoid the PUSCH collision by sending an UL resource grant to one or both specifying a different resource allocation (e.g., different resource blocks, etc.).
  • FIG. 17 is a block diagram 1700 of a mobile device 1 15 -a configured for transitional HARQ indicator and retransmission timing in TDD reconfiguration in accordance with various embodiments.
  • the mobile device 1 15-a may have any of various
  • the mobile device 1 15-a may have an internal power supply (not shown), such as a small battery, to facilitate mobile operation.
  • the mobile device 1 15-a may be the mobile devices 1 15 of FIG. 1.
  • the mobile device 1 15-a may generally include components for bi-directional voice and data communications including components for transmitting communications and components for receiving communications.
  • the mobile device 1 15-a may include a transceiver module 1710, antenna(s) 1705, memory 1780, and a processor module 1770, which each may communicate, directly or indirectly, with each other (e.g. , via one or more buses).
  • the transceiver module 1710 is configured to communicate bi-directionally, via the antenna(s) 1705 and/or one or more wired or wireless links, with one or more networks, as described above.
  • the transceiver module 1710 may be configured to
  • the transceiver module 1710 may include a modem configured to modulate the packets and provide the modulated packets to the antenna(s) 1705 for transmission, and to demodulate packets received from the antenna(s) 1705. While the mobile device 1 15-a may include a single antenna 1705, the mobile device 1 15-a may have multiple antennas 1705 capable of concurrently transmitting and/or receiving multiple wireless transmissions. The transceiver module 1710 may be capable of concurrently communicating with multiple eNBs 105 via multiple component carriers.
  • the memory 1780 may include random access memory (RAM) and read-only memory (ROM).
  • the memory 1780 may store computer-readable, computer-executable software/firmware code 1785 containing instructions that are configured to, when executed, cause the processor module 1770 to perform various functions described herein (e.g., call processing, database management, capture of handover delay, etc.).
  • the software/firmware code 1785 may not be directly executable by the processor module 1770 but be configured to cause a computer (e.g. , when compiled and executed) to perform functions described herein.
  • the processor module 1770 may include an intelligent hardware device, e.g., a central processing unit (CPU) such as those made by Intel® Corporation or AMD®, a microcontroller, an application-specific integrated circuit (ASIC), etc.
  • the mobile device 1 15-a may include a speech encoder (not shown) configured to receive audio via a microphone, convert the audio into packets (e.g., 20 ms in length, 30 ms in length, etc.) representative of the received audio, provide the audio packets to the transceiver module 1710, and provide indications of whether a user is speaking.
  • a speech encoder not shown
  • the mobile device 1 15-a may further include communications management module 1760, handover module 1765, TDD configuration transition module 1410-b, UL HARQ transmitter 1420-b, UL HARQ
  • ACK/NACK receiver 1430-b may be components of the mobile device 1 15-a in communication with some or all of the other components of the mobile device 1 15-a via a bus.
  • functionality of these modules may be implemented as a component of the transceiver module 1710, as a computer program product, and/or as one or more controller elements of the processor module 1770.
  • handover module 1765 may be utilized to perform handover procedures of the mobile device 1 15-a from one base station 105 to another.
  • the handover module 1765 may perform a handover procedure of the mobile device 1 15-a from one base station to another where voice and/or data communications are being received from the base stations.
  • the mobile device 1 15-a may be configured transmit and receive data using transitional HARQ indicator and retransmission timing for TDD reconfiguration as described above.
  • the components for mobile device 1 15-a may be configured to implement aspects discussed above with respect to UEs 1 15 of FIG. 1 and/or devices 1400 and/or 1500 of FIG. 14 and/or FIG. 15.
  • the TDD configuration transition module 1410-b, UL For example, the TDD configuration transition module 1410-b, UL
  • HARQ transmitter 1420-b, UL HARQ ACK/NACK receiver 1430-b, UL HARQ indicator scheduling module 1440-b, and/or UL HARQ Retransmission Scheduling Module 1550-a may be, respectively, examples of the TDD configuration transition module 1410, UL HARQ transmitter 1420, UL HARQ ACK/NACK receiver 1430, UL HARQ indicator scheduling module 1440, and/or UL HARQ Retransmission Scheduling Module 1550 of FIG. 14 and/or FIG. 15.
  • FIG. 18 shows a block diagram of a communications system 1800 that may be configured for transitional HARQ indicator and retransmission timing for TDD
  • This system 1800 may be an example of aspects of the system 100 depicted in FIG. 1.
  • the system 1800 includes a base station 105-a configured for communication with UEs 1 15 over wireless communication links 125.
  • Base station 105-a may be capable of receiving communication links 125 from other base stations (not shown).
  • Base station 105-a may be, for example, an eNB 105 as illustrated in system 100.
  • the base station 105-a may have one or more wired backhaul links.
  • Base station 105-a may be, for example, a macro eNB 105 having a wired backhaul link (e.g., S I interface, etc.) to the core network 130-a.
  • Base station 105-a may also communicate with other base stations 105, such as base station 105-m and base station 105-n via inter-base station communication links (e.g., X2 interface, etc.). Each of the base stations 105 may communicate with UEs 1 15 using different wireless communications technologies, such as different Radio Access Technologies. In some cases, base station 105-a may communicate with other base stations such as 105-m and/or 105-n utilizing base station communication module 1815. In some embodiments, base station communication module 1815 may provide an X2 interface within an LTE/LTE-A wireless communication network technology to provide communication between some of the base stations 105. In some embodiments, base station 105 -a may communicate with other base stations through core network 130-a. In some cases, the base station 105-a may communicate with the core network 130-a through network communications module 1865.
  • base station 105-a may communicate with other base stations through core network 130-a. In some cases, the base station 105-a may communicate with the core network 130-a
  • the components for base station 105-a may be configured to implement aspects discussed above with respect to base stations 105 of FIG. 1 and/or device 1600 of FIG. 16 may not be repeated here for the sake of brevity.
  • the TDD configuration transition module 1610-a, UL HARQ receiver 1620-a, UL HARQ indicator scheduling module 1630-a, UL HARQ ACK/NACK transmitter 1640-a, UL HARQ retransmission scheduling module 1650-a, UL decoder 1660-a, and/or UL HARQ retransmission collision avoidance module 1670-a may be, respectively, examples of the TDD configuration transition module 1610, UL HARQ receiver 1620, UL HARQ indicator scheduling module 1630, UL HARQ ACK/NACK transmitter 1640, UL HARQ retransmission scheduling module 1650, UL decoder 1660, and/or UL HARQ retransmission collision avoidance module 1670 of FIG. 16.
  • the base station 105-a may include antennas 1845, transceiver modules 1850, memory 1870, and a processor module 1860, which each may be in communication, directly or indirectly, with each other (e.g., over bus system 1880).
  • the transceiver modules 1850 may be configured to communicate bi-directionally, via the antennas 1845, with the UEs 1 15, which may be multi-mode devices.
  • the transceiver module 1850 (and/or other components of the base station 105-a) may also be configured to communicate bi-directionally, via the antennas 1845, with one or more other base stations (not shown).
  • the transceiver module 1850 may include a modem configured to modulate the packets and provide the modulated packets to the antennas 1845 for transmission, and to demodulate packets received from the antennas 1845.
  • the base station 105-a may include multiple transceiver modules 1850, each with one or more associated antennas 1845.
  • the memory 1870 may include random access memory (RAM) and read-only memory (ROM).
  • the memory 1870 may also store computer-readable, computer-executable software code 1875 containing instructions that are configured to, when executed, cause the processor module 1860 to perform various functions described herein (e.g., call processing, database management, message routing, etc.).
  • the software 1875 may not be directly executable by the processor module 1860 but be configured to cause the computer, e.g. , when compiled and executed, to perform functions described herein.
  • the processor module 1860 may include an intelligent hardware device, e.g., a central processing unit (CPU) such as those made by Intel® Corporation or AMD®, a microcontroller, an application-specific integrated circuit (ASIC), etc.
  • the processor module 1860 may include various special purpose processors such as encoders, queue processing modules, base band processors, radio head controllers, digital signal processors (DSPs), and the like.
  • the base station 105-a may further include a communications management module 1830.
  • the communications management module 1830 may manage communications with other base stations 105.
  • the communications management module may include a controller and/or scheduler for controlling
  • the communications management module 1830 may perform scheduling for transmissions to UEs 115 and/or various interference mitigation techniques such as beamforming and/or joint transmission.
  • the communications management module 1830 may perform scheduling for transmissions to UEs 115 and/or various interference mitigation techniques such as beamforming and/or joint transmission.
  • Information and signals may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor may be a
  • processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • Computer-readable media includes both computer storage media and
  • a storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.
  • computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special- purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • Disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne la gestion de temps des indicateurs HARQ et des retransmissions pour la reconfiguration TDD dans les systèmes de communication sans fil. La gestion de temps des indicateurs HARQ pour la reconfiguration TDD peut reposer sur la gestion de temps des indicateurs HARQ pour une configuration TDD de pré-reconfiguration ou bien de post-reconfiguration, ou peut reposer sur une configuration de référence prédéterminée. La gestion de temps des retransmissions HARQ pour la reconfiguration TDD peut être déterminée par des configurations de référence prédéterminées et peut comporter un remappage avec la configuration TDD de post-reconfiguration. La gestion de temps des retransmissions HARQ peut reposer sur une gestion de temps transitionnelle pour les retransmissions HARQ définissant une gestion de temps synchrone pour les retransmissions HARQ pour chaque sous-trame possédant des ressources de liaison descendante. On peut éviter les collisions de retransmission pour les procédés HARQ en suspendant les retransmissions HARQ et/ou en utilisant des techniques HARQ de liaison montante adaptatives. Ces techniques peuvent être appliquées aux systèmes de communication sans fil tels que les réseaux de gestion d'interférences et d'adaptation de trafic améliorés (eIMTA).
PCT/CN2013/000367 2013-03-29 2013-03-29 Conception de gestion des temps harq pour frontière de reconfiguration en eimta WO2014153688A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/000367 WO2014153688A1 (fr) 2013-03-29 2013-03-29 Conception de gestion des temps harq pour frontière de reconfiguration en eimta

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/000367 WO2014153688A1 (fr) 2013-03-29 2013-03-29 Conception de gestion des temps harq pour frontière de reconfiguration en eimta

Publications (1)

Publication Number Publication Date
WO2014153688A1 true WO2014153688A1 (fr) 2014-10-02

Family

ID=51622336

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/000367 WO2014153688A1 (fr) 2013-03-29 2013-03-29 Conception de gestion des temps harq pour frontière de reconfiguration en eimta

Country Status (1)

Country Link
WO (1) WO2014153688A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107040344A (zh) * 2016-02-04 2017-08-11 宏碁股份有限公司 处理混合自动重传请求传送的装置及方法
US10582508B2 (en) 2015-03-31 2020-03-03 At&T Intellectual Property I, L.P. Facilitation of network resources
CN113273292A (zh) * 2019-01-10 2021-08-17 索尼集团公司 通信设备、操作通信设备的方法、基础设施设备以及方法
US20220159668A1 (en) * 2019-04-04 2022-05-19 FG Innovation Company Limited Method and apparatus for operating configured grant timers in wireless communication system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102150389A (zh) * 2008-09-10 2011-08-10 高通股份有限公司 用于在无线通信系统中管理新数据指示符的方法和设备
CN102752090A (zh) * 2011-04-22 2012-10-24 北京三星通信技术研究有限公司 一种支持pusch的同步harq传输的方法
WO2012162877A1 (fr) * 2011-05-30 2012-12-06 Renesas Mobile Corporation Procédé, appareil et élément de réseau pour une configuration tdd dynamique

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102150389A (zh) * 2008-09-10 2011-08-10 高通股份有限公司 用于在无线通信系统中管理新数据指示符的方法和设备
CN102752090A (zh) * 2011-04-22 2012-10-24 北京三星通信技术研究有限公司 一种支持pusch的同步harq传输的方法
WO2012162877A1 (fr) * 2011-05-30 2012-12-06 Renesas Mobile Corporation Procédé, appareil et élément de réseau pour une configuration tdd dynamique

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10582508B2 (en) 2015-03-31 2020-03-03 At&T Intellectual Property I, L.P. Facilitation of network resources
CN107040344A (zh) * 2016-02-04 2017-08-11 宏碁股份有限公司 处理混合自动重传请求传送的装置及方法
EP3211813A3 (fr) * 2016-02-04 2017-11-15 Acer Incorporated Dispositif et procédé de gestion de transmission de demande de répétition automatique hybride
TWI669928B (zh) * 2016-02-04 2019-08-21 宏碁股份有限公司 處理混合自動重傳請求傳送的裝置及方法
US11452091B2 (en) 2016-02-04 2022-09-20 Acer Incorporated Device and method of handling hybrid automatic repeat request transmission
CN113273292A (zh) * 2019-01-10 2021-08-17 索尼集团公司 通信设备、操作通信设备的方法、基础设施设备以及方法
US12101761B2 (en) 2019-01-10 2024-09-24 Sony Group Corporation Communications devices, methods of operating communications devices, infrastructure equipment and methods
US20220159668A1 (en) * 2019-04-04 2022-05-19 FG Innovation Company Limited Method and apparatus for operating configured grant timers in wireless communication system
US12120727B2 (en) * 2019-04-04 2024-10-15 FG Innovation Company Limited Method and apparatus for operating configured grant timers in wireless communication system

Similar Documents

Publication Publication Date Title
KR102313331B1 (ko) Fdd-tdd 캐리어 어그리게이션을 위한 감소된 지연 harq 프로세스 타임라인
JP6768685B2 (ja) 簡略化されたｈａｒｑ管理
EP3213446B1 (fr) Canal physique de contrôle descendant (pdcch) à deux étages à drapeau dci et indicateur de taille et format dci
KR102427581B1 (ko) 동적 ｔｄｄ ｄｌ／ｕｌ 서브프레임 구성을 이용한 캐리어 집성
CA2922189C (fr) Agregation de porteuses fdd-tdd simplifiee
EP2946627B1 (fr) Procédés et appareil de reconfiguration hybride permettant une adaptation tdd
US10959216B2 (en) Multiple transmission time interval coordination with time division duplexing
EP3459194B1 (fr) Émissions découplées de retour de qualité de canal et retour d'accusé de réception/accusé de réception négatif
EP3216148B1 (fr) Réduction du temps de traitement pour une transmission et une réception à faible temps d'attente
WO2014166060A1 (fr) Signalisation destinée à indiquer la configuration de sous-trame de liaison montante-liaison descendante de drt dans la technologie lte
WO2014153688A1 (fr) Conception de gestion des temps harq pour frontière de reconfiguration en eimta
WO2014113902A1 (fr) Déplacement d'uci et nouvelle temporisation pusch permettant de lutter contre le brouillage dl-ul dans l'eimta
WO2015018073A1 (fr) Groupage et multiplexage d'a/n hybride en eimta
WO2014110690A1 (fr) Procédé, appareil, et produit programme d'ordinateur permettant de déterminer des ressources sur la liaison montante pour transmettre un harq-ack dans une reconfiguration tdd ul-dl

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13880272

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13880272

Country of ref document: EP

Kind code of ref document: A1